Re: [Openstack] ZeroMQ RPC Driver - FF-Exception request
On Tuesday, January 24, 2012 at 6:05 PM, Zhongyue Luo wrote: > I assume the messages will be delivered directly to the destination rather > than piling up on a queue server? > > > Although the blueprint doesn't specify this level of detail, the intention had originally been to deliver a queue-server model in Essex with a distributed-model in Folsom. The first-cut code which passes tests does pile onto a queue server. I now have code which implements a distributed model, but it is in a raw state. There are a number of edge-cases a distributed model can face, especially in regard to threading mechanisms (i.e. eventlet). My current blockers for having this code ready for a merge-proposal are not related to a single-server or distributed model. Once I address these problems, there can be a decision on how much time is left to debug a distributed model within a FFe time-frame, or if this can be accepted as a separate blueprint within E4. If I get a solid 1-2 weeks or more for a FFe, I'll be more confident in the distributed model as there is more room to test, debug, and fix. By the way, I must note in this thread, that I haven't done this alone. A good amount of this work, i.e. the first-first-cut, was completed by Zed Shaw and was made possible through his QAL. Duncan McGreggor has been on hand, helpful, and has contributed some commits as well. Regards,Eric Windisch___ 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] ZeroMQ RPC Driver - FF-Exception request
Sorry, I had originally sent only to Yun Mao. Sending to list. --- Rather than attempt to answer this, I defer to the ZeroMQ guide. It should be noted that the designers of AMPQ, iMatix, designed and build ZeroMQ. (RabbitMQ and QUID implement AMQP) http://zguide.zeromq.org/page:all#Why-We-Needed-MQ -- Eric Windisch On Tuesday, January 24, 2012 at 5:20 PM, Yun Mao wrote: > Hi I'm curious and unfamiliar with the subject. What's the benefit of > 0MQ vs Kombu? Thanks, > > Yun > > On Tue, Jan 24, 2012 at 7:08 PM, Eric Windisch (mailto:e...@cloudscaling.com)> wrote: > > Per today's meeting, I am proposing the ZeroMQ RPC driver for a > > feature-freeze exception. > > > > I am making good progress on this blueprint, it adds a new optional module > > and service without modifying any existing code or modules. I have been > > pushing to complete this work by E3, so I am close to completion, but cannot > > finish by tonight's deadline. > > > > The ZeroMQ driver will provide an alternative to Kombu (RabbitMQ) and QPID > > for messaging within Nova. Currently, the code passes unit tests but fails > > on smoketests. I expect to have the code viable for a merge proposal in less > > than a week, tomorrow if I'm smart, lucky, and the store doesn't sell out of > > RedBull. A two week grace would give me a nice buffer. > > > > Thanks, > > Eric Windisch > > > > > > ___ > > Mailing list: https://launchpad.net/~openstack > > Post to : openstack@lists.launchpad.net > > (mailto: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] No /etc/nova/nova.conf
Where would u like all the configs to be. I can attempt to make this better in the new devstack2. Might as well get it right the second time around ;) On 1/24/12 1:28 PM, "David Kranz" wrote: In general, it is unfortunate that there is such a big difference in the end result between deploying from source and from packages, even though they are supposed to function the same. Ideally the process structure, locations of configuration files, etc. could be the same. The location of nova.conf is just one small piece. The current situation is confusing to new users and makes it more difficult for old users to try new versions of OpenStack in "real" environments. I realize this is a difficult issue because different distros do the packaging differently. -David On 1/24/2012 2:19 PM, Jesse Andrews wrote: > There have been conversations about changing that. That nova should > use /etc/nova/nova.conf > > Thoughts? > > On Tue, Jan 24, 2012 at 10:40 AM, Jorge Luiz Correa > wrote: >> When using Devstack the files are written to /opt/stack/. So, you >> can find nova.conf in /opt/stack/nova/bin/. >> >> Regards. >> >> >> On Tue, Jan 24, 2012 at 3:48 PM, Joe Smithian >> wrote: >>> Hi All, >>> >>> I installed OpenStack using devsatck script (http://devstack.org/) on >>> Ubuntu 11.10. Installation was successful but there is no /etc/nova/ >>> directory and It looks like that devstack script doesn't install all >>> the nova services. Should I install them manually as described in the >>> getting started documents? >>> >>> All the openStack are installed at /opt/stack/. Should I create >>> symbolic link at /etc/nova? >>> >>> >>> >>> Thanks >>> >>> Joe >>> >>> ___ >>> Mailing list: https://launchpad.net/~openstack >>> Post to : openstack@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~openstack >>> More help : https://help.launchpad.net/ListHelp >> >> >> >> -- >> - MSc. Correa, J.L. >> >> >> ___ >> 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 ___ 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] Swift Container Name Restrictions
You'll also find this info in the Object Storage API document, see http://docs.openstack.org/api/openstack-object-storage/1.0/content/ch_object-storage-dev-api-storage.html On Tue, Jan 24, 2012 at 7:27 PM, John Dickinson wrote: > > On Jan 24, 2012, at 5:22 PM, Matthew Wodrich wrote: > >> Hi Folks, >> >> I'm trying to write some scripts to work with Swift containers, but I don't >> actually know what the restrictions on container names are. Does anyone >> know what the specification is, or where I can read up on it? >> >> For example: >> What are the length requirements for container names? (Maximum/Minimum >> numbers of characters?) > > min is one character, max is 256 > >> Starting character requirements? > > none > >> Allowable character sets? > > utf8 > >> Disallowed characters? > > non-utf8 > >> Disallowed patterns? (things like .., .-, -., --, ip address-like things, >> etc.) > > none > >> Anything else? > > the container name can't contain a "/" since that would be the delimiter > between the container and object name (eg /account/container/object) > > > --John > ___ > 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] ZeroMQ RPC Driver - FF-Exception request
I assume the messages will be delivered directly to the destination rather than piling up on a queue server? On Wed, Jan 25, 2012 at 10:49 AM, Duncan McGreggor wrote: > Under specific architectures, 0MQ can process millions of messages per > second vs. RabbitMQ's many thousands. > > RabbitMQ is a messaging system; 0MQ is a messaging framework. There's a > pretty good write-up on some of the basic differences here: > http://www.zeromq.org/docs:welcome-from-amqp > > Note that the creators of 0MQ (iMatix) were also the guys that invented > AMQP... so they've learned many excellent lessons ;-) > > d > > > On 24 Jan 2012 - 20:20, Yun Mao wrote: > > Hi I'm curious and unfamiliar with the subject. What's the benefit of > > 0MQ vs Kombu? Thanks, > > > > Yun > > > > On Tue, Jan 24, 2012 at 7:08 PM, Eric Windisch > wrote: > > > Per today's meeting, I am proposing the ZeroMQ RPC driver for a > > > feature-freeze exception. > > > > > > I am making good progress on this blueprint, it adds a new optional > module > > > and service without modifying any existing code or modules. I have been > > > pushing to complete this work by E3, so I am close to completion, but > cannot > > > finish by tonight's deadline. > > > > > > The ZeroMQ driver will provide an alternative to Kombu (RabbitMQ) and > QPID > > > for messaging within Nova. Currently, the code passes unit tests but > fails > > > on smoketests. I expect to have the code viable for a merge proposal > in less > > > than a week, tomorrow if I'm smart, lucky, and the store doesn't sell > out of > > > RedBull. A two week grace would give me a nice buffer. > > > > > > Thanks, > > > Eric Windisch > > > > > > > > > ___ > > > 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 > > ___ > 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] No /etc/nova/nova.conf
This is really just a dev choice. In the newer devstack it can be in a different place (programmer determined). I am making it typically be the following. $ROOTDIR/$COMPONENT/app (for the git checked out code) $ROOTDIR/$COMPONENT/config (for configs - unless overridden by the component class) $ROOTDIR/$COMPONENT/traces (for traces of what happened during install/start/stop...) For "production use" I think u are right, they should be in /etc (or where distros put them). Just don't forget devstack is a " an opinionated openstack developer installation." Although as more people use it we should try to adopt standard policies. Hopefully this newer one we are making can help that be possible. On 1/24/12 3:38 PM, "Ignace Mouzannar" wrote: Hi, On Tue, Jan 24, 2012 at 13:40, Jorge Luiz Correa wrote: > When using Devstack the files are written to /opt/stack/. So, you > can find nova.conf in /opt/stack/nova/bin/. Is there a reason why a configuration file is installed in a "bin/" directory (not following the FHS [1])? In my understanding, the "Editable Text Configuration" files should be located in an "etc/" directory. Cheers, Ignace M [1] http://www.pathname.com/fhs/pub/fhs-2.3.html#ETCHOSTSPECIFICSYSTEMCONFIGURATION ___ 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] ZeroMQ RPC Driver - FF-Exception request
Under specific architectures, 0MQ can process millions of messages per second vs. RabbitMQ's many thousands. RabbitMQ is a messaging system; 0MQ is a messaging framework. There's a pretty good write-up on some of the basic differences here: http://www.zeromq.org/docs:welcome-from-amqp Note that the creators of 0MQ (iMatix) were also the guys that invented AMQP... so they've learned many excellent lessons ;-) d On 24 Jan 2012 - 20:20, Yun Mao wrote: > Hi I'm curious and unfamiliar with the subject. What's the benefit of > 0MQ vs Kombu? Thanks, > > Yun > > On Tue, Jan 24, 2012 at 7:08 PM, Eric Windisch wrote: > > Per today's meeting, I am proposing the ZeroMQ RPC driver for a > > feature-freeze exception. > > > > I am making good progress on this blueprint, it adds a new optional module > > and service without modifying any existing code or modules. I have been > > pushing to complete this work by E3, so I am close to completion, but cannot > > finish by tonight's deadline. > > > > The ZeroMQ driver will provide an alternative to Kombu (RabbitMQ) and QPID > > for messaging within Nova. Currently, the code passes unit tests but fails > > on smoketests. I expect to have the code viable for a merge proposal in less > > than a week, tomorrow if I'm smart, lucky, and the store doesn't sell out of > > RedBull. A two week grace would give me a nice buffer. > > > > Thanks, > > Eric Windisch > > > > > > ___ > > 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 ___ 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] Swift Container Name Restrictions
On Jan 24, 2012, at 5:22 PM, Matthew Wodrich wrote: > Hi Folks, > > I'm trying to write some scripts to work with Swift containers, but I don't > actually know what the restrictions on container names are. Does anyone know > what the specification is, or where I can read up on it? > > For example: > What are the length requirements for container names? (Maximum/Minimum > numbers of characters?) min is one character, max is 256 > Starting character requirements? none > Allowable character sets? utf8 > Disallowed characters? non-utf8 > Disallowed patterns? (things like .., .-, -., --, ip address-like things, > etc.) none > Anything else? the container name can't contain a "/" since that would be the delimiter between the container and object name (eg /account/container/object) --John smime.p7s Description: S/MIME cryptographic signature ___ 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] ZeroMQ RPC Driver - FF-Exception request
Hi I'm curious and unfamiliar with the subject. What's the benefit of 0MQ vs Kombu? Thanks, Yun On Tue, Jan 24, 2012 at 7:08 PM, Eric Windisch wrote: > Per today's meeting, I am proposing the ZeroMQ RPC driver for a > feature-freeze exception. > > I am making good progress on this blueprint, it adds a new optional module > and service without modifying any existing code or modules. I have been > pushing to complete this work by E3, so I am close to completion, but cannot > finish by tonight's deadline. > > The ZeroMQ driver will provide an alternative to Kombu (RabbitMQ) and QPID > for messaging within Nova. Currently, the code passes unit tests but fails > on smoketests. I expect to have the code viable for a merge proposal in less > than a week, tomorrow if I'm smart, lucky, and the store doesn't sell out of > RedBull. A two week grace would give me a nice buffer. > > Thanks, > Eric Windisch > > > ___ > 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] ZeroMQ RPC Driver - FF-Exception request
FWIW, I'd love to see this land in E3... d On 24 Jan 2012 - 16:08, Eric Windisch wrote: > Per today's meeting, I am proposing the ZeroMQ RPC driver for a > feature-freeze exception. > > I am making good progress on this blueprint, it adds a new optional > module and service without modifying any existing code or modules. I > have been pushing to complete this work by E3, so I am close to > completion, but cannot finish by tonight's deadline. > > The ZeroMQ driver will provide an alternative to Kombu (RabbitMQ) and > QPID for messaging within Nova. Currently, the code passes unit tests > but fails on smoketests. I expect to have the code viable for a merge > proposal in less than a week, tomorrow if I'm smart, lucky, and the > store doesn't sell out of RedBull. A two week grace would give me a > nice buffer. > > Thanks, > Eric Windisch > > ___ > 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] ZeroMQ RPC Driver - FF-Exception request
Per today's meeting, I am proposing the ZeroMQ RPC driver for a feature-freeze exception. I am making good progress on this blueprint, it adds a new optional module and service without modifying any existing code or modules. I have been pushing to complete this work by E3, so I am close to completion, but cannot finish by tonight's deadline. The ZeroMQ driver will provide an alternative to Kombu (RabbitMQ) and QPID for messaging within Nova. Currently, the code passes unit tests but fails on smoketests. I expect to have the code viable for a merge proposal in less than a week, tomorrow if I'm smart, lucky, and the store doesn't sell out of RedBull. A two week grace would give me a nice buffer. Thanks, Eric Windisch ___ 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] No /etc/nova/nova.conf
Hi, On Tue, Jan 24, 2012 at 13:40, Jorge Luiz Correa wrote: > When using Devstack the files are written to /opt/stack/. So, you > can find nova.conf in /opt/stack/nova/bin/. Is there a reason why a configuration file is installed in a "bin/" directory (not following the FHS [1])? In my understanding, the "Editable Text Configuration" files should be located in an "etc/" directory. Cheers, Ignace M [1] http://www.pathname.com/fhs/pub/fhs-2.3.html#ETCHOSTSPECIFICSYSTEMCONFIGURATION ___ 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] Swift Container Name Restrictions
Hi Folks, I'm trying to write some scripts to work with Swift containers, but I don't actually know what the restrictions on container names are. Does anyone know what the specification is, or where I can read up on it? For example: What are the length requirements for container names? (Maximum/Minimum numbers of characters?) Starting character requirements? Allowable character sets? Disallowed characters? Disallowed patterns? (things like .., .-, -., --, ip address-like things, etc.) Anything else? Thanks in advance for any help anyone can provide, even if it's just a link to a document I somehow missed, Matt Wodrich ___ 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] [nova client] Can't get the diagnostics command to work
Monitoring can be done through libvirt monitoring plugins. For example:
http://honk.sigxcpu.org/projects/libvirt/
Vish
On Jan 24, 2012, at 2:01 PM, Leander Bessa wrote:
> How exactly do i install that particular extension and what can i use as an
> alternative to monitor instances with KVM?
>
>
> On Tue, Jan 24, 2012 at 6:11 PM, Kiall Mac Innes wrote:
> I've just verified this against my install, but since the diagnostics is
> unsupported when using libvirt/kvm, it still errors out (but with a 500,
> rather than 404)
>
> Thanks,
> Kiall
>
>
>
> On Tue, Jan 24, 2012 at 5:56 PM, Brian Waldon
> wrote:
> Actually the diagnostics command was not added in Essex, but it was converted
> to a true extension. However it is part of the Admin API, which means for
> Diablo you need to set the allow_admin_api flag on your nova-api node.
>
>
> On Jan 24, 2012, at 9:41 AM, Kiall Mac Innes wrote:
>
>> Hi,
>>
>> The diagnostics command was added in Essex, my packages are using the stable
>> Diablo version.
>>
>> Novaclient sadly shows these options even though they can't be used with
>> Diablo.
>>
>> Kiall
>>
>> Sent from my mobile - Sorry for being short.
>>
>> On Jan 24, 2012 5:04 p.m., "Leander Bessa" wrote:
>> Hello,
>>
>> I've setup a single node configuration with keystone using the packages from
>> https://launchpad.net/~managedit/+archive/openstack.
>>
>> I've managed to launch an instance, however when i run the commando nova
>> diagnostics i get this:
>>
>> REQ: curl -i http://127.0.0.1:5000/tokens -X POST -H "Content-Type:
>> application/json" -H "User-Agent: python-novaclient"
>>
>> REQ BODY: {"auth": {"tenantName": "admin", "passwordCredentials":
>> {"username": "admin", "password": "admin"}}}
>>
>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '200',
>> 'content-length': '1119', 'content-type': 'application/json; charset=UTF-8'}
>> {"access": {"token": {"expires": "2015-02-05T00:00:00", "id":
>> "999888777666", "tenant": {"id": "1", "name": "admin"}}, "serviceCatalog":
>> [{"endpoints": [{"adminURL": "http://127.0.0.1:8774/v1.1/1";, "region":
>> "RegionOne", "internalURL": "http://127.0.0.1:8774/v1.1/1";, "publicURL":
>> "http://127.0.0.1:8774/v1.1/1"}], "type": "compute", "name": "nova"},
>> {"endpoints": [{"adminURL": "http://127.0.0.1:8774/v1.0";, "region":
>> "RegionOne", "internalURL": "http://127.0.0.1:8774/v1.0";, "publicURL":
>> "http://127.0.0.1:8774/v1.0/"}], "type": "compute", "name": "nova_compat"},
>> {"endpoints": [{"adminURL": "http://127.0.0.1:9292/v1.1/1";, "region":
>> "RegionOne", "internalURL": "http://127.0.0.1:9292/v1.1/1";, "publicURL":
>> "http://127.0.0.1:9292/v1.1/1"}], "type": "image", "name": "glance"},
>> {"endpoints": [{"adminURL": "http://127.0.0.1:35357/v2.0";, "region":
>> "RegionOne", "internalURL": "http://127.0.0.1:5000/v2.0";, "publicURL":
>> "http://127.0.0.1:5000/v2.0"}], "type": "identity", "name": "identity"}],
>> "user": {"id": "1", "roles": [{"tenantId": "1", "id": "1", "name": "Admin"},
>> {"id": "1", "name": "Admin"}], "name": "admin"}}}
>>
>> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
>> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
>> "X-Auth-Token: 999888777666"
>>
>> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
>> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
>> "X-Auth-Token: 999888777666"
>>
>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
>> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404 Not
>> Found
>>
>> The resource could not be found.
>>
>>
>>
>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
>> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404 Not
>> Found
>>
>> The resource could not be found.
>>
>>
>> n/a (HTTP 404)
>>
>>
>> Any ideas?
>>
>> Regards,
>>
>> Leander
>>
>> ___
>> 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
>
>
>
> ___
> 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] Proposal for new devstack (v2?)
Ok dokie, Let me see what I can do to get a 6.2 system. Thx. On 1/24/12 1:53 PM, "Pádraig Brady" wrote: On 01/24/2012 06:39 PM, Joshua Harlow wrote: > Ok, I was using 6.1. > > Is there any reason that it isn't available for 6.1 and 6.2 (technically?) Well it's not been tested on 6.1 currently. One issue with 6.1 is the version of libvirt is too old I think. cheers, Pádraig. ___ 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] Defining vm network
Yes, I understand.
But My problem is:
i) I create a network: # nova-manage network create --label=public
--fixed_range_v4=8.8.8.0/24
ii) Then I spin up a vm: # nova boot --flavor 1 --image 2 --key_name
key instance1
But this vm does NOT have a fixed_ip associated to its interface, so I
think it's not attached to the network.
root@nova-controller:/var/lib/stackops# nova list
++-+--+--+
| ID | Name | Status |Networks |
++-+---+--+
| 7 | instance1| BUILD | |
| 8 | instance2| BUILD | |
++---++--+
I am using FlatDHCP and it was working fine before install Quantum,
now nova-network.log gives this error (complete TRACE in previous
e-mail):
(nova.rpc): TRACE: QuantumServerException: Server 420 error:
{"networkNotFound": {"message": "Unable to find a network with the
specified identifier.", "code": 420, "detail": "Network None could not
be found"}}
Have anyone had this problem before?
The problem can be Quantum with FlatDHCP?
Thank you very much for you attention, Dan.
2012/1/24, Dan Wendlandt :
> Hi Alisson,
>
> The --nic option was only added to nova client in Essex, thus it will not
> be available in Diablo code.
>
> However, if you spin up a VM with no --nic options, the VM will actually
> automatically get a NIC on each "global" network (i.e. no project is set)
> and each project network (--project set when creating the network). You
> need to create these networks using nova-network. This is all document
> here:
> http://docs.openstack.org/incubation/openstack-network/admin/content/QuantumManager-d1e450.html
>
> Dan
>
>
> On Tue, Jan 24, 2012 at 10:59 AM, Alisson Soares Limeira Pontes <
> apon...@cpqd.com.br> wrote:
>
>> Hello everybody.
>>
>>
>> I am searching for some days but I can't figure out how to attach a vm to
>> a network?
>>
>> I am using Quantum 2011.3 with OVS to create the network. And Diablo.
>>
>> I am looking to something like:
>>
>> $ nova boot --flavor 1 --image 2 *--nic net-id=* --key_name key
>> instance10
>>
>> But in Diablo *--nic* does not work
>>
>>
>> I apreciate any help.
>> Thank you.
>>
>>
>>
>> ps. I created the network and when I boot a vm nova-network.log returns
>>
>> 2012-01-24 18:27:34,941 DEBUG nova.network.quantum.quantum_connection [-]
>> Quantum Client Request:
>> POST /v1.0/tenants/default/networks/None/ports.json
>> from (pid=872) do_request
>> /var/lib/nova/nova/network/quantum/client.py:176
>> 2012-01-24 18:27:34,941 DEBUG nova.network.quantum.quantum_connection [-]
>> {"port": {"state": "ACTIVE"}} from (pid=872) do_request
>> /var/lib/nova/nova/network/quantum/client.py:178
>> 2012-01-24 18:27:36,540 DEBUG nova.network.quantum.quantum_connection [-]
>> Quantum Client Reply (code = 420) :
>> {"networkNotFound": {"message": "Unable to find a network with the
>> specified identifier.", "code": 420, "detail": "Network None could not be
>> found"}} from (pid=872) do_request
>> /var/lib/nova/nova/network/quantum/client.py:187
>> 2012-01-24 18:27:36,540 ERROR nova.rpc [-] Exception during message
>> handling
>> (nova.rpc): TRACE: Traceback (most recent call last):
>> (nova.rpc): TRACE: File "/var/lib/nova/nova/rpc/impl_kombu.py", line
>> 620, in _process_data
>> (nova.rpc): TRACE: rval = node_func(context=ctxt, **node_args)
>> (nova.rpc): TRACE: File
>> "/var/lib/nova/nova/network/quantum/manager.py",
>> line 175, in allocate_for_instance
>> (nova.rpc): TRACE: vif_rec['uuid'])
>> (nova.rpc): TRACE: File
>> "/var/lib/nova/nova/network/quantum/quantum_connection.py", line 86, in
>> create_and_attach_port
>> (nova.rpc): TRACE: resdict = self.client.create_port(net_id,
>> port_data, tenant=tenant_id)
>> (nova.rpc): TRACE: File "/var/lib/nova/nova/network/quantum/client.py",
>> line 81, in with_params
>> (nova.rpc): TRACE: ret = self.func(instance, *args)
>> (nova.rpc): TRACE: File "/var/lib/nova/nova/network/quantum/client.py",
>> line 277, in create_port
>> (nova.rpc): TRACE: return self.do_request("POST", self.ports_path %
>> (network), body=body)
>> (nova.rpc): TRACE: File "/var/lib/nova/nova/network/quantum/client.py",
>> line 202, in do_request
>> (nova.rpc): TRACE: % locals()))
>> (nova.rpc): TRACE: QuantumServerException: Server 420 error:
>> {"networkNotFound": {"message": "Unable to find a network with the
>> specified identifier.", "code": 420, "detail": "Network None could not be
>> found"}}
>> (nova.rpc): TRACE
--
Alisson Pontes
___
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] [nova client] Can't get the diagnostics command to work
If you're running diablo, you should just have to restart your nova-api nodes
with the allow_admin_api flag on. But as Kiall points out, 'diagnostics' is not
implemented for libvirt. Unfortunately, I don't know how to help you on that
front. Maybe somebody else has some pointers?
On Jan 24, 2012, at 2:01 PM, Leander Bessa wrote:
> How exactly do i install that particular extension and what can i use as an
> alternative to monitor instances with KVM?
>
>
> On Tue, Jan 24, 2012 at 6:11 PM, Kiall Mac Innes wrote:
> I've just verified this against my install, but since the diagnostics is
> unsupported when using libvirt/kvm, it still errors out (but with a 500,
> rather than 404)
>
> Thanks,
> Kiall
>
>
>
> On Tue, Jan 24, 2012 at 5:56 PM, Brian Waldon
> wrote:
> Actually the diagnostics command was not added in Essex, but it was converted
> to a true extension. However it is part of the Admin API, which means for
> Diablo you need to set the allow_admin_api flag on your nova-api node.
>
>
> On Jan 24, 2012, at 9:41 AM, Kiall Mac Innes wrote:
>
>> Hi,
>>
>> The diagnostics command was added in Essex, my packages are using the stable
>> Diablo version.
>>
>> Novaclient sadly shows these options even though they can't be used with
>> Diablo.
>>
>> Kiall
>>
>> Sent from my mobile - Sorry for being short.
>>
>> On Jan 24, 2012 5:04 p.m., "Leander Bessa" wrote:
>> Hello,
>>
>> I've setup a single node configuration with keystone using the packages from
>> https://launchpad.net/~managedit/+archive/openstack.
>>
>> I've managed to launch an instance, however when i run the commando nova
>> diagnostics i get this:
>>
>> REQ: curl -i http://127.0.0.1:5000/tokens -X POST -H "Content-Type:
>> application/json" -H "User-Agent: python-novaclient"
>>
>> REQ BODY: {"auth": {"tenantName": "admin", "passwordCredentials":
>> {"username": "admin", "password": "admin"}}}
>>
>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '200',
>> 'content-length': '1119', 'content-type': 'application/json; charset=UTF-8'}
>> {"access": {"token": {"expires": "2015-02-05T00:00:00", "id":
>> "999888777666", "tenant": {"id": "1", "name": "admin"}}, "serviceCatalog":
>> [{"endpoints": [{"adminURL": "http://127.0.0.1:8774/v1.1/1";, "region":
>> "RegionOne", "internalURL": "http://127.0.0.1:8774/v1.1/1";, "publicURL":
>> "http://127.0.0.1:8774/v1.1/1"}], "type": "compute", "name": "nova"},
>> {"endpoints": [{"adminURL": "http://127.0.0.1:8774/v1.0";, "region":
>> "RegionOne", "internalURL": "http://127.0.0.1:8774/v1.0";, "publicURL":
>> "http://127.0.0.1:8774/v1.0/"}], "type": "compute", "name": "nova_compat"},
>> {"endpoints": [{"adminURL": "http://127.0.0.1:9292/v1.1/1";, "region":
>> "RegionOne", "internalURL": "http://127.0.0.1:9292/v1.1/1";, "publicURL":
>> "http://127.0.0.1:9292/v1.1/1"}], "type": "image", "name": "glance"},
>> {"endpoints": [{"adminURL": "http://127.0.0.1:35357/v2.0";, "region":
>> "RegionOne", "internalURL": "http://127.0.0.1:5000/v2.0";, "publicURL":
>> "http://127.0.0.1:5000/v2.0"}], "type": "identity", "name": "identity"}],
>> "user": {"id": "1", "roles": [{"tenantId": "1", "id": "1", "name": "Admin"},
>> {"id": "1", "name": "Admin"}], "name": "admin"}}}
>>
>> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
>> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
>> "X-Auth-Token: 999888777666"
>>
>> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
>> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
>> "X-Auth-Token: 999888777666"
>>
>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
>> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404 Not
>> Found
>>
>> The resource could not be found.
>>
>>
>>
>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
>> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404 Not
>> Found
>>
>> The resource could not be found.
>>
>>
>> n/a (HTTP 404)
>>
>>
>> Any ideas?
>>
>> Regards,
>>
>> Leander
>>
>> ___
>> 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
>
>
>
___
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] [nova client] Can't get the diagnostics command to work
How exactly do i install that particular extension and what can i use as an
alternative to monitor instances with KVM?
On Tue, Jan 24, 2012 at 6:11 PM, Kiall Mac Innes wrote:
> I've just verified this against my install, but since the diagnostics is
> unsupported when using libvirt/kvm, it still errors out (but with a 500,
> rather than 404)
>
> Thanks,
> Kiall
>
>
>
> On Tue, Jan 24, 2012 at 5:56 PM, Brian Waldon
> wrote:
>
>> Actually the diagnostics command was not added in Essex, but it was
>> converted to a true extension. However it is part of the Admin API, which
>> means for Diablo you need to set the allow_admin_api flag on your nova-api
>> node.
>>
>>
>> On Jan 24, 2012, at 9:41 AM, Kiall Mac Innes wrote:
>>
>> Hi,
>>
>> The diagnostics command was added in Essex, my packages are using the
>> stable Diablo version.
>>
>> Novaclient sadly shows these options even though they can't be used with
>> Diablo.
>>
>> Kiall
>>
>> Sent from my mobile - Sorry for being short.
>> On Jan 24, 2012 5:04 p.m., "Leander Bessa" wrote:
>>
>>> Hello,
>>>
>>> I've setup a single node configuration with keystone using the packages
>>> from https://launchpad.net/~managedit/+archive/openstack.
>>>
>>> I've managed to launch an instance, however when i run the commando nova
>>> diagnostics i get this:
>>>
>>> REQ: curl -i http://127.0.0.1:5000/tokens -X POST -H "Content-Type:
>>> application/json" -H "User-Agent: python-novaclient"
>>>
>>> REQ BODY: {"auth": {"tenantName": "admin", "passwordCredentials":
>>> {"username": "admin", "password": "admin"}}}
>>>
>>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '200',
>>> 'content-length': '1119', 'content-type': 'application/json;
>>> charset=UTF-8'} {"access": {"token": {"expires": "2015-02-05T00:00:00",
>>> "id": "999888777666", "tenant": {"id": "1", "name": "admin"}},
>>> "serviceCatalog": [{"endpoints": [{"adminURL": "
>>> http://127.0.0.1:8774/v1.1/1";, "region": "RegionOne", "internalURL": "
>>> http://127.0.0.1:8774/v1.1/1";, "publicURL": "
>>> http://127.0.0.1:8774/v1.1/1"}], "type": "compute", "name": "nova"},
>>> {"endpoints": [{"adminURL": "http://127.0.0.1:8774/v1.0";, "region":
>>> "RegionOne", "internalURL": "http://127.0.0.1:8774/v1.0";, "publicURL": "
>>> http://127.0.0.1:8774/v1.0/"}], "type": "compute", "name":
>>> "nova_compat"}, {"endpoints": [{"adminURL": "
>>> http://127.0.0.1:9292/v1.1/1";, "region": "RegionOne", "internalURL": "
>>> http://127.0.0.1:9292/v1.1/1";, "publicURL": "
>>> http://127.0.0.1:9292/v1.1/1"}], "type": "image", "name": "glance"},
>>> {"endpoints": [{"adminURL": "http://127.0.0.1:35357/v2.0";, "region":
>>> "RegionOne", "internalURL": "http://127.0.0.1:5000/v2.0";, "publicURL": "
>>> http://127.0.0.1:5000/v2.0"}], "type": "identity", "name":
>>> "identity"}], "user": {"id": "1", "roles": [{"tenantId": "1", "id": "1",
>>> "name": "Admin"}, {"id": "1", "name": "Admin"}], "name": "admin"}}}
>>>
>>> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET
>>> -H "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
>>> "X-Auth-Token: 999888777666"
>>>
>>> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET
>>> -H "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
>>> "X-Auth-Token: 999888777666"
>>>
>>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
>>> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404
>>> Not Found
>>>
>>> The resource could not be found.
>>>
>>>
>>>
>>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
>>> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404
>>> Not Found
>>>
>>> The resource could not be found.
>>>
>>>
>>> n/a (HTTP 404)
>>>
>>>
>>> Any ideas?
>>>
>>> Regards,
>>>
>>> Leander
>>>
>>> ___
>>> 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
>>
>>
>>
>
___
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] Proposal for new devstack (v2?)
On 01/24/2012 06:39 PM, Joshua Harlow wrote: > Ok, I was using 6.1. > > Is there any reason that it isn’t available for 6.1 and 6.2 (technically?) Well it's not been tested on 6.1 currently. One issue with 6.1 is the version of libvirt is too old I think. cheers, Pádraig. ___ 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] Error getting image list via nova
I am using the latest version of nova, glance and swift from Ubuntu and I am
running into an issue getting the list of images via nova. When I run either
nova image-list or euca-describe-images I get the following (glance index works
just fine):
Internal Server error: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/eventlet/wsgi.py", line 336, in
handle_one_response
result = self.application(self.environ, start_response)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 147, in __call__
resp = self.call_func(req, *args, **self.kwargs)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 208, in call_func
return self.func(req, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/glance/common/wsgi.py", line 113, in
__call__
response = req.get_response(self.application)
File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1053, in
get_response
application, catch_exc_info=False)
File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1022, in
call_application
app_iter = application(self.environ, start_response)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 147, in __call__
resp = self.call_func(req, *args, **self.kwargs)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 208, in call_func
return self.func(req, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/glance/common/wsgi.py", line 113, in
__call__
response = req.get_response(self.application)
File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1053, in
get_response
application, catch_exc_info=False)
File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1022, in
call_application
app_iter = application(self.environ, start_response)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 159, in __call__
return resp(environ, start_response)
File "/usr/lib/pymodules/python2.7/routes/middleware.py", line 131, in
__call__
response = self.app(environ, start_response)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 159, in __call__
return resp(environ, start_response)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 147, in __call__
resp = self.call_func(req, *args, **self.kwargs)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 208, in call_func
return self.func(req, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/glance/common/wsgi.py", line 311, in
__call__
request, **action_args)
File "/usr/lib/python2.7/dist-packages/glance/common/wsgi.py", line 328, in
dispatch
return method(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/glance/api/v1/images.py", line 147, in
detail
**params)
File "/usr/lib/python2.7/dist-packages/glance/registry/__init__.py", line 42,
in get_images_detail
return c.get_images_detailed(**kwargs)
File "/usr/lib/python2.7/dist-packages/glance/registry/client.py", line 62,
in get_images_detailed
res = self.do_request("GET", "/images/detail", params=params)
File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 140, in
do_request
method, action, body=body, headers=headers, params=params)
File "/usr/lib/python2.7/dist-packages/glance/common/client.py", line 232, in
_do_request
raise Exception("Internal Server error: %s" % res.read())
Exception: Internal Server error: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/eventlet/wsgi.py", line 336, in
handle_one_response
result = self.application(self.environ, start_response)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 147, in __call__
resp = self.call_func(req, *args, **self.kwargs)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 208, in call_func
return self.func(req, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/glance/common/wsgi.py", line 113, in
__call__
response = req.get_response(self.application)
File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1053, in
get_response
application, catch_exc_info=False)
File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1022, in
call_application
app_iter = application(self.environ, start_response)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 159, in __call__
return resp(environ, start_response)
File "/usr/lib/pymodules/python2.7/routes/middleware.py", line 131, in
__call__
response = self.app(environ, start_response)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 159, in __call__
return resp(environ, start_response)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 147, in __call__
resp = self.call_func(req, *args, **self.kwargs)
File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 208, in call_func
return self.func(req, *args, **kwargs)
File "/usr/lib/python2.7/dist-packages/glance/common/wsgi.py", line 311, in
__call__
request, *
Re: [Openstack] No /etc/nova/nova.conf
It looks like some nova and keystone services are not running. So my question is how to check the status and restart all services in devStack? I can't use commands like "restart nova-api" because they are not installed. There should be other ways to start services in devStack. Devstack is for development. If you shut the machine off that's running it, you need to re-run the script. Many devs run devstack in a VM for convenience (pause command, easy to blow away if something gets screwed up, easy to do a clean install). ___ 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] No /etc/nova/nova.conf
In general, it is unfortunate that there is such a big difference in the end result between deploying from source and from packages, even though they are supposed to function the same. Ideally the process structure, locations of configuration files, etc. could be the same. The location of nova.conf is just one small piece. The current situation is confusing to new users and makes it more difficult for old users to try new versions of OpenStack in "real" environments. I realize this is a difficult issue because different distros do the packaging differently. -David On 1/24/2012 2:19 PM, Jesse Andrews wrote: There have been conversations about changing that. That nova should use /etc/nova/nova.conf Thoughts? On Tue, Jan 24, 2012 at 10:40 AM, Jorge Luiz Correa wrote: When using Devstack the files are written to /opt/stack/. So, you can find nova.conf in /opt/stack/nova/bin/. Regards. On Tue, Jan 24, 2012 at 3:48 PM, Joe Smithian wrote: Hi All, I installed OpenStack using devsatck script (http://devstack.org/) on Ubuntu 11.10. Installation was successful but there is no /etc/nova/ directory and It looks like that devstack script doesn't install all the nova services. Should I install them manually as described in the getting started documents? All the openStack are installed at /opt/stack/. Should I create symbolic link at /etc/nova? Thanks Joe ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- - MSc. Correa, J.L. ___ 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 ___ 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] Nova network creates network but
Hi Mohammed, On Tue, Jan 24, 2012 at 11:51 AM, Mohammad Banikazemi wrote: > Using the Dashboard GUI (on an openstack install on a single machine > using devstack with Quantum and OVS) and user Demo, I can create new > networks by using the button "Networks" under the Network section. A > message says the network was created and an ID is shown. However, I do not > see anything happening at Nova-network side or any other services. > No entry is created in the "networks" table of the nova database but the > "networks" table of ovs_quantum has a new entry for the new network. When I > click on the ID of the newly created network I get the message that the > details were not found and the Nova network service reports that it could > not find that network. What am I missing? > The Quantum integration with Horizon needs some work. Most importantly, it doesn't play nicely with Quantum Manager. We've been looking for volunteers to get it in good shape again. Would love to make progress on this in E-4 if anyone is interested (hint, hint!) > > I want to have two users have two different networks where only the VMs > from each user can communicate with each other. Right now, the VMs created > for Admin and Demo are all on the same network and can see each other. How > do I go about doing this? Thanks. > You can do this by creating project specific networks with "nova-manage network create" and passing a --project_id flag that specifies the integer ID for the project (note: the docs indicate that this project_id can be a string, but that is no longer the case. This was a recently discovered bug and we will be updating the docs for essex-3). Note: you will also need to prevent stack.sh from creating its default network (or delete it afterward), since this network has no project specified and is thus a global network that all VMs will get a NIC on. See the Quantum Admin Guide for more details on creating private and global networks: http://docs.openstack.org/incubation/openstack-network/admin/content/QuantumManager-d1e450.html Dan > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > -- ~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~ ___ 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] XCP and Openstack questions
> > If you have the Open vSwitch components installed in domain 0, then > there > > are a few scripts that wrap around it to set up the isolation rules > used > > in flat mode. These are in nova/plugins/xenapi/networking. > > I believe you mean: plugins/xenserver/networking Yes, those are the ones. > Nova in Debian now creates a nova-xcp-plugins taking files from > plugins/xenserver/xenapi/. I now believe that I should also make a > nova-xcp-network package. > > Having a quick look at the files in the plugins/xenserver/networking > folder, these would need some re-work. For example, the init.d scripts > are lacking LSB headers (to be used by insserv for parallel booting), > and also there's an etc/sysconfig, which really, is too much CentOS / > RedHat centric (in Debian, it would go in /etc/default). > > Now, I saw files in etc/xensource/scripts. I suppose that these, in > Debian, to respect both FHS and the work we've done with Mike and Jon, > these files should go in /usr/lib/xcp/scripts/. I just hope there's no > references to the wrong CentOS path in these scripts! If you know > things > that should be adapted right away, it'd be great to have the fixes made > for runtime, rather than a Debian specific patch, IMO, because patches > are annoying to maintain. > > You can expect that I will contribute these adaptations for Debian in > the next following days, and also fix the packaging to add this new > nova-xcp-network binary package. > > I will let you know how it goes. Those scripts are going to be 100% CentOS/XenServer dependent right now. They've been written specifically for that environment, and I don't know of anyone who's tried them in a pure Debian environment. We can certainly take any changes that would be required to make them work in either environment. > >> Does OpenStack + XCP still use nova-network? Is all traffic for the > VMs > >> routed through it as with KVM and libvirt? Should I still create a > >> bridge on the nova-network domU? > > > > It depends on which network mode you're using. If you're using the > > HA modes, then yes, traffic goes through nova-network. In flat mode > > it will come directly to domain 0 and the vSwitch. > > And using the VLAN manager? VLAN without HA will come through domain 0 directly I believe. The VLANs are managed as ports on the Open vSwitch. > > Devstack has all of the domU setup for HA networking > > -- see https://blueprints.launchpad.net/nova/+spec/xenapi-ha-nova- > network. > > I've always been directed to devstack, however, I'm really not > interested at all in using it: I'm working on packaging things > correctly > for Debian, and as a consequence, I want to use *only* the Debian > packages that we produce. Of course, I'll keep updating and modifying > them until it works. The point of directing you to devstack is not to say "go use devstack" it's to say "go read devstack and see what it does". Devstack is used to set up automated test systems, so it's always up to date with the configuration required in OpenStack. If you're in any doubt, it's the canonical reference for configuration settings. > >> How does Openstack injects IP addresses in an XCP VM? Can this even > be > >> done? > > > > It talks to an in-guest agent, typically. It writes it to XenStore, > and > > then this is picked up by the agent inside the VM. > > So, running the XCP software inside the VM is mandatory? If so, this > should change IMO, it's really not hosting provider friendly: customers > expect to take any AMI image, possibly from AWS, and run them on the > cloud, we can't force customers to use specific VM images for XCP. You're not running XCP inside the VM. You're running an agent inside the VM. If you don't want to do that, then you either have to accept filesystem injection (which some people like, some people don't) or you have to use DHCP to configure IP addresses. > > Security groups have only recently been implemented for XenAPI: > > https://blueprints.launchpad.net/nova/+spec/xenapi-security-groups. > > That got merged less than two weeks ago. > > Will this be in e3? Yes. > Do you know if the OVF files exported by VirtualBox would work? I have never tried that. You'd maybe be able to get it to work with a bit of effort, but you're likely to run into problems with the different kernel / driver set that I presume vbox uses. Citrix has a product -- XenConvert -- which deals with all of these kinds of conversion issues and will swap out drivers and so on. It's not a very simple problem to solve. Particularly the Windows case. You might be OK with up-to-date Linux though (i.e. 3.2 kernels). > >> 3/ Console > >> on the same wiki page, it tells about using VNC. While this does > work, > >> I > >> didn't have access to the login prompt. What's the way, if using > >> openstack, to tell that the console is hvc0 (or whatever is the Xen > >> console device name)? > > > > That's dependent on the in-guest setup. I think on
Re: [Openstack] Dashboard - Error: Unable to communicate with identity service: [Errno 111] Connection refused. (HTTP 400)
I'm seeing this type of result (400 errors) when I go through the install manual I just proposed that uses the Managed IT packages... I am running it in a VM on my Macbook. Would love to learn more. It nearly always happens after I work at work, then work from home, even if the IP address of the VM doesn't change. I suspect networking difficulties but can't really troubleshoot. Remember that the nova services are for Compute, the identity service is the Keystone project. So see if you can restart the keystone service and see if it is running. Keep asking - these are good questions and items I've struggled with after installing many times. Anne On Tue, Jan 17, 2012 at 4:20 PM, Joe Smithian wrote: > Hi, > > I was able to login to OpenStack dashboard from my PC but after I > rebooted my PC, trying to login failed with this message: > > > Error: Unable to communicate with identity service: > [Errno 111] Connection refused. (HTTP 400) > > > I rebooted Nova controller, it didn't help! Any idea what to do to fix it? > > Thanks > > Joe > > ___ > 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] No /etc/nova/nova.conf
Hi, Completely agreed that nova.conf should be moved to /etc/nova/nova.conf If the DB needs to be re-created the "nova-manage db sync" command will fail at least the nova.conf is in the /etc directory. So, if you are running devstack, you have to manually copy the file to avoid the problem. Thanks, Edgar -Original Message- From: openstack-bounces+eperdomo=cisco@lists.launchpad.net [mailto:openstack-bounces+eperdomo=cisco@lists.launchpad.net] On Behalf Of Jesse Andrews Sent: Tuesday, January 24, 2012 11:20 AM To: Jorge Luiz Correa Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] No /etc/nova/nova.conf There have been conversations about changing that. That nova should use /etc/nova/nova.conf Thoughts? On Tue, Jan 24, 2012 at 10:40 AM, Jorge Luiz Correa wrote: > When using Devstack the files are written to /opt/stack/. So, you > can find nova.conf in /opt/stack/nova/bin/. > > Regards. > > > On Tue, Jan 24, 2012 at 3:48 PM, Joe Smithian > wrote: >> >> Hi All, >> >> I installed OpenStack using devsatck script (http://devstack.org/) on >> Ubuntu 11.10. Installation was successful but there is no /etc/nova/ >> directory and It looks like that devstack script doesn't install all >> the nova services. Should I install them manually as described in the >> getting started documents? >> >> All the openStack are installed at /opt/stack/. Should I create >> symbolic link at /etc/nova? >> >> >> >> Thanks >> >> Joe >> >> ___ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp > > > > > -- > - MSc. Correa, J.L. > > > ___ > 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 ___ 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] Nova network creates network but
Using the Dashboard GUI (on an openstack install on a single machine using devstack with Quantum and OVS) and user Demo, I can create new networks by using the button "Networks" under the Network section. A message says the network was created and an ID is shown. However, I do not see anything happening at Nova-network side or any other services. No entry is created in the "networks" table of the nova database but the "networks" table of ovs_quantum has a new entry for the new network. When I click on the ID of the newly created network I get the message that the details were not found and the Nova network service reports that it could not find that network. What am I missing? I want to have two users have two different networks where only the VMs from each user can communicate with each other. Right now, the VMs created for Admin and Demo are all on the same network and can see each other. How do I go about doing this? Thanks.___ 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] Defining vm network
Hi Alisson,
The --nic option was only added to nova client in Essex, thus it will not
be available in Diablo code.
However, if you spin up a VM with no --nic options, the VM will actually
automatically get a NIC on each "global" network (i.e. no project is set)
and each project network (--project set when creating the network). You
need to create these networks using nova-network. This is all document
here:
http://docs.openstack.org/incubation/openstack-network/admin/content/QuantumManager-d1e450.html
Dan
On Tue, Jan 24, 2012 at 10:59 AM, Alisson Soares Limeira Pontes <
apon...@cpqd.com.br> wrote:
> Hello everybody.
>
>
> I am searching for some days but I can't figure out how to attach a vm to
> a network?
>
> I am using Quantum 2011.3 with OVS to create the network. And Diablo.
>
> I am looking to something like:
>
> $ nova boot --flavor 1 --image 2 *--nic net-id=* --key_name key
> instance10
>
> But in Diablo *--nic* does not work
>
>
> I apreciate any help.
> Thank you.
>
>
>
> ps. I created the network and when I boot a vm nova-network.log returns
>
> 2012-01-24 18:27:34,941 DEBUG nova.network.quantum.quantum_connection [-]
> Quantum Client Request:
> POST /v1.0/tenants/default/networks/None/ports.json
> from (pid=872) do_request /var/lib/nova/nova/network/quantum/client.py:176
> 2012-01-24 18:27:34,941 DEBUG nova.network.quantum.quantum_connection [-]
> {"port": {"state": "ACTIVE"}} from (pid=872) do_request
> /var/lib/nova/nova/network/quantum/client.py:178
> 2012-01-24 18:27:36,540 DEBUG nova.network.quantum.quantum_connection [-]
> Quantum Client Reply (code = 420) :
> {"networkNotFound": {"message": "Unable to find a network with the
> specified identifier.", "code": 420, "detail": "Network None could not be
> found"}} from (pid=872) do_request
> /var/lib/nova/nova/network/quantum/client.py:187
> 2012-01-24 18:27:36,540 ERROR nova.rpc [-] Exception during message
> handling
> (nova.rpc): TRACE: Traceback (most recent call last):
> (nova.rpc): TRACE: File "/var/lib/nova/nova/rpc/impl_kombu.py", line
> 620, in _process_data
> (nova.rpc): TRACE: rval = node_func(context=ctxt, **node_args)
> (nova.rpc): TRACE: File "/var/lib/nova/nova/network/quantum/manager.py",
> line 175, in allocate_for_instance
> (nova.rpc): TRACE: vif_rec['uuid'])
> (nova.rpc): TRACE: File
> "/var/lib/nova/nova/network/quantum/quantum_connection.py", line 86, in
> create_and_attach_port
> (nova.rpc): TRACE: resdict = self.client.create_port(net_id,
> port_data, tenant=tenant_id)
> (nova.rpc): TRACE: File "/var/lib/nova/nova/network/quantum/client.py",
> line 81, in with_params
> (nova.rpc): TRACE: ret = self.func(instance, *args)
> (nova.rpc): TRACE: File "/var/lib/nova/nova/network/quantum/client.py",
> line 277, in create_port
> (nova.rpc): TRACE: return self.do_request("POST", self.ports_path %
> (network), body=body)
> (nova.rpc): TRACE: File "/var/lib/nova/nova/network/quantum/client.py",
> line 202, in do_request
> (nova.rpc): TRACE: % locals()))
> (nova.rpc): TRACE: QuantumServerException: Server 420 error:
> {"networkNotFound": {"message": "Unable to find a network with the
> specified identifier.", "code": 420, "detail": "Network None could not be
> found"}}
> (nova.rpc): TRACE
>
>
> --
> Alisson Pontes
> __
> Network Technology Evolution Researcher
> CPqD - Center for Research and Development in Telecommunications
> Tel.: +55 19 3705-4996
> apon...@cpqd.com.br
> www.cpqd.com.br
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>
--
~~~
Dan Wendlandt
Nicira Networks: www.nicira.com
twitter: danwendlandt
~~~
___
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] dashboard in oneric
Thanks guys for the info. Out of curiosity , If somebody wants to implement openstack in their production environment which package repository should they consider? github, ubuntu, managedit or (any) others? Paras. On Mon, Jan 23, 2012 at 5:17 PM, Debo Dutta (dedutta) wrote: > FWIW I ran the old devstack and it worked (with horizon). Out of the box > except for some UI issues (horizon!) and with quantum > > > > debo > > > > From: openstack-bounces+dedutta=cisco@lists.launchpad.net > [mailto:openstack-bounces+dedutta=cisco@lists.launchpad.net] On Behalf > Of Denmat > Sent: Monday, January 23, 2012 2:25 PM > Cc: openstack > > > Subject: Re: [Openstack] dashboard in oneric > > > > FWIW, I got horizon/keystone from devstack working on a separate host to my > Ubuntu ppa openstack host. Couldn't get them on the one host due to python > libs getting installed to different locations. > > > > Den > > > On 24/01/2012, at 9:00, Joshua Harlow wrote: > > You should be able to use the newer devstack v2 to get horizon up and > running. > > I haven’t tested it to well but I think it will do it. > > https://github.com/yahoo/Openstack-Devstack2 > > ./stack –c horizon –a install –d $HOME/youropenstackplace (will install all > of horizons dependencies also) > > ./stack –c horizon –a start –d $HOME/youropenstackplace (should start > horizon + dependencies, haven’t messed around with this yet, might need a > little work) > > -Josh > > On 1/23/12 12:37 PM, "Paras pradhan" wrote: > > I have seen folks at openstack IRC who could get it working but all > packages from github. I have tried several options and the problem is > related with openstackx. I run diablo from ubuntu repo and its working > fine. Somebody told me that the dashboard / keystone at ubuntu is > broken . I could run dashboard and keystone that I checkout from > horizon. I could login in with errors but looks its really impossible > to fix (at least to me) the openstackx issue. > > > If anyone has working dashboard with diablo from Oneric please share > how they handle the issues with openstackx > Paras > > > On Mon, Jan 23, 2012 at 1:25 PM, Vishvananda Ishaya > wrote: >> Dashboard requires keystone, so I don't know if this is possible without a >> lot of hacking. >> >> Vish >> >> On Jan 23, 2012, at 10:56 AM, Jorge Luiz Correa wrote: >> >> Well, I tried to install from Ubuntu (Oneiric) repos but just could get it >> working without keystone. So, in this case, I couldn't use horizon >> (requires >> keystone). >> >> Trying to use the dashboard from repos, it didn't work. >> >> Currently, I'm running Diablo from ubuntu repos without dashboard, just >> command line tools to manage the cloud (euca2ools). >> >> Regards. >> >> On Mon, Jan 23, 2012 at 4:26 PM, Paras pradhan >> wrote: >>> >>> Has anyone recently able to run dashboard/horizon in Ubuntu Oneric. If >>> yes which one should I use? dashboard from ubuntu or horizon src from >>> github? >>> >>> Thanks >>> Paras. >>> >>> ___ >>> Mailing list: https://launchpad.net/~openstack >>> Post to : openstack@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~openstack >>> More help : https://help.launchpad.net/ListHelp >> >> >> >> >> -- >> - MSc. Correa, J.L. >> >> ___ >> 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 >> > > ___ > 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 > > > ___ > 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] No /etc/nova/nova.conf
Hi Kiall, Thanks for your reply, I was confused between DevStack and regular installation! The first time I installed devStack using the stack.sh script everything was fine and I was able to login to dashboard, but it doesn't work anymore, I think after I changed the IP address of the machine and moved it to another network. When I try to login to Dashboard it fails with this message: Error: Unable to communicate with identity service: [Errno 111] Connection refused. (HTTP 400) It looks like some nova and keystone services are not running. So my question is how to check the status and restart all services in devStack? I can't use commands like "restart nova-api" because they are not installed. There should be other ways to start services in devStack. Thanks again, Joe On Tue, Jan 24, 2012 at 2:14 PM, Kiall Mac Innes wrote: > Hi Joe, > > DevStack is intended for installing an OpenStack development environment, > rather than a production or even pre-production test environment. > > For this reason, things like init scripts and config files are not installed > permanently. > > When using DevStack, you do not need to follow the instructions in the > various doc's, these steps are all performed automatically to give you a > clean development environment as fast as possible. > > Thanks, > Kiall > > On Tue, Jan 24, 2012 at 5:48 PM, Joe Smithian > wrote: >> >> Hi All, >> >> I installed OpenStack using devsatck script (http://devstack.org/) on >> Ubuntu 11.10. Installation was successful but there is no /etc/nova/ >> directory and It looks like that devstack script doesn't install all >> the nova services. Should I install them manually as described in the >> getting started documents? >> >> All the openStack are installed at /opt/stack/. Should I create >> symbolic link at /etc/nova? >> >> >> >> Thanks >> >> Joe >> >> ___ >> 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] No /etc/nova/nova.conf
There have been conversations about changing that. That nova should use /etc/nova/nova.conf Thoughts? On Tue, Jan 24, 2012 at 10:40 AM, Jorge Luiz Correa wrote: > When using Devstack the files are written to /opt/stack/. So, you > can find nova.conf in /opt/stack/nova/bin/. > > Regards. > > > On Tue, Jan 24, 2012 at 3:48 PM, Joe Smithian > wrote: >> >> Hi All, >> >> I installed OpenStack using devsatck script (http://devstack.org/) on >> Ubuntu 11.10. Installation was successful but there is no /etc/nova/ >> directory and It looks like that devstack script doesn't install all >> the nova services. Should I install them manually as described in the >> getting started documents? >> >> All the openStack are installed at /opt/stack/. Should I create >> symbolic link at /etc/nova? >> >> >> >> Thanks >> >> Joe >> >> ___ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp > > > > > -- > - MSc. Correa, J.L. > > > ___ > 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] No /etc/nova/nova.conf
Hi Joe, DevStack is intended for installing an OpenStack development environment, rather than a production or even pre-production test environment. For this reason, things like init scripts and config files are not installed permanently. When using DevStack, you do not need to follow the instructions in the various doc's, these steps are all performed automatically to give you a clean development environment as fast as possible. Thanks, Kiall On Tue, Jan 24, 2012 at 5:48 PM, Joe Smithian wrote: > Hi All, > > I installed OpenStack using devsatck script (http://devstack.org/) on > Ubuntu 11.10. Installation was successful but there is no /etc/nova/ > directory and It looks like that devstack script doesn't install all > the nova services. Should I install them manually as described in the > getting started documents? > > All the openStack are installed at /opt/stack/. Should I create > symbolic link at /etc/nova? > > > > Thanks > > Joe > > ___ > 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] Defining vm network
Hello everybody.
I am searching for some days but I can't figure out how to attach a vm to a
network?
I am using Quantum 2011.3 with OVS to create the network. And Diablo.
I am looking to something like:
$ nova boot --flavor 1 --image 2 *--nic net-id=* --key_name key
instance10
But in Diablo *--nic* does not work
I apreciate any help.
Thank you.
ps. I created the network and when I boot a vm nova-network.log returns
2012-01-24 18:27:34,941 DEBUG nova.network.quantum.quantum_connection [-]
Quantum Client Request:
POST /v1.0/tenants/default/networks/None/ports.json
from (pid=872) do_request /var/lib/nova/nova/network/quantum/client.py:176
2012-01-24 18:27:34,941 DEBUG nova.network.quantum.quantum_connection [-]
{"port": {"state": "ACTIVE"}} from (pid=872) do_request
/var/lib/nova/nova/network/quantum/client.py:178
2012-01-24 18:27:36,540 DEBUG nova.network.quantum.quantum_connection [-]
Quantum Client Reply (code = 420) :
{"networkNotFound": {"message": "Unable to find a network with the
specified identifier.", "code": 420, "detail": "Network None could not be
found"}} from (pid=872) do_request
/var/lib/nova/nova/network/quantum/client.py:187
2012-01-24 18:27:36,540 ERROR nova.rpc [-] Exception during message handling
(nova.rpc): TRACE: Traceback (most recent call last):
(nova.rpc): TRACE: File "/var/lib/nova/nova/rpc/impl_kombu.py", line 620,
in _process_data
(nova.rpc): TRACE: rval = node_func(context=ctxt, **node_args)
(nova.rpc): TRACE: File "/var/lib/nova/nova/network/quantum/manager.py",
line 175, in allocate_for_instance
(nova.rpc): TRACE: vif_rec['uuid'])
(nova.rpc): TRACE: File
"/var/lib/nova/nova/network/quantum/quantum_connection.py", line 86, in
create_and_attach_port
(nova.rpc): TRACE: resdict = self.client.create_port(net_id, port_data,
tenant=tenant_id)
(nova.rpc): TRACE: File "/var/lib/nova/nova/network/quantum/client.py",
line 81, in with_params
(nova.rpc): TRACE: ret = self.func(instance, *args)
(nova.rpc): TRACE: File "/var/lib/nova/nova/network/quantum/client.py",
line 277, in create_port
(nova.rpc): TRACE: return self.do_request("POST", self.ports_path %
(network), body=body)
(nova.rpc): TRACE: File "/var/lib/nova/nova/network/quantum/client.py",
line 202, in do_request
(nova.rpc): TRACE: % locals()))
(nova.rpc): TRACE: QuantumServerException: Server 420 error:
{"networkNotFound": {"message": "Unable to find a network with the
specified identifier.", "code": 420, "detail": "Network None could not be
found"}}
(nova.rpc): TRACE
--
Alisson Pontes
__
Network Technology Evolution Researcher
CPqD - Center for Research and Development in Telecommunications
Tel.: +55 19 3705-4996
apon...@cpqd.com.br
www.cpqd.com.br
___
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] No /etc/nova/nova.conf
When using Devstack the files are written to /opt/stack/. So, you can find nova.conf in /opt/stack/nova/bin/. Regards. On Tue, Jan 24, 2012 at 3:48 PM, Joe Smithian wrote: > Hi All, > > I installed OpenStack using devsatck script (http://devstack.org/) on > Ubuntu 11.10. Installation was successful but there is no /etc/nova/ > directory and It looks like that devstack script doesn't install all > the nova services. Should I install them manually as described in the > getting started documents? > > All the openStack are installed at /opt/stack/. Should I create > symbolic link at /etc/nova? > > > > Thanks > > Joe > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > -- - MSc. Correa, J.L. ___ 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] Proposal for new devstack (v2?)
Ok, I was using 6.1. Is there any reason that it isn't available for 6.1 and 6.2 (technically?) It would be nice to not have to distinguish (6.1 vs 6.2) in the new devstack v2. My guess is the list I created then was using the 6.1 repo, which may not have those pkgs (darn it). mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-6&arch=$basearch -Josh On 1/24/12 2:33 AM, "Pádraig Brady" wrote: On 01/24/2012 12:35 AM, Joshua Harlow wrote: > So some of the issues after doing a comparison might be the following: > > For RHEL6 + EPEL a lot of the packages are there (yippe!). Yes there has been lots of work in this area. See here for details: https://fedoraproject.org/wiki/OpenStack#OpenStack_in_EPEL > > https://github.com/yahoo/Openstack-Devstack2/tree/master/conf/pkgs > > Some issues which the EPEL people's might be able to resolve: > > db.json > > Seems ok. > > general.json > > euca2ools is much newer in ubuntu (2.0.0~bzr464-0ubuntu2 vs 1.3.1-12.el6). > python-coverage does not seem to exist in EPEL (or at least my repo setup). > That would be useful to have for testing (and CI). > python-pip versions (1.0-1 vs 0.8-1.el6) > python-nose versions (1.0.0-1ubuntu1 vs 0.10.4-3.1.el6) > > glance.json > > python-sqlalchemy versions (0.6.8-1 vs 0.5.5-2.1.el6) Note EPEL has parallel installable versions, so that there is no clash with RHEL versions. The openstack packages within EPEL explicitly select the parallel versions like: http://pkgs.fedoraproject.org/gitweb/?p=openstack-nova.git;a=blob_plain;f=openstack-nova-newdeps.patch;hb=el6 You can see the corresponding python-sqlalchemy0.7 and python-webob1.0 packages within EPEL. > python-wsgiref does not seem to exist in rhel6 (?) Well it's not used by openstack-glance in EPEL at least. > python-paste-deploy versions (1.5.0-2 vs 1.3.3-2.1.el6) > python-xattr versions (0.6-1ubuntu2 vs 0.5.0-1.el6) > python-httplib2 versiosn (0.7.1-1ubuntu1 vs 0.4.0-5.el6) > > horizon.json > > mod_wsgi versions (3.3-2ubuntu3 vs 3.2-1.el6) > python-paste versions (1.7.5.1-4ubuntu1 vs 1.7.4-1.el6) > python-paste-deploy versions (1.5.0-2 vs 1.3.3-2.1.el6) > python-routes versions (1.12.3-1 vs 1.10.3-2.el6) > python-xattr versions (0.6-1ubuntu2 vs 0.5.0-1.el6) > python-sqlalchemy versions (0.6.8-1 vs 0.5.5-2.1.el6) > python-webob versions (1.0.8-1 vs 0.9.6.1-3.el6) Parallel versions in EPEL as mentioned > python-cherrypy3 does not exist > python-django-mailer does not exist > python-django-nose does not exist Yes, these 3 might be candidates for EPEL. > python-migrate versions (0.7.1-1 vs 0.6-6.el6) 0.6-6.el6 has been patched to support sqlalchemy 0.7 > > keystone-client.json/nova-client.json > > Should be ok. > > keystone.json > > python-lxml versions (2.3-0.1build1 vs 2.2.3-1.1.el6) > python-paste-deploy versions (1.5.0-2 vs 1.3.3-2.1.el6) > python-paste versions (1.7.5.1-4ubuntu1 vs 1.7.4-1.el6) > python-sqlite2 versions (2.6.3-2 vs 2.3.5-2.el6) > python-sqlalchemy versions (0.6.8-1 vs 0.5.5-2.1.el6) > python-webob versions (1.0.8-1 vs 0.9.6.1-3.el6) > python-routes versions (1.12.3-1 vs 1.10.3-2.el6) > libldap2-dev and libsasl2-dev equivalents?? > > n-cpu.json/n-vol.json (nova cpu/volume) > > Should be ok > > n-vnc.json (nova novnc) > > python-numpy does not seem to exist > > nova.json > > python-xattr versions (0.6-1ubuntu2 vs 0.5.0-1.el6) > python-lxml versions (2.7.8.dfsg-4 vs 2.2.3-1.1.el6) > libvirt versions (0.9.2-4ubuntu15.1 vs 0.8.7-18.el6) > vlan package? > python-migrate versions (0.7.1-1 vs 0.6-6.el6) > python-gflags versions (1.5.1-1 vs 1.4-3.el6) > libvirt-python versions (0.9.2-4ubuntu15.1 vs 0.8.7-18.el6) > python-routes versions (1.12.3-1 vs 1.10.3-2.el6) > python-paste-deploy versions (1.5.0-2 vs 1.3.3-2.1.el6) > python-tempita versions (0.5.1-1 vs 0.4-2.el6) > python-sqlalchemy versions (0.6.8-1 vs 0.5.5-2.1.el6) > > I will start to get the tests going to see if the version differences are > actually a problem. I am assuming large version differences will be an issue. > But its hard to tell how much of an issue yet. But it would be really great > if we could just get all those up to the same versions. Then possibly in the > future we can get RHEL6 (or equiv) hooked into the CI pipeline to ensure that > new versions/packages work on all distributions that openstack wants to > support. That way it ensures that packages and versions are uniform (or as > close to possible to uniform) and will work with the supported code. glance and nova should work well on RH6.2 + EPEL at least. cheers, Pádraig. ___ 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] Proposal for new devstack (v2?)
Although yes package managers do know how to pick up a version, they sometimes do this automatically with a newer version (if u leave out the version). This then brings back the problem of how exactly do people with other distributions know what version is going to work if the package manager selects the versions. Having it in the file at least gives people the knowledge that the given version was used by developers for creating a given openstack release and should be stable if they ever want to install that release in the future. Distromatch might make sense, but it still doesn't resolve the version issue (I am not an expert on distromatch). Right now this is (but hopefully won't be in the future) a big pain when trying to get openstack running (or even developed on) in another distribution. How do we know which version developers have been using, well we go to ubuntu 11, check that version and hope that the version is available in the other distribution (this is problematic since if its not and say its a python version, then u have to pray that the package will have all the necessary functions/classes - since python won't check until called, thanks to duck typing). So even though yes there are a lot of versions specified and a lot of packages specified it does seem like this is what is needed for a large project like openstack. I've seen ubuntu switch out versions sometimes though (ie blah-ubuntu1 to blah-ubuntu2), so I am not sure about 1 version, 1 active version maybe, but for a large project should the openstack community just expect that blah-ubuntu2 will work for everyone (hopefully nothing major changed between 1 and 2). Since everyone at openstack was say developing with blah-ubuntu1, changing to blah-ubuntu2 shouldn't happen unless its really needed since this may cause regressions or other problems. -Josh On 1/24/12 2:57 AM, "Bernhard M. Wiedemann" wrote: On 01/17/2012 08:20 PM, Joshua Harlow wrote: > My goals were/are/(may continue to be, haha) the following: > > > 1. Add in enough abstraction so that you can look at how each component is > installed/uninstalled/started/stopped by looking at a single file (maybe 2 > files) > 2. Have the ability to start/stop in different manners (not always screen) > 3. Have the ability to have pkg/pip installation (and definition separate > from the main code, already starting to be done), in more than 1 distro. > * This allows others to easily know what versions of packages work for > a given openstack release for more than one distro (yes that's right, more > than ubuntu) > 4. Increase the level of documentation (probably not going to be in the > end, inline like what is in devstack, since that just doesn't seem > maintainable in the long-term) > * This may mean having documentation created similar to nova, glance, > as a separate documentation document/page > > Still be simple "enough" to run and use so that the non-python dev can > install from trunk without having to understand what is going on. > > -Josh I was looking into how easy it would be to support openSUSE / SLES in devstack v2 and saw that there are currently 17 json files containing package names (with 293 versions) for ubuntu-oneiric and rhel-6. Shouldn't there be some better way than to list all this redundant information there, which makes it hard to maintain/extend? E.g. the distro's package manager already knows about dependencies and usually has just one version of a package for a given distribution anyway. And there was even one project about mapping package-names of one Linux distribution to another: http://enricozini.org/2011/debian/distromatch/ So it should be possible to build upon it, and just list packages once. Ciao Bernhard M. ___ 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] [nova client] Can't get the diagnostics command to work
I've just verified this against my install, but since the diagnostics is
unsupported when using libvirt/kvm, it still errors out (but with a 500,
rather than 404)
Thanks,
Kiall
On Tue, Jan 24, 2012 at 5:56 PM, Brian Waldon wrote:
> Actually the diagnostics command was not added in Essex, but it was
> converted to a true extension. However it is part of the Admin API, which
> means for Diablo you need to set the allow_admin_api flag on your nova-api
> node.
>
>
> On Jan 24, 2012, at 9:41 AM, Kiall Mac Innes wrote:
>
> Hi,
>
> The diagnostics command was added in Essex, my packages are using the
> stable Diablo version.
>
> Novaclient sadly shows these options even though they can't be used with
> Diablo.
>
> Kiall
>
> Sent from my mobile - Sorry for being short.
> On Jan 24, 2012 5:04 p.m., "Leander Bessa" wrote:
>
>> Hello,
>>
>> I've setup a single node configuration with keystone using the packages
>> from https://launchpad.net/~managedit/+archive/openstack.
>>
>> I've managed to launch an instance, however when i run the commando nova
>> diagnostics i get this:
>>
>> REQ: curl -i http://127.0.0.1:5000/tokens -X POST -H "Content-Type:
>> application/json" -H "User-Agent: python-novaclient"
>>
>> REQ BODY: {"auth": {"tenantName": "admin", "passwordCredentials":
>> {"username": "admin", "password": "admin"}}}
>>
>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '200',
>> 'content-length': '1119', 'content-type': 'application/json;
>> charset=UTF-8'} {"access": {"token": {"expires": "2015-02-05T00:00:00",
>> "id": "999888777666", "tenant": {"id": "1", "name": "admin"}},
>> "serviceCatalog": [{"endpoints": [{"adminURL": "
>> http://127.0.0.1:8774/v1.1/1";, "region": "RegionOne", "internalURL": "
>> http://127.0.0.1:8774/v1.1/1";, "publicURL": "http://127.0.0.1:8774/v1.1/1"}],
>> "type": "compute", "name": "nova"}, {"endpoints": [{"adminURL": "
>> http://127.0.0.1:8774/v1.0";, "region": "RegionOne", "internalURL": "
>> http://127.0.0.1:8774/v1.0";, "publicURL": "http://127.0.0.1:8774/v1.0/"}],
>> "type": "compute", "name": "nova_compat"}, {"endpoints": [{"adminURL": "
>> http://127.0.0.1:9292/v1.1/1";, "region": "RegionOne", "internalURL": "
>> http://127.0.0.1:9292/v1.1/1";, "publicURL": "http://127.0.0.1:9292/v1.1/1"}],
>> "type": "image", "name": "glance"}, {"endpoints": [{"adminURL": "
>> http://127.0.0.1:35357/v2.0";, "region": "RegionOne", "internalURL": "
>> http://127.0.0.1:5000/v2.0";, "publicURL": "http://127.0.0.1:5000/v2.0"}],
>> "type": "identity", "name": "identity"}], "user": {"id": "1", "roles":
>> [{"tenantId": "1", "id": "1", "name": "Admin"}, {"id": "1", "name":
>> "Admin"}], "name": "admin"}}}
>>
>> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET
>> -H "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
>> "X-Auth-Token: 999888777666"
>>
>> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET
>> -H "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
>> "X-Auth-Token: 999888777666"
>>
>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
>> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404
>> Not Found
>>
>> The resource could not be found.
>>
>>
>>
>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
>> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404
>> Not Found
>>
>> The resource could not be found.
>>
>>
>> n/a (HTTP 404)
>>
>>
>> Any ideas?
>>
>> Regards,
>>
>> Leander
>>
>> ___
>> 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
>
>
>
___
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] [nova client] Can't get the diagnostics command to work
My assumption here was actually incorrect. See my follow-up email for a
suggested fix.
On Jan 24, 2012, at 9:46 AM, Brian Waldon wrote:
> The diagnostics command moved to a server action. We will need to update
> novaclient to support this. I went ahead and filed a bug for it:
> https://bugs.launchpad.net/nova/+bug/921103
> On Jan 24, 2012, at 9:03 AM, Leander Bessa wrote:
>
>> Hello,
>>
>> I've setup a single node configuration with keystone using the packages from
>> https://launchpad.net/~managedit/+archive/openstack.
>>
>> I've managed to launch an instance, however when i run the commando nova
>> diagnostics i get this:
>>
>> REQ: curl -i http://127.0.0.1:5000/tokens -X POST -H "Content-Type:
>> application/json" -H "User-Agent: python-novaclient"
>>
>> REQ BODY: {"auth": {"tenantName": "admin", "passwordCredentials":
>> {"username": "admin", "password": "admin"}}}
>>
>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '200',
>> 'content-length': '1119', 'content-type': 'application/json; charset=UTF-8'}
>> {"access": {"token": {"expires": "2015-02-05T00:00:00", "id":
>> "999888777666", "tenant": {"id": "1", "name": "admin"}}, "serviceCatalog":
>> [{"endpoints": [{"adminURL": "http://127.0.0.1:8774/v1.1/1";, "region":
>> "RegionOne", "internalURL": "http://127.0.0.1:8774/v1.1/1";, "publicURL":
>> "http://127.0.0.1:8774/v1.1/1"}], "type": "compute", "name": "nova"},
>> {"endpoints": [{"adminURL": "http://127.0.0.1:8774/v1.0";, "region":
>> "RegionOne", "internalURL": "http://127.0.0.1:8774/v1.0";, "publicURL":
>> "http://127.0.0.1:8774/v1.0/"}], "type": "compute", "name": "nova_compat"},
>> {"endpoints": [{"adminURL": "http://127.0.0.1:9292/v1.1/1";, "region":
>> "RegionOne", "internalURL": "http://127.0.0.1:9292/v1.1/1";, "publicURL":
>> "http://127.0.0.1:9292/v1.1/1"}], "type": "image", "name": "glance"},
>> {"endpoints": [{"adminURL": "http://127.0.0.1:35357/v2.0";, "region":
>> "RegionOne", "internalURL": "http://127.0.0.1:5000/v2.0";, "publicURL":
>> "http://127.0.0.1:5000/v2.0"}], "type": "identity", "name": "identity"}],
>> "user": {"id": "1", "roles": [{"tenantId": "1", "id": "1", "name": "Admin"},
>> {"id": "1", "name": "Admin"}], "name": "admin"}}}
>>
>> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
>> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
>> "X-Auth-Token: 999888777666"
>>
>> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
>> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
>> "X-Auth-Token: 999888777666"
>>
>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
>> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404 Not
>> Found
>>
>> The resource could not be found.
>>
>>
>>
>> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
>> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404 Not
>> Found
>>
>> The resource could not be found.
>>
>>
>> n/a (HTTP 404)
>>
>>
>> Any ideas?
>>
>> Regards,
>>
>> Leander
>> ___
>> 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
___
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] [nova client] Can't get the diagnostics command to work
Actually the diagnostics command was not added in Essex, but it was converted
to a true extension. However it is part of the Admin API, which means for
Diablo you need to set the allow_admin_api flag on your nova-api node.
On Jan 24, 2012, at 9:41 AM, Kiall Mac Innes wrote:
> Hi,
>
> The diagnostics command was added in Essex, my packages are using the stable
> Diablo version.
>
> Novaclient sadly shows these options even though they can't be used with
> Diablo.
>
> Kiall
>
> Sent from my mobile - Sorry for being short.
>
> On Jan 24, 2012 5:04 p.m., "Leander Bessa" wrote:
> Hello,
>
> I've setup a single node configuration with keystone using the packages from
> https://launchpad.net/~managedit/+archive/openstack.
>
> I've managed to launch an instance, however when i run the commando nova
> diagnostics i get this:
>
> REQ: curl -i http://127.0.0.1:5000/tokens -X POST -H "Content-Type:
> application/json" -H "User-Agent: python-novaclient"
>
> REQ BODY: {"auth": {"tenantName": "admin", "passwordCredentials":
> {"username": "admin", "password": "admin"}}}
>
> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '200',
> 'content-length': '1119', 'content-type': 'application/json; charset=UTF-8'}
> {"access": {"token": {"expires": "2015-02-05T00:00:00", "id": "999888777666",
> "tenant": {"id": "1", "name": "admin"}}, "serviceCatalog": [{"endpoints":
> [{"adminURL": "http://127.0.0.1:8774/v1.1/1";, "region": "RegionOne",
> "internalURL": "http://127.0.0.1:8774/v1.1/1";, "publicURL":
> "http://127.0.0.1:8774/v1.1/1"}], "type": "compute", "name": "nova"},
> {"endpoints": [{"adminURL": "http://127.0.0.1:8774/v1.0";, "region":
> "RegionOne", "internalURL": "http://127.0.0.1:8774/v1.0";, "publicURL":
> "http://127.0.0.1:8774/v1.0/"}], "type": "compute", "name": "nova_compat"},
> {"endpoints": [{"adminURL": "http://127.0.0.1:9292/v1.1/1";, "region":
> "RegionOne", "internalURL": "http://127.0.0.1:9292/v1.1/1";, "publicURL":
> "http://127.0.0.1:9292/v1.1/1"}], "type": "image", "name": "glance"},
> {"endpoints": [{"adminURL": "http://127.0.0.1:35357/v2.0";, "region":
> "RegionOne", "internalURL": "http://127.0.0.1:5000/v2.0";, "publicURL":
> "http://127.0.0.1:5000/v2.0"}], "type": "identity", "name": "identity"}],
> "user": {"id": "1", "roles": [{"tenantId": "1", "id": "1", "name": "Admin"},
> {"id": "1", "name": "Admin"}], "name": "admin"}}}
>
> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
> "X-Auth-Token: 999888777666"
>
> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
> "X-Auth-Token: 999888777666"
>
> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404 Not
> Found
>
> The resource could not be found.
>
>
>
> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404 Not
> Found
>
> The resource could not be found.
>
>
> n/a (HTTP 404)
>
>
> Any ideas?
>
> Regards,
>
> Leander
>
> ___
> 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
___
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] [nova client] Can't get the diagnostics command to work
Oh, I had thought it didn't exist in Diablo.. My mistake!
Thanks,
Kiall
On Tue, Jan 24, 2012 at 5:46 PM, Brian Waldon wrote:
> The diagnostics command moved to a server action. We will need to update
> novaclient to support this. I went ahead and filed a bug for it:
> https://bugs.launchpad.net/nova/+bug/921103
> On Jan 24, 2012, at 9:03 AM, Leander Bessa wrote:
>
> Hello,
>
> I've setup a single node configuration with keystone using the packages
> from https://launchpad.net/~managedit/+archive/openstack.
>
> I've managed to launch an instance, however when i run the commando nova
> diagnostics i get this:
>
> REQ: curl -i http://127.0.0.1:5000/tokens -X POST -H "Content-Type:
> application/json" -H "User-Agent: python-novaclient"
>
> REQ BODY: {"auth": {"tenantName": "admin", "passwordCredentials":
> {"username": "admin", "password": "admin"}}}
>
> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '200',
> 'content-length': '1119', 'content-type': 'application/json;
> charset=UTF-8'} {"access": {"token": {"expires": "2015-02-05T00:00:00",
> "id": "999888777666", "tenant": {"id": "1", "name": "admin"}},
> "serviceCatalog": [{"endpoints": [{"adminURL": "
> http://127.0.0.1:8774/v1.1/1";, "region": "RegionOne", "internalURL": "
> http://127.0.0.1:8774/v1.1/1";, "publicURL": "http://127.0.0.1:8774/v1.1/1"}],
> "type": "compute", "name": "nova"}, {"endpoints": [{"adminURL": "
> http://127.0.0.1:8774/v1.0";, "region": "RegionOne", "internalURL": "
> http://127.0.0.1:8774/v1.0";, "publicURL": "http://127.0.0.1:8774/v1.0/"}],
> "type": "compute", "name": "nova_compat"}, {"endpoints": [{"adminURL": "
> http://127.0.0.1:9292/v1.1/1";, "region": "RegionOne", "internalURL": "
> http://127.0.0.1:9292/v1.1/1";, "publicURL": "http://127.0.0.1:9292/v1.1/1"}],
> "type": "image", "name": "glance"}, {"endpoints": [{"adminURL": "
> http://127.0.0.1:35357/v2.0";, "region": "RegionOne", "internalURL": "
> http://127.0.0.1:5000/v2.0";, "publicURL": "http://127.0.0.1:5000/v2.0"}],
> "type": "identity", "name": "identity"}], "user": {"id": "1", "roles":
> [{"tenantId": "1", "id": "1", "name": "Admin"}, {"id": "1", "name":
> "Admin"}], "name": "admin"}}}
>
> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
> "X-Auth-Token: 999888777666"
>
> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
> "X-Auth-Token: 999888777666"
>
> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404
> Not Found
>
> The resource could not be found.
>
>
>
> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404
> Not Found
>
> The resource could not be found.
>
>
> n/a (HTTP 404)
>
>
> Any ideas?
>
> Regards,
>
> Leander
> ___
> 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
>
>
___
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] No /etc/nova/nova.conf
Hi All, I installed OpenStack using devsatck script (http://devstack.org/) on Ubuntu 11.10. Installation was successful but there is no /etc/nova/ directory and It looks like that devstack script doesn't install all the nova services. Should I install them manually as described in the getting started documents? All the openStack are installed at /opt/stack/. Should I create symbolic link at /etc/nova? Thanks Joe ___ 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] [nova client] Can't get the diagnostics command to work
The diagnostics command moved to a server action. We will need to update
novaclient to support this. I went ahead and filed a bug for it:
https://bugs.launchpad.net/nova/+bug/921103
On Jan 24, 2012, at 9:03 AM, Leander Bessa wrote:
> Hello,
>
> I've setup a single node configuration with keystone using the packages from
> https://launchpad.net/~managedit/+archive/openstack.
>
> I've managed to launch an instance, however when i run the commando nova
> diagnostics i get this:
>
> REQ: curl -i http://127.0.0.1:5000/tokens -X POST -H "Content-Type:
> application/json" -H "User-Agent: python-novaclient"
>
> REQ BODY: {"auth": {"tenantName": "admin", "passwordCredentials":
> {"username": "admin", "password": "admin"}}}
>
> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '200',
> 'content-length': '1119', 'content-type': 'application/json; charset=UTF-8'}
> {"access": {"token": {"expires": "2015-02-05T00:00:00", "id": "999888777666",
> "tenant": {"id": "1", "name": "admin"}}, "serviceCatalog": [{"endpoints":
> [{"adminURL": "http://127.0.0.1:8774/v1.1/1";, "region": "RegionOne",
> "internalURL": "http://127.0.0.1:8774/v1.1/1";, "publicURL":
> "http://127.0.0.1:8774/v1.1/1"}], "type": "compute", "name": "nova"},
> {"endpoints": [{"adminURL": "http://127.0.0.1:8774/v1.0";, "region":
> "RegionOne", "internalURL": "http://127.0.0.1:8774/v1.0";, "publicURL":
> "http://127.0.0.1:8774/v1.0/"}], "type": "compute", "name": "nova_compat"},
> {"endpoints": [{"adminURL": "http://127.0.0.1:9292/v1.1/1";, "region":
> "RegionOne", "internalURL": "http://127.0.0.1:9292/v1.1/1";, "publicURL":
> "http://127.0.0.1:9292/v1.1/1"}], "type": "image", "name": "glance"},
> {"endpoints": [{"adminURL": "http://127.0.0.1:35357/v2.0";, "region":
> "RegionOne", "internalURL": "http://127.0.0.1:5000/v2.0";, "publicURL":
> "http://127.0.0.1:5000/v2.0"}], "type": "identity", "name": "identity"}],
> "user": {"id": "1", "roles": [{"tenantId": "1", "id": "1", "name": "Admin"},
> {"id": "1", "name": "Admin"}], "name": "admin"}}}
>
> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
> "X-Auth-Token: 999888777666"
>
> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
> "X-Auth-Token: 999888777666"
>
> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404 Not
> Found
>
> The resource could not be found.
>
>
>
> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404 Not
> Found
>
> The resource could not be found.
>
>
> n/a (HTTP 404)
>
>
> Any ideas?
>
> Regards,
>
> Leander
> ___
> 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] [nova client] Can't get the diagnostics command to work
Hi,
The diagnostics command was added in Essex, my packages are using the
stable Diablo version.
Novaclient sadly shows these options even though they can't be used with
Diablo.
Kiall
Sent from my mobile - Sorry for being short.
On Jan 24, 2012 5:04 p.m., "Leander Bessa" wrote:
> Hello,
>
> I've setup a single node configuration with keystone using the packages
> from https://launchpad.net/~managedit/+archive/openstack.
>
> I've managed to launch an instance, however when i run the commando nova
> diagnostics i get this:
>
> REQ: curl -i http://127.0.0.1:5000/tokens -X POST -H "Content-Type:
> application/json" -H "User-Agent: python-novaclient"
>
> REQ BODY: {"auth": {"tenantName": "admin", "passwordCredentials":
> {"username": "admin", "password": "admin"}}}
>
> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '200',
> 'content-length': '1119', 'content-type': 'application/json;
> charset=UTF-8'} {"access": {"token": {"expires": "2015-02-05T00:00:00",
> "id": "999888777666", "tenant": {"id": "1", "name": "admin"}},
> "serviceCatalog": [{"endpoints": [{"adminURL": "
> http://127.0.0.1:8774/v1.1/1";, "region": "RegionOne", "internalURL": "
> http://127.0.0.1:8774/v1.1/1";, "publicURL": "http://127.0.0.1:8774/v1.1/1"}],
> "type": "compute", "name": "nova"}, {"endpoints": [{"adminURL": "
> http://127.0.0.1:8774/v1.0";, "region": "RegionOne", "internalURL": "
> http://127.0.0.1:8774/v1.0";, "publicURL": "http://127.0.0.1:8774/v1.0/"}],
> "type": "compute", "name": "nova_compat"}, {"endpoints": [{"adminURL": "
> http://127.0.0.1:9292/v1.1/1";, "region": "RegionOne", "internalURL": "
> http://127.0.0.1:9292/v1.1/1";, "publicURL": "http://127.0.0.1:9292/v1.1/1"}],
> "type": "image", "name": "glance"}, {"endpoints": [{"adminURL": "
> http://127.0.0.1:35357/v2.0";, "region": "RegionOne", "internalURL": "
> http://127.0.0.1:5000/v2.0";, "publicURL": "http://127.0.0.1:5000/v2.0"}],
> "type": "identity", "name": "identity"}], "user": {"id": "1", "roles":
> [{"tenantId": "1", "id": "1", "name": "Admin"}, {"id": "1", "name":
> "Admin"}], "name": "admin"}}}
>
> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
> "X-Auth-Token: 999888777666"
>
> REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
> "X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
> "X-Auth-Token: 999888777666"
>
> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404
> Not Found
>
> The resource could not be found.
>
>
>
> RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
> 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404
> Not Found
>
> The resource could not be found.
>
>
> n/a (HTTP 404)
>
>
> Any ideas?
>
> Regards,
>
> Leander
>
> ___
> 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] [nova client] Can't get the diagnostics command to work
Hello,
I've setup a single node configuration with keystone using the packages
from https://launchpad.net/~managedit/+archive/openstack.
I've managed to launch an instance, however when i run the commando nova
diagnostics i get this:
REQ: curl -i http://127.0.0.1:5000/tokens -X POST -H "Content-Type:
application/json" -H "User-Agent: python-novaclient"
REQ BODY: {"auth": {"tenantName": "admin", "passwordCredentials":
{"username": "admin", "password": "admin"}}}
RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '200',
'content-length': '1119', 'content-type': 'application/json;
charset=UTF-8'} {"access": {"token": {"expires": "2015-02-05T00:00:00",
"id": "999888777666", "tenant": {"id": "1", "name": "admin"}},
"serviceCatalog": [{"endpoints": [{"adminURL": "http://127.0.0.1:8774/v1.1/1";,
"region": "RegionOne", "internalURL": "http://127.0.0.1:8774/v1.1/1";,
"publicURL": "http://127.0.0.1:8774/v1.1/1"}], "type": "compute", "name":
"nova"}, {"endpoints": [{"adminURL": "http://127.0.0.1:8774/v1.0";,
"region": "RegionOne", "internalURL": "http://127.0.0.1:8774/v1.0";,
"publicURL": "http://127.0.0.1:8774/v1.0/"}], "type": "compute", "name":
"nova_compat"}, {"endpoints": [{"adminURL": "http://127.0.0.1:9292/v1.1/1";,
"region": "RegionOne", "internalURL": "http://127.0.0.1:9292/v1.1/1";,
"publicURL": "http://127.0.0.1:9292/v1.1/1"}], "type": "image", "name":
"glance"}, {"endpoints": [{"adminURL": "http://127.0.0.1:35357/v2.0";,
"region": "RegionOne", "internalURL": "http://127.0.0.1:5000/v2.0";,
"publicURL": "http://127.0.0.1:5000/v2.0"}], "type": "identity", "name":
"identity"}], "user": {"id": "1", "roles": [{"tenantId": "1", "id": "1",
"name": "Admin"}, {"id": "1", "name": "Admin"}], "name": "admin"}}}
REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
"X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
"X-Auth-Token: 999888777666"
REQ: curl -i http://127.0.0.1:8774/v1.1/1/servers/3/diagnostics -X GET -H
"X-Auth-Project-Id: admin" -H "User-Agent: python-novaclient" -H
"X-Auth-Token: 999888777666"
RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404
Not Found
The resource could not be found.
RESP:{'date': 'Tue, 24 Jan 2012 16:56:24 GMT', 'status': '404',
'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'} 404
Not Found
The resource could not be found.
n/a (HTTP 404)
Any ideas?
Regards,
Leander
___
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] Reminder: OpenStack Project meeting - 21:00 UTC
Hello everyone, Our weekly project & release status meeting will take place at 21:00 UTC this Tuesday in #openstack-meeting on IRC. PTLs, if you can't make it, please name a substitute on [2]. Today is the *last* day before we cut Essex-3 milestone branches. Since E3 serves as a feature freeze milestone for Keystone, Glance and Nova, we'll be looking at unreached targets and defer them where necessary. You can doublecheck what 21:00 UTC means for your timezone at [1]: [1] http://www.timeanddate.com/worldclock/fixedtime.html?iso=20120124T21 See the meeting agenda, edit the wiki to add new topics for discussion: [2] http://wiki.openstack.org/Meetings/ProjectMeeting Cheers, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ 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] Proposal for new devstack (v2?)
On 01/17/2012 08:20 PM, Joshua Harlow wrote: My goals were/are/(may continue to be, haha) the following: 1. Add in enough abstraction so that you can look at how each component is installed/uninstalled/started/stopped by looking at a single file (maybe 2 files) 2. Have the ability to start/stop in different manners (not always screen) 3. Have the ability to have pkg/pip installation (and definition separate from the main code, already starting to be done), in more than 1 distro. * This allows others to easily know what versions of packages work for a given openstack release for more than one distro (yes that's right, more than ubuntu) 4. Increase the level of documentation (probably not going to be in the end, inline like what is in devstack, since that just doesn't seem maintainable in the long-term) * This may mean having documentation created similar to nova, glance, as a separate documentation document/page Still be simple "enough" to run and use so that the non-python dev can install from trunk without having to understand what is going on. -Josh I was looking into how easy it would be to support openSUSE / SLES in devstack v2 and saw that there are currently 17 json files containing package names (with 293 versions) for ubuntu-oneiric and rhel-6. Shouldn't there be some better way than to list all this redundant information there, which makes it hard to maintain/extend? E.g. the distro's package manager already knows about dependencies and usually has just one version of a package for a given distribution anyway. And there was even one project about mapping package-names of one Linux distribution to another: http://enricozini.org/2011/debian/distromatch/ So it should be possible to build upon it, and just list packages once. Ciao Bernhard M. ___ 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] Proposal for new devstack (v2?)
On 01/24/2012 12:35 AM, Joshua Harlow wrote: > So some of the issues after doing a comparison might be the following: > > For RHEL6 + EPEL a lot of the packages are there (yippe!). Yes there has been lots of work in this area. See here for details: https://fedoraproject.org/wiki/OpenStack#OpenStack_in_EPEL > > https://github.com/yahoo/Openstack-Devstack2/tree/master/conf/pkgs > > Some issues which the EPEL people’s might be able to resolve: > > db.json > > Seems ok. > > general.json > > euca2ools is much newer in ubuntu (2.0.0~bzr464-0ubuntu2 vs 1.3.1-12.el6). > python-coverage does not seem to exist in EPEL (or at least my repo setup). > That would be useful to have for testing (and CI). > python-pip versions (1.0-1 vs 0.8-1.el6) > python-nose versions (1.0.0-1ubuntu1 vs 0.10.4-3.1.el6) > > glance.json > > python-sqlalchemy versions (0.6.8-1 vs 0.5.5-2.1.el6) Note EPEL has parallel installable versions, so that there is no clash with RHEL versions. The openstack packages within EPEL explicitly select the parallel versions like: http://pkgs.fedoraproject.org/gitweb/?p=openstack-nova.git;a=blob_plain;f=openstack-nova-newdeps.patch;hb=el6 You can see the corresponding python-sqlalchemy0.7 and python-webob1.0 packages within EPEL. > python-wsgiref does not seem to exist in rhel6 (?) Well it's not used by openstack-glance in EPEL at least. > python-paste-deploy versions (1.5.0-2 vs 1.3.3-2.1.el6) > python-xattr versions (0.6-1ubuntu2 vs 0.5.0-1.el6) > python-httplib2 versiosn (0.7.1-1ubuntu1 vs 0.4.0-5.el6) > > horizon.json > > mod_wsgi versions (3.3-2ubuntu3 vs 3.2-1.el6) > python-paste versions (1.7.5.1-4ubuntu1 vs 1.7.4-1.el6) > python-paste-deploy versions (1.5.0-2 vs 1.3.3-2.1.el6) > python-routes versions (1.12.3-1 vs 1.10.3-2.el6) > python-xattr versions (0.6-1ubuntu2 vs 0.5.0-1.el6) > python-sqlalchemy versions (0.6.8-1 vs 0.5.5-2.1.el6) > python-webob versions (1.0.8-1 vs 0.9.6.1-3.el6) Parallel versions in EPEL as mentioned > python-cherrypy3 does not exist > python-django-mailer does not exist > python-django-nose does not exist Yes, these 3 might be candidates for EPEL. > python-migrate versions (0.7.1-1 vs 0.6-6.el6) 0.6-6.el6 has been patched to support sqlalchemy 0.7 > > keystone-client.json/nova-client.json > > Should be ok. > > keystone.json > > python-lxml versions (2.3-0.1build1 vs 2.2.3-1.1.el6) > python-paste-deploy versions (1.5.0-2 vs 1.3.3-2.1.el6) > python-paste versions (1.7.5.1-4ubuntu1 vs 1.7.4-1.el6) > python-sqlite2 versions (2.6.3-2 vs 2.3.5-2.el6) > python-sqlalchemy versions (0.6.8-1 vs 0.5.5-2.1.el6) > python-webob versions (1.0.8-1 vs 0.9.6.1-3.el6) > python-routes versions (1.12.3-1 vs 1.10.3-2.el6) > libldap2-dev and libsasl2-dev equivalents?? > > n-cpu.json/n-vol.json (nova cpu/volume) > > Should be ok > > n-vnc.json (nova novnc) > > python-numpy does not seem to exist > > nova.json > > python-xattr versions (0.6-1ubuntu2 vs 0.5.0-1.el6) > python-lxml versions (2.7.8.dfsg-4 vs 2.2.3-1.1.el6) > libvirt versions (0.9.2-4ubuntu15.1 vs 0.8.7-18.el6) > vlan package? > python-migrate versions (0.7.1-1 vs 0.6-6.el6) > python-gflags versions (1.5.1-1 vs 1.4-3.el6) > libvirt-python versions (0.9.2-4ubuntu15.1 vs 0.8.7-18.el6) > python-routes versions (1.12.3-1 vs 1.10.3-2.el6) > python-paste-deploy versions (1.5.0-2 vs 1.3.3-2.1.el6) > python-tempita versions (0.5.1-1 vs 0.4-2.el6) > python-sqlalchemy versions (0.6.8-1 vs 0.5.5-2.1.el6) > > I will start to get the tests going to see if the version differences are > actually a problem. I am assuming large version differences will be an issue. > But its hard to tell how much of an issue yet. But it would be really great > if we could just get all those up to the same versions. Then possibly in the > future we can get RHEL6 (or equiv) hooked into the CI pipeline to ensure that > new versions/packages work on all distributions that openstack wants to > support. That way it ensures that packages and versions are uniform (or as > close to possible to uniform) and will work with the supported code. glance and nova should work well on RH6.2 + EPEL at least. cheers, Pádraig. ___ 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] XCP and Openstack questions
Hi Ewan, Thanks *a lot* for your very accurate and long reply. That's going to help me so much for working on the Nova + XCP packaging in Debian. On 01/24/2012 06:19 AM, Ewan Mellor wrote: >> I already started writing a README.xcp_and_openstack to document how to >> do an Openstack + XCP setup. > > Thanks for doing this! Your hard work is very much appreciated. I'm happy if I can do my part of the job too! :) >> But would the VLan manage work? Also, should I use openvswitch? If yes, >> how does this work? > > Flat, VLAN, and the various HA modes should all work. > Flat is by far the simplest for getting started with though. My final goal is to be able to resell Openstack cloud instances, and in that case, only VLAN is the way to go, IMO. > Open vSwitch would be a good idea. It's what we use on XenServer 6.0 onwards, > so it's well tested. Very cool! That is, I believe, the best way you could have taken. > Is it packaged for Sid? Yes: http://packages.debian.org/search?keywords=openvswitch > If you have the Open vSwitch components installed in domain 0, then there > are a few scripts that wrap around it to set up the isolation rules used > in flat mode. These are in nova/plugins/xenapi/networking. I believe you mean: plugins/xenserver/networking Nova in Debian now creates a nova-xcp-plugins taking files from plugins/xenserver/xenapi/. I now believe that I should also make a nova-xcp-network package. Having a quick look at the files in the plugins/xenserver/networking folder, these would need some re-work. For example, the init.d scripts are lacking LSB headers (to be used by insserv for parallel booting), and also there's an etc/sysconfig, which really, is too much CentOS / RedHat centric (in Debian, it would go in /etc/default). Now, I saw files in etc/xensource/scripts. I suppose that these, in Debian, to respect both FHS and the work we've done with Mike and Jon, these files should go in /usr/lib/xcp/scripts/. I just hope there's no references to the wrong CentOS path in these scripts! If you know things that should be adapted right away, it'd be great to have the fixes made for runtime, rather than a Debian specific patch, IMO, because patches are annoying to maintain. You can expect that I will contribute these adaptations for Debian in the next following days, and also fix the packaging to add this new nova-xcp-network binary package. I will let you know how it goes. >> Does OpenStack + XCP still use nova-network? Is all traffic for the VMs >> routed through it as with KVM and libvirt? Should I still create a >> bridge on the nova-network domU? > > It depends on which network mode you're using. If you're using the > HA modes, then yes, traffic goes through nova-network. In flat mode > it will come directly to domain 0 and the vSwitch. And using the VLAN manager? > Devstack has all of the domU setup for HA networking > -- see https://blueprints.launchpad.net/nova/+spec/xenapi-ha-nova-network. I've always been directed to devstack, however, I'm really not interested at all in using it: I'm working on packaging things correctly for Debian, and as a consequence, I want to use *only* the Debian packages that we produce. Of course, I'll keep updating and modifying them until it works. >> How does Openstack injects IP addresses in an XCP VM? Can this even be >> done? > > It talks to an in-guest agent, typically. It writes it to XenStore, and > then this is picked up by the agent inside the VM. So, running the XCP software inside the VM is mandatory? If so, this should change IMO, it's really not hosting provider friendly: customers expect to take any AMI image, possibly from AWS, and run them on the cloud, we can't force customers to use specific VM images for XCP. >> Should I use dnsmaq on my nova domU? > > I don't think you need it. There's a comment in devstack that says > that the dnsmasq packages are needed for dhcp_release though, so > you may want to make sure that you have that at least. Not a pb then! I'll have it setup, if it's there and not used, it's not a big deal. > I'm not sure, but I think you're asking about this: > http://docs.openstack.org/diablo/openstack-compute/admin/content/associating-public-ip.html. Thanks, that's what I was looking for. > Security groups have only recently been implemented for XenAPI: > https://blueprints.launchpad.net/nova/+spec/xenapi-security-groups. > That got merged less than two weeks ago. Will this be in e3? FYI, I chatted with Ghe Rivero on IRC, who is also working on nova packaging. His plan is that, in Debian, we will release e3 in SID when e3 is out. >> 2/ Images >> What are OVF images? How to generate it? Where to download some? > > http://en.wikipedia.org/wiki/Open_Virtualization_Format > > They can be exported from XenServer using XenCenter. VMware have a > tool too, but I expect that those that VMware generate won't work > with OpenStack yet, because they'll use VMDK for the disk images, > and I'd be surprised i
