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

Cinder bugs list was far more manageable once this had been done. It is worth sharing the tool for this? I realise it's fairly trivial to write one, but some standardisation on the comment format etc seems valuable, particularly for Q/A folks who work between different projects. On 23 May 2016 at

Re: [openstack-dev] [openstack-operators][cinder] max_concurrent_builds in Cinder

On 24 May 2016 at 05:46, John Griffith wrote: > > ​Just curious about a couple things: Is this attempting to solve a > problem in the actual Cinder Volume Service or is this trying to solve > problems with backends that can't keep up and deliver resources under heavy > load? > I would posit tha

Re: [openstack-dev] [magnum][kuryr] Nested containers networking

Hi Hongbin, Thank you for starting this thread. The person that is going to work on this integration is Fawad (CC'ed) and hopefully others will help him (We have another person from Huawei that showed intrest in working on this). I think Fawad, given that he is the primary person working on this

[openstack-dev] [higgins] Should we rename "Higgins"?

Hi all, Unfortunately "higgins" is used by media server project on Launchpad and CI software on PYPI. Now, we use "python-higgins" for our project on Launchpad. IMO, we should rename project to prevent increasing points to patch. How about "Gatling"? It's only association from Magnum. It's not

[openstack-dev] [nova] [infra] resolving issues with Intel NFV CI

Hi all, There is an issue with jobs under Intel NFV CI not being registered. The issue is currently being investigated. ThirdPartySystems Wiki was updated. Updates to follow. Waldemar Znoinski -- Intel Research and Development Ireland

[openstack-dev] [oslo] Log spool in the context

Hi, I have a spec: https://review.openstack.org/227766 and implementation: https://review.openstack.org/316162 for adding a spooling logger to oslo.log. Neither is merged yet, reviews welcome. Looking at how I'd actually integrate this into Nova, most classes do: LOG = logging.getLogger(__na

[openstack-dev] [Nova] change console proxy URL for cells v2 ?

I am implementing the following spec and have encountered a problem related to the form of the console proxy URL provided to uses. https://specs.openstack.org/openstack/nova-specs/specs/newton/approved/convert-consoles-to-objects.html The spec changes the representation of the console auth toke

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

On 24.05.2016 09:34, Duncan Thomas wrote: > Cinder bugs list was far more manageable once this had been done. > > It is worth sharing the tool for this? I realise it's fairly trivial to > write one, but some standardisation on the comment format etc seems > valuable, particularly for Q/A folks who

[openstack-dev] [nova] Is verification of images in the image cache necessary?

During its periodic task, ImageCacheManager does a checksum of every image in the cache. It verifies this checksum against a previously stored value, or creates that value if it doesn't already exist.[1] Based on this information it generates a log message if the image is corrupt, but otherwise tak

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

Agenda: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Please add items if you want to guarantee time to talk about them. Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack

[openstack-dev] [fuel] release version numbers: let's use semvers

Hi, A number of Fuel components were previously tagged as "9.0". This isn't compatible with the semver scheme. Could we agree to switch to x.y.z going forward? Cheers, Thomas Goirand (zigo) __ OpenStack Development Mailing

Re: [openstack-dev] [Openstack-operators] [nova] Is verification of images in the image cache necessary?

On 24 May 2016 at 10:16, Matthew Booth wrote: > During its periodic task, ImageCacheManager does a checksum of every image > in the cache. It verifies this checksum against a previously stored value, > or creates that value if it doesn't already exist.[1] Based on this > information it generates a

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Chris Dent wrote: [...] I don't really know. I'm firmly in the camp that OpenStack needs to be smaller and more tightly focused if a unitary thing called OpenStack expects to be any good. So I'm curious about and interested in strategies for figuring out where the boundaries are. So that, of cou

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Morgan Fainberg wrote: [...] If we are accepting golang, I want it to be clearly documented that the expectation is it is used exclusively where there is a demonstrable case (such as with swift) and not a carte blanche to use it wherever-you-please. I want this to be a social contract looked at

[openstack-dev] update congress

Hi Tim and all, May I ask how to update the congress version with the Tokyo Hands on Lab environment? cause I use the command ＂openstack congress list version＂ it show the congress is 2013's version. The reason why I want to update it is that I write a demo driver, which I want to push data into

[openstack-dev] [Fuel] YAQL console for master node

Hi all, as you maybe know, new conditions for Fuel tasks were recently (in master and mitaka branches) introduced. Right after this I got several questions like 'hey, how can I check my new condition?' Answer could be 'use standard yaql console', but it hasn't have Fuel internal yaql functions whi

Re: [openstack-dev] [Openstack-operators] [nova] Is verification of images in the image cache necessary?

On Tue, May 24, 2016 at 11:06 AM, John Garbutt wrote: > On 24 May 2016 at 10:16, Matthew Booth wrote: > > During its periodic task, ImageCacheManager does a checksum of every > image > > in the cache. It verifies this checksum against a previously stored > value, > > or creates that value if it

[openstack-dev] [all][oslo_config] Improving Config Option Help Texts

Hi all, Based on the not yet merged spec of categorized config options [0] some project seems to have started improving the config option help texts. This is great but I noticed scary trend on clutter to be added on these sections. Now looking individual changes it does not look that bad at all in

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On Tue, 24 May 2016, Thierry Carrez wrote: Chris Dent wrote: So that, of course, leads back to the original question: Is OpenStack supposed to be a unitary. As a data point, since I heard that question rhetorically asked quite a few times over the past year... There is an old answer to that,

Re: [openstack-dev] [nova] Is verification of images in the image cache necessary?

On Tue, 24 May 2016, Matthew Booth wrote: I understand that corruption of bits on disks is a thing, but it's a thing for more than just the image cache. I feel that this is a problem much better solved at other layers, prime candidates being the block and filesystem layers. There are existing ro

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

+1 ttx. ("I'd prefer if we didn't have to special-case anyone") -- Dims On Tue, May 24, 2016 at 6:24 AM, Thierry Carrez wrote: > Morgan Fainberg wrote: >> >> [...] If we are accepting golang, I want it to be clearly >> documented that the expectation is it is used exclusively where there is

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On 24 May 2016 at 02:28, Gregory Haynes wrote: > On Mon, May 23, 2016, at 05:24 PM, Morgan Fainberg wrote: > > I really do not want to "special case" swift. It really doesn't go with > the spirit of inclusion. > > > I am not sure how inclusion is related to special casing. Inclusion here > implie

[openstack-dev] [Kuryr] - IRC Meeting time change

Hello Everyone, Just wanted to let you all know we changed our even biweekly IRC meeting time. It is now one hour earlier. The new meeting time is *every even Monday at 14:00 UTC in #openstack-meeting-4* You can see the changing patch here [1] Thanks Gal. [1] https://review.openstack.org/#/c/31

[openstack-dev] [ironic][neutron] bonding?

Hi, There's rumors floating around about Neutron having a bonding model in the near future. Are there any solid plans for that? For context, as part of the multitenant networking work, ironic has a portgroup concept proposed, where operators can configure bonding for NICs in a baremetal machine.

Re: [openstack-dev] [Openstack-operators] [nova] Is verification of images in the image cache necessary?

Hi John and Matt, I actually have a spec and patch up for review addressing some of what you’re referring to below. https://review.openstack.org/#/c/314222/ https://review.openstack.org/#/c/312210/ I think you’re quite right that the existing ImageCacheManager code serves little purpose. What

[openstack-dev] [Openstack-dev] scaling nova kvm and neutron l3-ha and ml2+openvswitch

Hello, (I didn't have any luck with this question on the openstack-operators list so I'm throwing it out here to see if I can catch anyone, according to Assaf he knew a couple of you devs running a similar environment, if not feel free to do what you please with this email hehe) I'm gonna give it

Re: [openstack-dev] [fuel] release version numbers: let's use semvers

Hey Zigo, In Python community there's a PEP-440 [1] that defines a versioning scheme. The thing you should know is, the PEP __is not__ compatible with semver, and it's totally fine to have two components version. So I don't think we should force version changes from two-components to three-com

Re: [openstack-dev] [Infra][Cinder] Nominating Zadara Storage VPSA CI for voting permissions

On Tue, May 24, 2016 at 09:47:23AM +0300, Shlomi Avihou wrote: > Hello, > > > > I’d like to nominate Zadara Storage VPSA CI system for voting permissions > in the Cinder program. > > The CI system has been posting comments (non-voting) for the past 24 days. > > > > *Third Party system info:

Re: [openstack-dev] [Openstack-dev] scaling nova kvm and neutron l3-ha and ml2+openvswitch

Hi! Recently I performed scale testing of Neutron L3 HA Liberty. Test plan and test results can be found http://docs.openstack.org/developer/performance-docs/index.html. On Tue, May 24, 2016 at 3:21 PM, Tobias Urdin wrote: > Hello, > > (I didn't have any luck with this question on the openstack

Re: [openstack-dev] [nova] Suggest to not deprecate os-migrations API

On 05/23/2016 10:16 PM, Zhenyu Zheng wrote: > Hi All, > > According > to > https://github.com/openstack/nova/blob/master/releasenotes/notes/os-migrations-ef225e5b309d5497.yaml > , we are going to deprecate the old os-migrations API, and two new APIs: > /servers/{server uuid}/migrations and /serve

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

On Tue, May 24, 2016 at 11:00:35AM +0200, Markus Zoeller wrote: > On 24.05.2016 09:34, Duncan Thomas wrote: > > Cinder bugs list was far more manageable once this had been done. > > > > It is worth sharing the tool for this? I realise it's fairly trivial to > > write one, but some standardisation

[openstack-dev] [nova] Stable disk device instance rescue reviews for libvirt and possible implementation by other virt drivers

Hello all, https://review.openstack.org/#/q/topic:bp/virt-rescue-stable-disk-devices I've been aimlessly pushing my patches around for this spec for a while now and would really appreciate reviews from the community. Tempest and devstack patches are also included in the above topic, reviews would

[openstack-dev] Plans to converge on one ldap client?

Hi All, Are there any plans to converge on one ldap client across projects? Some projects have moved to ldap3 and others are using pyldap (both are in global requirements). The issue we're running into in Ubuntu is that we can only have one ldap client in Ubuntu main, while the others will live

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

On Tue, May 24, 2016 at 1:34 AM, Duncan Thomas wrote: > Cinder bugs list was far more manageable once this had been done. > > It is worth sharing the tool for this? I realise it's fairly trivial to > write one, but some standardisation on the comment format etc seems > valuable, particularly for

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Excerpts from Geoff O'Callaghan's message of 2016-05-24 15:31:28 +1000: > > > On 24 May 2016, at 3:13 PM, Clint Byrum wrote: > > > > > [snip] > > > those other needs. Grab a python developer, land some code, and your > > feature is there. > > s/python/whateverlanguage/ > But that's just the

Re: [openstack-dev] [higgins] Should we rename "Higgins"?

Before considering a project rename.m, I suggest you seek guidance from the OpenStack technical committee, and/or the OpenStack-infra team. There is probably a simple workaround to the concern voiced below. -- Adrian > On May 24, 2016, at 1:37 AM, Shuu Mutou wrote: > > Hi all, > > Unfortunat

Re: [openstack-dev] [Fuel] YAQL console for master node

Hi, thank you Stas, long awaited tool :) Using it right now on the latest Fuel-10.0, very helpful and saves a lot of time (switching between nodes to test yaql for different roles is super cool). Regards, Alex On Tue, May 24, 2016 at 12:50 PM, Stanislaw Bogatkin wrote: > Hi all, > > as you ma

Re: [openstack-dev] [openstack-operators][cinder] max_concurrent_builds in Cinder

On 23/05, Ivan Kolodyazhny wrote: > Hi developers and operators, > I would like to get any feedback from you about my idea before I'll start > work on spec. > > In Nova, we've got max_concurrent_builds option [1] to set 'Maximum number > of instance builds to run concurrently' per each compute. Th

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On 23/05/16 21:57 +0100, Chris Dent wrote: [snip] So, yet another way to frame the original question (in a loaded way) may be: Are we trying to come up with a way of defining the community that lets us carry on doing what we've been doing, haphazardly, or are we trying to get the process of def

[openstack-dev] [aodh] Tempest gate not working

Hi, So it turns out we tried (especially Ryota) to add Tempest support via https://review.openstack.org/#/c/303921/ for Aodh's gate, but it does not actually run Tempest. Otherwise, we would have notice something wrong in https://review.openstack.org/#/c/318052/. As EmilienM noticed in Puppet Aod

Re: [openstack-dev] [nova] Stable disk device instance rescue reviews for libvirt and possible implementation by other virt drivers

Hi Lee, I'll try to get to these reviews later this afternoon. Thanks for your patience. Best, -jay On 05/24/2016 08:53 AM, Lee Yarwood wrote: Hello all, https://review.openstack.org/#/q/topic:bp/virt-rescue-stable-disk-devices I've been aimlessly pushing my patches around for this spec fo

Re: [openstack-dev] [Openstack-operators] [nova] Is verification of images in the image cache necessary?

On Tue, May 24, 2016 at 1:15 PM, Fichter, Dane G. wrote: > Hi John and Matt, > > I actually have a spec and patch up for review addressing some of what > you’re referring to below. > > https://review.openstack.org/#/c/314222/ > https://review.openstack.org/#/c/312210/ > > I think you’re quite rig

Re: [openstack-dev] [openstack-operators][cinder] max_concurrent_builds in Cinder

On 05/24/2016 04:38 PM, Gorka Eguileor wrote: > On 23/05, Ivan Kolodyazhny wrote: >> Hi developers and operators, >> I would like to get any feedback from you about my idea before I'll start >> work on spec. >> >> In Nova, we've got max_concurrent_builds option [1] to set 'Maximum number >> of in

Re: [openstack-dev] [glance] [defcore] [interop] Proposal for a virtual sync dedicated to Import Refactor May 26th

+1 > On May 23, 2016, at 8:25 PM, Mike Perez wrote: > >> On 18:00 May 20, Nikhil Komawar wrote: >> Hello all, >> >> >> I want to propose having a dedicated virtual sync next week Thursday May >> 26th at 1500UTC for one hour on the Import Refactor work [1] ongoing in >> Glance. We are making a

Re: [openstack-dev] Plans to converge on one ldap client?

On Tue, May 24, 2016 at 5:53 AM, Corey Bryant wrote: > Hi All, > > Are there any plans to converge on one ldap client across projects? Some > projects have moved to ldap3 and others are using pyldap (both are in > global requirements). > > The issue we're running into in Ubuntu is that we can on

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On Tue, May 24, 2016 at 8:20 AM, Flavio Percoco wrote: > > So, just to make sure I'm making myself clear, I believe we should go with > option #2 in Thierry's comment from May 23 11:3 on this[0] review. While > I'm not > entirely opposed to #1 I think #2 is better for us at this point in time. > H

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

> On 17 May 2016, at 13:07, Ihar Hrachyshka wrote: > > Hi stable-maint-core and all, > > I would like to propose Brian for neutron specific stable team. > > His stats for neutron stable branches are (last 120 days): > > mitaka: 19 reviews; liberty: 68 reviews (3rd place in the top); kilo: 16

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

The incorporation of tooz and Neutron is being discussed as part of https://bugs.launchpad.net/neutron/+bug/1552680 as an RFE for Newton. Hopefully I'll have some news to break in on this matter in the upcoming days (and if I do I'll update on the launchpad to eliminate duplicity). On Tue, May 24,

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On 05/24/2016 11:13 AM, Dean Troyer wrote: > On Tue, May 24, 2016 at 8:20 AM, Flavio Percoco > wrote: > > So, just to make sure I'm making myself clear, I believe we should > go with > option #2 in Thierry's comment from May 23 11:3 on this[0] review. > Wh

Re: [openstack-dev] [fuel] release version numbers: let's use semvers

The only thing I would like to mention here is that scripts for making automatic releases on PyPi using OpenStack Infra won’t work, if the version is not formatted according to semver. - romcheg > 24 трав. 2016 р. о 14:34 Igor Kalnitsky написав(ла): > > Hey Zigo, > > In Python community ther

Re: [openstack-dev] [Openstack-operators] [nova] Is verification of images in the image cache necessary?

> I like the idea of checking the md5 matches before each boot, as it > mirrors the check we do after downloading from glance. Its possible > thats very unlikely to spot anything that shouldn't already be worried > about by something else. It may just be my love of symmetry that makes > me like tha

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

On Mon, May 23, 2016 at 1:24 PM, Emilien Macchi wrote: > Hi Puppeteers! > > We'll have our weekly meeting tomorrow at 3pm UTC on > #openstack-meeting-4. > > Here's a first agenda: > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160524 > >

Re: [openstack-dev] Plans to converge on one ldap client?

On Tue, May 24, 2016 at 11:11 AM, Morgan Fainberg wrote: > > > On Tue, May 24, 2016 at 5:53 AM, Corey Bryant > wrote: > >> Hi All, >> >> Are there any plans to converge on one ldap client across projects? Some >> projects have moved to ldap3 and others are using pyldap (both are in >> global re

Re: [openstack-dev] [ironic][nova][horizon] Serial console support for ironic instances

Hi, > I'm working with Tien who is a submitter of one[1] of console specs. > I joined the console session in Austin. > > In the session, we got the following consensus. > - focus on serial console in Newton > - use nova-serial proxy as is > > We also got some requirements[2] for this feature in th

[openstack-dev] [kolla][security] Finishing the job on threat analysis for Kolla

Rob and Doug, At Summit we had 4 hours of highly productive work producing a list of "things" that can be "threatened". We have about 4 or 5 common patterns where we follow the principle of least privilege. On Friday of Summit we produced a list of all the things (in this case deployed contai

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

OpenStack is more then the sum of its various pieces. Often features need to cross more then one project. Cross project work is already extremely hard without having to change languages between. Language change should be done very carefully and deliberately. Thanks, Kevin _

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

On 05/24/2016 11:17 AM, Ihar Hrachyshka wrote: On 17 May 2016, at 13:07, Ihar Hrachyshka wrote: Hi stable-maint-core and all, I would like to propose Brian for neutron specific stable team. His stats for neutron stable branches are (last 120 days): mitaka: 19 reviews; liberty: 68 reviews (

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On 05/24/2016 06:19 AM, Thierry Carrez wrote: Chris Dent wrote: [...] I don't really know. I'm firmly in the camp that OpenStack needs to be smaller and more tightly focused if a unitary thing called OpenStack expects to be any good. So I'm curious about and interested in strategies for figuring

Re: [openstack-dev] [Openstack-operators] [nova] Is verification of images in the image cache necessary?

On 05/24/2016 11:54 AM, Dan Smith wrote: >> I like the idea of checking the md5 matches before each boot, as it >> mirrors the check we do after downloading from glance. Its possible >> thats very unlikely to spot anything that shouldn't already be worried >> about by something else. It may just be

Re: [openstack-dev] [nova] [infra] resolving issues with Intel NFV CI

The issue is now resolved. Apparently the job wasn't registered with gearman server as there weren't any slaves available in Jenkins to run it at the time of zuul restart (as some old nodepool nodes were left over and no new VMs were spawned). From: Znoinski, Waldemar [mailto:waldemar.znoin..

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

Excerpts from Markus Zoeller's message of 2016-05-24 11:00:35 +0200: > On 24.05.2016 09:34, Duncan Thomas wrote: > > Cinder bugs list was far more manageable once this had been done. > > > > It is worth sharing the tool for this? I realise it's fairly trivial to > > write one, but some standardisa

Re: [openstack-dev] [oslo] Log spool in the context

Excerpts from Alexis Lee's message of 2016-05-24 09:34:36 +0100: > Hi, > > I have a spec: https://review.openstack.org/227766 > and implementation: https://review.openstack.org/316162 > for adding a spooling logger to oslo.log. Neither is merged yet, reviews > welcome. > > Looking at how I'd actu

[openstack-dev] Summit evolution online town halls

Hi everyone, You might have seen the FAQ we posted last week about the continuing work on evolving the format and structure of the Summits: http://www.openstack.org/blog/2016/05/faq-evolving-the-openstack-design-summit/ I wanted to send a reminder note out to highlight that Thierry and I will

Re: [openstack-dev] [glance] [defcore] [interop] Proposal for a virtual sync dedicated to Import Refactor May 26th

+1 On 5/24/16, 11:11 AM, "Chris Hoge" wrote: >+1 > >> On May 23, 2016, at 8:25 PM, Mike Perez wrote: >> >>> On 18:00 May 20, Nikhil Komawar wrote: >>> Hello all, >>> >>> >>> I want to propose having a dedicated virtual sync next week Thursday >>>May >>> 26th at 1500UTC for one hour on the Im

Re: [openstack-dev] Plans to converge on one ldap client?

On Tue, May 24, 2016 at 8:55 AM, Corey Bryant wrote: > > > On Tue, May 24, 2016 at 11:11 AM, Morgan Fainberg < > morgan.fainb...@gmail.com> wrote: > >> >> >> On Tue, May 24, 2016 at 5:53 AM, Corey Bryant > > wrote: >> >>> Hi All, >>> >>> Are there any plans to converge on one ldap client across p

[openstack-dev] Fw: [glance] [defcore] [interop] Proposal for a virtual sync dedicated to Import Refactor May 26th

+1 - Catheine Diep - Forwarded by Catherine Cuong Diep/San Jose/IBM on 05/24/2016 10:31 AM - From: Brian Rosmaita To: "OpenStack Development Mailing List (not for usage questions)" Date: 05/24/2016 10:30 AM Subject:Re: [openstack-dev] [glance] [defcore] [int

Re: [openstack-dev] Plans to converge on one ldap client?

On Tue, May 24, 2016 at 1:23 PM, Morgan Fainberg wrote: > > > On Tue, May 24, 2016 at 8:55 AM, Corey Bryant > wrote: > >> >> >> On Tue, May 24, 2016 at 11:11 AM, Morgan Fainberg < >> morgan.fainb...@gmail.com> wrote: >> >>> >>> >>> On Tue, May 24, 2016 at 5:53 AM, Corey Bryant < >>> corey.bry...

[openstack-dev] Fwd: keystone federation user story

Colleagues, here is an actual use case for shadow users assignments, let's discuss possible solutions: all suggestions are appreciated. -- Forwarded message -- From: Andrey Grebennikov Date: Tue, May 24, 2016 at 9:43 AM Subject: keystone federation user story To: Alexander Makaro

[openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

The team working on live migration testing started with an experimental job on Ubuntu 16.04 to try to be using the latest and greatest libvirt + qemu under the assumption that a set of issues we were seeing are solved. The short answer is, it doesn't look like this is going to work. We run tests o

Re: [openstack-dev] [all][oslo_config] Improving Config Option Help Texts

-Original Message- From: Erno Kuvaja Reply: OpenStack Development Mailing List (not for usage questions) Date: May 24, 2016 at 06:06:14 To: OpenStack Development Mailing List (not for usage questions) Subject:  [openstack-dev] [all][oslo_config] Improving Config Option Help Texts > Hi a

[openstack-dev] [ironic] weekly sub team status report

Hi, We are rambunctious to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 16 May 2016) - Ironic: 192 bugs (+2) + 178 wishlist items (+1). 0 new, 138 in progress (+4)

Re: [openstack-dev] [oslo] Log spool in the context

On 05/24/2016 01:18 PM, Doug Hellmann wrote: > Excerpts from Alexis Lee's message of 2016-05-24 09:34:36 +0100: >> Hi, >> >> I have a spec: https://review.openstack.org/227766 >> and implementation: https://review.openstack.org/316162 >> for adding a spooling logger to oslo.log. Neither is merged y

Re: [openstack-dev] [ironic] usage of ironic-lib

Thanks for the feedback everyone. Lucas has submitted a patch to ironic-lib¹s README to clarify this: https://review.openstack.org/#/c/319251/. --ruby On 2016-05-20, 8:46 AM, "Jim Rollenhagen" wrote: >On Thu, May 19, 2016 at 01:21:35PM -0700, Devananda van der Veen wrote: >> On 05/16/2016 07:

[openstack-dev] [keystone] New Core Reviewer (sent on behalf of Steve Martinelli)

I want to welcome Rodrigo Duarte (rodrigods) to the keystone core team. Rodrigo has been a consistent contributor to keystone and has been instrumental in the federation implementations. Over the last cycle he has shown an understanding of the code base and contributed quality reviews. I am super

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

-Original Message- From: Joshua Harlow Reply: OpenStack Development Mailing List (not for usage questions) Date: May 23, 2016 at 15:23:32 To: OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack" > Sean

Re: [openstack-dev] [oslo] Log spool in the context

Excerpts from Sean Dague's message of 2016-05-24 14:16:13 -0400: > On 05/24/2016 01:18 PM, Doug Hellmann wrote: > > Excerpts from Alexis Lee's message of 2016-05-24 09:34:36 +0100: > >> Hi, > >> > >> I have a spec: https://review.openstack.org/227766 > >> and implementation: https://review.openstac

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Ok, probably should be chopped out of the oslo lib list then ;) I'll do that, since it seems to be really not the right name for what it is :) Ian Cordasco wrote: -Original Message- From: Joshua Harlow Reply: OpenStack Development Mailing List (not for usage questions) Date: May 23,

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

On 12:24 May 24, Thierry Carrez wrote: > Morgan Fainberg wrote: > >[...] If we are accepting golang, I want it to be clearly > >documented that the expectation is it is used exclusively where there is > >a demonstrable case (such as with swift) and not a carte blanche to use > >it wherever-you-ple

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

-Original Message- From: Jay Pipes Reply: OpenStack Development Mailing List (not for usage questions) Date: May 24, 2016 at 11:35:42 To: openstack-dev@lists.openstack.org Subject:  Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack" > On 05/24/2016 06:19 AM, Thierry Carre

Re: [openstack-dev] [ironic][neutron] bonding?

On 24 May 2016 at 04:51, Jim Rollenhagen wrote: > Hi, > > There's rumors floating around about Neutron having a bonding model in > the near future. Are there any solid plans for that? > Who spreads these rumors :)? To the best of my knowledge I have not seen any RFE proposed recently along thes

Re: [openstack-dev] [all][oslo_config] Improving Config Option Help Texts

+1 to what Ian said. We had an Ops session at the Austin summit on this and we didn't hear any concerns about the clutter from what I can recall. Some notes from that session are here [0]. May be the clutter is not a problem after all? At least, not yet. If it does become a problem down the line

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

Frankly, this is one of the major negatives we've felt from the Big Tent idea... OpenStack use to be more of a product then it is now. When there were common problems to be solved, there was pressure applied to solve them in a way everyone (OpenStack Project, OpenStack Users, and Openstack Opera

Re: [openstack-dev] [Mistral][Zaqar][Ceilometer][Searchlight] Triggering Mistral workflows from Zaqar messages

On 22/05/16 22:38, Lingxian Kong wrote: Hi, Zane, I think you must be interested in this: https://review.openstack.org/#/c/308664/ Oh! Yes that is very interesting. I'm glad that other people are thinking about these kinds of problems also. My blueprint has a different focus, in that it's mo

Re: [openstack-dev] [ironic][neutron] bonding?

The only thing I am remotely aware of that is relevant is: https://bugs.launchpad.net/bugs/1558626 But that's really just in one agent. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsu

Re: [openstack-dev] [PTLs][all][mentoring] Mentors needed in specific technical areas

Hi Emily, I'm the Nova Mentoring Czar and we have a Wiki page with a list of projects that would be good for new contributors: https://wiki.openstack.org/wiki/Nova/Mentoring For Nova, I'd encourage potential contributors to get involved with a specific project so that mentoring can happen organic

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

> On May 24, 2016, at 12:09 PM, Mike Perez wrote: > > On 12:24 May 24, Thierry Carrez wrote: >> Morgan Fainberg wrote: >>> [...] If we are accepting golang, I want it to be clearly >>> documented that the expectation is it is used exclusively where there is >>> a demonstrable case (such as with

Re: [openstack-dev] [all][oslo_config] Improving Config Option Help Texts

On 24 May 2016 at 19:03, Ian Cordasco wrote: > -Original Message- > From: Erno Kuvaja > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: May 24, 2016 at 06:06:14 > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev]

Re: [openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer

From: Steven Dake mailto:std...@cisco.com>> Reply-To: "openstack-dev@lists.openstack.org" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, May 17, 2016 at 12:00 PM To: "openstack-dev@lists.openstack.org"

[openstack-dev] [vitrage] Vitrage meeting on May 25 - SKIPPED

Hi, Vitrage weekly meeting on May 25 will be skipped, as many Vitrage developers won't be able to attend. We will meet next week as usual. Thanks, Ifat. __ OpenStack Development Mailing List (not for usage questions) Unsu

Re: [openstack-dev] update congress

Hi Yue, That version of Congress definitely doesn't have the Push driver. The Push driver code was implemented only in the latest release (Mitaka). Here are the upgrade instructions. They SHOULD work, but let us know if you run into problems, both so we can help you and so we can correct the in

[openstack-dev] [higgins] Continued discussion from the last team meeting

Hi all, At the last team meeting, we tried to define the scope of the Higgins project. In general, we agreed to focus on the following features as an initial start: * Build a container abstraction and use docker as the first implementation. * Focus on basic container operations

Re: [openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer

Thanks guys, it's a privilege to be part of team. :) 2016-05-24 17:02 GMT-03:00 Steven Dake (stdake) : > From: Steven Dake > Reply-To: "openstack-dev@lists.openstack.org" < > openstack-dev@lists.openstack.org> > Date: Tuesday, May 17, 2016 at 12:00 PM > To: "openstack-dev@lists.openstack.org" >

[openstack-dev] [nova][neutron][cloud-init] Questions around 'network_data.json'

Hi there all, I am working through code/refactoring in cloud-init to enable translation of the network_data.json file[1] provided by openstack (via nova via neutron?) into the equivalent sysconfig files (ubuntu files should already *mostly* work and systemd files are underway as well). Code

Re: [openstack-dev] [nova] Xvisor support

On Tue, May 24, 2016 at 11:42 PM, Muneeb Ahmad wrote: > If not, can I add it's support? any ideas how can I do that? > > On Sat, May 21, 2016 at 10:23 PM, Muneeb Ahmad > wrote: > >> Hey guys, >> >> Does OpenStack support Xvisor? >> > So, given I'd never heard of xvisor I think we can say that no

Re: [openstack-dev] [nova][neutron][cloud-init] Questions around 'network_data.json'

I think there is an implementation error. The spec mentions that link type can be "vif", "phy" or (future) "bond". Nova passes the "raw" Neutron VIF type instead. IMO, "bridge" should be "vif" as per spec. -- Mathieu On Tue, May 24, 2016 at 5:20 PM, Joshua Harlow wrote: > Hi there all, > > I am

Re: [openstack-dev] [nova][neutron][cloud-init] Questions around 'network_data.json'

On Tue, May 24, 2016 at 4:20 PM, Joshua Harlow wrote: > Hi there all, > > I am working through code/refactoring in cloud-init to enable translation > of the network_data.json file[1] provided by openstack (via nova via > neutron?) into the equivalent sysconfig files (ubuntu files should already >

Re: [openstack-dev] [PTLs][all][mentoring] Mentors needed in specific technical areas

On 12:54 May 24, Augustina Ragwitz wrote: > Hi Emily, > > I'm the Nova Mentoring Czar and we have a Wiki page with a list of > projects that would be good for new contributors: > https://wiki.openstack.org/wiki/Nova/Mentoring > > For Nova, I'd encourage potential contributors to get involved with

[openstack-dev] [magnum] Need helps to implement the full baremetals support

Hi all, One of the most important feature that Magnum team wants to deliver in Newton is the full baremetal support. There is a blueprint [1] created for that and the blueprint was marked as "essential" (that is the highest priority). Spyros is the owner of the blueprint and he is looking for h

[openstack-dev] [new][oslo] oslo.context 2.4.0 release (newton)

We are stoked to announce the release of: oslo.context 2.4.0: Oslo Context library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.context With package available at: https://pypi.python.org/pypi/oslo.context Pl

[openstack-dev] [new][oslo] oslo.cache 1.8.0 release (newton)

We are gleeful to announce the release of: oslo.cache 1.8.0: Cache storage for Openstack projects. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.cache With package available at: https://pypi.python.org/pypi/os

  1   2   >