Open Stack

On Sun, May 1, 2016 at 3:52 PM, Tristan Cacqueray <tdecacqu at redhat.com> 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