[openstack-dev] [TripleO] Revert "Migrate tripleo to centos-7"

Sending it again to [TripleO]. On Mon, 2016-06-06 at 20:06 -0400, Dan Prince wrote: > Hi all, > > Having a bit of a CI outage today due to (I think) the switch to > Centos > Jenkins slaves. I'd like to suggest that we revert that quickly to > keep > things moving i

[openstack-dev] Revert "Migrate tripleo to centos-7"

Hi all, Having a bit of a CI outage today due to (I think) the switch to Centos Jenkins slaves. I'd like to suggest that we revert that quickly to keep things moving in TripleO: https://review.openstack.org/326182 Revert "Migrate tripleo to centos- 7" And then perhaps we can follow up with a

Re: [openstack-dev] [tripleo] Nodes management in our shiny new TripleO API

On Fri, 2016-05-20 at 14:06 +0200, Dmitry Tantsur wrote: > On 05/20/2016 01:44 PM, Dan Prince wrote: > > > > On Thu, 2016-05-19 at 15:31 +0200, Dmitry Tantsur wrote: > > > > > > Hi all! > > > > > > We started some discussions on https://review.

Re: [openstack-dev] [tripleo] Zaqar messages standardization

On Fri, 2016-05-20 at 17:52 +0200, Jiri Tomasek wrote: > Hey all, > > I've been recently working on getting the TripleO UI integrated with > Zaqar, so it can receive a messages from Mistral workflows and act > upon them without having to do various polling hacks. > > Since there is currently

Re: [openstack-dev] [tripleo] Nodes management in our shiny new TripleO API

On Thu, 2016-05-19 at 15:31 +0200, Dmitry Tantsur wrote: > Hi all! > > We started some discussions on https://review.openstack.org/#/c/30020 > 0/  > about the future of node management (registering, configuring and  > introspecting) in the new API, but I think it's more fair (and  > convenient)

Re: [openstack-dev] [TripleO][CI] Tempest on periodic jobs

On Tue, 2016-05-17 at 20:03 +0300, Sagi Shnaidman wrote: > Hi, > raising again the question about tempest running on TripleO CI as it > was discussed in the last TripleO meeting. > > I'd like to get your attention that in these tests, which I ran just > for ensure it works, there were bugs

Re: [openstack-dev] [tripleo] composable roles team

On Fri, 2016-04-29 at 15:27 -0500, Emilien Macchi wrote: > Hi, > > One of the most urgent tasks we need to achieve in TripleO during > Newton cycle is the composable roles support. > So we decided to build a team that would focus on it during the next > weeks. > > We started this etherpad: >

[openstack-dev] [TripleO]: landing code faster

We've had a run of really spotty CI in TripleO. This is making it really hard to land patches if reviewers aren't online. Specifically we seem to get better CI results when the queue is less full (nights and weekends)... often when core reviewers aren't around. One thing that would help is if

Re: [openstack-dev] [TripleO] Can we create some subteams?

On Mon, 2016-04-11 at 05:54 -0400, John Trowbridge wrote: > Hola OOOers, > > It came up in the meeting last week that we could benefit from a CI > subteam with its own meeting, since CI is taking up a lot of the main > meeting time. > > I like this idea, and think we should do something similar

Re: [openstack-dev] [TripleO] FreeIPA integration

On Tue, 2016-04-05 at 19:19 -0600, Rich Megginson wrote: > On 04/05/2016 07:06 PM, Dan Prince wrote: > > > > On Sat, 2016-04-02 at 17:28 -0400, Adam Young wrote: > > > > > > I finally have enough understanding of what is going on with > > > Tri

Re: [openstack-dev] [TripleO] FreeIPA integration

On Sat, 2016-04-02 at 17:28 -0400, Adam Young wrote: > I finally have enough understanding of what is going on with Tripleo > to  > reasonably discuss how to implement solutions for some of the main  > security needs of a deployment. > > > FreeIPA is an identity management solution that can

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

erately from puppet-swift for example) Given this why would I need say two different version of puppet-swift in my Agent container (which is used to generate configs) for a given upgrade? Dan > > Thanks, > Kevin > From: Dan Prince [dpri...@redhat.com] > Sent: Sunday, April 03, 2

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Mon, 2016-04-04 at 02:31 +, Steven Dake (stdake) wrote: > > On 4/3/16, 6:38 PM, "Dan Prince" <dpri...@redhat.com> wrote: > > > > > > > > > > > On Mon, 2016-03-21 at 16:14 -0400, Zane Bitter wrote: > > > > &g

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Wed, 2016-03-23 at 19:11 +, Fox, Kevin M wrote: > If heat convergence worked (Is that a thing yet?), it could > potentially be used instead of a COE like kubernetes. > > The thing ansible buys us today would be upgradeability. Ansible is > config management, but its also a workflow like

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Mon, 2016-03-21 at 16:14 -0400, Zane Bitter wrote: > As of the Liberty release, Magnum now supports provisioning Mesos  > clusters, so TripleO wouldn't have to maintain the installer for > that  > either. (The choice of Mesos is somewhat unfortunate in our case,  > because Magnum's

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

t; like ansible or a container orchestration system like kubernes to ensure you > dont change too many things at once and break things. You need to be able to > run some old things and some new, all at the same time. And in some cases > different versions/config of > the same service on di

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Wed, 2016-03-23 at 07:54 -0400, Ryan Hallisey wrote: > *Snip* > > > > > Indeed, this has literally none of the benefits of the ideal Heat  > > deployment enumerated above save one: it may be entirely the wrong > > tool  > > in every way for the job it's being asked to do, but at least it > >

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Mon, 2016-03-21 at 16:14 -0400, Zane Bitter wrote: > tl;dr Containers represent a massive, and also mandatory, > opportunity  > for TripleO. Lets start thinking about ways that we can take maximum  > advantage to achieve the goals of the project. > > Now that you have the tl;dr I'm going to

Re: [openstack-dev] [tripleo] becoming third party CI (was: enabling third party CI)

On Thu, 2016-03-10 at 23:24 +, Jeremy Stanley wrote: > On 2016-03-10 16:09:44 -0500 (-0500), Dan Prince wrote: > > > > This seems to be the week people want to pile it on TripleO. > > Talking > > about upstream is great but I suppose I'd rather debate major >

Re: [openstack-dev] [tc][fuel][kolla][osa][tripleo] proposing type:deployment

On Tue, 2016-03-22 at 15:37 +, Steven Dake (stdake) wrote: > > On 3/22/16, 2:15 AM, "Thierry Carrez" wrote: > > > > > Steven Dake (stdake) wrote: > > > > > > Technical Committee, > > > > > > Please accept my proposal of a new type of project called a > > >

[openstack-dev] [TripleO] propose trown for core

I'd like to propose that we add John Trowbridge to the TripleO core review team. John has become one of the goto guys in helping to chase down upstream trunk chasing issues. He has contributed a lot to helping keep general CI issues running and been involved with several new features over the past

[openstack-dev] [TripleO] propose EmilienM for core

I'd like to propose that we add Emilien Macchi to the TripleO core review team. Emilien has been getting more involved with TripleO during this last release. In addition to help with various Puppet things he also has experience in building OpenStack installation tooling, upgrades, and would be a

[openstack-dev] [TripleO] propose ejuaso for core

http://russellbryant.net/openstack-stats/tripleo-reviewers-180.txt Our top reviewer over the last half a year ejuaso (goes by Ozz for Osorio or jaosorior on IRC). His reviews seem consistent, he consistently attends the meetings and he chimes in on lots of things. I'd like to propose we add him

[openstack-dev] [TripleO] core cleanup

Looking at the stats for the last 180 days I'd like to propose we cleanup TripleO core a bit: http://russellbryant.net/openstack-stats/tripleo-reviewers-180.txt There are a few reviewers with low numbers of reviews (just added to the tripleo-ui team, jtomasek and flfuchs). I think those will

Re: [openstack-dev] [tripleo] Logo for TripleO

On Thu, 2016-03-10 at 22:32 -0700, Jason Rist wrote: > Hey everyone - > We've been working on a UI for TripleO for a few months now and > we're > just about to beg to be a part of upstream... and we're in need of a > logo for the login page and header. > > In my evenings, I've come up with

Re: [openstack-dev] [tripleo] becoming third party CI (was: enabling third party CI)

On Thu, 2016-03-10 at 13:45 -0500, Paul Belanger wrote: > On Thu, Mar 10, 2016 at 05:32:15PM +, Jeremy Stanley wrote: > > > > On 2016-03-10 09:50:03 -0500 (-0500), Emilien Macchi wrote: > > [...] > > > > > > OpenStack Infra provides an easy way to plug CI systems and some > > > CIs (Nova,

Re: [openstack-dev] [tripleo] becoming third party CI (was: enabling third party CI)

This seems to be the week people want to pile it on TripleO. Talking about upstream is great but I suppose I'd rather debate major changes after we branch Mitaka. :/ Anyways, might as well get into it now. replies inline On Thu, 2016-03-10 at 17:32 +, Jeremy Stanley wrote: > On

[openstack-dev] [TripleO] Release notes etherpad

Hi TripleO, I've started an etherpad to collect all of the major features that we completed in Mitaka. If you've worked on any major/minor features that you'd like to see go into an official release notes doc could you please add it here along with a detailed description:

Re: [openstack-dev] [tripleo] CI jobs failures

On Tue, 2016-03-08 at 17:58 +, Derek Higgins wrote: > On 7 March 2016 at 18:22, Ben Nemec wrote: > > > > On 03/07/2016 11:33 AM, Derek Higgins wrote: > > > > > > On 7 March 2016 at 15:24, Derek Higgins > > > wrote: > > > > > > > > On 6 March 2016

Re: [openstack-dev] [TripleO] core members for tripleo-ui

On Mon, 2016-02-29 at 18:32 +0100, Ana Krivokapic wrote: > On Mon, Feb 29, 2016 at 4:27 PM, Dan Prince <dpri...@redhat.com> > wrote: > > > > There is a new projects for the ui called tripleo-ui. As most of > > the > > existing TripleO core members aren't g

Re: [openstack-dev] [tripleo] Contributing to TripleO is challenging

While I agree with some (not all) of the sentiment below I'm not sure I want to spend the time debating this rather broad set of topics in this email thread. I'm not sure we'd actually ever see the end of it if we did. Nor can the upstream TripleO team control all the forces at play here. So

Re: [openstack-dev] [tripleo] CI jobs failures

On Sat, 2016-03-05 at 11:15 -0500, Emilien Macchi wrote: > I'm kind of hijacking Dan's e-mail but I would like to propose some > technical improvements to stop having so much CI failures. > > > 1/ Stop creating swap files. We don't have SSD, this is IMHO a > terrible > mistake to swap on files

Re: [openstack-dev] [TripleO] IPv4 network isolation testing update

On Thu, 2016-03-03 at 21:38 -0500, Dan Prince wrote: > Some progress today: > > After rebuilding the test-env workers nodes in our CI rack to support > multiple-nics we got a stack to go into CREATE_COMPLETE with network > isolation enabled in CI. > > https://review.ope

[openstack-dev] [TripleO] IPv4 network isolation testing update

Some progress today: After rebuilding the test-env workers nodes in our CI rack to support multiple-nics we got a stack to go into CREATE_COMPLETE with network isolation enabled in CI. https://review.openstack.org/#/c/288163/ Have a look at the Ceph result here:

[openstack-dev] [TripleO] core members for tripleo-ui

There is a new projects for the ui called tripleo-ui. As most of the existing TripleO core members aren't going to be reviewing UI specific patches is seems reasonable that we might add a few review candidates who can focus specifically on UI specific patches. I'd like to proposed we add Jiri

[openstack-dev] [TripleO] Treating the undercloud as a black box

One of the things I like about TripleO is the way you can use the Undercloud remotely via its APIs to drive everything about your deployment. We don't prevent you from shelling into your undercloud though, and more recently with the switch to use instack and python- tripleoclient our upstream CI

Re: [openstack-dev] [TripleO] Should we rename "RDO Manager" to "TripleO" ?

On Wed, 2016-02-17 at 11:27 -0500, David Moreau Simard wrote: > Greetings, > > (Note: cross-posted between rdo-list and openstack-dev to reach a > larger audience) > > Today, because of the branding and the name "RDO Manager", you might > think that it's something other than TripleO - either

Re: [openstack-dev] [TripleO] Stable branch policy for Mitaka

On Wed, 2016-02-10 at 15:57 +, Steven Hardy wrote: > Hi all, > > We discussed this in our meeting[1] this week, and agreed a ML > discussion > to gain consensus and give folks visibility of the outcome would be a > good > idea. > > In summary, we adopted a more permissive "release branch"

[openstack-dev] [TripleO]: CI outage yesterday/today

Just a quick update about the CI outage today and yesterday. Turns out our jobs weren't running due to a bad Keystone URL (it was pointing to localhost:5000 instead of our public SSL endpoint). We've now fixed that issue and I'm told that as soon as Infra restarts nodepool (they cache the

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Mon, 2016-02-01 at 15:17 +0600, Renat Akhmerov wrote: > Hi, > > I’ve read only part of letters in this huge interesting thread so far > but I’d like to try to jump in and give some comments. > > API > I personally don’t support using Mistral API as is. Maybe you came to > agreement already

Re: [openstack-dev] [tripleo] use mitaka CI tested repo

On Fri, 2016-01-29 at 08:17 -0500, Emilien Macchi wrote: > Hi, > > I'm wondering why don't we use Mitaka CI tested repository [1]. > IIRC, TripleO is currently using a snapshot which is updated > asynchronously by TripleO CI folks. > The problem is that we're not consistent with what RDO CI is

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Wed, 2016-01-27 at 09:36 -0500, Dan Prince wrote: > On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote: > > On 01/26/2016 09:05 PM, Ben Nemec wrote: > > > On 01/25/2016 04:36 PM, Dan Prince wrote: > > > > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: &g

Re: [openstack-dev] [TripleO] spec-lite process for tripleo

On Wed, 2016-01-27 at 16:21 +, Derek Higgins wrote: > Hi All, > > We briefly discussed feature tracking in this weeks tripleo meeting. > I  > would like to provide a way for downstream consumers (and ourselves) > to  > track new features as they get implemented. The main things that > came  >

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Tue, 2016-01-26 at 14:05 -0600, Ben Nemec wrote: > On 01/25/2016 04:36 PM, Dan Prince wrote: > > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: > > > On 01/22/2016 06:19 PM, Dan Prince wrote: > > > > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote:

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Wed, 2016-01-27 at 14:32 +0100, Jiri Tomasek wrote: > On 01/26/2016 09:05 PM, Ben Nemec wrote: > > On 01/25/2016 04:36 PM, Dan Prince wrote: > > > On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: > > > > On 01/22/2016 06:19 PM, Dan Prince wrote: > > >

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Tue, 2016-01-26 at 09:56 -0500, James Slagle wrote: > > > On Tue, Jan 26, 2016 at 9:08 AM, Steven Hardy > wrote: > > On Tue, Jan 26, 2016 at 07:40:05AM -0500, James Slagle wrote: > > >    On Tue, Jan 26, 2016 at 4:46 AM, Steven Hardy > om> wrote: > > > >

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Mon, 2016-01-25 at 15:08 -0500, James Slagle wrote: > > > On Mon, Jan 25, 2016 at 1:09 PM, Dan Prince <dpri...@redhat.com> > wrote: > >   > > As for tripleo-heat-templates... sure it hasn't been an entirely > > smooth > > ride. I think a l

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Tue, 2016-01-26 at 09:23 -0500, Tzu-Mainn Chen wrote: > - Original Message - > > On Mon, Jan 25, 2016 at 05:45:30PM -0600, Ben Nemec wrote: > > > On 01/25/2016 03:56 PM, Steven Hardy wrote: > > > > On Fri, Jan 22, 2016 at 11:24:20AM -0600, Ben Nemec wrote: > > > > > So I haven't weighed

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Mon, 2016-01-25 at 06:55 -0800, Clint Byrum wrote: > Excerpts from Jiri Tomasek's message of 2016-01-25 06:09:33 -0800: > > On 01/25/2016 12:42 AM, Clint Byrum wrote: > > > Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: > > > > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Mon, 2016-01-25 at 09:32 -0500, James Slagle wrote: > > > On Mon, Jan 25, 2016 at 9:09 AM, Jiri Tomasek > wrote: > > On 01/25/2016 12:42 AM, Clint Byrum wrote: > > >  Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: > > > > > >   > > > >  I actually

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Sun, 2016-01-24 at 15:42 -0800, Clint Byrum wrote: > Excerpts from Dan Prince's message of 2016-01-22 16:19:07 -0800: > > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > > > So I haven't weighed in on this yet, in part because I was on > > > vacation > > > when it was first proposed and

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Mon, 2016-01-25 at 15:08 -0500, James Slagle wrote: > > > On Mon, Jan 25, 2016 at 1:09 PM, Dan Prince <dpri...@redhat.com> > wrote: > >   > > As for tripleo-heat-templates... sure it hasn't been an entirely > > smooth > > ride. I think a l

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Mon, 2016-01-25 at 15:31 -0600, Ben Nemec wrote: > On 01/22/2016 06:19 PM, Dan Prince wrote: > > On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > > > So I haven't weighed in on this yet, in part because I was on > > > vacation > > > when it

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Fri, 2016-01-22 at 11:24 -0600, Ben Nemec wrote: > So I haven't weighed in on this yet, in part because I was on > vacation > when it was first proposed and missed a lot of the initial > discussion, > and also because I wanted to take some time to order my thoughts on > it. >  Also because my

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

I gave a couple of ad-hoc demo's of my Mistral dev environment this week. For those interested in tinkering with TripleO Mistral actions in tripleo-common here are links to the code I used for those. Still a rough prototype but hopefully demonstrates how these things might work:

Re: [openstack-dev] [TripleO] add support for other types of virtual switches in os_net_config

On Thu, 2016-01-21 at 16:05 -0800, Xin Wu wrote: > Hi, all > >      This is Xin from Big Switch. I'm proposing to make os_net_config > support more types of virtual switches. >      Current os_net_config supports ovs_bridge, linux_bridge and > different types of interfaces associated with ovs and

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: > > - Original Message - > > On Wed, Jan 13, 2016 at 04:41:28AM -0500, Tzu-Mainn Chen wrote: > > > Hey all, > > > > > > I realize now from the title of the other TripleO/Mistral thread > > > [1] that > > > the discussion there may

Re: [openstack-dev] [TripleO] Removing unused/deprecated template parameters?

On Tue, 2016-01-12 at 20:47 +, Steven Hardy wrote: > Hi all, > > I've noticed that we have a fairly large number of unused parameters > in > t-h-t, some of which are marked deprecated, some aren't. > > Since we moved tripleoclient to use parameter_defaults everywhere, I > think > it should

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

On Wed, 2016-01-13 at 04:41 -0500, Tzu-Mainn Chen wrote: > Hey all, > > I realize now from the title of the other TripleO/Mistral thread [1] > that > the discussion there may have gotten confused.  I think using Mistral > for > TripleO processes that are obviously workflows - stack deployment, >

Re: [openstack-dev] [TripleO] Driving workflows with Mistral

On Tue, 2016-01-12 at 12:52 +0100, Jiri Tomasek wrote: > On 01/11/2016 04:51 PM, Dan Prince wrote: > > Background info: > > > > We've got a problem in TripleO at the moment where many of our > > workflows can be driven by the command line only. This causes some &g

Re: [openstack-dev] [TripleO] Driving workflows with Mistral

On Tue, 2016-01-12 at 13:24 -0500, Ryan Brown wrote: > On 01/12/2016 10:50 AM, Jiri Tomasek wrote: > > On 01/12/2016 04:22 PM, Ryan Brown wrote: > > > On 01/12/2016 06:52 AM, Jiri Tomasek wrote: > > > > On 01/11/2016 04:51 PM, Dan Prince wrote: > > > > >

[openstack-dev] [TripleO] Driving workflows with Mistral

Background info: We've got a problem in TripleO at the moment where many of our workflows can be driven by the command line only. This causes some problems for those trying to build a UI around the workflows in that they have to duplicate deployment logic in potentially multiple places. There are

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On Tue, 2015-12-22 at 15:36 +, Dougal Matthews wrote: > Hi all, > > This topic came up in the 2015-12-15 meeting[1], and again briefly > today. > After working with the code that came out of the deployment library > spec[2] I > had some concerns with how we are storing the templates. > >

[openstack-dev] [TripleO] no meeting tomorrow

The next TripleO IRC meeting will be on January 5th 2016. Thanks, Dan __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On Tue, 2015-12-22 at 15:36 +, Dougal Matthews wrote: > Hi all, > > This topic came up in the 2015-12-15 meeting[1], and again briefly > today. > After working with the code that came out of the deployment library > spec[2] I > had some concerns with how we are storing the templates. > >

Re: [openstack-dev] [TripleO] Stable/Liberty Backports & Reviews

Nice job on this. Looking forward to reaping the benefits of the stable branch stuff for our upgrades testing too. Dan On Fri, 2015-12-11 at 12:35 +, Steven Hardy wrote: > Hi all, > > So, after the painful process of getting CI working for > stable/liberty, > everything is now working

Re: [openstack-dev] [tripleo] Pin some puppet dependencies on git clone

On Fri, 2015-12-11 at 21:50 +0100, Jaume Devesa wrote: > Hi all, > > Today TripleO CI jobs failed because a new commit introduced on > puppetlabs-mysql[1]. > Mr. Jiri Stransky solved it as a temporally fix by pinning the puppet > module clone to a previous > commit in the tripleo-common

Re: [openstack-dev] [TripleO] workflow

On Mon, 2015-12-07 at 16:00 +, Dougal Matthews wrote: > > > On 7 December 2015 at 14:59, Dan Prince <dpri...@redhat.com> wrote: > > > > > > > > On Thu, 2015-12-03 at 15:47 -0500, Dan Prince wrote: > > > On Tue, 2015-11-24 at 15:25 +, Do

Re: [openstack-dev] [TripleO] workflow

On Thu, 2015-12-03 at 15:47 -0500, Dan Prince wrote: > On Tue, 2015-11-24 at 15:25 +, Dougal Matthews wrote: > > On 23 November 2015 at 14:37, Dan Prince <dpri...@redhat.com> > > wrote: > > > There are lots of references to "workflow" within TripleO

Re: [openstack-dev] [heat][tripleo] User Initiated Rollback

On Wed, 2015-12-02 at 16:02 +, Steven Hardy wrote: > So, chatting with Giulio today about https://bugs.launchpad.net/heat/ > +bug/1521944 > has be thinking about $subject. > > The root case of that issue is essentially a corner case of a stack- > update, > combined with some coupling within

Re: [openstack-dev] [TripleO] workflow

On Tue, 2015-11-24 at 15:25 +, Dougal Matthews wrote: > On 23 November 2015 at 14:37, Dan Prince <dpri...@redhat.com> wrote: > > There are lots of references to "workflow" within TripleO > > conversations > > these days. We are at (or near) the li

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

On Thu, 2015-11-19 at 16:16 +, Steven Hardy wrote: > On Mon, Nov 16, 2015 at 08:15:48PM +0100, Giulio Fidente wrote: > > On 11/16/2015 04:25 PM, Steven Hardy wrote: > > > Hi all, > > > > > > I wanted to start some discussion re $subject, because it's been > > > apparrent > > > that we have a

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

On Fri, 2015-11-20 at 16:53 +0100, Jiri Tomasek wrote: > On 11/16/2015 04:25 PM, Steven Hardy wrote: > > Hi all, > > > > I wanted to start some discussion re $subject, because it's been > > apparrent > > that we have a lack of clarity on this issue (and have done ever > > since we > > started

Re: [openstack-dev] [ironic][security] what is OK to put in DEBUG logs?

On Mon, 2015-11-23 at 11:43 -0500, Ruby Loo wrote: > On 20 November 2015 at 18:32, Ben Nemec > wrote: > > On 11/19/2015 06:00 AM, Lucas Alvares Gomes wrote: > > > Hi, > > > > > >> Also keep in mind that DEBUG logging, while still should have > > some masking > > >> of

[openstack-dev] [TripleO] workflow

There are lots of references to "workflow" within TripleO conversations these days. We are at (or near) the limit of what we can do within Heat with regards to upgrades. We've got a new TripleO API in the works (a new version of Tuskar basically) that is specifically meant to encapsulates business

Re: [openstack-dev] [TripleO] Proposing Ian Wienand as core reviewer on diskimage-builder

On Tue, 2015-11-03 at 15:25 +, Gregory Haynes wrote: > Hello everyone, > > I would like to propose adding Ian Wienand as a core reviewer on the > diskimage-builder project. Ian has been making a significant number > of > contributions for some time to the project, and has been a great help >

[openstack-dev] [TripleO] Summit etherpads

In case you haven't found this yet the TripleO etherpad locations are all documented here: https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#TripleO Dan __ OpenStack Development Mailing List (not for usage

[openstack-dev] [TripleO] weekly TripleO meetings starting Nov. 3rd

In today's IRC meeting we agreed that weekly TripleO meetings would again be useful. So starting Nov. 3rd (the week after the Tokyo Summit) we tentatively plan on resuming weekly meetings at 14:00 UTC on Tuesdays. https://review.openstack.org/#/c/237609/ Dan

Re: [openstack-dev] [TripleO] Auto-abandon bot

On Mon, 2015-10-12 at 11:38 -0500, Ben Nemec wrote: > On 10/10/2015 08:12 AM, Jeremy Stanley wrote: > > On 2015-10-09 17:10:15 -0500 (-0500), Ben Nemec wrote: > > > As discussed in the meeting a week or two ago, we would like to > > > bring > > > back the auto-abandon functionality for old,

Re: [openstack-dev] [TripleO] review priorities etherpad

On Tue, 2015-10-13 at 10:32 +0300, marios wrote: > On 10/10/15 00:16, Dan Prince wrote: > > On Thu, 2015-10-08 at 09:17 -0400, James Slagle wrote: > > > At the TripleO meething this week, we talked about using an > > > etherpad > > speaking of which - and given

Re: [openstack-dev] [TripleO] review priorities etherpad

On Thu, 2015-10-08 at 09:17 -0400, James Slagle wrote: > At the TripleO meething this week, we talked about using an etherpad > to help get some organization around reviews for the high priority > themes in progress. > > I started on one: >

[openstack-dev] [TripleO] meeting tomorrow

Our team meeting is tomorrow at 14:00 UTC. I made a couple changes to the agenda this week and added a new sections called "Review Highlights" which I hope will help us discuss and move forward some patches that look promising: https://wiki.openstack.org/wiki/Meetings/TripleO#Review_Highlights

Re: [openstack-dev] [tripleo] How to selectively enable new services?

On Wed, 2015-09-30 at 21:05 +0100, Steven Hardy wrote: > Hi all, > > So I wanted to start some discussion on $subject, because atm we have > a > couple of patches adding support for new services (which is great!): > > Manila: https://review.openstack.org/#/c/188137/ > Sahara:

Re: [openstack-dev] [TripleO] tripleo.org theme

On Fri, 2015-09-25 at 12:31 -0500, Ben Nemec wrote: > On 09/25/2015 07:34 AM, Dan Prince wrote: > > It has come to my attention that we aren't making great use of our > > tripleo.org domain. One thing that would be useful would be to have > > the > > new tri

Re: [openstack-dev] [TripleO] tripleo.org theme

On Mon, 2015-09-28 at 09:43 -0400, James Slagle wrote: > On Fri, Sep 25, 2015 at 8:34 AM, Dan Prince <dpri...@redhat.com> > wrote: > > It has come to my attention that we aren't making great use of our > > tripleo.org domain. One thing that would be useful would be to have

Re: [openstack-dev] [TripleO] tripleo.org theme

On Mon, 2015-09-28 at 16:04 +, Jeremy Stanley wrote: > On 2015-09-28 09:43:37 -0400 (-0400), James Slagle wrote: > > Would the content of tripleo-docs be exactly the same as what is > > published at http://docs.openstack.org/developer/tripleo-docs/ ? > > > > I think it probably should be, and

[openstack-dev] [TripleO] tripleo.org theme

It has come to my attention that we aren't making great use of our tripleo.org domain. One thing that would be useful would be to have the new tripleo-docs content displayed there. It would also be nice to have quick links to some of our useful resources, perhaps Derek's CI report [1], a custom

[openstack-dev] [TripleO] PTL candidacy

Hi TripleO, My name is Dan Prince and I'm running for the Mitaka TripleO PTL. I've been working on TripleO since Grizzly and OpenStack since Bexar. I care deeply about the project and would like to continue the vision of deploying OpenStack w/ OpenStack. TripleO has come a long way over the past

Re: [openstack-dev] [TripleO][Heat] instance_user fallout, keeping the 'heat-admin' user working

On Wed, 2015-09-02 at 20:32 -0400, James Slagle wrote: > On Wed, Sep 2, 2015 at 4:22 PM, Dan Prince <dpri...@redhat.com> > wrote: > > We had an IRC discussion today about the 'heat-admin' user in > > #tripleo. > > > > Upstream Heat recently reverted the 'i

[openstack-dev] [TripleO][Heat] instance_user fallout, keeping the 'heat-admin' user working

We had an IRC discussion today about the 'heat-admin' user in #tripleo. Upstream Heat recently reverted the 'instance_user' config file option which we relied on in TripleO to standardize the default (admin) user on our nodes. It is my understanding that Heat would prefer not to maintain this

Re: [openstack-dev] [kolla][tripleo] Deprecating config-internal

On Fri, 2015-08-07 at 14:21 +, Steven Dake (stdake) wrote: James and Dan, During the ansible-multi spec process that James Slagle reviewed, there was a serious commitment by the Kolla core team to maintain config-internal, pretty much for the tripleo use case. We didn’t want to

Re: [openstack-dev] [TripleO] Moving instack upstream

On Thu, 2015-08-06 at 16:54 -0400, James Slagle wrote: On Thu, Aug 6, 2015 at 8:12 AM, Dan Prince dpri...@redhat.com wrote: One more side effect is that I think it also means we no longer have the capability to test arbitrary Zuul refspecs for projects like Heat, Neutron, Nova

Re: [openstack-dev] [TripleO] Moving instack upstream

On Thu, 2015-07-23 at 07:40 +0100, Derek Higgins wrote: See below On 21/07/15 20:29, Derek Higgins wrote: Hi All, Something we discussed at the summit was to switch the focus of tripleo's deployment method to deploy using instack using images built with tripleo-puppet-elements.

[openstack-dev] [TripleO] [Puppet] Deploying OpenStack with Puppet modules on Docker with Heat

Hi, There is a lot of interest in getting support for container based deployment within TripleO and many different ideas and opinions on how to go about doing that. One idea on the table is to use Heat to help orchestrate the deployment of docker containers. This would work similar to our

[openstack-dev] [TripleO] package based overcloud upgrades

Hi, I put together a quick etherpad to help outline the remaining patches left to support package based upgrades within the TripleO heat templates: https://etherpad.openstack.org/p/tripleo-package-upgrades The etherpad includes a brief overview of the upgrade approach, a list of patches related

Re: [openstack-dev] [TripleO] package based overcloud upgrades

On Thu, 2015-06-25 at 12:01 -0700, Dan Smith wrote: Hi Dan, I put together a quick etherpad to help outline the remaining patches left to support package based upgrades within the TripleO heat templates: https://etherpad.openstack.org/p/tripleo-package-upgrades The etherpad

[openstack-dev] [TripleO] a bad week for CI

Last week was a really bad week for TripleO CI. Several breaking changes (2 of which Fedora package related) kept at least a subset of the jobs down for over half the week. Here is a brief summary of the issues we hit along with links to some of the work arounds. Fedora 21: python-address package

[openstack-dev] [TripleO] isolated networks: teasing apart the overcloud traffic

Hi, I wanted to send an email out to introduce a new idea in TripleO about how we can go about configuring isolated networks for our baremetal Overcloud traffic. The thoughts here are largely about the ability to split out the baremetal Overcloud traffic via our tooling (Heat templates). What

Re: [openstack-dev] [TripleO] puppet pacemaker thoughts... and an idea

On Thu, 2015-05-07 at 09:10 -0400, Jay Dobies wrote: On 05/07/2015 06:01 AM, Giulio Fidente wrote: On 05/07/2015 11:15 AM, marios wrote: On 07/05/15 05:32, Dan Prince wrote: [..] Something like this: https://review.openstack.org/#/c/180833/ +1 I like this as an idea. Given

Re: [openstack-dev] [TripleO] puppet pacemaker thoughts... and an idea

On Fri, 2015-05-08 at 11:41 -0400, James Slagle wrote: On Thu, May 7, 2015 at 5:46 PM, Giulio Fidente gfide...@redhat.com wrote: On 05/07/2015 07:35 PM, Dan Prince wrote: On Thu, 2015-05-07 at 17:36 +0200, Giulio Fidente wrote: On 05/07/2015 03:31 PM, Dan Prince wrote: On Thu, 2015

<    1   2   3   >