[Openstack] [OpenStack][Nova] Help with Cloudpipe setup

Hello, I've been trying to set up cloud pipe for OpenStack. I'm running OpenStack Essex on Ubuntu 12.04 with the default packages. I'm following the instructions from [1,2]. When i get to the part of generating certificates to connect to the cloudpipe instance i get this error [3]. Any ideas? [

Re: [Openstack] [OpenStack][Nova] Help with Cloudpipe setup

I'd like to add that i'm unable to ping or ssh this instance from any nodes in my setup. Ping and ssh are working on normal instances. On Fri, Sep 7, 2012 at 10:28 AM, Leander Bessa Beernaert < leande...@gmail.com> wrote: > Hello, > > I've been trying to set up cloud pipe for OpenStack. I'm runni

Re: [Openstack] [ceilometer] Weekly irc meetings time change?

On 09/05/2012 11:51 AM, Nick Barcet wrote: > Thanks for asking, I was just about to come up with this. So based on > the poll, it seems that the 3-4pm UTC time slot received the most favors > with 9 yes, 1 "if need be" and 1 no. So I guess we'll have to do > without Angus, unless we want to do al

Re: [Openstack] [ceilometer] Weekly irc meetings time change?

On 07/09/12 12:39 +0200, Nick Barcet wrote: On 09/05/2012 11:51 AM, Nick Barcet wrote: Thanks for asking, I was just about to come up with this. So based on the poll, it seems that the 3-4pm UTC time slot received the most favors with 9 yes, 1 "if need be" and 1 no. So I guess we'll have to do

Re: [Openstack] [ceilometer] Weekly irc meetings time change?

On Fri, Sep 7, 2012 at 6:39 AM, Nick Barcet wrote: > On 09/05/2012 11:51 AM, Nick Barcet wrote: > > Thanks for asking, I was just about to come up with this. So based on > > the poll, it seems that the 3-4pm UTC time slot received the most favors > > with 9 yes, 1 "if need be" and 1 no. So I gue

Re: [Openstack] issues with fixed_range blocking new instance creation?

On Thu, Sep 6, 2012 at 9:59 PM, Vishvananda Ishaya wrote: > fixed range is likely fine. I suspect you created your network with a > 10.0.0.0/24 though. It might be a bit tricky to switch to a larger range now. > You may have to create the rest of your fixed ips manually in the db > associated w

Re: [Openstack] [Keystone] LDAP integratiom

On 09/06/2012 05:23 PM, Ivan Kolodyazhny wrote: Hi Everyone, Keystone uses python-ldap library to communicate with LDAP server. There are to points where Keystone communicates with LDAP server: keystone.common ldap and keystone.identity.backends.ldap packages. According to the current Keyston

Re: [Openstack] [ceilometer] Weekly irc meetings time change?

Does 6PM UTC , Thursdays work?? This slot looks free. From: openstack-bounces+surya_prabhakar=dell@lists.launchpad.net [openstack-bounces+surya_prabhakar=dell@lists.launchpad.net] On Behalf Of Doug Hellmann [doug.hellm...@dreamhost.com] Sent: Frida

Re: [Openstack] [Keystone] LDAP integratiom

pip-requires/test-requires is aimed at developers and is broken up into two files more-so for documentation/organization purposes. IMO, including LDAP as a dependency should be solved by real packaging (e.g. $ apt-get install keystone keystone-ldap). -Dolph On Fri, Sep 7, 2012 at 8:30 AM, Adam

Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom

great work thanks; As you said the main missing feature of quantum is the multi-host L3-agent. So I wonder if we can combine nova-network and quantum in a way that nova-network is only used for L3 features? On Thu, Sep 6, 2012 at 6:29 PM, Dan Wendlandt wrote: > On Thu, Sep 6, 2012 at 12:50 AM,

[Openstack] After expanding fixed ip range instances no longer have network

Hi All, Running Essex on Ununtu 12.04 using multi-host FlatDHCP nova-networking I ran out of IPs on my fixed_ip range so I shut everything (instances, nova-network, nova-compute) down deleted the old network and recreated it with a smaller netmask. This seems to have almost worked. I can start

Re: [Openstack] After expanding fixed ip range instances no longer have network

On Fri, Sep 7, 2012 at 11:33 AM, Jonathan Proulx wrote: > Can any one tell me what I've looked? I assumed stopping and restarting nova-network would restart dnsmasq since dnsmasq doesn't have it's own init script, but this seems not to be the case. dnsmasq is listening on an IP the system nolon

Re: [Openstack] After expanding fixed ip range instances no longer have network

VERY IMPORTANT FIRST STEP: nova will have moved the ip from eth0 (or whichever device br100 is on) to br100, so if that ip address is needed, you will have to move it back to eth0. If you are connecting over that ip you will have to do it in a script so your connection doesn't drop. Check the /

Re: [Openstack] After expanding fixed ip range instances no longer have network

On Fri, Sep 07, 2012 at 11:59:20AM -0400, Jonathan Proulx wrote: :On Fri, Sep 7, 2012 at 11:33 AM, Jonathan Proulx wrote: :dnsmasq is listening on an IP the system nolonger has, I'm sure I'll :find the answer ot this on my own soon enough but how does one :properly restart openstack's dnsmasq (on

[Openstack] [Folsom] First Guide to try Folsom Packages into Ubuntu 12.04

Hi Stackers, This week, I've been moving forward with Folsom testing. It seems that I'm not alone in wanting to see what will provide Folsom and what will be the changes for Deployment. I also decided to start a guide (with some scripts) [1] which helps anyone who wants to deploy Folsom Testing Pa

Re: [Openstack] After expanding fixed ip range instances no longer have network

If you are sure this is the issue: killall dnsmasq restart nova-network Vish On Sep 7, 2012, at 8:59 AM, Jonathan Proulx wrote: > On Fri, Sep 7, 2012 at 11:33 AM, Jonathan Proulx wrote: > >> Can any one tell me what I've looked? > > I assumed stopping and restarting nova-network would resta

[Openstack] [HPC] Reminder monthly telecon Sep. 10

Hi, This is a reminder that we'll hold our next monthly HPC telecon this coming Monday, Sep. 10 and 12:00 noon Eastern Time. We'll use webex (details below). The agenda is somewhat open. Our default will be to start the conversation about HPC features that folks are interested in adding to t

Re: [Openstack] After expanding fixed ip range instances no longer have network

Thanks Vish, Your directions were correct & would have saved me a few hours of floundering had I just started a little later :) particularly the `killall dnsmasq` -Jon On Fri, Sep 07, 2012 at 09:12:52AM -0700, Vishvananda Ishaya wrote: :If you are sure this is the issue: : :killall dnsmasq :res

Re: [Openstack] [openstack-hpc] [HPC] Reminder monthly telecon Sep. 10

All, I have a blue print on proximity scheduler at http://wiki.openstack.org/ProximityScheduler, and would like to get feedback on it. Thanks, Joseph - Original Message - From: "John Paul Walters" To: openstack@lists.launchpad.net Cc: openstack-...@lists.openstack.org Sent: Friday, S

Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom

On Fri, Sep 7, 2012 at 8:36 AM, rohon mathieu wrote: > great work thanks; > > As you said the main missing feature of quantum is the multi-host L3-agent. > So I wonder if we can combine nova-network and quantum in a way that > nova-network is only used for L3 features? I agree that it would be gr

Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom

I'm I correct in believing that the Quantum L3 Abstractions and API Framework (https://blueprints.launchpad.net/quantum/+spec/quantum-l3-api) is the current plan of record for bringing L2toL3 functionality (e.g., VXLAN/NVGRE) into Quantum? Is anyone signed up to do this or has this blueprint be

Re: [Openstack] [Keystone] LDAP integratiom

On 09/07/2012 10:31 AM, Dolph Mathews wrote: pip-requires/test-requires is aimed at developers and is broken up into two files more-so for documentation/organization purposes. IMO, including LDAP as a dependency should be solved by real packaging (e.g. $ apt-get install keystone keystone-ldap)

Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom

Hi Syd, On Fri, Sep 7, 2012 at 10:34 AM, Syd (Sydney) Logan wrote: > I'm I correct in believing that the Quantum L3 Abstractions and API Framework > (https://blueprints.launchpad.net/quantum/+spec/quantum-l3-api) is the > current plan of record for bringing L2toL3 functionality (e.g., VXLAN/NVG

Re: [Openstack] [openstack-dev] Quantum vs. Nova-network in Folsom

I've observed and studied the OVS L3oL3 tunneling in a multi-node configuration with F3 by packet sniffing VM to VM pings, and have a basic understanding about how the mesh of tunnels comes into existence. Pretty cool. Guessing https://github.com/openstack/quantum/commit/3005d16fe3588bdf4b928e7

Re: [Openstack] [openstack-hpc] [HPC] Reminder monthly telecon Sep. 10

I am guessing your intent is to determine the maximum available bandwidth and lowest latency (commonly implemented as least hops) path between hosts. In other platforms there is the notion of Cell, Zone, Row, Rack etc where the host that you are running your workload has the topology encoded in

[Openstack] ResourceExtension member_actions question

Is it possible to define a ResourceExtension with a member_action that is the same for both PUT and GET requests? For example, let's say I want to add "foo" as a member action for images. I tried to define the extension as: res = extensions.ResourceExtension('images', MyC

Re: [Openstack] [Nova] Instance Type Extra Specs clarifications

Hello all, I am part of the SF south bay meetup group and trying to add a Disk I/O QoS feature which is based on the blkiotune in libvirt. We would like to add flavor types in which we specify the blkiotune in the create flavor screen. After reviewing the discussions and some emails it appears tha

Re: [Openstack] [Nova] Instance Type Extra Specs clarifications

Well, Yunhong added the API to allow you to update the extra specs table so he should be able to give you the details on that (he's in China, he might not get back to you until next week). Also, make sure you add a scope (where scope is a string followed by a `:' at the beginning of the key) to

Re: [Openstack] [Nova] Instance Type Extra Specs clarifications

Yes, the intent has been to use something along the lines of "OS-FLV-EXTRA-DATA:disk_qos" This leads to another question which I saw being discussed earlier in the email thread. Are we looking for consistency in adding the extra specs? For the most obvious ones it may be worth while to come up wit

Re: [Openstack] [Nova] Instance Type Extra Specs clarifications

OS-FLV-EXTRA-DATA: Do you really need a 17 character scope? Your current scope (I assume it's a derivative of OpenStack Flavor Extra Data) is really just redundant info, we know it's extra data for a flavor since we're talking about the `extra_specs' table which is used for flavors. I would t

[Openstack] OpenStack Community Weekly Newsletter (Aug 31-Sep 7)

Highlights of the week New OpenStack Foundation Gold Members: Intel, VmWare, NEC Today, the OpenStack Board of Directors approved the applications of three companies wishing to become Gold Members: Int

Re: [Openstack] [Folsom] First Guide to try Folsom Packages into Ubuntu 12.04

Thanks for the greate document and script. I have read the document and have some question, queston 1 If eth1 is connected to a Switch, it should be in tagged mode. my question is If the eth1 not connected to Switch, it wolud work? queston 2 Enable IP forwarding : my question is In Essex,