I agree with Kevin. Like in Juno, we as a subteam will be shooting for
option 1 (again) for Kilo - ideally we can land in Kilo, and we will work
closely with the community to try to accomplish that. In the meantime, we
need to have a repo to iterate our implementations, build package (Juno
based) t
I agree with Kevin. Any option in-tree or in-incubator would need core
review time, and they are already oversubscribed with nova parity issues
(for Juno). So the only option to continue collaboration on experimenting
with policy based networking on current openstack is on stackforge (option
5).
S
Thanks. This is good writeup.
>Of course this all assumes there is consensus that we should proceed with
GBP, that we should continue by iterating the currently proposed design and
code, and that GBP should eventually become part of Neutron. These
assumptions may still be the real issues :-( .
Un
On 9/10/14, 6:54 PM, Kevin Benton wrote:
Being in the incubator won't help with this if it's a different repo
as well.
Agreed.
Given the requirement for GBP to intercept API requests, the potential
couplings between policy drivers, ML2 mechanism drivers, and even
service plugins (L3 router),
Being in the incubator won't help with this if it's a different repo as
well.
On Wed, Sep 10, 2014 at 7:22 AM, Robert Kukura
wrote:
>
> On 9/9/14, 7:51 PM, Jay Pipes wrote:
>
>> On 09/09/2014 06:57 PM, Kevin Benton wrote:
>>
>>> Hi Jay,
>>>
>>> The main component that won't work without direct i
On 9/9/14, 7:51 PM, Jay Pipes wrote:
On 09/09/2014 06:57 PM, Kevin Benton wrote:
Hi Jay,
The main component that won't work without direct integration is
enforcing policy on calls directly to Neutron and calls between the
plugins inside of Neutron. However, that's only one component of GBP.
Al
4 04:31:05 AM---Tl;dr - Neutron incubator is only a wiki
> page with many uncertainties. Use StackForge to make progre
>
> From: Kevin Benton
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.ope
On 09/09/2014 06:57 PM, Kevin Benton wrote:
Hi Jay,
The main component that won't work without direct integration is
enforcing policy on calls directly to Neutron and calls between the
plugins inside of Neutron. However, that's only one component of GBP.
All of the declarative abstractions, rend
Hi Jay,
The main component that won't work without direct integration is enforcing
policy on calls directly to Neutron and calls between the plugins inside of
Neutron. However, that's only one component of GBP. All of the declarative
abstractions, rendering of policy, etc can be experimented with
On 09/04/2014 12:07 AM, Sumit Naiksatam wrote:
Hi,
There's been a lot of lively discussion on GBP a few weeks back and we
wanted to drive forward the discussion on this a bit more. As you
might imagine, we're excited to move this forward so more people can
try it out. Here are the options:
* N
active hide details for Kevin Benton ---09/05/2014 04:31:05
>> AM---Tl;dr - Neutron incubator is only a wiki page with many unce]Kevin
>> Benton ---09/05/2014 04:31:05 AM---Tl;dr - Neutron incubator is only a wiki
>> page with many uncertainties. Use StackForge to make progre
>
opment Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: 09/05/2014 04:31 AM
> Subject: Re: [openstack-dev] [neutron][policy] Group-based Policy next
> steps
> --
>
>
>
> Tl;dr - Neutron incubato
] [neutron][policy] Group-based Policy next
steps
Tl;dr - Neutron incubator is only a wiki page with many uncertainties. Use
StackForge to make progress and re-evaluate when the incubator exists.
I also agree that starting out in StackForge as a separate repo is a better
first step. I
Tl;dr - Neutron incubator is only a wiki page with many uncertainties. Use
StackForge to make progress and re-evaluate when the incubator exists.
I also agree that starting out in StackForge as a separate repo is a better
first step. In addition to the uncertainty around packaging and other
proce
I agree with Prasad here.
There remains lots of unknown about Neutron incubator and its workflow at
this point, and the idea of Neutron feature branch is at best in embryonic
stage. It seems like among the three options, the most well-defined one is
indeed through stackforge.
When and if the Neut
I agree. Also, as this does not preclude using the incubator when it is
ready, this is a good way to start iterating on implementation in parallel
with those issues being addressed by the community.
In my view, the issues raised around the incubator were significant enough
(around packaging, handl
Sumit
Thanks for initiating this and also good discussion today on the IRC.
My thoughts are that it is important to make this available to potential
users and customers as soon as possible so that we can get the necessary
feedback. Considering that the neutron cores and community are battling
nova
17 matches
Mail list logo
