Re: [openstack-dev] [tripleo] composable roles team

[Dan Prince]

On Fri, 2016-04-29 at 15:27 -0500, Emilien Macchi wrote:
> Hi,
> 
> One of the most urgent tasks we need to achieve in TripleO during
> Newton cycle is the composable roles support.
> So we decided to build a team that would focus on it during the next
> weeks.
> 
> We started this etherpad:
> https://etherpad.openstack.org/p/tripleo-composable-roles-work

Sorry I missed this. So there is an older etherpad where we are
actually maintaining stuff here now:

https://etherpad.openstack.org/p/tripleo-composable-services

Thanks,

Dan

> 
> So anyone can help or check where we are.
> We're pushing / going to push a lot of patches, we would appreciate
> some reviews and feedback.
> 
> Also, I would like to propose to -1 every patch that is not
> composable-role-helpful, it will help us to move forward. Our team
> will be available to help in the patches, so we can all converge
> together.
> 
> Any feedback is welcome, 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

Re: [openstack-dev] [tripleo] composable roles team

[Steven Hardy]

On Fri, Apr 29, 2016 at 03:27:29PM -0500, Emilien Macchi wrote:
> Hi,
> 
> One of the most urgent tasks we need to achieve in TripleO during
> Newton cycle is the composable roles support.
> So we decided to build a team that would focus on it during the next weeks.

Note that there is some confusion regarding the "composable roles" term -
what we're discussing here is the effort to decompose services within the
existing roles, which is a precursor to fully composable roles.

There are two BPs related to this:

https://review.openstack.org/#/q/topic:bp/refactor-puppet-manifests
https://blueprints.launchpad.net/tripleo/+spec/refactor-puppet-manifests

This is about breaking up the monolithic puppet manifests into per-service
profiles in puppet-tripleo

https://review.openstack.org/#q,topic:bp/composable-services-within-roles,n,z
https://blueprints.launchpad.net/tripleo/+spec/composable-services-within-roles

This is about consuming the per-service profiles via a new per-service
template definition (a new internal template API for service configuration
via heat templates)

Both can be tracked independently, but the composable-services-within-roles
BP depends on the refactor-puppet-manifests work.

Then, there is a final step which is enabling user defined additional roles
(e.g groups of nodes not deployed via the fixed Controller/Compute/*Storage
groups) - I proposed a possible approach for this in our summit session,
and will raise a BP to track this work (hopefully will have a prototype
implementation posted soon).

> We started this etherpad:
> https://etherpad.openstack.org/p/tripleo-composable-roles-work
> 
> So anyone can help or check where we are.
> We're pushing / going to push a lot of patches, we would appreciate
> some reviews and feedback.

Thanks, I think the etherpad will be helpful to focus reviewer attention -
please ensure the patches are tagged with one of the BPs above as
appropriate too.

> Also, I would like to propose to -1 every patch that is not
> composable-role-helpful, it will help us to move forward. Our team
> will be available to help in the patches, so we can all converge
> together.

To clarify, I think we should block any new services from landing in the
"old" non-composable interface, but it's probably not reasonable to block
everything (in particular high priority bugfixes) that touches the old
monolithic manifests, we should try to minimise the rebase pain for
composable services though.

Steve

__
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] composable roles team

[Tomas Sedovic]

On 05/02/2016 07:47 PM, Brent Eagles wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 05/01/2016 08:01 PM, Emilien Macchi wrote:




If a feature can't land without disruption, then why not using a
special branch to be merged once the feature is complete ?


The problem is that during our work, some people will update the
manifests, and it will affect us, since we're copy/pasting the
code somewhere else (in puppet-tripleo), that's why we might need
some outstanding help from the team, to converge to the new model.
I know asking that is tough, but if we want to converge quickly,
we need to make the adoption accepted by everyone. One thing we can
do, is asking our reviewer team to track the patches that will need
some work, and the composable team can help in the review process.

The composable roles is a feature that we all wait, having the
help from our contributors will really save us time.


s/wait/want/ I expect.

Well said. I understand the reservations on the -1 for non-composable
role patches. It *does* feel a bit strong, but in the end I think it's
just being honest. The likelihood that a patch on tht is going to land
"as is" prior to the merge of the related composable role changes
seems really unlikely. I for one, am willing to do what I can to help
anyone who has had their patch pre-empted during this period get their
patch refactored/ported once the comp-roles thing has settled down.


There is a precedent for this: back when we were using merge.py to 
generate the TripleO Heat templates, the patch that moved us to pure 
Heat was taking a long time to merge due to all the other t-h-t patches 
coming in and causing conflicts.


So we decided to -2 all the other t-h-t patches until this one got merged.

On the other hand, that lasted for a few days. I'm not sure how long 
until we get the composable roles landed.


Tomas




Cheers,

Brent

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXJ5KpAAoJEIXWptqvFlBWmA8P/1dBlsCNYIqOHBBWxzEnLM41
gP/K+UsGFHaXj86yOdus5gp58/JFX9KJ+mqr0Yi/8ail+h+t0yjgcCXLlp6HUTKo
7OtNfAzPMDeDkquB5R7WREJfLdtP7tVpBsd0Ezs00y5ZDUuDk/J0waleQFtAKUjr
Xiip2y/e8tZMdWa0gvp/q+kWJ3v+YhAnl9PNQMCeIGf/IwDQrTNYvDTIChLx6dud
g7tWfH+ej6nL/ty8UM4R3ac94ZyZLrxprShbdpAh798kYhrR1WPju+hmBgln8rlx
fcTzXq8b428QzCmNKFeKuNmP32yXjOCZlEi2/NijfiR7nFY6sLvh7ROIODiwmzx8
fPSb1W8bLqIijeAUy2YpZFfvbe+NZdn2iIHjseS6Yu4D85NakUunkrBJEpbnCy8L
26N9ShseHbVRckpMSyxEyi+jJfJcCp4FzR26SUFUamPcusMQVlBDQlhOh/8lr/Lq
frhxcYCn45JZ/R2pc3PS2HnRapmvM/TLxdFhbteUFMcEXBT4dvdQPcQdqH1Kx/Yw
S5C+1CESRMGH2KpqghHaMNnySYHFHYQNmCKEVfJjERGbI/U5dEEogIUuzHXHQlYV
kL83XvMh6gGHfRwbmeTOLsrR86c8+u3vaE5PzHPxQ3IBseezmRYiN2fmNclYsg8B
LvyHYCRNvOcj1y8gr0Yr
=obJ6
-END 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 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] composable roles team

[Brent Eagles]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 05/01/2016 08:01 PM, Emilien Macchi wrote:



>> If a feature can't land without disruption, then why not using a
>> special branch to be merged once the feature is complete ?
> 
> The problem is that during our work, some people will update the 
> manifests, and it will affect us, since we're copy/pasting the
> code somewhere else (in puppet-tripleo), that's why we might need
> some outstanding help from the team, to converge to the new model. 
> I know asking that is tough, but if we want to converge quickly,
> we need to make the adoption accepted by everyone. One thing we can
> do, is asking our reviewer team to track the patches that will need
> some work, and the composable team can help in the review process.
> 
> The composable roles is a feature that we all wait, having the
> help from our contributors will really save us time.

s/wait/want/ I expect.

Well said. I understand the reservations on the -1 for non-composable
role patches. It *does* feel a bit strong, but in the end I think it's
just being honest. The likelihood that a patch on tht is going to land
"as is" prior to the merge of the related composable role changes
seems really unlikely. I for one, am willing to do what I can to help
anyone who has had their patch pre-empted during this period get their
patch refactored/ported once the comp-roles thing has settled down.

Cheers,

Brent

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXJ5KpAAoJEIXWptqvFlBWmA8P/1dBlsCNYIqOHBBWxzEnLM41
gP/K+UsGFHaXj86yOdus5gp58/JFX9KJ+mqr0Yi/8ail+h+t0yjgcCXLlp6HUTKo
7OtNfAzPMDeDkquB5R7WREJfLdtP7tVpBsd0Ezs00y5ZDUuDk/J0waleQFtAKUjr
Xiip2y/e8tZMdWa0gvp/q+kWJ3v+YhAnl9PNQMCeIGf/IwDQrTNYvDTIChLx6dud
g7tWfH+ej6nL/ty8UM4R3ac94ZyZLrxprShbdpAh798kYhrR1WPju+hmBgln8rlx
fcTzXq8b428QzCmNKFeKuNmP32yXjOCZlEi2/NijfiR7nFY6sLvh7ROIODiwmzx8
fPSb1W8bLqIijeAUy2YpZFfvbe+NZdn2iIHjseS6Yu4D85NakUunkrBJEpbnCy8L
26N9ShseHbVRckpMSyxEyi+jJfJcCp4FzR26SUFUamPcusMQVlBDQlhOh/8lr/Lq
frhxcYCn45JZ/R2pc3PS2HnRapmvM/TLxdFhbteUFMcEXBT4dvdQPcQdqH1Kx/Yw
S5C+1CESRMGH2KpqghHaMNnySYHFHYQNmCKEVfJjERGbI/U5dEEogIUuzHXHQlYV
kL83XvMh6gGHfRwbmeTOLsrR86c8+u3vaE5PzHPxQ3IBseezmRYiN2fmNclYsg8B
LvyHYCRNvOcj1y8gr0Yr
=obJ6
-END 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

Re: [openstack-dev] [tripleo] composable roles team

[Emilien Macchi]

On Sun, May 1, 2016 at 3:52 PM, Tristan Cacqueray  wrote:
> That's an exciting news, please find a couple of comments bellow.
>
> On 04/29/2016 08:27 PM, Emilien Macchi wrote:
>> Hi,
>>
>> One of the most urgent tasks we need to achieve in TripleO during
>> Newton cycle is the composable roles support.
>> So we decided to build a team that would focus on it during the next weeks.
>>
>> We started this etherpad:
>> https://etherpad.openstack.org/p/tripleo-composable-roles-work
>
> Tracking such task isn't optimal with etherpads. Why not discuss the
> design through the mailing list and use gerrit topic instead ?

++
we already have the topic:
https://review.openstack.org/#/q/topic:composable_service

For the design, I think we covered it enough during the Summit, and we
already have Keystone & Glance as part of composable roles, right now
the work is to implement the other services...

> In general, be wary of using etherpad for long term collaboration, it's
> really best use only for punctual and short lived events.
>
>>
>> So anyone can help or check where we are.
>> We're pushing / going to push a lot of patches, we would appreciate
>> some reviews and feedback.
>>
>> Also, I would like to propose to -1 every patch that is not
>> composable-role-helpful, it will help us to move forward. Our team
>> will be available to help in the patches, so we can all converge
>> together.
>
> This sounds like a stiff strategy, how are you going to deal with
> stable branch fix for example ?

I don't think the plan is to backport this feature, it sounds a lot of
work, but my opinion might be wrong.

> If a feature can't land without disruption, then why not using
> a special branch to be merged once the feature is complete ?

The problem is that during our work, some people will update the
manifests, and it will affect us, since we're copy/pasting the code
somewhere else (in puppet-tripleo), that's why we might need some
outstanding help from the team, to converge to the new model.
I know asking that is tough, but if we want to converge quickly, we
need to make the adoption accepted by everyone.
One thing we can do, is asking our reviewer team to track the patches
that will need some work, and the composable team can help in the
review process.

The composable roles is a feature that we all wait, having the help
from our contributors will really save us time.

Thanks for your feedback,
-- 
Emilien Macchi

__
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] composable roles team

[Tristan Cacqueray]

That's an exciting news, please find a couple of comments bellow.

On 04/29/2016 08:27 PM, Emilien Macchi wrote:
> Hi,
> 
> One of the most urgent tasks we need to achieve in TripleO during
> Newton cycle is the composable roles support.
> So we decided to build a team that would focus on it during the next weeks.
> 
> We started this etherpad:
> https://etherpad.openstack.org/p/tripleo-composable-roles-work

Tracking such task isn't optimal with etherpads. Why not discuss the
design through the mailing list and use gerrit topic instead ?

In general, be wary of using etherpad for long term collaboration, it's
really best use only for punctual and short lived events.

> 
> So anyone can help or check where we are.
> We're pushing / going to push a lot of patches, we would appreciate
> some reviews and feedback.
> 
> Also, I would like to propose to -1 every patch that is not
> composable-role-helpful, it will help us to move forward. Our team
> will be available to help in the patches, so we can all converge
> together.

This sounds like a stiff strategy, how are you going to deal with
stable branch fix for example ?

If a feature can't land without disruption, then why not using
a special branch to be merged once the feature is complete ?


-Tristan



signature.asc
Description: OpenPGP digital 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

Re: [openstack-dev] [tripleo] composable roles team

[Ryan Brady]

On Fri, Apr 29, 2016 at 4:27 PM, Emilien Macchi  wrote:

> Hi,
>
> One of the most urgent tasks we need to achieve in TripleO during
> Newton cycle is the composable roles support.
> So we decided to build a team that would focus on it during the next weeks.
>
> We started this etherpad:
> https://etherpad.openstack.org/p/tripleo-composable-roles-work
>
> So anyone can help or check where we are.
> We're pushing / going to push a lot of patches, we would appreciate
> some reviews and feedback.
>
> Also, I would like to propose to -1 every patch that is not
> composable-role-helpful, it will help us to move forward. Our team
> will be available to help in the patches, so we can all converge
> together.
>

-1 everything else is too heavy handed.


>
> Any feedback is welcome, thanks.
> --
> Emilien Macchi
>
> __
> 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
>



-- 
- Ryan

Ryan Brady
rbr...@redhat.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

[openstack-dev] [tripleo] composable roles team

[Emilien Macchi]

Hi,

One of the most urgent tasks we need to achieve in TripleO during
Newton cycle is the composable roles support.
So we decided to build a team that would focus on it during the next weeks.

We started this etherpad:
https://etherpad.openstack.org/p/tripleo-composable-roles-work

So anyone can help or check where we are.
We're pushing / going to push a lot of patches, we would appreciate
some reviews and feedback.

Also, I would like to propose to -1 every patch that is not
composable-role-helpful, it will help us to move forward. Our team
will be available to help in the patches, so we can all converge
together.

Any feedback is welcome, thanks.
-- 
Emilien Macchi

__
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