Re: [openstack-dev] Stepping down from Neutron core team

[Miguel Lavalle]

Hi Hirofumi,

Thanks for your contributions to the project over these years. You will be
missed. We also wish the best in your future endeavors.

Best regards

Miguel

On Sun, Dec 2, 2018 at 8:11 AM Hirofumi Ichihara <
ichihara.hirof...@gmail.com> wrote:

> Hi all,
>
>
> I’m stepping down from the core team because my role changed and I cannot
> have responsibilities of neutron core.
>
>
> My start of neutron was 5 years ago. I had many good experiences from
> neutron team.
>
> Today neutron is great project. Neutron gets new reviewers, contributors
> and, users.
>
> Keep on being a great community.
>
>
> Thanks,
>
> Hirofumi
> __
> 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] [neutron] [drivers] Cancelling weekly meeting on November 23rd

[Miguel Lavalle]

Dear Neutron team,

Due to the Thanksgiving Holiday in the USA, several members of the team
will not be able to attend the weekly meeting. Let's cancel it and resume
normally on the 30th of November

Best regards

Miguel
__
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] [neutron] [drivers] Cancelling weekly meeting on November 16th

[Miguel Lavalle]

Hi Neutron Team,

The majority of the drivers team (Akihiro, Takashi and myself) are
attending the Berlin Summit and will be travelling the day of the meeting.
As a consequence, let's cancel it.

Best regards

Miguel
__
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] [neutron] Cancelling weekly meeting on November 12th

[Miguel Lavalle]

Dear Neutron Team,

Due to the OpenStack Summit in Berlin and the activities around it, let's
cancel the weekly IRC meeting on November 12th. We will resume normally on
the 20th.

Best regards

Miguel
__
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] Neutron stadium project Tempest plugins

[Miguel Lavalle]

Dear Neutron Stadium projects,

In a QA session during the recent PTG in Denver, it was suggested that the
Stadium projects should move their Tempest plugins to a repository of their
own or added to the Neutron Tempest plugin repository (
https://github.com/openstack/neutron-tempest-plugin). The purpose of this
message is to start a conversation for the Stadium projects to indicate
what is their preference. Please respond to this thread indicating how do
you want to move forward.

Best regards

Miguel
__
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] [neutron] [drivers] Cancelling drivers meeting on October 19th

[Miguel Lavalle]

Dear Neutron team,

We don't have triaged RFEs to be discussed during the drivers meeting on
October 19th. So let's skip that meeting and we will resume normally on the
26th.

Best regards

Miguel
__
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][neutron-release] feature/graphql branch rebase

[Miguel Lavalle]

Hi Gilles,

The merge of master into feature/graphql  has been approved:
https://review.openstack.org/#/c/609455. In the future, you can create your
own merge patch following the instructions here:
https://docs.openstack.org/infra/manual/drivers.html#merge-master-into-feature-branch.
The Neutron team will catch it in Gerrit and review it

Regards

Miguel

On Thu, Oct 4, 2018 at 11:44 PM Gilles Dubreuil  wrote:

> Hey Neutron folks,
>
> I'm just reiterating the request.
>
> Thanks
>
>
> On 20/06/18 11:34, Gilles Dubreuil wrote:
> > Could someone from the Neutron release group rebase feature/graphql
> > branch against master/HEAD branch please?
> >
> > Regards,
> > Gilles
> >
> >
>
>
__
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][stable] Stable Core Team Update

[Miguel Lavalle]

Hi Stable Team,

Since it has been more than a week since this nomination was posted and we
have received only positive feedback, can we move ahead and add Bernard
Cafarelli to Neutron Stable core team?

Thanks and regards

Miguel

On Wed, Oct 3, 2018 at 8:32 AM Nate Johnston 
wrote:

> On Tue, Oct 02, 2018 at 10:41:58AM -0500, Miguel Lavalle wrote:
>
> > I want to nominate Bernard Cafarrelli as a stable core reviewer for
> Neutron
> > and related projects. Bernard has been increasing the number of stable
> > reviews he is doing for the project [1]. Besides that, he is a stable
> > maintainer downstream for his employer (Red Hat), so he can bring that
> > valuable experience to the Neutron stable team.
>
> I'm not on the stable team, but an enthusiastic +1 from me!
>
> Nate
>
> __
> 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] [neutron][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue

[Miguel Lavalle]

Thomas, Miguel,

Next step is just push a patch for review with the definition of your job.
We can discuss the details in Gerrit

Cheers

On Wed, Oct 3, 2018 at 4:39 AM Miguel Angel Ajo Pelayo 
wrote:

> That's fantastic,
>
>I believe we could add some of the networking ovn jobs, we need to
> decide which one would be more beneficial.
>
> On Tue, Oct 2, 2018 at 10:02 AM  wrote:
>
>> Hi Miguel, all,
>>
>> The initiative is very welcome and will help make it more efficient to
>> develop in stadium projects.
>>
>> legacy-tempest-dsvm-networking-bgpvpn-bagpipe would be a candidate, for
>> networking-bgpvpn and networking-bagpipe (it covers API and scenario
>> tests for the BGPVPN API (networking-bgpvpn) and given that
>> networking-bagpipe is used as reference driver, it exercises a large
>> portion of networking-bagpipe as well).
>>
>> Having this one will help a lot.
>>
>> Thanks,
>>
>> -Thomas
>>
>>
>> On 9/30/18 2:42 AM, Miguel Lavalle wrote:
>> > Dear networking Stackers,
>> >
>> > During the recent PTG in Denver, we discussed measures to prevent
>> > patches merged in the Neutron repo breaking Stadium and related
>> > networking projects in general. We decided to implement the following:
>> >
>> > 1) For Stadium projects, we want to add non-voting jobs to the Neutron
>> > check queue
>> > 2) For non stadium projects, we are inviting them to add 3rd party CI
>> jobs
>> >
>> > The next step is for each project to propose the jobs that they want
>> > to run against Neutron patches.
>> >
>> > Best regards
>> >
>> > Miguel
>> >
>> >
>> __
>> > 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
>>
>>
>> _
>>
>> Ce message et ses pieces jointes peuvent contenir des informations
>> confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
>> recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
>> electroniques etant susceptibles d'alteration,
>> Orange decline toute responsabilite si ce message a ete altere, deforme
>> ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or privileged
>> information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and
>> delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have
>> been modified, changed or falsified.
>> Thank you.
>>
>>
>> __
>> 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
>>
>
>
> --
> Miguel Ángel Ajo
> OSP / Networking DFG, OVN Squad Engineering
> __
> 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] [neutron][stable] Stable Core Team Update

[Miguel Lavalle]

Hi Stable Team,

I want to nominate Bernard Cafarrelli as a stable core reviewer for Neutron
and related projects. Bernard has been increasing the number of stable
reviews he is doing for the project [1]. Besides that, he is a stable
maintainer downstream for his employer (Red Hat), so he can bring that
valuable experience to the Neutron stable team.

Thanks and regards

Miguel

[1]
https://review.openstack.org/#/q/(project:openstack/neutron+OR+openstack/networking-sfc+OR+project:openstack/networking-ovn)++branch:%255Estable/.*+reviewedby:%22Bernard+Cafarelli+%253Cbcafarel%2540redhat.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] [neutron][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue

[Miguel Lavalle]

Hi Takashi,

We are open to your suggestion. What job do you think will be helpful in
minimizing the possibility of Neutron patches breaking your project?

Best regards

On Sun, Sep 30, 2018 at 11:25 PM Takashi Yamamoto 
wrote:

> hi,
>
> what kind of jobs should it be?  eg. unit tests, tempest, etc...
> On Sun, Sep 30, 2018 at 9:43 AM Miguel Lavalle 
> wrote:
> >
> > Dear networking Stackers,
> >
> > During the recent PTG in Denver, we discussed measures to prevent
> patches merged in the Neutron repo breaking Stadium and related networking
> projects in general. We decided to implement the following:
> >
> > 1) For Stadium projects, we want to add non-voting jobs to the Neutron
> check queue
> > 2) For non stadium projects, we are inviting them to add 3rd party CI
> jobs
> >
> > The next step is for each project to propose the jobs that they want to
> run against Neutron patches.
> >
> > Best regards
> >
> > Miguel
> >
> __
> > 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] [neutron][neutron-lib] Seeking neutron-lib developers

[Miguel Lavalle]

Dear Neutron community,

As everybody knows, neutron-lib "is an OpenStack library project used by
Neutron, Advanced Services, and third-party projects that aims to provide
common functionality across all such consumers" (
https://docs.openstack.org/neutron-lib/latest/). In general terms, the
effort in neutron-lib consists of two steps:

   1. Extract common functionality from Neutron and re-home it in
   neutron-lib.
   2. Consume the re-homed functionality by Neutron and all its related
   networking projects.

This has been an on-going effort for several cycles and there is still a
lot do. During the recent Stein PTG in Denver, the team agreed to send a
message to the mailing list to invite community developers to help with
this effort. If you are interested in participating, please add your name
to this etherpad:
https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list.
Once we have a group of volunteers, Boden Russel (itc: boden) has agreed to
create a to-do list.

Best regards

Miguel
__
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] [neutron][stadium][networking] Seeking proposals for non-voting Stadium projects in Neutron check queue

[Miguel Lavalle]

Dear networking Stackers,

During the recent PTG in Denver, we discussed measures to prevent patches
merged in the Neutron repo breaking Stadium and related networking projects
in general. We decided to implement the following:

1) For Stadium projects, we want to add non-voting jobs to the Neutron
check queue
2) For non stadium projects, we are inviting them to add 3rd party CI jobs

The next step is for each project to propose the jobs that they want to run
against Neutron patches.

Best regards

Miguel
__
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] [ironic][neutron] SmartNics with Ironic

[Miguel Lavalle]

Hi,

Yes, this also matches the recollection of the joint conversation in
Denver. Please look at the "Ironic x-project discussion - Smartnics"
section in
http://lists.openstack.org/pipermail/openstack-dev/2018-September/135032.html

Regards

Miguel



On Thu, Sep 27, 2018 at 1:31 PM Julia Kreger 
wrote:

> Greetings everyone,
>
> Now that the PTG is over, I would like to go ahead and get the
> specification that was proposed to ironic-specs updated to represent
> the discussions that took place at the PTG.
>
> A few highlights from my recollection:
>
> * Ironic being the source of truth for the hardware configuration for
> the neutron agent to determine where to push configuration to. This
> would include the address and credential information (certificates
> right?).
> * The information required is somehow sent to neutron (possibly as
> part of the binding profile, which we could send at each time port
> actions are requested by Ironic.)
> * The Neutron agent running on the control plane connects outbound to
> the smartnic, using information supplied to perform the appropriate
> network configuration.
> * In Ironic, this would likely be a new network_interface driver
> module, with some additional methods that help facilitate the
> work-flow logic changes needed in each deploy_interface driver module.
> * Ironic would then be informed or gain awareness that the
> configuration has been completed and that the deployment can proceed.
> (A different spec has been proposed regarding this.)
>
> I have submitted a forum session based upon this and the agreed upon
> goal at the PTG was to have the ironic spec written up to describe the
> required changes.
>
> I guess the next question is, who wants to update the specification?
>
> -Julia
>
> __
> 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] [taas] rocky

[Miguel Lavalle]

Thanks Takashi

On Wed, Sep 26, 2018 at 4:57 AM Takashi Yamamoto 
wrote:

> hi,
>
> it seems we forgot to create rocky branch.
> i'll make a release and the branch sooner or later, unless someone
> beat me to do so.
>
> __
> 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] Neutron drivers meeting on September 21st

[Miguel Lavalle]

Hi,

Since we just came back from the PTG in Denver and we reviewed / discussed
many RFEs, let's skip the Drivers meeting tomorrow, Friday 21st. We will
resume the meeting on the 28th

Best regards

Miguel
__
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] Core status

[Miguel Lavalle]

Hi Gary,

As I say during our private conversation, we don't like to see you going,
but we understand that you have other career opportunities. I wish you luck
in your next challenge and please remember that you will always be welcome
here

Best regards

Miguel

On Thu, Sep 20, 2018 at 9:49 AM Brian Haley  wrote:

> On 09/19/2018 02:19 PM, Gary Kotton wrote:
> > Hi,
> >
> > I have recently transitioned to a new role where I will be working on
> > other parts of OpenStack. Sadly I do not have the necessary cycles to
> > maintain my core responsibilities in the neutron community. Nonetheless
> > I will continue to be involved.
>
> Thanks for all your work over the years, especially in keeping the
> reviews moving along on the neutron stable branches.  Good luck in your
> new role!
>
> -Brian
>
> __
> 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] [os-upstream-institute] Team lunch at the PTG next week - ACTION NEEDED

[Miguel Lavalle]

Hi Ildikó,

Wednesday lunch is fine with me

Regards

On Fri, Sep 7, 2018 at 5:30 PM, Ildiko Vancsa 
wrote:

> Hi Training Team,
>
> As a couple of us will be at the PTG next week it would be great to get
> together one of the days maybe for lunch.
>
> Wednesday would work the best for Kendall and me, but we can look into
> other days as well if it would not work for the majority of people around.
>
> So my questions would be:
>
> * Are you interested in getting together one of the lunch slots during
> next week?
>
> * Would Wednesday work for you or do you have another preference?
>
> Please drop a response to this thread and we will figure it out by Monday
> or early next week based on the responses.
>
> Thanks,
> Ildikó
> (IRC: ildikov)
>
>
>
> __
> 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] [neutron] PTG agenda

[Miguel Lavalle]

Dear Neutron Team,

I have scheduled all the topics that were proposed for the PTG in Denver
here: https://etherpad.openstack.org/p/neutron-stein-ptg. Please go to line
128 and onwards to see the detailed schedule. Please reach out to me should
we need to make any changes or adjustments

Best regards

Miguel
__
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] [neutron] Weekly meeting canceled on Tuesday 11th

[Miguel Lavalle]

Dear Neutron Team,

Due to the PTG in Denver, the Neutron weekly team on Tuesday 11th at 1400
UTC is canceled. We will resume our meeting on Monday September 17th at
2100 UTC

Best regards

Miguel
__
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] Stepping down from Neutron core team

[Miguel Lavalle]

Kuba,

I made a last ditch awkward effort to convince you to stay a little longer
unsuccessfully. I understand, though, that now you have other commitments.
I know you will be successful in your new adventures, because you are
really smart and hard working. And please remember that we will take you
back with open arms at any moment in the future.

Finally, I wish you good luck, because we all need a little bit of it

Best regards

Miguel

On Fri, Aug 31, 2018 at 3:49 AM, Slawomir Kaplonski 
wrote:

> It’s sad news. Thanks Kuba for all Your help You gave me when I was
> newcomer in Neutron community.
> Good luck in Your next projects :)
>
> > Wiadomość napisana przez Jakub Libosvar  w dniu
> 31.08.2018, o godz. 10:24:
> >
> > Hi all,
> >
> > as you have might already heard, I'm no longer involved in Neutron
> > development due to some changes. Therefore I'm officially stepping down
> > from the core team because I can't provide same quality reviews as I
> > tried to do before.
> >
> > I'd like to thank you all for the opportunity I was given in the Neutron
> > team, thank you for all I have learned over the years professionally,
> > technically and personally. Tomorrow it's gonna be exactly 5 years since
> > I started hacking Neutron and I must say I really enjoyed working with
> > all Neutrinos here and I had privilege to meet most of you in person and
> > that has an extreme value for me. Keep on being a great community!
> >
> > Thank you again!
> > Kuba
> >
> > 
> __
> > 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
>
> —
> Slawek Kaplonski
> Senior software engineer
> Red Hat
>
>
> __
> 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] [neutron][nova] Small bandwidth demo on the PTG

[Miguel Lavalle]

Nova room is fine. See you'all there

On Fri, Aug 31, 2018 at 3:29 AM, Balázs Gibizer  wrote:

>
>
> On Thu, Aug 30, 2018 at 8:13 PM, melanie witt  wrote:
>
>> On Thu, 30 Aug 2018 12:43:06 -0500, Miguel Lavalle wrote:
>>
>>> Gibi, Bence,
>>>
>>> In fact, I added the demo explicitly to the Neutron PTG agenda from
>>> 1:30  to 2, to give it visiblilty
>>>
>>
>> I'm interested in seeing the demo too. Will the demo be shown at the
>> Neutron room or the Nova room? Historically, lunch has ended at 1:30, so
>> this will be during the same time as the Neutron/Nova cross project time.
>> Should we just co-locate together for the demo and the session? I expect
>> anyone watching the demo will want to participate in the Neutron/Nova
>> session as well. Either room is fine by me.
>>
>>
> I assume that the nova - neturon cross project session will be in the nova
> room, so I propose to have the demo there as well to avoid unnecessarily
> moving people around. For us it is totally OK to start the demo at 1:30.
>
> Cheers,
> gibi
>
>
>
> -melanie
>>
>> On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer  <
>>> balazs.gibi...@ericsson.com <mailto:balazs.gibi...@ericsson.com>> wrote:
>>>
>>> Hi,
>>>
>>> Based on the Nova PTG planning etherpad [1] there is a need to talk
>>> about the current state of the bandwidth work [2][3]. Bence
>>> (rubasov) has already planned to show a small demo to Neutron folks
>>> about the current state of the implementation. So Bence and I are
>>> wondering about bringing that demo close to the nova - neutron cross
>>> project session. That session is currently planned to happen
>>> Thursday after lunch. So we are think about showing the demo right
>>> before that session starts. It would start 30 minutes before the
>>> nova - neutron cross project session.
>>>
>>> Are Nova folks also interested in seeing such a demo?
>>>
>>> If you are interested in seeing the demo please drop us a line or
>>> ping us in IRC so we know who should we wait for.
>>>
>>> Cheers,
>>> gibi
>>>
>>> [1] https://etherpad.openstack.org/p/nova-ptg-stein
>>> <https://etherpad.openstack.org/p/nova-ptg-stein>
>>> [2]
>>> https://specs.openstack.org/openstack/neutron-specs/specs/ro
>>> cky/minimum-bandwidth-allocation-placement-api.html
>>> <https://specs.openstack.org/openstack/neutron-specs/specs/r
>>> ocky/minimum-bandwidth-allocation-placement-api.html>
>>> [3]
>>> https://specs.openstack.org/openstack/nova-specs/specs/rocky
>>> /approved/bandwidth-resource-provider.html
>>> <https://specs.openstack.org/openstack/nova-specs/specs/rock
>>> y/approved/bandwidth-resource-provider.html>
>>>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> <http://openstack-dev-requ...@lists.openstack.org?subject:un
>>> subscribe>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>>>
>>>
>>>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.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:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Nominating Chris Dent for placement-core

[Miguel Lavalle]

I don't get to vote here either, but I was one of the first users of the
Placement API (Neutron Routed Networks) and I always got great support and
guidance from cdent. So +1 and well deserved

On Fri, Aug 31, 2018 at 10:45 AM, Eric Fried  wrote:

> The openstack/placement project [1] and its core team [2] have been
> established in gerrit.
>
> I hereby nominate Chris Dent for membership in the placement-core team.
> He has been instrumental in the design, implementation, and stewardship
> of the placement API since its inception and has shown clear and
> consistent leadership.
>
> As we are effectively bootstrapping placement-core at this time, it
> would seem appropriate to consider +1/-1 responses from heavy placement
> contributors as well as existing cores (currently nova-core).
>
> [1] https://review.openstack.org/#/admin/projects/openstack/placement
> [2] https://review.openstack.org/#/admin/groups/1936,members
>
> __
> 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] [octavia] Proposing Carlos Goncalves (cgoncalves) as an Octavia core reviewer

[Miguel Lavalle]

Well, I don't vote here but I stiil want to express my +1. I knew this was
going to happen sooner rather than later

On Thu, Aug 30, 2018 at 10:24 PM, Michael Johnson 
wrote:

> Hello Octavia community,
>
> I would like to propose Carlos Goncalves as a core reviewer on the
> Octavia project.
>
> Carlos has provided numerous enhancements to the Octavia project,
> including setting up the grenade gate for Octavia upgrade testing.
>
> Over the last few releases he has also been providing quality reviews,
> in line with the other core reviewers [1]. I feel that Carlos would
> make an excellent addition to the Octavia core reviewer team.
>
> Existing Octavia core reviewers, please reply to this email with your
> support or concerns with adding Jacky to the core team.
>
> Michael
>
> [1] http://stackalytics.com/report/contribution/octavia-group/90
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron][nova] Small bandwidth demo on the PTG

[Miguel Lavalle]

Gibi, Bence,

In fact, I added the demo explicitly to the Neutron PTG agenda from 1:30 to
2, to give it visiblilty

Cheers

On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer  wrote:

> Hi,
>
> Based on the Nova PTG planning etherpad [1] there is a need to talk about
> the current state of the bandwidth work [2][3]. Bence (rubasov) has already
> planned to show a small demo to Neutron folks about the current state of
> the implementation. So Bence and I are wondering about bringing that demo
> close to the nova - neutron cross project session. That session is
> currently planned to happen Thursday after lunch. So we are think about
> showing the demo right before that session starts. It would start 30
> minutes before the nova - neutron cross project session.
>
> Are Nova folks also interested in seeing such a demo?
>
> If you are interested in seeing the demo please drop us a line or ping us
> in IRC so we know who should we wait for.
>
> Cheers,
> gibi
>
> [1] https://etherpad.openstack.org/p/nova-ptg-stein
> [2] https://specs.openstack.org/openstack/neutron-specs/specs/ro
> cky/minimum-bandwidth-allocation-placement-api.html
> [3] https://specs.openstack.org/openstack/nova-specs/specs/rocky
> /approved/bandwidth-resource-provider.html
>
>
> __
> 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] [neutron][nova] Small bandwidth demo on the PTG

[Miguel Lavalle]

Gibi, Bence,

Thanks for putting this demo together. Please count me in

Regards

On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer  wrote:

> Hi,
>
> Based on the Nova PTG planning etherpad [1] there is a need to talk about
> the current state of the bandwidth work [2][3]. Bence (rubasov) has already
> planned to show a small demo to Neutron folks about the current state of
> the implementation. So Bence and I are wondering about bringing that demo
> close to the nova - neutron cross project session. That session is
> currently planned to happen Thursday after lunch. So we are think about
> showing the demo right before that session starts. It would start 30
> minutes before the nova - neutron cross project session.
>
> Are Nova folks also interested in seeing such a demo?
>
> If you are interested in seeing the demo please drop us a line or ping us
> in IRC so we know who should we wait for.
>
> Cheers,
> gibi
>
> [1] https://etherpad.openstack.org/p/nova-ptg-stein
> [2] https://specs.openstack.org/openstack/neutron-specs/specs/ro
> cky/minimum-bandwidth-allocation-placement-api.html
> [3] https://specs.openstack.org/openstack/nova-specs/specs/rocky
> /approved/bandwidth-resource-provider.html
>
>
> __
> 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] [neutron] Rocky PTG retrospective etherpad

[Miguel Lavalle]

Here's the etherpad:
https://etherpad.openstack.org/p/neutron-rocky-retrospective

On Wed, Aug 29, 2018 at 3:24 PM, Miguel Lavalle  wrote:

> Dear Neutrinos,
>
> In preparation for our PTG in Denver, I have started an etherpad to gather
> feedback for our retrospective session. Please add your comments there
>
> Best regards
>
> Miguel
>
__
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] [neutron] Rocky PTG retrospective etherpad

[Miguel Lavalle]

Dear Neutrinos,

In preparation for our PTG in Denver, I have started an etherpad to gather
feedback for our retrospective session. Please add your comments there

Best regards

Miguel
__
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] [Neutron] Denver PTG Team Dinner

[Miguel Lavalle]

Dear Neutron Team,

Our PTG Denver team dinner will take place on Thursday 7pm, at
https://www.famousdaves.com/Denver-Stapleton, 0.5 miles from the
Renaissance Hotel, which translates to an easy 10 minutes walk:
https://goo.gl/JZVg8D

I am holding a reservation under my name for 20 people. Please confirm your
attendance by adding a "Yes" to the line in the etherpad where you
registered your name: https://etherpad.openstack.org/p/neutron-stein-ptg

Looking forward to see you all there

Best regards

Miguel
__
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] [nova][cinder][neutron] Cross-cell cold migration

[Miguel Lavalle]

Hi Matt,

Isn't multiple port binding what we need in the case of ports? In my mind,
the big motivator for multiple port binding is the ability to change a
port's backend

Best regards

Miguel

On Mon, Aug 27, 2018 at 4:32 AM, Gorka Eguileor  wrote:

> On 24/08, Jay S Bryant wrote:
> >
> >
> > On 8/23/2018 12:07 PM, Gorka Eguileor wrote:
> > > On 23/08, Dan Smith wrote:
> > > > > I think Nova should never have to rely on Cinder's hosts/backends
> > > > > information to do migrations or any other operation.
> > > > >
> > > > > In this case even if Nova had that info, it wouldn't be the
> solution.
> > > > > Cinder would reject migrations if there's an incompatibility on the
> > > > > Volume Type (AZ, Referenced backend, capabilities...)
> > > > I think I'm missing a bunch of cinder knowledge required to fully
> grok
> > > > this situation and probably need to do some reading. Is there some
> > > > reason that a volume type can't exist in multiple backends or
> something?
> > > > I guess I think of volume type as flavor, and the same definition in
> two
> > > > places would be interchangeable -- is that not the case?
> > > >
> > > Hi,
> > >
> > > I just know the basics of flavors, and they are kind of similar, though
> > > I'm sure there are quite a few differences.
> > >
> > > Sure, multiple storage arrays can meet the requirements of a Volume
> > > Type, but then when you create the volume you don't know where it's
> > > going to land. If your volume type is too generic you volume could land
> > > somewhere your cell cannot reach.
> > >
> > >
> > > > > I don't know anything about Nova cells, so I don't know the
> specifics of
> > > > > how we could do the mapping between them and Cinder backends, but
> > > > > considering the limited range of possibilities in Cinder I would
> say we
> > > > > only have Volume Types and AZs to work a solution.
> > > > I think the only mapping we need is affinity or distance. The point
> of
> > > > needing to migrate the volume would purely be because moving cells
> > > > likely means you moved physically farther away from where you were,
> > > > potentially with different storage connections and networking. It
> > > > doesn't *have* to mean that, but I think in reality it would. So the
> > > > question I think Matt is looking to answer here is "how do we move an
> > > > instance from a DC in building A to building C and make sure the
> > > > volume gets moved to some storage local in the new building so we're
> > > > not just transiting back to the original home for no reason?"
> > > >
> > > > Does that explanation help or are you saying that's fundamentally
> hard
> > > > to do/orchestrate?
> > > >
> > > > Fundamentally, the cells thing doesn't even need to be part of the
> > > > discussion, as the same rules would apply if we're just doing a
> normal
> > > > migration but need to make sure that storage remains affined to
> compute.
> > > >
> > > We could probably work something out using the affinity filter, but
> > > right now we don't have a way of doing what you need.
> > >
> > > We could probably rework the migration to accept scheduler hints to be
> > > used with the affinity filter and to accept calls with the host or the
> > > hints, that way it could migrate a volume without knowing the
> > > destination host and decide it based on affinity.
> > >
> > > We may have to do more modifications, but it could be a way to do it.
> > >
> > >
> > >
> > > > > I don't know how the Nova Placement works, but it could hold an
> > > > > equivalency mapping of volume types to cells as in:
> > > > >
> > > > >   Cell#1Cell#2
> > > > >
> > > > > VolTypeA <--> VolTypeD
> > > > > VolTypeB <--> VolTypeE
> > > > > VolTypeC <--> VolTypeF
> > > > >
> > > > > Then it could do volume retypes (allowing migration) and that would
> > > > > properly move the volumes from one backend to another.
> > > > The only way I can think that we could do this in placement would be
> if
> > > > volume types were resource providers and we assigned them traits that
> > > > had special meaning to nova indicating equivalence. Several of the
> words
> > > > in that sentence are likely to freak out placement people, myself
> > > > included :)
> > > >
> > > > So is the concern just that we need to know what volume types in one
> > > > backend map to those in another so that when we do the migration we
> know
> > > > what to ask for? Is "they are the same name" not enough? Going back
> to
> > > > the flavor analogy, you could kinda compare two flavor definitions
> and
> > > > have a good idea if they're equivalent or not...
> > > >
> > > > --Dan
> > > In Cinder you don't get that from Volume Types, unless all your
> backends
> > > have the same hardware and are configured exactly the same.
> > >
> > > There can be some storage specific information there, which doesn't
> > > correlate to anything on other hardware.  Volume types may refer to a
> > > specific pool that has been configured in the array to 

[openstack-dev] Appointing Slawek Kaplonski to the Neutron Drivers team

[Miguel Lavalle]

Dear Neutron team,

In order to help the Neutron Drivers team to perform its very important job
of guiding the community to evolve the OpenStack Networking architecture to
meet the needs of our current and future users [1], I have asked Slawek
Kaplonski to join it. Over the past few years, he has gained very valuable
experience with OpenStack Networking, both as a deployer  and more recently
working with one of our key packagers. He played a paramount role in
implementing our QoS (Quality of Service) features, currently leading that
sub-team. He also leads the CI sub-team, making sure the prompt discovery
and fixing of bugs in our software. On top of that, he is one of our most
active reviewers, contributor of code to our reference implementation and
fixer of bugs. I am very confident in Slawek making great contributions to
the Neutron Drivers team.

Best regards

Miguel

[1]
https://docs.openstack.org/neutron/latest/contributor/policies/neutron-teams.html#drivers-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

Re: [openstack-dev] [neutron][api][grapql] Proof of Concept

[Miguel Lavalle]

Gilles,

Ok. Added the patches in Gerrit to this coming Tuesday Neutron weekly
meeting agenda. I will highlight the patches during the meeting

Regards

On Thu, Aug 23, 2018 at 7:09 PM, Gilles Dubreuil 
wrote:

>
>
> On 24/08/18 04:58, Slawomir Kaplonski wrote:
>
>> Hi Miguel,
>>
>> I’m not sure but maybe You were looking for those patches:
>>
>> https://review.openstack.org/#/q/project:openstack/neutron+b
>> ranch:feature/graphql
>>
>>
> Yes that's the one, it's under Tristan Cacqueray name as he helped getting
> started.
>
> Wiadomość napisana przez Miguel Lavalle  w dniu
>>> 23.08.2018, o godz. 18:57:
>>>
>>> Hi Gilles,
>>>
>>> Ed pinged me earlier today in IRC in regards to this topic. After
>>> reading your message, I assumed that you had patches up for review in
>>> Gerrit. I looked for them, with the intent to list them in the agenda of
>>> the next Neutron team meeting, to draw attention to them. I couldn't find
>>> any, though: https://review.openstack.org/#
>>> /q/owner:%22Gilles+Dubreuil+%253Cgdubreui%2540redhat.com%253E%22
>>>
>>> So, how can we help? This is our meetings schedule:
>>> http://eavesdrop.openstack.org/#Neutron_Team_Meeting. Given that you
>>> are Down Under at UTC+10, the most convenient meeting for you is the one on
>>> Monday (even weeks), which would be Tuesday at 7am for you. Please note
>>> that we have an on demand section in our agenda:
>>> https://wiki.openstack.org/wiki/Network/Meetings#On_Demand_Agenda. Feel
>>> free to add topics in that section when you have something to discuss with
>>> the Neutron team.
>>>
>>
> Now that we have a working base API serving GraphQL requests we need to do
> provide the data in respect of Oslo Policy and such.
>
> Thanks for the pointers, I'll add the latter to the Agenda and will be at
> next meeting.
>
>
>
>
>>> Best regards
>>>
>>> Miguel
>>>
>>> On Sun, Aug 19, 2018 at 10:57 PM, Gilles Dubreuil 
>>> wrote:
>>>
>>>
>>> On 25/07/18 23:48, Ed Leafe wrote:
>>> On Jun 6, 2018, at 7:35 PM, Gilles Dubreuil  wrote:
>>> The branch is now available under feature/graphql on the neutron core
>>> repository [1].
>>> I wanted to follow up with you on this effort. I haven’t seen any
>>> activity on StoryBoard for several weeks now, and wanted to be sure that
>>> there was nothing blocking you that we could help with.
>>>
>>>
>>> -- Ed Leafe
>>>
>>>
>>>
>>> Hi Ed,
>>>
>>> Thanks for following up.
>>>
>>> There has been 2 essential counterproductive factors to the effort.
>>>
>>> The first is that I've been busy attending issues on other part of my
>>> job.
>>> The second one is the lack of response/follow-up from the Neutron core
>>> team.
>>>
>>> We have all the plumbing in place but we need to layer the data through
>>> oslo policies.
>>>
>>> Cheers,
>>> Gilles
>>>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.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.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>> —
>> Slawek Kaplonski
>> Senior software engineer
>> Red Hat
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> --
> Gilles Dubreuil
> Senior Software Engineer - Red Hat - Openstack DFG Integration
> Email: gil...@redhat.com
> GitHub/IRC: gildub
> Mobile: +61 400 894 219
>
>
>
> __
> 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] [neutron][api][grapql] Proof of Concept

[Miguel Lavalle]

Hi Gilles,

Ed pinged me earlier today in IRC in regards to this topic. After reading
your message, I assumed that you had patches up for review in Gerrit. I
looked for them, with the intent to list them in the agenda of the next
Neutron team meeting, to draw attention to them. I couldn't find any,
though:
https://review.openstack.org/#/q/owner:%22Gilles+Dubreuil+%253Cgdubreui%2540redhat.com%253E%22

So, how can we help? This is our meetings schedule:
http://eavesdrop.openstack.org/#Neutron_Team_Meeting. Given that you are
Down Under at UTC+10, the most convenient meeting for you is the one on
Monday (even weeks), which would be Tuesday at 7am for you. Please note
that we have an on demand section in our agenda:
https://wiki.openstack.org/wiki/Network/Meetings#On_Demand_Agenda. Feel
free to add topics in that section when you have something to discuss with
the Neutron team.

Best regards

Miguel

On Sun, Aug 19, 2018 at 10:57 PM, Gilles Dubreuil 
wrote:

>
>
> On 25/07/18 23:48, Ed Leafe wrote:
>
>> On Jun 6, 2018, at 7:35 PM, Gilles Dubreuil  wrote:
>>
>>> The branch is now available under feature/graphql on the neutron core
>>> repository [1].
>>>
>> I wanted to follow up with you on this effort. I haven’t seen any
>> activity on StoryBoard for several weeks now, and wanted to be sure that
>> there was nothing blocking you that we could help with.
>>
>>
>> -- Ed Leafe
>>
>>
>>
>> Hi Ed,
>
> Thanks for following up.
>
> There has been 2 essential counterproductive factors to the effort.
>
> The first is that I've been busy attending issues on other part of my job.
> The second one is the lack of response/follow-up from the Neutron core
> team.
>
> We have all the plumbing in place but we need to layer the data through
> oslo policies.
>
> Cheers,
> Gilles
>
>
> __
> 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] [neutron] [l3-sub-team] Weekly meeting cancellation

[Miguel Lavalle]

Dear L3 sub-team members,

On August 16th I will be on a business trip and other team members will be
off on vacation. As a consequence, we will cancel our weekly meeting that
day. We will resume at the usual time on the August 23rd

Best regards

Miguel
__
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] [neutron] [drivers]

[Miguel Lavalle]

Dear Neutron team members,

Tomorrow I will be on an airplane during the drivers team meeting time and
one team member is off on vacation. Next week, two of our team members will
be off on vacation. As a consequence, Let's cancel the meetings on August
10th and 17th. We will resume normally on the 24th.

Best regards

Miguel
__
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] [neutron] Bug deputy report week July 30th - August 5th

[Miguel Lavalle]

Dear Neutron Team,

I was the bugs deputy for the week of July 39th - August 6th (inclusive, so
bcafarel has to start on the 7th). Here's the summary of the bugs that were
filed:

High:

https://bugs.launchpad.net/neutron/+bug/1785656
test_internal_dns.InternalDNSTest
fails even though dns-integration extension isn't loaded. Proposed fixes:
https://review.openstack.org/#/c/589247, https://review.openstack.org/#
/c/589255


Medium:

https://bugs.launchpad.net/neutron/+bug/1784837 Test
tempest.scenario.test_security_groups_basic_ops.TestSecurity
GroupsBasicOps.test_in_tenant_traffic fails in
neutron-tempest-dvr-ha-multinode-full job
https://bugs.launchpad.net/neutron/+bug/1784836 Functional tests from
neutron.tests.functional.db.migrations fails randomly
https://bugs.launchpad.net/neutron/+bug/1785582 Connectivity to instance
after L3 router migration from Legacy to HA fails. Assigned to Slawek


Low:

https://bugs.launchpad.net/neutron/+bug/1785025 Install and configure
controller node in Neutron
https://bugs.launchpad.net/neutron/+bug/1784586 Networking guide doesn't
clarify that subnets inherit the RBAC policies of their network. Fix:
https://review.openstack.org/#/c/588844


In discussion:
https://bugs.launchpad.net/neutron/+bug/1784484 intermittent issue getting
assigned MACs for SRIOV nics, causes nova timeout
https://bugs.launchpad.net/neutron/+bug/1784259 Neutron RBAC not working
for multiple extensions
https://bugs.launchpad.net/neutron/+bug/1785615 DNS resolution through
eventlet contact nameservers if there's an IPv4 or IPv6 entry present in
hosts file


RFEs:

https://bugs.launchpad.net/neutron/+bug/1784879 Neutron doesn't update
Designate with some use cases
https://bugs.launchpad.net/neutron/+bug/1784590 neutron-dynamic-routing bgp
agent should have options for MP-BGP
https://bugs.launchpad.net/neutron/+bug/1785608 [RFE] neutron ovs agent
support baremetal port using smart nic


Invalid:

https://bugs.launchpad.net/neutron/+bug/1784950 get_device_details RPC
fails if host not specified
https://bugs.launchpad.net/neutron/+bug/1785189 Floatingip and router
bandwidth speed limit failure


Incomplete:

https://bugs.launchpad.net/neutron/+bug/1785349 policy.json does not
contain rule for auto-allocated-topologies removal
https://bugs.launchpad.net/neutron/+bug/1785539 Some notifications related
to l3 flavor pass context



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

Re: [openstack-dev] [neutron] Stein PTG etherpad

[Miguel Lavalle]

Dear Neutron members,

I should have mentioned it before Please place your name / nick irc
next to the topics you propose in the etherpad, so we can coordinate as the
PTG approaches

Thanks and regards

Miguel

On Fri, Aug 3, 2018 at 10:39 AM, Miguel Lavalle  wrote:

> Dear Stackers,
>
> I have started an etherpad to collect topic proposals to be discussed
> during the PTG in Denver, September 10th - 14th:
> https://etherpad.openstack.org/p/neutron-stein-ptg . Please feel free to
> add your proposals under the "Proposed topics to be scheduled" section.
> Please also sign in under the "Attendance at the PTG" if you plan to be in
> Denver, indicating the days you will be there.
>
> I am looking forward to see many of you in Denver and have a very
> productive PTG!
>
> Best regards
>
> Miguel
>
__
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] Port mirroring for SR-IOV VF to VF mirroring

[Miguel Lavalle]

Hi Forrest,

Please place your name / irc nick next to the topics you propose

Regards




On Fri, Aug 3, 2018 at 8:18 PM, Zhao, Forrest 
wrote:

> Hi Miguel,
>
>
>
> Can we put the proposed topics to this PTG etherpad directly?  Or we
> should first discuss it in weekly Neutron project meeting?
>
>
>
> Please advise; then we’ll follow the process to propose the PTG topics.
>
>
>
> Thanks,
>
> Forrest
>
>
>
> *From:* Miguel Lavalle [mailto:mig...@mlavalle.com]
> *Sent:* Friday, August 3, 2018 11:41 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
>
> *Subject:* Re: [openstack-dev] [neutron] Port mirroring for SR-IOV VF to
> VF mirroring
>
>
>
> Forrest, Manjeet,
>
>
>
> Here you go: https://etherpad.openstack.org/p/neutron-stein-ptg
>
>
>
> Best regards
>
>
>
> On Wed, Aug 1, 2018 at 11:49 AM, Bhatia, Manjeet S <
> manjeet.s.bha...@intel.com> wrote:
>
> Hi,
>
>
>
> Yes, we need to refine spec for sure, once a consensus is reached focus
> will be on implementation,
>
> Here’s implementation patch (WIP) https://review.openstack.org/#/c/584892/
> , we can’t really
>
> review api part until spec if finalized but, other stuff like config and
> common issues can
>
> still be pointed out and progress can be made until consensus on api is
> reached. Miguel, I think
>
> this will be added to etherpad for PTG discussions as well ?
>
>
>
> Thanks and Regards !
>
> Manjeet
>
>
>
>
>
>
>
>
>
> *From:* Miguel Lavalle [mailto:mig...@mlavalle.com]
> *Sent:* Tuesday, July 31, 2018 10:26 AM
> *To:* Zhao, Forrest 
> *Cc:* OpenStack Development Mailing List  openstack.org>
> *Subject:* Re: [openstack-dev] [neutron] Port mirroring for SR-IOV VF to
> VF mirroring
>
>
>
> Hi Forrest,
>
>
>
> Yes, in my email, I was precisely referring to the work around
> https://review.openstack.org/#/c/574477. Now that we are wrapping up
> Rocky, I wanted to raise the visibility of this spec. I am glad you
> noticed. This week we are going to cut our RC-1 and I don't anticipate that
> we will will have a RC-2 for Rocky. So starting next week, let's go back to
> the spec and refine it, so we can start implementing in Stein as soon as
> possible. Depending on how much progress we make in the spec, we may need
> to schedule a discussion during the PTG in Denver, September 10 - 14, in
> case face to face time is needed to reach an agreement. I know that Manjeet
> is going to attend the PTG and he has already talked to me about this spec
> in the recent past. So maybe Manjeet could be the conduit to represent this
> spec in Denver, in case we need to talk about it there
>
>
>
> Best regards
>
>
>
> Miguel
>
>
>
> On Tue, Jul 31, 2018 at 4:12 AM, Zhao, Forrest 
> wrote:
>
> Hi Miguel,
>
>
>
> In your mail “PTL candidacy for the Stein cycle”, it mentioned that “port
> mirroring for SR-IOV VF to VF mirroring” is within Stein goal.
>
>
>
> Could you tell where is the place to discuss the design for this feature?
> Mailing list, IRC channel, weekly meeting or others?
>
>
>
> I was involved in its spec review at https://review.openstack.org/#
> /c/574477/; but it has not been updated for a while.
>
>
>
> Thanks,
>
> Forrest
>
>
>
>
> __
> 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] [neutron] Port mirroring for SR-IOV VF to VF mirroring

[Miguel Lavalle]

Forrest, Manjeet,

Here you go: https://etherpad.openstack.org/p/neutron-stein-ptg

Best regards

On Wed, Aug 1, 2018 at 11:49 AM, Bhatia, Manjeet S <
manjeet.s.bha...@intel.com> wrote:

> Hi,
>
>
>
> Yes, we need to refine spec for sure, once a consensus is reached focus
> will be on implementation,
>
> Here’s implementation patch (WIP) https://review.openstack.org/#/c/584892/
> , we can’t really
>
> review api part until spec if finalized but, other stuff like config and
> common issues can
>
> still be pointed out and progress can be made until consensus on api is
> reached. Miguel, I think
>
> this will be added to etherpad for PTG discussions as well ?
>
>
>
> Thanks and Regards !
>
> Manjeet
>
>
>
>
>
>
>
>
>
> *From:* Miguel Lavalle [mailto:mig...@mlavalle.com]
> *Sent:* Tuesday, July 31, 2018 10:26 AM
> *To:* Zhao, Forrest 
> *Cc:* OpenStack Development Mailing List  openstack.org>
> *Subject:* Re: [openstack-dev] [neutron] Port mirroring for SR-IOV VF to
> VF mirroring
>
>
>
> Hi Forrest,
>
>
>
> Yes, in my email, I was precisely referring to the work around
> https://review.openstack.org/#/c/574477. Now that we are wrapping up
> Rocky, I wanted to raise the visibility of this spec. I am glad you
> noticed. This week we are going to cut our RC-1 and I don't anticipate that
> we will will have a RC-2 for Rocky. So starting next week, let's go back to
> the spec and refine it, so we can start implementing in Stein as soon as
> possible. Depending on how much progress we make in the spec, we may need
> to schedule a discussion during the PTG in Denver, September 10 - 14, in
> case face to face time is needed to reach an agreement. I know that Manjeet
> is going to attend the PTG and he has already talked to me about this spec
> in the recent past. So maybe Manjeet could be the conduit to represent this
> spec in Denver, in case we need to talk about it there
>
>
>
> Best regards
>
>
>
> Miguel
>
>
>
> On Tue, Jul 31, 2018 at 4:12 AM, Zhao, Forrest 
> wrote:
>
> Hi Miguel,
>
>
>
> In your mail “PTL candidacy for the Stein cycle”, it mentioned that “port
> mirroring for SR-IOV VF to VF mirroring” is within Stein goal.
>
>
>
> Could you tell where is the place to discuss the design for this feature?
> Mailing list, IRC channel, weekly meeting or others?
>
>
>
> I was involved in its spec review at https://review.openstack.org/#
> /c/574477/; but it has not been updated for a while.
>
>
>
> Thanks,
>
> Forrest
>
>
>
> __
> 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] [neutron] Stein PTG etherpad

[Miguel Lavalle]

Dear Stackers,

I have started an etherpad to collect topic proposals to be discussed
during the PTG in Denver, September 10th - 14th:
https://etherpad.openstack.org/p/neutron-stein-ptg . Please feel free to
add your proposals under the "Proposed topics to be scheduled" section.
Please also sign in under the "Attendance at the PTG" if you plan to be in
Denver, indicating the days you will be there.

I am looking forward to see many of you in Denver and have a very
productive PTG!

Best regards

Miguel
__
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] Port mirroring for SR-IOV VF to VF mirroring

[Miguel Lavalle]

Hi Forrest,

Yes, in my email, I was precisely referring to the work around
https://review.openstack.org/#/c/574477. Now that we are wrapping up Rocky,
I wanted to raise the visibility of this spec. I am glad you noticed. This
week we are going to cut our RC-1 and I don't anticipate that we will will
have a RC-2 for Rocky. So starting next week, let's go back to the spec and
refine it, so we can start implementing in Stein as soon as possible.
Depending on how much progress we make in the spec, we may need to schedule
a discussion during the PTG in Denver, September 10 - 14, in case face to
face time is needed to reach an agreement. I know that Manjeet is going to
attend the PTG and he has already talked to me about this spec in the
recent past. So maybe Manjeet could be the conduit to represent this spec
in Denver, in case we need to talk about it there

Best regards

Miguel

On Tue, Jul 31, 2018 at 4:12 AM, Zhao, Forrest 
wrote:

> Hi Miguel,
>
>
>
> In your mail “PTL candidacy for the Stein cycle”, it mentioned that “port
> mirroring for SR-IOV VF to VF mirroring” is within Stein goal.
>
>
>
> Could you tell where is the place to discuss the design for this feature?
> Mailing list, IRC channel, weekly meeting or others?
>
>
>
> I was involved in its spec review at https://review.openstack.org/#
> /c/574477/; but it has not been updated for a while.
>
>
>
> Thanks,
>
> Forrest
>
__
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] [Neutron][PTL][Election] PTL candidacy for the Stein cycle

[Miguel Lavalle]

Hello OpenStackers,

I write this to submit my candidacy for Neutron PTL during the Stein cycle.
Being PTL of this project during the Queens and Rocky cycles has been the
highest honor of my career and I want to have another shot at the very
rewarding job of helping the community to deliver better networking
functionality in OpenStack.

We had a successful Rocky cycle, delivering on most of the goals we set for
ourselves in Dublin:

* Port forwardings for floating IPs was a feature under planning for several
  cycles. In Rocky we rolled up our sleeves and implemented it.
* We made the behavior of our API more consistent by properly handling
filters
  in requests.
* We had an excellent cross project experience with Nova, implementing
  multiple port bindings to better support live instances migration.
* We made great progress moving generic DB functionality to neutron-lib and
  consuming it from Neutron and the Stadium projects.
* We extended the logging API to support FWaaS v2.0.

Moving forward, these are some of the goals that I propose for the team
during
the Stein cycle:

* Conclude the implementation of bandwidth based scheduling, that will
enable
  Neutron and Nova to guarantee network bandwidth to instances based on QoS
  policies.
* Implement DVR-aware announcement of fixed IPs in neutron-dynamic-routing.
* Continue extending Neutron QoS to support L3 router gateway IPs and VPN
  services.
* Conclude specifying and implement port mirroring for SR-IOV VF to VF
  mirroring.
* Extend the logging API to support SNAT.
* Improve the performance of port creation in bulk.
* Neutron makes extensive use of the Ryu library, which will not be
supported
  by its implementor anymore. As decided in Vancouver, we will fork it and
  continue supporting it in the OpenStack community.
* We will continue our efforts of de-coupling common functionality from the
  Neutron repository and moving it to neutron-lib.
* With the recent departure of some of our contributors, we need to
strengthen
  our team of core reviewers. I have recently been working with some of our
  team members towards this goal and will propose nominations in the
up-coming
  cycle.

Thank you for your consideration and for taking the time to read this

Miguel Lavalle (mlavalle)
~
__
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] [neutron] Neutron L3 sub-team meeting canceled on July 26th

[Miguel Lavalle]

Dear Neutron Team,

Tomorrow's L3 sub team meeting will be canceled. We will resume next week,
on August 2nd, at 1500 UTC as normal

Best regards

Miguel
__
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] [neutron] Canceling Neutron drivers meeting on June 29th

[Miguel Lavalle]

Dear Neutron Team,

This week we don't have RFEs in the triaged stage to be discussed during
our weekly drivers meeting. As a consequence, I am canceling the meeting on
June 29th at 1400UTC.

We have new RFEs and RFEs in the confirmed stage. I encourage the team to
look and them, add your opinion and help to move them to the triaged stage


Best regards

Miguel
__
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] [neutron] neutron-lib consumption patches for the Neutron Stadium and networking projects

[Miguel Lavalle]

Dear Neutron Community,

As we are all aware, over the past few cycles we have been re-homing from
Neutron to neutron-lib all the common functionality that is shared with the
OpenStack Networking family of projects. In a nutshell, the process is the
following:

   1. Shared functionality is identified in the Neutron code-base and it is
   re-homed in neutron-lib
   2. Patches are submitted to the OpenStack Networking projects with
   stable branches, to consume the newly re-homed functionality from
   neutron-lib. It is important to mention here that all that is required from
   these projects is to review and merge the patches. Boden Russel takes care
   of creating, submitting and amending these patches until they merge
   3. Once all the stable branches projects merge the corresponding
   consumption patch, the shared functionality is removed from Neutron

Lately, we have found that some projects are not merging consumption
patches, either for lack of review and / or gate issues. This prevents the
team from being able to remove re-homed functionality from Neutron. To be
able to continue making progress in the neutron-lib effort, going forward
we are going to adopt the following policy:

   1. Projects will have two weeks to review and merge neutron-lib
   consumption patches
   2. Boden will stop submitting consumption patches that fail the previous
   point. The corresponding functionality will be removed from Neutron. At
   that point, it will be the responsibility of the project in question to
   catch up with the consumption of functionality from neutron-lib

Thanks for your cooperation

Best regards

Miguel
__
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] [neutron] Ports port_binding attribute is changing to an iterable

[Miguel Lavalle]

Dear OpenStack Networking community of projects,

As part of the implementation of multiple port bindings in the Neutron
reference implementation (
https://specs.openstack.org/openstack/neutron-specs/specs/backlog/pike/portbinding_information_for_nova.html),
the port_binding relationship in the Port DB model is changing to be an
iterable:

https://review.openstack.org/#/c/414251/66/neutron/plugins/ml2/models.py@64

and its name is being changed to port_bindings:

https://review.openstack.org/#/c/571041/4/neutron/plugins/ml2/models.py@61

Corresponding changes are being made to the Port Oslo Versioned Object:

https://review.openstack.org/#/c/414251/66/neutron/objects/ports.py@285
https://review.openstack.org/#/c/571041/4/neutron/objects/ports.py@285

I did my best to find usages of these attributes in the Neutron Stadium
projects and only found them in networking-odl:
https://review.openstack.org/#/c/572212/2/networking_odl/ml2/mech_driver.py.
These are the other projects that I checked:

   - networking-midonet
   - networking-ovn
   - networking-bagpipe
   - networking-bgpvpn
   - neutron-dynamic-routing
   - neutron-fwaas
   - neutron-vpnaas
   - networking-sfc

I STRONGLY ENCOURAGE these projects teams to double check and see if you
might be affected. I also encourage projects in the broader OpenStack
Networking community of projects to check for possible impacts. We will be
holding these two patches until June 14th before merging them.

If you need help dealing with the change, please ping me in the Neutron
channel

Best regards

Miguel
__
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] [DragonFlow][TC] State of the DragonFlow project

[Miguel Lavalle]

There was an project update presentation in Vancouver:
https://www.openstack.org/videos/vancouver-2018/dragonflow-project-update-2

On Fri, Jun 1, 2018 at 11:31 AM, Sean McGinnis 
wrote:

> Hello DragonFlow team,
>
> As part of reviewing release activities it was noticed that there was
> never a
> final Queens release for DragonFlow and there was never a stable/queens
> branch
> created.
>
> It appears there is still activity with this project [1], so I am
> wondering if
> we could get an update on the status of the DragonFlow.
>
> DragonFlow is under the "independent" release model, so it does not need to
> have regular cycle milestone releases [2], but we just want to make sure
> the
> project should continue under OpenStack governance and that we are not just
> missing communication on release needs.
>
> Thanks!
> Sean
>
> [1] https://github.com/openstack/dragonflow/compare/stable/pike...master
> [2] http://git.openstack.org/cgit/openstack/releases/tree/
> deliverables/_independent/dragonflow.yaml
>
> __
> 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] [neutron] Team dinner in Vancouver, Tuesday 22nd 7pm

[Miguel Lavalle]

Hi Dear Neutron Team,

Our team dinner will take place at Al Porto Ristorante, which is located
half a mile from the Summit venue:

321 Water St, Vancouver, BC V6B 1B8
Phone: +1 604-683-8376
http://www.alporto.ca
https://goo.gl/8q5Qy2

Our reservation is at 7pm, under mi name: "Miguel Lavalle"

Looking forward to see you all there!

Best regards

MIguel
__
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] [neutron] Neutron L3 sub-team meeting canceled on May 24th

[Miguel Lavalle]

Hi Dear Neutron Team,

Due to the OpenStack Summit in Vancouver next week, we will cancel the
drivers meeting scheduled on May 24th at 1500UTC. We will resume our
meetings on May 31st at 1500UTC

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

[openstack-dev] [neutron] Neutron drivers meeting canceled on May 25th

[Miguel Lavalle]

Hi Dear Neutron Team,

Due to the OpenStack Summit in Vancouver next week, we will cancel the
drivers meeting scheduled on May 25th at 1400UTC. We will resume our
meetings on June 1st at 1400UTC

Best regards

Miguel
__
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] [neutron] Neutron weekly meeting canceled on May 22nd

[Miguel Lavalle]

Hi Dear Neutron Team,

Due to the OpenStack Summit in Vancouver next week, we will cancel the team
meeting scheduled on May 22nd at 1400UTC. We will resume our meetings on
May 28th at 2100UTC

Best regards

Miguel
__
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] [neutron] [fwaas] Proposal for the evolution of the FWaaS API

[Miguel Lavalle]

Hi,

As discussed during the weekly FWaaS IRC meeting, there is a new proposal
for the evolution of the FWaaS API here:
https://docs.google.com/document/d/1lnzV6pv841pX43sM76gF3aZ7jceRH3FPbKaGpPumWgs/edit

This proposal is based on the current FWaaS V2.0 API as documented here:
https://specs.openstack.org/openstack/neutron-specs/specs/mitaka/fwaas-api-2.0.html.
The key additional features proposed are:

   1. Firewall groups not only associate with ports but also with subnets,
   other firewall groups and dynamic rules. A list of excluded ports can be
   specified
   2. Dynamic rules make possible the association with Nova instances by
   security tags and VM names
   3. Source and destination address groups can be lists
   4. A re-direct action in firewall rules
   5. Priority attribute in firewall policies
   6. A default rule resource

The agreement in the meeting was for the team to help identify the areas
where there is incremental features in the proposal compared to what is
currently in place plus the what is being already planned for
implementation. A spec will be developed based on that increment. We will
meet in Vancouver to continue the conversation face to face

Best regards

Miguel
__
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] [neutron] Bugs deputy duty calendar

[Miguel Lavalle]

Dear Neutrinos,

I just rolled over the bugs deputy duty calendar. Please take a look and
take note of your next duty week:
https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy

Best regards

Miguel
__
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] [openstack-infra] How to take over a project?

[Miguel Lavalle]

Hi,

Ihar raises a valid issue. In the spirit of preventing this request from
falling through the cracks, I reached out to Clark Boylan in the infra IRC
channel (
http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2018-04-25.log.html#t2018-04-25T15:46:41).
We decided to contact Vikram directly in the email account he has
registered in Gerrit. I just sent him a message, copying Clark and Sangho.
If he responds, Sangho can coordinate with him. If he doesn't after a week
or two, then we can switch to Sangho, who is a member of the ONOS core team.

Regards

Miguel

On Wed, Apr 25, 2018 at 9:46 AM, Ihar Hrachyshka 
wrote:

> ONOS is not part of Neutron and hence Neutron Release team should not
> be involved in its matters. If gerrit ACLs say otherwise, you should
> fix the ACLs.
>
> Ihar
>
> On Tue, Apr 24, 2018 at 1:22 AM, Sangho Shin 
> wrote:
> > Dear Neutron-Release team members,
> >
> > Can any of you handle the issue below?
> >
> > Thank you so much for your help in advance.
> >
> > Sangho
> >
> >
> >> On 20 Apr 2018, at 10:01 AM, Sangho Shin 
> wrote:
> >>
> >> Dear Neutron-Release team,
> >>
> >> I wonder if any of you can add me to the network-onos-release member.
> >> It seems that Vikram is busy. :-)
> >>
> >> Thank you,
> >>
> >> Sangho
> >>
> >>
> >>
> >>> On 19 Apr 2018, at 9:18 AM, Sangho Shin 
> wrote:
> >>>
> >>> Ian,
> >>>
> >>> Thank you so much for your help.
> >>> I have requested Vikram to add me to the release team.
> >>> He should be able to help me. :-)
> >>>
> >>> Sangho
> >>>
> >>>
>  On 19 Apr 2018, at 8:36 AM, Ian Wienand  wrote:
> 
>  On 04/19/2018 01:19 AM, Ian Y. Choi wrote:
> > By the way, since the networking-onos-release group has no neutron
> > release team group, I think infra team can help to include neutron
> > release team and neutron release team can help to create branches
> > for the repo if there is no reponse from current
> > networking-onos-release group member.
> 
>  This seems sane and I've added neutron-release to
>  networking-onos-release.
> 
>  I'm hesitant to give advice on branching within a project like neutron
>  as I'm sure there's stuff I'm not aware of; but members of the
>  neutron-release team should be able to get you going.
> 
>  Thanks,
> 
>  -i
> >>>
> >>
> >
>
> __
> 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] [neutron] [release]

[Miguel Lavalle]

Hi everybody,

This message is to announce that effective now Akihiro Amotoki has accepted
to be the new Neutron liaison with the Release team. As such, Akihiro will
be responsible for coordinating the releases of Neutron project and the
Neutron Stadium projects, starting with the upcoming Rocky-1 release

I also want to take this opportunity to thank Armando Migliaccio for the
support he has provided over the past few cycles releasing Neutron to the
community. This is only a tiny fraction of the many great contributions
that Armando has made to OpenStack over many years. Thank you and good luck!


Best regards

Miguel
__
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] Adding Brian Haley to the Neutron Drivers team

[Miguel Lavalle]

Hi Neutrinos,

As we all know, the Neutron Drivers team plays a crucial role in helping
the community to evolve the OpenStack Networking architecture to meet the
needs of our current and future users [1]. To strengthen this team, I have
decided to add Brian Haley to it. Brian has two decades of experience in
open source networking technology. He joined the OpenStack community
contributing code to nova-network in the Diablo release. His first Neutron
commit (known as Quantum at the time) dates back to March of 2013 [2].
Since then, his many contributions include the implementation and evolution
of our L3 and DVR code. He is one of our most active core reviewers and a
prolific contributor of code to our reference implementation. I am very
confident that Brian will be a continuous source of knowledge, experience
and valuable insight to the Drivers team.

Best regards

Miguel


[1]
https://docs.openstack.org/neutron/pike/contributor/policies/neutron-teams.html#drivers-team
[2] https://review.openstack.org/#/c/25564/
__
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][stable] New release for Pike is overdue

[Miguel Lavalle]

I just +1ed Kuba's patch

On Thu, Mar 15, 2018 at 10:49 AM, Jakub Libosvar 
wrote:

> Thanks for notice. I sent a patch to request a new release:
> https://review.openstack.org/#/c/553447/
>
> Jakub
>
> On 15/03/2018 11:28, Jens Harbott wrote:
> > The last neutron release for Pike has been made in November, a lot of
> > bug fixes have made it into the stable/pike branch, can we please get
> > a fresh release for it soon?
> >
> > 
> __
> > 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] [Neutron] Queens retrospective

[Miguel Lavalle]

Hi Neutrinos and broader OpenStack community,

I have started an etherpad to collect your thoughts on the retrospective
for the Queens cycle:
https://etherpad.openstack.org/p/neutron-queens-retrospective. Everyone is
welcome to provide feedback so we can improve our contribution to the
community in the future. The retrospective session is scheduled for
Wednesday 28th from 9 to 10

Looking forward to see you all in Dublin

Safe travels

Miguel
__
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] [Neutron] Weekly IRC meeting canceled on February 27th

[Miguel Lavalle]

Dear Neutrinos,

Due to the PTG in Dublin, we will cancel our weekly meeting on Tuesday
February 27th. We will resume them normally on March 5th 2100 UTC

Safe travels

Miguel
__
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] [Neutron][Drivers] Weekly IRC meeting cancelled on February 22nd and March 2nd

[Miguel Lavalle]

Dear Neutron Drivers,

Due to the PTG next week and the involved traveling to get to Dublin, we
will cancel our weekly meetings on February 22nd and March 2nd. We will
resume our meetings normally on March 8th at 2200UTC.

Safe travels

Miguel
__
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] [Neutron][L3-subteam] Weekly IRC meeting cancelled on February 22nd and March 1st

[Miguel Lavalle]

Dear L3 sub-team members,

Due to the PTG next week and the involved traveling to get to Dublin, we
will cancel our weekly meetings on February 22nd and March 1st. We will
resume our meetings normally on March 8th at 1500UTC.

Safe travels

Miguel
__
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] [neutron] Bug Deputy Report - resend

[Miguel Lavalle]

There is one critical bug from this week:
https://bugs.launchpad.net/neutron/+bug/1749667 - neutron doesn't correctly
handle unknown protocols and should whitelist known and handled protocols
There is a fix in progress for this already, thanks Brian for picking this
up.

There are three bugs that still need further attention:

https://bugs.launchpad.net/neutron/+bug/1748658 - Restarting Neutron
containers which make use of network namespaces doesn't work
This has a fix for the tripleo side but I believe it still needs attention
from neutron

https://bugs.launchpad.net/neutron/+bug/1749425 - Neutron integrated with
OpenVSwitch drops packets and fails to plug/unplug interfaces from OVS on
router interfaces at scale
There is some discussion in the comments of this bug in regard to easing
reproduction, should help confirmation when as that effort continues.

https://bugs.launchpad.net/neutron/+bug/1749982 - After l3-agent-router-add
inactive router gets all traffic
I didn't get much time with this one but couldn't manage to reproduce it.
However I'm not too familiar with this area, so I'm hoping someone else can
give a more definitive answer.

There is also one bug marked as incomplete:
https://bugs.launchpad.net/neutron/+bug/1748894 - intermittent dhcp failures
This could use some eyes as well to get confirmed.

Thanks everyone,
 - James Anziano
__
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] [PTL][SIG][PTG]Team Photos

[Miguel Lavalle]

Kendall,

I updated the Neutron team slot to 12:20 - 12:30 on Thursday? Hope that is
ok

Thanks

On Thu, Feb 15, 2018 at 3:56 PM, Kendall Nelson 
wrote:

> Updates!
>
> So, we have gotten permission to do photos down on the pitch at the
> stadium which is awesome!
>
> The only issue is that we need to condense into a more dense blocks
> (Tuesday afternoon or Thursday morning) so looking at the schedule we have
> to move some teams. If the following teams could move their times so that
> we can make this happen:
>
>- QA
>- SIG K8s
>- Cyborg
>- Neutron
>- Octavia
>- Requirements
>- Release Mgmt
>- OpenStack Ansible
>- Cinder
>
> I'm really sorry to make you guys move, but since we need to pay for an
> escort (with a 4 hour minimum) and don't want to conflict with lunch, we
> need to shift.
>
> We will have your team meet at registration at your selected time. Because
> we get to go on the pitch and this requires an escort, you NEED TO BE AT
> REG ON TIME OR EARLY. If you aren't, you will miss your chance to be in the
> photo.
>
> I will send out a reminder on Monday of PTG week.
>
> -Kendall (diablo_rojo)
>
> On Thu, Feb 8, 2018 at 10:21 AM Kendall Nelson 
> wrote:
>
>> This link might work better for everyone:
>> https://docs.google.com/spreadsheets/d/1J2MRdVQzSyakz9HgTHfwYPe49PaoT
>> ypX66eNURsopQY/edit?usp=sharing
>>
>> -Kendall (diablo_rojo)
>>
>>
>> On Wed, Feb 7, 2018 at 9:15 PM Kendall Nelson 
>> wrote:
>>
>>> Hello PTLs and SIG Chairs!
>>>
>>> So here's the deal, we have 50 spots that are first come, first
>>> served. We have slots available before and after lunch both Tuesday and
>>> Thursday.
>>>
>>> The google sheet here[1] should be set up so you have access to edit,
>>> but if you can't for some reason just reply directly to me and I can add
>>> your team to the list (I need team/sig name and contact email).
>>>
>>> I will be locking the google sheet on *Monday February 26th so I need
>>> to know if your team is interested by then. *
>>>
>>> See you soon!
>>>
>>> - Kendall Nelson (diablo_rojo)
>>>
>>> [1] https://docs.google.com/spreadsheets/d/
>>> 1J2MRdVQzSyakz9HgTHfwYPe49PaoTypX66eNURsopQY/edit?usp=sharing
>>>
>>>
>>>
>>>
> __
> 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] [neutron] Rocky PTG team dinner

[Miguel Lavalle]

Dear Neutrinos,

We will have our traditional PTG team dinner on Thursday March 1st at 7pm.
The place is to be defined. In the meantime, if you will attend the PTG,
please put your name in the "Attendees" section at to the top of the
etherpad (https://etherpad.openstack.org/p/neutron-ptg-rocky) with the
following information:

name - (irc nickname) - days in Dublin - Yes / No attending team dinner

Looking forward to see you in Dublin!

Cheers

Miguel
__
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] Lunchtime during PTG

[Miguel Lavalle]

Hi,

In order to schedule team sessions during the PTG I would like to know the
time lunch is going to be served. It is not in the schedule:
https://www.openstack.org/ptg/#tab_schedule

Cheers

Miguel
__
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] [PTL][SIG][PTG]Team Photos

[Miguel Lavalle]

Hi Kendall,

Can you add Neutron on Thursday at 2pm. If that is not available, then
anytime Wednesday or Thursday. I am the contact: mig...@mlavalle.com

Thanks

On Wed, Feb 7, 2018 at 11:15 PM, Kendall Nelson 
wrote:

> Hello PTLs and SIG Chairs!
>
> So here's the deal, we have 50 spots that are first come, first served. We
> have slots available before and after lunch both Tuesday and Thursday.
>
> The google sheet here[1] should be set up so you have access to edit, but
> if you can't for some reason just reply directly to me and I can add your
> team to the list (I need team/sig name and contact email).
>
> I will be locking the google sheet on *Monday February 26th so I need to
> know if your team is interested by then. *
>
> See you soon!
>
> - Kendall Nelson (diablo_rojo)
>
> [1] https://docs.google.com/spreadsheets/d/1J2MRdVQzSyakz9HgTHfwYPe49PaoT
> ypX66eNURsopQY/edit?usp=sharing
>
>
>
>
> __
> 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] [neutron] PTL candidacy for Rocky

[Miguel Lavalle]

Hello OpenStack Community,

I write this to submit my candidacy for the Neutron PTL position during the
Rocky cycle. I had the privilege of being the project's PTL for most of the
Queens release series and want to have another opportunity helping the team
and the community to deliver more and better networking  functionality.

I have worked for the technology industry 37+ years. After many years in
management, I decided to return to the "Light Side of the Force", the
technical path, and during the San Diego Summit in 2012 told the Neutron
(Quantum at the time) PTL that one day I wanted to be a member of the core
team. He and the team welcomed me and that started the best period of my
career, not only for the never ending learning experiences, but more
importantly, for the many talented women and men that I have met along the
way. Over these past few years I worked for Rackspace, helping them to
deploy and operate Neutron in their public cloud, IBM in their Linux
Technology Center, and currently for Huawei, as their Neutron upstream
development lead.

During the Queens release the team made significant progress in the
following fronts:

   - Continued with the adoption of Oslo Versioned Objects in the DB layer
   - Implemented QoS rate limits for floating IPs
   - Delivered the FWaaS V2.0 API
   - Concluded the implementation of the logging API for security groups,
   which implements a way to capture and store events related to security
   groups.
   - Continued moving externally referenced items to neutron-lib and
   adopting them in Neutron and the Stadium projects
   - Welcomed VPNaaS back into the Stadium after the team put it back in
   shape
   - Improved team processes such as having a pre-defined weekly schedule
   for team members to act as bug triagers, gave W+ to additional core members
   in neutron-lib and re-scheduled the Neutron drivers meeting on alternate
   days and hours to enable attendance of more people across different time
   zones

Some of the goals that I propose for the team to pursue during the Rocky
cycle are:

   - Finish the implementation of multiple port binding to solve the
   migration between VIF types in a generic way so operators can switch easily
   between backends. This is a joint effort with the Nova team
   - Implement QoS minimum bandwidth allocation in the Placement API to
   support scheduling of instances based on the network bandwidth available in
   hosts. This is another joint effort with the Nova team
   - Synchronize the adoption of the DB layer engine facade with the
   adoption of Oslo Versioned Objects to avoid situations where they don't
   cooperate nicely
   - Implement port forwarding based on floating IPs
   - Continue moving externally referenced items to neutron-lib and
   adopting them in Neutron and the Stadium projects. Finish documenting
   extensions in the API reference. Start the move of generic DB functionality
   to the library
   - Expand the work done with the logging API in security groups to FWaaS
   v2.0
   - Continue efforts in expanding our team and making its work easier.
   While we had some success during Queens, this is an area where we need to
   maintain our focus

Thank you for your consideration and for taking the time to read this

Miguel Lavalle (mlavalle)
__
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][neutron-fwaas] Request for inclusion of bug fixes in RC

[Miguel Lavalle]

Hi,

It was granted earlier today during the Neutron drivers meeting

Cheers

On Fri, Feb 2, 2018 at 12:22 AM, Sridar Kandaswamy (skandasw) <
skand...@cisco.com> wrote:

> Thanks An. The team has been working with An to review and validate these
> changes – we believe we are close to the final version and should be able
> to merge by tomorrow barring any unforeseen surprises. So pls consider
> adding these to the RC as they address some critical issues as outlined
> below.
>
> Thanks
>
> Sridar
>
> On 2/1/18, 10:12 PM, "a...@vn.fujitsu.com"  wrote:
>
> Hi,
>
> I would like to request inclusion of the following patches which
> address bugs found in our testing.
>
> https://review.openstack.org/#/c/539461/
> Addressing: https://bugs.launchpad.net/neutron/+bug/1746404
>
> 'auto_associate_default_firewall_group' got an error when new port is
> created
> We started with a CfgOpt to Disable default FWG on ports. This has
> caused issues with Conntrack so this option is being removed. Also on a
> related note, we were mistakenly applying on other ports - so tightened up
> the validation to ensure that it is a VM port.
>
> And
> https://review.openstack.org/#/c/536234/
> Addressing: https://bugs.launchpad.net/neutron/+bug/1746855
>
> FWaaS V2 failures with Ml2 is Linuxbridge or security group driver is
> iptables_hybrid
> We have failures with Linuxbridge as it is not a supported option and
> if SG uses iptables_hybrid driver - we have seen issues which possibly
> might be addressed [1], but with not enough validation we would like to
> prevent this scenario as well. With more testing and addressing any issues
> we can remove the restriction on SG with iptables_hybrid driver in the R
> release.
>
> [1] https://review.openstack.org/#/c/538154/
>
> Cheers,
> An
>
> 
> __
> 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] [Neutron] q-3 tag and FFE being tracked

[Miguel Lavalle]

This is the patch for VPNaaS:

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

On Fri, Jan 26, 2018 at 1:39 PM, Miguel Lavalle <mig...@mlavalle.com> wrote:

> Hi Neutron Team,
>
> This is our Queens 3 milestone patch:
>
> https://review.openstack.org/#/c/537651/.
>
> Please note that we still have to create a tag for VPNaaS, which recently
> rejoined the Neutron Stadium
>
> We have also created a list that we are targeting for RC1:
>
> https://launchpad.net/neutron/+milestone/queens-rc1
>
> We are going to block master branch to everything that is not in that
> list. If we have left out anything that is critical to land in Queens,
> please reach out to me
>
>
> Cheers
>
> Miguel
>
__
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] [Neutron] q-3 tag and FFE being tracked

[Miguel Lavalle]

Hi Neutron Team,

This is our Queens 3 milestone patch:

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

Please note that we still have to create a tag for VPNaaS, which recently
rejoined the Neutron Stadium

We have also created a list that we are targeting for RC1:

https://launchpad.net/neutron/+milestone/queens-rc1

We are going to block master branch to everything that is not in that list.
If we have left out anything that is critical to land in Queens, please
reach out to me


Cheers

Miguel
__
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][l3][flavors][floatingip] FFE request for patch no 523257 and 532993

[Miguel Lavalle]

Manjeets,

This FFE has been approved. Tracking it here:
https://launchpad.net/neutron/+milestone/queens-rc1

Cheers

On Thu, Jan 25, 2018 at 12:17 PM, Bhatia, Manjeet S <
manjeet.s.bha...@intel.com> wrote:

> Hello all !
>
>
>
> I’d like to request a FFE for patch 523257 [1] that adds new resources and
> events to handle operations
>
> For routers if L3 flavors framework is used. The neutron-lib part is
> already merged [lib] thanks to Boden and
>
> Miguel for quick reviews on that. The second patch 53993 [2] adds the
> missing notifications for floatingip update
>
> and delete events without which l3 flavor drivers Backends isn’t able to
> perform the update and delete operations
>
> on floatingip’s correctly. These two patches are needed for L3 flavors
> driver in networking-odl [nodll3].
>
>
>
>
>
> [1]. https://review.openstack.org/#/c/523257
>
> [2]. https://review.openstack.org/#/c/532993
>
>
>
> [lib] https://review.openstack.org/#/c/535512/
>
> [nodll3] https://review.openstack.org/#/c/504182/
>
>
>
>
>
> Sorry for 2nd email on this I forgot to add [openstack-dev] subject in
> last one.
>
>
>
>
>
> Thanks and regards !
>
> Manjeet Singh Bhatia
>
>
>
> __
> 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] [neutron] Rocky PTG planning

[Miguel Lavalle]

Hi,

I have started an etherpad (
https://etherpad.openstack.org/p/neutron-ptg-rocky) to start planning the
topics we are going to discuss in the Neutron sessions during the Rocky PTG
in Dublin. At this point in time, it is entirely free form. Just make sure
you put your name and / or IRC nickname next to the topics you add

See you in Dublin!
__
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] [Neutron] Bug deputy report

[Miguel Lavalle]

   - https://bugs.launchpad.net/neutron/+bug/1741954:
   create_and_list_trunk_subports rally scenario failed with timeouts. Armando
   Migliaccio assigned to it
   - CRITICAL: https://bugs.launchpad.net/neutron/+bug/1741889 functional:
   DbAddCommand sometimes times out after 10 seconds. This is causing repeated
   failures of the functional tests jobs.
   - https://bugs.launchpad.net/neutron/+bug/1741411: Centralized floating
   ip Error status. Needs environment to be reproduced. Will ask Swami for
   input
   - https://bugs.launchpad.net/neutron/+bug/1741407: L3 HA: 2 masters
   after restart of l3 agent. Needs environment to be reproduced. Will ask
   Swami for input
   - https://bugs.launchpad.net/neutron/+bug/1741079: Deleting heat stack
   doesn't delete dns records. Seems to be a problem in Heat. Gathering data
   from submitter
   - https://bugs.launchpad.net/neutron/+bug/1740885: Security group
   updates fail when port hasn't been initialized yet. Jakub Libosvar assigned
   on it
__
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] Tempest plugin for Neutron Stadium projects

[Miguel Lavalle]

Hi Neutron community,

During the last Neutron drivers meeting, we discussed whether all the
Neutron Stadium projects should have their Tempest code in
https://github.com/openstack/neutron-tempest-plugin/. It was decided to
allow Stadium projects to get their tests in the consolidated plugin but it
will not be a requirement. The assumption is that many projects might be
stretched in resources and we don't want to create more work for them.

Best regards

Miguel
__
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] Fwd: bug deputy report

[Miguel Lavalle]

-- Forwarded message --
From: Takashi Yamamoto <yamam...@midokura.com>
Date: Tue, Jan 2, 2018 at 7:45 AM
Subject: bug deputy report
To: Miguel Lavalle <mig...@mlavalle.com>


Hi,

I was a bug deputy but I don't think I can attend today's meeting.
(I'm not feeling well today.)
The week was quiet. I guess it's the most quiet week in a year.
There were nothing critical or urgent.

bug 1740068
lost composite primary key in firewall_group_port_associations_v2
A fix is available, it's unclear why migration tests couldn't catch this.

bug 1740198
DHCP was enabled successfully when IP pool is exhausted
seems like an old issue.
Miguel, can you take a look?

bug 1740450
Restarting l3 agent results in lost of centralized fip in snat ns
the report seems valid and even has a suggested fix.
asked bhaley to triage.
__
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] [Neutron] Weekly IRC meeting cancelled on December 25th

[Miguel Lavalle]

Hi Neutron Team,

We will cancel the weekly IRC meeting on Monday December 25th. We will
resume on Tuesday January 2nd at 1400UTC

Best regards

Miguel
__
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] Stepping down from core

[Miguel Lavalle]

Hi Armando,

I can only echo here the sadness I expressed to you last week during our
one on one conversation. This decision shows, like in many occasions in the
past, that above all, you are a man a deep principles. As I said, I admire
you for that. You have made invaluable contributions to OpenStack in
general and Neutron in particular. We thank you for that. On a personal
note, I will always be grateful for all the mentoring  and patience that
you have provided me for a long time.

What encourages me is your commitment to continue being a member of the
Neutron team. We need your knowledge, wisdom and guidance and we will
actively seek it. I am looking forward to it!

Un Abbraccio

Miguel


On Mon, Dec 18, 2017 at 7:32 AM, Sławomir Kapłoński 
wrote:

> Hi Armando,
>
> It's very sad to hear that.
> Thanks for all Your work for Neutron community as well as for all Your
> help for other contributors.
> Good luck!
>
> —
> Best regards
> Slawek Kaplonski
> sla...@kaplonski.pl
>
>
>
> > Wiadomość napisana przez Armando M.  w dniu
> 15.12.2017, o godz. 20:01:
> >
> > Hi neutrinos,
> >
> > To some of you this email may not come as a surprise.
> >
> > During the past few months my upstream community engagements have been
> more and more sporadic. While I tried hard to stay committed and fulfill my
> core responsibilities I feel like I failed to retain the level of quality
> and consistency that I would have liked ever since I stepped down from
> being the Neutron PTL back at the end of Ocata.
> >
> > I stated many times when talking to other core developers that being
> core is a duty rather than a privilege, and I personally feel like it's way
> overdue for me to recognize on the mailing list that it's the time that I
> state officially my intention to step down due to other commitments.
> >
> > This does not mean that I will disappear tomorrow. I'll continue to be
> on neutron IRC channels, support the neutron team, being the release
> liasion for Queens, participate at meetings, and be open to providing
> feedback to anyone who thinks my opinion is still valuable, especially when
> dealing with the neutron quirks for which I might be (git) blamed :)
> >
> > Cheers,
> > Armando
> >
> > 
> __
> > 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] [Neutron] Shifting the bug deputy schedule

[Miguel Lavalle]

Dear Neutrinos,

Recently two members of the team have been re-assigned by their companies
to other duties. As a consequence, we need to adjust our bugs deputy
schedule and your duty slot will be one week sooner than originally
expected. Please take some time to check the revised schedule here:
https://wiki.openstack.org/wiki/Network/Meetings

Best regards

Miguel
__
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] Propose Slawek Kaplonski for Neutron core

[Miguel Lavalle]

Hi Neutron Team,

It has been a week since Slawek's nomination to Neutron core went out. We
have received great positive feedback from the team and community members
at large. As a consequence, I want to welcome Slawek to the core team and
congratulate him on his hard work and many contributions to OpenStack
Networking. Keep it up!

Cheers

Miguel

On Mon, Dec 4, 2017 at 7:06 AM, Anna Taraday <akamyshnik...@mirantis.com>
wrote:

> +1 !
> Well deserved!
>
> On Sun, Dec 3, 2017 at 1:03 PM Gary Kotton <gkot...@vmware.com> wrote:
>
>> +1
>>
>>
>>
>> Welcome to the team!
>>
>>
>>
>> *From: *Miguel Lavalle <mig...@mlavalle.com>
>> *Reply-To: *OpenStack List <openstack-dev@lists.openstack.org>
>> *Date: *Wednesday, November 29, 2017 at 9:21 PM
>> *To: *OpenStack List <openstack-dev@lists.openstack.org>
>> *Subject: *[openstack-dev] [Neutron] Propose Slawek Kaplonski for
>> Neutron core
>>
>>
>>
>> Hi Neutron Team,
>>
>>
>>
>> I want to nominate Slawek Kaplonski (irc: slaweq) to Neutron core. Slawek
>> has been an active contributor to the project since the Mitaka cycle. He
>> has been instrumental in the development of the QoS capabilities in
>> Neutron, becoming the lead of the sub-team focused on that set of features.
>> More recently, he has collaborated in the implementation of OVO and is an
>> active participant in the CI sub-team. His number of code reviews during
>> the Queens cycle is on par with the leading core members of the team:
>> http://stackalytics.com/?module=neutron
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__stackalytics.com_-3Fmodule-3Dneutron=DwMFaQ=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=rEa-GCl_LWhEhOkR8gdNbWxIgwkU2lYb_8q2uuJTZeI=T9RadwyQl5YZYxztabqaw8koYKvSDE6H2qPnyHWoKAA=>
>>
>>
>>
>> In my opinion, his efforts are highly valuable to the team and we will be
>> very lucky to have him as a fully voting core.
>>
>>
>>
>> I will keep this nomination open for a week as customary,
>>
>>
>>
>> Thank you,
>>
>>
>>
>> Miguel
>> 
>> __
>> 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,
> Ann Taraday
>
> __
> 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] [Neutron] Propose Slawek Kaplonski for Neutron core

[Miguel Lavalle]

Hi Neutron Team,

I want to nominate Slawek Kaplonski (irc: slaweq) to Neutron core. Slawek
has been an active contributor to the project since the Mitaka cycle. He
has been instrumental in the development of the QoS capabilities in
Neutron, becoming the lead of the sub-team focused on that set of features.
More recently, he has collaborated in the implementation of OVO and is an
active participant in the CI sub-team. His number of code reviews during
the Queens cycle is on par with the leading core members of the team:
http://stackalytics.com/?module=neutron

In my opinion, his efforts are highly valuable to the team and we will be
very lucky to have him as a fully voting core.

I will keep this nomination open for a week as customary,

Thank you,

Miguel
__
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] [Neutron][Drivers-team] Weekly IRC meeting cancelled on November 24th

[Miguel Lavalle]

Dear Neutron team,

Due to the Thanksgiving Holiday in the US, we will cancel our weekly
meeting on November 24th. We will resume normally on the 30th

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

[openstack-dev] [Neutron][L3-subteam] Weekly IRC meeting cancelled on November 23rd

[Miguel Lavalle]

Dear L3-subteam,

Due to the Thanksgiving Holiday in the US, we will cancel our weekly
meeting on November 23rd. We will resume normally on the 30th

Regards

Miguel
__
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] [Neut​ron][Drivers-team] Weekly IRC meeting cancelled on November 9th

[Miguel Lavalle]

Dear Neutrinos,

Due to the Summit in Sydney, we will cancel the scheduled drivers meeting
on November 10th. We will resume normally on the 16th

Cheers

Miguel
__
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] [Neut​ron][L3-subteam] Weekly IRC meeting cancelled on November 9th

[Miguel Lavalle]

Dear Neutron L3 sub-team,

Several of the team members will be attending the Summit in Sydney.
Therefore, we will cancel the weekly meeting on November 9th. We will
resume normally on the 16th.

Cheers

Miguel
__
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] [neutron] - are you attending the Sydney summit?

[Miguel Lavalle]

Hi,

If you are a Neutron developer attending the Sydney Summit, please add your
name to the following etherpad so we can plan a team social event and
easily coordinate in person meetings:

https://etherpad.openstack.org/p/neutron-sydney-summit-attendees

Safe travels and see you Down Under!

Cheers

Miguel
__
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] [Neutron][L3-subteam] Weekly IRC meeting cancelled on October 19th

[Miguel Lavalle]

Dear L3 sub-team Neutrinos,

Due to unexpected agenda conflicts of several of the team members, we will
cancel today's meeting. We will resume normally on the 26th

Regards

Miguel
__
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] [ptls] Sydney Forum Project Onboarding Rooms

[Miguel Lavalle]

Neutron - Miguel Lavalle - mig...@mlavalle.com

On Mon, Oct 16, 2017 at 9:39 PM, Jeffrey Zhang <zhang.lei@gmail.com>
wrote:

> I am the speaker. Michal couldn't be Sydney this summit.
>
> On Tue, Oct 17, 2017 at 1:05 AM, Kendall Nelson <kennelso...@gmail.com>
> wrote:
>
>> Added Kolla to my list. Would the speakers be you and Michal?
>>
>> -Kendall (diablo_rojo)
>>
>>
>> On Thu, Oct 12, 2017 at 5:51 PM Jeffrey Zhang <zhang.lei@gmail.com>
>> wrote:
>>
>>> Hi Kendall,
>>>
>>> Kolla project would like to have a on-boarding session too.
>>>
>>> thanks.
>>>
>>> On Fri, Oct 13, 2017 at 5:58 AM, Kendall Nelson <kennelso...@gmail.com>
>>> wrote:
>>>
>>>> Added Nova to my list with Dan, Melanie, and Ed as speakers.
>>>>
>>>> Thanks Matt,
>>>> -Kendall (diablo_rojo)
>>>>
>>>> On Thu, Oct 12, 2017 at 2:43 PM Matt Riedemann <mriede...@gmail.com>
>>>> wrote:
>>>>
>>>>> On 10/9/2017 4:24 PM, Kendall Nelson wrote:
>>>>> > Wanted to keep this thread towards the top of inboxes for those I
>>>>> > haven't heard from yet.
>>>>> >
>>>>> > About a 1/4 of the way booked, so there are still slots available!
>>>>> >
>>>>> > -Kendall (diablo_rojo)
>>>>>
>>>>> I've tricked the following people into running a Nova on-boarding room:
>>>>>
>>>>> - "Super" Dan Smith <dansm...@redhat.com>
>>>>> - Melanie "Structured Settlement" Witt <melwi...@gmail.com>
>>>>> - Ed "Alternate Hosts" Leafe <e...@leafe.com>
>>>>>
>>>>> --
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Matt
>>>>>
>>>>> 
>>>>> __
>>>>> OpenStack Development Mailing List (not for usage questions)
>>>>> Unsubscribe: openstack-dev-requ...@lists.op
>>>>> enstack.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.op
>>>> enstack.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.op
>>> enstack.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:unsubscrib
>> e
>> 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

Re: [openstack-dev] [neutron] using different dns domains in neutorn networks

[Miguel Lavalle]

Hi Kim,

Thanks for trying the feature out! There are 2 levels of Neutron
integration with DNS:

   1. Integration with Neutron's own internal DNS service. In short, ports
   get a DHCP lease from a dnsmasq instance associated to their network. This
   dnsmasq instance also assigns DNS attributes to the port, which are shown
   to the user in the dns_assigment dictionary returned by the API. It
   contains a FQDN, that is the concatenation of the port's dns_name and the
   dns_domain defined in neutron.conf. The purpose of the dns_assignment
   attribute is exclusively to show to the user the DNS attributes that
   dnsmasq assigns to the port.
   2. Integration with external DNS services (OpenStack Designate being the
   reference implementation). If this integration is enabled, a port will be
   known to an external DNS service by the FQDN that results from
   concatenating its dns_name atribute and its network's dns_domain. This
   latter attribute has no influence whatsoever in the port's dns_assignment.
   In the latest release, Pike, we also added a dns_domain attribute to ports.
   But again, it only has an effect on the external DNS service, with no
   effect on dns_assigment

I hope this helps. Please feel free to ping me in #openstack-neutron. My
IRC nickname is mlavalle

Regards

Miguel

On Fri, Oct 6, 2017 at 7:50 AM, Kim-Norman Sahm 
wrote:

> I've tried to upgrade my testing environment to ocata but i have the
> same issue...
>
> does anybody has an idea?
>
> regards
> Kim
>
>
>
> Am Freitag, den 29.09.2017, 09:32 +0200 schrieb Kim-Norman Sahm:
> > Hi,
> >
> > i'm currently testing the integration of designate and i found the
> > dns integration on neutron:
> > https://docs.openstack.org/newton/networking-guide/config-dns-int.htm
> > l
> >
> > In this example the value "dns_domain = example.org." is set in the
> > neutron.conf.
> > if i create a port with the "--dns_name fancyname" it is assigned to
> > the domain example.org: fancyname.example.org.
> >
> > if i set another domain name in another network "neutron net-update
> > --dns-domain anotherdomain.org. net2" and create a port in this
> > network the dns records is still in the example.org. domain.
> > is there a way to overwrite the global dns domain in a project and
> > inherit the dns-domain to the ports in this network?
> >
> > Best regards
> > Kim
> > Kim-Norman Sahm
> > Cloud & Infrastructure(OCI)
> > noris network AG
> > Thomas-Mann-Straße 16-20
> > 90471 Nürnberg
> > Deutschland
> > Tel +49 911 9352 1433
> > Fax +49 911 9352 100
> >
> > kim-norman.s...@noris.de
> > https://www.noris.de - Mehr Leistung als Standard
> > Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel
> > Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB
> > 17689
> >
> >
> >
> >
> >  
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
> > cribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> Kim-Norman Sahm
> Cloud & Infrastructure(OCI)
> noris network AG
> Thomas-Mann-Straße 16-20
> 90471 Nürnberg
> Deutschland
> Tel +49 911 9352 1433
> Fax +49 911 9352 100
>
> kim-norman.s...@noris.de
> https://www.noris.de - Mehr Leistung als Standard
> Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel
> Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689
>
>
>
>
>
> __
> 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] [neutron] - Adding Takashi Yamamoto to the neutron-drivers team

[Miguel Lavalle]

Hi,

After the departure of Kevin Benton, I am adding Takashi Yamamoto to the
Neutron drivers team [1]. Takashi has been an active member of the Neutron
Core Reviewer team for more than 2 years, providing advice across the
reference implementation code.  He also leads the networking-midonet
sub-project team. As such, Takashi has a very good high level architectural
view of Neutron, necessary for deciding what features are feasible for the
platform. He will also provide valuable insights from the perspective of
the Neutron sub-projects.


1.
https://docs.openstack.org/neutron/latest/contributor/policies/neutron-teams.html#drivers-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

[openstack-dev] [neutron] Bugs triaging sprint

[Miguel Lavalle]

Hi Neutrinos,

I am this week's bugs deputy. In looking at the "Undecided" bugs I realized
that we have a huge number of them dating from several weeks ago. If we
want to catch up soon with this, I think we are going to need a triaging
sprint. How about next week's Wednesday, October 111th? What do folks think?

Best regards

Miguel
__
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] [neutron] Rotating bugs deputy schedule

[Miguel Lavalle]

Dear Neutrinos,

Thank you very much to all the team members who volunteered to be bug
deputy for one week. Given your excellent response, each one of us will
only have bug deputy duty once every three months and a half, as can be
seen in the scheduled rotation in our weekly meeting agenda:
https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy.

I will keep the schedule fresh every week, so everyone knows all the time
when his / her next duty week is. I also encourage other team members to
volunteer. Please feel free to add your name at the end of the rotation.

Best regards

Miguel
__
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] [neutron] Rotating bugs deputy role

[Miguel Lavalle]

Hi Neutrinos,

As discussed during the Denver PTG, we have experienced difficulty in our
IRC meetings to get volunteers for the bugs deputy role, who takes
responsibility for one week to triage bug reports (please see
https://docs.openstack.org/neutron/latest/contributor/policies/bugs.html#neutron-bug-deputy)
. As a consequence, we decided in the PTG to create a rotation roster for
this role. In other words, the people in the roster will take one week
turns playing the role of Neutron bugs deputy. The more volunteers we have,
the less frequently each one of us will be fulfilling this duty. So, please
help the Neutron community and add your name to this etherpad:
https://etherpad.openstack.org/p/neutron-rotating-bug-deputy-volunteers.
Based on the names in the etherpad, I will propose a roster over the nest
few days in the "Bugs deputy" section of the Networking meeting wiki page (
https://wiki.openstack.org/wiki/Network/Meetings)

Best regards

Miguel
__
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] Forum Reminder! Submissions due by Sept 29th

[Miguel Lavalle]

Jimmy,

Is this the link we are supposed to use: http://forumtopics.openstack.
org/cfp/create? http://odsreg.openstack.org/ returns an internal server
error

Cheers

On Mon, Sep 25, 2017 at 8:25 AM, Jimmy McArthur  wrote:

> Hello!
>
> This is a friendly reminder that all proposed Forum session leaders must
> submit their abstracts at:
>
> http://odsreg.openstack.org
>
> before 11:59PM UTC on Friday, September 29th!
>
> Cheers,
> Jimmy
>
>
>
>
> __
> 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] [neutron] Denver PTG summary

[Miguel Lavalle]

Hi All!



Following below is a high-level update of what was discussed during the
PTG. If there is something I left out, please reply to this email thread to
add it. However, if you want to continue the discussion on any of the
individual points summarized below, please start a new thread so we don’t
have a ton of discussions going on attached to this update.


You can find the etherpad we used during the PTG here:
https://etherpad.openstack.org/p/neutron-queens-ptg. You can also playback
the conversations here:


* Wednesday morning session: https://www.youtube.com/watch?v=58AyKXHkI-I

* Wednesday afternoon session: https://www.youtube.com/watch?v=LPxydx5ypAE

* Thursday morning session: https://www.youtube.com/watch?v=zSHIpkR9Jxg

* Thursday afternoon Neutron / Nova x-project session:
https://www.youtube.com/watch?v=kF5uat0MbuY

* Thursday late afternoon session: https://www.youtube.com/watch?
v=lJm8vIwxGec



Documentation

===

* The documentation team has defined a new mission for itself:
https://review.openstack.org/#/c/499556/. This means that the Neutron team
has to create and maintain its own documentation. The documentation team
will only provide tools and guidance.

* Code patchsets must include documentation from now on, when applicable.
This will be enforced by all code reviewers. As a consequence, we will not
use the DocImpact tag anymore. We are updating the contributors guide
accordingly: https://review.openstack.org/#/c/503710/

* Patches that impact the API must depend on a corresponding patch in
neutron-lib that update api-ref

* Boden has graciously accepted to be the liaison with the documentation
team: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation

* The release checklist has to be updated to include a step to insure there
are no broken links in the docs

* We need volunteers to move the archived configuration guide (
https://github.com/openstack/neutron/tree/master/doc/source/admin/archives)
into the networking guide

* Pike install guides need to be verified. We also need volunteers for this

* The stable/pike document backport policy is to backport patches as they
come, with the exception of API reference contributions, which must target
the master branch of neutron-lib



neutron-lib



* New callback payload adoption: we will treat the adoption of the new
payload style objects as we have been with other lib impact changes.

* Decoupling of DB related access for neutron-lib: recommendation was to
move OVO fields definitions to neutron-lib, instead of the currently
proposed approach (PoC https://review.openstack.org/#/c/476652) to extract
specific objects methods from the different OVOs


DevStack

=

* We have several patches that need the attention of DevStack core
reviewers: https://review.openstack.org/#/q/status:open+topi
c:new-neutron-devstack-in-gate

* Miguel Lavalle to talk to DevStack team to get them to pay attention to
these patches


Common Classification Framework

==

* The spec is: https://review.openstack.org/#/c/320439

* Making good progress towards releasing V1 during Queens

* Message sent to the distribution list requesting feedback on protocols
that should be supported: http://lists.openstack.org/pip
ermail/openstack-dev/2017-August/121531.html

* FWaaS, SFC and Dragonflow have shown interest in adopting CCF

* Adding classifying based on neutron resources is being considered. A SFC
PoC is going to be implemented



CLI related topics

=

* With OSC resource attributes extensions must be added directly/statically to
the sdk's resource and then consumed in the client, unlike the
python-neutronclient, where that doesn’t require any client-side code
changes.

* As a consequence, we will not drop support for python-neutronclient until
we achieve parity.

* Boden Russel will follow up with a message to the mailing list to request
the current status of support for attribute extensions in OSC

* Akihiro Motoki will discuss the future of LBaaS CLI with octavia team

* yushiro will discuss with the FWaaS team the future of the v1 CLI/API



Pike backlog plans

==

* Security group logging. Remaining 4 functionality patches are ready for
review and targeted to merge by Q-1:

- Logging agent extension: https://review.openstack.org/396104

- RPC stuff and driver api: https://review.openstack.org/468265

- OVS firewall logging driver: https://review.openstack.org/468281

- CLI: https://review.openstack.org/#/c/409819/

* Security group logging: testing and documentation patches are targeted to
merge in Q-2

- API and scenario test: https://review.openstack.org/#/c/482886/

- Functional test: https://review.openstack.org/#/c/418862/

- Documentation: https://review.openstack.org/#/c/480117/

* Trevor McCasland will conclude the implementation of QinQ network type
driver

* Boden Russell will re-propose network resource diagnostics for Queens:
https://review.openstack.org/#/c/308973

[openstack-dev] [neutron] This week drivers meeting

[Miguel Lavalle]

Hi Neutrinos,

We will cancel this week's drivers meeting. We will resume normally next
week, on September 28th

Best regards

Miguel
__
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] [Neutron] Weekly IRC meeting cancelled on September 18th

[Miguel Lavalle]

Dear Neutrinos,

Since this is the first day after the PTG, we are going to cancel today's
weekly IRC meeting at 2100 UTC. We will resume the weekly meetings on
Tuesday, September 26th, at 1400 UTC.

I will send a message soon with the summary of the PTG. In the meantime,
team members can watch and listen all the sessions from Wednesday and
Thursday here:

Wednesday morning: https://www.youtube.com/watch?v=lJm8vIwxGec
Wedensday afternoon: https://www.youtube.com/watch?v=LPxydx5ypAE
Thursday Morning: https://www.youtube.com/watch?v=zSHIpkR9Jxg
Neutron / Nova x-project: https://www.youtube.com/watch?v=kF5uat0MbuY
Thursday late afternoon: https://www.youtube.com/watch?v=lJm8vIwxGec

Best regards

Miguel
__
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] [Neutron] Denver PTG sessions video

[Miguel Lavalle]

Hi Neutrinos,

We are broadcasting and recording the PTG sessions in Denver. You can watch
live (with a little delay) or you can watch the recorded video at your own
convenience. I am posting the links in the etherpad, lines 62 - 68:
https://etherpad.openstack.org/p/neutron-queens-ptg

Please keep in mind that the times shown in the etherpad are in US Mountain
Daylight Time, which is UTC - 6. We will be announcing the topic we are
covering here:  http://ptg.openstack.org/ptg.html


Best regards

Miguel
__
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] [Neutron] Denver Team Dinner

[Miguel Lavalle]

Dear Neutrinos,

Our social event will take place on Thursday September 12th at 7:30pm. The
venue is going to be https://www.famousdaves.com/Denver-Stapleton. It is
located 0.4 miles from the Renaissance Hotel, which translates to an easy 9
minutes walk.

I have a reservation for a group of 30 people under my name. Please respond
to this message with your attendance confirmation by Wednesday night, so I
can get a more accurate head count.

Looking forward to see y'all Thursday night

Best regards

Miguel
__
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] [Neutron][L3-subteam] Weekly IRC meeting cancelled on September 14th

[Miguel Lavalle]

Dear L3-subteam,

Due to the OpenStack PTG next week in Denver, we will cancel our weekly
meeting on September 14th. We will resume normally on the 21st

See you in Denver!
__
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] [os-upstream-institute][all] Get together at the PTG

[Miguel Lavalle]

Ildiko,

For me it would be great if we can meet on Monday or Tuesday. Those two I
have also to find time to get together with the Docs team

Regards

On Fri, Aug 25, 2017 at 9:36 AM, Ildiko Vancsa 
wrote:

> Hi Training Team and All,
>
> As we have our next PTG coming up shortly I think that would be a great
> opportunity for the team and everyone who’s interested to meet and check
> where we are and what our future plans are. :)
>
> I would like to ask you to raise your hand by replying to this mail if you
> will be around during the PTG week in Denver and would be interested in
> joining. Please also indicate your availability for the week.
>
> Based on the responses we will pick a day and a time that works best for
> most to have our gathering.
>
> Please let me know if you have any questions.
>
> Thanks and Best Regards,
> Ildikó
> (IRC: ildikov)
>
>
>
> __
> 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