Re: [openstack-dev] [Fuel] Remove nova-network as a deployment option in Fuel?

2015-12-01 Thread Alexander Arzhanov 
Hi, we have plugins for neutron (DVS and NSX). We'll finish the work
on component
registry <https://review.openstack.org/#/c/229306/>.
You could safely remove nova-network altogether.

On Tue, Dec 1, 2015 at 5:49 PM, Sheena Gregson <sgreg...@mirantis.com>
wrote:

> We do support Neutron for vCenter, but – as I mentioned a few months ago –
> we do not yet have a fully vetted way to deploy the multi-hypervisor use
> case with both KVM/QEMU and vCenter.  This depends on our ability to select
> multiple networking options and align them to the correct hypervisors.
>
>
>
> Per a conversation with Andrian Noga and his team yesterday, they are
> finishing work on the component registry [1] which will enable the
> multi-hypervisor, multi-network use case.  This work is being completed now.
>
>
>
> My recommendation remains that we should avoid deprecating nova-network
> until we have at least tested the basic multi-hypervisor use case with the
> new functionality.  Can we remove nova-network after FF as a High priority
> bug?
>
>
>
> [1] https://review.openstack.org/#/c/229306/
>
>
>
> *From:* Mike Scherbakov [mailto:mscherba...@mirantis.com]
>
> *Sent:* Tuesday, December 01, 2015 1:37 AM
>
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [Fuel] Remove nova-network as a deployment
> option in Fuel?
>
>
>
> Aleksey, can you clarify it? Why it can't be deployed? According to what I
> see at our fakeUI install [1], wizard allows to choose nova-network only in
> case if you choose vcenter.
>
>
>
> Do we support Neutron for vCenter already? If so - we could safely remove
> nova-network altogether.
>
>
>
> [1] http://demo.fuel-infra.org:8000/
>
>
>
> On Mon, Nov 30, 2015 at 4:27 AM Aleksey Kasatkin <akasat...@mirantis.com>
> wrote:
>
> This remains unclear.
>
> Now, for 8.0, the Environment with Nova-Network can be created but cannot
> be deployed (and its creation is tested in UI integration tests).
> AFAIC, we should either remove the ability of creation of environments
> with Nova-Network in 8.0 or return it back into working state.
>
>
> Aleksey Kasatkin
>
>
>
> On Fri, Oct 23, 2015 at 3:42 PM, Sheena Gregson <sgreg...@mirantis.com>
> wrote:
>
> As a reminder: there are no individual networking options that can be used
> with both vCenter and KVM/QEMU hypervisors once we deprecate nova-network.
>
>
>
> The code for vCenter as a stand-alone deployment may be there, but the
> code for the component registry (
> https://blueprints.launchpad.net/fuel/+spec/component-registry) is still
> not complete.  The component registry is required for a multi-HV
> environment, because it provides compatibility information for Networking
> and HVs.  In theory, landing this feature will enable us to configure DVS +
> vCenter and Neutron with GRE/VxLAN + KVM/QEMU in the same environment.
>
>
>
> While Andriy Popyvich has made considerable progress on this story, I
> personally feel very strongly against deprecating nova-network until we
> have confirmed that we can support *all current use cases* with the
> available code base.
>
>
>
> Are we willing to lose the multi-HV functionality if something prevents
> the component registry work from landing in its entirety before the next
> release?
>
>
>
> *From:* Sergii Golovatiuk [mailto:sgolovat...@mirantis.com]
> *Sent:* Friday, October 23, 2015 6:30 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [Fuel] Remove nova-network as a deployment
> option in Fuel?
>
>
>
> Hi,
>
>
>
> As far as I know neutron code for VCenter is ready. Guys are still testing
> it. Keep patience... There will be announce soon.
>
>
> --
> Best regards,
> Sergii Golovatiuk,
> Skype #golserge
> IRC #holser
>
>
> __
> 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
>
> --
>
> Mike Scherbakov
> #mihgen
>
> __

Re: [openstack-dev] [Fuel] Remove nova-network as a deployment option in Fuel?

2015-12-01 Thread Aleksey Kasatkin 
It can be selected but we have no tests for deployment which are run on
periodical basis. So, we do not have any recent status.
Also, serializer in Nailgun for Nova-Network is now not in use (it is not
tested how serialization will work in 8.0).


Aleksey Kasatkin


On Tue, Dec 1, 2015 at 9:36 AM, Mike Scherbakov <mscherba...@mirantis.com>
wrote:

> Aleksey, can you clarify it? Why it can't be deployed? According to what I
> see at our fakeUI install [1], wizard allows to choose nova-network only in
> case if you choose vcenter.
>
> Do we support Neutron for vCenter already? If so - we could safely remove
> nova-network altogether.
>
> [1] http://demo.fuel-infra.org:8000/
>
> On Mon, Nov 30, 2015 at 4:27 AM Aleksey Kasatkin <akasat...@mirantis.com>
> wrote:
>
>> This remains unclear.
>> Now, for 8.0, the Environment with Nova-Network can be created but cannot
>> be deployed (and its creation is tested in UI integration tests).
>> AFAIC, we should either remove the ability of creation of environments
>> with Nova-Network in 8.0 or return it back into working state.
>>
>>
>> Aleksey Kasatkin
>>
>>
>> On Fri, Oct 23, 2015 at 3:42 PM, Sheena Gregson <sgreg...@mirantis.com>
>> wrote:
>>
>>> As a reminder: there are no individual networking options that can be
>>> used with both vCenter and KVM/QEMU hypervisors once we deprecate
>>> nova-network.
>>>
>>>
>>>
>>> The code for vCenter as a stand-alone deployment may be there, but the
>>> code for the component registry (
>>> https://blueprints.launchpad.net/fuel/+spec/component-registry) is
>>> still not complete.  The component registry is required for a multi-HV
>>> environment, because it provides compatibility information for Networking
>>> and HVs.  In theory, landing this feature will enable us to configure DVS +
>>> vCenter and Neutron with GRE/VxLAN + KVM/QEMU in the same environment.
>>>
>>>
>>>
>>> While Andriy Popyvich has made considerable progress on this story, I
>>> personally feel very strongly against deprecating nova-network until we
>>> have confirmed that we can support *all current use cases* with the
>>> available code base.
>>>
>>>
>>>
>>> Are we willing to lose the multi-HV functionality if something prevents
>>> the component registry work from landing in its entirety before the next
>>> release?
>>>
>>>
>>>
>>> *From:* Sergii Golovatiuk [mailto:sgolovat...@mirantis.com]
>>> *Sent:* Friday, October 23, 2015 6:30 AM
>>> *To:* OpenStack Development Mailing List (not for usage questions) <
>>> openstack-dev@lists.openstack.org>
>>> *Subject:* Re: [openstack-dev] [Fuel] Remove nova-network as a
>>> deployment option in Fuel?
>>>
>>>
>>>
>>> Hi,
>>>
>>>
>>>
>>> As far as I know neutron code for VCenter is ready. Guys are still
>>> testing it. Keep patience... There will be announce soon.
>>>
>>>
>>> --
>>> Best regards,
>>> Sergii Golovatiuk,
>>> Skype #golserge
>>> IRC #holser
>>>
>>>
>>> __
>>> 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
>>
> --
> Mike Scherbakov
> #mihgen
>
> __
> 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] [Fuel] Remove nova-network as a deployment option in Fuel?

2015-12-01 Thread Sheena Gregson 
We do support Neutron for vCenter, but – as I mentioned a few months ago –
we do not yet have a fully vetted way to deploy the multi-hypervisor use
case with both KVM/QEMU and vCenter.  This depends on our ability to select
multiple networking options and align them to the correct hypervisors.



Per a conversation with Andrian Noga and his team yesterday, they are
finishing work on the component registry [1] which will enable the
multi-hypervisor, multi-network use case.  This work is being completed now.



My recommendation remains that we should avoid deprecating nova-network
until we have at least tested the basic multi-hypervisor use case with the
new functionality.  Can we remove nova-network after FF as a High priority
bug?



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



*From:* Mike Scherbakov [mailto:mscherba...@mirantis.com]

*Sent:* Tuesday, December 01, 2015 1:37 AM
*To:* OpenStack Development Mailing List (not for usage questions) <
openstack-dev@lists.openstack.org>
*Subject:* Re: [openstack-dev] [Fuel] Remove nova-network as a deployment
option in Fuel?



Aleksey, can you clarify it? Why it can't be deployed? According to what I
see at our fakeUI install [1], wizard allows to choose nova-network only in
case if you choose vcenter.



Do we support Neutron for vCenter already? If so - we could safely remove
nova-network altogether.



[1] http://demo.fuel-infra.org:8000/



On Mon, Nov 30, 2015 at 4:27 AM Aleksey Kasatkin <akasat...@mirantis.com>
wrote:

This remains unclear.

Now, for 8.0, the Environment with Nova-Network can be created but cannot
be deployed (and its creation is tested in UI integration tests).
AFAIC, we should either remove the ability of creation of environments with
Nova-Network in 8.0 or return it back into working state.


Aleksey Kasatkin



On Fri, Oct 23, 2015 at 3:42 PM, Sheena Gregson <sgreg...@mirantis.com>
wrote:

As a reminder: there are no individual networking options that can be used
with both vCenter and KVM/QEMU hypervisors once we deprecate nova-network.



The code for vCenter as a stand-alone deployment may be there, but the code
for the component registry (
https://blueprints.launchpad.net/fuel/+spec/component-registry) is still
not complete.  The component registry is required for a multi-HV
environment, because it provides compatibility information for Networking
and HVs.  In theory, landing this feature will enable us to configure DVS +
vCenter and Neutron with GRE/VxLAN + KVM/QEMU in the same environment.



While Andriy Popyvich has made considerable progress on this story, I
personally feel very strongly against deprecating nova-network until we
have confirmed that we can support *all current use cases* with the
available code base.



Are we willing to lose the multi-HV functionality if something prevents the
component registry work from landing in its entirety before the next
release?



*From:* Sergii Golovatiuk [mailto:sgolovat...@mirantis.com]
*Sent:* Friday, October 23, 2015 6:30 AM
*To:* OpenStack Development Mailing List (not for usage questions) <
openstack-dev@lists.openstack.org>
*Subject:* Re: [openstack-dev] [Fuel] Remove nova-network as a deployment
option in Fuel?



Hi,



As far as I know neutron code for VCenter is ready. Guys are still testing
it. Keep patience... There will be announce soon.


--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser


__
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

-- 

Mike Scherbakov
#mihgen
__
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] [Fuel] Remove nova-network as a deployment option in Fuel?

2015-11-30 Thread Mike Scherbakov 
Aleksey, can you clarify it? Why it can't be deployed? According to what I
see at our fakeUI install [1], wizard allows to choose nova-network only in
case if you choose vcenter.

Do we support Neutron for vCenter already? If so - we could safely remove
nova-network altogether.

[1] http://demo.fuel-infra.org:8000/

On Mon, Nov 30, 2015 at 4:27 AM Aleksey Kasatkin <akasat...@mirantis.com>
wrote:

> This remains unclear.
> Now, for 8.0, the Environment with Nova-Network can be created but cannot
> be deployed (and its creation is tested in UI integration tests).
> AFAIC, we should either remove the ability of creation of environments
> with Nova-Network in 8.0 or return it back into working state.
>
>
> Aleksey Kasatkin
>
>
> On Fri, Oct 23, 2015 at 3:42 PM, Sheena Gregson <sgreg...@mirantis.com>
> wrote:
>
>> As a reminder: there are no individual networking options that can be
>> used with both vCenter and KVM/QEMU hypervisors once we deprecate
>> nova-network.
>>
>>
>>
>> The code for vCenter as a stand-alone deployment may be there, but the
>> code for the component registry (
>> https://blueprints.launchpad.net/fuel/+spec/component-registry) is still
>> not complete.  The component registry is required for a multi-HV
>> environment, because it provides compatibility information for Networking
>> and HVs.  In theory, landing this feature will enable us to configure DVS +
>> vCenter and Neutron with GRE/VxLAN + KVM/QEMU in the same environment.
>>
>>
>>
>> While Andriy Popyvich has made considerable progress on this story, I
>> personally feel very strongly against deprecating nova-network until we
>> have confirmed that we can support *all current use cases* with the
>> available code base.
>>
>>
>>
>> Are we willing to lose the multi-HV functionality if something prevents
>> the component registry work from landing in its entirety before the next
>> release?
>>
>>
>>
>> *From:* Sergii Golovatiuk [mailto:sgolovat...@mirantis.com]
>> *Sent:* Friday, October 23, 2015 6:30 AM
>> *To:* OpenStack Development Mailing List (not for usage questions) <
>> openstack-dev@lists.openstack.org>
>> *Subject:* Re: [openstack-dev] [Fuel] Remove nova-network as a
>> deployment option in Fuel?
>>
>>
>>
>> Hi,
>>
>>
>>
>> As far as I know neutron code for VCenter is ready. Guys are still
>> testing it. Keep patience... There will be announce soon.
>>
>>
>> --
>> Best regards,
>> Sergii Golovatiuk,
>> Skype #golserge
>> IRC #holser
>>
>> __
>> 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
>
-- 
Mike Scherbakov
#mihgen
__
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] [Fuel] Remove nova-network as a deployment option in Fuel?

2015-11-30 Thread Aleksey Kasatkin 
This remains unclear.
Now, for 8.0, the Environment with Nova-Network can be created but cannot
be deployed (and its creation is tested in UI integration tests).
AFAIC, we should either remove the ability of creation of environments with
Nova-Network in 8.0 or return it back into working state.


Aleksey Kasatkin


On Fri, Oct 23, 2015 at 3:42 PM, Sheena Gregson <sgreg...@mirantis.com>
wrote:

> As a reminder: there are no individual networking options that can be used
> with both vCenter and KVM/QEMU hypervisors once we deprecate nova-network.
>
>
>
> The code for vCenter as a stand-alone deployment may be there, but the
> code for the component registry (
> https://blueprints.launchpad.net/fuel/+spec/component-registry) is still
> not complete.  The component registry is required for a multi-HV
> environment, because it provides compatibility information for Networking
> and HVs.  In theory, landing this feature will enable us to configure DVS +
> vCenter and Neutron with GRE/VxLAN + KVM/QEMU in the same environment.
>
>
>
> While Andriy Popyvich has made considerable progress on this story, I
> personally feel very strongly against deprecating nova-network until we
> have confirmed that we can support *all current use cases* with the
> available code base.
>
>
>
> Are we willing to lose the multi-HV functionality if something prevents
> the component registry work from landing in its entirety before the next
> release?
>
>
>
> *From:* Sergii Golovatiuk [mailto:sgolovat...@mirantis.com]
> *Sent:* Friday, October 23, 2015 6:30 AM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [Fuel] Remove nova-network as a deployment
> option in Fuel?
>
>
>
> Hi,
>
>
>
> As far as I know neutron code for VCenter is ready. Guys are still testing
> it. Keep patience... There will be announce soon.
>
>
> --
> Best regards,
> Sergii Golovatiuk,
> Skype #golserge
> IRC #holser
>
> __
> 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] [Fuel] Remove nova-network as a deployment option in Fuel?

2015-10-23 Thread Sheena Gregson 
As a reminder: there are no individual networking options that can be used
with both vCenter and KVM/QEMU hypervisors once we deprecate nova-network.



The code for vCenter as a stand-alone deployment may be there, but the code
for the component registry (
https://blueprints.launchpad.net/fuel/+spec/component-registry) is still
not complete.  The component registry is required for a multi-HV
environment, because it provides compatibility information for Networking
and HVs.  In theory, landing this feature will enable us to configure DVS +
vCenter and Neutron with GRE/VxLAN + KVM/QEMU in the same environment.



While Andriy Popyvich has made considerable progress on this story, I
personally feel very strongly against deprecating nova-network until we
have confirmed that we can support *all current use cases* with the
available code base.



Are we willing to lose the multi-HV functionality if something prevents the
component registry work from landing in its entirety before the next
release?



*From:* Sergii Golovatiuk [mailto:sgolovat...@mirantis.com]
*Sent:* Friday, October 23, 2015 6:30 AM
*To:* OpenStack Development Mailing List (not for usage questions) <
openstack-dev@lists.openstack.org>
*Subject:* Re: [openstack-dev] [Fuel] Remove nova-network as a deployment
option in Fuel?



Hi,



As far as I know neutron code for VCenter is ready. Guys are still testing
it. Keep patience... There will be announce soon.


--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
__
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] [Fuel] Remove nova-network as a deployment option in Fuel?

2015-10-23 Thread Igor Kalnitsky 
Hi all,

> Just a small note, we shouldn't remove it completely from Nailgun
> codebase, because we still have old environments to support,

How many releases we should wait before nova-network completely?
AFAIK, it was deprecated since 6.1.. and it was kept in 7.0 only for
VCenter case. If so, maybe it's time to remove it completely in 8.0
and don't care for old environments? Otherwise, legacy code will never
be removed.

Igor.

On Thu, Oct 22, 2015 at 9:52 PM, Mike Scherbakov
 wrote:
> Hi all,
> I'm back to this thread. Who can take a lead here and remove nova-network
> starting from 8.0 and all following releases?
>
>
> On Thu, Oct 1, 2015 at 3:15 AM Sergii Golovatiuk 
> wrote:
>>
>> Hi,
>>
>> Can we get the latest supported release version? We will remove from
>> nailgun after End of Life of that particular release...
>>
>>
>> --
>> Best regards,
>> Sergii Golovatiuk,
>> Skype #golserge
>> IRC #holser
>> __
>> 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
>
> --
> Mike Scherbakov
> #mihgen
>
> __
> 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] [Fuel] Remove nova-network as a deployment option in Fuel?

2015-10-23 Thread Sergii Golovatiuk 
Hi,

As far as I know neutron code for VCenter is ready. Guys are still testing
it. Keep patience... There will be announce soon.

--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
__
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] [Fuel] Remove nova-network as a deployment option in Fuel?

2015-10-22 Thread Mike Scherbakov 
Hi all,
I'm back to this thread. Who can take a lead here and remove nova-network
starting from 8.0 and all following releases?


On Thu, Oct 1, 2015 at 3:15 AM Sergii Golovatiuk 
wrote:

> Hi,
>
> Can we get the latest supported release version? We will remove from
> nailgun after End of Life of that particular release...
>
>
> --
> Best regards,
> Sergii Golovatiuk,
> Skype #golserge
> IRC #holser
> __
> 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
>
-- 
Mike Scherbakov
#mihgen
__
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] [Fuel] Remove nova-network as a deployment option in Fuel?

2015-10-01 Thread Evgeniy L 
Hi,

Just a small note, we shouldn't remove it completely from Nailgun codebase,
because we still have old environments to support, we should remove it from
newest releases only.

Thanks,

On Thu, Oct 1, 2015 at 1:10 AM, Mike Scherbakov 
wrote:

> Hi team,
> where do we stand with it now? I remember there was a plan to remove
> nova-network support in 7.0, but we've delayed it due to vcenter/dvr or
> something which was not ready for it.
>
> Can we delete it now? The early in the cycle we do it, the easier it will
> be.
>
> Thanks!
> --
> Mike Scherbakov
> #mihgen
>
> __
> 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] [Fuel] Remove nova-network as a deployment option in Fuel?

2015-10-01 Thread Sergii Golovatiuk 
Hi,

Can we get the latest supported release version? We will remove from
nailgun after End of Life of that particular release...


--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
__
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] [Fuel] Remove nova-network as a deployment option in Fuel?

2015-09-30 Thread Mike Scherbakov 
Hi team,
where do we stand with it now? I remember there was a plan to remove
nova-network support in 7.0, but we've delayed it due to vcenter/dvr or
something which was not ready for it.

Can we delete it now? The early in the cycle we do it, the easier it will
be.

Thanks!
-- 
Mike Scherbakov
#mihgen
__
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