openstack team mailing list archive

[Umar Draz <unix.co@xxxxxxxxx>]

Hi thanks For your awnswers.

I did everything. But nova boot not working.

nova boot --flavor 1 --image ubuntuRebel --availability-zone nova:compute1
myInstanceName
but the output is

| Property                            |
Value                                                    |
+-------------------------------------+----------------------------------------------------------+
| OS-DCF:diskConfig                   |
MANUAL                                                   |
| OS-EXT-SRV-ATTR:host                |
compute2                                                 |
| OS-EXT-SRV-ATTR:hypervisor_hostname | compute2.yourdomain.com
|
| OS-EXT-SRV-ATTR:instance_name       |
instance-0000005a                                        |
| OS-EXT-STS:power_state              |
0                                                        |
| OS-EXT-STS:task_state               |
scheduling                                               |
| OS-EXT-STS:vm_state                 | building


Here is the nova.conf file compute1

node_availability_zone=compute1

and here is the nova.conf file of compute2

node_availability_zone=compute2

I think there is bug in openstack ??

Best Regards,

Umar

On Mon, Jan 7, 2013 at 1:46 AM, Anne Gentle <anne@xxxxxxxxxxxxx> wrote:

> Answers below.
>
> On Sun, Jan 6, 2013 at 12:22 PM, Umar Draz <unix.co@xxxxxxxxx> wrote:
>
>> Hi
>>
>> 1) How I can check which Release of Openstack I am using.
>>
>
> From
> http://docs.openstack.org/trunk/openstack-compute/install/apt/content/compute-verifying-install.html
> :
>
> You can find the version of the installation by using the *nova-manage*command, as root:
>
> # nova-manage version list
>
> The version number 2012.2 corresponds with the Folsom release of Compute.
>
> 2012.2 (2012.1-LOCALBRANCH:LOCALREVISION)
>
> Here's a table showing the release names corresponding to the version
> numbers.
>
> http://docs.openstack.org/trunk/openstack-compute/install/apt/content/version.html
>
>
>> 2) I want to boot instance on specific compute-node using this command
>>     nova boot --image <uuid> --flavor m1.tiny --key_name mykey
>> --availability-zone nova:server2
>>
>
> --force_hosts no longer available in Folsom. It was available in Essex.
> There was a recent mailing list discussion about the use of policies to
> enable non-admin users to use the availability-zone param:
> https://lists.launchpad.net/openstack/msg19784.html
>
>
>
>>
>>     but its not working. What is the correct way to do this?
>>
>
> This is how it works on Essex:
>
> http://docs.openstack.org/essex/openstack-compute/admin/content/specify-host-to-boot-instances-on.html
>
>
> Hope this gets you on track.
>
> Anne
>
>
>>
>> Best Regards,
>>
>> Umar
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>


-- 
Umar Draz
Network Architect