[openstack-dev] [Neutron] How are Tenant VMs' traffic routed to Service VMs

Hi, folks I'm trying tacker to start some service VMs as Service Function VNF by "heat" tenant user, service VMs have special Neutron net & subnet, other common tenant VMs will have their own Neutron net & subnet, my question is how to route the traffic to service VMs in Openstack environment,

Re: [openstack-dev] [oslo] Graduate cliutils.py into oslo.utils

-Original Message- From: Doug Hellmann [mailto:d...@doughellmann.com] Sent: 16 November 2015 21:46 To: openstack-dev Subject: Re: [openstack-dev] [oslo] Graduate cliutils.py into oslo.utils Excerpts from Kekane, Abhishek's message of 2015-11-16 07:33:48 +: > Hi, > > As apiclient is n

Re: [openstack-dev] OpenStack-Announce List

Excerpts from Tom Fifield's message of 2015-11-19 20:00:20 -0800: > Hi all, > > I'd like to get your thoughts about the OpenStack-Announce list. > > We describe the list as: > > """ > Subscribe to this list to receive important announcements from the > OpenStack Release Team and OpenStack Secur

Re: [openstack-dev] Is there any way I can completely erase all the data when deleting a cinder volume

Oh, I missed that configuration. Thanks very much! On Wed, Nov 18, 2015 at 9:21 PM, Duncan Thomas wrote: > For the LVM and raw block device drivers, there is already an option to do > that - set volume_clear to 'zero' in cinder.conf > > If you want this for other drivers, then the code could

Re: [openstack-dev] [Neutron] Bug update

Hi, One extra thing. A large chunk of the latest bugs opened are RFE's. These are tagged with 'rfe'. In addition to this I would suggest changing the title of the bug to have [RFE]. This will at least help those who are perusing over the bugs to see what are actually real bug and what are new fe

[openstack-dev] [Neutron] Bug update

Hi, There are a ton of old and ancient bugs that have not been trained. If you guys have some time then please go over them. In most cases some are not even bugs and are just questions. I have spent the last few days going over and training a few. Over the last two days a number of bugs related

Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

+1 to remove containers On Fri, Nov 20, 2015 at 12:29 AM, Thomas Goirand wrote: > On 11/19/2015 03:59 PM, Vladimir Kozhukalov wrote: > > Anyway, the idea is to get > > rid of Docker containers on the master node and switch to plane package > > based approach that we used before. > > +1 > > > ___

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Dmitry, I mean whole feature. Btw, why do you want to grant capabilities via puppet? It should be done by post-install package section, I believe. Also I doesn't know if supervisord can bound process capabilities like systemd can - we could use this opportunity too. On Thu, Nov 19, 2015 at 7:44 P

Re: [openstack-dev] OpenStack-Announce List

On 2015-11-19 11:00 PM, Tom Fifield wrote: > > Personally, I no longer consider this volume "low traffic" :) > > In addition, I have been recently receiving feedback that users have > been unsubscribing from or deleting without reading the list's posts. > > That isn't good news, given this is sup

Re: [openstack-dev] [Ceilometer]:Subscribe and Publish Notification frame work in Ceilometer !

On 19/11/15 10:26 PM, Srikanth Vavilapalli wrote: Hi Gord On your second point, Yes, Ceilometer does provide a framework to capture a notification and republish to multiple “publish targets” in addition to the collector service using udp/kafka/notification as the transport mechanisms… We b

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

On 19/11/15 08:53 PM, Matt Riedemann wrote: On 11/19/2015 5:52 PM, gord chung wrote: ceilometer cares. we listen to all notifications and build Measurement and Event data from (some of) them. to be honest, i don't know if changes in nova notifications have/are broken in ceilometer because qu

[openstack-dev] What's Up Doc, 20 Nov 2015

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, This week I've been working on catching up with some reviews and bug triage, I've been speaking to O'Reilly about the future of the Ops Guide, and also been working on a range of other things including docs-specs core team review, and

Re: [openstack-dev] [Neutron] Mid-cycle meetup for Mitaka

Guys, Is there a conclusion now? What's the schedule of Neutron Mid-cycle? On Thu, Nov 5, 2015 at 9:31 PM, Gary Kotton wrote: > Hi, > In Nova the new black is the os-vif-lib > (https://etherpad.openstack.org/p/mitaka-nova-os-vif-lib). It may be > worthwhile seeing if we can maybe do something at

[openstack-dev] What's Up, Doc? 20 Nov 2015

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, This week I've been working on catching up with some reviews and bug triage, I've been speaking to O'Reilly about the future of the Ops Guide, and also been working on a range of other things including docs-specs core team review, and

[openstack-dev] OpenStack-Announce List

Hi all, I'd like to get your thoughts about the OpenStack-Announce list. We describe the list as: """ Subscribe to this list to receive important announcements from the OpenStack Release Team and OpenStack Security Team. This is a low-traffic, read-only list. """ Up until July 2015, it was

Re: [openstack-dev] [Ceilometer]:Subscribe and Publish Notification frame work in Ceilometer !

Hi Gord On your second point, Yes, Ceilometer does provide a framework to capture a notification and republish to multiple "publish targets" in addition to the collector service using udp/kafka/notification as the transport mechanisms... We believe this is how "Event Alarm Evaluator" module in

[openstack-dev] [tacker] Automatic flavor creation

Hi tackers, I am working on automatic flavor creation RFE[1]. I have written my thoughts on implementing on it. I would like to see your comments on it. Due to time differences, I was not able to directly ping core members in IRC. [1]https://bugs.launchpad.net/tacker/+bug/1516193 RegardsBharath T

Re: [openstack-dev] [Neutron][ThirdPartyCI] Running third party CI on networking-foo projects

On Fri, Nov 20, 2015 at 2:27 AM, Fawad Khaliq wrote: > Thanks a lot, Yamamoto. > > kakuma, I am assuming if you were able to set it up for a ofagent repo, then > it should have been the standard procedure documented here [1]. I reach out > to infra for any help. > > [1] http://docs.openstack.org/i

[openstack-dev] [cinder][nova]Move encryptors to os-brick

Hi all, To fix bug [1][2] in Cinder, Cinder needs to use nova/volume/encryptors[3] to attach/detach encrypted volumes. To decrease the code duplication, I raised a BP[4] to move encryptors to os-brick[5]. Once it is done, Nova needs to update to use the common library. This is BP raised. [6]

Re: [openstack-dev] How to add a periodic check for typos?

Just talking about the idea of auto-spelling-fix. My example patch https://review.openstack.org/#/c/247261/ doesn't work. Topy fixes something and break others. So it is just okay to do auto-spelling-check now, not fix :( On Fri, Nov 20, 2015 at 6:31 AM, Matt Riedemann wrote: > > > On 11/18/20

[openstack-dev] [Senlin]Support more complicated scaling scenario

Hi, guys, Xu Jun is a contributor from CMCC. He asked a very interesting question about cluster scaling support in Senlin. To make the discussion more thorough, I just post the question and my answer here. The question from Jun is as following: For an action, senlin will check all according poli

Re: [openstack-dev] [Neutron] Call for review focus

On 19 November 2015 at 18:26, Assaf Muller wrote: > On Wed, Nov 18, 2015 at 9:14 PM, Armando M. wrote: > > Hi Neutrites, > > > > We are nearly two weeks away from the end of Mitaka 1. > > > > I am writing this email to invite you to be mindful to what you review, > > especially in the next coupl

Re: [openstack-dev] [Neutron] Call for review focus

On Wed, Nov 18, 2015 at 9:14 PM, Armando M. wrote: > Hi Neutrites, > > We are nearly two weeks away from the end of Mitaka 1. > > I am writing this email to invite you to be mindful to what you review, > especially in the next couple of weeks. Whenever you have the time to review > code, please co

Re: [openstack-dev] [release][stable] OpenStack 2014.2.4 (juno)

fyi https://review.openstack.org/#/c/247677/ On Thu, Nov 19, 2015 at 8:56 PM, Rochelle Grober wrote: > Again, my plea to leave the Juno repository on git.openstack.org, but locked > down to enable at least grenade testing for Juno->Kilo upgrades. For upgrade > testing purposes, python2.6 is no

[openstack-dev] [release][stable] OpenStack 2014.2.4 (juno)

Again, my plea to leave the Juno repository on git.openstack.org, but locked down to enable at least grenade testing for Juno->Kilo upgrades. For upgrade testing purposes, python2.6 is not needed as any cloud would have to upgrade python before upgrading to kilo. The testing could/should be li

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

On 11/19/2015 5:52 PM, gord chung wrote: ceilometer cares. we listen to all notifications and build Measurement and Event data from (some of) them. to be honest, i don't know if changes in nova notifications have/are broken in ceilometer because quite frankly there are far too many notification

Re: [openstack-dev] [Horizon] Bug day! Yeah!

Thanks Rob, next Tuesday is fine with me. -Zhenguo Sent from my iPhone > On Nov 19, 2015, at 19:19, Rob Cresswell (rcresswe) > wrote: > > Hey folks, > > Our bug list is… rather large. We’ve discussed having a bug day, where as a > community we all dedicate some time to triaging bugs and dis

Re: [openstack-dev] [all]Can we get some sanity in the Neutron logs please?

Thanks both Armando and Matt! I am cross posting this to the operators' list (as the main post -- operators, simple reply and no spam to dev). The logging tag should be a tag in all projects. I'm glad it's already there in Neutron. And, this sort of feedback is exactly what we need operators

Re: [openstack-dev] [openstack][openstack-operators] IRC meeting(s)

++ > -Original Message- > From: Thierry Carrez [mailto:thie...@openstack.org] > Sent: Thursday, November 19, 2015 1:52 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [openstack][openstack-operators] IRC > meeting(s) > > JJ Asghar wrote: > > I've been seeing some

Re: [openstack-dev] [Openstack-operators] [openstack-ansible] Fedora/CentOS/other Support

On 11/19/2015 09:32 AM, Kevin Carter wrote: > I don't believe we should have a class system in the OS's that we choose > to support. If we're going to bring in a new OS I think we should first > bring it in using non-voting jobs however once all of the bits have been > finalized the supported OS

Re: [openstack-dev] [Horizon] Bug day! Yeah!

Great, I'll be around next Tuesday. -Lin On Thu, Nov 19, 2015 at 12:53 PM, Rob Cresswell (rcresswe) < rcres...@cisco.com> wrote: > As requested, > https://etherpad.openstack.org/p/horizon-bug-day > > Rob > > From: Richard Jones > Reply-To: "OpenStack Development Mailing List (not for usage ques

Re: [openstack-dev] [ironic] Redfish drivers in ironic

Hello, Vladyslav Drok said on Thu, Nov 19, 2015 at 03:59:41PM +0200: Hi list and Bruno, I’m interested in adding virtual media boot interface for redfish ( https://blueprints.launchpad.net/ironic/+spec/redfish-virtual-media-boot). It depends on https://blueprints.launchpad.net/ironic/+spec/iron

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

ceilometer cares. we listen to all notifications and build Measurement and Event data from (some of) them. to be honest, i don't know if changes in nova notifications have/are broken in ceilometer because quite frankly there are far too many notifications to test and track. as a consumer of da

Re: [openstack-dev] [magnum] Mesos Conductor

It's great that we come to some agreement on unifying the client call ;-) As i proposed in previous thread, I think that "magnum app-create" may be better than "magnum create", I want to use "magnum app-create" to distinguish with "magnum container-create". The "app-create" may also not a good nam

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

On Tue, Nov 17, 2015 at 12:35 AM, Jim Rollenhagen wrote: > > > My preference is 4) no mid-cycle -- and try to work more effectively with > > people in different locations and time zones. > > ++ that was part of my thought process when I proposed not having an > official midcycle. > Thanks for th

Re: [openstack-dev] [puppet] weekly meeting #59

Clayton O'Neill wrote: > On Tue, Nov 17, 2015 at 4:38 PM, Cody Herriges > wrote: > > Now that the standard is $::os_service_default does it mean that current > changes up for review with parameters set to the string ' DEFAULT>' should be changed to $::os_se

Re: [openstack-dev] How to add a periodic check for typos?

On 11/18/2015 8:00 PM, Gareth wrote: Hi stacker, We could use some 3rd tools like topy: pip install topy topy -a git commit & git review Here is an example: https://review.openstack.org/#/c/247261/ Could we have a periodic job like Jenkins users updating our requirement.txt?

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

On 11/19/2015 4:05 PM, Ryan Rossiter wrote: Reading through [1] I started getting worries in the back of my head about versioning these notifications. The main concern being how can the consumer know about the versions and what's different between them? Because these versioned notification payl

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

> > Another idea I floated last week was to do a virtual midcycle of sorts. > > Treat it like a normal midcycle in that everyone tells their management > > "I'm out for 3-4 days for the midcycle", but they don't travel anywhere. > > We come up with an agenda, see if there's any planning/syncing wor

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On 19 November 2015 at 09:25, Brad P. Crochet wrote: > I have pushed up a draft of the spec. Let's move comments there. > > I tried to incorporate as much as I could from the discussion here. > There was a lot of disjointed suggestions and was a bit difficult to > follow. So I've taken what I can

Re: [openstack-dev] [Fuel] Number of IP addresses in a public network

The high value of the bug here reflects that the error message is wrong. >From a UX side we could maybe even justify this as Critical. The error message must reflect the correct quantity of addresses required. On Tue, Nov 17, 2015 at 1:31 PM Roman Prykhodchenko wrote: > Folks, we should resurre

[openstack-dev] [nova] Versioned notifications... who cares about the version?

Reading through [1] I started getting worries in the back of my head about versioning these notifications. The main concern being how can the consumer know about the versions and what's different between them? Because these versioned notification payloads hold live nova objects, there can be a

Re: [openstack-dev] [ironic] weekly subteam status report

On 17 November 2015 at 01:34, Naohiro Tamura wrote: > Ruby, > > Thanks for taking care of our weekly status report. > I'd like to just let you know that the iRMC part is somehow consolidated > with old statuses which I reported two and three weeks ago. > If this report were generated by a script,

Re: [openstack-dev] [nova] release notes with reno and which patches need that?

Le 19/11/2015 20:46, Sylvain Bauza a écrit : Le 19/11/2015 18:37, Markus Zoeller a écrit : If you ever had a patch which contained "UpgradeImpact" or "DocImpact", this mail is for you. You may have already heard of "reno" and how it will change the handling of the release notes. If not, [1]

Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

On 11/19/2015 03:59 PM, Vladimir Kozhukalov wrote: > Anyway, the idea is to get > rid of Docker containers on the master node and switch to plane package > based approach that we used before. +1 __ OpenStack Development Mai

Re: [openstack-dev] [magnum] Mesos Conductor

+1, I found that 'kubectl create -f FILENAME’ (https://github.com/kubernetes/kubernetes/blob/release-1.1/docs/user-guide/kubectl/kubectl_create.md) works very well for different type of objects and I think we should try to use it. but I think we should support two use-cases - 'magnum container

Re: [openstack-dev] [infra][glance] How do we fix the glance_store git > glance-store LP mapping?

On 11/19/2015 11:38 AM, Clark Boylan wrote: On Thu, Nov 19, 2015, at 08:00 AM, Matt Riedemann wrote: Patches in Gerrit aren't syncing status to the glance-store project in launchpad b/c the project in launchpad is called glance-store and in git it's glance_store. Looking at the project creato

Re: [openstack-dev] [tc][infra][neutron] branches for release-independent projects targeting Openstack release X

On Thu, 19 Nov 2015, Julien Danjou wrote: It would be good to support that as being *normal*, not "potentially incorrect and random"! Yes. The underlying issue in this thread is the dominance of the six month cycle and the way this is perceived to be (any may actually be) a benefit for distri

Re: [openstack-dev] [Horizon] Bug day! Yeah!

As requested, https://etherpad.openstack.org/p/horizon-bug-day Rob From: Richard Jones mailto:r1chardj0...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Thursday, 19 November 2015 20:39 To: "OpenStack Develop

[openstack-dev] [security][sahara] creating a threat analysis to aid operators

hello all, during the security midcycle meetup we had a session about creating threat analysis for openstack projects. the folks at HPE were kind enough to offer their documentation and examples as an aid to creating these analysis. after talking with the sahara team, i am confident that we

Re: [openstack-dev] [Horizon] Bug day! Yeah!

Let's do it. I'd like to suggest we use an etherpad to keep track of what people have done. If it's not created when I start my day, I'll make one. Richard On 19 November 2015 at 22:19, Rob Cresswell (rcresswe) wrote: > Hey folks, > > Our bug list is… rather large. We’ve discussed having

Re: [openstack-dev] [infra][glance] How do we fix the glance_store git > glance-store LP mapping?

Yes, that is why I have suggested you either update the mapping so it is correct or you use glance which is what the mapping currently says you want to use. On Thu, Nov 19, 2015, at 12:08 PM, Nikhil Komawar wrote: > When I originally wanted to create the naming for glance_store to be > consistent

Re: [openstack-dev] [infra][glance] How do we fix the glance_store git > glance-store LP mapping?

When I originally wanted to create the naming for glance_store to be consistent across platforms, we already had the library glance_store out (actually it first called glance.store but due to the anxiety of namespace conflicts it was quickly renamed to glance_store in git/gerrit etc.). Creating a p

[openstack-dev] [Cinder] Mitaka Midcycle Sprint

Cinder Mitaka Midcycle Sprint Dates: January 26-29 (29th will be optional hack day) Location: NetApp Office 7301 Kit Creek Road, Research Triangle Park, NC 27709 https://www.openstreetmap.org/search?query=35.8578%2C-78.8839#map=16/35.8569/-78.8851 Contact: Tom Barron (tbarron) Nearest airport: R

Re: [openstack-dev] [nova] release notes with reno and which patches need that?

Le 19/11/2015 18:37, Markus Zoeller a écrit : If you ever had a patch which contained "UpgradeImpact" or "DocImpact", this mail is for you. You may have already heard of "reno" and how it will change the handling of the release notes. If not, [1] is the announcement and [2] is an example. I wan

Re: [openstack-dev] How to add a periodic check for typos?

So since requirements usually has an 's' on the end, would you make my cheque for $1.00 payable to the Campaign Against Smog Hazard please? Just use our initials. -- MC __ OpenStack Development Mailing List (not for usage qu

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

My personal preference is to say: 1. Any templates which are included in the default environment (e.g overcloud-resource-registry-puppet.yaml), must expose their parameters via overcloud-without-mergepy.yaml 2. Any templates which are included in the default environment, but via a "noop" impleme

Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

Hey guys, Despite the fact I like containers (as deployment unit), we don't use them so. That means I +1 idea to drop containers, just because I believe that would * simplify a lot of things * helps get rid of huge amount of hacks * increase master node deployment * release us from annoying suppo

Re: [openstack-dev] [oslo] Should we make qpid/proton optional dependencies? (please say yes)

On 11/19/2015 12:22 PM, Matt Riedemann wrote: I want to fix a thing in oslo.messaging but to my surprise I can't run pep8. This is because python-qpid-proton tries to install qpid-proton and it can't get that because the apache site where it's hosted is down. [1] The apache site for qpid has a

Re: [openstack-dev] [oslo] Should we make qpid/proton optional dependencies? (please say yes)

yes :) On Thu, Nov 19, 2015 at 1:22 PM, Matt Riedemann wrote: > I want to fix a thing in oslo.messaging but to my surprise I can't run pep8. > This is because python-qpid-proton tries to install qpid-proton and it can't > get that because the apache site where it's hosted is down. [1] > > The a

Re: [openstack-dev] [lbaas] [octavia] Proposing Bertrand Lallau as Octavia Core

+1 On Thu, Nov 19, 2015 at 9:35 AM, Eichberger, German wrote: > All, > > > > As I said in a previous e-mail I am really excited about the deep talent in > the Octavia sub-project. So it is my pleasure to propose Bertrand Lallau (irc > blallau) as a new core for the OpenStack Neutron Octavia sub

Re: [openstack-dev] [Openstack-operators] [logs] Neutron not logging user information on wsgi requests by default

Sorry, I missed this earlier. I was in no way meaning to suggest running devstack for production. I was asking that operators look at their wsgi logs, and see if they are logging a username/tenant for Neutron requests. If not, providing a way to fix that (which I happened to take from DevStack)

Re: [openstack-dev] [lbaas] [octavia] Proposing Bertrand Lallau as Octavia Core

+1 > On Nov 19, 2015, at 11:39 AM, Brandon Logan > wrote: > > +1 > > On Thu, 2015-11-19 at 17:35 +, Eichberger, German wrote: >> All, >> >> >> >> As I said in a previous e-mail I am really excited about the deep talent in >> the Octavia sub-project. So it is my pleasure to propose Bert

Re: [openstack-dev] [magnum] Mesos Conductor

I’m open to allowing magnum to pass a blob of data (such as a lump of JSON or YAML) to the Bay's native API. That approach strikes a balance that’s appropriate. Adrian On Nov 19, 2015, at 10:01 AM, bharath thiruveedula mailto:bharath_...@hotmail.com>> wrote: Hi, At the present scenario, we c

Re: [openstack-dev] [lbaas] [octavia] Proposing Bertrand Lallau as Octavia Core

+1 On Thu, 2015-11-19 at 17:35 +, Eichberger, German wrote: > All, > > > > As I said in a previous e-mail I am really excited about the deep talent in > the Octavia sub-project. So it is my pleasure to propose Bertrand Lallau (irc > blallau) as a new core for the OpenStack Neutron Octavia

Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

Folks I guess it should be pretty simple to roll back - install older version and restore the backup with preservation of /var/log directory. On Thu, Nov 19, 2015 at 7:38 PM, Sergii Golovatiuk wrote: > Hi, > > On Thu, Nov 19, 2015 at 5:50 PM, Matthew Mosesohn > wrote: > >> Vladimir, >> >> The

[openstack-dev] [oslo] Should we make qpid/proton optional dependencies? (please say yes)

I want to fix a thing in oslo.messaging but to my surprise I can't run pep8. This is because python-qpid-proton tries to install qpid-proton and it can't get that because the apache site where it's hosted is down. [1] The apache site for qpid has actually been down a lot lately, I coincidental

[openstack-dev] [nova] What things do we want to get into a python-novaclient 3.0 release?

We've been talking about doing a 3.0 release for novaclient for awhile so we can make some backward incompatible changes, like: 1. Removing the novaclient.v1_1 module 2. Dropping py26 support (if there is any explicit py26 support in there) What else are people aware of? Monty was talking abou

Re: [openstack-dev] [openstack-dev ] [Heat] how to verify heat resource plugin

Hi Mohan, well, you should have the service you are developing the resource plugin for installed somewhere and run heat against it, creating the stack with the new resource type your plugin is defining, and checking that the thing it creates is working, can be updated and deleted via heat template

Re: [openstack-dev] [magnum] Mesos Conductor

Hi, At the present scenario, we can have mesos conductor with existing attributes[1]. Or we can add extra options like 'portMappings', 'instances', 'uris'[2]. And the other options is to take json file as input to 'magnum container-create' and dispatch it to corresponding conductor. And the con

Re: [openstack-dev] [Manila] Mitaka deadlines

On 11/19/2015 12:24 PM, Ben Swartzlander wrote: Based on discussions going back to the Liberty feature freeze, we have decided to add some additional deadlines for Mitaka, to avoid having fire drills at the end of the release, and to focus core reviewer attention on the right things. As always,

[openstack-dev] [Manila] Midcycle meetup survey

If you planning to attend the midcycle in any capacity, please vote your preferences here: https://www.surveymonkey.com/r/BXPLDXT -Ben __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-

Re: [openstack-dev] [Neutron][IPAM] Arbitrary JSON blobs in ipam db tables

On Mon, Nov 9, 2015 at 1:39 PM, Shraddha Pandhe wrote: > Thats great. L3 layer network model is definitely one of our most important > requirements. All our go-forward deployments are going to be L3. So this is > a big deal for us. I think we're on a good path to getting this figured out over the

Re: [openstack-dev] [trove] trove unit tests failing on stable/kilo [imm]

> On Nov 19, 2015, at 11:24 AM, Matt Riedemann > wrote: > > > > On 11/19/2015 10:22 AM, Amrith Kumar wrote: >> Just catching up on this thread, have fixes been submitted for this already? >> >> Thanks, >> >> -amrith >> >>> -Original Message- >>> From: Matt Riedemann [mailto:mrie...

Re: [openstack-dev] [infra][glance] How do we fix the glance_store git > glance-store LP mapping?

On Thu, Nov 19, 2015, at 08:00 AM, Matt Riedemann wrote: > Patches in Gerrit aren't syncing status to the glance-store project in > launchpad b/c the project in launchpad is called glance-store and in git > it's glance_store. > > Looking at the project creators guide it says to specify a group f

Re: [openstack-dev] [Neutron] Call for review focus

++ On Wed, Nov 18, 2015 at 7:14 PM, Armando M. wrote: > Hi Neutrites, > > We are nearly two weeks away from the end of Mitaka 1. > > I am writing this email to invite you to be mindful to what you review, > especially in the next couple of weeks. Whenever you have the time to review > code, pleas

[openstack-dev] [nova] release notes with reno and which patches need that?

If you ever had a patch which contained "UpgradeImpact" or "DocImpact", this mail is for you. You may have already heard of "reno" and how it will change the handling of the release notes. If not, [1] is the announcement and [2] is an example. I wanted to preemptively ask if we want to add some gui

Re: [openstack-dev] [lbaas] [octavia] Proposing Bertrand Lallau as Octavia Core

All, As I said in a previous e-mail I am really excited about the deep talent in the Octavia sub-project. So it is my pleasure to propose Bertrand Lallau (irc blallau) as a new core for the OpenStack Neutron Octavia sub project. His contributions [1] are in line with other cores and he has be

[openstack-dev] [nova] build_instance pre hook cannot set injected_files for new instance

I have some code that uses the build_instance pre hook to set injected_files in the new instance. With the kilo code, the argv[7] was passed as [] - so I could append/extend this value to add more injected_files. With the latest code, this is passed as None, so I can't set it. How can I pass

Re: [openstack-dev] [Neutron][ThirdPartyCI] Running third party CI on networking-foo projects

Thanks a lot, Yamamoto. kakuma, I am assuming if you were able to set it up for a ofagent repo, then it should have been the standard procedure documented here [1]. I reach out to infra for any help. [1] http://docs.openstack.org/infra/system-config/third_party.html Fawad Khaliq On Wed, Nov 18

Re: [openstack-dev] [trove] trove unit tests failing on stable/kilo [imm]

Thanks Matt, Craig (cp16net) is working on fixing this. -amrith > -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: Thursday, November 19, 2015 12:24 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [trove] trove unit tests fail

[openstack-dev] [Manila] Mitaka deadlines

Based on discussions going back to the Liberty feature freeze, we have decided to add some additional deadlines for Mitaka, to avoid having fire drills at the end of the release, and to focus core reviewer attention on the right things. As always, we will enforce a Feature Freeze on the M-3 mi

Re: [openstack-dev] [trove] trove unit tests failing on stable/kilo [imm]

On 11/19/2015 10:22 AM, Amrith Kumar wrote: Just catching up on this thread, have fixes been submitted for this already? Thanks, -amrith -Original Message- From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] Sent: Wednesday, November 18, 2015 2:54 PM To: openstack-dev@lists.ope

Re: [openstack-dev] [releases] Release countdown for week R-19, Nov 23-27

On 11/19/2015 8:42 AM, Doug Hellmann wrote: Excerpts from Matt Riedemann's message of 2015-11-18 18:22:59 -0600: On 11/18/2015 4:09 PM, Doug Hellmann wrote: Focus - We are currently working towards the Mitaka 1 milestone scheduled for Dec 1-3. Teams should be focusing on wrapping up inc

Re: [openstack-dev] [neutron][tap-as-a-service] weekly meeting

Hi Yamamoto, Thanks for resuming work on this effort. TAP-as-a-service is a very important feature, and great to see we are considering use case scenarios and adjusting APIs accordingly. I have some thoughts on the use case scenarios, which are seen as most common ones, when talking to operators.

Re: [openstack-dev] [infra][glance] How do we fix the glance_store git > glance-store LP mapping?

On 11/19/15, 10:00, "Matt Riedemann" wrote: >Patches in Gerrit aren't syncing status to the glance-store project in >launchpad b/c the project in launchpad is called glance-store and in git >it's glance_store. > >Looking at the project creators guide it says to specify a group for the >mapping

Re: [openstack-dev] [nova] [Openstack-operators] Profiling nova-conductor and eventlet

Kris and I also experimented with: https://gist.github.com/harlowja/d2b5fc5282c76f10bc3f (which is like the entrypoint to cProfile but instead using the eventlet profiler module instead), that didn't appear to go so well... So any thoughts would be great here (especially around how to profile

Re: [openstack-dev] [nova][infra] Getting a bleeding edge libvirt gate job running

Tony Breeds wrote on 11/18/2015 10:43:30 PM: > From: Tony Breeds > To: "Daniel P. Berrange" , "OpenStack Development > Mailing List (not for usage questions)" > Date: 11/18/2015 10:44 PM > Subject: Re: [openstack-dev] [nova][infra] Getting a bleeding edge > libvirt gate job running > > On We

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

On Thu, Nov 19, 2015 at 06:50:35PM +0200, Juan Antonio Osorio wrote: >On Thu, Nov 19, 2015 at 6:16 PM, Steven Hardy wrote: > > On Mon, Nov 16, 2015 at 08:15:48PM +0100, Giulio Fidente wrote: > > On 11/16/2015 04:25 PM, Steven Hardy wrote: > > >Hi all, > > > > > >I wan

Re: [openstack-dev] [Infra] Remove .mailmap files from OpenStack repos

On Thu, Nov 19, 2015 at 07:28:03PM +0300, Mikhail Fedosin wrote: > Currently we have .mailmap files in the root of almost all OpenStack repos: > https://github.com/openstack/glance/blob/master/.mailmap > https://github.com/openstack/horizon/blob/master/.mailmap > https://github.com/openstack/nova/b

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

My main concern with using linux capabilities/acls on files is actually puppet support or, actually, the lack of it. ACLs are possible AFAIK, but we'd need to write a custom type/provider for capabilities. I suggest to wait with capabilities support till systemd support. On Tue, Nov 17, 2015 at 9:

Re: [openstack-dev] [tc][infra][neutron] branches for release-independent projects targeting Openstack release X

Doug : [snip] I get your point. This would indeed correctly model intermediate releases. But since no other project in Openstack depends on networking-bgpvpn, what is the value of forcing a release of the project synched at the end of a cycle ? It raises your chances of having your project pack

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

On Thu, Nov 19, 2015 at 6:16 PM, Steven Hardy wrote: > On Mon, Nov 16, 2015 at 08:15:48PM +0100, Giulio Fidente wrote: > > On 11/16/2015 04:25 PM, Steven Hardy wrote: > > >Hi all, > > > > > >I wanted to start some discussion re $subject, because it's been > apparrent > > >that we have a lack of c

Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

Hi, On Thu, Nov 19, 2015 at 5:50 PM, Matthew Mosesohn wrote: > Vladimir, > > The old site.pp is long out of date and should just be recreated from the > content of all the other $service-only.pp files. > > My main question is how do we propose to do a rollback from an update (in > theory, from 8

Re: [openstack-dev] [Infra] Remove .mailmap files from OpenStack repos

On Thu, Nov 19 2015, Mikhail Fedosin wrote: > Currently we have .mailmap files in the root of almost all OpenStack repos: > https://github.com/openstack/glance/blob/master/.mailmap > https://github.com/openstack/horizon/blob/master/.mailmap > https://github.com/openstack/nova/blob/master/.mailmap

Re: [openstack-dev] [tc][infra][neutron] branches for release-independent projects targeting Openstack release X

On Thu, Nov 19 2015, Jim Rollenhagen wrote: > This is actually the idea of the cycle-with-intermediary model. Projects > following this model may release as early and often as they like, and > choose a release near the same time as the coordinated release, to be > the "cycle" release and the base

Re: [openstack-dev] [magnum] Issue on history of renamed file/folder

As I see this, we need to pick the better of two options, even when neither is perfect. I’d rather have magnum’s source as intuitive and easy to maintain as possible. If it becomes more difficult to follow the commit history for a file in order to achieve that improvement, I’m willing to live wi

Re: [openstack-dev] [tc][infra][neutron] branches for release-independent projects targeting Openstack release X

On Thu, Nov 19, 2015 at 04:35:24PM +0100, Julien Danjou wrote: > On Thu, Nov 19 2015, Doug Hellmann wrote: > > > In my mind the “independent” release model was originally meant to mean that > > the project was completely on their own, doing potentially incorrect and > > random > > releases. It wa

[openstack-dev] [Infra] Remove .mailmap files from OpenStack repos

Currently we have .mailmap files in the root of almost all OpenStack repos: https://github.com/openstack/glance/blob/master/.mailmap https://github.com/openstack/horizon/blob/master/.mailmap https://github.com/openstack/nova/blob/master/.mailmap https://github.com/openstack/cinder/blob/master/.mail

[openstack-dev] [nova] [Openstack-operators] Profiling nova-conductor and eventlet

Calling all Proflers! I am running into an issue with CPU usage on remote nova-conductor and I am trying to profile it to see where its consuming the most amount of cpu, so that we can investigate further. The etherpad where we have been working on this issue is located at: https://etherpad.o

  1   2   >