Re: [openstack-dev] [nova] Reminder: 1/19 is non-client library release freeze

The only one I can remember is https://review.openstack.org/421482. hope we can merge it and release new version of oslo.serialization. 2017-01-19 4:49 GMT+08:00 Matt Riedemann : > This is just a reminder that tomorrow (Thursday 1/19) is the non-client > library release freeze for Ocata. This me

Re: [openstack-dev] [release][stable] nominating Alan Pevec (apevec) for stable release core

Doug Hellmann wrote: > Based on Tony's recommendation, and Alan's recent review work, I > am nominating Alan Pevec (apevec) to have core reviewer rights on > stable releases in the openstack/releases repository. > > Release team, please either +1 or raise any concerns you have. +1 from me! -- T

[openstack-dev] [cloudkitty] IRC Meeting

Dear OpenStackers, As a reminder we will have an IRC meeting today at 13:30 UTC on #cloudkitty. We'll use it to coordinate our efforts to finish the actions in Ocata ! I hope to see many of you All the best Christophe Sauthier, PTL of Cloudkitty Christophe Sauthier

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

Hi Matt! This should be discussed, for sure, but there is a lot of potential. In general, it depends on how far we are willing to go. In the minimum approximation we can seamlessly replace Glance with Glare and operators simply get additional features for versioning, validation (and conversion, if

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

On Wed, Jan 18, 2017 at 9:30 PM, Doug Hellmann wrote: > Excerpts from Mikhail Fedosin's message of 2017-01-18 19:54:01 +0300: > > Hello! > > > > In this letter I want to tell you the current status of Glare project and > > discuss its future development within the entire OpenStack community. > >

[openstack-dev] [cinder] [qa] [infra] Proposed new Cinder gate jobs

Hi all, I've seen some confusion around new Cinder CI jobs being proposed to project-config in yesterday's IRC scrollback. This email aims to sum this up and explain purposes of what's being proposed. Background == For a few releases we're aiming to increase our functional and integratio

Re: [openstack-dev] [validations][ui][tripleo] resetting state of validations

On 01/18/2017 10:14 PM, Dan Trainor wrote: Hi - Is there a way to reset the state of all the validations that have previously ran, back to the original state they were prior to running? Using the UI, for example, some validations (by design) run as soon as you log in. Others run after differen

Re: [openstack-dev] [cinder] [qa] [infra] Proposed new Cinder gate jobs

On 2017-01-19 11:10, Michal Dulko wrote: > Hi all, > > I've seen some confusion around new Cinder CI jobs being proposed to > project-config in yesterday's IRC scrollback. This email aims to sum > this up and explain purposes of what's being proposed. Thanks a lot, Michal! That helps me seeing t

Re: [openstack-dev] [containers][magnum] Magnum team at Summit?

Hi. It would be great to meet in any case. We've been exploring Atomic system containers (as in 'atomic install --system ...') for our internal plugins at CERN, and having some issues with runc and selinux definitions plus some atomic command bugs. It's mostly due to the config.json being a hard

[openstack-dev] [vote][kolla] deprecation for Debian distro support

As discussed in one of the last team meetings I want to propose the deprecation (this cycle) and removal (next cycle) of the Debian support in Kolla. More than 1 week ago I sent a pre warning mail to the openstack-operators mailing list, without any reply [0]. Kolla core reviewers, please vote

[openstack-dev] [all][tc][swift][designate] New language addition process has been approved

Greetings, The Technical Committe recently approved a new reference document which describes how new programming languages can be proposed for inclusion as supported languages by OpenStack. The new reference document can be found here[0]. I'd like to take this chance not only to share this new p

[openstack-dev] [QA] Announcing my candidacy for PTL of the Pike cycle

Hi All, First and foremost would like to wish you all a successful 2017 ahead and with this I'm announcing my PTL candidacy of the Quality Assurance team for the Pike release cycle. I am glad to work in OpenStack community and would like to thank all the contributors who supported me to explor

Re: [openstack-dev] [containers][magnum] Magnum team at Summit?

Adrian Otto wrote: >> On Jan 18, 2017, at 10:18 AM, Josh Berkus wrote: >> [...] >> Is there going to be a magnum team meeting around OpenStack Summit in >> Boston? >> >> I'm the community manager for Atomic Host, so if you're going to have >> Magnum meetings, I'd like to send you some Atomic engin

Re: [openstack-dev] [vote][kolla] deprecation for Debian distro support

My vote for option 2 to deprecate Debian images. Since the last deprecation vote nobody tried to maintain Debian images. No gates, not tested and not maintained sound like good reasons to deprecate Debian. Regards 2017-01-19 10:53 GMT+00:00 Christian Berendt : > As discussed in one of the last t

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Jan. 20 2017

1) Roll Call 2) OPNFV: Daisy CI Progress 3) OPNFV: Daisy Support Escalator 4) OpenStack: Core Code Definition Wind Up 5) OpenStack: Choose Kolla Image Version To Deploy/Upgrade B. R., Zhijiang__ OpenStack Develo

[openstack-dev] [freezer] Freezer PTL Non-candidacy

Hello everyone, As I already announced during our IRC meeting, I'm not planning to run for the Pike PTL position. Having held this role for two cycle now and I think it is time for someone else to step in. I'll continue to contribute as a core-team member and will be available to help the new PTL

Re: [openstack-dev] [vote][kolla] deprecation for Debian distro support

My vote is for option 2 to deprecate Debian as there has been very little activity and operators seem uninterested in Debian as a platform. We could always add it back in at a later date if operators were to request it and the Debian team were interested in maintaining it. Regards -steve

Re: [openstack-dev] [vote][kolla] deprecation for Debian distro support

2 2017-01-19 8:50 GMT-03:00 Steven Dake (stdake) : > My vote is for option 2 to deprecate Debian as there has been very little > activity and operators seem uninterested in Debian as a platform. > > We could always add it back in at a later date if operators were to > request it and the Debian te

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

Glare does not compete with Swift, it uses this service as one of the possible backeds. On the whole I should note that in some cases the use of Swift is excessive: for example, for small files (a few kilobytes), it is easier to store them directly in the database. And Glare just let you do this -

[openstack-dev] [tripleo] [ptl] PTL candidacy for Pike

This is my candidacy for PTL role in the TripleO team for the Pike cycle. https://review.openstack.org/422587 Leading TripleO team during Ocata was tremendous. Together, we have moved forward in how we design, develop, deploy and use TripleO. Though Ocata cycle was too short and I have the motiv

Re: [openstack-dev] [charms] monitoring interface

Hi Brad, Thanks for looking into it. I think things should actually work out of the box as they are now. So, juju deploy nrpe nrpe-glance juju deploy nrpe nrpe-cinder juju deploy nagios juju deploy glance juju deploy cinder juju add-relation nrpe-glance glance juju add-relation nrpe-glance nagios

[openstack-dev] Proposing Jeremy Liu as core for cloudkitty

Hello developers mailing list folks, I'd like to propose that we add Jeremy Liu (liujiong) as an OpenStack cloudkitty core reviewer. He has been a member of our community for many months, contributing very seriously in cloudkitty and cloudkitty-dashboard. He also provided many reviews on bot

[openstack-dev] [watcher] PTG preparation

Hello folks, We already are one month away from the PTG event (mid-cycle) for Watcher. I started a new etherpad [1] to prepare the agenda. Please complete the topics list with all the items you want to discuss. Even if you don't plan to be in Atlanta, I'd like to have all Watcher community plans d

[openstack-dev] [neutron] neutron-lib impact: providernet extension moved to neutron-lib

A new version (1.1.0) of neutron-lib was recently released. Among other things, this release rehomes the neutron providernet API extension [1]. A consumption patch to use the rehomed code has been submitted to neutron [2] and once merged will impact consumers who use providernet constants from neu

Re: [openstack-dev] [cinder] [qa] [infra] Proposed new Cinder gate jobs

Thanks for giving this review Michal. On Thu, Jan 19, 2017 at 8:29 AM, Andreas Jaeger wrote: > On 2017-01-19 11:10, Michal Dulko wrote: > > Hi all, > > > > I've seen some confusion around new Cinder CI jobs being proposed to > > project-config in yesterday's IRC scrollback. This email aims to su

[openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7!

Hey folks, Our multi-os work has paid off and I was able to wrap up a CentOS 7 deployment of OpenStack-Ansible's master branch yesterday. My environment only has four physical servers, so I deployed the basics: - keystone - nova - glance - neutron - heat - horizon - galera/rabbitm

Re: [openstack-dev] Proposing Jeremy Liu as core for cloudkitty

Hi, OK to add Jeremy as core dev for Cloudkitty Regards, -- Maxime Cottret - Consultant Cloud/DataOps @ OBJECTIF-LIBRE Mail : maxime.cott...@objectif-libre.com Tel : 05 82 95 65 36 (standard) Web : www.objectif-libre.com Twitter: @objectiflibre Le 2017-01-19 14:18, Christophe Sauthier a écri

Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7!

That is great news! Congrats! -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/m

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

> On 19 Jan 2017, at 19:13, Mikhail Fedosin wrote: > > Plus, Swift does not provide data immutability. Where is the guarantee that > user won't change his files in Swift or completely remove them? Glare manages > this behavior and provides full immutability for stored data, regardless of > th

Re: [openstack-dev] [neutron] "Setup firewall filters only for required ports" bug

On Wed, Jan 18, 2017 at 10:45 PM, Bernard Cafarelli wrote: > Hi neutrinos, > > I would like your feedback on the mentioned changeset in title[1] > (yes, added since Liberty). > > With this patch, we (should) skip ports with > port_security_enabled=False or with an empty list of security groups >

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

Excerpts from Mikhail Fedosin's message of 2017-01-19 12:48:13 +0300: > Hi Matt! > > This should be discussed, for sure, but there is a lot of potential. In > general, it depends on how far we are willing to go. In the minimum > approximation we can seamlessly replace Glance with Glare and operato

[openstack-dev] [horizon] feature freeze exception request -- nova simple tenant usages api pagination

I would like to request a feature freeze exception for the following patch: https://review.openstack.org/#/c/410337 This patch adds support for retrieving the simple tenant usages from Nova in chunks, and it is necessary for correct data given that related patches have been already merged in Nova

Re: [openstack-dev] [Openstack] [OSSN-0074] Nova metadata service should not be used for sensitive information

- Original Message - > From: "Luke Hinds" > To: openst...@lists.openstack.org, openstack-dev@lists.openstack.org > Sent: Monday, December 19, 2016 4:26:24 AM > Subject: [Openstack] [OSSN-0074] Nova metadata service should not be used for > sensitive information > > OpenStack Security Not

Re: [openstack-dev] [keystone] 2017-1-11 policy meeting

Hi Lance, Your option 3 is not clear for me. You say that ‘The result would 0 policy files to maintain in tree and everything would be in code.’ Without this file, how can we define policies? Can user configure policies? Ruan From: Lance Bragstad [mailto:lbrags...@gmail.com] Sent: mercredi 18 ja

Re: [openstack-dev] [keystone] webob 1.7

On Wed, Jan 18, 2017 at 9:08 AM, Ian Cordasco wrote: > -Original Message- > From: Chuck Short > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: January 18, 2017 at 08:01:46 > To: OpenStack Development Mailing List > Subject: [openstack-dev] [keystone] web

[openstack-dev] [Fuel][Ci] New keyword for triggering deployment tests

Hi all, please be informed that for re-triggering fuel deployment tests [1] should be used Gerrit reply with keyword 'fuel: redeploy' [2] By implementing this change, we're separating heavy and time-consuming deployment tests from other tests, which gives us much more flexible re-triggering proce

Re: [openstack-dev] [all] Ubuntu 14.04 support in Newton and on

On 2017-01-18 15:19:36 -0800 (-0800), Eric K wrote: > Hi all, Is there any community-wide policy on how long we strive > to maintain compatibility with Ubuntu 14.04? For example by > avoiding relying on MySQL 5.7 features. I've had a hard time > finding it on openstack.org and ML discussions. Thank

[openstack-dev] [ironic][ptl] Announcing Ironic PTL candidacy for Pike

Greetings everyone! I would like to nominate myself as a candidate for ironic PTL for the Pike cycle. For those that don't know me, I'm TheJulia. I have been working in the OpenStack community since mid-2014, and ironic since early 2015. I'm likely best known for bifrost and advocating support for

Re: [openstack-dev] [tripleo][ui] FYI, the tripleo-ui package is currently broken

On 18 January 2017 at 11:35, Julie Pichon wrote: > I'm sorry to report we're finding ourselves in the same situation > again - CI will fail on all the UI patches, please don't recheck until > we have a new dependencies package available. > > On the plus side, with the help of amoralej on #rdo we f

Re: [openstack-dev] [keystone] 2017-1-11 policy meeting

Ruan, Good question! I should clarify that there would be no *default* policy file to maintain in the project source code, like in keystone currently [0]. All policy defaults would be coded into the project. Nova has already taken this approach with their policy file [1], which leaves them with no

[openstack-dev] [cinder] "Snapshot-manage imports snapshots with wrong size"

Hi, folks. Having worked on this bug [0] I could reproduce it with lvm as a backend. And during it further investigation, I found the real problem that triggers it. Here [1] after getting the real snapshot size, we are trying to update 'size' column. But actually snapshot's size is stored in cinde

[openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

Sylvain and I were talking about how he's going to work placement microversion requests into his filter scheduler patch [1]. He needs to make requests to the placement API with microversion 1.4 [2] or later for resource provider filtering on specific resource classes like VCPU and MEMORY_MB.

Re: [openstack-dev] [Openstack] [nova] Accessing instance.flavor.projects fails due to orphaned Flavor

On Fri, Jan 13, 2017 at 9:51 AM, Balazs Gibizer wrote: On Thu, Jan 12, 2017 at 4:56 PM, Jay Pipes wrote: On 01/12/2017 05:31 AM, Balazs Gibizer wrote: Hi, The flavor field of the Instance object is a lazy-loaded field and the projects field of the Flavor object is also lazy-loaded. Now it

Re: [openstack-dev] [Openstack] [OSSN-0074] Nova metadata service should not be used for sensitive information

On 2017-01-19 09:34:21 -0500 (-0500), Steve Gordon wrote: [...] > Does this configuration directive provide any mitigation for this > issue?: > > "use_forwarded_for = False (BoolOpt) Treat X-Forwarded-For > as the canonical remote address. Only enable this if you have a > sanitizing proxy.

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

Le 19/01/2017 16:27, Matt Riedemann a écrit : > Sylvain and I were talking about how he's going to work placement > microversion requests into his filter scheduler patch [1]. He needs to > make requests to the placement API with microversion 1.4 [2] or later > for resource provider filtering on s

Re: [openstack-dev] [tripleo][ui] FYI, the tripleo-ui package is currently broken

Thanks for being on top of this, Julie. Honza Pokorny On 2017-01-19 15:17, Julie Pichon wrote: > On 18 January 2017 at 11:35, Julie Pichon wrote: > > I'm sorry to report we're finding ourselves in the same situation > > again - CI will fail on all the UI patches, please don't recheck until > > w

Re: [openstack-dev] [keystone] webob 1.7

-Original Message- From: Corey Bryant Reply: OpenStack Development Mailing List (not for usage questions) Date: January 19, 2017 at 08:52:25 To: OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] [keystone] webob 1.7 > On Wed, Jan 18, 2017 at 9:08

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On 1/19/2017 9:43 AM, Sylvain Bauza wrote: Le 19/01/2017 16:27, Matt Riedemann a écrit : Sylvain and I were talking about how he's going to work placement microversion requests into his filter scheduler patch [1]. He needs to make requests to the placement API with microversion 1.4 [2] or late

[openstack-dev] [fuel] Weekly meeting Jan 19 is canceled

Nothing is on the agenda [0] this week, so I'm calling to cancel the meeting. If you have anything to discuss please come chat in #fuel or add it to the agenda to discuss next week. [0] https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda --- WBR, Alexey Shtokolov OpenStack Fuel PTL __

Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7!

Hi Major, great news indeed. BTW are you implying that Ubuntu LTS is unstable or not stable enough to run OpenStack? I think that it would be valuable if you could share more details in this regard, point to Ubuntu specific bugs etc. Thanks. On Thu, Jan 19, 2017 at 2:58 PM, Sean M. Collins wrote:

Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7!

-Original Message- From: Adam Heczko Reply: OpenStack Development Mailing List (not for usage questions) Date: January 19, 2017 at 10:06:14 To: OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7! > Hi

Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7!

On 01/19/2017 10:04 AM, Adam Heczko wrote: > Hi Major, great news indeed. > BTW are you implying that Ubuntu LTS is unstable or not stable enough to > run OpenStack? > I think that it would be valuable if you could share more details in > this regard, point to Ubuntu specific bugs etc. I believe t

Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7!

-Original Message- From: Monty Taylor Reply: OpenStack Development Mailing List (not for usage questions) Date: January 19, 2017 at 10:18:20 To: openstack-dev@lists.openstack.org Subject:  Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7! > On 01/19/2017 10:04 AM, Adam

[openstack-dev] [infra][mitmstack] initial member of mitmstack groups

Hi, Infra team, Could you please help add me as initial member in mitmstack-core and mitmstack-release ? Thank you. -- Yujun __

Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7!

On 01/19/2017 10:14 AM, Ian Cordasco wrote: > -Original Message- > From: Adam Heczko > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: January 19, 2017 at 10:06:14 > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstac

Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7!

-Original Message- From: Monty Taylor Reply: OpenStack Development Mailing List (not for usage questions) Date: January 19, 2017 at 10:22:23 To: openstack-dev@lists.openstack.org Subject:  Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7! > On 01/19/2017 10:14 AM, Ian

Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7!

On 01/19/2017 10:04 AM, Adam Heczko wrote: > BTW are you implying that Ubuntu LTS is unstable or not stable enough to run > OpenStack? > I think that it would be valuable if you could share more details in this > regard, point to Ubuntu specific bugs etc. Hey Adam, One of the bigger issues (as

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann wrote: > Sylvain and I were talking about how he's going to work placement > microversion requests into his filter scheduler patch [1]. He needs to make > requests to the placement API with microversion 1.4 [2] or later for > resource provider filter

Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7!

On 01/19/2017 10:19 AM, Ian Cordasco wrote: >> I believe this is more about supporting folks who want to run on >> Centos/RHEL, rather than a step to removing Ubuntu support. > That's also correct. OpenStack-Ansible is attempting to support > multiple distros at the same time. =) Correct! The Oca

Re: [openstack-dev] [keystone] webob 1.7

On Thu, Jan 19, 2017 at 10:46 AM, Ian Cordasco wrote: > -Original Message- > From: Corey Bryant > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: January 19, 2017 at 08:52:25 > To: OpenStack Development Mailing List (not for usage questions) > > Subject:

Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7!

Major, thanks for sharing this! On Thu, Jan 19, 2017 at 5:24 PM, Major Hayden wrote: > On 01/19/2017 10:04 AM, Adam Heczko wrote: > > BTW are you implying that Ubuntu LTS is unstable or not stable enough to > run OpenStack? > > I think that it would be valuable if you could share more details i

Re: [openstack-dev] [openstack-ansible] Ocata deployed on CentOS 7!

Thanks for sharing this. Great news! Hao Ran Hu (Vern) Software Developer Phone: 86-21-60928179 E-mail: huhao...@cn.ibm.com     - Original message -From: Adam Heczko To: "OpenStack Development Mailing List (not for usage questions)" Cc:Subject: Re: [openstack-dev] [openstack-ansible] Ocata

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

Le 19/01/2017 17:00, Matt Riedemann a écrit : > On 1/19/2017 9:43 AM, Sylvain Bauza wrote: >> >> >> Le 19/01/2017 16:27, Matt Riedemann a écrit : >>> Sylvain and I were talking about how he's going to work placement >>> microversion requests into his filter scheduler patch [1]. He needs to >>> ma

[openstack-dev] [nova] Do not recheck changes until 422709 is merged

The py35 unit test job is broken for Nova until this patch is merged: https://review.openstack.org/#/c/422709/ So please hold off on the rechecks until that happens. -- Thanks, Matt Riedemann __ OpenStack Development Ma

[openstack-dev] [tripleo] CI Squad Meeting Summary (week 4)

Everybody interested in the TripleO CI and Quickstart is welcome to join the weekly meeting: Time: Thursdays, 15:30-16:30 UTC Place: https://bluejeans.com/4113567798/ Here's this week's summary: * There aren't any blockers or bottlenecks slowing down the transition to the Quickstart based CI.

[openstack-dev] Subject: [all][api] POST /api-wg/news

Greetings OpenStack community, Today's meeting [0] was a relatively quiet one; I attribute it to cdent's absence. :) Most of the meeting was concerned with reviews of existing issues, and those didn't generate much discussion. There was some discussion of cdent's response to the OpenStack Tech

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On 01/19/2017 11:25 AM, Alex Schultz wrote: On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann wrote: Sylvain and I were talking about how he's going to work placement microversion requests into his filter scheduler patch [1]. He needs to make requests to the placement API with microversion 1.4 [2

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

> >> Sylvain and I were talking about how he's going to work placement > >> microversion requests into his filter scheduler patch [1]. He needs to > >> make > >> requests to the placement API with microversion 1.4 [2] or later for > >> resource provider filtering on specific resource classes like

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On Thu, Jan 19, 2017 at 10:34 AM, Jay Pipes wrote: > On 01/19/2017 11:25 AM, Alex Schultz wrote: >> >> On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann >> wrote: >>> >>> Sylvain and I were talking about how he's going to work placement >>> microversion requests into his filter scheduler patch [1].

Re: [openstack-dev] [infra][mitmstack] initial member of mitmstack groups

On Thu, Jan 19, 2017, at 08:19 AM, Yujun Zhang wrote: > Hi, Infra team, > > Could you please help add me as initial member > in > mitmstack-core > and mitmstack-release > ? Thank y

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On 01/19/2017 01:18 PM, Alex Schultz wrote: On Thu, Jan 19, 2017 at 10:34 AM, Jay Pipes wrote: On 01/19/2017 11:25 AM, Alex Schultz wrote: On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann wrote: Sylvain and I were talking about how he's going to work placement microversion requests into his

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On 01/19/2017 12:59 PM, Eoghan Glynn wrote: I think Alex is suggesting something different than falling back to the legacy behaviour. The ocata scheduler would still roll forward to basing its node selection decisions on data provided by the placement API, but would be tolerant of the 3 different

[openstack-dev] [release][ptl] Release countdown for week R-4 (Ocata-3 Milestone), Jan 23-27

We're rapidly approaching the end of the Ocata cycle. There are several deadlines coming up within the next few weeks, so please review the schedule and make sure you understand how they affect your teams. Focus - This week begins Feature Freeze for all milestone-based projects. No feature pa

[openstack-dev] [qa] PTL non-candidacy

Hi, I will step down as PTL after this Ocata cycle. I was happy to see new ideas and folks who try making ideas true in this 2 cycles. Now QA project has a lot of components with many people's effort and we help each other as a community. This experience is very exciting for me, I am proud to bein

[openstack-dev] [keystone] [ptl] PTL candidacy for Pike

Greetings, I want to run for keystone PTL to facilitate an environment for others to grow and make meaningful changes so that we continue to build keystone into a more stable, scalable and performant project [0]. January marks my fifth anniversary working with OpenStack. In that time I've had the

[openstack-dev] [neutron] neutron-lib impact: portbindings extension moved to neutron-lib

A new version (1.1.0) of neutron-lib was recently released. Among other things, this release rehomes the neutron portbindings API extension [1]. A consumption patch to use the rehomed code has been submitted to neutron [2] and once merged will impact consumers who use portbindings constants from n

Re: [openstack-dev] [qa] PTL non-candidacy

Thank you for your great effort! I'm very proud of you as a colleague :) -- Masayuki Igawa On Fri, Jan 20, 2017 at 6:16 AM, Ken'ichi Ohmichi wrote: > Hi, > > I will step down as PTL after this Ocata cycle. > I was happy to see new ideas and folks who try making ideas true in > this 2 cycles. > N

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On Thu, Jan 19, 2017 at 11:45 AM, Jay Pipes wrote: > On 01/19/2017 01:18 PM, Alex Schultz wrote: >> >> On Thu, Jan 19, 2017 at 10:34 AM, Jay Pipes wrote: >>> >>> On 01/19/2017 11:25 AM, Alex Schultz wrote: On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann wrote: > > >>>

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On Thu, Jan 19, 2017 at 2:29 PM, Alex Schultz wrote: > > What are these issues? My original message was to highlight one > particular deployment type which is completely independent of how > things get packaged in the traditional sense of the word > (rpms/deb/tar.gz). Perhaps it's getting lost in

Re: [openstack-dev] [all] Ubuntu 14.04 support in Newton and on

Hi Jeremy, thank you for the pointers and the background on Newton! On 1/19/17, 7:12 AM, "Jeremy Stanley" wrote: >On 2017-01-18 15:19:36 -0800 (-0800), Eric K wrote: >> Hi all, Is there any community-wide policy on how long we strive >> to maintain compatibility with Ubuntu 14.04? For example by

[openstack-dev] (dis)Continuation of Neutron VPNaaS

Hi, November last year the Neutron team has announced that VPN as a Service will be no longer part of Neutron[1]. We run a public cloud based in New Zealand called Catalyst Cloud[2]. Our customers find the VPN service extremely useful to integrate their cloud tenant's with on-premise infrastructu

[openstack-dev] [trove] self-nomination for Trove PTL

I am writing to submit my candidacy for re-election as the PTL for the Trove project (Pike cycle). I have been an active technical contributor to the Trove project since just before the Icehouse release when Trove was integrated into OpenStack. I have also contributed code[1] and reviews[2] to some

[openstack-dev] [puppet] Nominating mkarpin for core for the Puppet OpenStack modules

Hey Puppet Cores, I would like to nominate Mykyta Karpin as a Core reviewer for the Puppet OpenStack modules. He has been providing quality patches and reviews for some time now and I believe he would be a good addition to the team. His stats for the last 90 days can be viewed here[0] Please re

Re: [openstack-dev] [keystone] [nova] [glance] [oslo] webob 1.7

On Thu, Jan 19, 2017 at 11:34 AM, Corey Bryant wrote: > > > On Thu, Jan 19, 2017 at 10:46 AM, Ian Cordasco > wrote: > >> -Original Message- >> From: Corey Bryant >> Reply: OpenStack Development Mailing List (not for usage questions) >> >> Date: January 19, 2017 at 08:52:25 >> To: OpenS

[openstack-dev] [networking-sfc]

Hello, Are there updated install docs for sfc? The only install steps for a testbed I can find are here and they seem outdated: https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining Also from the conference videos there seems to be some Horizon menu / screens that are available?

Re: [openstack-dev] [nova] Do not recheck changes until 422709 is merged

On 1/19/2017 10:56 AM, Matt Riedemann wrote: The py35 unit test job is broken for Nova until this patch is merged: https://review.openstack.org/#/c/422709/ So please hold off on the rechecks until that happens. We're good to go again for rechecks. -- Thanks, Matt Riedemann _

Re: [openstack-dev] [nova] Feature-related changes that need a final +2 (1/18)

On 1/18/2017 4:43 PM, Matt Riedemann wrote: Just to bring this to the awareness of other reviewers, here is a list of blueprint-related patches that have a +2 and need a final push: 1. https://blueprints.launchpad.net/nova/+spec/ironic-plug-unplug-vifs-update https://review.openstack.org/#/c/36

Re: [openstack-dev] (dis)Continuation of Neutron VPNaaS

On 19 January 2017 at 13:41, Bruno L wrote: > Hi, > > November last year the Neutron team has announced that VPN as a Service > will be no longer part of Neutron[1]. > > We run a public cloud based in New Zealand called Catalyst Cloud[2]. Our > customers find the VPN service extremely useful to i

[openstack-dev] [TripleO] Defining Custom Deployment Networks

I would like to call attention to two patches which Steven Hardy proposed for Ocata to add the ability to create custom deployment networks [1] [2]. This would allow the use of networks other than the built-in 6 networks. These have gotten a little attention, and a couple of alternative methods wer

Re: [openstack-dev] [horizon] feature freeze exception request -- nova simple tenant usages api pagination

FFE granted for the three patches. We need to support that nova API change. On 20 January 2017 at 01:28, Radomir Dopieralski wrote: > I would like to request a feature freeze exception for the following patch: > > https://review.openstack.org/#/c/410337 > > This patch adds support for retrieving

Re: [openstack-dev] [puppet] Nominating mkarpin for core for the Puppet OpenStack modules

On Thu, Jan 19, 2017 at 5:25 PM, Alex Schultz wrote: > Hey Puppet Cores, > > I would like to nominate Mykyta Karpin as a Core reviewer for the > Puppet OpenStack modules. He has been providing quality patches and > reviews for some time now and I believe he would be a good addition to > the team.

Re: [openstack-dev] [qa] PTL non-candidacy

Thanks Kenichi for all your hardwork and nice leadership. Its been very good and lot of things we finished under your leadership. You managed all the activities in a very cool and polite way (Japanese style :)). ​-gmann On Fri, Jan 20, 2017 at 4:16 AM, Ken'ichi Ohmichi wrote: > Hi, > > I will

[openstack-dev] [qa] PTL Candidacy for Pike

Dear all, I’d like to announce my candidacy for PTL of the QA Program for the Pike cycle. I started working with OpenStack towards the end of 2011. Since 2014 I’ve been a core developer for Tempest. I’ve always aimed for Tempest to be able to run against any OpenStack cloud; a lot of my contribut

Re: [openstack-dev] [qa] PTL non-candidacy

Thank you Ken for the great work and for your leadership! I'm really glad you'll stay in the team and keep contributing. On Fri, Jan 20, 2017 at 12:41 AM Ghanshyam Mann wrote: > Thanks Kenichi for all your hardwork and nice leadership. > > Its been very good and lot of things we finished under

Re: [openstack-dev] [all] [barbican] [security] Why are projects trying to avoid Barbican, still?

Embrace the larger world instead of trying to recreate parts of it, create alliances with the CNCF and/or other companies The CNCF isn't a company... Yes, fair, good point, thanks for the correction. that are getting actively involved there and make bets that solutions there are things tha

Re: [openstack-dev] [keystone] [nova] [glance] [oslo] webob 1.7

Corey Bryant wrote: Added [nova] and [oslo] to the subject. This is also affecting nova and oslo.middleware. I know Sean's initial response on the thread was that this shouldn't be a priority for ocata but we're completely blocked by it. Would those teams be able to prioritize a fix for this?

Re: [openstack-dev] [all] Improving Vendor Driver Discoverability

On 17:38 Jan 18, Morales, Victor wrote: > Just a FYI, Ankur have been working on have a Feature Classification Matrix > in Neutron[1] which collects some of this information > > [1] https://review.openstack.org/#/c/318192/ I actually didn't know Nova also generated this with a script and ini file

Re: [openstack-dev] [qa] PTL non-candidacy

Yes really nice and hard work:) Though because of the reason of different time zone, I don't often have the chance to talk with Kenichi, but I am impressed by his working time, which is almost spreaded to 24 hours:) http://stackalytics.com/report/users/oomichi Original Mail Sender: ＜

Re: [openstack-dev] [keystone] [nova] [glance] [oslo] webob 1.7

On Thu, Jan 19, 2017 at 8:29 PM, Joshua Harlow wrote: > Corey Bryant wrote: > >> >> Added [nova] and [oslo] to the subject. This is also affecting nova and >> oslo.middleware. I know Sean's initial response on the thread was that >> this shouldn't be a priority for ocata but we're completely bl

Re: [openstack-dev] [nova] Do not recheck changes until 422709 is merged

On 1/19/2017 5:09 PM, Matt Riedemann wrote: On 1/19/2017 10:56 AM, Matt Riedemann wrote: The py35 unit test job is broken for Nova until this patch is merged: https://review.openstack.org/#/c/422709/ So please hold off on the rechecks until that happens. We're good to go again for rechecks.

  1   2   >