Re: [openstack-dev] [openstack-helm] [vote] Core Reviewer nomination for Chris Wedgwood

[Richard Wellum]

+1

On Fri, Aug 3, 2018 at 11:39 AM Steve Wilkerson 
wrote:

> +1
>
> On Fri, Aug 3, 2018 at 10:05 AM, MCEUEN, MATT  wrote:
>
>> OpenStack-Helm core reviewer team,
>>
>> I would like to nominate Chris Wedgwood as core review for the
>> OpenStack-Helm.
>>
>> Chris is one of the most prolific reviewers in the OSH community, but
>> more importantly is a very thorough and helpful reviewer.  Many of my most
>> insightful reviews are thanks to him, and I know the same is true for many
>> other team members.  In addition, he is an accomplished OSH engineer and
>> has contributed features that run the gamut, including Ceph integration,
>> Calico support, Neutron configuration, Gating, and core Helm-Toolkit
>> functionality.
>>
>> Please consider this email my +1 vote.
>>
>> A +1 vote indicates that you are in favor of his core reviewer candidacy,
>> and a -1 is a veto.  Voting will be open for the next seven days (closing
>> 8/10) or until all OpenStack-Helm core reviewers cast their vote.
>>
>> Thank you,
>> Matt McEuen
>>
>> __
>> 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
>
__
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] [kolla][vote]Core nomination for Mark Goddard (mgoddard) as kolla core member

[Richard Wellum]

+1

On Fri, Apr 27, 2018 at 2:07 AM Paul Bourke  wrote:

> +1, always great working with Mark :)
>
> On 26/04/18 16:31, Jeffrey Zhang wrote:
> > Kolla core reviewer team,
> >
> > It is my pleasure to nominate
> > ​
> > mgoddard for kolla core team.
> > ​
> > Mark has been working both upstream and downstream with kolla and
> > kolla-ansible for over two years, building bare metal compute clouds with
> > ironic for HPC. He's been involved with OpenStack since 2014. He started
> > the kayobe deployment project which complements kolla-ansible. He is
> > also the most active non-core contributor for last 90 days[1]
> > ​​
> > Consider this nomination a +1 vote from me
> >
> > A +1 vote indicates you are in favor of
> > ​
> > mgoddard as a candidate, a -1
> > is a
> > ​​
> > veto. Voting is open for 7 days until
> > ​May
> > ​4​
> > th, or a unanimous
> > response is reached or a veto vote occurs.
> >
> > [1] http://stackalytics.com/report/contribution/kolla-group/90
> >
> > --
> > Regards,
> > Jeffrey Zhang
> > Blog: http://xcodest.me 
> >
> >
> >
> __
> > 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
>
__
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] [kolla][vote]Retire kolla-kubernetes project

[Richard Wellum]

+1

On Tue, Apr 17, 2018 at 9:52 PM Jeffrey Zhang 
wrote:

> Since many of the contributors in the kolla-kubernetes project are moved
> to other things. And there is no active contributor for months.  On the
> other hand, there is another comparable project, openstack-helm, in the
> community.  For less confusion and disruptive community resource, I propose
> to retire the kolla-kubernetes project.
>
> More discussion about this you can check the mail[0] and patch[1]
>
> please vote +1 to retire the repo, or -1 not to retire the repo. The vote
> will be open until everyone has voted, or for 1 week until April 25th, 2018.
>
> [0]
> http://lists.openstack.org/pipermail/openstack-dev/2018-March/128822.html
> [1] https://review.openstack.org/552531
>
> --
> Regards,
> Jeffrey Zhang
> Blog: http://xcodest.me
> __
> 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] [kolla][kolla-kubernete][tc][openstack-helm]propose retire kolla-kubernetes project

[Richard Wellum]

On Thu, Mar 29, 2018 at 8:14 PM Surya Singh <singh.surya64mn...@gmail.com>
wrote:

> Dear All,
>
> Thanks Rich for putting thoughts on continuation with kolla-k8s.
>
>
> On Fri, Mar 30, 2018 at 2:26 AM, Richard Wellum <richwel...@gmail.com>
> wrote:
> >
> > Hi,
> >
> > So as a current Kolla-Kubernetes Core - I have a slightly different
> opinion than most, I'll try to verbalize it coherently.
> >
> > Lets talk about what Kolla is:
> >
> > Kolla is a project that builds OpenStack docker images, stores them on
> dockerhub, and provides tools to build your own images from your own
> source. Both the images and the tools it provides, are widely used, very
> popular and extremely stable; TripleO, openstack-helm and kolla-ansible to
> name a few are all deployment methods that use Kolla.
> >
> > Kolla has two sub-projects, that both revolve around deployment methods;
> kolla-ansible and kolla-kubernetes. Kolla-ansible is proven, stable and
> used by many in the industry. Part of Kolla's quality is it's rock-solid
> dependability in many scenarios. As Kubernetes took over most of the COE
> world, it's only correct that the Kolla team created this sub-project; if
> swarm became suddenly very popular then we should create a kolla-swarm
> sub-project.
> >
> > So if we abandon kolla-kubernetes ('sunset' seems much more romantic
> admittedly) - we are abandoning the core Kolla team's efforts in this
> space. No matter how good openstack-helm is (and I've deployed it, know a
> lot of the cores and it's truly excellent and well driven), what happens
> down the line if openstack-helm decide to move on from Kolla - say
> focussing on Loci images or a new flavor that comes along? Then Kolla the
> core project, will no longer have any validation of it's docker
> images/containers running on Kubernetes. That to me is the big risk here.
> >
> > The key issue in my opinion is that the core Kolla team has focussed on
> kolla-ansible almost exclusively, and have not migrated to using
> kolla-kubernetes as well. As the code base has stagnated, the gates get
> intro trouble, and new features and configurations added to kolla-ansible
> are not translated to kolla-kubernetes.
> >
> > So I think the real question is not whether we should 'sunset'
> kolla-kubernetes the sub-project, but should we drop Kolla support on
> Kubernetes? Relying on a different team to do so is probably not the
> answer; although it's the one championed in this thread.
>
> +1
>
> >
> > In my opinion we should set some realistic goals before we sunset:
> >
> > 1. Pick a feature set for a Rocky v1.0 release, and commit to trying to
> get there. We have a long list of items, maybe pair this down to something
> reasonable.
>
> I am agree that we should have feature set for Rocky v1.0 release and
> AFAIK community already have that.
>
> > 2. Agreement within Kolla core team to learn kolla-kubernetes and start
> to put a percentage of time into this sub-project.
> > 3. Identify the people who are genuinely interested in working with it
> within the Kolla team.
>
> Though currently I am not the MVP in kolla-k8s but i would love to
> help with some concrete item for v1.0, IMHO before that we need a
> leader then identify volunteers.
> And for that if we need more thought on this
> https://review.openstack.org/#/c/552531
>
> I missed this and will review.

Thanks,

||Rich


> >
> > Without '2' I think sunsetting is the way forward, but the risks should
> be fully understood and hopefully I've made a case for what those are above.
> >
> > Thanks,
> >
> > ||Rich
> >
> >
> > On Wed, Mar 28, 2018 at 1:54 PM Chuck Short <zul...@gmail.com> wrote:
> >>
> >> +1
> >>
> >> Regards
> >> chuck
> >> On Wed, Mar 28, 2018 at 11:47 AM, Jeffrey Zhang <
> zhang.lei@gmail.com> wrote:
> >>>
> >>> There are two projects to solve the issue that run OpenStack on
> >>> Kubernetes, OpenStack-helm, and kolla-kubernetes. Them both
> >>> leverage helm tool for orchestration. There is some different
> perspective
> >>> at the beginning, which results in the two teams could not work
> together.
> >>>
> >>> But recently, the difference becomes too small. and there is also no
> active
> >>> contributor in the kolla-kubernetes project.
> >>>
> >>> So I propose to retire kolla-kubernetes project. If you are still
> >>> interested in running OpenStack on kubernetes, please refer to
> >>> openstack-helm project.
> &g

Re: [openstack-dev] [kolla][kolla-kubernete][tc][openstack-helm]propose retire kolla-kubernetes project

[Richard Wellum]

Hi Gema,

On Thu, Mar 29, 2018 at 2:48 PM Gema Gomez <g...@ggomez.me> wrote:

>
>
> On 29/03/18 18:26, Richard Wellum wrote:
> > Hi,
> >
> > So as a current Kolla-Kubernetes Core - I have a slightly different
> > opinion than most, I'll try to verbalize it coherently.
> >
> > Lets talk about what Kolla is:
> >
> > Kolla is a project that builds OpenStack docker images, stores them on
> > dockerhub, and provides tools to build your own images from your own
> > source. Both the images and the tools it provides, are widely used, very
> > popular and extremely stable; TripleO, openstack-helm and kolla-ansible
> > to name a few are all deployment methods that use Kolla.
> >
> > Kolla has two sub-projects, that both revolve around deployment methods;
> > kolla-ansible and kolla-kubernetes. Kolla-ansible is proven, stable and
> > used by many in the industry. Part of Kolla's quality is it's rock-solid
> > dependability in many scenarios. As Kubernetes took over most of the COE
> > world, it's only correct that the Kolla team created this sub-project;
> > if swarm became suddenly very popular then we should create a
> > kolla-swarm sub-project.
> >
> > So if we abandon kolla-kubernetes ('sunset' seems much more romantic
> > admittedly) - we are abandoning the core Kolla team's efforts in this
> > space. No matter how good openstack-helm is (and I've deployed it, know
> > a lot of the cores and it's truly excellent and well driven), what
> > happens down the line if openstack-helm decide to move on from Kolla -
> > say focussing on Loci images or a new flavor that comes along? Then
> > Kolla the core project, will no longer have any validation of it's
> > docker images/containers running on Kubernetes. That to me is the big
> > risk here.
> >
> > The key issue in my opinion is that the core Kolla team has focussed on
> > kolla-ansible almost exclusively, and have not migrated to using
> > kolla-kubernetes as well. As the code base has stagnated, the gates get
> > intro trouble, and new features and configurations added to
> > kolla-ansible are not translated to kolla-kubernetes.
> >
> > So I think the real question is not whether we should 'sunset'
> > kolla-kubernetes the sub-project, but should we drop Kolla support on
> > Kubernetes? Relying on a different team to do so is probably not the
> > answer; although it's the one championed in this thread.
> >
> > In my opinion we should set some realistic goals before we sunset:
> >
> > 1. Pick a feature set for a Rocky v1.0 release, and commit to trying to
> > get there. We have a long list of items, maybe pair this down to
> > something reasonable.
>
> Are you volunteering to drive this effort forward? I'd be happy to help
> define MVP for Rocky.
>

Yes I am.


>
> > 2. Agreement within Kolla core team to learn kolla-kubernetes and start
> > to put a percentage of time into this sub-project.
>
> Whilst this would be ideal, we cannot really force people that have no
> interest in this sub-project to contribute.
>

That's not what I was inferring, more trying to get a shift in attitude
within the Kolla team. For example, if I am working on kolla-kubernetes,
and make a change that breaks kolla-ansible - the Kolla community would
expect me to fix it of course? Same if I added a feature, and didn't apply
and test it with kolla-ansible then the same no? So I'm just saying that
the same should apply in the other direction; which it is currently not. As
a community we should support both deployment methods. Or if we don't then
we are all agreeing that Kolla will not have support on Kubernetes from the
core Kolla community.


>
> > 3. Identify the people who are genuinely interested in working with it
> > within the Kolla team.
>
> +1 if we find enough contributors to make the reasonable list of items
> happen during Rocky.
>
> > Without '2' I think sunsetting is the way forward, but the risks should
> > be fully understood and hopefully I've made a case for what those are
> above.
>
> How many contributors are necessary to make MVP?
>
We were doing fairly well with 4-5 contributors imo.

Thanks,

||Rich


>
> Cheers,
> Gema
>
> >
> > Thanks,
> >
> > ||Rich
> >
> >
> > On Wed, Mar 28, 2018 at 1:54 PM Chuck Short <zul...@gmail.com
> > <mailto:zul...@gmail.com>> wrote:
> >
> > +1
> >
> > Regards
> > chuck
> > On Wed, Mar 28, 2018 at 11:47 AM, Jeffrey Zhang
> > <zhang.lei@gmail.com <mailto:zhang.lei@gmail.com>> wrote:
> >
> > 

Re: [openstack-dev] [kolla][kolla-kubernete][tc][openstack-helm]propose retire kolla-kubernetes project

[Richard Wellum]

Hi,

So as a current Kolla-Kubernetes Core - I have a slightly different opinion
than most, I'll try to verbalize it coherently.

Lets talk about what Kolla is:

Kolla is a project that builds OpenStack docker images, stores them on
dockerhub, and provides tools to build your own images from your own
source. Both the images and the tools it provides, are widely used, very
popular and extremely stable; TripleO, openstack-helm and kolla-ansible to
name a few are all deployment methods that use Kolla.

Kolla has two sub-projects, that both revolve around deployment methods;
kolla-ansible and kolla-kubernetes. Kolla-ansible is proven, stable and
used by many in the industry. Part of Kolla's quality is it's rock-solid
dependability in many scenarios. As Kubernetes took over most of the COE
world, it's only correct that the Kolla team created this sub-project; if
swarm became suddenly very popular then we should create a kolla-swarm
sub-project.

So if we abandon kolla-kubernetes ('sunset' seems much more romantic
admittedly) - we are abandoning the core Kolla team's efforts in this
space. No matter how good openstack-helm is (and I've deployed it, know a
lot of the cores and it's truly excellent and well driven), what happens
down the line if openstack-helm decide to move on from Kolla - say
focussing on Loci images or a new flavor that comes along? Then Kolla the
core project, will no longer have any validation of it's docker
images/containers running on Kubernetes. That to me is the big risk here.

The key issue in my opinion is that the core Kolla team has focussed on
kolla-ansible almost exclusively, and have not migrated to using
kolla-kubernetes as well. As the code base has stagnated, the gates get
intro trouble, and new features and configurations added to kolla-ansible
are not translated to kolla-kubernetes.

So I think the real question is not whether we should 'sunset'
kolla-kubernetes the sub-project, but should we drop Kolla support on
Kubernetes? Relying on a different team to do so is probably not the
answer; although it's the one championed in this thread.

In my opinion we should set some realistic goals before we sunset:

1. Pick a feature set for a Rocky v1.0 release, and commit to trying to get
there. We have a long list of items, maybe pair this down to something
reasonable.
2. Agreement within Kolla core team to learn kolla-kubernetes and start to
put a percentage of time into this sub-project.
3. Identify the people who are genuinely interested in working with it
within the Kolla team.

Without '2' I think sunsetting is the way forward, but the risks should be
fully understood and hopefully I've made a case for what those are above.

Thanks,

||Rich


On Wed, Mar 28, 2018 at 1:54 PM Chuck Short  wrote:

> +1
>
> Regards
> chuck
> On Wed, Mar 28, 2018 at 11:47 AM, Jeffrey Zhang 
> wrote:
>
>> There are two projects to solve the issue that run OpenStack on
>> Kubernetes, OpenStack-helm, and kolla-kubernetes. Them both
>> leverage helm tool for orchestration. There is some different perspective
>> at the beginning, which results in the two teams could not work together.
>>
>> But recently, the difference becomes too small. and there is also no
>> active
>> contributor in the kolla-kubernetes project.
>>
>> So I propose to retire kolla-kubernetes project. If you are still
>> interested in running OpenStack on kubernetes, please refer to
>> openstack-helm project.
>>
>> --
>> Regards,
>> Jeffrey Zhang
>> Blog: http://xcodest.me
>>
>> __
>> 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
>
__
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] [kolla][vote] core nomination for caoyuan

[Richard Wellum]

+1

On Thu, Mar 15, 2018 at 5:40 AM Martin André  wrote:

> +1
>
> On Tue, Mar 13, 2018 at 5:50 PM, Swapnil Kulkarni 
> wrote:
> > On Mon, Mar 12, 2018 at 7:36 AM, Jeffrey Zhang 
> wrote:
> >> Kolla core reviewer team,
> >>
> >> It is my pleasure to nominate caoyuan for kolla core team.
> >>
> >> caoyuan's output is fantastic over the last cycle. And he is the most
> >> active non-core contributor on Kolla project for last 180 days[1]. He
> >> focuses on configuration optimize and improve the pre-checks feature.
> >>
> >> Consider this nomination a +1 vote from me.
> >>
> >> A +1 vote indicates you are in favor of caoyuan as a candidate, a -1
> >> is a veto. Voting is open for 7 days until Mar 12th, or a unanimous
> >> response is reached or a veto vote occurs.
> >>
> >> [1] http://stackalytics.com/report/contribution/kolla-group/180
> >> --
> >> Regards,
> >> Jeffrey Zhang
> >> Blog: http://xcodest.me
> >>
> >>
> __
> >> 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
> >>
> >
> > +1
> >
> >
> __
> > 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
>
__
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] [kolla] Proposal to add Marcin (hrw) to kolla images core team

[Richard Wellum]

+1 great contributor

Cheers,

//Rich

On Thu, Nov 2, 2017, 12:55 PM Steven Dake (stdake)  wrote:

> +1
>
> Cheers
> -steve
>
> On 11/3/17, 2:59 AM, "Michał Jastrzębski"  wrote:
>
> It's my great pleasure to start another voting for core team addition!
>
> Everyone knows hrw, thanks to him Kolla now runs on both Power and ARM!
> Voting will be open for 14 days (until 16th of Nov).
>
> Consider this mail my +1 vote
>
> Regards,
> Michal
>
>
> __
> 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
>
__
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] Fwd: [Kolla] kolla-kubernetes production ready?

[Richard Wellum]

No it is currently still in development. We are targeting a 1.0 release for
Rocky.

Hope that helps,

||Rich

On Thu, Sep 7, 2017 at 3:52 AM Kim-Norman Sahm 
wrote:

> Hi,
>
> does anybody know when kolla-kubernetes is ready for production?
> is someone using kolla-kubernetes for production now?
>
> regards
> Kim
>
> --
> Kim-Norman Sahm
> Cloud & Infrastructure(OCI)
>
> noris network AG
> Thomas-Mann-Straße 16-20
> 90471 Nürnberg
> Deutschland
>
> Tel +49 911 9352 1433 <+49%20911%2093521433>
> Fax +49 911 9352 100 <+49%20911%209352100>
>
> kim-norman.s...@noris.de
>
> https://www.noris.de - Mehr Leistung als Standard
> Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel
> Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689
>
>
>
>
>
>
>
>
> __
> 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] [kolla] [cinder] [ironic] [tripleo] PTG cross-platform meetup possibility

[Richard Wellum]

Yes.

Thanks,

Rich

On Sat, Sep 9, 2017, 12:59 AM Emilien Macchi  wrote:

> On Fri, Sep 8, 2017 at 7:04 PM, Michał Jastrzębski 
> wrote:
> > I know about wed meeting. This is when we wanted to discuss kolla-k8s and
> > tripleo shared resources,  whatever they might be.  I assumed Mon
> meeting is
> > different?
>
> So Monday is cross deployment projects collaboration meeting and
> Wednesday is whatever TripleO / Kolla collab related things.
> Does it make sense?
> --
> 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
>
__
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] [kolla] [cinder] [ironic] [tripleo] PTG cross-platform meetup possibility

[Richard Wellum]

No I think it's the same thing, couple of us just didn't know it had been
scheduled for Wednesday. Sorry for confusion.

4pm Monday can still be used for cinder, ironic and kolla cross platform,
and we can use the room I've booked.

Cheers,

Rich

On Fri, Sep 8, 2017, 10:04 PM Michał Jastrzębski <inc...@gmail.com> wrote:

> Hey,
>
> I know about wed meeting. This is when we wanted to discuss kolla-k8s and
> tripleo shared resources,  whatever they might be.  I assumed Mon meeting
> is different?
>
> On Sep 8, 2017 6:22 PM, "Richard Wellum" <richwel...@gmail.com> wrote:
>
>> Emilien,
>>
>> Can you please update this on the schedule if it's not already? The link
>> to the spreadsheet is in this thread.
>>
>> Michal didn't seem to know about this Wednesday meeting because he
>> replied to my email for Monday, with a confirmation, But maybe I'm missing
>> something. And we, kolla, all thought it was Monday, although we searched
>> for the conversation today and couldn't find anything. So not sure everyone
>> is synched up. Could just be me; it's been a long week.
>>
>> Cheers,
>>
>> Rich
>>
>> On Fri, Sep 8, 2017, 5:15 PM Vikram Hosakote (vhosakot) <
>> vhosa...@cisco.com> wrote:
>>
>>> Cool, we’ll hold the room reservation in Durango on Monday 2-4 pm for
>>> the cross-project
>>>
>>> meeting with the deployment tool groups (Kolla, Ansible, TripleO, Chef,
>>> Puppet, Helm,
>>>
>>> etc).
>>>
>>>
>>>
>>> Regards,
>>>
>>> Vikram Hosakote
>>>
>>> IRC:  vhosakot
>>>
>>>
>>>
>>> *From: *Emilien Macchi <emil...@redhat.com>
>>> *Reply-To: *"OpenStack Development Mailing List (not for usage
>>> questions)" <openstack-dev@lists.openstack.org>
>>> *Date: *Friday, September 8, 2017 at 4:04 PM
>>> *To: *"OpenStack Development Mailing List (not for usage questions)" <
>>> openstack-dev@lists.openstack.org>
>>> *Subject: *Re: [openstack-dev] [kolla] [cinder] [ironic] [tripleo] PTG
>>> cross-platform meetup possibility
>>>
>>>
>>>
>>> On Fri, Sep 8, 2017 at 12:49 PM, Richard Wellum <richwel...@gmail.com>
>>> wrote:
>>>
>>> Triple-O team - can you please confirm the Monday slot, 2-4pm still works
>>>
>>> for you?
>>>
>>>
>>>
>>> TripleO / Kolla interactions were scheduled on Wednesday morning in
>>>
>>> the TripleO room but I'm fine if you want to move it (just let us
>>>
>>> know).
>>>
>>> On Monday afternoon, Deployment tools group (Kolla, Ansible, TripleO,
>>>
>>> Chef, Puppet, Helm, etc) was supposed to meet in the Packaging room
>>>
>>> and collaborate.
>>>
>>>
>>>
>>> All of this was scheduled a few days / weeks ago but we're happy to
>>>
>>> re-visit it. Please let us know though because it will confuse people
>>>
>>> otherwise.
>>>
>>>
>>>
>>> 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
>>>
>>>
>>>
>>> __
>>> 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
>>
>> __
> 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] [kolla] [cinder] [ironic] [tripleo] PTG cross-platform meetup possibility

[Richard Wellum]

Emilien,

Can you please update this on the schedule if it's not already? The link to
the spreadsheet is in this thread.

Michal didn't seem to know about this Wednesday meeting because he replied
to my email for Monday, with a confirmation, But maybe I'm missing
something. And we, kolla, all thought it was Monday, although we searched
for the conversation today and couldn't find anything. So not sure everyone
is synched up. Could just be me; it's been a long week.

Cheers,

Rich

On Fri, Sep 8, 2017, 5:15 PM Vikram Hosakote (vhosakot) <vhosa...@cisco.com>
wrote:

> Cool, we’ll hold the room reservation in Durango on Monday 2-4 pm for the
> cross-project
>
> meeting with the deployment tool groups (Kolla, Ansible, TripleO, Chef,
> Puppet, Helm,
>
> etc).
>
>
>
> Regards,
>
> Vikram Hosakote
>
> IRC:  vhosakot
>
>
>
> *From: *Emilien Macchi <emil...@redhat.com>
> *Reply-To: *"OpenStack Development Mailing List (not for usage
> questions)" <openstack-dev@lists.openstack.org>
> *Date: *Friday, September 8, 2017 at 4:04 PM
> *To: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> *Subject: *Re: [openstack-dev] [kolla] [cinder] [ironic] [tripleo] PTG
> cross-platform meetup possibility
>
>
>
> On Fri, Sep 8, 2017 at 12:49 PM, Richard Wellum <richwel...@gmail.com>
> wrote:
>
> Triple-O team - can you please confirm the Monday slot, 2-4pm still works
>
> for you?
>
>
>
> TripleO / Kolla interactions were scheduled on Wednesday morning in
>
> the TripleO room but I'm fine if you want to move it (just let us
>
> know).
>
> On Monday afternoon, Deployment tools group (Kolla, Ansible, TripleO,
>
> Chef, Puppet, Helm, etc) was supposed to meet in the Packaging room
>
> and collaborate.
>
>
>
> All of this was scheduled a few days / weeks ago but we're happy to
>
> re-visit it. Please let us know though because it will confuse people
>
> otherwise.
>
>
>
> 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
>
>
> __
> 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] [kolla] [cinder] [ironic] [tripleo] PTG cross-platform meetup possibility

[Richard Wellum]

No problem Michal.

Triple-O team - can you please confirm the Monday slot, 2-4pm still works
for you?

Thanks,

||Rich

On Fri, Sep 8, 2017 at 3:31 PM Michał Jastrzębski <inc...@gmail.com> wrote:

> Awesome!
>
> Thanks Rich and see you all in Denver!
>
> On 8 September 2017 at 12:19, Richard Wellum <richwel...@gmail.com> wrote:
> > Room booked: 'Durango', 2-4pm for Kolla+Triple-O and 4-6 for
> > Kolla+Ironic+Cinder.
> >
> > Please see: https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms
> -
> > for more details.
> >
> > Thanks,
> >
> > ||Rich
> >
> >
> > On Thu, Sep 7, 2017 at 11:09 AM Vikram Hosakote (vhosakot)
> > <vhosa...@cisco.com> wrote:
> >>
> >> Sending the confirmed cross-project meets with the kolla community:
> >>
> >>
> >>
> >> Monday with Triple-O at 2 pm
> >>
> >> Monday with Cinder and Ironic at 4 pm
> >>
> >>
> >>
> >> Regards,
> >>
> >> Vikram Hosakote
> >>
> >> IRC:  vhosakot
> >>
> >>
> >>
> >> From: Jay S Bryant <jungleb...@gmail.com>
> >> Reply-To: "jsbry...@electronicjungle.net" <
> jsbry...@electronicjungle.net>,
> >> "OpenStack Development Mailing List (not for usage questions)"
> >> <openstack-dev@lists.openstack.org>
> >> Date: Thursday, August 31, 2017 at 1:43 PM
> >> To: "openstack-dev@lists.openstack.org"
> >> <openstack-dev@lists.openstack.org>
> >> Subject: Re: [openstack-dev] [kolla] [cinder] [ironic] PTG
> cross-platform
> >> meetup possibility
> >>
> >>
> >>
> >> Rich,
> >>
> >> I can make Monday at 4 pm work.  Conflicts with some Docs discussions
> but
> >> I can step out for a bit.
> >>
> >> Thanks!
> >>
> >> Jay
> >>
> >>
> >>
> >>
> >>
> >> On 8/31/2017 8:25 AM, Richard Wellum wrote:
> >>
> >> Hi,
> >>
> >>
> >>
> >> How does Monday at 4pm sound? Kolla already has a cross-platform
> >> discussion with Triple-O at 2pm, so this would dovetail nicely.
> >>
> >>
> >>
> >> Thanks,
> >>
> >>
> >> ||Rich
> >>
> >>
> >>
> >> On Wed, Aug 30, 2017 at 2:48 PM Ivan Kolodyazhny <e...@e0ne.info>
> wrote:
> >>
> >> Hi team,
> >>
> >>
> >>
> >> I'm interested in cinder containerization too. It would be great if we
> can
> >> schedule our meetup after 3pm or even 4pm, It will increase my chances
> to
> >> attend it.
> >>
> >>
> >>
> >> Thanks in advance.
> >>
> >>
> >> Regards,
> >> Ivan Kolodyazhny,
> >> http://blog.e0ne.info/
> >>
> >>
> >>
> >> On Wed, Aug 30, 2017 at 4:23 PM, Dmitry Tantsur <dtant...@redhat.com>
> >> wrote:
> >>
> >> Hi!
> >>
> >> I'm all for it. Monday sounds okay to me, though I'll have to manage
> some
> >> conflicts, of course.
> >>
> >>
> >>
> >> On 08/29/2017 05:56 PM, Richard Wellum wrote:
> >>
> >> Hi Folks,
> >>
> >> Would there be some interest from Cinder and Ironic (and others of
> course)
> >> team members to have a quick session at the PTG with the Kolla team on
> the
> >> latest developments in Kolla (like the new kolla-ansible devmode for
> >> example)?
> >>
> >> Also it would give the Kolla team an opportunity to hear about your
> teams
> >> interest and experiences in containerization and what you need from
> Kolla
> >> going forward.
> >>
> >> I'm thinking an hour or two on Monday afternoon, the first day of the
> PTG?
> >>
> >> Thanks,
> >>
> >> ||Rich
> >>
> >>
> __
> >> 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)
> >> Unsubsc

Re: [openstack-dev] [kolla] [cinder] [ironic] PTG cross-platform meetup possibility

[Richard Wellum]

Room booked: 'Durango', 2-4pm for Kolla+Triple-O and 4-6 for
Kolla+Ironic+Cinder.

Please see: https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms -
for more details.

Thanks,

||Rich

On Thu, Sep 7, 2017 at 11:09 AM Vikram Hosakote (vhosakot) <
vhosa...@cisco.com> wrote:

> Sending the confirmed cross-project meets with the kolla community:
>
>
>
> Monday with Triple-O at 2 pm
>
> Monday with Cinder and Ironic at 4 pm
>
>
>
> Regards,
>
> Vikram Hosakote
>
> IRC:  vhosakot
>
>
>
> *From: *Jay S Bryant <jungleb...@gmail.com>
> *Reply-To: *"jsbry...@electronicjungle.net" <jsbry...@electronicjungle.net>,
> "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> *Date: *Thursday, August 31, 2017 at 1:43 PM
> *To: *"openstack-dev@lists.openstack.org" <
> openstack-dev@lists.openstack.org>
> *Subject: *Re: [openstack-dev] [kolla] [cinder] [ironic] PTG
> cross-platform meetup possibility
>
>
>
> Rich,
>
> I can make Monday at 4 pm work.  Conflicts with some Docs discussions but
> I can step out for a bit.
>
> Thanks!
>
> Jay
>
>
>
>
>
> On 8/31/2017 8:25 AM, Richard Wellum wrote:
>
> Hi,
>
>
>
> How does Monday at 4pm sound? Kolla already has a cross-platform
> discussion with Triple-O at 2pm, so this would dovetail nicely.
>
>
>
> Thanks,
>
>
> ||Rich
>
>
>
> On Wed, Aug 30, 2017 at 2:48 PM Ivan Kolodyazhny <e...@e0ne.info> wrote:
>
> Hi team,
>
>
>
> I'm interested in cinder containerization too. It would be great if we can
> schedule our meetup after 3pm or even 4pm, It will increase my chances to
> attend it.
>
>
>
> Thanks in advance.
>
>
> Regards,
> Ivan Kolodyazhny,
> http://blog.e0ne.info/
>
>
>
> On Wed, Aug 30, 2017 at 4:23 PM, Dmitry Tantsur <dtant...@redhat.com>
> wrote:
>
> Hi!
>
> I'm all for it. Monday sounds okay to me, though I'll have to manage some
> conflicts, of course.
>
>
>
> On 08/29/2017 05:56 PM, Richard Wellum wrote:
>
> Hi Folks,
>
> Would there be some interest from Cinder and Ironic (and others of course)
> team members to have a quick session at the PTG with the Kolla team on the
> latest developments in Kolla (like the new kolla-ansible devmode for
> example)?
>
> Also it would give the Kolla team an opportunity to hear about your teams
> interest and experiences in containerization and what you need from Kolla
> going forward.
>
> I'm thinking an hour or two on Monday afternoon, the first day of the PTG?
>
> Thanks,
>
> ||Rich
>
> __
> 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
>
>
>
> __
> 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
>
>
>
> __
> 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] [kolla] [neutron] PTG cross-platform meetup possibility

[Richard Wellum]

Hi,

I have booked the room 'Vail', Tuesday from 2pm for these discussions.
Please see: https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms for
more details.

Thanks,

||Rich

On Thu, Sep 7, 2017 at 12:15 PM  wrote:

> Vikram Hosakote (vhosakot), 2017-09-07 15:38:
> > Would there be any interest in meeting with the Kolla team at the PTG
> > to discuss neutron’s
> > integration with containers and Kubernetes especially about the new
> > networking
> > technologies like VPP, fd.io, OpenDaylight, OVS-DPDK, OVN, service
> > chaining (SFC), etc?
> >
> > If yes, would Tuesday 2 pm work?  I’m thinking about an hour or two
> > for the session.
>
> If this happens I'm interested to follow.
>
> -Thomas
>
>
>
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
> recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been
> modified, changed or falsified.
> Thank you.
>
>
> __
> 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] [kolla] [cinder] [ironic] PTG cross-platform meetup possibility

[Richard Wellum]

Hi,

How does Monday at 4pm sound? Kolla already has a cross-platform discussion
with Triple-O at 2pm, so this would dovetail nicely.

Thanks,

||Rich

On Wed, Aug 30, 2017 at 2:48 PM Ivan Kolodyazhny <e...@e0ne.info> wrote:

> Hi team,
>
> I'm interested in cinder containerization too. It would be great if we can
> schedule our meetup after 3pm or even 4pm, It will increase my chances to
> attend it.
>
> Thanks in advance.
>
> Regards,
> Ivan Kolodyazhny,
> http://blog.e0ne.info/
>
> On Wed, Aug 30, 2017 at 4:23 PM, Dmitry Tantsur <dtant...@redhat.com>
> wrote:
>
>> Hi!
>>
>> I'm all for it. Monday sounds okay to me, though I'll have to manage some
>> conflicts, of course.
>>
>>
>> On 08/29/2017 05:56 PM, Richard Wellum wrote:
>>
>>> Hi Folks,
>>>
>>> Would there be some interest from Cinder and Ironic (and others of
>>> course) team members to have a quick session at the PTG with the Kolla team
>>> on the latest developments in Kolla (like the new kolla-ansible devmode for
>>> example)?
>>>
>>> Also it would give the Kolla team an opportunity to hear about your
>>> teams interest and experiences in containerization and what you need from
>>> Kolla going forward.
>>>
>>> I'm thinking an hour or two on Monday afternoon, the first day of the
>>> PTG?
>>>
>>> Thanks,
>>>
>>> ||Rich
>>>
>>>
>>>
>>> __
>>> 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
>>
>
> __
> 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

[openstack-dev] [kolla] [cinder] [ironic] PTG cross-platform meetup possibility

[Richard Wellum]

Hi Folks,

Would there be some interest from Cinder and Ironic (and others of course)
team members to have a quick session at the PTG with the Kolla team on the
latest developments in Kolla (like the new kolla-ansible devmode for
example)?

Also it would give the Kolla team an opportunity to hear about your teams
interest and experiences in containerization and what you need from Kolla
going forward.

I'm thinking an hour or two on Monday afternoon, the first day of the PTG?

Thanks,

||Rich
__
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] [kolla][PTL][elections] Candidacy for Kolla PTL

[Richard Wellum]

+1

Rich Wellum

On Wed, Aug 2, 2017 at 2:44 PM Michał Jastrzębski  wrote:

> Hello everyone,
>
> Once more unto the breach dear friends! I would like to run for PTL again
> for
> Queens. Pike was very exciting release for Kolla. With strong focus on
> Kolla-Kubernetes, Kolla-Ansible getting more and more production
> deployments
> and Kolla images being successfully consumed by project outside of Kolla
> like TripleO or OpenStack-Helm, I think this was quite a success for us.
>
> We managed to improve one of biggest pain points we saw in Kolla - gates.
> We
> still have lengths to go, but progress is significant.
>
> I'd love to help our community to make Queens even better. We have several
> exiting features in our plates, like automated push mechanism for images or
> orchestration layer for kolla-kubernetes.
>
> We also need to focus on another big pain point of Kolla - documentation.
>
> I would like us to strengthen cooperation with Kubernetes community and I'm
> strong believer that best bridge between communities is built on top of
> common
> technical issues and mutual help. I think Kolla-Kubernetes naturally helps
> with this cooperation and we can use it even more.
>
> Per request, I also add small haiku to my nomination;)
>
> Glues Stack together
> Project by great people made
> Queens approaching soon
>
> Regards,
> Michal inc0 Jastrzebski
>
> __
> 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] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables

[Richard Wellum]

As a relatively new member of the openstack community I think the idea of a
mentorship program is a good one; I'd like to throw my hat in the ring if
the kolla community needs a guinea-pig to try this on. :)

Rich

On Wed, Apr 12, 2017 at 7:53 PM Matt Riedemann  wrote:

> On 4/12/2017 3:40 PM, Steven Dake (stdake) wrote:
> > Matt,
> >
> > Thanks for the response.  It is helpful.
> >
> > Regards
> > -steve
> >
> > -Original Message-
> > From: Matt Riedemann 
> > Reply-To: "OpenStack Development Mailing List (not for usage questions)"
> 
> > Date: Wednesday, April 12, 2017 at 4:36 PM
> > To: "openstack-dev@lists.openstack.org" <
> openstack-dev@lists.openstack.org>
> > Subject: Re: [openstack-dev] [kolla][nova] Starting a core reviewer
> mentorship program for Kolla deliverables
> >
> > On 4/12/2017 11:59 AM, Steven Dake (stdake) wrote:
> > > Hey folks,
> > >
> > >
> > >
> > > In today’s Kolla team meeting, the idea was proposed of adopting
> nova’s
> > > “protocore” mentorship program for Kolla.  We would like to know
> what
> > > nova has learned from this effort.
> > >
> > >
> > >
> > > In today’s Kolla meeting we had broad consensus on the following:
> > >
> > > 1)   Kolla has participants that want to be core reviewers
> > >
> > > 2)   These participants don’t know how to become core reviewers
> > >
> > > 3)   The core reviewers in Kolla should mentor “protocore”
> reviewers
> > > on how to do good reviews
> > >
> > >
> > >
> > > From that, we concluded some form of mentorship program for
> potential
> > > core reviewers was in order.  We got into some debate about
> _/how/_ the
> > > program should be rolled out.  Let’s use this thread to discuss
> how it
> > > should be rolled out since that seems to be the sticking point of
> the
> > > discussion.  I saw no dissent in the discussion that the basic
> concepts
> > > were a negative change.
> > >
> > >
> > >
> > > I am aware that nova uses a +1 review from a “protocore” and a
> +2/+w
> > > from a core reviewer prior to merge.  Nova cores – would you mind
> > > defining your process (on the ml is fine) more thoroughly and your
> > > experiences so we can learn from you?
> > >
> > >
> > >
> > > All kolla contributors, feel free to debate the **how** such a
> > > mentorship program should be rolled out.  I think we have a lot to
> learn
> > > from our peers in the OpenStack community and learning from their
> > > experiences may be helpful.
> > >
> > >
> > >
> > > Regards
> > >
> > > -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
> > >
> >
> > Nova has this thing? That's news to me. :)
> >
> > I don't think Nova has a formal process for something like this.
> There
> > was talk at the BCN summit about giving some people +2 rights on
> parts
> > of the tree but not full core on everything. We never implemented
> that.
> >
> > Maybe what you're referring to is how we consider a +1 from a domain
> > expert like a +2, or at least something that's good to have before
> cores
> > are looking into the change in more detail? For example, gibi is the
> > lead for the versioned notifications effort and we/I generally look
> for
> > his +1 on a change before digging into it, or approving it. We have
> > similar unofficial things like this in other parts of Nova, or
> subteams,
> > like Timofey and Pawel with the live migration subteam.
> >
> > To be sure, someone that is leading a subteam effort and is looked to
> > for their opinion on a whole series of changes eventually gets into
> the
> > conversation when we're talking about potential core reviewers, in
> part
> > because, at least I personally, am looking for not only strong code
> > review skills but also leadership/ownership within the project,
> because
> > those are also the people that tend to stick around awhile so I'm
> more
> > comfortable investing my time into them (and building a trust
> > relationship with them).
> >
> > So that's all unofficial non-formal stuff and basically grew up
> > organically around the subteam efforts that started several releases
> > ago. I don't know if this helps you or not.
> >
> > --
> >
> > Thanks,
> >
> > Matt
> >
> >
>  __
> > OpenStack Development Mailing List (not for usage