Re: [openstack-dev] [neutron] [networking-sfc] A standards-compliant SFC API

2016-04-21 Thread Vikram Choudhary 
Hi Igor,

Thanks for understanding. Let's continue the discussion over the submitted
spec.

Thanks
Vikram

On Thu, Apr 21, 2016 at 3:04 PM, Duarte Cardoso, Igor <
igor.duarte.card...@intel.com> wrote:

> Hi Vikram,
>
>
>
> Thanks for the response. I’m happy to provide enhancements instead of
> building the API from scratch, the semantics may change considerably
> though, resulting in what’s essentially a new API, but let’s see. I invite
> you to read the spec [1] thoroughly. Let’s continue there so we can better
> scope the discussion.
>
>
>
> [1] https://review.openstack.org/#/c/308453/
>
>
>
> Best regards,
>
> Igor.
>
>
>
> *From:* Vikram Choudhary [mailto:viks...@gmail.com]
> *Sent:* Thursday, April 21, 2016 3:39 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [neutron] [networking-sfc] A
> standards-compliant SFC API
>
>
>
> Just a quick glance over the proposal seems like the networking-sfc also
> does the same. In addition, networking-sfc is successfully integrated with
> ONOS[1] and planned for ODL[2], OVN [3] & Tacker[4] (without any issues
> with the existing API's so far). In addition, If we feel the existing
> networking-sfc API's has issues then let's enhance them rather than a fresh
> effort from the scratch.
>
>
>
> Let's discuss more about the proposal over the submitted spec.
>
>
>
> [1]
> https://github.com/openstack/networking-onos/blob/master/doc/source/devref/sfc_driver.rst
>
> [2] https://review.openstack.org/#/c/300898/
>
> [3]
> https://blueprints.launchpad.net/networking-sfc/+spec/networking-sfc-ovn-driver
>
> [4]
> https://blueprints.launchpad.net/networking-sfc/+spec/tacker-networking-sfc-driver
>
>
>
>
>
> On Thu, Apr 21, 2016 at 1:24 AM, Duarte Cardoso, Igor <
> igor.duarte.card...@intel.com> wrote:
>
> Thanks for the feedback Armando,
>
>
>
> Adding missing tag.
>
>
>
> Best regards,
>
> Igor.
>
>
>
> *From:* Armando M. [mailto:arma...@gmail.com]
> *Sent:* Wednesday, April 20, 2016 6:03 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [neutron][sfc] A standards-compliant SFC
> API
>
>
>
>
>
> On 20 April 2016 at 09:31, Duarte Cardoso, Igor <
> igor.duarte.card...@intel.com> wrote:
>
> Dear OpenStack Community,
>
>
>
> We've been investigating options in/around OpenStack for supporting
> Service Function Chaining. The networking-sfc project has made significant
> progress in this space, and we see lots of value in what has been
> completed. However, when we looked at the related IETF specs on SFC we
> concluded that there would be value in further developing an SFC API and
> related classification functionality to enhance the alignment between the
> work in the OpenStack community with the standards work. We would like to
> propose the SFC part as a potential networking-sfc v2 API, but are open to
> other options too based on your feedback.
>
>
>
> I have submitted a spec to the neutron-specs repo [1], where you can check
> what our initial thoughts for this new API are, and provide your feedback
> or questions regarding the same.
>
>
>
> Your thoughts on this are deeply appreciated. We are looking forward to
> having further discussions with everyone interested in giving feedback or
> establishing collaborations during the OpenStack Summit in Austin.
>
>
>
> [1] https://review.openstack.org/#/c/308453
>
>
>
> Thanks for reaching out.
>
>
>
> The networking-sfc initiative so far has been pretty autonomous. The
> project has its own launchpad project [1] and its own docs to document APIs
> and proposals [2]. During the long journey that Neutron has been through,
> we have been adjusting how to manage the project in order to strike a good
> balance between development agility, product stability and community needs.
> We're always looking forward to improving that balance and this means that
> how we track certain initiatives may evolve in the future. For now, it's
> probably best to target the mailing list with tag [networking-sfc] (in
> addition to neutron), as well as the project noted below.
>
>
>
> [1] https://launchpad.net/networking-sfc
>
> [2] http://docs.openstack.org/developer/networking-sfc/
>
>
>
>
>
> Thank you,
>
> Igor & the Intel OpenStack networking team.
>
>
> __
> O

Re: [openstack-dev] [neutron] [networking-sfc] A standards-compliant SFC API

2016-04-21 Thread Duarte Cardoso, Igor 
Hi Vikram,

Thanks for the response. I’m happy to provide enhancements instead of building 
the API from scratch, the semantics may change considerably though, resulting 
in what’s essentially a new API, but let’s see. I invite you to read the spec 
[1] thoroughly. Let’s continue there so we can better scope the discussion.

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

Best regards,
Igor.

From: Vikram Choudhary [mailto:viks...@gmail.com]
Sent: Thursday, April 21, 2016 3:39 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [neutron] [networking-sfc] A standards-compliant 
SFC API

Just a quick glance over the proposal seems like the networking-sfc also does 
the same. In addition, networking-sfc is successfully integrated with ONOS[1] 
and planned for ODL[2], OVN [3] & Tacker[4] (without any issues with the 
existing API's so far). In addition, If we feel the existing networking-sfc 
API's has issues then let's enhance them rather than a fresh effort from the 
scratch.

Let's discuss more about the proposal over the submitted spec.

[1] 
https://github.com/openstack/networking-onos/blob/master/doc/source/devref/sfc_driver.rst
[2] https://review.openstack.org/#/c/300898/
[3] 
https://blueprints.launchpad.net/networking-sfc/+spec/networking-sfc-ovn-driver
[4] 
https://blueprints.launchpad.net/networking-sfc/+spec/tacker-networking-sfc-driver


On Thu, Apr 21, 2016 at 1:24 AM, Duarte Cardoso, Igor 
<igor.duarte.card...@intel.com<mailto:igor.duarte.card...@intel.com>> wrote:
Thanks for the feedback Armando,

Adding missing tag.

Best regards,
Igor.

From: Armando M. [mailto:arma...@gmail.com<mailto:arma...@gmail.com>]
Sent: Wednesday, April 20, 2016 6:03 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [neutron][sfc] A standards-compliant SFC API


On 20 April 2016 at 09:31, Duarte Cardoso, Igor 
<igor.duarte.card...@intel.com<mailto:igor.duarte.card...@intel.com>> wrote:
Dear OpenStack Community,

We've been investigating options in/around OpenStack for supporting Service 
Function Chaining. The networking-sfc project has made significant progress in 
this space, and we see lots of value in what has been completed. However, when 
we looked at the related IETF specs on SFC we concluded that there would be 
value in further developing an SFC API and related classification functionality 
to enhance the alignment between the work in the OpenStack community with the 
standards work. We would like to propose the SFC part as a potential 
networking-sfc v2 API, but are open to other options too based on your feedback.

I have submitted a spec to the neutron-specs repo [1], where you can check what 
our initial thoughts for this new API are, and provide your feedback or 
questions regarding the same.

Your thoughts on this are deeply appreciated. We are looking forward to having 
further discussions with everyone interested in giving feedback or establishing 
collaborations during the OpenStack Summit in Austin.

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

Thanks for reaching out.

The networking-sfc initiative so far has been pretty autonomous. The project 
has its own launchpad project [1] and its own docs to document APIs and 
proposals [2]. During the long journey that Neutron has been through, we have 
been adjusting how to manage the project in order to strike a good balance 
between development agility, product stability and community needs. We're 
always looking forward to improving that balance and this means that how we 
track certain initiatives may evolve in the future. For now, it's probably best 
to target the mailing list with tag [networking-sfc] (in addition to neutron), 
as well as the project noted below.

[1] https://launchpad.net/networking-sfc
[2] http://docs.openstack.org/developer/networking-sfc/


Thank you,
Igor & the Intel OpenStack networking team.

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

Re: [openstack-dev] [neutron] [networking-sfc] A standards-compliant SFC API

2016-04-20 Thread Vikram Choudhary 
Just a quick glance over the proposal seems like the networking-sfc also
does the same. In addition, networking-sfc is successfully integrated with
ONOS[1] and planned for ODL[2], OVN [3] & Tacker[4] (without any issues
with the existing API's so far). In addition, If we feel the existing
networking-sfc API's has issues then let's enhance them rather than a fresh
effort from the scratch.

Let's discuss more about the proposal over the submitted spec.

[1]
https://github.com/openstack/networking-onos/blob/master/doc/source/devref/sfc_driver.rst
[2] https://review.openstack.org/#/c/300898/
[3]
https://blueprints.launchpad.net/networking-sfc/+spec/networking-sfc-ovn-driver
[4]
https://blueprints.launchpad.net/networking-sfc/+spec/tacker-networking-sfc-driver


On Thu, Apr 21, 2016 at 1:24 AM, Duarte Cardoso, Igor <
igor.duarte.card...@intel.com> wrote:

> Thanks for the feedback Armando,
>
>
>
> Adding missing tag.
>
>
>
> Best regards,
>
> Igor.
>
>
>
> *From:* Armando M. [mailto:arma...@gmail.com]
> *Sent:* Wednesday, April 20, 2016 6:03 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [neutron][sfc] A standards-compliant SFC
> API
>
>
>
>
>
> On 20 April 2016 at 09:31, Duarte Cardoso, Igor <
> igor.duarte.card...@intel.com> wrote:
>
> Dear OpenStack Community,
>
>
>
> We've been investigating options in/around OpenStack for supporting
> Service Function Chaining. The networking-sfc project has made significant
> progress in this space, and we see lots of value in what has been
> completed. However, when we looked at the related IETF specs on SFC we
> concluded that there would be value in further developing an SFC API and
> related classification functionality to enhance the alignment between the
> work in the OpenStack community with the standards work. We would like to
> propose the SFC part as a potential networking-sfc v2 API, but are open to
> other options too based on your feedback.
>
>
>
> I have submitted a spec to the neutron-specs repo [1], where you can check
> what our initial thoughts for this new API are, and provide your feedback
> or questions regarding the same.
>
>
>
> Your thoughts on this are deeply appreciated. We are looking forward to
> having further discussions with everyone interested in giving feedback or
> establishing collaborations during the OpenStack Summit in Austin.
>
>
>
> [1] https://review.openstack.org/#/c/308453
>
>
>
> Thanks for reaching out.
>
>
>
> The networking-sfc initiative so far has been pretty autonomous. The
> project has its own launchpad project [1] and its own docs to document APIs
> and proposals [2]. During the long journey that Neutron has been through,
> we have been adjusting how to manage the project in order to strike a good
> balance between development agility, product stability and community needs.
> We're always looking forward to improving that balance and this means that
> how we track certain initiatives may evolve in the future. For now, it's
> probably best to target the mailing list with tag [networking-sfc] (in
> addition to neutron), as well as the project noted below.
>
>
>
> [1] https://launchpad.net/networking-sfc
>
> [2] http://docs.openstack.org/developer/networking-sfc/
>
>
>
>
>
> Thank you,
>
> Igor & the Intel OpenStack networking 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 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] [networking-sfc] A standards-compliant SFC API

2016-04-20 Thread Duarte Cardoso, Igor 
Thanks for the feedback Armando,

Adding missing tag.

Best regards,
Igor.

From: Armando M. [mailto:arma...@gmail.com]
Sent: Wednesday, April 20, 2016 6:03 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [neutron][sfc] A standards-compliant SFC API


On 20 April 2016 at 09:31, Duarte Cardoso, Igor 
> wrote:
Dear OpenStack Community,

We've been investigating options in/around OpenStack for supporting Service 
Function Chaining. The networking-sfc project has made significant progress in 
this space, and we see lots of value in what has been completed. However, when 
we looked at the related IETF specs on SFC we concluded that there would be 
value in further developing an SFC API and related classification functionality 
to enhance the alignment between the work in the OpenStack community with the 
standards work. We would like to propose the SFC part as a potential 
networking-sfc v2 API, but are open to other options too based on your feedback.

I have submitted a spec to the neutron-specs repo [1], where you can check what 
our initial thoughts for this new API are, and provide your feedback or 
questions regarding the same.

Your thoughts on this are deeply appreciated. We are looking forward to having 
further discussions with everyone interested in giving feedback or establishing 
collaborations during the OpenStack Summit in Austin.

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

Thanks for reaching out.

The networking-sfc initiative so far has been pretty autonomous. The project 
has its own launchpad project [1] and its own docs to document APIs and 
proposals [2]. During the long journey that Neutron has been through, we have 
been adjusting how to manage the project in order to strike a good balance 
between development agility, product stability and community needs. We're 
always looking forward to improving that balance and this means that how we 
track certain initiatives may evolve in the future. For now, it's probably best 
to target the mailing list with tag [networking-sfc] (in addition to neutron), 
as well as the project noted below.

[1] https://launchpad.net/networking-sfc
[2] http://docs.openstack.org/developer/networking-sfc/


Thank you,
Igor & the Intel OpenStack networking 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 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