Re: [openstack-dev] [mistral] Promoting Dougal Matthews to the core team

Ok, thank you all! Dougal, welcome to the core team! I’m hoping for fruitful collaboration with you :) Renat Akhmerov @Nokia > On 8 Nov 2016, at 17:18, Anastasia Kuznetsova > wrote: > > +1 from my side! > > On Tue, Nov 8, 2016 at 11:34 AM, Gershenzon, Michal

[openstack-dev] [Horizon] Meeting at 20:00 UTC this Wednesday, 9nd November

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 9nd November in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon Anyone is welcome to to add agenda items and everyone interested in Horizon is encouraged to

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On Tue, Nov 8, 2016 at 2:27 AM, Thierry Carrez wrote: > Ash wrote: > > [...] > > Here's another take on the situation. If there are people who genuinely > > wish to see a CI pipeline that can support something like Go, perhaps > > you can establish a prerequisite of

Re: [openstack-dev] [Magnum] New Core Reviewers

+1 for both. -Original Message- From: Adrian Otto [mailto:adrian.o...@rackspace.com] Sent: Tuesday, November 8, 2016 12:36 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Magnum] New Core Reviewers Magnum

Re: [openstack-dev] [nova][neutron] When are subnets needed on a network to create ports?

On 8 November 2016 at 18:35, Matt Riedemann wrote: > I've been looking at this nova bug: > > https://bugs.launchpad.net/nova/+bug/1637118 > > And the neutronv2 API code in nova and need some help from the neutron > team on how this should actually work. > If I am not

Re: [openstack-dev] [nova] cells v2 ocata summit sessions recap

On 11/8/2016 7:47 PM, melanie witt wrote: I think the only resources that are unclear as to whether they are in the API database are things like cores, ram, etc and I thought these will end up being represented in the inventories or allocations table once the resource providers work progresses

[openstack-dev] [nova][neutron] When are subnets needed on a network to create ports?

I've been looking at this nova bug: https://bugs.launchpad.net/nova/+bug/1637118 And the neutronv2 API code in nova and need some help from the neutron team on how this should actually work. The validation code that runs from nova-api when creating a server checks the requested/available

Re: [openstack-dev] [nova] cells v2 ocata summit sessions recap

On Tue, 8 Nov 2016 14:25:08 -0600, Matt Riedemann wrote: While talking about that in the session, there was some brainstorming on doing limit checks differently in the API. Basically, do away with reservations, do a quick DB query to check quota before an operation begins, and if it's OK go

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

On 11/8/2016 7:14 PM, Adrian Turjak wrote: On 09/11/16 11:12, Gage Hugo wrote: This spec was discussed at the keystone meeting today and during the conversation that continued afterwards, an idea of using the keystone configuration to set a list of keys was mentioned. The idea is that a

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

On 09/11/16 11:12, Gage Hugo wrote: > This spec was discussed at the keystone meeting today and during the > conversation that continued afterwards, an idea of using the keystone > configuration to set a list of keys was mentioned. > > The idea is that a cloud admin could define a list of keys

[openstack-dev] [new][horizon] django_openstack_auth 2.4.2 release (newton)

We are tickled pink to announce the release of: django_openstack_auth 2.4.2: Django authentication backend for use with OpenStack Identity This release is part of the newton stable release series. The source is available from: http://git.openstack.org/cgit/openstack/django_openstack_auth/

[openstack-dev] [Zun] Zun PTL election

Hi all, As discussed at the last team meeting, the Zun team will have a PTL election. Please note the following: * The electorate for this election are the Foundation individual members that are also committers for one of the Zun project teams repositories (openstack/zun,

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

On 11/8/2016 4:12 PM, Gage Hugo wrote: This spec was discussed at the keystone meeting today and during the conversation that continued afterwards, an idea of using the keystone configuration to set a list of keys was mentioned. The idea is that a cloud admin could define a list of keys that

[openstack-dev] [neutron] Weekly neutron-lib meeting canceled

See https://review.openstack.org/395034 We now have a slot in the main neutron project meeting. If we do need extra meeting time for neutron-lib we can set up something based on who wants to attend and when. __ OpenStack

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

On 04/11/16 08:15 PM, Steve Martinelli wrote: > > We have somewhat had support for this, we have an "extras" column > defined in our database schema, whatever a user puts in a request that > doesn't match up with our API, those key-values are dumped into the > "extras" column. It's not a

Re: [openstack-dev] [all] important changes to pep8 python jobs

On Tue, Nov 08, 2016 at 02:58:38PM -0500, Paul Belanger wrote: > On Thu, Nov 03, 2016 at 12:29:09PM -0400, Paul Belanger wrote: > > Greetings, > > > > We (openstack-infra) are proposing a change to the current pep8[1] job for > > python jobs, and would like to bring your attention to it. > > > >

Re: [openstack-dev] [openstack-infra] Please add a initial core member to meteos-core.

Hi Clark. > Done. Let us know if you have any issues, concerns, or questions. Thank you for your help. Regards, Hiroyuki Hiroyuki Eguchi -Original Message- From: Clark Boylan [mailto:cboy...@sapwetik.org] Sent: Wednesday, November 09, 2016 3:12 AM To:

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

This spec was discussed at the keystone meeting today and during the conversation that continued afterwards, an idea of using the keystone configuration to set a list of keys was mentioned. The idea is that a cloud admin could define a list of keys that they need for their setup within keystone's

[openstack-dev] [Horizon] [Keystone] Inaugural weekly cross-project meeting summary

Hi folks, Today we had the first of what will be a regular cross-project meeting series for Horizon and Keystone developers[1]. It was a very productive meeting, and we resolved to continue to keep our ongoing notes and status summaries in the etherpad[2] while still ensuring that BPs or bugs

Re: [openstack-dev] [requirements][kolla][security] pycrypto vs cryptography

Hey Steve, All of the credential generation is optional right? I mean, as far as kolla is concerned - it doesn't *need* to generate the passwords... If /etc/kolla/passwords.yml is created outside of kolla-genpwd, then kolla isn't creating any credentials itself and the algorithm, entropy and

Re: [openstack-dev] [requirements][kolla][security] pycrypto vs cryptography

Ok, Pavo has told me he has exceptions in place for everything related to Kolla. He says as long as we don’t use MD5, he is good to go for a 232 node deploy with more to follow (assuming Kolla works out of the box at that scale - we have only tested 123 node scale). We do some basic PRNG to

[openstack-dev] Anyone want to meetup at KubeCon?

We have been developing a keystone authz webhook for easy integration. If anyone is interested we can look at open-sourcing it Stephen McQuaid Sr. Software Engineer | Kubernetes & Openstack GoDaddy M: 484.727.8383 | O: 669.600.5852 smcqu...@godaddy.com

Re: [openstack-dev] [requirements][kolla][security] pycrypto vs cryptography

Excerpts from Ian Cordasco's message of 2016-11-08 16:11:26 -0500: > Can I ask why FIPS compliance is a requirement for Kolla? This seems > like an odd request for a deployment project. > Guessing it's for the modules that need to communicate securely with OpenStack itself.

Re: [openstack-dev] [kolla][release] Version numbers for kolla-ansible repository.

Thanks Jeremy. That is a hugely helpful piece of advice. I will include a link to your email to make sure I’m doing it correctly when I split the repo. Regards, -steve On 11/8/16, 8:24 AM, "Jeremy Stanley" wrote: >On 2016-11-08 19:07:07 +0530 (+0530), Swapnil

Re: [openstack-dev] [kolla][release] Version numbers for kolla-ansible repository.

On 11/8/16, 9:08 AM, "Doug Hellmann" wrote: >Excerpts from Steven Dake (stdake)'s message of 2016-11-08 13:08:11 +: >> Hey folks, >> >> As we split out the repository per our unanimous vote several months ago, we >> have a choice to make (I think, assuming we

Re: [openstack-dev] [release] change in plan for releases repo data model updates

On Tue, Nov 08, 2016 at 12:28:28PM -0500, Doug Hellmann wrote: > At the summit we said we would move the data that tells us the type > and release model for each deliverable out of the governance > repository and into the releases repository where it is easier to > change over time, but that we

[openstack-dev] [all] Registration open for the Project Teams Gathering, Atlanta Feb 20-24, 2017

Hi everyone, The registration is now open for the first OpenStack Project Teams Gathering event (which will take place in Atlanta, GA the week of February 20, 2017). This event is geared toward existing upstream team members, and will provide a venue for those project teams to meet, discuss and

Re: [openstack-dev] [release] New hacking 0.12.0

  -Original Message- From: Ihar Hrachyshka Reply: OpenStack Development Mailing List (not for usage questions) Date: November 8, 2016 at 11:19:42 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [requirements][kolla][security] pycrypto vs cryptography

-Original Message- From: Rob C Reply: OpenStack Development Mailing List (not for usage questions) Date: November 7, 2016 at 07:39:57 To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [nova] cells v2 ocata summit sessions recap

We had two design summit sessions for cells v2 at the Ocata summit in Barcelona. The full etherpads are here: https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-scheduler https://etherpad.openstack.org/p/ocata-nova-summit-cellsv2-quotas In the first session we mostly talked about the

[openstack-dev] [tc][ux] UX team extra-ATCs expired

UX team, In the process of cleaning up expired ATCs in the governance repository, https://review.openstack.org/#/c/388170/ removed all of the names of extra-atcs for the UX project. If any of those folks would not otherwise be considered ATC, they can be added back with new expiration dates

Re: [openstack-dev] [nova] Follow up on BCN review cadence discussions

On 11/08/2016 12:13 PM, Matt Riedemann wrote: I'd also like to say that I dislike the constant comparisons to the kernel. If people are going to make that comparison, then let's say the kernel overall is all of OpenStack, and there are subsystems, like nova/cinder/glance/etc, with their own

Re: [openstack-dev] [all] important changes to pep8 python jobs

On Thu, Nov 03, 2016 at 12:29:09PM -0400, Paul Belanger wrote: > Greetings, > > We (openstack-infra) are proposing a change to the current pep8[1] job for > python jobs, and would like to bring your attention to it. > > We'll be removing the extra-index-url field from pip.conf which forces the

Re: [openstack-dev] [nova] Follow up on BCN review cadence discussions

On Nov 8, 2016 1:13 PM, "Matt Riedemann" wrote: > > On 11/8/2016 11:39 AM, Dan Smith wrote: >>> >>> I do imagine, however, that most folks who have been working >>> on nova for long enough have a list of domain experts in their heads >>> already. Would actually putting

Re: [openstack-dev] [nova] Live migrations: Post-Copy and Auto-Converge features research

Daniel, Thanks for your suggestions. Yes, there is a plan to do several more types of research in very similar areas. Best — Vlad > On Nov 8, 2016, at 12:37, Daniel P. Berrange wrote: > > On Mon, Nov 07, 2016 at 10:34:39PM +0200, Vlad Nykytiuk wrote: >> Hi, >> >> As you

[openstack-dev] [MassivelyDistributed] IRC Meeting postponed

Dear all, We are still looking for a final slot for our bi-weekly IRC meeting and thus we have to postpone our first meeting to a date to be determined (hopefully next week, i.e. Wednesday Nov the 16th). I will come back to you with the final time as soon as possible. Meanwhile, you can

[openstack-dev] [tripleo] Please review, tripleo ci transition to the quickstart tool set

Greetings, As discussed at the ocata summit, work is being done to update the set of tools used in tripleo ci to tripleo-quickstart and tripleo-quickstart-extras [1-2]. There is work, review, and validation required prior to the transition. A draft of the work items is available [3], please if

Re: [openstack-dev] [nova] Follow up on BCN review cadence discussions

On 11/8/2016 11:39 AM, Dan Smith wrote: I do imagine, however, that most folks who have been working on nova for long enough have a list of domain experts in their heads already. Would actually putting that on paper really hurt? You mean like this?

Re: [openstack-dev] [openstack-infra] Please add a initial core member to meteos-core.

On Mon, Nov 7, 2016, at 11:25 PM, Hiroyuki Eguchi wrote: > Hello Infra Team. > > I've created new projects named meteos and python-meteosclient. > Cloud you please add me (Hiroyuki Eguchi ) > as a initial core member of meteos-core ? Done. Let us know if you have any

Re: [openstack-dev] [Congress] Error datasource create

Here's the pertinent error. It looks like you have a typo in one of your translators. 2016-11-08 12:15:29.906 TRACE congress.dse2.dse_node InvalidParamException: Params (field_translators, selector_type) are invalid. Valid params: ('translation-type', 'table-name', 'parent-key', 'id-col',

Re: [openstack-dev] [requirements][kolla][security] pycrypto vs cryptography

Hey Guys, If FIPS 140-2 compliance is important you might want to look at something like a PKCS#11 wrapper and let your PKCS#11 complaint module be the deciding factor in meeting that compliance level. There are wrappers for most languages. (We have our own python p11 implementation tailored to

Re: [openstack-dev] [nova] Follow up on BCN review cadence discussions

> I do imagine, however, that most folks who have been working > on nova for long enough have a list of domain experts in their heads > already. Would actually putting that on paper really hurt? You mean like this? https://wiki.openstack.org/wiki/Nova#Developer_Contacts Those are pretty much

[openstack-dev] [release] change in plan for releases repo data model updates

At the summit we said we would move the data that tells us the type and release model for each deliverable out of the governance repository and into the releases repository where it is easier to change over time, but that we needed to think more about what might break by making that change. After

Re: [openstack-dev] [nova] Follow up on BCN review cadence discussions

On Mon, 2016-11-07 at 11:50 +, Matthew Booth wrote: > I'd like to follow up on the discussions we had in Barcelona around > review cadence. I took a lot away from these discussions, and I > thought they were extremely productive. I think the summary of the > concerns was: > >   Nova is a

Re: [openstack-dev] [release] New hacking 0.12.0

> On 8 Nov 2016, at 17:23, Ian Cordasco wrote: > > > > -Original Message- > From: Ihar Hrachyshka > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: November 8, 2016 at

Re: [openstack-dev] [kolla][release] Version numbers for kolla-ansible repository.

Excerpts from Steven Dake (stdake)'s message of 2016-11-08 13:08:11 +: > Hey folks, > > As we split out the repository per our unanimous vote several months ago, we > have a choice to make (I think, assuming we are given latitude of the > release team who is in the cc list) as to which

Re: [openstack-dev] [all] Embracing new languages in OpenStack

Excerpts from Flavio Percoco's message of 2016-11-08 08:33:41 -0800: > On 08/11/16 16:20 +, Hayes, Graham wrote: > >On 08/11/2016 15:55, Doug Hellmann wrote: > >> Excerpts from Hayes, Graham's message of 2016-11-08 13:04:08 +: > >>> On 08/11/2016 10:30, Thierry Carrez wrote: > Ash

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On 08/11/2016 16:39, Flavio Percoco wrote: > On 08/11/16 16:20 +, Hayes, Graham wrote: >> On 08/11/2016 15:55, Doug Hellmann wrote: >>> Excerpts from Hayes, Graham's message of 2016-11-08 13:04:08 +: On 08/11/2016 10:30, Thierry Carrez wrote: > Ash wrote: >> [...] >>

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On 2016-11-08 06:43:33 -0800 (-0800), Flavio Percoco wrote: [...] > I think part of the community-wide concerns that were raised > originated from the lack of an actual process for this evaluation > to be done and the lack of up front work, which is something that > I'm trying to address here.

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On 08/11/16 16:20 +, Hayes, Graham wrote: On 08/11/2016 15:55, Doug Hellmann wrote: Excerpts from Hayes, Graham's message of 2016-11-08 13:04:08 +: On 08/11/2016 10:30, Thierry Carrez wrote: Ash wrote: [...] Here's another take on the situation. If there are people who genuinely wish

Re: [openstack-dev] [kolla][release] Version numbers for kolla-ansible repository.

On 2016-11-08 19:07:07 +0530 (+0530), Swapnil Kulkarni wrote: [...] > I would love to get inputs from release team, though one of the recent > repo split I remember is neutron and if I look at the history, old > tags from git revisions are preserved. I think we can follow the same > process for

Re: [openstack-dev] [release] New hacking 0.12.0

  -Original Message- From: Ihar Hrachyshka Reply: OpenStack Development Mailing List (not for usage questions) Date: November 8, 2016 at 02:39:24 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On 08/11/2016 15:55, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-11-08 13:04:08 +: >> On 08/11/2016 10:30, Thierry Carrez wrote: >>> Ash wrote: [...] Here's another take on the situation. If there are people who genuinely wish to see a CI pipeline that

Re: [openstack-dev] [all] Embracing new languages in OpenStack

Excerpts from Hayes, Graham's message of 2016-11-08 13:04:08 +: > On 08/11/2016 10:30, Thierry Carrez wrote: > > Ash wrote: > >> [...] > >> Here's another take on the situation. If there are people who genuinely > >> wish to see a CI pipeline that can support something like Go, perhaps > >>

Re: [openstack-dev] [Magnum] New Core Reviewers

+1 for both Cheers, Spyros On 8 November 2016 at 03:34, Yuanying OTSUKA wrote: > +1 for both. > > Best regards > -yuanying > > 2016年11月8日(火) 4:23 Hongbin Lu : > >> +1! >> >> Both jvgrant and yatin contributed a lot to the Magnum project. It would

Re: [openstack-dev] [all] Embracing new languages in OpenStack

Excerpts from Joshua Harlow's message of 2016-11-07 15:53:51 -0800: > > > > Concretely - oslo.config is important because it shapes what the config > > files look like. The implementation language of a particular service > > shouldn't change what our config files look like, yeah? > > Standards

Re: [openstack-dev] [openstack-infra][nova][tempest][qa][infra] NUMA topology, cpu pinning, hugepages tempest tests upstream or plugin

I'd like to invite everybody to collaborate around nfv feature testing in OpenStack in etherpad [1]. [1] https://etherpad.openstack.org/p/nfv-tests From: Znoinski, Waldemar [mailto:waldemar.znoin...@intel.com] Sent: Tuesday, November 8, 2016 12:26 PM To: openstack...@lists.openstack.org;

[openstack-dev] [charms] design summit sessions summary

Hi All After some extended travel after the summit, I've finally got round to writing a summary of the two design summit sessions we held in Barcelona (see [0] and [1] for full notes). 1) Cross Charm Initiatives We had general agreement to switch all charms to Python 3, dropping charm support

Re: [openstack-dev] [nova] Nova-MultiJob CI (non-voting) request to comment

Hi Lenny, Matt et al, We've touched the same NFV features testing topic on live-migration meeting today and apart a ML [1] post we'd invite everybody to collaborate around nfv tests in etherpad [2]. [1] http://lists.openstack.org/pipermail/openstack-dev/2016-November/106949.html [2]

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On 08/11/16 13:04 +, Hayes, Graham wrote: On 08/11/2016 10:30, Thierry Carrez wrote: That said, I think that if we can have more confidence that our structure can handle it (from infra to release/stable/dep management) and that the OpenStack community will share expertise and best practices

Re: [openstack-dev] [searchlight] Propose Zhenyu Zheng for Searchlight core

Sorry for the delay, I was out of town. This is now done. Welcome to the core team! From: Zhenyu Zheng Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Monday, November 7, 2016 at 8:13 PM To: "OpenStack Development Mailing List (not for usage questions)" Subject:

[openstack-dev] [winstackers][hyperv] IRC Hyper-V team meeting

Hello, We will resume the weekly Hyper-V meetings on Wednesdays, 13:00 UTC, on the #openstack-meeting-3 IRC channel, starting with tomorrow. Meeting details: https://wiki.openstack.org/wiki/Meetings/Hyper-V Feel free to join! Best regards, Claudiu Belu

Re: [openstack-dev] [Browbeat] Nominate Justin Kilpatrick as core.

+1. I think Justin's done some awesome work and would be a great addition to the core team. Better get reviewing some patches Justin! ;) On Fri, Oct 28, 2016 at 10:28 AM, Joe Talerico wrote: > Justin has been doing a great deal of work on the Browbeat-CI and > stabilizing

Re: [openstack-dev] [cinder] consistency groups in ceph

You cannot remove a volume completely if there is still a group snapshot. You can remove the volume from the group but you can’t delete the volume because it still has snapshot dependent on it. So if you want to completely remove a volume that is in a group, you can delete the group snapshot

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

Hi, We have weekly Nova API meeting tomorrow. 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

Re: [openstack-dev] [nova] Do we have users of CryptsetupEncryptor and if so why?

On 07-11-16 17:42:02, Lee Yarwood wrote: > Hello all, > > The following bug was recently discovered where encrypted volumes > created prior to Newton use a slightly mangled passphrase : > > The passphrase used to encrypt or decrypt volumes was mangled prior to Newton >

Re: [openstack-dev] [neutron] Ocata End user and operator feedback recap

On Tue, Nov 8, 2016 at 12:57 AM, Oleg Bondarev wrote: > > > On Tue, Nov 8, 2016 at 12:22 AM, Carl Baldwin wrote: >> >> Ocata End user and operator feedback recap >> >> >> The purpose of this

Re: [openstack-dev] [kolla][release] Version numbers for kolla-ansible repository.

On Tue, Nov 8, 2016 at 6:38 PM, Steven Dake (stdake) wrote: > Hey folks, > > As we split out the repository per our unanimous vote several months ago, we > have a choice to make (I think, assuming we are given latitude of the > release team who is in the cc list) as to which

[openstack-dev] [kolla][release] Version numbers for kolla-ansible repository.

Hey folks, As we split out the repository per our unanimous vote several months ago, we have a choice to make (I think, assuming we are given latitude of the release team who is in the cc list) as to which version to call kolla-ansible. My personal preference is to completely retag our newly

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On 08/11/2016 10:30, Thierry Carrez wrote: > Ash wrote: >> [...] >> Here's another take on the situation. If there are people who genuinely >> wish to see a CI pipeline that can support something like Go, perhaps >> you can establish a prerequisite of working with the Infra team on >> establishing

Re: [openstack-dev] [ptl][release] ocata release management communication

Doug, As predecessor PTL for Kolla, I have followed your recommendations 1-4 including this ack, although I am not sure its really necessary for me. Note, I am not sure Michal (inc0 on irc) wants me to continue as release liaison or do the job himself, so that step has not yet been taken. I

Re: [openstack-dev] [nova] Live migrations: Post-Copy and Auto-Converge features research

Thanks, Pawel! — Vlad > On Nov 8, 2016, at 09:53, Koniszewski, Pawel > wrote: > > Adding operators list, as it might be interesting for them. Please note that > some of tested options are not available in nova, i.e., XBZRLE and > postcopy-after-precopy.

[openstack-dev] [openstack-infra][nova][tempest][qa][infra] NUMA topology, cpu pinning, hugepages tempest tests upstream or plugin

Hi all, Due to recent discussions around Enhanced Platform Awareness (EPA) and their testing in OpenStack thinking was started to take what Intel NFV 3rd party CI [1] runs at this moment and merge some/all into upstream Tempest. Currently intel-nfv-ci-tests is a Tempest plugin [2] [3] and it's

Re: [openstack-dev] [Congress] Error datasource create

Hi everybody, really, I've not been able to create the datasource for magnum. Now, I've seen that I've these errors when I restart the congress server.. "ERROR congress.dse2.dse_node [-] Error loading instance of module 'congress.datasources.magnum_driver.MagnumDriver' 2016-11-08 12:15:29.906

Re: [openstack-dev] [barbican] Nominating Arun Kant for barbican-core

Congratulations Arun, you've put a lot of work in! On Mon, Nov 7, 2016 at 10:05 PM, Fernando J Diaz wrote: > +1 Congrats Arun, welcome to Barbican Core. > > > __ > OpenStack Development Mailing List (not

Re: [openstack-dev] [nova] Live migrations: Post-Copy and Auto-Converge features research

On Mon, Nov 07, 2016 at 10:34:39PM +0200, Vlad Nykytiuk wrote: > Hi, > > As you may know, currently QEMU supports several features that help live > migrations to operate more predictively. These features are: auto-converge > and post-copy. > I made a research on performance characteristics of

Re: [openstack-dev] [all] Embracing new languages in OpenStack

Ash wrote: > [...] > Here's another take on the situation. If there are people who genuinely > wish to see a CI pipeline that can support something like Go, perhaps > you can establish a prerequisite of working with the Infra team on > establishing the new pipeline. In my opinion, this seems to be

Re: [openstack-dev] [mistral] Promoting Dougal Matthews to the core team

+1 from my side! On Tue, Nov 8, 2016 at 11:34 AM, Gershenzon, Michal (Nokia - IL) < michal.gershen...@nokia.com> wrote: > +1 > > J > > > > Michal Gershenzon > Software Engineer, CloudBand > Application & Analytics , Nokia > Contact number: +972 9 793 3163 > > > > *From:* Deja, Dawid

Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

thanks very much for the update! Cheers, Lingxian Kong (Larry) On Tue, Nov 8, 2016 at 12:36 PM, Michael Johnson wrote: > Ocata LBaaS retrospective and next steps recap > -- > > This session lightly

[openstack-dev] [nova] hierarchy quota spec

Hi, I'd like community to look at hierarchy quota spec [1]. It uses a little different approach than previously proposed nested quota spec [2] and allows quota overbooking thing. I think it's possible to do this in parallel with cells-quota-api-db spec [3]. I'd happy to get some comments and

Re: [openstack-dev] [Congress] Run unit test

Hi everybody, I've been able to restart the congress server, add the driver for magnum and create a datasource. Now, how can I run the unit test for this driver? Which steps have I to do? Ruben - Messaggio originale - Da: "Ruben" A: "Eric"

Re: [openstack-dev] [Openstack-operators] [MassivelyDistributed] bi-weekly meeting

Thierry Carrez wrote: > [...] > That said, it's a balancing act and we may be past the point when > scheduling pain takes over the need to spread meetings out. I'll do a > quick pass to try to free up slots taken by dead meetings, and if we > can't free enough slots we'll likely add a new meeting

[openstack-dev] [Horizon] ui-cookiecutter

Hi Horizoners, Thanks for picking up ui-cookiecutter[1] and setting Ocata-2 milestone at summit[2]. Thai or Cindy? Thank you!! I'm maintaining ui-cookiecutter, but I'm ready for transferring it as Horizon subproject. Can I start to create subproject for ui-cookiecutter? Or please let me know

Re: [openstack-dev] [Openstack-operators] [MassivelyDistributed] bi-weekly meeting

Blair Bethwaite wrote: > Devil's advocate - what is "full enough"? Surely another channel is > essentially free and having flexibility in available timing is of utmost > importance? See http://docs.openstack.org/project-team-guide/open-community.html#public-meetings-on-irc That said, it's a

Re: [openstack-dev] [Openstack-operators] [MassivelyDistributed] bi-weekly meeting

Devil's advocate - what is "full enough"? Surely another channel is essentially free and having flexibility in available timing is of utmost importance? On 8 Nov 2016 5:37 PM, "Tony Breeds" wrote: > On Mon, Nov 07, 2016 at 05:52:43PM +0100, lebre.adr...@free.fr wrote: >

Re: [openstack-dev] [release] New hacking 0.12.0

> On 7 Nov 2016, at 21:47, Ken'ichi Ohmichi wrote: > > Hi, > > Today a new hacking 0.12.0 is released. > The release contains a new hacking rule: > > [H904] Delay string interpolations at logging calls. > > BTW, the hacking repo starts containing reno since this

Re: [openstack-dev] [mistral] Promoting Dougal Matthews to the core team

+1 ☺ Michal Gershenzon Software Engineer, CloudBand Application & Analytics , Nokia Contact number: +972 9 793 3163 From: Deja, Dawid [mailto:dawid.d...@intel.com] Sent: Tuesday, November 08, 2016 10:21 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [mistral] Promoting

Re: [openstack-dev] [mistral] Promoting Dougal Matthews to the core team

+1 It's good to have you on board Dougal! Dawid Deja On Tue, 2016-11-08 at 19:46 +1300, Lingxian Kong wrote: +1 of course! Cheers, Lingxian Kong (Larry) On Tue, Nov 8, 2016 at 6:09 PM, Renat Akhmerov > wrote: Hi, I’d like to promote