Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

2017-07-10 Thread Ed Leafe
On Jul 10, 2017, at 5:06 AM, Mikhail Fedosin wrote: > Given all the advantages and features of Glare, I believe that it can become > the successful drop-in replacement. Can you clarify this? Let’s assume I have a decent-sized deployment running Glance. If I were to remove

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread James Slagle
On Mon, Jul 10, 2017 at 2:54 PM, Giulio Fidente wrote: > On 07/10/2017 07:06 PM, James Slagle wrote: >> On Mon, Jul 10, 2017 at 11:19 AM, Giulio Fidente wrote: >>> splitstack though requires changes in how the *existing* openstack >>> services are

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

2017-07-10 Thread Monty Taylor
On 07/10/2017 04:31 PM, Mikhail Fedosin wrote: Thank you for asking this! It's really very important and interesting, so I'm going to explain those things more detailed. First, when we designed Glare, we kept in mind the compatibility with Glance, and I can tell that Glance data from the

Re: [openstack-dev] [congress] Using congress to improve the consistency of configuration files.

2017-07-10 Thread Tim Hinrichs
Hi Valentin, Sounds like an interesting use case. Typically we've focused on information available through APIs. In this case the information would be pulled off the disks of the machines running each service. Here's the info for our weekly meeting. If you can make that, it's a good place to

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

2017-07-10 Thread Joshua Harlow
Ed Leafe wrote: On Jul 10, 2017, at 5:06 AM, Mikhail Fedosin > wrote: Given all the advantages and features of Glare, I believe that it can become the successful drop-in replacement. Can you clarify this? Let’s assume I have a decent-sized

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

2017-07-10 Thread Chris Dent
On Mon, 10 Jul 2017, Monty Taylor wrote: However, as you said, conceptually the calls are very similar so making an API controller that can be registered in the catalog as "image" should be fairly easy to do, no? In general I think we should always keep this strategy in mind when we are

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

2017-07-10 Thread Kekane, Abhishek
Hi Saverio, Thank you for reply. Currently we are using Ocata release for Openstack. Please let me know if you get any update. Thank you, Abhishek -Original Message- From: Saverio Proto [mailto:ziopr...@gmail.com] Sent: Monday, July 10, 2017 12:52 PM To: Kekane, Abhishek Cc:

[openstack-dev] [l2gw] Adding TripleO CI jobs as part of networking-l2gw checks

2017-07-10 Thread Ricardo Noriega De Soto
Please L2GWers, review the following patch: https://review.openstack.org/#/c/480641/ It seems we can benefit from TripleO coverage to have L2GW service plugin deployed in production-like deployments. Cheers -- Ricardo Noriega Senior Software Engineer - NFV Partner Engineer | Office of

Re: [openstack-dev] [tripleo] proposing Alex Schultz tripleo-core in all projects

2017-07-10 Thread Julie Pichon
On 7 July 2017 at 18:39, Emilien Macchi wrote: > Alex has demonstrated high technical and community skills in TripleO - > where he's already core on THT, instack-undercloud, and puppet-tripleo > - but also very involved in other repos. > I propose that we extend his core

[openstack-dev] [nova] notification update week 28

2017-07-10 Thread Balazs Gibizer
Hi, Here is the status update / focus setting mail about notification work for week 28. Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1684860 Versioned server notifications don't include updated_at Takashi's fix needs a second +2 https://review.openstack.org/#/c/475276/ [Low]

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread Giulio Fidente
On 07/10/2017 03:19 PM, Steven Hardy wrote: > On Fri, Jul 7, 2017 at 6:50 PM, James Slagle wrote: [...] > Yeah, I think the first step is to focus on a clean "split stack" > model where the nodes/networks etc are still deployed via heat, then > ansible handles the

Re: [openstack-dev] [tripleo] proposing Alex Schultz tripleo-core in all projects

2017-07-10 Thread Ben Nemec
+1 for sure On 07/07/2017 12:39 PM, Emilien Macchi wrote: Alex has demonstrated high technical and community skills in TripleO - where he's already core on THT, instack-undercloud, and puppet-tripleo - but also very involved in other repos. I propose that we extend his core status to all

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-10 Thread Doug Hellmann
Excerpts from sfinucan's message of 2017-07-10 17:20:37 +0100: > On Fri, 2017-07-07 at 15:58 +0100, sfinu...@redhat.com wrote: > > tl;dr: pbr's 'build_spinx' derivative is broken again, and we want to just > > remove the feature at this point. However, this is going to necessitate some > >

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread Emilien Macchi
On Mon, Jul 10, 2017 at 6:19 AM, Steven Hardy wrote: [...] > 1. How to perform end-to-end configuration via ansible (outside of > heat, but probably still using data and possibly playbooks generated > by heat) I guess we're talking about removing Puppet from TripleO and use

Re: [openstack-dev] [tc] Status update, July 7th

2017-07-10 Thread Emilien Macchi
On Fri, Jul 7, 2017 at 1:19 AM, Thierry Carrez wrote: [...} > Who is up for discussing those items at our usual meeting slot > time on Tuesday ? Yes, count on me. [...] Thanks, -- Emilien Macchi __

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread James Slagle
On Mon, Jul 10, 2017 at 11:37 AM, Lars Kellogg-Stedman wrote: > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle wrote: >> >> There are also some ideas forming around pulling the Ansible playbooks >> >> and vars out of Heat so that they can be rerun (or run

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread Alex Schultz
On Fri, Jul 7, 2017 at 11:50 AM, James Slagle wrote: > I proposed a session for the PTG > (https://etherpad.openstack.org/p/tripleo-ptg-queens) about forming a > common plan and vision around Ansible in TripleO. > > I think it's important however that we kick this

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread Giulio Fidente
On 07/10/2017 07:06 PM, James Slagle wrote: > On Mon, Jul 10, 2017 at 11:19 AM, Giulio Fidente wrote: >> On 07/10/2017 03:19 PM, Steven Hardy wrote: >>> On Fri, Jul 7, 2017 at 6:50 PM, James Slagle wrote: >> >> [...] >> >>> Yeah, I think the first

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

2017-07-10 Thread Mauricio Lima
+1 2017-06-28 13:07 GMT-03:00 Swapnil Kulkarni : > 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.

[openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration startin

2017-07-10 Thread Doug Hellmann
According to the dashboard, it looks like we still have almost 100 repositories with documentation that have no patches with the doc-migration topic, indicating that they have not started moving content or updating the theme. I have tried to tag those teams in the subject, but I may have missed

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread Michał Jastrzębski
Hey, I'll just throw a grenade (pun intended) into your discussion - sorry! How about kolla-kubernetes? State awareness is done by kubernetes, it's designed for containers and we already have most of services ready and we'll be running ansible inside containers on top of k8s, for all the things

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-10 Thread Anne Gentle
On Mon, Jul 10, 2017 at 12:20 PM, wrote: > On Fri, 2017-07-07 at 15:58 +0100, sfinu...@redhat.com wrote: >> tl;dr: pbr's 'build_spinx' derivative is broken again, and we want to just >> remove the feature at this point. However, this is going to necessitate some >>

Re: [openstack-dev] [tripleo] weekly meetings on #tripleo

2017-07-10 Thread Michele Baldessari
On Mon, Jul 10, 2017 at 11:36:03AM -0230, Brent Eagles wrote: > +1 for giving it a try. Agreed. > > On Wed, Jul 5, 2017 at 2:26 PM, Emilien Macchi wrote: > > > After reading http://lists.openstack.org/pipermail/openstack-dev/2017- > > June/118899.html > > - we might want

Re: [openstack-dev] [nova] notification update week 28

2017-07-10 Thread Matt Riedemann
On 7/10/2017 3:22 AM, Balazs Gibizer wrote: Hi, Here is the status update / focus setting mail about notification work for week 28. Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1684860 Versioned server notifications don't include updated_at Takashi's fix needs a second +2

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread David Moreau Simard
That sounds like a good fit for an Ansible plugin to control how variables or host inventories are designed [1] and is the intended use case for extending Ansible behavior. [1]: http://docs.ansible.com/ansible/dev_guide/developing_plugins.html#vars-plugins David Moreau Simard Senior Software

[openstack-dev] [puppet] Meeting on July 11, 2017

2017-07-10 Thread Alex Schultz
Hey folks, Just a heads up we have a meeting scheduled for tomorrow July 11, 2017 @ 1500 UTC. The agenda is available here[0]. I would like to take a few mins to review any outstanding work for Pike. Feel free to add any additional topics. Thanks, -Alex [0]

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-10 Thread sfinucan
On Fri, 2017-07-07 at 15:58 +0100, sfinu...@redhat.com wrote: > tl;dr: pbr's 'build_spinx' derivative is broken again, and we want to just > remove the feature at this point. However, this is going to necessitate some > mechanical changes for most projects with docs and this mail serves as a >

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread James Slagle
On Mon, Jul 10, 2017 at 9:19 AM, Steven Hardy wrote: > On Fri, Jul 7, 2017 at 6:50 PM, James Slagle wrote: > Yeah so my idea with (4), and subsequent patches such as[1] is to > gradually move the deploy steps performed to configure services (on >

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-10 Thread Anne Gentle
On Mon, Jul 10, 2017 at 1:11 PM, Doug Hellmann wrote: > Excerpts from sfinucan's message of 2017-07-10 17:20:37 +0100: >> On Fri, 2017-07-07 at 15:58 +0100, sfinu...@redhat.com wrote: >> > tl;dr: pbr's 'build_spinx' derivative is broken again, and we want to just >> >

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread Mark Goddard
I'll throw a second grenade in. Kayobe[1][2] is an OpenStack deployment tool based on kolla-ansible that adds sounds in some ways similar to what you're describing. It roughly follows the TripleO undercloud/overcloud model, with Bifrost used to deploy the overcloud. Kayobe augments kolla-ansible

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

2017-07-10 Thread Kendall Nelson
Hello Mike :) WRT the PTG, if you get approved as an official project before the end of the month, we would love to have you! The PTG isn't formatted the same as the Forum though. The PTG is more project focused technical discussions amongst project contributors- think midcycle rather than

[openstack-dev] [docs] migration status

2017-07-10 Thread Doug Hellmann
Progress After more than 580 patches, the migration is moving along very well. We do still have quite a few repositories that haven't been updated [1], though, so please help us trim that list. It's really important that we finish the migration before we create stable/pike branches to

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

2017-07-10 Thread Andreas Jaeger
On 2017-07-07 17:37, Doug Szumski wrote: > >> On 2017-07-05 12:13, Joshua Hesketh wrote: >>> Hi all, >>> >>> Very sorry for the delay on processing this request. I have now EOL'd >>> stable/mitaka branches for projects listed in [1]. >>> >>> If there are any mistakes it should be possible to

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread Lars Kellogg-Stedman
On Fri, Jul 7, 2017 at 1:50 PM, James Slagle wrote: > There are also some ideas forming around pulling the Ansible playbooks > and vars out of Heat so that they can be rerun (or run initially) > independently from the Heat SoftwareDeployment delivery mechanism: > I think

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread James Slagle
On Mon, Jul 10, 2017 at 11:19 AM, Giulio Fidente wrote: > On 07/10/2017 03:19 PM, Steven Hardy wrote: >> On Fri, Jul 7, 2017 at 6:50 PM, James Slagle wrote: > > [...] > >> Yeah, I think the first step is to focus on a clean "split stack" >> model

Re: [openstack-dev] [docs] [pbr] [ptl] [oslo] Removing pbr's custom 'build_sphinx' setuptools command

2017-07-10 Thread Doug Hellmann
Excerpts from Anne Gentle's message of 2017-07-10 13:14:52 -0400: > On Mon, Jul 10, 2017 at 1:11 PM, Doug Hellmann wrote: > > Excerpts from sfinucan's message of 2017-07-10 17:20:37 +0100: > >> On Fri, 2017-07-07 at 15:58 +0100, sfinu...@redhat.com wrote: > >> > >> Of

[openstack-dev] [kolla] why common_options type is dictionary ?

2017-07-10 Thread Margin Hu
Hi Guys: I want to set docker_common_options parameter but find its type is dictionary. why? ansible/roles/zun/tasks/pull.yml:5:common_options: "{{ docker_common_options }}" tests/test_kolla_docker.py:44: common_options=dict(required=False, type='dict', default=dict()),

Re: [openstack-dev] [tc] Status update, July 7th

2017-07-10 Thread Flavio Percoco
On 07/07/17 10:19 +0200, Thierry Carrez wrote: == Need for a TC meeting next Tuesday == I propose we have a meeting next week to discuss the next steps in establishing the vision. I feel like we should approve it soon, otherwise we'll get too close to the vision date (Spring 2019)... We also

Re: [openstack-dev] [heat][ironic][telemetry][dragonflow][freezer][kuryr][manila][mistral][monasca][neutron][ansible][congress][rally][senlin][storlets][zun][docs] repos without signs of migration sta

2017-07-10 Thread Renat Akhmerov
On 11 Jul 2017, 00:27 +0700, wrote: > openstack/mistral-dashboard > openstack/mistral-extra These two are not supposed to have docs at all. We should probably just remove the “doc” folder and corresponding CI jobs. >  openstack/mistral-lib This should be taken care of soon. Renat Akhmerov

[openstack-dev] [kolla] failed to download image from TryStack

2017-07-10 Thread Margin Hu
Hi Guys I want to try community image , bug failed to download. [root@server opt]# wget https://tarballs.openstack.org/kolla/images/centos-source-registry-ocata.tar.gz --2017-07-11 09:12:37-- https://tarballs.openstack.org/kolla/images/centos-source-registry-ocata.tar.gz Resolving

Re: [openstack-dev] [ironic] [stable] another ironic-stable-maint update proposal

2017-07-10 Thread Matt Riedemann
On 6/30/2017 11:10 AM, Dmitry Tantsur wrote: Hi all! I'd like to propose another round of changes to the ironic-stable-maint group [0]: 1. Add Julia Kreger (TheJulia) to the group. Julia is one of the top reviewers in Ironic, and she is quite active on stable branches as well [1]. 2.

[openstack-dev]  [kolla][kolla-ansible] ceph_osd error when startup ceph_osd container.

2017-07-10 Thread zhou.ya
Hi kolla-ansible team: I have met a weird problem when start up the ceph_osd container。 CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 64b4617ff502

Re: [openstack-dev] [tricircle]

2017-07-10 Thread Vega Cai
Hi Meher, According to the DevStack script, for RHEL, the Apache configuration files are placed in /etc/httpd/conf.d BR Zhiyuan On Mon, 10 Jul 2017 at 22:14 wrote: > Hello everybody, > > > > I posted before a problem related to installing the tricircle on a single >

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread Giulio Fidente
On 07/10/2017 09:23 PM, James Slagle wrote: > On Mon, Jul 10, 2017 at 2:54 PM, Giulio Fidente wrote: >> On 07/10/2017 07:06 PM, James Slagle wrote: >>> On Mon, Jul 10, 2017 at 11:19 AM, Giulio Fidente >>> wrote: splitstack though requires changes

[openstack-dev] [ironic] this week's priorities and subteam reports

2017-07-10 Thread Yeleswarapu, Ramamani
Hi, We are glad to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1. Docs due to the

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

2017-07-10 Thread Mikhail Fedosin
Thank you for asking this! It's really very important and interesting, so I'm going to explain those things more detailed. First, when we designed Glare, we kept in mind the compatibility with Glance, and I can tell that Glance data from the database can be ported to Glare with a simple script

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

2017-07-10 Thread Monty Taylor
On 07/10/2017 01:21 PM, Ed Leafe wrote: On Jul 10, 2017, at 5:06 AM, Mikhail Fedosin > wrote: Given all the advantages and features of Glare, I believe that it can become the successful drop-in replacement. Can you clarify this? Let’s assume I

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread Fox, Kevin M
I think the migration path to something like kolla-kubernetes would be fine, as you have total control over the orchestration piece, ansible and the config generation ansible and since it is all containerized and TripleO production isn't, you should be able to 'upgrade' from non containtered to

[openstack-dev] July 14 CFP Deadline - Sydney Summit

2017-07-10 Thread Allison Price
Hi everyone, Friendly reminder that the OpenStack Summit Sydney Call for Presentations closes THIS Friday, July 14 at 11:59 pm Pacific Time/ July 15 at 6:59 UTC. Don’t miss your chance to present in Sydney! View the new tracks here.

Re: [openstack-dev] [tripleo] proposing Alex Schultz tripleo-core in all projects

2017-07-10 Thread Emilien Macchi
Sounds like we've got a bunch of positive feedback here - Thanks Alex for your work and involvment, you're now tripleo-core in _all_ tripleo projects. On Mon, Jul 10, 2017 at 8:38 AM, Ben Nemec wrote: > +1 for sure > > > On 07/07/2017 12:39 PM, Emilien Macchi wrote: >> >>

Re: [openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

2017-07-10 Thread Monty Taylor
On 07/10/2017 04:31 PM, Monty Taylor wrote: On 07/10/2017 01:21 PM, Ed Leafe wrote: On Jul 10, 2017, at 5:06 AM, Mikhail Fedosin > wrote: Given all the advantages and features of Glare, I believe that it can become the successful drop-in

Re: [openstack-dev] [tripleo] proposing Alex Schultz tripleo-core in all projects

2017-07-10 Thread James Slagle
On Fri, Jul 7, 2017 at 1:39 PM, Emilien Macchi wrote: > Alex has demonstrated high technical and community skills in TripleO - > where he's already core on THT, instack-undercloud, and puppet-tripleo > - but also very involved in other repos. > I propose that we extend his

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread Giulio Fidente
On 07/07/2017 07:50 PM, James Slagle wrote: > I proposed a session for the PTG > (https://etherpad.openstack.org/p/tripleo-ptg-queens) about forming a > common plan and vision around Ansible in TripleO. > > I think it's important however that we kick this discussion off more > broadly before the

Re: [openstack-dev] [tripleo] proposing Alex Schultz tripleo-core in all projects

2017-07-10 Thread Giulio Fidente
thanks Alex! +1 On 07/07/2017 07:39 PM, Emilien Macchi wrote: > Alex has demonstrated high technical and community skills in TripleO - > where he's already core on THT, instack-undercloud, and puppet-tripleo > - but also very involved in other repos. > I propose that we extend his core status to

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

2017-07-10 Thread Gary Kotton
Hi, Will this also be moving to eol - https://github.com/openstack/requirements/blob/stable/mitaka/global-requirements.txt? Thanks Gary On 7/10/17, 9:23 AM, "Andreas Jaeger" wrote: On 2017-07-07 17:37, Doug Szumski wrote: > >> On 2017-07-05 12:13, Joshua Hesketh

Re: [openstack-dev] [tripleo] proposing Alex Schultz tripleo-core in all projects

2017-07-10 Thread Brent Eagles
On Fri, Jul 7, 2017 at 3:09 PM, Emilien Macchi wrote: > Alex has demonstrated high technical and community skills in TripleO - > where he's already core on THT, instack-undercloud, and puppet-tripleo > - but also very involved in other repos. > I propose that we extend his

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

2017-07-10 Thread Sean Dague
On 07/05/2017 03:23 PM, Emilien Macchi wrote: > > I also believe that some of the scripts could be transformed into > native features of Storyboard where bugs could be auto-triaged > periodically without human intervention. > Maybe it would convince more OpenStack projects to leave Launchpad and

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

2017-07-10 Thread Andreas Jaeger
On 2017-07-10 13:33, Gary Kotton wrote: > Hi, > Will this also be moving to eol - > https://github.com/openstack/requirements/blob/stable/mitaka/global-requirements.txt? No, not planned yet, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH,

Re: [openstack-dev] [tripleo] proposing Alex Schultz tripleo-core in all projects

2017-07-10 Thread Steven Hardy
+1 On Fri, Jul 7, 2017 at 6:39 PM, Emilien Macchi wrote: > Alex has demonstrated high technical and community skills in TripleO - > where he's already core on THT, instack-undercloud, and puppet-tripleo > - but also very involved in other repos. > I propose that we extend his

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

2017-07-10 Thread Sean Dague
On 07/05/2017 03:07 PM, Emilien Macchi wrote: > On Wed, Jun 28, 2017 at 7: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

[openstack-dev] [Glare][TC] Application for inclusion of Glare in the list of official projects

2017-07-10 Thread Mikhail Fedosin
Hello! Recently I applied for inclusion of Glare in the list of official OpenStack projects: https://review.openstack.org/#/c/479285/ In this regard, I would like to ask the community what other things can be improved in the project to meet all the necessary requirements. Also in this thread I

Re: [openstack-dev] [congress] Using congress to improve the consistency of configuration files.

2017-07-10 Thread valentin.matton
Hi Eric, Here is the blueprint : https://blueprints.launchpad.net/congress/+spec/configuration-files-validation As Pierre Crégut presented it in his reply to Clint, the use of Congress we suggested and config management systems complement one

[openstack-dev] [horizon] Bug reports and backporting

2017-07-10 Thread Rob Cresswell
Hey everyone! Over the past few months there's been an increase in the number of patches without bug reports, and a decrease in the number of backports. I wanted to take a moment to explain why bug reports are useful, not just bureaucracy, and how they link to backports. Bug reports help in a

Re: [openstack-dev] [tripleo] proposing Alex Schultz tripleo-core in all projects

2017-07-10 Thread Jiří Stránský
On 7.7.2017 19:39, Emilien Macchi wrote: Alex has demonstrated high technical and community skills in TripleO - where he's already core on THT, instack-undercloud, and puppet-tripleo - but also very involved in other repos. I propose that we extend his core status to all TripleO projects and of

Re: [openstack-dev] index_footer in openstack logs

2017-07-10 Thread Wesley Hayutin
On Mon, Jul 10, 2017 at 2:24 AM, Andreas Jaeger wrote: > On 2017-07-10 05:03, Wesley Hayutin wrote: > > posting to openstack-dev > > > > On Sun, Jul 9, 2017 at 10:08 AM, Wesley Hayutin > > wrote: > > > > Greetings Andreas,

[openstack-dev] [oslo] scheduling oslosphinx for retirement at the start of queens

2017-07-10 Thread Doug Hellmann
Oslo team, With all documentation now moving to use the openstackdocs theme, I propose that we retire the oslosphinx repository during Queens. We should go ahead and create the stable/pike branch at the end of this cycle, so that we have a way to deal with bugs in existing pike releases, but I

Re: [openstack-dev] index_footer in openstack logs

2017-07-10 Thread Andreas Jaeger
On 2017-07-10 05:03, Wesley Hayutin wrote: > posting to openstack-dev > > On Sun, Jul 9, 2017 at 10:08 AM, Wesley Hayutin > wrote: > > Greetings Andreas, Paul > > I'm looking for some pointers on how to include some instructions in >

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

2017-07-10 Thread Kekane, Abhishek
Hi Operators, Could you please let me know your opinion on below scenario? It will help me to proceed my work. Thank you, Abhishek -Original Message- From: Kekane, Abhishek [mailto:abhishek.kek...@nttdata.com] Sent: Tuesday, July 04, 2017 2:52 PM To: OpenStack Development Mailing

Re: [openstack-dev] [tricircle]

2017-07-10 Thread meher.hihi
Hello everybody, I posted before a problem related to installing the tricircle on a single node, the script stopped with a keystone startup. You advised me to see the / etc / apache2 / sites-enabled folder to see if the keystone config files are included. But, I have not found this folder, yet

[openstack-dev] [oslo][all] next week is deadline for final release for non-client libraries

2017-07-10 Thread ChangBo Guo
OpenStackers, According to Pike Schedule https://releases.openstack.org/pike/schedule.html Jul 17 - Jul 21 is the deadline for final release for oslo libraries, so please pay more attentions to your reviews which are needed for Pike. Feel free to ping me if you want to quicken the review

Re: [openstack-dev] [oslo] scheduling oslosphinx for retirement at the start of queens

2017-07-10 Thread Davanum Srinivas
+1 from me On Mon, Jul 10, 2017 at 9:10 AM, Doug Hellmann wrote: > Oslo team, > > With all documentation now moving to use the openstackdocs theme, > I propose that we retire the oslosphinx repository during Queens. > We should go ahead and create the stable/pike branch at

[openstack-dev] [Oslo] PTG Planning

2017-07-10 Thread ChangBo Guo
Hi Oslo folks, I created a planning etherpad[1] for topics for the next PTG in Denver. Please add any topics there, then we can schedule the topics before the PTG. [1]https://etherpad.openstack.org/p/oslo-ptg-queens -- ChangBo Guo(gcb)

Re: [openstack-dev] [tripleo] weekly meetings on #tripleo

2017-07-10 Thread Brent Eagles
+1 for giving it a try. On Wed, Jul 5, 2017 at 2:26 PM, Emilien Macchi wrote: > After reading http://lists.openstack.org/pipermail/openstack-dev/2017- > June/118899.html > - we might want to collect TripleO's community feedback on doing > weekly meetings on #tripleo instead

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread Steven Hardy
On Fri, Jul 7, 2017 at 6:50 PM, James Slagle wrote: > I proposed a session for the PTG > (https://etherpad.openstack.org/p/tripleo-ptg-queens) about forming a > common plan and vision around Ansible in TripleO. > > I think it's important however that we kick this

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

2017-07-10 Thread Steven Hardy
On Sun, Jul 9, 2017 at 8:44 AM, Yolanda Robla Mota wrote: > What i'd like to dig more is how Ansible and Heat can live together. And > what features do Heat offer that are not covered by Ansible as well? Is > there still the need to have Heat as the main engine, or could that

Re: [openstack-dev] [tripleo] proposing Alex Schultz tripleo-core in all projects

2017-07-10 Thread Michele Baldessari
On Fri, Jul 07, 2017 at 10:39:25AM -0700, Emilien Macchi wrote: > Alex has demonstrated high technical and community skills in TripleO - > where he's already core on THT, instack-undercloud, and puppet-tripleo > - but also very involved in other repos. > I propose that we extend his core status to

Re: [openstack-dev] [oslo] scheduling oslosphinx for retirement at the start of queens

2017-07-10 Thread Sean Dague
On 07/10/2017 09:10 AM, Doug Hellmann wrote: > Oslo team, > > With all documentation now moving to use the openstackdocs theme, > I propose that we retire the oslosphinx repository during Queens. > We should go ahead and create the stable/pike branch at the end of > this cycle, so that we have a

Re: [openstack-dev] [oslo] scheduling oslosphinx for retirement at the start of queens

2017-07-10 Thread ChangBo Guo
+1 2017-07-10 21:38 GMT+08:00 Davanum Srinivas : > +1 from me > > On Mon, Jul 10, 2017 at 9:10 AM, Doug Hellmann > wrote: > > Oslo team, > > > > With all documentation now moving to use the openstackdocs theme, > > I propose that we retire the