Hide Forgot
Description of problem: Replace(Node, Osd, mons) This is just a logical extension of remove a service and create a new one Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
From mail thread Ju Lim says: " I followed-up with Kyle Bader offline regarding the disk replacement requirement, and his recommendation is to to do a remove and then add vs. 1:1 replacement (of recycling osd id and key). --- Excerpt from discussion with Kyle: Although you might be able to recycle an osd id and it's key, it's probably a pain to do and totally not worth it. ssh ${osdhost} sudo killall osd.1 ssh ${osdhost} mount|grep osd.1|awk '{print $1}'|xargs sudo umount ceph osd rm osd.1 ceph osd crush rm osd.1 ceph osd auth del osd.1 ssh ${osdhost} sudo ceph-disk prepare /dev/sdx ssh ${osdhost} sudo ceph-disk activate /dev/sdx1 ... Hope this helps clarify the direction. Thanks, Ju" So we're not planning on doing anything special here. Does it make sense to have this endpoint can we solve this by just having Red Hat Storage Controller issuing deletes then configures ?
Talked with Dusmant, If we deliver this feature USM will be responsible for