Re: [openstack-dev] [TripleO] Consolidating TripleO validations with Browbeat validations

On 06/20/2016 08:58 PM, Assaf Muller wrote: On Mon, Jun 20, 2016 at 12:43 PM, Joe Talerico wrote: On Mon, Jun 20, 2016 at 12:41 PM, Ihar Hrachyshka wrote: On 20 Jun 2016, at 18:37, Joe Talerico wrote: Hello - It would seem

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Le 21/06/2016 10:04, Chris Dent a écrit : On Mon, 20 Jun 2016, Jay Pipes wrote: Flask seems to be the most widely used and known WSGI framework so for consistency's sake, I'm recommending we just use it and not rock this boat. There are more important things to get hung up on than this

[openstack-dev] [Nova] Live migration meeting today

Agenda here: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration We will go over the non-priority feature status today Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] Version header for OpenStack microversion support

On 06/21/2016 01:59 AM, Clint Byrum wrote: > Excerpts from Edward Leafe's message of 2016-06-20 20:41:56 -0500: >> On Jun 18, 2016, at 9:03 AM, Clint Byrum wrote: >> >>> Whatever API version is used behind the compute API is none of the user's >>> business. >> >> Actually, yeah,

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Le 21/06/2016 14:00, Sean Dague a écrit : On 06/21/2016 07:39 AM, Jay Pipes wrote: On 06/21/2016 05:43 AM, Sylvain Bauza wrote: Le 21/06/2016 10:04, Chris Dent a écrit : On Mon, 20 Jun 2016, Jay Pipes wrote: Flask seems to be the most widely used and known WSGI framework so for

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

On 06/21/2016 12:37 AM, Andre Florath wrote: Hi! Before things getting said twice (looks that there is some public interest here ;-) ): :) Can you please rerun and skip the partition part of the loop device for fdisk -l? E.g. instead of /dev/loop0p1 just /dev/loop0? (This was my original

[openstack-dev] [Monasca] Locked (latched) alarms

Hello everyone, I have written a short blueprint on locked/latched alarms for Monasca [1]. The functionality allows the operator to define an alarm which after transition to ALARM state, stays in that state until it is manually reset. What name should we use for that? Locked, lockable,

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On 06/21/2016 05:43 AM, Sylvain Bauza wrote: Le 21/06/2016 10:04, Chris Dent a écrit : On Mon, 20 Jun 2016, Jay Pipes wrote: Flask seems to be the most widely used and known WSGI framework so for consistency's sake, I'm recommending we just use it and not rock this boat. There are more

[openstack-dev] [nova] PCI Based NUMA Scheduling can't really achieve pci numa binding in some cases

Hi, In the current implementation scheme: /nova/pci/stats.py def _filter_pools_for_numa_cells(pools, numa_cells): # Some systems don't report numa node info for pci devices, in # that case None is

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Chris Dent wrote: On Mon, 20 Jun 2016, Doug Wiegley wrote: So, it sounds like you’ve just described the job of the TC. And they have so far refused to define OpenStack, leading to a series of derivative decisions that seem … inconsistent over time. Thanks for writing down what I was thinking.

Re: [openstack-dev] [neutron][qos] Egress minimum bandwidth assurance

On 2016/06/15 18:54, Alonso Hernandez, Rodolfo wrote: Hello: Context: try to develop a driver for this feature in OVS. During the last week I’ve been testing several scenarios to make a POC of this feature. Scenario 1: 3 VM connected to br-int, sending traffic through br-physical to

Re: [openstack-dev] [TripleO] Consolidating TripleO validations with Browbeat validations

On 06/20/2016 06:37 PM, Joe Talerico wrote: Hello - It would seem there is a little bit of overlap with TripleO validations ( clapper validations ) and Browbeat *Checks*. I would like to see these two come together, and I wanted to get some feedback on this. For reference here are the Browbeat

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On 06/21/2016 07:39 AM, Jay Pipes wrote: > On 06/21/2016 05:43 AM, Sylvain Bauza wrote: >> Le 21/06/2016 10:04, Chris Dent a écrit : >>> On Mon, 20 Jun 2016, Jay Pipes wrote: >>> Flask seems to be the most widely used and known WSGI framework so for consistency's sake, I'm recommending

Re: [openstack-dev] [all] Proposal: Architecture Working Group

On 06/20/2016 08:07 PM, Clint Byrum wrote: > Excerpts from Jesse Cook's message of 2016-06-20 16:58:48 +: >> +1 >> >> The points about the PWG and TC are worth some consideration. >> >> From my perspective, I think it would make sense for the PWG to define the >> expected behaviors of the

[openstack-dev] Reply: Release naming for P and Q open for nominations

2016-6-22 4:50 Monty Taylor [mailto:mord...@inaugust.com] wrote: > Hey everyone! > > It's time to pick a name for the P and Q releases. > > If you have a name you'd like us to vote on, please add it here: > > https://wiki.openstack.org/wiki/Release_Naming/P_Proposals > >

[openstack-dev] RHEL free for developer use (was: Require a level playing field for OpenStack projects)

On 2016-06-21 14:48:58 +0200 (+0200), Zane Bitter wrote: > That isn't my understanding, but it's hard to give a definitive > answer without knowing what kinds of non-free software you're > referring to (since I know there have been fierce disagreements > even e.g. within Debian on topics like

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

On Wed, 22 Jun 2016 at 05:59 Matt Riedemann wrote: > Angus, what should we be looking at from the privsep side for debugging > this? > The line above the screen-n-cpu.txt.gz failure you linked to is: 2016-06-21 16:21:30.994

[openstack-dev] [requirements][packaging] Normalizing requirements file

Hi, as a packager, I spend a lot of time to scrutinize the requirements repo, and I find it easier to read if specifiers are ordered. So in a quick glance, you can check which is the min version required and max one without trying to search them among other specifiers. I scripted a basic linter

Re: [openstack-dev] [oslo][monasca][requirements] Kafka 1.x for Oslo.Messaging and Monasca

Davanum, We started work on getting Monasca into the global requirements with two reviews [1] [2] that add gate jobs and check requirements jobs for the Monasca repositories. Some repositories are being adapted to use versions of libraries that OpenStack currently accepts [3] and we¹re looking

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

[openstack-dev] [mistal] Mistral logo ideas?

Hi, We’d like to finally come up with a logo for Mistral and it’d be cool to hear some ideas from the community. Some ideas from me: • A picture of a graph (but the point is that it must be very very simple) • A picture of a rocket (meaning that Mistral helps take off of the

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

2016-06-22 7:23 GMT+02:00 Tony Breeds : > > I'm fine with doign something like this. I wrote [1] some time ago but didn't > push on it as I needed to verify that this wouldn't create a "storm" of > pointless updates that just reorder things in every projects >

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

On Wed, Jun 22, 2016 at 10:15 AM, Haïkel wrote: > Hi, > > as a packager, I spend a lot of time to scrutinize the requirements > repo, and I find it easier to read if specifiers are ordered. > So in a quick glance, you can check which is the min version required > and

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

On Wed, Jun 22, 2016 at 06:45:31AM +0200, Haïkel wrote: > Hi, > > as a packager, I spend a lot of time to scrutinize the requirements > repo, and I find it easier to read if specifiers are ordered. > So in a quick glance, you can check which is the min version required > and max one without

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Excerpts from Sean Dague's message of 2016-06-21 08:00:50 -0400: > On 06/21/2016 07:39 AM, Jay Pipes wrote: > > On 06/21/2016 05:43 AM, Sylvain Bauza wrote: > >> Le 21/06/2016 10:04, Chris Dent a écrit : > >>> On Mon, 20 Jun 2016, Jay Pipes wrote: > >>> > Flask seems to be the most widely

Re: [openstack-dev] [Neutron] IRC meeting for VLAN-aware VM's

Today there's no IRC meeting dedicated to the trunk port work. Most of the discussion is going on in gerrit: https://review.openstack.org/#/q/topic:bp/vlan-aware-vms+-status:abandoned Or here in the mailing list. If you feel the need for it let us know and we can easily revive it. -- Bence On

[openstack-dev] Does nova-compute interact with nova Db?

I want to collect an *extra_resource* info from compute node(s) and add it in to the compute_nodes table. I like to understand how nova-compute interacts with DB currently. Thanks, Rao Adnan Khan AT Integrated Cloud (AIC) Development | SE Software Development & Engineering (SD) Emai:

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

On 20/06/16 18:50, Jeremy Stanley wrote: On 2016-06-20 18:43:44 +0200 (+0200), Zane Bitter wrote: The binaries are free-as-in-beer - IIUC you can't redistribute them. The source code, of course, remains free-as-in-speech as it has always been. (It's easy to forget the distinction when you work

[openstack-dev] [Cinder][Tempest][Infra] Cinder team seeks test/tempest/infra experts

The Cinder team has begun a test working group[1] with the goal of improving coverage and quality. We meet Weekly[2] at 1500 UTC in #openstack-cinder and would welcome anyone interested in providing expertise in Tempest/Infra/QA. Our Cinder team contributors have a smattering of knowledge and

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On 21/06/2016 13:04, Sean Dague wrote: > On 06/21/2016 07:39 AM, Jay Pipes wrote: >> On 06/21/2016 05:43 AM, Sylvain Bauza wrote: >>> Le 21/06/2016 10:04, Chris Dent a écrit : On Mon, 20 Jun 2016, Jay Pipes wrote: > Flask seems to be the most widely used and known WSGI framework so

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Chris Dent's message of 2016-06-21 09:25:44 +0100: > On Mon, 20 Jun 2016, Doug Wiegley wrote: > > > So, it sounds like you’ve just described the job of the TC. And they > > have so far refused to define OpenStack, leading to a series of > > derivative decisions that seem …

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

A reminder that this will happen in ~2 weeks. Please note that you can spare bug reports if you leave a comment there which says one of these (case-sensitive flags): * CONFIRMED FOR: NEWTON * CONFIRMED FOR: MITAKA * CONFIRMED FOR: LIBERTY On 23.05.2016 13:02, Markus Zoeller wrote: > TL;DR:

[openstack-dev] [Neutron] Intermittent failures on unit tests

Neutrinos, There's been a number of intermittent failures induced by the DNS integration code that popped up lately. One has been reported in [1], another showed up in [2]. I am in the progress of digging deeper to see what's going on, but if someone knows or working on the issue, please let us

[openstack-dev] [oslo][monasca][requirements] Kafka 1.x for Oslo.Messaging and Monasca

Roland Hochmuth, Joe Keen, The oslo.messaging folks have been trying off and on again [1] to get to python-kafka 1.x. Right now they are waiting on the Monasca team as we reverted python-kafka 1.x in [2] for the Monasca Team. I still don't see a review for adding Monasca to projects.txt which is

Re: [openstack-dev] [puppet] Action parameter missing in generated stonith fence manifests

Hi Devon, Devon Mizelle writes: > Greetings, > > I was directed here from #puppet-openstack to submit an e-mail. Well, the best way to have it done, would be to make bug in launchap[1] If you don't have the an account or the time time let me know I will do it for you, np.

[openstack-dev] [Neutron] Deprecation and release notes

Hi Neutrinos, I would like to remind you to be extra careful when handling the deprecation of config options. Do not forget to associate release notes when appropriate, or even bug reports tagged with 'deprecation' to track the deprecation cycle. Alerting operators/deployers/packagers of

Re: [openstack-dev] [all][oslo] pbr potential breaking change coming

> On 21 Jun 2016, at 15:01, Doug Hellmann wrote: > > A while back pbr had a feature that let projects pass "warnerror" > through to Sphinx during documentation builds, causing any warnings in > that build to be treated as an error and fail the build. This lets us > avoid

Re: [openstack-dev] [Neutron] Intermittent failures on unit tests

On 21 June 2016 at 08:41, Armando M. wrote: > Neutrinos, > > There's been a number of intermittent failures induced by the DNS > integration code that popped up lately. One has been reported in [1], > another showed up in [2]. I am in the progress of digging deeper to see >

Re: [openstack-dev] [neutron][SFC]

Hi all, I 'm still trying to integrate sfc project with devstack using [1] but the L2 agent is unable to chech status of br-int (see error bellow). I think that the error is not due to OpenFlow version negociation since I can execute the command "sudo ovs-ofctl dump-flows br-int -O OpenFlow13

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On 06/21/2016 08:42 AM, Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2016-06-21 08:00:50 -0400: >> On 06/21/2016 07:39 AM, Jay Pipes wrote: >>> On 06/21/2016 05:43 AM, Sylvain Bauza wrote: Le 21/06/2016 10:04, Chris Dent a écrit : > On Mon, 20 Jun 2016, Jay Pipes wrote:

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Excerpts from Sean Dague's message of 2016-06-21 09:10:00 -0400: > The amount of wsgi glue above Routes / Paste is pretty minimal (after > you get rid of all the extensions facilities). > > Templating and Session handling are things we don't need. We're not a > webapp, we're a REST service.

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

Excerpts from Sean Dague's message of 2016-06-21 08:00:50 -0400: > On 06/21/2016 07:39 AM, Jay Pipes wrote: > > On 06/21/2016 05:43 AM, Sylvain Bauza wrote: > >> Le 21/06/2016 10:04, Chris Dent a écrit : > >>> On Mon, 20 Jun 2016, Jay Pipes wrote: > >>> > Flask seems to be the most widely

[openstack-dev] [Tripleo] X509 Management

When deploying the overcloud with TLS, the current "no additional technology" approach is to use opensssl and self signed. While this works for a Proof of concept, it does not make sense if the users need to access the resources from remote systems. It seems to me that the undercloud, as the

Re: [openstack-dev] [nova] Virtuozzo (Compute) CI is incorrectly patching for resize support

15.06.2016 0:51, Matt Riedemann пишет: It was pointed out today in IRC that the Virtuozzo CI has been failing on this change for the libvirt imagebackend refactor: https://review.openstack.org/#/c/282580/ Diana was having a hard time sorting out the line numbers in the stack trace though

[openstack-dev] [all][oslo] pbr potential breaking change coming

A while back pbr had a feature that let projects pass "warnerror" through to Sphinx during documentation builds, causing any warnings in that build to be treated as an error and fail the build. This lets us avoid things like links to places that don't exist in the docs, bad but renderable rst,

Re: [openstack-dev] [all] Proposal: Architecture Working Group

On 20/06/16 19:27, Clint Byrum wrote: Excerpts from Doug Wiegley's message of 2016-06-20 10:40:56 -0600: So, it sounds like you’ve just described the job of the TC. It may sound like that, but the TC have repeatedly (and perhaps wisely) disclaimed that as part of their job. So any attempt to

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On Tue, Jun 21, 2016 at 08:00:50AM -0400, Sean Dague wrote: > > Keystone - custom WSGI with Routes / Paste > Keystone is moving toward Flask. I have an experimental patch that moves us in that direction. I'm in the process to rebasing and fixing it up since it's wildly out of date. -- David

Re: [openstack-dev] [all][oslo] pbr potential breaking change coming

Excerpts from Ihar Hrachyshka's message of 2016-06-21 15:40:45 +0200: > > > On 21 Jun 2016, at 15:01, Doug Hellmann wrote: > > > > A while back pbr had a feature that let projects pass "warnerror" > > through to Sphinx during documentation builds, causing any warnings in

[openstack-dev] [kolla] Need help from all core reviewers

Hey folks, We have a spec under review for Kolla + Kubernetes, which has been cooking for 6-8 weeks. The specification may have some gaps, but it gives a solid feeling to me atleast the work is achievable. Note specifications are point in time plans and are never revised in the repository.

Re: [openstack-dev] [TripleO] Consolidating TripleO validations with Browbeat validations

On Tue, Jun 21, 2016 at 12:41 PM, Tomas Sedovic wrote: > On 06/20/2016 06:37 PM, Joe Talerico wrote: >> >> Hello - It would seem there is a little bit of overlap with TripleO >> validations ( clapper validations ) and Browbeat *Checks*. I would >> like to see these two come

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On 06/21/2016 10:11 AM, Clint Byrum wrote: > Excerpts from Sean Dague's message of 2016-06-21 09:10:00 -0400: >> The amount of wsgi glue above Routes / Paste is pretty minimal (after >> you get rid of all the extensions facilities). >> >> Templating and Session handling are things we don't need.

Re: [openstack-dev] Version header for OpenStack microversion support

On 06/21/2016 10:27 AM, Sean Dague wrote: > On 06/21/2016 10:47 AM, Monty Taylor wrote: > >> >> I'll agree with Clint here, and give an example. >> >> When I talk to Nova and get a detail record for a server, Nova talks to >> Neutron and puts data that it receives into the addresses dict on the

Re: [openstack-dev] [Monasca] Locked (latched) alarms

Hi Witek, Thanks for the blueprint. We can review tomorrow if you would like. Personally, I like the term "locked". The alarm definition makes more sense (option 2). I don't think an operator will want to lock/latch an alarm sub-expression. The operator will want to lock/latch an entire alarm.

[openstack-dev] [stable] [manila] Stable check of openstack/manila failed

-Original Message- From: A mailing list for the OpenStack Stable Branch test reports. Reply: openstack-dev@lists.openstack.org Date: June 21, 2016 at 01:13:47 To: openstack-stable-ma...@lists.openstack.org

Re: [openstack-dev] Version header for OpenStack microversion support

On 06/21/2016 12:59 AM, Clint Byrum wrote: > Excerpts from Edward Leafe's message of 2016-06-20 20:41:56 -0500: >> On Jun 18, 2016, at 9:03 AM, Clint Byrum wrote: >> >>> Whatever API version is used behind the compute API is none of the user's >>> business. >> >> Actually, yeah,

Re: [openstack-dev] [all] Proposal: Architecture Working Group

On Mon, Jun 20, 2016 at 10:59 AM Clint Byrum wrote: > > As you should be, and we all must be. It's not going to happen if we > just dream it. That's kind of the point. Let's write down a design _for > the group that writes down designs_. > If I had any confidence that this

Re: [openstack-dev] [puppet] Action parameter missing in generated stonith fence manifests

Greetings Sofer, Thanks for your reply. I've went ahead and followed your instructions to file a bug here: https://bugs.launchpad.net/puppet-pacemaker/+bug/1594870 I'll keep a watch on it! Thanks for your help! Devon On Tue, Jun 21, 2016 at 9:00 AM, Sofer Athlan-Guyot

Re: [openstack-dev] [all] Proposal: Architecture Working Group

  -Original Message- From: Michael Krotscheck Reply: OpenStack Development Mailing List (not for usage questions) Date: June 21, 2016 at 10:18:25 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

On 06/21/2016 08:43 AM, Markus Zoeller wrote: A reminder that this will happen in ~2 weeks. Please note that you can spare bug reports if you leave a comment there which says one of these (case-sensitive flags): * CONFIRMED FOR: NEWTON * CONFIRMED FOR: MITAKA * CONFIRMED FOR: LIBERTY On

Re: [openstack-dev] Does nova-compute interact with nova Db?

Hi, nova-compute hasn't direct access to DB only scheduler, conductor and API can use it. See schema: http://docs.openstack.org/developer/nova/architecture.html. I think for your case you could write some script (ansible, puppet?) to collect data and nova-manage command to update DB. On Tue,

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On 06/21/2016 10:10 AM, Clint Byrum wrote: > Excerpts from Sean Dague's message of 2016-06-21 08:00:50 -0400: >> On 06/21/2016 07:39 AM, Jay Pipes wrote: >>> On 06/21/2016 05:43 AM, Sylvain Bauza wrote: Le 21/06/2016 10:04, Chris Dent a écrit : > On Mon, 20 Jun 2016, Jay Pipes wrote:

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

://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160621 > > Feel free to add more topics, and any outstanding bug and patch. > > See you tomorrow! > Thanks, > -- > Emilien Macchi -- Emilien Macchi _

Re: [openstack-dev] [nova] ability to set metadata on instances (but config drive is not updated)

On 06/21/2016 10:06 AM, Jay Faulkner wrote: > > > On 6/17/16 3:04 PM, Joshua Harlow wrote: >> Hi folks, >> >> I was noticing that its possible to do something like: >> >> $ nova meta josh-testr3 set "e=f" >> >> Then inside the VM I can do the following to eventually see that this >> changes

Re: [openstack-dev] Does nova-compute interact with nova Db?

On 06/21/2016 10:07 AM, KHAN, RAO ADNAN wrote: I want to collect an *extra_resource* info from compute node(s) and add it in to the compute_nodes table. I like to understand how nova-compute interacts with DB currently. nova-compute does not interact with the database directly. Only via the

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

[Non-specific to nova] I generated a list of which frameworks were in use in Mitaka - it's at the top of the blog post I reference below, so you don't have to dig into it too much to get the data. TL/DR: - falcon: 4 projects - custom + routes: 12 projects - pecan: 12 projects - flask: 2 projects

Re: [openstack-dev] Version header for OpenStack microversion support

On 06/21/2016 10:47 AM, Monty Taylor wrote: > > I'll agree with Clint here, and give an example. > > When I talk to Nova and get a detail record for a server, Nova talks to > Neutron and puts data that it receives into the addresses dict on the > server record. This is not the neutron data

Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration

Gal, Thanks for starting this ML. Since the work involves both team, I think it is a good idea to start by splitting the task first. Then, we can see which items go to which teams. Vikas, do you mind to update this ML once the task is spitted? Thanks in advance. Best regards, Hongbin From:

Re: [openstack-dev] [Tripleo] X509 Management

-Original Message- From: John Dennis Reply: OpenStack Development Mailing List (not for usage questions) Date: June 21, 2016 at 10:28:22 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Tripleo] X509 Management

On 06/21/2016 11:26 AM, John Dennis wrote: On 06/21/2016 10:55 AM, Ian Cordasco wrote: -Original Message- From: Adam Young Reply: OpenStack Development Mailing List (not for usage questions) Date: June 21, 2016 at 09:40:39 To:

Re: [openstack-dev] [Tripleo] X509 Management

-Original Message- From: Adam Young Reply: OpenStack Development Mailing List (not for usage questions) Date: June 21, 2016 at 09:40:39 To: OpenStack Development Mailing List Subject: 

Re: [openstack-dev] [nova] ability to set metadata on instances (but config drive is not updated)

On 6/17/16 3:04 PM, Joshua Harlow wrote: Hi folks, I was noticing that its possible to do something like: $ nova meta josh-testr3 set "e=f" Then inside the VM I can do the following to eventually see that this changes shows up in the instance metadata exposed at the following: $ curl -s

Re: [openstack-dev] [Tripleo] X509 Management

On 06/21/2016 10:55 AM, Ian Cordasco wrote: -Original Message- From: Adam Young Reply: OpenStack Development Mailing List (not for usage questions) Date: June 21, 2016 at 09:40:39 To: OpenStack Development Mailing List

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Hello Jay, Yes - the partition alignment is a problem: grub2 needs at least 63 blocks between the MBR and the first partition. Here for you the partition directly starts at block 1, therefore grub has no way to put its data on the disk. The root cause is, that all the partitioning tools I found

Re: [openstack-dev] [Neutron][LBaaS][Octavia]In amphora plugin_vip(), why cidr and gateway are required but not used?

Thank you the info Lubosz. On Fri, Jun 17, 2016 at 5:01 PM, Kosnik, Lubosz wrote: > Here is a bug for that - https://bugs.launchpad.net/octavia/+bug/1585804 > You’re more than welcome to fix this issue. > > Lubosz Kosnik > Cloud Software Engineer OSIC >

Re: [openstack-dev] [all] Proposal: Architecture Working Group

> On Jun 21, 2016, at 11:29 AM, Jay Pipes wrote: > > On 06/21/2016 12:53 PM, Doug Wiegley wrote: >>> On Jun 21, 2016, at 2:56 AM, Thierry Carrez >>> wrote: >>> Chris Dent wrote: On Mon, 20 Jun 2016, Doug Wiegley wrote: > So, it sounds like

Re: [openstack-dev] [all] Proposal: Architecture Working Group

> On Jun 21, 2016, at 2:56 AM, Thierry Carrez wrote: > > Chris Dent wrote: >> On Mon, 20 Jun 2016, Doug Wiegley wrote: >>> So, it sounds like you’ve just described the job of the TC. And they >>> have so far refused to define OpenStack, leading to a series of >>>

Re: [openstack-dev] [Neutron] Elevating context to remove subnets created by admin

On Tue, Jun 21, 2016 at 12:47 AM, Armando M. wrote: > It seems it may potentially limit the ability to describe ownership. > Virtually all Neutron models have it. Not sure I see the value in its > absence. I'm just saying that I don't see value in its presence. The value that

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Ian Cordasco's message of 2016-06-21 11:12:40 -0500: >   > > -Original Message- > From: Michael Krotscheck > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: June 21, 2016 at 10:18:25 >

Re: [openstack-dev] [all] Proposal: Architecture Working Group

On 06/21/2016 04:25 AM, Chris Dent wrote: However, I worry deeply that it could become astronauts with finger paints. Yes. This. I will happily take software design suggestions from people that demonstrate with code and benchmarks that their suggestion actually works outside of the

Re: [openstack-dev] [all] Proposal: Architecture Working Group

On 06/21/2016 12:53 PM, Doug Wiegley wrote: On Jun 21, 2016, at 2:56 AM, Thierry Carrez wrote: Chris Dent wrote: On Mon, 20 Jun 2016, Doug Wiegley wrote: So, it sounds like you’ve just described the job of the TC. And they have so far refused to define OpenStack,

Re: [openstack-dev] [nova] Placement API WSGI code -- let's just use flask

On Mon, 20 Jun 2016, Jay Pipes wrote: Flask seems to be the most widely used and known WSGI framework so for consistency's sake, I'm recommending we just use it and not rock this boat. There are more important things to get hung up on than this battle right now. That seems perfectly

Re: [openstack-dev] [Fuel] Nominate Artur Svechnikov to the fuel-web-core team

Congratulations, Arthur! Well done! On Tue, Jun 21, 2016 at 10:50 AM, Aleksey Kasatkin wrote: > Well, the agreement is reached. I've added Artur to fuel-web-core group. > > Let's continue discussion on time management questions if it will become an > issue. > > Artur,

Re: [openstack-dev] [all] Proposal: Architecture Working Group

On Mon, 20 Jun 2016, Doug Wiegley wrote: So, it sounds like you’ve just described the job of the TC. And they have so far refused to define OpenStack, leading to a series of derivative decisions that seem … inconsistent over time. Thanks for writing down what I was thinking. I agree that

Re: [openstack-dev] [nova] ability to set metadata on instances (but config drive is not updated)

Agreed, it appears supported right-now (whether intentional or not), So the question at that point is what can we do to make it better... I think we all agree that the config-drive probably shouldn't have the equivalent of the metadata service in it; because if the metadata service can change

[openstack-dev] [Neutron][networking-sfc] NO networking-sfc project IRC meetings on 6/23/2016 and 6/30/2016

Hi everyone, Since some of the project members are either in Summit/Conference or on vacation, we will not have project meetings on 6/23/2016 and 6/30/2016. Thanks, Cathy __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

> On Jun 20, 2016, at 6:56 AM, Doug Hellmann wrote: > > > I'm also, I think, edging away from the "we need to find a compromise" > camp into the "why is this turning into such a big deal" camp. How did > we get into a situation where the community has set a clear

[openstack-dev] Release naming for P and Q open for nominations

Hey everyone! It's time to pick a name for the P and Q releases. If you have a name you'd like us to vote on, please add it here: https://wiki.openstack.org/wiki/Release_Naming/P_Proposals https://wiki.openstack.org/wiki/Release_Naming/Q_Proposals The nominations will be open until 2016-06-28

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

"discuss" wrote on 06/17/2016 05:24:19 PM: > From: Cathy Zhang > To: Na Zhu > Cc: Srilatha Tangirala/San Francisco/IBM@IBMUS, "OpenStack > Development Mailing List \(not for usage questions\)"

[openstack-dev] Gerrit downtime on 1 July 2016 at 20:00 UTC

Hi everybody, On 1 July 2016 at 20:00 UTC Gerrit will be unavailable for approximately 120 minutes (2 hours) while we upgrade zuul.openstack.org and static.openstack.org to Ubuntu Trusty. During this time, running jobs will be stopped as both new servers for zuul.openstack.org and

Re: [openstack-dev] [Tripleo] X509 Management

On Tue, Jun 21, 2016 at 10:51 PM, Adam Young wrote: > On 06/21/2016 02:42 PM, Juan Antonio Osorio wrote: > > Adam, this is pretty much the proposal for TLS for the internal services > (which you were added already as a reviewer for the spec) >

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Jay Pipes's message of 2016-06-21 12:47:46 -0400: > On 06/21/2016 04:25 AM, Chris Dent wrote: > > However, I worry deeply that it could become astronauts with finger > > paints. > > Yes. This. > > I will happily take software design suggestions from people that > demonstrate with

Re: [openstack-dev] networking-sfc: unable to use SFC (ovs driver) with multiple networks

Hi MartinX, I sent you a reply on 6/14. Cathy -Original Message- From: Banszel, MartinX [mailto:martinx.bans...@intel.com] Sent: Thursday, June 16, 2016 4:49 AM To: 'openstack-dev@lists.openstack.org' Subject: [openstack-dev] networking-sfc: unable to use SFC (ovs driver) with

Re: [openstack-dev] [Tripleo] X509 Management

Adam, this is pretty much the proposal for TLS for the internal services (which you were added already as a reviewer for the spec) https://review.openstack.org/#/c/282307/ The services in the overcloud fetching their certificates via certmonger is actually work in progress, which you could review

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

Excerpts from Jay Pipes's message of 2016-06-21 14:20:07 -0400: > On 06/21/2016 02:01 PM, Andre Florath wrote: > > Hello Jay, > > > > Yes - the partition alignment is a problem: > > grub2 needs at least 63 blocks between the MBR and the first > > partition. Here for you the partition directly

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Jay Pipes's message of 2016-06-21 13:29:32 -0400: > On 06/21/2016 12:53 PM, Doug Wiegley wrote: > > Don’t get me wrong, I welcome this initiative. I find it mildly > > disconcerting that the folks that I thought we were electing to fill > > this role will instead be filled by others,

Re: [openstack-dev] [diskimage-builder] ERROR: embedding is not possible, but this is required for cross-disk install

On 06/21/2016 02:01 PM, Andre Florath wrote: Hello Jay, Yes - the partition alignment is a problem: grub2 needs at least 63 blocks between the MBR and the first partition. Here for you the partition directly starts at block 1, therefore grub has no way to put its data on the disk. The root

Re: [openstack-dev] [Neutron] Elevating context to remove subnets created by admin

> On 21 Jun 2016, at 08:47, Armando M. wrote: > > > > On 20 June 2016 at 18:41, Carl Baldwin wrote: > Somehow, this thread hid from me for a couple of weeks. I just > reviewed something relevant to this here [1]. It proposes adding > tenant id to

Re: [openstack-dev] [Tripleo] X509 Management

On 06/21/2016 02:42 PM, Juan Antonio Osorio wrote: Adam, this is pretty much the proposal for TLS for the internal services (which you were added already as a reviewer for the spec) https://review.openstack.org/#/c/282307/ The services in the overcloud fetching their certificates via

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

On 6/15/2016 1:11 AM, Angus Lees wrote: oslo.privsep change: https://review.openstack.org/#/c/329766/ And the nova change that uses it: https://review.openstack.org/#/c/329769 In particular I'm unsure if os-brick/os-vif is even loaded at this point in nova-compute main(). Does anyone know when

Re: [openstack-dev] [nova] ability to set metadata on instances (but config drive is not updated)

Excerpts from Joshua Harlow's message of 2016-06-21 15:12:09 -0700: > Agreed, it appears supported right-now (whether intentional or not), > > So the question at that point is what can we do to make it better... > > I think we all agree that the config-drive probably shouldn't have the >

  1   2   >