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

uot;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 yo

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

[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

[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] Quantum VLAN / GRE-node

> > What is a “preferred” deployment model? Why would I choose one over the > other?? > > Hari > > ** ** > > *From:* Openstack [mailto:openstack-bounces+hari.kannan= > hp@lists.launchpad.net] *On Behalf Of *Aaron Rosen > *Sent:* Wednesday, June 05, 2013 3

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 N

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

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 wrote: > >> Hi, i'm converting from GRE tunnel to

[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 & OVS] How to bi-direction communicate between VM instances and "old" LAN network(s)

stination=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, 钟生平 wrote: > You should also perform the following commands: > quantum router-gateway-set old_lan5 > >

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

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

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

rk 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 hel