Re: [openstack-dev] Validation of IP

You can instead use netaddr: import netaddr try: netaddr.IPAddress(input) except AddrFormatError: logging.error('Nope!') else: doSomethingWith(input) You could also: if netaddr.IPAddress('10.0.0.1') in netaddr.IPNetwork('10.0.0.0/8'): logging.error('Yup!') Assaf Muller, Cloud Net

[openstack-dev] FW: Installing Havana release along with Ceph storage

Can someone please respond to the following mail incase you are aware of any document? -Original Message- From: Lalitha Maruthachalam Sent: Tuesday, January 21, 2014 12:49 PM To: Dnsbed Ops; openst...@lists.openstack.org; openstack-d...@lists.openstack.org Subject: [Openstack-docs] Insta

[openstack-dev] [nova][neutron]About creating vms without ip address

Hi fellow OpenStackers I found that we could not create vms without ip address. But in the telecom scene, the ip address usually managed by the telecom network element themselves. So they need a vm without ip address and configurate it through some specific method. How can we provide a kind of vms

Re: [openstack-dev] Can somebody help me to determine if an URL validation in python-glanceclient & horizon projects is safe

On 20/01/14 17:43 +, Victor Joel Morales Ruvalcaba wrote: I'm implementing an URL validation that checks if the external location value provided exists and if it's reachable. To achieve that I'm using the method urlopen of six.moves.urllib.request module which it seems similar like to the de

Re: [openstack-dev] [Tempest - Stress test] : cleanup() removing resources for all tenants with an admin_manager

Hello Boris, I'll check Rally in order to see what tool is the best for my tests. Best Regards, Julien LELOUP julien.lel...@3ds.com From: Boris Pavlovic [mailto:bpavlo...@mirantis.com] Sent: Monday, January 20, 2014 5:52 PM To: OpenStack Development Mailing List (not for usage questions) Subje

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Document updated to talk about network aware scheduling ( https://docs.google.com/document/d/1vadqmurlnlvZ5bv3BlUbFeXRS_wh-dsgi5plSjimWjU/edit#- section just before the use case list). Based on yesterday's meeting, rkukura would also like to see network-aware scheduling to work for non-PCI cases -

Re: [openstack-dev] [savanna] paramiko requirement of >= 1.9.0?

Hey Matt, that's correct, we should bump paramiko version to >= 1.9.0. It was released more than year ago and so all of us use paramiko >= 1.9.0 Thanks for catching this. On Sun, Jan 19, 2014 at 7:44 AM, Matthew Farrellee wrote: > jon, > > please confirm a suspicion of mine. > > the neutron-

Re: [openstack-dev] [savanna] paramiko requirement of >= 1.9.0?

Here is a change for global-requirements https://review.openstack.org/#/c/68088/ On Tue, Jan 21, 2014 at 3:30 PM, Sergey Lukjanov wrote: > Hey Matt, > > that's correct, we should bump paramiko version to >= 1.9.0. It was > released more than year ago and so all of us use paramiko >= 1.9.0 > > Th

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

> > > So, I actually don't think the two concepts (reservations and > > > "isolated instances") are competing ideas. Isolated instances are > > > actually not reserved. They are simply instances that have a > > > condition placed on their assignment to a particular compute node > > > that the node

[openstack-dev] [Neutron] Selectively disabling certain built in iptables rules

Feel free to tell me this is a bad idea and scold me for even asking, but please help me figure out how to do it anyway. This is for a specific tenant in a specific lab that was built specifically for that one tenant to do some experimental work that requires VMs to route and other VMs to act as

Re: [openstack-dev] Climate - Was: Next steps for Whole Host allocation / Pclouds

> Hi Phil and Jay, > >Phil, maybe you remember I discussed with you about the possibility of using >pclouds with Climate, but we finally ended up using Nova aggregates and a >dedicated filter. >That works pretty fine. We don't use instance_properties >but rather aggregate metadata but the idea

Re: [openstack-dev] Top Gate Reseting issues that need attention - Tuesday morning update

Brief update on where we stand on the gate (still not great) - gate is currently 126 deep - top of queue entered 51hrs ago Bug 1270680 - v3 extensions api inherently racey wrt instances - patch landed (seems to have helped though the exception is still showing up quite a bit, so don't know if th

Re: [openstack-dev] [Neutron] Selectively disabling certain built in iptables rules

Paul, There's an extension for this that is, I think, presently only implemented by the Nicira plugin. Look for portsecurity. Whatever they do is probably the way you should do it too. Cheers, -- Ian. On 21 January 2014 13:10, CARVER, PAUL wrote: > Feel free to tell me this is a bad idea

Re: [openstack-dev] Climate - Was: Next steps for Whole Host allocation / Pclouds

Hi Phil, Le 21/01/2014 13:13, Day, Phil a écrit : Hi Phil and Jay, Phil, maybe you remember I discussed with you about the possibility of using pclouds with Climate, but we finally ended up using Nova aggregates and a dedicated filter. That works pretty fine. We don't use instance_properties

Re: [openstack-dev] [Neutron] Selectively disabling certain built in iptables rules

I think there is a blueprint for that. Anyway, see idea for current releases below: >Feel free to tell me this is a bad idea and scold me for even asking, but >please >help me figure out how to do it anyway. This is for a specific tenant in a >specific lab that was built specifically for that

[openstack-dev] [Nova] Libvirt driver platform support

Hi, Libvert driver has the below code snippet, where it assumes that the Host platform supports "pit" etc when libvirt is configured for KVM. For PowerPC [Freescale] platform below code is causing issues. Code snippet from driver.py: if CONF.libvirt_type == "kvm": # TODO(berrange)

Re: [openstack-dev] [Nova] Libvirt driver platform support

On Tue, Jan 21, 2014 at 01:19:32PM +, balaj...@freescale.com wrote: > Hi, > > Libvert driver has the below code snippet, where it assumes that the Host > platform supports "pit" etc when libvirt is configured for KVM. > > For PowerPC [Freescale] platform below code is causing issues. > > Co

Re: [openstack-dev] Disabling file injection *by default*

On 01/20/2014 09:29 PM, Robert Collins wrote: > I was reminded of this while I cleaned up failed file injection nbd > devices on ci-overcloud.tripleo.org :/ - what needs to happen for us > to change the defaults around file injection so that it's disabled? It should use libguestfs for file injecti

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

Le 21/01/2014 12:57, Day, Phil a écrit : So, I actually don't think the two concepts (reservations and "isolated instances") are competing ideas. Isolated instances are actually not reserved. They are simply instances that have a condition placed on their assignment to a particular compute node t

Re: [openstack-dev] [infra] [devstack-gate] Nominating Sean Dague for devstack-gate-core

On 01/03/2014 12:46 PM, James E. Blair wrote: > Occasionally it becomes clear that a part of the project infrastructure > has its own community interested in it. Such is the case with > devstack-gate, which is the nexus of infra and openstack. Not only does > it interact with infrastructure syste

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

> Exactly - that's why I wanted to start this debate about the way forward > for the > Pcloud Blueprint, which was heading into some kind of middle ground. As > per > my original post, and it sounds like the three of us are at least aligned > I'm > proposing to spilt this into two streams: > >

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

> > > > I think there is clear water between this and the existing aggregate based > isolation. I also think this is a different use case from reservations. > It's > *mostly* like a new scheduler hint, but because it has billing impacts I > think it > needs to be more than just that - for exa

[openstack-dev] [TripleO] [Tuskar] Terminology Revival #1 - Roles

Hi folks, when I was getting feedback on wireframes and we talked about Roles, there were various objections and not much suggestions. I would love to call for action and think a bit about the term for concept currently known as Role (= Resource Category). Definition: Role is a representatio

Re: [openstack-dev] [TripleO] [Tuskar] Terminology Revival #1 - Roles

Thanks for starting this! Comments in-line: > Hi folks, > > when I was getting feedback on wireframes and we talked about Roles, > there were various objections and not much suggestions. I would love to > call for action and think a bit about the term for concept currently > known as Role (= Res

Re: [openstack-dev] [TripleO] [Tuskar] Terminology Revival #1 - Roles

On 21/01/14 14:19, Jaromir Coufal wrote: when I was getting feedback on wireframes and we talked about Roles, there were various objections and not much suggestions. I would love to call for action and think a bit about the term for concept currently known as Role (= Resource Category). This in

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Just one comment: The devices allocated for an instance are immediately known after the domain is created. Therefore it's possible to do a port update and have the device configured while the instance is booting. --Robert On 1/19/14 2:15 AM, "Irena Berezovsky" wrote: >Hi Robert, Yonhong,

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

I want to explore the linkage between the proposed exclusive use filter and scheduling a little more. At the Icehouse summit I heard the concern that without advance preparation, there may well be zero hosts that are acceptable. Why is that not a concern now? What does the Nova scheduler do n

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Yunhong, Just try to understand your use case: -- a VM can only work with cards from vendor V1 -- a VM can work with cards from both vendor V1 and V2 So stats in the two flavors will overlap in the PCI flavor solution. I'm just trying to say that this is something that needs to be

Re: [openstack-dev] [Neutron] Selectively disabling certain built in iptables rules

Darragh O'Reilly wrote: >Neutron does not know about flavors or images. But it has ports which have a >name attribute that can be set to an arbitrary string, e.g. 'anti_spoof_off'. >The >name does not need to be unique within the tenant. Then your overridden methods >could check for that string.

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

Le 21/01/2014 15:28, Day, Phil a écrit : I think there is clear water between this and the existing aggregate based isolation. I also think this is a different use case from reservations. It's *mostly* like a new scheduler hint, but because it has billing impacts I think it needs to be more

Re: [openstack-dev] [TripleO] [Tuskar] Terminology Revival #1 - Roles

Thanks for starting this! Comments in-line: Hi folks, when I was getting feedback on wireframes and we talked about Roles, there were various objections and not much suggestions. I would love to call for action and think a bit about the term for concept currently known as Role (= Resource Cate

Re: [openstack-dev] Climate - Was: Next steps for Whole Host allocation / Pclouds

Hi Phill, Sylvain has described almost everything about Climate :) And as he said first time, idea for using Pclouds came to Climate because of reserving of compute nodes. And now for our first release we're preparing two types of reservations: 1) compute node reservation 2) virtual instance rese

Re: [openstack-dev] [ceilometer] Discussion of the resource loader support patch

> If the resources defined in the pipeline doesn't match any resource > file loader, it will be treated as directly passing to the pollsters. E.g. > resources: > - fileloader:///foo/bar > - snmp://2.2.2.2 > The endpoint 'snmp://2.2.2.2' will be passed to the pollsters along >

[openstack-dev] [requirements][oslo] Upgrade six to 1.5.2?

six 1.5.2 has been released on 2014-01-06, it provides urllib/urlparse compatibility. Is there any plan to upgrade six to 1.5.2? (since it is fresh new, may need some time to test) six 1.4.1 is lack of urllib/urlparse support, so oslo-incubator/py3kcompat is needed, and it is used in some projects

Re: [openstack-dev] Top Gate Reseting issues that need attention - Tuesday morning update

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/21/2014 07:14 AM, Sean Dague wrote: > Brief update on where we stand on the gate (still not great) - gate > is currently 126 deep - top of queue entered 51hrs ago > > Bug 1270680 - v3 extensions api inherently racey wrt instances - > patch lande

Re: [openstack-dev] [Neutron][IPv6] A pair of mode keywords

I don't see a second new attribute being proposed - I only see one new one and the existing enable_dhcp attribute. Can we get a writeup of what is being proposed? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http:/

Re: [openstack-dev] [Diesel] Proposal for new project

Hi Adrian, Jay and Raj Thanks for your responses on relationship between Solum and Diesel. It does sound like they are in the same domain. My feeling was that it was a very different approach where Solum was aimed at developer, Diesel was aimed at the cloud provider. In some companies these roles

Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds

> -Original Message- > From: Khanh-Toan Tran [mailto:khanh-toan.t...@cloudwatt.com] > Sent: 21 January 2014 14:21 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] Next steps for Whole Host allocation / Pclouds > > > > Exactly - that's why I

Re: [openstack-dev] [Diesel] Proposal for new project

On 01/21/2014 11:31 AM, Raymond, Rob wrote: > Hi Adrian, Jay and Raj > > Thanks for your responses on relationship between Solum and Diesel. It does > sound like they are in the same domain. My feeling was that it was a very > different approach where Solum was aimed at developer, Diesel was aimed

Re: [openstack-dev] a "common" client library

On 17 Jan 2014, at 22:00, Jamie Lennox wrote: > (I don't buy the problem with large amounts of dependencies, if you have a > meta-package you just have one line in requirements and pip will figure the > rest out.) +1 Renat Akhmerov @ Mirantis Inc. __

Re: [openstack-dev] a "common" client library

On 17 Jan 2014, at 22:06, Robert Collins wrote: > On 17 January 2014 09:22, Renat Akhmerov wrote: >> Since it’s pretty easy to get lost among all the opinions I’d like to >> clarify/ask a couple of things: >> >> Keeping all the clients physically separate/combining them in to a single >> libr

[openstack-dev] [Nova] PCI flavor objects - please review this proposal

Hi, We've had a few comments about creating a new table specifically for PCI flavors versus using the already existing host aggregates table, and John Garbutt asked me to explain the concepts involved here to see what the body of opinion was on the subject. My opinion, which which this account is

Re: [openstack-dev] a "common" client library

On Jan 21, 2014, at 10:54 AM, Renat Akhmerov mailto:rakhme...@mirantis.com>> wrote: On 17 Jan 2014, at 22:00, Jamie Lennox mailto:jamielen...@redhat.com>> wrote: (I don't buy the problem with large amounts of dependencies, if you have a meta-package you just have one line in requirements and

Re: [openstack-dev] a "common" client library

On 18 Jan 2014, at 07:48, Sean Dague wrote: > I also think auto generated clients have a lot of challenges in the same > way that full javascript pages in browsers have. If you screw up in a > subtle way you can just completely disable your clients from connecting > to your server entirely (or b

[openstack-dev] Unified Guest Agent, PoC for os-collect-config

Hello folks, At the end of the previous discussion on the topic [1] I've decided to make a PoC based on oslo.messaging. Clint suggested and I agreed to make it for os-collect-config. Actually I've made a PoC for Savanna first :-) but anyway here is the one for os-collect-config [2]. I've made a c

Re: [openstack-dev] [savanna] client release 0.4.1

python-savannaclient 0.4.1 will be available in savanna repos after https://review.openstack.org/#/c/66723/ will be merged. On Thu, Jan 16, 2014 at 12:09 AM, Sergey Lukjanov wrote: > 0.4.1 python-savannaclient released. > > pypi: https://pypi.python.org/pypi/python-savannaclient/0.4.1 > tarball:

Re: [openstack-dev] [infra] [devstack-gate] Nominating Sean Dague for devstack-gate-core

FWIW +1 On Tue, Jan 21, 2014 at 6:16 PM, Anita Kuno wrote: > On 01/03/2014 12:46 PM, James E. Blair wrote: > > Occasionally it becomes clear that a part of the project infrastructure > > has its own community interested in it. Such is the case with > > devstack-gate, which is the nexus of infr

Re: [openstack-dev] [infra] hacking checks for infra projects

James, do you have any thoughts on it? On Tue, Jan 14, 2014 at 12:16 AM, Sergey Lukjanov wrote: > Hi folks, > > I think that we can enable hacking checks for python infra projects to > help themselves write better code. Probably we should enable only specific > subset of hacking checks instead o

Re: [openstack-dev] a "common" client library

On 01/21/2014 11:54 AM, Renat Akhmerov wrote: > > On 17 Jan 2014, at 22:00, Jamie Lennox > wrote: > >> (I don't buy the problem with large amounts of dependencies, if you >> have a meta-package you just have one line in requirements and pip >> will figure the rest

Re: [openstack-dev] [Neutron][3rd Party Testing] Jenkins setup

Hi, > For step 3/5, is the right procedure. Or is there a way to use a cmd to > run all the tests and use a different mechanism to specify a filter for the > tests to be run. > > I don't know if Tempest allows you to filter for the tests to be run. I'm following these steps to configure Jenkins b

Re: [openstack-dev] [infra] [devstack-gate] Nominating Sean Dague for devstack-gate-core

On 01/03/2014 09:46 AM, James E. Blair wrote: Occasionally it becomes clear that a part of the project infrastructure has its own community interested in it. Such is the case with devstack-gate, which is the nexus of infra and openstack. Not only does it interact with infrastructure systems (in

Re: [openstack-dev] [OpenStack-Dev] Cherry picking commit from oslo-incubator

On Jan 17, 2014 12:24 AM, "Flavio Percoco" wrote: > > On 16/01/14 17:32 -0500, Doug Hellmann wrote: >> >> On Thu, Jan 16, 2014 at 3:19 PM, Ben Nemec wrote: >> >>On 2014-01-16 13:48, John Griffith wrote: >> >>Hey Everyone, >> >>A review came up today that cherry-picked a specif

Re: [openstack-dev] a "common" client library

Hello, I would like to end this requirements talk cause it doesn't make any sense in term of python clients. Initially the discussion was about "many clients projects with separate requirements" VS "single client project with single requirements list". At that moment we should have stop and actua

Re: [openstack-dev] question of vcpu-memory-hotplug progress

On Jan 18, 2014, at 12:03 AM, Wangshen (Peter) wrote: >> -Original Message- >> From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] >> Sent: Friday, January 17, 2014 1:01 AM >> To: OpenStack Development Mailing List (not for usage questions) >> Cc: Jinbo (Justin) >> Subject: Re: [open

Re: [openstack-dev] [OpenStack-Dev] Cherry picking commit from oslo-incubator

On 01/21/2014 01:14 PM, Joe Gordon wrote: > > On Jan 17, 2014 12:24 AM, "Flavio Percoco" > wrote: >> >> On 16/01/14 17:32 -0500, Doug Hellmann wrote: >>> >>> On Thu, Jan 16, 2014 at 3:19 PM, Ben Nemec > wrote: >>> >>>On 2014-01-16 13:4

Re: [openstack-dev] a "common" client library

I would like to propose to use this thread to gather and discuss software requirements that our clients should meet. Later we'll summarize all the requirements and use them during our work of improving the clients. By reaching listed requirements we'll be able to evaluate the success of our refacto

Re: [openstack-dev] a "common" client library

On Jan 21, 2014, at 12:19 PM, Alexei Kornienko mailto:alexei.kornie...@gmail.com>> wrote: Hello, I would like to end this requirements talk cause it doesn't make any sense in term of python clients. Initially the discussion was about "many clients projects with separate requirements" VS "sing

Re: [openstack-dev] [Neutron][3rd Party Testing] Jenkins setup

For vmware minesweeper ,we filter tests following way: 1. testr list-tests > alltests 2. exclude-tests (file with test names we want to filter) 3. alltests - excludetests = tests_to_be_run 4. testr run —load-list=tests_to_be_run hope that helps On Jan 21, 2014, at 9:56 AM, Lucas Eznarriaga wro

Re: [openstack-dev] a "common" client library

don't do this here - the thread is way too deep already. If we get into discussing individual points let's do one question per thread and prefix the emails with [client] or something to tie it all together - Original Message - > From: "Alexei Kornienko" > To: "OpenStack Development Mai

Re: [openstack-dev] [Fuel-dev] [OSTF][Ceilometer] ceilometer meters and samples delete

Right now, Fuel deploys Ceilometer to use the OpenStack mySQL DB for Ceilometer data, although we’re expecting to utilize MongoDB in the 4.1 Fuel version. This is, as you mention, primarily to address the performance issues with a shared mySQL DB. That said, I don’t know that it really changes th

Re: [openstack-dev] a "common" client library

>It is when most openstack clouds don’t just run keystone. Or nova, or swift. Or when each client acts, smells and behaves differently. It matters a LOT when you’re trying to write applications on top of a mature openstack deployment. I still don't understand the problem here. Installed packages u

Re: [openstack-dev] [Neutron] Selectively disabling certain built in iptables rules

> >Darragh O'Reilly wrote: > >>Neutron does not know about flavors or images. But it has ports which have a >>name attribute that can be set to an arbitrary string, e.g. 'anti_spoof_off'. >>The >>name does not need to be unique within the tenant. Then your overridden >>methods >>could check fo

Re: [openstack-dev] a "common" client library

On Jan 21, 2014, at 12:59 PM, Alexei Kornienko mailto:alexei.kornie...@gmail.com>> wrote: >It is when most openstack clouds don’t just run keystone. Or nova, or swift. >Or when each client acts, smells and behaves differently. It matters a LOT >when you’re trying to write applications on top o

Re: [openstack-dev] [OpenStack-Dev] Cherry picking commit from oslo-incubator

On Tue, Jan 21, 2014 at 11:14 AM, Joe Gordon wrote: > > On Jan 17, 2014 12:24 AM, "Flavio Percoco" wrote: >> >> On 16/01/14 17:32 -0500, Doug Hellmann wrote: >>> >>> On Thu, Jan 16, 2014 at 3:19 PM, Ben Nemec >>> wrote: >>> >>>On 2014-01-16 13:48, John Griffith wrote: >>> >>>Hey Ever

Re: [openstack-dev] [OpenStack-Dev] Cherry picking commit from oslo-incubator

On 2014-01-21 12:28, Sean Dague wrote: On 01/21/2014 01:14 PM, Joe Gordon wrote: On Jan 17, 2014 12:24 AM, "Flavio Percoco" mailto:fla...@redhat.com>> wrote: On 16/01/14 17:32 -0500, Doug Hellmann wrote: On Thu, Jan 16, 2014 at 3:19 PM, Ben Nemec > wrote:

Re: [openstack-dev] a "common" client library

On 21 Jan 2014, at 09:07, Jesse Noller wrote: > Do you use any other platform than Linux? Even donald - one of the python > packaging leads and PyPI leads said this is a bad end-user experience for > consumers of openstack clouds. That fact that someone (even very smart experience) said somet

Re: [openstack-dev] a "common" client library

On 21 Jan 2014, at 09:40, Sean Dague wrote: > On 01/21/2014 11:54 AM, Renat Akhmerov wrote: >> >> On 17 Jan 2014, at 22:00, Jamie Lennox > > wrote: >> >>> (I don't buy the problem with large amounts of dependencies, if you >>> have a meta-package you just have on

[openstack-dev] [Murano] Repositoris re-organization

Hi folks, As we are moving towards incubation application, I took a closer look at what is going on with our repositories. An here is what I found. We currently have 11 repositories at stackforge: - murano-api - murano-conductor - murano-repository - murano-dashboard - murano-commo

Re: [openstack-dev] [Infra] Meeting Tuesday January 21st at 19:00 UTC

On Mon, Jan 20, 2014 at 11:01 AM, Elizabeth Krumbach Joseph wrote: > The OpenStack Infrastructure (Infra) team is hosting our weekly > meeting tomorrow, Tuesday January 21st, at 19:00 UTC in > #openstack-meeting Meeting minutes and log: Minutes: http://eavesdrop.openstack.org/meetings/infra/201

Re: [openstack-dev] a "common" client library

+1 for opening new threads regarding specific questions. On 21 Jan 2014, at 11:54, Renat Akhmerov wrote: > > On 21 Jan 2014, at 09:40, Sean Dague wrote: > >> On 01/21/2014 11:54 AM, Renat Akhmerov wrote: >>> >>> On 17 Jan 2014, at 22:00, Jamie Lennox >> > wrote

Re: [openstack-dev] [Neutron] Relationship between Neutron LBaaS and Libra

On Jan 19, 2014, at 8:19 AM, Clint Byrum wrote: > Excerpts from Thomas Herve's message of 2014-01-19 01:52:56 -0800: >> >>> Hi, >>> >>> I haven’t read through those (need to go spend time with family so replying >>> quickly) but given the dates the planning phases for Quantum/Neutron LBaaS >>>

[openstack-dev] [TripleO][Neutron] PMTUd broken in gre networks

Hi, https://bugs.launchpad.net/neutron/+bug/1270646 - we've triaged this as critical in TripleO, because by default GRE overlay networks will cause huge fragmentation in the datacentre LAN. We're looking for someone to 'own' this bug (in tripleo) and drive getting a real, permanent fix / anal

[openstack-dev] [neutron] Neutron should disallow /32 CIDR

Currently, NeutronDbPluginV2._validate_allocation_pools() does some very basic checking to be sure the specified subnet is valid. One thing that's missing is checking for a CIDR of /32. A subnet with one IP address in it is unusable as the sole IP address will be allocated to the gateway, and t

Re: [openstack-dev] [TripleO][Neutron] PMTUd broken in gre networks

On 21 January 2014 21:23, Robert Collins wrote: > In OpenStack we've got documentation[1] that advises setting a low MTU > for tenants to workaround this issue (but the issue itself is > unsolved) - this is a problem because PMTU is fairly important :) > Lowering *every* tenant when one tenant so

Re: [openstack-dev] [Nova] Can someone from the Nova core team please take a look at patch 40467

http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html On Mon, Jan 20, 2014 at 9:26 AM, Genin, Daniel I. wrote: > Hello Nova core team, > > I have three small patches implementing ephemeral storage encryption for > LVM backed instances. > > https://review.openstack.org/#/c

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

Wouldn't be easier just to check if: cidr is 32? I believe it is a good idea to not allow /32 network but this is just my opinion Edgar From: Paul Ward Reply-To: OpenStack List Date: Tuesday, January 21, 2014 12:35 PM To: OpenStack List Subject: [openstack-dev] [neutron] Neutron should

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

/30 is the minimum allowable mask, not /31. On 21 January 2014 22:04, Edgar Magana wrote: > Wouldn't be easier just to check if: > > cidr is 32? > > I believe it is a good idea to not allow /32 network but this is just my > opinion > > Edgar > > From: Paul Ward > Reply-To: OpenStack List > Da

Re: [openstack-dev] [qa] negative test framework: ready for review

http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html On Fri, Jan 17, 2014 at 7:02 AM, Koderer, Marc wrote: > Hi all, > > first part of the negative test framework is ready for review: > > https://review.openstack.org/#/c/64733/ > > Please have a look. > > Regards > Marc

Re: [openstack-dev] [Ironic] Third-party drivers and testing

On Sun, Jan 19, 2014 at 7:47 PM, Christopher Yeoh wrote: > > On Mon, Jan 20, 2014 at 6:17 AM, Devananda van der Veen < > devananda@gmail.com> wrote: > >> 1. each driver must adhere to the existing driver interfaces. >> 2. each driver must have comprehensive unit test coverage and sufficient >

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

Using a /32 has use cases. When trying to build a L3 only routed network /32 routes are required. While it can be inconvenient for the more generic L2 network use case, I wouldn't remove it since there are other use cases where it is useful. -Carl On 01/21/2014 12:35 PM, Paul Ward wrote: > > Cu

Re: [openstack-dev] [gantt] Sync up patches

On Thu, Jan 16, 2014 at 4:42 PM, Dugger, Donald D wrote: > OK, it looks like the concensus is that we don't try and keep the gantt > tree in sync with nova instead we: > > 1) Get the current gantt tree to pass unit tests > 2) Get gantt to pass integration tests (e.g. get it working as the nova

Re: [openstack-dev] Disabling file injection *by default*

[CC'ed libguestfs author, Rich Jones] Heya, On 01/21/2014 07:59 AM, Robert Collins wrote: > I was reminded of this while I cleaned up failed file injection nbd > devices on ci-overcloud.tripleo.org :/ - what needs to happen for us > to change the defaults around file injection so that it's disab

Re: [openstack-dev] Disabling file injection *by default*

On 22 January 2014 10:50, Kashyap Chamarthy wrote: > [CC'ed libguestfs author, Rich Jones] > > Heya, > > > On 01/21/2014 07:59 AM, Robert Collins wrote: >> I was reminded of this while I cleaned up failed file injection nbd >> devices on ci-overcloud.tripleo.org :/ - what needs to happen for us >>

[openstack-dev] [nova][neutron] PCI passthrough SRIOV

Hi Folks, As the debate about PCI flavor versus host aggregate goes on, I'd like to move forward with the SRIOV side of things in the same time. I know that tomorrow's IRC will be focusing on the BP review, and it may well continue into Thursday. Therefore, let's start discussing SRIOV side of

Re: [openstack-dev] Disabling file injection *by default*

On 22 January 2014 03:03, Russell Bryant wrote: > On 01/20/2014 09:29 PM, Robert Collins wrote: >> I was reminded of this while I cleaned up failed file injection nbd >> devices on ci-overcloud.tripleo.org :/ - what needs to happen for us >> to change the defaults around file injection so that it'

Re: [openstack-dev] [Ironic] Third-party drivers and testing

On Mon, Jan 20, 2014 at 8:29 AM, Jay Pipes wrote: > On Sun, Jan 19, 2014 at 2:47 PM, Devananda van der Veen < > devananda@gmail.com> wrote: > >> Hi all, >> >> I've been thinking about how we should treat third-party drivers in >> Ironic for a while, and had several discussions at the Hong Kon

Re: [openstack-dev] Disabling file injection *by default*

On Wed, Jan 22, 2014 at 10:57:29AM +1300, Robert Collins wrote: [...] I'm a bit surprised that file injection is on by default. I thought it was disabled by default upstream. (Just checked and it is enabled as you say.) So yes, file injection should be off by default, but read below. > There's

Re: [openstack-dev] Top Gate Reseting issues that need attention - Tuesday morning update

I have some hints which the people looking at neutron failures might find useful. # 1 - in [1] a weird thing happens with DHCP. A DHCPDISCOVER with for fa:16:3e:cc:d9:c7 is pretty much simultaneously received by two dnsmasq instances, which are listening on ports belonging to two distinct networks

[openstack-dev] [gantt] How to include nova modules in unit tests

I almost have the unit tests for gantt working except for one problem - is there a way to have the test infrastructure allow the gantt tree to import objects from the nova tree. The problem is that we want to break out just the scheduler code into the gantt tree without duplicating all of nova.

Re: [openstack-dev] [TripleO][Neutron] PMTUd broken in gre networks

On 22 January 2014 10:01, Ian Wells wrote: > On 21 January 2014 21:23, Robert Collins wrote: >> >> In OpenStack we've got documentation[1] that advises setting a low MTU >> for tenants to workaround this issue (but the issue itself is >> unsolved) - this is a problem because PMTU is fairly import

Re: [openstack-dev] [TripleO] [Tuskar] Terminology Revival #1 - Roles

On Jan 21, 2014, at 9:40 AM, Dougal Matthews wrote: > On 21/01/14 14:19, Jaromir Coufal wrote: >> when I was getting feedback on wireframes and we talked about Roles, >> there were various objections and not much suggestions. I would love to >> call for action and think a bit about the term for

Re: [openstack-dev] Cinder unit test failure

On Tue, 2014-01-21 at 08:29 +0530, iKhan wrote: > I am worried which one is better in terms of performance? iniparse or > ConfigParser? > > I am aware iniparse will do a better job of maintaining INI file's > structure, but I am more interested in performance. The parsing of INI files is the last

Re: [openstack-dev] [gantt] How to include nova modules in unit tests

Hi Don, Look at how Climate is doing this [1]. The idea is to pull the master tarball as an eggfile. That works fine, the only issues we have is when we register opts to CONF where we could get DuplicateOpt if we try to register opt with same name when importing. -Sylvain [1] : https://github.c

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

I think there may be some confusion between the two concepts: subnet and allocation pool. You are right that an ipv4 subnet smaller than /30 is not useable on a network. However, this method is checking the validity of an allocation pool. These pools should not include room for a gateway nor bro

Re: [openstack-dev] [Neutron][IPv6] A pair of mode keywords

Hi, Anthony: I think we are saying the same thing. Yes, there must be two parameters, and they are independent. What I mean of "simplifying" referred to the CLI. If user provides RA mode, then the 2nd parameter will have default value if user doesn't specify it. However, user can also indicate

Re: [openstack-dev] Unified Guest Agent, PoC for os-collect-config

Excerpts from Dmitry Mescheryakov's message of 2014-01-21 09:30:17 -0800: > Hello folks, > > At the end of the previous discussion on the topic [1] I've decided to make > a PoC based on oslo.messaging. Clint suggested and I agreed to make it for > os-collect-config. Actually I've made a PoC for Sa

Re: [openstack-dev] [Glance] Property protections not being enforced?

On Mon, Jan 20, 2014 at 6:02 AM, Tom Leaman wrote: > I'm looking at a possible bug here but I just want to confirm > that I'm not missing something obvious. > > I'm currently working with Devstack on Ubuntu 12.04 LTS > > Once Devstack is up and running, I'm creating a file > /etc/glance/property-

Re: [openstack-dev] [TripleO] [Tuskar] Terminology Revival #1 - Roles

> On Jan 21, 2014, at 9:40 AM, Dougal Matthews wrote: > > > On 21/01/14 14:19, Jaromir Coufal wrote: > >> when I was getting feedback on wireframes and we talked about Roles, > >> there were various objections and not much suggestions. I would love to > >> call for action and think a bit about th

Re: [openstack-dev] [gantt] How to include nova modules in unit tests

On 22 January 2014 11:57, Dugger, Donald D wrote: > I almost have the unit tests for gantt working except for one problem – is > there a way to have the test infrastructure allow the gantt tree to import > objects from the nova tree. > > > > The problem is that we want to break out just the schedu

Re: [openstack-dev] Cinder unit test failure

On Tue, Jan 21, 2014 at 4:06 PM, Jay Pipes wrote: > On Tue, 2014-01-21 at 08:29 +0530, iKhan wrote: >> I am worried which one is better in terms of performance? iniparse or >> ConfigParser? >> >> I am aware iniparse will do a better job of maintaining INI file's >> structure, but I am more interes

  1   2   >