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

[Armando M.]

On 13 April 2016 at 03:18, Ilya Chukhnakov <ichukhna...@mirantis.com> wrote:

> Hello everyone!
>
> Count me in for the VLAN aware VMS. I already have a [seemingly working]
> proof-of-concept for the OVS driver case and expect to submit it for the
> review in a few days.
>
>
Please provide feedback on [1], as that should be the entry point to
discuss your PoC idea.

[1] https://review.openstack.org/#/c/273954/


>
> On 13 Apr 2016, at 12:51, Oleg Bondarev <obonda...@mirantis.com> wrote:
>
>
> -- Forwarded message --
> From: Sukhdev Kapur <sukhdevka...@gmail.com>
> Date: Mon, Apr 11, 2016 at 7:33 AM
> Subject: Re: [openstack-dev] [Neutron] Newton blueprints call for action
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Cc: Bence Romsics <bence.roms...@ericsson.com>, yan.songm...@zte.com.cn
>
>
> Hi Rossella,
>
> Good to hear that you will follow through with this. Ironic is looking for
> this API as well for bare metal deployments. We would love to work with you
> to make sure that this API/Implementation works for all servers ( VMs as
> well BMs)
>
> Thanks
> -Sukhdev
>
>
> On Wed, Apr 6, 2016 at 4:32 AM, Rossella Sblendido <rsblend...@suse.com>
> wrote:
>
>>
>>
>> On 04/05/2016 05:43 AM, Armando M. wrote:
>> >
>> > With this email I would like to appeal to the people in CC to report
>> > back their interest in continuing working on these items in their
>> > respective capacities, and/or the wider community, in case new owners
>> > need to be identified.
>> >
>> > I look forward to hearing back, hoping we can find the right resources
>> > to resume progress, and bring these important requirements to completion
>> > in time for Newton.
>>
>> Count me in for the vlan-aware-vms. We have now a solid design, it's
>> only a matter of putting it into code. I will help any way I can, I
>> really want to see this feature in Newton.
>>
>> cheers,
>>
>> Rossella
>>
>> __
>> 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: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://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] Newton blueprints call for action

[Ilya Chukhnakov]

Hello everyone!

Count me in for the VLAN aware VMS. I already have a [seemingly working] 
proof-of-concept for the OVS driver case and expect to submit it for the review 
in a few days.


> On 13 Apr 2016, at 12:51, Oleg Bondarev <obonda...@mirantis.com> wrote:
> 
> 
> -- Forwarded message --
> From: Sukhdev Kapur <sukhdevka...@gmail.com <mailto:sukhdevka...@gmail.com>>
> Date: Mon, Apr 11, 2016 at 7:33 AM
> Subject: Re: [openstack-dev] [Neutron] Newton blueprints call for action
> To: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev@lists.openstack.org <mailto:openstack-dev@lists.openstack.org>>
> Cc: Bence Romsics <bence.roms...@ericsson.com 
> <mailto:bence.roms...@ericsson.com>>, yan.songm...@zte.com.cn 
> <mailto:yan.songm...@zte.com.cn>
> 
> 
> Hi Rossella, 
> 
> Good to hear that you will follow through with this. Ironic is looking for 
> this API as well for bare metal deployments. We would love to work with you 
> to make sure that this API/Implementation works for all servers ( VMs as well 
> BMs)
> 
> Thanks
> -Sukhdev
> 
> 
> On Wed, Apr 6, 2016 at 4:32 AM, Rossella Sblendido <rsblend...@suse.com 
> <mailto:rsblend...@suse.com>> wrote:
> 
> 
> On 04/05/2016 05:43 AM, Armando M. wrote:
> >
> > With this email I would like to appeal to the people in CC to report
> > back their interest in continuing working on these items in their
> > respective capacities, and/or the wider community, in case new owners
> > need to be identified.
> >
> > I look forward to hearing back, hoping we can find the right resources
> > to resume progress, and bring these important requirements to completion
> > in time for Newton.
> 
> Count me in for the vlan-aware-vms. We have now a solid design, it's
> only a matter of putting it into code. I will help any way I can, I
> really want to see this feature in Newton.
> 
> cheers,
> 
> Rossella
> 
> __
> 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:unsubscribe>
> 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.openstack.org?subject:unsubscribe 
> <http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe>
> 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.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Sukhdev Kapur]

Hi Rossella,

Good to hear that you will follow through with this. Ironic is looking for
this API as well for bare metal deployments. We would love to work with you
to make sure that this API/Implementation works for all servers ( VMs as
well BMs)

Thanks
-Sukhdev


On Wed, Apr 6, 2016 at 4:32 AM, Rossella Sblendido 
wrote:

>
>
> On 04/05/2016 05:43 AM, Armando M. wrote:
> >
> > With this email I would like to appeal to the people in CC to report
> > back their interest in continuing working on these items in their
> > respective capacities, and/or the wider community, in case new owners
> > need to be identified.
> >
> > I look forward to hearing back, hoping we can find the right resources
> > to resume progress, and bring these important requirements to completion
> > in time for Newton.
>
> Count me in for the vlan-aware-vms. We have now a solid design, it's
> only a matter of putting it into code. I will help any way I can, I
> really want to see this feature in Newton.
>
> cheers,
>
> Rossella
>
> __
> OpenStack Development Mailing 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] Newton blueprints call for action

[Armando M.]

Folks, thanks to everyone who has replied to the the thread. Much
appreciated it.

I'll reach out individually to figure out next steps and come back here to
provide a status update.

Cheers,
Armando

On 6 April 2016 at 07:17, Brent Eagles  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi Armando,
>
> On 05/04/16 01:13 AM, Armando M. wrote:
> > Hi Neutrinos,
> >
> > During today's team meeting [0], we went through the current
> > milestone workload [1].
> >
> > This is mostly made of Mitaka backlog items, amongst which we
> > discussed two blueprints [2, 3]. These two efforts had their spec
> > approved during the Mitaka timeframe, but code lagged behind, and
> > hence got deferred [4].
> >
> > I would like to understand if these need new owners (both assignees
> > and approvers). Code submitted [5,6] has not been touched in a
> > while, and whilst I appreciate people have been busy focussing on
> > Mitaka (myself included), the Newton master branch has been open
> > for a while.
> >
> > With this email I would like to appeal to the people in CC to
> > report back their interest in continuing working on these items in
> > their respective capacities, and/or the wider community, in case
> > new owners need to be identified.
> >
> > I look forward to hearing back, hoping we can find the right
> > resources to resume progress, and bring these important
> > requirements to completion in time for Newton.
> >
> > Many thanks, Armando
>
> As it happens, I've been tasked to work on TripleO as a general
> contributor with a networking focus. For better or worse, the database
> related work was the only thing on my early radar and I will shepherd
> that along as needed, but I won't be able to commit to the larger bits
> of the remaining work.
>
> While we could wait for summit to hand off, I think it would be better
> for someone who is looking to take over ownership of all or some of
> the pieces to sync up with Bence, myself, and Songming ASAP.
>
> Cheers,
>
> Brent
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJXBRpyAAoJEIXWptqvFlBWIHgQAL3e+HjvDXvziee1oLfkz/kT
> DIghPQoqZg+oLJYmezoa4ixzNY53pE/EtkTxCtXrmEfbvwCqNWkgNWqTKm4nGe1J
> Uv1HFpdrUtg9j7bS9bIPRKQKaWr9nkNUJZPL5fjIs467WWQP0e6YbigVgoJQRYXi
> t/o5ZKgRKp8DOW+bqjXvQvM69WXq9iyH7KmjVfbJ2o3NeoFOmPTlXtAunbp33xj4
> 6MuFH4USJZS11x0IgIiaCZHJS+RWfDdxI+4ONCqQ1lYkrLp9wl8XNznQzum60wFU
> jhjJcaRtfdbMHmRd72//QVeIlX9VA6b5q36a/adPxbKrD2XTd4pntJ86dnU0aQFJ
> sriJRk3KlD0IMDMS+rRsKz7EyJJP+9b5zlWCzX0V+1zNlcB6eiowOmo3QUQrFBQT
> O50KS9YC7ef0EMWE6kikxyK8AxZ1Hjcm3eM50mShU+eCI/JPgkHeRQX+Z16RBybj
> xhEBgRIvLS7bH8c6vqjIgmLQ1zxQ3EPR440Zpi0rw3rChP/lugYYQpcjXDfVFWED
> gwe+RQvevj4tJeVjXG662DMuzmjy/cM2nNLZm3AZsaASkR73/M+Qmy53Y22T+T2o
> VVcbOsK2+1Y8JFAVZguUib9pQ/z8DgBKs4+rfWiV4mzBAGwVIxePiNDiQ1kQU/Z0
> 3kUfgrNS0CgmE/nmg05x
> =7kzU
> -END PGP SIGNATURE-
>
__
OpenStack Development Mailing 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] Newton blueprints call for action

[Brent Eagles]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Armando,

On 05/04/16 01:13 AM, Armando M. wrote:
> Hi Neutrinos,
> 
> During today's team meeting [0], we went through the current
> milestone workload [1].
> 
> This is mostly made of Mitaka backlog items, amongst which we
> discussed two blueprints [2, 3]. These two efforts had their spec
> approved during the Mitaka timeframe, but code lagged behind, and
> hence got deferred [4].
> 
> I would like to understand if these need new owners (both assignees
> and approvers). Code submitted [5,6] has not been touched in a
> while, and whilst I appreciate people have been busy focussing on
> Mitaka (myself included), the Newton master branch has been open
> for a while.
> 
> With this email I would like to appeal to the people in CC to
> report back their interest in continuing working on these items in
> their respective capacities, and/or the wider community, in case
> new owners need to be identified.
> 
> I look forward to hearing back, hoping we can find the right
> resources to resume progress, and bring these important
> requirements to completion in time for Newton.
> 
> Many thanks, Armando

As it happens, I've been tasked to work on TripleO as a general
contributor with a networking focus. For better or worse, the database
related work was the only thing on my early radar and I will shepherd
that along as needed, but I won't be able to commit to the larger bits
of the remaining work.

While we could wait for summit to hand off, I think it would be better
for someone who is looking to take over ownership of all or some of
the pieces to sync up with Bence, myself, and Songming ASAP.

Cheers,

Brent

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXBRpyAAoJEIXWptqvFlBWIHgQAL3e+HjvDXvziee1oLfkz/kT
DIghPQoqZg+oLJYmezoa4ixzNY53pE/EtkTxCtXrmEfbvwCqNWkgNWqTKm4nGe1J
Uv1HFpdrUtg9j7bS9bIPRKQKaWr9nkNUJZPL5fjIs467WWQP0e6YbigVgoJQRYXi
t/o5ZKgRKp8DOW+bqjXvQvM69WXq9iyH7KmjVfbJ2o3NeoFOmPTlXtAunbp33xj4
6MuFH4USJZS11x0IgIiaCZHJS+RWfDdxI+4ONCqQ1lYkrLp9wl8XNznQzum60wFU
jhjJcaRtfdbMHmRd72//QVeIlX9VA6b5q36a/adPxbKrD2XTd4pntJ86dnU0aQFJ
sriJRk3KlD0IMDMS+rRsKz7EyJJP+9b5zlWCzX0V+1zNlcB6eiowOmo3QUQrFBQT
O50KS9YC7ef0EMWE6kikxyK8AxZ1Hjcm3eM50mShU+eCI/JPgkHeRQX+Z16RBybj
xhEBgRIvLS7bH8c6vqjIgmLQ1zxQ3EPR440Zpi0rw3rChP/lugYYQpcjXDfVFWED
gwe+RQvevj4tJeVjXG662DMuzmjy/cM2nNLZm3AZsaASkR73/M+Qmy53Y22T+T2o
VVcbOsK2+1Y8JFAVZguUib9pQ/z8DgBKs4+rfWiV4mzBAGwVIxePiNDiQ1kQU/Z0
3kUfgrNS0CgmE/nmg05x
=7kzU
-END PGP SIGNATURE-

__
OpenStack Development Mailing 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] Newton blueprints call for action

[Rossella Sblendido]

On 04/05/2016 05:43 AM, Armando M. wrote:
> 
> With this email I would like to appeal to the people in CC to report
> back their interest in continuing working on these items in their
> respective capacities, and/or the wider community, in case new owners
> need to be identified.
> 
> I look forward to hearing back, hoping we can find the right resources
> to resume progress, and bring these important requirements to completion
> in time for Newton.

Count me in for the vlan-aware-vms. We have now a solid design, it's
only a matter of putting it into code. I will help any way I can, I
really want to see this feature in Newton.

cheers,

Rossella

__
OpenStack Development Mailing 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] Newton blueprints call for action

[Sean M. Collins]

Armando M. wrote:
> I would like to understand if these need new owners (both assignees and
> approvers). Code submitted [5,6] has not been touched in a while, and
> whilst I appreciate people have been busy focussing on Mitaka (myself
> included), the Newton master branch has been open for a while.
> 
> With this email I would like to appeal to the people in CC to report back
> their interest in continuing working on these items in their respective
> capacities, and/or the wider community, in case new owners need to be
> identified.

My involvement in the FwaaS project has been reduced significantly over
the past couple of months, and I think because of this, someone should
probably step in and replace me.

I would like to apologize for my failure, because I advocated publicly for
using the FwaaS API as the vehicle for more granular and more advanced
packet filtering features, as opposed to extending the security group
API. It is a failure on my part to advocate for a solution,
then not be able to deliver the required work. I am sorry for this,
truly.

-- 
Sean M. Collins

__
OpenStack Development Mailing 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] Newton blueprints call for action

[Armando M.]

Hi Neutrinos,

During today's team meeting [0], we went through the current milestone
workload [1].

This is mostly made of Mitaka backlog items, amongst which we discussed two
blueprints [2, 3]. These two efforts had their spec approved during the
Mitaka timeframe, but code lagged behind, and hence got deferred [4].

I would like to understand if these need new owners (both assignees and
approvers). Code submitted [5,6] has not been touched in a while, and
whilst I appreciate people have been busy focussing on Mitaka (myself
included), the Newton master branch has been open for a while.

With this email I would like to appeal to the people in CC to report back
their interest in continuing working on these items in their respective
capacities, and/or the wider community, in case new owners need to be
identified.

I look forward to hearing back, hoping we can find the right resources to
resume progress, and bring these important requirements to completion in
time for Newton.

Many thanks,
Armando

[0]
http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-04-04-21.00.log.html
[1] https://launchpad.net/neutron/+milestone/newton-1
[2] https://blueprints.launchpad.net/neutron/+spec/fwaas-api-2.0
[3] https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms
[4]
https://github.com/openstack/neutron-specs/tree/master/specs/backlog/mitaka
[5] https://review.openstack.org/#/q/status:open+topic:bp/vlan-aware-vms
[6] https://review.openstack.org/#/q/status:open+topic:fwaas_v2_api
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev