Bug 1388255 - Disable tripleo update on already created overcloud nodes during scale out [NEEDINFO]
Summary: Disable tripleo update on already created overcloud nodes during scale out
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo
Version: 7.0 (Kilo)
Hardware: All
OS: Linux
high
urgent
Target Milestone: async
: ---
Assignee: Brad P. Crochet
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-24 21:18 UTC by Andreas Karis
Modified: 2020-04-15 14:46 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-01 16:46:19 UTC
Target Upstream Version:
aschultz: needinfo? (akaris)

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Andreas Karis 2016-10-24 21:18:14 UTC 
Description of problem:
Looking for a way to disable tripleo update on already created overcloud nodes during a scale out of nodes with OpenStack Director. Director should only deploy new nodes (CREATE) and modify mapping in /etc/hosts on all nodes

Version-Release number of selected component (if applicable):
OSP 7

Additional info:
The customer does not seem to use Director to update existing nodes - they do have ansible to do so, and would prefer to continue to use ansible.
Note You need to log in before you can comment on or make changes to this bug.