I do not understand why I have in the dashboard (Web Application) all instances with the private network IP addresses, not public? Configuration 2 PC with 2 network cards and the configuration was done with "OpenStack Beginner's Guide for Ubuntu 4.11 installation. Logically, we should have, at minimum, the public addresses.
Do you have an idea? Thank you.
For more information, see the screenshots :
https://docs.google.com/viewer?a=v&pid=explorer&chrome=true&srcid=0B6UEJFMrvusLMWVjNDE3NmMtNDAzZC00ZDhlLThiMWItZTcxMTIzY2I0ZmFk&hl=en_US (https://docs.google.com/viewer?a=v&pi...)
Nova only assigns a private IP when instances are created. If you want to give an instance a public IP, you have to do so manually using the commands:
euca-allocate-address euca-associate-address
Also see:
http://docs.openstack.org/cactus/openstack-compute/admin/content/allocating-associating-ip-addresses.html (http://docs.openstack.org/cactus/open...) http://docs.openstack.org/cactus/openstack-compute/admin/content/associating-public-ip.html (http://docs.openstack.org/cactus/open...)
Hope this helps, Everett
On Wed, Jun 1, 2011 at 7:25 AM, Laurent Borensky < question159849@answers.launchpad.net > wrote:
Question #159849 on OpenStack Compute (nova) changed: https://answers.launchpad.net/nova/+question/159849 (https://answers.launchpad.net/nova/+q...)
Laurent Borensky posted a new comment: I do not understand why I have in the dashboard (Web Application) all instances with the private network IP addresses, not public? Configuration 2 PC with 2 network cards and the configuration was done with "OpenStack Beginner's Guide for Ubuntu 4.11 installation. Logically, we should have, at minimum, the public addresses.
Do you have an idea? Thank you.
For more information, see the screenshots :
https://docs.google.com/viewer?a=v&pid=explorer&chrome=true&srcid=0B6UEJFMrvusLMWVjNDE3NmMtNDAzZC00ZDhlLThiMWItZTcxMTIzY2I0ZmFk&hl=en_US (https://docs.google.com/viewer?a=v&pi...)
You received this question notification because you are an answer contact for OpenStack Compute (nova).
Thank you Everett,
OK, this is because, for my virtual machines are created, but they do not start (image problem). The problem is there.
I am trying to run openstack compute on two nodes(One controller and one compute) , using this guide http://nova.openstack.org/2011.1/adminguide/multi.node.install.html (http://nova.openstack.org/2011.1/admi...) and http://docs.openstack.org/bexar/openstack-compute/admin/content/ch03s03.html#d5e340 (http://docs.openstack.org/bexar/opens...) . I have started my instances and I go from launching ---> networking , but never get to running state. No Ip address get allocated to any of the instances. I have the network flag configured to flat manager .If I run nova-manage floating list . Nothing is returned. Can some one help me?
Hi,
1) It is better to use the latest release Cactus or the first release of Diablo (d1). 2) Choose a hypervisor based on the characteristics of the physical server, or qemu or KVM. 3) Check the file "nova.conf" and the initial reservations of IP addresses private and public. 4) If you are using a good image (eg: 32 or 64 bits to 64 bits OS nova-compute), there will be no problem at launch. You must have a log file "console.log" in "/var/lib/nova/instances /..." which shows traces of boot. 5) Search in other Q&A of launcpad, a procedure for recording glance through the good images (eg: uec-publish-tarball), 6) Etc.
However, the reasons may be varied and must proceed methodically. The tutorials provided are valid (eg OpenStack Beginner's Guide for Ubuntu 11.04 / Installation & Configuration).
Regards,
Asked: 2011-06-01 07:53:30 -0500
Seen: 107 times
Last updated: Jun 28 '11
