← Back to team overview

openstack team mailing list archive

Re: Flavor change in Essex?

 

It sounds like we need to update the cli to reflect this
disk-configuration-parity change.  It is also likely that some nova-api
work will need to be done to get this humming.
https://bugs.launchpad.net/nova/+bug/932423

On Tue, Feb 14, 2012 at 1:57 PM, Jesse Andrews <anotherjesse@xxxxxxxxx>wrote:

> Deliberate change.
>
> It used to be that KVM and XS did different things as far as disk
> partitioning.
>
> https://blueprints.launchpad.net/nova/+spec/disk-configuration-parity
>
> Now a flavor can specify the root vs ephemeral partition size
> independently instead of being decided by choice of hypervisor.
>
> Jesse
>
> On Tue, Feb 14, 2012 at 1:47 PM, David Kranz <david.kranz@xxxxxxxxxx>
> wrote:
> > In tracking down a problem with the tempest flavors test I noticed that
> > 'nova flavor-list' returns this in Essex:
> >
> > +----+-----------+-----------+------+----------+-------+-------------+
> > | ID |    Name   | Memory_MB | Swap | Local_GB | VCPUs | RXTX_Factor |
> > +----+-----------+-----------+------+----------+-------+-------------+
> > | 1  | m1.tiny   | 512       |      | 0        | 1     | 1.0         |
> > | 2  | m1.small  | 2048      |      | 10       | 1     | 1.0         |
> > | 3  | m1.medium | 4096      |      | 10       | 2     | 1.0         |
> > | 4  | m1.large  | 8192      |      | 10       | 4     | 1.0         |
> > | 5  | m1.xlarge | 16384     |      | 10       | 8     | 1.0         |
> > +----+-----------+-----------+------+----------+-------+-------------+
> >
> > and this in Diablo:
> >
> > +----+-----------+-----------+------+----------+-------+-------------+
> > | ID |    Name   | Memory_MB | Swap | Local_GB | VCPUs | RXTX_Factor |
> > +----+-----------+-----------+------+----------+-------+-------------+
> > | 1  | m1.tiny   | 512       | 0    | 0        | 1     |             |
> > | 2  | m1.small  | 2048      | 0    | 20       | 1     |             |
> > | 3  | m1.medium | 4096      | 0    | 40       | 2     |             |
> > | 4  | m1.large  | 8192      | 0    | 80       | 4     |             |
> > | 5  | m1.xlarge | 16384     | 0    | 160      | 8     |             |
> > +----+-----------+-----------+------+----------+-------+-------------+
> >
> > Note that Local_GB changed from 0,20,40,80,160 to 0,10,10,10,10. These
> > values are coming straight from the API call.
> > Is this a bug or a deliberate change?
> >
> >  -David
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~openstack
> > Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~openstack
> > More help   : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>

References