Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1433735

Summary: [RFE] Include CNS deployment in openshift ansible installer
Product: OpenShift Container Platform Reporter: daniel <dmoessne>
Component: RFEAssignee: Scott Dodson <sdodson>
Status: CLOSED ERRATA QA Contact: Wenkai Shi <weshi>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.6.0CC: aos-bugs, eparis, erich, jarrpa, jialiu, jokerman, mmccomas, pprakash, rcyriac, sdodson, trankin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-11 18:53:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1422090, 1445221, 1446041, 1447588, 1457126    
Bug Blocks:    

Description daniel 2017-03-19 15:34:37 UTC
1. Proposed title of this feature request
Include CNS deployment in ansible installer 


3. What is the nature and description of the request?
When deploying a new OCP environment with advanced installtion method aka ansible
it should be possible to also install CNS  with this method. currently CNS deployment is
an additional step which makes it necessary to redeploy infra pods, e.g. registry after
CNS deployment. It would be much better if CNS would be deployed with advanced inst method
so it is already there when infra pods are deployed. 


4. Why does the customer need this? (List the business requirements here)
In order to be able to run installtion as much as possible in one step so that there is no
need to run many manual steps afterwards. This is esp very usefule when deploying many 
different environments. Further on it makes keeping track of current configuration much 
easier if one needs to only have a look at ansible hosts file (which can reference another
file).


5. How would the customer like to achieve this? (List the functional requirements here)
Ansible hosts file should have all necessary options in it, possibly reference topology file


6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
make options available to install CNS as today via ansible  (advanced install method) so that needed options are as options
in /etc/ansible/hosts

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
found none


8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
asap


9. Is the sales team involved in this request and do they have any additional input?
yes (SA)


10. List any affected packages or components.
Documentation
ansible playbook


11. Would the customer be able to assist in testing this functionality if implemented?
yes

Comment 3 Wenkai Shi 2017-08-01 09:54:11 UTC
Verified with version openshift-ansible-3.6.173.0.1-1.git.0.71e81fa.el7, CNS deployment inside the openshift ansible installer now.

Comment 4 Wenkai Shi 2017-08-04 04:39:39 UTC
Move status to "ASSUBED" cause BZ #1478198

Comment 6 Johnny Liu 2017-08-10 06:22:02 UTC
At final comment, the regression bug BZ#1478198 is fixed by openshift-ansible-3.6.173.0.5-3.git.0.522a92a.el7, so move this bug to verified status.

Comment 8 Scott Dodson 2017-08-11 18:53:22 UTC
This was delivered in 3.6 GA https://access.redhat.com/errata/product/290/ver=3.6/rhel---7/x86_64/RHEA-2017:1716