OK, lets go with that, though given how packed Juno-3 is, I'd lean
towards working out the kinks and architecture here and then we circle
back for Kilo and get this work approved and moving forward. We can
chat in August if by chance major progress is made.
Thanks,
Kyle
On Mon, Jul 21, 2014 at 2:
That would be my thinking as well, but if we managed to make an impressive
progress from now until the Feature Freeze proposal deadline, I'd be
willing to reevaluate the situation.
A.
On 21 July 2014 12:13, Kyle Mestery wrote:
> On Mon, Jul 21, 2014 at 2:03 PM, Armando M. wrote:
> > I think t
On Mon, Jul 21, 2014 at 2:03 PM, Armando M. wrote:
> I think the specs under the umbrella one can be approved/treated
> individually.
>
> The umbrella one is an informational blueprint, there is not going to be
> code associated with it, however before approving it (and the individual
> ones) we'd
I think the specs under the umbrella one can be approved/treated
individually.
The umbrella one is an informational blueprint, there is not going to be
code associated with it, however before approving it (and the individual
ones) we'd need all the parties interested in vsphere support for Neutron
On Sun, Jul 20, 2014 at 4:21 AM, Gary Kotton wrote:
> Hi,
> I would like to propose the following for spec freeze exception:
>
> https://review.openstack.org/#/c/105369
>
> This is an umbrella spec for a number of VMware DVS support specs. Each has
> its own unique use case and will enable a lot o
Hi,
I would like to propose the following for spec freeze exception:
* https://review.openstack.org/#/c/105369
This is an umbrella spec for a number of VMware DVS support specs. Each has its
own unique use case and will enable a lot of existing VMware DVS users to start
to use OpenStack.
F
