Hey guys ! - Sorry to hear this. - Im home now from paternity leave, and am spending a little more time now at my machine. - Ive renamed this JIRA. https://issues.apache.org/jira/browse/BIGTOP-1286 to codify this task to create a new CI. - We can recover.
... And when we do bigtop will be better : Its time to build a new, modern immutable CI for the BigTop ecosystem ... I feel bad for all the hard work you guys lost on this, but there is in some ways a silver lining : *** We will now release bigtop 0.8.0 with a first class, fresh CI that is coherent and up to date. *** On Fri, Sep 12, 2014 at 12:42 PM, Andrew Bayer <[email protected]> wrote: > No idea, and I don't seem to actually have the keys. > > A. > > On Fri, Sep 12, 2014 at 9:35 AM, Roman Shaposhnik <[email protected]> wrote: > > > Hi! > > > > in an extremely unfortunate turn of events it seems that > > we have just suffered the biggest outage ever in the > > entire history of Bigtop CI :-( > > > > All. I repeat ALL of our Amazon EC2 VMs are now gone. > > > > It'll take us quite some time to recover :-( Bigtop 0.8.0 > > is... well... delayed again. > > > > Now for the uncomfortable bit: given that all of our > > infrastructure is gone for good makes me suspect > > that perhaps it wasn't an Amazon outage, but > > a buggy application of EC2 APIs. There are only > > a few folks (you know who you are) with > > access to Bigtop Amazon keys. If you think there > > could be something, anything that may possible > > contribute to this mystery -- please contact me. > > > > Way to start a Fri :-( > > > > Thanks, > > Roman. > > > > On Wed, Sep 10, 2014 at 2:20 PM, Alexander Denissov > > <[email protected]> wrote: > > > http://bigtop01.cloudera.org:8080/ is not responding, anyone knows > what > > is > > > going on ? > > > > > > --Alex > > > -- jay vyas
