Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Support for all-in-one API deployment: RHV+OSP (+CFME) (+OCP) #83

Open
wants to merge 9 commits into
base: master
Choose a base branch
from
Open

[WIP] Support for all-in-one API deployment: RHV+OSP (+CFME) (+OCP) #83

wants to merge 9 commits into from

Conversation

LaVLaS
Copy link
Contributor

@LaVLaS LaVLaS commented Jan 16, 2017

Add fusor_api support for deploying RHV+OSP+CFME+OCP in the same deployment. The RHVFusorAPI and OSPFusorAPI classes didn't support all-in-one deployments so they have been refactored and combined into 1 QCIDeploymentAPI class. Existing API deployment tests have been updated to support the new QCIDeploymentAPI object and a new test was created that will test api deployments of RHV, OSP, RHV+OSP. CFME and/or OCP can be included with any of the deployment combinations

In order to support all-in-one deployments of QCI, we needed to create a
new api deployment class to support a single deployment with RHV and
OSP.
The new test_api_qci_deployment.py supports api deployments for both RHV
and/or OSP.
The rhsm_subs key did have a list of of 1 with a subscription pool name
but it wasn't used for any tests and redundant since all the info for
subscriptions is in deployment.products.sat.rhsm_satellite
Api deployment will always make sure there are enough quantities of the
default subscriptions and attach extra if necessary.

Added 'subscriptions' key to sat yaml property for the default
subscription necessary for syncing qci content
@LaVLaS LaVLaS changed the title [WIP] Support for all-in-one API deployment: RHV+OSP (+CFME) (+OCP) Support for all-in-one API deployment: RHV+OSP (+CFME) (+OCP) Mar 6, 2017
@LaVLaS LaVLaS changed the title Support for all-in-one API deployment: RHV+OSP (+CFME) (+OCP) [WIP] Support for all-in-one API deployment: RHV+OSP (+CFME) (+OCP) Mar 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant