The director can now deploy an Amazon EC2 API. The steps for including the ec2-api service in a deployment must be documented. Comment from awaugama: "The test case is that when you install a system, you include the ec2-api template which installs and sets up the feature. The documentation (in my opinion) should cover the install/including the template, and then all the settings the template changes on the OPS System."
Assigning to Dan for review. Dan to assess what documentation is required for this feature.
Changing target release to OSP 11. If this is in our 11 program it needs to turn up in our 11 program BZ list.
Pasting part of comment 3 here (since it wasn't marked 'Private' originally, and only moved to that status because of an internal link): "EC2-API will not be supported in GA, because an important upstream fix came in to late. It will be fixed in a future update. We need to document that in the release notes or similar, so that customers don't upgrade to OSP11 before that update is released." Dan, adding a needinfo on you as a reminder to check whether there are any places in the director docs that might need a warning added. If not, and the Release Notes fix is merged, we can close this bug.
I think I might need to temporarily remove the EC2-API reference from the composable role page. Other than that, I think this BZ is good to close.
The changes for this bug are now published: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/release_notes/#idm139781412795552 Moving to CLOSED.