Re: [Openstack] Provider networks and manual ip management

Alright so the proposed patch (on the abandoned review) doesn't fix the problem either, so I guess I take a look at Grizzly. If I were to want to test this out is Grizzly is the best option to just grab the code from git and deploy it that way or is there a snapshot that passes the tests? Basicall

Re: [Openstack] HA Openstack with Pacemaker

What if the VIP is created on a different host than keystone is started on? It seems like you either need to set net.ipv4.ip_nonlocal_bind = 1 or create a colocation in pacemaker (which would either require all services to be on the same host, or have an ip-per-service). On Wed, Feb 13, 2013

Re: [Openstack] Getting the 2012.2.3 release in Ubuntu

+10 for 2012.2.3 @ Ubuntu Cloud Archives! On 11 February 2013 18:48, Logan McNaughton wrote: > Hi, > > I've added the Ubuntu Cloud Archive to my apt sources, however it looks > like the latest release there is 2012.2.1. > > How can I get the latest 2012.2.3 release in Ubuntu 12.04? > > _

Re: [Openstack] HA Openstack with Pacemaker

There we gohttps://review.openstack.org/#/c/21581/ Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15 Le 13 févr. 2013 à 20:15, Razique Mahroua a écrit :I'm currently updating that part of the documentation - indeed it states that two IPs are u

Re: [Openstack] HA Openstack with Pacemaker

I'm currently updating that part of the documentation - indeed it states that two IPs are used, but in fact, you end up with only one VIP for the API service.I'll send the patch tonight Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15 Le 13 févr. 2013 à 20:05, Samuel Wi

Re: [Openstack] HA Openstack with Pacemaker

In that documentation it looks like each openstack service gets it own IP (keystone is being assigned 192.168.42.103 and glance is getting 192.168.42.104). I might be missing something too because in the section titled "Configure the VIP" it create a primitive called "p_api-ip" (or p_ip_api if you

Re: [Openstack] HA Openstack with Pacemaker

Hi Samuel: Yes, it's possible with pacemaker. Look at http://docs.openstack.org/trunk/openstack-ha/content/ch-intro.html. Regards, JuanFra 2013/2/13 Samuel Winchenbach > Hi All, > > I currently have a HA OpenStack cluster running where the OpenStack > services are kept alive with a combinatio

[Openstack] HA Openstack with Pacemaker

Hi All, I currently have a HA OpenStack cluster running where the OpenStack services are kept alive with a combination of haproxy and keepalived. Is it possible to configure pacemaker so that all the OpenStack services are served by the same IP? With keepalived I have a virtual ip that can move

Re: [Openstack] How to debug a Swift's "not found" error while downloading a file?

Hi Giuseppe, The first thing you can do is use the swift-get-nodes utility to find out where those objects would normally be located. In your case it will look something like: swift-get-nodes /etc/swift/object.ring.gz AUTH_ACCOUNTHASH images 8ab06434-5152-4563-b122-f293fd9af465 Of course substi

Re: [Openstack] [SWIFT] code reading

This part of the code gets the account info, but if the account isn't found and account autocreation is set (eg for tempauth and keystone), then we need to create the account first before returning the info. However, since there are multiple replicas of the account in the cluster, we can't simp

Re: [Openstack] use of internal endpoint url instead of public url

On 13/02/13 17:07, Scott Devoid wrote: > We're also lacking support for setting --endpoint-type in keystone. In > my case, it's trying to use adminURL when publicURL is the only one > externally reachable. The keystone client doesn't use the --endpoint-type flag, since you have to supply a URL in

Re: [Openstack] metadata issue

First of all, make sure metadata is DNAT'd to nova-api on your nova-network node. For that, please issue 'iptables -t nat -S' and look at the corresponding entry : -A nova-network-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination :8775 If this is correct, mak

Re: [Openstack] [OpenStack][Swift] Error while starting container, account, object servers.

Yes the problem got solved. Thank you for the responses. The problem was in the conf files object-server.conf, container-server.conf, account-server.conf i had given incorrect bind_ip of the host machine which gave socket bind error. now i changed those IP address to the correct address of the mach

Re: [Openstack] use of internal endpoint url instead of public url

We're also lacking support for setting --endpoint-type in keystone. In my case, it's trying to use adminURL when publicURL is the only one externally reachable. Are all of these effectively the same? --os-endpoint --endpoint-type --bypass-url ~ Scott On Wed, Feb 13, 2013 at 8:15 AM, Mac Innes

Re: [Openstack] [OpenStack][Swift] Error while starting container, account, object servers.

Excellent :) Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15 Le 13 févr. 2013 à 17:02, Sujay M a écrit :Yes the problem got solved. Thank you for the responses. The problem was in the conf files object-server.conf, container-server.conf, account-s

Re: [Openstack] Horizon Keystone Endpoint Issue

Is the dash configured to talk with the Keystone backend?can you run something like $ keystone endoint-list thanks  Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15 Le 12 févr. 2013 à 16:54, Logan McNaughton a écrit :I've had this problem before, in

Re: [Openstack] metadata issue

First of all, make sure metadata is DNAT'd to nova-api on your nova-network node. For that, please issue 'iptables -t nat -S' and look at the corresponding entry : -A nova-network-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-

Re: [Openstack] metadata issue

I ran that command on compute node. I am using nova-network and flatdhcpmanager. I have another setup which has quantam . Having difficulties with the same problem in quantam. Paras. On Wed, Feb 13, 2013 at 9:15 AM, Razique Mahroua wrote: > HI :) > do you use nova-network or quantum? And accor

Re: [Openstack] metadata issue

HI :)do you use nova-network or quantum? And according to the model you use, which kind? For instance vlan, flat, flatDHP for nova-network ? thanks, Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15 Le 12 févr. 2013 à 17:03, Paras pradhan a écrit

Re: [Openstack] [nova] python-novaclient 2.11.0 release

Can't this be fixed by configuring the underlying keyring config file to use a different backing storage? http://pypi.python.org/pypi/keyring#customize-your-keyring-by-config-file Sent from my really tiny device... On Feb 13, 2013, at 2:14 AM, "Daniel P. Berrange" mailto:berra...@redhat.com>>

Re: [Openstack] [OpenStack][Swift] Error while starting container, account, object servers.

I think it's the object-server which cannot bind the IP. Have you updated all the configuration files for it in order not to have the same bidings ports ? Razique Mahroua - Nuage & Corazique.mahr...@gmail.comTel : +33 9 72 37 94 15 Le 12 févr. 2013 à 09:42, Sujay M a écrit :M

Re: [Openstack] use of internal endpoint url instead of public url

Hi Patrick, Both the cinder and nova CLI's support a --endpoint-type argument, it defaults to publicURL. If you use '--endpoint-type internalURL' it should do the right thing.. Thanks, Kiall On 13/02/13 11:09, Patrick Petit wrote: > Dear All, > > How can I direct nova CLI to use the internal

Re: [Openstack] [nova] python-novaclient 2.11.0 release

nice 在 2013-2-13，下午1:41，Vishvananda Ishaya 写道： > Hello Everyone, > > I just pushed version 2.11.0 of python-novaclient to Pypi. There are a lot of > fixes and features in this release. Here is a brief overview: > > Bug Fixes > - > > private key files now created with 400 permissions

[Openstack] How to debug a Swift's "not found" error while downloading a file?

Hi all, I'm receiving an error "not found" while trying to download a file from a Swift container. This happens even if I can see that file when listing the container's content. I was wondering which is the best way to inspect the problem and manually recover the file when this kind of things happ

Re: [Openstack] use of internal endpoint url instead of public url

I forgot to mention, cinderclient doesn't support this attribute yet, but it's worth to add it. -Sylvain Le 13/02/2013 12:46, Sylvain Bauza a écrit : --bypass-url Use this API endpoint instead of the Service Catalog In client.py : if self.bypass_url:

Re: [Openstack] use of internal endpoint url instead of public url

--bypass-url Use this API endpoint instead of the Service Catalog In client.py : if self.bypass_url: self.set_management_url(self.bypass_url) Is this what you expect ? -Sylvain Le 13/02/2013 12:08, Patrick Petit a écrit : Dear All, How can I d

[Openstack] use of internal endpoint url instead of public url

Dear All, How can I direct nova CLI to use the internal service endpoint URL instead of the public one? Same question applies to cinder CLI. I managed to find my way through with glance CLI which supports an OS_IMAGE_URL environment variable whereas OS_COMPUTE_URL and OS_VOLUME_URL seem to ha

Re: [Openstack] n-api installation problem with devstack (on Ubuntu )

Swapnil, >From the n-api logs available on the bug, it looks like the EC2 port (default 8773) is being used by some other service. You can check this using 'netstat -pan |grep 8773'. You can either configure the EC2 port (by specifying 'ec2_listen_port' in nova.conf) or configure the other service

Re: [Openstack] n-api installation problem with devstack (on Ubuntu )

Hi Swapnil, Your problem is : Address already in use (Socket already in use) I think you have another process that listening on the same port as nova-api. Try to find the PID of this process. (netstat -tanpe) If it's not a fresh install, did you run unstack.sh before stack.sh ? Regards, Jean

[Openstack] n-api installation problem with devstack (on Ubuntu )

Hi All, I posted below bug on launchpad, but i didn't get any response from the team, may be its not that active as openstack mailing list. I am facing an issue detailed here [ https://bugs.launchpad.net/devstack/+bug/1122764 ]. Thanks Swapnil ___ Ma

Re: [Openstack] [nova] python-novaclient 2.11.0 release

On Tue, Feb 12, 2013 at 09:41:11PM -0800, Vishvananda Ishaya wrote: > Hello Everyone, > > I just pushed version 2.11.0 of python-novaclient to Pypi. There are a lot of > fixes and features in this release. Here is a brief overview: > > Bug Fixes > - > > simplified keyring support Sigh,