Re: [openstack-dev] [tripleo] CI'ing ceph-ansible against TripleO scenarios

On Fri, Jan 26, 2018 at 7:29 AM, Giulio Fidente wrote: > On 01/26/2018 01:49 AM, Paul Belanger wrote: >> On Thu, Jan 25, 2018 at 04:22:56PM -0800, Emilien Macchi wrote: >>> Is there any plans to run TripleO CI jobs in ceph-ansible? >>> I know the project is on github but

Re: [openstack-dev] [tripleo][opendaylight puppet] failed to deploy odl master with latest opendaylight puppet

Hi Tim Can this be because of version bump? Moshe is using custom build ODL rpm based on master. -- Forwarded message -- From: Moshe Levi Date: Tue, Jan 30, 2018 at 6:41 PM Subject: [openstack-dev] [tripleo][opendaylight puppet] failed to deploy odl master

[openstack-dev] [keystone][nova][ironic][heat] Do we want a BM/VM room at the PTG?

At the last PTG we had some time on Monday and Tuesday for cross-project discussions related to baremetal and VM management. We don't currently have that on the schedule for this PTG. There is still some free time available that we can ask for[1]. Should we try to schedule some time for this?

Re: [openstack-dev] [requirement][cyborg]FFE - pyspdk requirement dependency

On 18-01-30 11:58:17, Thierry Carrez wrote: > We We wrote: > > The pyspdk is a important tool library [1] which  supports Cyborg SPDK > > driver [2] to manage the backend SPDK-base app, so we need to upload > > pyspdk into the pypi [3]  and then append 'pyspdk>=0.0.1’ item into > >

Re: [openstack-dev] [kolla] Policy regarding template customisation

Paul Bourke writes: > So I think everyone is in agreement that it should be option 2. I'm > leaning towards this also but I'm wondering how much of this makes > things easier for us as developers rather than operators. > How committed this are we in practice? For example, if we take >

[openstack-dev] [tripleo][opendaylight puppet] failed to deploy odl master with latest opendaylight puppet

Hi all, We are trying to test solution of the odl hw offload in tripleo. We have already merged the odl support for ovs hardware offload [1]. We are trying to test that everting is working with tripleo, but we get failure with jetty.xml.orig. For some reason it get configure like [2] and causing

Re: [openstack-dev] [kolla] Policy regarding template customisation

Sometimes there are features that require different containers to be deployed, or different config files to be generated. These are things that cannot be done simply through merging a fixed set of config files. nova_compute_virt_type is an example of such a variable - various non-config tasks

Re: [openstack-dev] [Release-job-failures][mistral][release][requirements] Pre-release of openstack/mistral-extra failed

On Mon, Jan 29, 2018 at 8:02 PM, Doug Hellmann wrote: > Excerpts from zuul's message of 2018-01-30 00:40:13 +: >> Build failed. >> >> - release-openstack-python >>

[openstack-dev] bug deputy report (week of Jan 22)

Hi neutrinos, Sorry for a bit late report of the bug deputy of last week. I think there are several number of interesting bugs reported. [Needs attention] https://bugs.launchpad.net/neutron/+bug/1745642 SG hybrid iptables driver and FWaaS OVS driver create overlapping conntrack zones MTU

[openstack-dev] [tripleo] Gate resets - do not recheck or approve any patch now

Please do not recheck or approve any patch now, we're having some gate issue, the team is working on it on #tripleo. Thanks, -- Emilien Macchi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [release][searchlight] problem with release job configurations

Hi Doug, Apologies, I was travelling all day yesterday. I've put up https://review.openstack.org/539231 to change the project config and made the release review (https://review.openstack.org/538321) depend on it. Thanks for the detailed information! Steve On 1/29/18, 6:21 PM, "Doug

Re: [openstack-dev] [nova][ceilometer] versioned notifications coverage

On Tue, Jan 30, 2018 at 10:19 AM, Matt Riedemann wrote: > > Gibi's burndown chart is here to see what's remaining: > > http://burndown.peermore.com/nova-notification/ > > And this is the list of what's already done: > >

[openstack-dev] PTG Dublin - Price Increase this Thursday

Hi everyone, We are four weeks out from the Dublin Project Teams Gathering (February 26 - March 2nd), and we are expecting the event to sell out! You have two more days to book your ticket at the normal price. We'll switch to last-minute price (USD $200) on Thursday, February 1st at 12 noon CT

[openstack-dev] [nova][osc] How to deal with add/remove fixed/floating CLIs after novaclient 10.0.0?

The 10.0.0 release of python-novaclient dropped some deprecated CLIs and python API bindings for the server actions to add/remove fixed and floating IPs: https://docs.openstack.org/releasenotes/python-novaclient/queens.html#id2 python-openstackclient was using some of those python API

Re: [openstack-dev] [tc] Technical Committee Status update, January 26th

On 1/26/2018 10:26 AM, Thierry Carrez wrote: == Rocky goals == We are in the final steps of selecting a set of community goals for Rocky. We need wide community input on which goals are doable and make the most sense! Please see the list of proposed goals and associated champions: * Storyboard

Re: [openstack-dev] [kolla] Policy regarding template customisation

On 30/01/18 12:54, Simon Leinen wrote: The perceived downside of (2) - or a perceived advantage of (1) - is that in an ideal world, (1) isolates us from the arcane configuration file details that the crazy devs of individual services come up with. In practice, it turns out that (a) those files

[openstack-dev] RHOSP 10 failed overcloud deployment

Hello, As previously stated in my previous mail on this list , I am trying to deploy OpenStack 10 using OpenStack Platform Director 10. I am using a bare-metal server with RedHat 7.4, on which I have created 3 VMs: 1st VM is the undercloud node, 2nd VM is the overcloud controller node and the

Re: [openstack-dev] [keystone] Keystone Team Update - Week of 22 January 2018

On 01/27/2018 01:16 PM, Colleen Murphy wrote: > # Keystone Team Update - Week of 22 January 2018 > > ## News > > ### Feature freeze > > This week was feature freeze and client freeze. While we approved > everything we cared about for this release on time, some CI issues > (some unexpected and

[openstack-dev] [nova][ceilometer] versioned notifications coverage

hi, we've had an open item to consume versioned notifications in ceilometer. the question that remains is: do all unversioned notifications have a versioned version or are there still some items missing? the blocker for us is that we can't consume both as then we'd end up duplicating data but

Re: [openstack-dev] [requirements][Blazar] FFE - add python-blazarclient in global-requirements

On 18-01-30 17:03:58, Masahito MUROI wrote: > Hi requirements team, > > This is a FFE request for adding python-blazarclient to > global-requirements.txt. Blazar team had release problems for updating the > blazarclient to pypo. > > Luckily, the problems are fixed and the client is published at

Re: [openstack-dev] [magnum] [ironic] Why does magnum create instances with ports using 'fixed-ips' ?

Any thoughts on this ? Greg. From: Greg Waines Reply-To: "openstack-dev@lists.openstack.org" Date: Friday, January 19, 2018 at 3:10 PM To: "openstack-dev@lists.openstack.org" Cc: "Nasir, Shoaib"

Re: [openstack-dev] [ptg] Dublin PTG proposed track schedule

Thierry Carrez wrote: > Here is the proposed pre-allocated track schedule for the Dublin PTG: > > https://docs.google.com/spreadsheets/d/e/2PACX-1vRmqAAQZA1rIzlNJpVp-X60-z6jMn_95BKWtf0csGT9LkDharY-mppI25KjiuRasmK413MxXcoSU7ki/pubhtml?gid=1374855307=true Following feedback I made small

Re: [openstack-dev] [release][searchlight] problem with release job configurations

Excerpts from McLellan, Steven's message of 2018-01-30 15:03:59 +: > Hi Doug, > > Apologies, I was travelling all day yesterday. I've put up > https://review.openstack.org/539231 to change the project config and made the > release review (https://review.openstack.org/538321) depend on it.

Re: [openstack-dev] [nova][ceilometer] versioned notifications coverage

On 1/30/2018 9:01 AM, gordon chung wrote: hi, we've had an open item to consume versioned notifications in ceilometer. the question that remains is: do all unversioned notifications have a versioned version or are there still some items missing? the blocker for us is that we can't consume both

Re: [openstack-dev] [keystone][nova][ironic][heat] Do we want a BM/VM room at the PTG?

On Tue, Jan 30, 2018 at 10:33 AM, Colleen Murphy wrote: > At the last PTG we had some time on Monday and Tuesday for > cross-project discussions related to baremetal and VM management. We > don't currently have that on the schedule for this PTG. There is still > some free

Re: [openstack-dev] [nova][ceilometer] versioned notifications coverage

On 1/30/2018 9:37 AM, Mathieu Gagné wrote: So I just discovered this documentation. It's awesome! Great job to all the ones involved! Now I wish we had the same in all projects. =) Maybe it's worth putting something into the community goals etherpad:

Re: [openstack-dev] [requirement][cyborg]FFE - pyspdk requirement dependency

> Hi, > I have modified and resubmitted pyspdk to the pypi. Please check it. > Thx, > Helloway > 在 2018年1月30日，下午12:52，We We > > 写道： > > Hi, > The pyspdk is a important tool library [1] which supports Cyborg SPDK driver > [2] to manage the

Re: [openstack-dev] [kolla] Policy regarding template customisation

On 30 January 2018 at 09:34, Joshua Harlow wrote: > I'm ok with #2, > > Though I would like to show an alternative that we have been experimenting > with that avoids the whole needs for a globals.yml and such files in the > first place (and feels more naturally inline with

Re: [openstack-dev] [requirement][cyborg]FFE - pyspdk requirement dependency

Excerpts from We We's message of 2018-01-31 01:54:04 +0800: > > Hi, > > > I have modified and resubmitted pyspdk to the pypi. Please check it. > > > Thx, > > > Helloway Is there a public source repository for the library somewhere? > > > 在 2018年1月30日，下午12:52，We We

Re: [openstack-dev] [tc] [all] TC Report 18-05

On 30/01/18 18:34, Chris Dent wrote: > > ## Today's Board Meeting > > I attended [today's Board > Meeting](https://wiki.openstack.org/wiki/Governance/Foundation/30Jan2018BoardMeeting) > > but it seems that according to the [transparency >

Re: [openstack-dev] [legal-discuss] [tc] [all] TC Report 18-05

On 01/30/2018 01:05 PM, Monty Taylor wrote: On 01/30/2018 12:53 PM, Graham Hayes wrote: On 30/01/18 18:34, Chris Dent wrote: ## Today's Board Meeting I attended [today's Board Meeting](https://wiki.openstack.org/wiki/Governance/Foundation/30Jan2018BoardMeeting) but it seems that

[openstack-dev] [tc] [all] TC Report 18-05

Linkified: https://anticdent.org/tc-report-18-05.html Your author has been rather ill, so this week's TC Report will be a bit abridged and mostly links. I'll try to return with more robust commentary next week. ## RDO Test Days dmsimard showed up in `#openstack-tc` channel to [provide some

Re: [openstack-dev] [nova][ceilometer] versioned notifications coverage

On 1/30/18, 11:17 AM, "Matt Riedemann" wrote: On 1/30/2018 9:37 AM, Mathieu Gagné wrote: > So I just discovered this documentation. It's awesome! Great job to > all the ones involved! > Now I wish we had the same in all projects. =) Maybe it's worth

Re: [openstack-dev] [nova][osc] How to deal with add/remove fixed/floating CLIs after novaclient 10.0.0?

On 01/30/2018 09:15 AM, Matt Riedemann wrote: The 10.0.0 release of python-novaclient dropped some deprecated CLIs and python API bindings for the server actions to add/remove fixed and floating IPs: https://docs.openstack.org/releasenotes/python-novaclient/queens.html#id2

Re: [openstack-dev] [kolla] Policy regarding template customisation

I'm ok with #2, Though I would like to show an alternative that we have been experimenting with that avoids the whole needs for a globals.yml and such files in the first place (and feels more naturally inline with how ansible works IMHO). So short explanation first; we have this yaml format

Re: [openstack-dev] [nova][ceilometer] versioned notifications coverage

On 1/30/2018 11:17 AM, Matt Riedemann wrote: Maybe it's worth putting something into the community goals etherpad: https://etherpad.openstack.org/p/community-goals I added the "Convert from legacy to versioned notifications" entry to keep the idea for the future. -- Thanks, Matt

Re: [openstack-dev] [keystone][nova][ironic][heat] Do we want a BM/VM room at the PTG?

+1 to Jim, I'm specifically interested in app creds and RBAC as I'd like to find a way to pass some of API access creds to the ironic deploy ramdisk, and it seems one of those could help. Let's discuss :) Cheers, On Tue, Jan 30, 2018 at 6:03 PM, Jim Rollenhagen wrote:

Re: [openstack-dev] [tc] [all] TC Report 18-05

On 30/01/18 18:34, Chris Dent wrote: > > Linkified: https://anticdent.org/tc-report-18-05.html > > Your author has been rather ill, so this week's TC Report will be a > bit abridged and mostly links. I'll try to return with more robust > commentary next week. > > ## RDO Test Days > > dmsimard

[openstack-dev] [I18n][PTL] PTL nomination for I18n

This is my announcement for re-candidacy as I18n PTL in Rocky Cycle. The time from the last cycle passed very fast. I had to manage all the things that a PTL expects. But we documented everything very well and I always had the full support of the team. I asked the team and it would continue to

Re: [openstack-dev] [nova][ceilometer] versioned notifications coverage

On 2018-01-30 10:19 AM, Matt Riedemann wrote: > Gibi's burndown chart is here to see what's remaining: > > http://burndown.peermore.com/nova-notification/ this answer far exceeded my expectations :) thanks! -- gord __

Re: [openstack-dev] [masakari] BUG in Masakari Installation and Procedure and/or Documentation

FYI ... I tried updating /etc/masakari/masakari.conf with [nova] nova_catalog_admin_info = compute:nova:publicURL and restarting masakari-engine and masakari-api ... but that didn’t work ... not sure why. So I manually changed the default nova_catalog_admin_info to ‘compute:nova:publicURL’ ...

Re: [openstack-dev] Race in FixedIP.associate_pool

> On Jan 29, 2018, at 16:45, Arun SAG wrote: > > If anyone is running into db race while running database in > master-slave mode with async replication, The bug has been identified > and getting fixed here > https://bugs.launchpad.net/oslo.db/+bug/1746116 Thanks for your

Re: [openstack-dev] [Release-job-failures][mistral][release][requirements] Pre-release of openstack/mistral-extra failed

Excerpts from Brad P. Crochet's message of 2018-01-30 08:16:52 -0500: > On Mon, Jan 29, 2018 at 8:02 PM, Doug Hellmann wrote: > > Excerpts from zuul's message of 2018-01-30 00:40:13 +: > >> Build failed. > >> > >> - release-openstack-python > >>

[openstack-dev] [tripleo] The Weekly Owl - 7th Edition

Note: this is the seventh edition of a weekly update of what happens in TripleO. The goal is to provide a short reading (less than 5 minutes) to learn where we are and what we're doing. Any contributions and feedback are welcome. Link to the previous version:

[openstack-dev] [nova][ironic] Tagging newton EOL

Hi All, When we tagged newton EOL in October there were in-flight reviews for nova and ironic that needed to land before we could EOL them. That work completed but I dropped the ball. So can we tag those last 2 repos? As in October a member of the infra team needs to do this *or* I can be

[openstack-dev] [glance] Q-3 milestone released

Glance 16.0.0.0b3 was released today, The tag was created at this commit: http://git.openstack.org/cgit/openstack/glance/commit/?id=631add1ba849eac67ecb36ea4c90b57a300a96fa which is dated Thu, 18 Jan 2018 12:09:11 + As you'll notice, that was about 2 weeks ago. Which prompts the question,

Re: [openstack-dev] [nova][ceilometer] versioned notifications coverage

On Wed, Jan 31, 2018 at 1:17 AM, Matt Riedemann wrote: > On 1/30/2018 9:37 AM, Mathieu Gagné wrote: > >> So I just discovered this documentation. It's awesome! Great job to >> all the ones involved! >> Now I wish we had the same in all projects. =) >> > > Maybe it's worth

Re: [openstack-dev] [nova][osc] How to deal with add/remove fixed/floating CLIs after novaclient 10.0.0?

On 1/30/2018 1:04 PM, Chris Friesen wrote: Is there a plan going forward to ensure that python-novaclient and OSC are on the same page as far as deprecating CLIs and API bindings? There is no official plan, no. The 10.0.0 novaclient release came out late. If there was more lead time, or if I

Re: [openstack-dev] [legal-discuss] [tc] [all] TC Report 18-05

On Tue, 30 Jan 2018, Monty Taylor wrote: On 01/30/2018 01:05 PM, Monty Taylor wrote: That is correct. As officers information published from Board members could be construed as "official" communication. The approach we've taken on this topic is that Board members refrain from publishing their

[openstack-dev] [manila][ptl] Stepping down as Manila PTL

After leading the Manila project for 5 years, it's time for me to step down. I feel incredibly proud of the project and the team that's worked to bring Manila from an idea at the Folsom design summit to the successful project is it today. Manila has reached a point of stability where I feel

[openstack-dev] [os-upstream-institute][ptg] Schedule Upstream Institute working sessions for the PTG

Hi Training Team, Good news, we are planning to have working sessions at the PTG! :) The challenging part is that all of us are involved in several activities which makes it difficult to schedule these. We are looking into co-locating some parts of the discussions with related sessions, like

Re: [openstack-dev] [kolla] Policy regarding template customisation

Yup, I am hoping to avoid all of these kinds of customizations if possible... But if we have to we'll probably have to make something like that. Or we'll just have to render out files for each host and serve it from the same REST endpoint, ya da ya da... -Josh Michał Jastrzębski wrote:

[openstack-dev] [FEMDC] Wed. 31 Jan - IRC Meeting 15:00 UTC

Dear all, A gentle reminder for our tomorrow meeting at 15:00 UTC A draft of the agenda is available at line 141, you are very welcome to add any item. https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2018

[openstack-dev] [blazar] [Release-job-failures] Release of openstack/blazar-nova failed

There was a failure with releasing blazar-nova. It would appear this has a dependency on nova, but nova is not in the required-projects. This will need to be corrected before we can complete the blazar-nova release.

[openstack-dev] [heat] [Release-job-failures] Tag of openstack/python-heatclient failed

We had a release job failure for python-heatclient. See below for details. This appears to be from the fact that this repo is configured with the release-notes-job [1], and it does have a couple of notes, but the release note infrastructure has not been set up for the repo. This is safe to

Re: [openstack-dev] [requirements][Blazar] FFE - add python-blazarclient in global-requirements

2018-01-30 16:53 GMT+01:00 Matthew Thode : > LGTM, +2 +2 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [heat] [Release-job-failures] Tag of openstack/heat-agents failed

We have another failure. Looks to be the same as the last one, caused by the release notes job being defined for the repo but the release note setup not being complete. - Forwarded message from z...@openstack.org - Date: Tue, 30 Jan 2018 22:43:14 + From: z...@openstack.org To:

Re: [openstack-dev] [I18n][PTL] PTL nomination for I18n

+1 Frank Kloeker 于2018年1月31日周三 上午3:08写道： > This is my announcement for re-candidacy as I18n PTL in Rocky Cycle. > > The time from the last cycle passed very fast. I had to manage all the > things that a PTL expects. But we documented everything very well and I > always had the

[openstack-dev] [all][Kingbird]Multi-Region Orchestrator

*Kingbird (The Multi Region orchestrator):* We are proud to announce kingbird is not only a centralized quota and resource-manager but also a Multi-region Orchestrator. *Use-cases covered:*- Admin can synchronize and periodically balance quotas across regions and can have a global view of

Re: [openstack-dev] [requirement][cyborg]FFE - pyspdk requirement dependency

We We wrote: > The pyspdk is a important tool library [1] which  supports Cyborg SPDK > driver [2] to manage the backend SPDK-base app, so we need to upload > pyspdk into the pypi [3]  and then append 'pyspdk>=0.0.1’ item into > ‘OpenStack/Cyborg/requirements.txt’ , so that  SPDK driver can be

Re: [openstack-dev] [kolla] Policy regarding template customisation

So I think everyone is in agreement that it should be option 2. I'm leaning towards this also but I'm wondering how much of this makes things easier for us as developers rather than operators. How committed this are we in practice? For example, if we take nova.conf[0], if we follow option 2,

Re: [openstack-dev] [requirements][Blazar] FFE - add python-blazarclient in global-requirements

Masahito MUROI wrote: > Hi requirements team, > > This is a FFE request for adding python-blazarclient to > global-requirements.txt.  Blazar team had release problems for updating > the blazarclient to pypo. > > Luckily, the problems are fixed and the client is published at pypi this > morning.

[openstack-dev] [requirements][Blazar] FFE - add python-blazarclient in global-requirements

Hi requirements team, This is a FFE request for adding python-blazarclient to global-requirements.txt. Blazar team had release problems for updating the blazarclient to pypo. Luckily, the problems are fixed and the client is published at pypi this morning. 1.

Re: [openstack-dev] [requirements][Blazar] FFE - add python-blazarclient in global-requirements

On Tue, Jan 30, 2018 at 4:18 PM, Thierry Carrez wrote: > Masahito MUROI wrote: > > Hi requirements team, > > > > This is a FFE request for adding python-blazarclient to > > global-requirements.txt. Blazar team had release problems for updating > > the blazarclient to

[openstack-dev] [charms] Dublin PTG devroom

Hi Team The Dublin PTG is not so far away now, so lets start on the agenda for our Devroom: https://etherpad.openstack.org/p/DUB-charms-devroom We had a fairly formal agenda of design related topics in Denver for the first day, and spent most of the second day mini-sprinting on various

Re: [openstack-dev] [kolla] Policy regarding template customisation

may be we could move those specific options / templates to sample overrides? Operators would move necessary pieces back to /etc/kolla/config . Just thinking of config plug-ins / third-party supported things. Thanks, Vlad On 01/30/2018 01:46 PM, Paul Bourke wrote: So I think everyone is in

Re: [openstack-dev] [masakari] BUG in Masakari Installation and Procedure and/or Documentation

Thanks Honjo, I reported bug in masakari Launchpad. https://bugs.launchpad.net/masakari/+bug/1746229 Greg. From: Rikimaru Honjo Reply-To: "openstack-dev@lists.openstack.org" Date: Tuesday, January 30, 2018 at 1:49 AM To: