Description of problem: Currently Customers who wants to put a node into maintenance mode need to follow set of instructions in chapter 17 of https://access.redhat.com/documentation/en/red-hat-ceph-storage/1.3/red-hat-ceph-administration-guide/part-v-adding-and-removing-osd-nodes. Since this is a common procedure for node replacement and FW upgrade having a tool that help with it will be beneficial. Version-Release number of selected component (if applicable): 1.3 How reproducible: N/A Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I do not have access to Ceph 2.0 documentation. Assuming little changes for putting node into maintenance mode for Ceph 2.x the ask is for a new command of type ceph fw-update --"url for gw version" --user -- password where last two parameters are optional credential for FW access. The script will cycle thru every node in OSD cluster, take one node at a time into maintenance mode and update FW to specified version. Leave it to implementer to disable cluster rebuild or not during update. Script will calculate that it has sufficient spare capacity in a cluster to do it. I recommend that operation is async since it takes long time to do. For extra bonus an extra command to check the status of fw-update and shows percentage of nodes update and current node under update. Ditto for UI for Ceph.
Arkady, Please take a look at https://bugzilla.redhat.com/show_bug.cgi?id=1464945. Does this accomplish what you're looking for?
Closing as duplicate due to lack of response from originator. *** This bug has been marked as a duplicate of bug 1464945 ***
It is not a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1464945. This BZ is not specific to disk replacement even though some of the steps used in https://bugzilla.redhat.com/show_bug.cgi?id=1464945 will be applicable here. Documentation will be very different. One need a generic way to put node in a maintenance mode. The goal is to minimize data transfer and potentially create a new states for a node - not available. For maintenance mode we know that we will bring the node back on line, so it should not be treated as failure. Once in a maintenance mode once can what is required. For example, update FW or BIOS on a node or for any of its components, replace any component, like disk or NIC or processors, or even motherboard. Some specific steps maybe required depending what components were replaced. Reopening.
So it sounds like you're looking for a host-wide equivalent of the "ceph osd add-noout" command? Is there any behaviour you're looking for other than for the OSDs on a particular host to not be marked out?
I have closed this issue because it has been inactive for some time now. If you feel this still deserves attention feel free to reopen it.