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
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
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
ent 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 P
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
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
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
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" ,
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.
+1 Great job Bertrand!
Regards,
Vikram Hosakote
IRC: vhosakot
From: Michał Jastrzębski >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
Date:
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,
+1 Great job Duong!
Regards,
Vikram Hosakote
IRC: vhosakot
From: Michał Jastrzębski >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
Date:
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)"
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)"
+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
+1
Regards,
Vikram Hosakote
IRC: vhosakot
From: Mauricio Lima >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
Date: Wednesday,
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
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
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,
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:
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)"
+1.
Great work Christian!
Regards,
Vikram Hosakote
IRC: vhosakot
From: "Steven Dake (stdake)" >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
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)"
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
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
+1.
Great work Dave!
Regards,
Vikram Hosakote
IRC: vhosakot
From: "Steven Dake (stdake)" >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
Date:
+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)"
+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,
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
+1
Regards,
Vikram Hosakote
IRC: vhosakot
From: "Swapnil Kulkarni (coolsvap)"
>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
Date: Wednesday,
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)"
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
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:
ey 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)
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 Peele
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
+1 for the attic.
Regards,
Vikram Hosakote
IRC: vhosakot
From: Ryan Hallisey >
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
Date: Monday,
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:
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)"
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)"
/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
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:
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)"
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:
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
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
46 matches
Mail list logo