Re: [openstack-dev] [TripleO] additional git repo(s) for tripleo-quickstart

[Paul Belanger]

On Wed, Aug 10, 2016 at 03:26:18PM -0400, Wesley Hayutin wrote:
> Greetings,
> 
> In an effort to make TripleO CI composable and managed and governed by the
> TripleO project we have  found the need to create additional git repos in
> openstack under the TripleO project.  This could also be done outside of
> the TripleO project, but ideally it's in TripleO.
> 
> I'm proposing the creation of a repo called tripleo-quickstart-extras that
> would contain some or all of the current third party roles used with
> TripleO-Quickstart.
> 
> The context behind this discussion is that we would like to use oooq to
> document baremetal deployments to supplement and or replace the current
> TripleO documentation.  It would be ideal of the code used to create this
> documentation was part of the TripleO project.
> 
> We're looking for discussion and permission for a new TripleO git repo to
> be created.
> 
>From an infrastructure point of view, creating additional git repos is
straight forward.

The way I see it is, either create tripleo-quickstart-extras repo with all your
roles, or start doing individual roles for example:

  ansible-role-tripleo-build-all-the-things

I'd be on board with using the ansible-role-tripleo prefix for roles specific to
tripleo. And it seems to be your current naming schema too.

> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] additional git repo(s) for tripleo-quickstart

[Wesley Hayutin]

On Wed, Aug 10, 2016 at 9:45 PM, Lars Kellogg-Stedman 
wrote:

> On Wed, Aug 10, 2016 at 03:26:18PM -0400, Wesley Hayutin wrote:
> > I'm proposing the creation of a repo called tripleo-quickstart-extras
> that
> > would contain some or all of the current third party roles used with
> > TripleO-Quickstart.
>
> Which roles in particular would you place in this -extras repository?
> One of our goals in moving roles *out* of the quickstart was to move
> them into a one-repository-per-role model that makes things easily
> composable (install only those roles you need) and that
> compartmentalizes related sets of changes.
>

Lars, I'm thinking about this with the following priorities in mind..
1. TripleO-Quickstart code needs to be upstream and governed by the TripleO
project
2. TripleO-Quickstart itself is a replacement for instack-virt-setup
3. TripleO-Quickstart's roles need to be composable
4. TripleO-Quickstart needs to be composable for 3rd party git repositories

If we can get one additional git repo under the TripleO umbrella I think
we've accomplished 1-3.  We can prove #4 with yum repos outside of
OpenStack.

Compartmentalizing changes in their own git repositories is nice, but also
has disadvantages.  For instance, there is less governance across the roles
by oooq core members.  If I had to weigh compartmentalizing the roles vs. a
tripleo-quickstart-extras repo in TripleO, my vote would be for the
latter.  This is just my opinion though.

James made it clear that if TripleO-Quickstart is to provide automatically
generated documentation for the TripleO project the src code has to be
under the TripleO project and the execution itself must run in the TripleO
CI environment.

It would be great if TripleO cores could weigh in and assist us in getting
one additional git repo so we can proceed with determining if automatically
generated documentation would be something TripleO would like.

Thanks



>
> Is this just a convenience for a bunch of roles that are typically
> installed together?
>
> --
> Lars Kellogg-Stedman  | larsks @
> {freenode,twitter,github}
> Cloud Engineering / OpenStack  | http://blog.oddbit.com/
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] additional git repo(s) for tripleo-quickstart

[Lars Kellogg-Stedman]

On Wed, Aug 10, 2016 at 03:26:18PM -0400, Wesley Hayutin wrote:
> I'm proposing the creation of a repo called tripleo-quickstart-extras that
> would contain some or all of the current third party roles used with
> TripleO-Quickstart.

Which roles in particular would you place in this -extras repository?
One of our goals in moving roles *out* of the quickstart was to move
them into a one-repository-per-role model that makes things easily
composable (install only those roles you need) and that
compartmentalizes related sets of changes.

Is this just a convenience for a bunch of roles that are typically
installed together?

-- 
Lars Kellogg-Stedman  | larsks @ {freenode,twitter,github}
Cloud Engineering / OpenStack  | http://blog.oddbit.com/



signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [TripleO] additional git repo(s) for tripleo-quickstart

[Wesley Hayutin]

Greetings,

In an effort to make TripleO CI composable and managed and governed by the
TripleO project we have  found the need to create additional git repos in
openstack under the TripleO project.  This could also be done outside of
the TripleO project, but ideally it's in TripleO.

I'm proposing the creation of a repo called tripleo-quickstart-extras that
would contain some or all of the current third party roles used with
TripleO-Quickstart.

The context behind this discussion is that we would like to use oooq to
document baremetal deployments to supplement and or replace the current
TripleO documentation.  It would be ideal of the code used to create this
documentation was part of the TripleO project.

We're looking for discussion and permission for a new TripleO git repo to
be created.

Thanks!
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev