Re: [Openstack] Multi host nova-networking and local DNS resolving
Ok, thanks. But how I can configure the external DNS ? Should I manually set it ? Doude. On Fri, Oct 5, 2012 at 9:44 PM, Gui Maluf guimal...@gmail.com wrote: I think it's true. Maybe you will have to setup some external dns if you want resolution between hosts. On Thu, Oct 4, 2012 at 4:51 AM, Doude doudou...@gmail.com wrote: Hi all, I saw this question : https://answers.launchpad.net/nova/+question/197603 Is it still true ? If yes, which workaround is possible ? Regards, Doude. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- *guilherme* \n \tab *maluf* ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Multi host nova-networking and local DNS resolving
Hi all, I saw this question : https://answers.launchpad.net/nova/+question/197603 Is it still true ? If yes, which workaround is possible ? Regards, Doude. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Fail to reboot VM with Nova + Quantum/OVS
When I try reboot a VM, the nova-compute fails and the daemon stop. It fails on unpluging VIF interface of the rebooted VM. I use Nova with Quantum and OVS. 2012-03-01 18:12:31 DEBUG nova.rpc.common [-] Making asynchronous call on network ... from (pid=21485) multicall /usr/local/src/nova/nova/rpc/amqp.py:318 2012-03-01 18:12:31 DEBUG nova.rpc.common [-] MSG_ID is b77f0f284af045f396b90fddd16f724e from (pid=21485) multicall /usr/local/src/nova/nova/rpc/amqp.py:321 2012-03-01 18:12:33 DEBUG nova.utils [-] Running cmd (subprocess): sudo nova-rootwrap ovs-vsctl del-port br-int tap9f5ef54c-38 from (pid=21485) execute /usr/local/src/nova/nova/utils.py:208 2012-03-01 18:12:33 DEBUG nova.utils [-] Running cmd (subprocess): sudo nova-rootwrap ip link delete tap9f5ef54c-38 from (pid=21485) execute /usr/local/src/nova/nova/utils.py:208 2012-03-01 18:12:34 DEBUG nova.utils [-] Running cmd (subprocess): sudo nova-rootwrap ovs-vsctl del-port br-int tap285c8465-dd from (pid=21485) execute /usr/local/src/nova/nova/utils.py:208 2012-03-01 18:12:34 DEBUG nova.utils [-] Running cmd (subprocess): sudo nova-rootwrap ip link delete tap285c8465-dd from (pid=21485) execute /usr/local/src/nova/nova/utils.py:208 2012-03-01 18:12:34 DEBUG nova.utils [-] Attempting to grab semaphore iptables for method apply... from (pid=21485) inner /usr/local/src/nova/nova/utils.py:824 2012-03-01 18:12:34 DEBUG nova.utils [-] Got semaphore iptables for method apply... from (pid=21485) inner /usr/local/src/nova/nova/utils.py:828 2012-03-01 18:12:34 DEBUG nova.utils [-] Attempting to grab file lock iptables for method apply... from (pid=21485) inner /usr/local/src/nova/nova/utils.py:832 2012-03-01 18:12:34 DEBUG nova.utils [-] Got file lock iptables for method apply... from (pid=21485) inner /usr/local/src/nova/nova/utils.py:839 2012-03-01 18:12:34 DEBUG nova.utils [-] Running cmd (subprocess): sudo nova-rootwrap iptables-save -t filter from (pid=21485) execute /usr/local/src/nova/nova/utils.py:208 2012-03-01 18:12:35 INFO nova.virt.libvirt.connection [-] [instance: 9300df8d-1a47-40ce-b90e-28f1a84f064d] Instance destroyed successfully. 2012-03-01 18:12:35 DEBUG nova.utils [-] Running cmd (subprocess): sudo nova-rootwrap iptables-restore from (pid=21485) execute /usr/local/src/nova/nova/utils.py:208 2012-03-01 18:12:35 DEBUG nova.utils [-] Running cmd (subprocess): sudo nova-rootwrap iptables-save -t nat from (pid=21485) execute /usr/local/src/nova/nova/utils.py:208 2012-03-01 18:12:35 DEBUG nova.utils [-] Running cmd (subprocess): sudo nova-rootwrap iptables-restore from (pid=21485) execute /usr/local/src/nova/nova/utils.py:208 2012-03-01 18:12:35 DEBUG nova.network.linux_net [-] IPTablesManager.apply completed with success from (pid=21485) apply /usr/local/src/nova/nova/network/linux_net.py:336 2012-03-01 18:12:37 DEBUG nova.utils [-] Running cmd (subprocess): sudo nova-rootwrap ovs-vsctl del-port br-int tap9f5ef54c-38 from (pid=21485) execute /usr/local/src/nova/nova/utils.py:208 2012-03-01 18:12:37 DEBUG nova.utils [-] Result was 1 from (pid=21485) execute /usr/local/src/nova/nova/utils.py:224 2012-03-01 18:12:37 WARNING nova.virt.libvirt.vif [-] Failed while unplugging vif of instance 'instance-0002' Do you have this problem ? Regards, Doude. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Interaction between nova and melange : ip fixed not found
I made dirty fix to bypass this problem:
http://paste.openstack.org/show/5326/
Doude.
2012/2/28 Jérôme Gallard jeronimo...@gmail.com
Hi all,
I use the trunk version of Nova, Quantum (with the OVS plugin) and Melange.
I created networks, everything seems to be right.
I have two questions :
- the first VM I boot takes always a wrong IP address (for instance
172.16.0.0). However, when I boot a second VM, this one takes a good
IP (for instance 172.16.0.2). Do you know why this can happened ?
- I have an error regarding an fixed IP not found. Effectively, when I
check the nova database, the fixed_ip table is empty but as I am using
quantum and melange and their tables seems to be nicely filled. Do you
have an idea about this issue ?
This is a copy/paste of the error:
2012-02-28 10:45:53 DEBUG nova.rpc.common [-] received
{u'_context_roles': [u'admin'], u'_context_request_id':
u'req-461788a6-3570-4fa9-8620-6705eb69243c', u│··
'_context_read_deleted': u'no', u'args': {u'address': u'172.16.0.2'},
u'_context_auth_token': None, u'_context_strategy': u'noauth',
u'_context_is_admin': Tr│··
ue, u'_context_project_id': None, u'_context_timestamp':
u'2012-02-28T09:45:53.484445', u'_context_user_id': None, u'method':
u'lease_fixed_ip', u'_context_r│··
emote_address': None} from (pid=8844) _safe_log
/usr/local/src/nova/nova/rpc/common.py:144 │··
2012-02-28 10:45:53 DEBUG nova.rpc.common
[req-461788a6-3570-4fa9-8620-6705eb69243c None None] unpacked context:
{'request_id': u'req-461788a6-3570-4fa9-8620│··
-6705eb69243c', 'user_id': None, 'roles': [u'admin'], 'timestamp':
'2012-02-28T09:45:53.484445', 'is_admin': True, 'auth_token': None,
'project_id': None, 'r│··
emote_address': None, 'read_deleted': u'no', 'strategy': u'noauth'}
from (pid=8844) unpack_context
/usr/local/src/nova/nova/rpc/amqp.py:187 │··
2012-02-28 10:45:53 DEBUG nova.network.manager
[req-461788a6-3570-4fa9-8620-6705eb69243c None None] Leased IP
|172.16.0.2| from (pid=8844) lease_fixed_ip
/us│··r/local/src/nova/nova/network/manager.py:1186 │··
2012-02-28 10:45:53 ERROR nova.rpc.common [-] Exception during message
handling │··(nova.rpc.common): TRACE: Traceback (most recent call
last): │··
(nova.rpc.common): TRACE: File /usr/local/src/nova/nova/rpc/amqp.py,
line 250, in _process_data │··(nova.rpc.common): TRACE: rval =
node_func(context=ctxt, **node_args) │··(nova.rpc.common): TRACE: File
/usr/local/src/nova/nova/network/manager.py, line 1187, in
lease_fixed_ip │··(nova.rpc.common): TRACE: fixed_ip =
self.db.fixed_ip_get_by_address(context, address) │··
(nova.rpc.common): TRACE: File /usr/local/src/nova/nova/db/api.py,
line 473, in fixed_ip_get_by_address │··(nova.rpc.common): TRACE:
return IMPL.fixed_ip_get_by_address(context, address)
│··(nova.rpc.common): TRACE: File
/usr/local/src/nova/nova/db/sqlalchemy/api.py, line 119, in wrapper
│··
(nova.rpc.common): TRACE: return f(*args, **kwargs)
│··(nova.rpc.common): TRACE: File
/usr/local/src/nova/nova/db/sqlalchemy/api.py, line 1131, in
fixed_ip_get_by_address │··
(nova.rpc.common): TRACE: raise
exception.FixedIpNotFoundForAddress(address=address) │··
(nova.rpc.common): TRACE: FixedIpNotFoundForAddress: Fixed ip not
found for address 172.16.0.2. │··
(nova.rpc.common): TRACE:
Thank you very much for your help.
Regards,
Jérôme
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Essex-3 Milestone of Quantum Available
Nice job netstackers. I've got a remark. I downloaded the Quantum archive from Quantum project Launchpad page and I untared it but I cannot find any OVS agent in the plugin directory. Does it mean it's packaged alone ? If yes, where I can find it ? Regards, Doude. On Fri, Jan 27, 2012 at 1:59 PM, Shake Chen shake.c...@gmail.com wrote: Hi Now the Qautum E3 whether work with Horizon E3? whether I can manage the Qauntum in Horizon Dashboard? On Fri, Jan 27, 2012 at 7:57 PM, Leandro Reox leandro.r...@gmail.comwrote: Excellent job guys ! Well definitely try it next week, the last release worked out pretty good so far for us. Keep up the good work! Cheers Lean On Thu, Jan 26, 2012 at 8:36 PM, Dan Wendlandt d...@nicira.com wrote: Congrats to the Quantum team! The latest + greatest version of Quantum was release this morning, see: https://launchpad.net/quantum/essex/essex-3 I delayed the announce in order to complete updating the documentation, due to the fact that install procedures changed significantly with this release. See PDF on downloads page. Changes since Essex-2 include: - client code in separate repo to simplify development dependencies on other projects. - integration with Nova Floating IPs. - API filters for efficient queries and improved API error codes (API v1.1 only) - fixes to python setup tools scripts to make life easier for distros packagers. - port packet statistics extension If you have an OpenStack distro and are looking to package Quantum for Essex, the packaging should now be in its final form. Let us know how we can help. E-3 was also the first release for which Quantum was part of the standard OpenStack build process, thanks to the CI team for all the help! Since Quantum is still in incubation, E-4 is not a feature frozen milestone, though we will shutting the door to major merges at least a week before the official milestone branch point to avoid last-minute churn. Thanks to all who contributed to E-3. Looking forward to a great E-4 milestone with lots of early merge proposals :) Dan -- ~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- 陈沙克 手机：13661187180 msn：shake.c...@hotmail.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Libvirt block live migration with OpenStack Diablo
Hi Kei, I use the Diablo release of openStack and I didn't change anything in the libvirt XML template. I can saw a difference for the console file. The trunk version of Nova use a file for the logging console but the Diablo Release use a pipe. Can I change it manually ? Must I open a bur for Diablo release ? Regards, Doude. On Thu, Nov 17, 2011 at 2:23 PM, Kei.masumoto kei.masum...@gmail.com wrote: I think you should use exactly same template as below. https://github.com/openstack/nova/blob/master/nova/virt/libvirt.xml.template Kei (2011/11/17 2:41), Doude wrote: Hi all, I use OpenStack Diablo release 2011.3-0ubuntu6.2 on ubuntu 11.10 with libvirt 0.9.2-4ubuntu15.1 I try to block migrate a VM from one host to another one. OpenStack uses the 'migrateToURI' method from libvirt python library. But this call fails. Libvirt log : - Source host: 18:27:30.475: 24622: error : remoteIO:5985 : unable to set user and group to '107:118' on '/var/lib/nova/instances/instance-00b7/console.fifo.in': No such file or directory - Target host: 27:29.737: 27244: error : virSecurityDACSetOwnership:125 : unable to set user and group to '107:118' on '/var/lib/nova/instances/instance-00b7/console.fifo.in': No such file or directory 18:27:29.917: 27244: error : virSecurityDACRestoreSecurityFileLabel:143 : cannot resolve symlink /var/lib/nova/instances/instance-00b7/console.fifo.out: No such file or directory So the migration fails. VM disks are transfered to the target host but console files aren't. XML file of domain: domain type='kvm' nameinstance-00b7/name memory2097152/memory os typehvm/type boot dev=hd / /os features acpi/ /features vcpu2/vcpu devices disk type='file' driver type='qcow2'/ source file='/var/lib/nova/instances/instance-00b7/disk'/ target dev='vda' bus='virtio'/ /disk disk type='file' driver type='qcow2'/ source file='/var/lib/nova/instances/instance-00b7/disk.local'/ target dev='vdb' bus='virtio'/ /disk interface type='bridge' source bridge='br102'/ mac address='02:16:3e:36:c4:70'/ model type='virtio'/ filterref filter=nova-instance-instance-00b7-02163e36c470 parameter name=IP value=172.16.2.3 / parameter name=DHCPSERVER value=172.16.2.1 / /filterref /interface !-- The order is significant here. File must be defined first -- serial type=pipe source path='/var/lib/nova/instances/instance-00b7/console.fifo'/ target port='1'/ /serial console type='pty' tty='/dev/pts/2' source path='/dev/pts/2'/ target port='0'/ /console serial type='pty' source path='/dev/pts/2'/ target port='0'/ /serial graphics type='vnc' port='-1' autoport='yes' keymap='fr' listen='0.0.0.0'/ /devices /domain Could you help me ? Regards, Doude. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Libvirt block live migration with OpenStack Diablo
Hi all, I use OpenStack Diablo release 2011.3-0ubuntu6.2 on ubuntu 11.10 with libvirt 0.9.2-4ubuntu15.1 I try to block migrate a VM from one host to another one. OpenStack uses the 'migrateToURI' method from libvirt python library. But this call fails. Libvirt log : - Source host: 18:27:30.475: 24622: error : remoteIO:5985 : unable to set user and group to '107:118' on '/var/lib/nova/instances/instance-00b7/console.fifo.in': No such file or directory - Target host: 27:29.737: 27244: error : virSecurityDACSetOwnership:125 : unable to set user and group to '107:118' on '/var/lib/nova/instances/instance-00b7/console.fifo.in': No such file or directory 18:27:29.917: 27244: error : virSecurityDACRestoreSecurityFileLabel:143 : cannot resolve symlink /var/lib/nova/instances/instance-00b7/console.fifo.out: No such file or directory So the migration fails. VM disks are transfered to the target host but console files aren't. XML file of domain: domain type='kvm' nameinstance-00b7/name memory2097152/memory os typehvm/type boot dev=hd / /os features acpi/ /features vcpu2/vcpu devices disk type='file' driver type='qcow2'/ source file='/var/lib/nova/instances/instance-00b7/disk'/ target dev='vda' bus='virtio'/ /disk disk type='file' driver type='qcow2'/ source file='/var/lib/nova/instances/instance-00b7/disk.local'/ target dev='vdb' bus='virtio'/ /disk interface type='bridge' source bridge='br102'/ mac address='02:16:3e:36:c4:70'/ model type='virtio'/ filterref filter=nova-instance-instance-00b7-02163e36c470 parameter name=IP value=172.16.2.3 / parameter name=DHCPSERVER value=172.16.2.1 / /filterref /interface !-- The order is significant here. File must be defined first -- serial type=pipe source path='/var/lib/nova/instances/instance-00b7/console.fifo'/ target port='1'/ /serial console type='pty' tty='/dev/pts/2' source path='/dev/pts/2'/ target port='0'/ /console serial type='pty' source path='/dev/pts/2'/ target port='0'/ /serial graphics type='vnc' port='-1' autoport='yes' keymap='fr' listen='0.0.0.0'/ /devices /domain Could you help me ? Regards, Doude. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OSAPI and Zones
Thanks a lot for your answers. But why do you want to move the Zone code into the extension part ? It's a core part of OpenStack, why it doesn't stay in the core code ? Another question about extensions. I had understand that an extension will be integrated to the core OSAPI when it will be mature, is that true ? The extension mechanism is like an incubator for OSAPI functionalities ? Regards, Édouard. On Mon, Nov 14, 2011 at 7:09 PM, Sandy Walsh sandy.wa...@rackspace.com wrote: Jorge is correct. The zones stuff was added before the API was finalized and before the extensions mechanism was in place. We simply haven't taken the time to convert it yet. -S From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of Anne Gentle [a...@openstack.org] Sent: Monday, November 14, 2011 12:25 PM To: Doude Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] OSAPI and Zones Hi Édouard - I believe zones are documented in the Developer docs in http://nova.openstack.org/devref/zone.html. The howto scenarios are documented using the nova python client only currently (probably due to the refactoring Jorge mentions). When you run into these gaps, please do log a bug against either nova or openstack-manuals (http://bugs.launchpad.net/openstack-manuals). The nova-docs team is small and working through a backlog of such items, and bugs definitely help with prioritization and tracking. Thanks, Anne On Mon, Nov 14, 2011 at 9:49 AM, Doude doudou...@gmail.com wrote: Hi all, I'm trying to understand the multi-zone architecture of OpenStack. I saw zone commands (list, show, select ...) have been added to the OSAPI v1.1 (not as an extension but as a core component of the API) but I cannot find any documentations in the OSAPI book: http://docs.openstack.org/trunk/openstack-compute/developer/openstack-compute-api-1.1/content/ Where I can find this documentation ? In OpenStack wiki ? Where I can open a bug about this lack of documentation ? Regards, Édouard. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] OSAPI and Zones
Hi all, I'm trying to understand the multi-zone architecture of OpenStack. I saw zone commands (list, show, select ...) have been added to the OSAPI v1.1 (not as an extension but as a core component of the API) but I cannot find any documentations in the OSAPI book: http://docs.openstack.org/trunk/openstack-compute/developer/openstack-compute-api-1.1/content/ Where I can find this documentation ? In OpenStack wiki ? Where I can open a bug about this lack of documentation ? Regards, Édouard. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] How to use glance and nova-manage in command with keystone
Hi,
I've got an issue with CLI Glance and Keystone authentication.
I try the above method with env variables, but I get this error:
# glance -d index
Traceback (most recent call last):
File /usr/bin/glance, line 1206, in module
result = command(options, args)
File /usr/bin/glance, line 60, in wrapper
ret = func(*args, **kwargs)
File /usr/bin/glance, line 497, in images_index
print_header=True)
File /usr/bin/glance, line 443, in _images_index
images = client.get_images(**parameters)
File /usr/lib/python2.7/dist-packages/glance/client.py, line 53,
in get_images
res = self.do_request(GET, /images, params=params)
File /usr/lib/python2.7/dist-packages/glance/common/client.py,
line 136, in do_request
self._authenticate()
File /usr/lib/python2.7/dist-packages/glance/common/client.py,
line 123, in _authenticate
auth_plugin.authenticate()
File /usr/lib/python2.7/dist-packages/glance/common/auth.py, line
103, in authenticate
_authenticate(auth_url)
File /usr/lib/python2.7/dist-packages/glance/common/auth.py, line
91, in _authenticate
self._v2_auth(token_url)
File /usr/lib/python2.7/dist-packages/glance/common/auth.py, line
180, in _v2_auth
raise Exception(_('Unexpected response: %s') % resp.status)
Exception: Unexpected response: 400
And if I set the token to the glance CLI command, it works:
# glance -A 999888777666 index
ID Name Disk Format
Container Format Size
--
--
5Debian stable 6.0.2.1 AMD64 ne iso
bare 176160768
3OpenSIPs AMI ami
ami 1326645248
2Ubuntu natty kernelaki
aki 4592896
1Ubuntu 11.04 server amd64 qcow2
bare 1040449536
Can you help me ?
Doude.
2011/10/10 Vishvananda Ishaya vishvana...@gmail.com:
It looks like if you change your authurl to port 35357 in your glancerc that
you can use glance index without passing in the auth key.
On Oct 9, 2011, at 5:45 PM, Jae Sang Lee wrote:
Hi,
This is my glance and nova-client rc. Change User, Key value for your
configuration.
glancerc:
export OS_AUTH_USER=admin
export OS_AUTH_KEY=secrete
export OS_AUTH_TENANT=demo
export OS_AUTH_URL=192.168.0.151:5000/v2.0/ --- Keystone IP
export OS_AUTH_STRATEGY=keystone
testrc: (different with novarc from nova-manage)
export NOVA_URL=http://localhost:35357/v2.0/; --- Keystone IP
export NOVA_VERSION=1.1
export NOVA_API_KEY=secrete
export NOVA_USERNAME=admin
export NOVA_PROJECT_ID=demo
export NOVA_REGION_NAME=RegionOne
for example,
-glance-
root@nova151:~# glance index
Not authorized to make this request. Check your credentials (OS_AUTH_USER,
OS_AUTH_KEY, ...).
root@nova151:~# cat glancerc
export OS_AUTH_USER=admin
export OS_AUTH_KEY=secrete
export OS_AUTH_TENANT=demo
export OS_AUTH_URL=192.168.0.151:5000/v2.0/
export OS_AUTH_STRATEGY=keystone
root@nova151:~# . glancerc
root@nova151:~# glance -A 999888777666 index -- add your service token -A
ID Name Disk Format
Container Format Size
--
--
13 ubuntu-apm ami
ami 1071644672
12 initrd-ubuntu-apm ari
ari 4005981
11 vmlinuz-ubuntu-apm aki
aki 4107552
10 ubuntu ami
ami 524288000
9initrd ari
ari 7988037
8vmlinuzaki
aki 4099360
-nova-
root@nova151:~# nova list
You must provide a username, eithervia --username or via env[NOVA_USERNAME]
root@nova151:~# cat testrc
export NOVA_URL=http://localhost:35357/v2.0/;
export NOVA_VERSION=1.1
export NOVA_API_KEY=secrete
export NOVA_USERNAME=admin
export NOVA_PROJECT_ID=demo
export NOVA_REGION_NAME=RegionOne
root@nova151:~# . testrc
root@nova151:~# nova list
++---++--+
| ID | Name | Status | Networks |
++---++--+
| 6 | rose | ACTIVE | private=10.0.0.7 |
| 9 | lilly | ACTIVE | private=10.0.0.8 |
++---++--+
If you want to know exact information, try to see keystone db.
2011/10/10 mao weijie mwjpi...@gmail.com
Hi,
I used devstack to install openstack and it work well with dashboard. But
now I want to use command(glance or nova-manage), it tells me
that credentials problem. Does anyone use dashboard with keystone and also
use command in terminal?
非淡泊無以明志，非寧靜無以致遠
Re: [Openstack] nova-compute is unable to contact the metadata server
Hi, Which network mode do you use ? I think I get the same problem in VLAN network mode. Can you check your 'nova-api' logs ? The DNAT rule in pre-routing table change the destination of meta data packets but SNAT rule in post routing table change the source IP of all outgoing traffic. So, the meta data handler cannot identify the origin of the meta data request. The flag 'use_forwarded_for' permit to use the HTTP header field 'X-Forwarded-For' tio identify the IP source of the meta data request. But I don't know how configure 'cloud-init' to set this HTTP header ? Doude. On Sun, Oct 2, 2011 at 8:01 PM, Jesse Andrews anotherje...@gmail.comwrote: If the request isn't coming into the nova-api then I recommend checking the network path using tcpdump (or wireshark - there is a curses version). As you can see it tries 100 times to hit the metadata server so you should see traffic every couple seconds On Sat, Oct 1, 2011 at 1:59 PM, Shashank Sahni shredde...@linuxers.org wrote: Hi everyone, I'm working on a single node installation of openstack(for testing). I'm using ubuntu uec images and am successfully able to boot them. But unfortunately, I get the error DataSourceEc2.py[WARNING]: 20:07:30 [17/100]: url error [[Errno 101] Network is unreachable] at the end of euca-get-console-output. I believe that is the reason why I'm not able to either ping or ssh into the instance. There already exists a pre-routing rule to redirect all the communication from 169.254.169.254:80 to nova-api:8773. -A nova-network-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination 10.2.4.135:8773 Any suggestions? Regards, Shashank Sahni ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Host filter - Instance Type Filter with virt layer Libvirt
Hi,
I try to add code to the Libvirt layer to enable the Instance Type Filter
needed by the zone aware scheduler.
I looked the code of fake virt layer which implement that. The table
‘host_status’ in class ‘FakeConnection’ contains all capabilities of the
host:
self.host_status = {
'host_name-description': 'Fake Host',
'host_hostname': 'fake-mini',
'host_memory_total': 80,
'host_memory_overhead': 1000,
'host_memory_free': 79,
'host_memory_free_computed': 79,
'host_other_config': {},
'host_ip_address': '192.168.1.109',
'host_cpu_info': {},
'disk_available': 5000,
'disk_total': 6000,
'disk_used': 1000,
'host_uuid': 'cedb9b39-9388-41df-8891-c5c9a0c0fe5f',
'host_name_label': 'fake-mini'
}
Nothing explain what corresponding each elements of this table and what unit
use. I suppose, the unit is bytes for disk and memory.
And in the code of the host filtering in the scheduler
(nova/scheduler/host_filter.py method class ‘InstanceTypeFilter’ method
‘host_filtrer’), the scheduler compares the host capabilities with specified
resources of the instance to determined which host can support it. But
specified resources of the instance is in Mbytes for memory and Gbytes for
the disk. Is it normal ?
Doude.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
