Description of problem: RHS-C needs to be manually deployed and attached to the Ceph cluster built by OSPd for the OSP10 release. RHS-c will be utilized as the day 2 manager for the Ceph cluster. The documentation for this process needs to be created and tested for the OSP10 release. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: A complete document of a validated process will be supplied. Additional info:
Anjana, will you be taking care of this?
Why can't console be deployed as a qcow/VM? this would greatly simplify the process
We indeed expect the deployment to be based on a QCOW image, but the process to download/import into OSP will not be automated in the 10 release. Hence we need a bit of documentation to walk the customer through this process. Assumption is the customer has a Ceph entitlement via having purchased OSP, or via having purchased RHCS. They need to download the Qcow image, put it in the right place in OSP, and launch it (via Horizon or other OSP mechanism).
*** Bug 1365990 has been marked as a duplicate of this bug. ***
*** Bug 1291948 has been marked as a duplicate of this bug. ***
Changing target release to OSP12, hopefully we can get QE coverage in that release.
OSP10 EOL'd [1] and Storage Console has been replaced with newer alternatives. And as per BZ 1790754 OSPd is able to deploy these alternatives so I'm marking this bug as a duplicate. [1] https://access.redhat.com/support/policy/updates/openstack/platform *** This bug has been marked as a duplicate of bug 1790754 ***
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days