[openstack-dev] [Neutron] Lack of low-hanging-fruit Neutron bugs

[Vikram Hosakote (vhosakot)]

Dear Neutron developers,

I have been playing with OpenStack Neutron since Grizzly but never
committed a bug upstream. I want to fix a neutron bug and do not see
any unassigned low-hanging-fruit starter bug in
https://bugs.launchpad.net/neutron/+bugs?field.tag=low-hanging-fruit.
I was not able to get info about unassigned low-hanging-fruit bugs in
the Neutron meetings webpage
https://wiki.openstack.org/wiki/Network/Meetings either. Clearly, I do
not know where to look. Hence, sending this email :)

I do not know which bug to pick from
https://bugs.launchpad.net/neutron. I need help to pick one please.

I have experience with Neutron, namespaces, OVS bridge, agents (dhcp-
agent [dnsmasq], L3-agent, LBaaS), reading Neutron¹s Python code,
Linux, DevStack, git, gerrit, *.ini config files, REST, etc.

I prefer a Low/Medium importance bug. ŒLow¹ would be best as it will
be my first Neutron bug. I would like to fix a bug in neutron-server/
neutron-agents rather than a bug in Neutron clients (like Neutron CLI,
python-neutron-client).

Can anyone please give me a bug to fix :) I may ask help if needed
once I start fixing it.

Thanks a lot!

Regards,
Vikram Hosakote   |  vhosakot at cisco dot com
Cloud and Virtualization Group
Cisco Systems   |  Boxborough MA (snow is melting!)

__
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] [neutron][tap-as-a-service] weekly meeting

[Vikram Hosakote (vhosakot)]

Hi,

TAAS looks great for traffic monitoring.

Some questions about TAAS.

1) Can TAAS be used for provider networks as well, or just for tenant
networks ?

2) Will there be any performance impact is every neutron port and every
packet is mirrored/duplicated ?

3) How is TAAS better than a non-mirroring approaches like packet-sniffing
(wireshark/tcpdump) and tracking interface counters/metrics ?

4) Is TAAS a legal/lawful way to intercept/duplicate customer traffic in a
production cloud ? Or, TAAS is used just for debugging/troubleshooting ?

I was not able to find answers for these questions in
https://etherpad.openstack.org/p/mitaka-neutron-unplugged-track.

Thanks!


Regards,
Vikram Hosakote
vhosa...@cisco.com
Software Engineer
Cloud and Virtualization Group (CVG)
Cisco Systems
Boxborough MA USA

From: Takashi Yamamoto >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Tuesday, November 10, 2015 at 10:08 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [neutron][tap-as-a-service] weekly meeting

hi,

tap-as-a-service meeting will be held weekly, starting today.
http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting
anyone interested in the project is welcome.
sorry for immediate notice.

__
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] OSIC cluster accepteed

[Vikram Hosakote (vhosakot)]

I'd like to help with kolla scaling on the OSIC cluster too.

Regards,
Vikram Hosakote
IRC: vhosakot

From: Jeffrey Zhang >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Wednesday, June 8, 2016 at 9:42 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: Re: [openstack-dev] [kolla] OSIC cluster accepteed

Cool.
Do we have any test list now?
and how can i help for this? I am very interested in this
test.

On Tue, Jun 7, 2016 at 4:52 PM, Paul Bourke 
> wrote:
Michal,

I'd be interested in helping with this. Keep us updated!

-Paul


On 03/06/16 17:58, Michał Jastrzębski wrote:
Hello Kollagues,

Some of you might know that I submitted request for 130 nodes out of
osic cluster for testing Kolla. We just got accepted. Time window will
be 3 weeks between 7/22 and 8/14, so we need to make most of it. I'd
like some volunteers to help me with tests, setup and such. We need to
prepare test scenerios, streamline bare metal deployment and prepare
architectures we want to run through. I would also make use of our
global distribution to keep nodes being utilized 24h.

Nodes we're talking about are pretty powerful 256gigs of ram each, 12
ssd disks in each and 10Gig networking all the way. We will get IPMI
access to it so bare metal provisioning will have to be there too
(good time to test out bifrost right?:))

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



--
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] stepping down from core

[Vikram Hosakote (vhosakot)]

Thanks for all the contributions to kolla and good luck Jeff!

Regards,
Vikram Hosakote
IRC: vhosakot

From: "Steven Dake (stdake)" >
Reply-To: OpenStack Development Mailing List 
>
Date: Monday, June 6, 2016 at 6:14 PM
To: OpenStack Development Mailing List 
>
Subject: Re: [openstack-dev] [kolla] stepping down from core

Jeff,

Thanks for the notification.  Likewise it has been a pleasure working with
you over the last 3 years on Kolla.  I've removed you from gerrit.

You have made a big impact on Kolla.  For folks that don't know, at one
point Kolla was nearly dead, and Jeff was one of our team of 3 that stuck
to it.  Without Jeff to carry the work forward, OpenStack deployment in
containers would have been set back years.

Best wishes on what you work on next.

Regards
-steve

On 6/6/16, 12:36 PM, "Jeff Peeler" 
> wrote:

Hi all,

This is my official announcement to leave core on Kolla /
Kolla-Kubernetes. I've enjoyed working with all of you and hopefully
we'll cross paths again!

Jeff

__
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] Request for changing the meeting time to 1600 UTC for all meetings

[Vikram Hosakote (vhosakot)]

+1

Regards,
Vikram Hosakote
IRC: vhosakot

From: "Swapnil Kulkarni (coolsvap)" 
>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Wednesday, June 8, 2016 at 8:54 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla] Request for changing the meeting time to 1600 
UTC for all meetings

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.

--
Best Regards,
Swapnil Kulkarni
irc : coolsvap

__
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] Flame creates incorrect HEAT template for provider network

[Vikram Hosakote (vhosakot)]

Hi OpenStack Flame developers,

I see that the HEAT template generated by OpenStack Flame for a provider
network is incorrect and has missing fields.

For the provider network Provider_153, Flame creates the HEAT template

  network_0:
properties:
  admin_state_up: true
  name: Provider_153
  shared: true
type: OS::Neutron::Net


instead of


  network_0:
properties:
  admin_state_up: true
  name: Provider_153
  shared: true
  provider:physical_network: physnet2  <- Missing
  provider:network_type: vlan  <- Missing
  provider:segmentation_id: 153<- Missing
type: OS::Neutron::Net


If I propose a fix for this bug, will I get an ATC code for the OpenStack 
summit in
Austin ?  Also, I am not able to find the OpenStack Flame project in Launchpad
https://launchpad.net/openstack. Where do I file this bug ?

I cloned Flame from https://github.com/openstack/flame.

FYI, the neutron CLI used to create the provider network is

neutron net-create --provider:physical_network=physnet2 
--provider:network_type=vlan --provider:segmentation_id=153 --shared 
Provider_153


Regards,
Vikram Hosakote
OpenStack Software Developer
Cisco Systems
vhosa...@cisco.com
Boxborough MA
__
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] [infra] Size of images built in the gate

[Vikram Hosakote (vhosakot)]

/var/lib/docker/aufs  takes a lot of space if many containers are running and
writing data to their volumes.

If the gate VM's  /var/lib/docker  partition is small, you could move
/var/lib/docker  to a different partition that is big enough (like /home or 
/tmp)
and create a symbolic link to  /var/lib/docker.

mv  /var/lib/docker  /home/new_docker_path_with_more_space
ln -s  /home/new_docker_path_with_more_space  /var/lib/docker

Alternatively, you can use the -g option for the docker daemon to use a 
different
path instead of  /var/lib/docker  if it runs out of disk space.

DOCKER_OPTS="-g /home/new_docker_path_with_more_space"

Restart the docker daemon after making the above change.

https://github.com/docker/docker/issues/3127

Regards,
Vikram Hosakote
IRC: vhosakot

From: Paul Bourke >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Monday, March 14, 2016 at 11:25 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla] [infra] Size of images built in the gate

Hi all,

I'm currently working to add new gates for the oraclelinux image base
type (https://blueprints.launchpad.net/kolla/+spec/oraclelinux-gate) and
had a question on size available in the gate VMs.

Right now the binary build is running out of space in the gate, as it
exceeds the 10GB we're allocating for /var/lib/docker. For me, a current
local build using binary+oraclelinux is clocking in at 10.01GB, where as
the centos+binary is a little smaller at 8.89GB.

Is it written anywhere exactly what space is available in the gate VMs?
Sam mentioned briefly that different providers used in the gate give a
variety of disk sizes, so do we have an idea what we can reasonably bump
the docker partition to?

The above number indicates centos will likely soon run into the same
problem as we dockerise more of the big tent, so I think it's a good
idea to check this now before more gates start falling over.

Thanks,
-Paul

p.s. if people are interested here's lists sorted by name of the
oraclelinux and centos builds:

oraclelinux: http://paste.fedoraproject.org/339672/96915914
centos: http://paste.fedoraproject.org/339673/57969163

__
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] ubuntu deploy gate

[Vikram Hosakote (vhosakot)]

FYI, the bug is seen in Ubuntu gate just on  devstack-trusty-rax  machine and
not on  devstack-trusty-osic  and  devstack-trusty-ovh.

Regards,
Vikram Hosakote
IRC: vhosakot

From: "Steven Dake (stdake)" >
Reply-To: 
"openstack-dev@lists.openstack.org" 
>
Date: Wednesday, March 9, 2016 at 9:50 AM
To: 
"openstack-dev@lists.openstack.org" 
>
Subject: [openstack-dev] [kolla] ubuntu deploy gate

The ubuntu deploy gate is failing because of commit 
7f6de0a7e0d784181a6f99270768712e761f113a.

Please see review https://review.openstack.org/#/c/290243/ for more details.

For the moment ignore the ubuntu deploy gate until the appropriate fix is 
merged.

TIA
-steve
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Vikram Hosakote (vhosakot)]

I value the friendliness and approachability that contributors seek.

I am totally fine with minor mistakes in documentation.

As they make more changes, they will understand/follow the process.

+1


Regards,
Vikram Hosakote
IRC: vhosakot

From: "Steven Dake (stdake)" >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Monday, April 11, 2016 at 3:37 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla][vote] Nit-picking documentation changes

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.

This is an unofficial vote and carries no commitment from the core reviewers, 
but I've included vote in the subject just to catch people's attention and to 
get folks thoughts on this matter.

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

Re: [openstack-dev] [Kolla] DocImpact in reviews

[Vikram Hosakote (vhosakot)]

Good point.  I think this should be caught during code review.

Regards,
Vikram Hosakote
IRC: vhosakot

From: Swapnil Kulkarni >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Monday, March 7, 2016 at 1:40 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [Kolla] DocImpact in reviews

Hello,

I was triaging some of the bugs reported to Kolla and I found a couple
of bugs [1] [2] created due to incorrect usage of DocImpact[1] tag in
reviews. The DocImapct tag should only be used in case if you have
done some change which requires following two,

1) Update in some existing documentation
2) Add some new documentation

which are not addressed in the current changeset where you are adding
the DocImapct.


[1] https://wiki.openstack.org/wiki/Documentation/DocImpact
[2] https://bugs.launchpad.net/kolla/+bug/1553291
[3] https://bugs.launchpad.net/kolla/+bug/1553405

Best Regards,
Swapnil Kulkarni
irc : coolsvap

__
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

[Vikram Hosakote (vhosakot)]

Thanks a lot for the opportunity Steve, the kolla core team, and the kolla 
community! :)

Regards,
Vikram Hosakote
IRC: vhosakot

From: "Steven Dake (stdake)" >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Monday, April 4, 2016 at 4:31 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core 
Reviewer

The vote is unanimous in favor of Vikram joining the core reviewer team.  I 
have made the appropriate permission changes in gerrit.

Welcome to the core reviewer team Vikram!

Regards
-steve

From: Steven Dake >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Tuesday, March 29, 2016 at 9:07 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core 
Reviewer

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

Re: [openstack-dev] [neutron] Social at the summit

[Vikram Hosakote (vhosakot)]

Well, neutron is needed by most OpenStack projects :)

If it is open to non-neutron cores and non-neutron devs, I'd like to attend and
know what is happening is neutron in Newton.

And, yes, Bangers on Rainey St has great IPA ;)

Regards,
Vikram Hosakote
IRC: vhosakot

From: Darek Smigiel 
>
Reply-To: 
"openstack-dev@lists.openstack.org" 
>
Date: Wednesday, April 27, 2016 at 12:41 AM
To: 
"openstack-dev@lists.openstack.org" 
>
Subject: Re: [openstack-dev] [neutron] Social at the summit

Great idea Kyle,
This place looked awesome.

FYI, I've sent request for reservation. Just in case if Thursday would be 
crowded, especially that a lot of teams could have the same idea.

Thanks,
Darek

On Apr 26, 2016, at 8:27 PM, Kyle Mestery 
> wrote:
I propose we meet at Bangers on Rainey St. at 6PM. I don't have a reservation 
but it should be able to hold 50+ people. See y'all at 6PM Thursday!
Kyle
On Apr 25, 2016, at 1:07 PM, Kyle Mestery 
> wrote:
OK, there is enough interest, I'll find a place on 6th Street for us
and get a reservation for Thursday around 7 or so.
Thanks folks!
On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han 
> wrote:
+1 :)
Han Zhou
Irc: zhouhan
On Monday, April 25, 2016, Korzeniewski, Artur
> wrote:
Sign me up :)
Artur
IRC: korzen
-Original Message-
From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
Sent: Monday, April 25, 2016 7:19 PM
To: OpenStack Development Mailing List (not for usage questions)
>
Subject: Re: [openstack-dev] [neutron] Social at the summit
Count me in!
Will be good to meet all you guys!
Darek (dasm) Smigiel
On Apr 25, 2016, at 12:13 PM, Doug Wiegley
> wrote:
On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
>
wrote:
WAT???
It was never supposed to be core only. Everyone is welcome!
+2
irony intended.
Socials are not controlled by gerrit ACLs.  :-)
doug
Sent from my iPhone
On 25 Apr 2016, at 11:56, Edgar Magana 
>
wrote:
Would you extend it to ex-cores?
Edgar
On 4/25/16, 10:55 AM, "Kyle Mestery" 
> wrote:
Ihar, Henry and I were talking and we thought Thursday night makes
sense for a Neutron social in Austin. If others agree, reply on this thread
and we'll find a place.
Thanks!
Kyle
___
___ 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
__
OpenStack 

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

[Vikram Hosakote (vhosakot)]

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)" >
Reply-To: 
"openstack-dev@lists.openstack.org" 
>
Date: Tuesday, May 17, 2016 at 3:00 PM
To: 
"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

Re: [openstack-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes repository management proposal up for vote

[Vikram Hosakote (vhosakot)]

Please add me too to the list!

Regards,
Vikram Hosakote
IRC: vhosakot

From: Michał Jastrzębski <inc...@gmail.com<mailto:inc...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Saturday, April 30, 2016 at 9:58 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
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) 
<std...@cisco.com<mailto:std...@cisco.com>> 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 brid

Re: [openstack-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes repository management proposal up for vote

[Vikram Hosakote (vhosakot)]

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.

Regards,
Vikram Hosakote
IRC: vhosakot

From: Vikram Hosakote <vhosa...@cisco.com<mailto:vhosa...@cisco.com>>
Date: Sunday, May 1, 2016 at 11:36 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
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 <inc...@gmail.com<mailto:inc...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Saturday, April 30, 2016 at 9:58 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
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) 
<std...@cisco.com<mailto:std...@cisco.com>> 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

Re: [openstack-dev] [kolla][infra] Gate bused until Sunday April 17th

[Vikram Hosakote (vhosakot)]

Here is the infra patch set that should fix the shade-nodepool issue.

https://review.openstack.org/#/c/306835/

Thanks for the fix Monty!


Regards,
Vikram Hosakote
IRC: vhosakot

From: "Steven Dake (stdake)" >
Reply-To: 
"openstack-dev@lists.openstack.org" 
>
Date: Saturday, April 16, 2016 at 11:38 PM
To: 
"openstack-dev@lists.openstack.org" 
>
Subject: [openstack-dev] [kolla][infra] Gate bused until Sunday April 17th

Core Reviewers and developers,

Hey folks.  A shade + nodepool change has broken our gating functionality on 
the OVH cloud provider and probably some others.  The net result is we can't 
actually gate our changes.

I'd recommend for the moment to provide +1 reviews and revisit the review queue 
Sunday or Monday after the fix has been deployed.  OpenStack infra is aware of 
the problem and taking care of it.  Please do not workflow any patches until 
the infrastructure we depend on is fixed.   You will know this has happened 
because a recheck will return a functional gate.  I will also send a followup 
announcement that the gate is operational again.  The one liner problem has 
already been identified and a fix is in the works.

If your still interested in working on Kolla during this outage of the gate 
feel free to fix Kolla defects and get them in the queue.  Another helpful 
thing is testing Kolla stable/mitaka.

The estimated fix date is Sunday, April 17th.

Our release deadline for 2.0.0 is April 21st.

Logs of discussion on irc here:
http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2016-04-17.log.html#t2016-04-17T01:53:28

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

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

[Vikram Hosakote (vhosakot)]

+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] Applying for stable-follows tag

[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
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] our mascot - input needed

[Vikram Hosakote (vhosakot)]

Sorry, I missed the kolla mid-cycle summit as I was at a conference.

I will review the mid-cycle etherpad.

Yes for the koala bear!!  :)

Regards,
Vikram Hosakote
IRC:  vhosakot

From: "Steven Dake (stdake)" >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Thursday, July 14, 2016 at 1:08 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla] our mascot - input needed

Hey folks,

The OpenStack foundation is putting together mascots for every project with a 
proper artist doing the work.  The cool thing about this is we a) get stickers 
b) have consistent look and feel among mascots in OpenStack.

The downside is we have to make a decision.  The foundation wants 3-5 choices.

The mascot must be an animal and it can't involve glue or other inc007 inspired 
ideas :)

Obviously Koala bear is probably everyone's first choice since we have sort of 
been using that as a mascot since day one.  Anyone else have anything else for 
me to provide the foundation with a choices 2-5?

Please respond quickly, the foundation needs the information shortly.  I'd like 
to offer up two alternatives just in case.

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

Re: [openstack-dev] [kolla] Contributors welcome to kolla-kubernetes 0.5.0

[Vikram Hosakote (vhosakot)]

Yes, I'd like to contribute to the blueprints and will ask questions in the 
kolla
IRC channel.

Regards,
Vikram Hosakote
IRC:  vhosakot

From: "Steven Dake (stdake)" >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Wednesday, January 18, 2017 at 12:07 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla] Contributors welcome to kolla-kubernetes 0.5.0

Hey folks,

The release team released kolla-kubernetes 0.4.0 Sunday January 15th.  Now we 
are in 0.5.0 development which lasts one month.

The general architecture of OpenStack based deployments with a Kubernetes 
underlay is taking form.  There are 5 blueprints in 0.5.0 which we expect 
should land prior to the PTG:
https://launchpad.net/kolla-kubernetes/+milestone/0.5.0

If you have personal interest in any of these blueprints, the fact that they 
are "assigned" doesn't mean there isn't a contribution to be made.  If you 
click through to an individual blueprint, you can see the "Work Items" field 
which contains each work item that needs addressing in each of these master 
blueprints.  For each master blueprint, there may be 10+ work items or more.

The goal of these "master" blueprints is to distribute the work among the 
development community.  There should be enough to work from in the whiteboard 
patches to produce an implementation.

Feel free to change "unassigned" to your Launchpad id for any of the blueprint 
work items.  The person assigned is responsible for tracking the state of the 
blueprint's work items or generally leading the effort around those blueprints 
as has been done in other Kolla deliverables.

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

Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

[Vikram Hosakote (vhosakot)]

Great, thanks a lot for setting this up Steve!

Regards,
Vikram Hosakote
IRC: vhosakot

From: "Steven Dake (stdake)" >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Saturday, February 18, 2017 at 8:16 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

Hey folks,

To take some load off Michal I've setup remote participation for day #1 of the 
PTG.

Michal had suggested he might setup zoom instead of webex, however, I haven't 
seen that happen and several people have asked on IRC how remote participation 
will work at the PTG.  If Michal sets up remote participation in some othe 
rway, ignore this email (and he will follow up with a zoom.us calendar invite).

Note I feel like google hangouts is difficult to manage and is a non-starter 
because google Is not available to our worldwide participants.

See below for details:



From: Steven Dake >
Reply-To: "Steven Dake (stdake)" >
Date: Saturday, February 18, 2017 at 12:02 AM
To: "Steven Dake (stdake)" >
Subject: (Forward to others) WebEx meeting invitation: Kolla PTG Day #1

You can forward this invitation to others.


Hello,

Steven Dake invites you to join this WebEx meeting.





Kolla PTG Day #1

Monday, February 20, 2017

9:00 am  |  Eastern Standard Time (New York, GMT-05:00)  |  6 hrs





Join WebEx 
meeting


Meeting number:

204 403 514

Meeting password:

OpenStackKolla (67367822 from phones)


Join from a video conferencing system or application

Dial 204403...@cisco.webex.com<%20sip:204403...@cisco.webex.com>

>From the Cisco internal network, dial *267* and the 9-digit meeting number. If 
>you are the host, enter your PIN when prompted.





Join by phone

+1-866-432-9903 Call-in toll-free number (US/Canada)

+1-408-525-6800 Call-in toll number (US/Canada)

Access code: 204 403 514

Global call-in 
numbers
  |  Toll-free calling 
restrictions





Add this 
meeting
 to your calendar. (Cannot add from mobile devices.)





Can't join the meeting? Contact support.





IMPORTANT NOTICE: Please note that this WebEx service allows audio and other 
information sent during the session to be recorded, which may be discoverable 
in a legal matter. By joining this session, you automatically consent to such 
recordings. If you do not consent to being recorded, discuss your concerns with 
the host or do not join the session.




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

[Vikram Hosakote (vhosakot)]

+1.

Great work Eduardo contributing to the third party plugin support kolla
blueprint!

Regards,
Vikram Hosakote
IRC:  vhosakot

From: "Steven Dake (stdake)" >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Thursday, August 18, 2016 at 7:09 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
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

Re: [openstack-dev] [kolla] important instructions or Newton Milestone #3 Release today 8/31/2015 @ ~23:30 UTC

[Vikram Hosakote (vhosakot)]

Great work kolla and kolla-kubernetes communities!

Big thanks to the openstyack-infra team as well :)

Regards,
Vikram Hosakote
IRC:  vhosakot

From: "Steven Dake (stdake)" >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Wednesday, August 31, 2016 at 6:37 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla] important instructions or Newton Milestone #3 
Release today 8/31/2015 @ ~23:30 UTC

Hey folks,

Milestone 3 will be submitted for tagging to the release team today around my 
end of work day.  All milestone 3 blueprints and bugs will be moved to rc1 in 
the case they don't make the August 31st(today) deadline.

We require fernet in rc1, so if there is anything that can be done to 
accelerate Shuan's work there, please chip in.  I'd like this to be our highest 
priority blueprint merge.  The earlier it merges (when functional) the more 
time we have to test the changes.  Please iterate on this review and review 
daily until merged.

We have made tremendous progress in milestone 3.  We ended up carrying over 
some blueprints as FFEs to rc1 which are all in review state right now and 
nearly complete.

The extension for  features concludes September 15th, 2016 when rc1 is tagged.  
If features don't merge by that time, they will be retargeted for Ocata.  When 
we submit the rc1 tag, master will branch.  After rc1, we will require bug 
backports from master to newton (and mitaka and liberty if appropriate).

We have a large bug backlog.  If folks could tackle that, it would be 
appreciated.  I will be spending most of my time doing that sort of work and 
would appreciate everyone on the team to contribute.  Tomorrow afternoon I will 
have all the rc1 bugs prioritized as seems fitting.

Please do not workflow+1 any blueprint work in the kolla repo until rc1 has 
been tagged.  Master of kolla is frozen for new features not already listed in 
the rc1 milestone.  Master of kolla-kubernetes is open for new features as we 
have not made a stable deliverable out of this repository (a 1.0.0 release).  
As a result, no branch will be made of the kolla-kubernetes repository (I 
think..).  If a branch is made, I'll request it be deleted.

If you have a bug that needs fixing and it doesn't need a backport, just use 
TrivialFix to speed up the process.  If it needs a backport, please use a bug 
id.  After rc1, all patches will need backports so everything should have a bug 
id.  I will provide further guidance after rc1.

A big shout out goes to our tremendous community that has pulled off 3 
milestones on schedule and in functional working order for the Kolla repository 
while maintaining 2 branches and releasing 4 z streams on a 45 day schedule.  
Fantastic work everyone!

Kolla-kubernetes also deserves a shout out - we have a functional compute-kit 
kubernetes underlay that deploys Kolla containers using mostly native 
kuberenetes functionality  We are headed towards a fully Kubernetes 
implementation.  The deployment lacks the broad feature-set of kolla-ansible 
but uses the json API to our containers and is able to spin up nova virtual 
machines with full network (OVS) connectivity - which is huge!

Cheers!
-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-dev] OSIC cluster ready with CentOS

[Vikram Hosakote (vhosakot)]

Hi Kollagues,

Scenario # 11 (fio_many_osd) ended successfully.  Daviey and I installed
CentOS on all the 130 target nodes in the OSIC cluster today.  We also:

1.  Deleted all the Ubuntu images and volumes on the deploy node
(729494-comp-s3500-002).
2.  Cleaned up /var/lib/docker on the deploy node.
3.  Started building kolla CentOS source images.
4.  Updated the cobbler profile and cobbler kickstart for CentOS.

The same kolla-ansible inventory file used for Ubuntu testing can be
used for CentOS as well.  Once the images are built, we can run tests on
CentOS before handing the OSIC cluster back tomorrow.

Regards,
Vikram Hosakote
IRC:  vhosakot
__
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][osic] OSIC cluster ready with CentOS

[Vikram Hosakote (vhosakot)]

Hi Kollagues,

Scenario # 11 (fio_many_osd) ended successfully.  Daviey and I installed
CentOS on all the 130 target nodes in the OSIC cluster today.  We also:

1.  Deleted all the Ubuntu images and volumes on the deploy node
(729494-comp-s3500-002).
2.  Cleaned up /var/lib/docker on the deploy node.
3.  Started building kolla CentOS source images.
4.  Updated the cobbler profile and cobbler kickstart for CentOS.

The same kolla-ansible inventory file used for Ubuntu testing can be
used for CentOS as well.  Once the images are built, we can run tests on
CentOS before handing the OSIC cluster back tomorrow.

Regards,
Vikram Hosakote
IRC:  vhosakot
__
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)

[Vikram Hosakote (vhosakot)]

+1.

Great work Christian!

Regards,
Vikram Hosakote
IRC:  vhosakot

From: "Steven Dake (stdake)" >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Wednesday, September 7, 2016 at 10:59 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [vote][kolla] Core Nomination for Christian Berendt 
(berendt on irc)

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:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla][ptl] Self non-nomination for Kolla PTL for Ocata cycle

[Vikram Hosakote (vhosakot)]

Thanks a lot Steve for being a great PTL, leader and a mentor!

Regards,
Vikram Hosakote
IRC:  vhosakot

From: "Steven Dake (stdake)" >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Monday, September 12, 2016 at 1:04 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla][ptl] Self non-nomination for Kolla PTL for 
Ocata cycle

To the OpenStack Community,

Consider this email my self non-nomination for PTL of Kolla for
the coming Ocata release.  I let the team know in our IRC team meeting
several months ago I was passing the on baton at the conclusion of Newton,
but I thought the broader OpenStack community would appreciate the information.

I am super proud of what our tiny struggling community produced starting
3 years ago with only 3 people to the strongly emergent system that is Kolla
with over 467 total contributors [1] since inception and closing in on 5,000
commits today.

In my opinion, the Kolla community is well on its way to conquering the last
great challenge OpenStack faces: Making operational deployment management (ODM)
of OpenStack cloud platforms straight-forward, easy, and most importantly
cost effective for the long term management of OpenStack.

The original objective the Kolla community set out to accomplish, deploying
OpenStack in containers at 100 node scale has been achieved as proven by this
review [2].  In these 12 scenarios, we were able to deploy with 3
controllers, 100 compute nodes, and 20 storage nodes using Ceph for all
storage and run rally as well as tempest against the deployment.

Kolla is _No_Longer_a_Toy_ and _has_not_been_ since Liberty 1.1.0.

I have developed a strong leadership pipeline and expect several candidates
to self-nominate.  I wish all of them the best in the future PTL elections.

Finally, I would like to thank all of the folks that have supported Kolla's
objectives.  If I listed the folks individually this email would be far too
long, but you know who you are :) Thank you for placing trust in my judgement.

It has been a pleasure to serve as your leader.

Regards
-steak

[1] http://stackalytics.com/report/contribution/kolla-group/2000
[2] https://review.openstack.org/#/c/352101/

__
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

[Vikram Hosakote (vhosakot)]

Yes, I vote Option C.

Regards,
Vikram Hosakote
IRC:  vhosakot

From: Michał Jastrzębski >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Thursday, September 15, 2016 at 9:57 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: Re: [openstack-dev] [vote][kolla] Splitting out Ansible into a 
separate deliverable

Option C will be best, but I guess we almost have enough votes for it?:)

I vote for C.

On 15 September 2016 at 06:45, Mauricio Lima 
> wrote:
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

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

[Vikram Hosakote (vhosakot)]

I vote for option 2.

Regards,
Vikram Hosakote
IRC:  vhosakot

From: Ryan Hallisey >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Monday, September 19, 2016 at 2:58 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: Re: [openstack-dev] [vote][kolla] deprecation for fedora distro support

option 2

Thanks
-Ryan

- Original Message -
From: "Mauricio Lima" >
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Sent: Monday, September 19, 2016 2:21:51 PM
Subject: Re: [openstack-dev] [vote][kolla] deprecation for fedora distro support

Option 2

2016-09-19 14:56 GMT-03:00 Christian Berendt < 
bere...@betacloud-solutions.de > :


Thanks for moving this forward.

On 19 Sep 2016, at 19:40, Jeffrey Zhang < 
zhang.lei@gmail.com > 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

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

[Vikram Hosakote (vhosakot)]

+1.

Great work Dave!

Regards,
Vikram Hosakote
IRC:  vhosakot

From: "Steven Dake (stdake)" >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Tuesday, August 23, 2016 at 4:45 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla][vote] Core nomination for Dave Walker (Daviey 
on irc)

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

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

[Vikram Hosakote (vhosakot)]

Yes, I'm +1 for this.

I've seen TrivialFix used for a lot of non-trivial fixes.

May be, we need a spec to define what is trivial?  ;)

Regards,
Vikram Hosakote
IRC:  vhosakot

From: Paul Bourke >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Thursday, November 3, 2016 at 6:51 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

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

[openstack-dev] Search in OpenStack IRC logs

[Vikram Hosakote (vhosakot)]

At the kolla design summit yesterday in Barcelona, someone said there is no
tool to search words in the logs of an OpenStack IRC channel.

https://wiki.openstack.org/wiki/IRC

The OpenStack IRC logs have invaluable information and solutions to many
problems.

Attached is a little script I wrote to search regular expressions in the
#openstack-kolla IRC channel.  It can be updated to search words in any
OpenStack IRC channel.

For example, if you need help about the error "DockerException: Error while
fetching server API version" in the logs of the #openstack-kolla IRC channel,
just do the following.

$ ./search_openstack_irc.py ".*DockerException: Error while fetching server API 
version.*"
Found in  
http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/%23openstack-kolla.2016-09-05.log.html

Below is the snippet in the IRC log.

[cid:FEBA5E60-8D92-47C5-93E9-0F3DA57C2E84]

Hope it helps and let me know if you find any bug in the script!

Regards,
Vikram Hosakote
IRC:  vhosakot
#! /usr/bin/python

##
# 
# Author:  Vikram Hosakote (vhosa...@cisco.com)
#
# This script searches a regular expression in OpenStack Kolla's IRC logs
# in a multi-threaded manner.
#
# The "link" variable in this script can be changed to search any 
# OpenStack project's IRC logs.
#
# For example:  To search OpenStack Neutron IRC logs, set
# link = "http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/;
#
# Usage:   ./search_openstack_irc.py 
#
# Examples:
#
# To search a whole word, escape \b as \\b
#
# $ ./search_openstack_irc.py "\\bvhosakot\\b"
# [u'vhosakot']
# 
# $ ./search_openstack_irc.py "\\bvho\\b"
# 
# $ ./search_openstack_irc.py "vhosakot"
# [u'vhosakot']
# 
# $ ./search_openstack_irc.py "vhosakot.*"
# [u'vhosakot has joined #openstack-kolla15:30']
# 
# $ ./search_openstack_irc.py ".*akot"
# [u'*** vhosakot']
# 
# $ ./search_openstack_irc.py ".*akot.*"
# [u'*** vhosakot has joined #openstack-kolla15:30']
#
##

from bs4 import BeautifulSoup
from multiprocessing import Pool
import re
import sys
import urllib

def print_usage():
print "\
$ ./search_openstack_irc.py \"bvhosakotb\"  \n\
[u'vhosakot']  \n\
  \n\
$ ./search_openstack_irc.py \"bvhob\"  \n\
  \n\
$ ./search_openstack_irc.py \"vhosakot\"  \n\
[u'vhosakot']  \n\
  \n\
$ ./search_openstack_irc.py \"vhosakot.*\"  \n\
[u'vhosakot has joined #openstack-kolla15:30']  \n\
  \n\
$ ./search_openstack_irc.py \".*akot\"  \n\
[u'*** vhosakot']  \n\
  \n\
$ ./search_openstack_irc.py \".*akot.*\"  \n\
[u'*** vhosakot has joined #openstack-kolla15:30']  \n\
"

if len(sys.argv) < 2:
print "\nNothing to search."
print "\nUsage:   ./search_openstack_irc.py \n"
print "Examples:"
print_usage()
sys.exit()

if len(sys.argv) > 2:
print "\nEnter the regular expression to search in quotes."
print "\nUsage:   ./search_openstack_irc.py \n"
print "Examples:"
print_usage()
sys.exit()

regexp_to_search = sys.argv[1]

# The link below can be changed to search any OpenStack project's IRC logs
# For example:  To search OpenStack Neutron IRC logs, set
# link = "http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/;

link = "http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/;
f = urllib.urlopen(link)
irc_page = f.read()

def t_search_in_each_irc_link(irc_link, regexp_to_search):
f = urllib.urlopen(irc_link)
html_page = f.read()
soup = BeautifulSoup(html_page, "lxml")
irc_logs = soup.text
r = re.findall(regexp_to_search, irc_logs, re.IGNORECASE)
if r != []:
print "Found in ", irc_link

pool = Pool(processes=100)

for line in irc_page.splitlines():
if ".html" in line and "href" in line:
link_suffix = re.findall(r'"([^"]*)"', line)[0]
irc_link = link + link_suffix
pool.apply_async(t_search_in_each_irc_link, (irc_link, regexp_to_search))

pool.close()
pool.join()
__
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

[Vikram Hosakote (vhosakot)]

+1

Regards,
Vikram Hosakote
IRC:  vhosakot

From: Mauricio Lima >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Wednesday, November 16, 2016 at 5:33 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

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)" 
>
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] Vote to add zhubingbing to core team

[Vikram Hosakote (vhosakot)]

+1

Regards,
Vikram Hosakote
IRC:  vhosakot

From: Michał Jastrzębski >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Tuesday, November 29, 2016 at 11:21 AM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla] Vote to add zhubingbing to core team

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

[Vikram Hosakote (vhosakot)]

+1  Great job Duong!

Regards,
Vikram Hosakote
IRC:  vhosakot

From: Michał Jastrzębski >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Wednesday, March 08, 2017 at 11:21 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
>
Subject: [openstack-dev] [kolla] Proposing duonghq for core

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

[Vikram Hosakote (vhosakot)]

I like the idea and would love to help with mentoring.

I’ve learned a lot being a Kolla core.

I think every contributor is the same – core or not ☺.  At the end of the 
mentorship, I
think we need to make sure that non-cores feel no different than cores, and 
that every
contributor is the same, welcome, helped and mentored in the community ☺.

I’ll add my name is the signup sheet!

Regards,
Vikram Hosakote
IRC:  vhosakot

From: "Steven Dake (stdake)" 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Thursday, April 13, 2017 at 9:19 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship 
program for Kolla deliverables

Ok sounds fair.  I guess I had misunderstood what nova had done, and thought it 
was a path to success.

I’m happy we can have the conversation about a mentorship program now at least 
in the Kolla project.

I’m not sure how to evaluate the cost of the mentorship program in terms of 
core reviewer time.  Perhaps we should start there.  I know core reviewers are 
swamped for bandwidth, however, I also feel making time for mentorship is 
essential to the project’s long term health.

I am also not sure if we have more individuals interested.  If only Rich is 
interested, that is only one person to mentor.  If 100 people are interested, 
that is beyond our capacity as a team to handle ☺

To help sort out the time commitment for core reviewers, I have started a 
“sign-up sheet” for folks interested in mentoring here:
https://etherpad.openstack.org/p/kolla-mentorship-signup

Regards
-steve


From: "Serguei Bezverkhi (sbezverk)" 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Thursday, April 13, 2017 at 8:45 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship 
program for Kolla deliverables

The idea is great, no doubt here, meaning mentoring and everything, but it 
should not come with price of reducing quality control. 2 x +2 +w should still 
be required from “regular” cores for PS to merge.

Serguei

From: Richard Wellum [mailto:richwel...@gmail.com]
Sent: Thursday, April 13, 2017 7:02 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship 
program for Kolla deliverables

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

Re: [openstack-dev] [kolla-kubernetes] Proposing Rich Wellum to core team

[Vikram Hosakote (vhosakot)]

Rich? Well, um ;)

Although I’m not a kolla-kubernetes core and my vote does not matter at all, 
I’ll still give
my +1 to Rich ☺.

Amazing work in kolla-kubernetes Rich especially your recent contribution of 
the Python
tool to automate the deployment of kolla-kubernetes.

https://review.openstack.org/#/c/487972/

Regards,
Vikram Hosakote
IRC: vhosakot

From: Michał Jastrzębski 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, August 11, 2017 at 12:01 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [kolla-kubernetes] Proposing Rich Wellum to core team

Hello,

It's my pleasure to start another core team vote. This time for our
colleague rwellum. I propose that he joins kolla-kubernetes team.

This is my +1 vote. Every kolla-kubernetes core has a vote and it can
be veto'ed.

Voting will last 2 weeks and will end at 25th of August.

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][kolla-ansible] Proposing Bertrand Lallau for kolla and kolla-ansible core

[Vikram Hosakote (vhosakot)]

+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] [all][deployment][kolla][tripleo][osa] Service diagnostics task force

[Vikram Hosakote (vhosakot)]

Beautiful goal!

I want to do this ☺

Regards,
Vikram Hosakote
IRC:  vhosakot

From: Michał Jastrzębski 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Wednesday, September 13, 2017 at 5:45 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [all][deployment][kolla][tripleo][osa] Service 
diagnostics task force

Hello my dearest of communities,

During deployment tools session on PTG we discussed need for deep
health checking and metering of running services. It's very relevant
in context of containers (especially k8s) and HA. Things like
watchdog, heartbeats or exposing relative metrics (I don't want to get
into design here, suffice to say it's non-trivial problem to solve).

We would like to start a "task force", few volunteers from both
deployment tool side (ops, ha) and project dev teams. We would like to
design together a proper health check mechanism for one of projects to
create best practices and design, that later could be implemented in
all other services.

We would to ask for volunteer project team to join us and spearhead this effort.

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] [cinder] [ironic] [tripleo] PTG cross-platform meetup possibility

[Vikram Hosakote (vhosakot)]

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 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, September 8, 2017 at 4:04 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

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

On Fri, Sep 8, 2017 at 12:49 PM, Richard Wellum 
> 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-dev] FW: [kolla] [neutron] PTG cross-platform meetup possibility

[Vikram Hosakote (vhosakot)]

Meeting room “Vail” has been reserved on Tuesday 2-4 pm for this.

https://ethercalc.openstack.org/Queens-PTG-Discussion-Rooms

Regards,
Vikram Hosakote
IRC:  vhosakot

From: Thomas Morin <thomas.mo...@orange.com>
Date: Thursday, September 7, 2017 at 10:39 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [kolla] [neutron] PTG cross-platform meetup 
possibility

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

__
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

[Vikram Hosakote (vhosakot)]

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 
Reply-To: "jsbry...@electronicjungle.net" , 
"OpenStack Development Mailing List (not for usage questions)" 

Date: Thursday, August 31, 2017 at 1:43 PM
To: "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 
> 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 
> 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-dev] [kolla] [neutron] PTG cross-platform meetup possibility

[Vikram Hosakote (vhosakot)]

Hi neutron team,

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.

Regards,
Vikram Hosakote
IRC:  vhosakot
__
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 team dinner tonight (Sept 13) in Denver downtown

[Vikram Hosakote (vhosakot)]

The Kolla team is planning for dinner tonight Wednesday September 13th
in Denver downtown after today’s PTG session.

This will be a self-paid team dinner.  So, your operating cost depends on
the size of the container you eat in and the ingress policies that control
the number of ReplicaSets for your beer ;)

If you are not contributing to Kolla, Kolla-ansible or Kolla-kubernetes and
would like to join, you are welcome.

Regards,
Vikram Hosakote
IRC:  vhosakot
__
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

[Vikram Hosakote (vhosakot)]

Yes!  Exactly right, Monday is with deployment tool teams and Wednesday
is Kolla+TripleO meet.

Today is Saturday, and tomorrow is Sunday! ☺

Regards,
Vikram Hosakote
IRC:  vhosakot

From: Richard Wellum 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Saturday, September 9, 2017 at 7:52 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

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


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] PTL non candidacy

[Vikram Hosakote (vhosakot)]

Thanks for being a great PTL for kolla Michał ☺

You’re not announcing your non-candidacy for drinking with your
OpenStack friends and this does not mean we can’t drink together ;)

Regards,
Vikram Hosakote
IRC:  vhosakot

From: Michał Jastrzębski 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Wednesday, January 10, 2018 13, 2017 at 10:50 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [kolla] PTL non candidacy

Hello,

A bit earlier than usually, but I'd like to say that I won't be
running for PTL reelection for Rocky cycle. I had privilege of being
PTL of Kolla for last 3 cycles and I would like to thank Kolla
community for this opportunity and trust. I'm very proud of what we've
accomplished over last 3 releases and I'm sure we will accomplish even
greater things in the future!

It's good for project to change leadership every now and then. I would
encourage everyone in community to consider running, I can promise
that this job is ... very interesting;) and extremely rewarding!

Thank you all for support and please, support new PTL as much as you
supported me.

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