ceph version 14.2.3-349-g7b1552ea82 (7b1552ea827cf5167b6edbba96dd1c4a9dc16937) nautilus (stable)
salt-run osd.remove $id
uses ceph-volume lvm zap --osd-id $id --destroy to zap a disk remotely on the minion.
In previous releases we expected a string Zapping successful for OSD in the return message.
With this release we get: --> Zapping: /dev/ceph-a8e4a78d-e3....
Since there are no significant changes that would indicate a change in the return string I assume it's due to the changes in logging in recent commits. mlogger vs terminal.success
This raises the question if invoking shell commands is the right way when we have an python api to use. A couple of things need to be verified though.
- Is the zap command consumable via the API
- Does it return meaningful messages
- Is it more efficient since it needs to be wrapped in a minion module to be called from the master (via a runner)
ceph version 14.2.3-349-g7b1552ea82 (7b1552ea827cf5167b6edbba96dd1c4a9dc16937) nautilus (stable)
salt-run osd.remove $iduses
ceph-volume lvm zap --osd-id $id --destroyto zap a disk remotely on the minion.In previous releases we expected a string
Zapping successful for OSDin the return message.With this release we get:
--> Zapping: /dev/ceph-a8e4a78d-e3....Since there are no significant changes that would indicate a change in the return string I assume it's due to the changes in logging in recent commits. mlogger vs terminal.success
This raises the question if invoking shell commands is the right way when we have an python api to use. A couple of things need to be verified though.