[openstack-dev] [nova][database] Update compute_nodes table

Abbass MAROUNI abbass.marouni at virtualscale.fr
Tue Dec 3 08:54:28 UTC 2013


I am aware of this work, in fact I reused a column (pci_stats) in the
compute_nodes table to store a JSON blob.
I track the resource in the resource_tracker and update the column and then
use the blob in a filter.
Maybe I should reformulate my question, How can I add a column to the table
and use it in resource_tracker without breaking something ?

Best regards,


2013/12/2 <openstack-dev-request at lists.openstack.org>

>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 02 Dec 2013 12:06:21 -0500
> From: Russell Bryant <rbryant at redhat.com>
> To: openstack-dev at lists.openstack.org
> Subject: Re: [openstack-dev] [nova][database] Update compute_nodes
>         table
> Message-ID: <529CBE0D.608 at redhat.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 12/02/2013 11:47 AM, Abbass MAROUNI wrote:
> > Hello,
> >
> > I'm looking for way to a add new attribute to the compute nodes by
> >  adding a column to the compute_nodes table in nova database in order to
> > track a metric on the compute nodes and use later it in nova-scheduler.
> >
> > I checked the  sqlalchemy/migrate_repo/versions and thought about adding
> > my own upgrade then sync using nova-manage db sync.
> >
> > My question is :
> > What is the process of upgrading a table in the database ? Do I have to
> > modify or add a new variable in some class in order to associate the
> > newly added column with a variable that I can use ?
>
> Don't add this.  :-)
>
> There is work in progress to just have a column with a json blob in it
> for additional metadata like this.
>
> https://blueprints.launchpad.net/nova/+spec/extensible-resource-tracking
> https://wiki.openstack.org/wiki/ExtensibleResourceTracking
>
> --
> Russell Bryant
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131203/59e91013/attachment.html>


More information about the OpenStack-dev mailing list