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

[Kwasniewska, Alicja]

+1 Congrats☺

Regards,
Alicja Kwasniewska

From: "Vikram Hosakote (vhosakot)" 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Monday, May 8, 2017 at 6:54 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

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

+1  Great job Bertrand!

Regards,
Vikram Hosakote
IRC:  vhosakot

From: Michał Jastrzębski >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Tuesday, May 02, 2017 at 10:13 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla][kolla-ansible] Proposing Bertrand Lallau for 
kolla and kolla-ansible core

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
__
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

[Kwasniewska, Alicja]

+1

From: Mauricio Lima >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Wednesday, March 8, 2017 at 5:34 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: Re: [openstack-dev] [kolla] Proposing duonghq for core

+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][kolla-kubernetes] Kolla core election policy change - vote

[Kwasniewska, Alicja]

+1

From: Jeffrey Zhang [mailto:zhang.lei@gmail.com]
Sent: Thursday, November 17, 2016 2:56 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla 
core election policy change - vote

+1

On Thu, Nov 17, 2016 at 8:26 PM, Steven Dake (stdake) 
> wrote:
Can we stick to one tag [kolla] for all ML discussion?  A whole slew of people 
already have filters setup.  Kolla is one project with one mission with 
multiple deliverables.  No other project that has multiple deliverables tags 
emails per deliverable.  I don’t think this is an occasion to be a special 
snowflake.

TIA :)
-steve





On 11/16/16, 11:23 AM, "Michał Jastrzębski" 
> wrote:

>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



--
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][vote] Core nomination for Dave Walker (Daviey on irc)

[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) 

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

Re: [openstack-dev] [vote][kolla] Core nomination proposal for Eduardo Gonzalez Gutierrez (egonzales90 on irc)

[Kwasniewska, Alicja]

+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%2540gmail.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

Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag

[Kwasniewska, Alicja]

+1 too

From: Mauricio Lima [mailto:mauricioli...@gmail.com]
Sent: Tuesday, July 19, 2016 5:29 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag

+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)" 
>
Date: Tuesday, July 19, 2016 at 9:20 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
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)" 
>
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

Re: [openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer

[Kwasniewska, Alicja]

+1

Kind regards,
Alicja 

-Original Message-
From: Michał Jastrzębski [mailto:inc...@gmail.com] 
Sent: Wednesday, May 18, 2016 6:41 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer

+1 :)

On 18 May 2016 at 10:02, Ryan Hallisey  wrote:
> +1 nice work mlima!
>
> -Ryan
>
> - Original Message -
> From: "Vikram Hosakote (vhosakot)" 
> To: openstack-dev@lists.openstack.org
> Sent: Wednesday, May 18, 2016 9:45:53 AM
> Subject: Re: [openstack-dev] [kolla] Proposing Mauricio Lima for core   
> reviewer
>
> Yes, +1 for sure!
>
> Thanks a lot Mauricio for all the great work especially for adding 
> Manila to kolla and also updating the cleanup scripts and documentation!
>
>
> Regards,
> Vikram Hosakote
> IRC: vhosakot
>
> From: "Steven Dake (stdake)" < std...@cisco.com >
> Reply-To: " openstack-dev@lists.openstack.org " < 
> openstack-dev@lists.openstack.org >
> Date: Tuesday, May 17, 2016 at 3: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
>
> __
>  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][vote][kubernetes][infra] kolla-kubernetes repository management proposal up for vote

[Kwasniewska, Alicja]

+1

Cheers,
Alicja


-Original Message-
From: Hui Kang [mailto:hkang.sun...@gmail.com] 
Sent: Sunday, May 1, 2016 12:40 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

+1

- Hui

On Sat, Apr 30, 2016 at 10:50 AM, 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 job.  If you feel you would like to join this initial 
> bootstrapping process, please add your name to the etherpad in [1].
>
> After 8 weeks (July 15h), folks that have not been actively reviewing 
> or committing code will be removed from the kolla-k8s-core group.  We 
> will use the governance repository metrics for team size [2] which is 
> either 30 reviews over 6 months (in this case, 10 reviews), or 6 
> commits over 6 months (in this case 2 commits) to the repository.  
> Folks that don't meet the qualifications are still welcome to commit 
> to the repository and contribute code or documentation but will lose approval 
> rights on patches.
>
> The kubernetes codebase will be maintained in the 
> https://github.com/openstack/kolla repository under the kubernees top 
> level directory.  Contributors that become active in the kolla 
> repository itself will be proposed over time to the kolla-core group.  
> Only core-kolla members will be permitted to participate in policy 
> decisions and voting thereof, so there is some minimal extra 
> responsibility involved in joining the kolla-core ACL team for those 
> folks wanting to move into the kolla core team over time.  The goal 
> will be to over time entirely remove the kolla-k8s-core team and make one 
> core reviewer team in the kolla-core ACL.
>
> Members in the kolla-k8s-core group will have the ability to +2 or –2 
> any change to the main kolla repository via ACLs, however, I propose 
> we trust these folks to only +2/-2 changes related to the kubernetes 
> directory in the kolla repository and remove folks that consistently break 
> this agreement.
> Initial errors as folks learn the system will be tolerated and commits 
> reverted as makes sense.
>
> I feel we made a couple errors with the creation of Kolla-mesos that I 
> feel needs correction.  Our first error the kolla-mesos-core team made 
> a lack of a diversely affiliated team membership developing the code 
> base.  The above list has significant diversity.  The second error is 
> that the repository was split in the first place.  This resulted in a 
> separate ABI to the containers being implemented which was a sore spot 
> for me personally.  We did our best to build both sides of the bridge 
> here, but this time I'd like the bridge between these two interests 
> and set of individuals to be fully built before 

Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

[Kwasniewska, Alicja]

+1

Kind regards,
Alicja Kwaśniewska

From: Vikram Hosakote (vhosakot) [mailto:vhosa...@cisco.com]
Sent: Tuesday, April 26, 2016 9:44 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

+1 for the attic.

Regards,
Vikram Hosakote
IRC: vhosakot

From: Ryan Hallisey >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Monday, April 25, 2016 at 5:00 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

+1

- Original Message -
From: "Angus Salkeld" >
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Sent: Sunday, April 24, 2016 11:01:38 AM
Subject: Re: [openstack-dev] [kolla][vote] Place kolla-mesos in
openstack-attic



+1
On Sat, 23 Apr 2016 3:08 am Michał Rostecki < 
michal.roste...@gmail.com > wrote:


+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

__
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] Nit-picking documentation changes

[Kwasniewska, Alicja]

+1 to approach suggested by sdake.

Furthermore, I think it would be good if -1/0/+1 only reflects logical meaning 
of reviewed docs while still providing some suggestions on improving spelling 
and grammar in comment even if we +1 given patch.

Alicja

From: Martin André [mailto:martin.an...@gmail.com]
Sent: Wednesday, April 13, 2016 12:03 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [kolla][vote] Nit-picking documentation changes


On Tue, Apr 12, 2016 at 10:05 PM, Steve Gordon 
> wrote:
- Original Message -
> From: "Jeff Peeler" >
> To: "OpenStack Development Mailing List (not for usage questions)" 
> >
>
> On Mon, Apr 11, 2016 at 3:37 AM, Steven Dake (stdake) 
> >
> wrote:
> > Hey folks,
> >
> > The reviewers in Kolla tend to nit-pick the quickstart guide to death
> > during
> > reviews.  I'd like to keep that high bar in place for the QSG, because it
> > is
> > our most important piece of documentation at present.  However, when new
> > contributors see the nitpicking going on in reviews, I think they may get
> > discouraged about writing documentation for other parts of Kolla.
> >
> > I'd prefer if the core reviewers held a lower bar for docs not related to
> > the philosophy or quiickstart guide document.  We can always iterate on
> > these new documents (like the operator guide) to improve them and raise the
> > bar on their quality over time, as we have done with the quickstart guide.
> > That way contributors don't feel nitpicked to death and avoid improving the
> > documentation.
> >
> > If you are a core reveiwer and agree with this approach please +1, if not
> > please –1.
>
> I'm fine with relaxing the reviews on documentation. However, there's
> a difference between having a missed comma versus the whole patch
> being littered with misspellings. In general in the former scenario I
> try to comment and leave the code review set at 0, hoping the
> contributor fixes it. The danger is that a 0 vote people sometimes
> miss, but it doesn't block progress.
My typical experience with (very) occasional drive by commits to operational 
project docs (albeit not Kolla) is that the type of nit that comes up is more 
typically -1 thanks for adding X, can you also add Y and Z. Before you know it 
a simple drive by commit to flesh out one area has become an expectation to 
write an entire chapter.

That's because you're a native speaker and you write proper English to begin 
with :)

We should be asking ourselves this simple question when reviewing documentation 
patch "does it make the documentation better?". Often the answer is yes, that's 
why I'm trying to ask for additional improvements in follow-up patches.
Regarding spelling or a grammatical mistakes, why not fix it now while it's 
still hot when we spot one in the new documentation that's being written? It's 
more time consuming to fix it later. If needed a native speaker can take over 
the patch and correct English.
Martin

-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] Nominating Vikram Hosakot for Core Reviewer

[Kwasniewska, Alicja]

+1


-Original Message-
From: Michal Rostecki [mailto:michal.roste...@gmail.com] 
Sent: Wednesday, March 30, 2016 7:18 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core 
Reviewer

+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][vote] Just make Mitaka deploy Liberty within the Liberty branch

[Kwasniewska, Alicja]

+1


-Original Message-
From: Paul Bourke [mailto:paul.bou...@oracle.com] 
Sent: Wednesday, March 30, 2016 11:00 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty 
within the Liberty branch

+1

On 30/03/16 04:27, Steven Dake (stdake) wrote:
> Dear cores,
>
> inc0 has been investigating our backport options for 1.1.0 and they 
> look bleak.  At this time we would have to backport heka because of 
> changes in Docker 1.10.z which are incompatible with the syslog dev 
> file.  We had originally spoken about just taking Mitaka and placing 
> it in Liberty, validating the defaults directory of Ansible, fixing 
> the repo pointers, fixing the source pointers, and modifying 
> containers as necessary to make that happen.
>
> I know this is vastly different then what we have discussed in the 
> past related to Liberty management, but beyond giving up entirely on 
> Liberty which is unacceptable to me, it seems like our only option.
>
> The good news is we will be able to leverage all of the testing we 
> have done with liberty and all of the testing we have done developing 
> Mitaka, and have a smooth stable backport experience for Mitaka and Liberty.
>
> Consider this proposal a +1 vote for me.  Our core team has 11 
> members, which means we need 6 +1 votes in order for this new plan to 
> pass.  Note I see no other options, so abstaining or voting -1 is in 
> essence recommending abandonment of the Liberty branch.
>
> I'll leave voting open for 7 days until Tuesday April 5th unless there 
> is a majority before then.  If  there is a majority prior to the 
> voting deadline, I'll close voting early but leave discussion open for 
> those that wish to have it.
>
> We won't be having this happen again, as our Mitaka architecture is 
> stable and strong minus a few straggling bugs remaining.
>
> 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

Re: [openstack-dev] Nominating Vikram Hosakot for Core Reviewer

[Kwasniewska, Alicja]

+1

-Original Message-
From: Ryan Hallisey [mailto:rhall...@redhat.com] 
Sent: Tuesday, March 29, 2016 6:40 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core 
Reviewer

+1

- Original Message -
From: "Paul Bourke" 
To: openstack-dev@lists.openstack.org
Sent: Tuesday, March 29, 2016 12:10:38 PM
Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core 
Reviewer

+1

On 29/03/16 17:07, Steven Dake (stdake) wrote:
> Hey folks,
>
> Consider this proposal a +1 in favor of Vikram joining the core 
> reviewer team.  His reviews are outstanding.  If he doesn’t have 
> anything useful to add to a review, he doesn't pile on the review with 
> more –1s which are slightly disheartening to people.  Vikram has 
> started a trend amongst the core reviewers of actually diagnosing gate 
> failures in peoples patches as opposed to saying gate failed please 
> fix.  He does this diagnosis in nearly every review I see, and if he 
> is stumped  he says so.  His 30 days review stats place him in pole 
> position and his 90 day review stats place him in second position.  Of 
> critical notice is that Vikram is ever-present on IRC which in my 
> professional experience is the #1 indicator of how well a core reviewer will 
> perform long term.
>Besides IRC and review requirements, we also have code requirements 
> for core reviewers.  Vikram has implemented only 10 patches so far, 
> butI feel he could amp this up if he had feature work to do.  At the 
> moment we are in a holding pattern on master development because we 
> need to fix Mitaka bugs.  That said Vikram is actively working on 
> diagnosing root causes of people's bugs in the IRC channel pretty much 
> 12-18 hours a day so we can ship Mitaka in a working bug-free state.
>
> Our core team consists of 11 people.  Vikram requires at minimum 6 +1 
> votes, with no veto –2 votes within a 7 day voting window to end on 
> April 7th.  If there is a veto vote prior to April 7th I will close 
> voting.  If there is a unanimous vote prior to April 7th, I will make 
> appropriate changes in gerrit.
>
> Regards
> -steve
>
> [1] http://stackalytics.com/report/contribution/kolla-group/30
> [2] http://stackalytics.com/report/contribution/kolla-group/90
>
>
> __
>  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][vote] Proposing Alicja Kwasniewska for core reviewer

[Kwasniewska, Alicja]

Thank you!

I really appreciate being a part of Kolla project and now also core reviewers 
team! It is a pleasure to work with you guys. Thank you all for your support 
and help (especially for all -1 ;) ), wouldn't be here without you!

Kind regards,
Alicja

PS best present for Women's Day ever! :)

From: Steven Dake (stdake) [mailto:std...@cisco.com]
Sent: Tuesday, March 8, 2016 7:15 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for 
core reviewer

The vote is unanimous.

Welcome to the core reviewer team Alicja!  Ping me when you get online next and 
our timezone overlaps, and I'll walk you through the differences in the gerrit 
interface you should know.

I have made appropriate changes in gerrit.

Regards
-steve

From: Steven Dake >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Friday, March 4, 2016 at 9:55 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for core 
reviewer

Core Reviewers,

Alicja has been instrumental in our work around jinja2 docker file creation, 
removing our symlink madness.  She has also been instrumental in actually 
getting Diagnostics implemented in a sanitary fashion.  She has also done a 
bunch of other work that folks in the community already know about that I won't 
repeat here.

I had always hoped she would start reviewing so we could invite her to the core 
review team, and over the last several months she has reviewed quite a bit!  
Her 90 day stats[1] place her at #9 with a solid ratio of 72%.  Her 30 day 
stats[2] are even better and place her at #6 with an improving ratio of 67%.  
She also just doesn't rubber stamp reviews or jump in reviews at the end; she 
sticks with them from beginning to end and finds real problems, not trivial 
things.  Finally Alicja is full time on Kolla as funded by her employer so she 
will be around for the long haul and always available.

Please consider my proposal to be a +1 vote.

To be approved for the core reviewer team, Alicja requires a majority vote of 6 
total votes with no veto within the one week period beginning now and ending 
Friday March 11th.  If your on the fence, you can always abstain.  If the vote 
is unanimous before the voting ends, I will make appropriate changes to 
gerrit's acls.  If their is a veto vote, voting will close prior to March 11th.

Regards,
-steve

[1] http://stackalytics.com/report/contribution/kolla-group/90
[2] http://stackalytics.com/report/contribution/kolla-group/30
__
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] Introduction of Heka in Kolla

[Kwasniewska, Alicja]

Eric, Patrick, Simon, Clark thanks for your comments.

I don't know Heka, so that's why I ask a lot of questions. I hope you are fine 
with that:) I am not against Heka, I was just curious how reliable it is  and 
how much experience you have with setting it up in Docker environment in order 
to know both advantages and disadvantages of this solution. 

@Eric, great that you are going to create POC, it will explain a lot and it 
will show us possible problems. 

Kind regards,
Alicja Kwaśniewska


-Original Message-
From: Eric LEMOINE [mailto:elemo...@mirantis.com] 
Sent: Wednesday, January 13, 2016 10:55 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

Hi Alicja


Thank you for your comments.  Answers and comments below.



On Tue, Jan 12, 2016 at 1:19 PM, Kwasniewska, Alicja 
<alicja.kwasniew...@intel.com> wrote:
> Unfortunately I do not have any experience in working or testing Heka, 
> so it’s hard for me to compare its performance vs Logstash 
> performance. However I’ve read that Heka possess a lot advantages over 
> Logstash in this scope.
>
>
> But which version of Logstash did you test? One guy from the Logstash 
> community said that: “The next release of logstash (1.2.0 is in beta) 
> has a 3.5x improvement in event throughput. For numbers: on my 
> workstation at home
> (6 vcpu on virtualbox, host OS windows, 8 GB ram, host cpu is FX-8150) 
> - with logstash 1.1.13, I can process roughly 31,000 events/sec 
> parsing apache logs. With logstash 1.2.0.beta1, I can process 102,000 
> events/sec.”


I've used the latest Docker image:
<https://hub.docker.com/r/library/logstash/>.  It uses Logstash 2.1.1, which is 
the most recent stable version.



> You also said that Heka is a unified data processing, but do we need this?


Heka, as a unified data processing, enables to derive metrics from logs, HTTP 
response times for example.  Alerts can also be triggered on specific log 
patterns.


> Heka seems to address stream processing needs, while Logstash focuses 
> mainly on processing logs. We want to create a central logging 
> service, and Logstash was created especially for it and seems to work 
> well for this application.
>
>
> One thing that is obvious is the fact that the Logstash is better 
> known, more popular and tested. Maybe it has some performance 
> disadvantages, but at least we know what we can expect from it. Also, 
> it has more pre-built plugins and has a lot examples of usage, while 
> Heka doesn’t have many of them yet and is nowhere near the range of 
> plugins and integrations provided by Logstash.


As Simon said Heka already includes quite a lot of plugins.  See the Heka 
documentation [*] for an exhaustive list.  It may indeed be the case that 
Logstash includes even more plugins, but Heka has taken us pretty far already.



> In the case of adding plugins, I’ve read that in order to add Go 
> plugins, the binary has to be recompiled, what is a little bit 
> frustrating (static linking - to wire in new plugins, have to 
> recompile). On the other hand, the Lua plugins do not require it, but 
> the question is whether Lua plugins are sufficient? Or maybe adding Go 
> plugins is not so bad?


See Simon's answer.



> You also said that you didn’t test the Heka with Docker, right?


I did test Heka with Docker.  In my performance tests both Heka and Logstash 
ran in Docker containers.  What I haven't tested yet is the Docker Log Input 
plugin.  We'll do more tests as part of the work on specifications.



> But do you
> have any experience in setting up Heka in Docker container? I saw that 
> with Heka 0.8.0 new Docker features were implemented (included 
> Dockerfiles to generate Heka Docker containers for both development 
> and deployment), but did you test it? If you didn’t, we could not be 
> sure whether there are any issues with it.
>
>
> Moreover you will have to write your own Dockerfile for Heka that 
> inherits from Kolla base image (as we discussed during last meeting, 
> we would like to have our own images), you won’t be able to inherit 
> from ianneub/heka:0.10 as specified in the link that you sent 
> http://www.ianneubert.com/wp/2015/03/03/how-to-use-heka-docker-and-tutum/.



As I said in my first email Heka has no dependencies, so creating a Dockerfile 
for Heka is quite easy.  See 
<https://github.com/elemoine/heka-logstash-comparison/blob/master/Dockerfile>
for the super-simple Dockerfile I've used so far.


> There are also some issues with DockerInput Module which you want to use.
> For example splitters are not available in DockerInput 
> (https://github.com/mozilla-services/heka/issues/1643). I can’t say 
> that it will affect us, but we also don’t know which new issues may 
> arise du