Bug 1963244

The idea is to have a quick reference of what the workflow looked like in ceph-ansible vs how the workflow now looks like with cephadm. That's mostly targeted at users that are already familiar with ceph-ansible now need a way to quickly jump on cephadm without reading the full RHCS docs.

Hi,

1) In all places where we mention about site.yml, site-container.yml as site.yml was only for containerized cluster
2) In third row, 
>> Run the gather ceph logs playbook. 
has been compared to 
>> Run the journalctl command.

I don't think its comparable, playbook collects logs file from all nodes to admin node, but journalctl just displays logs in a particular node
I've initiated a conversation in cephadm deployment chat room
3)[optional]  in multiple instances of mention about shrink-<daemon> , daemon are mentioned in capital letters, would be nice if it can be mentioned in lower case to follow original name
4) in row 'Block device mirroring' column 2 can be edited to 
>> `Run the site.yml/site-container.yml playbook. `
As 1) following convention in other parts of the same section 2) users would need to run playbooks adter editing inventory file
5) in row 'Upgrading from Red Hat Ceph Storage 4 to Red Hat Ceph Storage 5 ' , third column should say not supported as rhcs 4.x cluster cannot be upgraded to rhcs 5.x using cephadm

Please let me know if there are any concerns.

Regards,
Vasishta Shastry
QE, Ceph