On 1/30/2014 7:10 AM, Christopher Yeoh wrote:
On Thu, Jan 30, 2014 at 2:08 PM, Michael Still mi...@stillhq.com
mailto:mi...@stillhq.com wrote:
On Thu, Jan 30, 2014 at 2:29 PM, Christopher Yeoh cbky...@gmail.com
mailto:cbky...@gmail.com wrote:
So if nova-network doesn't go away
Tasks which we've identified need to be done:
1) Convert existing networks
2) Convert existing port allocations
3) Convert existing security groups
4) Convert existing security rules
5) Convert existing floating IP allocations
Additional tasks:
6) Create routers for each network, where
Applicable Blueprints:
https://blueprints.launchpad.net/neutron/+spec/nova-to-quantum-upgrade
https://blueprints.launchpad.net/nova/+spec/deprecate-nova-network
https://blueprints.launchpad.net/neutron/+spec/nova-network-to-neutron-recipes
Previous Discussions that relate:
On Thu, Jan 30, 2014 at 2:08 PM, Michael Still mi...@stillhq.com wrote:
On Thu, Jan 30, 2014 at 2:29 PM, Christopher Yeoh cbky...@gmail.com
wrote:
So if nova-network doesn't go away this has implications for the V3 API
as
it currently doesn't support
nova-network. I'm not sure that we
On 01/30/2014 08:10 AM, Christopher Yeoh wrote:
On Thu, Jan 30, 2014 at 2:08 PM, Michael Still mi...@stillhq.com
mailto:mi...@stillhq.com wrote:
On Thu, Jan 30, 2014 at 2:29 PM, Christopher Yeoh cbky...@gmail.com
mailto:cbky...@gmail.com wrote:
So if nova-network doesn't go
On 01/29/2014 05:24 PM, Kyle Mestery wrote:
On Jan 29, 2014, at 12:04 PM, Russell Bryant rbry...@redhat.com wrote:
On 01/29/2014 12:45 PM, Daniel P. Berrange wrote:
I was thinking of an upgrade path more akin to what users got when we
removed the nova volume driver, in favour of cinder.
On Fri, Jan 31, 2014 at 12:27 AM, Russell Bryant rbry...@redhat.com wrote:
On 01/30/2014 08:10 AM, Christopher Yeoh wrote:
On Thu, Jan 30, 2014 at 2:08 PM, Michael Still mi...@stillhq.com
mailto:mi...@stillhq.com wrote:
On Thu, Jan 30, 2014 at 2:29 PM, Christopher Yeoh
On 01/30/2014 09:13 AM, Christopher Yeoh wrote:
On Fri, Jan 31, 2014 at 12:27 AM, Russell Bryant rbry...@redhat.com
I can't say in any sort of confidence that I think nova-network will go
away in the foreseeable future. Yes, this has an unfortunate big impact
on our original
On 01/30/14 at 09:31am, Russell Bryant wrote:
On 01/30/2014 09:13 AM, Christopher Yeoh wrote:
On Fri, Jan 31, 2014 at 12:27 AM, Russell Bryant rbry...@redhat.com
I can't say in any sort of confidence that I think nova-network will go
away in the foreseeable future. Yes, this has an
If necessary the tasks work could be done solely as an extension, but I
would really prefer to avoid that so I'll get this ball rolling quickly.
I agree that doing it as a bolt-on to v3 would be significantly less
favorable than making it an integrated feature of the API. IMHO, if a
server
On Fri, Jan 31, 2014 at 3:21 AM, Dan Smith d...@danplanet.com wrote:
If necessary the tasks work could be done solely as an extension, but I
would really prefer to avoid that so I'll get this ball rolling quickly.
I agree that doing it as a bolt-on to v3 would be significantly less
On 1/29/2014 10:47 AM, Russell Bryant wrote:
Greetings,
A while back I mentioned that we would revisit the potential deprecation
of nova-network in Icehouse after the icehouse-2 milestone. The time
has come. :-)
First, let me recap my high level view of the blockers to deprecating
Effective immediately, I would like to unfreeze nova-network
development.
I fully support this plan, while also agreeing that Neutron is the
future of networking for OpenStack. As we have seen with recent
performance-related gate failures, we cannot continue to ignore
nova-network while the
On Wed, Jan 29, 2014 at 11:47:07AM -0500, Russell Bryant wrote:
Greetings,
A while back I mentioned that we would revisit the potential deprecation
of nova-network in Icehouse after the icehouse-2 milestone. The time
has come. :-)
First, let me recap my high level view of the blockers
On 01/29/2014 12:27 PM, Daniel P. Berrange wrote:
On Wed, Jan 29, 2014 at 11:47:07AM -0500, Russell Bryant wrote:
Greetings,
A while back I mentioned that we would revisit the potential deprecation
of nova-network in Icehouse after the icehouse-2 milestone. The time
has come. :-)
First,
On Wed, Jan 29, 2014 at 12:39:23PM -0500, Russell Bryant wrote:
On 01/29/2014 12:27 PM, Daniel P. Berrange wrote:
On Wed, Jan 29, 2014 at 11:47:07AM -0500, Russell Bryant wrote:
Greetings,
A while back I mentioned that we would revisit the potential deprecation
of nova-network in
On 1/29/14 7:39 PM, Russell Bryant rbry...@redhat.com wrote:
On 01/29/2014 12:27 PM, Daniel P. Berrange wrote:
On Wed, Jan 29, 2014 at 11:47:07AM -0500, Russell Bryant wrote:
Greetings,
A while back I mentioned that we would revisit the potential
deprecation
of nova-network in Icehouse
On 01/29/2014 12:45 PM, Daniel P. Berrange wrote:
I was thinking of an upgrade path more akin to what users got when we
removed the nova volume driver, in favour of cinder.
https://wiki.openstack.org/wiki/MigrateToCinder
ie no guest visible downtime / interuption of service, nor running
I was thinking for the upgrade process that we could leverage the port
attach/detach BP done by Dan Smith a while ago. This has libvirt support
and there are patches pending approval for Xen and Vmware. Not sure about
the other drivers.
If the guest can deal with the fact that the nova port
To: Daniel P. Berrange
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova][Neutron] nova-network in Icehouse and
beyond
On 01/29/2014 12:45 PM, Daniel P. Berrange wrote:
I was thinking of an upgrade path more akin to what users got when we
On Jan 29, 2014, at 10:45 AM, Dan Smith d...@danplanet.com wrote:
I was thinking for the upgrade process that we could leverage the port
attach/detach BP done by Dan Smith a while ago. This has libvirt support
and there are patches pending approval for Xen and Vmware. Not sure about
the
On 01/29/2014 11:34 PM, Russell Bryant wrote:
[. . .]
There's a bit of a bigger set of questions here, too ...
Should nova-network *ever* go away? Or will there always just be a
choice between the basic/legacy nova-network option, and the new fancy
SDN-enabling Neutron option? Is the
On 01/29/2014 04:20 PM, Kashyap Chamarthy wrote:
On 01/29/2014 11:34 PM, Russell Bryant wrote:
[. . .]
There's a bit of a bigger set of questions here, too ...
Should nova-network *ever* go away? Or will there always just be a
choice between the basic/legacy nova-network option, and the
On Jan 29, 2014, at 12:04 PM, Russell Bryant rbry...@redhat.com wrote:
On 01/29/2014 12:45 PM, Daniel P. Berrange wrote:
I was thinking of an upgrade path more akin to what users got when we
removed the nova volume driver, in favour of cinder.
On Thu, Jan 30, 2014 at 4:34 AM, Russell Bryant rbry...@redhat.com wrote:
On 01/29/2014 12:45 PM, Daniel P. Berrange wrote:
I was thinking of an upgrade path more akin to what users got when we
removed the nova volume driver, in favour of cinder.
On Thu, Jan 30, 2014 at 2:29 PM, Christopher Yeoh cbky...@gmail.com wrote:
So if nova-network doesn't go away this has implications for the V3 API as
it currently doesn't support
nova-network. I'm not sure that we have time to add support for it in
icehouse now, but if nova-network is
not
: [openstack-dev] [Nova][Neutron] nova-network in Icehouse
and beyond
On 01/29/2014 12:45 PM, Daniel P. Berrange wrote:
I was thinking of an upgrade path more akin to what users got when we
removed the nova volume driver, in favour of cinder.
https://wiki.openstack.org/wiki/MigrateToCinder
On 29 January 2014 23:13, Vishvananda Ishaya vishvana...@gmail.com wrote:
I see the process as going something like this:
* Migrate network data from nova into neutron
* Turn off nova-network on the node
* Run the neutron l3 agent and trigger it to create the required bridges
etc.
* Use
28 matches
Mail list logo
