Sounds like this LED flashing business is going to evolve. I'll let you guys know when I have a first pass implementation in play...you can tell me which future pieces I might've forgotten to take into account. Really, really great info. I think the key takeaway for me is to see how much I can get done in Ceph by itself, and involve Calamari and Calamari-clients only when necessary. At least to start. -----Original Message----- From: John Spray [mailto:john.spray@xxxxxxxxxx] Sent: Wednesday, April 01, 2015 5:08 PM To: Mark Nelson; Handzik, Joe; ceph-devel@xxxxxxxxxxxxxxx Subject: Re: Advice for implementation of LED behavior in Ceph ecosystem On 01/04/2015 23:04, John Spray wrote: > On 01/04/2015 22:57, Mark Nelson wrote: >> It seems to me that the OSD potentially would flash the LED on it's >> way down if it thinks it's drive is dead/dying? > That's a good idea for the case where ceph-osd is proactively > identifying a failing drive. I'm also thinking about the case where > we come back from a reboot and a drive is sufficiently unreadable that > ceph-disk doesn't see the OSD partitions and ceph-osd never gets > started, or the OSD's local filesystem is unmountable. Because the > keyring lives on that local filesystem, OSDs couldn't phone home in > that case, even to report a failure. Sorry, mental lapse: we're not talking about phoning home, we're talking about flashing the LED. So perhaps ceph-disk itself could be modified to flash an LED on a drive if it has a GPT partition ID for a ceph osd but we can't mount it or start an OSD service. John -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
