Re: [openstack-dev] [tripleo] Proposing Bob Fournier as core reviewer

+1 Cheers, Brent On Mon, Oct 22, 2018 at 7:06 AM Saravanan KR wrote: > +1 > > Regards, > Saravanan KR > On Fri, Oct 19, 2018 at 5:53 PM Juan Antonio Osorio Robles > wrote: > > > > Hello! > > > > > > I would like to propose Bob Fournier (bfournie) as a core reviewer in > > TripleO. His patches

Re: [openstack-dev] [tripleo] Proposing Marius Cornea core on upgrade bits

+1 !!! On Fri, Apr 20, 2018 at 9:42 AM, Brad P. Crochet wrote: > +1 from me! > > On Fri, Apr 20, 2018 at 8:04 AM Yolanda Robla Mota > wrote: > >> +1, Marius has been a great help >> >> On Thu, Apr 19, 2018 at 7:01 PM, Emilien Macchi >>

[openstack-dev] [tripleo] [neutron] Current containerized neutron agents introduce a significant regression in the dataplane

and stopping/restarting containers effectively breaks the dataplane. At the moment this is being considered a blocker and unless we can find a resolution, we may need to recommend running the L3, DHCP and metadata agents on baremetal. Cheers, Brent Eagles Daniel Alvarez

Re: [openstack-dev] Nominate chem and matbu for tripleo-core !

On Thu, Nov 9, 2017 at 5:14 AM, Marios Andreou wrote: > Hello fellow owls, > > I would like to nominate (and imo these are both long overdue already): > > Sofer Athlan Guyot (chem) and > > Mathieu Bultel (matbu) > > to tripleo-core. They have both made many many core

Re: [openstack-dev] [tripleo] Proposing John Fulton core on TripleO

On Wed, Nov 8, 2017 at 6:54 PM, Giulio Fidente wrote: > Hi, > > I would like to propose John Fulton core on TripleO. > > I think John did an awesome work during the Pike cycle around the > integration of ceph-ansible as a replacement for puppet-ceph, for the > deployment of

Re: [openstack-dev] [tripleo][networking] Organizing the networking squad

articipate in the networking > squad. > > Regards, > Saravanan KR > > On Mon, Oct 16, 2017 at 6:43 PM, Brent Eagles <beag...@redhat.com> wrote: > > Hi, > > > > On Tue, Oct 10, 2017 at 10:55 AM, Brent Eagles <beag...@redhat.com> > wrote: > >

Re: [openstack-dev] [tripleo][networking] Organizing the networking squad

​Hi,​ On Tue, Oct 10, 2017 at 10:55 AM, Brent Eagles <beag...@redhat.com> wrote: > Hi all, > > The list of TripleO squads includes a "networking squad". In previous > cycles, coordinating outside of IRC and email conversations seemed > unnecessary as the

[openstack-dev] [tripleo][networking] Organizing the networking squad

Hi all, The list of TripleO squads includes a "networking squad". In previous cycles, coordinating outside of IRC and email conversations seemed unnecessary as there were only a few contributors and a small number of initiatives. However, with future container related work, increased usage of

Re: [openstack-dev] [tripleo] Proposing Saravanan KR core

On Fri, Jul 21, 2017 at 12:31 PM, Emilien Macchi wrote: > Saravanan KR has shown an high level of expertise in some areas of > TripleO, and also increased his involvement over the last months: > - Major contributor in DPDK integration > - Derived parameter works > - and a lot

Re: [openstack-dev] [tripleo] Proposing Bogdan Dobrelya core on TripleO / Containers

On Fri, Jul 21, 2017 at 12:25 PM, Emilien Macchi wrote: > Hi, > > Bogdan (bogdando on IRC) has been very active in Containerization of > TripleO and his quality of review has increased over time. > I would like to give him core permissions on container work in TripleO. > Any

Re: [openstack-dev] [tripleo] weekly meetings on #tripleo

+1 for giving it a try. On Wed, Jul 5, 2017 at 2:26 PM, Emilien Macchi wrote: > After reading http://lists.openstack.org/pipermail/openstack-dev/2017- > June/118899.html > - we might want to collect TripleO's community feedback on doing > weekly meetings on #tripleo instead

Re: [openstack-dev] [tripleo] proposing Alex Schultz tripleo-core in all projects

On Fri, Jul 7, 2017 at 3:09 PM, Emilien Macchi wrote: > Alex has demonstrated high technical and community skills in TripleO - > where he's already core on THT, instack-undercloud, and puppet-tripleo > - but also very involved in other repos. > I propose that we extend his

Re: [openstack-dev] [TripleO] Propose Attila Darazs and Gabriele Cerami for tripleo-ci core

On Wed, Mar 15, 2017 at 1:14 PM, John Trowbridge wrote: > Both Attila and Gabriele have been rockstars with the work to transition > tripleo-ci to run via quickstart, and both have become extremely > knowledgeable about how tripleo-ci works during that process. They are > both

Re: [openstack-dev] [tripleo] propose Alex Schultz core on tripleo-heat-templates

On Mon, Mar 13, 2017 at 12:00 PM, Emilien Macchi wrote: > Hi, > > Alex is already core on instack-undercloud and puppet-tripleo. > His involvement and knowledge in TripleO Heat Templates has been very > appreciated over the last months and I think we can give him +2 on > this

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

Hi all, Not that it matters one way or the other, Carlos's comment reminded me of some trivia regarding owl eye color that I had read recently: https://owlpedia.wordpress.com/2015/08/06/why-do-owls-have-different-colour-eyes/ On Mon, Mar 13, 2017 at 6:16 AM, Carlos Camacho Gonzalez <

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On Fri, Mar 10, 2017 at 12:56 PM, Heidi Joy Tretheway < heidi...@openstack.org> wrote: > Hi TripleO team, > > Here’s an update on your project logo. Our illustrator tried to be as true > as possible to your original, while ensuring it matched the line weight, > color palette and style of the

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

Hi, FWIW, I prefer the existing logo. There are several valid practical reasons why it would be good to keep it, but I also just like it better. On Mon, Feb 13, 2017 at 11:08 PM, Emilien Macchi wrote: > Team, I've got this email from Heidi. > > I see 3 options : > > 1. Keep

Re: [openstack-dev] [TripleO] Proposing Dmitry Tantsur and Alex Schultz as instack-undercloud cores

On Tue, Jan 31, 2017 at 12:32 PM, Ben Nemec wrote: > In the spirit of all the core team changes, here are a couple more I'd > like to propose. > > Dmitry has been very helpful reviewing in instack-undercloud for a long > time so this is way overdue. I'm also going to

[openstack-dev] [tripleo] Feature Freeze Exception request for octavia-services-integration

some new issues of what can be done during deployment, having the basic services easily deployable allows contributors and other interested parties to better evaluate, discuss, develop and test solutions. Cheers, Brent Eagles

Re: [openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

On Tue, Jan 24, 2017 at 1:33 PM, Juan Antonio Osorio wrote: > Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both > on the current CI solution and in getting tripleo-quickstart jobs for > it); So I would like to propose him as part of the TripleO CI core

Re: [openstack-dev] [tripleo] Update TripleO core members

On Mon, Jan 23, 2017 at 3:33 PM, Emilien Macchi wrote: > Greeting folks, > > I would like to propose some changes in our core members: > > - Remove Jay Dobies who has not been active in TripleO for a while > (thanks Jay for your hard work!). > - Add Flavio Percoco core on

Re: [openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

On Thu, Dec 1, 2016 at 7:03 PM, James Slagle wrote: > On Thu, Dec 1, 2016 at 5:26 PM, Emilien Macchi wrote: > > Team, > > > > Alex Schultz (mwhahaha on IRC) has been active on TripleO since a few > > months now. While he's very active in different

Re: [openstack-dev] [TripleO] Proposing Julie Pichon for tripleo core

On Tue, Nov 22, 2016 at 1:31 PM, Dougal Matthews wrote: > Hi all, > > I would like to propose we add Julie (jpich) to the TripleO core team for > python-tripleoclient and tripleo-common. This nomination is based partially > on review stats[1] and also my experience with her

Re: [openstack-dev] [tripleo] Is it time to reconsider how we configure OVS bridges in the overcloud?

Hi Dan, On Thu, Nov 10, 2016 at 1:25 PM, Dan Sneddon wrote: > ​ > > Brent, > > Thanks for taking the time to analyze this situation. I see a couple of > potential issues with the topology you are suggesting. > > First of all, what about the scenario where a system has only

Re: [openstack-dev] [tripleo] possible backports for stable/newton

Hi Alan, On Wed, Nov 9, 2016 at 6:10 AM, Alan Pevec wrote: > > Since our cherry picks don't seem to be considered equivalents by git > > (probably because of modified commit messages) > > I'd like to understand why is that, do you have an example? > It should work when

[openstack-dev] [tripleo] Is it time to reconsider how we configure OVS bridges in the overcloud?

Hi all, A recent critical issue that has come up that has compelled me to propose reconsidering our default and OVS based network configuration examples : https://bugs.launchpad.net/tripleo/+bug/1640812 - Network connectivity lost on node reboot I've been thinking about it for awhile, but you

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

On Fri, Nov 4, 2016 at 3:10 PM, Emilien Macchi wrote: > MIchele Baldessari (bandini on IRC) has consistently demonstrated high > levels of contributions in TripleO projects, specifically in High > Availability area where's he's for us a guru (I still don't understand > how

Re: [openstack-dev] [tripleo] possible backports for stable/newton

Hi Michele, vous autres, On Thu, Nov 3, 2016 at 4:50 AM, Michele Baldessari <mich...@acksyn.org> wrote: > Hi Brent ;) > > On Thu, Nov 03, 2016 at 01:20:12AM -0230, Brent Eagles wrote: > > puppet-tripleo > > > > https://review.openstack.org/#/c/389583/ Set redis f

[openstack-dev] [tripleo] possible backports for stable/newton

Hi all, ​After forgetting to backport something to stable newton (thanks Emilien and Alex!), I felt it worthwhile to check for patches that may have been missed. Since our cherry picks don't seem to be considered equivalents by git (probably because of modified commit messages), I resorted to

Re: [openstack-dev] [tripleo][ci] Temporary increase for the OVB undercloud instance memory

Hi, On Thu, Sep 22, 2016 at 1:48 PM, James Slagle wrote: > On Thu, Sep 22, 2016 at 10:36 AM, Gabriele Cerami > wrote: > > Hi, > > > > As reported on this bug > > > > https://bugs.launchpad.net/tripleo/+bug/1626483 > > > > HA gate and periodic jobs

Re: [openstack-dev] [tripleo] composable roles team

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/01/2016 08:01 PM, Emilien Macchi wrote: >> If a feature can't land without disruption, then why not using a >> special branch to be merged once the feature is complete ? > > The problem is that during our work, some people will update the

Re: [openstack-dev] [Neutron] Newton blueprints call for action

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Armando, On 05/04/16 01:13 AM, Armando M. wrote: > Hi Neutrinos, > > During today's team meeting [0], we went through the current > milestone workload [1]. > > This is mostly made of Mitaka backlog items, amongst which we > discussed two

[openstack-dev] [nova][neutron][SR-IOV] Hardware changes and shifting PCI addresses

Hi, I was recently informed of a situation that came up when an engineer added an SR-IOV nic to a compute node that was hosting some guests that had VFs attached. Unfortunately, adding the card shuffled the PCI addresses causing some degree of havoc. Basically, the PCI addresses associated with

Re: [openstack-dev] [Nova][Neutron] Cross-project coordination

Hi, On Thu, May 07, 2015 at 10:03:30PM +, Sean M. Collins wrote: On Wed, Apr 22, 2015 at 06:41:58PM EDT, Jay Pipes wrote: Agreed. I'm hoping that someone in the Nova community -- note, this does not need to be a Nova core contributor -- can step up to the plate and serve in this

Re: [openstack-dev] [Nova][Neutron] out-of-tree plugin for Mech driver/L2 and vif_driver

Hi all, On Wed, Mar 04, 2015 at 10:52:10AM -0330, Brent Eagles wrote: Hi all, snip/ Thanks Maxime. I've made some updates to the etherpad. (https://etherpad.openstack.org/p/nova_vif_plug_script_spec) I'm going to start some proof of concept work these evening. If I get anything worth

Re: [openstack-dev] [Nova][Neutron] out-of-tree plugin for Mech driver/L2 and vif_driver

Hi all, On Wed, Feb 18, 2015 at 04:12:11PM -0330, Brent Eagles wrote: Hi, snip/ Thanks Maxime. I've made some updates to the etherpad. (https://etherpad.openstack.org/p/nova_vif_plug_script_spec) I'm going to start some proof of concept work these evening. If I get anything worth reading

Re: [openstack-dev] [Nova][Neutron] out-of-tree plugin for Mech driver/L2 and vif_driver

Hi, On 18/02/2015 1:53 PM, Maxime Leroy wrote: Hi Brent, snip/ Thanks for your help on this feature. I have just created a channel irc: #vif-plug-script-support to speak about it. I think it will help to synchronize effort on vif_plug_script development. Anyone is welcome on this channel!

Re: [openstack-dev] [Nova][Neutron] out-of-tree plugin for Mech driver/L2 and vif_driver

Hi Maxime, Neil, On 16/01/2015 1:39 PM, Maxime Leroy wrote: On Wed, Jan 14, 2015 at 6:16 PM, Neil Jerram neil.jer...@metaswitch.com wrote: Maxime Leroy maxime.le...@6wind.com writes: Ok, thank you for the details. I will look how to implement this feature. Hi Maxime, Did you have time

Re: [openstack-dev] [Nova][Neutron] Thoughts on the nova-neutron interface

is being worked around, relevant changes made in the neutron API itself. In that sense it is not unlike what Salvatore proposes but the approach is different and ultimately not nova-specific at all. Cheers, Brent Eagles

Re: [openstack-dev] [nova] pci pass through turing complete config options?

Hi, On 28/10/2014 10:39 AM, Sean Dague wrote: On 10/28/2014 08:31 AM, Daniel P. Berrange wrote: snip I don't think that is really very extensible for the future to drop the key name. We've already extended the info we record here at least once, and I expect we'd want to add more fields

Re: [openstack-dev] [Nova][Neutron][Technical Committee] nova-network - Neutron. Throwing a wrench in the Neutron gap analysis

On Wed, Aug 06, 2014 at 01:40:28PM +0800, Tom Fifield wrote: snip/ While DB migrations are running things like the nova metadata service can/will misbehave - and user code within instances will be affected. Thats arguably VM downtime. OTOH you could define it more narrowly as 'VMs are not

[openstack-dev] [nova][neutron] Networks without subnets

Hi, A bug titled Creating quantum L2 networks (without subnets) doesn't work as expected (https://bugs.launchpad.net/nova/+bug/1039665) was reported quite some time ago. Beyond the discussion in the bug report, there have been related bugs reported a few times. *

Re: [openstack-dev] Informal meeting before SR-IOV summit presentation

On 09/05/14 04:21 PM, Sandhya Dasu (sadasu) wrote: Thanks for all your replies. Thanks for the great inputs on how to frame the discussion in the etherpad so it becomes easier for people to get on board. We will add author indent to track the source of the changes. Will work on cleaning that

Re: [openstack-dev] Informal meeting before SR-IOV summit presentation

On Thu, May 08, 2014 at 08:40:01PM +, Robert Li (baoli) wrote: On 5/8/14, 4:33 PM, Steve Gordon sgor...@redhat.com wrote: snip FWIW, it is nice to keep the author of a particular indent level in the message /snip Dan Smith d...@danplanet.com wrote: What would be the purpose of doing

Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the FloatingIPChecker control point

Salvatore Orlando wrote: Before starting this post I confess I did not read with the required level of attention all this thread, so I apologise for any repetition. I just wanted to point out that floating IPs in neutron are created asynchronously when using the l3 agent, and I think this is

Re: [openstack-dev] [neutron][qa] test_network_basic_ops and the FloatingIPChecker control point

Hi, Yair Fried wrote: I would also like to point out that, since Brent used compute.build_timeout as the timeout value ***It takes more time to update FLIP in nova DB, than for a VM to build*** Yair Agreed. I think that's an extremely important highlight of this discussion. Propagation of

[openstack-dev] [neutron][qa] test_network_basic_ops and the FloatingIPChecker control point

Hi, Yair and I were discussing a change that I initiated and was incorporated into the test_network_basic_ops test. It was intended as a configuration control point for floating IP address assignments before actually testing connectivity. The question we were discussing was whether this

Re: [openstack-dev] [neutron] Creating recipes for mimicking behavior of nova-networking network managers.

On 12/09/2013 04:05 PM, Brent Eagles wrote: On 12/04/2013 07:56 PM, Tom Fifield wrote: On 05/12/13 01:14, Brent Eagles wrote: Hi, snip I think that's a great idea. What kind of format would you like to see the recepies in? Regards, Tom I think a wiki is the right way to start

[openstack-dev] [neutron] Creating recipes for mimicking behavior of nova-networking network managers.

Hi, As part of the Icehouse nova-networking parity effort, we need to describe how nova-networking managers work and how the behavior is mapped to neutron. The benefits are: 1. It aides migration: deployers who are nova-network savvy can see how functionality maps from one to the other.