Re: [Openstack] Bringing High Availability to OpenStack Keystone and Glance
We have a prototype of similar capabilities targeting Nova services, using ZooKeeper (heartbeat/membership, leader election, etc -- will share with the community soon). Would be interesting to compare the two approaches. Regards, Alex From: Martin Gerhard Loschwitz martin.loschw...@hastexo.com To: openstack@lists.launchpad.net, Date: 03/04/2012 06:23 PM Subject:[Openstack] Bringing High Availability to OpenStack Keystone andGlance Sent by:openstack-bounces+glikson=il.ibm@lists.launchpad.net Hi folks, there have been some discussions lately on the topic of OpenStack and High Availability. To take this discussion one step further, I started to work on OCF resource agents for Keystone and Glance. They allow administrators to integrate keystone, glance-registry and glance-api into the Pacemaker cluster manager. I tested them a lot and they worked just fine in my setup, so I thought i'd put them up here for discussion. I wrote a blog post about this which includes the links to the actual files. You can find it here: http://www.hastexo.com/blogs/martin/2012/04/02/bringing-high-availability-openstack-keystone-and-glance I am keen on hearing your opinion and your feedback on this, so please don't hestitate to either reply to this email or leave a comment behind in my blog. Thanks a lot! Best regards Martin -- Martin Gerhard Loschwitz Principal Consultant hastexo Professional Services ___ 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] Last Essex RCs: Keystone RC2, Horizon RC2 and Nova RC3 available
Hello everyone, The last 2012.1 (Essex) release candidates for Keystone, Horizon and Nova are finally out ! Please check out: https://launchpad.net/keystone/essex/essex-rc2 https://launchpad.net/horizon/essex/essex-rc2 https://launchpad.net/nova/essex/essex-rc3 Together with Glance 2012.1 RC3 and Swift 1.4.8, those RCs will be formally released as OpenStack 2012.1 (Essex) final version on Thursday, unless a critical last-minute regression is found and is considered a release blocker. Please test the proposed release deliverables and let us know of any issue by filing bugs to the corresponding project and tag them with essex-rc-potential. At this point, only last-minute regressions (things that used to work recently but suddenly stopped) will be considered, other issues will be documented as known bugs in the release notes. Regards, -- 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] Swift and keystone: asking for an auth token.
Thanks to all for your feedback it has been helpfull ! On 04/03/2012 06:42 PM, Dolph Mathews wrote: See `keystone help role-list`. Great, makes more sense now ! On 04/04/2012 06:42 AM, Chmouel Boudjnah wrote: You are in the group Admin and your operator_roles is admin (lowercase). That was spot on ! After having reset swift to use Admin as operator_roles things started to work much better. Thanks ! On 04/04/2012 06:03 AM, Pete Zaitcev wrote: I'm surprised this works at all, because if service_protocol is not set, it defaults to https:. However, your -A argument points to http: I do no know why it work neither :-) Thanks for the service_protocol tip, i have added it in my config file (and added a i need to use https for keystone item on my TODO list on top of that). ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Swift tools with Keystone: swift-bench and swift-dispersion-*
Cheers Chmouel. I'll get on it and do some testing. Kev On 2 April 2012 23:35, Chmouel Boudjnah chmo...@chmouel.com wrote: There is a review on the go here: https://review.openstack.org/#change,6088 which should address swift-dispertion to be able to connect to auth version 2.0 servers. Feel free to log a bug if there is other tools missing. Chmouel. On Mon, Apr 2, 2012 at 10:57 PM, Kevin Jackson ke...@linuxservices.co.uk wrote: Hello All, Is it possible to use Swift tools such as swift-bench and swift-dispersion-populate/report with Keystone? If so, how? The examples refer to the SAIO configuration of authentication using tempauth on port 11000 but I can't find reference to what should run on port 11000 (I'm presuming this is the default for proxy-server or have I misread something?)... Cheers, Kev -- Kevin Jackson @itarchitectkev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Kevin Jackson @itarchitectkev ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] No networking for instances on second compute node
Hi all, I have a two node Essex setup: One node is running all services including -compute, the other node is only running nova-compute and -network. When I launch an instance on the first node, everything is fine but when I use the second (compute-only) node the instance gets no ip address. These are the network related settings from my nova.conf: # Network --network_manager=nova.network.manager.FlatDHCPManager --cc_host=192.168.122.2 --ec2_host=192.168.122.2 --network_host=192.168.122.2 --floating_range=192.168.124.0/24 # flat DHCP mode --dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --fixed_range=192.168.125.0/24 --flat_network_dhcp_start=192.168.125.20 --flat_interface=eth2 --flat_network_bridge=br100 --flat_injected=False What could be wrong here? Log files can be provided if necessary. tia, Alex ___ 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] Best approach for deploying Essex?
+1 on the Ubuntu 12.04 Precise and Essex. Whilst there are other methods and OS of choice, given you've been using 11.10 - 12.04 is the natural home for it. The betas of Precise are rock-solid and can vouch for the Ubuntu packaging following quite quickly behind the devs. I highly recommend this approach. Kev On 3 April 2012 20:02, Lillie Ross-CDSR11 ross.lil...@motorolasolutions.com wrote: Hi Adam, Thanks for the update. Actually, I'm in the process of reading about your testing and integration framework for Openstack ( http://ubuntuserver.wordpress.com/2012/02/08/704/) as I write this. Yes, Keystone integration seemed to be the big bugaboo in the Ubuntu/Diablo release. I've successfully got everything authenticating with keystone in our current deployment, but as you well know, this precludes using S3 bindings with Swift, and you must use the Openstack glance client to bundle/upload images. This had me pulling my hair out in the early stages. Today I've spun up 3 generic 11.10 servers that I'm planning on testing the next Ubuntu release and Openstack packages. Should I start my testing with the beta1 release of 12.04LTS? In particular I'm interested in seeing and understanding the process of migrating my existing installation and configs to the new release. Once I'm satisfied that I understand everything (not possible) in the new release, I can migrate our operational cloud in a couple of days. Also, what's the best place to keep abreast on the Ubuntu/Canonical integration of openstack? The Ubuntu Wiki? Mailing list? Thanks again, Ross On Apr 3, 2012, at 1:21 PM, Adam Gandelman wrote: On 04/03/2012 08:20 AM, Lillie Ross-CDSR11 wrote: My question is, should I base our new installation directly off the Essex branch in the git repository, or use the packages that will be deployed as part of the associated Ubuntu 12.04LTS release? With Diablo, I was forced to use packages from the ManagedIT PPA with additional Keystone patches to get a consistent, stable platform up and running. Obviously, some of these problems were due to confusion caused by various documents describing different incarnations of Openstack, and not really knowing what was current and stable. Especially the packages shipped with Ubuntu made assumptions about how Openstack was to be deployed that wasn't really apparent. Hey Ross- I can say that the Ubuntu precise packages have been kept relatively in-sync with each components' trunk git repository this cycle. We've made a concerted effort to do weekly snapshot uploads of all Openstack components into the Precise archive starting from the beginning of the Essex+Precise dev cycles. We've also maintained our own trunk PPA (updated continously) around which we center our testing efforts. Now that we're nearing the release of Essex, we've been ensuring the release candidates hit our archive as soon as they are released. As soon as Essex final hits, it'll be uploaded into Ubuntu and give any users who care the remainder of the Ubuntu dev cycle (~1 month) to test and identify issues before LTS ships. Re: deployment assumptions. Last cycle, we were caught off-guard by Keystone's last-minute inclusion into Openstack core and the dependencies this introduced (dashboard especially) It's not that we were making assumptions about how Openstack Diablo should be deployed, just that there was no way we could shoe-horn a new component into the release so late in the game. This time around, a similar curve ball was thrown our way with the Keystone Lite rewrite, but we were able to get this sorted on our end relatively quickly to ensure pending security reviews and main inclusion processes for Keystone weren't blocked. We're making very few assumptions going into LTS and hope to provide as-close-to-pure Essex experience as any. I can only think of a few patches we're carrying, and there are only two default configuration files we ship that differ from those you'd find in the git repos [2]. Perhaps when we release Essex into Precise this/next week, we'll put some notes somewhere outlining any Ubuntu-specific changes for those who are interested. Hope that helps, and of course we welcome your testing and bug reports! -Adam [1] We ship a default nova.conf that configures some Ubuntu defaults: defaults to libvirt compute, uses nova-rootwrap for sudo shell execution (requested by our security team), uses tgt iscsi initiator instead of ietd (tgt is supported in our main archive, ietd is not). Our default Keystone config defaults to the SQL catalog backend instead of the default templated file, though I think SQL catalog is the new default in folsom. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help :
[Openstack] OpenStack immaturity
Hi everyone, According to the statement of this article from Gartner group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a highly immature platform. But why? What's make Openstack so immature? Any comments on that? Thank you in advance :) ___ 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] Instance fails to spawn when instance_path is nfs mounted
I had a problem like this when the umask was locked down. Setting the umask
to 022 in the init script for nova-compute solved my problem.
I'm running from devstack setup - so I don't have an init-script. All the
processes run in a screen session.
Here is what I did :
1. Stopped nova-compute using Ctrl-C
2. Checked existing umask using umask command it was set to 0002
3. Updated umask using umask 022 - checked that it was indeed updated - this
time umask command returned 0022
4. Started nova-compute as follows :
mandar@ubuntu-dev-mandar:/opt/stack/nova$ cd /opt/stack/nova sg
libvirtd /opt/stack/nova/bin/nova-compute
5. Spawned an instance from Dashboard
Still getting same error.
-Mandar
On Tue, Apr 3, 2012 at 1:56 PM, Diego Parrilla Santamaría
diego.parrilla.santama...@gmail.com wrote:
We use nfs backed instances a lot, and this problem normally has to do
with wrong permission management in your filer and/or client.
Check if not only root can write on the nfs share (specially libvirt user).
Diego
--
Diego Parrilla
CEO
www.stackops.com | diego.parri...@stackops.com | +34 649 94 43 29
| skype:diegoparrilla
On Tue, Apr 3, 2012 at 6:43 PM, Mandar Vaze / मंदार वझे
mandarv...@gmail.com wrote:
I saw an old question posted here :
https://answers.launchpad.net/nova/+question/164689
But I am not trying live migration.
I have nfs mounted instances_path - so when I try to spawn an
instance I run into the above errors. Especially following :
File /usr/lib/python2.7/dist-packages/libvirt.py, line 372, in
createWithFlags
40842 2012-04-03 05:42:27 TRACE nova.rpc.amqp if ret == -1: raise
libvirtError ('virDomainCreateWithFlags() failed', dom=self)
40843 2012-04-03 05:42:27 TRACE nova.rpc.amqp libvirtError: internal
error Process exited while reading console log output: chardev:
opening backend file failed
But as you can see below, several files are created in this folder,
so I am not sure if mine if permissions issue (Else none of the files
would get created) The problem is reported when libvirt tries to
write to console.log (File itself is created with correct permissions
- just that this is zero byte file)
mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-0005
$ ll total 10944 drwxrwxr-x 2 mandar libvirtd 4096 2012-04-03
05:42 ./ drwxrwxrwx 4 root root 4096 2012-04-03 05:42 ../
-rw-rw 1 mandar libvirtd 0 2012-04-03 05:42 console.log
-rw-r--r-- 1 mandar libvirtd 6291968 2012-04-03 05:42 disk
-rw-rw-r-- 1 mandar libvirtd 4731440 2012-04-03 05:42 kernel
-rw-rw-r-- 1 mandar libvirtd 1067 2012-04-03 05:42 libvirt.xml
-rw-rw-r-- 1 mandar libvirtd 2254249 2012-04-03 05:42 ramdisk
I'm suspecting :
https://bugs.launchpad.net/ubuntu/maverick/+source/libvirt/+bug/63269
6 But I the above doesn't show itself in non-NFS setup
Please suggest !!!
-Mandar
___
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
__
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
Re: [Openstack] OpenStack immaturity
Immaturity of a platform is something you can easily fix paying the right fee to your favorite analyst firm. Seriously, Openstack is an open platform and an open community. This means problems and issues are open to discuss to everyone. Propietary platforms issues are rarely disclosed, and they look more mature. And believe me, I have used most of them and Openstack is not more unstable (or stable) than others. Anyway, it's time to move the stack from 'devs' to 'ops'. When somebody says 'you have to install the development version to fix this' instead of 'you have to follow this procedure on the stable version', you cannot imagine the damage made to Openstack Nova. It's painful, but it's the only way to have a robust platform. Let's forget about 'you will have it in the next release': we are not Microsoft. This is real, not vapourware. My two cents Diego -- Diego Parrilla http://www.stackops.com/*CEO* *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 | skype:diegoparrilla* * http://www.stackops.com/ ** On Wed, Apr 4, 2012 at 12:24 PM, Sébastien Han han.sebast...@gmail.comwrote: Hi everyone, According to the statement of this article from Gartner group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a highly immature platform. But why? What's make Openstack so immature? Any comments on that? Thank you in advance :) ___ 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] Instance fails to spawn when instance_path is nfs mounted
Ø Check if not only root can write on the nfs share (specially libvirt user).
It doesn’t look like permissions issue to me. Just to be doubly sure, I
“touched” a file, in that folder, edited and deleted the file. All operations
worked w/o error.
As I have listed below, several files got created with correct user/group
settings. In fact, “instance-0005” folder itself was created with correct
permissions.
mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-0005$ ll
total 10944
drwxrwxr-x 2 mandar libvirtd4096 2012-04-03 05:42 ./
drwxrwxrwx 4 root root4096 2012-04-03 05:42 ../
-rw-rw 1 mandar libvirtd 0 2012-04-03 05:42 console.log
-rw-r--r-- 1 mandar libvirtd 6291968 2012-04-03 05:42 disk
-rw-rw-r-- 1 mandar libvirtd 4731440 2012-04-03 05:42 kernel
-rw-rw-r-- 1 mandar libvirtd1067 2012-04-03 05:42 libvirt.xml
-rw-rw-r-- 1 mandar libvirtd 2254249 2012-04-03 05:42 ramdisk
I also moved the mount point from “/” to my home folder – still didn’t help
-Mandar
On Tue, Apr 3, 2012 at 6:43 PM, Mandar Vaze / मंदार वझे
mandarv...@gmail.commailto:mandarv...@gmail.com wrote:
I saw an old question posted here :
https://answers.launchpad.net/nova/+question/164689
But I am not trying live migration.
I have nfs mounted instances_path - so when I try to spawn an instance I
run into the above errors. Especially following :
File /usr/lib/python2.7/dist-packages/libvirt.py, line 372, in createWithFlags
40842 2012-04-03 05:42:27 TRACE nova.rpc.amqp if ret == -1: raise
libvirtError ('virDomainCreateWithFlags() failed', dom=self)
40843 2012-04-03 05:42:27 TRACE nova.rpc.amqp libvirtError: internal error
Process exited while reading console log output: chardev: opening backend
file failed
But as you can see below, several files are created in this folder, so I
am not sure if mine if permissions issue (Else none of the files would
get created) The problem is reported when libvirt tries to write to
console.log (File itself is created with correct permissions - just that
this is zero byte file)
mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-0005$ ll
total 10944
drwxrwxr-x 2 mandar libvirtd4096 2012-04-03 05:42 ./
drwxrwxrwx 4 root root4096 2012-04-03 05:42 ../
-rw-rw 1 mandar libvirtd 0 2012-04-03 05:42 console.log
-rw-r--r-- 1 mandar libvirtd 6291968 2012-04-03 05:42 disk
-rw-rw-r-- 1 mandar libvirtd 4731440 2012-04-03 05:42 kernel
-rw-rw-r-- 1 mandar libvirtd1067 2012-04-03 05:42 libvirt.xml
-rw-rw-r-- 1 mandar libvirtd 2254249 2012-04-03 05:42 ramdisk
I'm suspecting :
https://bugs.launchpad.net/ubuntu/maverick/+source/libvirt/+bug/632696
But I the above doesn't show itself in non-NFS setup
Please suggest !!!
-Mandar
___
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
__
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
Re: [Openstack] Instance fails to spawn when instance_path is nfs mounted
Please have a look at my experience to see if it can help.Thanks-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -To: Razique Mahroua razique.mahr...@gmail.comFrom: Yong Sheng Gong/China/IBM@IBMCNSent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.netDate: 03/29/2012 07:39PMCc: "openstack@lists.launchpad.net \(openstack@lists.launchpad.net\)" openstack@lists.launchpad.netSubject: Re: [Openstack] KVM cannot start vm when the disk is on NFSThanks for the reply. I have figured it out.I am running nova control node with root account on the side of nfs4 server side (redhat6.1), while on the side of compute node is ubuntu.So on ubuntu side, I have executed:$sudo bash,#nova-computeIn fact what I need to do is to let kvm binary run under root user id.I found the solution from http://libvirt.org/drvqemu.html.Here are what I did on ubuntu side:#chown root:root /var/run/libvirt/qemu /var/lib/libvirt/qemu /var/cache/libvirt/qemuedit /etc/libvirt/qemu.conf# The user ID for QEMU processes run by the system instance.user = "root"# The group ID for QEMU processes run by the system instance.group = "root"after restarting libvirt-bin, nova-compute can provision vm from the images on NFS share dir now.-Razique Mahroua razique.mahr...@gmail.com wrote: -To: Yong Sheng Gong/China/IBM@IBMCNFrom: Razique Mahroua razique.mahr...@gmail.comDate: 03/29/2012 06:00PMCc: "openstack@lists.launchpad.net (openstack@lists.launchpad.net)" openstack@lists.launchpad.netSubject: Re: [Openstack] KVM cannot start vm when the disk is on NFSHello Yong,as you may understand, the chmod 777 is not the best thing to do.it looks like the files belong to the user root, while it's the user nova which runs the cloud.The first thing to do is to give the rights to the user nova of the directory (755) to nova:nova.Thanks! Nuage Co - Razique Mahrouarazique.mahr...@gmail.com Le 29 mars 2012 à 09:50, Yong Sheng Gong a écrit :I have to run chmod 777 /var/lib/nova/instances/instance-0007 to start the vm on kvm. Appreciate any help from stackers. HostA ( 192.168.1.90): redhat 6.1 nfs4/etc/exports:/var/lib/nova/instances 192.168.1.0/24(rw,sync,fsid=0,no_root_squash)/etc/idmapd:[General]Domain = openstack#service nfs restart#service rpcidmapd restartHostB ( 192.168.1.94): ubuntu 11.10#sudo bash/etc/idmapd:[General]Verbosity = 0Pipefs-Directory = /var/lib/nfs/rpc_pipefsDomain = openstack/etc/fstab:192.168.1.90:/ /var/lib/nova/instances nfs4 defaults 0 0#mount -a -vroot@openubuntu:/var/lib/nova/instances/instance-0007# lltotal 14168drwxr-xr-x 2 root root 4096 2012-03-29 14:23 ./drwxr-xr-x 9 nobody nogroup 4096 2012-03-29 14:21 ../-rw-rw 1 root root 0 2012-03-29 14:17 console.log-rw-r--r-- 1 root root 6291968 2012-03-29 14:18 disk-rw-r--r-- 1 root root 4404752 2012-03-29 14:18 kernel-rw-r--r-- 1 root root 1619 2012-03-29 14:17 libvirt.xml-rw-r--r-- 1 root root 5882349 2012-03-29 14:18 ramdiskroot@openubuntu:/var/lib/nova/instances/instance-0007# virsh start instance-0007error: Failed to start domain instance-0007error: internal error Process exited while reading console log output: chardev: opening backend "file" failedroot@openubuntu:/var/lib/nova/instances/instance-0007# chmod 777 console.logroot@openubuntu:/var/lib/nova/instances/instance-0007# virsh start instance-0007error: Failed to start domain instance-0007error: internal error Process exited while reading console log output: char device redirected to /dev/pts/3kvm: -drive file=/var/lib/nova/instances/instance-0007/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none: could not open disk image /var/lib/nova/instances/instance-0007/disk: Permission deniedroot@openubuntu:/var/lib/nova/instances/instance-0007# chmod 777 *root@openubuntu:/var/lib/nova/instances/instance-0007# virsh start instance-0007Domain instance-0007 startedThanksYong Sheng Gong ___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 -openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -To: Nathanael Burton nathanael.i.bur...@gmail.com, Diego Parrilla Santamaría diego.parrilla.santama...@gmail.comFrom: "Vaze, Mandar" mandar.v...@nttdata.comSent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.netDate: 04/04/2012 06:28PMCc: "openstack@lists.launchpad.net" openstack@lists.launchpad.netSubject: Re: [Openstack] Instance fails to spawn when instance_path is nfs mounted I had a problem like this when the umask was locked down. Setting the umask to 022 in the init script for nova-compute solved my problem.I'm
Re: [Openstack] Instance fails to spawn when instance_path is nfs mounted
All,
On the link given below vish asked if I could “chown” the files in that folder
– turns out I couldn’t.
I’ve answered his query on the link below – but repeating the updates here for
larger audience (Unfortunately, I have revived a question that is marked as
“solved” – so not many people may refer/respond to the link)
Vish :
1) is it possible to chown files on your nfs mount?
Not sure whom should I give the ownership to ? As the dir listing shows above,
the files are created with correct owner/group settings. These files were
created by nova-compute process.
I touched a file for testing - which was created with mandar:mandar - I
tried changing the ownership, but I keep getting invalid argument - not sure
if that is what you were referring to ..
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ touch x
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ ll
total 16
drwxrwxrwx 4 root root 4096 2012-04-04 03:46 ./
drwxr-xr-x 15 mandar mandar 4096 2012-04-04 03:39 ../
drwxrwxr-x 2 mandar libvirtd 4096 2012-04-04 02:18 _base/
drwxr-xr-x 2 mandar libvirtd 4096 2012-04-04 03:41 instance-000f/
-rw-rw-r-- 1 mandar mandar 0 2012-04-04 03:46 x
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ chown root x
chown: changing ownership of `x': Invalid argument
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ ll
total 16
drwxrwxrwx 4 root root 4096 2012-04-04 03:46 ./
drwxr-xr-x 15 mandar mandar 4096 2012-04-04 03:39 ../
drwxrwxr-x 2 mandar libvirtd 4096 2012-04-04 02:18 _base/
drwxr-xr-x 2 mandar libvirtd 4096 2012-04-04 03:41 instance-000f/
-rw-rw-r-- 1 mandar mandar 0 2012-04-04 03:46 x
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ sudo chown root x
chown: changing ownership of `x': Invalid argument
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ chgrp libvirtd x
chgrp: changing group of `x': Invalid argument
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ sudo chgrp libvirtd x
chgrp: changing group of `x': Invalid argument
I also debugged the _chown_console_log_for_instance in
nova/virt/libvirt/connection.py
and with breakpoint before if os.path.exists(console_log) - I touched
console.log at the appropriate path from another terminal.
Over there also I am getting the same error:
2012-04-04 03:56:55 TRACE nova.rpc.amqp Command: sudo
/usr/local/bin/nova-rootwrap chown 1000
/home/mandar/nfs_shared_instances_path/instance-0010/console.log
2012-04-04 03:56:55 TRACE nova.rpc.amqp Exit code: 1
2012-04-04 03:56:55 TRACE nova.rpc.amqp Stdout: ''
2012-04-04 03:56:55 TRACE nova.rpc.amqp Stderr: /bin/chown: changing ownership
of `/home/mandar/nfs_shared_instances_path/instance-0010/console.log':
Invalid argument\n
So what is the fix for this ?
-Mandar
From: openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net] On
Behalf Of Mandar Vaze / ? ???
Sent: Tuesday, April 03, 2012 10:14 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] Instance fails to spawn when instance_path is nfs mounted
I saw an old question posted here :
https://answers.launchpad.net/nova/+question/164689
But I am not trying live migration.
I have nfs mounted instances_path - so when I try to spawn an instance I
run into the above errors. Especially following :
File /usr/lib/python2.7/dist-packages/libvirt.py, line 372, in createWithFlags
40842 2012-04-03 05:42:27 TRACE nova.rpc.amqp if ret == -1: raise
libvirtError ('virDomainCreateWithFlags() failed', dom=self)
40843 2012-04-03 05:42:27 TRACE nova.rpc.amqp libvirtError: internal error
Process exited while reading console log output: chardev: opening backend
file failed
But as you can see below, several files are created in this folder, so I
am not sure if mine if permissions issue (Else none of the files would
get created) The problem is reported when libvirt tries to write to
console.log (File itself is created with correct permissions - just that
this is zero byte file)
mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-0005$ ll
total 10944
drwxrwxr-x 2 mandar libvirtd4096 2012-04-03 05:42 ./
drwxrwxrwx 4 root root4096 2012-04-03 05:42 ../
-rw-rw 1 mandar libvirtd 0 2012-04-03 05:42 console.log
-rw-r--r-- 1 mandar libvirtd 6291968 2012-04-03 05:42 disk
-rw-rw-r-- 1 mandar libvirtd 4731440 2012-04-03 05:42 kernel
-rw-rw-r-- 1 mandar libvirtd1067 2012-04-03 05:42 libvirt.xml
-rw-rw-r-- 1 mandar libvirtd 2254249 2012-04-03 05:42 ramdisk
I'm suspecting :
https://bugs.launchpad.net/ubuntu/maverick/+source/libvirt/+bug/632696
But I the above doesn't show itself in non-NFS setup
Please suggest !!!
-Mandar
__
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
Re: [Openstack] Instance fails to spawn when instance_path is nfs mounted
Are you sure your libvirtd will start /usr/bin/kvm with libvirtd group?In default, the /usr/bin/kvm is running with libvirt-qemu like user (that depends on how it is built). you can try to check it by running "ps -ef" to see the effective user and group id after starting a VM in your way.-openstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -To: Diego Parrilla Santamaría diego.parrilla.santama...@gmail.comFrom: "Vaze, Mandar" mandar.v...@nttdata.comSent by: openstack-bounces+gongysh=cn.ibm@lists.launchpad.netDate: 04/04/2012 06:43PMCc: "openstack@lists.launchpad.net" openstack@lists.launchpad.netSubject: Re: [Openstack] Instance fails to spawn when instance_path is nfs mountedØ
Check if not only root can write on the nfs share (specially libvirt user).It doesn’t look like permissions issue to me. Just to be doubly sure, I “touched” a file, in that folder, edited and deleted the
file. All operations worked w/o error.
As I have listed below, several files got created with correct user/group settings. In fact, “instance-0005” folder itself
was created with correct permissions.
mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-0005$ ll
total 10944
drwxrwxr-x 2 mandar libvirtd 4096 2012-04-03 05:42 ./
drwxrwxrwx 4 root root4096 2012-04-03 05:42 ../
-rw-rw 1 mandar libvirtd0 2012-04-03 05:42 console.log
-rw-r--r-- 1 mandar libvirtd 6291968 2012-04-03 05:42 disk
-rw-rw-r-- 1 mandar libvirtd 4731440 2012-04-03 05:42 kernel
-rw-rw-r-- 1 mandar libvirtd 1067 2012-04-03 05:42 libvirt.xml
-rw-rw-r-- 1 mandar libvirtd 2254249 2012-04-03 05:42 ramdisk
I also moved the mount point from “/” to my home folder – still didn’t help
-Mandar
On Tue, Apr 3, 2012 at 6:43 PM, Mandar Vaze /
मंदार वझे mandarv...@gmail.com wrote:
I saw an old question posted here :
https://answers.launchpad.net/nova/+question/164689
ButI am not trying live migration.
I have nfs mounted instances_path - so when I try to spawn an instance I
run into the above errors. Especially following :
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 372, in createWithFlags
40842 2012-04-03 05:42:27 TRACE nova.rpc.amqp if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self)
40843 2012-04-03 05:42:27 TRACE nova.rpc.amqp libvirtError: internal error Process exited while reading console log output: chardev: openingbackend "file" failed
But as you can see below, several files are created in this folder, so I
am not sure if mine if permissions issue (Else none of the files would
get created) The problem is reported when libvirt tries to write to
console.log (File itself is created with correct permissions - just that
this is zero byte file)
mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-0005$ ll
total 10944
drwxrwxr-x 2 mandar libvirtd 4096 2012-04-03 05:42 ./
drwxrwxrwx 4 root root4096 2012-04-03 05:42 ../
-rw-rw 1 mandar libvirtd0 2012-04-03 05:42 console.log
-rw-r--r-- 1 mandar libvirtd 6291968 2012-04-03 05:42 disk
-rw-rw-r-- 1 mandar libvirtd 4731440 2012-04-03 05:42 kernel
-rw-rw-r-- 1 mandar libvirtd 1067 2012-04-03 05:42 libvirt.xml
-rw-rw-r-- 1 mandar libvirtd 2254249 2012-04-03 05:42 ramdisk
I'm suspecting :
https://bugs.launchpad.net/ubuntu/maverick/+source/libvirt/+bug/632696
But I the above doesn't show itself in non-NFS setup
Please suggest !!!
-Mandar
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
__
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/~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] Last Essex RCs: Keystone RC2, Horizon RC2 and Nova RC3 available
Hello Thierry, Do you know if exists some page that have information about diablo bugs that was fixed on essex?] Thanks Em 4 de abril de 2012 04:44, Thierry Carrez thie...@openstack.orgescreveu: Hello everyone, The last 2012.1 (Essex) release candidates for Keystone, Horizon and Nova are finally out ! Please check out: https://launchpad.net/keystone/essex/essex-rc2 https://launchpad.net/horizon/essex/essex-rc2 https://launchpad.net/nova/essex/essex-rc3 Together with Glance 2012.1 RC3 and Swift 1.4.8, those RCs will be formally released as OpenStack 2012.1 (Essex) final version on Thursday, unless a critical last-minute regression is found and is considered a release blocker. Please test the proposed release deliverables and let us know of any issue by filing bugs to the corresponding project and tag them with essex-rc-potential. At this point, only last-minute regressions (things that used to work recently but suddenly stopped) will be considered, other issues will be documented as known bugs in the release notes. Regards, -- 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 -- Atenciosamente, Guilherme Santos Souza Sistemas de Informação - PUCRS Fone: (51) 9695-1070 ___ 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] Quota classes
Eoghan Glynn wrote: - how is the mapping between project and quota-class established? I was expecting a project_quota_class_association table or some-such in the nova DB. Is this association maintained by keystone instead? - is the quota_class attribute currently being set on the request context anywhere in the dispatch path? Is the idea that the auth middleware takes care of this? Kevin Mitchell wrote: The basic answer is that there isn't anything in nova right now that does this, partly because it's a slightly difficult question to answer correctly for everyone. In my testing environment, for instance, I use a Turnstile preprocessor to set the quota_class attribute on the request context to be the same as the selected rate limit class. I envisioned that, ultimately, the quota_class would be set by the authentication processing middleware(s), but I'm not against adding an association to nova to manage that. One more follow-up question on this. So IIUC the mechanism as it currently stands implies a 1:M mapping between quota classes and projects/tenants. Only a single quota class may be selected for each request context, so *all* the individual hard limits for the different resource types encompassed by that class are inherited as default quotas for the request. But might there be a usecase for mutiple quota classes applying to an individual project (for different resource types)? e.g. compute-hungry/storage-light customers might select the premium package for instances/cores/RAM combined with the basic package for volumes/gigabytes (or vice versa for storage-heavy but narrowly-scaled apps). If we were to go down that road, we'd require an N:M association between quota class names projects, right? Or equivalently, a 1:M mapping between quota class IDs and projects. Also the single quota class name in the request context would have to be replaced with a list of either quota class IDs or (quota class name, resource type) pairs. I guess the other alternative would be to simply create new quota classes for each permutation of resource limits required, e.g. premium-compute-basic-storage, basic-compute-premium-storage etc. We'd get asome proliferation on the number of quota classes, but in realistic scenarios it wouldn't go combinatorial. Cheers, Eoghan ___ 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
It depends on what you expect OpenStack to do for you. If you want pre-packaged, click-to-install software, it is not there, yet. But if you want to be able to influence the future of the project you want to bet your business on, you have a much higher chance of doing that with OpenStack than with other projects in this space. Just my $.02 worth. Jacek Artymiak author: http://docs.openstack.org/api/openstack-compute/programmer/content/ (please submit patches so we can improve this document) On Wed, Apr 4, 2012 at 12:24 PM, Sébastien Han han.sebast...@gmail.com wrote: Hi everyone, According to the statement of this article from Gartner group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a highly immature platform. But why? What's make Openstack so immature? Any comments on that? Thank you in advance :) ___ 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 believe this Openstack is a highly immature platform. is referring more to nova than swift. The simple reason for that is nova is more focused on dev than ops but that is changing.In mature projects the questions like How do I run this reliably every day? and How can I safely upgrade from one version to the next? are just as important as What new features are coming?. Time will tell. On Wed, Apr 4, 2012 at 6:27 AM, Frans Thamura fr...@meruvian.org wrote: I think this news is good Make us must work hard. Time will tell Like linux, now lead. On Apr 4, 2012 5:57 PM, Diego Parrilla Santamaría diego.parrilla.santama...@gmail.com wrote: Immaturity of a platform is something you can easily fix paying the right fee to your favorite analyst firm. Seriously, Openstack is an open platform and an open community. This means problems and issues are open to discuss to everyone. Propietary platforms issues are rarely disclosed, and they look more mature. And believe me, I have used most of them and Openstack is not more unstable (or stable) than others. Anyway, it's time to move the stack from 'devs' to 'ops'. When somebody says 'you have to install the development version to fix this' instead of 'you have to follow this procedure on the stable version', you cannot imagine the damage made to Openstack Nova. It's painful, but it's the only way to have a robust platform. Let's forget about 'you will have it in the next release': we are not Microsoft. This is real, not vapourware. My two cents Diego -- Diego Parrilla CEO www.stackops.com | diego.parri...@stackops.com | +34 649 94 43 29 | skype:diegoparrilla On Wed, Apr 4, 2012 at 12:24 PM, Sébastien Han han.sebast...@gmail.com wrote: Hi everyone, According to the statement of this article from Gartner group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a highly immature platform. But why? What's make Openstack so immature? Any comments on that? Thank you in advance :) ___ 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] Instance fails to spawn when instance_path is nfs mounted
I was able to resolve the problem – Thanks to hint Vish provided and suggestion
from Rohit (CC’ed)
Turns out there is some problem with nfs v4 – So we mounted the share using nfs
version 3 (mount –o vers=3)
Now we could “chown” the files in nfs folder, and the instance creation also
worked !!!
Thanks Rohit !!!
Thanks Vish !!
-Mandar
From: Vaze, Mandar
Sent: Wednesday, April 04, 2012 4:41 PM
To: openstack@lists.launchpad.net
Cc: 'vishvana...@gmail.com'
Subject: RE: [Openstack] Instance fails to spawn when instance_path is nfs
mounted
All,
On the link given below vish asked if I could “chown” the files in that folder
– turns out I couldn’t.
I’ve answered his query on the link below – but repeating the updates here for
larger audience (Unfortunately, I have revived a question that is marked as
“solved” – so not many people may refer/respond to the link)
Vish :
1) is it possible to chown files on your nfs mount?
Not sure whom should I give the ownership to ? As the dir listing shows above,
the files are created with correct owner/group settings. These files were
created by nova-compute process.
I touched a file for testing - which was created with mandar:mandar - I
tried changing the ownership, but I keep getting invalid argument - not sure
if that is what you were referring to ..
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ touch x
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ ll
total 16
drwxrwxrwx 4 root root 4096 2012-04-04 03:46 ./
drwxr-xr-x 15 mandar mandar 4096 2012-04-04 03:39 ../
drwxrwxr-x 2 mandar libvirtd 4096 2012-04-04 02:18 _base/
drwxr-xr-x 2 mandar libvirtd 4096 2012-04-04 03:41 instance-000f/
-rw-rw-r-- 1 mandar mandar 0 2012-04-04 03:46 x
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ chown root x
chown: changing ownership of `x': Invalid argument
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ ll
total 16
drwxrwxrwx 4 root root 4096 2012-04-04 03:46 ./
drwxr-xr-x 15 mandar mandar 4096 2012-04-04 03:39 ../
drwxrwxr-x 2 mandar libvirtd 4096 2012-04-04 02:18 _base/
drwxr-xr-x 2 mandar libvirtd 4096 2012-04-04 03:41 instance-000f/
-rw-rw-r-- 1 mandar mandar 0 2012-04-04 03:46 x
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ sudo chown root x
chown: changing ownership of `x': Invalid argument
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ chgrp libvirtd x
chgrp: changing group of `x': Invalid argument
mandar@ubuntu-dev-mandar:~/nfs_shared_instances_path$ sudo chgrp libvirtd x
chgrp: changing group of `x': Invalid argument
I also debugged the _chown_console_log_for_instance in
nova/virt/libvirt/connection.py
and with breakpoint before if os.path.exists(console_log) - I touched
console.log at the appropriate path from another terminal.
Over there also I am getting the same error:
2012-04-04 03:56:55 TRACE nova.rpc.amqp Command: sudo
/usr/local/bin/nova-rootwrap chown 1000
/home/mandar/nfs_shared_instances_path/instance-0010/console.log
2012-04-04 03:56:55 TRACE nova.rpc.amqp Exit code: 1
2012-04-04 03:56:55 TRACE nova.rpc.amqp Stdout: ''
2012-04-04 03:56:55 TRACE nova.rpc.amqp Stderr: /bin/chown: changing ownership
of `/home/mandar/nfs_shared_instances_path/instance-0010/console.log':
Invalid argument\n
So what is the fix for this ?
-Mandar
From:
openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.netmailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net]mailto:[mailto:openstack-bounces+mandar.vaze=vertex.co...@lists.launchpad.net]
On Behalf Of Mandar Vaze / ? ???
Sent: Tuesday, April 03, 2012 10:14 PM
To: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: [Openstack] Instance fails to spawn when instance_path is nfs mounted
I saw an old question posted here :
https://answers.launchpad.net/nova/+question/164689
But I am not trying live migration.
I have nfs mounted instances_path - so when I try to spawn an instance I
run into the above errors. Especially following :
File /usr/lib/python2.7/dist-packages/libvirt.py, line 372, in createWithFlags
40842 2012-04-03 05:42:27 TRACE nova.rpc.amqp if ret == -1: raise
libvirtError ('virDomainCreateWithFlags() failed', dom=self)
40843 2012-04-03 05:42:27 TRACE nova.rpc.amqp libvirtError: internal error
Process exited while reading console log output: chardev: opening backend
file failed
But as you can see below, several files are created in this folder, so I
am not sure if mine if permissions issue (Else none of the files would
get created) The problem is reported when libvirt tries to write to
console.log (File itself is created with correct permissions - just that
this is zero byte file)
mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-0005$ ll
total 10944
drwxrwxr-x 2 mandar libvirtd4096 2012-04-03 05:42 ./
drwxrwxrwx 4 root root4096 2012-04-03
Re: [Openstack] Last Essex RCs: Keystone RC2, Horizon RC2 and Nova RC3 available
Guilherme Souza wrote: Do you know if exists some page that have information about diablo bugs that was fixed on essex?] Those are listed in the milestone pages, and should move on the final release page once released. In the mean time, the simpler is probably to look at: https://bugs.launchpad.net/openstack/+bugs?orderby=-date_last_updatedfield.status%3Alist=FIXRELEASED -- 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] Xen Hypervisor
Hi, I have tried this but still doesn't work. Here is my interfaces config of DomU: auto eth0:1iface eth0:1 inet staticaddress 192.168.110.1netmask 255.255.255.0broadcast 192.168.120.255gateway 192.168.110.1 auto eth0:2iface eth0:2 inet staticaddress 192.168.100.224 netmask 255.255.255.0broadcast 192.168.100.255gateway 192.168.100.1 and here is ifconfig of controller, domU and dom0: lis@controller:~$ ifconfigeth0 Link encap:Ethernet HWaddr 78:e7:d1:72:05:a7 inet6 addr: fe80::7ae7:d1ff:fe72:5a7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:883334 errors:0 dropped:0 overruns:0 frame:0 TX packets:281119 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:202144816 (202.1 MB) TX bytes:148539506 (148.5 MB) Interrupt:43 Base address:0x2000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:680408 errors:0 dropped:0 overruns:0 frame:0 TX packets:680408 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:383428479 (383.4 MB) TX bytes:383428479 (383.4 MB) xenbr0Link encap:Ethernet HWaddr 78:e7:d1:72:05:a7 inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::f02c:82ff:fe1b:1abc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:735854 errors:0 dropped:0 overruns:0 frame:0 TX packets:280977 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:175547260 (175.5 MB) TX bytes:148518318 (148.5 MB) - lis@UbuntuServer:~$ ifconfigeth0 Link encap:Ethernet HWaddr 12:1f:9d:1f:62:4c inet addr:192.168.100.221 Bcast:192.168.100.255 Mask:255.255.255.0 inet6 addr: fe80::101f:9dff:fe1f:624c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5419443 errors:0 dropped:0 overruns:0 frame:0 TX packets:2245580 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7458905436 (7.4 GB) TX bytes:244815051 (244.8 MB) Interrupt:26 eth0:1Link encap:Ethernet HWaddr 12:1f:9d:1f:62:4c inet addr:192.168.110.1 Bcast:192.168.120.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:26 eth0:2Link encap:Ethernet HWaddr 12:1f:9d:1f:62:4c inet addr:192.168.100.224 Bcast:192.168.100.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:26 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) virbr0Link encap:Ethernet HWaddr 3e:86:97:11:da:21 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) - [root@localhost ~]# ifconfigeth0 Link encap:Ethernet HWaddr 78:E7:D1:55:CD:8C UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:50546572 errors:0 dropped:0 overruns:0 frame:0 TX packets:25511413 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4193390563 (3.9 GiB) TX bytes:3644720382 (3.3 GiB) Interrupt:254 Base address:0xc000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2110471 errors:0 dropped:0 overruns:0 frame:0 TX packets:2110471 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2181820646 (2.0 GiB) TX bytes:2181820646 (2.0 GiB) vif43.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP PROMISC MTU:1500 Metric:1 RX packets:2246978 errors:0 dropped:0 overruns:0 frame:0 TX packets:5422937 errors:0 dropped:44 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:213788859 (203.8 MiB) TX bytes:3242683616 (3.0 GiB) vif44.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP PROMISC MTU:1500 Metric:1 RX packets:849 errors:0 dropped:0
[Openstack] Bugmail avalanche coming up ?
Everyone, As we get ready to release Essex, I should move all Essex blueprints and bugs (for Nova, Glance, Horizon and Keystone) to target the release milestone, in an effort to present all features and bugs fixed on that release a single page, like: https://launchpad.net/nova/diablo/2011.3 For those subscribed to bugmail, it will result in a lot of emails (around 1600 for all projects, 800 for Nova only). Alternatively, we could keep the features on bugs on each milestone page (like https://launchpad.net/nova/essex/essex-rc2), and point to them from each final release page. It's slightly less like a reference page, but a page with 750 bugs listed is probably not easy to parse anyway. Thoughts ? -- 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 immaturity
The "immaturity" being exposed here has nothing to do with neither stability nor bugs - in fact the angle is more about an ease of deployment.Such statements are not new, and well known from "enterprises" point of view.I remember same articles about Linux, few years back about Zimbra, few months back about proxmox, etc...This is an endless statement : "Is it possible for a community-driven project to find it's place in business needs ?" The answer for Openstack is NO, when it comes to ease of deployment compared to VMmware, and any CLI-less required installers...But even if fantastic progress has been made, on the different projects, let's face it, even more progress are required today to give a satisfaction to the OP.Let's keep working as we are doing : fixing, testing, thinking, updating.When all the projects will be stable enough to work on a same level - I'm quite confident we could see more positives feedbacks from Gartner Nuage Co - Razique Mahrouarazique.mahr...@gmail.com Le 4 avr. 2012 à 14:48, Jacek Artymiak a écrit :It depends on what you expect OpenStack to do for you. If you wantpre-packaged, click-to-install software, it is not there, yet. But ifyou want to be able to influence the future of the project you want tobet your business on, you have a much higher chance of doing that withOpenStack than with other projects in this space.Just my $.02 worth.Jacek Artymiakauthor: http://docs.openstack.org/api/openstack-compute/programmer/content/(please submit patches so we can improve this document)On Wed, Apr 4, 2012 at 12:24 PM, Sébastien Han han.sebast...@gmail.com wrote:Hi everyone,According to the statement of this article from Gartnergrouphttp://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/Openstackisahighly immature platform.But why?What's make Openstack so immature?Any comments on that?Thank you in advance :)___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] Bugmail avalanche coming up ?
On 04/04/2012 09:06 AM, Thierry Carrez wrote: Everyone, As we get ready to release Essex, I should move all Essex blueprints and bugs (for Nova, Glance, Horizon and Keystone) to target the release milestone, in an effort to present all features and bugs fixed on that release a single page, like: https://launchpad.net/nova/diablo/2011.3 For those subscribed to bugmail, it will result in a lot of emails (around 1600 for all projects, 800 for Nova only). Alternatively, we could keep the features on bugs on each milestone page (like https://launchpad.net/nova/essex/essex-rc2), and point to them from each final release page. It's slightly less like a reference page, but a page with 750 bugs listed is probably not easy to parse anyway. Thoughts ? I say go for it. I don't think the email volume should be a factor. I think it would be nice to have a full picture of Essex in one place. -- 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
Re: [Openstack] OpenStack immaturity
H. While ease of deployment is definitely an area of future strength for OS, the gap is closing rapidly and the reality for the enterprise is that initial, comparable (apples to apples) VMWare installations all come with an initial professional services engagement anyway. Having just done a bake-off twixt the latest OS builds and VMWare for creating an enterprise private IaaS cloud, my strategic money's on OpenStack and the community is starting to make significant in-roads on the tactical value as well. Lots of areas of future strength but the promise remains immense and the feasibility for the enterprise continues to grow. Keep up the good work. Keep Calm, Carry On, and all that. Jan PS: Anybody got an extra ticket to the design summit? On Apr 4, 2012, at 6:14 AM, Razique Mahroua razique.mahr...@gmail.com wrote: The immaturity being exposed here has nothing to do with neither stability nor bugs - in fact the angle is more about an ease of deployment. Such statements are not new, and well known from enterprises point of view. I remember same articles about Linux, few years back about Zimbra, few months back about proxmox, etc... This is an endless statement : Is it possible for a community-driven project to find it's place in business needs ? The answer for Openstack is NO, when it comes to ease of deployment compared to VMmware, and any CLI-less required installers... But even if fantastic progress has been made, on the different projects, let's face it, even more progress are required today to give a satisfaction to the OP. Let's keep working as we are doing : fixing, testing, thinking, updating. When all the projects will be stable enough to work on a same level - I'm quite confident we could see more positives feedbacks from Gartner Nuage Co - Razique Mahroua razique.mahr...@gmail.com NUAGECO-LOGO-Fblan_petit.jpg Le 4 avr. 2012 à 14:48, Jacek Artymiak a écrit : It depends on what you expect OpenStack to do for you. If you want pre-packaged, click-to-install software, it is not there, yet. But if you want to be able to influence the future of the project you want to bet your business on, you have a much higher chance of doing that with OpenStack than with other projects in this space. Just my $.02 worth. Jacek Artymiak author: http://docs.openstack.org/api/openstack-compute/programmer/content/ (please submit patches so we can improve this document) On Wed, Apr 4, 2012 at 12:24 PM, Sébastien Han han.sebast...@gmail.com wrote: Hi everyone, According to the statement of this article from Gartner group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a highly immature platform. But why? What's make Openstack so immature? Any comments on that? Thank you in advance :) ___ 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 Wed, Apr 4, 2012 at 8:14 AM, Razique Mahroua razique.mahr...@gmail.comwrote: The immaturity being exposed here has nothing to do with neither stability nor bugs - in fact the angle is more about an ease of deployment. Such statements are not new, and well known from enterprises point of view. I remember same articles about Linux, few years back about Zimbra, few months back about proxmox, etc... This is an endless statement : Is it possible for a community-driven project to find it's place in business needs ? The answer for Openstack is NO, when it comes to ease of deployment compared to VMmware, and any CLI-less required installers... But even if fantastic progress has been made, on the different projects, let's face it, even more progress are required today to give a satisfaction to the OP. Let's keep working as we are doing : fixing, testing, thinking, updating. When all the projects will be stable enough to work on a same level - I'm quite confident we could see more positives feedbacks from Gartner *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 4 avr. 2012 à 14:48, Jacek Artymiak a écrit : It depends on what you expect OpenStack to do for you. If you want pre-packaged, click-to-install software, it is not there, yet. But if you want to be able to influence the future of the project you want to bet your business on, you have a much higher chance of doing that with OpenStack than with other projects in this space. Just my $.02 worth. Jacek Artymiak author: http://docs.openstack.org/api/openstack-compute/programmer/content/ (please submit patches so we can improve this document) On Wed, Apr 4, 2012 at 12:24 PM, Sébastien Han han.sebast...@gmail.com wrote: Hi everyone, According to the statement of this article from Gartner group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a highly immature platform. But why? What's make Openstack so immature? Any comments on that? Thank you in advance :) ___ 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] Best approach for deploying Essex?
On Tue, Apr 3, 2012 at 2:21 PM, Adam Gandelman ad...@canonical.com wrote: On 04/03/2012 08:20 AM, Lillie Ross-CDSR11 wrote: My question is, should I base our new installation directly off the Essex branch in the git repository, or use the packages that will be deployed as part of the associated Ubuntu 12.04LTS release? With Diablo, I was forced to use packages from the ManagedIT PPA with additional Keystone patches to get a consistent, stable platform up and running. Obviously, some of these problems were due to confusion caused by various documents describing different incarnations of Openstack, and not really knowing what was current and stable. Especially the packages shipped with Ubuntu made assumptions about how Openstack was to be deployed that wasn't really apparent. [snip] Perhaps when we release Essex into Precise this/next week, we'll put some notes somewhere outlining any Ubuntu-specific changes for those who are interested. DreamHost is interested! It'd be great if you could do this :-) 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
[Openstack] nova-manage error message CRITICAL nova [-] cannot import name util
Hi, I just install the current source code of nova, glance and python-novaclient on a CentOS 6.2 node. Running command: #nova-manage db sync Gives me the following error message: Command failed, please check log for more info 2012-04-04 16:40:57 CRITICAL nova [-] cannot import name util Any idea what I do wrong? Best Regeards vic smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] python-glanceclient
On Tue, Apr 3, 2012 at 10:39 PM, Brian Waldon brian.wal...@rackspace.com wrote: 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. Coolness! I've added it to the command mapping in http://wiki.openstack.org/UnifiedCLI/Mapping and it looks pretty close. (Ignoring the verb-object vs object-verb debate). The biggest difference is the name for image membser: 'member' vs 'image-member'. I decided that 'member' was a bit too generic for a combined client; with a glance-only client that context makes it obvious. 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 I see some things in the old CLI that I don't see in the new one at a quick glance. Will do more study once it is in DevStack (see below). 4) Integrate with DevStack It's on the roadmap now dt -- Dean Troyer dtro...@gmail.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
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
Re: [Openstack] Dashboard VNC Console failed to connect to server
Lucian - Could you also paste your iptables nat rules to the question? Usually, when I get into a funky network state like you are in, I bust out tcpdump and map out exactly how packets are getting moved from interface to interface. That usually gets to the problem quickly. A On Wed, Apr 4, 2012 at 5:53 AM, Lucian Thomaz luciantho...@hotmail.comwrote: Hi Vish, Thank you, it's really working, but I'm having another trouble yet. I'm having this trouble in the log of the machine from Dashboard: wget: can't connect to remote host (169.254.169.254): No route to host And there are some other thing weird, in the log I can see that the network is trying during a while get the private ip for the machine and sometime it works, but sometime the network can't take that and so it takes a public ip from dhcp. Do you know something about that? Sending select for 10.0.0.3... Received DHCP NAK Sending discover... Sending select for 10.0.0.3... Received DHCP NAK Sending discover... Sending select for 192.168.100.219... Lease of 192.168.100.219 obtained, lease time 3600 starting DHCP forEthernet interface eth0 [ [1;32mOK [0;39m ] cloud-setup: checking http://169.254.169.254/2009-04-04/meta-data/instance-id wget: can't connect to remote host (169.254.169.254): No route to host My question in lauchpad have all my configurations and log. The only thing that I added in the configurations diferent from launchpad was this two flags: --cc_host=192.168.100.140 --routing_source_ip=192.168.100.140 https://answers.launchpad.net/nova/+question/192153 *Lucian Thomaz * Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server From: vishvana...@gmail.com Date: Tue, 3 Apr 2012 11:16:04 -0700 CC: sleepsonthefl...@gmail.com; openstack@lists.launchpad.net To: luciantho...@hotmail.com It is working! You are in the bios screen, so you probably just need to wait (software mode booting can take a while) If the vm doesn't ever actually boot, you may be attempting to boot a non-bootable image. ___ 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 error message CRITICAL nova [-] cannot import name util
On 04/04/2012 11:36 AM, Mauch, Viktor (SCC) wrote: Hi, I just install the current source code of nova, glance and python-novaclient on a CentOS 6.2 node. Running command: #nova-manage db sync Gives me the following error message: Command failed, please check log for more info 2012-04-04 16:40:57 CRITICAL nova [-] cannot import name util Any idea what I do wrong? How did you do the install? Did you use packages? If so, which ones? -- 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
Re: [Openstack] nova-manage error message CRITICAL nova [-] cannot import name util
Am 04.04.2012 18:29, schrieb Russell Bryant: On 04/04/2012 11:36 AM, Mauch, Viktor (SCC) wrote: Hi, I just install the current source code of nova, glance and python-novaclient on a CentOS 6.2 node. Running command: #nova-manage db sync Gives me the following error message: Command failed, please check log for more info 2012-04-04 16:40:57 CRITICAL nova [-] cannot import name util Any idea what I do wrong? How did you do the install? Did you use packages? If so, which ones? Hi, No, I used the current available source code from git repository: I used CentOS 6.2 with all current updates I imported the EPEL Repository: http://fedoraproject.org/wiki/EPEL Then: #yum install python-devel openssl-devel git qemu-kvm qemu-img libvirt virt-manager xorg-x11-xauth xorg-x11-server-utils mysql mysql-server euca2ools gcc gcc-c++ make libxml2-devel libxslt-devel python-gflags python-pip #easy_install virtualenv greenlet pip eventlet iso8601 lockfile webob paste pastedeploy routes sqlalchemy migrate paramiko nose pygments babel wsgiref markdown xattr kombu utils #system-config-firewall-tui # deactivate firewall #nano /etc/sysconfig/selinux# set ‘SELINUX=disabled’ #reboot #git clone https://github.com/openstack/nova.git #./run_tests.sh python setup.py build python setup.py install #git clone https://github.com/openstack/glance.git python setup.py build python setup.py install #git clone https://github.com/openstack/python-novaclient.git python setup.py build python setup.py install #nova-manage db sync Command failed, please check log for more info 2012-04-04 16:40:57 CRITICAL nova [-] cannot import name util I also try the stable diablo source code and the current source code from grid dynamics. But here I got another error message when tried to run nova-manage db sync: #nova-manage db sync /usr/lib/python2.6/site-packages/migrate-0.2.2-py2.6.egg/migrate/versioning/unique_instance.py:19: DeprecationWarning: object.new() takes no parameters instances[key] = super(UniqueInstance,cls).new(cls,*p,**k) Possible wrong number of arguments supplied Sync the database up to the most recent version. Usage: nova-manage db sync [options] Options: -h, --help show this help message and exit --version= Database version 2012-04-04 17:41:00,344 CRITICAL nova [-] init() takes exactly 1 argument (2 given) 2012-04-04 17:41:00,344 CRITICAL nova [-] init() takes exactly 1 argument (2 given) Thanks for your help!! Best Regards vic ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Dashboard VNC Console failed to connect to server
Anthony, I added my iptables rules in the launchpad question https://answers.launchpad.net/nova/+question/192153 And I'll try the tcpdump, thanks. Lucian Thomaz Date: Wed, 4 Apr 2012 09:25:43 -0700 Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server From: sleepsonthefl...@gmail.com To: luciantho...@hotmail.com CC: vishvana...@gmail.com; openstack@lists.launchpad.net Lucian - Could you also paste your iptables nat rules to the question? Usually, when I get into a funky network state like you are in, I bust out tcpdump and map out exactly how packets are getting moved from interface to interface. That usually gets to the problem quickly. A On Wed, Apr 4, 2012 at 5:53 AM, Lucian Thomaz luciantho...@hotmail.com wrote: Hi Vish,Thank you, it's really working, but I'm having another trouble yet. I'm having this trouble in the log of the machine from Dashboard: wget: can't connect to remote host (169.254.169.254): No route to host And there are some other thing weird, in the log I can see that the network is trying during a while get the private ip for the machine and sometime it works, but sometime the network can't take that and so it takes a public ip from dhcp. Do you know something about that? Sending select for 10.0.0.3... Received DHCP NAK Sending discover... Sending select for 10.0.0.3... Received DHCP NAK Sending discover... Sending select for 192.168.100.219... Lease of 192.168.100.219 obtained, lease time 3600 starting DHCP forEthernet interface eth0 [ [1;32mOK [0;39m ] cloud-setup: checking http://169.254.169.254/2009-04-04/meta-data/instance-id wget: can't connect to remote host (169.254.169.254): No route to host My question in lauchpad have all my configurations and log. The only thing that I added in the configurations diferent from launchpad was this two flags: --cc_host=192.168.100.140--routing_source_ip=192.168.100.140 https://answers.launchpad.net/nova/+question/192153 Lucian Thomaz Subject: Re: [Openstack] Dashboard VNC Console failed to connect to server From: vishvana...@gmail.com Date: Tue, 3 Apr 2012 11:16:04 -0700 CC: sleepsonthefl...@gmail.com; openstack@lists.launchpad.net To: luciantho...@hotmail.com It is working! You are in the bios screen, so you probably just need to wait (software mode booting can take a while) If the vm doesn't ever actually boot, you may be attempting to boot a non-bootable image. ___ 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..
On Apr 3, 2012, at 5:49 PM, Michael March wrote: I accidentally posted this on openstack-operat...@lists.openstack.org.. -- Forwarded message -- Everyone, After googlin' around I can not find any docs on how to setup OpenStack with ESXi as a hypervisor. This official link is dead: http://nova.openstack.org/vmwareapi_readme.html Does anyone have any links that might help in this endeavor? thanks! Hi Mike: That link was killed by this commit authored by Doug Hellmann about a month ago: https://github.com/openstack/nova/commit/c16cd04cf61fc Doug, do you recall why the vmwareapi_readme.rst docs got moved to the unused_docs list? Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.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] ESXi documentation..
I think it was because it was not linked from any of the other rst files. Which table of contents should it be listed in? Doug On Apr 4, 2012, at 1:41 PM, Lorin Hochstein lo...@nimbisservices.com wrote: On Apr 3, 2012, at 5:49 PM, Michael March wrote: I accidentally posted this on openstack-operat...@lists.openstack.org.. -- Forwarded message -- Everyone, After googlin' around I can not find any docs on how to setup OpenStack with ESXi as a hypervisor. This official link is dead: http://nova.openstack.org/vmwareapi_readme.html Does anyone have any links that might help in this endeavor? thanks! Hi Mike: That link was killed by this commit authored by Doug Hellmann about a month ago: https://github.com/openstack/nova/commit/c16cd04cf61fc Doug, do you recall why the vmwareapi_readme.rst docs got moved to the unused_docs list? Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.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] nova-manage error message CRITICAL nova [-] cannot import name util
On 04/04/2012 01:21 PM, Viktor Mauch wrote: Am 04.04.2012 18:29, schrieb Russell Bryant: On 04/04/2012 11:36 AM, Mauch, Viktor (SCC) wrote: Hi, I just install the current source code of nova, glance and python-novaclient on a CentOS 6.2 node. Running command: #nova-manage db sync Gives me the following error message: Command failed, please check log for more info 2012-04-04 16:40:57 CRITICAL nova [-] cannot import name util Any idea what I do wrong? How did you do the install? Did you use packages? If so, which ones? Hi, No, I used the current available source code from git repository: I used CentOS 6.2 with all current updates I imported the EPEL Repository: http://fedoraproject.org/wiki/EPEL If you're already using EPEL, there are packages there for OpenStack. They are currently on Diablo, but will be updated to Essex within the next week or two. -- 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
Re: [Openstack] ESXi documentation..
Doug: I'm not sure. I'll port these to compute admin docs so it shows up in the OpenStack Compute Admin guide at docs.openstack.org. Mike, in the meantime, you can view this page by going to: https://github.com/openstack/nova/blob/master/doc/source/vmwareapi_readme.rst The missing block diagram is here: https://github.com/openstack/nova/blob/master/doc/source/images/vmwareapi_blockdiagram.jpg Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com On Apr 4, 2012, at 1:43 PM, Doug Hellmann wrote: I think it was because it was not linked from any of the other rst files. Which table of contents should it be listed in? Doug On Apr 4, 2012, at 1:41 PM, Lorin Hochstein lo...@nimbisservices.com wrote: On Apr 3, 2012, at 5:49 PM, Michael March wrote: I accidentally posted this on openstack-operat...@lists.openstack.org.. -- Forwarded message -- Everyone, After googlin' around I can not find any docs on how to setup OpenStack with ESXi as a hypervisor. This official link is dead: http://nova.openstack.org/vmwareapi_readme.html Does anyone have any links that might help in this endeavor? thanks! Hi Mike: That link was killed by this commit authored by Doug Hellmann about a month ago: https://github.com/openstack/nova/commit/c16cd04cf61fc Doug, do you recall why the vmwareapi_readme.rst docs got moved to the unused_docs list? Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.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] ESXi documentation..
Thanks everyone, BTW, I was able to pull up a Google cache version of the document this morning too. Is this one page the extent of the vSphere docs? On Wed, Apr 4, 2012 at 10:56 AM, Lorin Hochstein lo...@nimbisservices.comwrote: Doug: I'm not sure. I'll port these to compute admin docs so it shows up in the OpenStack Compute Admin guide at docs.openstack.org. Mike, in the meantime, you can view this page by going to: https://github.com/openstack/nova/blob/master/doc/source/vmwareapi_readme.rst The missing block diagram is here: https://github.com/openstack/nova/blob/master/doc/source/images/vmwareapi_blockdiagram.jpg Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com On Apr 4, 2012, at 1:43 PM, Doug Hellmann wrote: I think it was because it was not linked from any of the other rst files. Which table of contents should it be listed in? Doug On Apr 4, 2012, at 1:41 PM, Lorin Hochstein lo...@nimbisservices.com wrote: On Apr 3, 2012, at 5:49 PM, Michael March wrote: I accidentally posted this on openstack-operat...@lists.openstack.org.. -- Forwarded message -- Everyone, After googlin' around I can not find any docs on how to setup OpenStack with ESXi as a hypervisor. This official link is dead: http://nova.openstack.org/vmwareapi_readme.html Does anyone have any links that might help in this endeavor? thanks! Hi Mike: That link was killed by this commit authored by Doug Hellmann about a month ago: https://github.com/openstack/nova/commit/c16cd04cf61fc Doug, do you recall why the vmwareapi_readme.rst docs got moved to the unused_docs list? Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com -- -- 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 immaturity
According to the statement of this article from Gartner group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a highly immature platform. But why? What's make Openstack so immature? Any comments on that? Thank you in advance :) I agree that it's an immature platform. That said, it's also a very young platform and isn't that to be expected? There's a number of things that need to be fixed before I'd ever recommend Nova's use in production: 1. There's no upgrade path currently. Upgrading requires fairly substantial downtime. 2. Live migration is broken. Utterly. 3. Every release fixes so many things that it's really important to upgrade every time; however, only one release will likely be supported every Ubuntu LTS release, meaning you're either stuck with a really old (likely broken) version of nova, or you're stuck will a very likely unstable version of Ubuntu. This will be easier over time, when nova is more stable and has less bugs, but it's incredibly painful right now. That said, I feel OpenStack's strengths greatly outweigh its immatureness. I ran a private cloud at my last organization using a VMWare ESXi cluster. It was more mature, upgrades worked appropriately, live migration was solid, etc. I had (and still have) the choice to run VMWare for my current project and am extremely happy with my choice of OpenStack. The flexibility provided by the platform and my ability to contribute to its future make its immaturity a non-concern. Every release gets closer and closer to a stability point I'm comfortable with. This article isn't bad news. In fact, I'd say it shows that competitors see OpenStack as a fairly major threat. We should be celebrating this ;). - Ryan ___ 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
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 From: openstack-bounces+tim.bell=cern...@lists.launchpad.net [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On Behalf Of Jan Drake Sent: 04 April 2012 16:37 To: Razique Mahroua Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] OpenStack immaturity H. While ease of deployment is definitely an area of future strength for OS, the gap is closing rapidly and the reality for the enterprise is that initial, comparable (apples to apples) VMWare installations all come with an initial professional services engagement anyway. Having just done a bake-off twixt the latest OS builds and VMWare for creating an enterprise private IaaS cloud, my strategic money's on OpenStack and the community is starting to make significant in-roads on the tactical value as well. Lots of areas of future strength but the promise remains immense and the feasibility for the enterprise continues to grow. Keep up the good work. Keep Calm, Carry On, and all that. Jan PS: Anybody got an extra ticket to the design summit? On Apr 4, 2012, at 6:14 AM, Razique Mahroua razique.mahr...@gmail.com wrote: The immaturity being exposed here has nothing to do with neither stability nor bugs - in fact the angle is more about an ease of deployment. Such statements are not new, and well known from enterprises point of view. I remember same articles about Linux, few years back about Zimbra, few months back about proxmox, etc... This is an endless statement : Is it possible for a community-driven project to find it's place in business needs ? The answer for Openstack is NO, when it comes to ease of deployment compared to VMmware, and any CLI-less required installers... But even if fantastic progress has been made, on the different projects, let's face it, even more progress are required today to give a satisfaction to the OP. Let's keep working as we are doing : fixing, testing, thinking, updating. When all the projects will be stable enough to work on a same level - I'm quite confident we could see more positives feedbacks from Gartner Nuage Co - Razique Mahroua razique.mahr...@gmail.com NUAGECO-LOGO-Fblan_petit.jpg Le 4 avr. 2012 à 14:48, Jacek Artymiak a écrit : It depends on what you expect OpenStack to do for you. If you want pre-packaged, click-to-install software, it is not there, yet. But if you want to be able to influence the future of the project you want to bet your business on, you have a much higher chance of doing that with OpenStack than with other projects in this space. Just my $.02 worth. Jacek Artymiak author: http://docs.openstack.org/api/openstack-compute/programmer/content/ (please submit patches so we can improve this document) On Wed, Apr 4, 2012 at 12:24 PM, Sébastien Han han.sebast...@gmail.com wrote: Hi everyone, According to the statement of this article from Gartner group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a highly immature platform. But why? What's make Openstack so immature? Any comments on that? Thank you in advance :) ___ 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 smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] OpenStack Plugin for Jenkins
I've created a quick OpenStack plugin for Jenkins, using the Java bindings that Luis I created. It's available on github here: https://github.com/platformlayer/openstack-jenkins (no binaries - yet!) Right now, it has the same (jenkins) functionality as the S3 plugin; it can store artifacts into Swift. I'm going to implement compute next so that we can use OpenStack VMs to 'burst' building, like the EC2 plugin does. I'd love to hear from anyone that would be interested in using this, to better understand what everyone wants. For example, the S3 plugin flattens all directories when copying artifacts, that just seems wrong to me, so I'd like to just fix it. 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
Re: [Openstack] OpenStack immaturity
There are many projects rolled up into the thing called OpenStack. Nova is only one of them and is the one that most people are talking about when they say OpenStack. This does a huge disservice to the other projects especially Swift. It's very frustrating to see the other projects all painted with the Nova brush. On Wed, Apr 4, 2012 at 1:25 PM, Ryan Lane rl...@wikimedia.org wrote: According to the statement of this article from Gartner group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a highly immature platform. But why? What's make Openstack so immature? Any comments on that? Thank you in advance :) I agree that it's an immature platform. That said, it's also a very young platform and isn't that to be expected? There's a number of things that need to be fixed before I'd ever recommend Nova's use in production: 1. There's no upgrade path currently. Upgrading requires fairly substantial downtime. 2. Live migration is broken. Utterly. 3. Every release fixes so many things that it's really important to upgrade every time; however, only one release will likely be supported every Ubuntu LTS release, meaning you're either stuck with a really old (likely broken) version of nova, or you're stuck will a very likely unstable version of Ubuntu. This will be easier over time, when nova is more stable and has less bugs, but it's incredibly painful right now. That said, I feel OpenStack's strengths greatly outweigh its immatureness. I ran a private cloud at my last organization using a VMWare ESXi cluster. It was more mature, upgrades worked appropriately, live migration was solid, etc. I had (and still have) the choice to run VMWare for my current project and am extremely happy with my choice of OpenStack. The flexibility provided by the platform and my ability to contribute to its future make its immaturity a non-concern. Every release gets closer and closer to a stability point I'm comfortable with. This article isn't bad news. In fact, I'd say it shows that competitors see OpenStack as a fairly major threat. We should be celebrating this ;). - Ryan ___ 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 Plugin for Jenkins
Justin++ This is really cool plugin. Good Job! 2012/4/4 Justin Santa Barbara jus...@fathomdb.com: I've created a quick OpenStack plugin for Jenkins, using the Java bindings that Luis I created. It's available on github here: https://github.com/platformlayer/openstack-jenkins (no binaries - yet!) Right now, it has the same (jenkins) functionality as the S3 plugin; it can store artifacts into Swift. I'm going to implement compute next so that we can use OpenStack VMs to 'burst' building, like the EC2 plugin does. I'd love to hear from anyone that would be interested in using this, to better understand what everyone wants. For example, the S3 plugin flattens all directories when copying artifacts, that just seems wrong to me, so I'd like to just fix it. 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 ___ 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
+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
[Openstack] Nova 2012.1 RC4 available
Hello everyone, Murphy striked, two regressions were found in recent commits in Nova. We therefore rebuilt a new (and hopefully last) release candidate for OpenStack Compute (Nova) 2012.1: https://launchpad.net/nova/essex/essex-rc4 Now let's get those release notes right: http://wiki.openstack.org/ReleaseNotes/Essex Regards, -- 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 immaturity
Maybe it would be more interesting, instead of getting on the defensive to instead start asking what people think is broken or is immature and fix those areas. Push forward, get peoples feelings about it, and take it as constructive input. If people think its immature, ask for why and then fix those points... -Josh On 4/4/12 1:05 PM, Jay Payne lett...@gmail.com wrote: There are many projects rolled up into the thing called OpenStack. Nova is only one of them and is the one that most people are talking about when they say OpenStack. This does a huge disservice to the other projects especially Swift. It's very frustrating to see the other projects all painted with the Nova brush. On Wed, Apr 4, 2012 at 1:25 PM, Ryan Lane rl...@wikimedia.org wrote: According to the statement of this article from Gartner group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a highly immature platform. But why? What's make Openstack so immature? Any comments on that? Thank you in advance :) I agree that it's an immature platform. That said, it's also a very young platform and isn't that to be expected? There's a number of things that need to be fixed before I'd ever recommend Nova's use in production: 1. There's no upgrade path currently. Upgrading requires fairly substantial downtime. 2. Live migration is broken. Utterly. 3. Every release fixes so many things that it's really important to upgrade every time; however, only one release will likely be supported every Ubuntu LTS release, meaning you're either stuck with a really old (likely broken) version of nova, or you're stuck will a very likely unstable version of Ubuntu. This will be easier over time, when nova is more stable and has less bugs, but it's incredibly painful right now. That said, I feel OpenStack's strengths greatly outweigh its immatureness. I ran a private cloud at my last organization using a VMWare ESXi cluster. It was more mature, upgrades worked appropriately, live migration was solid, etc. I had (and still have) the choice to run VMWare for my current project and am extremely happy with my choice of OpenStack. The flexibility provided by the platform and my ability to contribute to its future make its immaturity a non-concern. Every release gets closer and closer to a stability point I'm comfortable with. This article isn't bad news. In fact, I'd say it shows that competitors see OpenStack as a fairly major threat. We should be celebrating this ;). - Ryan ___ 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] Best approach for deploying Essex?
Hi Kevin, I'm in the process of looking at the Ubuntu packages. I've booted up 3 12.04 instances in our existing cloud and have installed the Ubuntu packages. I'm playing with the new keystone 'lite' service as I write this. In fact, I'm looking at your script to bootstrap keystone versus the script installed via the package in /usr/share/keystone. So far so good, other than some iptable hacks that will be needed (I believe, but haven't looked closely) to let these instances to see their underlying public ip addresses (no problem, obviously seeing their private vlan address). Thanks for your inputs. Regards, Ross On Apr 4, 2012, at 4:20 AM, Kevin Jackson wrote: +1 on the Ubuntu 12.04 Precise and Essex. Whilst there are other methods and OS of choice, given you've been using 11.10 - 12.04 is the natural home for it. The betas of Precise are rock-solid and can vouch for the Ubuntu packaging following quite quickly behind the devs. I highly recommend this approach. Kev On 3 April 2012 20:02, Lillie Ross-CDSR11 ross.lil...@motorolasolutions.commailto:ross.lil...@motorolasolutions.com wrote: Hi Adam, Thanks for the update. Actually, I'm in the process of reading about your testing and integration framework for Openstack (http://ubuntuserver.wordpress.com/2012/02/08/704/) as I write this. Yes, Keystone integration seemed to be the big bugaboo in the Ubuntu/Diablo release. I've successfully got everything authenticating with keystone in our current deployment, but as you well know, this precludes using S3 bindings with Swift, and you must use the Openstack glance client to bundle/upload images. This had me pulling my hair out in the early stages. Today I've spun up 3 generic 11.10 servers that I'm planning on testing the next Ubuntu release and Openstack packages. Should I start my testing with the beta1 release of 12.04LTS? In particular I'm interested in seeing and understanding the process of migrating my existing installation and configs to the new release. Once I'm satisfied that I understand everything (not possible) in the new release, I can migrate our operational cloud in a couple of days. Also, what's the best place to keep abreast on the Ubuntu/Canonical integration of openstack? The Ubuntu Wiki? Mailing list? Thanks again, Ross On Apr 3, 2012, at 1:21 PM, Adam Gandelman wrote: On 04/03/2012 08:20 AM, Lillie Ross-CDSR11 wrote: My question is, should I base our new installation directly off the Essex branch in the git repository, or use the packages that will be deployed as part of the associated Ubuntu 12.04LTS release? With Diablo, I was forced to use packages from the ManagedIT PPA with additional Keystone patches to get a consistent, stable platform up and running. Obviously, some of these problems were due to confusion caused by various documents describing different incarnations of Openstack, and not really knowing what was current and stable. Especially the packages shipped with Ubuntu made assumptions about how Openstack was to be deployed that wasn't really apparent. Hey Ross- I can say that the Ubuntu precise packages have been kept relatively in-sync with each components' trunk git repository this cycle. We've made a concerted effort to do weekly snapshot uploads of all Openstack components into the Precise archive starting from the beginning of the Essex+Precise dev cycles. We've also maintained our own trunk PPA (updated continously) around which we center our testing efforts. Now that we're nearing the release of Essex, we've been ensuring the release candidates hit our archive as soon as they are released. As soon as Essex final hits, it'll be uploaded into Ubuntu and give any users who care the remainder of the Ubuntu dev cycle (~1 month) to test and identify issues before LTS ships. Re: deployment assumptions. Last cycle, we were caught off-guard by Keystone's last-minute inclusion into Openstack core and the dependencies this introduced (dashboard especially) It's not that we were making assumptions about how Openstack Diablo should be deployed, just that there was no way we could shoe-horn a new component into the release so late in the game. This time around, a similar curve ball was thrown our way with the Keystone Lite rewrite, but we were able to get this sorted on our end relatively quickly to ensure pending security reviews and main inclusion processes for Keystone weren't blocked. We're making very few assumptions going into LTS and hope to provide as-close-to-pure Essex experience as any. I can only think of a few patches we're carrying, and there are only two default configuration files we ship that differ from those you'd find in the git repos [2]. Perhaps when we release Essex into Precise this/next week, we'll put some notes somewhere outlining any Ubuntu-specific changes for those who are interested. Hope that helps, and of course we
Re: [Openstack] OpenStack immaturity
Another perspective worth considering is immaturity vs growth. Are there enough progresses being made? When problems are identified, are these solved swiftly and effectively? I think the people involved in the OpenStack community do and have done a great job in this regard, and should be praised rather than bashed. I personally think that talking about immaturity does not address the major question one should ask: assess if the platform fit the bill for whatever goals/requirements one has. So going back to Sébastien Han's question: what are you looking for in OpenStack? My 2c A. On Wed, Apr 4, 2012 at 9:48 PM, Joshua Harlow harlo...@yahoo-inc.com wrote: Maybe it would be more interesting, instead of getting on the defensive to instead start asking what people think is broken or is immature and fix those areas. Push forward, get peoples feelings about it, and take it as constructive input. If people think its immature, ask for why and then fix those points... -Josh On 4/4/12 1:05 PM, Jay Payne lett...@gmail.com wrote: There are many projects rolled up into the thing called OpenStack. Nova is only one of them and is the one that most people are talking about when they say OpenStack. This does a huge disservice to the other projects especially Swift. It's very frustrating to see the other projects all painted with the Nova brush. On Wed, Apr 4, 2012 at 1:25 PM, Ryan Lane rl...@wikimedia.org wrote: According to the statement of this article from Gartner group http://blogs.gartner.com/lydia_leong/2012/04/03/citrix-cloudstack-openstack-and-the-war-for-open-source-clouds/ Openstack is a highly immature platform. But why? What's make Openstack so immature? Any comments on that? Thank you in advance :) I agree that it's an immature platform. That said, it's also a very young platform and isn't that to be expected? There's a number of things that need to be fixed before I'd ever recommend Nova's use in production: 1. There's no upgrade path currently. Upgrading requires fairly substantial downtime. 2. Live migration is broken. Utterly. 3. Every release fixes so many things that it's really important to upgrade every time; however, only one release will likely be supported every Ubuntu LTS release, meaning you're either stuck with a really old (likely broken) version of nova, or you're stuck will a very likely unstable version of Ubuntu. This will be easier over time, when nova is more stable and has less bugs, but it's incredibly painful right now. That said, I feel OpenStack's strengths greatly outweigh its immatureness. I ran a private cloud at my last organization using a VMWare ESXi cluster. It was more mature, upgrades worked appropriately, live migration was solid, etc. I had (and still have) the choice to run VMWare for my current project and am extremely happy with my choice of OpenStack. The flexibility provided by the platform and my ability to contribute to its future make its immaturity a non-concern. Every release gets closer and closer to a stability point I'm comfortable with. This article isn't bad news. In fact, I'd say it shows that competitors see OpenStack as a fairly major threat. We should be celebrating this ;). - Ryan ___ 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 Plugin for Jenkins
This is a plugin for OpenStack; it won't support any other clouds. This means there will be no baggage from having to support EC2, or any of the other clouds that JClouds supports. We can support all the OpenStack goodness directly. JClouds is great, but it's an abstraction layer that doesn't give OpenStack users anything. I hope the OpenStack CI team will join me in working on something that advances OpenStack, rather than spending any more time propping up the dying clouds :-) Justin On Wed, Apr 4, 2012 at 2:54 PM, Andrew Hutchings and...@linuxjedi.co.ukwrote: On 04/04/12 20:42, Justin Santa Barbara wrote: I've created a quick OpenStack plugin for Jenkins, using the Java bindings that Luis I created. It's available on github here: https://github.com/platformlayer/openstack-jenkins (no binaries - yet!) Whilst it is cool that there is effort going into this what does it give that the Jenkins Jclouds plugin does not? (I think it is at https://github.com/jenkinsci/jclouds-plugin) The OpenStack CI team are also assisting in the development of the Jcouds plugin with a view to using it on OpenStack's Jenkins server. Kind Regards -- Andrew Hutchings - LinuxJedi - http://www.linuxjedi.co.uk/ ___ 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
Justin, it's a pleasure work with you Great work with the Jenkins stuff Cheers! Luis On Thu, Apr 5, 2012 at 12:40 AM, Justin Santa Barbara jus...@fathomdb.comwrote: This is a plugin for OpenStack; it won't support any other clouds. This means there will be no baggage from having to support EC2, or any of the other clouds that JClouds supports. We can support all the OpenStack goodness directly. JClouds is great, but it's an abstraction layer that doesn't give OpenStack users anything. I hope the OpenStack CI team will join me in working on something that advances OpenStack, rather than spending any more time propping up the dying clouds :-) Justin On Wed, Apr 4, 2012 at 2:54 PM, Andrew Hutchings and...@linuxjedi.co.ukwrote: On 04/04/12 20:42, Justin Santa Barbara wrote: I've created a quick OpenStack plugin for Jenkins, using the Java bindings that Luis I created. It's available on github here: https://github.com/platformlayer/openstack-jenkins (no binaries - yet!) Whilst it is cool that there is effort going into this what does it give that the Jenkins Jclouds plugin does not? (I think it is at https://github.com/jenkinsci/jclouds-plugin) The OpenStack CI team are also assisting in the development of the Jcouds plugin with a view to using it on OpenStack's Jenkins server. Kind Regards -- Andrew Hutchings - LinuxJedi - http://www.linuxjedi.co.uk/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- --- Luis Alberto Gervaso Martin Woorea Solutions, S.L CEO CTO mobile: (+34) 627983344 luis@ luis.gerv...@gmail.comwoorea.es ___ 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
Justin Santa Barbara jus...@fathomdb.com writes: This is a plugin for OpenStack; it won't support any other clouds. This means there will be no baggage from having to support EC2, or any of the other clouds that JClouds supports. We can support all the OpenStack goodness directly. I second Andrew's commendation on your work on Java bindings for OpenStack, but I also share his concern that effort would be well spent helping with established projects. What you wrote above is pretty vague, and in my mind, not a compelling reason to start a new project rather than contributing to an existing one actively developed by a diverse and engaged group of people. JClouds is great, but it's an abstraction layer that doesn't give OpenStack users anything. On the contrary, there are a lot of people with apps running in clouds that are not OpenStack right now who would probably like to use OpenStack soon. Being able to run in multiple clouds simultaneously while migrating, not to mention being able to migrate without changing code, is a great reason to have an abstraction layer. I'm not so worried about OpenStack's performance that I think source-level vendor-lock-in is the way to keep users. I hope the OpenStack CI team will join me in working on something that advances OpenStack, rather than spending any more time propping up the dying clouds :-) I think providing a migration path for users to OpenStack is an excellent way to advance it. Since the Essex design summit, the OpenStack CI team has learned a lot about running tests on cloud nodes. In order to run the kinds of tests we need to run, we need features that aren't in any of the Jenkins cloud plugins currently. We need disposable machines that are only used for one test, which means spinning up and terminating hundreds of machines per day. We need to use machines from multiple providers simultaneously so that we're resilient against errors with one provider. We need to pull nodes from a pool of machines that have been spun up ahead of time for speed. We need to be able to select from different kinds of images for certain tests. Machines need to be checked for basic functionality before being added to the pool (we frequently get nodes without a functioning network). They need to be started from snapshots with cached data on them to avoid false negatives from network problems. We need to keep them around after failures to diagnose problems, and we need to delete those after a certain amount of time. These are just some of the things we've learned. None of those tasks are OpenStack specific, but they are all useful to someone who wants to use cloud computing nodes with Jenkins. In other words, an abstraction layer is the perfect place to put that kind of work. A layer that knows about things like images, pools of machines, how to retrieve them from a provider (any provider), and then another layer that hands that information to Jenkins. The devstack-gate[1] project is the system we use to do that right now. It's a set of python scripts that manages all of what I've described above, external to Jenkins. We consider it a prototype. That logic belongs in something accessible to Jenkins directly so that Jenkins can manage the full life-cycle of the node. That's why we're working with the jclouds developers on incorporating everything we've learned into jclouds (and yes, the pooling logic, etc, are going in jclouds, not the jclouds plugin -- Jenkins isn't the only system that might use that tactic), so that the jclouds Jenkins plugin can eventually support everything we're doing now, and more. I wish you well as I would any software that supports OpenStack. But I think the jclouds project is going to provide a great benefit to OpenStack as I outlined above, and I'm going to be thrilled when we are able to express the cloud testing requirements of the OpenStack CI project directly in Jenkins. As Monty has for quite some time, I would encourage anyone interested in working in this area to contribute to the jclouds project. And of course anyone interested in CI or developer tooling is welcome to contribute to the OpenStack CI system. We run the project infrastructure just like any other OpenStack project -- all of our code[2] and puppet scripts[3] are in gerrit and our bugs (we have a huge task list) are in launchpad[4]. We meet weekly on IRC[5]. [1] https://github.com/openstack-ci/devstack-gate [2] https://github.com/openstack/openstack-ci [3] https://github.com/openstack/openstack-ci-puppet [4] https://bugs.launchpad.net/openstack-ci/ [5] http://wiki.openstack.org/Meetings -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
[Openstack] make instances not communicate each other
Greeting: I want my instances not be able to communicate to each other, I know it is possible to set the firewall manually. I just want know if there are more graceful way to do that thanks William Herry -- Where there is a will, there is a way. williamherrych...@gmail.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] OpenStack Plugin for Jenkins
Thanks - there are some good feature requests here. Have you proposed a design summit session where you are going to talk about OpenStack features that you would like to see? Things like supporting cloud federation, instance pooling, or fixing that networking bug? The Jenkins features (e.g. associating a test to an image) should be done as part of Jenkins: JClouds plugin, OpenStack plugin, it doesn't matter - may the best code win. However, all the OpenStack features should be done as part of OpenStack itself, not buried in some third party project that is only available to people that use Java. 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] make instances not communicate each other
Use the flag --allow_same_net_traffic : This flag will allow all traffic from other vms (and host machines) in the same network. It defaults to true. If you would prefer to block all vm-vm traffic and use security groups to manage vm-vm traffic, set this flag to false. On Wed, Apr 4, 2012 at 6:59 PM, William Herry william.herry.ch...@gmail.com wrote: Greeting: I want my instances not be able to communicate to each other, I know it is possible to set the firewall manually. I just want know if there are more graceful way to do that thanks William Herry -- Where there is a will, there is a way. williamherrych...@gmail.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] Client debugs??
On Wed, Apr 4, 2012 at 7:24 PM, Joshua Harlow harlo...@yahoo-inc.com wrote: keystone token-get --debug U get: keystone: error: unrecognized arguments: --debug But if u do it before it works, odd. Guess that’s a “false” message/error. Actually that is exactly how it is supposed to work. Although it is hidden, --debug is a global option (defined in keystone/shell.py) just like --os_username and friends, which means it must appear before the command. All options that follow the command are command specific. dt -- Dean Troyer dtro...@gmail.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-poc] [Bug 960487] Re: Request deserializer does not pass an empty body
** Changed in: openstack-common Status: Fix Committed = In Progress -- 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/960487 Title: Request deserializer does not pass an empty body Status in openstack-common: In Progress Bug description: When a POST is sent via an API call and the body is empty the body is lost and not sent along and sending back a general 400 error. This should send a body even if it is empty to the method in the route specified. The common/wsgi.py Request deserializer for the body needs an update so that this is possible. This will allow the API developer to create a validation message to the client with what is invalid in the body of the action. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-common/+bug/960487/+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
