[Openstack] OpenStack Community Weekly Newsletter (Mar 8-22)

Highlights of the week Kwapi: an energy efficiency architecture XLcloud HPC project focuses on providing high performance HPC services, while improving energy efficiency. Kwapi makes a smart u

[Openstack] Keystone Too Many Connections Problem

Hi, I have a loop that gets PKI tokens from Keystone (RC2). After about 116 loops I get the following error and have to reset Keystone to continue. Has anyone else run into this? Thanks, Mark (keystone.auth.controllers): 2013-03-29 11:14:01,274 ERROR (OperationalError) (1040, 'Too many conne

[Openstack] br-int not recreated after compute node reboot

I have a fairly fresh Folsom install on Quantal with just a couple of test virts. In preparation for setting up Ceph, I upgraded the kernel to linux-3.6.11 on my compute node, then rebooted. But, as the subject suggests, this went very badly as br-int wasn't recreated. BEFORE: http://pastebin.co

[Openstack] Documentation - Push for Grizzly

Hi all, We need your help to get the documentation up to scratch for grizzly. Please see if there is anything you can address from the list at: https://bugs.launchpad.net/openstack-manuals/+milestone/grizzly 55 bugs ready for your work 59 completed so far, 8 in progress Thanks to the efforts o

[Openstack] TC Election Results

The Sprint 2013 TC Election has concluded. The at-large members elected are: vishy ttx For a term of one year. mikal For a term of six months. Congratulations. http://www.cs.cornell.edu/w8/~andru/cgi-perl/civs/results.pl?id=E_5af0b5341a01b892 ___ M

[Openstack] OpenStack Grizzly Install Guide

Hi Stackers, I present to you my new guide : OpenStack Grizzly Install Guide by Bilel Msekni. This is an easy way to deploy Grizzly on a single node and get to know the new features it presents ! Two branches are currently created :

Re: [Openstack] [nova-network] add-network-to-project

thanks for the "admin" clarify : ) here is more information about other extensions avoid the problem: i read the policy.json file, find some other extension meet the same problem and watch how they impl for example. the quota api just shows like this GET v2/{tenant_id}/os-quota-sets/{tenant_id} S

[Openstack] Horizon and Swift Grizzly RC2 available !

Hello everyone, Due to various reported issues, we created new Grizzly release candidates for OpenStack Object Storage ("Swift") and OpenStack Dashboard ("Horizon"). You can find those RC2 tarballs and see lists of fixed bugs at: https://launchpad.net/swift/grizzly/1.8.0-rc2 https://launchpad.net

Re: [Openstack] nova-api-metadata on compute node with folsom

Actually it looks like you shouldn't need the iptables rule and nova-api-metadata running if you use this method http://docs.openstack.org/folsom/openstack-network/admin/content/adv_cfg_l3_agent_metadata.html On Fri, Mar 29, 2013 at 12:22 AM, Aaron Rosen wrote: > Hi, > > I believe you have this

Re: [Openstack] How to get around bug 1135948

I don't think that bug is preventing you from pinging your instances. That bug just cleans up left over dnsmaq processes after a network has been deleted while the quantum dhcp agent was down. If you stop the quantum dhcp agent; sudo pkill dnsmaq ; start quantum-dhcp agent that should do the clean

Re: [Openstack] nova-api-metadata on compute node with folsom

Hi, I believe you have this setup on the wrong node. When the VM does a request to 169.254.169.254 this will end up on the network node. On the network node you need that iptables rule and nova-api-metadata installed and running. > My questions are: > >- Am I missing something simple here?

[Openstack] nova-api-metadata on compute node with folsom

Hi stackers, I have deployed a fully working multi-host cluster with 3 hosts featuring quantum with gre network: 1. controller 2. network 3. compute For various reasons I would like to achieve the ​ retrieval of the VM metadata directly on the compute node. For this I have nova-api-m