Bug 1394036

Summary: [RFE] Support change of existing roles on running environments (removing service from existing roles)
Product: Red Hat OpenStack Reporter: Jaromir Coufal <jcoufal>
Component: rhosp-directorAssignee: Emilien Macchi <emacchi>
Status: CLOSED WORKSFORME QA Contact: Gurenko Alex <agurenko>
Severity: unspecified Docs Contact:
Priority: high    
Version: 11.0 (Ocata)CC: augol, dbecker, emacchi, mburns, morazi, nlevinki, sclewis
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-08 15:15:53 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:
Bug Depends On: 1394029, 1394035    
Bug Blocks:    

Description Jaromir Coufal 2016-11-10 21:08:33 UTC

Comment 1 Jaromir Coufal 2016-11-10 21:09:21 UTC
USER STORIES:

* As a cloud operator, I want to change placement of services across roles/nodes without any service disruption so that I can change my architecture on-fly.

Comment 8 Jaromir Coufal 2017-03-08 22:06:23 UTC
Example use case:

* As a cloud operator I want to separate my RabbitMQ from Controller into standalone role so that I increase my performance of control plane.

In this case, user wants to remove RabbitMQ from Controller heat-template and create new heat-template called MessageBus which contains that service, trigger stack update and end up with new architecture.

Target is to apply similar use case to any of the roles which we defined as they can be "standalone" and support these changes after user deployed his stack. From deployment framework, we should be capable of providing flexible model which would allow to expand this scope to more services through out the time (not just limited set).

Comment 9 Jaromir Coufal 2017-03-16 18:26:12 UTC
We are targeting this effort to be on top of containers, therefor moving to OSP13.