Open Stack

Hi Chu,

You might want to check this link.

http://docs.openstack.org/trunk/openstack-network/admin/content/adv_cfg_l3_agent_multi_extnet.html

you can create multiple floating ip pools in association with different ext
nets


-Ashok


On Thu, May 23, 2013 at 10:38 AM, Chu Duc Minh <chu.ducminh at gmail.com>wrote:

> Hi, thank you for your help, but I can't follow your guides because I
> already have an external network (123.x.y.0/24)
>
> I tried some ways to add 2 floating IP(s) (belong to 2 network/subnet) to
> an instance, but still not success...
>
> Do you or others have another idea?
>
> Thank you very much!
>
>
>
>
> On Thu, May 23, 2013 at 12:40 AM, Naveen Joy (najoy) <najoy at cisco.com>wrote:
>
>>  Hi Chu,****
>>
>> ** **
>>
>> I was able to get my instances and  LAN servers communicate by following
>> the below steps. The basic idea is that you should add the external network
>> interface to br-ex,  then create an external network in quantum with
>> --router:external=True and allocate floating IPs to your instances from
>> this external network. Now your LAN servers can talk to your instances
>> using these routable floating IPs that you have allocated from the external
>> network.****
>>
>> ** **
>>
>> Steps:****
>>
>> **1.      **Create an external bridge named br-ex and add the network
>> card to that bridge. Also assign an IP on the external bridge so you can
>> manage it. Assuming eth1 is your network card.****
>>
>> sudo ovs-vsctl add-br br-ex****
>>
>> sudo ovs-vsctl add-port br-ex eth1****
>>
>> sudo ip addr add <ip/mask> dev br-ex****
>>
>> sudo ip link set br-ex up****
>>
>> ** **
>>
>> **2.      **Set eth1 as a promiscuous interface in Ubuntu with no IP
>> address so your host OS does not mess with it.****
>>
>> Edit your /etc/network/interfaces and add the below lines:****
>>
>> iface eth1 inet manual****
>>
>>     up ifconfig $IFACE 0.0.0.0 up****
>>
>>     up ifconfig $IFACE promisc****
>>
>>     down ifconfig $IFACE down****
>>
>> ****
>>
>> **3.      **Create a shared public network and subnet for your tenant
>> routers to plug in. ****
>>
>> Note that this network should be mapped to your existing LAN network and
>> you should also set an existing gateway and assign IP allocation pools.**
>> **
>>
>> quantum net-create public --shared --router:external=True
>> --provider:network_type local****
>>
>> quantum subnet-create --name public-subnet --gateway <gateway-ip>
>>  --allocation-pool start=<start-ip>,end=<end-ip> public
>> <external-LAN-subnet/mask>****
>>
>> ** **
>>
>> **4.      **Then set an external gateway IP for your tenant routers and
>> create your user nets****
>>
>> quantum router-create router1****
>>
>> quantum router-gateway-set router1 public****
>>
>> quantum net-create usernet1****
>>
>> quantum subnet-create --name subnet1 usernet1 10.0.0.0/24****
>>
>> quantum router-interface-add router1 subnet1****
>>
>> ** **
>>
>> **5.      **To enable bi-directional network communication your old LAN
>> network server farm use floating IPs. Allocate a floating IP and map it to
>> your instance port either using command line or via horizon.****
>>
>> quantum floatingip-create --port_id $SERVER_PORT_ID public****
>>
>> ** **
>>
>> Hope this helps.****
>>
>> ** **
>>
>> Naveen/****
>>
>> ** **
>>
>> ** **
>>
>> *From:* Openstack [mailto:openstack-bounces+najoy=
>> cisco.com at lists.launchpad.net] *On Behalf Of *Chu Duc Minh
>> *Sent:* Wednesday, May 22, 2013 5:04 AM
>> *To:* openstack at lists.launchpad.net
>> *Subject:* [Openstack] [Quantum & OVS] How to bi-direction communicate
>> between VM instances and "old" LAN network(s)****
>>
>> ** **
>>
>> Hi, i deployed a Openstack Grizzly cluster with Quantum using
>> network-model *"Per-tenant Routers with Private Networks"*. Everything
>> is ok. ****
>>
>> Now, i need to communicate (bi-direction) between VM network(s) and "old"
>> LAN network(s) of old server farm. (192.168.2.0/24, 192.168.3.0/24,
>> v.v...)****
>>
>> I added a network card to Network-node and plug it to a LAN network (
>> 192.168.3.0/24).
>> But still not yet figured out how i can achieve it (old server farm can
>> connect to VM instance and vice-versa) ****
>>
>> Could you help me, pls? Thanks a lot, folks!****
>>
>> *PS:* I attach my network topology in this mail for reference. ****
>>
>> I think that, maybe I need to create a new "br-ex" for LAN, create
>> port/interface in router of each tenant, then add a LAN IP (192.168.3.x) to
>> router-interface.
>> Then add route to 192.168.0.0/16 to 192.168.3.1
>> v.v....
>>
>> But "how to implement it" still not clear... :-(****
>>
>> ** **
>>
>> ** **
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Regds,

Ashok ,
Delivery Consultant,
HP.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130523/d98711b5/attachment.html>