[Openstack] Launchpad PO file outdated
Hi OpenStack developers, Could anyone responsible for the PO file generation take a look at this bug? The current launchpad PO file obsolete. https://bugs.launchpad.net/nova/+bug/973980 I think it is urgent. I hope the PO file should be updated. Can anyone help with it? Best wishes! Vincent___ 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 Plugin for Jenkins
I've got Compute functionality working with the OpenStack Jenkins plugin, so it can launch nova instances as on-demand slaves now, run builds on them, and archive the results into swift. I'd like to open GitHub issues to track your requirements, but I have a few questions. We need disposable machines that are only used for one test, which means spinning up and terminating hundreds of machines per day. Sounds like we want a function to terminate the machine after the job has run. https://github.com/platformlayer/openstack-jenkins/issues/1 We need to use machines from multiple providers simultaneously so that we're resilient against errors with one provider. Label expressions should work here; you would apply a full set of axis labels to each machine (rax oneiric python26) but then you would filter based only on the required axes (oneric python26). Are labels sufficient for this? We need to pull nodes from a pool of machines that have been spun up ahead of time for speed. This sounds like a custom NodeProvisioner implementation. The current implementation is optimized around minimizing CPU hours, by doing load prediction. You have a different criteria, based on minimizing launch latency. It looks like it should be relatively easy to implement a new algorithm, although perhaps a bit tricky to figure out how to plug it in. https://github.com/platformlayer/openstack-jenkins/issues/2 We need to be able to select from different kinds of images for certain tests. Are labels sufficient for this? Machines need to be checked for basic functionality before being added to the pool (we frequently get nodes without a functioning network). I believe Jenkins does this anyway; a node which doesn't have networking won't be able to get the agent. And you can run your own scripts after the slave boots up (apt-get install openjdk, for example). Those scripts can basically do any checks you want. Is that enough? They need to be started from snapshots with cached data on them to avoid false negatives from network problems. Can you explain this a bit more? This is to protect against the apt repositories / python sources / github repos being down? Would an http proxy be enough? We need to keep them around after failures to diagnose problems, and we need to delete those after a certain amount of time. From the github docs, it sounds like you don't get access anyway because of the providers' policies. Would it not therefore be better to take a ZIP or disk snapshot after a failed test, and then shut down the machine as normal? Also... You currently auto-update your images, which is cool (devstack-update-vm-image). Do you think this is something a plugin should do, or do you think this is better done through scripts and a matrix job? I'm leaning towards keeping it in scripts. The one thing I think we definitely need here is some sort of 'best match' image launching, rather than hard-coding to a particular ID, so that the cloud plugin will always pick up the newest image. https://github.com/platformlayer/openstack-jenkins/issues/3 Justin ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] No official Diablo 2011.3.1 for oneiric?
Philipp Wollermann wrote: am I right, that the official packages of openstack (nova) for Ubuntu 11.10 (oneiric) were never updated to Diablo 2011.3.1 and no bug-fixes from after the initial release were ever included? I checked the change log of the nova packages, and it seems like the maintainers only fixed security issues. The stable/diablo branches, and the resulting 2011.3.1 release, are a cross-distro effort to maintain a stable version of past releases. Each distribution of OpenStack follows its own rules on what patches it backports, in the case of Ubuntu itself, it follows: https://wiki.ubuntu.com/StableReleaseUpdates -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Launchpad PO file outdated
Sheng Bo Hou wrote: Could anyone responsible for the PO file generation take a look at this bug? The current launchpad PO file obsolete. https://bugs.launchpad.net/nova/+bug/973980 https://bugs.launchpad.net/nova/+bug/973980 It's actually a duplicate of bug 960060. The translations import chain is broken (and has been for a few months). We'll have to fix this post-release. -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] ESXi documentation..
Hello all, Following are the steps we followed to install and configure Openstack on ESX hypervisor. 1.Install the OS. We have mentioned the steps for Ubuntu as the OS.\ 2.Setup the network connections and configure apt-get. 3.Do an update as: sudo apt-get update INSTALL NECESSARY SOFTWARE: 1.Install python-suds. This software is needed by nova-compute service. If not installed, the nova-compute service shuts down with the message: Unable to import suds sudo apt-get install python-suds 2.Install SSH services: sudo apt-get install openssh-server 3.Install tomcat. sudo apt-get install tomcat6 copy the folder wsdl into /var/lib/tomcat6/webapps. This can be downloaded from http://www.vmware.com/support/developer/vc-sdk/. The wsdl folder is also attached with this mail in case you are unable to download. (Attachments.ZIP) INSTALL OPENSTACK: 1.Install openstack glance. Glance is the openstack image service. sudo apt-get install glance 2.Openstack people have provided a script to install Openstack. This will install and ask necessary details for configuring the same. The script can be downloaded from: https://raw.github.com/elasticdog/OpenStack-NOVA-Installer-Script/master/nova-install. A copy of this attached with this mail in the Attachments.ZIP file. 3.Run the script. a.sudo chmod 777 nova-install (Give executable permission to the script) b.sudo bash nova-install -t cloud(Run the script) The script will ask for various details during the installation period. Following is the sample that we used. Cloud Controller host IP address [10.207.230.122]: 127.0.0.1 S3 host IP address [127.0.0.1]: 127.0.0.1 RabbitMQ host IP address [127.0.0.1]: 127.0.0.1 MySQL host IP address [127.0.0.1]: 127.0.0.1 Desired MySQL root password Enter this machine's IP address [10.207.230.122]: 10.207.230.122 Enter this machine's broadcast address [10.207.231.255]: 10.207.231.255 Enter this machine's netmask [255.255.252.0]: 255.255.252.0 Enter this machine's gateway [10.207.228.1]: 10.207.228.1 Enter this machine's DNS nameserver address [10.201.50.100]: 10.201.50.100 Network range for ALL projects (normally x.x.x.x/12): 128.88.146.0/24 Total amount of usable IPs for ALL projects: 255 User name for the project administrator: admin Name for the project: cloud Desired network range for the 'cloud' project (normally x.x.x.x/24): 128.88.146.0/24 How many networks for the 'cloud' project: 1 How many available IPs per 'cloud' project network: 255 Once these inputs are provided openstack will be installed the machine and cloud is ready for use. 4.Edit network settings in the file /etc/network/interfaces. This is to ensure we are able to ping the machine from the instances launched through openstack. Ensure that you are including the proper values here. This is just the way we have implemented. # The loopback network interface auto lo iface lo inet loopback auto eth1 auto eth0 iface eth0 inet static address XXX netmask broadcast XX gateway XXX dns-nameservers X 5.Add the below lines in /etc/nova/nova.conf --network_manager=nova.network.manager.FlatDHCPManager --flat_network_dhcp_start=128.88.146.2 --flat_interface=eth0 --network_host=127.0.0.1 --quota_cores=20 --quota_instances=20 --connection_type=vmwareapi --vmwareapi_host_ip=ESX hypervisor machine IP --vmwareapi_host_username= ESX hypervisor username --vmwareapi_host_password= ESX hypervisor password --vmwareapi_wsdl_loc=http://127.0.0.1:8080/wsdl/vim25/vimService.wsdl --glance_api_servers=127.0.0.1:9292 --image_service=nova.image.glance.GlanceImageService 6.Change the /root/creds/novarc file. The entries for EC2_URL, S3_URL and NOVA_URL should be changed from the IP of the machine to 127.0.0.1. 7.Register an image with glance using the below command: glance --verbose add name=Ubuntu is_public=true /root/Ubuntu11-04-flat.vmdk This command will generate the ami id (ami-0001) which will be used for launching instances. 8.Generate the keypair using the command: euca-add-keypair first openstack.pem ; chmod 600 openstack.pem Now we have completed setting up Openstack. We can go ahead and launch instances using the command: euca-run-instances -k first -t m1.tiny ami-0001 Thanks. Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not
Re: [Openstack] No official Diablo 2011.3.1 for oneiric?
I've been testing some versions and decided to use ubuntu packages because the same concerns you've mentioned. But, I reached a point where I can't instantiate more than 16 virtual machines. There are a lot of changes in the network component that fix this problem but I've checked they weren't applied to the code of the distributed packages. I really hope this situation changes in 12.04 LTS Server. I'm in the same situation as you! Cheers. On Thu, Apr 5, 2012 at 6:47 AM, Thierry Carrez thie...@openstack.orgwrote: Philipp Wollermann wrote: am I right, that the official packages of openstack (nova) for Ubuntu 11.10 (oneiric) were never updated to Diablo 2011.3.1 and no bug-fixes from after the initial release were ever included? I checked the change log of the nova packages, and it seems like the maintainers only fixed security issues. The stable/diablo branches, and the resulting 2011.3.1 release, are a cross-distro effort to maintain a stable version of past releases. Each distribution of OpenStack follows its own rules on what patches it backports, in the case of Ubuntu itself, it follows: https://wiki.ubuntu.com/StableReleaseUpdates -- 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 -- - MSc. Correa, J.L. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] OpenStack 2012.1 (Essex) is RELEASED !
Hello everyone, I'm very happy to announce the immediate release of OpenStack 2012.1 (code-named Essex). This coordinated release contains 5 components: OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/2012.1 OpenStack Object Storage (Swift) 1.4.8: https://launchpad.net/swift/essex/1.4.8 OpenStack Image Service (Glance) 2012.1: https://launchpad.net/glance/essex/2012.1 OpenStack Identity (Keystone) 2012.1: https://launchpad.net/keystone/essex/2012.1 OpenStack Dashboard (Horizon) 2012.1: https://launchpad.net/horizon/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. You are strongly encouraged to read the Release Notes at: http://wiki.openstack.org/ReleaseNotes/Essex Enjoy! -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack 2012.1 (Essex) is RELEASED !
Nicely done! Congratulations, everyone!!! d On Thu, Apr 5, 2012 at 10:52 AM, Thierry Carrez thie...@openstack.org wrote: Hello everyone, I'm very happy to announce the immediate release of OpenStack 2012.1 (code-named Essex). This coordinated release contains 5 components: OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/2012.1 OpenStack Object Storage (Swift) 1.4.8: https://launchpad.net/swift/essex/1.4.8 OpenStack Image Service (Glance) 2012.1: https://launchpad.net/glance/essex/2012.1 OpenStack Identity (Keystone) 2012.1: https://launchpad.net/keystone/essex/2012.1 OpenStack Dashboard (Horizon) 2012.1: https://launchpad.net/horizon/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. You are strongly encouraged to read the Release Notes at: http://wiki.openstack.org/ReleaseNotes/Essex Enjoy! -- 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
[Openstack] where nova-compute runs: KVM vs Xen
Right now, if you use KVM via libvirt (the default case), on the compute node, nova-compute runs on the host. If you use Xen via xenapi, nova-compute runs on Dom-U. (I'll ignore Xen via libvirt since no one really uses it.) What's the fundamental design decision to make the distinction? Presumably, it is not *that* hard to run nova-compute in a KVM VM, since the libvirt control socket works on tcp. I can see updating iptables rules would be painful but shouldn't we have the same problem with Xen? Conversely, it's also not impossible to run nova-compute in Dom-0. I understand running something in a VM is more secure in some sense than running in Dom0. But shouldn't the same argument apply to KVM's case as well? Your input is appreciated. Thanks, Yun ___ 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 2012.1 (Essex) is RELEASED !
Congrats everybody for the great work.
Nuage Co - Razique Mahrouarazique.mahr...@gmail.com
Le 5 avr. 2012 à 17:02, Duncan McGreggor a écrit :Nicely done!Congratulations, everyone!!!dOn Thu, Apr 5, 2012 at 10:52 AM, Thierry Carrez thie...@openstack.org wrote:Hello everyone,I'm very happy to announce the immediate release of OpenStack 2012.1(code-named "Essex"). This coordinated release contains 5 components:OpenStack Compute ("Nova") 2012.1:https://launchpad.net/nova/essex/2012.1OpenStack Object Storage ("Swift") 1.4.8:https://launchpad.net/swift/essex/1.4.8OpenStack Image Service ("Glance") 2012.1:https://launchpad.net/glance/essex/2012.1OpenStack Identity ("Keystone") 2012.1:https://launchpad.net/keystone/essex/2012.1OpenStack Dashboard ("Horizon") 2012.1:https://launchpad.net/horizon/essex/2012.1You can find tarballs for download, as well as comprehensive lists offeatures and bugfixes, at the URLs above.You are strongly encouraged to read the Release Notes at:http://wiki.openstack.org/ReleaseNotes/EssexEnjoy!--Thierry Carrez (ttx)Release Manager, OpenStack___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help : https://help.launchpad.net/ListHelp___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore 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 2012.1 (Essex) is RELEASED !
w00t! On Thu, Apr 5, 2012 at 8:02 AM, Duncan McGreggor dun...@dreamhost.com wrote: Nicely done! Congratulations, everyone!!! d On Thu, Apr 5, 2012 at 10:52 AM, Thierry Carrez thie...@openstack.org wrote: Hello everyone, I'm very happy to announce the immediate release of OpenStack 2012.1 (code-named Essex). This coordinated release contains 5 components: OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/2012.1 OpenStack Object Storage (Swift) 1.4.8: https://launchpad.net/swift/essex/1.4.8 OpenStack Image Service (Glance) 2012.1: https://launchpad.net/glance/essex/2012.1 OpenStack Identity (Keystone) 2012.1: https://launchpad.net/keystone/essex/2012.1 OpenStack Dashboard (Horizon) 2012.1: https://launchpad.net/horizon/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. You are strongly encouraged to read the Release Notes at: http://wiki.openstack.org/ReleaseNotes/Essex Enjoy! -- 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 -- -- @lloyddewolf http://www.pistoncloud.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
[Openstack] Quantum and Melange 2012.1 (Essex) are out
Hello everyone, We also had two projects in incubation during the Essex timeframe: Melange and Quantum. They were both released today: Melange 2012.1: https://launchpad.net/melange/essex/2012.1 Quantum 2012.1: https://launchpad.net/quantum/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. Note that Quantum was promoted to Core project status and will be an integral part of the future Folsom release. Cheers, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack 2012.1 (Essex) is RELEASED !
great, thanks 2012/4/5 Razique Mahroua razique.mahr...@gmail.com Congrats everybody for the great work. *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 5 avr. 2012 à 17:02, Duncan McGreggor a écrit : Nicely done! Congratulations, everyone!!! d On Thu, Apr 5, 2012 at 10:52 AM, Thierry Carrez thie...@openstack.org wrote: Hello everyone, I'm very happy to announce the immediate release of OpenStack 2012.1 (code-named Essex). This coordinated release contains 5 components: OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/2012.1 OpenStack Object Storage (Swift) 1.4.8: https://launchpad.net/swift/essex/1.4.8 OpenStack Image Service (Glance) 2012.1: https://launchpad.net/glance/essex/2012.1 OpenStack Identity (Keystone) 2012.1: https://launchpad.net/keystone/essex/2012.1 OpenStack Dashboard (Horizon) 2012.1: https://launchpad.net/horizon/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. You are strongly encouraged to read the Release Notes at: http://wiki.openstack.org/ReleaseNotes/Essex Enjoy! -- 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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- 彭勇 (Peng Yong) 常州贝特康姆(BitComm)软件技术有限公司 地址：常州市科教城信息产业园南4楼 电话：+86.519.68887168 传真：+86.519.68887169 手机：+86.18915883399 邮箱：p...@pubyun.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] python-glanceclient
We should definitely push to consolidate common code for clients! We can use either glanceclient or quantumclient as a prototype. As for the auth code specifically, it can be replaced with something as simple as this: https://github.com/openstack/python-glanceclient/blob/master/glanceclient/shell.py#L119 On Apr 4, 2012, at 9:11 AM, Dan Wendlandt wrote: Very cool guys! We'll be reworking the Quantum client in a similar alignment effort during Folsom. One question to that end: is there any effort to get much of the code that will be common across all OpenStack python-*client projects into something like openstack-common (or an openstack-client-common)? It seems like much of what is in https://github.com/openstack/python-glanceclient/tree/master/glanceclient/common would be useful across all projects. The same could likely be said for the basic keystone code required by a client (e.g., https://github.com/openstack/python-novaclient/blob/master/novaclient/service_catalog.py). Thanks, Dan On Tue, Apr 3, 2012 at 8:39 PM, Brian Waldon brian.wal...@rackspace.com wrote: In an effort to further align OpenStack API clients, Jay Pipes, Monty Taylor and myself have set up the python-glanceclient project. It is not intended to be a drop-in replacement for the existing client that lives in Glance, but a complete rewrite with a shiny new interface that maintains feature-parity. As for integrating this new client with the necessary OpenStack projects, here's a little roadmap I came up with: X 1) Basic functionality X 2) Integrate with Gerrit 3) Verify feature parity 4) Integrate with DevStack 5) Integrate with Nova 6) Drop old client from Glance If anybody is interested in playing with the new client, here it is: https://github.com/openstack/python-glanceclient. You can either yell at me or use Gerrit to fix anything I may have overlooked. Thanks! Brian Waldon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack 2012.1 (Essex) is RELEASED !
Congratulations!! 5 core services and counting. It's now a real stack. On 4/5/12 9:52 AM, Thierry Carrez thie...@openstack.org wrote: Hello everyone, I'm very happy to announce the immediate release of OpenStack 2012.1 (code-named Essex). This coordinated release contains 5 components: OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/2012.1 OpenStack Object Storage (Swift) 1.4.8: https://launchpad.net/swift/essex/1.4.8 OpenStack Image Service (Glance) 2012.1: https://launchpad.net/glance/essex/2012.1 OpenStack Identity (Keystone) 2012.1: https://launchpad.net/keystone/essex/2012.1 OpenStack Dashboard (Horizon) 2012.1: https://launchpad.net/horizon/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. You are strongly encouraged to read the Release Notes at: http://wiki.openstack.org/ReleaseNotes/Essex Enjoy! -- 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] OpenStack 2012.1 (Essex) is RELEASED !
Congrats and thank you to everyone involved! On 4/5/12 10:30 AM, Lloyd Dewolf lloydost...@gmail.com wrote: w00t! On Thu, Apr 5, 2012 at 8:02 AM, Duncan McGreggor dun...@dreamhost.com wrote: Nicely done! Congratulations, everyone!!! d On Thu, Apr 5, 2012 at 10:52 AM, Thierry Carrez thie...@openstack.org wrote: Hello everyone, I'm very happy to announce the immediate release of OpenStack 2012.1 (code-named Essex). This coordinated release contains 5 components: OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/2012.1 OpenStack Object Storage (Swift) 1.4.8: https://launchpad.net/swift/essex/1.4.8 OpenStack Image Service (Glance) 2012.1: https://launchpad.net/glance/essex/2012.1 OpenStack Identity (Keystone) 2012.1: https://launchpad.net/keystone/essex/2012.1 OpenStack Dashboard (Horizon) 2012.1: https://launchpad.net/horizon/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. You are strongly encouraged to read the Release Notes at: http://wiki.openstack.org/ReleaseNotes/Essex Enjoy! -- 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 -- -- @lloyddewolf http://www.pistoncloud.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 ___ 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] where nova-compute runs: KVM vs Xen
On Apr 5, 2012, at 10:06 AM, Yun Mao wrote: Right now, if you use KVM via libvirt (the default case), on the compute node, nova-compute runs on the host. If you use Xen via xenapi, nova-compute runs on Dom-U. (I'll ignore Xen via libvirt since no one really uses it.) What's the fundamental design decision to make the distinction? Presumably, it is not *that* hard to run nova-compute in a KVM VM, since the libvirt control socket works on tcp. I can see updating iptables rules would be painful but shouldn't we have the same problem with Xen? Conversely, it's also not impossible to run nova-compute in Dom-0. I understand running something in a VM is more secure in some sense than running in Dom0. But shouldn't the same argument apply to KVM's case as well? Running compute on the host for KVM is the simpler solution, there is less to manage. We run compute on a DomU on XenServer because on XenServer the Dom0 is basically an appliance VM itself, and it has issues like an ancient version of python (2.4), and the Dom0 being resource restricted. We *could* change that, but the point of XenServer is that it's basically an appliance, and is easier to manage/upgrade, etc if left as-is. Also, using a utility VM for compute lets you do things like upgrading compute by just deploying a new VM image (and as mentioned above, it isolates the Dom0 from compute. If nova-compute runs away and eats all of the ram/disk/cpu, it won't take down the host.) Now, this is relevant to current versions of XenServer. Future versions, or XCP, may be a whole nother ball o' wax. Your input is appreciated. Thanks, Yun ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Monsyne M. Dragon OpenStack/Nova cell 210-441-0965 work x 5014190 ___ 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] regarding 3-Minute OpenStack Survey
Hello together. First of all: Essex is out.. yeah :) I received a mail from dimensionalresearch.com with the subject 3-Minute OpenStack Survey containing the attached text a few minutes ago. It's signed with The OpenStack Team (who is that?) and it's named OpenStack Community Survey. Is this an official request of the OpenStack project initiated by the board? If so: I would really like to see that you write a short announcement before sending requests to participate in a survey. Also I want to now what you'll exactly do with the collected data and if the data will be published after finishing the survey. Bye, Christian. ---snip--- Hello OpenStack Supporter, We would like to invite you to complete a brief survey on your involvement with OpenStack. Your participation in this survey will help us understand the impact of OpenStack on the job market. We will share the findings of this survey with all participants. Responses to this survey will be used only for the purpose of this report and all individual answers will be kept strictly confidential. This survey is sponsored by OpenStack and conducted by Dimensional Research. If you are not the correct person at your company to answer this type of survey, please forward this email to the appropriate contact. Thank you! The OpenStack Team ---snap--- -- Christian Berendt Solution Architect Mail: bere...@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 ___ 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 2012.1 (Essex) is RELEASED !
F*** YEAH! Congrats and thanks to all , this is an awesome release guys ! Lean On Thu, Apr 5, 2012 at 1:13 PM, Jim Curry jim.cu...@rackspace.com wrote: Congrats and thank you to everyone involved! On 4/5/12 10:30 AM, Lloyd Dewolf lloydost...@gmail.com wrote: w00t! On Thu, Apr 5, 2012 at 8:02 AM, Duncan McGreggor dun...@dreamhost.com wrote: Nicely done! Congratulations, everyone!!! d On Thu, Apr 5, 2012 at 10:52 AM, Thierry Carrez thie...@openstack.org wrote: Hello everyone, I'm very happy to announce the immediate release of OpenStack 2012.1 (code-named Essex). This coordinated release contains 5 components: OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/2012.1 OpenStack Object Storage (Swift) 1.4.8: https://launchpad.net/swift/essex/1.4.8 OpenStack Image Service (Glance) 2012.1: https://launchpad.net/glance/essex/2012.1 OpenStack Identity (Keystone) 2012.1: https://launchpad.net/keystone/essex/2012.1 OpenStack Dashboard (Horizon) 2012.1: https://launchpad.net/horizon/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. You are strongly encouraged to read the Release Notes at: http://wiki.openstack.org/ReleaseNotes/Essex Enjoy! -- 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 -- -- @lloyddewolf http://www.pistoncloud.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 ___ 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 2012.1 (Essex) is RELEASED !
Congrats :) Thanks, Kiall On Thu, Apr 5, 2012 at 3:52 PM, Thierry Carrez thie...@openstack.orgwrote: Hello everyone, I'm very happy to announce the immediate release of OpenStack 2012.1 (code-named Essex). This coordinated release contains 5 components: OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/2012.1 OpenStack Object Storage (Swift) 1.4.8: https://launchpad.net/swift/essex/1.4.8 OpenStack Image Service (Glance) 2012.1: https://launchpad.net/glance/essex/2012.1 OpenStack Identity (Keystone) 2012.1: https://launchpad.net/keystone/essex/2012.1 OpenStack Dashboard (Horizon) 2012.1: https://launchpad.net/horizon/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. You are strongly encouraged to read the Release Notes at: http://wiki.openstack.org/ReleaseNotes/Essex Enjoy! -- 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] OpenStack 2012.1 (Essex) is RELEASED !
Congratulations to everyone in the OpenStack community for achieving this milestone! John -Original Message- From: openstack-bounces+john=openstack@lists.launchpad.net [mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf Of Thierry Carrez Sent: Thursday, April 05, 2012 9:52 AM To: openstack@lists.launchpad.net Subject: [Openstack] OpenStack 2012.1 (Essex) is RELEASED ! Hello everyone, I'm very happy to announce the immediate release of OpenStack 2012.1 (code-named Essex). This coordinated release contains 5 components: OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/2012.1 OpenStack Object Storage (Swift) 1.4.8: https://launchpad.net/swift/essex/1.4.8 OpenStack Image Service (Glance) 2012.1: https://launchpad.net/glance/essex/2012.1 OpenStack Identity (Keystone) 2012.1: https://launchpad.net/keystone/essex/2012.1 OpenStack Dashboard (Horizon) 2012.1: https://launchpad.net/horizon/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. You are strongly encouraged to read the Release Notes at: http://wiki.openstack.org/ReleaseNotes/Essex Enjoy! -- 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] OpenStack 2012.1 (Essex) is RELEASED !
Hi, We have packages available for Ubuntu Precise 12.04 now as well. Regards chuck On Thu, 5 Apr 2012 16:13:12 + Jim Curry jim.cu...@rackspace.com wrote: Congrats and thank you to everyone involved! On 4/5/12 10:30 AM, Lloyd Dewolf lloydost...@gmail.com wrote: w00t! On Thu, Apr 5, 2012 at 8:02 AM, Duncan McGreggor dun...@dreamhost.com wrote: Nicely done! Congratulations, everyone!!! d On Thu, Apr 5, 2012 at 10:52 AM, Thierry Carrez thie...@openstack.org wrote: Hello everyone, I'm very happy to announce the immediate release of OpenStack 2012.1 (code-named Essex). This coordinated release contains 5 components: OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/2012.1 OpenStack Object Storage (Swift) 1.4.8: https://launchpad.net/swift/essex/1.4.8 OpenStack Image Service (Glance) 2012.1: https://launchpad.net/glance/essex/2012.1 OpenStack Identity (Keystone) 2012.1: https://launchpad.net/keystone/essex/2012.1 OpenStack Dashboard (Horizon) 2012.1: https://launchpad.net/horizon/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. You are strongly encouraged to read the Release Notes at: http://wiki.openstack.org/ReleaseNotes/Essex Enjoy! -- 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 -- -- @lloyddewolf http://www.pistoncloud.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 ___ 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] python-glanceclient
I think Dean Troyer was going to take an even farther stance at the Summit. A unified client for all the core projects (and OpenStack client) instead of the proliferation of separate clients that we have. As we got into really testing the Essex release these past weeks, it because pretty clear to me that the user experience of working with nova, glance, and keystone (sorry Dan, I wasn't trying to through Quantum in the mix too at the time) - was definitely working with totally separate projects. On top of which is required some pretty deep knowledge of how and where things tied in to use those clients effectively (i..e don't use nova project list, use keystone tenant-list. These all made sense while focused on the individual projects, but make for a confusing proliferation of tools needed to deploy, run and use OpenStack. OpenStack would be well served to consolidate the clients, or at the very least drive further against the ideas started in http://wiki.openstack.org/UnifiedCLI to make the command structure, responses, and options available in clients consistent. For horizon, just having python libraries that don't require the entire back-end of a system to be installed was necessary, so the proliferation didn't matter that much. We are evolving beyond that now. -joe On Apr 5, 2012, at 9:04 AM, Brian Waldon wrote: We should definitely push to consolidate common code for clients! We can use either glanceclient or quantumclient as a prototype. As for the auth code specifically, it can be replaced with something as simple as this: https://github.com/openstack/python-glanceclient/blob/master/glanceclient/shell.py#L119 On Apr 4, 2012, at 9:11 AM, Dan Wendlandt wrote: Very cool guys! We'll be reworking the Quantum client in a similar alignment effort during Folsom. One question to that end: is there any effort to get much of the code that will be common across all OpenStack python-*client projects into something like openstack-common (or an openstack-client-common)? It seems like much of what is in https://github.com/openstack/python-glanceclient/tree/master/glanceclient/common would be useful across all projects. The same could likely be said for the basic keystone code required by a client (e.g., https://github.com/openstack/python-novaclient/blob/master/novaclient/service_catalog.py). Thanks, Dan On Tue, Apr 3, 2012 at 8:39 PM, Brian Waldon brian.wal...@rackspace.com wrote: In an effort to further align OpenStack API clients, Jay Pipes, Monty Taylor and myself have set up the python-glanceclient project. It is not intended to be a drop-in replacement for the existing client that lives in Glance, but a complete rewrite with a shiny new interface that maintains feature-parity. As for integrating this new client with the necessary OpenStack projects, here's a little roadmap I came up with: X 1) Basic functionality X 2) Integrate with Gerrit 3) Verify feature parity 4) Integrate with DevStack 5) Integrate with Nova 6) Drop old client from Glance If anybody is interested in playing with the new client, here it is: https://github.com/openstack/python-glanceclient. You can either yell at me or use Gerrit to fix anything I may have overlooked. Thanks! Brian Waldon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ 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 2012.1 (Essex) is RELEASED !
Awesome.. when will this his the Ubuntu Server dailies for 12.04? On Thu, Apr 5, 2012 at 9:43 AM, John Purrier j...@openstack.org wrote: Congratulations to everyone in the OpenStack community for achieving this milestone! John -Original Message- From: openstack-bounces+john=openstack@lists.launchpad.net [mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf Of Thierry Carrez Sent: Thursday, April 05, 2012 9:52 AM To: openstack@lists.launchpad.net Subject: [Openstack] OpenStack 2012.1 (Essex) is RELEASED ! Hello everyone, I'm very happy to announce the immediate release of OpenStack 2012.1 (code-named Essex). This coordinated release contains 5 components: OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/2012.1 OpenStack Object Storage (Swift) 1.4.8: https://launchpad.net/swift/essex/1.4.8 OpenStack Image Service (Glance) 2012.1: https://launchpad.net/glance/essex/2012.1 OpenStack Identity (Keystone) 2012.1: https://launchpad.net/keystone/essex/2012.1 OpenStack Dashboard (Horizon) 2012.1: https://launchpad.net/horizon/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. You are strongly encouraged to read the Release Notes at: http://wiki.openstack.org/ReleaseNotes/Essex Enjoy! -- 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 -- -- Michael F. March - mma...@gmail.com Ph: (415) 894-9269 Fax: (602)296-0400 Twitter: cowmix -- Skype: Cowmix ___ 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 2012.1 (Essex) is RELEASED !
Wot! 2012/4/5 Chuck Short chuck.sh...@canonical.com: Hi, We have packages available for Ubuntu Precise 12.04 now as well. Regards chuck On Thu, 5 Apr 2012 16:13:12 + Jim Curry jim.cu...@rackspace.com wrote: Congrats and thank you to everyone involved! On 4/5/12 10:30 AM, Lloyd Dewolf lloydost...@gmail.com wrote: w00t! On Thu, Apr 5, 2012 at 8:02 AM, Duncan McGreggor dun...@dreamhost.com wrote: Nicely done! Congratulations, everyone!!! d On Thu, Apr 5, 2012 at 10:52 AM, Thierry Carrez thie...@openstack.org wrote: Hello everyone, I'm very happy to announce the immediate release of OpenStack 2012.1 (code-named Essex). This coordinated release contains 5 components: OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/2012.1 OpenStack Object Storage (Swift) 1.4.8: https://launchpad.net/swift/essex/1.4.8 OpenStack Image Service (Glance) 2012.1: https://launchpad.net/glance/essex/2012.1 OpenStack Identity (Keystone) 2012.1: https://launchpad.net/keystone/essex/2012.1 OpenStack Dashboard (Horizon) 2012.1: https://launchpad.net/horizon/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. You are strongly encouraged to read the Release Notes at: http://wiki.openstack.org/ReleaseNotes/Essex Enjoy! -- 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 -- -- @lloyddewolf http://www.pistoncloud.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 ___ 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 immaturity
+ ? On 4/5/12 9:43 AM, Jay Pipes jaypi...@gmail.com wrote: +1. On 04/04/2012 04:20 PM, David Kranz wrote: +1000 I believe the nova team should make backporting essential bugs to a stable essex base and dealing with the upgrade issue the highest priority for the start (at least) of the Folsom cycle. We need people to deploy real systems using Essex. With regard to smooth upgrades, they won't happen if the issue is always punted to the end of a release cycle. The way to do this is to create a test very early in Folsom that demonstrates how a real large-scale style deployment can be upgraded to a new version containing no code changes. Any future change that breaks that test must be evaluated to compare the value of the change against whatever upgrade pain will be caused. In terms of real deployments, this issue scares me more than the fact that there are bugs. There will always be bugs. But we can't have it be tricky and risky to deploy the fixes. -David On 4/4/2012 2:30 PM, Tim Bell wrote: Essex is a key release in this respect. With the excellent work done by the developers, testers and packaging teams, OpenStack is much better positioned than with Diablo. As the work proceeds on Folsom, back porting critical bugs and planning for a smooth migration path for production sites will become factors in keeping the early adopters enthusiastic. These are the user stories that will drive the next wave of OpenStack growth as much as expanding the feature set. Tim Bell CERN ___ 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] python-glanceclient
Hi Joe, I've often had a similar thought myself of whether a single 'osclient' would be better. I see consistency across all clients as the bare minimum, and a single client as an interesting option to explore. Thanks for driving this Dean, I look forward to talking about it at the summit. Dan On Thu, Apr 5, 2012 at 10:08 AM, Joseph Heck he...@me.com wrote: I think Dean Troyer was going to take an even farther stance at the Summit. A unified client for all the core projects (and OpenStack client) instead of the proliferation of separate clients that we have. As we got into really testing the Essex release these past weeks, it because pretty clear to me that the user experience of working with nova, glance, and keystone (sorry Dan, I wasn't trying to through Quantum in the mix too at the time) - was definitely working with totally separate projects. On top of which is required some pretty deep knowledge of how and where things tied in to use those clients effectively (i..e don't use nova project list, use keystone tenant-list. These all made sense while focused on the individual projects, but make for a confusing proliferation of tools needed to deploy, run and use OpenStack. OpenStack would be well served to consolidate the clients, or at the very least drive further against the ideas started in http://wiki.openstack.org/UnifiedCLI to make the command structure, responses, and options available in clients consistent. For horizon, just having python libraries that don't require the entire back-end of a system to be installed was necessary, so the proliferation didn't matter that much. We are evolving beyond that now. -joe On Apr 5, 2012, at 9:04 AM, Brian Waldon wrote: We should definitely push to consolidate common code for clients! We can use either glanceclient or quantumclient as a prototype. As for the auth code specifically, it can be replaced with something as simple as this: https://github.com/openstack/python-glanceclient/blob/master/glanceclient/shell.py#L119 On Apr 4, 2012, at 9:11 AM, Dan Wendlandt wrote: Very cool guys! We'll be reworking the Quantum client in a similar alignment effort during Folsom. One question to that end: is there any effort to get much of the code that will be common across all OpenStack python-*client projects into something like openstack-common (or an openstack-client-common)? It seems like much of what is in https://github.com/openstack/python-glanceclient/tree/master/glanceclient/commonwould be useful across all projects. The same could likely be said for the basic keystone code required by a client (e.g., https://github.com/openstack/python-novaclient/blob/master/novaclient/service_catalog.py). Thanks, Dan On Tue, Apr 3, 2012 at 8:39 PM, Brian Waldon brian.wal...@rackspace.comwrote: In an effort to further align OpenStack API clients, Jay Pipes, Monty Taylor and myself have set up the python-glanceclient project. It is not intended to be a drop-in replacement for the existing client that lives in Glance, but a complete rewrite with a shiny new interface that maintains feature-parity. As for integrating this new client with the necessary OpenStack projects, here's a little roadmap I came up with: X 1) Basic functionality X 2) Integrate with Gerrit 3) Verify feature parity 4) Integrate with DevStack 5) Integrate with Nova 6) Drop old client from Glance If anybody is interested in playing with the new client, here it is: https://github.com/openstack/python-glanceclient. You can either yell at me or use Gerrit to fix anything I may have overlooked. Thanks! Brian Waldon ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira Networks: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- ~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] OpenStack 2012.1 (Essex) is RELEASED !
Congratulations! There is a list of all people that participated to the development of 2012.1 in the Essex Hall Of Fame: http://www.openstack.org/blog/2012/04/openstack-essex-hall-of-fame/ /stef On Thu, 2012-04-05 at 16:52 +0200, Thierry Carrez wrote: Hello everyone, I'm very happy to announce the immediate release of OpenStack 2012.1 (code-named Essex). This coordinated release contains 5 components: OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/2012.1 OpenStack Object Storage (Swift) 1.4.8: https://launchpad.net/swift/essex/1.4.8 OpenStack Image Service (Glance) 2012.1: https://launchpad.net/glance/essex/2012.1 OpenStack Identity (Keystone) 2012.1: https://launchpad.net/keystone/essex/2012.1 OpenStack Dashboard (Horizon) 2012.1: https://launchpad.net/horizon/essex/2012.1 You can find tarballs for download, as well as comprehensive lists of features and bugfixes, at the URLs above. You are strongly encouraged to read the Release Notes at: http://wiki.openstack.org/ReleaseNotes/Essex Enjoy! ___ 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] Using glance to upload/add??
Hi all, I was looking at the glance add command and I am trying to figure out how to use it to upload images to locations other than the default_store = file How does one go about telling it which store should be used. It seems like there is a location option, but that is the fully specified location, and I am unsure about that since the function that eventually gets called in these storage objects doesn't have/receive that. def add(self, image_id, image_file, image_size): Is it expected that people will only add to locations that use the default_store? Might be nice to actually be able to specify that, and resort to the default_store if its not provided (thus the reason its called default). Thx! -Josh ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [Nova-Orchestration] Nova-Orchestration proposal - review request
Vish, Could you please review our session proposal for Nova-Orchestration (http://summit.openstack.org/sessions/view/69)? This would help us fill in the gaps before the summit. Thanks, -Sriram ___ 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 glance to upload/add??
Heya! Answers inline. :)
On 04/05/2012 02:38 PM, Joshua Harlow wrote:
Hi all,
I was looking at the glance add command and I am trying to figure out
how to use it to upload images to locations other than the
“default_store = file”
How does one go about telling it which store should be used.
You can pass the X-Image-Meta-Store: header to one of swift, s3, or
rds. Unfortunately, this is not supported in the glance CLI tool right
now. You could add a quick hack that adds the X-Image-Meta-Store header
to the features variable. Something like this git diff shows...
diff --git a/bin/glance b/bin/glance
index 9eb68ae..f298cce 100755
--- a/bin/glance
+++ b/bin/glance
@@ -228,6 +228,8 @@ EXAMPLES
'min_ram': fields.pop('min_ram', 0),
}
+alternate_store = fields.pop('store', None)
+
for format in ['disk_format', 'container_format']:
if format in fields:
image_meta[format] = fields.pop(format)
@@ -260,6 +262,9 @@ EXAMPLES
# otherwise error out
image_data = sys.stdin
+if alternate_store:
+features['X-Image-Meta-Store'] = alternate_store
+
# allow owner to be set when image is created
if 'owner' in fields.keys():
image_meta['owner'] = fields.pop('owner')
and try that :)
If it works out, feel free to contribute the patch to Glance ;)
It seems like there is a /location /option, but that is the fully
specified location, and I am unsure about that since the function that
eventually gets called in these storage objects doesn't have/receive that.
def add(self, image_id, image_file, image_size):
Is it expected that people will only add to locations that use the
default_store?
No, but it hasn't been something that users have clamoured for up until
now -- mostly because people standing up Glance are typically standing
it up with some default store and only storing images using that store.
But the plumbing is there to support this. as mentioned above.
Best,
-jay
Might be nice to actually be able to specify that, and resort to the
default_store if its not provided (thus the reason its called default).
Thx!
-Josh
___
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 glance to upload/add??
You got it.
Specifically...
https://github.com/openstack/glance/blob/master/glance/api/v1/images.py#L370
Best,
jay
On 04/05/2012 04:56 PM, Joshua Harlow wrote:
Cool, so glance internally does some lookup of ‘X-Image-Meta-Store’ and
this will over-ride the default_store?
-Josh
On 4/5/12 1:16 PM, Jay Pipes jaypi...@gmail.com wrote:
Heya! Answers inline. :)
On 04/05/2012 02:38 PM, Joshua Harlow wrote:
Hi all,
I was looking at the glance add command and I am trying to figure out
how to use it to upload images to locations other than the
“default_store = file”
How does one go about telling it which store should be used.
You can pass the X-Image-Meta-Store: header to one of swift, s3, or
rds. Unfortunately, this is not supported in the glance CLI tool right
now. You could add a quick hack that adds the X-Image-Meta-Store header
to the features variable. Something like this git diff shows...
diff --git a/bin/glance b/bin/glance
index 9eb68ae..f298cce 100755
--- a/bin/glance
+++ b/bin/glance
@@ -228,6 +228,8 @@ EXAMPLES
'min_ram': fields.pop('min_ram', 0),
}
+ alternate_store = fields.pop('store', None)
+
for format in ['disk_format', 'container_format']:
if format in fields:
image_meta[format] = fields.pop(format)
@@ -260,6 +262,9 @@ EXAMPLES
# otherwise error out
image_data = sys.stdin
+ if alternate_store:
+ features['X-Image-Meta-Store'] = alternate_store
+
# allow owner to be set when image is created
if 'owner' in fields.keys():
image_meta['owner'] = fields.pop('owner')
and try that :)
If it works out, feel free to contribute the patch to Glance ;)
It seems like there is a /location /option, but that is the fully
specified location, and I am unsure about that since the function that
eventually gets called in these storage objects doesn't
have/receive that.
def add(self, image_id, image_file, image_size):
Is it expected that people will only add to locations that use the
default_store?
No, but it hasn't been something that users have clamoured for up until
now -- mostly because people standing up Glance are typically standing
it up with some default store and only storing images using that store.
But the plumbing is there to support this. as mentioned above.
Best,
-jay
Might be nice to actually be able to specify that, and resort to the
default_store if its not provided (thus the reason its called
default).
Thx!
-Josh
___
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] can not start VM instance with specific image
I would try this again. 1. Delete all instances on the host. 2. Clean out the _base directory. 3. Restart nova-compute 4. Try to run the instance again. If that doesn't work, I would suspect a bad sector on your hard drive that is getting reused. Vish On Apr 5, 2012, at 2:43 AM, yuanke wei wrote: hi all, prob1: I deployed openstack on a 1controller+Ncompute basis. All the compute node seems work well and windows 2008 server image can be spawned successfully, except on one compute node, I encountered the following errors, can someone tell me what might be the problem?? after deleting all the files under _base dir, the error still there. if needed, further info can be provided 2012-04-05 09:30:03,874 DEBUG nova.rpc [-] Making asynchronous cast on network... from (pid=3068) cast /var/lib/nova/nova/rpc/impl_kombu.py:756 2012-04-05 09:30:03,932 ERROR nova.rpc [-] Exception during message handling (nova.rpc): TRACE: Traceback (most recent call last): (nova.rpc): TRACE: File /var/lib/nova/nova/rpc/impl_kombu.py, line 620, in _process_data (nova.rpc): TRACE: rval = node_func(context=ctxt, **node_args) (nova.rpc): TRACE: File /var/lib/nova/nova/exception.py, line 100, in wrapped (nova.rpc): TRACE: return f(*args, **kw) (nova.rpc): TRACE: File /var/lib/nova/nova/compute/manager.py, line 485, in run_instance (nova.rpc): TRACE: self._run_instance(context, instance_id, **kwargs) (nova.rpc): TRACE: File /var/lib/nova/nova/compute/manager.py, line 481, in _run_instance (nova.rpc): TRACE: _cleanup() (nova.rpc): TRACE: File /var/lib/nova/nova/compute/manager.py, line 406, in _cleanup (nova.rpc): TRACE: _deallocate_network() (nova.rpc): TRACE: File /usr/lib/python2.6/contextlib.py, line 23, in __exit__ (nova.rpc): TRACE: self.gen.next() (nova.rpc): TRACE: File /var/lib/nova/nova/compute/manager.py, line 459, in _run_instance (nova.rpc): TRACE: network_info, block_device_info) (nova.rpc): TRACE: File /var/lib/nova/nova/exception.py, line 100, in wrapped (nova.rpc): TRACE: return f(*args, **kw) (nova.rpc): TRACE: File /var/lib/nova/nova/virt/libvirt/connection.py, line 629, in spawn (nova.rpc): TRACE: block_device_info=block_device_info) (nova.rpc): TRACE: File /var/lib/nova/nova/virt/libvirt/connection.py, line 896, in _create_image (nova.rpc): TRACE: size=size) (nova.rpc): TRACE: File /var/lib/nova/nova/virt/libvirt/connection.py, line 788, in _cache_image (nova.rpc): TRACE: call_if_not_exists(base, fn, *args, **kwargs) (nova.rpc): TRACE: File /var/lib/nova/nova/utils.py, line 687, in inner (nova.rpc): TRACE: retval = f(*args, **kwargs) (nova.rpc): TRACE: File /var/lib/nova/nova/virt/libvirt/connection.py, line 786, in call_if_not_exists (nova.rpc): TRACE: fn(target=base, *args, **kwargs) (nova.rpc): TRACE: File /var/lib/nova/nova/virt/libvirt/connection.py, line 800, in _fetch_image (nova.rpc): TRACE: images.fetch_to_raw(context, image_id, target, user_id, project_id) (nova.rpc): TRACE: File /var/lib/nova/nova/virt/images.py, line 88, in fetch_to_raw (nova.rpc): TRACE: path_tmp, staged) (nova.rpc): TRACE: File /var/lib/nova/nova/utils.py, line 190, in execute (nova.rpc): TRACE: cmd=' '.join(cmd)) (nova.rpc): TRACE: ProcessExecutionError: Unexpected error while running command. (nova.rpc): TRACE: Command: qemu-img convert -O raw /var/lib/nova/instances/_base/bc33ea4e26e5e1af1408321416956113a4658763.part /var/lib/nova/instances/_base/bc33ea4e26e5e1af1408321416956113a4658763.converted (nova.rpc): TRACE: Exit code: 1 (nova.rpc): TRACE: Stdout: '' (nova.rpc): TRACE: Stderr: 'qemu-img: error while reading\n' (nova.rpc): TRACE: prob2: since the problem may be on the fact that the cached image on the compute node is broken, so how to force the compute node to abandon its local cached images and get from the remote image server??? simply deleting all the files under _base dir seems don't work, I see no data transfer between the compute node and the image server. thks in advance! - 韦远科 wei yuanke(wei) gtalk: weiyuanke...@gmail.com msn: weiyuanke...@hotmail.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 ___ 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] Java 7 File Provider for OpenStack Storage
Java 7 includes a pluggable filesystem abstraction, so I created a basic filesystem provider for Swift using the Java OpenStack bindings. It is available here: https://github.com/platformlayer/openstack-fileprovider If anyone is interested in using this, please let me know and I'll fix up any bugs you find! There's almost no documentation out there on how to do this, so I don't think any of the legacy clouds support this. Another small step forward for OpenStack! Justin --- Justin Santa Barbara Founder, FathomDB ___ 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] Melange Unittests
Can anyone enlighten me as to why the gate-melange-unittests-python26 job is only running a single test? The first time it ran it correctly found all 500+ tests but now it seems to be just running one. :( This is happening locally for me too and I'm not quite sure where the disconnect is. I don't see any obvious changes in the code between the good/bad test runs that might account for this discrepancy. Any pointing in the right direction would be appreciated! Good Run: https://jenkins.openstack.org/job/gate-melange-unittests-python26/1/console Bad Run: https://jenkins.openstack.org/job/gate-melange-unittests-python26/2/console Brian ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] No official Diablo 2011.3.1 for oneiric?
On Apr 5, 2012, at 18:47, Thierry Carrez wrote: Philipp Wollermann wrote: am I right, that the official packages of openstack (nova) for Ubuntu 11.10 (oneiric) were never updated to Diablo 2011.3.1 and no bug-fixes from after the initial release were ever included? I checked the change log of the nova packages, and it seems like the maintainers only fixed security issues. The stable/diablo branches, and the resulting 2011.3.1 release, are a cross-distro effort to maintain a stable version of past releases. Each distribution of OpenStack follows its own rules on what patches it backports, in the case of Ubuntu itself, it follows: https://wiki.ubuntu.com/StableReleaseUpdates Thank you for the explanation. I understand that some users would rather live with known unfixed bugs than the risk of introducing new ones through a fix and that this is the way Ubuntu handles updates to packages. However, I was wondering, because nova is already part of the SRU process, yet the latest version of nova in ubuntu-proposed is hanging in this state since 4 months. Even if it ever gets released to ubuntu-updates, it's probably outdated again. It's totally acceptable if Ubuntu chooses to handle their packages like this, providing a very stable and reliable base system - though as it is also the primary and kind of official platform for OpenStack deployments, I think it would be greatly appreciated if there would be an officially maintained PPA which contains the most up-to-date stable release of OpenStack for the latest version(s) of Ubuntu. Then, users themselves could choose whether to trust and track the official releases or stick to Ubuntu's releases. Best regards, -- Philipp Wollermann Infrastructure Engineer CyberAgent, Inc. (Tokyo) https://github.com/philwo ___ 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 immaturity
I've been giving this thread some thought and it dawned on my that we need to expand this page: http://openstack.org/user-stories/ Pretty much everyone featured on that page are 'big' organizations and there really isn't any detail on their experiences of trying to deploy (and maintain) Openstack. There's definitely not stories that a mid-range sized IT shop could related to. This lack of antidotal user experiences I think contributes the perceived immaturity of OpenStack. -- Michael F. March - mma...@gmail.com Ph: (415) 894-9269 Fax: (602)296-0400 Twitter: cowmix -- Skype: Cowmix ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Swift nee st code weirdness
Hi, All:
In the process of tinkering for lp:959221, I made a benign modification
to make it possible to invoke swift as a module, when everything broke
loose with errors like NameError: global name 'parser' is not defined.
Looking at the code it seems like a thinko, with the following fix:
diff --git a/bin/swift b/bin/swift
index 0cac5d6..a14c646 100755
--- a/bin/swift
+++ b/bin/swift
@@ -1202,7 +1203,7 @@ download --all OR download container [options] [object]
[object] ...
stdout.'''.strip('\n')
-def st_download(options, args, print_queue, error_queue):
+def st_download(parser, args, print_queue, error_queue):
parser.add_option('-a', '--all', action='store_true', dest='yes_all',
default=False, help='Indicates that you really want to download '
'everything in the account')
@@ -1378,7 +1379,7 @@ list [options] [container]
'''.strip('\n')
-def st_list(options, args, print_queue, error_queue):
+def st_list(parser, args, print_queue, error_queue):
parser.add_option('-p', '--prefix', dest='prefix', help='Will only list '
'items beginning with the prefix')
parser.add_option('-d', '--delimiter', dest='delimiter', help='Will roll '
@@ -1423,7 +1424,7 @@ stat [container] [object]
args given (if any).'''.strip('\n')
-def st_stat(options, args, print_queue, error_queue):
+def st_stat(parser, args, print_queue, error_queue):
(options, args) = parse_args(parser, args)
args = args[1:]
conn = get_conn(options)
@@ -1548,7 +1549,7 @@ post [options] [container] [object]
post -m Color:Blue -m Size:Large'''.strip('\n')
-def st_post(options, args, print_queue, error_queue):
+def st_post(parser, args, print_queue, error_queue):
parser.add_option('-r', '--read-acl', dest='read_acl', help='Sets the '
'Read ACL for containers. Quick summary of ACL syntax: .r:*, '
'.r:-.example.com, .r:www.example.com, account1, account2:user2')
@@ -1619,7 +1620,7 @@ upload [options] container file_or_directory
[file_or_directory] [...]
'''.strip('\n')
-def st_upload(options, args, print_queue, error_queue):
+def st_upload(parser, args, print_queue, error_queue):
parser.add_option('-c', '--changed', action='store_true', dest='changed',
default=False, help='Will only upload files that have changed since '
'the last upload')
Seems obvious if I look at this:
globals()['st_%s' % args[0]](parser, argv[1:], print_queue, error_queue)
The parser is always the first argument, so... Someone please tell me
if I am missing something here. Or should I just file it in Gerrit?
Weird part is, unit tests pass both on the current code and the one
with my patch above. The problem seems too gross to let it work, but
everything appears in order.
-- Pete
___
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] Melange Unittests
On Fri, 2012-04-06 at 00:04 +, Brian Lamar wrote: Can anyone enlighten me as to why the gate-melange-unittests-python26 job is only running a single test? The first time it ran it correctly found all 500+ tests but now it seems to be just running one. :( This is happening locally for me too and I'm not quite sure where the disconnect is. I don't see any obvious changes in the code between the good/bad test runs that might account for this discrepancy. Any pointing in the right direction would be appreciated! Good Run: https://jenkins.openstack.org/job/gate-melange-unittests-python26/1/console Bad Run: https://jenkins.openstack.org/job/gate-melange-unittests-python26/2/console I haven't looked at it at all, but my gut instinct is its another namespace issue. Try moving the tests directory out of the package's namespace into the root of the repo and see if it picks up the tests correctly there. Happy Hacking! 7-11 ___ 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] Melange Unittests
On 04/05/2012 07:12 PM, Jason Kölker wrote: On Fri, 2012-04-06 at 00:04 +, Brian Lamar wrote: Can anyone enlighten me as to why the gate-melange-unittests-python26 job is only running a single test? The first time it ran it correctly found all 500+ tests but now it seems to be just running one. :( This is happening locally for me too and I'm not quite sure where the disconnect is. I don't see any obvious changes in the code between the good/bad test runs that might account for this discrepancy. Any pointing in the right direction would be appreciated! If I run nosetests on a fresh checkout of master: $ nosetests test_config_file OK 0.00 /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/reflection.py:47: SAWarning: Did not recognize type 'BIGINT' of column 'allocatable_ip_counter' ret = fn(self, con, *args, **kw) /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/reflection.py:47: SAWarning: Did not recognize type 'BIGINT' of column 'address' ret = fn(self, con, *args, **kw) /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/reflection.py:47: SAWarning: Did not recognize type 'BIGINT' of column 'next_address' ret = fn(self, con, *args, **kw) -- Ran 1 test in 1.102s OK And an exit code of 0. If I disable the openstack nose plugin (edit setup.cfg) and re-run, I get this: $ nosetests ./home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/reflection.py:47: SAWarning: Did not recognize type 'BIGINT' of column 'allocatable_ip_counter' ret = fn(self, con, *args, **kw) /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/reflection.py:47: SAWarning: Did not recognize type 'BIGINT' of column 'address' ret = fn(self, con, *args, **kw) /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/reflection.py:47: SAWarning: Did not recognize type 'BIGINT' of column 'next_address' ret = fn(self, con, *args, **kw) EE == ERROR: test suite for module 'melange.tests.functional' from '/home/corvus/melange/melange/tests/functional/__init__.pyc' -- Traceback (most recent call last): File /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/nose/suite.py, line 208, in run self.setUp() File /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/nose/suite.py, line 291, in setUp self.setupContext(ancestor) File /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/nose/suite.py, line 314, in setupContext try_run(context, names) File /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/nose/util.py, line 478, in try_run return func() File /home/corvus/melange/melange/tests/functional/__init__.py, line 32, in setup db_api.db_reset(conf, db_based_ip_generator, db_based_mac_generator) File /home/corvus/melange/melange/db/sqlalchemy/api.py, line 259, in db_reset db_sync(options) File /home/corvus/melange/melange/db/sqlalchemy/api.py, line 246, in db_sync migration.db_sync(options, version, repo_path) File /home/corvus/melange/melange/db/sqlalchemy/migration.py, line 124, in db_sync upgrade(options, version=version, repo_path=repo_path) File /home/corvus/melange/melange/db/sqlalchemy/migration.py, line 66, in upgrade return versioning_api.upgrade(sql_connection, repo_path, version) File /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/migrate/versioning/api.py, line 186, in upgrade return _migrate(url, repository, version, upgrade=True, err=err, **opts) File string, line 2, in _migrate File /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/migrate/versioning/util/__init__.py, line 159, in with_engine return f(*a, **kw) File /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/migrate/versioning/api.py, line 366, in _migrate schema.runchange(ver, change, changeset.step) File /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/migrate/versioning/schema.py, line 91, in runchange change.run(self.engine, step) File /home/corvus/melange/.tox/py27/local/lib/python2.7/site-packages/migrate/versioning/script/py.py, line 145, in run script_func(engine) File /home/corvus/melange/melange/db/sqlalchemy/migrate_repo/versions/002_device_id_to_uuid.py, line 29, in upgrade _db_connect() File
Re: [Openstack] Swift nee st code weirdness
Pete,
There is clearly something interesting going on with scope. 'options',
which appears to really be 'parser' get passed in as a variable, but are
then gets over written before being used by the call using the global
'parser'.
(options, args) = parse_args(parser, args)
The history of the commands you run and the stacktrace from the errors/logs
might help.
What were you expecting/trying to do with the code change?
Most of that code looks like it was written by Greg Holt and/or Chuck Thier.
Hopefully they can shed more light on this by eyeballing the code than I
can.
On Thu, Apr 5, 2012 at 8:43 PM, Pete Zaitcev zait...@redhat.com wrote:
Hi, All:
In the process of tinkering for lp:959221, I made a benign modification
to make it possible to invoke swift as a module, when everything broke
loose with errors like NameError: global name 'parser' is not defined.
Looking at the code it seems like a thinko, with the following fix:
diff --git a/bin/swift b/bin/swift
index 0cac5d6..a14c646 100755
--- a/bin/swift
+++ b/bin/swift
@@ -1202,7 +1203,7 @@ download --all OR download container [options]
[object] [object] ...
stdout.'''.strip('\n')
-def st_download(options, args, print_queue, error_queue):
+def st_download(parser, args, print_queue, error_queue):
parser.add_option('-a', '--all', action='store_true', dest='yes_all',
default=False, help='Indicates that you really want to download '
'everything in the account')
@@ -1378,7 +1379,7 @@ list [options] [container]
'''.strip('\n')
-def st_list(options, args, print_queue, error_queue):
+def st_list(parser, args, print_queue, error_queue):
parser.add_option('-p', '--prefix', dest='prefix', help='Will only
list '
'items beginning with the prefix')
parser.add_option('-d', '--delimiter', dest='delimiter', help='Will
roll '
@@ -1423,7 +1424,7 @@ stat [container] [object]
args given (if any).'''.strip('\n')
-def st_stat(options, args, print_queue, error_queue):
+def st_stat(parser, args, print_queue, error_queue):
(options, args) = parse_args(parser, args)
args = args[1:]
conn = get_conn(options)
@@ -1548,7 +1549,7 @@ post [options] [container] [object]
post -m Color:Blue -m Size:Large'''.strip('\n')
-def st_post(options, args, print_queue, error_queue):
+def st_post(parser, args, print_queue, error_queue):
parser.add_option('-r', '--read-acl', dest='read_acl', help='Sets the '
'Read ACL for containers. Quick summary of ACL syntax: .r:*, '
'.r:-.example.com, .r:www.example.com, account1, account2:user2')
@@ -1619,7 +1620,7 @@ upload [options] container file_or_directory
[file_or_directory] [...]
'''.strip('\n')
-def st_upload(options, args, print_queue, error_queue):
+def st_upload(parser, args, print_queue, error_queue):
parser.add_option('-c', '--changed', action='store_true',
dest='changed',
default=False, help='Will only upload files that have changed
since '
'the last upload')
Seems obvious if I look at this:
globals()['st_%s' % args[0]](parser, argv[1:], print_queue, error_queue)
The parser is always the first argument, so... Someone please tell me
if I am missing something here. Or should I just file it in Gerrit?
Weird part is, unit tests pass both on the current code and the one
with my patch above. The problem seems too gross to let it work, but
everything appears in order.
-- Pete
___
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] [Ops] OpenStack and Operations: Input from the Wild
Interested in devops. Off the top of my head. live upgrades api queryable indications of cluster health api queryable cluster version and configuration info enabling monitoring as a first class concern in OpenStack (either as a cross cutting concern, or as it's own project) a framework for gathering and sharing performance benchmarks with architecture and configuration On Thu, Apr 5, 2012 at 1:52 PM, Duncan McGreggor dun...@dreamhost.comwrote: For anyone interested in DevOps, Ops, cloud hosting management, etc., there's a proposed session we could use your feedback on for topics of discussion: http://summit.openstack.org/sessions/view/57 Respond with your thoughts and ideas, and I'll be sure to add them to the list. Thanks! d ___ 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] Keypair injection failure should fail instance creation
Hi Vishy, While launching an instance if key-pair injection fails, still the instance comes up running. It is possible to change the administrator password for an instance by performing the 'changePassword' action, however the support is available in Xen but not in KVM. I am therefore inclined towards having the instance creation fail if key-pair injection fails. Please refer: https://bugs.launchpad.net/nova/+bug/967994 Launchpad answers: https://answers.launchpad.net/nova/+question/192108 Thanks Regards, Unmesh Gurjar | Lead Engineer | Vertex Software Private Ltd. | w. +91.20.6604.1500 x 379 | m. +91.9823.247.631 | unmesh.gur...@nttdata.commailto:unmesh.gur...@nttdata.com | Follow us on Twitter@NTTDATAAmericas __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding___ 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-poc] [Bug 915039] Re: flags.FLAGS( crashes bpython
** Changed in: nova
Milestone: essex-3 = 2012.1
--
You received this bug notification because you are a member of OpenStack
Common Drivers, which is the registrant for openstack-common.
https://bugs.launchpad.net/bugs/915039
Title:
flags.FLAGS( crashes bpython
Status in OpenStack Compute (Nova):
Fix Released
Status in openstack-common:
Fix Committed
Bug description:
Bpython tries to do some fancy stuff like lookup obj.__name__ and
check for AttributeError. The code in common/cfg.py has a special
getattr that raises a non AttributeError exception so it leads to a
crash and stack trace in bpython:
Traceback (most recent call last):
File /usr/local/share/python/bpython, line 9, in module
load_entry_point('bpython==0.10.1', 'console_scripts', 'bpython')()
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 1756, in main
banner=banner)
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 1658, in curses_wrapper
return func(stdscr, *args, **kwargs)
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 1727, in main_curses
clirepl.repl()
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 1015, in repl
inp = self.get_line()
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 600, in get_line
if self.p_key(key) is None:
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 911, in p_key
self.addstr(key)
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 290, in addstr
self.complete()
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/cli.py,
line 383, in complete
self.list_win_visible = repl.Repl.complete(self, tab)
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/repl.py,
line 540, in complete
if not self.get_args():
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/repl.py,
line 511, in get_args
self.argspec = inspection.getargspec(func, f)
File
/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages/bpython/inspection.py,
line 229, in getargspec
func_name = getattr(f, '__name__', None)
File nova/flags.py, line 114, in __getattr__
return getattr(self._conf, name)
File nova/common/cfg.py, line 777, in __getattr__
return self._substitute(self._get(name))
File nova/common/cfg.py, line 930, in _get
info = self._get_opt_info(name, group)
File nova/common/cfg.py, line 1010, in _get_opt_info
raise NoSuchOptError(opt_name, group)
nova.common.cfg.NoSuchOptError: no such option: __name__
To test, you do:
bpython
then at prompt:
from nova import flags
flags.FLAGS(
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/915039/+subscriptions
___
Mailing list: https://launchpad.net/~openstack-poc
Post to : openstack-poc@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack-poc
More help : https://help.launchpad.net/ListHelp
[Openstack-poc] [Bug 954488] Re: nova/openstack/common/cfg.py: 'nova.api.openstack.contrib.standard_extensions' is non-existant
** Changed in: nova Milestone: essex-rc1 = 2012.1 -- You received this bug notification because you are a member of OpenStack Common Drivers, which is the registrant for openstack-common. https://bugs.launchpad.net/bugs/954488 Title: nova/openstack/common/cfg.py: 'nova.api.openstack.contrib.standard_extensions' is non-existant Status in OpenStack Compute (Nova): Fix Released Status in openstack-common: Fix Committed Bug description: nova/openstack/common/cfg.py refers to 'nova.api.openstack.contrib.standard_extensions' but this is a non- existant path. nova/openstack/common/cfg.py: DEFAULT_EXTENSIONS = [ 'nova.api.openstack.contrib.standard_extensions' ] To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/954488/+subscriptions ___ Mailing list: https://launchpad.net/~openstack-poc Post to : openstack-poc@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-poc More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: precise-openstack-essex-glance-trunk #167
Title: precise-openstack-essex-glance-trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise-openstack-essex-glance-trunk/167/Project:precise-openstack-essex-glance-trunkDate of build:Thu, 05 Apr 2012 21:46:02 -0400Build duration:10 secBuild cause:Started by user adamBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesNo ChangesConsole OutputStarted by user adamBuilding remotely on pkg-builderCheckout:precise-openstack-essex-glance-trunk / /var/lib/jenkins/slave/workspace/precise-openstack-essex-glance-trunk - hudson.remoting.Channel@1d008ff:pkg-builderUsing strategy: DefaultLast Built Revision: Revision f460a99baee6e37b624c070527f70d4a868b6223 (origin/milestone-proposed)Checkout:glance / /var/lib/jenkins/slave/workspace/precise-openstack-essex-glance-trunk/glance - hudson.remoting.LocalChannel@3fea5d72Wiping out workspace first.Cloning the remote Git repositoryCloning repository originFetching upstream changes from https://github.com/openstack/glance.gitERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Email was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
