Re: [Openstack] dashboard very slow + "nova list" very slow

I recall having this issue and it was either as David describes, but also try checking any environment proxy settings to see if they're interfering. Regards, Kev On 6 January 2013 01:14, Jian Hua Geng wrote: > I encountered similar issue before. The root cause is there are some > problems in m

[Openstack] Introducing the Hyper-V Quantum plugin

As part of our ongoing work to bring OpenStack to Hyper-V and Windows, after the Nova Hyper-V driver, Cinder Windows Storage driver and Cloud-Init for Windows guests we just released a Quantum plugin for Hyper-V 2008 R2 and 2012. The current initial release of the plugin supports VLAN, flat and

Re: [Openstack] cannot restart the instance

no one knows how to fix this? help me please 2012/12/31 小盆儿 > hey guys~ > > I just shutoff one of my instance . > but when I try to start it ,I got the errors like below: > > 2012-12-31 16:31:12 ERROR nova.openstack.common.rpc.amqp [-] Exception > during message handling > 2012-12-31 16:31:12 T

Re: [Openstack] cannot restart the instance

How did you shut off your instance? Are you sure you didn't terminate it? Does "nova list" or "euca-describe-instances" still show information about this instance? Nate On Jan 6, 2013 12:46 PM, "小盆儿" wrote: > no one knows how to fix this? > help me please > > > 2012/12/31 小盆儿 > >> hey guys~ >>

[Openstack] Openstack Version (Essex or Folsom)

Hi 1) How I can check which Release of Openstack I am using. 2) I want to boot instance on specific compute-node using this command nova boot --image --flavor m1.tiny --key_name mykey --availability-zone nova:server2 but its not working. What is the correct way to do this? Best Regards,

Re: [Openstack] Openstack Version (Essex or Folsom)

Hi Umar, For question 2, I suspect the compute node name is missing in the command sent by yourself. nova boot -image --flavor --key_name --availability_zone nova:computenodename name of the instance. This command works fine in OpenStack ESSEX version. Thanks Krishnaprasad From: openstack-

Re: [Openstack] Openstack Version (Essex or Folsom)

By default, this requires the admin role to launch instances on specific hosts. Nate On Jan 6, 2013 1:24 PM, "Umar Draz" wrote: > Hi > > 1) How I can check which Release of Openstack I am using. > 2) I want to boot instance on specific compute-node using this command > nova boot --image --f

Re: [Openstack] Openstack Version (Essex or Folsom)

HI Narayanan, What is this mean? http://docs.openstack.org/trunk/openstack-compute/admin/content/specify-host-to-boot-instances-on.html ? Onething what kind of configuration I should do in (controller's nova.conf and compute's nova.conf) ? Best Regards, Umar On Sun, Jan 6, 2013 at 11:34 PM,

Re: [Openstack] Openstack Version (Essex or Folsom)

I am Admin and I used this command on Controller node as root, then what else admin? Best Regards, Umar On Sun, Jan 6, 2013 at 11:40 PM, Nathanael Burton < nathanael.i.bur...@gmail.com> wrote: > By default, this requires the admin role to launch instances on specific > hosts. > > Nate > On Jan

Re: [Openstack] Openstack Version (Essex or Folsom)

On Jan 6, 2013 1:43 PM, "Umar Draz" wrote: > > I am Admin > > and I used this command on Controller node as root, then what else admin? > > Best Regards, > > Umar > Umar, The OpenStack user account that you are using to launch instances needs to have the admin role in keystone for the tenant you

Re: [Openstack] Openstack Version (Essex or Folsom)

Instance crreating is not the problem. Problem is specific compute node. Here is my bashrc export OS_TENANT_NAME="admin" export OS_USERNAME="admin" export OS_PASSWORD="mypass" export OS_AUTH_URL="http://xx.xx.xx.xx:5000/v2.0/"; export ADMIN_PASSWORD="mypass" export SERVICE_PASSWORD="mypass" export

Re: [Openstack] Openstack Version (Essex or Folsom)

Answers below. On Sun, Jan 6, 2013 at 12:22 PM, Umar Draz 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 usin

Re: [Openstack] Openstack Version (Essex or Folsom)

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| +--

Re: [Openstack] Openstack Version (Essex or Folsom)

Hi Umar, In the nova boot command, have you specified --availability-zone or --availability_zone? The correct command is --availability_zone. Can you try this and pass on the feedback? Thanks Krishnaprasad From: openstack-bounces+narayana=uni-mainz...@lists.launchpad.net [mailto:openstack-boun

Re: [Openstack] Openstack Version (Essex or Folsom)

Ah! It looks like you've changed the default availability zone for your two nodes. Host "compute1" is in AZ "compute1", host "compute2" is in AZ "compute2". What does "nova-manage service list" show? How about trying the following to boot an instance on compute2 (basically the format of the valu