[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

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

Re: [Openstack] Call to API very slow [Grizzly]

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

[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

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

[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:

Re: [Openstack] Quantum VLAN tag mismatch between Network-node and Compute-node

/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

Re: [Openstack] [Quantum OVS] How to bi-direction communicate between VM instances and old LAN network(s)

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

Re: [Openstack] [Quantum OVS] How to bi-direction communicate between VM instances and old LAN network(s)

: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

Re: [Openstack] [Quantum OVS] How to bi-direction communicate between VM instances and old LAN network(s)

** ** 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