[Openstack] Can't ssh to anything not on control node

2012-08-06 Thread Dave Pigott
https://answers.launchpad.net/nova/+question/204852

Can anyone help me? I'm banging my head against a brick wall. I can't ever get 
an instance on anything but the control node to be accessible.

Thanks

Dave

Dave Pigott
Validation Engineer
T: +44 1223 40 00 63 | M +44 7940 45 93 44
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

___
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] Can't ssh/ping any instance that isn't on a control node

2012-08-07 Thread Dave Pigott
Hi all,

I posted this last night before I had officially joined the mailing list, so it 
may not have made it's way through:

https://answers.launchpad.net/nova/+question/204852

Can anyone help me? I'm banging my head against a brick wall. I can't ever get 
an instance on anything but the control node to be accessible.

Thanks

Dave

Dave Pigott
Validation Engineer
T: +44 1223 40 00 63 | M +44 7940 45 93 44
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

___
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] Can't ssh/ping any instance that isn't on a control node

2012-08-07 Thread Dave Pigott
Shake,

Thanks so much. It finally works! What was missing was the "multi_host=true" in 
nova.conf. I would have expected that to be a default!

Thanks again,

Dave

On 7 Aug 2012, at 10:30, Shake Chen wrote:

> I can share my setting for you. hope can hope help you.
> 
> 
> http://www.chenshake.com/wp-content/uploads/2012/07/openstack_config.zip
> 
> my network is flatdhcp and mutilhost =T 
> 
> my fix ip netwok
> nova-manage network create private --fixed_range_v4=192.168.22.0/24 \
>  --num_networks=1 --bridge=br100 --bridge_interface=eth1 --network_size=256 
> --multi_host=T
> 
> floating IP
> 
> nova-manage floating create --ip_range=10.1.199.32/27
> 
> the other thing is the compute node need install below package
> 
> 
> apt-get install -y nova-api  nova-common nova-compute \
> nova-compute-kvm  nova-network  \
> python-nova python-novaclient \
> python-keystone python-keystoneclient 
> 
> 
> 
> On Tue, Aug 7, 2012 at 3:19 PM, Dave Pigott  wrote:
> Hi all,
> 
> I posted this last night before I had officially joined the mailing list, so 
> it may not have made it's way through:
> 
> https://answers.launchpad.net/nova/+question/204852
> 
> Can anyone help me? I'm banging my head against a brick wall. I can't ever 
> get an instance on anything but the control node to be accessible.
> 
> Thanks
> 
> Dave
> 
> Dave Pigott
> Validation Engineer
> T: +44 1223 40 00 63 | M +44 7940 45 93 44
> Linaro.org │ Open source software for ARM SoCs
> Follow Linaro: Facebook | Twitter | Blog
> 
> 
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> 
> -- 
> Shake Chen
> 
> 

___
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] Weird ping problem

2012-08-31 Thread Dave Pigott
Hi all,

I now have a nicely stable OpenStack install running on five servers, with one 
acting as control with all the services, and the rest just compute/network 
nodes.

The strange thing now, is that if an instance is running on the control node, 
it can ping the outside world, but if it's running on any other node, it can't 
ping the outside world, even on the LAN. The odd thing is, it *does* 
successfully do a dns lookup. Additionally, it can ping other instances on the 
private network address range.

Any ideas?

Thanks

Dave Pigott
Validation Engineer
T: +44 1223 40 00 63 | M +44 7940 45 93 44
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

___
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] Weird ping problem

2012-09-03 Thread Dave Pigott
Hi Vish,

Thanks for replying.

multi_host is set up on all nodes. Where are ip_forward and the snat rules 
documented?

Thanks

Dave

On 31 Aug 2012, at 16:54, Vishvananda Ishaya wrote:

> Are you running multi_host, as in nova-network on both nodes? I would check 
> ip_forward is enabled on both nodes. Nova-network creates an snat rule so 
> that Instances can get to the outside world, so you should also make sure 
> that the snat rule exists and seems to be working properly.
> 
> Vish
> 
> On Aug 31, 2012, at 5:43 AM, Dave Pigott  wrote:
> 
>> Hi all,
>> 
>> I now have a nicely stable OpenStack install running on five servers, with 
>> one acting as control with all the services, and the rest just 
>> compute/network nodes.
>> 
>> The strange thing now, is that if an instance is running on the control 
>> node, it can ping the outside world, but if it's running on any other node, 
>> it can't ping the outside world, even on the LAN. The odd thing is, it 
>> *does* successfully do a dns lookup. Additionally, it can ping other 
>> instances on the private network address range.
>> 
>> Any ideas?
>> 
>> Thanks
>> 
>> Dave Pigott
>> Validation Engineer
>> T: +44 1223 40 00 63 | M +44 7940 45 93 44
>> Linaro.org │ Open source software for ARM SoCs
>> Follow Linaro: Facebook | Twitter | Blog
>> 
>> ___
>> 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


Re: [Openstack] Weird ping problem

2012-09-03 Thread Dave Pigott
Hi Vish,

Just checked on ip_forward. It's enabled on all nodes. The snat rule: Is that 
the one about ssh and ping being allowed through? In which case I'd already 
done all that.

Thanks

Dave

On 31 Aug 2012, at 16:54, Vishvananda Ishaya wrote:

> Are you running multi_host, as in nova-network on both nodes? I would check 
> ip_forward is enabled on both nodes. Nova-network creates an snat rule so 
> that Instances can get to the outside world, so you should also make sure 
> that the snat rule exists and seems to be working properly.
> 
> Vish
> 
> On Aug 31, 2012, at 5:43 AM, Dave Pigott  wrote:
> 
>> Hi all,
>> 
>> I now have a nicely stable OpenStack install running on five servers, with 
>> one acting as control with all the services, and the rest just 
>> compute/network nodes.
>> 
>> The strange thing now, is that if an instance is running on the control 
>> node, it can ping the outside world, but if it's running on any other node, 
>> it can't ping the outside world, even on the LAN. The odd thing is, it 
>> *does* successfully do a dns lookup. Additionally, it can ping other 
>> instances on the private network address range.
>> 
>> Any ideas?
>> 
>> Thanks
>> 
>> Dave Pigott
>> Validation Engineer
>> T: +44 1223 40 00 63 | M +44 7940 45 93 44
>> Linaro.org │ Open source software for ARM SoCs
>> Follow Linaro: Facebook | Twitter | Blog
>> 
>> ___
>> 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


Re: [Openstack] Private instances can't access Internet

2012-09-10 Thread Dave Pigott
Oh yeah. And then do a db sync

Dave

Sent from my Aldis Lamp

On 7 Sep 2012, at 20:50, Jason Cooper  wrote:

> Hi Everyone. I just completed the steps in the OpenStack Compute Starter 
> Guide to get OpenStack up and running on my server, and everything is working 
> wonderfully except that my private instances cannot access the public 
> Internet.
> 
> I have configured the physical server on which OpenStack is running to access 
> the public Internet over eth0. I have also set up an internal network on eth1 
> with a bridge so the instances, which all have fixed private IP addresses 
> (e.g. 192.168.4.x) should be able to ping the public Internet through this 
> bridge. However, this isn't working, and I'm hoping you can help explain what 
> I'm doing wrong.
> 
> I have already tried to setup IP forwarding by following the instructions at 
> https://lists.launchpad.net/openstack/msg15559.html, but this did not help.
> 
> Here is my /etc/network/interfaces:
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> # The primary network interface
> auto eth0
> iface eth0 inet static
>   address 10.0.1.130
>   netmask 255.255.0.0
>   broadcast 10.0.1.255
>   gateway 10.0.0.1
>   dns-nameservers 8.8.8.8
> 
> auto eth1
> iface eth1 inet static
>   address 192.168.3.1
>   netmask 255.255.255.0
>   network 192.168.3.0
>   broadcast 192.168.3.255
> 
> 
> And here is my /etc/nova/nova.conf:
> 
> --dhcpbridge_flagfile=/etc/nova/nova.conf
> --dhcpbridge=/usr/bin/nova-dhcpbridge
> --logdir=/var/log/nova
> --state_path=/var/lib/nova
> --lock_path=/var/lock/nova
> --allow_admin_api=true
> --use_deprecated_auth=false
> --auth_strategy=keystone
> --scheduler_driver=nova.scheduler.simple.SimpleScheduler
> --s3_host=10.0.1.130
> --ec2_host=10.0.1.130
> --rabbit_host=10.0.1.130
> --cc_host=10.0.1.130
> --nova_url=http://10.0.1.130:8774/v1.1/
> --routing_source_ip=10.0.1.130
> --glance_api_servers=10.0.1.130:9292
> --image_service=nova.image.glance.GlanceImageService
> --iscsi_ip_prefix=192.168.4
> --sql_connection=mysql://novadbadmin:novasecret@10.0.1.130/nova
> --ec2_url=http://10.0.1.130:8773/services/Cloud
> --keystone_ec2_url=http://10.0.1.130:5000/v2.0/ec2tokens
> --api_paste_config=/etc/nova/api-paste.ini
> --libvirt_type=kvm
> --libvirt_use_virtio_for_bridges=true
> --start_guests_on_host_boot=true
> --resume_guests_state_on_host_boot=true
> # vnc specific configuration
> --novnc_enabled=true
> --novncproxy_base_url=http://10.0.1.130:6080/vnc_auto.html
> --vncserver_proxyclient_address=10.0.1.130
> --vncserver_listen=10.0.1.130
> # network specific settings
> --network_manager=nova.network.manager.FlatDHCPManager
> --public_interface=eth0
> --flat_interface=eth1
> --flat_network_bridge=br100
> --fixed_range=192.168.4.1/27
> #--floating_range=10.10.10.2/27
> --network_size=32
> --flat_network_dhcp_start=192.168.4.33
> --flat_injected=False
> --force_dhcp_release
> --iscsi_helper=tgtadm
> --connection_type=libvirt
> --root_helper=sudo nova-rootwrap
> --verbose
> 
> 
> Lastly, here is the command I used to create the network:
> 
> sudo nova-manage network create private --fixed_range_v4=192.168.4.32/27 
> --num_networks=1 --bridge=br100 --bridge_interface=eth1 --network_size=32
> 
> 
> You can see that I'm not using a floating IP range. My instances are able to 
> access the public Internet if I change my configuration to use a floating 
> range, but I prefer to find a solution that allows me to assign an internal 
> IP to my instances and use the specified bridge to contact the outside world.
> 
> Any help is appreciated, and many thanks in advance.
> - Jason
> ___
> 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


Re: [Openstack] Private instances can't access Internet

2012-09-10 Thread Dave Pigott
Hi Jason,

Try setting --multi_host in nova.conf

Dave

Sent from my Aldis Lamp

On 7 Sep 2012, at 20:50, Jason Cooper  wrote:

> Hi Everyone. I just completed the steps in the OpenStack Compute Starter 
> Guide to get OpenStack up and running on my server, and everything is working 
> wonderfully except that my private instances cannot access the public 
> Internet.
> 
> I have configured the physical server on which OpenStack is running to access 
> the public Internet over eth0. I have also set up an internal network on eth1 
> with a bridge so the instances, which all have fixed private IP addresses 
> (e.g. 192.168.4.x) should be able to ping the public Internet through this 
> bridge. However, this isn't working, and I'm hoping you can help explain what 
> I'm doing wrong.
> 
> I have already tried to setup IP forwarding by following the instructions at 
> https://lists.launchpad.net/openstack/msg15559.html, but this did not help.
> 
> Here is my /etc/network/interfaces:
> 
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> # The primary network interface
> auto eth0
> iface eth0 inet static
>   address 10.0.1.130
>   netmask 255.255.0.0
>   broadcast 10.0.1.255
>   gateway 10.0.0.1
>   dns-nameservers 8.8.8.8
> 
> auto eth1
> iface eth1 inet static
>   address 192.168.3.1
>   netmask 255.255.255.0
>   network 192.168.3.0
>   broadcast 192.168.3.255
> 
> 
> And here is my /etc/nova/nova.conf:
> 
> --dhcpbridge_flagfile=/etc/nova/nova.conf
> --dhcpbridge=/usr/bin/nova-dhcpbridge
> --logdir=/var/log/nova
> --state_path=/var/lib/nova
> --lock_path=/var/lock/nova
> --allow_admin_api=true
> --use_deprecated_auth=false
> --auth_strategy=keystone
> --scheduler_driver=nova.scheduler.simple.SimpleScheduler
> --s3_host=10.0.1.130
> --ec2_host=10.0.1.130
> --rabbit_host=10.0.1.130
> --cc_host=10.0.1.130
> --nova_url=http://10.0.1.130:8774/v1.1/
> --routing_source_ip=10.0.1.130
> --glance_api_servers=10.0.1.130:9292
> --image_service=nova.image.glance.GlanceImageService
> --iscsi_ip_prefix=192.168.4
> --sql_connection=mysql://novadbadmin:novasecret@10.0.1.130/nova
> --ec2_url=http://10.0.1.130:8773/services/Cloud
> --keystone_ec2_url=http://10.0.1.130:5000/v2.0/ec2tokens
> --api_paste_config=/etc/nova/api-paste.ini
> --libvirt_type=kvm
> --libvirt_use_virtio_for_bridges=true
> --start_guests_on_host_boot=true
> --resume_guests_state_on_host_boot=true
> # vnc specific configuration
> --novnc_enabled=true
> --novncproxy_base_url=http://10.0.1.130:6080/vnc_auto.html
> --vncserver_proxyclient_address=10.0.1.130
> --vncserver_listen=10.0.1.130
> # network specific settings
> --network_manager=nova.network.manager.FlatDHCPManager
> --public_interface=eth0
> --flat_interface=eth1
> --flat_network_bridge=br100
> --fixed_range=192.168.4.1/27
> #--floating_range=10.10.10.2/27
> --network_size=32
> --flat_network_dhcp_start=192.168.4.33
> --flat_injected=False
> --force_dhcp_release
> --iscsi_helper=tgtadm
> --connection_type=libvirt
> --root_helper=sudo nova-rootwrap
> --verbose
> 
> 
> Lastly, here is the command I used to create the network:
> 
> sudo nova-manage network create private --fixed_range_v4=192.168.4.32/27 
> --num_networks=1 --bridge=br100 --bridge_interface=eth1 --network_size=32
> 
> 
> You can see that I'm not using a floating IP range. My instances are able to 
> access the public Internet if I change my configuration to use a floating 
> range, but I prefer to find a solution that allows me to assign an internal 
> IP to my instances and use the specified bridge to contact the outside world.
> 
> Any help is appreciated, and many thanks in advance.
> - Jason
> ___
> 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


Re: [Openstack] Private instances can't access Internet

2012-09-11 Thread Dave Pigott
You have to set muli_host in nova.conf and then do a nova-manage db sync to run 
on more than one compute node.

Dave

Sent from my Aldis Lamp

On 11 Sep 2012, at 18:31, Gui Maluf  wrote:

> I'm facing the same problem and I can't solve it!
> Please, someone help us!
> Instances from cc-node can reach Internet, but the node instances can't!
> 
> CC-node configs: http://paste.openstack.org/show/20861/
> Node configs: http://paste.openstack.org/show/20862/
> 
> ps: i'm not using multi_host
> 
> I've tried many things, but I can't make my instance on node reach internet.
> 
> 
> Dave Pigott
> Mon, 10 Sep 2012 03:09:34 -0700
> 
> Hi Jason,
> 
> Try setting --multi_host in nova.conf
> 
> Dave
> 
> Sent from my Aldis Lamp
> 
> On 7 Sep 2012, at 20:50, Jason Cooper  wrote:
> 
> > Hi Everyone. I just completed the steps in the OpenStack Compute Starter 
> > Guide to get OpenStack up and running on my server, and everything is 
> > working 
> > wonderfully except that my private instances cannot access the public 
> > Internet.
> > 
> > I have configured the physical server on which OpenStack is running to 
> > access 
> > the public Internet over eth0. I have also set up an internal network on 
> > eth1 
> > with a bridge so the instances, which all have fixed private IP addresses 
> > (e.g. 192.168.4.x) should be able to ping the public Internet through this 
> > bridge. However, this isn't working, and I'm hoping you can help explain 
> > what 
> > I'm doing wrong.
> > 
> > I have already tried to setup IP forwarding by following the instructions 
> > at 
> > https://lists.launchpad.net/openstack/msg15559.html, but this did not help.
> > 
> > Here is my /etc/network/interfaces:
> > 
> > # The loopback network interface
> > auto lo
> > iface lo inet loopback
> > 
> > # The primary network interface
> > auto eth0
> > iface eth0 inet static
> >   address 10.0.1.130
> >   netmask 255.255.0.0
> >   broadcast 10.0.1.255
> >   gateway 10.0.0.1
> >   dns-nameservers 8.8.8.8
> > 
> > auto eth1
> > iface eth1 inet static
> >   address 192.168.3.1
> >   netmask 255.255.255.0
> >   network 192.168.3.0
> >   broadcast 192.168.3.255
> > 
> > 
> > And here is my /etc/nova/nova.conf:
> > 
> > --dhcpbridge_flagfile=/etc/nova/nova.conf
> > --dhcpbridge=/usr/bin/nova-dhcpbridge
> > --logdir=/var/log/nova
> > --state_path=/var/lib/nova
> > --lock_path=/var/lock/nova
> > --allow_admin_api=true
> > --use_deprecated_auth=false
> > --auth_strategy=keystone
> > --scheduler_driver=nova.scheduler.simple.SimpleScheduler
> > --s3_host=10.0.1.130
> > --ec2_host=10.0.1.130
> > --rabbit_host=10.0.1.130
> > --cc_host=10.0.1.130
> > --nova_url=http://10.0.1.130:8774/v1.1/
> > --routing_source_ip=10.0.1.130
> > --glance_api_servers=10.0.1.130:9292
> > --image_service=nova.image.glance.GlanceImageService
> > --iscsi_ip_prefix=192.168.4
> > --sql_connection=mysql://novadbadmin:novasecret@10.0.1.130/nova
> > --ec2_url=http://10.0.1.130:8773/services/Cloud
> > --keystone_ec2_url=http://10.0.1.130:5000/v2.0/ec2tokens
> > --api_paste_config=/etc/nova/api-paste.ini
> > --libvirt_type=kvm
> > --libvirt_use_virtio_for_bridges=true
> > --start_guests_on_host_boot=true
> > --resume_guests_state_on_host_boot=true
> > # vnc specific configuration
> > --novnc_enabled=true
> > --novncproxy_base_url=http://10.0.1.130:6080/vnc_auto.html
> > --vncserver_proxyclient_address=10.0.1.130
> > --vncserver_listen=10.0.1.130
> > # network specific settings
> > --network_manager=nova.network.manager.FlatDHCPManager
> > --public_interface=eth0
> > --flat_interface=eth1
> > --flat_network_bridge=br100
> > --fixed_range=192.168.4.1/27
> > #--floating_range=10.10.10.2/27
> > --network_size=32
> > --flat_network_dhcp_start=192.168.4.33
> > --flat_injected=False
> > --force_dhcp_release
> > --iscsi_helper=tgtadm
> > --connection_type=libvirt
> > --root_helper=sudo nova-rootwrap
> > --verbose
> > 
> > 
> > Lastly, here is the command I used to create the network:
> > 
> > sudo nova-manage network create private --fixed_range_v4=192.168.4.32/27 
> > --num_networks=1 --bridge=br100 --bridge_interface=eth1 --network_size=32
> > 
> > 
> > You can see that I'm not using a floating IP range. My instances are able 
> > to 
> > access the public Internet if I 

Re: [Openstack] Cannot ping nor SSH to VM

2012-10-10 Thread Dave Pigott
Have you set multi_hopst? This was my problem when I encountered it. You also 
have to do a db-sync afterwards.

Dave

On 10 Oct 2012, at 14:37, Daniel Oliveira  wrote:

> Hello. I've successfully installed openstack on a machine running Ubuntu 
> Server 12.04 this morning. I had a problem, though. I cannot ping/SSH to any 
> VM I create, and I've already entered secgroup-add-rule commands for both, so 
> I think it comes down to network configuration. Can anyone help me? Thanks in 
> advance.
> 
> -- 
> My best regards,
> 
> Daniel Oliveira.
> 
> ___
> 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] Can't ping self public IP address

2013-01-09 Thread Dave Pigott
Hi all,

I note from https://bugs.launchpad.net/nova/+bug/1096259 that there's an issue 
that means an instance can't ping it's own public IP address. Does anyone know 
of a workaround until this gets fixed?

Thanks

Dave___
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] Non responding instance

2013-04-08 Thread Dave Pigott
Hi all,

I've got an instance that's been running for several months now, and suddenly 
we can not ping or telnet to it. It shows up in the list as Active and Running, 
but just isn't responding. We earlier had a disk full problem on that node, but 
this happened before that occurred, so I don't think that's responsible (but I 
could be wrong). The instance is used extensively so I'd prefer to fix it 
rather than have to kill it and spin up another instance. FYI all other 
instances in the cloud are fine and we can ssh and ping them.

Any ideas what I can do to get this instance active again?

Thanks

Dave
Lava Lab Lead
Linaro Ltd
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp