[Openstack] Call to API very slow [Grizzly]
All operations in my Openstack dashboard very slow (compare to my old
Openstack deployment)
Then i do some check on an instance:
$ time curl http://169.254.169.254/openstack
2012-08-10
2013-04-04
latest
real0m*5.605s*
user0m0.004s
sys0m0.004s
5 seconds for a simple API query !??
in quantum-ns-metadata-proxy.log, i saw:
2013-07-25 *17:17:09 * DEBUG [quantum.agent.metadata.namespace_proxy]
Request: GET /openstack HTTP/1.0
Accept: */*
Content-Type: text/plain
Host: 169.254.169.254
User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1
zlib/1.2.3.4 libidn/1.23 librtmp/2.3
2013-07-25 *17:17:14*DEBUG [quantum.agent.metadata.namespace_proxy]
{'date': 'Thu, 25 Jul 2013 10:17:14 GMT', 'status': '200',
'content-length': '28', 'content-type': 'text/html; charset=UTF-8',
'content-location': u'http://169.254.169.254/openstack'}
2013-07-25 17:17:14DEBUG [quantum.agent.metadata.namespace_proxy]
2012-08-10
2013-04-04
latest
I take a look at metadata-agent.log, and saw almost request/response
finished @*17:17:09
*
But the last finished *@**17:17:14
*2013-07-25 *17:17:14*DEBUG [quantum.agent.metadata.agent] {'date':
'Thu, 25 Jul 2013 10:17:14 GMT', 'status': '200', 'content-length': '28',
'content-type': 'text/html; charset=UTF-8', 'content-location': u'
http://172.30.1.14:8775/openstack'}
*
*
I enabled slow query log on MySql, but can't find any slow query.
Do you know possible problems in this situation?
Thank you very much!
___
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] Call to API very slow [Grizzly]
Check some more API (I run these command below from Controller node):
# time quantum subnet-list
(...have 4 subnet)
real0m0.676s
user0m0.196s
sys 0m0.020s
# time quantum router-list
(...have 1 router)
real0m0.496s
user0m0.164s
sys 0m0.052s
# time nova list --all_tenants=1
(...have 5 instances)
real0m1.290s
user0m0.308s
sys 0m0.040s
Compare with my old OpenStack deployment on weaker servers, it took 1/3 in
times.
On Thu, Jul 25, 2013 at 5:43 PM, Peter Cheung mcheun...@hotmail.com wrote:
I am having a problem about calling API speed is up and down, something
need 0.1s, something it needs 3s
Thanks
from Peter
--
Date: Thu, 25 Jul 2013 17:41:11 +0700
From: chu.ducm...@gmail.com
To: openstack@lists.launchpad.net; openst...@lists.openstack.org
Subject: [Openstack] Call to API very slow [Grizzly]
All operations in my Openstack dashboard very slow (compare to my old
Openstack deployment)
Then i do some check on an instance:
$ time curl http://169.254.169.254/openstack
2012-08-10
2013-04-04
latest
real0m*5.605s*
user0m0.004s
sys0m0.004s
5 seconds for a simple API query !??
in quantum-ns-metadata-proxy.log, i saw:
2013-07-25 *17:17:09 * DEBUG [quantum.agent.metadata.namespace_proxy]
Request: GET /openstack HTTP/1.0
Accept: */*
Content-Type: text/plain
Host: 169.254.169.254
User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1
zlib/1.2.3.4 libidn/1.23 librtmp/2.3
2013-07-25 *17:17:14*DEBUG [quantum.agent.metadata.namespace_proxy]
{'date': 'Thu, 25 Jul 2013 10:17:14 GMT', 'status': '200',
'content-length': '28', 'content-type': 'text/html; charset=UTF-8',
'content-location': u'http://169.254.169.254/openstack'}
2013-07-25 17:17:14DEBUG [quantum.agent.metadata.namespace_proxy]
2012-08-10
2013-04-04
latest
I take a look at metadata-agent.log, and saw almost request/response
finished @*17:17:09
*
But the last finished *@**17:17:14
*2013-07-25 *17:17:14*DEBUG [quantum.agent.metadata.agent] {'date':
'Thu, 25 Jul 2013 10:17:14 GMT', 'status': '200', 'content-length': '28',
'content-type': 'text/html; charset=UTF-8', 'content-location': u'
http://172.30.1.14:8775/openstack'}
*
*
I enabled slow query log on MySql, but can't find any slow query.
Do you know possible problems in this situation?
Thank you very much!
___ Mailing list:
https://launchpad.net/~openstack Post to :
openstack@lists.launchpad.netUnsubscribe :
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] Call to API very slow [Grizzly]
On Thu, Jul 25, 2013 at 7:30 PM, Jay Pipes jaypi...@gmail.com wrote:
You will need to provide more details than old vs. new OpenStack.
For example...
1) What is your network model in the old vs. new
Old: nova-network + FlatDHCP
New: Quantum + OpenvSwitch + network-namespace + metadata-ns-proxy
2) What version of OpenStack is the old
Old: Essex
New: Grizzly
3) Is Keystone used in old and new? If so, what drivers are used in
Keystone?
Yes, both use Keystone with SQL backend
4) Do you have errors in any of your log files (usually an indication that
something like a timeout or failure on
RPC which may affect performance)
No, i didn't found it.
5) Are you using nova-conductor in the new?
I have nova-conductor process run on Controller node, but seem nova-compute
don't use this.
6) What database backend are you using?
MySQL.
7) Do a time keystone user-list on both old and new
# keystone user-list
Old:
Run 1st time:
real*0m2.494s*
user0m0.112s
sys 0m0.040s
2nd time:
real*0m0.279s*
user0m0.112s
sys 0m0.020s
New:
Run 1st time:
real*0m1.687s*
user0m0.176s
sys 0m0.012s
2nd time:
real*0m0.213s*
user0m0.160s
sys 0m0.040s
8) Pastebin your conf files, with passwords removed
My config files are quite large.
I can sum up that all services API are HA-ed using HAproxy, RabbitMQ
Cluster, Database replication, v.v...
This morning, i just do some tuning memcached for Dashboard service (HA-ed
using HAProxy), then my Dashboard become faster significantly.
The questions remain are:
1. Why metadata query so slow? Possible problems? ( curl
http://169.254.169.254/openstack; took 2.5-5 seconds to complete,
ec2metadata took 14-17 seconds to complete - i tested many times.)
2. Why API calls using *-client reduce time from 2nd time on my old Essex
deployment, but not on my new Grizzly deployment? Maybe I need some cache
settings?
Thank you very much!
The more information you give, the better folks can help you.
Best,
-jay
On 07/25/2013 07:14 AM, Chu Duc Minh wrote:
Check some more API (I run these command below from Controller node):
# time quantum subnet-list
(...have 4 subnet)
real0m0.676s
user0m0.196s
sys 0m0.020s
# time quantum router-list
(...have 1 router)
real0m0.496s
user0m0.164s
sys 0m0.052s
# time nova list --all_tenants=1
(...have 5 instances)
real0m1.290s
user0m0.308s
sys 0m0.040s
Compare with my old OpenStack deployment on weaker servers, it took 1/3
in times.
On Thu, Jul 25, 2013 at 5:43 PM, Peter Cheung mcheun...@hotmail.com
mailto:mcheun...@hotmail.com** wrote:
I am having a problem about calling API speed is up and down,
something need 0.1s, something it needs 3s
Thanks
from Peter
--**--**
Date: Thu, 25 Jul 2013 17:41:11 +0700
From: chu.ducm...@gmail.com mailto:chu.ducm...@gmail.com
To: openstack@lists.launchpad.net
mailto:openstack@lists.**launchpad.netopenstack@lists.launchpad.net
;
openst...@lists.openstack.org
mailto:openstack@lists.**openstack.orgopenst...@lists.openstack.org
Subject: [Openstack] Call to API very slow [Grizzly]
All operations in my Openstack dashboard very slow (compare to my
old Openstack deployment)
Then i do some check on an instance:
$ time curl
http://169.254.169.254/**openstackhttp://169.254.169.254/openstack
2012-08-10
2013-04-04
latest
real0m*5.605s*
user0m0.004s
sys0m0.004s
5 seconds for a simple API query !??
in quantum-ns-metadata-proxy.**log, i saw:
2013-07-25 *17:17:09 * DEBUG
[quantum.agent.metadata.**namespace_proxy] Request: GET /openstack
HTTP/1.0
Accept: */*
Content-Type: text/plain
Host: 169.254.169.254
User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0
OpenSSL/1.0.1 zlib/1.2.3.4 http://1.2.3.4 libidn/1.23 librtmp/2.3
2013-07-25 *17:17:14*DEBUG
[quantum.agent.metadata.**namespace_proxy] {'date': 'Thu, 25 Jul 2013
10:17:14 GMT', 'status': '200', 'content-length': '28',
'content-type': 'text/html; charset=UTF-8', 'content-location':
u'http://169.254.169.254/**openstackhttp://169.254.169.254/openstack
'}
2013-07-25 17:17:14DEBUG
[quantum.agent.metadata.**namespace_proxy] 2012-08-10
2013-04-04
latest
I take a look at metadata-agent.log, and saw almost request/response
finished @*17:17:09
*
But the last finished *@**17:17:14
*2013-07-25 *17:17:14*DEBUG [quantum.agent.metadata.agent]
{'date': 'Thu, 25 Jul 2013 10:17:14 GMT', 'status': '200',
'content-length': '28', 'content-type': 'text/html; charset=UTF-8',
'content-location':
u'http://172.30.1.14:8775/**openstackhttp://172.30.1.14:8775/openstack
'}
*
*
I enabled slow query log on MySql
[Openstack] Some instances duplicate network can't ping
When I launch 5-10 instances simultaneously (from Dashboard), some instances duplicate network like that: (in Overview of instance) IP Addresses -- Net_Proj1 10.2.1.20, 10.2.1.2 Security Groups -- default - ALLOW -1:-1 from 0.0.0.0/0 - ALLOW 22:22 from 0.0.0.0/0 default - ALLOW -1:-1 from 0.0.0.0/0 - ALLOW 22:22 from 0.0.0.0/0 I can't ping both IP 10.2.1.20 10.2.1.2 Some instances have single IP but I can't ping too. Do some check, i found that these instances can't get IP Address due to IPtables problem. In a compute node, the DHCP Discovery request being dropped in Chain * quantum-openvswi-sg-fallback* (I used ULOG to log dropped packet, then i pretty sure about this) PS: I'm using bonding with OpenvSwitch on br-prv (VM network) I dont' know it could be affect ? ___ 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] [Swift] Swift load balancing
If you choose to use DNS round robin, you can set TTL small and use a script/tool to continous check proxy nodes to reconfigure DNS record if one proxy node goes down, and vice-versa. If you choose to use SW load-balancer, I suggest HAProxy for performance (many high-traffic websites use it) and NGinx for features (if you really need features provided by Nginx). IMHO, I like Nginx more than Haproxy. It's stable, modern, high performance, and full-featured. On Fri, Jun 7, 2013 at 6:28 AM, Kotwani, Mukul mukul.g.kotw...@hp.comwrote: Hello folks, I wanted to check and see what others are using in the case of a Swift installation with multiple proxy servers for load balancing/distribution. Based on my reading, the approaches used are DNS round robin, or SW load balancers such as Pound, or HW load balancers. I am really interested in finding out what others have been using in their installations. Also, if there are issues that you have seen related to the approach you are using, and any other information you think would help would be greatly appreciated. ** ** As I understand it, DNS round robin does not check the state of the service behind it, so if a service goes down, DNS will still send the record and the record requires manual removal(?). Also, I am not sure how well it scales or if there are any other issues. About Pound, I am not sure what kind of resources it expects and what kind of scalability it has, and yet again, what other issues have been seen. ** ** Real world examples and problems seen by you guys would definitely help in understanding the options better. ** ** Thanks! Mukul ** ** ___ 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] Quantum VLAN tag mismatch between Network-node and Compute-node
Hi, i'm converting from GRE tunnel to VLAN tagging, and deleted all old project/user/net/subnet. in file /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini @ all nodes, I already set: network_vlan_ranges = physnet1:2:4094 When I create a new net: +---+--+ | Field | Value| +---+--+ | admin_state_up| True | | id| 6d7b116e-be0b-4019-8769-a50a9ca13406 | | name | net_proj_one | | provider:network_type | vlan | | provider:physical_network | physnet1 | *| provider:segmentation_id | 2 * | | router:external | False| | shared| False| | status| ACTIVE | | subnets | 959fe9e0-a79d-4d0f-8040-ebfab26d8182 | | tenant_id | 29ba82e97f374492a4ca02c62eb0a953 | +---+--+ But when i show in network-node: # ovs-vsctl show ... Bridge br-int Port tapdddef664-ee *tag: 1* Interface tapdddef664-ee type: internal Port qr-f9ba0308-2c *tag: 1* Interface qr-f9ba0308-2c type: internal Port int-br-eth0 Interface int-br-eth0 Port br-int Interface br-int type: internal Bridge br-eth0 Port br-eth0 Interface br-eth0 type: internal Port phy-br-eth0 Interface phy-br-eth0 Port eth0 Interface eth0 interface for router dhcp created are created in VLAN 1 (wrong! it should be created with VLAN 2) I try to find in config and database, but i can't found which setting that start with VLAN 1. Because of VLAN tag mismatch, I can't access to VM instance. Another weird thing is on compute node, tag is not constant when i create/terminate new instance: # ovs-vsctl show a9900940-f882-42f8-9b7c-9b42393ed8a4 Bridge qbred613362-fe Port qvbed613362-fe Interface qvbed613362-fe Port qbred613362-fe Interface qbred613362-fe type: internal Port taped613362-fe Interface taped613362-fe Bridge br-eth1 Port eth1 Interface eth1 Port br-eth1 Interface br-eth1 type: internal Port phy-br-eth1 Interface phy-br-eth1 Bridge br-int Port br-int Interface br-int type: internal Port qvo9816466e-22 *tag: 5* Interface qvo9816466e-22 Port int-br-eth1 Interface int-br-eth1 Port qvoed613362-fe *tag: 5* Interface qvoed613362-fe Bridge qbr9816466e-22 Port qbr9816466e-22 Interface qbr9816466e-22 type: internal Port tap9816466e-22 Interface tap9816466e-22 Port qvb9816466e-22 Interface qvb9816466e-22 Bridge virbr0 Port virbr0 Interface virbr0 type: internal Do you know why it happen? When everything is ok, *tag* on both Network-node Compute-node should equal *2 *(for first VM network) when I configured *network_vlan_ranges = physnet1:2:4094* ?? Thank you very much! ___ 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] Quantum VLAN tag mismatch between Network-node and Compute-node
Thank you very much! I don't have much knowledge about OpenvSwitch OpenFlow. I checked VLAN follow your guide and found everything seems correct. Finally, I figure out why it did not work - because before it, i created some VLAN manually using vconfig (to confirm that trunk port is configured correctly). Openvswitch (use brcompat module) does not work correctly if 8021q module is used to create VLAN. Again, thank you very much indeed, Aaron! On 6/5/13, Aaron Rosen aro...@nicira.com wrote: Hi, Those vlan tags you are showing are not the actual tags that will be seen on the wire. Those tags are auto incremented and used for each new port that lands on a server that is in a different network. If you run ovs-ofctl dump-flows br-int you'll see those vlan tags are stripped off and the correct one is added. Look here https://github.com/openstack/quantum/blob/master/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py#L326 if your curious about what's going on. Aaron On Wed, Jun 5, 2013 at 2:25 AM, Chu Duc Minh chu.ducm...@gmail.com wrote: Hi, i'm converting from GRE tunnel to VLAN tagging, and deleted all old project/user/net/subnet. in file /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini @ all nodes, I already set: network_vlan_ranges = physnet1:2:4094 When I create a new net: +---+--+ | Field | Value| +---+--+ | admin_state_up| True | | id| 6d7b116e-be0b-4019-8769-a50a9ca13406 | | name | net_proj_one | | provider:network_type | vlan | | provider:physical_network | physnet1 | *| provider:segmentation_id | 2 * | | router:external | False| | shared| False| | status| ACTIVE | | subnets | 959fe9e0-a79d-4d0f-8040-ebfab26d8182 | | tenant_id | 29ba82e97f374492a4ca02c62eb0a953 | +---+--+ But when i show in network-node: # ovs-vsctl show ... Bridge br-int Port tapdddef664-ee *tag: 1* Interface tapdddef664-ee type: internal Port qr-f9ba0308-2c *tag: 1* Interface qr-f9ba0308-2c type: internal Port int-br-eth0 Interface int-br-eth0 Port br-int Interface br-int type: internal Bridge br-eth0 Port br-eth0 Interface br-eth0 type: internal Port phy-br-eth0 Interface phy-br-eth0 Port eth0 Interface eth0 interface for router dhcp created are created in VLAN 1 (wrong! it should be created with VLAN 2) I try to find in config and database, but i can't found which setting that start with VLAN 1. Because of VLAN tag mismatch, I can't access to VM instance. Another weird thing is on compute node, tag is not constant when i create/terminate new instance: # ovs-vsctl show a9900940-f882-42f8-9b7c-9b42393ed8a4 Bridge qbred613362-fe Port qvbed613362-fe Interface qvbed613362-fe Port qbred613362-fe Interface qbred613362-fe type: internal Port taped613362-fe Interface taped613362-fe Bridge br-eth1 Port eth1 Interface eth1 Port br-eth1 Interface br-eth1 type: internal Port phy-br-eth1 Interface phy-br-eth1 Bridge br-int Port br-int Interface br-int type: internal Port qvo9816466e-22 *tag: 5* Interface qvo9816466e-22 Port int-br-eth1 Interface int-br-eth1 Port qvoed613362-fe *tag: 5* Interface qvoed613362-fe Bridge qbr9816466e-22 Port qbr9816466e-22 Interface qbr9816466e-22 type: internal Port tap9816466e-22 Interface tap9816466e-22 Port qvb9816466e-22 Interface qvb9816466e-22 Bridge virbr0 Port virbr0 Interface virbr0 type: internal Do you know why it happen? When everything is ok, *tag* on both Network-node Compute-node should equal *2 *(for first VM network) when I configured *network_vlan_ranges = physnet1:2:4094* ?? Thank you very much! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack
Re: [Openstack] [Quantum OVS] How to bi-direction communicate between VM instances and old LAN network(s)
Hi, finally I can make it run with multi l3-agent, but still have some problems. (I change my network model, an instance now have 2 VM interface, each interface connect to a separate router, and each router have an separate external network - 192.168.5.0/24 (old_LAN) and x.y.z.0/24 (WAN network in my Datacenter)) First, the config of router(s) (interface+IP) not stable, depend on running order or l3-agent(s) Second, sometimes floating-ip can't not be attached to interface and iptables rules can't not be created, because the request being sent to wrong l3-agent (because we have 2 l3-agent on a node) Third, a instance can have mulltiple floating IP (on multi ext_net), but only one Floating-IP *working*, because when an instance have multi default gateway, the traffic can in out in different way. *PS: Why I can't simple add a port to my router, then add a LAN IP to this port (ex: 192.168.5.254), then add this port to another br-ex (another NIC card) *(I created *br-ex-lan* and add ethX to it), then plug this port to my old LAN switch/router, to add some routes like: quantum router-update id_of_router --routes type=dict list=true destination=192.168.0.0/16,nexthop=192.168.5.1 *Or have a way to do that, and I don't know?* Can you guide me a way, pls? Thank you very much!! On Thu, May 23, 2013 at 3:08 PM, 钟生平 chd...@163.com wrote: You should also perform the following commands: quantum router-gateway-set id_of_project_router old_lan5 At 2013-05-23 15:21:10,Chu Duc Minh chu.ducm...@gmail.com wrote: Thanks Ashok Kumaran, I follow your link, but when i associate a Floating IP in new_Ext_net to an instance, Horizon throw an error: *Error: *External network 4a7f4ca5-a787-4f64-8a4b-22a11f9b55f7 is not reachable from subnet 9c921f72-a60e-4eae-b53f-f3eff3218627. Therefore, cannot associate Port d105d3e7-6702-4ff6-81f8-65fba219bd0b with a Floating IP. PS: I run: quantum net-create --tenant-id id_of_admin_tenant old_lan5 --router:external=True quantum subnet-create --tenant-id 2fcd718a8d084ffc866bbb39640c8cd1 --allocation-pool start=192.168.5.31,end=192.168.5.34 --gateway 192.168.5.30 old_lan5 192.168.5.0/24 --enable_dhcp=False quantum router-interface-add id_of_project_router id_of_new_subnet quantum router-update 5def5511-7a43-48ca-b234-be290020509c --routes type=dict list=true destination=192.168.0.0/16,nexthop=192.168.5.1 On Thu, May 23, 2013 at 12:41 PM, Ashok Kumaran ashokkumara...@gmail.comwrote: 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.ducm...@gmail.comwrote: 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) na...@cisco.comwrote: 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
Re: [Openstack] [Quantum OVS] How to bi-direction communicate between VM instances and old LAN network(s)
Thanks Ashok Kumaran, I follow your link, but when i associate a Floating IP in new_Ext_net to an instance, Horizon throw an error: *Error: *External network 4a7f4ca5-a787-4f64-8a4b-22a11f9b55f7 is not reachable from subnet 9c921f72-a60e-4eae-b53f-f3eff3218627. Therefore, cannot associate Port d105d3e7-6702-4ff6-81f8-65fba219bd0b with a Floating IP. PS: I run: quantum net-create --tenant-id id_of_admin_tenant old_lan5 --router:external=True quantum subnet-create --tenant-id 2fcd718a8d084ffc866bbb39640c8cd1 --allocation-pool start=192.168.5.31,end=192.168.5.34 --gateway 192.168.5.30 old_lan5 192.168.5.0/24 --enable_dhcp=False quantum router-interface-add id_of_project_router id_of_new_subnet quantum router-update 5def5511-7a43-48ca-b234-be290020509c --routes type=dict list=true destination=192.168.0.0/16,nexthop=192.168.5.1 On Thu, May 23, 2013 at 12:41 PM, Ashok Kumaran ashokkumara...@gmail.comwrote: 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.ducm...@gmail.comwrote: 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) na...@cisco.comwrote: 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@lists.launchpad.net] *On Behalf Of *Chu Duc Minh *Sent:* Wednesday, May 22, 2013 5:04 AM *To:* openstack@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
Re: [Openstack] [Quantum OVS] How to bi-direction communicate between VM instances and old LAN network(s)
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) na...@cisco.comwrote: 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@lists.launchpad.net] *On Behalf Of *Chu Duc Minh *Sent:* Wednesday, May 22, 2013 5:04 AM *To:* openstack@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@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
