Re: [openstack-dev] [kolla] Kolla is now stable:follows-policy project

Folks, The addition of this project maturity tag is a great achievement! This is one of many factors used by Operators to determine maturity of OpenStack projects. Glad to see our project’s persistence in this area paid off for the kolla and kolla-ansible deliverables. Good work all!

[openstack-dev] [chef] stable/ocata has been released

Ohai! We released the stable/ocata branch of the cookbooks today. For this release, we included updates to the following repos: cookbook-openstack-block-storage (Cinder) cookbook-openstack-common (shared configuration and libraries) cookbook-openstack-compute (Nova) cookbook-openstack-dashboard

[openstack-dev] [kolla] Kolla is now stable:follows-policy project

As of today Kolla got this tag. That doesn't really mean we change anything in our model as tag is given to projects which already follows rules of stable policy, but that makes it official:) Keep up with good work Kolla team! Cheers, Michal

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

On Fri, Aug 18, 2017 at 07:00:08PM +, gordon chung wrote: > apologies, I'm currently away on vacation (for a while) > > we can merge the stable/pike patch as it seems there are others dependent on > it. I don't believe it affects us either way. > > I don't see the auto patch that creates

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

apologies, I'm currently away on vacation (for a while) we can merge the stable/pike patch as it seems there are others dependent on it. I don't believe it affects us either way. I don't see the auto patch that creates tag so I guess we need to do it via releases project -- gord

Re: [openstack-dev] [TripleO][CI] FreeIPA Deployment

On Fri, Aug 18, 2017 at 8:34 AM, Harry Rybacki wrote: > Greetings Stackers, > > Recently, I brought up a discussion around deploying FreeIPA via > TripleO-Quickstart vs TripleO. This is part of a larger discussion > around expanding security related CI coverage for OpenStack.

[openstack-dev] [nova] [placement] [api] cache headers in placement service

(I put [api] in the subject tags because this might be of interest to a wider audience that cares about APIs.) Long ago and far away I made this bug: https://bugs.launchpad.net/nova/+bug/1632852 "placement api responses should not be cacehable" Today I've pushed up a WIP that

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

If the topics below interest you and you want to contribute to the discussion, feel free to join the next meeting: Time: Thursdays, 14:30-15:30 UTC Place: https://bluejeans.com/4113567798/ Full minutes: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting Topics discussed: We debated

[openstack-dev] The OpenStack Summit Sydney schedule is live!

Hi everyone, The main conference schedule for the upcoming OpenStack Summit in Sydney is now available! SCHEDULE: https://www.openstack.org/summit/sydney-2017/summit-schedule/ Log

Re: [openstack-dev] [tripleo] Adding new roles after upgrade is broken.

On 18.8.2017 17:25, Marios Andreou wrote: On Fri, Aug 18, 2017 at 4:22 PM, Jiří Stránský wrote: On 18.8.2017 13:18, Sofer Athlan-Guyot wrote: Hi, We may have missing packages when the user is adding a new role to its roles_data file and the base image is coming from

Re: [openstack-dev] [Octavia]Questions about octavia flavors spec

Hi, Flavors are intended to be setup by the operator/admin only. They capture details of the load balancer offering and any local specific configuration. The intent here is the flavor options and descriptions will be visible to end users, but creation/modification would require an admin role.

[openstack-dev] [TripleO][CI] FreeIPA Deployment

Greetings Stackers, Recently, I brought up a discussion around deploying FreeIPA via TripleO-Quickstart vs TripleO. This is part of a larger discussion around expanding security related CI coverage for OpenStack. A few months back, I added the ability to deploy FreeIPA via TripleO-Quickstart

Re: [openstack-dev] [tricircle-Service Function Chaining]

Hi Zhiyuan, Thank you very much, I'll join the next meeting! Meher Message: 3 Date: Thu, 17 Aug 2017 12:26:06 + From: Vega Cai To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re:

[openstack-dev] [tricircle-North South Networking via Direct Provider Networks]

Hello everyone, Still in the test phase of the scenarios proposed by the Tricircle documentation, I try to do "North South Networking via Direct Provider Networks" but I failed to start an instance with 2 NICs, apparently the Cirros image does not support this option by default. So I will add

Re: [openstack-dev] [tripleo] Adding new roles after upgrade is broken.

On Fri, Aug 18, 2017 at 4:22 PM, Jiří Stránský wrote: > On 18.8.2017 13:18, Sofer Athlan-Guyot wrote: > >> Hi, >> >> We may have missing packages when the user is adding a new role to its >> roles_data file and the base image is coming from previous version. >> >> The workflow

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

> > >> > > >> Can someone on the release team clarify this for us? > > > > > > That's correct the bit you're missing is cycle-with-intermediary > doesn't > > > have pre-releases (b{1,2,3},rc{1,2}) so when the ceilometer team feels > > > they have the code in shape for a release they'll tag that

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

Thierry Carrez wrote on 08/17/2017 03:35:20 AM: > From: Thierry Carrez > To: openstack-dev@lists.openstack.org > Date: 08/17/2017 03:37 AM > Subject: Re: [openstack-dev] [release] [telemetry] Ceilometer > stable/pike branch outlook > > Tony Breeds

Re: [openstack-dev] [barbican] [security] custodia @ PTG

Sure, I'll be there, see you guys on Thursday. On Thu, Aug 17, 2017 at 1:53 PM Luke Hinds wrote: > Hi Raildo, > > That's great news. Are you around next Thursday to jump on > #openstack-meeting-alt at 17:00 UTC? we can then go over some topics. > > @Dave, unless you prefer to

Re: [openstack-dev] [tripleo] Adding new roles after upgrade is broken.

On 18.8.2017 13:18, Sofer Athlan-Guyot wrote: Hi, We may have missing packages when the user is adding a new role to its roles_data file and the base image is coming from previous version. The workflow would be this one: - install newton - upgrade to ocata - add collectd to roles_data

Re: [openstack-dev] [tc] Technical Committee Status update, August 18th

Flavio Percoco wrote: > On 18/08/17 11:17 +0200, Thierry Carrez wrote: >> == Need for a TC meeting next Tuesday == >> >> I'll be off next week (therefore skipping this update next Friday). I >> don't think we have anything thoroughly blocked at this point requiring >> a meeting. However if

[openstack-dev] [ptg] Room schedule posted for Denver PTG

Hi everyone, The list of available rooms for the Project Teams Gathering in Denver is now finalized, with thematic inter-project rooms on Monday/Tuesday and team-specific meetings on Wednesday/Thursday/Friday. You can find the list (and explanation of what will be covered in each) on the event

[openstack-dev] [nova] placement/resource providers update 32

Placement Update 32 # Meta To avoid noise that nobody seems to care about, I've taken the liberty of not making reference here to reviews that have received no attention for more than a month. As we all have understandably limited attention, that seems to be the best. I do keep track of new

Re: [openstack-dev] [kolla] [tripleo] [openstack-ansible] [deployment] Collaboration at PTG

On 17/08/17 10:24 -0500, Major Hayden wrote: On 08/17/2017 09:30 AM, Emilien Macchi wrote: If you're working on Kolla / OpenStack-Ansible - please let us know if you have specific constraints on the schedule, so we can maybe block a timeslot in the agenda from now. We'll have a "Packaging" room

[openstack-dev] [tripleo] Adding new roles after upgrade is broken.

Hi, We may have missing packages when the user is adding a new role to its roles_data file and the base image is coming from previous version. The workflow would be this one: - install newton - upgrade to ocata - add collectd to roles_data and redeploy the stack For instance if one is adding

Re: [openstack-dev] [tc] Technical Committee Status update, August 18th

On 18/08/17 11:17 +0200, Thierry Carrez wrote: == Need for a TC meeting next Tuesday == I'll be off next week (therefore skipping this update next Friday). I don't think we have anything thoroughly blocked at this point requiring a meeting. However if something comes up and requires a meeting

[openstack-dev] [tc] Technical Committee Status update, August 18th

Hi! This is the weekly update on Technical Committee initiatives. You can find the full list of all open topics at: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee == Recently-approved changes == * Resolution to "Describe what upstream support means" [1][2] * Add

[openstack-dev] [docs][ptg] Doc team attendance

Hi everyone, I’ve updated the docs PTG etherpad with a few details: https://etherpad.openstack.org/p/denver-doc-PTG All those attending, could you please put your names/availability on the etherpad. Also – to those interested who cannot attend on the Mon-Tues for Queens planning sessions,

[openstack-dev] [release] Release countdown for week R-1, August 18-25

Welcome to our regular release countdown email! Development Focus - We are entering the last week before release week. Focus should be on producing the last Pike release candidates and intermediary releases, including updated translations and requirements updates. If your team

[openstack-dev] [octavia] octavia 1.0.0.0rc2 (pike)

Hello everyone, A new release candidate for octavia for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/octavia/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

[openstack-dev] [keystone] keystone 12.0.0.0rc2 (pike)

Hello everyone, A new release candidate for keystone for the end of the Pike cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/keystone/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be