Port flavors to novaclient from openstackx

[Jake Dahn]

Flavors needs to be implemented with novaclient instead of openstackx

[Jake Dahn (jakedahn)]

This can not be used yet, as vcpus are not in nova core, but it can be mostly implemented and stored in a branch.

[Cole Robinson (crobinso)]

I've submitted a patch for the nova side of this:

https://review.openstack.org/3197

[Anthony Young (sleepsonthefloor)]

Hey Cole thanks for helping with this. Are you planning to do any other work re openstackx? I'm also trying to eliminate the dep, and don't want to duplicate effort. Thanks again for the great work.

Sent from my Verizon Wireless Phone

----- Reply message -----
From: "Cole Robinson" <email address hidden>
Date: Thu, Jan 19, 2012 4:55 PM
Subject: [Bug 848392] Re: Port flavors to novaclient from openstackx
To: <email address hidden>

I've submitted a patch for the nova side of this:

https://review.openstack.org/3197

--
You received this bug notification because you are a bug assignee.
https://bugs.launchpad.net/bugs/848392

Title:
  Port flavors to novaclient from openstackx

Status in OpenStack Dashboard (Horizon):
  Confirmed

Bug description:
  Flavors needs to be implemented with novaclient instead of openstackx

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/848392/+subscriptions

[Cole Robinson (crobinso)]

Hi Anthony, I've been poking at the usage bits as well, which I'll probably have initial patches for later today. That looks like mostly novaclient+horizon work (plus some small nova fixes).

I haven't looked into the servers bit yet.

Just FYI my motivation is to hopefully drop the openstackx dep by essex-3 (not sure if that's overly ambitious or not), since that will be the first horizon package for fedora and I don't want to have to package an extra dep :)

[Anthony Young (sleepsonthefloor)]

Hey Cole,

That's great to hear - I'm also trying to kill the openstackx dep by e3,
and between the two of us it should be no problem.

I'm looking into the servers api issues now, and probably will have them
resolved today or tomorrow.

Are you also planning to to the novaclient work for flavors? Once that is
done, the horizon work will be trivial.

I'm curious what you've found so far with usage - what do you think needs
to be changed in nova? As I recall, the usage extension we put in nova was
more stripped down than openstackx.

A

On Fri, Jan 20, 2012 at 11:37 AM, Cole Robinson
<email address hidden>wrote:

> Hi Anthony, I've been poking at the usage bits as well, which I'll
> probably have initial patches for later today. That looks like mostly
> novaclient+horizon work (plus some small nova fixes).
>
> I haven't looked into the servers bit yet.
>
> Just FYI my motivation is to hopefully drop the openstackx dep by
> essex-3 (not sure if that's overly ambitious or not), since that will be
> the first horizon package for fedora and I don't want to have to package
> an extra dep :)
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/848392
>
> Title:
> Port flavors to novaclient from openstackx
>
> Status in OpenStack Dashboard (Horizon):
> Confirmed
>
> Bug description:
> Flavors needs to be implemented with novaclient instead of openstackx
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/horizon/+bug/848392/+subscriptions
>

[Cole Robinson (crobinso)]

Yeah I've already got novaclient+horizon work done for flavors, just waiting for the nova patch to be mostly settled before submitting.