Re: [openstack-dev] [qa] [tc] Need champion for "cold upgrades capabilities" goal

Hi, Thank you so much for your warm comments/links/etc,etc! I'll check them and start to write a proposal for the goal for Rocky early next week. -- Masayuki On 01/11, Emilien Macchi wrote: > Sorry I forgot an important action: propose the goal for Rocky :-) > > An example with

Re: [openstack-dev] [all] [tc] Community Goals for Rocky

On Thu, Jan 11, 2018 at 9:59 PM, ChangBo Guo wrote: > I would like to help the goal - enable mutable configuration, would like to > post a patch for that later. are you interested to be the "Champion" for this goal? > > 2018-01-10 2:37 GMT+08:00 Emilien Macchi

Re: [openstack-dev] [all] [tc] Community Goals for Rocky

I would like to help the goal - enable mutable configuration, would like to post a patch for that later. 2018-01-10 2:37 GMT+08:00 Emilien Macchi : > As promised, let's continue the discussion and move things forward. > > This morning Thierry brought the discussion during the

Re: [openstack-dev] [qa] [tc] Need champion for "cold upgrades capabilities" goal

Sorry I forgot an important action: propose the goal for Rocky :-) An example with https://review.openstack.org/#/c/532361/ (from Sean). Thanks, On Thu, Jan 11, 2018 at 9:29 PM, Emilien Macchi wrote: > On Thu, Jan 11, 2018 at 7:13 PM, Masayuki Igawa >

Re: [openstack-dev] [ceilometer] Retiring ceilometerclient

hey Dan, On 2018-01-11 06:05 PM, Daniel Dyer wrote: > My understanding was that the API is not officially deprecated until queens. > Is this not the case? not quite. we removed the API permanently in queens. it was actually deprecated back in 2016[1] officially. we've

Re: [openstack-dev] [ceilometer] Retiring ceilometerclient

On Thu, Jan 11, 2018 at 3:05 PM, Daniel Dyer wrote: > My understanding was that the API is not officially deprecated until queens. > Is this not the case? https://docs.openstack.org/releasenotes/ceilometer/ocata.html#deprecation-notes

Re: [openstack-dev] [qa] [tc] Need champion for "cold upgrades capabilities" goal

On Thu, Jan 11, 2018 at 7:13 PM, Masayuki Igawa wrote: > Hi Emilien, > > I'd love to take this role! Wow, this is AWESOME. > I have some tempest experience but not QA work which you mentioned > (devstack, grenade, zuul layout) that much. However, I think it will > be a

Re: [openstack-dev] [qa][requirements] CentOS libvirt versus newton/ocata libvirt-python

On 01/12/2018 02:53 PM, Matthew Thode wrote: First, about newton, it's dead (2017-10-11). Yeah, there were a few opt-outs, which is why I think devstack still runs it. Not worth a lot of effort. Next, about ocata, it looks like it can support newer libvirt, but just because a distro updated

Re: [openstack-dev] [qa][requirements] CentOS libvirt versus newton/ocata libvirt-python

On 18-01-12 12:42:49, Ian Wienand wrote: > Hi, > > So I guess since CentOS included libvirt 3.2 (7-1708, or around RHEL > 7.4), it's been incompatible with libvirt-python requirements of 2.1.0 > in newton [1] and 2.5.0 in ocata [2] (pike, at 3.5.0, works). > > Do we want to do anything about

Re: [openstack-dev] [qa] [tc] Need champion for "cold upgrades capabilities" goal

Hi Emilien, I'd love to take this role! I have some tempest experience but not QA work which you mentioned (devstack, grenade, zuul layout) that much. However, I think it will be a very good opportunity to step-up. So, for me, the next step might be to know grenade / upgrade jobs / plugin

[openstack-dev] [qa][requirements] CentOS libvirt versus newton/ocata libvirt-python

Hi, So I guess since CentOS included libvirt 3.2 (7-1708, or around RHEL 7.4), it's been incompatible with libvirt-python requirements of 2.1.0 in newton [1] and 2.5.0 in ocata [2] (pike, at 3.5.0, works). Do we want to do anything about this? I can think of several options * bump the

Re: [openstack-dev] [all] How to use libxml2 with tox

On Thu, Jan 11, 2018, at 1:52 PM, Kwan, Louie wrote: > Would like to use libxml2 and having issues for tox. > > What needs to be included in the requirements.txt file etc. > > Any tip is much appreciated. You likely need to make sure that libxml2 header packages are installed so that the

Re: [openstack-dev] [ceilometer] Retiring ceilometerclient

Gordon, My understanding was that the API is not officially deprecated until queens. Is this not the case? Dan > On Jan 11, 2018, at 7:05 AM, gordon chung wrote: > > > > On 2018-01-11 01:48 AM, Thomas Bechtold wrote: >> >> It was at lease for openSUSE: >>

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

On 1/11/2018 10:36 AM, Colleen Murphy wrote: 1) All trademark-related tests should go in the tempest repo, in accordance with the original resolution. This would mean that even projects that have never had tests in tempest would now have to add at least some of their black-box tests

Re: [openstack-dev] Retirement of astara repos?

On Thu, Jan 11, 2018 at 04:55:03PM -0500, Mark McClain wrote: > Sean, Andreas- > > Sorry I missed Andres’ message earlier in December about retiring astara. > Everyone is correct that development stopped a good while ago. We attempted > in Barcelona to find others in the community to take over

Re: [openstack-dev] Retirement of astara repos?

Sean, Andreas- Sorry I missed Andres’ message earlier in December about retiring astara. Everyone is correct that development stopped a good while ago. We attempted in Barcelona to find others in the community to take over the day-to-day management of the project. Unfortunately, nothing

[openstack-dev] [all] How to use libxml2 with tox

Would like to use libxml2 and having issues for tox. What needs to be included in the requirements.txt file etc. Any tip is much appreciated. Thanks. Louie __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Release-job-failures] release-post job for openstack/releases failed

On Thu, Jan 11, 2018 at 09:08:38PM +, z...@openstack.org wrote: > Build failed. > > - tag-releases > http://logs.openstack.org/a5/a52aa0b2ad06a52e50be8879f9256576ceceb91c/release-post/tag-releases/fecf776/ > : SUCCESS in 3m 53s > - publish-static >

Re: [openstack-dev] [nova] Working toward Queens feature freeze and RC1

> From: William M Edmonds/Raleigh/IBM > To: "OpenStack Development Mailing List \(not for usage questions\)" > > Date: 01/08/2018 03:11 PM > Subject: Re: [openstack-dev] [nova] Working toward Queens feature > freeze and RC1 > > > From: Matt Riedemann

Re: [openstack-dev] Retirement of astara repos?

It’s my understanding that the development has been moved back into DreamHost. I stopped working on it over two years ago. I’ll ping them to double check that repo retiring is what they want. Thanks for asking first! On Wed, Jan 10, 2018 at 21:56 Swapnil Kulkarni wrote: >

[openstack-dev] [qa] [tc] Need champion for "cold upgrades capabilities" goal

Some projects are still not testing cold upgrades and therefore don't have the "supports-upgrade" tag. https://governance.openstack.org/tc/reference/tags/assert_supports-upgrade.html This goal would mostly benefit the operators community as we would continue to ensure OpenStack can be upgraded

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

Excerpts from Saverio Proto's message of 2018-01-11 15:23:46 +0100: > Hello, > > we recently enabled the JSON logging to feed a Kibana dashboard and look > at the logs with modern tooling. > > however it looks like in our Openstack Newton deployment that some > information in the JSON files is

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, Wide-ranging conversations in the API-SIG meeting today [7]. We started out discussing techniques for driving the adoption of the guidelines published by the group. Two ideas received most of the attention: * Provide guidance on the tools available to make it

[openstack-dev] [release] Release countdown for week R-6, January 13 - 19

Development Focus - Teams should be focused on implementing planned work. Work should be wrapping up on non-client libraries to meet the lib deadline Thursday, the 18th. General Information --- We are now getting close to the end of the cycle. The non-client

[openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

Hi everyone, We have governance review under debate[1] that we need the community's help on. The debate is over what recommendation the TC should make to the Interop team on where the tests it uses for the OpenStack trademark program should be located, specifically those for the new add-on

[openstack-dev] [security] Security PTG Planning, x-project request for topics.

Hello All, I am seeking topics for the PTG from all projects, as this will be where we try out are new form of being a SIG. For this PTG, we hope to facilitate more cross project collaboration topics now that we are a SIG, so if your project has a security need / problem / proposal than please

[openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

Hello, we recently enabled the JSON logging to feed a Kibana dashboard and look at the logs with modern tooling. however it looks like in our Openstack Newton deployment that some information in the JSON files is missing. most important missing bit is the request-id, that we use to track an

Re: [openstack-dev] [all] [tc] Community Goals for Rocky -- privsep

Emilien Macchi wrote: > [...] > Thierry mentioned privsep migration (done in Nova and Zun). (action, > ping mikal about it). It's not "done" in Nova: Mikal planned to migrate all of nova-compute (arguably the largest service using rootwrap) to privsep during Queens, but AFAICT it's still work in

Re: [openstack-dev] [ceilometer] Retiring ceilometerclient

On 2018-01-11 01:48 AM, Thomas Bechtold wrote: > > It was at lease for openSUSE: > https://build.opensuse.org/package/show/Cloud:OpenStack:Pike/openstack-ceilometer ah, maybe just centos then... or i'm not searching the correct place. :) -- gord

Re: [openstack-dev] [qa] [api] [all] use gabbi and tempest with just YAML

On Thu, 4 Jan 2018, Chris Dent wrote: The gabbi-tempest plugin is responsible for getting authentication and service catalog information (using standard tempest calls) from keystone and creating a suite of environment variables (such as PLACEMENT_SERVICE and COMPUTE_BASE). I have a sample

Re: [openstack-dev] [vitrage] rules in vitrage_aggregated_state()

From: "Yujun Zhang (ZTE)" Date: Thursday, 11 January 2018 at 10:52 I have almost understood it thanks to your explanation. [Ifat] I liked the “almost” ;-) The confusion is mainly caused by the naming. I guess the main reason is that the scope evolves but the naming

Re: [openstack-dev] [vitrage] rules in vitrage_aggregated_state()

I have almost understood it thanks to your explanation. The confusion is mainly caused by the naming. I guess the main reason is that the scope evolves but the naming is not updated with it. For example 1. `vitrage_aggregated_state` actually applies for both resource state and alarm

[openstack-dev] [publiccloud-wg]Rocky PTG Planning Etherpad

Hi Team, I drafted an initial framework of the etherpad we could use for Rocky PTG in Dublin. You are more than welcomed to provide input: https://etherpad.openstack.org/p/publiccloud-wg-ptg-rocky -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Product Line Huawei

[openstack-dev] [mogan] Transitioning PTL role to Li Tao

Hi team, Due to my job responsibilities changed a while ago, I will transition the PTL role to Li Tao. If anyone has any concerns with this, please reach out to me. -- Best Regards, Zhenguo Niu __ OpenStack Development