Comment Re:It *WAS* a Design Issue! (Score 1) 139
- as mentioned, the cables should not be able to be connected wrong - different connectors, different cable lengths, etc.
- there should have be QA steps that ensured these were done correctly
- there should have been checkouts at the factory, the engine test or at the launch site to verify correct connectivity (or all three for expensive payloads).
This appears to be a rookie mistake that we had to learn early on at one of the rocket startups I worked at. There is no excuse to make this kind of mistake at a mature aerospace company, and based on what was shared, it is not cool that they would claim it was human error. It was design, process, checkout and lastly, human error. This appear to be scapegoating from everything I read and appears to be a systemic issue that management should step up and own
Comment Re:How do you back up Ceph? (Score 5, Informative) 18
(Inktank community guy here)
There are a number of different options for backup/disaster recovery solutions with Ceph, depending on what piece(s) of the platform you are using. For instance, the object gateways (think S3) from multiple clusters can be plugged together for multi-site replication. The CephFS and block device portions both have snapshotting built in that can be replicated offsite.
In the medium-term we're looking at having a way to replicate your entire cluster over the wire at the RADOS level (underlying object store). Longer-term we'd love to be able to offer WAN-scale replication for a single cluster and the ability to snapshot a cluster (or portions/pools therein) easily.
I hope that helps. If you have more questions hit me up on #ceph at OFTC.net IRC.
Comment Re:What it needs is some beef (Score 1) 152
- * Native API
- * Via a RESTful interface that can handle native Amazon S3 and Swift API calls
- * As a thinly provisioned block device
- * Mount it as a POSIX-compliant file system via CephFS (although this is a bit rough for production environments just yet)
Josh Durgin has actually done some really interesting work in using the block device (RBD) to back Cinder which you can read a bit about here.
The cool part about Ceph is it was designed to be massively scalable (petabytes and beyond) and extremely fault tolerant / HA / etc. DreamHost actually just built out a huge production deployment of Ceph and OpenStack for their new DreamCompute / DreamObjects offering. If you have questions feel free to hit up the #Ceph irc channel at irc.oftc.net or poke me via email (my UN at inktank.com) and I'll see if I can't find the right person to help.
OpenStack really has some awesome potential, and we're excited about poking at it more with our semi-sharp Ceph-stick. Good luck.
Comment Storage advancements in the kernel? (Score -1, Redundant) 460
(full disclosure: I work for Inktank now, the consulting/services company that employs most of the core Ceph engineers)
Comment Storage advancements in the kernel? (Score 2) 460
(full disclosure: I work for Inktank now, the consulting/services company that employs most of the core Ceph engineers)
Submission + - Intel and Micron Unveil 128Gb 20nm NAND Flash (arstechnica.com)
Submission + - Stack Exchange Website Profiler Now Open Source (samsaffron.com)
Submission + - Mainstream Media Looks at Anonymous (guardian.co.uk)
Comment Re:Do nothing (Score 1) 709
Submission + - Startups a Safer Bet Than Behemoths (techcrunch.com)
Bluetooth 4.0 Devices To Make the Scene Later This Year 48
Microsoft "Courier" Pictures 230
Submission + - Couple raises virtual child.. and starves real one (cnn.com)