openstack team mailing list archive

[Jimmy Tsai <cmingt@xxxxxxxxx>]

Hi Meena,

Thanks for your reply, this solve my third question. :D
Wait for someone who could help with the First 2 questions.
how to change the IP address after instance has launched and get an address
from dnsmasq ?
and how to bind a loopback IP address (lo:0) or an alias IP address
(eth0:0) ?

I just started to test Quantum + Melange, don't know if it helps with my
questions.

Thanks,
-Jimmy

2012/4/26 <raja.meena@xxxxxxxxx>

>  Hi ,****
>
> ** **
>
> This link should help you on the multinic feature .****
>
> ** **
>
>
> http://docs.openstack.org/trunk/openstack-compute/admin/content/using-multi-nics.html#using-multiple-nics-usage
> ****
>
> ** **
>
> ** **
>
> ** **
>
> Thanks****
>
> Meena Raja****
>
> ** **
>
> ** **
>
> *From:* openstack-bounces+raja.meena=wipro.com@xxxxxxxxxxxxxxxxxxx[mailto:
> openstack-bounces+raja.meena=wipro.com@xxxxxxxxxxxxxxxxxxx] *On Behalf Of
> *Jimmy Tsai
> *Sent:* Thursday, April 26, 2012 2:52 PM
> *To:* openstack@xxxxxxxxxxxxxxxxxxx; Jimmy
> *Subject:* [Openstack] questions about IP addressing and network config***
> *
>
> ** **
>
> Hi everyone,****
>
>  ****
>
> I'm running with Essex 2012.1, ****
>
> and have some questions about the nova network operation, ****
>
>  ****
>
> 1. Is it possible manually assigned IP address to a launched instance, my
> situation is :****
>
> after instance boot up (OS: CentOS 6.2), I changed the
> /etc/sysconfig/network-scripts/ifcfg-eth0 setting ****
>
> from dhcp to static (the same subnet as created by command : nova-manage
> create network....), and restart the network service, ****
>
> And then I couldn't ssh or ping the instance from other server with the
> same subnet.****
>
> What is the problem ?  I checked the iptables policies on the compute
> host, and find nothing about the DROP packets.
> I also tried to change the DB record from nova.fixed_ips table and
> libvirt.xml of the instance directory, then reboot the instance, I can see
> the instance get new IP from DHCP, but still not worked(can't ping & ssh).
> ****
>
> I used FlatDHCP  as my network manager.****
>
>  ****
>
> 2. According to the first question, I have another requirement to set up a
> loopback IP address (lo:0) on the running instance, after setting
> completed,I couldn't ping or ssh the loopback IP from the same subnet, and
> I tried to set a alias IP address with eth0:0, but still not get worked.**
> **
>
> Any ideas with this ?****
>
>  ****
>
> 3. Is there any way to use 2 NICs with different subnets on instances? I
> want to separate the network traffic.  ****
>
> Now I'm running with one bridged interface (br100), and it works well.  In
> order to backup the large log files,****
>
> I'm planing to use 2 NICs for the compute hosts, I want use 2 vNICs on
> instance, one for web service and the other for log backup,****
>
> I think I should create a new network for the second bridged interface,
> but I can't find any document to guild me.****
>
>  ****
>
> List my nova.conf below ****
>
> ==========================================****
>
> --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=172.19.7.1****
>
> --ec2_host=172.19.7.1****
>
> --rabbit_host=172.19.7.1****
>
> --cc_host=172.19.7.1****
>
> --nova_url=http://172.19.7.1:8774/v1.1/****
>
>  #--routing_source_ip=172.19.7.1****
>
> --glance_api_servers=172.19.7.1:9292****
>
>  --image_service=nova.image.glance.GlanceImageService****
>
> #--iscsi_ip_prefix=192.168.22****
>
> --sql_connection=mysql://nova:nova@172.19.7.1/nova****
>
>  --ec2_url=http://172.19.7.1:8773/services/Cloud ****
>
> --keystone_ec2_url=http://172.19.7.1: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****
>
> --novnc_enabled=true****
>
> #--vncproxy_url=http://172.19.7.1:6080/vnc_auto.html****
>
>  ****
>
>  #--vnc_console_proxy_url=http://172.19.7.1:6080****
>
>  --novncproxy_base_url=http://172.19.7.1:6080/vnc_auto.html****
>
>  --xvpvncproxy_base_url=http://172.19.7.1:6081/console****
>
>  #--vncserver_listen=172.19.7.1****
>
> #--vncserver_proxyclient_address=172.19.7.1****
>
> --vncserver_listen=0.0.0.0****
>
> --vncserver_proxyclient_address=0.0.0.0****
>
>  ****
>
> # network specific settings ****
>
> --network_manager=nova.network.manager.FlatDHCPManager****
>
> #--network_manager=nova.network.quantum.manager.QuantumManager****
>
> #--quantum_connection_host=172.19.7.1****
>
> #--quantum_connection_port=9696****
>
> --public_interface=eth0****
>
> --flat_interface=eth0****
>
> --flat_network_bridge=br100****
>
> --fixed_range=172.19.7.0/24****
>
>  --network_size=254****
>
> --flat_network_dhcp_start=172.19.7.41****
>
> --multi_host****
>
> --flat_injected=False****
>
> --force_dhcp_release****
>
> --iscsi_helper=tgtadm****
>
> --connection_type=libvirt****
>
> --root_helper=sudo nova-rootwrap****
>
> #--verbose****
>
> #--verbose=true****
>
> --verbose=false****
>
> --libvirt_xml_template=/usr/share/pyshared/nova/virt/libvirt.xml.template*
> ***
>
> --allow_resize_to_same_host=true****
>
> --max_cores=30****
>
> =================================================****
>
>  ****
> if I misunderstand something, please correct me, thanks.****
>
>  ****
>
> -Jimmy****
>
> * Please do not print this email unless it is absolutely necessary. *****
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>
> www.wipro.com
>