Re: [openstack-dev] [kolla] Request for changing the meeting time to 1600 UTC for all meetings

[Mauricio Lima]

+1

2016-06-08 10:29 GMT-03:00 Jeffrey Zhang :

> it will be mid-night (0:00) in my local time. But i think i am OK with it.
> so +1 for this.
>
> On Wed, Jun 8, 2016 at 9:12 PM, Paul Bourke 
> wrote:
>
>> +1
>>
>> On 08/06/16 13:54, Swapnil Kulkarni (coolsvap) wrote:
>>
>>> Dear Kollagues,
>>>
>>> Some time ago we discussed the requirement of alternating meeting
>>> times for Kolla weekly meeting due to major contributors from
>>> kolla-mesos were not able to attend weekly meeting at UTC 1600 and we
>>> implemented alternate US/APAC meeting times.
>>>
>>> With kolla-mesos not active anymore and looking at the current active
>>> contributors, I wish to reinstate the UTC 1600 time for all Kolla
>>> Weekly meetings.
>>>
>>> Please let me know your views.
>>>
>>>
>> __
>> 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
>>
>
>
>
> --
> 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-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes repository management proposal up for vote

[Mauricio Lima]

Hello guys,

Reading the conversation and analyzing a few trouble that happened with
kolla-mesos and nothing can guarantee that will not happen the same with
the K8S, as well as ensuring that the history will not lost. So, don't
split the repo.
__
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][kubernetes][infra] kolla-kubernetes repository management proposal up for vote

[Mauricio Lima]

Just to clarify my vote.

+1 for single repository

2016-05-02 14:11 GMT-03:00 Jeff Peeler :

> Also +1 for working on kolla-kubernetes. (Please read this thread if
> you haven't yet):
>
> http://lists.openstack.org/pipermail/openstack-dev/2016-May/093575.html
>
> On Mon, May 2, 2016 at 10:56 AM, Ryan Hallisey 
> wrote:
> > +1 to start kolla-kubernetes work.
> >
> > - Original Message -
> > From: "Swapnil Kulkarni" 
> > To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> > Sent: Monday, May 2, 2016 12:59:40 AM
> > Subject: Re: [openstack-dev] [kolla][vote][kubernetes][infra]
> kolla-kubernetes repository management proposal up for vote
> >
> > On Mon, May 2, 2016 at 10:08 AM, Vikram Hosakote (vhosakot)
> >  wrote:
> >> A separate repo will land us in the same spot as we had with kolla-mesos
> >> originally.  We had all kinds of variance in the implementation.
> >>
> >> I’m in favor of a single repo.
> >>
> >> +1 for the single repo.
> >>
> >
> > I agree with you Vikram, but we should consider the bootstrapping
> > requirements for new deployment technologies and learn from our
> > failures with kolla-mesos.
> >
> > At the same time, it will help us evaluate the deployment technologies
> > going ahead without distrupting the kolla repo which we can treat as a
> > repo with stable images & associated deployment tools.
> >
> >> Regards,
> >> Vikram Hosakote
> >> IRC: vhosakot
> >>
> >> From: Vikram Hosakote 
> >> Date: Sunday, May 1, 2016 at 11:36 PM
> >>
> >> To: "OpenStack Development Mailing List (not for usage questions)"
> >> 
> >> Subject: Re: [openstack-dev] [kolla][vote][kubernetes][infra]
> >> kolla-kubernetes repository management proposal up for vote
> >>
> >> Please add me too to the list!
> >>
> >> Regards,
> >> Vikram Hosakote
> >> IRC: vhosakot
> >>
> >> From: Michał Jastrzębski 
> >> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
> >> 
> >> Date: Saturday, April 30, 2016 at 9:58 AM
> >> To: "OpenStack Development Mailing List (not for usage questions)"
> >> 
> >> Subject: Re: [openstack-dev] [kolla][vote][kubernetes][infra]
> >> kolla-kubernetes repository management proposal up for vote
> >>
> >> Add me too please Steven.
> >>
> >> On 30 April 2016 at 09:50, Steven Dake (stdake) 
> wrote:
> >>
> >> Fellow core reviewers,
> >>
> >> We had a fantastic turnout at our fishbowl kubernetes as an underlay for
> >> Kolla session.  The etherpad documents the folks interested and
> discussion
> >> at summit[1].
> >>
> >> This proposal is mostly based upon a combination of several discussions
> at
> >> open design meetings coupled with the kubernetes underlay discussion.
> >>
> >> The proposal (and what we are voting on) is as follows:
> >>
> >> Folks in the following list will be added to a kolla-k8s-core group.
> >>
> >>   This kolla-k8s-core group will be responsible for code reviews and
> code
> >> submissions to the kolla repository for the /kubernetes top level
> directory.
> >> Individuals in kolla-k8s-core that consistently approve (+2) or
> disapprove
> >> with a (-2) votes to TLD directories other then kubernetes will be
> handled
> >> on a case by case basis with several "training warnings" followed by
> removal
> >> of the kolla-k8s-core group.  The kolla-k8s-core group will be added as
> a
> >> subgroup of the kolla-core reviewer team, which means they in effect
> have
> >> all of the ACL access as the existing kolla repository.  I think it is
> >> better in this case to trust these individuals to the right thing and
> only
> >> approve changes for the kubernetes directory until proposed for the
> >> kolla-core reviewer group where they can gate changes to any part of the
> >> repository.
> >>
> >> Britt Houser
> >>
> >> mark casey
> >>
> >> Steven Dake (delta-alpha-kilo-echo)
> >>
> >> Michael Schmidt
> >>
> >> Marian Schwarz
> >>
> >> Andrew Battye
> >>
> >> Kevin Fox (kfox)
> >>
> >> Sidharth Surana (ssurana)
> >>
> >>   Michal Rostecki (mrostecki)
> >>
> >>Swapnil Kulkarni (coolsvap)
> >>
> >>MD NADEEM (mail2nadeem92)
> >>
> >>Vikram Hosakote (vhosakot)
> >>
> >>Jeff Peeler (jpeeler)
> >>
> >>Martin Andre (mandre)
> >>
> >>Ian Main (Slower)
> >>
> >> Hui Kang (huikang)
> >>
> >> Serguei Bezverkhi (sbezverk)
> >>
> >> Alex Polvi (polvi)
> >>
> >> Rob Mason
> >>
> >> Alicja Kwasniewska
> >>
> >> sean mooney (sean-k-mooney)
> >>
> >> Keith Byrne (kbyrne)
> >>
> >> Zdenek Janda (xdeu)
> >>
> >> Brandon Jozsa (v1k0d3n)
> >>
> >> Rajath Agasthya (rajathagasthya)
> >>
> >>
> >> If you already are in the kolla-core review team, you won't be added to
> the
> >> kolla-k8s-core team as you will already have the necessary ACLs to do
> the
> >> 

Re: [openstack-dev] [kolla] better solution for the non-ini format configure file

[Mauricio Lima]

I agree with your approach Jeffrey, although this is not ideal, this is an
approach already used in kolla.

2016-05-04 12:01 GMT-03:00 Jeffrey Zhang :

> Recently, Jack Ning pushed a PS[0], which export the `WEBROOT` to the
> globals.yml file.
> Because there is no chance to change the horizon/apache configure file now.
>
> The root cause is that: Kolla do not support non-ini format configure
> file. for the
> ini-format file, we use a merge_config module[1] to merge all the found
> file. But it
> will be not work for configure file for apache, rabbitmq and so on.
>
> I would like to the current merge_config implementation. It is directly
> and easy to use.
> Not like the puppet, we have to remember the variable name defined in the
> module. we have
> no chance to add some user-defined variable.
>
> Export the variable to global is very bad and ugly. It will became a
> disaster when more
> and more variables is exported.
>
> So we should catch up a better solution to handle the configure file.
>
> One solution I have is use overwrite mechanism. for example when there is
> a file in
> /etc/kolla/config/apache.conf, it will overwrite the templates in the
> roles. But this
> is still not ideal.
>
> Any body has better solution?
>
> [0] https://review.openstack.org/306928
> [1]
> http://git.openstack.org/cgit/openstack/kolla/tree/ansible/action_plugins/merge_configs.py
>
> --
> 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-dev] [kolla] xenial or trusty

[Mauricio Lima]

Which will be the default when kolla begin to support xenial? Xenial or
Trusty?

One proposal is to support both, at least in this beginning and just do
some checks to get which version that the user is using.

Regards,
__
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] Proposing Mauricio Lima for core reviewer

[Mauricio Lima]

Thanks guys, it's a privilege to be part of team. :)

2016-05-24 17:02 GMT-03:00 Steven Dake (stdake) <std...@cisco.com>:

> From: Steven Dake <std...@cisco.com>
> Reply-To: "openstack-dev@lists.openstack.org" <
> openstack-dev@lists.openstack.org>
> Date: Tuesday, May 17, 2016 at 12:00 PM
> To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org
> >
> Subject: [openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer
>
> Hello core reviewers,
>
> I am proposing Mauricio (mlima on irc) for the core review team.  He has
> done a fantastic job reviewing appearing in the middle of the pack for 90
> days [1] and appearing as #2 in 45 days [2].  His IRC participation is also
> fantastic and does a good job on technical work including implementing
> Manila from zero experience :) as well as code cleanup all over the code
> base and documentation.  Consider my proposal a +1 vote.
>
> I will leave voting open for 1 week until May 24th.  Please vote +1
> (approve), or –2 (veto), or abstain.  I will close voting early if there is
> a veto vote, or a unanimous vote is reached.
>
> Thanks,
> -steve
>
> [1] http://stackalytics.com/report/contribution/kolla/90
> [2] http://stackalytics.com/report/contribution/kolla/45
>
>
> Mauricio,
>
> Congratulations, the vote passed with (iirc 10 votes).  A couple people
> are out on vacation, so I wouldn't take offense :)
>
> I've added you to the appropriate group in gerrit.  Ping me when you next
> see me and I'll give you a crash course on the policies for core reviewers.
>
> 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
>
>
__
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] Applying for stable-follows tag

[Mauricio Lima]

+1

2016-07-19 12:23 GMT-03:00 Vikram Hosakote (vhosakot) :

> +1 sure.
>
> Regards,
> Vikram Hosakote
> IRC:  vhosakot
>
> From: Michał Jastrzębski 
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Tuesday, July 19, 2016 at 9:20 AM
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag
>
> +1 ofc
>
> On 19 July 2016 at 06:02, Ryan Hallisey  wrote:
>
> +1
>
> -Ryan
>
> - Original Message -
> From: "Jeffrey Zhang" 
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Sent: Monday, July 18, 2016 9:16:09 PM
> Subject: Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag
>
> +1 to apply
> I'd like to be the volunteer.
>
> On Mon, Jul 18, 2016 at 9:04 PM, Swapnil Kulkarni (coolsvap)
>  wrote:
>
> On Mon, Jul 18, 2016 at 6:23 PM, Paul Bourke 
> wrote:
>
> Hi Steve,
>
> +1 to applying. I'll volunteer for the backport team also.
>
> -Paul
>
>
> On 18/07/16 13:07, Steven Dake (stdake) wrote:
>
>
> Hey Koalians,
>
> I'd like us to consider applying  for the stable follows policy tag.
>Full details are here:
>
>
>
> http://github.com/openstack/governance/blob/master/reference/tags/stable_follows-policy.rst
>
> Because of the magic work we did to make liberty functional, it is
> possible that we may not be able to apply for this tag until Liberty
> falls into EOL.  Still I personally believe intent matters most, and our
> intent has always been for these to be stable low-rate-of-change
> no-feature-backport branches.  There are some exceptions I think we
> would fit under for the Liberty case, so I think it is worth a shot.
>
> I'd need 2-4 people to commit to joining the stable backport team for
> Kolla reviews specifically.  These folks would be the only folks that
> could ACK patches in the stable branch maintenance queue.  Anyone could
> continue to submit backport patches as they desire.
>
> I'll leave voting open for 1 week or until there I a majority (6 core
> reviewers) or until there is a unanimous vote.  If there is not, then we
> won't apply.  The deadline for this vote is July 25th.
>
> Thanks!
> -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
>
>
> __
> 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 to apply for stable follows policy.
> I would like to volunteer for the backport team.
>
> __
> 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
>
>
>
>
> --
> 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
>
>
> __
> 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] New specs process - a dicussion

[Mauricio Lima]

+1 I agree

2016-07-12 13:55 GMT-03:00 Paul Bourke :

> Sounds reasonable +1
>
>
> On 12/07/16 15:32, Michał Jastrzębski wrote:
>
>> Hey guys,
>>
>> Since our project matured, we decided that we should have a discussion
>> regarding our spec process.
>>
>> https://etherpad.openstack.org/p/kolla-N-midcycle-specs
>>
>> Currently we do specs for most critical things, and they require majority
>> vote.
>>
>> We want to introduce another way, to enable non-nuclear specs.
>> To summarize our discussion so far:
>>
>> 1. Specs will require only 2 * +2 by default
>> 2. Specs sit at minimum 2 weeks in gerrit before first +2 arrives, so
>> other people will have time to look at it
>> 3. Any core can require a rollcall vote - then it becomes rollcall vote
>> 4. If nobody calls for rollcall vote, after 2 weeks spec can be merged
>> with normal 2 * +2
>>
>> Thoughts?
>> 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] [vote][kolla] deprecation for Debian distro support

[Mauricio Lima]

2

2017-01-19 8:50 GMT-03:00 Steven Dake (stdake) :

> My vote is for option 2 to deprecate Debian as there has been very little
> activity and operators seem uninterested in Debian as a platform.
>
> We could always add it back in at a later date if operators were to
> request it and the Debian team were interested in maintaining it.
>
> Regards
> -steve
>
>
> -Original Message-
> From: Christian Berendt 
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Thursday, January 19, 2017 at 3:53 AM
> To: "openstack-dev@lists.openstack.org"  >
> Subject: [openstack-dev] [vote][kolla] deprecation for Debian distro
> support
>
> As discussed in one of the last team meetings I want to propose the
> deprecation (this cycle) and removal (next cycle) of the Debian support in
> Kolla.
>
> More than 1 week ago I sent a pre warning mail to the
> openstack-operators mailing list, without any reply [0].
>
> Kolla core reviewers, please vote now. The vote will be open for 7
> days (26.01.2017).
>
> 1. Kolla needs support for Debian, it should not be deprecated
>
> 2. Kolla should deprecate support for Debian
>
> [0] http://lists.openstack.org/pipermail/openstack-operators/
> 2017-January/012427.html
>
> --
> Christian Berendt
> Chief Executive Officer (CEO)
>
> Mail: bere...@betacloud-solutions.de
> Web: https://www.betacloud-solutions.de
>
> Betacloud Solutions GmbH
> Teckstrasse 62 / 70190 Stuttgart / Deutschland
>
> Geschäftsführer: Christian Berendt
> Unternehmenssitz: Stuttgart
> Amtsgericht: Stuttgart, HRB 756139
>
>
> 
> __
> 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] [vote][kolla] Core nomination proposal for Eduardo Gonzalez Gutierrez (egonzales90 on irc)

[Mauricio Lima]

+1
Em 19/08/2016 14:14, "Jeffrey Zhang"  escreveu:

> +1
>
> On Sat, Aug 20, 2016 at 1:07 AM, Swapnil Kulkarni 
> wrote:
> > Thanks sdake.
> >
> > +1 :)
> >
> > On Aug 19, 2016 10:35 PM, "Steven Dake (stdake)" 
> wrote:
> >>
> >> Coolsvap mentioned he wasn't receiving his emails at his home email
> >> server, so he will respond from a different mail service.  Just bringing
> >> this up again so he can see the thread.
> >>
> >> Regards
> >> -steve
> >>
> >> On 8/19/16, 7:09 AM, "Kwasniewska, Alicja" <
> alicja.kwasniew...@intel.com>
> >> wrote:
> >>
> >> >+1 :)
> >> >
> >> >-Original Message-
> >> >From: Ryan Hallisey [mailto:rhall...@redhat.com]
> >> >Sent: Friday, August 19, 2016 2:50 PM
> >> >To: OpenStack Development Mailing List (not for usage questions)
> >> >
> >> >Subject: Re: [openstack-dev] [vote][kolla] Core nomination proposal for
> >> >Eduardo Gonzalez Gutierrez (egonzales90 on irc)
> >> >
> >> >+1
> >> >
> >> >-Ryan
> >> >
> >> >- Original Message -
> >> >From: "Steven Dake (stdake)" 
> >> >To: "OpenStack Development Mailing List (not for usage questions)"
> >> >
> >> >Sent: Thursday, August 18, 2016 7:09:35 PM
> >> >Subject: [openstack-dev] [vote][kolla] Core nomination proposal for
> >> >Eduardo Gonzalez Gutierrez (egonzales90 on irc)
> >> >
> >> >Kolla Core Review Team:
> >> >
> >> >I am nominating Eduardo for the core reviewer team. His reviews are
> >> >fantastic, as I'm sure most of you have seen after looking over the
> >> >review queue. His 30 day stats place him at #3 by review count [1] and
> 60
> >> >day stats [2] at #4 by review count. He is also first to review a
> >> >significant amount of the time ­ which is impressive for someone new to
> >> >Kolla. He participates in IRC and he has done some nice code
> contribution
> >> >as well [3] including the big chunk of work on enabling Senlin in
> Kolla,
> >> >the dockerfile customizations work, as well as a few documentation
> fixes.
> >> >Eduardo is not affiliated with any particular company. As a result he
> is
> >> >not full time on Kolla like many of our other core reviewers. The fact
> >> >that he is part time and still doing fantastically well at reviewing
> is a
> >> >great sign of things to come :)
> >> >
> >> >Consider this nomination as my +1 vote.
> >> >
> >> >Voting is open for 7 days until August 24th. Joining the core review
> team
> >> >requires a majority of the core review team to approve within a 1 week
> >> >period with no veto (-1) votes. If a veto or unanimous decision is
> >> >reached prior to August 24th, voting will close early.
> >> >
> >> >Regards
> >> >-steve
> >> >
> >> >[1] http://stackalytics.com/report/contribution/kolla/30
> >> >[2] http://stackalytics.com/report/contribution/kolla/60
> >> >[3]
> >>
> >> > >https://review.openstack.org/#/q/owner:%22Eduardo+Gonzalez+
> %253Cdabarren%2
> >> >540gmail.com%253E%22
> >> >
> >>
> >> > >___
> ___
> >> >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
> >
>
>
>
> --
> 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
>

Re: [openstack-dev] [kolla] which footer format we need

[Mauricio Lima]

I agree with Jeffrey.

2016-09-02 11:52 GMT-03:00 Michał Jastrzębski :

> +1 to Jeffrey's points. We should deprecate old footer mechanism and
> remove it alltogether in Ocata timeframe.
>
> On 1 September 2016 at 23:51, Jeffrey Zhang 
> wrote:
> > 1. so i think we need add the deprecated status to the include_footer
> option
> > and print a warn.
> > 2. when the use specifies both two footers,  they should both work rather
> > than ignore one. it print warn already.
> >
> > On Fri, Sep 2, 2016 at 11:42 AM, Swapnil Kulkarni 
> > wrote:
> >>
> >> On Fri, Sep 2, 2016 at 8:32 AM, Jeffrey Zhang 
> >> wrote:
> >> > We introduced customization solution.
> >> >
> >> > Now, we support two format of footer.
> >> >
> >> > 1. the legacy way: {{ include_footer }}
> >> > 2. the new way: {% block footer %}{% endblock %}
> >> >
> >> > there two conflict about this now[0][1].
> >> >
> >> > I think the option 2 is better. We can get more consistent solution.
> >> >
> >> > [0] https://review.openstack.org/#/c/357746
> >> > [1] https://review.openstack.org/#/c/361253
> >> >
> >> > --
> >> > 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
> >> >
> >>
> >>
> >> I tend towards #2, patchset [0] is corresponding to a discussion on
> >> #openstack-kolla and if we keep #2, we need to keep #1 in all
> >> dockerfiles with a deprecation warning for next cycle.
> >>
> >> Also what if user specifies both the footer blocks? We need to confirm
> >> we ignore  #1 if #2 is chosen.
> >>
> >> 
> __
> >> 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
> >
> >
> >
> >
> > --
> > 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] [vote][kolla] Core Nomination for Christian Berendt (berendt on irc)

[Mauricio Lima]

+1

2016-09-08 5:52 GMT-03:00 Dave Walker :

> +1
>
> Great stuff Christian
>
> On 8 September 2016 at 03:59, Steven Dake (stdake) 
> wrote:
>
>> Kolla core reviewer team,
>>
>>
>>
>> It is my pleasure to nominate Christian Berendt for the Kolla core team.
>>
>>
>>
>> Christian’s output over the last cycle has been fantastic – cracking the
>> top 10 reviewer list for the full cycle.  His 30 day stats [1] place him in
>> solid 7th position, and considering the size of the core review team we
>> have, this is a great accomplishment.  Christian also has solid 60 day
>> review stats [2] place him in solid 7th position.  But more importantly
>> his reviews are of high quality.  He has great IRC participation as well as
>> having implemented all kinds of bug fixes all over the code base.  He
>> clearly understands Kolla by the quality of his reviews.
>>
>>
>>
>> Consider this nomination a +1 vote from me.
>>
>>
>>
>> A +1 vote indicates you are in favor of Christian as a candidate, a 0
>> vote indicates an abstain, and a -1 is a veto.  Voting is open for 7 days
>> until September 15th, or a unanimous response is reached or a veto vote
>> occurs.  If a unanimous response is reached or a veto occurs, voting will
>> close early.
>>
>>
>>
>> Regards,
>>
>> -steve
>>
>>
>>
>> [1] http://stackalytics.com/report/contribution/kolla/30
>>
>> [2] http://stackalytics.com/report/contribution/kolla/60
>>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> 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] [vote][kolla] Splitting out Ansible into a separate deliverable

[Mauricio Lima]

Option c.

2016-09-15 8:25 GMT-03:00 Eduardo Gonzalez :

> Option C
>
> On Thu, Sep 15, 2016, 1:23 PM Dave Walker  wrote:
>
>> Option C
>>
>> Thanks
>>
>> On 15 September 2016 at 12:10, Ryan Hallisey  wrote:
>>
>>> Option c.
>>>
>>> - Ryan
>>>
>>> > On Sep 15, 2016, at 4:33 AM, Paul Bourke 
>>> wrote:
>>> >
>>> > c)   Split the repository shortly after tagging 3.0.0 – creating a
>>> kolla-ansible deliverable for Ocata.
>>> >
>>> >> On 15/09/16 07:12, Steven Dake (stdake) wrote:
>>> >> Core Reviewers:
>>> >>
>>> >>
>>> >>
>>> >> The facts:
>>> >>
>>> >> We have roughly 250 bugs in rc2.  Of those, I suspect over half can
>>> just
>>> >> be closed out as dupes, fixed, wontfix, or the like.
>>> >>
>>> >> The core reviewer team has had various discussions around splitting
>>> the
>>> >> repository at various times but has not come to a concrete conclusion
>>> >> via a vote.
>>> >>
>>> >> Once RC1 is tagged, the stable/newton branch will be created
>>> automatically.
>>> >>
>>> >> All rc2 bug fixes will require bug IDs and backports to stable/newton
>>> to
>>> >> enable the ability to manage the release of rc2 and 3.0.0.
>>> >>
>>> >> There is an expectation for core reviewers to do the work of
>>> backporting
>>> >> to stable/newton – only our backports team typically does this work –
>>> >> however during release we really need everyone’s participation.
>>> >>
>>> >>
>>> >>
>>> >> My understanding of general consensus beliefs:
>>> >>
>>> >> We believe splitting out the Ansible implementation into a separate
>>> >> repository will produce a better outcome for both Kolla-Ansible and
>>> >> Kolla-Kubernetes
>>> >>
>>> >> We have been unable to achieve consensus on the right timing for a
>>> repo
>>> >> split in the past but generally believe the timing is right at some
>>> >> point between rc1 and Summit or shortly thereafter, if we are to do
>>> the
>>> >> repo split during Newton or very early Ocata.)
>>> >>
>>> >>
>>> >>
>>> >> This vote is a multiple choice (one choice please) vote.  Feel free to
>>> >> discuss before making a decision.
>>> >>
>>> >>
>>> >>
>>> >> Please vote:
>>> >>
>>> >> a)   Do not split the repository between rc1 and Summit or shortly
>>> >> thereafter at all, keeping the Ansible implementation intact in Ocata
>>> >>
>>> >> b)   Split the repository shortly after tagging RC1 – creating of
>>> a
>>> >> kolla-ansible deliverable for Ocata.
>>> >>
>>> >> c)   Split the repository shortly after tagging 3.0.0 – creating a
>>> >> kolla-ansible deliverable for Ocata.
>>> >>
>>> >>
>>> >>
>>> >> Voting is open for 7 days until September 21^st , 2016. Please do not
>>> >> abstain on this critical vote.  Remember, no veto vote is available in
>>> >> roll-call votes.  If a majority can’t be reached on any one choice,
>>> but
>>> >> there is a majority around B & C, (which are the same idea, but
>>> >> different timing) a second vote will be triggered around when to split
>>> >> the repository.  The implication there is if you vote for b or c, your
>>> >> voting for a repository split.  If you vote for A you are voting for
>>> no
>>> >> repository split.  I hate to overload voting in this way.  It is only
>>> an
>>> >> optimization to speed things up as execution may need to happen now,
>>> or
>>> >> can be pushed out a month, or may not be needed at this time.
>>> >>
>>> >>
>>> >>
>>> >> 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
>>> >
>>> > 
>>> __
>>> > 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
> 

Re: [openstack-dev] [vote][kolla] deprecation for fedora distro support

[Mauricio Lima]

Option 2

2016-09-19 14:56 GMT-03:00 Christian Berendt :

> Thanks for moving this forward.
>
> > On 19 Sep 2016, at 19:40, Jeffrey Zhang  wrote:
> >
> > 1. Kolla needs support fedora( if so, we need some guys to set up the
> > gate and fix all the issues ASAP in O cycle)
> > 2. Kolla should deprecate fedora support
>
> +1 on option 2.
>
> __
> 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] [vote][kolla] deprecation for debian distro support

[Mauricio Lima]

Option 2

2016-09-19 14:55 GMT-03:00 Christian Berendt :

> Thanks for moving this forward.
>
> > On 19 Sep 2016, at 19:44, Jeffrey Zhang  wrote:
> >
> > Please vote:
> >
> > 1. Kolla needs support Debian( if so, we need some guys to set up the
> > gate and fix all the issues ASAP in O cycle)
> > 2. Kolla should deprecate Debian support
>
> +1 on option 2.
>
> __
> 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 Dave Walker (Daviey on irc)

[Mauricio Lima]

+1

2016-08-24 9:15 GMT-03:00 Kwasniewska, Alicja 
:

> +1
>
>
>
> *From:* Eduardo Gonzalez [mailto:dabar...@gmail.com]
> *Sent:* Wednesday, August 24, 2016 1:42 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [kolla][vote] Core nomination for Dave
> Walker (Daviey on irc)
>
>
>
> +1
>
>
>
> On Wed, Aug 24, 2016, 1:25 PM Martin André  wrote:
>
> +1
>
> On Tue, Aug 23, 2016 at 10:45 PM, Steven Dake (stdake) 
> wrote:
> > Kolla core reviewers,
> >
> > I am nominating Dave Walker for the Kolla core reviewer team.  His 30 day
> > review stats [1] place him in the middle of the pack for reviewers and
> his
> > 60 day stats[2] are about equivalent.  Dave participates heavily in IRC
> and
> > has done some good technical work including the Watcher playbook and
> > container.  He also worked on Sensu, but since we are unclear if we are
> > choosing Sensu or Tig, that work is on hold.  He will also be helping us
> > sort out how to execute with PBR going into the future on our stable and
> > master branches.  Dave has proven to me his reviews are well thought out
> and
> > he understands the Kolla Architecture.  Dave is part time like many Kolla
> > core reviewers and is independent of any particular affiliation.
> >
> > Consider this nomination as a +1 from me.
> >
> > As a reminder, a +1 vote indicates you approve of the candidate, an
> abstain
> > vote indicates you don't care or don't know for certain, and a –1 vote
> > indicates a veto.  If a veto occurs or a unanimous response is reached
> prior
> > to our 7 day voting window which concludes on August 30th, voting will be
> > closed early.
> >
> > [1] http://stackalytics.com/report/contribution/kolla/30
> > [2] http://stackalytics.com/report/contribution/kolla/60
> >
> > 
> __
> > 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][kolla-ansible][kolla-kubernetes] Kolla core election policy change - vote

[Mauricio Lima]

+1

2016-11-16 16:55 GMT-03:00 Ryan Hallisey :

> +1
>
> -Ryan
>
> - Original Message -
> From: "Michał Jastrzębski" 
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Sent: Wednesday, November 16, 2016 1:23:27 PM
> Subject: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla
> core election policy change - vote
>
> Hello,
>
> In light of recent events (kolla-kubernetes becoming thriving project,
> kolla-ansible being split) I feel we need to change of core reviewer
> election process.
>
> Currently Kolla was single core team. That is no longer the case, as
> right now we have 3 distinct core teams (kolla, kolla-ansible and
> kolla-kubernetes), although for now with big overlap in terms of
> people in them.
>
> For future-proofing, as we already have difference between teams, I
> propose following change to core election process:
>
>
> Core reviewer voting rights are reserved by core team in question.
> Which means if someone propose core reviewer to kolla-kubernetes, only
> kolla-kubernetes cores has a voting right (not kolla or kolla-ansible
> cores).
>
>
> Voting will be open until 30 Nov '16 end of day. Reviewers from all
> core teams in kolla has voting rights on this policy change.
>
> 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] [kolla] Source build gates are now voting

[Mauricio Lima]

great!

2016-11-18 14:51 GMT-03:00 Michał Jastrzębski :

> Hello,
>
> Since we split ansible, we can now afford to have some voting gates,
> for start - source build gates for 3 major distros are now voting.
>
> Cheers,
> 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

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

[Mauricio Lima]

I Agree. +1

2016-11-03 10:21 GMT-03:00 Paul Bourke :

> Kolleagues,
>
> How do people feel above removing the requirement of having TrivialFix in
> commit messages where a bug/bp is not required?
>
> I'm seeing a lot of valid and important commits being held up because of
> this, in my opinion, unnecessary requirement. It also causes friction for
> new contributers to the project.
>
> Are there any major benefits we're getting from the use of this tag that
> I'm missing?
>
> Cheers,
> -Paul
>
> __
> 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 to add zhubingbing to core team

[Mauricio Lima]

+1

2016-11-29 13:21 GMT-03:00 Michał Jastrzębski :

> Hello team!
>
> I'd like to propose to add zhubingbing to kolla (and kolla-ansible)
> core teams. He did great job reviewing code during last couple of
> months.
>
> Consider this proposal +1 from me, voting will be open for 1 week
> (until Dec 6) or if we get unanimous agreement (or veto) before.
>
> 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

Re: [openstack-dev] [kolla] Proposing duonghq for core

[Mauricio Lima]

+1

2017-03-08 7:34 GMT-03:00 Christian Berendt 
:

> +1
>
> > On 8 Mar 2017, at 07:41, Michał Jastrzębski  wrote:
> >
> > Hello,
> >
> > I'd like to start voting to include Duong (duonghq) in Kolla and
> > Kolla-ansible core teams. Voting will be open for 2 weeks (ends at
> > 21st of March).
> >
> > Consider this my +1 vote.
> >
> > Cheers,
> > 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
>
> --
> Christian Berendt
> Chief Executive Officer (CEO)
>
> Mail: bere...@betacloud-solutions.de
> Web: https://www.betacloud-solutions.de
>
> Betacloud Solutions GmbH
> Teckstrasse 62 / 70190 Stuttgart / Deutschland
>
> Geschäftsführer: Christian Berendt
> Unternehmenssitz: Stuttgart
> Amtsgericht: Stuttgart, HRB 756139
>
>
> __
> 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-ansible] Proposing Surya (spsurya) for core

[Mauricio Lima]

+1

2017-06-28 13:07 GMT-03:00 Swapnil Kulkarni :

> On Wed, Jun 14, 2017 at 9:16 PM, Michał Jastrzębski 
> wrote:
> > Hello,
> >
> > With great pleasure I'm kicking off another core voting to
> > kolla-ansible and kolla teams:) this one is about spsurya. Voting will
> > be open for 2 weeks (till 28th Jun).
> >
> > Consider this mail my +1 vote, you know the drill:)
> >
> > 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
>
>
> +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

Re: [openstack-dev] [kolla][kolla-ansible] Proposing Bertrand Lallau for kolla and kolla-ansible core

[Mauricio Lima]

+1

2017-05-03 1:43 GMT-03:00 Christian Berendt 
:

> +1
>
> > On 2. May 2017, at 17:30, Michał Jastrzębski  wrote:
> >
> > Hello,
> >
> > It's my pleasure to start another core reviewer vote. Today it's
> > Bertrand (blallau). Consider this mail my +1 vote. Members of
> > kolla-ansible and kolla core team, please cast your votes:) Voting
> > will be open for 2 weeks (until 16th of May).
> >
> > I also wanted to say that Bertrand went through our core mentorship
> > program (if only for few weeks because he did awesome job before too)
> > :)
> >
> > Thank you,
> > 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
>
> --
> Christian Berendt
> Chief Executive Officer (CEO)
>
> Mail: bere...@betacloud-solutions.de
> Web: https://www.betacloud-solutions.de
>
> Betacloud Solutions GmbH
> Teckstrasse 62 / 70190 Stuttgart / Deutschland
>
> Geschäftsführer: Christian Berendt
> Unternehmenssitz: Stuttgart
> Amtsgericht: Stuttgart, HRB 756139
>
>
> __
> 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