[Openstack] HA for glance api service

Hi, Any plan to support HA (High Availability) in glance api service? I noticed in Folsom it comes with a tool to facilitate the replication of glance api service (see the following link), http://docs.openstack.org/trunk/openstack-compute/admin/content/replicating-images.html But to

Re: [Openstack] OpenStack (+ Quantum Deployment) Scenarios

Hi Skible, It will be great that if you could also cover Nova network, iptables, name space, and linux bridge (bridges that are handled by brctl CLIs). Thanks. Dennis Qin From: openstack-bounces+xiaohong.qin=emc@lists.launchpad.net

Re: [Openstack] [quantum] Relationship between br-int and physical bridge mapping in OVS plugin

Hi Vinay, I have sent the following email out a while ago, --- In the following quantum command, quantum net-create --tenant-id $TENANT_ID net1 --provider:network_type vlan --provider:physical_network physnet1 --provider:segmentation_id 1024 provider:segmentation_id is actually a VLAN id

Re: [Openstack] OpenStack + Nova list, nova show location

Hi, This is just an entering point to load all client side nova code, the nova list CLI eventually invokes the following code in your stack directory, python-novaclient/novaclient/v1_1/shell.py Inside this file, you can see the following function, def do_list That prints out the list of VMs.

Re: [Openstack] Quantum features in the folsom release

Hi, I have added the following section to the bug report, --- In the following quantum command, quantum net-create --tenant-id $TENANT_ID net1 --provider:network_type vlan --provider:physical_network physnet1 --provider:segmentation_id 1024 provider:segmentation_id is actually a VLAN id

[Openstack] iptables rule missing in multi node setup

Hi All, In one of my lab setups, I found the following iptable rules are missing on the controller node, Chain nova-compute-inst-3 (1 references) target prot opt source destination DROP all -- anywhere anywhere state INVALID ACCEPT all --

Re: [Openstack] Quantum features in the folsom release

I have also tried it out in my lab by following steps documented in this URL, http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo .html The floating IP address assigned to VM spawned off in controller node is working from, however, for VMs spawned off on compute node,