[openstack-dev] [tripleo] Sample Roles
skramaja at redhat.com
Thu Mar 16 06:13:43 UTC 2017
Thanks Alex. This is really an important requirement. Today, product
documentation has such roles incorporated to it, which is not good.
This patch simplifies it.
A suggestion though, instead of an external generation tool, is it not
possible to include the individual roles yaml files directly to the a
parent yam file? Why to add one extra step. May be we can provide all
options in the list and say enabled as 0 or 1. Much simpler to use.
This external tool can be an mistral action to derive the final roles
On Thu, Mar 16, 2017 at 3:37 AM, Emilien Macchi <emilien at redhat.com> wrote:
> On Wed, Mar 15, 2017 at 5:28 PM, Alex Schultz <aschultz at redhat.com> wrote:
>> Ahoy folks,
>> For the Pike cycle, we have a blueprint to provide a few basic
>> environment configurations with some custom roles. For this effort
>> and to reduce the complexity when dealing with roles I have put
>> together a patch to try and organize roles in a more consumable
>> fashion. The goal behind this is that we can document the standard
>> role configurations and also be able to ensure that when we add a new
>> OS::TripleO::Service::* we can make sure they get applied to all of
>> the appropriate roles. The goal of this initial change is to also
>> allow us all to reuse the same roles and work from a single
>> configuration repository. Please also review the existing roles in
>> the review and make sure we're not missing any services.
> Sounds super cool!
>> Also my ask is that if you have any standard roles, please consider
>> publishing them to the new roles folder so we can also identify
>> future CI testing scenarios we would like to support.
> Can we document it here maybe?
>>  https://blueprints.launchpad.net/tripleo/+spec/example-custom-role-environments
>>  https://review.openstack.org/#/c/445687/
> Emilien Macchi
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev