Re: [Openstack] Fwd: Four compute-node, everytime the 1st and 2nd are choosen
I have seen this issue myself when I had a clock skew between the compute nodes. The scheduler assumed one of my nodes was dead because it was so long since it reported, because the compute clock was behind the schedulers clock. I think that was using Cactus, can't 100% remember now. Cheers, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Sateesh Chodapuneedi Sent: 09 November 2011 12:03 To: Razique Mahroua; openstack (openstack@lists.launchpad.net) Subject: Re: [Openstack] Fwd: Four compute-node, everytime the 1st and 2nd are choosen Hi Razique, Which scheduler are you using? And what is the underlying hypervisor? Regards, Sateesh This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. From: openstack-bounces+sateesh.chodapuneedi=citrix@lists.launchpad.net [mailto:openstack-bounces+sateesh.chodapuneedi=citrix@lists.launchpad.net] On Behalf Of Razique Mahroua Sent: Wednesday, November 09, 2011 3:22 PM To: openstack (openstack@lists.launchpad.net) Subject: [Openstack] Fwd: Four compute-node, everytime the 1st and 2nd are choosen I confirm that issue, since I've disabled the nova-compute service on the first 3 nodes, and when I spawn a new instance, now it goes to the last one, so the scheduler would have been able to choose them I've now a disbalanced farm : Host 1 : High load (11 instances) Host2 : Middel load (9 instance) Host 3 : null load (0 instances) Host 4 : null load (1 instance) I use nova 2011.2 (Cactus stable) Thanks Début du message réexpédié : De : Razique Mahroua razique.mahr...@gmail.commailto:razique.mahr...@gmail.com Objet : Four compute-node, everytime the 1st and 2nd are choosen Date : 9 novembre 2011 10:39:17 HNEC À : openstack (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Hl all, I've four compute-nodes, around 20 instances runing. I've four nodes registered to nova-scheduler (nova-manage shows them) but everytime I spawn a new instance, the 3rd an 4th node are never choosen for the instances. the ressources are the same on the nodes (around 24gb of ram), they are idle, and available. Can I force the scheduler to use them for an instance ? Thanks Razique - doc team - inline: image001.gif___ 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] Providing packages for stable releases of OpenStack
On 06 Dec 2011 - 13:52, Duncan McGreggor wrote: Yikes! I forgot an incredibly important one: * What is the migration path story (diablo to essex, essex to f, etc.)? I think it was going to be the Upgrades Team? ___ 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] Nova VMware support improvements
We have recently updated the XenServer/XCP code so the storage is configurable, if you want a pattern to copy. https://github.com/citrix-openstack/nova/blob/everett/nova/virt/xenapi/vm_utils.py If I remember correctly, they assumed standalone ESX hosts with local storage, so never got around to adding a flag to configure which storage is used. Cheers, 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 Graham Hagger Sent: 23 February 2012 01:27 To: Ewan Mellor Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Nova VMware support improvements Right now I'd mostly like to know what the reasoning was behind making the driver only pick the first available local datastore, rather than making it configurable? Also, on http://nova.openstack.org/vmwareapi_readme.html it mentions nova.network.vmwareapi_net for vlan networking support, but it doesn't appear to actually exist in the code - am I missing something? At present I'm just evaluating OpenStack, but support for configurable vmware storage options is one of the first things I'd look to add if it gets picked up. Right now my Python foo is somewhat lacking, but I'll happily contribute what I can when the need arises. Thanks, Graham On Wed, Feb 22, 2012 at 2:03 AM, Ewan Mellor ewan.mel...@eu.citrix.com wrote: It's generally working OK; we (Citrix) did a bit of work on it a couple of months ago. It's not going to get much attention in the near future though, so if you're keen to keep it up to date you'd be more than welcome to get involved. Cheers, Ewan. From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net] On Behalf Of Graham Hagger Sent: Monday, February 20, 2012 11:01 AM To: openstack@lists.launchpad.net Subject: [Openstack] Nova VMware support improvements Greetings all, Is anyone actively working to improve the VMware support within Nova, and is there any kind of roadmap for enhancements? I can find general information about the direction of the project, but nothing specific to VMware right now. Many thanks, Graham ___ 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 with Xen
Hopefully this will help: http://wiki.openstack.org/XenXCPAndXenServer You can get started using DevStack: http://wiki.openstack.org/XenServer/DevStack Thanks, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Eduardo Nunes Sent: 09 March 2012 14:13 To: openstack@lists.launchpad.net Subject: [Openstack] Openstack with Xen i want to use the another hypervisor, so i decide use Xen, how i can do this? ___ 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 with Xen
Hi, So glad people are reading the docs I drafted on the wiki last week :-) Ewan has taken these and added some more color on some of the details. Hopefully these will get pushed into the manuals, and I will update the wiki. With any luck that should clear up some of the confusion. We have XenServer and DevStack working well together, so I felt I could tackle the docs for that combination. My fault there is very little mention of Kronos, I haven't yet got around to trying it. I am half waiting for the DevStack changes to land in trunk. Hopefully I will have chance to visit Mike on Wednesday and try and work on getting the docs to include more Kronos details, and get Kronos and DevStack working together nicely. 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 Anne Gentle Sent: 10 March 2012 14:15 To: Thomas Goirand Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Openstack with Xen I would also ask Ewan to ensure his patch with the Xen chapter to land for openstack-manuals. Thanks Anne On Sat, Mar 10, 2012 at 5:28 AM, Thomas Goirand tho...@goirand.fr wrote: On 03/10/2012 06:10 PM, Armando M. wrote: That's great! if you find gaps, it's a wiki...feel free to fill them up or ask the authors to do so. You are in a great position due to your packaging experience, and your input would be very valuable. This is on my TODO, when I will consider that I'm ready myself with Openstack + XCP, which isn't the case yet. For the moment, I write notes in README.Debian files. Thomas ___ 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] doubt about documentation
Hi, When using XenServer/XCP/Kronos, you will need a para-virtualized VM on that hypervisor to run the nova services. The diagram in this page should help visualize what is going on: http://wiki.openstack.org/XenXCPAndXenServer The easiest way I know to get started is to follow the DevStack instructions: http://wiki.openstack.org/XenServer/DevStack You can then more easily see how everything fits together. You can use XCP (iso or through kronos packages) or Citrix XenServer (free edition has all the features you will need to get started). See what fits your needs the best. Hope that helps, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Eduardo Nunes Sent: 09 March 2012 17:52 To: openstack@lists.launchpad.net Subject: [Openstack] doubt about documentation on the http://wiki.openstack.org/XenServerDevelopment, in some point , it's mentione XenServerhttp://wiki.openstack.org/XenServer requires a nova-compute domU what is nova-compute domU, and where i can find documentation about it? ___ 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-devel] XENAPI_PLUGIN_FAILURE with kronos
On Behalf Of Thomas Goirand which installs the above in the correct folders (which are *NOT* the same as for CentOS). I'd love to have a bit of help from Citrix to test all this by the way. I hear you, and want to help out :-) I hope we can setup some Jenkins tests on various XenServer/XCP/Kronos flavors, public and running against trunk, in the near future. We have the beginnings of a devstack + XenServer one here (it kinda works in our lab, I want to simplyify it and get it using more scripts in DevStack trunk): https://github.com/citrix-openstack/qa/blob/everett/jenkins/run-devstack.sh Cheers, 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
Re: [Openstack] error on nova-compute on domU on xen
Looks like you don't have xenapi installed, somehow. This should do the trick: pip install xenapi It would be interesting to know how you got to that error? Are you using DevStack? Thanks, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Eduardo Nunes Sent: 15 March 2012 17:01 To: openstack@lists.launchpad.net Subject: [Openstack] error on nova-compute on domU on xen got this error on log, 2012-03-15 16:52:33,809 ERROR nova.compute.manager [-] Unable to load the virtualization driver: No module named XenAPI my nova-compute version diablo 2011.3 ___ 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] Devstack +XCP/XenServer Kernel Panic
Hi, We actively working on improving these guides. Hopefully they will become more bullet proof very soon! We are working on getting the wiki up to scratch as a first step: http://wiki.openstack.org/XenServerhttp://wiki.openstack.org/XenServer/XenXCPAndXenServer I have not seen this error myself. How did you install the xva image? Did you use build_domU.sh? Where you running as route when doing build_xva? Can you give me the output of xe vm-param-list for your VM? I can compare that with mine to see if there are any settings that could be causing the issue (like not being in the correct PV-mode, or similar, although not seen that cause a kernel panic myself) Thanks, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Kieran Evans Sent: 17 March 2012 4:38 To: openstack@lists.launchpad.net Subject: [Openstack] Devstack +XCP/XenServer Kernel Panic Hi all, I'm not sure if this is the right place for this (and if not, can anyone point out where). I've used the devstack scripts to try to set up Openstack on both XenServer 6.0 and XCP 1.5 using the following guides: http://wiki.xen.org/wiki/XCP_DevStack https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md Wether on XenServer or XCP, I always seem to hit the same issue. When the ALLINONE VM is fired up, it shuts down after a few seconds with a kernel panic ( as seen here: http://imgur.com/i85fC). The same issue occurs with the domU_multi scripts too. A note, in case it may affect the build scripts somehow, For external storage, rather than using a different machine, or external USB, I've mounted /root to an NFS share before running prepare_dom0.sh. We've currently got a Diablo Openstack installation up and running using StackOps, but I'm currently trying out essex on some spare machines (both to get to know it, and an attempt to see if running with Xen is of any advantage to us). Thanks /Kieran ___ 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] using xenapi hypervisor
Hi, As Todd said, I am concentrating on getting the developer docs straight first. Hence the current fixation on DevStack as a sort of deployment documentation. The current idea (feel free to say this will not work for you) is that people can try out OpenStack with DevStack, kick the tyres. They can then use that as a reference to build another deployment using the tools of their own choosing, copying flag files, etc, as required. Feel free to raise some documentation bugs/requests for areas that you think are the most confusing, and we will do our best to look at those first. Cheers, 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 Todd Deshane Sent: 19 March 2012 10:32 To: Eduardo Nunes Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] [OpenStack] using xenapi hypervisor On Mon, Mar 19, 2012 at 2:19 PM, Eduardo Nunes eduardo.ke...@gmail.com wrote: I wanna use the xenpi as a hypervisor, i see there are many tutorials, but almost all of then is using the devstack, i don't wanna use the devstack, is there a tutorial about how i create a domU, what image i sould use on the domU, an the conf of xen? Some more general documentation has been started here: https://review.openstack.org/#change,5419 The devstack scripts are written in bash and include example configurations within them so that you can make your own custom setups and scripts based on them. There are also chef recipes for working with XenServer here: https://github.com/openstack/openstack-chef/tree/master/cookbooks/xenserver If you look carefully at the individual devstack scripts there are techniques to build stage files, build XVA files, etc. The documentation linked from http://wiki.openstack.org/XenServer is still work in progress, but is written by the actual developers that are making all of this work. The latest devstack scripts are being used and tested by these developers as well. The compute manual, devstack, chef scripts, etc. will evolve over time to include more details and even more information, but as things are built up, you should just ask if you don't understand something so that we can explain and then include more in the documentation. Hope that helps. Thanks, Todd -- Todd Deshane http://www.linkedin.com/in/deshantm http://blog.xen.org/ http://wiki.xen.org/ ___ 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] [Xen-API] nova-xcp-network plugin searching for a xapi0 interface
I have tried to throw together some pictures that help describe the guest networking modes with XenServer: http://wiki.openstack.org/XenServer/NetworkingFlags The idea is to complement the existing diagrams currently in the manuals. It would be great if someone can review these diagrams for me. I can then maybe look at polishing them, and getting them into the manuals. Thanks, John -Original Message- From: Salvatore Orlando Sent: 21 March 2012 00:51 To: John Garbutt; 'Thomas Goirand' Cc: PKG OpenStack; Dave Scott; openstack@lists.launchpad.net; xen-api Subject: RE: [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Hi Thomas, I can probably help you somehow with Openstack networking on XenServer, as I did some work on it in the past. I see you are trying to use the VLAN manager, but the behaviour is not the expected one. However, since you can spin up instances, and they appear to be attached to the appropriate bridge, I'd dare to say you're very close! In a nutshell, when using the VLAN manager on XenServer: 1) A PIF identified either by (A) the vlan_interface flag or (B) the bridge_interface column in the networks db table will be used for creating a XenServer VLAN network. The VLAN tag is found in the vlan column, still in the networks table, and by default the first tag is 100, if my memory does not fail me. 2) VIF for VM instances within this network will be plugged in this VLAN network. As you said, you won't see the bridge until a VIF is plugged in it. This behaviour is the same in XS, XCP, and Kronos. 3) The 'Openstack domU', i.e. the VM running the nova network node, instead will not be plugged into this network; since it acts as a gateway for multiple VLAN networks, it has to be attached on a VLAN trunk. For this reason it must have an interface on the parent bridge of the VLAN bridge where VM instances are plugged. I realized this is quite obscure, so to cut a long story short, if vlan_interface is eth0 it must be plugged in xenbr0, eth1 -- xenbr1, and so on (on Kronos you might also end up with brwlan0). 4) Within the Openstack domU, 'ip link' is then used to configure VLAN interfaces on the 'trunk' port. Each of this vlan interfaces is associated with a dnsmasq instance, which will distribute IP addresses to instances. The lease file for dnsmasq is constantly updated by nova-network, thus ensuring VMs get the IP address specified by the With this configuration, VM instances should be able to get the IP address assigned to them from the appropriate dnsmasq instance, and should be able to communicate without any problem with other VMs on the same network and with the their gateway. The above point (3) probably needs some more explanations. With Open vSwitch, we don't really have distinct bridges for different VLANs; even if they appear as distinct bridges to linux and xen server, they are actually the same OVS instance, which runs a distinct 'fake-bridge' for each VLAN. The 'real' bridge is the 'parent' of the fake one. You can easily navigate fake and real bridges with ovs-vsctl. As you can see I am referring to Openvswitch only. This is for a specific reason: the fake-parent mechanism automatically imply that ports which are not on a fake bridge are trunk ports. This does not happen with linux bridge. A packet forwarded on a VLAN interfaces does not get back in the xenbrX bridge for ethX. So, coming back to your problem I would check that: 1) The XenServer network whose bridge is xapi0 is configured correctly (check PIF, VLAN tag) 2) The Openstack domU is connected to the appropriate bridge according to the value of vlan_interface (which seems wrong in your conf file) 3) Open vSwitch is enabled 4) Check the networks table in your database I hope I have been exhaustive enough to not become pedant... At this point you might wonder why this has not been documented anywhere. Well, my answer is that it was documented, I am very sure it was. However I cannot find the wiki page anymore. I have the sources on my laptop, and I will make sure that VLAN networking and possibly all the other network managers on xenapi backend are documented; including Quantum. Regards, Salvatore -Original Message- From: openstack- bounces+salvatore.orlando=eu.citrix@lists.launchpad.net [mailto:openstack- bounces+salvatore.orlando=eu.citrix@lists.launchpad.net] On Behalf bounces+Of John Garbutt Sent: 19 March 2012 18:01 To: 'Thomas Goirand' Cc: PKG OpenStack; Dave Scott; openstack@lists.launchpad.net; xen-api Subject: Re: [Openstack] [Xen-API] nova-xcp-network plugin searching for a xapi0 interface Hi, Looks like the network configuration is not quite right. Have a look at this, for an example of how things could look networking wise (when using DevStack and XenServer with two nics): http://wiki.openstack.org/XenServer/XenXCPAndXenServer
Re: [Openstack] Devstack +XCP/XenServer Kernel Panic
6.0.0 should work fine. I must have gained some weak mind reading powers, and I just wrote a few more wiki pages. Here is the best place to start: http://wiki.openstack.org/XenServer I actually just added this wiki page (still a work in progress really): http://wiki.openstack.org/XenServer/PostInstall Hope that helps, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Kieran Evans Sent: 22 March 2012 9:49 To: openstack@lists.launchpad.net Subject: Re: [Openstack] Devstack +XCP/XenServer Kernel Panic In hindsight, that makes sense (though I swear I disabled root-squashing). I've been having other issues now, so quick question; Most guides referer/specify XenServer 6.0.2, should 6.0 work (due to 6.0.2 being temporarily unavailable?). I'm going to try now with XenServer 6.0 and build remotely. Another quick question: Should this all work on a completely vanilla install of XenServer or XCP or is there any prep-work not mentioned anywhere, or any steps a complete Xen newb may miss? /Kieran On 21 Mar 2012, at 20:11, Ewan Mellor wrote: I've never seen that kernel panic before. If you're building on an NFS share though, that often screws up the permissions. You could have root-squashing turned on, and then every file that's supposed to be owned by root is owned by an unprivileged user instead. It wouldn't surprise me that this freaks out the init process. I'd try building somewhere else and see if that helps. Or see whether you've got root-squashing or some other permission-modifying option turned on. Cheers, Ewan. From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.netmailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.netmailto:citrix@lists.launchpad.net] On Behalf Of Kieran Evans Sent: Saturday, March 17, 2012 9:38 AM To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: [Openstack] Devstack +XCP/XenServer Kernel Panic Hi all, I'm not sure if this is the right place for this (and if not, can anyone point out where). I've used the devstack scripts to try to set up Openstack on both XenServer 6.0 and XCP 1.5 using the following guides: http://wiki.xen.org/wiki/XCP_DevStack https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md Wether on XenServer or XCP, I always seem to hit the same issue. When the ALLINONE VM is fired up, it shuts down after a few seconds with a kernel panic ( as seen here: http://imgur.com/i85fC). The same issue occurs with the domU_multi scripts too. A note, in case it may affect the build scripts somehow, For external storage, rather than using a different machine, or external USB, I've mounted /root to an NFS share before running prepare_dom0.sh. We've currently got a Diablo Openstack installation up and running using StackOps, but I'm currently trying out essex on some spare machines (both to get to know it, and an attempt to see if running with Xen is of any advantage to us). Thanks /Kieran ___ 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] Devstack +XCP/XenServer Kernel Panic
Afraid I haven't finished producing the supplemental packs yet (might be a few weeks till I get around to finishing that stuff off). I was aiming to allow the supplemental packs to work in both cases, if I can. Cheers, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Kieran Evans Sent: 22 March 2012 1:36 To: openstack@lists.launchpad.net Subject: Re: [Openstack] Devstack +XCP/XenServer Kernel Panic Thanks for the help/advice all. I did have root squashing disabled, but something else must've been playing up. I did the build on another machine and it's working now. At least, the ALLINONE vm booted and prepare_guest.sh is running, so fingers crossed! On one of the wiki pages, it says that an Openstack supplemental pack is in the works, would it be safe to assume this would be a production oriented pack, rather than the devstack style dev oriented setup? /Kieran On 22 Mar 2012, at 11:31, John Garbutt wrote: 6.0.0 should work fine. I must have gained some weak mind reading powers, and I just wrote a few more wiki pages. Here is the best place to start: http://wiki.openstack.org/XenServer I actually just added this wiki page (still a work in progress really): http://wiki.openstack.org/XenServer/PostInstall Hope that helps, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.netmailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.netmailto:eu.citrix@lists.launchpad.net] On Behalf OfKieran Evans Sent: 22 March 2012 9:49 To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Devstack +XCP/XenServer Kernel Panic In hindsight, that makes sense (though I swear I disabled root-squashing). I've been having other issues now, so quick question; Most guides referer/specify XenServer 6.0.2, should 6.0 work (due to 6.0.2 being temporarily unavailable?). I'm going to try now with XenServer 6.0 and build remotely. Another quick question: Should this all work on a completely vanilla install of XenServer or XCP or is there any prep-work not mentioned anywhere, or any steps a complete Xen newb may miss? /Kieran On 21 Mar 2012, at 20:11, Ewan Mellor wrote: I've never seen that kernel panic before. If you're building on an NFS share though, that often screws up the permissions. You could have root-squashing turned on, and then every file that's supposed to be owned by root is owned by an unprivileged user instead. It wouldn't surprise me that this freaks out the init process. I'd try building somewhere else and see if that helps. Or see whether you've got root-squashing or some other permission-modifying option turned on. Cheers, Ewan. From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.netmailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.netmailto:citrix@lists.launchpad.net] On Behalf Of Kieran Evans Sent: Saturday, March 17, 2012 9:38 AM To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: [Openstack] Devstack +XCP/XenServer Kernel Panic Hi all, I'm not sure if this is the right place for this (and if not, can anyone point out where). I've used the devstack scripts to try to set up Openstack on both XenServer 6.0 and XCP 1.5 using the following guides: http://wiki.xen.org/wiki/XCP_DevStack https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md Wether on XenServer or XCP, I always seem to hit the same issue. When the ALLINONE VM is fired up, it shuts down after a few seconds with a kernel panic ( as seen here: http://imgur.com/i85fC). The same issue occurs with the domU_multi scripts too. A note, in case it may affect the build scripts somehow, For external storage, rather than using a different machine, or external USB, I've mounted /root to an NFS share before running prepare_dom0.sh. We've currently got a Diablo Openstack installation up and running using StackOps, but I'm currently trying out essex on some spare machines (both to get to know it, and an attempt to see if running with Xen is of any advantage to us). Thanks /Kieran ___ 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] Xen Hypervisor
I certainly changed the plugin so it always required the host_uuid, but I also changed the call_plugin code in xenapi_conn to ensure we always pass the host_uuid. Indeed it looks like in the code path below, that you should get the host_uuid passed all the way though. I have not tested with XCP myself, only with XenServer 6. I am afraid I will not get chance to try this out till Wednesday (currently on holiday). One other useful log will be from XCP where it logs the parameters passed into the plugin (on XenSever it is /var/log/xensource.log, it could be /var/log/xcp.log? or xapi.log, can't remember I am afraid) You should be able to track the host_uuid to ensure it gets from nova-xapi client-xapi server-plugin If you want to move on with your deployment a work around is to add this into the xenhost plugin: Change: host_uuid=arg_dict['host_uuid'] Into: host_uuid=_run_command(xe host-list | grep uuid).split(:)[-1].strip() The above does not work in all cases, but it should work for your particular case (no pools). If you could raise a nova bug for this, mentioning the version of XCP you are using, that would be great. I hope that helps, John From: Ewan Mellor Sent: 25 March 2012 19:56 To: Alexandre Leites; openstack@lists.launchpad.net Cc: John Garbutt Subject: RE: [Openstack] [OpenStack] Xen Hypervisor It looks like you're hitting a recently introduced bug (maybe). I haven't run the code, but from reading through, it looks like the xenhost.host_data plugin command is going to barf if it is not passed a host_uuid parameter. It used to gracefully handle that case, but since 37a392dc it's not doing so any more. The plugin is being called with no arguments from nova.virt.xenapi.host. Cc'd John Garbutt, who wrote that bit of code. Ewan. From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net] On Behalf Of Alexandre Leites Sent: 23 March 2012 10:46 To: openstack@lists.launchpad.net Subject: Re: [Openstack] [OpenStack] Xen Hypervisor Hi folks, Sorry for late reply, i was trying to install this without following any ready-to-use scripts ( but i used one :( ) to understand how things are made. So i installed XCP 1.4.90 from DVD and configured it from installation screen. Execute the following commands on dom0 --- Dom 0 Extra Config cd /etc/xapi.d/plugins/ wget -q https://raw.github.com/openstack/nova/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/xenhost wget -q https://raw.github.com/openstack/nova/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/xenstore.py wget -q https://raw.github.com/openstack/nova/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/pluginlib_nova.py wget -q https://raw.github.com/openstack/nova/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/migration wget -q https://raw.github.com/openstack/nova/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/glance wget -q https://raw.github.com/openstack/nova/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/agent chmod 777 * service xapi restart --- After that i downloaded XenCenter and created a VM from Ubuntu Server 11.10 CD... (all from below is on guest) After this, i did updated all the system with command apt-get update apt-get upgrade -y apt-get dist-upgrade -y and rebooted the machine. When you do this, you'll boot on newer kernel (3.0.0-16-server, check with uname -a command)... and unsinstall the old kernel (apt-get purge linux-image-3.0.0-12-server). After this, i did installed the virtual kernel (3.0.0-16-virtual) and rebooted the machine. Check if you rebooted in this kernel via uname -a and unsinstall the old kernel. After this, execute on dom0 again: --- Dom 0 Extra Config cd ~ wget http://94.212.78.134/res/xenserver/makepv.sh chmod +x makepv.sh ./makepv.sh YOUR-XEN-GUEST-NAME --- After this, you can do apt-get install -y cracklib-runtime curl wget ssh openssh-server tcpdump ethtool python-pip git vim-nox sudo and pip install xenapi wget http://images.ansolabs.com/xen/xe-guest-utilities_5.6.100-651_amd64.deb -O xe-guest-utilities_5.6.100-651_amd64.deb dpkg -i xe-guest-utilities_5.6.100-651_amd64.deb update-rc.d -f xe-linux-distribution remove update-rc.d xe-linux-distribution defaults mkdir -p /usr/share/cracklib echo a | cracklib-packer pwconv echo root:password | chpasswd rm -f /etc/localtime groupadd libvirtd useradd stack -s /bin/bash -d /opt/stack -G libvirtd echo stack:password | chpasswd echo stack ALL=(ALL) NOPASSWD: ALL etc/sudoers mkdir -p /opt/stack chown -R stack /opt/stack After all this, you can install nova-compute , copy nova.conf from your controller and configure the following vars: --connection_type=xenapi --xenapi_connection_username=root --xenapi_connection_password=password --xenapi_connection_url=http://XENDOM0IP and restart your nova-compute service. You
Re: [Openstack] [OpenStack] Xen Hypervisor
-Original Message- From: Thomas Goirand [mailto:tho...@goirand.fr] Why not using: xe host-list --minimal instead of the grep, split, strip code, which adds useless complexity? [JG] Sure, that is much better. I just cut and paste the old code to save retesting. Also, this piece of code doesn't seem to be resistant to having more than one host as reply (in which case the UUID would be separated by a coma, if I'm not mistaking). [JG] Agreed, my change that removed that code was to fix that exact problem. I think I warned against using it with pools (which is not the OpenStack default). ___ 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] Xen Hypervisor
The public interface, I thought was the interface of the DomU running the service, and it attached its own bridges inside the DomU? I have tried to describe all this here: http://wiki.openstack.org/XenServer/NetworkingFlags Would be cool if people can check that for me, and I can push it into the manuals. Cheers, John From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] Sent: 29 March 2012 19:15 To: John Garbutt Cc: Salvatore Orlando; Alexandre Leites; Ewan Mellor; openstack@lists.launchpad.net; todd.desh...@xen.org Subject: Re: [Openstack] [OpenStack] Xen Hypervisor On Mar 29, 2012, at 7:40 AM, John Garbutt wrote: If you want all your traffic going through a single nic (Management, Instance, Public), it might be possible using these settings: public_interface=eth0 I don't think this will work unless the implementation is very different in xen. xenbr0 will be bridged into eth0, so you actually want to be adding ips to the bridge not the raw eth device. I would suggest public_interface=xenbr0 Xen experts, please correct me if I'm wrong. flat_interface=eth0 flat_network_bridge=xenbr0 ___ 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] [Doc] Nova options changes and documentation
How else can we parcel out the doc work and track it? Open to any and all ideas here. I think a blueprint for the 'Essex Flags' documentation will help track it. We can then link bugs to the blueprint, and update the blueprint with any additional notes or links. I think a single bug for each group of options will probably suffice; there will only be a few people working on this anyways. Can automate that? Maybe get Jenkins, when it merges a branch, to raise a doc bug if a new flag has been added, or the flag comment or default has changed? You might get a few false positives, but that is probably no bad thing. Cheers, 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
Re: [Openstack] [OpenStack] Xen Hypervisor
Just double checking, but about the other machine you have put on the same network as your VMs, is the interface configured in the same subnet as the VMs? Also, Just to be clear, not sure anyone has ever tried the sort of setup you are wanting (Single interface, with no VLANs). I have seen many setups using a single interface and VLANs, and many setups using different physical interfaces, and some combinations of the two, but I haven't seen anyone try collapsing everything onto a single physical interface. It might not work due to the way nova network in flatDHCP works (i.e. adds a DHCP server onto your network). Just checking, but you are using FlatDHCP networking, I presume? If you haven't assigned a floating ip and you are using some kind of flat networking, the public network configuration should be largely unimportant. I think you want these settings: flat_networking_bridge=xenbr0 flat_interface=eth0 What is the state of your VM, does it seem to have the correct IP address from the nova network DHCP? I think you are close with your flags now, but I can't be specific with the help without more information: * a list of your flags in nova.conf * networking info (ifconfig or otherwise) from both Dom0 and DomU (with compute running) and the VM * networking config from XenServer (networks, DomU VIFs and VM VIFs) * a copy (in text form) of the network related tables in your DB (or all the values from your nova-manage network create and related calls) More general advice is: To make sure all the new network settings get applied, I would recommend: * stop all nova services * reset your nova DB o delete the old DB o Create the DB, do DB migration again, etc. o Add in your network again, (please tell us what values you use for that) * start all nova services It might be worth adding a second VIF on the same network, calling that eth1 in the Nova domU and then using that as the flat_interface. Normally it is not recommended that you configure an IP address on the interface that nova-network uses for the guest networking. Not sure what you are trying will work. Thanks, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Alexandre Leites Sent: 02 April 2012 14:53 To: openstack@lists.launchpad.net Subject: Re: [Openstack] [OpenStack] Xen Hypervisor I tried the last thing about changing public interface to eth0... but it still doesn't work. I still with erro of can't ping anything outside of VM (created by nova on xen). From: todd.desh...@xen.org Date: Mon, 2 Apr 2012 09:15:52 -0400 Subject: Re: [Openstack] [OpenStack] Xen Hypervisor To: alex_...@live.com CC: openstack@lists.launchpad.net On Mon, Apr 2, 2012 at 8:49 AM, Alexandre Leites alex_...@live.commailto:alex_...@live.com wrote: Ok, anyway i tested it and didn't worked. Any other solution? You should be more specific. You should explain the specific flags you tried and then post the relevant logs files. Thanks, Todd -- Todd Deshane http://www.linkedin.com/in/deshantm http://blog.xen.org/ http://wiki.xen.org/ ___ 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-manage required or deprecated for essex?
I thought live-migration can happen through the nova CLI now (that is quite new I think). However, there are also some commands for the XenServer storage migration volume driver that can only be done using nova-manage. I assume the intention is to add nova api extensions at some point, so that could be considered deprecated (Renuka should be able to confirm) Cheers, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Anne Gentle Sent: 02 April 2012 15:29 To: Lorin Hochstein Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net) Subject: Re: [Openstack] nova-manage required or deprecated for essex? Woops, meant to paste in a reference to http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2012-01-31.log team meeting on January 31 derp. :) Anne On Mon, Apr 2, 2012 at 9:21 AM, Anne Gentle a...@openstack.orgmailto:a...@openstack.org wrote: Hi Lorin - My understanding is nova-manage image is not available any longer, but based on the team meeting on , we are not planning to remove it from docs since it's just too much work in the timed release timeframe for Essex. For certain nova-manage image is not available, that's the point behind doc bug https://bugs.launchpad.net/openstack-manuals/+bug/957618 For Essex, the docs (and admins) still need to use nova-manage commands for: -network creation -migrating from deprecated auth to Keystone -quick status checks on running services (nova-manage service list) -database sync (migration) -live migration seems to be using it a bit Most other admin tasks can be accomplished in other ways and aren't documented with nova-manage commands. Let me know if this list of nova-manage commands sounds accurate - Vish, Joe Heck, Brian Waldon? Thanks, Anne On Sun, Apr 1, 2012 at 8:58 PM, Lorin Hochstein lo...@nimbisservices.commailto:lo...@nimbisservices.com wrote: Is nova-manage deprecated in essex, or are there some commands that still require nova-manage? I'd like to update the docs accordingly. Yaguang Tang in this bug https://bugs.launchpad.net/openstack-manuals/+bug/957618 said nova-manage will be deprecated. But I couldn't tell from the context if he was referring specifically to nova-manage image, or to nova-manage in general. Right now, the docs have about 100 mentions of nova-manage: [(master) docbkx]$ find . -name '*.xml' | xargs grep nova-manage| wc -l 98 Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.comhttps://www.nimbisservices.com/ ___ Mailing list: https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack 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] Moving nova.rpc into openstack.common
+1 for move to nova.common I remember discussion about versioning these messages to aid rolling / zero-downtime upgrades. Might be worth considering those when doing the decoupling? Cheers, 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 Chris Behrens Sent: 02 April 2012 23:53 To: Russell Bryant Cc: Duncan McGreggor; openstack@lists.launchpad.net; Chris Behrens Subject: Re: [Openstack] Moving nova.rpc into openstack.common Awesome, thanks :) On Apr 2, 2012, at 3:46 PM, Russell Bryant wrote: I just threw up a patch a little while ago: https://review.openstack.org/6119 -- Russell Bryant On 04/02/2012 06:37 PM, Chris Behrens wrote: Seems like a sensible plan. Carrot can go now. I marked it deprecated so we can remove in folsom. I can take care of this today, even. On Apr 2, 2012, at 3:02 PM, Duncan McGreggor dun...@dreamhost.com wrote: +1 Thanks for exploring this, Russell! Next step: getting a common REST API abstraction in place that all the projects can use... ;-) d On Mon, Apr 2, 2012 at 4:26 PM, Russell Bryant rbry...@redhat.com wrote: Greetings, There was a thread on this list a little while ago about moving the notification drivers that are in nova and glance into openstack.common since they provide very similar functionality, but have implementations that have diverged over time. Is anyone actively working on this? If so, please let me know. For the message queue notifiers, nova uses nova.rpc to do the heavy lifting. Glance has notifiers written against the messaging libs directly. I think it makes sense to take the nova approach. This would mean moving nova.rpc into openstack.common before the notifiers can get moved. I have started looking at moving nova.rpc to openstack.common.rpc. My plan is: 1) Write a series of patches that reduces coupling in nova.rpc on the rest of nova. 2) Submit changes needed to support this decoupling to openstack.common. 3) Once nova.rpc is sufficiently decoupled, move it to openstack.common. While doing the above, I want to aim for the least amount of disruption to the rpc interface as is practical. While we're at it, is it time to drop nova.rpc.impl_carrot? It is marked as deprecated in Essex. Is there any reason anyone would still use impl_carrot over impl_kombu? Thoughts? Thanks, -- Russell Bryant ___ 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] [OpenStack] Xen Hypervisor
Thanks for the info. The one thing I am missing is the ifconfig info from inside your VM instance (I would personally use XenCenter to access the console and see what is going on). I am assuming that it is not getting the correct IP address from the DHCP server in nova-network. And I am assuming there is no other DHCP server on that network. OK, so it looks like you have this: --flat_network_bridge=xenbr0 --flat_interface=eth0 --network_manager=nova.network.manager.FlatDHCPManager --public_interface=eth0 Good news is that the DB looks to correctly have the flat_interface. I can't see how your DomU can be listening on 192.168.100.228, given your current config0, looks like nova network has attached and reconfigured eth0 for you. Are you launching instances using horizon or the nova CLI? One idea that might make this work (others please correct me if I am wrong): * Add two extra VIFs (virtual network interface) on your DomU VM * Attach those VIFs to xenbr0, just like the other VIF that is eth0 on your DomU Now try the following configuration: * Configure eth0 to have the IP address you want (presumably it is a static address, as you can't have a DHCP on that network and use flatDHCP?): 192.168.100.238 * Do not configure eth1 to have any address * Configure eth2 to have another IP address that is public facing: 10.42.0.42 / 255.255.255.0, something in the floating ip network maybe * Change the flags: --flat_network_bridge=xenbr0 --flat_interface=eth1 --network_manager=nova.network.manager.FlatDHCPManager --public_interface=eth2 That might leave things a little less broken than trying with a single interface in DomU? However, I am no expert on how nova-network works, hopefully others can confirm the best way forward. Cheers, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Alexandre Leites Sent: 03 April 2012 13:35 To: openstack@lists.launchpad.net Subject: Re: [Openstack] [OpenStack] Xen Hypervisor Dom0: 192.168.100.251 DomU: 192.168.100.238 nova.conf http://pastebin.com/B0PVVWiv ifconfig (dom0 and domU): http://pastebin.com/iCLX91RS nova network table: http://pastebin.com/k5XcXHee Please, explain me how to take others informations if you want, i think i have been taken all information. Thank you. From: john.garb...@citrix.com To: alex_...@live.com; openstack@lists.launchpad.net Date: Mon, 2 Apr 2012 16:05:15 +0100 Subject: RE: [Openstack] [OpenStack] Xen Hypervisor Just double checking, but about the other machine you have put on the same network as your VMs, is the interface configured in the same subnet as the VMs? Also, Just to be clear, not sure anyone has ever tried the sort of setup you are wanting (Single interface, with no VLANs). I have seen many setups using a single interface and VLANs, and many setups using different physical interfaces, and some combinations of the two, but I haven't seen anyone try collapsing everything onto a single physical interface. It might not work due to the way nova network in flatDHCP works (i.e. adds a DHCP server onto your network). Just checking, but you are using FlatDHCP networking, I presume? If you haven't assigned a floating ip and you are using some kind of flat networking, the public network configuration should be largely unimportant. I think you want these settings: flat_networking_bridge=xenbr0 flat_interface=eth0 What is the state of your VM, does it seem to have the correct IP address from the nova network DHCP? I think you are close with your flags now, but I can't be specific with the help without more information: * a list of your flags in nova.conf * networking info (ifconfig or otherwise) from both Dom0 and DomU (with compute running) and the VM * networking config from XenServer (networks, DomU VIFs and VM VIFs) * a copy (in text form) of the network related tables in your DB (or all the values from your nova-manage network create and related calls) More general advice is: To make sure all the new network settings get applied, I would recommend: * stop all nova services * reset your nova DB * delete the old DB * Create the DB, do DB migration again, etc. * Add in your network again, (please tell us what values you use for that) * start all nova services It might be worth adding a second VIF on the same network, calling that eth1 in the Nova domU and then using that as the flat_interface. Normally it is not recommended that you configure an IP address on the interface that nova-network uses for the guest networking. Not sure what you are trying will work. Thanks, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of
Re: [Openstack] Moving nova.rpc into openstack.common
However, I'm not sure how people would feel about having both openstack.common.exception and nova.exception in the tree since they overlap quite a bit. I like being able to do work in pieces, but having them both in the tree leaves the code in an odd state, so we need some end goal in mind. I'm not a huge fan of openstack.common.exception Yeah, I don't see too much value in having everything inherit from a common exception base class. I think the different projects will typically want to customize the error message text... My vote would be to have some handy mix-ins in openstack.common, if that works for everyone ___ 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] Limit flavors to specific hosts
+1 It is certainly worth a session to decide how to modify the scheduler. I suspect all you would need is to do on the compute side is add a stub implementations for add/remove host operations in the compute manager base class (rather than throw NotImplemented exceptions), and maybe an extra XenServer specific flag to suppress the pool creation. I think it has all the DB and metadata functionality required. One thing worth raising, is that currently all hosts in an aggregate must be in the same availability zone. That seems reasonable to me. From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] Sent: 03 April 2012 19:11 To: Day, Phil Cc: John Garbutt; Jan Drake; Lorin Hochstein; openstack@lists.launchpad.net Subject: Re: [Openstack] Limit flavors to specific hosts On Apr 3, 2012, at 6:45 AM, Day, Phil wrote: Hi John, Maybe the problem with host aggregates is that it too quickly became something that was linked to hypervisor capability, rather than being the more general mechanism of which one form of aggregate could be linked to hypervisor capabilities ? Should we have a host aggregates 2.0 session at the Design Summit ? + 1 I think the primary use case is associating metadata with groups of hosts that can be interpreted by the scheduler. Obviously, this same metadata can be used to create pools/etc. in the hypervisor, but we can't forget about the scheduler. Modifying flags on the hosts for capabilities is ugly. Vish ___ 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] EC2 compat.
I got asked by E2C support by RealStatus who have a cool 3D modeling tool that works against EC2 and would love better APIs to make that work well with OpenStack: http://www.youtube.com/watch?feature=player_embeddedv=SOkWRxDwTNI Hopefully I should be able to lend a hand with some of this EC2 work. See you all at the summit session on EC2! Cheers, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Joshua Harlow Sent: 11 April 2012 10:42 To: Duncan McGreggor Cc: openstack Subject: Re: [Openstack] EC2 compat. Sweet, Ideas and thoughts are welcome. There is a lot of cleanup/testing/validation that needs to happen, but someones got to do it :-P On 4/11/12 8:06 AM, Duncan McGreggor dun...@dreamhost.com wrote: Lurking on the thread, but love what I'm seeing :-) Nice work, guys! d On Tue, Apr 10, 2012 at 10:43 PM, Joshua Harlow harlo...@yahoo-inc.com wrote: Very cool, glad to see that is being worked on, it looks pretty similar to what I was thinking of. I'm all for open dialogues. In fact. I was thinking of what is needed to make this work better. Open questions/thoughts/brainstorm (at least that I was thinking of): How strict do we want to be with the XSD? (there aren't a lot of tolerant xsd validators out there, which sux) Should we use something like jaxb for python, that should be more tolerant (unsure as what the best solution here is) How do we continuously measure the compatibility level? # of test cases passing, # of xml differences, # of xsd issues Should we use boto as a intermediate layer? (it is very tolerant) From what I understand there XML code is basically selecting certain attributes out of the XML using SAX, then adding any unknown attributes dynamically on to a object How do we make it repeatable? For a given test X, if there is a problem with test X and its response Y, how do we easily recreate that test X and response Y (so that dev's can fix it)? Do we have a golden set of responses that when test X is called it should match golden response Z (otherwise there is an issue) This is where the mock server maybe useful, in that we can point test X at the mock server; get the expected responses Z, Then point the test X at the real openstack server and get responses Y that should match Z (exactly, minus the request id?) EC2 seems to also already have some type of mocking, but I haven't used it... (http://bit.ly/HJkdh7) I like how there is a tests folder that u guys have, that seems like it could be a good location for the content checking tests which actually require code/logic to dig into the XML response. It might make sense to use another tool to verify the XSD's (how tolerant we want to be is an open question) and another tool that will show u the xml differences (some of which might be ok, some not). I have used in java xmlunit to do those kind of xml difference comparisons, it provides some nifty ways of ignoring certain differences and such. If say we had 3 levels of tests I think that would make sense (starting say from XSD validation, to difference comparisons to content comparisons), and would make a hell of a EC2 cool validation toolkit. The other usage of the site I was making was to list all the known error conditions, and any other incompatibilities that I am noticing with EC2 (error conditions, features, parameters...). That seems really needed to allow for anyone to actually use the EC2 apis and handle all the cases which could be thrown at them. -Josh On 4/10/12 7:02 PM, Eric Windisch e...@cloudscaling.com wrote: Josh, as a follow-up, it would be good to keep an open dialogue on this. When/if you get a chance to review the aws-compat branch, I'd like to get your feedback as well. PS I meant to write assess, not access. I only noticed when I read back my email. I'm too pedantic to not correct myself. ___ 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] Regular XenAPI Meeting
Hi, Are people keen for a XenAPI virt layer meetup on IRC every month? I have added a suggested time to the wiki, as a starting point: Monthly, second Wednesday at 17:00 UTC Does that seem a reasonable time for those that want to attend? It can be more frequent if we find that useful. I don't want to detract from the other meetings, but it would be good to keep all of us working on the XenAPI layer in regular contact. Cheers, 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
Re: [Openstack] Regular XenAPI Meeting
Good plan, I have started a wiki page to capture that stuff: http://wiki.openstack.org/XenAPIMeetings Cheers, John -Original Message- From: Armando Migliaccio [mailto:amigliac...@internap.com] Sent: 24 April 2012 16:23 To: Alan Kavanagh Cc: John Garbutt; openstack@lists.launchpad.net Subject: Re: [Openstack] Regular XenAPI Meeting I'd be interest to join too. Shall we use a wiki page to collate names and affiliations of people interested (there's a Launchpad group set up by the way - https://launchpad.net/~openstack-xenapi), as well as meeting details? Thanks, Armando On Tue, Apr 24, 2012 at 3:32 PM, Alan Kavanagh alan.kavan...@ericsson.com wrote: Hi John +1 would be interested for monthly meeting. Time is ok. Alan From: openstack- bounces+alan.kavanagh=ericsson@lists.launchpad.net [mailto:openstack- bounces+alan.kavanagh=ericsson.com@lists.launchpad.n et] On Behalf Of John Garbutt Sent: April-23-12 1:21 PM To: openstack@lists.launchpad.net Subject: [Openstack] Regular XenAPI Meeting Hi, Are people keen for a XenAPI virt layer meetup on IRC every month? I have added a suggested time to the wiki, as a starting point: Monthly, second Wednesday at 17:00 UTC Does that seem a reasonable time for those that want to attend? It can be more frequent if we find that useful. I don't want to detract from the other meetings, but it would be good to keep all of us working on the XenAPI layer in regular contact. Cheers, 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] Regular XenAPI Meeting
That looks like enough interest to be worthwhile. Date of next meeting: Wednesday 9th May, 17:00 UTC I have updated the wiki page: http://wiki.openstack.org/Meetings/XenAPI Not sure how the meetbot finds out about my plans, advice welcome... Thanks, John -Original Message- From: Zhixue Wu [mailto:zhixue...@gmail.com] Sent: 25 April 2012 00:44 To: John Garbutt Cc: Armando Migliaccio; Alan Kavanagh; openstack@lists.launchpad.net Subject: Re: [Openstack] Regular XenAPI Meeting John, Please count me in as well. Wu Sent from my iPad On Apr 24, 2012, at 11:44 PM, John Garbutt john.garb...@citrix.com wrote: Good plan, I have started a wiki page to capture that stuff: http://wiki.openstack.org/XenAPIMeetings Cheers, John -Original Message- From: Armando Migliaccio [mailto:amigliac...@internap.com] Sent: 24 April 2012 16:23 To: Alan Kavanagh Cc: John Garbutt; openstack@lists.launchpad.net Subject: Re: [Openstack] Regular XenAPI Meeting I'd be interest to join too. Shall we use a wiki page to collate names and affiliations of people interested (there's a Launchpad group set up by the way - https://launchpad.net/~openstack-xenapi), as well as meeting details? Thanks, Armando On Tue, Apr 24, 2012 at 3:32 PM, Alan Kavanagh alan.kavan...@ericsson.com wrote: Hi John +1 would be interested for monthly meeting. Time is ok. Alan From: openstack- bounces+alan.kavanagh=ericsson@lists.launchpad.net [mailto:openstack- bounces+alan.kavanagh=ericsson.com@lists.launchpad.n et] On Behalf Of John Garbutt Sent: April-23-12 1:21 PM To: openstack@lists.launchpad.net Subject: [Openstack] Regular XenAPI Meeting Hi, Are people keen for a XenAPI virt layer meetup on IRC every month? I have added a suggested time to the wiki, as a starting point: Monthly, second Wednesday at 17:00 UTC Does that seem a reasonable time for those that want to attend? It can be more frequent if we find that useful. I don't want to detract from the other meetings, but it would be good to keep all of us working on the XenAPI layer in regular contact. Cheers, 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 ___ 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 VMWare ESXi with openstack
The VMWare and XenServer OpenStack support have very similar architectures. Every hypervisor has a VM that runs the nova-compute code. You don’t as such install it into the hypervisor. In the case of XenServer, there are certainly some plugins that are installed, but nova, at the moment, still runs in a VM on top of the hypervisor. I don’t think OpenStack requires vCenter at all. The email linked below looks like what is in the manual (and was previously on the wiki). I guess the format of the nova conf should be updated, but it looks mostly accurate from what I remember. I hope that helps a little. Thanks, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Jorge de la Cruz Sent: 25 April 2012 14:33 To: Atul Gosain Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Using VMWare ESXi with openstack Hi, I worked with Cloudstack too, Cloudstack use the vCenter for launch the VM's, destroy, etc. That is a good idea but you depend, always, for the good funcionality of vCenter. The Information for Openstack is so short: http://docs.openstack.org/trunk/openstack-compute/admin/content/VMWare_configuration_options.html But i readed a good message before, this: https://lists.launchpad.net/openstack/msg09607.html Cheers -- Jorge de la Cruz Cloud Architect www.stackops.comhttp://www.stackops.com/ | jorge.delac...@stackops.comlogin.jsp?at=a467f3be-21c0-4b31-9a1c-beee62395a4emailto=jorge.delac...@stackops.com | +34 91 309 48 77 | skype:jorge.delacruz.stackops http://www.stackops.com/ [cid:~WRD000.jpg] 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. De: Atul Gosain atul.gos...@gmail.com Para: openstack@lists.launchpad.net Enviados: Miércoles, 25 de Abril 2012 15:18:35 Asunto: [Openstack] Using VMWare ESXi with openstack Hi I tried to see how we can control any existing infrastructure of VMWare/XenServer etc from openstack. What i understood is that nova compute needs to be installed on the hypervisors(compute hosts) which can be Ubuntu Servers for KVM etc. Also for XenServer, we can build a package on Ubuntu and then will have to install on XenServer so that it can be controlled by cloud controller. Basically openstack compute should be installed on hypervisor and accepts the instructions from controller to create VM's, assign IP addresses, destroy, attaching volumes etc. Please confirm this understanding. Based on this, i did not find anything on VMWare ESXi. How does the compute gets installed on ESXi server ? Also, i have seen cloudstack working which seems to be little different than how openstack works. Cloudstack can control existing VMWare/XenServer/KVM etc using their respective API's. It doesnt require any installation on the
Re: [Openstack] raw or qcow2
XenServer does snapshots, but it uses VHD files on the EXT file system. That means it is not supported with LVM storage. As far as I understand things: Snapshot = upload current state of disk to Glance as a new image I have not seen any support for incremental snapshots/backups as yet, but I may have missed that going in? Thanks, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Lorin Hochstein Sent: 25 April 2012 15:44 To: Vishvananda Ishaya Cc: williamherrych...@gmail.com; openstack Subject: Re: [Openstack] raw or qcow2 Since we're talking snapshots, quick doc-related snapshot questions: - Are snapshots only supported on qemu/kvm, or do they work with other hypervisors as well? (Does Xen support qcow2 images?) - Does OpenStack do anything with snapshots other than using them to generate new images? I was a little confused by the existence of the Snapshots pane in Diablo Horizon. I originally thought snapshotting was just a qemu/kvm implementation detail about how nova created a new image from a running instance, so I didn't understand why there was a Snapshots pane in addition to an Images pane. Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.comhttps://www.nimbisservices.com/ On Apr 25, 2012, at 1:55 AM, Vishvananda Ishaya wrote: ? Did you mistype your comment or misread mine? Raw does NOT work for snapshots. snapshots only work for qcow2. Implementing snapshotting with raw would be possible. Logic just needs to be added to skip the internal snapshot step and just use the entire file when uploading to glance. This would be pretty darn slow for large images though. If you are asking about differencing images in glance that is a different question and one that we haven't addressed. It has a lot of implications and needs changes in both nova and glance to be useful. Logic needs to be added around dependency chains and coalescing. Plus it has implications when trying to migrate and resize instances, so there is a lot to consider. As caitlin mentioned, something will be implemented in the volume service anyway, so it might be better to wait and see what happens there. Vish On Apr 24, 2012, at 4:30 PM, Joshua Harlow wrote: What changes would be needed to make qcow2 files work as snapshots? Some type of image dependency management in glance (and failure cases) and the corresponding dependency fetching in nova (and failure cases)? Might be something pretty useful to have, instead of forcing raw for snapshots? On 4/24/12 3:51 PM, Vishvananda Ishaya vishvana...@gmail.comx-msg://474/vishvana...@gmail.com wrote: On Apr 17, 2012, at 2:04 AM, William Herry wrote: so, what changes should I make if I want use raw in openstack, I didn't find some configure option in nova.conf.sample I also try to modify the source code in nova/virt/libvirt/utils.py, and didn't succeed I noticed that the type of snapshot is same as the instance's image by default, does this right, and what about the type of model image that uploaded to glance, does it affect the disk type I use? Thanks snapshots will not work with raw images. To make openstack use raw images, you simply have to set: use_cow_images=false you can upload to glance in qcow or raw, it will be decoded to raw when the image is downloaded to the compute host. Vish ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netx-msg://474/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.netmailto: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] database migration cleanup
I may have missed this in the discussions, but does this impact on upgrade? I am guessing you have tested Essex - Folsom upgrade, but does this affect people upgrading from any of the Essex milestones to Folsom? I guess the deeper question is which upgrade paths do we want to maintain... 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 Dan Prince Sent: 02 May 2012 21:20 To: Vishvananda Ishaya Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] database migration cleanup - Original Message - From: Vishvananda Ishaya vishvana...@gmail.com To: Dan Prince dpri...@redhat.com Cc: openstack@lists.launchpad.net Sent: Thursday, April 26, 2012 4:14:25 PM Subject: Re: [Openstack] database migration cleanup +1. Might be nice to have some kind of test to verify that the new migration leaves the tables in exactly the same state as the old migrations. Hey Vish, This is an outline of what I did to test MySQL and PostgreSQL to ensure the compact migration script generates *exactly* the same schemas as before: http://wiki.openstack.org/database_migration_testing As things stand both MySQL and PostgreSQL are exactly the same. I have some pending changes that I've found in the schemas that need to be fixed in Folsom... but the goal here was to replicate Essex with migration 082 so that is what I did. Sqlite has a few differences (indexes for example). How important is it that the Sqlite schema be exactly the same? Unit tests are passing. Dan Vish On Apr 26, 2012, at 12:24 PM, Dan Prince wrote: The OpenStack Essex release had 82 database migrations. As these grow in number it seems reasonable to clean house from time to time. Now seems as good a time as any. I came up with a first go at it here: https://review.openstack.org/#/c/6847/ The idea is that we would: * Do this early in the release cycle to minimize risk. * Compact all pre-Folsom migrations into a single migration. This migration would be used for new installations. * New migrations during the Folsom release cycle would proceed as normal. * Migrations added during Folsom release cycle could be compacted during E release cycle. TBD if/when we do the next compaction. * Users upgrading from pre-Essex would need to upgrade to Essex first. Then Folsom. -- I think this scheme would support users who follow stable releases as well as users who follow trunk very closely. We talked about this at the conference but I thought this issue might be near and dear to some of our end users so it was worth discussing on the list. What are general thoughts on this approach? Dan (dprince) ___ 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] [QA] Aligning smoke / acceptance / promotion test efforts
+1 to this plan From the above, I would surmise that smoke tests should have all three of the following characteristics: * Test basic operations of an API, usually in a specific order that makes sense as a bare-bones use case of the API * Test only the correct action paths -- in other words, smoke tests do not throw random or invalid input at an API * Use the default client tools to complete the actions * Take a short amount of time to complete [JG] That sounds good. I wonder if we should also restrict them to be user actions only? Maybe we should also try to concentrate on actions that are likely to be available on all OpenStack installations? I am thinking things like resize are less important than VM start. However, I like the idea of testing every user facing compute CLI call using Tempest, but that scope would seem too large for a smoke test. It would be super-awesome if Tempest could be used to remove some of this duplication of efforts. [JG] +1 * Create a base test class that uses the default CLI tools instead of raw HTTP calls [JG] we need to test the default tools, so this sounds like a good plan * Create a set of Manager classes that would provide a config object and one or more client objects to test cases -- this is similar to the tempest.openstack.Manager class currently in the source code, but would allow using the default project client libraries instead of the raw HTTP client currently in Tempest * Allow test cases that derive from the base SmokeTest class to use an ordered test method system -- e.g. test_001_foo, test_002_bar [JG] I don't like order dependent tests, but I think it makes sense in this case * Have the base smoke test case class automatically annotate all of its test methods with type=smoke so that we can run all smoke tests with: nosetests --attr=type=smoke tempest I have put together some code that shows the general idea as a draft patchset [5] [JG] I would like to take this and get it running on several XenServer setups. ___ 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] EC2 api testing
I am certainly up for helping with this effort. I wondered about this approach: * Starting with Tempest (mostly for its reporting, and configuration) * Creating a new category EC2_Compat or something like that * Trying to add in all the tests from those two repos into the new thing * Looking at what the gaps are I am not sure it makes sense for these tests to leave in tempest, but it does seem silly to create our own set of configuration and test runner code, if we don't have to. Seems too early to push this shared code into something like openstack-common-tests, but maybe that is what we need long term? A totally different approach, that sounds attractive, is testing with some of the tools people actually want to use: boto, eucatools. However, this does then mean you end up writing N times as many tests, and it means you have to somehow pick which tools you want to test. Maybe the tests are easier to write, so the fact there is more doesn't matter. While those tests don't really test if we comply with ec2, maybe they do test what people care about. Cheers, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Joshua Harlow Sent: 07 May 2012 18:17 To: Doug Hellmann; Martin Packman Cc: openstack Subject: Re: [Openstack] [Nova] EC2 api testing TBD afaik. I think it would be nice if we could have one tool to rule them all, but I need to get my hands on this enstrsatus thingy to see what is there :-) I've started documenting some EC2 stuff that I see @ https://github.com/yahoo/Openstack-EC2/issues If others want to put stuff on there (or a better location, that's cool with me). On 5/4/12 3:04 PM, Doug Hellmann doug.hellm...@dreamhost.com wrote: On Fri, May 4, 2012 at 1:09 PM, Martin Packman martin.pack...@canonical.com wrote: At the Folsom Design Summit we discussed[1] trying to collaborate on a test suite for EC2 api support. Currently nova supports the common stuff pretty well has differing behaviour in a lot of edge cases. Having a separate suite, along the lines of tempest, that could be run against other existing clouds as well as OpenStack would let us test the tests as well, and would be useful for other projects. Various parties have done work in this direction in the past, the trick is going to be combining it into something we can all use. The existing code I know about includes aws-compat[2], Openstack-EC2[3], the tests in nova itself, some experimental code in awsome, and an Enstratus test suite. I'm hoping to find out more about the Enstratus code, James Urquhart suggested opening the remaining parts would be a reasonable step. Is there anything else out there we should look at as well? Are there any strong opinions over the right way of getting started on this? Are you going to try to get all of the code for those projects into one package, or build a meta-tool that downloads the others and uses them? I don't have an opinion one way or the other, I'm just curious. Doug Martin [1] Nova EC2 compatibility sesson etherpad http://etherpad.openstack.org/FolsomEC2Compatibility [2] https://github.com/cloudscaling/aws-compat [3] https://github.com/yahoo/Openstack-EC2 ___ 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] Reminder: XenAPI meeting
Hi, I plan the first XenAPI meeting is this Wednesday at 17:00 UTC on IRC #openstack-meeting. You can see what 17:00 UTC means here: http://www.timeanddate.com/worldclock/fixedtime.html?iso=20120509T17 You can see the proposed Agenda here: http://wiki.openstack.org/Meetings/XenAPI Hopefully see some of you there! Cheers, John __ John Garbutt Senior Software Development Engineer, Cloud T: +44 1954 283663 john.garb...@citrix.commailto:john.garb...@citrix.com http://www.citrix.comhttp://www.citrix.com/ [cid:image001.jpg@01CD2D40.EC51C0B0] inline: image001.jpg___ 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] EC2 api testing
I was really just thinking of borrowing the test framework around tempest, rather than push the tests back to tempest. I agree we don't want to be too tied to OpenStack. I certainly would like to have this running against CloudStack too. I hoped we could look at doing testing from a user perspective. Maybe having tests like: test_instatance_s3_style_success, test_instance_s3_style_failure_bad_image, etc. Each can check the request, functional and scheme compliance. Could the documentation start a the list of passed and failed tests? Possibly the failure should either be non-compliant or not implemented. Maybe non-compliant could specify which versions it is not compliant with. Cheers, John From: Joshua Harlow [mailto:harlo...@yahoo-inc.com] Sent: 08 May 2012 18:49 To: John Garbutt; Doug Hellmann; Martin Packman; Joe Gordon; jaypi...@gmail.com Cc: openstack Subject: Re: [Openstack] [Nova] EC2 api testing So the tempest approach I think starts to pull this EC2 validation suite into openstack to much. A goal that I think is useful is to have this not that tightly integrated with openstack, so that say cloudstack, and others can use this type of suite as well. That way everyone benefits and everyone can contribute (not just the openstack pep's). I'd personally like to see the following kinds of validations/compliance checks: Request compliance: 1. Send in X request, expect Y response (or at least Z sub-fields of Y response) to match known valid response Y2 * This means we have a need for a whole bunch of requests, a whole bunch of valid responses and a way to determine differences (xmlunit in java provides some of this, I don't know of anything in python). I have created something like this (a framework) that was used for the yahoo-bing ad provider xml transtiion project stuff here, that we might be able to use. Schema compliance: 1. Something along the lines of validating XSDs? Amazon has about 10 versions of there api's, which ones are u complaint with (or that kind of question is to be answered here). * Questions as to how strict and such need to be tackled here (all the python XSD validators seem to blow up on the first error, not so useful when trying to see multiple errors) * https://github.com/yahoo/Openstack-EC2/tree/master/data/xsds Functional compliance: 1. This is where we start to say use boto (which itself uses a very tolerant SAX parser to create python objects) and test anything the above 2 types of tests could not accomplish (say u need a if statement to check some conditions, the above 2 ways probably won't get that). Euca2ools runs on boto, so I would consider that the same case, but using a library might not be the best approach because then u start to run into the issue of the library is not compliant either (ie testing the library instead of the apis). Documentation compliance: 1. This is I guess where we or others document how compliant a suite target is and what the known issues with it are. That was my thoughts anyway :-) - Josh On 5/8/12 8:32 AM, John Garbutt john.garb...@citrix.com wrote: I am certainly up for helping with this effort. I wondered about this approach: * Starting with Tempest (mostly for its reporting, and configuration) * Creating a new category EC2_Compat or something like that * Trying to add in all the tests from those two repos into the new thing * Looking at what the gaps are I am not sure it makes sense for these tests to leave in tempest, but it does seem silly to create our own set of configuration and test runner code, if we don't have to. Seems too early to push this shared code into something like openstack-common-tests, but maybe that is what we need long term? A totally different approach, that sounds attractive, is testing with some of the tools people actually want to use: boto, eucatools. However, this does then mean you end up writing N times as many tests, and it means you have to somehow pick which tools you want to test. Maybe the tests are easier to write, so the fact there is more doesn't matter. While those tests don't really test if we comply with ec2, maybe they do test what people care about. Cheers, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Joshua Harlow Sent: 07 May 2012 18:17 To: Doug Hellmann; Martin Packman Cc: openstack Subject: Re: [Openstack] [Nova] EC2 api testing TBD afaik. I think it would be nice if we could have one tool to rule them all, but I need to get my hands on this enstrsatus thingy to see what is there :-) I've started documenting some EC2 stuff that I see @ https://github.com/yahoo/Openstack-EC2/issues If others want to put stuff on there (or a better location, that's cool with me). On 5/4/12 3:04 PM, Doug Hellmann doug.hellm...@dreamhost.com wrote: On Fri, May 4, 2012
Re: [Openstack] xcp+quantum+vlans= not working security groups
Hi, From Roman Sokolkov: We use XCP + quantum + tenant vlans . One XCP box and one Ubuntu 12.04 box(controller). Nova-compute host it is domU on XCP. Boxes connected with patch-cord and we able to use VLANs inside. There are problems with security groups. They not work at all. We use firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver. And I see expected iptables rules on Dom0, but without any profit. As I understand iptables couldn't work with L2 openvswitch traffic? Not sure that was tested with VLANs, and I don't think there has (yet) been any work to create and OpenVSwitch based firewall driver. Have you seen specific problems with packets getting around the firewall rules when using openvswitch? I know there were plans for making an OpenVSwitch firewall driver, but there are some big performance issues around rule explosion. I don't think there is anything penciled in for Folsom right now. I will get in touch with the networking experts and get back to you. Thanks, 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
Re: [Openstack] [OpenStack][Nova] deference between live-migration and migrate
I have been meaning to draft a blueprint around this. What we have today: * Migrate: move a VM from one server to another, reboots across the move (I think) and destination is picked by scheduler * LiveMigration: move a VM form one server to another, VM doesn't appear to reboot, need to specify the destination I propose we extent the Migrate API (thinking about nova CLI here really) to include: * Optional Flag to force non-live migration, default to live migration * Optional destination host, by default let the scheduler choose * Deprecate the existing live migration API and CLI calls What do people think? I am in the process of adding Live migration support to XenServer: https://blueprints.launchpad.net/nova/+spec/xenapi-live-migration If people like the idea, I should get chance to draft and implement this for Folsom, but I am happy for others to do this if they are also interested. Cheers, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Eric Luo Sent: 25 May 2012 09:55 To: openstack@lists.launchpad.net Subject: [Openstack] [OpenStack][Nova] deference between live-migration and migrate Hello ,all I saw there are tow commands in nova live-migration Migrates a running instance to a new machine. migrate Migrate a server. I know that live-migration means live migration of an instance. But what is this migrate for ? And what does Migrate a server. mean here :)Does it mean Migrates a non-running instance to a new machine here? Thank you! Best regards! Eric Luo 2012-05-25 ___ 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] [XenAPI] Implementing text console (log)
Awesome, this has been on my team's TODO list for far too long. Have you added back the xapi-serial-console blueprint anywhere? At the moment, I have a sort-of working concept of it that only runs under XS6 (the only one that offers VT100 terminals), however it has a fallback to returning nothing if it doesn't find one, however, there is an issue. Yep, we got it added into XS6 especially for OpenStack, certainly missing in previous version. Maybe the API should return some kind of Not Supported response? The way to get the console output is by getting the console URL and CONNECT-ing to it, an example of this in a curl is the following: curl -k -X CONNECT 'https://192.168.1.215/console?uuid=6e12b329-6d72-19a4-f8ea- 61dedcd049b9session_id=OpaqueRef:d04043d3-4328-c1b6-1a2a- 4a3638419967' The curl process will appear to be hanging, but if you run any commands or type anything, you'll see it appear in the screen. Obviously, you need your own session_id and console UUID with type VT100. Right, that seems odd. I have added Wu who was working on this when he was at Citrix. He may have some ideas for you. I can have a word with the XenServer developers about the best way do this, and take a look myself. Have you gone through how KVM/LibVirt code deals with this? Cheers, 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
Re: [Openstack] [OpenStack][Nova] deference between live-migration and migrate
From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] Keep in mind that we actually have three options Good point, I forgot about resize. I guess we have: - Live Migrate (with/without block migrate) - (Non-live) Migrate - Resize I guess the more general way of looking at this is having an optional scheduler hint: - user might want to live-migrate to a different availability zone - user might want to resize to same availability zone - admin might what to migrate (live or otherwise) to a specific server Yun actually suggested that resize/migrate be simplified to do the following instead of scping the file over: * snapshot to glance * boot new image from snapshot This would definitely simplify the code, unfortunately it could have billing/metering repercussions. Forgot about that, I like that too. To get the same semantics, I guess it would be: stop VM, snapshot VM, start new VM, destroy old VM, allow user to delete snapshot. Rollback just resumes VM and deletes snapshot. I guess you could have something like this will use data warning you get on mobiles, but something like: This operation involves you being billed for a snapshot. You may delete the snapshot once the operation has completed What do people think about the billing issues from this change? Cheers, 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
Re: [Openstack] XCP with DevStack
Hi, I assume you are using xcp-xapi in Ubuntu. First of all, is it all running correctly (i.e. xe vm-list is returning correctly): http://wiki.xen.org/wiki/Using_XCP_-_preparing_the_toolstack It turns out the current DevStack will not work with this, but I have pushed some changes to support it: https://review.openstack.org/#/c/7673/ The networking configuration can be a little confusing, there is an overview on the wiki: http://wiki.openstack.org/XenServer/NetworkingFlags The DevStack flags are there to configure each of the VIFs on the DomU, the defaults can be seen here: https://github.com/openstack-dev/devstack/blob/master/tools/xen/xenrc If things are still un clear, do ask some more questions. I have plans to document this exact setup in some detail in the near future. Feel free to add to these docs on the wiki. 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 Takaaki Suzuki Sent: 01 June 2012 10:12 To: openstack@lists.launchpad.net Cc: dev Subject: [Openstack] XCP with DevStack Hi all. I need your knowledge. :) I prepared XCP plus OpenvSwitch with Ubuntu precise on own environment. And I want to prepare DevStack for XCP(Ubuntu). https://github.com/openstack- dev/devstack/blob/master/tools/xen/README.md I don't understand localrc network settings part. The script launched DevStackOSDomU. after that network settings part failed. If you know any other DevStack/OpenStack for XCP installation or configuration document. Please let me know. Thanks! -- Midokura Japan Suzuki ___ 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] Install OpenStack on Fedora 16 and xen (not Xen Cloud Platform)
I think it should be as simple as looking at this step: If you are testing OpenStack in a virtual machine, you need to configure nova to use qemu without KVM and hardware virtualization: $ echo '--libvirt_type=qemu' | sudo tee -a /etc/nova/nova.conf And adding xen rather than qemu. There may be other required changes that other people know about. Cheers, John -Original Message- From: Massimo Canonico [mailto:m...@di.unipmn.it] Sent: 05 June 2012 14:51 To: John Garbutt Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Install OpenStack on Fedora 16 and xen (not Xen Cloud Platform) Hi and thanks for your answer. I was just wondering when I have to specify libvirt_type in the following procedure: http://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova Thanks, Massimo On 06/01/2012 05:28 PM, John Garbutt wrote: You can use Xen with OpenStack without XCP. You do Xen+libvirt. libvirt_type=xen I haven't tried that myself, I am concentrating on XenAPI bases systems. Cheers, John -Original Message- From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix.com@lists.launchpad. net] On Behalf Of Massimo Canonico Sent: 01 June 2012 15:22 To: openstack@lists.launchpad.net Subject: [Openstack] Install OpenStack on Fedora 16 and xen (not Xen Cloud Platform) Hi all, first of thank you very much for your support. Right now I have a fedora 16 with xen (NOT XCP), that is, I have installed those package: xen-licenses-4.1.2-7.fc16.x86_64 xen-hypervisor-4.1.2-7.fc16.x86_64 xen-runtime-4.1.2-7.fc16.x86_64 netxen-firmware-4.0.534-4.fc15.noarch xen-libs-4.1.2-7.fc16.x86_64 xen-4.1.2-7.fc16.x86_64 and xen seems happy: [mex@minicloud03 ~]$ sudo xm info [sudo] password for mex: host : minicloud03.di.unipmn.it release: 3.3.7-1.fc16.x86_64 version: #1 SMP Tue May 22 13:59:39 UTC 2012 machine: x86_64 nr_cpus: 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz: 2400 hw_caps: bfebfbff:20100800::0940:e3bd::0001:00 0 0 virt_caps : hvm total_memory : 4094 free_memory: 717 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params: virt_start=0x8000 xen_changeset : unavailable xen_commandline: placeholder cc_compiler: gcc version 4.6.3 20120306 (Red Hat 4.6.3-2) (GCC) cc_compile_by : mockbuild cc_compile_domain : phx2.fedoraproject.org cc_compile_date: Mon May 7 23:28:57 UTC 2012 xend_config_format : 4 Now the question is: - Can I install openstack in this machine or I must use XCP? Thanks, Massimo ___ 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] Can't launch VM with XCP plus OpenStack Essex release version
It is not well documented (I promise to work on that soon), but you should use an EXT3 local SR, not LVM. It is certainly worth moving to EXT3, just to rule a few things out. I see you are using the Ubuntu XCP packages. This is a version of XenAPI I have not yet started doing much QA on, but I did get a VM started OK when using EXT3. However, I used to get LVM working for the basics with earlier versions of xenapi, so I am shocked that is totally broken on the latest. Also, what sort of VM are you trying to launch? Is it a three part image with external kernel? If you want to get going with XenAPI and OpenStack quickly, I would recommend DevStack and XenServer 6.0.2 (free download) or XCP 1.5 Beta. That is the combination I am testing today. Hoping to test Ubuntu XCP and OpenStack in the next few weeks. Thanks, John PS: I think the problem you are hitting is because there was a recent change in XCP/XenAPI where mounting the VDI into dom0 no longer automatically exposes the partitions of that disk to the Dom0 Kernel, so you need to use kpartx (or similar) to mount to appropriate partition. I can see you are hit this because the device returned is /dev/sm/guid/guid rather than /dev/sda1 or something like that. I got normal VMs working OK despite this, but have not yet gone through all the XenAPI plugins to ensure all the issues are fixed. -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 Takaaki Suzuki Sent: 11 June 2012 04:07 To: openstack@lists.launchpad.net Cc: dev; Ryu Ishimoto Subject: [Openstack] Can't launch VM with XCP plus OpenStack Essex release version Hi all. I need your support again. We had this parted error with XCP plus OpenStack Essex release version. Nova can't launch VM with XCP with OpenStack. I use SR with Local LVM. Did you get parted command error? If you have any idea. Please let me know. -- nova-compute log: -- 2012-06-11 11:42:49 DEBUG nova.compute.manager [req-85e34ab4-885c-4006-ac22-47b0323b9e21 4a7c390b523d40c49aab4ca4dfd92ced 6f9b5c555cc94910bf5b7b4a0b3af4b6] [instance: ae09a885-ab5c-4b10-9582-73423932e40c] Deallocati ng network for instance from (pid=3057) _deallocate_network /usr/lib/python2.7/dist-packages/nova/compute/manager.py:616 2012-06-11 11:42:49 DEBUG nova.rpc.amqp [req-85e34ab4-885c-4006-ac22-47b0323b9e21 4a7c390b523d40c49aab4ca4dfd92ced 6f9b5c555cc94910bf5b7b4a0b3af4b6] Making asynchronous cast on network... from (pid=3057) cast /usr/l ib/python2.7/dist-packages/nova/rpc/amqp.py:346 2012-06-11 11:42:49 ERROR nova.rpc.amqp [req-85e34ab4-885c-4006-ac22-47b0323b9e21 4a7c390b523d40c49aab4ca4dfd92ced 6f9b5c555cc94910bf5b7b4a0b3af4b6] Exception during message handling 2012-06-11 11:42:49 TRACE nova.rpc.amqp Traceback (most recent call last): 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py, line 252, in _process_data 2012-06-11 11:42:49 TRACE nova.rpc.amqp rval = node_func(context=ctxt, **node_args) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/exception.py, line 114, in wrapped 2012-06-11 11:42:49 TRACE nova.rpc.amqp return f(*args, **kw) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 177, in decorated_function 2012-06-11 11:42:49 TRACE nova.rpc.amqp sys.exc_info()) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/contextlib.py, line 24, in __exit__ 2012-06-11 11:42:49 TRACE nova.rpc.amqp self.gen.next() 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 171, in decorated_function 2012-06-11 11:42:49 TRACE nova.rpc.amqp return function(self, context, instance_uuid, *args, **kwargs) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 651, in run_instance 2012-06-11 11:42:49 TRACE nova.rpc.amqp do_run_instance() 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/utils.py, line 945, in inner 2012-06-11 11:42:49 TRACE nova.rpc.amqp retval = f(*args, **kwargs) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 650, in do_run_instance 2012-06-11 11:42:49 TRACE nova.rpc.amqp self._run_instance(context, instance_uuid, **kwargs) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 451, in _run_instance 2012-06-11 11:42:49 TRACE nova.rpc.amqp self._set_instance_error_state(context, instance_uuid) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/contextlib.py, line 24, in __exit__ 2012-06-11 11:42:49 TRACE nova.rpc.amqp
Re: [Openstack] Can't launch VM with XCP plus OpenStack Essex release version
Happy to help :-) You shouldn't need to use kpartx yourself. We may need to use it in the nova code where we try to mount VDIs in Dom0 (in XenAPI plugins) Long term, I should probably look at ways around doing that. Cheers, John -Original Message- From: suz...@midokura.jp [mailto:suz...@midokura.jp] On Behalf Of Takaaki Suzuki Sent: 11 June 2012 11:37 To: John Garbutt Cc: openstack@lists.launchpad.net; dev; Ryu Ishimoto; Mike McClurg Subject: Re: [Openstack] Can't launch VM with XCP plus OpenStack Essex release version Hi John. Thank you for your support again :) Also, what sort of VM are you trying to launch? Is it a three part image with external kernel? Yes, I use this VM images. ttylinux-uec-amd64-12.1_2.6.35-22_1 - ttylinux-uec-amd64-12.1_2.6.35-22_1.img - ttylinux-uec-amd64-12.1_2.6.35-22_1-initrd - ttylinux-uec-amd64-12.1_2.6.35-22_1-loader cirros-0.3.0-x86_64-uec - cirros-0.3.0-x86_64-blank.img - cirros-0.3.0-x86_64-initrd - cirros-0.3.0-x86_64-vmlinuz I'll check use EXT3 local SR and kpartx command. Thanks! Suzuki On Mon, Jun 11, 2012 at 7:03 PM, John Garbutt john.garb...@citrix.com wrote: It is not well documented (I promise to work on that soon), but you should use an EXT3 local SR, not LVM. It is certainly worth moving to EXT3, just to rule a few things out. I see you are using the Ubuntu XCP packages. This is a version of XenAPI I have not yet started doing much QA on, but I did get a VM started OK when using EXT3. However, I used to get LVM working for the basics with earlier versions of xenapi, so I am shocked that is totally broken on the latest. Also, what sort of VM are you trying to launch? Is it a three part image with external kernel? If you want to get going with XenAPI and OpenStack quickly, I would recommend DevStack and XenServer 6.0.2 (free download) or XCP 1.5 Beta. That is the combination I am testing today. Hoping to test Ubuntu XCP and OpenStack in the next few weeks. Thanks, John PS: I think the problem you are hitting is because there was a recent change in XCP/XenAPI where mounting the VDI into dom0 no longer automatically exposes the partitions of that disk to the Dom0 Kernel, so you need to use kpartx (or similar) to mount to appropriate partition. I can see you are hit this because the device returned is /dev/sm/guid/guid rather than /dev/sda1 or something like that. I got normal VMs working OK despite this, but have not yet gone through all the XenAPI plugins to ensure all the issues are fixed. -Original Message- From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix.com@lists.launchpad. net] On Behalf Of Takaaki Suzuki Sent: 11 June 2012 04:07 To: openstack@lists.launchpad.net Cc: dev; Ryu Ishimoto Subject: [Openstack] Can't launch VM with XCP plus OpenStack Essex release version Hi all. I need your support again. We had this parted error with XCP plus OpenStack Essex release version. Nova can't launch VM with XCP with OpenStack. I use SR with Local LVM. Did you get parted command error? If you have any idea. Please let me know. -- nova-compute log: -- 2012-06-11 11:42:49 DEBUG nova.compute.manager [req-85e34ab4-885c-4006-ac22-47b0323b9e21 4a7c390b523d40c49aab4ca4dfd92ced 6f9b5c555cc94910bf5b7b4a0b3af4b6] [instance: ae09a885-ab5c-4b10-9582-73423932e40c] Deallocati ng network for instance from (pid=3057) _deallocate_network /usr/lib/python2.7/dist-packages/nova/compute/manager.py:616 2012-06-11 11:42:49 DEBUG nova.rpc.amqp [req-85e34ab4-885c-4006-ac22-47b0323b9e21 4a7c390b523d40c49aab4ca4dfd92ced 6f9b5c555cc94910bf5b7b4a0b3af4b6] Making asynchronous cast on network... from (pid=3057) cast /usr/l ib/python2.7/dist-packages/nova/rpc/amqp.py:346 2012-06-11 11:42:49 ERROR nova.rpc.amqp [req-85e34ab4-885c-4006-ac22-47b0323b9e21 4a7c390b523d40c49aab4ca4dfd92ced 6f9b5c555cc94910bf5b7b4a0b3af4b6] Exception during message handling 2012-06-11 11:42:49 TRACE nova.rpc.amqp Traceback (most recent call last): 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py, line 252, in _process_data 2012-06-11 11:42:49 TRACE nova.rpc.amqp rval = node_func(context=ctxt, **node_args) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/exception.py, line 114, in wrapped 2012-06-11 11:42:49 TRACE nova.rpc.amqp return f(*args, **kw) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 177, in decorated_function 2012-06-11 11:42:49 TRACE nova.rpc.amqp sys.exc_info()) 2012-06-11 11:42:49 TRACE nova.rpc.amqp File /usr/lib/python2.7/contextlib.py, line 24, in __exit__ 2012-06-11 11:42:49 TRACE nova.rpc.amqp self.gen.next
[Openstack] Errors running individual tests that call into the database
Hi, I am trying to run tests like test_xenapi and test_libvirt by themselves do things like: nosetests test_xenapi But it does work, I get DB errors relating to missing tables. However, I can successfully run all the tests. The way I understand it: - nova.tests.__init__.py setup() does the database setup - nova.test.py TestCase.setUp() does the resetting of the db It is almost like doing nosetests test_asdf skips the database setup in nova.tests.__init__.py, is that correct? Any ideas on how to run tests individually, but still get the database correclty initialized? Am I just calling the tests incorrectly? Thanks, 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
Re: [Openstack] Errors running individual tests that call into the database
I have pushed a possible way we can fix this:
https://bugs.launchpad.net/nova/+bug/1012179
Not sure I like the fix I have come up with though.
Cheers,
John
-Original Message-
From: Daniel P. Berrange [mailto:berra...@redhat.com]
Sent: 11 June 2012 18:14
To: John Garbutt
Cc: openstack@lists.launchpad.net; Monty Taylor
Subject: Re: [Openstack] Errors running individual tests that call into the
database
On Mon, Jun 11, 2012 at 05:51:44PM +0100, Daniel P. Berrange wrote:
On Mon, Jun 11, 2012 at 05:04:51PM +0100, John Garbutt wrote:
Hi,
I am trying to run tests like test_xenapi and test_libvirt by
themselves do things like:
nosetests test_xenapi
But it does work, I get DB errors relating to missing tables.
However, I can successfully run all the tests.
The way I understand it:
- nova.tests.__init__.py setup() does the database setup
- nova.test.py TestCase.setUp() does the resetting of the db
It is almost like doing nosetests test_asdf skips the database
setup in nova.tests.__init__.py, is that correct?
Any ideas on how to run tests individually, but still get the
database correclty initialized? Am I just calling the tests incorrectly?
I don't know the answer to your question, but I found this regression
in functionality was caused by the following commit:
commit cf31b789927cedfd08c67dcf207b4a10ce2b1db6
Author: Monty Taylor mord...@inaugust.com
Date: Sun Jun 3 13:03:21 2012 -0400
Finalize tox config.
Shrink tox.ini to the new short version.
Fix the test cases to be able to be run in nosetets plus the
openstack.nose_plugin, which finally removes the need for
nova/testing/runner.py
Also, now we'll just output directly to stdout, which will
make nose collect the trace logging directly and either output
it at the end of the run, or inject it into the xunit output
appropriately.
Change-Id: I1456e18a11a840145492038108bdfe812c8230d1
Before that commit, it was possible to just invoke something like
./run_tests.sh -N -P test_libvirt
from the nova top level GIT directory to run an individual test suite.
After examining that commit I discovered that the old testing/runner.py file
have a bit of magic to auto-prefix nova.tests onto any args:
# If any argument looks like a test name but doesn't have nova.tests in
# front of it, automatically add that so we don't have to type as much
for i, arg in enumerate(argv):
if arg.startswith('test_'):
argv[i] = 'nova.tests.%s' % arg
Since we lost this, you now have to fully specify the names of the individual
tests you want to run. eg this works for me:
./run_tests.sh -N -P nova.tests.test_libvirt
Regards,
Daniel
--
|: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
___
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-operators] Nova Controller HA issues
I know there is some work in the XenAPI driver to make it resilient to these kinds of failures (to allow frequent updates of the nova code), and I think there were plans for the work to be reused in the Libvirt driver. AFAIK, in Essex and lower, bad things can happen if you don't wait for all the tasks to finish. You may well be OK some of the time. It boils down to an issue of consuming the message from Rabbit but not completing the task, and not being able to recover from half completed tasks. Hope that helps, John From: Igor Laskovy [mailto:igor.lask...@gmail.com] Sent: 15 June 2012 11:31 To: Christian Parpart Cc: John Garbutt; openstack-operat...@lists.openstack.org; lt,openstack@lists.launchpad.netgt, Subject: Re: [Openstack-operators] Nova Controller HA issues I am using OpenStack for my little lab for a short time too)) Ok, you are right of course, but I meant a some another design when told about virtualization controller nodes. It is can be only two dedicated hypetvisor with dedicated share/drbd between them. This hypervisors will be standalone, and not be part of nova. Than, maybe pacemaker or another tool can take availability function to restart VM to alive node when active will die. Main question here - how worth can be if occurs controller nodes unexpected power off. In another word, when VM restart it will be in crash consisted state. Will some nova services will loose here? Will RabbiMQ loose some data here? (I am new to RabbitMQ too) Igor Laskovy facebook.com/igor.laskovyhttp://facebook.com/igor.laskovy Kiev, Ukraine On Jun 15, 2012 10:54 AM, Christian Parpart tra...@gmail.commailto:tra...@gmail.com wrote: Hey, well, I said I might be wrong because I have no clear vision on how OpenStack works in its deepest detail, however, I would not like to depend on a controller node that is inside a virtual machine, controlled by compute nodes, that are controlled by the controller node. This sounds quite like a chicken-and-egg problem. However, at the time of this writing, I think you'll have to have a working nova-scheduler process, which is responsible on deciding on which compute node to spawn your VM (what else?), and think about what you do when this (or all your controller-)VMs terribly die, and you want to rebuild it, how do you plan to do this when your controller node is out-of-service? I in my case have put the controller services onto two compute nodes, and use Pacemaker to switch between them, in case one node goes down, the other can take over (via shared service-IP). Again, these are my thoughts, and I am using OpenStack for just about a month now :-) But I hope this helps a bit... Best regards, Christian Parpart. On Fri, Jun 15, 2012 at 8:16 AM, Igor Laskovy igor.lask...@gmail.commailto:igor.lask...@gmail.com wrote: Why? Can you please clarify. Igor Laskovy facebook.com/igor.laskovyhttp://facebook.com/igor.laskovy Kiev, Ukraine On Jun 15, 2012 1:55 AM, Christian Parpart tra...@gmail.commailto:tra...@gmail.com wrote: I don't think putting the controller node completely into a VM is a good advice, at least when speaking of nova-scheduler and nova-api (if central). I may be wrong, and if so, please correct me. Christian. On Thu, Jun 14, 2012 at 7:20 PM, Igor Laskovy igor.lask...@gmail.commailto:igor.lask...@gmail.com wrote: Hi, have any updates there? Can anybody clarify what happens if controller nodes just going hard shutdown? I thinking about solution with two hypervisors and putting controller node in VM shared storage, which can be relaunched when active hypervisor will die. Any ideas, advise? On Tue, Jun 12, 2012 at 3:52 PM, John Garbutt john.garb...@citrix.commailto:john.garb...@citrix.com wrote: Sure, I get your point. I think Florian is working on some docs to help on that. Not sure how much has been done already. Cheers, John From: Christian Parpart [mailto:tra...@gmail.commailto:tra...@gmail.com] Sent: 12 June 2012 13:47 To: John Garbutt Cc: openstack-operat...@lists.openstack.orgmailto:openstack-operat...@lists.openstack.org Subject: Re: [Openstack-operators] Nova Controller HA issues Hey, ya I also found this page, but didn't find it yet that helpful, it rather much sounds like a theoretical paper on how they implemented it rather then telling me on how to actually make it happen (from the sysop point of view :-) I hoped that someone had to face this already, since I really find it very unintuitive to realize, or need to wait until I get more time to investigate dedicated. :-) Regards, Christian. On Tue, Jun 12, 2012 at 12:52 PM, John Garbutt john.garb...@citrix.commailto:john.garb...@citrix.com wrote: I thought Rabbit had a built in HA solution these days: http://www.rabbitmq.com/ha.html From: openstack-operators-boun...@lists.openstack.orgmailto:openstack-operators-boun...@lists.openstack.org [mailto:openstack-operators-boun...@lists.openstack.orgmailto:openstack
Re: [Openstack] XCP with DevStack
Hi,
I developed those changes with Ubuntu 12.04, so it should be OK.
I think that error means you don't have anything set in HOST_IP (i.e. IP
address of the XenServer) at the point in install_os_domU.sh:
https://github.com/openstack-dev/devstack/blob/master/tools/xen/install_os_domU.sh#L257
The HOST_IP should have been setup by this (or whatever is in your localrc
file):
https://github.com/openstack-dev/devstack/blob/master/tools/xen/install_os_domU.sh#L168
Have you got the networking working correctly on your XenServer on Ubuntu?
Ifconfig should list xenbr0 having an appropriate IP address.
Hope that helps,
John
From: r...@midokura.jp [mailto:r...@midokura.jp] On Behalf Of Ishimoto, Ryu
Sent: 22 June 2012 3:11
To: John Garbutt
Cc: Takaaki Suzuki; openstack@lists.launchpad.net
Subject: Re: [Openstack] XCP with DevStack
Hi John,
Thanks for all your help. I have a question regarding your patch to make
devstack work with XCP (https://review.openstack.org/#/c/7673/). Does this
patch apply to devstack with XCP 1.3.2(the package version that comes with
Ubuntu 12.04?) We verified that devstack does install without a problem with
XCP 1.5 but we are still having issues with 1.3.2.
After looking into this issue a bit further, we noticed that the problem occurs
during the OpenStack DomU VM installation process. The preseed file location
is incorrect ('http:///devstackubuntupressed.cfg') even though this file was
copied to the correct location by the script prior to the installation step.
Due to our lack of knowledge in this matter, all we could manage was to
hard-code the proper URL in the kernel parameter set in
'tools/xen/scripts/install-os-vpx.sh' script. To be more precise, we added the
hard-coded URL in the generation of kernel parameters in 'set_kernel_params()'
method, and this successfully got us through the installation process.
Although this temporary hack got us moving forward, we would love to get some
inputs on how we can actually fix this.
We would really like devstack to work with 1.3, so if you or anyone could point
us in the right direction, we would be more than happy to help out on this.
Thanks in advance!
Cheers,
Ryu
On Fri, Jun 1, 2012 at 9:18 PM, John Garbutt
john.garb...@citrix.commailto:john.garb...@citrix.com wrote:
Hi,
I assume you are using xcp-xapi in Ubuntu. First of all, is it all running
correctly (i.e. xe vm-list is returning correctly):
http://wiki.xen.org/wiki/Using_XCP_-_preparing_the_toolstack
It turns out the current DevStack will not work with this, but I have pushed
some changes to support it:
https://review.openstack.org/#/c/7673/
The networking configuration can be a little confusing, there is an overview on
the wiki:
http://wiki.openstack.org/XenServer/NetworkingFlags
The DevStack flags are there to configure each of the VIFs on the DomU, the
defaults can be seen here:
https://github.com/openstack-dev/devstack/blob/master/tools/xen/xenrc
If things are still un clear, do ask some more questions.
I have plans to document this exact setup in some detail in the near future.
Feel free to add to these docs on the wiki.
Thanks,
John
-Original Message-
From:
openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.netmailto:eu.citrix@lists.launchpad.net
[mailto:openstack-bounces+john.garbuttmailto:openstack-bounces%2Bjohn.garbutt=eu.citrix@lists.launchpad.netmailto:eu.citrix@lists.launchpad.net]
On Behalf Of Takaaki Suzuki
Sent: 01 June 2012 10:12
To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Cc: dev
Subject: [Openstack] XCP with DevStack
Hi all.
I need your knowledge. :)
I prepared XCP plus OpenvSwitch with Ubuntu precise on own environment.
And I want to prepare DevStack for XCP(Ubuntu).
https://github.com/openstack-
dev/devstack/blob/master/tools/xen/README.md
I don't understand localrc network settings part.
The script launched DevStackOSDomU. after that network settings part failed.
If you know any other DevStack/OpenStack for XCP installation or
configuration document.
Please let me know.
Thanks!
--
Midokura Japan
Suzuki
___
Mailing list: https://launchpad.net/~openstack
Post to :
openstack@lists.launchpad.netmailto: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] HVM + Xen Hypervisor via libvirt possible?
I have asked some of the Xen.org guys if they know anyone who has time to fix this. I will let you know if I have any luck. But yes, the XenAPI driver (talking to XCP) is probably the best way forward with Xen right now. If there are any blockers making that work, I am happy to help were I can. Cheers, 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 Thomas Goirand Sent: 22 June 2012 2:40 Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] HVM + Xen Hypervisor via libvirt possible? On 06/22/2012 05:56 PM, Daniel P. Berrange wrote: 3. or some good reasons to migrate from Xen to KVM? I'd favour KVM for a variety of reasons, but lets not turn this into a bikeshed discussion about which is best ;-P Let's put it this way: if you want to run with libvirt and Openstack, then yes, you should probably switch to KVM. But if you want to keep Xen, then you should probably switch to XCP. Thomas ___ 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] XCP with DevStack
Glad your networking is fine :)
One other possibility is, do you have anything in the PRESEED_URL variable?
Are you OK to share your localrc file?
Cheers,
John
From: r...@midokura.jp [mailto:r...@midokura.jp] On Behalf Of Ishimoto, Ryu
Sent: 25 June 2012 3:49
To: John Garbutt
Cc: Takaaki Suzuki; openstack@lists.launchpad.net
Subject: Re: [Openstack] XCP with DevStack
Hi John,
I think that error means you don't have anything set in HOST_IP (i.e. IP
address of the XenServer) at the point in install_os_domU.sh:
https://github.com/openstack-dev/devstack/blob/master/tools/xen/install_os_domU.sh#L257
The HOST_IP should have been setup by this (or whatever is in your localrc
file):
https://github.com/openstack-dev/devstack/blob/master/tools/xen/install_os_domU.sh#L168
Thanks for pointing these out. While tracing out the problem, interestingly, I
noticed that HOST_IP was indeed set properly inside the script(and so was
PRESEED_URL). Even so, for whatever reason during the DomU install, the IP got
stripped out from the preseed URL:
http:///devstackubuntupreseed.cfghttp://devstackubuntupreseed.cfg.
Have you got the networking working correctly on your XenServer on Ubuntu?
Ifconfig should list xenbr0 having an appropriate IP address.
Yes, networking is working properly. It is solely a DomU installation issue
that we are having with devstack + XCP 1.3. Everything else is working like a
charm so far.
Good to know that you have already gotten it to work on 12.04. It is most
likely some silly configuration mistake that I've made that's causing this. I
will try digging a bit more myself and will let you know if I come across any
interesting finding.
Thanks!
Ryu
Hope that helps,
John
From: r...@midokura.jpmailto:r...@midokura.jp
[mailto:r...@midokura.jpmailto:r...@midokura.jp] On Behalf Of Ishimoto, Ryu
Sent: 22 June 2012 3:11
To: John Garbutt
Cc: Takaaki Suzuki;
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: Re: [Openstack] XCP with DevStack
Hi John,
Thanks for all your help. I have a question regarding your patch to make
devstack work with XCP (https://review.openstack.org/#/c/7673/). Does this
patch apply to devstack with XCP 1.3.2(the package version that comes with
Ubuntu 12.04?) We verified that devstack does install without a problem with
XCP 1.5 but we are still having issues with 1.3.2.
After looking into this issue a bit further, we noticed that the problem occurs
during the OpenStack DomU VM installation process. The preseed file location
is incorrect ('http:///devstackubuntupressed.cfg') even though this file was
copied to the correct location by the script prior to the installation step.
Due to our lack of knowledge in this matter, all we could manage was to
hard-code the proper URL in the kernel parameter set in
'tools/xen/scripts/install-os-vpx.sh' script. To be more precise, we added the
hard-coded URL in the generation of kernel parameters in 'set_kernel_params()'
method, and this successfully got us through the installation process.
Although this temporary hack got us moving forward, we would love to get some
inputs on how we can actually fix this.
We would really like devstack to work with 1.3, so if you or anyone could point
us in the right direction, we would be more than happy to help out on this.
Thanks in advance!
Cheers,
Ryu
On Fri, Jun 1, 2012 at 9:18 PM, John Garbutt
john.garb...@citrix.commailto:john.garb...@citrix.com wrote:
Hi,
I assume you are using xcp-xapi in Ubuntu. First of all, is it all running
correctly (i.e. xe vm-list is returning correctly):
http://wiki.xen.org/wiki/Using_XCP_-_preparing_the_toolstack
It turns out the current DevStack will not work with this, but I have pushed
some changes to support it:
https://review.openstack.org/#/c/7673/
The networking configuration can be a little confusing, there is an overview on
the wiki:
http://wiki.openstack.org/XenServer/NetworkingFlags
The DevStack flags are there to configure each of the VIFs on the DomU, the
defaults can be seen here:
https://github.com/openstack-dev/devstack/blob/master/tools/xen/xenrc
If things are still un clear, do ask some more questions.
I have plans to document this exact setup in some detail in the near future.
Feel free to add to these docs on the wiki.
Thanks,
John
-Original Message-
From:
openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.netmailto:eu.citrix@lists.launchpad.net
[mailto:openstack-bounces+john.garbuttmailto:openstack-bounces%2Bjohn.garbutt=eu.citrix@lists.launchpad.netmailto:eu.citrix@lists.launchpad.net]
On Behalf Of Takaaki Suzuki
Sent: 01 June 2012 10:12
To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Cc: dev
Subject: [Openstack] XCP with DevStack
Hi all.
I need your knowledge. :)
I prepared XCP plus OpenvSwitch with Ubuntu precise on own environment.
And I want to prepare DevStack for XCP(Ubuntu).
https
Re: [Openstack] XCP with DevStack
From: Thomas Goirand I wrote it before, and I will write it again: a shell script is not, and will never replace, a documentation. What you need to do is write enough documentation so that an experienced admin can write his own script, not the other way around! So please write a decent tutorial. I don' t disagree, it's by no means perfect at the moment. I plan to write a tutorial at some point soon, to complement the scripts. My docs plans for Folsom are: - Update the getting started guide for new DevStack - Review docs for KVM specific material - Raise and fix bugs around the above issues - Write a manual getting started guide Hopefully that should leave us in a better position, and hopefully I will get on to that soon. Afraid QA and coding currently proving higher priority. Cheers, 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
[Openstack] PEP8 checks
Hi, I noticed I can now run the pep8 tests like this (taken from Jenkins job): tox -v -epep8 ... pep8: commands succeeded congratulations :) But the old way to run tests seems to fail: ./run-tests.sh -p ... File /home/johngar/openstack/nova/.venv/local/lib/python2.7/site-packages/pep8.py, line 1220, in check_logical for result in self.run_check(check, argument_names): TypeError: 'NoneType' object is not iterable Is this expected? Did I just miss an email about this change? Cheers, 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
Re: [Openstack] PEP8 checks
I had pep8 v1.2 in my virtual env from this: https://github.com/openstack/nova/commit/2fa2cd2254a4044aaa584c4fcf5d6c3e1ec60d1f#tools/test-requires Rebased with trunk and re-creating my virtualenv (i.e. move back to pep8 v1.1) seemed to fix things. Thanks for your help, John -Original Message- From: Monty Taylor [mailto:mord...@inaugust.com] Sent: 02 July 2012 1:28 To: John Garbutt Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] PEP8 checks On 07/02/2012 06:46 AM, John Garbutt wrote: Hi, I noticed I can now run the pep8 tests like this (taken from Jenkins job): tox -v -epep8 ... pep8: commands succeeded congratulations :) But the old way to run tests seems to fail: ./run-tests.sh -p ... File /home/johngar/openstack/nova/.venv/local/lib/python2.7/site- packages/pep8.py, line 1220, in check_logical for result in self.run_check(check, argument_names): TypeError: 'NoneType' object is not iterable Is this expected? Did I just miss an email about this change? I cannot reproduce this on my system. Can you run bash -x run_tests.sh -p and pastebin the output? Also, tools/with_venv.sh pep8 --version just to be sure. ___ 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] How do I stop image-create from using /tmp?
Sorry to go back in the tread, but just wanted to ask a possibly dumb question. Daniel P. Berrange wrote: In the particular case of the qemu-img command described in earlier in this thread, I'm not convinced we need a new option. Instead of using /tmp when extracting a snapshot from an existing disk image, it could just use the path where the source image already resides. ie the existing FLAGS.instances_path directory, which can be assumed to be a suitably large persistent data store. Would that not be a bad idea for those having FLAGS.instances_path on a shared file system, like gluster? Cheers, 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
Re: [Openstack] How do I stop image-create from using /tmp?
From: Daniel P. Berrange [mailto:berra...@redhat.com] Sent: 03 July 2012 11:09 This would suggest there's a potential use case for a new config parameter FLAGS.local_scratch_path, whose default value matches FLAGS.instances_path if not set. +1 Cheers, 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
Re: [Openstack] Setting VM passwords when not running on Xen
This seemed to crop up quite a lot in different sessions at the Design summit. I am certainly interested in a standard way to inject information into VMs. What I think we need is a cross hypervisor two-way guest communication channel that is fairly transparent to the user of that VM (i.e. ideally not a network connection). If I understand things correctly, we currently have these setup ideas: * Config Drive (not supported by XenAPI, but not a two way transport) * Cloud-Init / Metadata service (depends on DHCP(?), and not a two-way transport) But to set the password, we ideally want two way communication. We currently have these: * XenAPI guest plugin (XenServer specific, uses XenStore, but two way, no networking assumed ) * Serial port (used by http://wiki.libvirt.org/page/Qemu_guest_agent but not supported on XenServer) I like the idea of building a common interface (maybe write out to a known file system location) for the above two hypervisor specific mechanisms. The agent should be able to pick which mechanism works. Then on top of that, we could write a common agent that can be shared for all the different hypervisors. You could also fallback to the metadata service and config drive when no two way communication is available. I would love this Guest Agent to be an OpenStack project that can then be up streamed into many Linux distribution cloud images. Sadly, I don't have any time to work on this right now, but hopefully that will change in the near future. Cheers, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Day, Phil Sent: 03 July 2012 3:07 To: openstack@lists.launchpad.net (openstack@lists.launchpad.net) (openstack@lists.launchpad.net) Subject: [Openstack] Setting VM passwords when not running on Xen Hi Folks, Is anyone else looking at how to support images that need a password rather than an ssh key (windows) on hypervisors that don't support set_admin_password (e.g. libvirt) ? Thanks Phil ___ 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] Setting VM passwords when not running on Xen
Interesting idea, that seams reasonable. The password is encrypted when it leaves the VM in the XenServer case too (if I have understood the code correctly). My only concerns are thinking about the more general solution: * It only works on boot, so harder to change password if you forgot it. * I guess it leaves people who are depended on Config drive stuck * We are making more changes to an API we don't really own * How does the VM know to trust it is not an evil metadata service, but I guess the same applies to injecting the SSH keys Cheers, John From: Day, Phil [mailto:philip@hp.com] Sent: 03 July 2012 6:06 To: John Garbutt; openstack@lists.launchpad.net (openstack@lists.launchpad.net) (openstack@lists.launchpad.net) Subject: RE: Setting VM passwords when not running on Xen Thanks John, One approach we were wondering about is to have an agent in Windows which: o Generates a random password and sets it for the admin account o Gets the public ssh key from the metadata service o Encrypts the password with the public key o Pushes the encrypted public key back to the metadata server (requires the metadata server to support Push) The user can then get the encrypted password from the API and decrypt it with their private key The advantage would be that the clear text password never leaves the VM, so there are fewer security concerns about Nova having access to clear text passwords. It would also seem to be a small change in the metadata service and no change in the API layer - not sure if there are concerns about what a VM could break if it updates its own metadata, but I guess we could also limit what values can be set. Thoughts ? Phil From: John Garbutt [mailto:john.garb...@citrix.com] Sent: 03 July 2012 16:41 To: Day, Phil; openstack@lists.launchpad.net (openstack@lists.launchpad.net) (openstack@lists.launchpad.net) Subject: RE: Setting VM passwords when not running on Xen This seemed to crop up quite a lot in different sessions at the Design summit. I am certainly interested in a standard way to inject information into VMs. What I think we need is a cross hypervisor two-way guest communication channel that is fairly transparent to the user of that VM (i.e. ideally not a network connection). If I understand things correctly, we currently have these setup ideas: * Config Drive (not supported by XenAPI, but not a two way transport) * Cloud-Init / Metadata service (depends on DHCP(?), and not a two-way transport) But to set the password, we ideally want two way communication. We currently have these: * XenAPI guest plugin (XenServer specific, uses XenStore, but two way, no networking assumed ) * Serial port (used by http://wiki.libvirt.org/page/Qemu_guest_agent but not supported on XenServer) I like the idea of building a common interface (maybe write out to a known file system location) for the above two hypervisor specific mechanisms. The agent should be able to pick which mechanism works. Then on top of that, we could write a common agent that can be shared for all the different hypervisors. You could also fallback to the metadata service and config drive when no two way communication is available. I would love this Guest Agent to be an OpenStack project that can then be up streamed into many Linux distribution cloud images. Sadly, I don't have any time to work on this right now, but hopefully that will change in the near future. Cheers, John From: openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.netmailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net]mailto:[mailto:openstack-bounces+john.garbutt=eu.citrix@lists.launchpad.net] On Behalf Of Day, Phil Sent: 03 July 2012 3:07 To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) Subject: [Openstack] Setting VM passwords when not running on Xen Hi Folks, Is anyone else looking at how to support images that need a password rather than an ssh key (windows) on hypervisors that don't support set_admin_password (e.g. libvirt) ? Thanks Phil ___ 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] Time for a UK Openstack User Group meeting ?
Sounds good. I am up in Cambridge, so London works well for me. There are some meetup groups already, but nothing has been arranged, AFIK: http://www.meetup.com/Openstack-London/ http://www.meetup.com/openstack-uk/ Cheers, 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 Daniel P. Berrange Sent: Wednesday, July 4, 2012 8:14 PM To: Day, Phil Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net) (openstack@lists.launchpad.net) Subject: Re: [Openstack] Time for a UK Openstack User Group meeting ? On Wed, Jul 04, 2012 at 04:38:28PM +0100, Day, Phil wrote: Hi All, I'm thinking it's about time we had an OpenStack User Group meeting in the UK , and would be interested in hearing from anyone interested in attending, presenting, helping to organise, etc. I can do presentations about libvirt with a focus on KVM/LXC, and SELinux / security / sandboxing. I could probably manage something semi-intelligent about libvirt integration with Nova too, depending on intended audience interests London would seem the obvious choice, but we could also host here in HP Bristol if that works for people. I work in London, so if something was organized in the area I was free, I'd hope to attend. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ 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] Setting VM passwords when not running on Xen
That should be fine, as long as you don't mind a reboot if you want to change your password. That sounds reasonable enough, given the complexity of the alternative. Cheers, 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 Thierry Carrez Sent: Wednesday, July 4, 2012 10:33 AM To: openstack@lists.launchpad.net Subject: Re: [Openstack] Setting VM passwords when not running on Xen Scott Moser wrote: Is it for some reason not possible to have code that runs on first instance boot that reads the metadata service (or config drive) and sets the password appropriately? I see no reason why you could not. Windows scripting supported both running scripts at boot and setting user passwords last time I looked :) Using the same mechanism as cloud-init on Linux sounds a lot better to me than a Windows-only hack to enable server-side generation and two-way communication... -- 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 ___ 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] Setting VM passwords when not running on Xen
From: Scott Moser [mailto:ssmos...@gmail.com] On Behalf Of Scott Moser * Cloud-Init / Metadata service (depends on DHCP(?), and not a two-way transport) cloud-init does not require dhcp. It explicitly supports the passing of network interface definitions into it in Ubuntu 12.04. Ie, config-drive with static networking passed in works as it should. Sorry, I was just thinking about relying on DHCP to get the IP address, then using the Metadata Service, on XenAPI were config drive has not been implemented. Its 2012, do we really need to design for the case where IP is broken or not available? I was only really worried about the case of Flat without DHCP that config drive can address. Given things are going this way, I guess that increases the need of implementing config drive for XenAPI. Has anyone already got plans to implement that in Folsom? I might try to find someone in our Citrix team to take a look at implementing that. Cheers, 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
Re: [Openstack] QA for Live Migration
Hi, There are currently no tests for live migration. I imagine that the reason is because there is very poor documentation on the os-migrateLive API extension. I'd be happy to help you in writing the tests. Cool, thanks. I'd love some help in identifying some documentation ... we need to know the contractual state changes that need to be asserted in the Tempest tests. Additionally, I'd like to point out that there is a lot of confusion as to what is different between the standard Compute API call to migrate a server (POST /servers/SERVER_ID/action with 'migrate' action...) and the live migration extension. ... +1 Renuka and I are looking at proposing a blueprint to try and sort out some of this confusion. I think this is the current situation: - historically XenAPI had migrate, Libvirt had live migrate - But by end of Folsom we should have both having both - Live migration was originally only nova-manage controlled - Migrate is useful, but requires things like passwordless ssh - We could re-implement migrate as snapshot and restart - Above is also true for Resize - But there may be billing implications for the above changes - Live-migrate is more useful than migrate - But live-migrate not always possible (miss matched CPUs, etc) - Ideally we would have single migrate/live-migrate API Possible first steps for Folsom: - Extend the migrate API to support a live and live-block migration options - Maybe add live with fallback to non-live option - Maybe above should be the default, add a non-live option - Fully document the expanded migrate API for Folsom Does this sound reasonable? Cheers, 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
Re: [Openstack] QA for Live Migration
- historically XenAPI had migrate, Libvirt had live migrate - But by end of Folsom we should have both having both Yes, but what is the difference between the two? Got you. I think this is right: Migration: - shutdown the VM - move current disk to the destination - start VM - user sees reboot, and sees downtime - resize is very similar, just starts as different flavour Live-migration: - snapshot running state - copy memory + CPU state to other machine - start - user sees VM pause for a small amount of time - assumes VM is on shared storage, so disks are not moved Block-migration and live-migration: - as above, but disk needs to be copied Live migration can only happen when the source and destination CPU matches Hopefully my comments make more sense now? - Live migration was originally only nova-manage controlled - Migrate is useful, but requires things like passwordless ssh - We could re-implement migrate as snapshot and restart This seems entirely reasonable. - Above is also true for Resize That is actually how it already happens, with the CONFIRM_RESIZE state acting as the quiescence point for the operation. I thought it just did a copy and left the old image on the previous machine, but that might just be XenAPI. I was more thinking upload the snapshot into glance as a private image, rather than do a 'behind the scenes' copy between hypervisors. - But live-migrate not always possible (miss matched CPUs, etc) - Ideally we would have single migrate/live-migrate API This would be my preference. The way it stands today is entirely confusing. Cool ___ 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] QA for Live Migration
I pinged Anne Gentle about the docs missing this (apparently
core) API server action and she will be working to get this added to the
current docs -- especially since novaclient already has support for it...
Good good.
The more I think about it, I believe a single migration API would be simplest,
with the ability to specify options for the migration.
Something like:
POST /servers/SERVER_ID/action
{
'action': 'migrate',
'migrate_options':
{
'live': true,
'no_live_fallback': true,
'migrate_disks':
{
DISK_UUID1, ...
}
}
}
With the options being fairly self-explanatory other than the
'no_live_fallback': true being used to indicate the caller wishes to fallback
on a stop/move/start migration if shared disk (or a hypervisor restriction or
non-matching CPU restriction) prohibits the live migration.
+1
This is exactly what I was attempting to propose in the blueprint Renuka was
planning to write and work on.
Cheers,
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
Re: [Openstack] [CHEF] Clarification on osops/chef-repo/roles/nova-compute.rb
I should be able to help out getting these working with XenServer/XCP, if that is useful to anyone? Curiosity leads me to ask: Where do I find the puppet equivalent these days? Cheers, 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 Matt Ray Sent: 10 July 2012 10:23 To: Jay Pipes Cc: openstack@lists.launchpad.net; Nati Ueno Subject: Re: [Openstack] [CHEF] Clarification on osops/chef- repo/roles/nova-compute.rb Bluntness appreciated, this process is already in motion. http://opscode.com/openstack was launched 2 weeks ago and I promptly left for conferences and vacation. I am consolidating GitHub repos here: https://github.com/opscode/openstack-chef-repo https://github.com/opscode-cookbooks/nova https://github.com/opscode-cookbooks/glance https://github.com/opscode-cookbooks/horizon https://github.com/opscode-cookbooks/keystone https://github.com/opscode-cookbooks/swift Work is being done in my own repos until it's ready for an initial release, which will include a Getting Started with Chef and OpenStack document. https://github.com/mattray/ I'm working with quite a few folks already, Rackspace, Dell, DreamHost and others and Intel is sponsoring this work. Jay and I chatted a bit in IRC, we're quite aligned in how we plan on working this and the goal will be to get github.com/openstack/chef-repo gated with Gerrit and CI and pulling from Opscode's repos soon. Please feel free to join the discussion on our new mailing list focused on this effort here: http://groups.google.com/group/opscode-chef-openstack And an IRC channel: #openstack-chef on irc.freenode.net Thanks, Matt Ray Senior Technical Evangelist | Opscode Inc. m...@opscode.com | (512) 731-2218 Twitter, IRC, GitHub: mattray On Tue, Jul 10, 2012 at 11:25 AM, Jay Pipes jaypi...@gmail.com wrote: Apologies in advance for my blunt and somewhat dour response, Matt. I'm not singling you out at all, and I know you've tried your best to get the various Chef stakeholders to work together. Also apologies for top-posting, but there's not a whole lot of use inline posting this. tl;dr - We need to stop the needless fracturing of the operational knowledge of the Chef community and try working as a team towards some common goals instead of creating fork after fork of repos of Chef cookbooks. There is a ton of wasted effort in this area. Proposal: * Get our act together and treat Chef repos (and puppet/juju/whatever) as we do other OpenStack core and supporting projects -- use Gerrit, use a CI gating system, do real code reviews on it, and in general treat them as a supporting OpenStack project * Mark ALL Chef repos that are not currently maintained with an OBSELETE marker and/or DELETE the repo on Github * Consolidate all *cookbooks* into a repository in github.com/openstack/chef-repo * Use git submodules to manage cookbooks that are upstreamed in github.com/opscode/ that have little to no changes in them * Actually fix the documentation of the dang cookbooks -- right now, half of them include the documentation from the memcache cookbook, as they were lazily copy-pasted around, or the standard example doc that is created when using something like knife. * Put as much variation in deployment philosophy into *roles* and attribute overrides/defaults More/Rant/Details - Maybe it's just the open source developer in me, but I don't understand why there is such an aversion to coordination in the deployment/ops community around the scripts and deployment cookbooks/modules/charms/whatever. Is it that everyone has a different idea of what is best? Is it because deployers/ops folks think that coordinating with other contributors is too time-consuming? Is it because the chef repos are not controlled in the same way as, say, devstack or the core projects, with an automated patch queue manager and code review system that actually encourages debate over patches? A combination of all of the above? Over the last 2 years, I've worked at 3 companies in the OpenStack ecosystem. All three companies had their own repos of Chef cookbooks (still do to this day). 50-60% of the content of these cookbooks is identical. 10-20% of the content of these cookbooks is different -- but only slightly or cosmetically. And a good portion of the remaining 20-40% are differences that are incorrectly (IMHO) placed in the cookbooks and recipes instead of where they should be: in roles and environments, with cookbooks created that deal with variations in deployments with attributes and the occasional if/else block. In trying to determine the appropriate Chef repo to use for the TryStack project, we found the following repo: https://github.com/osops/chef-repo to
Re: [Openstack] What is the most commonly used Hypervisor and toolset combination?
To my knowledge, if you want to use Xen, using XCP or XenServer (i.e. using XenAPI driver) is the way to go. If you look at the contributions to the drivers, you can have a good guess at who is using them. I know people are going into production on XenAPI, not heard about Xen+libvirt in production. Having said this, I have seen some fixes to Folsom around Xen + libvirt, I think from SUSE? I work for Citrix on the XenAPI driver, so I am not exactly impartial. My testing is certainly running XenServer 6.0.2 (+ development builds of the next release) with the XenAPI driver. If you have any problems getting going with XenAPI, I am happy to help. Preferably through the ML to share the knowledge. I am currently doing some work improving the documentation. I have got a few patches in already, hopefully I get around to adding some more very soon. I hope that helps, 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 Huang Zhiteng Sent: Wednesday, July 18, 2012 5:47 AM To: Wang Li Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] What is the most commonly used Hypervisor and toolset combination? I'd suggest: CentOS 6.3/RHEL 6.3 + KVM + OpenStack Essex, you may replace CentOS with Ubuntu/Fedora if you want. If you are big fan of Xen or having huge legacy PV VMs, you might want to try XenServer + XenAPI + OpenStack Essex. On Wed, Jul 18, 2012 at 12:20 PM, Wang Li fox...@gmail.com wrote: hi, all My team is trying to deploy openstack in production environment. We tried to get libvirt + xen 3.4.3 + CenOS 5.4 + Openstack 2012.2 working, but encountered lots of issues. We already have thousands of virtual machines running in production, and that's why we are trying Xen 3.4.3 and CentOS 5.4. After we solved one problem, there comes more, which is very annoying So, my question is: In real production environment using Openstack, what's the most commonly used Hypervisor and toolset? We hope to deploy Openstack quickly, and stay in main stream. Thank u. Regards Wang Li ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Regards Huang Zhiteng ___ 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] What are you XenAPI deployment pains?
From: Kiall Mac Innes Anyway! DevStack is Ubuntu+KVM (by default), All the per commit testing is Ubuntu+QEMU/KVM.. The docs are best for Ubuntu+KVM. If you're doing your first install - I would suggest sticking to that. Once you have that all figured out, moving to something less documented like XenAPI should be much much easier. Hopefully the docs are getting better. DevStack should do the XenAPI deploy for you. Granted getting your head around the networking isn't easy, but the docs should help with that now. Any thoughts on the best things to tackle next are gratefully received. Really interested in what the sticking points are when people trying using XenAPI. I was thinking about producing an ISO so you can install that to get XenServer/XCP + DevStack in one shot. Does that sound useful? Cheers, 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
Re: [Openstack] Solaris Fails as Guest VM
You might be able to use XenServer/XCP. It's not supported as such, and I have never tried it, but these people seem to have: http://360is.blogspot.co.uk/2010/03/paravirtualized-opensolaris-solaris-on.html -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 Narayan Desai Sent: Thursday, July 19, 2012 7:28 PM To: Joshua Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Solaris Fails as Guest VM That is worth a shot. I haven't played with Xen personally, so I don't know what would be involved, but iirc there was a solaris xen port. -nld On Thu, Jul 19, 2012 at 1:07 PM, Joshua j...@root.bz wrote: Would xen as the hypervisor be able to boot the solaris vm? On Thu, Jul 19, 2012 at 11:35 AM, Joshua j...@root.bz wrote: Thanks for the updates, it hurts to hear that solaris is not support. I was hoping I could nest the vm, but even that has been removed as a feature. Anyone have any workarounds on getting solaris running within openstack. On Wed, Jul 18, 2012 at 6:48 PM, Narayan Desai narayan.de...@gmail.com wrote: On Wed, Jul 18, 2012 at 7:38 PM, Michael March mma...@gmail.com wrote: I don't follow Solaris that closely but I vaguely remember the Joyent folks ported all of KVM to Solaris, right? Or am I just missing the whole point here? They did, and it is a fairly impressive piece of work. Their focus (as a hosting provider) was running kvm virtual machines in a illumos host. That support is completely separate from the guest drivers to make virtio work for block and network devices. afaict, network device support is complete, but block device support isn't finished yet. This means you can't run illumos/solaris as a guest using kvm with virtio. -nld ___ 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] Default reply to behavior for mailing list
Thierry Carrez wrote: Daniel P. Berrange wrote: People never agree on the best setting. Asking for this reply-to setting to be changed is merely shifting the pain away from one set of users (which includes you) onto other set of users (which includes me). There's no net gain here. Just shifting the pain. +1 +1 Especially since Launchpad-based MLs don't give us the option to change that behavior anyway :) Sometimes the best feature of a system is the lack of certain features :-) Cheers, 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
Re: [Openstack] [nova] Disk attachment consistency
You can see what XenAPI exposes here: http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/api/?c=VBD I think the only thing you can influence when plugging in the disk is the “userdevice” which is the disk position: 0,1,2… When you have attached the disk you can find out the “device” name, such as /dev/xvda I don't know about Xen with libvirt. But from the previous discussion it seems using the disk position would also work with KVM? It seems disk position is also suitably OS agnostic, but I may have missed something there. For backwards compatibility, we could make a best effort of translating the specified device name to a position. But as mentioned already, it seems fraught with danger in the general case. I like the idea of an extra field to help report to the user what the likely device name is, if available. It would allow us to spot when the above guessing did not gone the way we had hoped. Related to this, there is a limitation in Xen (a limitation in the blkbk/blkfrnt protocol I am told) that means you can't cancel the operation of removing a disk from a VM. So if the disk is in use, it may return with an exception saying the disk is in-use, but as soon as the disk can be released, it will be removed anyway. Currently, nova isn't very good at expressing to the user that this is what is happening: https://bugs.launchpad.net/nova/+bug/1030108 Cheers, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Wangpan Sent: 15 August 2012 5:11 To: Vishvananda Ishaya Cc: openstack Subject: Re: [Openstack] [nova] Disk attachment consistency This is definitely another solution, although it seems less usable than the device serial number which can be an arbitrary string. If this works for xen though, that would be a plus. Vish I don't have a Xen hypervisor in hand, so anybody else can try it on Xen ? 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] [nova] Disk attachment consistency
From: Daniel P. Berrange [mailto:berra...@redhat.com]
On Wed, Aug 15, 2012 at 03:49:45PM +0100, John Garbutt wrote:
You can see what XenAPI exposes here:
http://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/api/?c=VBD
I think the only thing you can influence when plugging in the disk is the
“userdevice”
which is the disk position: 0,1,2… When you have attached the disk
you can find out the “device” name, such as /dev/xvda
I don't know about Xen with libvirt. But from the previous discussion
it seems using the disk position would also work with KVM?
No, this doesn't really work in general. Virtio disks get assigned SCSI device
numbers on a first-come first served basis. In the configuration you only have
control over the PCI device slot/function. You might assume that your disks
are
probed in PCI device order, and thus get SCSI device numbers in that same
order.
This is not really safe though. Further more if the guest has any other kinds
of
devices, eg perhaps they logged into an iSCSI target, then all bets are off
for
what SCSI device you get assigned.
All the host can safely say is
- Virtio-blk disks get PCI address domain:bus:slot:function
- Virtio-SCSI disks get SCSI address A.B.C.D
- Disks have an unique serial string ZZZ
As a guest OS admin you can use this info get reliable disk names in
/dev/disk/by-{path,id}.
Doh, I guess my plan doesn't work then. After checking, apparently the same
problem is also present with how Xen deals with exposing the position to the
guest VM.
Relying on /dev/sdXXX is doomed to failure in the long term, even on bare
metal, and should be avoided wherever possible.
I agree, long term, this is not the way forward. I was just thinking in terms
of backwards compatibility.
If your disk has a filesystem on it, you can also get a unique UUID and /or
filesystem label, which means you can refer to the device from /dev/disk/by-
{uuid,label} too.
That sounds the interesting for those attaching volumes that have a file system
on it. Would it be reasonable to make this the best practice way for users to
discover where the volume has been attached?
Maybe we should simply leave nova to report where the disk has been attached?
XenAPI driver can simply attach in the next available slot, and report back
what it can about the device location. Sounds like the libvirt driver could do
the same?
We could document the current device (or whatever we call it) as a driver
specific hint. Although this doesn't seem very satisfying.
Cheers,
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
Re: [Openstack] What is the most commonly used Hypervisor and toolset combination?
For the record, we (i.e. Citrix) are certainly looking at exposing the GPU pass-through support in XCP (a Xen.org project that includes XenAPI) and XenServer in the Grizzly timeframe. I now sit next to a lot of the Citrix Xen.org and XenServer people. We are all based in Cambridge, UK. However, you will probably get answers just as quickly by asking on the Xen mailing lists. Thanks, John -Original Message- From: John Paul Walters [mailto:jwalt...@isi.edu] Sent: Thursday, August 16, 2012 4:11 PM To: Boris-Michel Deschenes Cc: Jim Fehlig; John Garbutt; openstack@lists.launchpad.net Subject: Re: [Openstack] What is the most commonly used Hypervisor and toolset combination? Hi Boris, We have GPU passthrough working with NVIDIA GPUs in Xen 4.1.2, if I recall correctly. We don't yet have a stable Xen + Libvirt installation working, but we're looking at it. Perhaps it would be worth collaborating since it sounds like this could be a win for both of us. best, JP On Aug 16, 2012, at 9:31 AM, Boris-Michel Deschenes wrote: That would be great Jim, I've built a cloud that uses CentOS+libvirt+Xen 4.1.3 to do GPU passthrough and I just love to be able to use libvirt with Xen, this setup makes a lot of sense to me since our main, bigger cloud is the standard libvirt+KVM, using libvirt across the board is great for us. I'm following your work closely, the GPU cloud is still using libvirt+xend but when I move to Xen 4.2 my understanding is that I will need libvirt+xl (xenlight) so I guess there's still some work to be done in libvirt there... The reason I want to move to Xen 4.2 is the GPU passthrough of NVIDIA GPUs... currently, with Xen 4.1.3, I successfully passthrough ATI GPUs only. Boris -Message d'origine- De : openstack-bounces+boris-michel.deschenes=ubisoft.com@lists.launchpad.n et [mailto:openstack-bounces+boris-michel.deschenes=ubisoft@lists.lau nchpad.net] De la part de Jim Fehlig Envoyé : 18 juillet 2012 17:56 À : John Garbutt Cc : openstack@lists.launchpad.net Objet : Re: [Openstack] What is the most commonly used Hypervisor and toolset combination? John Garbutt wrote: To my knowledge, if you want to use Xen, using XCP or XenServer (i.e. using XenAPI driver) is the way to go. If you look at the contributions to the drivers, you can have a good guess at who is using them. I know people are going into production on XenAPI, not heard about Xen+libvirt in production. Having said this, I have seen some fixes to Folsom around Xen + libvirt, I think from SUSE? Yes, I'm slowly working on improving support for xen.org Xen via the libvirt driver and hope to have these improvements in for the Folsom release. Regards, Jim ___ 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] boot image + glance connection failed
Hi, Sorry for the slow response, I have been out of email contact. You are best running all the services in a DomU, in the single server case. You only need the xenapi plugins running on Dom0, assuming you are not running Quantum. When you add the second machine, you only need compute, network (and console I think) Can you please point me to the bit of the Essex install guide that tells you to run the other services in Dom0 so I can get that updated to stop any further confusion? If you want to get something running quickly, I recommend trying DevStack. You can then using that as a template for a more production focused setup. I hope that helps, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Afef MDHAFFAR Sent: Tuesday, September 4, 2012 3:03 PM To: openstack@lists.launchpad.net Subject: [Openstack] boot image + glance connection failed Hi all, I got these errors when trying to boot an image. There are related to glance. I install openstack on an Ubuntu 12.04 (with Xen Server). Dom0 runs nova-api, glance service, nova-scheduler, nova-cert and nova-console. DomU runs nova-compute and nova-network. Do I have to install glance service on DomU Here are log errors (picked from nova-compute.log). 2012-09-04 15:54:40 ERROR nova.image.glance [req-a516f35c-4207-4180-86b9-3a85687067b7 cf8971efd8934844b559d26e238506cc 141d12e2431f47a5bf77f90da4800960] Connection error contacting glance server, retrying 2012-09-04 15:54:40 TRACE nova.image.glance Traceback (most recent call last): 2012-09-04 15:54:40 TRACE nova.image.glance File /usr/lib/python2.7/dist-packages/nova/image/glance.py, line 145, in _call_retry 2012-09-04 15:54:40 TRACE nova.image.glance return getattr(client, name)(*args, **kwargs) 2012-09-04 15:54:40 TRACE nova.image.glance File /usr/lib/python2.7/dist-packages/glance/client.py, line 101, in get_image_meta 2012-09-04 15:54:40 TRACE nova.image.glance res = self.do_request(HEAD, /images/%s % image_id) 2012-09-04 15:54:40 TRACE nova.image.glance File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 58, in wrapped 2012-09-04 15:54:40 TRACE nova.image.glance return func(self, *args, **kwargs) 2012-09-04 15:54:40 TRACE nova.image.glance File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 420, in do_request 2012-09-04 15:54:40 TRACE nova.image.glance headers=headers) 2012-09-04 15:54:40 TRACE nova.image.glance File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 75, in wrapped 2012-09-04 15:54:40 TRACE nova.image.glance return func(self, method, url, body, headers) 2012-09-04 15:54:40 TRACE nova.image.glance File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 562, in _do_request 2012-09-04 15:54:40 TRACE nova.image.glance raise exception.ClientConnectionError(e) 2012-09-04 15:54:40 TRACE nova.image.glance ClientConnectionError: There was an error connecting to a server 2012-09-04 15:54:40 TRACE nova.image.glance Details: [Errno 111] ECONNREFUSED 2012-09-04 15:54:40 TRACE nova.image.glance 2012-09-04 15:54:41 ERROR nova.rpc.amqp [req-a516f35c-4207-4180-86b9-3a85687067b7 cf8971efd8934844b559d26e238506cc 141d12e2431f47a5bf77f90da4800960] Exception during message handling 2012-09-04 15:54:41 TRACE nova.rpc.amqp Traceback (most recent call last): 2012-09-04 15:54:41 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py, line 253, in _process_data 2012-09-04 15:54:41 TRACE nova.rpc.amqp rval = node_func(context=ctxt, **node_args) 2012-09-04 15:54:41 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/exception.py, line 114, in wrapped 2012-09-04 15:54:41 TRACE nova.rpc.amqp return f(*args, **kw) 2012-09-04 15:54:41 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 183, in decorated_function 2012-09-04 15:54:41 TRACE nova.rpc.amqp sys.exc_info()) 2012-09-04 15:54:41 TRACE nova.rpc.amqp File /usr/lib/python2.7/contextlib.py, line 24, in __exit__ 2012-09-04 15:54:41 TRACE nova.rpc.amqp self.gen.next() 2012-09-04 15:54:41 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 177, in decorated_function 2012-09-04 15:54:41 TRACE nova.rpc.amqp return function(self, context, instance_uuid, *args, **kwargs) 2012-09-04 15:54:41 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 657, in run_instance 2012-09-04 15:54:41 TRACE nova.rpc.amqp do_run_instance() 2012-09-04 15:54:41 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/utils.py, line 945, in inner 2012-09-04 15:54:41 TRACE nova.rpc.amqp retval = f(*args, **kwargs) 2012-09-04 15:54:41 TRACE nova.rpc.amqp File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 656, in do_run_instance 2012-09-04 15:54:41
Re: [Openstack] boot image + glance connection failed
Hi, The docs are mostly talking about using OpenStack with XenServer (connecting via XenAPI), not using OpenStack with Xen+libvirt. If you want to use Ubuntu as your host OS, you can use the xcp-xapi package to install get XenAPI running, or you can install XenServer on your system. In both cases you then run all the nova services in a domU, which can be Ubuntu. If you want to stick with Xen+libvirt, there is the SUSE distro that might help you. I believe you want to deploy all the services in Dom0 when you are using Xen+libvirt. I don't know how well it will work when you run them in an unprivileged VM, I haven't tried libvirt+Xen+OpenStack. Thanks, John From: Afef MDHAFFAR [mailto:afef.mdhaf...@gmail.com] Sent: Thursday, September 6, 2012 12:41 PM To: John Garbutt Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] boot image + glance connection failed Hi, Thanks a lot for your answer. Here is the link of the tutorial that I used to install OpenStack: http://docs.openstack.org/essex/openstack-compute/install/apt/openstack-install-guide-essex.pdf Page 41 shows an overview of the architecture of OpenStack with Xen. Actually, I am trying to use libvirt to connect to the hypervisor. I modified a little the code of openstack to make the connection to the hypervisor from a para virtualized domU possible (just modified the url to let make a remote connection). Regards, Afef 2012/9/5 John Garbutt john.garb...@citrix.commailto:john.garb...@citrix.com Hi, Sorry for the slow response, I have been out of email contact. You are best running all the services in a DomU, in the single server case. You only need the xenapi plugins running on Dom0, assuming you are not running Quantum. When you add the second machine, you only need compute, network (and console I think) Can you please point me to the bit of the Essex install guide that tells you to run the other services in Dom0 so I can get that updated to stop any further confusion? If you want to get something running quickly, I recommend trying DevStack. You can then using that as a template for a more production focused setup. I hope that helps, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.netmailto:citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbuttmailto:openstack-bounces%2Bjohn.garbutt=citrix@lists.launchpad.netmailto:citrix@lists.launchpad.net] On Behalf Of Afef MDHAFFAR Sent: Tuesday, September 4, 2012 3:03 PM To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: [Openstack] boot image + glance connection failed Hi all, I got these errors when trying to boot an image. There are related to glance. I install openstack on an Ubuntu 12.04 (with Xen Server). Dom0 runs nova-api, glance service, nova-scheduler, nova-cert and nova-console. DomU runs nova-compute and nova-network. Do I have to install glance service on DomU Here are log errors (picked from nova-compute.log). 2012-09-04 15:54:40 ERROR nova.image.glance [req-a516f35c-4207-4180-86b9-3a85687067b7 cf8971efd8934844b559d26e238506cc 141d12e2431f47a5bf77f90da4800960] Connection error contacting glance server, retrying 2012-09-04 15:54:40 TRACE nova.image.glance Traceback (most recent call last): 2012-09-04 15:54:40 TRACE nova.image.glance File /usr/lib/python2.7/dist-packages/nova/image/glance.py, line 145, in _call_retry 2012-09-04 15:54:40 TRACE nova.image.glance return getattr(client, name)(*args, **kwargs) 2012-09-04 15:54:40 TRACE nova.image.glance File /usr/lib/python2.7/dist-packages/glance/client.py, line 101, in get_image_meta 2012-09-04 15:54:40 TRACE nova.image.glance res = self.do_request(HEAD, /images/%s % image_id) 2012-09-04 15:54:40 TRACE nova.image.glance File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 58, in wrapped 2012-09-04 15:54:40 TRACE nova.image.glance return func(self, *args, **kwargs) 2012-09-04 15:54:40 TRACE nova.image.glance File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 420, in do_request 2012-09-04 15:54:40 TRACE nova.image.glance headers=headers) 2012-09-04 15:54:40 TRACE nova.image.glance File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 75, in wrapped 2012-09-04 15:54:40 TRACE nova.image.glance return func(self, method, url, body, headers) 2012-09-04 15:54:40 TRACE nova.image.glance File /usr/lib/python2.7/dist-packages/glance/common/client.py, line 562, in _do_request 2012-09-04 15:54:40 TRACE nova.image.glance raise exception.ClientConnectionError(e) 2012-09-04 15:54:40 TRACE nova.image.glance ClientConnectionError: There was an error connecting to a server 2012-09-04 15:54:40 TRACE nova.image.glance Details: [Errno 111] ECONNREFUSED 2012-09-04 15:54:40 TRACE nova.image.glance 2012-09-04 15:54:41 ERROR nova.rpc.amqp [req-a516f35c-4207-4180-86b9-3a85687067b7 cf8971efd8934844b559d26e238506cc 141d12e2431f47a5bf77f90da4800960] Exception
Re: [Openstack] Generalsied host aggregates in Folsom
I thought it could be used for anything on the XenAPI side too, although I have not tried it that way yet. We have posted some docs on the XenAPI side. Around the pooled live migration that uses this anyway: https://review.openstack.org/#/c/13202/ Cheers, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Joe Gordon Sent: Wednesday, September 19, 2012 11:45 PM To: Day, Phil Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net) (openstack@lists.launchpad.net) Subject: Re: [Openstack] Generalsied host aggregates in Folsom On Wed, Sep 19, 2012 at 1:14 PM, Day, Phil philip@hp.commailto:philip@hp.com wrote: Thanks Joe, I was anticipating something more complex to be able to say when an aggregate should or shouldn't be linked to the hypevisor and overlooked the obvious. So just to make sure I've got it - on libvirt systems an aggregate can be used for anything (because of the NoOp in the driver), but on xen systems it's still liked to the hypervisor pools ? Libvirt can be used for anything. And Xen can be a xen hypervisor pool or anything depending on the aggregate metadata (https://github.com/openstack/nova/blob/master/nova/virt/xenapi/pool.py#L80 https://github.com/openstack/nova/blob/master/nova/virt/xenapi/pool_states.py) Thanks Phil From: Joe Gordon [mailto:j...@cloudscaling.commailto:j...@cloudscaling.com] Sent: 19 September 2012 19:02 To: Day, Phil Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) Subject: Re: [Openstack] Generalsied host aggregates in Folsom On Wed, Sep 19, 2012 at 10:18 AM, Day, Phil philip@hp.commailto:philip@hp.com wrote: Hi Folks, Trying to catch-up (I'm thinking of changing my middle name to catch-up :) ) with the generalisation of host aggregates - and looking at the code it looks to me as if the chain for adding a host to an aggregate still ends up calling the virt layer api/openstack/compute/contrib/aggregates/AggregateController/action() compute/api/AggregateAPI/add_host_to_aggregate() RPC compute/manager/add_aggregate_host() virt/add_to_aggregate() I thought the change was to be able to create aggregates that can be linked to a hypervisor concept, but could also just be a way of tagging hosts into pools for other scheduler reasons - am I missing somethign ? The RPC component is there to ensure XenAPI still works. In the libvirt driver, add_to_aggregate() is a noop. So you can create an aggregate that can be linked to a hypervisor but also as a way to tag hosts Thanks, Phil ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto: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] Generalsied host aggregates in Folsom
Sorry got confused with indentation. +1 to Joe's comment. From: John Garbutt Sent: Thursday, September 20, 2012 5:30 PM To: 'Joe Gordon'; Day, Phil Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net) (openstack@lists.launchpad.net) Subject: RE: [Openstack] Generalsied host aggregates in Folsom I thought it could be used for anything on the XenAPI side too, although I have not tried it that way yet. We have posted some docs on the XenAPI side. Around the pooled live migration that uses this anyway: https://review.openstack.org/#/c/13202/ Cheers, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.netmailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net]mailto:[mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Joe Gordon Sent: Wednesday, September 19, 2012 11:45 PM To: Day, Phil Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) Subject: Re: [Openstack] Generalsied host aggregates in Folsom On Wed, Sep 19, 2012 at 1:14 PM, Day, Phil philip@hp.commailto:philip@hp.com wrote: Thanks Joe, I was anticipating something more complex to be able to say when an aggregate should or shouldn't be linked to the hypevisor and overlooked the obvious. So just to make sure I've got it - on libvirt systems an aggregate can be used for anything (because of the NoOp in the driver), but on xen systems it's still liked to the hypervisor pools ? Libvirt can be used for anything. And Xen can be a xen hypervisor pool or anything depending on the aggregate metadata (https://github.com/openstack/nova/blob/master/nova/virt/xenapi/pool.py#L80 https://github.com/openstack/nova/blob/master/nova/virt/xenapi/pool_states.py) Thanks Phil From: Joe Gordon [mailto:j...@cloudscaling.commailto:j...@cloudscaling.com] Sent: 19 September 2012 19:02 To: Day, Phil Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) (openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net) Subject: Re: [Openstack] Generalsied host aggregates in Folsom On Wed, Sep 19, 2012 at 10:18 AM, Day, Phil philip@hp.commailto:philip@hp.com wrote: Hi Folks, Trying to catch-up (I'm thinking of changing my middle name to catch-up :) ) with the generalisation of host aggregates - and looking at the code it looks to me as if the chain for adding a host to an aggregate still ends up calling the virt layer api/openstack/compute/contrib/aggregates/AggregateController/action() compute/api/AggregateAPI/add_host_to_aggregate() RPC compute/manager/add_aggregate_host() virt/add_to_aggregate() I thought the change was to be able to create aggregates that can be linked to a hypervisor concept, but could also just be a way of tagging hosts into pools for other scheduler reasons - am I missing somethign ? The RPC component is there to ensure XenAPI still works. In the libvirt driver, add_to_aggregate() is a noop. So you can create an aggregate that can be linked to a hypervisor but also as a way to tag hosts Thanks, Phil ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto: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 -- xcp - devstack
Hi, I suspect the problem is that your VM was unable to access the internet on the VM's interface specified by: HOST_IP_IFACE You can see how the Ubuntu install parameters are specified here: https://github.com/openstack-dev/devstack/blob/master/tools/xen/scripts/install_ubuntu_template.sh#L53 What version of XCP are you running? Are you using any tools to connect to the console of the VM? I hope that helps, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Afef MDHAFFAR Sent: Wednesday, September 26, 2012 9:39 AM To: openstack@lists.launchpad.net Subject: Re: [Openstack] openstack -- xcp - devstack Actually, when I deeply looked on the problem, I found that there is no partition in the device that could be mapped by the kpartx command. Any ideas how to solve it? Thank you, Afef 2012/9/26 Afef MDHAFFAR afef.mdhaf...@gmail.commailto:afef.mdhaf...@gmail.com Hi all, I am trying to install openstack via devstack. I use Ubuntu Server 12.04 and XCP. I mainly followed this link : https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md. The execution of the script hangs in this state: + echo 'Waiting for DevStackOSDomU to finish installation...' Waiting for DevStackOSDomU to finish installation... + sleep 20 + true ++ xe_min vm-list name-label=DevStackOSDomU power-state=halted ++ local cmd=vm-list ++ shift ++ xe vm-list --minimal name-label=DevStackOSDomU power-state=halted + state= + '[' -n '' ']' *** I thought that installing DomU from the scratch could take time, and I waited more 1H and 30 min. Unfortunately, nothing happened. Then, I tried to shutdown the machine manually via : xe vm-shutdown name-label=DevStackOSDomU force=true. The script continues working, but it then exits while showing a mapping error : Failed to find mapping Would you please help to fix this problem? Thank you Best regards, Afef -- Afef MDHAFFAR http://www.redcad.org/members/mdhaffar/ ___ 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] Devstack -- fails to launch instance
OK, so XCP-XAPI install is not that well documented yet. There is at least one manual step to make the XenAPI plugins work. What you need to run, on your Dom0 is this: sudo mkdir -p /usr/etc I think it is simply not present because it is Ubuntu and not CentOS 5.x that you get with XenServer and the XCP ISO. Hope that helps, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Afef MDHAFFAR Sent: Tuesday, October 2, 2012 3:03 PM To: Bilel Msekni Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Devstack -- fails to launch instance Here is my localrc file: MYSQL_PASSWORD=password SERVICE_TOKEN=password ADMIN_PASSWORD=password SERVICE_PASSWORD= RABBIT_PASSWORD=password # This is the password for your guest (for both stack and root users) GUEST_PASSWORD=password # IMPORTANT: The following must be set to your dom0 root password! XENAPI_PASSWORD=password # Do not download the usual images yet! IMAGE_URLS= # Explicitly set virt driver here VIRT_DRIVER=xenserver # Explicitly set multi-host MULTI_HOST=1 # Give extra time for boot ACTIVE_TIMEOUT=45 # Interface on which you would like to access services HOST_IP_IFACE=eth3 # First time Ubuntu network install params NETINSTALLIP=dhcp NAMESERVERS=ip1 NETMASK=255.255.255.0 GATEWAY=ip1 PUB_IP=ip2 PUB_BR=xenbr0 PUB_DEV=eth0 #ENABLE_GI=false UBUNTU_INST_IP=dhcp UBUNTU_INST_NAMESERVERS= UBUNTU_INST_NETMASK= UBUNTU_INST_GATEWAY= UBUNTU_INST_ARCH=amd64 UBUNTU_INST_REPOSITORY=http://archive.ubuntu.net/ubuntu; UBUNTU_INST_LOCALE=en_US UBUNTU_INST_KEYBOARD=us 2012/10/2 Bilel Msekni ski...@hotmail.frmailto:ski...@hotmail.fr Le 02/10/2012 15:39, Afef MDHAFFAR a écrit : Hi all, I used devstack to install openstack on an ubuntu 12.04 with xcp. I followed this link: https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md The script installed almost everything. The dashboard is working and shows that all services are running. However, launching nova-manage service list shows that nova-compute is not working. I also was unable to launch an instance from the dashboard and command line. Here are errors shown by nova-compute. Is there any way to solve this problem? --- 2012-10-02 09:34:10 DEBUG nova.virt.xenapi.driver [-] Got exception: ['XENAPI_PLUGIN_FAILURE', 'host_data', 'IOError', [Errno 2] No such file or directory: '/usr/etc/xenhost.conf'] from (pid=4770) _unwrap_plugin_exceptions /opt/stack/nova/nova/virt/xenapi/driver.py:728 2012-10-02 09:34:10 ERROR nova.virt.xenapi.host [-] The call to host_data returned an error: ['XENAPI_PLUGIN_FAILURE', 'host_data', 'IOError', [Errno 2] No such file or directory: '/usr/etc/xenhost.conf']. Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/eventlet/hubs/poll.py, line 97, in wait readers.get(fileno, noop).cb(fileno) File /usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main result = function(*args, **kwargs) File /opt/stack/nova/nova/service.py, line 132, in run_server server.start() File /opt/stack/nova/nova/service.py, line 410, in start self.manager.update_available_resource(ctxt) File /opt/stack/nova/nova/compute/manager.py, line 2775, in update_available_resource self.resource_tracker.update_available_resource(context) File /opt/stack/nova/nova/utils.py, line 760, in inner retval = f(*args, **kwargs) File /opt/stack/nova/nova/compute/resource_tracker.py, line 366, in update_available_resource resources = self.driver.get_available_resource() File /opt/stack/nova/nova/virt/xenapi/driver.py, line 380, in get_available_resource host_stats = self.get_host_stats(refresh=True) File /opt/stack/nova/nova/virt/xenapi/driver.py, line 542, in get_host_stats return self.host_state.get_host_stats(refresh=refresh) File /opt/stack/nova/nova/virt/xenapi/driver.py, line 159, in host_state self._host_state = host.HostState(self._session) File /opt/stack/nova/nova/virt/xenapi/host.py, line 134, in __init__ self.update_status() File /opt/stack/nova/nova/virt/xenapi/host.py, line 162, in update_status data[disk_total] = total TypeError: 'str' object does not support item assignment Removing descriptor: 5 2012-10-02 09:34:11 CRITICAL nova [-] 'str' object does not support item assignment 2012-10-02 09:34:11 TRACE nova Traceback (most recent call last): 2012-10-02 09:34:11 TRACE nova File /usr/local/bin/nova-compute, line 7, in module 2012-10-02 09:34:11 TRACE nova execfile(__file__) 2012-10-02 09:34:11 TRACE nova File /opt/stack/nova/bin/nova-compute, line 48, in module 2012-10-02 09:34:11 TRACE nova service.wait() 2012-10-02 09:34:11 TRACE nova File /opt/stack/nova/nova/service.py, line 659, in wait 2012-10-02 09:34:11 TRACE nova _launcher.wait() 2012-10-02 09:34:11 TRACE nova File
Re: [Openstack] Devstack -- fails to launch instance
No problem, sorry you hit so many problems. This is very dependent on how you have configured your guest network and Floating IP addresses. I suspect if you have a machine on the same network and subnet as your VM, it will just work. If you could give the ifconfig details from your DomU, Dom0 and VM launched via dashboard, I should be able to help more. John From: Afef MDHAFFAR [mailto:afef.mdhaf...@gmail.com] Sent: Tuesday, October 2, 2012 5:11 PM To: John Garbutt Cc: Bilel Msekni; openstack@lists.launchpad.net Subject: Re: [Openstack] Devstack -- fails to launch instance Yes! that's solves the problem! Thanks a lot for your help. Now, I could launch an instance from the dashboard. It has an ip address. Unfortunately, I can ping and ssh this instance only from the privileged DomU. How can I let this instance accessible from all machines of my network? Thank you, Afef 2012/10/2 John Garbutt john.garb...@citrix.commailto:john.garb...@citrix.com OK, so XCP-XAPI install is not that well documented yet. There is at least one manual step to make the XenAPI plugins work. What you need to run, on your Dom0 is this: sudo mkdir -p /usr/etc I think it is simply not present because it is Ubuntu and not CentOS 5.x that you get with XenServer and the XCP ISO. Hope that helps, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.netmailto:citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbuttmailto:openstack-bounces%2Bjohn.garbutt=citrix@lists.launchpad.netmailto:citrix@lists.launchpad.net] On Behalf Of Afef MDHAFFAR Sent: Tuesday, October 2, 2012 3:03 PM To: Bilel Msekni Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Devstack -- fails to launch instance Here is my localrc file: MYSQL_PASSWORD=password SERVICE_TOKEN=password ADMIN_PASSWORD=password SERVICE_PASSWORD= RABBIT_PASSWORD=password # This is the password for your guest (for both stack and root users) GUEST_PASSWORD=password # IMPORTANT: The following must be set to your dom0 root password! XENAPI_PASSWORD=password # Do not download the usual images yet! IMAGE_URLS= # Explicitly set virt driver here VIRT_DRIVER=xenserver # Explicitly set multi-host MULTI_HOST=1 # Give extra time for boot ACTIVE_TIMEOUT=45 # Interface on which you would like to access services HOST_IP_IFACE=eth3 # First time Ubuntu network install params NETINSTALLIP=dhcp NAMESERVERS=ip1 NETMASK=255.255.255.0 GATEWAY=ip1 PUB_IP=ip2 PUB_BR=xenbr0 PUB_DEV=eth0 #ENABLE_GI=false UBUNTU_INST_IP=dhcp UBUNTU_INST_NAMESERVERS= UBUNTU_INST_NETMASK= UBUNTU_INST_GATEWAY= UBUNTU_INST_ARCH=amd64 UBUNTU_INST_REPOSITORY=http://archive.ubuntu.net/ubuntu; UBUNTU_INST_LOCALE=en_US UBUNTU_INST_KEYBOARD=us 2012/10/2 Bilel Msekni ski...@hotmail.frmailto:ski...@hotmail.fr Le 02/10/2012 15:39, Afef MDHAFFAR a écrit : Hi all, I used devstack to install openstack on an ubuntu 12.04 with xcp. I followed this link: https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md The script installed almost everything. The dashboard is working and shows that all services are running. However, launching nova-manage service list shows that nova-compute is not working. I also was unable to launch an instance from the dashboard and command line. Here are errors shown by nova-compute. Is there any way to solve this problem? --- 2012-10-02 09:34:10 DEBUG nova.virt.xenapi.driver [-] Got exception: ['XENAPI_PLUGIN_FAILURE', 'host_data', 'IOError', [Errno 2] No such file or directory: '/usr/etc/xenhost.conf'] from (pid=4770) _unwrap_plugin_exceptions /opt/stack/nova/nova/virt/xenapi/driver.py:728 2012-10-02 09:34:10 ERROR nova.virt.xenapi.host [-] The call to host_data returned an error: ['XENAPI_PLUGIN_FAILURE', 'host_data', 'IOError', [Errno 2] No such file or directory: '/usr/etc/xenhost.conf']. Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/eventlet/hubs/poll.py, line 97, in wait readers.get(fileno, noop).cb(fileno) File /usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main result = function(*args, **kwargs) File /opt/stack/nova/nova/service.py, line 132, in run_server server.start() File /opt/stack/nova/nova/service.py, line 410, in start self.manager.update_available_resource(ctxt) File /opt/stack/nova/nova/compute/manager.py, line 2775, in update_available_resource self.resource_tracker.update_available_resource(context) File /opt/stack/nova/nova/utils.py, line 760, in inner retval = f(*args, **kwargs) File /opt/stack/nova/nova/compute/resource_tracker.py, line 366, in update_available_resource resources = self.driver.get_available_resource() File /opt/stack/nova/nova/virt/xenapi/driver.py, line 380, in get_available_resource host_stats = self.get_host_stats(refresh=True) File /opt/stack/nova/nova/virt/xenapi/driver.py, line
Re: [Openstack] fails to launch instance
There are a few bugs with Raw images Mate is working though at the moment (see folsom release notes too): https://bugs.launchpad.net/nova/+bug/1055413 https://bugs.launchpad.net/nova/+bug/1055431 Maybe you are hitting those bugs? How new is the version of nova you are running? Can you give us the glance cli output for your image showing all the metadata (or the horizon view)? Thanks, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Afef MDHAFFAR Sent: Wednesday, October 3, 2012 4:45 PM To: openstack@lists.launchpad.net Subject: [Openstack] fails to launch instance Hi all, I am running openstack on Ubuntu 12.04 (with XCP). I create an ubuntu image (Raw). The creation of the image is successful. However, when I try to launch an instance using this image, I get this error: - 2012-10-03 15:39:15 DEBUG nova.virt.xenapi.vm_utils [req-ad542f39-2dff-4567-ae6b-9e11b692781a admin demo] [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] Fetched VDIs of type 'os_raw' with UUID '5674bc5f-4649-435f-9be0-b1aeee201a17' from (pid=5918) _fetch_image /opt/stack/nova/nova/virt/xenapi/vm_utils.py:948 2012-10-03 15:39:15 ERROR nova.utils [req-ad542f39-2dff-4567-ae6b-9e11b692781a admin demo] [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] Failed to spawn, rolling back 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] Traceback (most recent call last): 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] File /opt/stack/nova/nova/virt/xenapi/vmops.py, line 355, in spawn 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] vdis = create_disks_step(undo_mgr) 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] File /opt/stack/nova/nova/virt/xenapi/vmops.py, line 139, in inner 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] rv = f(*args, **kwargs) 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] File /opt/stack/nova/nova/virt/xenapi/vmops.py, line 257, in create_disks_step 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] image_meta, block_device_info) 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] File /opt/stack/nova/nova/virt/xenapi/vmops.py, line 224, in _create_disks 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] block_device_info=block_device_info) 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] File /opt/stack/nova/nova/virt/xenapi/vm_utils.py, line 427, in get_vdis_for_instance 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] image_type) 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] File /opt/stack/nova/nova/virt/xenapi/vm_utils.py, line 919, in _create_image 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] image_id, image_type) 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] File /opt/stack/nova/nova/virt/xenapi/vm_utils.py, line 843, in _create_cached_image 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] root_vdi = vdis['root'] 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] KeyError: 'root' 2012-10-03 15:39:15 TRACE nova.utils [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] 2012-10-03 15:39:15 ERROR nova.compute.manager [req-ad542f39-2dff-4567-ae6b-9e11b692781a admin demo] [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] Instance failed to spawn 2012-10-03 15:39:15 TRACE nova.compute.manager [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] Traceback (most recent call last): 2012-10-03 15:39:15 TRACE nova.compute.manager [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] File /opt/stack/nova/nova/compute/manager.py, line 748, in _spawn 2012-10-03 15:39:15 TRACE nova.compute.manager [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] block_device_info) 2012-10-03 15:39:15 TRACE nova.compute.manager [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] File /opt/stack/nova/nova/virt/xenapi/driver.py, line 179, in spawn 2012-10-03 15:39:15 TRACE nova.compute.manager [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] admin_password, network_info, block_device_info) 2012-10-03 15:39:15 TRACE nova.compute.manager [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] File /opt/stack/nova/nova/virt/xenapi/vmops.py, line 369, in spawn 2012-10-03 15:39:15 TRACE nova.compute.manager [instance: ea4d2039-64c3-4f6f-a866-84db1f0e3693] undo_mgr.rollback_and_reraise(msg=msg, instance=instance) 2012-10-03 15:39:15 TRACE nova.compute.manager [instance:
Re: [Openstack] instance + shutdown state
I would have a look at the VM console for the image during the boot process to see what is happening. What you might find is that it is failing to boot (for some reason) then shutting down the instance because of the boot failure. Where did you get that Ubuntu image? Thanks, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Afef MDHAFFAR Sent: Wednesday, October 3, 2012 9:49 PM To: openstack@lists.launchpad.net Subject: [Openstack] instance + shutdown state Hi all, I installed openstack on ubuntu 12.04 (with XCP). I created an ubuntu image (Raw). When I try to launch an instance, while using the ubuntu image, I get the state shutdown for the instance. Rebooting the instance does not solve the problem, because the instance is still unavailable. My log file shows this error: 2012-10-03 20:19:31 ERROR nova.manager [-] Error during ComputeManager._poll_bandwidth_usage: 'module' object has no attribute 'fetch_bandwidth' 2012-10-03 20:19:31 TRACE nova.manager Traceback (most recent call last): 2012-10-03 20:19:31 TRACE nova.manager File /opt/stack/nova/nova/manager.py, line 175, in periodic_tasks 2012-10-03 20:19:31 TRACE nova.manager task(self, context) 2012-10-03 20:19:31 TRACE nova.manager File /opt/stack/nova/nova/compute/manager.py, line 2543, in _poll_bandwidth_usage 2012-10-03 20:19:31 TRACE nova.manager bw_counters = self.driver.get_all_bw_counters(instances) 2012-10-03 20:19:31 TRACE nova.manager File /opt/stack/nova/nova/virt/xenapi/driver.py, line 313, in get_all_bw_counters 2012-10-03 20:19:31 TRACE nova.manager all_counters = self._vmops.get_all_bw_counters() 2012-10-03 20:19:31 TRACE nova.manager File /opt/stack/nova/nova/virt/xenapi/vmops.py, line 1221, in get_all_bw_counters 2012-10-03 20:19:31 TRACE nova.manager counters = vm_utils.fetch_bandwidth(self._session) 2012-10-03 20:19:31 TRACE nova.manager AttributeError: 'module' object has no attribute 'fetch_bandwidth' 2012-10-03 20:19:31 TRACE nova.manager --- Would you please help me to fix this problem? Thank you, Afef ___ 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] When will the distro (specifically Ubuntu) have package for Folsom release
Actually, that work around isn't working for me: apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 5EDB1B62EC4926EA ... gpgkeys: HTTP fetch error 7: couldn't connect: Connection refused gpg: no valid OpenPGP data found. gpg: Total number processed: 0 I am assuming this is because of the company firewall. Turns out you can get the key via the keyservers web GUI if you search for cloud archive: http://keyserver.ubuntu.com:11371/pks/lookup?op=getsearch=0x5EDB1B62EC4926EA Then, obviously, apt-key add to the above and you are up and running. Cheers, John -Original Message- From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Atul Jha Sent: Thursday, October 4, 2012 7:31 AM To: David Kranz; openstack@lists.launchpad.net Subject: Re: [Openstack] When will the distro (specifically Ubuntu) have package for Folsom release David, Did you had chance to check the OpenStack Documentation ? We updated the ubuntu install doc next day Foslom released. http://docs.openstack.org/trunk/openstack- compute/install/apt/content/ap_installingfolsomubuntuprecise.html Since Quantum has still not made to the cloud repo we have used nova-network in the doc, we are testing it everyday and will update the doc once we have it well tested. We exclusively mentioned solution of the issue you had. It gives me a feeling people without visiting doc site come here and shoot there questions. Not good for documentation contributors i suppose. :( Sincere request check the doc/file bug and let us know what we are missing before jumping the list with issue. Thanks!! Atul Jha From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net [openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of David Kranz [david.kr...@qrclab.com] Sent: Thursday, October 04, 2012 12:36 AM To: openstack@lists.launchpad.net Subject: Re: [Openstack] When will the distro (specifically Ubuntu) have package for Folsom release I am really confused about this. There are two pages that suggest the cloud archive is ready to use: http://blog.canonical.com/2012/09/14/now-you-can-have-your-openstack- cake-and-eat-it/ https://wiki.ubuntu.com/ServerTeam/CloudArchive What they tell you to put in /etc/apt/sources.list is different, but both give errors like this after putting the lines in and doing 'apt-get update': Reading package lists... Done W: GPG error: http://ubuntu-cloud.archive.canonical.com precise- proposed/folsom Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5EDB1B62EC4926EA W: GPG error: http://ubuntu-cloud.archive.canonical.com precise- updates/folsom Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5EDB1B62EC4926EA u Can any one in the know explain what the real story about this? Or am I just doing something wrong? -David On 10/1/2012 1:20 PM, Nathanael Burton wrote: From the release notes: http://wiki.openstack.org/ReleaseNotes/Folsom#Ubuntu_12.04_.2BAC8_Ubun t u_12.10 On Oct 1, 2012 1:17 PM, Matt Joyce matt.jo...@cloudscaling.commailto:matt.jo...@cloudscaling.com wrote: I am not sure indecently was the word you were looking for there. But I gather you are asking if Ubuntu is packaging folsom on their own (as in it's not part of openstack). So yes, Ubuntu is packaging folsom on their own. And I assume ubuntu will let people know when they are done packaging. They tend to be pretty good about that sort of thing. -Matt On Mon, Oct 1, 2012 at 10:02 AM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Hello, Does anybody know when will the distress, specifically Ubuntu, have packages for the OpenStack Folsom release. Is this effort done indecently of OpenStack by Ubuntu and the release date will be mentioned on Ubuntu's website? Regards, Ahmed. ___ Mailing list: https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe :
Re: [Openstack] When will the distro (specifically Ubuntu) have package for Folsom release
My bad, I missed DaveW's much easier method: sudo apt-get install ubuntu-cloud-keyring Cheers, John -Original Message- From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of John Garbutt Sent: Thursday, October 4, 2012 10:38 AM To: Atul Jha; David Kranz; openstack@lists.launchpad.net Subject: Re: [Openstack] When will the distro (specifically Ubuntu) have package for Folsom release Actually, that work around isn't working for me: apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 5EDB1B62EC4926EA ... gpgkeys: HTTP fetch error 7: couldn't connect: Connection refused gpg: no valid OpenPGP data found. gpg: Total number processed: 0 I am assuming this is because of the company firewall. Turns out you can get the key via the keyservers web GUI if you search for cloud archive: http://keyserver.ubuntu.com:11371/pks/lookup?op=getsearch=0x5EDB1B62E C4926EA Then, obviously, apt-key add to the above and you are up and running. Cheers, John -Original Message- From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Atul Jha Sent: Thursday, October 4, 2012 7:31 AM To: David Kranz; openstack@lists.launchpad.net Subject: Re: [Openstack] When will the distro (specifically Ubuntu) have package for Folsom release David, Did you had chance to check the OpenStack Documentation ? We updated the ubuntu install doc next day Foslom released. http://docs.openstack.org/trunk/openstack- compute/install/apt/content/ap_installingfolsomubuntuprecise.html Since Quantum has still not made to the cloud repo we have used nova-network in the doc, we are testing it everyday and will update the doc once we have it well tested. We exclusively mentioned solution of the issue you had. It gives me a feeling people without visiting doc site come here and shoot there questions. Not good for documentation contributors i suppose. :( Sincere request check the doc/file bug and let us know what we are missing before jumping the list with issue. Thanks!! Atul Jha From: openstack-bounces+atul.jha=csscorp@lists.launchpad.net [openstack-bounces+atul.jha=csscorp@lists.launchpad.net] on behalf of David Kranz [david.kr...@qrclab.com] Sent: Thursday, October 04, 2012 12:36 AM To: openstack@lists.launchpad.net Subject: Re: [Openstack] When will the distro (specifically Ubuntu) have package for Folsom release I am really confused about this. There are two pages that suggest the cloud archive is ready to use: http://blog.canonical.com/2012/09/14/now-you-can-have-your-openstack- cake-and-eat-it/ https://wiki.ubuntu.com/ServerTeam/CloudArchive What they tell you to put in /etc/apt/sources.list is different, but both give errors like this after putting the lines in and doing 'apt-get update': Reading package lists... Done W: GPG error: http://ubuntu-cloud.archive.canonical.com precise- proposed/folsom Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5EDB1B62EC4926EA W: GPG error: http://ubuntu-cloud.archive.canonical.com precise- updates/folsom Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5EDB1B62EC4926EA u Can any one in the know explain what the real story about this? Or am I just doing something wrong? -David On 10/1/2012 1:20 PM, Nathanael Burton wrote: From the release notes: http://wiki.openstack.org/ReleaseNotes/Folsom#Ubuntu_12.04_.2BAC8_Ubu n t u_12.10 On Oct 1, 2012 1:17 PM, Matt Joyce matt.jo...@cloudscaling.commailto:matt.jo...@cloudscaling.com wrote: I am not sure indecently was the word you were looking for there. But I gather you are asking if Ubuntu is packaging folsom on their own (as in it's not part of openstack). So yes, Ubuntu is packaging folsom on their own. And I assume ubuntu will let people know when they are done packaging. They tend to be pretty good about that sort of thing. -Matt On Mon, Oct 1, 2012 at 10:02 AM, Ahmed Al-Mehdi ah...@coraid.commailto:ah...@coraid.com wrote: Hello, Does anybody know when will the distress, specifically Ubuntu, have packages for the OpenStack Folsom release. Is this effort done indecently of OpenStack by Ubuntu and the release date will be mentioned on Ubuntu's website? Regards, Ahmed. ___ Mailing list: https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack
[Openstack] XCP 1.6 Test Day Tomorrow
Hi, Alongside the recent XenServer 6.1 release, you may have noticed XCP 1.6 beta has been released. If you are a user of XCP, please help influence the future of XCP by participating in this survey: http://www.xen.org/download/xcp/index_1.6.0.html#survey It would be great if you can also participate in the XCP test day tomorrow. More details below. In related news, you might also want to checkout the recent Xen 4.2 release: http://xen.org/download/index_4.2.0.html Thanks, John -Original Message- From: xen-users-boun...@lists.xen.org [mailto:xen-users- boun...@lists.xen.org] On Behalf Of Mike McClurg Sent: 08 October 2012 2:43 To: xen-us...@lists.xen.org; xen-...@lists.xen.org Subject: Re: [Xen-users] Reminder: XCP 1.6 Test Day on Tue the 9th Hi XCP users, Don't forget that the XCP 1.6 test day is tomorrow! See Lars' email below for the details. Also, we have resolved the issue that prevented upgrades to XCP 1.6. A new beta build can be found here: http://downloads.xen.org/XCP/61002c/ The links on the download page will be updated shortly. Mike On 05/10/12 15:04, Lars Kurth wrote: Hi, After the success of the first Xen Test Day and with XCP 1.6 being close to release, we will run an XCP test day next week. The *XCP 1.6 Test Day* will be on Tuesday, October 9th, on IRC freenode channel *#xentest*. The plan is to test XCP 1.6 beta, which should be released shortly. You can find more information about Xen Test Days on: * http://wiki.xen.org/wiki/Xen_Test_Days * http://wiki.xen.org/wiki/XCP_1.6_test_instructions What is a Xen Test Day? === Xen test days are all day IRC events, facilitated by members of the Xen community. The purpose of Test Days is to * Provide focus in testing Xen/XCP Release Candidates * Primary focus will be on new features and ensuring the RC/beta works with your hardware and in your environment How Does it Work? = The pattern is the same as for Xen Document Days: * Join us on IRC: freenode channel #xentest * Tell people what you intend to test * Make sure that a XCP release works for you * Help others, get help! * And above all: have fun! It is also OK, do to some testing before and jon the Test Day, if you get stuck and need some help. Looking forward to see you on IRC! Best Regards Lars ___ Xen-users mailing list xen-us...@lists.xen.org http://lists.xen.org/xen-users ___ 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] Failed to get metadata for ip x.x.x.x
I think Mate has just spotted this bug on trunk this morning.
He should be raising the bug and uploading a patch for that ASAP.
Clearly some unit tests are missing in this bit of code.
Thanks,
John
From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net
[mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On
Behalf Of Afef MDHAFFAR
Sent: 08 October 2012 1:43
To: openstack@lists.launchpad.net
Subject: [Openstack] Failed to get metadata for ip x.x.x.x
Hi all,
I am trying to install openstack on 3 nodes (Ubuntu 12.04 + XCP).
The platform is composed of a cloud controller and 2 compute nodes.
The installation of the cloud controller looks successful. I am able to create
and launch instances.
But launching instances on the compute nodes raise the following error:
--
2012-10-08 11:40:59 DEBUG nova.openstack.common.rpc.amqp [-] Making
asynchronous call on network ... from (pid=26752) multicall
/opt/stack/nova/nova/openstack/common/rpc/amqp.py:351
2012-10-08 11:40:59 DEBUG nova.openstack.common.rpc.amqp [-] MSG_ID is
85ce008c9916415c9454c4087c468109 from (pid=26752) multicall
/opt/stack/nova/nova/openstack/common/rpc/amqp.py:354
2012-10-08 11:40:59 ERROR nova.api.metadata.handler
[req-e9540e8a-9729-40ba-9655-22d0725c82b7 None None] Failed to get metadata for
ip: 10.0.0.21
2012-10-08 11:40:59 TRACE nova.api.metadata.handler Traceback (most recent call
last):
2012-10-08 11:40:59 TRACE nova.api.metadata.handler File
/opt/stack/nova/nova/api/metadata/handler.py, line 75, in __call__
2012-10-08 11:40:59 TRACE nova.api.metadata.handler meta_data =
self.get_metadata(remote_address)
2012-10-08 11:40:59 TRACE nova.api.metadata.handler File
/opt/stack/nova/nova/api/metadata/handler.py, line 57, in get_metadata
2012-10-08 11:40:59 TRACE nova.api.metadata.handler data =
base.get_metadata_by_address(address)
2012-10-08 11:40:59 TRACE nova.api.metadata.handler File
/opt/stack/nova/nova/api/metadata/base.py, line 383, in
get_metadata_by_address
2012-10-08 11:40:59 TRACE nova.api.metadata.handler return
InstanceMetadata(instance, address)
2012-10-08 11:40:59 TRACE nova.api.metadata.handler File
/opt/stack/nova/nova/api/metadata/base.py, line 102, in __init__
2012-10-08 11:40:59 TRACE nova.api.metadata.handler self.mappings =
_format_instance_mapping(ctxt, instance)
2012-10-08 11:40:59 TRACE nova.api.metadata.handler File
/opt/stack/nova/nova/api/metadata/base.py, line 388, in
_format_instance_mapping
2012-10-08 11:40:59 TRACE nova.api.metadata.handler return
block_device.instance_block_mapping(instance, bdms)
2012-10-08 11:40:59 TRACE nova.api.metadata.handler File
/opt/stack/nova/nova/block_device.py, line 97, in instance_block_mapping
2012-10-08 11:40:59 TRACE nova.api.metadata.handler if
FLAGS.compute_driver.endswith('xenapi.XenAPIDriver'):
2012-10-08 11:40:59 TRACE nova.api.metadata.handler File
/opt/stack/nova/nova/openstack/common/cfg.py, line 1039, in __getattr__
2012-10-08 11:40:59 TRACE nova.api.metadata.handler return self._get(name)
2012-10-08 11:40:59 TRACE nova.api.metadata.handler File
/opt/stack/nova/nova/openstack/common/cfg.py, line 1361, in _get
2012-10-08 11:40:59 TRACE nova.api.metadata.handler value =
self._substitute(self._do_get(name, group))
2012-10-08 11:40:59 TRACE nova.api.metadata.handler File
/opt/stack/nova/nova/openstack/common/cfg.py, line 1377, in _do_get
2012-10-08 11:40:59 TRACE nova.api.metadata.handler info =
self._get_opt_info(name, group)
2012-10-08 11:40:59 TRACE nova.api.metadata.handler File
/opt/stack/nova/nova/openstack/common/cfg.py, line 1470, in _get_opt_info
2012-10-08 11:40:59 TRACE nova.api.metadata.handler raise
NoSuchOptError(opt_name, group)
2012-10-08 11:40:59 TRACE nova.api.metadata.handler NoSuchOptError: no such
option: compute_driver
2012-10-08 11:40:59 TRACE nova.api.metadata.handler
2012-10-08 11:40:59 INFO nova.api.ec2 [-] 0.228018s 10.0.0.21 GET
/2009-04-04/meta-data/instance-id None:None 500 [Python-urllib/2.7] text/plain
text/plain
2012-10-08 11:40:59 INFO nova.metadata.wsgi.server [-] 10.0.0.21 - -
[08/Oct/2012 11:40:59] GET /2009-04-04/meta-data/instance-id HTTP/1.1 500 248
0.228905
However, the launching process seems to be ok. I can ping the instance but
can't ssh it.
when I try to ssh an instance launched on the compute node, I get this error:
Read from socket failed: Connection reset by peer
Can you please help to solve this problem ??
Thank you,
Afef
___
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] A simple guide to install OpenStack Folsom
Awesome stuff. I went thought this the other day, and it seemed like the most annoying part of setting up OpenStack. Sure the flexibility is good, but adding a few shortcuts looks like a good idea. For registering the services, I wonder if the following would be a good way to register the service with keystone, using the currently specified settings: (nova|glance|...)-manage keystone register admin_username password Cheers, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Joshua Harlow Sent: Wednesday, October 10, 2012 11:38 PM To: Dolph Mathews Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] A simple guide to install OpenStack Folsom I second this idea, seems like a good way forward. From: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Date: Wednesday, October 10, 2012 3:33 PM To: Joshua Harlow harlo...@yahoo-inc.commailto:harlo...@yahoo-inc.com Cc: Alan Pevec ape...@gmail.commailto:ape...@gmail.com, Skible OpenStack skible.openst...@gmail.commailto:skible.openst...@gmail.com, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] A simple guide to install OpenStack Folsom I played around with the idea this afternoon, and settled on something as simple as this in keystoneclient rather than keystone-manage: $ keystone help bootstrap usage: keystone bootstrap [--user-name user-name] --pass password [--role-name role-name] [--tenant-name tenant-name] Grants a new role to a new user on a new tenant, after creating each. Optional arguments: --user-name user-name The name of the user to be created (default=admin). --pass password The password for the new user. --role-name role-name The name of the role to be created and granted to the user (default=admin). --tenant-name tenant-name The name of the tenant to be created (default=admin). Example usage: $ keystone-manage db_sync $ keystone-all $ keystone --token=ADMIN --endpoint=http://localhost:35357/v2.0/bootstrap --pass=secrete $ keystone --os-username=admin --os-password=secrete --os-tenant-name=admin --os-auth-url=http://localhost:35357/v2.0/ token-get +---+--+ | Property | Value | +---+--+ | expires | 2012-10-11T22:25:02Z | | id| 4ae78bd2cd9049888060d07acddf88d1 | | tenant_id | 8fbba4f7f77e4acb80d746c65f20882b | | user_id | d8e31d9a341243a2bb8d575707a273ea | +---+--+ The same shortcut idea could apply to other extremely common usage patterns on the CLI (e.g. registering a service *and* all of it's endpoints in a single CLI command), thus eliminating most of the complexity of basic setup scripts like sample_data.sh and it's variants. I also put this up for review: https://review.openstack.org/#/c/14314 -Dolph On Wed, Oct 10, 2012 at 1:15 PM, Joshua Harlow harlo...@yahoo-inc.commailto:harlo...@yahoo-inc.com wrote: That sounds great to me. I can help out in converting this code into that code. It seems like a trivial kind of thing to do, what format would that command take, a yaml file? Something similar to https://github.com/yahoo/Openstack-Anvil/blob/master/conf/templates/keystone/init_what.yaml maybe, idk. From: Dolph Mathews dolph.math...@gmail.commailto:dolph.math...@gmail.com Date: Wednesday, October 10, 2012 11:13 AM To: Joshua Harlow harlo...@yahoo-inc.commailto:harlo...@yahoo-inc.com Cc: Alan Pevec ape...@gmail.commailto:ape...@gmail.com, Skible OpenStack skible.openst...@gmail.commailto:skible.openst...@gmail.com, openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] A simple guide to install OpenStack Folsom I'd like to simplify the scope of sample_data.sh to the absolute bare minimum (service tenant, admin role, admin user, identity service/endpoints, etc), and integrate it into keystone-manage as a 'bootstrap' command: $ keystone-manage bootstrap -Dolph On Wed, Oct 10, 2012 at 12:34 PM, Joshua Harlow harlo...@yahoo-inc.commailto:harlo...@yahoo-inc.com wrote: You guys should also consider the 'anvil' way of doing this (pure python baby, haha). Which is improved from lorin's and has been working for yahoo! for a while now. https://github.com/yahoo/Openstack-Anvil/blob/master/anvil/components/helpe rs/keystone.py#L25 Please feel free to take the code!! Its only 'real' dependency is the keystone client + yaml parsing... On 10/10/12 2:23 AM, Alan Pevec ape...@gmail.commailto:ape...@gmail.com wrote: On Wed, Oct 10, 2012 at 11:10 AM, Skible
Re: [Openstack] Volume booting and HVM
Just a heads up. There are a few bugs in that area that have been fixed in Grizzly, and are not yet backported to Folsom stable. Things like deleting the root volume after terminating a boot from volume instance. -Original Message- From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Egoitz Aurrekoetxea Aurre Sent: Monday, October 22, 2012 10:35 AM To: Vishvananda Ishaya Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Volume booting and HVM Thank you very much Vishvananda Best regards, El 22/10/2012, a las 18:53, Vishvananda Ishaya vishvana...@gmail.com escribió: The ability to clone an image to a volume was only recently added to cinder, so there is no automatic clone on boot in horizon yet. You will have to manually create a volume from an image and then boot from it. For older versions of openstack, the instructions are here: http://docs.openstack.org/trunk/openstack-compute/admin/content/boot-f rom-volume.html In folsom you can skip the mount and copy step and just create a volume directly from an image: IMAGE_ID=f4addd24-4e8a-46bb-b15d-fae2591f1a35 cinder create --image-id $IMAGE_ID --display-name my-volume 10 VOLUME_ID=uuid from above command $ nova boot --image $IMAGE_ID --flavor 2 --key_name mykey --block_device_mapping vda=$VOLUME_ID boot-from-vol-test Vish On Oct 22, 2012, at 4:02 AM, Egoitz Aurrekoetxea Aurre ego...@ramattack.net wrote: Good morning, I have noticed I was confused about the volume concept and booting from volume. I was thinking, when I clicked in Horizon boot from volume AND selected an HVM image (located at glance) that image was being dumped to the volume, and following times that volume would be able to boot by it's own. But have seen when I terminate de instance I'm not getting my purpose and I'm not able to later boot from that volume with preserved changes (configs and so).. How could I manage for getting my goal??. We're used to use the vms with XenCenter and then I was able to stop a vm and later to boot it. I'm looking for a similar manner with Openstack. I though I was get my goal by selecting booting from volume AND launching and image.. Any help would be very appreciated, Best regards ___ 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] Failed to get metadata for ip x.x.x.x
I was fairly sure trunk has been fixed now, just about the sametime his patch was uploaded, that had other issues. Are you still seeing the problem? I will double check the bug has been updated when I get online. Thanks, John Robert Collins robe...@robertcollins.net wrote: On Tue, Oct 9, 2012 at 3:56 AM, John Garbutt john.garb...@citrix.com wrote: I think Mate has just spotted this bug on trunk this morning. He should be raising the bug and uploading a patch for that ASAP. Clearly some unit tests are missing in this bit of code. It's been nearly three weeks now - can we revert the broken patch (which looks like it will break for everyone) and get back to a good state? If thats acceptable, I'll propose a patch to do that. -Rob ___ 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] Failed to get metadata for ip x.x.x.x
If you are using XenServer I automatically install the tools shipped with the product. It is a free download, so that might be your best bet for getting started right now. I will follow up with the XCP guys to see what we should be doing long term. Thank you for the heads up! John From: Afef MDHAFFAR [mailto:afef.mdhaf...@gmail.com] Sent: Monday, October 29, 2012 7:53 AM To: John Garbutt Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Failed to get metadata for ip x.x.x.x Hi, The folsom release solves the problem! However, I noticed that the url used by devstack to download xe-guest-utilities (http://images.ansolabs.com/xen/xe-guest-utilities_5.6.100-651_amd64.deb) does not work any more. For me, I just used my last downloads. But, a new devstack user will not be able to install openstack with XCP, without this deb file. Please try to fix this problem as soon as possible. Thank you Regards, Afef 2012/10/29 John Garbutt john.garb...@citrix.commailto:john.garb...@citrix.com I was fairly sure trunk has been fixed now, just about the sametime his patch was uploaded, that had other issues. Are you still seeing the problem? I will double check the bug has been updated when I get online. Thanks, John Robert Collins robe...@robertcollins.netmailto:robe...@robertcollins.net wrote: On Tue, Oct 9, 2012 at 3:56 AM, John Garbutt john.garb...@citrix.commailto:john.garb...@citrix.com wrote: I think Mate has just spotted this bug on trunk this morning. He should be raising the bug and uploading a patch for that ASAP. Clearly some unit tests are missing in this bit of code. It's been nearly three weeks now - can we revert the broken patch (which looks like it will break for everyone) and get back to a good state? If thats acceptable, I'll propose a patch to do that. -Rob ___ 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] Question about pv mode on compute and network
Hi, Sorry I missed this, I am still behind on my email. In the current model every XCP node gets a VM with nova-compute running on it, and it must be a linux PV VM. That node does several management tasks. For example, with raw images, it will stream the image into a VDI attached to that VM. In the current world, you need to be a PV VM for the hotplug of that volume to be allowed. So, to cut a long story short, yes, it needs to be a PV VM. I noticed some storage questions. Generally you should have a single local SR of type EXT on each of your XCP hosts. Hopefully that is all covered in the Admin guide. Let me know if anything is confusing, and I will update the guide to help clarify things. If you want shared storage you need to look towards using Cinder. So attaching volumes, doing boot-from-volume, and other such things. Right now we have support for things that produce iSCSI targets, and some NFS shared storage support is just dropping into Grizzly over the next week or so. I hope that helps, John -Original Message- From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Egoitz Aurrekoetxea Aurre Sent: 04 November 2012 10:32 To: openstack@lists.launchpad.net Subject: Re: [Openstack] Question about pv mode on compute and network or just I nova-compute and nova-network -- 1 nova-compute and nova... I wanted to mean. El 04/11/2012, a las 11:04, Egoitz Aurrekoetxea Aurre ego...@ramattack.net escribió: Hi all, Why the nova-compute and nova-network services should run in pv mode??. What's the real reason for it?. If I have a farm of five servers of Xen Cloud Platform. all of them belonging to the same pool (same cloud) should I have a nova-compute per xcp server?? or just I nova-compute and nova-network will handle the whole pool smoothly??. Best regards, ___ 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] Generating Linux pv images uploadables to glance and bootable from Xen Cloud Platform through Nova
Sorry for the late response. What you really want to do is export the OVF through XenCenter, inside there you will find the VHD file, which is what you really want to be uploading to Glance (I think there are instructions there for VHD files). Mate has a nice blog post on quicker ways to extract the VHD file, and some videos to help make it easier: http://blogs.citrix.com/2012/09/06/vhd-to-openstack-using-a-xapi-host-plugin/ Thanks, John -Original Message- From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Egoitz Aurrekoetxea Aurre Sent: 28 October 2012 00:05 To: openstack@lists.launchpad.net Subject: [Openstack] Generating Linux pv images uploadables to glance and bootable from Xen Cloud Platform through Nova Good night, Could anyone know how to do this?. I have been able to create a image for FreeBSD... because it runs in hvm mode. So... I have just export to xva, then take the vhd file convert to raw and upload to glance glance add name=FreeBSD-9.1RC1-AMD64 disk_format=raw container_format=bare FREEBSD.raw Same thing is not working for Centos it hangs saying : Error 13: Invalid or unsupported executable format So like any procedures found are for KVM I would be very thankful if someone has experience doing this... I have done some checks, read doc and so... but no way... Best regards, ___ 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 different sr
Cinder is the way forward to look at exposing multiple volume types. The Cinder guys should be able to help you with how to get that working: https://blueprints.launchpad.net/cinder/+spec/volume-type-scheduler XCP NFS support should be in there soon too: https://blueprints.launchpad.net/cinder/+spec/xenapi-storage-manager-nfs Let me know if you have specific requirements for some other type of SR. I would be very interested in how we can help you get that working. Cheers, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Egoitz Aurrekoetxea Aurre Sent: 02 November 2012 20:42 To: Armando Migliaccio Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Nova different sr Egoirz Aurrekoetxea Aurre ego...@ramattack.netmailto:ego...@ramattack.net Sent from my smartphone El 02/11/2012, a las 21:12, Armando Migliaccio amigliac...@internap.commailto:amigliac...@internap.com escribió: Egoirz, On Fri, Nov 2, 2012 at 6:29 PM, Egoitz Aurrekoetxea Aurre ego...@ramattack.netmailto:ego...@ramattack.net wrote: Good afternoon Armando, Thanks a lot for you're answer. Yes basically I want to setup a virtual housing service in the way you can create a machine in sas or sata storage for example. If each nova-compute should point to just one sr (storage kind) of xcp it would be one or the other one (in this example... sas or sata)... Ok then. So you mean the right way of doing this with Openstack is to basically have different nova-computes pointing to different sr and sharing the other properties... Have I understand properly?? That's not exactly what I meant, especially in relation to what is _right_ in OpenStack; I was providing input in relation to the use of the flag you mentioned. Ok so is not perhaps the right way but it's a possibility. #128515; Actually, if you want to support storage at different levels of QoS, Cinder is another project worth looking at. http://wiki.openstack.org/Cinder I'll tale a look at it... Mainly if this gives me the possibilty... A. In the last two paragraph I assume you're just talking about load balancing... Isn't it?? Where did you get that? No I wasn't ;) Because you were talking about where to create vm and how to manage the schwduler iirc #128515; Very thankful for you're time. Regards, Egoirz Aurrekoetxea Aurre ego...@ramattack.netmailto:ego...@ramattack.net Sent from my smartphone El 02/11/2012, a las 18:47, Armando Migliaccio amigliac...@internap.commailto:amigliac...@internap.com escribió: Hi, If I understand your request correctly, say you have two storage backends with different QoS and you want to use both of them in your OpenStack/XCP deployment, what you can do is: 1) create SR1 for XCP1 that maps to storage array at QoS1 1a) configure the compute domU for XCP1 to point to SR1, by specifying sr_matching_filter in your nova.conf accordingly. 2) create SR2 for XCP2 that maps to storage array at QoS2 2a) configure the compute domU for XCP2 to point to SR2, by specifying sr_matching_filter in your nova.conf accordingly. You can find more details here: http://wiki.openstack.org/XenServer/NovaFlags Obviously this can be extended to multiple nodes; then you can use the CLI/scheduler filters to redirect the create request to the right host. That is one way, but there are a few others like or compute extra capabilities (Essex) or general host aggregates (Folsom+) Hope this helps, Armando On Fri, Nov 2, 2012 at 9:34 AM, Egoitz Aurrekoetxea Aurre ego...@ramattack.netmailto:ego...@ramattack.net wrote: Or unless… If I had to use forcibly the same storage…. for all vm provisioned in a single nova-compute…. is it anyway of saying Openstack to create a vm in a nova-compute or another one… depending on the storage attached to the nova-compute's dom0?? El 02/11/2012, a las 10:25, Egoitz Aurrekoetxea Aurre ego...@ramattack.netmailto:ego...@ramattack.net escribió: Good morning, Perhaps I have not explained properly…. I have different IBM arrays whose disks are disks of different speeds… and wanted to have the possibility of provisioning vm on different speed storages for example…. Could this be possible??… I'm using XCP (1.5, 1.1 and 1.6 versions so I could test it in all of them)… Anne the link you provided me, although has important information… does not answer my question… Sorry… Best regards, El 01/11/2012, a las 15:35, Anne Gentle a...@openstack.orgmailto:a...@openstack.org escribió: Hi Egoitz - This topic would probably help answer your question: http://docs.openstack.org/trunk/openstack-compute/install/yum/content/terminology-storage.html Anne On Wed, Oct 31, 2012 at 4:29 PM, Egoitz Aurrekoetxea Aurre ego...@ramattack.netmailto:ego...@ramattack.net wrote: Good night, Could anyone know if it's possible to use different nfs servers or different storages for launching instances in
Re: [Openstack] instance disk space
Sounds like a bug worth reporting. What flavor where you selecting, and what image were you using? There is some code in XenAPI driver that tries to resize the partition of the disk, and the file system on it, if I remember correctly. Can you see that in the logs? Maybe it fails because your image doesn't have a file system type it expects, or doesn't have a partition table on the disk, or vv. John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Afef MDHAFFAR Sent: 02 November 2012 09:31 To: openstack@lists.launchpad.net Subject: [Openstack] instance disk space Hi all, I am running openstack, with XCP on ubuntu 12.04. When I tried to launch instance using the majority of existing flavors, I noticed that the instance never takes into account the mentioned disk space. I also tried to create a new flavor with Ephemeral disk, but this does not solve the problem. I never get the required disk space. Do I have to mount some partitions??? Your answers are very appreciated! Thank you, Afef ___ 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 different sr
My bad, I noticed you have some IBM arrays. What SR type are you using to connect to those? I think Cinder has some code of some IBM arrays. If that connects with iSCSI, it should work with XCP. Cheers, John From: John Garbutt Sent: 09 November 2012 12:08 To: 'Egoitz Aurrekoetxea Aurre'; Armando Migliaccio; Mate Lakat Cc: openstack@lists.launchpad.net Subject: RE: [Openstack] Nova different sr Cinder is the way forward to look at exposing multiple volume types. The Cinder guys should be able to help you with how to get that working: https://blueprints.launchpad.net/cinder/+spec/volume-type-scheduler XCP NFS support should be in there soon too: https://blueprints.launchpad.net/cinder/+spec/xenapi-storage-manager-nfs Let me know if you have specific requirements for some other type of SR. I would be very interested in how we can help you get that working. Cheers, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.netmailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Egoitz Aurrekoetxea Aurre Sent: 02 November 2012 20:42 To: Armando Migliaccio Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: Re: [Openstack] Nova different sr Egoirz Aurrekoetxea Aurre ego...@ramattack.netmailto:ego...@ramattack.net Sent from my smartphone El 02/11/2012, a las 21:12, Armando Migliaccio amigliac...@internap.commailto:amigliac...@internap.com escribió: Egoirz, On Fri, Nov 2, 2012 at 6:29 PM, Egoitz Aurrekoetxea Aurre ego...@ramattack.netmailto:ego...@ramattack.net wrote: Good afternoon Armando, Thanks a lot for you're answer. Yes basically I want to setup a virtual housing service in the way you can create a machine in sas or sata storage for example. If each nova-compute should point to just one sr (storage kind) of xcp it would be one or the other one (in this example... sas or sata)... Ok then. So you mean the right way of doing this with Openstack is to basically have different nova-computes pointing to different sr and sharing the other properties... Have I understand properly?? That's not exactly what I meant, especially in relation to what is _right_ in OpenStack; I was providing input in relation to the use of the flag you mentioned. Ok so is not perhaps the right way but it's a possibility. #128515; Actually, if you want to support storage at different levels of QoS, Cinder is another project worth looking at. http://wiki.openstack.org/Cinder I'll tale a look at it... Mainly if this gives me the possibilty... A. In the last two paragraph I assume you're just talking about load balancing... Isn't it?? Where did you get that? No I wasn't ;) Because you were talking about where to create vm and how to manage the schwduler iirc #128515; Very thankful for you're time. Regards, Egoirz Aurrekoetxea Aurre ego...@ramattack.netmailto:ego...@ramattack.net Sent from my smartphone El 02/11/2012, a las 18:47, Armando Migliaccio amigliac...@internap.commailto:amigliac...@internap.com escribió: Hi, If I understand your request correctly, say you have two storage backends with different QoS and you want to use both of them in your OpenStack/XCP deployment, what you can do is: 1) create SR1 for XCP1 that maps to storage array at QoS1 1a) configure the compute domU for XCP1 to point to SR1, by specifying sr_matching_filter in your nova.conf accordingly. 2) create SR2 for XCP2 that maps to storage array at QoS2 2a) configure the compute domU for XCP2 to point to SR2, by specifying sr_matching_filter in your nova.conf accordingly. You can find more details here: http://wiki.openstack.org/XenServer/NovaFlags Obviously this can be extended to multiple nodes; then you can use the CLI/scheduler filters to redirect the create request to the right host. That is one way, but there are a few others like or compute extra capabilities (Essex) or general host aggregates (Folsom+) Hope this helps, Armando On Fri, Nov 2, 2012 at 9:34 AM, Egoitz Aurrekoetxea Aurre ego...@ramattack.netmailto:ego...@ramattack.net wrote: Or unless… If I had to use forcibly the same storage…. for all vm provisioned in a single nova-compute…. is it anyway of saying Openstack to create a vm in a nova-compute or another one… depending on the storage attached to the nova-compute's dom0?? El 02/11/2012, a las 10:25, Egoitz Aurrekoetxea Aurre ego...@ramattack.netmailto:ego...@ramattack.net escribió: Good morning, Perhaps I have not explained properly…. I have different IBM arrays whose disks are disks of different speeds… and wanted to have the possibility of provisioning vm on different speed storages for example…. Could this be possible??… I'm using XCP (1.5, 1.1 and 1.6 versions so I could test it in all of them)… Anne the link you provided me, although has important information… does not answer my question… Sorry… Best regards, El 01/11
Re: [Openstack] nova.virt.xenapi.driver [-] Got exception: ['XENAPI_MISSING_PLUGIN', 'xenhost']
DevStack is able to automate this whole process for you, if you follow the XenServer Readme: https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md It basically installs all the plugins, and creates the VM that runs the nova services for you. Understanding the networking can be a little tricky (because of some assumptions the scripts make) if you don’t follow the example networking exactly; but I am willing to help you through that. If you are going more manually, the docs have some more info on the issues you might be hitting (and some info on possible networking options): http://docs.openstack.org/folsom/openstack-compute/admin/content/introduction-to-xen.html#xenapi-install The above will point you towards the readme about the required XenAPI plugins: https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/README I hope that helps. John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Mohammed Naser Sent: 18 November 2012 3:27 PM To: Afef MDHAFFAR Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] nova.virt.xenapi.driver [-] Got exception: ['XENAPI_MISSING_PLUGIN', 'xenhost'] Hi there, 2012-11-15 19:57:05 DEBUG nova.virt.xenapi.driver [-] Got exception: ['XENAPI_MISSING_PLUGIN', 'xenhost'] from (pid=25140) _unwrap_plugin_exceptions /opt/stack/nova/nova/virt/xenapi/driver.py:754 Please login to your main XenServer dom0 and make sure you have the plugins installed from the source https://github.com/openstack/nova/tree/master/plugins/xenserver/xenapi Good luck On Thu, Nov 15, 2012 at 3:22 PM, Afef MDHAFFAR afef.mdhaf...@gmail.commailto:afef.mdhaf...@gmail.com wrote: The first problem has been solved by synchronizing the 2 nodes. But, I could not find a solution to the second one -- nova-compute does not want to start 2012/11/15 Afef MDHAFFAR afef.mdhaf...@gmail.commailto:afef.mdhaf...@gmail.com Hi all, I tried to add a third compute node to a running openstack platform (composed of a head node and a compute node). I use Ubuntu 12.04 + XCP + folsom (stable release). And, I use devstack to install the compute node. The first problem is that the 2nd (new) compute node is not able to see that the head node nova services are enabled, however it is still able to detect that nova services of the first compute node are running and available. nova-manage service list 2012-11-15 20:02:46 DEBUG nova.utils [req-44c68f9f-b9f4-498b-a081-c0273e23e05f None None] backend module 'nova.db.sqlalchemy.api' from '/opt/stack/nova/nova/db/sqlalchemy/api.pyc' from (pid=25406) __get_backend /opt/stack/nova/nova/utils.py:502 Binary Host Zone Status State Updated_At nova-consoleauth DevStackOSDomU nova enabled XXX 2012-11-15 20:01:37 nova-certcomputeDomU01nova enabled :-) 2012-11-15 20:02:30 nova-network computeDomU01nova enabled :-) 2012-11-15 20:02:33 nova-scheduler computeDomU01nova enabled :-) 2012-11-15 20:02:33 nova-compute computeDomU01nova enabled :-) 2012-11-15 20:02:30 nova-network DevStackOSDomU nova enabled XXX 2012-11-15 20:01:40 nova-scheduler DevStackOSDomU nova enabled XXX 2012-11-15 20:01:40 nova-certDevStackOSDomU nova enabled XXX 2012-11-15 20:01:35 nova-compute DevStackOSDomU nova enabled XXX 2012-11-15 20:01:40 nova-network computeDomU02nova enabled :-) 2012-11-15 20:02:43 nova-compute computeDomU02nova enabled XXX None nova-scheduler computeDomU02nova enabled :-) 2012-11-15 20:02:43 nova-certcomputeDomU02nova enabled :-) 2012-11-15 20:02:43 The nova-services are of course running on the head node. Actually, launching nova-manage service list on the head node or the first compute node returns the following output: nova-manage service list 2012-11-15 20:05:08 DEBUG nova.utils [req-47839159-dc05-4947-a070-66b9f0db36e7 None None] backend module 'nova.db.sqlalchemy.api' from '/opt/stack/nova/nova/db/sqlalchemy/api.pyc' from (pid=6912) __get_backend /opt/stack/nova/nova/utils.py:502 Binary Host Zone Status State Updated_At nova-consoleauth DevStackOSDomU nova enabled :-) 2012-11-15 20:04:10 nova-certcomputeDomU01nova enabled :-) 2012-11-15 20:05:03
Re: [Openstack] Networking issues for openstack on XCP
There are docs here: http://docs.openstack.org/folsom/openstack-compute/admin/content/introduction-to-xen.html And networking info here: http://docs.openstack.org/folsom/openstack-compute/admin/content/xenapi-flat-dhcp-networking.html Let me know what bits are confusing, and I will make an effort to improve the docs around that area, and help you through things. Firstly, quantum support in XCP (with OVS) is still a work in progress. Help to review the changes in Gerrit are very welcome! Now, lets look at your questions... 1 Controller node: no Xen, only Ubuntu 12.04, everything for openstack service except for nova-compute 2 Compute node: XCP 1.6 beta, with nova-compute in special domU (Ubuntu 12.04), xenapi plugin installed in dom0 each node has two NIC, one with public IP (Only limited floating IP), and another in private network (Any IP is OK) flat network or flat dhcp network I want to use eth0 for public traffic and service request, and eth1 for inter-vm traffic. OK, but where is your management traffic, like Rabbit and MySQL going? I would have expected one nic for management network, and one nic for public traffic, with maybe with a separate VLAN for instance traffic? 1.) does each domU need nova-network running? My understanding is it's OK to run nova-network individually, but then how to mange the floating IP globally? Correct. If multi_host=true, you are running nova-network on every node, if false you just run one. It depends if you don't mind the extra overhead or not. Others can describe the trade-offs more clearly. http://docs.openstack.org/folsom/openstack-compute/admin/content/xenapi-flat-dhcp-networking.html 2.) in document for flatdhcp network, I saw four interfaces for each management domU. Is it OK to have only two interfaces? Say, eth0-xenbr0 for public IP and services, and eth1-xenbr1 for VM network? As above, you need to think about where your management traffic like MySQL and Rabbit traffic is going. Three is certainly fine. 3.) Is the network isolation rules a must for test install? I found the patch to vif is still for xenserver 5.6_p2, and can not be applied to vif of xcp 1.6 or xenserver 6.1, which might be a trouble. It is not required for a test setup. Do bug me if you are having problems with that stuff on XCP, and I can ask the XCP guys to help me get that working for you. Sorry for the slow response. I was on holiday. Thanks, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Yan Zhai Sent: 20 November 2012 7:52 AM To: Afef MDHAFFAR Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Networking issues for openstack on XCP have even more trouble setting up quantum itself. The plugin support in XCP looks not as good as KVM: the first problem is python 2.6 and it's solved by adding new repository. But when I installed the openvswitch agent, it can not start, requiring some quantum python module, which then seems have dependency on libudev. And this means I have to update almost the whole dom0, including libc, udev, and blablabla to get that library. That's too risky. Maybe I shall stay with bridge plugin and see if things can be a little better... On Sat, Nov 17, 2012 at 1:18 PM, Afef MDHAFFAR afef.mdhaf...@gmail.com wrote: Hi all, I am also trying to install openstack, with xcp. I used devstack to do that, since it is more simple. However, I am still facing a network problem. Actually, I got a private network per physical node. I am able to access the tenant VMs from the corresponding openstack DomU. But, these tenant VMs are not inaccessible from any other machines. Is that normal (ie. a private network per physical node? The created tenant VMs can access external machines, but they are invisible to other machines? Is there any way to let my VMs accessible, at least from other tenant VMs (created on other physical nodes)? How can Quantum solve this problem? Thank you Regards, Afef 2012/11/17 Yan Zhai zhaiyan...@gmail.com Hi Robert, thanks for reply. Currently I am just looking for a way to bring it up for internal trial, so if Quantum is better I will move to that. The only reason that I am still asking for questions about nova-network is because of the document order: I am setting things following the install document, but when it comes to the network part I encountered above confusions. I will check the quantum document to see if anything can be simplified. Thanks again! best Yan On Fri, Nov 16, 2012 at 11:54 PM, Robert Garron robert.gar...@access3000.net wrote: Yan, In my opinion, if you are going to spend all the time learning a new product -- i.e. nova network vs quantum. And if you are only testing a concept, I would spend it upon Folsom and move from Essex and/or nova network and nova storage. Quantum eases many of the issues Nova network has
Re: [Openstack] Citrix Xen Server + XenApi Failed to start nova-compute service
+1 you can’t use the libvirt specific firewall driver with XenAPI There are some example nova.conf files here that may help: http://docs.openstack.org/folsom/openstack-compute/admin/content/xenapi-flat-dhcp-networking.html If you use DevStack, it should have “chosen” the correct firewall driver for you. Cheers, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Mohammed Naser Sent: 21 November 2012 14:06 To: Lei Zhang Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Citrix Xen Server + XenApi Failed to start nova-compute service Your firewall driver in your nova.conf seems to be incorrect 2012-11-21 01:33:47 TRACE nova self.firewall_driver = fw_class(xenapi_session=self._session) 2012-11-21 01:33:47 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/firewall.py, line 227, in __init__ It's trying to use the libvirt driver. # grep firewall /etc/nova/nova.conf firewall_driver=nova.virt.xenapi.firewall.Dom0IptablesFirewallDriver Good luck with OpenStack! On Wed, Nov 21, 2012 at 1:46 AM, Lei Zhang zhang.lei@gmail.commailto:zhang.lei@gmail.com wrote: Hi All, I am tring install the openstack with Xen Server following the guide of http://wiki.openstack.org/XenServer/XenXCPAndXenServer. But I run into error when start the nova-compute service . Here is the error message. Who can figure out why it happended and how to fix this issue. Error Message root@ubuntu:/etc/nova# nova-compute 2012-11-21 01:33:47 CRITICAL nova [-] 'get_connection' 2012-11-21 01:33:47 TRACE nova Traceback (most recent call last): 2012-11-21 01:33:47 TRACE nova File /usr/bin/nova-compute, line 47, in 2012-11-21 01:33:47 TRACE nova server = service.Service.create(binary='nova-compute') 2012-11-21 01:33:47 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 241, in create 2012-11-21 01:33:47 TRACE nova report_interval, periodic_interval) 2012-11-21 01:33:47 TRACE nova File /usr/lib/python2.7/dist-packages/nova/service.py, line 150, in __init__ 2012-11-21 01:33:47 TRACE nova self.manager = manager_class(host=self.host, *args, **kwargs) 2012-11-21 01:33:47 TRACE nova File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 204, in __init__ 2012-11-21 01:33:47 TRACE nova utils.import_object(compute_driver), 2012-11-21 01:33:47 TRACE nova File /usr/lib/python2.7/dist-packages/nova/utils.py, line 89, in import_object 2012-11-21 01:33:47 TRACE nova return cls() 2012-11-21 01:33:47 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/connection.py, line 76, in get_connection 2012-11-21 01:33:47 TRACE nova conn = xenapi_conn.get_connection(read_only) 2012-11-21 01:33:47 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py, line 144, in get_connection 2012-11-21 01:33:47 TRACE nova return XenAPIConnection(url, username, password) 2012-11-21 01:33:47 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/xenapi_conn.py, line 157, in __init__ 2012-11-21 01:33:47 TRACE nova self._vmops = vmops.VMOps(self._session, self._product_version) 2012-11-21 01:33:47 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/xenapi/vmops.py, line 160, in __init__ 2012-11-21 01:33:47 TRACE nova self.firewall_driver = fw_class(xenapi_session=self._session) 2012-11-21 01:33:47 TRACE nova File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/firewall.py, line 227, in __init__ 2012-11-21 01:33:47 TRACE nova self.nwfilter = NWFilterFirewall(kwargs['get_connection']) 2012-11-21 01:33:47 TRACE nova KeyError: 'get_connection' 2012-11-21 01:33:47 TRACE nova nova.conf connection_type=xenapi xenapi_connection_password=*** xenapi_connection_url=http://192.168.0.98 xenapi_connection_username=root -- Lei Zhang Blog: http://jeffrey4l.github.com twitter/weibo: @jeffrey4l ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Mohammed Naser — vexxhost - D. 514-316-8872 D. 800-910-1726 ext. 200 E. mna...@vexxhost.commailto:mna...@vexxhost.com W. http://vexxhost.comhttp://vexxhost.com/ ___ 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] Handling of adminPass is arguably broken (essex)
Those agents use the Xen/XenAPI specific stuff called xenstore. There was talk of extending cloud-init and the metadata service to support some kind of password generation on boot or at a poll interval, but I don't remember that conversation getting too far. Anyone one else remember what came of those ideas? John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Sam Stoelinga Sent: 28 November 2012 06:26 To: Pádraig Brady Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Handling of adminPass is arguably broken (essex) Hi, Just noticed the following two projects: https://github.com/rackspace/openstack-guest-agents-windows-xenserver https://github.com/rackspace/openstack-guest-agents-unix Would those be useful in creating an agent like Vish described? It seems they currently only support Xen? Haven't taken a deep look yet. a) put a public key on the instance via metadata or config drive (for ease of use this could actually just be the ssh public key you normally use for logging into the vm). b) have a daemon in the windows instance that: * generates a random password * sets the administrator password to the random password * encrypts it with the public key * serves the encrypted password over https on a known port (say ) c) open up port () in the instance's security group d) retrieve the encrypted password and decrypt it e) close port () in the instances security group Was wondering if it's planned for Grizzly a way to change the password for libvirt/kvm guests (unix and windows)? Is there any blueprint available? Sam On Sat, Nov 3, 2012 at 3:15 AM, Pádraig Brady p...@draigbrady.commailto:p...@draigbrady.com wrote: On 11/02/2012 07:03 PM, Lars Kellogg-Stedman wrote: On Thu, Nov 01, 2012 at 11:03:14AM -0700, Vishvananda Ishaya wrote: The new config drive code defaults to iso-9660, so that should work. The vfat version should probably create a partition table. Is that what Folsom is using? Or is it new-er than that? That's in Folsom ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto: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] how to let the instance name (instance-xxx) equal to the hostname of the instance (chosen by the user)??
Hi, Not quick sure which name of the instance you are refereeing to. Do you mean when you open XenCenter it shows you a different name? Thanks, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Afef MDHAFFAR Sent: 23 November 2012 17:22 To: openstack@lists.launchpad.net Subject: [Openstack] how to let the instance name (instance-xxx) equal to the hostname of the instance (chosen by the user)?? Hi all, Due to some requirements, I have to modify openstack source code in order to let the name of the instance (in Xen Server) equal to the hostname of the instance (chosen by the user). Is it possible to do that by only configuring openstack? If yes, could you please guide me to the suitable flag? If not, could you please guide me to the right python files that need to be changed. I use the folsom release, with XCP as a virtualization technology. Thank you, Afef ___ 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] how to let the instance name (instance-xxx) equal to the hostname of the instance (chosen by the user)??
I think this is the flag you want to change and its default: instance_name_template=instance-%08x You should try: instance_name_template=%(hostname)s This is the code that deals with it: https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/models.py#L203 This is where the name gets set inside XenAPI: https://github.com/openstack/nova/blob/master/nova/virt/xenapi/vmops.py#L260 Which eventually gets here (i.e. you could just hack this file, if the above fails): https://github.com/openstack/nova/blob/master/nova/virt/xenapi/vm_utils.py#L193 Hope that helps, John From: Afef MDHAFFAR [mailto:afef.mdhaf...@gmail.com] Sent: 28 November 2012 18:18 To: John Garbutt Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] how to let the instance name (instance-xxx) equal to the hostname of the instance (chosen by the user)?? Hi, Yes - when you list your vms via xe vm-list, you get the name-label of the instance. The question is how to modify openstack to let the hostname of the created instance equal to this name-label? Thank you, Afef 2012/11/28 John Garbutt john.garb...@citrix.commailto:john.garb...@citrix.com Hi, Not quick sure which name of the instance you are refereeing to. Do you mean when you open XenCenter it shows you a different name? Thanks, John From: openstack-bounces+john.garbutt=citrix@lists.launchpad.netmailto:citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbuttmailto:openstack-bounces%2Bjohn.garbutt=citrix@lists.launchpad.netmailto:citrix@lists.launchpad.net] On Behalf Of Afef MDHAFFAR Sent: 23 November 2012 17:22 To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Subject: [Openstack] how to let the instance name (instance-xxx) equal to the hostname of the instance (chosen by the user)?? Hi all, Due to some requirements, I have to modify openstack source code in order to let the name of the instance (in Xen Server) equal to the hostname of the instance (chosen by the user). Is it possible to do that by only configuring openstack? If yes, could you please guide me to the suitable flag? If not, could you please guide me to the right python files that need to be changed. I use the folsom release, with XCP as a virtualization technology. Thank you, Afef -- Afef MDHAFFAR http://www.redcad.org/members/mdhaffar/ ___ 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] resizing instance fails
Hi,
This is interesting:
2012-12-03 14:38:25 ERROR nova.compute.manager
[req-3e393b4e-d0ed-430f-b0cc-53a9167e afef cep4cma] [instance:
d3dba21b-3877-4da3-a2ab-8128f8515573] VHD coalesce attempts exceeded (5),
giving up Setting instance vm_state to ERROR
Is it possible to get the logs from your XenServer host to tell us what was
going wrong when this happened?
What is the version of your server, and I am assuming the VM disks are on an
EXT3 SR?
John
From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net
[mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On
Behalf Of Afef MDHAFFAR
Sent: 03 December 2012 14:42
To: openstack@lists.launchpad.net
Subject: [Openstack] resizing instance fails
Hi all,
when I try to resize a running instance, I get this error:
Is there any way to solve it?
2012-12-03 14:38:25 ERROR nova.compute.manager
[req-3e393b4e-d0ed-430f-b0cc-53a9167e afef cep4cma] [instance:
d3dba21b-3877-4da3-a2ab-8128f8515573] VHD coalesce attempts exceeded (5),
giving up Setting instance vm_state to ERROR
2012-12-03 14:38:25 DEBUG nova.manager [-] Running periodic task
SchedulerManager._expire_reservations from (pid=19093) periodic_tasks
/opt/stack/nova/nova/manager.py:171
2012-12-03 14:38:25 DEBUG nova.openstack.common.lockutils
[req-3e393b4e-d0ed-430f-b0cc-53a9167e afef cep4cma] Got semaphore
compute_resources for method update_usage... from (pid=19070) inner
/opt/stack/nova/nova/openstack/common/lockutils.py:185
2012-12-03 14:38:26 DEBUG nova.openstack.common.rpc.amqp [-] received
{u'_context_roles': [], u'_context_request_id':
u'req-9cc1eaf2-4773-4db0-b4d7-d80e4cf306eb', u'_context_quota_class': None,
u'_context_project_name': None, u'_context_service_catalog': None,
u'_context_user_name': None, u'_context_auth_token': 'SANITIZED', u'args':
{u'service_name': u'compute', u'host': u'computeDomU03', u'capabilities':
{u'host_name-description': u'Default install of XenServer', u'disk_available':
230087983104, u'host_hostname': u'compute09', u'supported_instances':
[[u'x86_64', u'xapi', u'xen'], [u'x86_32p', u'xapi', u'xen'], [u'x86_32',
u'xapi', u'hvm'], [u'x86_32p', u'xapi', u'hvm'], [u'x86_64', u'xapi', u'hvm']],
u'host_memory_overhead': 106897408, u'enabled': u'true', u'host_ip':
u'10.0.1.19', u'host_capabilities': [u'xen-3.0-x86_64', u'xen-3.0-x86_32p',
u'hvm-3.0-x86_32', u'hvm-3.0-x86_32p', u'hvm-3.0-x86_64'], u'host_uuid':
u'03433673-d30c-4f8e-94cc-43d53f9c2207', u'host_memory_free': 5261139968,
u'disk_total': 242124587008, u'host_ip_address': u'10.0.1.166',
u'hypervisor_hostname': u'compute09', u'host_memory_total': 8589463552,
u'host_memory_free_computed': 5178503168, u'disk_used': 12036603904,
u'host_other-config': {u'agent_start_time': u'1353496206.', u'boot_time':
u'1353496188.', u'no_local_storage': u'true'}, u'host_name-label':
u'compute09', u'host_cpu_info': {u'physical_features':
u'---', u'modelname': u'Dual-Core AMD
Opteron(tm) Processor 2216 HE', u'vendor': u'AuthenticAMD', u'features':
u'---', u'family': 15, u'maskable': u'no',
u'cpu_count': 4, u'flags': u'fpu de tsc msr pae cx8 apic cmov pat clflush mmx
fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow rep_good nopl
extd_apicid pni cx16 hypervisor lahf_lm cmp_legacy extapic cr8_legacy',
u'stepping': 2, u'model': 65, u'features_after_reboot':
u'---', u'speed': u'2394.010'}}},
u'_context_instance_lock_checked': False, u'_context_is_admin': True,
u'version': u'2.0', u'_context_project_id': None, u'_context_timestamp':
u'2012-12-03T14:38:26.342811', u'_context_read_deleted': u'no',
u'_context_user_id': None, u'method': u'update_service_capabilities',
u'_context_remote_address': None} from (pid=19093) _safe_log
/opt/stack/nova/nova/openstack/common/rpc/common.py:195
2012-12-03 14:38:26 DEBUG nova.openstack.common.rpc.amqp [-] unpacked context:
{'project_name': None, 'user_id': None, 'roles': [], 'timestamp':
u'2012-12-03T14:38:26.342811', 'auth_token': 'SANITIZED', 'remote_address':
None, 'quota_class': None, 'is_admin': True, 'service_catalog': None,
'request_id': u'req-9cc1eaf2-4773-4db0-b4d7-d80e4cf306eb',
'instance_lock_checked': False, 'project_id': None, 'user_name': None,
'read_deleted': u'no'} from (pid=19093) _safe_log
/opt/stack/nova/nova/openstack/common/rpc/common.py:195
2012-12-03 14:38:26 DEBUG nova.scheduler.host_manager
[req-9cc1eaf2-4773-4db0-b4d7-d80e4cf306eb None None] Received compute service
update from (u'computeDomU03', u'compute09'). from (pid=19093)
update_service_capabilities /opt/stack/nova/nova/scheduler/host_manager.py:340
2012-12-03 14:38:26 DEBUG nova.openstack.common.lockutils
[req-3e393b4e-d0ed-430f-b0cc-53a9167e afef cep4cma] Got semaphore
compute_resources for method update_usage... from (pid=19070) inner
/opt/stack/nova/nova/openstack/common/lockutils.py:185
2012-12-03 14:38:26
Re: [Openstack] Wiki content imported into MediaWiki - please check
One more thing I spotted around links. In the migrated wiki: [[XenServer/DevStack|XenServer and [[DevStack Clearly it's a simple fix to this: [[XenServer/DevStack|XenServer and DevStack]] I guess this extra link (that is obviously not valid syntax, and wasn't in the original page) got added when the page was imported? Cheers, John -Original Message- From: openstack-bounces+john.garbutt=citrix@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=citrix@lists.launchpad.net] On Behalf Of Thierry Carrez Sent: 18 December 2012 10:04 To: openstack@lists.launchpad.net Subject: Re: [Openstack] Wiki content imported into MediaWiki - please check Ryan Lane wrote: I've just finished importing the content from the MoinMoin wiki into the MediaWiki instance. Please check the content: https://wiki-staging.openstack.org/wiki/Main_Page [...] Also note that the migration script doesn't map from MoinMoin to MediaWiki perfectly and we'll need to clean up some of the content manually. We'll need to create some templates for missing features too (like columned layout). The most obvious issue is how ugly the new main page is :) The loss of image inclusion and columns transformed an admittedly not perfect page (disclaimer: I authored it) into something unreadable and very unwelcoming. Note that it's probably the only page that uses column layout, so maybe we can just special case the main page rather than write a generic column- handler. Image inclusion however is a bit more problematic, as it's being used in several pages (like http://wiki.openstack.org/Documentation/Translation/Status) that are now broken. The second most obvious issue is the loss of the OpenStack theme on all pages: it would be good to theme the wiki before we complete the transition. Other issues to watch for before completing the transition: * Broken table layouts, and no more cell background colors: See examples at https://wiki-staging.openstack.org/wiki/GrizzlyReleaseSchedule or https://wiki-staging.openstack.org/wiki/Releases * URL: The new wiki URL appear under a wiki/ subdirectory: https://wiki-staging.openstack.org/wiki/Projects -- would be great to make sure that once the migration is completed they can still be accessed from previous URLs (http://wiki.openstack.org/Projects) so that we don't have to change URL pointers from other sites. * TableOfContents: we used that macro on a lot of pages -- but I guess we could abandon them * Protected pages: A limited number of pages are protected in the old wiki (mostly governance pages, main page and list of official projects) to avoid random edits -- will this feature be kept ? We're going to leave the wiki up for a couple days in this state. If the content is mostly agreeable and we decide to press forward, I'll migrate the data again and we'll replace MoinMoin. I fear we are more than just a couple of days away from being able to migrate content in a mostly agreeable way, but you're the expert :) -- 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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
