Re: [Openstack] Newby question
Hi Alexandre, you can build a simple SingleNode in Flat Network mode with our StackOps Distro: http://www.stackops.org Once you have installed and configured the Single Node, then you can go to /etc/nova/nova-controller.conf and you can find the configuration details. If you feel brave enough to try a multi node deployment, then the Stackops Distro will create a specific nova-network configuration file in /etc/nova/nova-network.conf Don't forget that starting from Diablo some network configuration stuff must be performed directly with nova-manage command. Enjoy! Diego -- Diego Parrilla http://www.stackops.com/*CEO* *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 | skype:diegoparrilla* * http://www.stackops.com/ * * ADVERTENCIA LEGAL Le informamos, como destinatario de este mensaje, que el correo electrónico y las comunicaciones por medio de Internet no permiten asegurar ni garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción, por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias. Si no consintiese en la utilización del correo electrónico o de las comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene información confidencial y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico remitido a nuestra atención y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley. * PRIVILEGED AND CONFIDENTIAL We hereby inform you, as addressee of this message, that e-mail and Internet do not guarantee the confidentiality, nor the completeness or proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does not assume any liability for those circumstances. Should you not agree to the use of e-mail or to communications via Internet, you are kindly requested to notify us immediately. This message is intended exclusively for the person to whom it is addressed and contains privileged and confidential information protected from disclosure by law. If you are not the addressee indicated in this message, you should immediately delete it and any attachments and notify the sender by reply e-mail. In such case, you are hereby notified that any dissemination, distribution, copying or use of this message or any attachments, for any purpose, is strictly prohibited by law. On Fri, Dec 16, 2011 at 8:21 AM, Alexandre Parenteau aubonbeu...@gmail.comwrote: Hi, For my company, I'd like to set-up a nova-compute All-In-One node, to replace a eucalyptus cluster which is showing age. Unfortunately I'm not well versed in networking, and have trouble grasping the difference between the multiple network managers, but I think I would need a Flat mode in my case. I have a simple question: could someone please provide a functional euca.conf, that is using only one NIC, and the relative /etc/network/interfaces, for Ubuntu 11.10/Diablo? Help much appreciated! alex p.s.: as a side node, I tried everywhere the web for an explanation of how 'nova-manage network' relates to the flags passed inside nova.conf. ___ 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] Quantum essex-2 tag
Hi, https://launchpad.net/quantum/essex/essex-2 says essex-2 for quantum is release, but I don't see any Git tags. Could someone correct that? -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com ☎ +33 1 49 70 99 81 ___ 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] Essex-2 milestone available for Keystone, Glance, Nova and Horizon
Hi everyone, At the end of a long day, I'm pleased to announce the immediate availability of the second milestone of the Essex development cycle for Keystone, Glance, Nova and Horizon. Note that Nova now provides python-novaclient as an additional release deliverable. You can see the full list of new features and fixed bugs, as well as tarball downloads, at: https://launchpad.net/keystone/essex/essex-2 https://launchpad.net/glance/essex/essex-2 https://launchpad.net/nova/essex/essex-2 https://launchpad.net/horizon/essex/essex-2 You can test the Glance Nova milestones on Ubuntu by enabling the following PPAs: ppa:nova-core/milestone ppa:glance-core/milestone The next milestone, essex-3, is scheduled for release on January 26th. Happy holidays ! -- 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] Quantum essex-2 tag
Julien Danjou wrote: https://launchpad.net/quantum/essex/essex-2 says essex-2 for quantum is release, but I don't see any Git tags. Could someone correct that? Quantum is still in incubation / manual release mode, which might explain why it couldn't be tagged. I'll see with Dan so that the right version gets properly tagged, though. -- 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
[Openstack] [OpenStack + Keystone] Cannot get integration to work.
Hello,
I've been trying to set up openstack with the keystone service. I'm using a
virtual machine with ubuntu 11.10 and installed openstack through the main
repository.
After configuring keystone with the example data, i try to run the commands
from http://keystone.openstack.org/adminAPI_curl_examples.html. However,
instead of the expected result from the first command (curl
http://0.0.0.0:35357) i get the following ouput:
{IdentityFault: {message: Unhandled error, code: 500, details:
Template u'/usr/keystone/content/service/version.json.tpl' not found at
line 0 column 0}}
Also, when i attempt to run any of the euca-* commands i get the following
error:
Warning: failed to parse error message from AWS: unknown:1:0: syntax error
None: None
Any ideias?
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
Re: [Openstack] [OpenStack + Keystone] Cannot get integration to work.
Hi, I've keystone at least running on Ubuntu 11.10 with the openstack sru updates ppa [1]. Is the service running on your system? I'd check with $ sudo netstat -ntaupe | grep 5000 and $ sudo netstat -ntaupe | grep 35357 Both should be served by a keystone process. Regards, Torsten [1] https://launchpad.net/~zulcss/+archive/openstack-sru-updates ___ 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] [OpenStack + Keystone] Cannot get integration to work.
The first command (templated version response) failing is non-critical (the
functional calls should still work), but it looks like keystone isn't
finding it's static content where expected.
Where is keystone actually located in your install? (not /usr/keystone/?)
Ping me on IRC (dolphm) if that's more convenient.
-Dolph
On Fri, Dec 16, 2011 at 5:56 AM, Leander Bessa leande...@gmail.com wrote:
Hello,
I've been trying to set up openstack with the keystone service. I'm using
a virtual machine with ubuntu 11.10 and installed openstack through the
main repository.
After configuring keystone with the example data, i try to run the
commands from http://keystone.openstack.org/adminAPI_curl_examples.html.
However, instead of the expected result from the first command (curl
http://0.0.0.0:35357) i get the following ouput:
{IdentityFault: {message: Unhandled error, code: 500, details:
Template u'/usr/keystone/content/service/version.json.tpl' not found at
line 0 column 0}}
Also, when i attempt to run any of the euca-* commands i get the following
error:
Warning: failed to parse error message from AWS: unknown:1:0: syntax
error
None: None
Any ideias?
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] [OpenStack + Keystone] Cannot get integration to work.
Both ports are running a python process, which i suppose is keystone. That
directory does not exist on my system. I installed all the packages from
the official repository. Maybe something is outdated or misconfigured
because i already dealt with an issue where some python modules where
missing from the keystone egg in the python dist-package folder.
On Fri, Dec 16, 2011 at 1:42 PM, Dolph Mathews dolph.math...@gmail.comwrote:
The first command (templated version response) failing is non-critical
(the functional calls should still work), but it looks like keystone isn't
finding it's static content where expected.
Where is keystone actually located in your install? (not /usr/keystone/?)
Ping me on IRC (dolphm) if that's more convenient.
-Dolph
On Fri, Dec 16, 2011 at 5:56 AM, Leander Bessa leande...@gmail.comwrote:
Hello,
I've been trying to set up openstack with the keystone service. I'm using
a virtual machine with ubuntu 11.10 and installed openstack through the
main repository.
After configuring keystone with the example data, i try to run the
commands from http://keystone.openstack.org/adminAPI_curl_examples.html.
However, instead of the expected result from the first command (curl
http://0.0.0.0:35357) i get the following ouput:
{IdentityFault: {message: Unhandled error, code: 500,
details: Template u'/usr/keystone/content/service/version.json.tpl' not
found at line 0 column 0}}
Also, when i attempt to run any of the euca-* commands i get the
following error:
Warning: failed to parse error message from AWS: unknown:1:0: syntax
error
None: None
Any ideias?
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] Metadata and File Injection
On Thu, 15 Dec 2011, Vishvananda Ishaya wrote: On Dec 15, 2011, at 10:37 AM, Scott Moser wrote: What does a Server Personality give me that cannot be accomplished accomplished by guest and lauching-entity agreeing on a key-value pair with keyname server-personality. I think you are stating the same thing here. Basically repurposing the existing personality code to be key, value instead of filename, data Then I violently agree. Sorry for additional spam. Jesse, Thank you for leading this. I think its very valuable. I've just now subscribed to http://wiki.openstack.org/guest-configuration, but is there some other way I can make sure I follow this? I'd like to have cloud-init and 12.04 images using the preferred mechanism. ___ 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] Keystone client
Hi, I've just a small question about Keystone client code. Correct me if I'm wrong, but it seems that currently there's Keystone client code inside python-novaclient as novaclient.keystone. OTOH, horizon seems to use python-keystoneclient which is not part of OpenStack. I don't see the point to have 2 clients libraries and use them both in the project. Is there a goal to unify these two, to drop one, or anything? -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com ☎ +33 1 49 70 99 81 ___ 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] Metadata and File Injection
One use case is providing metadata to an instance before that instance starts their network stack. A bit of an edge case, but I guess one instance of this use case is the network injection logic used for Flat networking. Would injected files cover the above case? Would it still work after the proposed changes? I guess it should work, assuming nova injects the files in the same way it does for injecting network configuration, rather than relying on the agent to write the files once the system has booted by getting data from the metadata service. Maybe this is what the configuration drive could be used for (assuming either the agent isn't responsible for correctly mounting the configuration drive, or it can mount the disk before it has access to any network)? Thanks, John -Original Message- From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Vishvananda Ishaya Sent: 15 December 2011 22:50 To: Scott Moser Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Metadata and File Injection On Dec 15, 2011, at 10:37 AM, Scott Moser wrote: On Thu, 15 Dec 2011, Jesse Andrews wrote: On Thu, Dec 15, 2011 at 8:43 AM, Scott Moser smo...@ubuntu.com wrote: I'm just curious, what are the motivations behind inventing something other than the EC2 Metadata service? It is generally functional, and quite a lot can (and has) built atop this simple service. I should clarify - the idea is that ec2 metadata service is a great starting point - but there are already a handful of additions that should be added. In the existing (ec2) metadata service the urls look like: http://169.254.169.254/(version)/(resource) My hope is that we can add features like: * injected files / personality (or you can think of them as multiple named userdata sections) See below, but I don't see a reason to call something injected files, as opposed to a key of: files/etc/passwd : contents here and letting the guest agents and consumers sort out naming conventions. * updatable metadata params (the key/value params in the openstack api) with CRUD (so you can remove/update from guest) Secondly, There are 2 features that I feel are missing from the metadata service. And I'd hope that these could be accounted for if there is going to be invention done. a.) user-data is a single entity. There are potentially multiple sources that want to provide input to a guest (the end user might want to install some packages at boot, and the cloud infrastructure might want to tell the guest of a local mirror). cloud-init supports multipart-mime in userdata, so that there can be separate pieces inside that single source, but even then, all parties involved have to agree that they do not completely own that resource. The multipart-mime stuff is a great hack but isn't very user friendly as you state. In the openstack api we have server personalities that are similar to userdata except you can have multiple of them and they are named. http://docs.openstack.org/api/openstack- compute/1.1/content/Server_Pe rsonality-d1e2543.html If the guest (client) is in charge of pulling the personality data instead of the host injecting it, would this fulfill the usecase? I find specific designed use like this to be unnecessary. EC2 basically says heres a place to store a blob of data, do with it what you want. From that, best practices, good ideas, bad ideas, and even standards will evolve. What does a Server Personality give me that cannot be accomplished accomplished by guest and lauching-entity agreeing on a key-value pair with keyname server-personality. I think you are stating the same thing here. Basically repurposing the existing personality code to be key, value instead of filename, data If the guest agent wants to interpret keys as filenames it can. we could repurpose metadata as well, but it multiple key/value with potentially large values seems ideal. Basically, I'm saying dont bother with special keys/locations in a spec if there is no reason to. b.) There is no way to disable it. cloud-init supports writing a null-route to the metadata service, which can make it inaccessible to any non-root entity on the system. However, it would be nicer if there was a way to disable it entirely. With that in place, passing credentials into the guest would be easier as once they're consumed they can be removed. The usecase of passing credentials is one reason we want to have the metadata passed via the openstack API mutable via the metadata service http://docs.openstack.org/api/openstack- compute/1.1/content/Server_Me tadata-d1e2529.html A hashed password could be provided to the guest via the metadata service in a
Re: [Openstack] Keystone client
Yes (and there's actually more than 2 floating around, in various states); we're moving towards providing a single client, independent of keystone, which can be consumed by other projects (including keystone itself). There's no milestone target for this effort yet, but: https://blueprints.launchpad.net/keystone/+spec/keystone-client -Dolph On Fri, Dec 16, 2011 at 8:05 AM, Julien Danjou julien.dan...@enovance.comwrote: Hi, I've just a small question about Keystone client code. Correct me if I'm wrong, but it seems that currently there's Keystone client code inside python-novaclient as novaclient.keystone. OTOH, horizon seems to use python-keystoneclient which is not part of OpenStack. I don't see the point to have 2 clients libraries and use them both in the project. Is there a goal to unify these two, to drop one, or anything? -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com ☎ +33 1 49 70 99 81 ___ 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] Keystone client
Dolph Mathews wrote: Yes (and there's actually more than 2 floating around, in various states); we're moving towards providing a single client, independent of keystone, which can be consumed by other projects (including keystone itself). There's no milestone target for this effort yet, but: https://blueprints.launchpad.net/keystone/+spec/keystone-client The idea would be to get all the client splits in order for Essex-3, so that we don't introduce new release deliverables at the last milestone. -- 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] Newby question
Diego, Just one word: fantastic! I could install, configure, launch my first VM while sipping a coffee! I can't wait to try the dial-nodes, do I need only a second switch? Thanks so much for stackops, and thanks all for your quick answers! alex 2011/12/16 Diego Parrilla Santamaría diego.parrilla.santama...@gmail.com Hi Alexandre, you can build a simple SingleNode in Flat Network mode with our StackOps Distro: http://www.stackops.org Once you have installed and configured the Single Node, then you can go to /etc/nova/nova-controller.conf and you can find the configuration details. If you feel brave enough to try a multi node deployment, then the Stackops Distro will create a specific nova-network configuration file in /etc/nova/nova-network.conf Don't forget that starting from Diablo some network configuration stuff must be performed directly with nova-manage command. Enjoy! Diego -- Diego Parrilla http://www.stackops.com/*CEO* *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 | skype:diegoparrilla* * http://www.stackops.com/ * * ADVERTENCIA LEGAL Le informamos, como destinatario de este mensaje, que el correo electrónico y las comunicaciones por medio de Internet no permiten asegurar ni garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción, por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias. Si no consintiese en la utilización del correo electrónico o de las comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene información confidencial y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico remitido a nuestra atención y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley. * PRIVILEGED AND CONFIDENTIAL We hereby inform you, as addressee of this message, that e-mail and Internet do not guarantee the confidentiality, nor the completeness or proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does not assume any liability for those circumstances. Should you not agree to the use of e-mail or to communications via Internet, you are kindly requested to notify us immediately. This message is intended exclusively for the person to whom it is addressed and contains privileged and confidential information protected from disclosure by law. If you are not the addressee indicated in this message, you should immediately delete it and any attachments and notify the sender by reply e-mail. In such case, you are hereby notified that any dissemination, distribution, copying or use of this message or any attachments, for any purpose, is strictly prohibited by law. On Fri, Dec 16, 2011 at 8:21 AM, Alexandre Parenteau aubonbeu...@gmail.com wrote: Hi, For my company, I'd like to set-up a nova-compute All-In-One node, to replace a eucalyptus cluster which is showing age. Unfortunately I'm not well versed in networking, and have trouble grasping the difference between the multiple network managers, but I think I would need a Flat mode in my case. I have a simple question: could someone please provide a functional euca.conf, that is using only one NIC, and the relative /etc/network/interfaces, for Ubuntu 11.10/Diablo? Help much appreciated! alex p.s.: as a side node, I tried everywhere the web for an explanation of how 'nova-manage network' relates to the flags passed inside nova.conf. ___ 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] Metadata and File Injection
On Fri, 16 Dec 2011, John Garbutt wrote: One use case is providing metadata to an instance before that instance starts their network stack. A bit of an edge case, but I guess one instance of this use case is the network injection logic used for Flat networking. Would injected files cover the above case? Would it still work after the proposed changes? I guess it should work, assuming nova injects the files in the same way it does for injecting network configuration, rather than relying on the agent to write the files once the system has booted by getting data from the metadata service. Maybe this is what the configuration drive could be used for (assuming either the agent isn't responsible for correctly mounting the configuration drive, or it can mount the disk before it has access to any network)? I think it is reasonable to inject static networking configuration via configuration drive. It could even be re-named network-configuration-drive if there is seen to be no other use for it. I'd add code to cloud-init for ubuntu configuration based on that. I've been meaning to get around to it anyway, I just haven't done it. I think it would be quite clean to do logic on boot like: * if a scan of block devices shows one labeled netconfig * mount that (iso9660 or vfat) filesystem, read /config file in its root filesystem. * modify /etc/network/interfaces accordingly * continue on with boot. The only issue above that there is nothing that guarantees that the config drive volume is going to be present at the instant in boot when I start looking (it may just not have shown up yet on the scsi bus or whatever). If its not there, and cloud-init goes on with life it may expose a race. I'd have to think about that more. ___ 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] Keystone client
Well, I'm certainly not planning on writing a client from scratch, so I'd be happy to hear some discussion on which client we should deem official and replace the others with. My only concern is that we provide an intuitive python API supporting the various auth flows. -Dolph On Fri, Dec 16, 2011 at 8:43 AM, Julien Danjou julien.dan...@enovance.comwrote: On Fri, Dec 16 2011, Dolph Mathews wrote: Yes (and there's actually more than 2 floating around, in various states); we're moving towards providing a single client, independent of keystone, which can be consumed by other projects (including keystone itself). There's no milestone target for this effort yet, but: https://blueprints.launchpad.net/keystone/+spec/keystone-client Thanks Dolph, I missed that blueprint. Now I think it would be cool if a decision could be done about the library Gabriel wrote. Since it's used by horizon, it seems obvious that it should be integrated as an official OpenStack component, but, eh… anyone's call? :) -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com ☎ +33 1 49 70 99 81 ___ 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] Newby question
Thank you for your nice words! Dual configuration is the most common configuration we use: you only need to be cautious about how to configure the different networks. Just some hints: 1) Leave the management network as simple as possible. 2) The service network (the one that connects all the virtual machines and nova-network) needs a dedicated NIC (or virtual NIC if you are deploying in a virtual lab with VMware for example) and must be connected to the same group of ports, all with a single VLAN statically assigned to these ports. It's important that nova-network and the virtual machines can see each other. 3) The public network (the one you will use for the floating IPs) cannot be shared with the service network at all. It can be shared with the management network, but normally you can't do real stuff. A good solution is to have a dedicated NIC connected to internet and configured with a public CIDR, or if you are in a corporate environment connect it to the corporate network. Probably you will have to statically assign the port of the switch to the VLAN of the corporate network. To be honest, most of the complains about the distro has to do with networking, and we can't do a lot about it. We normally try to explain that the single node deployment is like installing a MySQL server for development in 10 minutes -everybody can do it-, but configuring a MySQL server for production highly available is hard. Dual and Multi node deployments can be like deploying the production-ready MySQL: it's not a 10' tasks :-( Regards Diego -- Diego Parrilla http://www.stackops.com/*CEO* *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 | skype:diegoparrilla* * http://www.stackops.com/ * * ADVERTENCIA LEGAL Le informamos, como destinatario de este mensaje, que el correo electrónico y las comunicaciones por medio de Internet no permiten asegurar ni garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción, por lo que STACKOPS TECHNOLOGIES S.L. no asume responsabilidad alguna por tales circunstancias. Si no consintiese en la utilización del correo electrónico o de las comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene información confidencial y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico remitido a nuestra atención y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley. * PRIVILEGED AND CONFIDENTIAL We hereby inform you, as addressee of this message, that e-mail and Internet do not guarantee the confidentiality, nor the completeness or proper reception of the messages sent and, thus, STACKOPS TECHNOLOGIES S.L. does not assume any liability for those circumstances. Should you not agree to the use of e-mail or to communications via Internet, you are kindly requested to notify us immediately. This message is intended exclusively for the person to whom it is addressed and contains privileged and confidential information protected from disclosure by law. If you are not the addressee indicated in this message, you should immediately delete it and any attachments and notify the sender by reply e-mail. In such case, you are hereby notified that any dissemination, distribution, copying or use of this message or any attachments, for any purpose, is strictly prohibited by law. 2011/12/16 Alexandre Parenteau aubonbeu...@gmail.com Diego, Just one word: fantastic! I could install, configure, launch my first VM while sipping a coffee! I can't wait to try the dial-nodes, do I need only a second switch? Thanks so much for stackops, and thanks all for your quick answers! alex 2011/12/16 Diego Parrilla Santamaría diego.parrilla.santama...@gmail.com Hi Alexandre, you can build a simple SingleNode in Flat Network mode with our StackOps Distro: http://www.stackops.org Once you have installed and configured the Single Node, then you can go to /etc/nova/nova-controller.conf and you can find the configuration details. If you feel brave enough to try a multi node deployment, then the Stackops Distro will create a specific nova-network configuration file in /etc/nova/nova-network.conf Don't forget that starting from Diablo some network configuration stuff must be performed directly with nova-manage command. Enjoy! Diego -- Diego Parrilla http://www.stackops.com/*CEO* *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 |
Re: [Openstack] novaclient + keystone (HTTP 404, The resource could not be found.)
On Thu, Dec 15, 2011 at 2:29 PM, Dong-In David Kang dk...@isi.edu
wrote:
I'm trying to make novaclient work with keystone.
It looks like authentication is working, but actual interaction
between novaclient and nova does not work.
Here is what I get (with added debugging messages I added in
novaclient)
I'll appreciate any help.
David.
$ nova list
initial auth_url: http://10.0.10.1:5000/v2.0/
POST with body = {'auth': {'tenantName': 'demo',
'passwordCredentials': {'username': 'demo', 'password':
'guest'}}}
request: args = ('http://10.0.10.1:5000/v2.0/tokens', 'POST')
request: kwargs = {'body': '{auth: {tenantName: demo,
passwordCredentials: {username: demo, password:
guest}}}', 'headers': {'Content-Type': 'application/json',
'User-Agent': 'python-novaclient'}}
request: resp = {'date': 'Thu, 15 Dec 2011 19:20:10 GMT',
'status':
'200', 'content-length': '993', 'content-type':
'application/json;
charset=UTF-8'}
request: body = {access: {token: {expires:
2011-12-16T11:30:09.098995, id:
6ad85291-8d26-4bd5-a667-525322fd66a8, tenant: {id: 2,
name: demo}}, serviceCatalog: [{endpoints: [{region:
RegionOne, internalURL: http://10.0.10.1:8774/v1.1/;,
publicURL: http://10.0.10.1:8774/v1.1/}], type: compute,
name: nova}, {endpoints: [{region: RegionOne,
internalURL: http://10.0.11.1:9292/v1.1/;, publicURL:
http://10.0.11.1:9292/v1.1/}, {region: RegionOne,
internalURL: http://10.0.1.3:9292/v1.1/;, publicURL:
http://10.0.1.3:9292/v1.1/}, {region: RegionOne,
internalURL: http://10.0.11.1:9292/v1/;, publicURL:
http://10.0.11.1:9292/v1/}], type: image, name:
glance},
{endpoints: [{region: RegionOne, internalURL:
http://10.0.10.1:5000/v2.0;, publicURL:
http://10.0.10.1:5000/v2.0}], type: identity, name:
keystone}], user: {id: 2, roles: [{tenantId: 2,
id: 4, name: Member}], name: demo}}}
resp of POST = {'date': 'Thu, 15 Dec 2011 19:20:10 GMT',
'status':
'200', 'content-length': '993', 'content-type':
'application/json;
charset=UTF-8'}
service_catalog = module 'novaclient.service_catalog' from
'/home/dkang/venv/lib/python2.6/site-packages/novaclient/service_catalog.pyc'
auth_token = 6ad85291-8d26-4bd5-a667-525322fd66a8
management_url = http://10.0.10.1:8774/v1.1/
v2_auth is done
request: args =
(u'http://10.0.10.1:8774/v1.1//servers/detail?fresh=1323976810.06',
'GET')
Unless I'm mistaken, shouldn't the above URI include the TenantId
between /v1.1/ and /servers?
-jay
Thank you for the catch.
I've modified the keystone db, and rerun $nova list.
Now I have HTTP 500 error.
$ nova list
REQ: curl -i http://10.0.10.1:5000/v2.0/tokens -X POST -H
Content-Type: application/json -H User-Agent: python-novaclient
REQ BODY: {auth: {tenantName: demo, passwordCredentials:
{username: demo, password: guest}}}
RESP:{'date': 'Thu, 15 Dec 2011 22:54:31 GMT', 'status': '200',
'content-length': '1229', 'content-type': 'application/json;
charset=UTF-8'} {access: {token: {expires:
2011-12-16T11:30:09.098995, id:
6ad85291-8d26-4bd5-a667-525322fd6
6a8, tenant: {id: 2, name: demo}}, serviceCatalog:
[{endpoints: [{region: RegionOne, internalURL:
http://10.0.10.1:8774/v1.1/1;, publicURL:
http://10.0.10.1:8774/v1.1/1}, {region: RegionOne,
internalURL: http://
10.0.10.1:8774/v1.1/2, publicURL: http://10.0.10.1:8774/v1.1/2},
{region: RegionOne, internalURL:
http://10.0.10.1:8774/v1.1/3;, publicURL:
http://10.0.10.1:8774/v1.1/3}], type: compute, name:
nova}, {endpoints: [{reg
ion: RegionOne, internalURL: http://10.0.11.1:9292/v1.1/;,
publicURL: http://10.0.11.1:9292/v1.1/}, {region: RegionOne,
internalURL: http://10.0.1.3:9292/v1.1/;, publicURL:
http://10.0.1.3:9292/v1.1/}, {region: RegionOne
, internalURL: http://10.0.11.1:9292/v1/;, publicURL:
http://10.0.11.1:9292/v1/}], type: image, name: glance},
{endpoints: [{region: RegionOne, internalURL:
http://10.0.10.1:5000/v2.0;, publicURL: http://10.0.10.1:50
00/v2.0}], type: identity, name: keystone}], user: {id:
2, roles: [{tenantId: 2, id: 4, name: Member}],
name: demo}}}
REQ: curl -i
http://10.0.10.1:8774/v1.1/1/servers/detail?fresh=1323989671.41 -X
GET -H X-Auth-Project-Id: demo -H User-Agent: python-novaclient
-H X-Auth-Token: 6ad85291-8d26-4bd5-a667-525322fd66a8
REQ: curl -i
http://10.0.10.1:8774/v1.1/1/servers/detail?fresh=1323989671.41 -X
GET -H X-Auth-Project-Id: demo -H User-Agent: python-novaclient
-H X-Auth-Token: 6ad85291-8d26-4bd5-a667-525322fd66a8
RESP:{'date': 'Thu, 15 Dec 2011 22:54:31 GMT', 'status': '500',
'content-length': '128', 'content-type': 'application/json;
charset=UTF-8'} {computeFault: {message: The server has either
erred or is incapable of performing the requested op
eration., code: 500}}
RESP:{'date': 'Thu, 15 Dec 2011 22:54:31 GMT', 'status': '500',
'content-length': '128', 'content-type': 'application/json;
charset=UTF-8'}
Re: [Openstack] Glance 2012.1-dev! ERROR: NO 'app_factory' attribute
cc'ing mailing list as this is generally useful and something I myself
ran into last night when I grabbed the latest devstack and re-ran
stack.sh...
I found the solution was to remove all the old .pyc files, like so:
cd $GLANCE_SRC_DIR
find . -type f -name *.pyc -exec sudo rm -f {} \;
And then restart Glance servers...
Please let me know if that works for you as well.
Thanks,
-jay
On Thu, Dec 15, 2011 at 10:39 PM, jeffrey coho
jeffreycohob...@gmail.com wrote:
Hi,Jay
Thanks.I copied those to my config files,and restarted
with glance-control .Anyway,it is still not working.
port 9292 is still not listening.So what is the stable release of Glance
now?
and how can i get one?(i am using ubuntu11.10)
Yours,
jeff
2011/12/15 Jay Pipes jaypi...@gmail.com
Yeah, I was worried we would run into these kinds of problems with a
recent commit...
Basically, do what Hugo suggested. We recently overhauled the
configuration and paste deploy factories in Glance to align with the
common cfg work being done in Nova and Glance. This means that the
glance-api.conf and glance-registry.conf paste deploy sections need to
be updated.
You can see the changes needed by looking at this diff:
https://review.openstack.org/#patch,sidebyside,2139,1,etc/glance-api.conf
https://review.openstack.org/#patch,sidebyside,2139,1,etc/glance-cache.conf
https://review.openstack.org/#patch,sidebyside,2139,1,etc/glance-registry.conf
Ping us back if you have issues figuring out the needed changes.
Thanks!
-jay
On Thu, Dec 15, 2011 at 8:28 AM, jeffrey coho jeffreycohob...@gmail.com
wrote:
Hi,all,
Glance version i am running is 2012.1-dev. But glance-api can't be
started(maybe this version is just unstable for now?).Here is some
details:
#sudo glance-api glance-api.conf --debug -v
[1]27173
Error trying to load config /etc/glance/glance-api.conf:module
'glance.api.v1' from
'/usr/local/lib/python2.7/dist-packages/glance-2012.1-py2.7.egg/glance/api/v1/__init__.pyc'
has no 'app_factory' attribute
Any ideas?Thanks very much.
Yours,
Jeff
___
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] Quantum essex-2 tag
On Fri, Dec 16 2011, Dan Wendlandt wrote: Apologies. Because Quantum is still in incubation, the tag is not created automatically and I forgot to do it manually after sending out the release email last night. Thanks a lot Dan. -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com ☎ +33 1 49 70 99 81 ___ 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] proposal to move non-standard ec2 admin api in essex
IMPORTANT: this is NOT about removing EC2 api or admin apis - it is about moving admin extensions to openstack api extensions. When we first created nova, we created a set of admin apis that helped make the project configurable without nova-manage. We shoved them into the ec2 api layer since the boto libary was so easy to extend. The primary usecase of these admin apis was the dashboard project prior to incubation and the nova-adminclient. During Diablo the dashboard was rewritten to use openstack apis. Given that those who require the EC2 api, the reasoning is for interoperability, I propose we remove the (mostly undocumented) admin apis. Blueprint: https://blueprints.launchpad.net/nova/+spec/remove-ec2-extensions For those who don't know what I'm talking about: The service side: * https://github.com/openstack/nova/blob/master/nova/api/ec2/admin.py The client: * https://launchpad.net/nova-adminclient The functionality that has been ported to openstack extensions: * user/project/roles: now the domain of keystone * host list - already ported: https://github.com/openstack/nova/blob/master/nova/api/openstack/v2/contrib/hosts.py Things that need to be port from to openstack extensions: * cloudpipe api (launch/terminate/list vpn instances) xtoddx is writing a blueprint to port to openstack api * provider firewall rules - http://wiki.openstack.org/spec-provider-firewall xtoddx is writing a blueprint to port to openstack api * x509 cert generation - exposed in cactus dashboard, used to sign images in ec2 bundling processes part of a blueprint for exposing https://blueprints.launchpad.net/horizon/+spec/ec2-credentials-download Thoughts from those who use nova-adminclient or the /services/Admin ec2 api endpoint? Thanks, Jesse ___ 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] using objects returned from DB layer
Johannes Erdfelt johan...@erdfelt.com said: I'm not saying you need to do it, but this is something that doesn't have an obvious design and implementation. It would be easier to understand and discuss with some real meat behind it. From what Monsyne Dragon and Jonathan LaCour have said on this topic, I feel confident that the nova-db subteam has a good handle on the issues we are currently facing with the db layer. And I'm sure they will have some good proposals for how we can move forward. I am happy for nova-core to enforce consistency until we decide to adopt one of their proposals. ___ 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] using objects returned from DB layer
On Dec 16, 2011, at 11:30 AM, Mark Washenberger wrote: Johannes Erdfelt johan...@erdfelt.com said: I'm not saying you need to do it, but this is something that doesn't have an obvious design and implementation. It would be easier to understand and discuss with some real meat behind it. From what Monsyne Dragon and Jonathan LaCour have said on this topic, I feel confident that the nova-db subteam has a good handle on the issues we are currently facing with the db layer. And I'm sure they will have some good proposals for how we can move forward. I am happy for nova-core to enforce consistency until we decide to adopt one of their proposals. I'd be happy to get more involved in the discussion, to provide some code, or to connect with the right people in the SQLAlchemy community for a review of the approach we're taking. How can I help? -- Jonathan LaCour VP, Software Development DreamHost (W) 323.372.5984 (C) 404.784.1081 ___ 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] Glance 2012.1-dev! ERROR: NO 'app_factory' attribute
Something I've found useful to help with the cleanup situation is the
following.
http://pastebin.com/Vm03EafN
It at least does some basic devstack cleanup then attempts to install a new
version from git (nothing special really) - ubuntu only...
Maybe others will find it useful...
On 12/16/11 8:10 AM, Jay Pipes jaypi...@gmail.com wrote:
cc'ing mailing list as this is generally useful and something I myself
ran into last night when I grabbed the latest devstack and re-ran
stack.sh...
I found the solution was to remove all the old .pyc files, like so:
cd $GLANCE_SRC_DIR
find . -type f -name *.pyc -exec sudo rm -f {} \;
And then restart Glance servers...
Please let me know if that works for you as well.
Thanks,
-jay
On Thu, Dec 15, 2011 at 10:39 PM, jeffrey coho
jeffreycohob...@gmail.com wrote:
Hi,Jay
Thanks.I copied those to my config files,and restarted
with glance-control .Anyway,it is still not working.
port 9292 is still not listening.So what is the stable release of Glance
now?
and how can i get one?(i am using ubuntu11.10)
Yours,
jeff
2011/12/15 Jay Pipes jaypi...@gmail.com
Yeah, I was worried we would run into these kinds of problems with a
recent commit...
Basically, do what Hugo suggested. We recently overhauled the
configuration and paste deploy factories in Glance to align with the
common cfg work being done in Nova and Glance. This means that the
glance-api.conf and glance-registry.conf paste deploy sections need to
be updated.
You can see the changes needed by looking at this diff:
https://review.openstack.org/#patch,sidebyside,2139,1,etc/glance-api.conf
https://review.openstack.org/#patch,sidebyside,2139,1,etc/glance-cache.conf
https://review.openstack.org/#patch,sidebyside,2139,1,etc/glance-registry.conf
Ping us back if you have issues figuring out the needed changes.
Thanks!
-jay
On Thu, Dec 15, 2011 at 8:28 AM, jeffrey coho jeffreycohob...@gmail.com
wrote:
Hi,all,
Glance version i am running is 2012.1-dev. But glance-api can't be
started(maybe this version is just unstable for now?).Here is some
details:
#sudo glance-api glance-api.conf --debug -v
[1]27173
Error trying to load config /etc/glance/glance-api.conf:module
'glance.api.v1' from
'/usr/local/lib/python2.7/dist-packages/glance-2012.1-py2.7.egg/glance/api/v1/__init__.pyc'
has no 'app_factory' attribute
Any ideas?Thanks very much.
Yours,
Jeff
___
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] Keystone client
Hrm. For some reason I thought we'd already decided to use the 4P/python-keystoneclient (it's been a todo list item for me to move it in to the openstack repos) I take it that we have _not_ decided that we should use that library as the keystone client library? On 12/16/2011 10:16 AM, Dolph Mathews wrote: Well, I'm certainly not planning on writing a client from scratch, so I'd be happy to hear some discussion on which client we should deem official and replace the others with. My only concern is that we provide an intuitive python API supporting the various auth flows. -Dolph On Fri, Dec 16, 2011 at 8:43 AM, Julien Danjou julien.dan...@enovance.com mailto:julien.dan...@enovance.com wrote: On Fri, Dec 16 2011, Dolph Mathews wrote: Yes (and there's actually more than 2 floating around, in various states); we're moving towards providing a single client, independent of keystone, which can be consumed by other projects (including keystone itself). There's no milestone target for this effort yet, but: https://blueprints.launchpad.net/keystone/+spec/keystone-client Thanks Dolph, I missed that blueprint. Now I think it would be cool if a decision could be done about the library Gabriel wrote. Since it's used by horizon, it seems obvious that it should be integrated as an official OpenStack component, but, eh… anyone's call? :) -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com mailto:julien.dan...@enovance.com ☎ +33 1 49 70 99 81 tel:%2B33%201%2049%2070%2099%2081 ___ 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] Keystone client
python-keystoneclient is based on python-novaclient, and is already in use by horizon as mentioned. What are the reasons for not using python-keystoneclient? Jesse On Fri, Dec 16, 2011 at 1:47 PM, Monty Taylor mord...@inaugust.com wrote: Hrm. For some reason I thought we'd already decided to use the 4P/python-keystoneclient (it's been a todo list item for me to move it in to the openstack repos) I take it that we have _not_ decided that we should use that library as the keystone client library? On 12/16/2011 10:16 AM, Dolph Mathews wrote: Well, I'm certainly not planning on writing a client from scratch, so I'd be happy to hear some discussion on which client we should deem official and replace the others with. My only concern is that we provide an intuitive python API supporting the various auth flows. -Dolph On Fri, Dec 16, 2011 at 8:43 AM, Julien Danjou julien.dan...@enovance.com mailto:julien.dan...@enovance.com wrote: On Fri, Dec 16 2011, Dolph Mathews wrote: Yes (and there's actually more than 2 floating around, in various states); we're moving towards providing a single client, independent of keystone, which can be consumed by other projects (including keystone itself). There's no milestone target for this effort yet, but: https://blueprints.launchpad.net/keystone/+spec/keystone-client Thanks Dolph, I missed that blueprint. Now I think it would be cool if a decision could be done about the library Gabriel wrote. Since it's used by horizon, it seems obvious that it should be integrated as an official OpenStack component, but, eh… anyone's call? :) -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com mailto:julien.dan...@enovance.com ☎ +33 1 49 70 99 81 tel:%2B33%201%2049%2070%2099%2081 ___ 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] Extension Documentation
Joe, I fully support your effort in creating a central reference page like the one on your mock...and in fact I'm working with some of the doc tools folks to help make that happen. I think that the extension site contains different kind of docs for different audience -- made up of implementors and language binding builders. The need there is to evaluate exactly how an individual extension modifies the core -- you can certainly build a centralized reference page from the info contained there in. -jOrGe W. -Original Message- From: Joseph Heck he...@mac.com Date: Fri, 9 Dec 2011 11:47:27 -0800 To: Brian Waldon brian.wal...@rackspace.com Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net) openstack@lists.launchpad.net Subject: Re: [Openstack] Extension Documentation I totally agree with Anne that the documentation in this split up format is very hard to both find and parse. It's not inaccurate, so much as it leaves a gaping hole in understanding what is and isn't available when you have 9+ documents to read and they're not really interlinked. The effort I kicked off, but haven't had a lot of time to put into lately, to create a single unified portal/page for the API was an idea to address this weakness with the current structure. I've created a github pages site to stub out how this might work - https://github.com/heckj/api-site-mock, with the generated site at http://heckj.github.com/api-site-mock/. It's very much a work in progress, which I hope to resume work on in a few weeks when I should be able to free up some additional time. I have documented my intention for the site's goals (https://github.com/heckj/api-site-mock/blob/master/GOALS.md) and design (https://github.com/heckj/api-site-mock/blob/master/DESIGN.md) - tl;dr, making a unified API directory for immediate web-based consumption (i.e. browser) along the lines of: * https://www.parse.com/docs/rest * https://dev.twitter.com/docs/api If anyone else would be interested in collaborating on this site live to move it forward, I would be happy to add your accounts to directly push into the repository. And of course I'm happy to take pull requests. -joe On Dec 9, 2011, at 6:29 AM, Brian Waldon wrote: Hey Anne, Great feedback! As for number 8, I think the nova-api team might be the best group to be tasked with reviewing code and documentation for any extensions proposed to Nova's codebase. And we can absolutely discuss this at the meeting today! Brian On Dec 9, 2011, at 9:17 AM, Anne Gentle wrote: Hi everyone - Overall I support this effort and have discussed it at length with the Rackers working on it. I'd really like to get feedback from everyone who thinks they'll consume this type of information. I don't find it easy to use from an API consumer's perspective, but it is an absolute must for the projects to have a way to describe what parts of their API is an extension. Here are my suggestions on this first iteration, which I've talked to Jorge about but also want to share with the list to get input. 1. The header - at first it may confuse people since it's an OpenStack header on a Rackspace domain name. I understand this convention was chosen since you intend to give it over to OpenStack. 2. In the header, I don't believe Extensions Documentation is the correct label, probably just highlight Documentation. 3. I don't have a good sense of how readers will get to API documentation from this page. With the API site also being worked on, we'll need to find a good secondary nav for these types of sites. 4. All of the links need to add an additional /content/ to the link to avoid redirects. 5. All of these mini-docs need to use a processing instruction or pom directive to avoid the tiny chunking and only chunk at the chapter level. 6. I made some minor changes to the DocBook template so that people can find the WADL normalizer tool. 7. For the API site we're constructing, we're not yet sure how to handle extensions for the API reference. Right now we need to fill in a lot of reference information. Suggestions for integration are welcomed. 8. We need a discussion about who will review these extension submissions and ensure they get built. Based on the struggle to get these docs written, I also want to know if you all find the templates useful and think you'll author these. Any suggestions for the authoring side? Brian, can we discuss at the nova-api meeting tomorrow at 3:00 CST in #openstack-manuals as well? I'll also discuss at the Doc Team meeting Monday 12/12 at 2:00 CST (20:00 UTC). Thanks for all the work here. Let's iterate on this site. Thanks, Anne On Thu, Dec 8, 2011 at 10:58 AM, Jorge Williams jorge.willi...@rackspace.com wrote: Hi All, I've started putting together a site to hold extension documentation. You can see it here: http://docs.rackspace.com/openstack-extensions/ The idea is to have a repository for all extensions,
Re: [Openstack] Keystone client
Who suggested not using python-keystoneclient? On 12/16/11 4:12 PM, Jesse Andrews anotherje...@gmail.com wrote: python-keystoneclient is based on python-novaclient, and is already in use by horizon as mentioned. What are the reasons for not using python-keystoneclient? Jesse On Fri, Dec 16, 2011 at 1:47 PM, Monty Taylor mord...@inaugust.com wrote: Hrm. For some reason I thought we'd already decided to use the 4P/python-keystoneclient (it's been a todo list item for me to move it in to the openstack repos) I take it that we have _not_ decided that we should use that library as the keystone client library? On 12/16/2011 10:16 AM, Dolph Mathews wrote: Well, I'm certainly not planning on writing a client from scratch, so I'd be happy to hear some discussion on which client we should deem official and replace the others with. My only concern is that we provide an intuitive python API supporting the various auth flows. -Dolph On Fri, Dec 16, 2011 at 8:43 AM, Julien Danjou julien.dan...@enovance.com mailto:julien.dan...@enovance.com wrote: On Fri, Dec 16 2011, Dolph Mathews wrote: Yes (and there's actually more than 2 floating around, in various states); we're moving towards providing a single client, independent of keystone, which can be consumed by other projects (including keystone itself). There's no milestone target for this effort yet, but: https://blueprints.launchpad.net/keystone/+spec/keystone-client Thanks Dolph, I missed that blueprint. Now I think it would be cool if a decision could be done about the library Gabriel wrote. Since it's used by horizon, it seems obvious that it should be integrated as an official OpenStack component, but, eh… anyone's call? :) -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com mailto:julien.dan...@enovance.com ☎ +33 1 49 70 99 81 tel:%2B33%201%2049%2070%2099%2081 ___ 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] IRC bots
Folks, this is a very important topic. I tried to get ahold of the person/people that manages the bots but I didn't succeed so far. Today I noticed that Network team meeting logs are broken (only txt summary and the full html logs give 404). See http://wiki.openstack.org/Network/MeetingLogs We need to be able to share the burden of managing, and fix things in case they break. Do you run an IRC bot on any of the #openstack channels or do you know somebody that does? thanks stef On Sun, 2011-12-11 at 10:08 -0800, Monty Taylor wrote: Hey guys! We have mutliple IRC bots in our channels, each of which do things that are pretty important. I have no idea who runs most of them or where they run. I would love to get these managed, for a few reasons: - They're killer cool, and people will be sad if they stop working - We have a few feature requests out for them - Their operation should probably be documented somewhere - We've got the ability now to handle management of these things through puppet, which means that changes to it can go through gerrit, which means everybody can play. SO - if you are one of the people running one of the IRC bots (or know any of the people running any of these systems) could you ping me so we can talk about if/how if makes any sense to add management of them to systems that we know about and run. Thanks! Monty ___ 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] novaclient + keystone (HTTP 404, The resource could not be found.)
On Fri, Dec 16, 2011 at 10:46 AM, Dong-In David Kang dk...@isi.edu wrote: The server has either erred or is incapable of performing the requested operation. (HTTP 500) It was due to the version of webob. The installed version was 1.2b. After reverting it to 1.1.1, it works fine. Hmmm, could it be related to this? https://bugs.launchpad.net/swift/+bug/888371 If so, looks like this is a bug that applies to Nova as well? -jay I think they are similar. Here is the log of nova-api. David. 2011-12-16 10:01:51,998 INFO nova.api.openstack.wsgi [b4427885-3601-47c3-9870-4260a3753f7d 2 1] GET http://10.0.10.1:8774/v1.1/1/servers/detail?fresh=1324047711.96 2011-12-16 10:01:51,998 DEBUG nova.api.openstack.wsgi [b4427885-3601-47c3-9870-4260a3753f7d 2 1] Unrecognized Content-Type provided in request from (pid=11529) deserialize_body /usr/local/nova/nova/api/openstack/wsgi.py:257 2011-12-16 10:01:51,998 ERROR nova.api.openstack.v2 [b4427885-3601-47c3-9870-4260a3753f7d 2 1] Caught error: The attribute None is deprecated: disabled starting WebOb 1.2, use GET instead (nova.api.openstack.v2): TRACE: Traceback (most recent call last): (nova.api.openstack.v2): TRACE: File /usr/local/nova/nova/api/openstack/v2/__init__.py, line 61, in __call__ (nova.api.openstack.v2): TRACE: return req.get_response(self.application) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/webob/request.py, line 1149, in get_response (nova.api.openstack.v2): TRACE: application, catch_exc_info=False) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/webob/request.py, line 1118, in call_application (nova.api.openstack.v2): TRACE: app_iter = application(self.environ, start_response) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/keystone/middleware/auth_token.py, line 310, in __call__ (nova.api.openstack.v2): TRACE: return self._forward_request(env, start_response, proxy_headers) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/keystone/middleware/auth_token.py, line 488, in _forward_request (nova.api.openstack.v2): TRACE: return self.app(env, start_response) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/webob/dec.py, line 146, in __call__ (nova.api.openstack.v2): TRACE: return resp(environ, start_response) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/webob/dec.py, line 146, in __call__ (nova.api.openstack.v2): TRACE: return resp(environ, start_response) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/webob/dec.py, line 132, in __call__ (nova.api.openstack.v2): TRACE: resp = self.call_func(req, *args, **self.kwargs) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/webob/dec.py, line 197, in call_func (nova.api.openstack.v2): TRACE: return self.func(req, *args, **kwargs) (nova.api.openstack.v2): TRACE: File /usr/local/nova/nova/api/openstack/wsgi.py, line 499, in __call__ (nova.api.openstack.v2): TRACE: response = req.get_response(self.application) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/webob/request.py, line 1149, in get_response (nova.api.openstack.v2): TRACE: application, catch_exc_info=False) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/webob/request.py, line 1118, in call_application (nova.api.openstack.v2): TRACE: app_iter = application(self.environ, start_response) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/webob/dec.py, line 146, in __call__ (nova.api.openstack.v2): TRACE: return resp(environ, start_response) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/routes/middleware.py, line 131, in __call__ (nova.api.openstack.v2): TRACE: response = self.app(environ, start_response) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/webob/dec.py, line 146, in __call__ (nova.api.openstack.v2): TRACE: return resp(environ, start_response) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/webob/dec.py, line 132, in __call__ (nova.api.openstack.v2): TRACE: resp = self.call_func(req, *args, **self.kwargs) (nova.api.openstack.v2): TRACE: File /usr/lib/python2.6/site-packages/webob/dec.py, line 197, in call_func (nova.api.openstack.v2): TRACE: return self.func(req, *args, **kwargs) (nova.api.openstack.v2): TRACE: File /usr/local/nova/nova/api/openstack/wsgi.py, line 567, in __call__ (nova.api.openstack.v2): TRACE: action_result = self.dispatch(request, action, args) (nova.api.openstack.v2): TRACE: File /usr/local/nova/nova/api/openstack/wsgi.py, line 599, in dispatch (nova.api.openstack.v2): TRACE: return controller_method(req=request, **action_args) (nova.api.openstack.v2): TRACE: File /usr/local/nova/nova/api/openstack/v2/extensions.py, line 166, in process
[Openstack] OpenStack Community Newsletter –December 16, 2011
OpenStack Community Newsletter –December 16, 2011 HIGHLIGHTS * Proposal to move non-standard ec2 “admin” api in essex https://lists.launchpad.net/openstack/msg06218.html * Proposed branches for Essex-2 milestones have been cut https://launchpad.net/openstack/+milestone/essex-2 * Number of open bugs on Nova keeps increasing http://webnumbr.com/open-nova-bugs * Documentation Team started to work on localization effort and new Launchpad project for openstack.org * Full meeting summary http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-12-20.03.html EVENTS * Holiday season started :) * OpenStack Meetup Jan 5th 2012 — San Francisco http://www.meetup.com/openstack/ OTHER NEWS * There is still time to submit talks to the FOSDEM “Open Source Virtualization and Cloud” devroom https://lists.fosdem.org/pipermail/fosdem/2011-November/001354.html * OpenStack Wiki Recent Changes – http://wiki.openstack.org/RecentChanges * Packaging for RHEL http://wiki.openstack.org/Packaging/RHEL and Fedora http://wiki.openstack.org/Packaging/Fedora * Quantum development http://wiki.openstack.org/QuantumDevelopment * Quantum packages http://wiki.openstack.org/QuantumPackages * New corporate contributor: Samsung SDS http://wiki.openstack.org/CoporateCLAList * Team meeting summary http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-06-21.01.html * Network meeting summary http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-12-13-22.00.txt COMMUNITY STATISTICS * Activity on the OpenStack repositories, lines of code added and removed by the developers from Mon Dec 05 00:00:00 UTC 2011 to Sun Dec 11 00:00:00 UTC 2011 2011-49-glance 2011-49-horizon 2011-49-keystone 2011-49-manuals 2011-49-quantum 2011-49-swift 2011-49-nova ___ 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] IRC bots
Hi stef, No bot there... just a human who introduced a copy/paste issue into the two most recent HTML logs (I guess my algorithm of only checking the text logs is faulty). Now fixed. If someone has a bot that we can use to post the meeting logs, I'm all for setting it up. Dan On Fri, Dec 16, 2011 at 3:36 PM, Stefano Maffulli stef...@openstack.orgwrote: Folks, this is a very important topic. I tried to get ahold of the person/people that manages the bots but I didn't succeed so far. Today I noticed that Network team meeting logs are broken (only txt summary and the full html logs give 404). See http://wiki.openstack.org/Network/MeetingLogs We need to be able to share the burden of managing, and fix things in case they break. Do you run an IRC bot on any of the #openstack channels or do you know somebody that does? thanks stef On Sun, 2011-12-11 at 10:08 -0800, Monty Taylor wrote: Hey guys! We have mutliple IRC bots in our channels, each of which do things that are pretty important. I have no idea who runs most of them or where they run. I would love to get these managed, for a few reasons: - They're killer cool, and people will be sad if they stop working - We have a few feature requests out for them - Their operation should probably be documented somewhere - We've got the ability now to handle management of these things through puppet, which means that changes to it can go through gerrit, which means everybody can play. SO - if you are one of the people running one of the IRC bots (or know any of the people running any of these systems) could you ping me so we can talk about if/how if makes any sense to add management of them to systems that we know about and run. Thanks! Monty ___ 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 -- ~~~ 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
[Openstack] Swift-core PPA appears broken
While following the saio instructions (http://swift.openstack.org/development_saio.html) I ran into a problem with the swift-core ppa. I get the following on apt-get update after adding the ppa repo: W: Failed to fetch http://ppa.launchpad.net/swift-core/ppa/ubuntu/dists/lucid/main/binary-amd64/Packages.gz 404 Not Found It appears that there the lucid dist was removed from the ppa, probably on Dec 11, as the directory /swift-core/ppa/ubuntu/dists is shown as modified on that date and no longer contains the lucid subdirectory. Who has responsibility for maintaining the ppa repo, and is there anything I can do to help get it working again? I'm also interested in finding out how the dependencies in the swift-core ppa are maintained, as I would like to be able to isolate python dependencies in a virtualenv but the swift source repo doesn't appear to list the dependencies and their required versions. Thanks! Maru ___ 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-core PPA appears broken
Please disregard. I've added a bug in launchpad and submitted a fix to gerrit. Apologies for the newb email. Thanks! Maru On 2011-12-16, at 7:24 PM, Maru Newby wrote: While following the saio instructions (http://swift.openstack.org/development_saio.html) I ran into a problem with the swift-core ppa. I get the following on apt-get update after adding the ppa repo: W: Failed to fetch http://ppa.launchpad.net/swift-core/ppa/ubuntu/dists/lucid/main/binary-amd64/Packages.gz 404 Not Found It appears that there the lucid dist was removed from the ppa, probably on Dec 11, as the directory /swift-core/ppa/ubuntu/dists is shown as modified on that date and no longer contains the lucid subdirectory. Who has responsibility for maintaining the ppa repo, and is there anything I can do to help get it working again? I'm also interested in finding out how the dependencies in the swift-core ppa are maintained, as I would like to be able to isolate python dependencies in a virtualenv but the swift source repo doesn't appear to list the dependencies and their required versions. Thanks! Maru ___ 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] Keystone client
That's totally fine. The choice to go with python-keystoneclient was based on a small sample of votes present at the time. I only asked in case someone has an alternate, better suggestion - I would want to hear the argument. Z On 12/16/11 7:35 PM, Dolph Mathews dolph.math...@gmail.com wrote: Me, not being aware that we were already moving towards supporting python-keystoneclient, implied that someone was /against/ python-keystoneclient. I have no objections :) -Dolph Mathews On Dec 16, 2011, at 4:56 PM, Ziad Sawalha ziad.sawa...@rackspace.com wrote: Who suggested not using python-keystoneclient? On 12/16/11 4:12 PM, Jesse Andrews anotherje...@gmail.com wrote: python-keystoneclient is based on python-novaclient, and is already in use by horizon as mentioned. What are the reasons for not using python-keystoneclient? Jesse On Fri, Dec 16, 2011 at 1:47 PM, Monty Taylor mord...@inaugust.com wrote: Hrm. For some reason I thought we'd already decided to use the 4P/python-keystoneclient (it's been a todo list item for me to move it in to the openstack repos) I take it that we have _not_ decided that we should use that library as the keystone client library? On 12/16/2011 10:16 AM, Dolph Mathews wrote: Well, I'm certainly not planning on writing a client from scratch, so I'd be happy to hear some discussion on which client we should deem official and replace the others with. My only concern is that we provide an intuitive python API supporting the various auth flows. -Dolph On Fri, Dec 16, 2011 at 8:43 AM, Julien Danjou julien.dan...@enovance.com mailto:julien.dan...@enovance.com wrote: On Fri, Dec 16 2011, Dolph Mathews wrote: Yes (and there's actually more than 2 floating around, in various states); we're moving towards providing a single client, independent of keystone, which can be consumed by other projects (including keystone itself). There's no milestone target for this effort yet, but: https://blueprints.launchpad.net/keystone/+spec/keystone-client Thanks Dolph, I missed that blueprint. Now I think it would be cool if a decision could be done about the library Gabriel wrote. Since it's used by horizon, it seems obvious that it should be integrated as an official OpenStack component, but, eh… anyone's call? :) -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com mailto:julien.dan...@enovance.com ☎ +33 1 49 70 99 81 tel:%2B33%201%2049%2070%2099%2081 ___ 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] Swift slow write performance
increasing concurrency （with -c）should boost write performance. 发自我的 iPhone 在 2011-12-16，11:20，Rustam Aliyev rus...@code.az 写道： Hi, I'm testing swift 1.4.4 setup with 4 nodes/zones on RHEL 5.7. I ran into the problem of slow writes. Using swift-bench we generated load, writing hundreds of 4K files. Results: - Writes - ~3 PUTs/sec (very slow) - Reads - ~25 GETs/sec (ok) It's clear that writes are not limited by I/O. To prove that, I increased file size to 8K, 32K and 64K. In all cases, even with 64K, I had same result - 3 PUTs/sec. In the logs of the object servers I can see that each PUT operation actually took around 0.3 sec which is inline with 3 PUTs/ sec reported by swift-bench. Is that expected performance for such small cluster? Can I break down those 0.3 seconds spent for PUT operation to see where's bottleneck? Any advice for troubleshooting this is welcome. Regards, Rustam. ___ 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-volume] [Bug 884984] Re: Cannot boot from volume with 2 devices
Adding openstack-volumes team to cc: ** Tags added: volumes -- You received this bug notification because you are a member of Nova volume, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/884984 Title: Cannot boot from volume with 2 devices Status in OpenStack Compute (Nova): Confirmed Bug description: More details on: https://answers.launchpad.net/nova/+question/176938 Summary: - Say I had 2 disks, disk1 and disk2 (represented by 2 volumes). disk1 has the root-file-system and disk2 has some data. I boot an instances using the boot-from-volumes extension, and specify the 2 disks such as disk1 should be attached to /dev/vda and disk2 to /dev/vdb. When the instance is launched it fails to boot, because it tries to find the root-filesystem on disk2 instead. The underlying problem is with virsh/libvirt. Boot fails because in the libvirt.xml file created by Openstack, disk2 (/dev/vdb) is listed before disk1 (/dev/vda). So, what happens is that the hypervisor attaches disk2 first (since its listed first in the XML). Therefore when these disks are attached on the guest, disk2 appears as /dev/vda and disk1 as /dev/vdb. Later the kernel tries to find the root filesystem on '/dev/vda' (because that's what is selected as the root) and it fails for obvious reason. I think it's a virsh bug. It should be smart about it and attach the devices in the right order. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/884984/+subscriptions -- Mailing list: https://launchpad.net/~openstack-volume Post to : openstack-volume@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-volume More help : https://help.launchpad.net/ListHelp
