Re: [openstack-dev] [stable][release] Last release date vs End of Life date

Thanks tony for raising up this, better document this in some place :-) 2017-06-28 16:51 GMT+08:00 Thierry Carrez : > Sean McGinnis wrote: > > On Tue, Jun 27, 2017 at 02:47:30PM -0400, Doug Hellmann wrote: > >> Excerpts from Tony Breeds's message of 2017-06-27 16:51:37

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On Wed, Jun 28, 2017 at 2:50 PM, Monty Taylor wrote: > On 06/28/2017 09:50 AM, Thierry Carrez wrote: > >> Hi everyone, >> >> Two weeks ago, as a result of a discussion at the Board+TC+UC workgroup >> working on "better communicating what is openstack", I started a >>

[openstack-dev] [octavia] Weekly meeting time and channel change

As discussed in today's octavia IRC meeting we are changing the meeting time and IRC channel for the weekly meeting. Starting next week we will now be meeting at 17:00 UTC on Wednesdays in channel #openstack-meeting. This is the same day, just three hours earlier to accommodate team members in

[openstack-dev] [glance] stepping down from glance core and other related groups

I am thankful to the community for such amazing experience over the past few years. For the changes required for glance personnel in the active cycle, I would like to step down from core as I cannot commit as much time upstream. I was hanging out to help in general but even that time commitment

Re: [openstack-dev] [glance] nominating Abhishek Kekane for glance core

This is a good move. I appreciate strong decisions as these are much needed now. On Fri, Jun 16, 2017 at 10:26 AM, Brian Rosmaita wrote: > I'm nominating Abhishek Kekane (abhishekk on IRC) to be a Glance core > for the Pike cycle. Abhishek has been around the

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

> > The central issue being discussed here is an issue of external > perception. It's hard for newcomers to the OpenStack world to see what > is a part of OpenStack and what's not. If you google "openstack machine > learning", the first hits are Cognitive and Meteos, and it's impossible > to tell

Re: [openstack-dev] [heat] Deprecate/Remove deferred_auth_method=password config option

Hi, > No, I think we still need this, because it is disabled by default - > this option allows you to enable defeating token expiry via trusts, My understanding for the current implementation is.. `deferred_auth_method=trust` triggers getting trust_id and storing it in the db.

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On Wed, Jun 28, 2017 at 5:50 PM, Monty Taylor wrote: > Such people are under the misguided impression that kicking cloudkitty out > of OpenStack will somehow cause Nova features to land quicker. I can't even > begin to express all of the ways in which it's wrong. So much

[openstack-dev] [QA] Meeting Thursday June 29th at 8:00 UTC

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, June 29th at 8:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_June_29th_2017_.280800_UTC.29

Re: [openstack-dev] [keystone] removing domain configuration upload via keystone-manage

Cool - I'm glad this is generating discussion. I personally don't see a whole lot of maintenance costs with `keystone-manage domain_config_upload`. I was parsing deprecation warnings in the code base and noticed it was staged for removal, but it wasn't clear when or why. It also wasn't very clear

Re: [openstack-dev] [tricircle]

Hi Meher, Welcome to join Tricircle! Both Keystone and Tricircle services are running under Apache, so if Keystone failed to start after enabling Tricircle, I guess there might be some problems of Apache configuration. You can check what services are enabled in Apache by listing this folder:

Re: [openstack-dev] [TripleO][keystone] Pt. 2 of Passing along some field feedback

On 06/28/2017 03:20 PM, Ben Nemec wrote: > > > On 06/28/2017 02:47 PM, Lance Bragstad wrote: >> >> >> On 06/28/2017 02:29 PM, Fox, Kevin M wrote: >>> I think everyone would benefit from a read-only role for keystone >>> out of the box. Can we get this into keystone rather then in the >>> various

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Hi ! I thought my perspective might be valuable as the author of a project that would likely end up being slashed: ARA [1]. In a nutshell, ARA provides easy and seamless Ansible reporting on playbook runs. It has nothing to do with OpenStack, to be honest: it doesn't require OpenStack to run,

Re: [openstack-dev] [tripleo] Queens PTG

On 06/28/2017 04:35 PM, Emilien Macchi wrote: > Hey folks, > > Let's start to prepare the next PTG in Denver. > > Here's the schedule draft: > https://docs.google.com/spreadsheets/d/1xmOdT6uZ5XqViActr5sBOaz_mEgjKSCY7NEWcAEcT-A/pubhtml?gid=397241312=true=gmail > We'll have a room Wednesday,

Re: [openstack-dev] [stable]requirements] Bootstrapiing requirements-stable-core

> > This has been out there for just under 1 week with only positive > feedback. So I'm going to jump the gun by 70mins and just go ahead and > do this. > > Welcome Dirk, Matthew and Sean! > > Yours Tony. Thanks Tony, I will do my best to help out in whatever way I can. Sean

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On Wed, Jun 28, 2017 at 11:50:34PM +, Jeremy Stanley wrote: > Indeed, that's a bummer. I hadn't noticed it until you pointed it > out and assumed it had made it into the 2.13 series. Well, we're > planning to look at logistics for a 2.14 upgrade soon once 2.13 is > (hopefully!) in production,

Re: [openstack-dev] [openstack-helm] Announcing OpenStack-Helm as a hosted project

This is a amazing news. Let’s make it super great together. :)  Jaesuk Ahn, Ph.D.  Open System Lab, SK Telecom  . OpenStack Korea User Group Coordinator &  . Cloud Native Computing Seoul Meetup Organizer  On 2017년 6월 29일 (목) at 오전 9:31 Ihor Dvoretskyi < mailto:Ihor Dvoretskyi

Re: [openstack-dev] [stable]requirements] Bootstrapiing requirements-stable-core

On Thu, Jun 22, 2017 at 11:48:09AM +1000, Tony Breeds wrote: > Hi All, > Recently it's been clear that we need a requirements-stable team. > Until npw that's been handled by the release managers and the > stable-maint-core team. > > With the merge of [1] The have the groundwork for that

Re: [openstack-dev] [openstack-helm] Announcing OpenStack-Helm as a hosted project

Amazing news, my congratulations! I'm excited to see how Kubernetes+OpenStack collaboration moves forward. On Thu, Jun 29, 2017 at 3:07 AM, Steve Wilkerson wrote: > Hello everyone! > > > Now that Boston has come and gone, we'd like to formally announce that >

[openstack-dev] [openstack-helm] Announcing OpenStack-Helm as a hosted project

Hello everyone! Now that Boston has come and gone, we'd like to formally announce that OpenStack-Helm is now a hosted project on OpenStack infra. We received a great deal of positive feedback in Boston, and we're excited to see what's next for both OpenStack and Kubernetes together. We'd like

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On 2017-06-28 13:21:46 +1000 (+1000), Tony Breeds wrote: > On Tue, Jun 27, 2017 at 08:59:27PM +, Jeremy Stanley wrote: > > > Fingers crossed that we'll be able to switch to Gerrit 2.13 soon and > > resume that much needed development effort. > > This looks to have landed in 2.14[1] :( I

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Thierry Carrez writes: > Removing the root cause would be a more radical move: stop offering > hosting to non-OpenStack projects on OpenStack infrastructure > altogether. We originally did that for a reason, though. The benefits of > offering that service are: > > 1- it

[openstack-dev] [octavia] Webex to discuss Octavia L3 active/active spec

As discussed in the weekly Octavia irc meeting, I am scheduling a Webex and follow-up meeting to discuss the L3 active/active spec (https://review.openstack.org/#/c/453005/). The goal of this meeting is to finalize the details around the spec in order to get it accepted for the Pike release.

Re: [openstack-dev] [Neutron] Journey to running functional job with Python 3

Hello, I just added fullstack python35 job in project-config Patch to add testing in tox.ini is ready to review also: https://review.openstack.org/#/c/477681 I also wrote some notes in Your etherpad and made first patch to fix fullstack tests: https://review.openstack.org/#/c/478652 I hope it

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 06/28/2017 09:50 AM, Thierry Carrez wrote: Hi everyone, Two weeks ago, as a result of a discussion at the Board+TC+UC workgroup working on "better communicating what is openstack", I started a thread[1] about moving away from big tent terminology. The thread went in a lot of directions,

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 06/28/2017 01:48 PM, Clay Gerrard wrote: On Wed, Jun 28, 2017 at 7:50 AM, Thierry Carrez > wrote: 2- it lets us host things that are not openstack but which we work on (like abandoned Python libraries or GPL-licensed things)

Re: [openstack-dev] [keystone] removing domain configuration upload via keystone-manage

++ to what colleen said. I've always preferred using the file-backed approach. I think we deprecated it for completeness and to only have a single tool for configuring LDAP-backed domains. If it's tested well enough and not much effort to support then we should keep it around as an alternative

Re: [openstack-dev] [keystone] removing domain configuration upload via keystone-manage

> > On Wed, Jun 28, 2017 at 2:00 AM, Lance Bragstad > wrote: > >> Hi all, >> >> Keystone has deprecated the domain configuration upload capability >> provided through `keystone-manage`. We discussed it's removal in today's >> meeting [0] and wanted to send a quick note to the

Re: [openstack-dev] [TripleO] Pt. 2 of Passing along some field feedback

On 06/28/2017 03:03 PM, Steven Hardy wrote: On Wed, Jun 28, 2017 at 8:06 PM, Ben Nemec wrote: A few weeks later than I had planned, but here's the other half of the field feedback I mentioned in my previous email: * They very emphatically want in-place upgrades to

Re: [openstack-dev] [storyboard][infra][docs] Report a bug and storyboard

Hi Andreas, On 2017-06-28 07:33, Andreas Jaeger wrote: Hi Storyboard team, the openstackdocstheme has a "Report a bug" feature, where you can click on the Bug icon and get a link to project's bug area in launchpad together with information about the documentation (bug tag, git URL of build,

Re: [openstack-dev] [TripleO][keystone] Pt. 2 of Passing along some field feedback

On 06/28/2017 02:47 PM, Lance Bragstad wrote: On 06/28/2017 02:29 PM, Fox, Kevin M wrote: I think everyone would benefit from a read-only role for keystone out of the box. Can we get this into keystone rather then in the various distro's? Yeah - I think that would be an awesome idea. John

[openstack-dev] [tc][swg] The future of the Stewardship Working Group

Hello Stackers, As many of you know, I recently took a job with Spotify in New York City. I spoke with many folks about the transition plans when I was at the Boston Forum, and we all decided that it would make sense for me to get settled into the new position before deciding what amounts of time

Re: [openstack-dev] [TripleO] Pt. 2 of Passing along some field feedback

On Wed, Jun 28, 2017 at 8:06 PM, Ben Nemec wrote: > A few weeks later than I had planned, but here's the other half of the field > feedback I mentioned in my previous email: > > * They very emphatically want in-place upgrades to work when moving from > non-containerized to

Re: [openstack-dev] [TripleO][keystone] Pt. 2 of Passing along some field feedback

On 06/28/2017 02:29 PM, Fox, Kevin M wrote: > I think everyone would benefit from a read-only role for keystone out of the > box. Can we get this into keystone rather then in the various distro's? Yeah - I think that would be an awesome idea. John Garbutt had some good work on this earlier in

Re: [openstack-dev] [TripleO][keystone] Pt. 2 of Passing along some field feedback

I think everyone would benefit from a read-only role for keystone out of the box. Can we get this into keystone rather then in the various distro's? Thanks, Kevin From: Ben Nemec [openst...@nemebean.com] Sent: Wednesday, June 28, 2017 12:06 PM To:

Re: [openstack-dev] [keystone] removing domain configuration upload via keystone-manage

That sounds like reason enough to bump the removal of it to Queens or later. This was also discussed in IRC today [0]. We've decided to move forward with the following steps: - Deprecate the ability to have file-backed domain configuration since removing the ability to upload domains via

[openstack-dev] [TripleO] Pt. 2 of Passing along some field feedback

A few weeks later than I had planned, but here's the other half of the field feedback I mentioned in my previous email: * They very emphatically want in-place upgrades to work when moving from non-containerized to containerized. I think this is already the plan, but I told them I'd make sure

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On Wed, Jun 28, 2017 at 7:50 AM, Thierry Carrez wrote: > It's hard for newcomers to the OpenStack world to see what > is a part of OpenStack and what's not. Just an aside, this Perception problems works in our favor sometimes too. I know in the past some BigCorp

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On Wed, Jun 28, 2017 at 7:50 AM, Thierry Carrez wrote: > > 2- it lets us host things that are not openstack but which we work on > (like abandoned Python libraries or GPL-licensed things) in a familiar > environment > > Do we no longer think openstack hosted infra holds a

[openstack-dev] [keystone] office-hours tag

Hey all, I've created a new official tag, 'office-hours' [0]. If you're reviewing or triaging bugs and come across one that would be a good fit for us to tackle during office hours, please feel free to tag it. I was maintaining lists locally, and I'm sure you were, too. This should help reduce

[openstack-dev] [doc[ptls] Doc meeting

Hey everyone, The docs meeting will continue in #openstack-meeting as scheduled (Thursday, 29th of June at 16:00 UTC). There will be no official agenda, I am opening up this meeting for any docs liaisons and PTLs to come and chat about the docs migration and any questions they may have. The

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 06/28/2017 01:07 PM, Clint Byrum wrote: The root cause of all of this until now has been not really knowing what OpenStack is. The visioning recently done was a great step in the right direction toward this. I would like to make sure that we acknowledge this while we address symptoms of the

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

This message makes a bunch of salient, valid points, none of which I wish to directly address. However, on the whole, I think the analysis stops short of pushing through to a root cause, and thus, the solution proposed is entirely focused on symptoms. The root cause of all of this until now has

Re: [openstack-dev] [octavia] fail to plug vip to amphora

Hi Yipei, I have meant to add this as a config option, but in the interim you can do the following to disable the automatic cleanup by disabling the revert flow in taskflow: octavia/common/base_taskflow.py line 37 add “never_resolve=True,” to the engine load parameters. Michael

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Anita Kuno wrote: > On 2017-06-28 10:50 AM, Thierry Carrez wrote: >> For (1) we could have an "onboarding" project team that would help >> incoming projects through the initial steps of becoming an openstack >> project. The team would act as an umbrella team, an experimental area >> for projects

[openstack-dev] [tripleo][kolla][puppet] DLRN maintenance on June 29, 8:00 AM UTC

This is also of interest for CI jobs in TripleO, kolla and puppet-openstack-integration. Javier - Forwarded Message - Hi, We need to run some maintenance activities on the DLRN public instance on June 29, starting at 8:00 UTC time (10:00 CET). As a result, the repositories hosted by

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On 2017-06-28 10:50 AM, Thierry Carrez wrote: For (1) we could have an "onboarding" project team that would help incoming projects through the initial steps of becoming an openstack project. The team would act as an umbrella team, an experimental area for projects that have some potential to

Re: [openstack-dev] [kolla][kolla-ansible] Proposing Surya (spsurya) for core

On Wed, Jun 14, 2017 at 9:16 PM, Michał Jastrzębski wrote: > Hello, > > With great pleasure I'm kicking off another core voting to > kolla-ansible and kolla teams:) this one is about spsurya. Voting will > be open for 2 weeks (till 28th Jun). > > Consider this mail my +1 vote,

Re: [openstack-dev] [octavia] fail to plug vip to amphora

Hi, Ganpat, Thanks a lot for your comments. I do not really understand your solution. Do you mean I need to create a dummy file and verify it in the amphora? Best regards, Yipei __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

On Wed, Jun 28, 2017 at 3:50 PM Thierry Carrez wrote: > Removing the root cause would be a more radical move: stop offering > hosting to non-OpenStack projects on OpenStack infrastructure > altogether. [...] I think this is the right solution for OpenStack. In

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

Excerpts from Andreas Jaeger's message of 2017-06-28 08:45:47 +0200: > For those migrating from oslosphinx to openstackdocstheme, I strongly > advise to follow the docs for openstackdocstheme 1.11 on how to set it up: > > https://docs.openstack.org/openstackdocstheme/latest/ > > Andreas Another

Re: [openstack-dev] [masakari][nova] Allow evacuation of instances in resized state

On 06/28/2017 05:50 AM, Kekane, Abhishek wrote: In masakari, we are setting an instance to an error state if the vmstate is resized before evacuating it to a new host. Arguably the instance should be set to an error state as soon as you notice that the compute node is down. Once an

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

Excerpts from Alexandra Settle's message of 2017-06-23 12:09:41 +: > Hi everyone, > > This morning (afternoon) the specification for the documentation migration > was merged. Thanks to all that took time to review :) > > You can now view here in all its glory: >

Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Excerpts from Thierry Carrez's message of 2017-06-28 16:50:01 +0200: > Hi everyone, > > Two weeks ago, as a result of a discussion at the Board+TC+UC workgroup > working on "better communicating what is openstack", I started a > thread[1] about moving away from big tent terminology. The thread

Re: [openstack-dev] [nova] bug triage experimentation

On 06/28/2017 10:33 AM, Ben Nemec wrote: > > > On 06/23/2017 11:52 AM, Sean Dague wrote: >> The Nova bug backlog is just over 800 open bugs, which while >> historically not terrible, remains too large to be collectively usable >> to figure out where things stand. We've had a few recent issues

Re: [openstack-dev] realtime kvm cpu affinities

On 06/28/2017 03:34 AM, Sahid Orentino Ferdjaoui wrote: On Tue, Jun 27, 2017 at 04:00:35PM +0200, Henning Schild wrote: As far as i remember it was not straight forward to get two novas onto one host in the older release, i am not surprised that causing trouble with the update to mitaka. If

[openstack-dev] [all][tc] How to deal with confusion around "hosted projects"

Hi everyone, Two weeks ago, as a result of a discussion at the Board+TC+UC workgroup working on "better communicating what is openstack", I started a thread[1] about moving away from big tent terminology. The thread went in a lot of directions, including discussing GitHub mirroring strategy, what

Re: [openstack-dev] [kolla][kolla-ansible] Proposing Surya (spsurya) for core

Aaaand it's done. Congrats Surya and welcome to core team! On 27 June 2017 at 19:56, zhubingbing wrote: > > > > +1 > >>> -Original Message- >>> From: Michał Jastrzębski [mailto:inc...@gmail.com] >>> Sent: Wednesday, June 14, 2017 10:46 PM >>> To: OpenStack

[openstack-dev] [tripleo] Queens PTG

Hey folks, Let's start to prepare the next PTG in Denver. Here's the schedule draft: https://docs.google.com/spreadsheets/d/1xmOdT6uZ5XqViActr5sBOaz_mEgjKSCY7NEWcAEcT-A/pubhtml?gid=397241312=true=gmail We'll have a room Wednesday, Thursday and Friday. We'll probably finish by end of Friday

[openstack-dev] [telemetry][ceilometer]Cannot get vmware virtual machine's disk usage rate via vsphere inspector

HI, all Today I try to add a new pollster plugin in ceilometer-agent-compute to collect vmware virtual machines's disk usage rate. After researched the vmware docs: https://www.vmware.com/support/developer/converter- sdk/conv61_apireference/disk_counters.html#usage I think I can call the vsphere

Re: [openstack-dev] [nova] bug triage experimentation

On 06/23/2017 11:52 AM, Sean Dague wrote: The Nova bug backlog is just over 800 open bugs, which while historically not terrible, remains too large to be collectively usable to figure out where things stand. We've had a few recent issues where we just happened to discover upgrade bugs filed 4

Re: [openstack-dev] [tc][all] Move away from meeting channels

On 2017-06-28 11:41:50 +0200 (+0200), Flavio Percoco wrote: > On 27/06/17 18:22 +, Jeremy Stanley wrote: [...] > >By lurking in official meeting channels I'm often able to jump > >straight into a discussion when someone asks me a question in a > >meeting I wouldn't normally attend but am

Re: [openstack-dev] [Watcher] handle multiple data sources in watcher

Vincent, Thanks for your comment. Here is my understanding of the problem: 1. cloud operators will choose one particular metrics monitoring stack/source but not multiple of them on the same target; 2. in the same cloud, it is possible that some compute are monitored with Monasca, some computes

Re: [openstack-dev] diskimage builder works for trusty but not for xenial

PS PS Unfortunately os-refresh-config is not working also for centos7 if I create a new image today and then a new centos 7 instance on ocata. Last centos7 image where os-refresh-config works fine has been created with diskimage-builder on 23 of March 2017. Please, what is changed meanwhile ?

[openstack-dev] [tricircle]

Hello everyone, I introduce myself; Meher Hihi; I am doing my internship at Orange Labs Networks Lannion-France for the diploma of computer network and telecommunications engineer. I am working on innovative distribution solutions for the virtualization infrastructure of the network functions

Re: [openstack-dev] [OpenStack-docs] [Openstack-operators][dev][doc] Operations Guide future

Hi Mario, Just so everyone is aware that you’re offering assistance, I’ve re-added the ML back in. Definitely appreciate the help! The only schedule is that it is delivered by the Pike release. You can see the details and dates here: https://releases.openstack.org/pike/schedule.html Thank

[openstack-dev] [masakari][nova] Allow evacuation of instances in resized state

Hi Devs, Masakari [1] provides Virtual Machine High Availability (VMHA) service for OpenStack clouds by automatically recovering the KVM-based Virtual Machine(VM)s from failure events such as VM process down, provisioning process down, and nova-compute host failure. It also provides API

Re: [openstack-dev] diskimage builder works for trusty but not for xenial

PS I generated a centos7 and a xenial image with the same disk image builder version/procedure but when I create a xenial instance on ocata, running os-refresh-config it reports the following output: root@nuovaxenial:~# os-refresh-config [2017-06-28 10:32:28,104] (os-refresh-config) [INFO]

Re: [openstack-dev] [ironic] Routed Networks, flat driver and physical network awareness

Thanks for the interest in Ironic routed networks support! I think some of our on-going work should solve the issues you’ve described here. On the ironic service side the major feature required for routed networks support is physical network awareness, patches for this are progressing well and

Re: [openstack-dev] [octavia] fail to plug vip to amphora

Hello Yipei, "*octavia.amphorae.backends.agent.api_server.listener [-] Failed to verify haproxy file: Command '['haproxy', '-c', '-L', 'NK20KVuD6oi5NrRP7KOVflM* *3MsQ', '-f', '/var/lib/octavia/bca2c985-471a-4477-8217-92fa71d04cb7/haproxy.cfg.new']' returned non-zero exit status 1*" Verification

Re: [openstack-dev] [octavia] fail to plug vip to amphora

Hi, Michael, Thanks for your help. I have already created a load balancer successfully, but failed creating a listener. The detailed errors of amphora-agent and syslog in the amphora are as follows. In amphora-agent.log: [2017-06-28 08:54:12 +] [1209] [INFO] Starting gunicorn 19.7.0

Re: [openstack-dev] [tc][all] Move away from meeting channels

On 27/06/17 18:22 +, Jeremy Stanley wrote: On 2017-06-26 15:27:21 +0200 (+0200), Thierry Carrez wrote: Flavio Percoco wrote: > [...] > Not being able to easily ping someone during a meeting is kind > of a bummer but I'd argue that assuming someone is in the > meeting channel and available

Re: [openstack-dev] [openstack-ansible][neutron][designate] Failure trying to set dns_domain from command line

On 27/06/17 23:53, Lawrence J. Albinson wrote: > Hi Graham, > > As ever, many thanks for clarifying that. And I shall put in a feature > request as you suggest. > > In the meantime, presumably the missing pieces that I need are those > described in: > >

Re: [openstack-dev] [keystone] removing domain configuration upload via keystone-manage

On the TripleO side we use the file based approach. Using the API would have been easier to orchestrate (no need for reloads/restarts) but it's not available yet in puppet-keystone. On Wed, Jun 28, 2017 at 2:00 AM, Lance Bragstad wrote: > Hi all, > > Keystone has deprecated

Re: [openstack-dev] realtime kvm cpu affinities

On Tue, Jun 27, 2017 at 04:00:35PM +0200, Henning Schild wrote: > Am Tue, 27 Jun 2017 09:44:22 +0200 > schrieb Sahid Orentino Ferdjaoui : > > > On Mon, Jun 26, 2017 at 10:19:12AM +0200, Henning Schild wrote: > > > Am Sun, 25 Jun 2017 10:09:10 +0200 > > > schrieb Sahid

[openstack-dev] [ironic] Routed Networks, flat driver and physical network awareness

Hi, With the following Neutron patches recently merged, it is now possible to provide DHCP service to instances on remote routed networks that have a dhcp forwarder configured. https://review.openstack.org/#/c/459861/ https://review.openstack.org/#/c/468744/  https://review.openstack.org/476477

Re: [openstack-dev] diskimage builder works for trusty but not for xenial

Hello, I said that disk image builder works fine for xenial, but also if it is able to create the image, instances not working with heat softwaredeployment: os-collect-config and os-refresh-config give a lot of errors. This not happens with centos7. Regards Ignazio 2017-06-22 8:00 GMT+02:00

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Cool, thanks Dougal! Renat Akhmerov @Nokia On 28 Jun 2017, 15:21 +0700, Dougal Matthews , wrote: > > On 23 June 2017 at 12:52, Thierry Carrez wrote: > > > Dougal Matthews wrote: > > > >>     We have been trying to break the requirement on mistral (from

Re: [openstack-dev] [stable][release] Last release date vs End of Life date

Sean McGinnis wrote: > On Tue, Jun 27, 2017 at 02:47:30PM -0400, Doug Hellmann wrote: >> Excerpts from Tony Breeds's message of 2017-06-27 16:51:37 +1000: >>> Hi all, >>> Up 'til now we haven't set a last release date for a stable branch >>> approaching end of life. It seems like formalizing

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 23 June 2017 at 12:52, Thierry Carrez wrote: > Dougal Matthews wrote: > >> We have been trying to break the requirement on mistral (from > >> tripleo-common) but it is proving to be harder than expected. We are > >> really doing some nasty things, but I wont

Re: [openstack-dev] [watcher] Nominate Yumeng Bao to the core team

+1 On 27/06/17 15:45, ? ? (Alexander Chadin) wrote: Hi watcher folks, I'd like to nominate Yumeng Bao to the core team. She has made a lot of contributions including specifications, features and bug fixes. Yumeng has attended PTG and Summit with her presentation related to the

Re: [openstack-dev] [ptls][all][tc][docs] Documentation migration spec

For those migrating from oslosphinx to openstackdocstheme, I strongly advise to follow the docs for openstackdocstheme 1.11 on how to set it up: https://docs.openstack.org/openstackdocstheme/latest/ Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH,

Re: [openstack-dev] [tripleo] OpenStack manuals project migration - Progress for TripleO

On 2017-06-27 22:54, Emilien Macchi wrote: > Full background, context and details can be read here: > http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html > > TL;DR: there is a massive cross-project effort which aims to migrate > documentations out of a central

[openstack-dev] [storyboard][infra][docs] Report a bug and storyboard

Hi Storyboard team, the openstackdocstheme has a "Report a bug" feature, where you can click on the Bug icon and get a link to project's bug area in launchpad together with information about the documentation (bug tag, git URL of build, date, SHA, extra text). How can this be done with

Re: [openstack-dev] [stable][release] Last release date vs End of Life date

On Tue, Jun 27, 2017 at 02:47:30PM -0400, Doug Hellmann wrote: > Excerpts from Tony Breeds's message of 2017-06-27 16:51:37 +1000: > > Hi all, > > Up 'til now we haven't set a last release date for a stable branch > > approaching end of life. It seems like formalizing that would be a good > >