Re: [openstack-dev] [Tripleo] deploy software on Openstack controller on the Overcloud

On Mon, May 29, 2017 at 5:05 AM, Dnyaneshwar Pawar wrote: > Hi, > > I am tying to deploy a software on openstack controller on the overcloud. > One way to do this is by modifying ‘overcloud image’ so that all packages of > our software are added to image and then

Re: [openstack-dev] [TripleO] Passing along some field feedback

On Fri, May 26, 2017 at 3:34 PM, Ben Nemec wrote: > Hi, > > As some of you may know, I have a weekly meeting with some of the Red Hat > folks who are out in the field using TripleO to deploy OpenStack at customer > sites. The past couple of weeks have been particularly

Re: [openstack-dev] [release][infra][puppet][stable] Re: [Release-job-failures] Release of openstack/puppet-nova failed

On Mon, May 22, 2017 at 10:34 AM, Jeremy Stanley <fu...@yuggoth.org> wrote: > On 2017-05-22 09:06:26 -0600 (-0600), Alex Schultz wrote: > [...] >> We ran into this for the puppet-module-build check job so I created a >> puppet-agent-install builder. Perhaps

Re: [Openstack-operators] Fuel setup problem

On Fri, May 19, 2017 at 11:15 PM, Matthieu Lejeune < matthieu.leje...@exxoss.com> wrote: > Hi all, > > Please someone as some experience with fuel and problem like ? > > On an other side someone have production expercience with fuel ? It's a > good idea? > > Matthieu > > > > > Le 11/05/17 à

Re: [openstack-dev] [release][infra][puppet][stable] Re: [Release-job-failures] Release of openstack/puppet-nova failed

On Mon, May 22, 2017 at 9:05 AM, Paul Belanger wrote: > On Mon, May 22, 2017 at 10:53:32AM -0400, Doug Hellmann wrote: >> Excerpts from jenkins's message of 2017-05-22 10:49:09 +: >> > Build failed. >> > >> > - puppet-nova-tarball >> >

Re: [openstack-dev] [release][infra][puppet][stable] Re: [Release-job-failures] Release of openstack/puppet-nova failed

On Mon, May 22, 2017 at 8:53 AM, Doug Hellmann wrote: > Excerpts from jenkins's message of 2017-05-22 10:49:09 +: >> Build failed. >> >> - puppet-nova-tarball >> http://logs.openstack.org/89/89c58e7958b448364cb0290c1879116f49749a68/release/puppet-nova-tarball/fe9daf7/

[openstack-dev] [puppet] Meeting Reminder for May 23, 2017

Hey Folks, Just a reminder that we have a meeting schedule for tomorrow, May 23, 2017 @ 1500 UTC. If you wish to talk about something, please add it to the agenda[0]. Thanks, -Alex [0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20170523

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 1:02 PM, Michał Jastrzębski <inc...@gmail.com> wrote: > On 5 May 2017 at 11:33, Alex Schultz <aschu...@redhat.com> wrote: >> On Fri, May 5, 2017 at 10:48 AM, Chris Dent <cdent...@anticdent.org> wrote: >>> On Fri, 5 May 2017, A

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 1:49 PM, Sean Dague <s...@dague.net> wrote: > On 05/05/2017 12:36 PM, Alex Schultz wrote: >> On Fri, May 5, 2017 at 6:16 AM, Sean Dague <s...@dague.net> wrote: >>> On 05/04/2017 11:08 AM, Alex Schultz wrote: >>> >>> The gener

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 10:48 AM, Chris Dent <cdent...@anticdent.org> wrote: > On Fri, 5 May 2017, Alex Schultz wrote: > >> You have to understand that as I'm mainly dealing with having to >> actually deploy/configure the software, when I see 'new project X' >> t

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 10:52 AM, Dean Troyer <dtro...@gmail.com> wrote: > On Fri, May 5, 2017 at 11:36 AM, Alex Schultz <aschu...@redhat.com> wrote: >> configuration and usability issues. But those aren't exciting so >> people don't want to work on them... > > [N

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Fri, May 5, 2017 at 6:16 AM, Sean Dague <s...@dague.net> wrote: > On 05/04/2017 11:08 AM, Alex Schultz wrote: >> On Thu, May 4, 2017 at 5:32 AM, Chris Dent <cdent...@anticdent.org> wrote: >>> On Wed, 3 May 2017, Drew Fisher wrote: >>> >>&

Re: [openstack-dev] [tc] [all] OpenStack moving both too fast and too slow at the same time

On Thu, May 4, 2017 at 5:32 AM, Chris Dent wrote: > On Wed, 3 May 2017, Drew Fisher wrote: > >> This email is meant to be the ML discussion of a question I brought up >> during the TC meeting on April 25th.; [1] > > > Thanks for starting this Drew, I hope my mentioning it

Re: [Openstack-operators] [puppet] module dependencies in final Mitaka release

On Wed, Apr 26, 2017 at 5:22 AM, Alex Schultz <aschu...@redhat.com> wrote: > On Wed, Apr 26, 2017 at 3:26 AM, Justin Cattle <j...@ocado.com> wrote: >> Hi, >> >> >> It looks like there is some invalid dependencies in the neutron module: >> >> >&

Re: [Openstack-operators] [puppet] module dependencies in final Mitaka release

On Wed, Apr 26, 2017 at 3:26 AM, Justin Cattle wrote: > Hi, > > > It looks like there is some invalid dependencies in the neutron module: > > > +{ > +"name": "openstack/vswitch", > +"version_requirement": ">=4.3.0 <5.0.0" > +}, > > > There

[openstack-dev] [puppet] Reminder meeting April 25, 2017 @ 1500 UTC

Just a reminder, but we have a meeting tomorrow. Please add anything you wish to talk about to the agenda[0]. Thanks, -Alex [0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20170425 __ OpenStack

[Openstack-operators] [puppet] Warning running low of contributors

Hey folks, So in recent months, we've seen a drop off contributors and reviewers to the various Puppet OpenStack modules. Additionally with the recent resignation of a few of our cores, we're getting to a spot where the modules under the Puppet OpenStack umbrella are becoming dangerously close to

[openstack-dev] [puppet] Warning running low of contributors

Hey folks, So in recent months, we've seen a drop off contributors and reviewers to the various Puppet OpenStack modules. Additionally with the recent resignation of a few of our cores, we're getting to a spot where the modules under the Puppet OpenStack umbrella are becoming dangerously close to

Re: [openstack-dev] [puppet][fuel] stepping down from puppet/fuel core groups

ll of you! I've learn a lot! Thank you > all for all your help and advises. > > Also want to especially say "Thank you" to Emilien Macchi, Alex Schultz, > Sergii Golovatiuk, Vladimir Kuklin and other core guys - you're best! :) > > If you will need my help, please don't hesi

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

On Wed, Apr 12, 2017 at 6:21 PM, Tony Breeds <t...@bakeyournoodle.com> wrote: > On Wed, Apr 12, 2017 at 07:53:17AM -0600, Alex Schultz wrote: > >> Please EOL the Puppet OpenStack projects that have the stable/mitaka branch. > > Thanks Alex! I've added: > openstack/pup

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

On Wed, Apr 12, 2017 at 12:47 AM, Tony Breeds wrote: > Hi all, > I'm late in sending this announement, but I'm glad to see several projects > have already requested EOL releases to make it trivial and obvious where to > apply the tag. > > I'm proposing to EOL all

[openstack-dev] [puppet] Meeting April 11, 2017 @1500 UTC

Just a reminder, we have a meeting scheduled tomorrow April 11, 2017 @1500UTC[0]. Please add something to the agenda[1] if you have something you would like to talk about. Thanks, -Alex [0] https://docs.openstack.org/developer/puppet-openstack-guide/meetings.html [1]

Re: [openstack-dev] [puppet] stepping down from puppet-openstack core

On Tue, Apr 4, 2017 at 3:23 PM, Matt Fischer wrote: > I am stepping down as core in the puppet openstack project. This is the > culmination of a long and slow refocus of my work efforts into other areas. > Additionally I'm not sure what the future holds for me at this point,

Re: [openstack-dev] [tripleo] Idempotence of the deployment process

On Sun, Apr 2, 2017 at 6:01 AM, Dan Prince <dpri...@redhat.com> wrote: > On Fri, 2017-03-31 at 17:21 -0600, Alex Schultz wrote: >> Hey folks, >> >> I wanted to raise awareness of the concept of idempotence[0] and how >> it affects deployment(s). In the pu

[openstack-dev] [tripleo] Idempotence of the deployment process

Hey folks, I wanted to raise awareness of the concept of idempotence[0] and how it affects deployment(s). In the puppet world, we consider this very important because since puppet is all about ensuring a desired state (ie. a system with config files + services). That being said, I feel that it

Re: [openstack-dev] [tripleo] os-cloud-config retirement

On Thu, Mar 30, 2017 at 6:58 AM, Dan Prince wrote: > There is one case that I was thinking about reusing this piece of code > within a container to help initialize keystone endpoints. It would > require some changes and updates (to match how puppet-* configures > endpoints). >

Re: [openstack-dev] [puppet] Stepping down from puppet core

On Wed, Mar 29, 2017 at 8:57 AM, Ivan Berezovskiy wrote: > Hello Puppeteers! > > I'd like to step down as a core review for the OpenStack Puppet. > Unfortunately, as you could see I didn't participate in Puppet > activities last few months. My career objective has

[openstack-dev] [tripleo] Log collection of overcloud nodes

Hey folks, So as part of the capture-environment-status-and-logs blueprint[0], I'm working on adding a single command to perform status and log collection of the overcloud nodes via the tripleoclient that can be used on the undercloud. I would like to bring up switching over to this as part of

[openstack-dev] [puppet] Meeting Mar 28, 2017 @1500 UTC

Hey puppet folks, Just a reminder we have a meeting schedule tomorrow. The agenda[0] is currently empty. If you have something you would like to discuss, please add it to the list. If the agenda is empty at meeting time we will cancel the meeting for this week. Thanks, -Alex [0]

Re: [openstack-dev] [tripleo] patch abandoment policy

On Mon, Mar 27, 2017 at 6:47 AM, Dan Prince <dpri...@redhat.com> wrote: > On Mon, 2017-03-27 at 13:49 +0200, Flavio Percoco wrote: >> On 24/03/17 17:16 -0400, Dan Prince wrote: >> > On Thu, 2017-03-23 at 16:20 -0600, Alex Schultz wrote: >> > > Hey f

Re: [openstack-dev] [tripleo] patch abandoment policy

On Fri, Mar 24, 2017 at 3:16 PM, Dan Prince <dpri...@redhat.com> wrote: > On Thu, 2017-03-23 at 16:20 -0600, Alex Schultz wrote: >> Hey folks, >> >> So after looking at the backlog of patches to review across all of >> the >> tripleo projects, I noti

[openstack-dev] [tripleo] patch abandoment policy

Hey folks, So after looking at the backlog of patches to review across all of the tripleo projects, I noticed we have a bunch of really old stale patches. I think it's time we address when we can abandon these stale patches. Please comment on the proposed policy[0]. I know this has previously

Re: [openstack-dev] [TripleO]:triple-o undercloud installation error on CentOS7.3

On Thu, Mar 23, 2017 at 7:43 AM, pranab boruah wrote: > Hi, I am trying to install triple-o undercloud on a physical machine. > The installation fails every time. I have reinstalled the OS and tried > starting from scratch but got the same error. > > System Details :

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

On Wed, Mar 22, 2017 at 7:58 AM, Paul Belanger <pabelan...@redhat.com> wrote: > On Tue, Mar 21, 2017 at 05:53:35PM -0600, Alex Schultz wrote: >> On Tue, Mar 21, 2017 at 5:35 PM, John Dickinson <m...@not.mn> wrote: >> > >> > >> > On 21 Mar 2017, at 1

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

On Wed, Mar 22, 2017 at 12:23 AM, Tim Bell <tim.b...@cern.ch> wrote: > >> On 22 Mar 2017, at 00:53, Alex Schultz <aschu...@redhat.com> wrote: >> >> On Tue, Mar 21, 2017 at 5:35 PM, John Dickinson <m...@not.mn> wrote: >>> >>> >>> On

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

On Tue, Mar 21, 2017 at 5:35 PM, John Dickinson <m...@not.mn> wrote: > > > On 21 Mar 2017, at 15:34, Alex Schultz wrote: > >> On Tue, Mar 21, 2017 at 3:45 PM, John Dickinson <m...@not.mn> wrote: >>> I've been following this thread, but I must adm

Re: [openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)

On Tue, Mar 21, 2017 at 3:45 PM, John Dickinson wrote: > I've been following this thread, but I must admit I seem to have missed > something. > > What problem is being solved by storing per-server service configuration > options in an external distributed CP system that is

Re: [openstack-dev] [tripleo] Sample Roles

I would like to see improvements in how we are exposing these services/roles to the end user. I agree that rolling this into a workflow would be a good idea. Thanks, -Alex > Regards, > Saravanan KR > > On Thu, Mar 16, 2017 at 3:37 AM, Emilien Macchi <emil...@redhat.com> wr

[openstack-dev] [tripleo] Sample Roles

Ahoy folks, For the Pike cycle, we have a blueprint[0] to provide a few basic environment configurations with some custom roles. For this effort and to reduce the complexity when dealing with roles I have put together a patch to try and organize roles in a more consumable fashion[1]. The goal

[openstack-dev] [puppet] No meeting Mar 14, 2017, next meeting Mar 21, 2017

The agenda[0] was empty. So canceling the meeting for this week. The next meeting will be on Mar 21, 2017 @ 1500 UTC. Feel free put something on the agenda[1]. Thanks, -Alex [0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20170314 [1]

Re: [openstack-dev] [puppet][tripleo][release] puppet module versioning

On Thu, Mar 9, 2017 at 10:54 AM, Doug Hellmann wrote: > Excerpts from Alex Schultz's message of 2017-03-07 12:56:17 -0700: >> Ahoy folks, >> >> I would like to bring attention to deriving version numbers for puppet >> modules (for packaging) as part of the release process.

[openstack-dev] [puppet][tripleo][release] puppet module versioning

Ahoy folks, I would like to bring attention to deriving version numbers for puppet modules (for packaging) as part of the release process. Today we uncovered an issue[0] in the way that version numbers were being derived for packages which ultimately broke the TripleO CI upgrade jobs because the

Re: [openstack-dev] [puppet] puppet-cep beaker test

Hey Stefan, On Tue, Mar 7, 2017 at 7:09 AM, Scheglmann, Stefan wrote: > Hi, > > currently got some problems running the beaker test for the puppet-cep > module. Working on OSX using Vagrant version 1.8.6 and VirtualBox version > 5.1.14. Call is 'BEAKER_destroy=no

[openstack-dev] [puppet] Reminder meeting Mar 7th @ 1500 UTC

Hey Puppet Folk, Just a reminder, but we will be having our meeting tomorrow. Please add something to the meeting etherpad[0] if you have a specific topic you wish to talk about. Thanks, -Alex [0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20170307

[openstack-dev] [puppet] Reminder next meeting on Feb 28 @ 1500 UTC

Due to the PTG this week, we are skipping the meeting tomorrow. The next meeting will be on Feb 28th. The agenda[0] is currently empty. If you have something you wish to talking about, please add it to the list. Thanks, -Alex [0]

Re: [Openstack-operators] [puppet][fuel][packstack][tripleo] puppet 3 end of life

/releases.html#releases-summary On Fri, Nov 11, 2016 at 2:11 PM, Alex Schultz <aschu...@redhat.com> wrote: > On Thu, Nov 3, 2016 at 11:31 PM, Sam Morrison <sorri...@gmail.com> wrote: >> >> On 4 Nov. 2016, at 1:33 pm, Emilien Macchi <emil...@redhat.com> wrote: >> >>

Re: [openstack-dev] [Openstack-operators] [puppet][fuel][packstack][tripleo] puppet 3 end of life

/releases.html#releases-summary On Fri, Nov 11, 2016 at 2:11 PM, Alex Schultz <aschu...@redhat.com> wrote: > On Thu, Nov 3, 2016 at 11:31 PM, Sam Morrison <sorri...@gmail.com> wrote: >> >> On 4 Nov. 2016, at 1:33 pm, Emilien Macchi <emil...@redhat.com> wrote: >> >>

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Thu, Feb 16, 2017 at 9:12 AM, Ed Leafe wrote: > On Feb 16, 2017, at 10:07 AM, Doug Hellmann wrote: > >> When we signed off on the Big Tent changes we said competition >> between projects was desirable, and that deployers and contributors >> would make

Re: [openstack-dev] [chef] Making the Kitchen Great Again: A Retrospective on OpenStack & Chef

On Wed, Feb 15, 2017 at 9:02 AM, Samuel Cassiba wrote: > >> On Feb 15, 2017, at 02:07, Thierry Carrez wrote: >> >> Samuel Cassiba wrote: >>> [...] >>> *TL;DR* if you don't want to keep going - >>> OpenStack-Chef is not in a good place and is not

[openstack-dev] [puppet] mascot

Hey folks, The final mascot is available for viewing here: https://www.dropbox.com/sh/oax7i1xvca3edxc/AAAtfQSyx0rJijKBoqoZmp-va?dl=0 Thanks, -Alex __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [puppet] Reminder meeting on Feb 14th @ 1500 UTC

Just a reminder but we will be having our meeting tomorrow Feb 14th at 1500 UTC in #openstack-meeting-4 unless the agenda[0] remains empty. So if you have something you wish to talk about it, please add it to the agenda. As always the the previous meeting logs and agendas are reviewable here[1].

[openstack-dev] [puppet] No meeting Feb 7, 2017, next meeting Feb 14, 2017

Hey all, The agenda etherpad[0] was empty so we're skipping today's meeting. The next meeting will be on Feb 14th, 2017. If you have something to discuss, please add it to the agenda etherpad[1]. Thanks, -Alex [0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20170207 [1]

[openstack-dev] [puppet] No meeting today - Jan 31, 2017

Hi all, Since the agenda[0] for the meeting is empty, I'm canceling the meeting. If you wish to talk about something next week, please add it to the agenda[1]. Thanks, -Alex [0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20170131 [1]

Re: [openstack-dev] [puppet] Nominating zhongshengping for core of the Puppet OpenStack modules

On Fri, Jan 20, 2017 at 10:19 AM, Alex Schultz <aschu...@redhat.com> wrote: > Hey Puppet Cores, > > I would like to nominate Zhong Shengping as a Core reviewer for the > Puppet OpenStack modules. He is an excellent contributor to our > modules over the last several cycles. H

Re: [openstack-dev] [puppet] Nominating mkarpin for core for the Puppet OpenStack modules

On Thu, Jan 19, 2017 at 3:25 PM, Alex Schultz <aschu...@redhat.com> wrote: > Hey Puppet Cores, > > I would like to nominate Mykyta Karpin as a Core reviewer for the > Puppet OpenStack modules. He has been providing quality patches and > reviews for some time now and I belie

Re: [openstack-dev] [puppet] CI status for Ubuntu

On Tue, Jan 24, 2017 at 6:43 AM, Corey Bryant <corey.bry...@canonical.com> wrote: > > On Fri, Jan 20, 2017 at 6:34 PM, Alex Schultz <aschu...@redhat.com> wrote: >> >> Just FYI, >> >> We switched the Ubuntu scenario jobs to non-voting this week due

[openstack-dev] [puppet] CI status for Ubuntu

Just FYI, We switched the Ubuntu scenario jobs to non-voting this week due to the large amount of breakage caused by the ocata-proposed update to m2 based packages. The Ubuntu beaker jobs are still voting on the modules themselves. Here's where we're keeping track of issues:

[openstack-dev] [puppet] PTL candidacy

configurations have already been removed. I look forward to working with all of you. As always, I'm open to any suggestions or ideas for additional places to improve our processes and modules. Thanks, Alex Schultz irc: mwhahaha https://review.openstack.org/423514

[openstack-dev] [puppet] Nominating zhongshengping for core of the Puppet OpenStack modules

Hey Puppet Cores, I would like to nominate Zhong Shengping as a Core reviewer for the Puppet OpenStack modules. He is an excellent contributor to our modules over the last several cycles. His stats for the last 90 days can be viewed here[0]. Please response with your +1 or any objections. If

[openstack-dev] [puppet] Nominating mkarpin for core for the Puppet OpenStack modules

Hey Puppet Cores, I would like to nominate Mykyta Karpin as a Core reviewer for the Puppet OpenStack modules. He has been providing quality patches and reviews for some time now and I believe he would be a good addition to the team. His stats for the last 90 days can be viewed here[0] Please

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On Thu, Jan 19, 2017 at 11:45 AM, Jay Pipes <jaypi...@gmail.com> wrote: > On 01/19/2017 01:18 PM, Alex Schultz wrote: >> >> On Thu, Jan 19, 2017 at 10:34 AM, Jay Pipes <jaypi...@gmail.com> wrote: >>> >>> On 01/19/2017 11:25 AM, Alex Schultz wrote: &

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On Thu, Jan 19, 2017 at 10:34 AM, Jay Pipes <jaypi...@gmail.com> wrote: > On 01/19/2017 11:25 AM, Alex Schultz wrote: >> >> On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann >> <mrie...@linux.vnet.ibm.com> wrote: >>> >>> Sylvain and I

Re: [openstack-dev] [nova] Order of n-api (placement) and n-sch upgrades for Ocata

On Thu, Jan 19, 2017 at 8:27 AM, Matt Riedemann wrote: > Sylvain and I were talking about how he's going to work placement > microversion requests into his filter scheduler patch [1]. He needs to make > requests to the placement API with microversion 1.4 [2] or later

Re: [openstack-dev] [nova][puppet][tripleo][kolla][fuel] Let's talk nova cell v2 deployments and upgrades

On Fri, Jan 13, 2017 at 1:05 PM, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > On 1/13/2017 11:43 AM, Alex Schultz wrote: >> >> Ahoy folks, >> >> So we've been running into issues with the addition of the cell v2 >> setup as part of the r

[openstack-dev] [nova][puppet][tripleo][kolla][fuel] Let's talk nova cell v2 deployments and upgrades

Ahoy folks, So we've been running into issues with the addition of the cell v2 setup as part of the requirements for different parts of nova. It was recommended that we move the conversation to the ML to get a wider audience. Basically, cell v2 has been working it's way into a required thing

Re: [Openstack-operators] [puppet] Virtual midcycle/sprint - Jan 11/12

On Tue, Dec 6, 2016 at 12:32 PM, Alex Schultz <aschu...@redhat.com> wrote: > Hey everyone, > > We're going to be running a small midcycle/sprint on January 11-12, > 2017 in #puppet-openstack on freenode. We will be reviewing the work > items for Ocata and doing some bug tri

Re: [openstack-dev] [puppet] Virtual midcycle/sprint - Jan 11/12

On Tue, Dec 6, 2016 at 12:32 PM, Alex Schultz <aschu...@redhat.com> wrote: > Hey everyone, > > We're going to be running a small midcycle/sprint on January 11-12, > 2017 in #puppet-openstack on freenode. We will be reviewing the work > items for Ocata and doing some bug tri

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 10:25 AM, Michał Jastrzębski wrote: > Ad kolla-ansible core team +2ing new deliverable,I agree with Sam, > there is no reason in my mind for kolla-ansible/k8s core team to vote > on accepting new deliverable. I think this should be lightweight and > easy,

Re: [openstack-dev] [tc][kolla] Adding new deliverables

On Thu, Jan 5, 2017 at 8:58 AM, Sam Yaple wrote: > Involving kolla-ansible and kolla-kubernetes in a decision about > kolla-salt (or kolla-puppet, or kolla-chef) is silly since the projects are > unrelated. That would be like involving glance when cinder has a new > service

[openstack-dev] [puppet] Dec 27, Jan 3 meetings canceled

Hey, Given that the next few meetings will be right after some holidays, we're going to go ahead and cancel the meetings on Dec 27 and Jan 3. Our next meeting will be on Jan 10. See you then. Thanks, -Alex __ OpenStack

[openstack-dev] [puppet] Virtual midcycle/sprint - Jan 11/12

Hey everyone, We're going to be running a small midcycle/sprint on January 11-12, 2017 in #puppet-openstack on freenode. We will be reviewing the work items for Ocata and doing some bug triage. Feel free to add additional topics to the etherpad[0]. Thanks, -Alex [0]

[Openstack-operators] [puppet] Virtual midcycle/sprint - Jan 11/12

Hey everyone, We're going to be running a small midcycle/sprint on January 11-12, 2017 in #puppet-openstack on freenode. We will be reviewing the work items for Ocata and doing some bug triage. Feel free to add additional topics to the etherpad[0]. Thanks, -Alex [0]

Re: [openstack-dev] [tripleo] [ironic] Need to update kernel parameters on local boot

On Fri, Dec 2, 2016 at 7:29 AM, Oliver Walsh wrote: > Hi Yolanda, > > I've the same requirements for a real-time compute role. > > I'm current using #4. Puppet sets the kernel cmdline in > /etc/defaults/grub, then touches a file that triggers a reboot in an > os-refresh-config

[openstack-dev] [tripleo] Requesting files from the overcloud from the undercloud

Hey folks, So I'm in the process of evaluating options for implementing the capture-environment-status-and-logs[0] blueprint. At the moment my current plan is to implement a mistral workflow to execute the sosreport to bundle the status and logs up on the requested nodes. I'm leveraging a

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

On Tue, Nov 22, 2016 at 5:13 PM, Tony Breeds <t...@bakeyournoodle.com> wrote: > On Tue, Nov 22, 2016 at 09:21:00AM -0700, Alex Schultz wrote: > >> For the puppet items on the second list[0], the liberty branches of >> puppet-aodh and puppet-openstack_spec_helper can be EOL'

Re: [openstack-dev] [TripleO] How to add support for setting 'my_ip' in nova.conf?

Hey Melanie, On Tue, Nov 22, 2016 at 4:36 PM, melanie witt wrote: > Hi all, > > In the Nova configuration, the 'my_ip' setting is the IP address the host > uses to connect to the management network [1]. This is the IP Nova uses to > set up iptables rules for the metadata

Re: [openstack-dev] [tripleo] POC patch for using tripleo-repos for repo setup

On Tue, Nov 22, 2016 at 11:06 AM, Ben Nemec <openst...@nemebean.com> wrote: > > > On 11/21/2016 05:26 PM, Alex Schultz wrote: >> >> On Mon, Nov 21, 2016 at 2:57 PM, Ben Nemec <openst...@nemebean.com> wrote: >>> >>> Hi, >>> >>>

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

Hey Tony, On Mon, Nov 21, 2016 at 7:35 PM, Tony Breeds wrote: > Hi all, > I'm late in sending this announement, but I'm glad to see several projects > have already requested EOL releases to make it trivial and obvious where to > apply the tag. > > I'm proposing to

Re: [openstack-dev] [tripleo] POC patch for using tripleo-repos for repo setup

On Mon, Nov 21, 2016 at 2:57 PM, Ben Nemec wrote: > Hi, > > I have a POC patch[1] up to demonstrate the use of the tripleo-repos tool > [2] as a replacement for most of tripleo.sh --repo-setup. It has now passed > all of the CI jobs so I wanted to solicit some feedback. >

Re: [Openstack-operators] [puppet][fuel][packstack][tripleo] puppet 3 end of life

; > > > > > > My guess is that this would also be the case for RedHat and other distros > too. > > > Fedora is shipping Puppet 4 and we're going to do the same for Red Hat > and CentOS7. > > Thoughts? > > > > On 4 Nov. 2016, at 2:58 am, Alex Schultz <as

Re: [openstack-dev] [Openstack-operators] [puppet][fuel][packstack][tripleo] puppet 3 end of life

; > > > > > > My guess is that this would also be the case for RedHat and other distros > too. > > > Fedora is shipping Puppet 4 and we're going to do the same for Red Hat > and CentOS7. > > Thoughts? > > > > On 4 Nov. 2016, at 2:58 am, Alex Schultz <as

Re: [Openstack-operators] [puppet] openstack provider errors with openrc and keystone v3

haven't been using puppet-openstack_extras, but I'll look at > that for the openrc file at least :) > > > > > > Cheers, > Just > > On 10 November 2016 at 16:32, Alex Schultz <aschu...@redhat.com> wrote: >> >> Hey Justin, >> >> >> >

Re: [Openstack-operators] [puppet] openstack provider errors with openrc and keystone v3

Hey Justin, On Thu, Nov 10, 2016 at 8:48 AM, Justin Cattle wrote: > Hi, > > > I was looking at this class in the keystone module: > > keystone::disable_admin_token_auth > > ..which suggests: > > # After this class is run, > # future puppet runs must have an openrc file with

[openstack-dev] [puppet][fuel][packstack][tripleo] puppet 3 end of life

Hey everyone, Puppet 3 is reaching it's end of life at the end of this year[0]. Because of this we are planning on dropping official puppet 3 support as part of the Ocata cycle. While we currently are not planning on doing any large scale conversion of code over to puppet 4 only syntax, we may

[Openstack-operators] [puppet][fuel][packstack][tripleo] puppet 3 end of life

Hey everyone, Puppet 3 is reaching it's end of life at the end of this year[0]. Because of this we are planning on dropping official puppet 3 support as part of the Ocata cycle. While we currently are not planning on doing any large scale conversion of code over to puppet 4 only syntax, we may

Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

others on this email that this change should not affect anyone consuming the puppet modules because our default is still UUID and will be even after keystone's default changes. Thanks, -Alex > On Thu, Nov 3, 2016 at 10:23 AM, Alex Schultz <aschu...@redhat.com> wrote: >> >> He

Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

Hey Steve, On Thu, Nov 3, 2016 at 8:11 AM, Steve Martinelli wrote: > As a heads up to some of keystone's consuming projects, we will be changing > the default token format from UUID to Fernet. Many patches have merged to > make this possible [1]. The last 2 that you

Re: [openstack-dev] [puppet] weekly meeting #95

A meeting was had by all. http://eavesdrop.openstack.org/meetings/puppet_openstack/2016/puppet_openstack.2016-11-01-15.00.html Thanks, -Alex On Mon, Oct 31, 2016 at 11:06 AM, Alex Schultz <aschu...@redhat.com> wrote: > Hey folks, > > Just a reminder that we will have our meeting

[openstack-dev] [puppet] weekly meeting #95

Hey folks, Just a reminder that we will have our meeting tomorrow at 3pm UTC on #openstack-meeting-4. Here's the current agenda: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20161101 Thanks, -Alex __

[openstack-dev] [puppet] no meeting

Hey All, We're skipping the meeting today due to the summit. See you all next week. Thanks, -Alex __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [QA][Tempest] Check puppet jobs on the gate

On Fri, Oct 21, 2016 at 4:02 PM, Ken'ichi Ohmichi wrote: > Hi QA team, > > There are three gate jobs related to puppet jobs (like > gate-puppet-openstack-integration-4-scenario001-tempest-centos-7-nv) > and they are marked as non-voting now. > If finding these jobs failures

Re: [openstack-dev] [puppet][tripleo][fuel] Upcoming changes to defaults around using processor count for worker configurations

Hey Sergii, On Thu, Oct 20, 2016 at 3:34 AM, Sergii Golovatiuk <sgolovat...@mirantis.com> wrote: > Hi, > > > On Thu, Sep 29, 2016 at 11:57 PM, Alex Schultz <aschu...@redhat.com> wrote: >> >> Hello all, >> >> So for many years we've been usin

Re: [Openstack-operators] [openstack-dev] [puppet][tripleo][fuel] Upcoming changes to defaults around using processor count for worker configurations

Hey Sergii, On Thu, Oct 20, 2016 at 3:34 AM, Sergii Golovatiuk <sgolovat...@mirantis.com> wrote: > Hi, > > > On Thu, Sep 29, 2016 at 11:57 PM, Alex Schultz <aschu...@redhat.com> wrote: >> >> Hello all, >> >> So for many years we've been usin

Re: [openstack-dev] [tripleo][ironic][puppet] Spine/Leaf: Adding Multiple Subnets to ironic-inspector-dnsmasq

On Wed, Oct 19, 2016 at 11:33 AM, Dan Sneddon wrote: > I am doing research to support the spec for TripleO deployment on > routed networks [1]. I would like some input on how to represent > multiple subnet ranges for the provisioning network in undercloud.conf. > > The Ironic

Re: [openstack-dev] [rpm-packaging][chef][puppet][salt][openstack-ansible][HA][tripleo][kolla][fuel] Schema proposal for config file handling for services

On Thu, Oct 13, 2016 at 3:27 AM, Thomas Bechtold <tbecht...@suse.com> wrote: > On Tue, Oct 11, 2016 at 12:32:40PM -0600, Alex Schultz wrote: >> On Tue, Oct 11, 2016 at 1:39 AM, Thomas Bechtold <tbecht...@suse.com> wrote: >> > Hi, >> > >> > On Mon

Re: [openstack-dev] [rpm-packaging][chef][puppet][salt][openstack-ansible][HA][tripleo][kolla][fuel] Schema proposal for config file handling for services

On Tue, Oct 11, 2016 at 1:39 AM, Thomas Bechtold <tbecht...@suse.com> wrote: > Hi, > > On Mon, Oct 10, 2016 at 10:07:05AM -0600, Alex Schultz wrote: >> On Mon, Oct 10, 2016 at 5:03 AM, Thomas Bechtold <tbecht...@suse.com> wrote: >> > Hi, >> > >> &

Re: [openstack-dev] [rpm-packaging][chef][puppet][salt][openstack-ansible][HA] Schema proposal for config file handling for services

On Mon, Oct 10, 2016 at 5:03 AM, Thomas Bechtold wrote: > Hi, > > in the rpm-packaging project we started to package the services and are > currently discussing a possible schema for configuration files and > snippets used by the systemd .service files (but this would also

[openstack-dev] [puppet] Presence at the PTG

Hi, We chatted about this a bit in the last meeting[0], but I wanted to send a note to the wider audience. Our initial thought was that the puppet group will not have a specific presence at the upcoming PTG in Atlanta. We don't think we'll have any topics that we can't work through via our

[Openstack-operators] [puppet] Presence at the PTG

Hi, We chatted about this a bit in the last meeting[0], but I wanted to send a note to the wider audience. Our initial thought was that the puppet group will not have a specific presence at the upcoming PTG in Atlanta. We don't think we'll have any topics that we can't work through via our

[Openstack-operators] [puppet][tripleo][fuel] Upcoming changes to defaults around using processor count for worker configurations

Hello all, So for many years we've been using either the service defaults (usually python determined processor count) or the $processorcount fact from facter in puppet for worker configuration options for the OpenStack services. If you are currently using the default values provided by the

<    1   2   3   4   >