Re: [Openstack] what is the difference between 2013.1 and grizzly?

2013-04-01 Thread Liu Wenmao
Thank Oleg and Thierr, it's really helpful On Wed, Mar 27, 2013 at 5:20 PM, Thierry Carrez wrote: > Oleg Gelbukh wrote: > > Generally, grizzly-X is a milestone tag inside release cycle codenamed > > 'Grizzly'. > > Note that tagging scheme has changed between milestones 2 and 3 of > > 'Grizzly' r

[Openstack] Folsom with Quantum installer script

2013-04-01 Thread Darragh OReilly
Hi all, for anyone interested in playing with Quantum, I have written an  Ansible script that automates a Folsom with Quantum install onto 3  VirtualBox VMs - a controller node, a network node and 1 compute node. The script is at https://github.com/djoreilly/quantum-ansible and there  is a diagra

Re: [Openstack] Keystone Too Many Connections Problem

2013-04-01 Thread Dolph Mathews
I'm attempting to reproduce this now (haven't been successful with PKI + sqlite on disk), but in the meantime I opened a bug on this issue for tracking: https://bugs.launchpad.net/keystone/+bug/1162845 -Dolph On Fri, Mar 29, 2013 at 1:35 PM, Miller, Mark M (EB SW Cloud - R&D - Corvallis) wr

Re: [Openstack] Keystone Too Many Connections Problem

2013-04-01 Thread Dolph Mathews
I also opened bug 1162857, which produces a slightly different symptom with a different configuration (sqlite), but may share the same underlying cause. -Dolph On Mon, Apr 1, 2013 at 10:26 AM, Dolph Mathews wrote: > I'm attempting to reproduce this now (haven't been successful with PKI + > sql

Re: [Openstack] Keystone Too Many Connections Problem

2013-04-01 Thread Dolph Mathews
Mark, Which token driver are you using? -Dolph On Mon, Apr 1, 2013 at 10:49 AM, Dolph Mathews wrote: > I also opened bug 1162857, which produces a slightly different symptom > with a different configuration (sqlite), but may share the same underlying > cause. > > > -Dolph > > > On Mon, Apr 1,

Re: [Openstack] Keystone Too Many Connections Problem

2013-04-01 Thread Dolph Mathews
Thanks! I was able to reproduce and I've proposed a fix to both master and grizzly. master- https://review.openstack.org/#/c/25831/ grizzly- https://review.openstack.org/#/c/25833/ If you can verify this patch on your system, that would be really helpful. -Dolph On Mon, Apr 1, 2013 at 1:57 PM

[Openstack] openstack segregation and flavors

2013-04-01 Thread Jean-Daniel BUSSY
Hi stackers, I am looking for a way to separate groups of host with their own instance flavors. In the aggregation levels [cells, regions, availability zone, aggregates], where does the flavors aggregation starts? Since regions have their own components and own API, I would saw flavors are grouped

Re: [Openstack] nova calls libvirt but failed:Operation not supported

2013-04-01 Thread Aaron Rosen
Do you have the following line (bolded) in /etc/libvirt/qemu.conf ? cgroup_device_acl = [ "/dev/null", "/dev/full", "/dev/zero", "/dev/random", "/dev/urandom", "/dev/ptmx", "/dev/kvm", "/dev/kqemu", "/dev/rtc", "/dev/hpet"*,"/dev/net/tun",* ] On Mon, Apr 1, 2013 at 8:42 PM, Liu

[Openstack] nova calls libvirt but failed:Operation not supported

2013-04-01 Thread Liu Wenmao
Hi all: I use github to install nova and quantum, but when I launch an instance, nova-compute fails: 2013-04-02 11:00:15DEBUG [nova.openstack.common.lockutils] Released file lock "iptables" at /var/lock/nova/nova-iptables for method "_apply"... 2013-04-02 11:00:17ERROR [nova.compute.manag

Re: [Openstack] nova calls libvirt but failed:Operation not supported

2013-04-01 Thread Aaron Rosen
I believe that with older versions of libvirt you need to uncomment the following lines in /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" I'd also check what's in /var