networking through openstack installed on vm

Posted by Mandar Katdare on Server Fault See other posts from Server Fault or by Mandar Katdare
Published on 2012-06-22T08:08:04Z Indexed on 2012/06/22 9:17 UTC
Read the original article Hit count: 667

I am trying to set up a test installation of Openstack on a Ubuntu 12.04 VM running on a ESXi server. So far I have been able to launch the VMs on the ESXi, however am unable to assign IP addresses to them. As the VM with the Openstack installation has a single public IP, I wish to assign IPs to the VMs create through Openstack so that they can directly interact with the public network itself without having a separate private network. So I feel that bridging would not be the correct option here. But am unable to find the correct documents to go ahead with such an install.

My ifconfig looks as follows:

eth0 Link encap:Ethernet HWaddr 00:0c:29:6f:8a:d7
      inet addr:192.168.4.167 Bcast:192.168.4.255 Mask:255.255.255.0
      inet6 addr: fe80::20c:29ff:fe6f:8ad7/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:391640 errors:33 dropped:98 overruns:0 frame:0
      TX packets:545044 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:40303931 (40.3 MB) TX bytes:763127348 (763.1 MB)
      Interrupt:18 Base address:0x2000

lo Link encap:Local Loopback
      inet addr:127.0.0.1 Mask:255.0.0.0
      inet6 addr: ::1/128 Scope:Host
      UP LOOPBACK RUNNING MTU:16436 Metric:1
      RX packets:146127 errors:0 dropped:0 overruns:0 frame:0
      TX packets:146127 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:799815763 (799.8 MB) TX bytes:799815763 (799.8 MB)

virbr0 Link encap:Ethernet HWaddr 8a:80:33:32:63:a0
      UP BROADCAST MULTICAST MTU:1500 Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

The eth0 is the adapter that I intend to use for all communication.

My nova.conf looks as follows:

--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--allow_admin_api=true
--use_deprecated_auth=false
--auth_strategy=keystone
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
--s3_host=192.168.4.167
--ec2_host=192.168.4.167
--rabbit_host=192.168.4.167
--cc_host=192.168.4.167
--nova_url=http://192.168.4.167:8774/v1.1/
--routing_source_ip=192.168.4.167
--glance_api_servers=192.168.4.167:9292
--image_service=nova.image.glance.GlanceImageService
--iscsi_ip_prefix=192.168.4
--sql_connection=mysql://novadbadmin:[email protected]/nova
--ec2_url=http://192.168.4.167:8773/services/Cloud
--keystone_ec2_url=http://192.168.4.167:5000/v2.0/ec2tokens
--api_paste_config=/etc/nova/api-paste.ini
--libvirt_type=kvm
--libvirt_use_virtio_for_bridges=true
--start_guests_on_host_boot=true
--resume_guests_state_on_host_boot=true
--vnc_enabled=true
--vncproxy_url=http://192.168.4.167:6080
--vnc_console_proxy_url=http://192.168.4.167:6080
# network specific settings
--network_manager=nova.network.manager.FlatDHCPManager
--public_interface=eth0
--vmwareapi_host_ip=192.168.4.254
--vmwareapi_host_username=****
--vmwareapi_host_password=****
--vmwareapi_wsdl_loc=http://127.0.0.1:8080/wsdl/vim25/vimService.wsdl
--fixed_range=192.168.4.190/24
--floating_range=192.168.4.190/24
--network_size=32
--flat_network_dhcp_start=192.168.4.190
--flat_injected=False
--force_dhcp_release
--iscsi_helper=tgtadm
--connection_type=vmwareapi
--root_helper=sudo nova-rootwrap
--verbose
--libvirt_use_virtio_for_bridges
--ec2_private_dns_show
--novnc_enabled=true
--novncproxy_base_url=http://192.168.4.167:6080/vnc_auto.html
--vncserver_proxyclient_address=192.168.4.167
--vncserver_listen=192.168.4.167

192.168.4.167 is my VM with the Openstack installation and 192.168.4.254 is my ESXi server on which the VM runs.

Can anyone advice me about how to proceed?

Thanks,

Mandar

© Server Fault or respective owner

Related posts about networking

Related posts about vmware-esxi