Re: [openstack-dev] [TripleO] Propose adding StevenK to core reviewers

On 9.9.2014 20:32, Gregory Haynes wrote: Hello everyone! I have been working on a meta-review of StevenK's reviews and I would like to propose him as a new member of our core team. +1 As I'm sure many have noticed, he has been above our stats requirements for several months now. More

[openstack-dev] [TripleO] Tuskar CLI after architecture changes

Hi all, TL;DR: I believe that As an infrastructure administrator, Anna wants a CLI for managing the deployment providing the same fundamental features as UI. With the planned architecture changes (making tuskar-api thinner and getting rid of proxying to other services), there's not an obvious

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

A few clarifications added, next time i'll need to triple-read after myself :) On 11.12.2013 13:33, Jiří Stránský wrote: Hi all, TL;DR: I believe that As an infrastructure administrator, Anna wants a CLI for managing the deployment providing the same fundamental features as UI

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

proxying from tuskar API to other APIs is looked down upon. Jiri and I had been talking yesterday and he mentioned it to me when I started to ask these same sorts of questions. On 12/11/2013 07:33 AM, Jiří Stránský wrote: Hi all, TL;DR: I believe that As an infrastructure administrator, Anna wants

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 12.12.2013 11:49, Radomir Dopieralski wrote: On 11/12/13 13:33, Jiří Stránský wrote: [snip] TL;DR: I believe that As an infrastructure administrator, Anna wants a CLI for managing the deployment providing the same fundamental features as UI. With the planned architecture changes (making

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 12.12.2013 14:26, Jiří Stránský wrote: On 12.12.2013 11:49, Radomir Dopieralski wrote: On 11/12/13 13:33, Jiří Stránský wrote: [snip] TL;DR: I believe that As an infrastructure administrator, Anna wants a CLI for managing the deployment providing the same fundamental features as UI

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 12.12.2013 17:10, Mark McLoughlin wrote: On Wed, 2013-12-11 at 13:33 +0100, Jiří Stránský wrote: Hi all, TL;DR: I believe that As an infrastructure administrator, Anna wants a CLI for managing the deployment providing the same fundamental features as UI. With the planned architecture

Re: [openstack-dev] [TripleO] Tuskar CLI after architecture changes

On 21.12.2013 06:10, Jay Pipes wrote: On 12/20/2013 11:34 AM, Clint Byrum wrote: Excerpts from Radomir Dopieralski's message of 2013-12-20 01:13:20 -0800: On 20/12/13 00:17, Jay Pipes wrote: On 12/19/2013 04:55 AM, Radomir Dopieralski wrote: On 14/12/13 16:51, Jay Pipes wrote: [snip]

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

On 13.1.2014 11:43, Jaromir Coufal wrote: On 2014/10/01 21:17, Jay Dobies wrote: Another question: - A Role (sounds like we're moving away from that so I'll call it Resource Category) can have multiple Node Profiles defined (assuming I'm interpretting the + and the tabs in the Create a Role

Re: [openstack-dev] [TripleO][Tuskar] Editing Nodes

On 15.1.2014 14:07, James Slagle wrote: I'll start by laying out how I see editing or updating nodes working in TripleO without Tuskar: To do my initial deployment: 1. I build a set of images for my deployment for different roles. The images are different based on their role, and only contain

Re: [openstack-dev] [TripleO] [Ironic] Roadmap towards heterogenous hardware support

On 01/30/2014 11:26 AM, Tomas Sedovic wrote: 1.1 Treat similar hardware configuration as equal The way I understand it is this: we use a scheduler filter that wouldn't do a strict match on the hardware in Ironic. E.g. if our baremetal flavour said 16GB ram and 1TB disk, it would also match a

Re: [openstack-dev] [TripleO][Tuskar] Dealing with passwords in Tuskar-API

On 20.2.2014 12:18, Radomir Dopieralski wrote: On 20/02/14 12:02, Radomir Dopieralski wrote: Anybody who gets access to Tuskar-API gets the passwords, whether we encrypt them or not. Anybody who doesn't have access to Tuskar-API doesn't get the passwords, whether we encrypt them or not. Yeah,

[openstack-dev] [TripleO] Tuskar CLI UX

Hello, i went through the CLI way of deploying overcloud, so if you're interested what's the workflow, here it is: https://gist.github.com/jistr/9228638 I'd say it's still an open question whether we'll want to give better UX than that ^^ and at what cost (this is very much tied to the

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On 26.2.2014 20:43, Jay Dobies wrote: I'd say it's still an open question whether we'll want to give better UX than that ^^ and at what cost (this is very much tied to the benefits and drawbacks of various solutions we discussed in December [1]). All in all it's not as bad as i expected it to be

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On 27.2.2014 10:16, Dougal Matthews wrote: On 26/02/14 13:34, Jiří Stránský wrote: get Tuskar UI a bit closer back to the fact that Undercloud is OpenStack too, and keep the name Flavors instead of changing it to Node Profiles. I wonder if that would be unwelcome to the Tuskar UI UX, though

Re: [openstack-dev] [TripleO] Tuskar CLI UX

On 26.2.2014 21:34, Dean Troyer wrote: On Wed, Feb 26, 2014 at 1:43 PM, Jay Dobies jason.dob...@redhat.com wrote: I like the notion of OpenStackClient. I'll talk ideals for a second. If we had a standard framework and each project provided a command abstraction that plugged in, we could pick

[openstack-dev] [TripleO] os-cloud-config ssh access to cloud

Hi, there's one step in cloud initialization that is performed over SSH -- calling keystone-manage pki_setup. Here's the relevant code in keystone-init [1], here's a review for moving the functionality to os-cloud-config [2]. The consequence of this is that Tuskar will need passwordless ssh

Re: [openstack-dev] [TripleO] os-cloud-config ssh access to cloud

On 7.3.2014 14:50, Imre Farkas wrote: On 03/07/2014 10:30 AM, Jiří Stránský wrote: Hi, there's one step in cloud initialization that is performed over SSH -- calling keystone-manage pki_setup. Here's the relevant code in keystone-init [1], here's a review for moving the functionality to os

Re: [openstack-dev] [TripleO] os-cloud-config ssh access to cloud

-10 17:10 GMT+04:00 Jiří Stránský ji...@redhat.com: On 7.3.2014 14:50, Imre Farkas wrote: On 03/07/2014 10:30 AM, Jiří Stránský wrote: Hi, there's one step in cloud initialization that is performed over SSH -- calling keystone-manage pki_setup. Here's the relevant code in keystone-init [1

Re: [openstack-dev] [TripleO] [Heat] os-cloud-config ssh access to cloud

On 12.3.2014 17:03, Jiří Stránský wrote: Thanks for all the replies everyone :) I'm leaning towards going the way Robert suggested on the review [1] - upload pre-created signing cert, signing key and CA cert to controller nodes using Heat. This seems like a much cleaner approach

Re: [openstack-dev] [TripleO] [Heat] os-cloud-config ssh access to cloud

On 14.3.2014 14:42, Steven Dake wrote: On 03/14/2014 06:33 AM, Jiří Stránský wrote: On 12.3.2014 17:03, Jiří Stránský wrote: Thanks for all the replies everyone :) I'm leaning towards going the way Robert suggested on the review [1] - upload pre-created signing cert, signing key and CA cert

Re: [openstack-dev] [TripleO] [Heat] os-cloud-config ssh access to cloud

On 16.3.2014 21:20, Steve Baker wrote: On 15/03/14 02:33, Jiří Stránský wrote: On 12.3.2014 17:03, Jiří Stránský wrote: Thanks for all the replies everyone :) I'm leaning towards going the way Robert suggested on the review [1] - upload pre-created signing cert, signing key and CA cert

Re: [openstack-dev] [TripleO] os-cloud-config ssh access to cloud

(Removing [Heat] from the subject.) So here are the steps i think are necessary to get the PKI setup done and safely passed through Jenkins. If anyone thinks something is redundant or missing, please shout: 1. Patch to os-cloud-config: * Generation of keys and certs for cases user doesn't

Re: [openstack-dev] [TripleO] [Horizon] Searching for a new name for Tuskar UI

On 27.3.2014 18:21, Dougal Matthews wrote: On 27/03/14 15:56, Jaromir Coufal wrote: Hi OpenStackers, User interface which is managing the OpenStack Infrastructure is currently named Tuskar-UI because of historical reasons. Tuskar itself is a small service, which is giving logic into generating

Re: [openstack-dev] [TripleO] reviewer update march

On 3.4.2014 13:02, Robert Collins wrote: Getting back in the swing of things... Hi, like most OpenStack projects we need to keep the core team up to date: folk who are not regularly reviewing will lose context over time, and new folk who have been reviewing regularly should be trusted with

Re: [openstack-dev] [TRIPLEO] tripleo-core update october

Clint and Monty, thank you for such good responses. I am new in TripleO team indeed and I was mostly concerned by the line in the sand. Your responses shed some more light on the issue for me and i hope we'll be heading the right way :) Thanks Jiri

Re: [openstack-dev] [TripleO] TripleO core reviewer update - november

On 30.10.2013 10:06, Robert Collins wrote: Hi, like most OpenStack projects we need to keep the core team up to date: folk who are not regularly reviewing will lose context over time, and new folk who have been reviewing regularly should be trusted with -core responsibilities. In this months

Re: [openstack-dev] [TripleO] Version numbering of TripleO releases

On 31.10.2013 06:09, Roman Podoliaka wrote: Hi all, 0.MAJOR.MINOR versioning totally makes sense to me until we get to 1.0.0. Just a couple of examples of releases we are doing this week: 1) tripleo-image-elements is bumped from 0.0.8 to 0.1.0 (we introduced a kind of incompatible change by

Re: [openstack-dev] [TripleO] Summit session wrapup

Hi all, just a few thoughts (subjective opinions) regarding the whole debate: * I think that having a manually picking images for machines approach would make TripleO more usable in the beginning. I think it will take a good deal of time to get our smart solution working with the admin

Re: [openstack-dev] [Tripleo] Core reviewer update Dec

On 4.12.2013 08:12, Robert Collins wrote: Hi, like most OpenStack projects we need to keep the core team up to date: folk who are not regularly reviewing will lose context over time, and new folk who have been reviewing regularly should be trusted with -core responsibilities. In this

Re: [openstack-dev] [TripleO] Proposal to add Jon Paul Sullivan and Alexis Lee to core review team

On 9.7.2014 17:52, Clint Byrum wrote: So, I propose that we add jonpaul-sullivan and lxsli to the TripleO core reviewer team. +1 Jirka ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org

Re: [openstack-dev] [TripleO][Tuskar] Feedback on init-keystone spec

On 30.4.2014 09:02, Steve Kowalik wrote: Hi, I'm looking at moving init-keystone from tripleo-incubator to os-cloud-config, and I've drafted a spec at https://etherpad.openstack.org/p/tripleo-init-keystone-os-cloud-config . Feedback welcome. Cheers, Hi Steve, that looks

Re: [openstack-dev] [tripleO] Should #tuskar business be conducted in the #tripleo channel?

On 30.5.2014 11:06, Tomas Sedovic wrote: On 30/05/14 02:08, James Slagle wrote: On Thu, May 29, 2014 at 12:25 PM, Anita Kuno ante...@anteaya.info wrote: As I was reviewing this patch today: https://review.openstack.org/#/c/96160/ It occurred to me that the tuskar project is part of the

Re: [openstack-dev] [Tuskar] [TripleO] The vision and looking ahead

On 19.9.2013 10:08, Tomas Sedovic wrote: Hi everyone, Some of us Tuskar developers have had the chance to meet the TripleO developers face to face and discuss the visions and goals of our projects. Tuskar's ultimate goal is to have to a full OpenStack management solution: letting the cloud

Re: [openstack-dev] [TripleO] Core reviewer update proposal

On 5.5.2015 13:57, James Slagle wrote: Hi, I'd like to propose adding Giulio Fidente and Steve Hardy to TripleO Core. Giulio has been an active member of our community for a while. He worked on the HA implementation in the elements and recently has been making a lot of valuable contributions

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

Hi Dan, On 7.5.2015 04:32, Dan Prince wrote: Looking over some of the Puppet pacemaker stuff today. I appreciate all the hard work going into this effort but I'm not quite happy about all of the conditionals we are adding to our puppet overcloud_controller.pp manifest. Specifically it seems

[openstack-dev] [TripleO] HA CI job is green, please consider it when merging patches

Hi all, after an epic battle with bugs this week, we have a passing CI job for HA. Looking at the jobs which ran during last night, the success rate is decent (14 all-green runs vs. just 1 run where HA job was the sole CI failure). I'm a bit reluctant still to say let's make it voting right

Re: [openstack-dev] [tripleo] Plugin integration and environment file naming

On 8.9.2015 10:40, Steven Hardy wrote: Hi all, So, lately we're seeing an increasing number of patches adding integration for various third-party plugins, such as different neutron and cinder backends. This is great to see, but it also poses the question of how we organize the user-visible

Re: [openstack-dev] [tripleo] Plugin integration and environment file naming

On 8.9.2015 13:47, Jiří Stránský wrote: Apart from "cinder" and "neutron-ml2" directories, we could also have a "combined" (or sth similar) directory for env files which combine multiple other env files. The use case which i see is for extra pre-deployment config

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

On 15.12.2015 17:46, Emilien Macchi wrote: For information, Puppet OpenStack CI is consistent for unit & functional tests, we use a single (versionned) Puppetfile: https://github.com/openstack/puppet-openstack-integration/blob/master/Puppetfile TripleO folks might want to have a look at this to

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

On 15.12.2015 19:12, Emilien Macchi wrote: On 12/15/2015 12:23 PM, Jiří Stránský wrote: On 15.12.2015 17:46, Emilien Macchi wrote: For information, Puppet OpenStack CI is consistent for unit & functional tests, we use a single (versionned) Puppetfile: https://github.com/openstack/pu

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

My personal preference is to say: 1. Any templates which are included in the default environment (e.g overcloud-resource-registry-puppet.yaml), must expose their parameters via overcloud-without-mergepy.yaml 2. Any templates which are included in the default environment, but via a "noop"

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

On 26.11.2015 14:12, Jiří Stránský wrote: My personal preference is to say: 1. Any templates which are included in the default environment (e.g overcloud-resource-registry-puppet.yaml), must expose their parameters via overcloud-without-mergepy.yaml 2. Any templates which are included

Re: [openstack-dev] [TripleO] Deploy Overcloud Keystone in HTTPD

On 19.1.2016 03:59, Adam Young wrote: I have a review here for switching Keystone to HTTPD https://review.openstack.org/#/c/269377/ But I have no idea how to kick off the CI to really test it. The check came back way too quick for it to have done a full install; less than 3 minutes. I think

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

+1 On 29.2.2016 16:27, Dan Prince wrote: 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

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

On 18.1.2016 19:49, Tzu-Mainn Chen wrote: - Original Message - 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

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

+1 On 14.3.2016 15:38, Dan Prince wrote: 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

Re: [openstack-dev] [TripleO] Aodh upgrades - Request backport exception for stable/liberty

On 16.5.2016 23:54, Pradeep Kilambi wrote: On Mon, May 16, 2016 at 3:33 PM, James Slagle wrote: On Mon, May 16, 2016 at 10:34 AM, Pradeep Kilambi wrote: Hi Everyone: I wanted to start a discussion around considering backporting Aodh to

Re: [openstack-dev] [tripleo] State of upgrade CLI commands

On 16.8.2016 21:08, Brad P. Crochet wrote: Hello TripleO-ians, I've started to look again at the introduced, but unused/undocumented upgrade commands. It seems to me that given the current state of the upgrade process (at least from Liberty -> Mitaka), these commands make a lot less sense. I

Re: [openstack-dev] [TripleO] Proposing Dmitry Tantsur and Alex Schultz as instack-undercloud cores

On 31.1.2017 19:08, Ben Nemec wrote: On 01/31/2017 11:03 AM, James Slagle wrote: On Tue, Jan 31, 2017 at 11:02 AM, Ben Nemec wrote: In the spirit of all the core team changes, here are a couple more I'd like to propose. Dmitry has been very helpful reviewing in

Re: [openstack-dev] [tripleo] Update TripleO core members

On 23.1.2017 20:03, Emilien Macchi wrote: Greeting folks, I would like to propose some changes in our core members: - Remove Jay Dobies who has not been active in TripleO for a while (thanks Jay for your hard work!). - Add Flavio Percoco core on tripleo-common and tripleo-heat-templates docker

Re: [openstack-dev] [tripleo] Proposing Honza Pokorny core on tripleo-ui

On 24.1.2017 14:52, Emilien Macchi wrote: I have been discussed with TripleO UI core reviewers and it's pretty clear Honza's work has been valuable so we can propose him part of Tripleo UI core team. His quality of code and reviews make him a good candidate and it would also help the other 2

Re: [openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

On 24.1.2017 18:03, Juan Antonio Osorio wrote: Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both on the current CI solution and in getting tripleo-quickstart jobs for it); So I would like to propose him as part of the TripleO CI core team. +1 I think he'll make a great

Re: [openstack-dev] [heat][yaql] Deep merge map of lists?

On 30.8.2016 10:17, Steven Hardy wrote: Yeah, that gets us closer, but we do need to handle more than one value (list entry) per key, e.g: data: l: - "gnocchi_metricd_node_names": ["a0", "a1", "a2"] "tripleo_packages_node_names": ["a0", "a1",

Re: [openstack-dev] [heat][yaql] Deep merge map of lists?

expression: $.data.l.reduce($1.mergeWith($2)) Or maybe it's better with seed value for reduce, just in case: $.data.l.reduce($1.mergeWith($2), {}) Jirka __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [heat][yaql] Deep merge map of lists?

On 30.8.2016 18:16, Zane Bitter wrote: On 30/08/16 12:02, Steven Hardy wrote: debug_tripleo2: value: yaql: expression: $.data.l.reduce($1.mergeWith($2)) data: l: - "gnocchi_metricd_node_names": ["overcloud-controller-0",

Re: [openstack-dev] [heat][yaql] Deep merge map of lists?

On 30.8.2016 18:02, Steven Hardy wrote: On Tue, Aug 30, 2016 at 04:10:47PM +0200, Jiří Stránský wrote: On 30.8.2016 10:17, Steven Hardy wrote: Yeah, that gets us closer, but we do need to handle more than one value (list entry) per key, e.g: data: l

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

+1, Michele does great reviews, and his contributions around HA and upgrades have been crucial. On 4.11.2016 18:40, Emilien Macchi wrote: MIchele Baldessari (bandini on IRC) has consistently demonstrated high levels of contributions in TripleO projects, specifically in High Availability area

Re: [openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

On 1.12.2016 23:26, Emilien Macchi wrote: Team, Alex Schultz (mwhahaha on IRC) has been active on TripleO since a few months now. While he's very active in different areas of TripleO, his reviews and contributions on puppet-tripleo have been very useful. Alex is a Puppet guy and also the

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

On 30.3.2017 14:58, 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). For TripleO containers we use various

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

On 30.3.2017 18:02, Bogdan Dobrelya wrote: On 30.03.2017 15:40, Jiří Stránský wrote: What might be interesting is solving the keystone init within containers along with our container entrypoint situation. We've talked earlier that we may have to build our custom entrypoints into the images

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

service management. Looks like there's still a feature gap at the moment. Jirka [1] http://docs.ansible.com/ansible/list_of_cloud_modules.html#openstack On 30 Mar 2017 16:42, "Jiří Stránský" <ji...@redhat.com> wrote: On 30.3.2017 14:58, Dan Prince wrote: There is

Re: [openstack-dev] [tripleo] Roadmap for Container CI work

On 6.4.2017 12:46, Jiří Stránský wrote: On 4.4.2017 22:01, Emilien Macchi wrote: After our weekly meeting of today, I found useful to share and discuss our roadmap for Container CI jobs in TripleO. They are ordered by priority from the highest to lowest: 1. Swap ovb-nonha job with ovb

Re: [openstack-dev] [tripleo] Roadmap for Container CI work

On 4.4.2017 22:01, Emilien Macchi wrote: After our weekly meeting of today, I found useful to share and discuss our roadmap for Container CI jobs in TripleO. They are ordered by priority from the highest to lowest: 1. Swap ovb-nonha job with ovb-containers, enable introspection on the container

Re: [openstack-dev] [tripleo] Proposing Florian Fuchs for tripleo-validations core

On 6.4.2017 11:53, Martin André wrote: Hellooo, I'd like to propose we extend Florian Fuchs +2 powers to the tripleo-validations project. Florian is already core on tripleo-ui (well, tripleo technically so this means there is no changes to make to gerrit groups). Florian took over many of the

Re: [openstack-dev] [tripleo][kolla] extended start and hostpath persistent dirs

Responses inline :) I started snipping parts out because the quotations are getting long. tl;dr use kolla images and bootsrap OR upstream images with direct commands: .. code-block:: yaml kolla_config: /var/lib/kolla/config_files/foo.json command: /usr/bin/foo We insist on using

Re: [openstack-dev] [tripleo] propose Alex Schultz core on tripleo-heat-templates

On 13.3.2017 15:30, Emilien Macchi wrote: Hi, Alex is already core on instack-undercloud and puppet-tripleo. His involvement and knowledge in TripleO Heat Templates has been very appreciated over the last months and I think we can give him +2 on this project. As usual, feel free to vote -1/+1

Re: [openstack-dev] [tripleo] Fwd: TripleO mascot - how can I help your team?

On 10.3.2017 17:26, Heidi Joy Tretheway wrote: Hi TripleO team, Here’s an update on your project logo. Our illustrator tried to be as true as possible to your original, while ensuring it matched the line weight, color palette and style of the rest. We also worked to make sure that three Os in

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 14.7.2017 23:00, Ben Nemec wrote: On 07/14/2017 11:43 AM, Joshua Harlow wrote: Out of curiosity, since I keep on hearing/reading all the tripleo discussions on how tripleo folks are apparently thinking/doing? redesigning the whole thing to use ansible + mistral + heat, or ansible +

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 14.7.2017 11:17, Flavio Percoco wrote: Greetings, As some of you know, I've been working on the second phase of TripleO's containerization effort. This phase if about migrating the docker based deployment onto Kubernetes. These phase requires work on several areas: Kubernetes deployment,

[openstack-dev] [tripleo] containers-multinode-upgrades-nv is stable, please respect the results

Hi all, i'm just sending this plea -- let's pay attention to the containers-multinode-upgrades-nv job results in the CI please, and treat it as voting if possible. There's been a fair amount of breakage lately but all was caused by merging TripleO patches on which the job failed. The job in

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

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] [TripleO] breaking changes, new container image parameter formats

On 25.7.2017 04:40, Michał Jastrzębski wrote: ... DockerInsecureRegistryAddress: 172.19.0.2:8787/tripleoupstream DockerKeystoneImage: 172.19.0.2:8787/tripleoupstream/centos-binary- keystone:latest ... That's strange construction, are you sure guys that you don't want to

Re: [openstack-dev] [tripleo] Proposing Bogdan Dobrelya core on TripleO / Containers

On 21.7.2017 16:55, Emilien Macchi wrote: Hi, Bogdan (bogdando on IRC) has been very active in Containerization of TripleO and his quality of review has increased over time. I would like to give him core permissions on container work in TripleO. Any feedback is welcome as usual, we'll vote as a

Re: [openstack-dev] [TripleO] breaking changes, new container image parameter formats

On 19.7.2017 14:41, Dan Prince wrote: I wanted to give a quick heads up on some breaking changes that started landing last week with regards to how container images are specified with Heat parameters in TripleO. There are a few patches associated with converting over to the new changes but the

Re: [openstack-dev] [tripleo] CI Squad Meeting Summary (week 26) - job renaming discussion

On 30.6.2017 15:04, Attila Darazs wrote: = Renaming the CI jobs = When we started the job transition to Quickstart, we introduced the concept of featuresets[1] that define a certain combination of features for each job. This seemed to be a sensible solution, as it's not practical to mention

Re: [openstack-dev] [tripleo] CI Squad Meeting Summary (week 26) - job renaming discussion

On 30.6.2017 17:06, Jiří Stránský wrote: On 30.6.2017 15:04, Attila Darazs wrote: = Renaming the CI jobs = When we started the job transition to Quickstart, we introduced the concept of featuresets[1] that define a certain combination of features for each job. This seemed to be a sensible

Re: [openstack-dev] [tripleo] critical situation with CI / upgrade jobs

On 17.8.2017 00:47, Emilien Macchi wrote: Here's an update on the situation. On Tue, Aug 15, 2017 at 6:33 PM, Emilien Macchi wrote: Problem #1: Upgrade jobs timeout from Newton to Ocata https://bugs.launchpad.net/tripleo/+bug/1702955 [...] - revert distgit patch in RDO:

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

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

[openstack-dev] [tripleo][ci] Upgrade CI job for O->P (containerization)

Hi all, the upgrade job which tests Ocata -> Pike/master upgrade (from bare-metal to containers) just got a green flag from the CI [1]. I've listed the remaining patches we need to land at the very top of the container CI etherpad [2], please let's get them reviewed and landed as soon as we

[openstack-dev] [tripleo][ci] Saving memory in OOOQ multinode jobs

Hi all, we can save some memory in our OOOQ multinode jobs by specifying custom role data -- getting rid of resources and YAQL crunching for roles that aren't used at all in the end. Shout out to shardy for suggesting we should look into doing this. First observations, hopefully at least

Re: [openstack-dev] [tripleo][ci] Upgrade CI job for O->P (containerization)

On 12.5.2017 15:30, Emilien Macchi wrote: On Wed, May 10, 2017 at 9:26 AM, Jiří Stránský <ji...@redhat.com> wrote: Hi all, the upgrade job which tests Ocata -> Pike/master upgrade (from bare-metal to containers) just got a green flag from the CI [1]. I've listed the remaining patche

Re: [openstack-dev] [TripleO] Undercloud backup and restore

On 24.5.2017 15:02, Marios Andreou wrote: On Wed, May 24, 2017 at 10:26 AM, Carlos Camacho Gonzalez < ccama...@redhat.com> wrote: Hey folks, Based on what we discussed yesterday in the TripleO weekly team meeting, I'll like to propose a blueprint to create 2 features, basically to backup and

Re: [openstack-dev] [tripleo] CI Squad Meeting Summary (week 21) - Devmode OVB, RDO Cloud and config management

On 30.5.2017 23:03, Emilien Macchi wrote: On Fri, May 26, 2017 at 4:58 PM, Attila Darazs wrote: If the topics below interest you and you want to contribute to the discussion, feel free to join the next meeting: Time: Thursdays, 14:30-15:30 UTC Place:

Re: [openstack-dev] [TripleO] overcloud containers patches todo

On 5.6.2017 08:59, Sagi Shnaidman wrote: Hi I think a "deep dive" about containers in TripleO and some helpful documentation would help a lot for valuable reviews of these container patches. The knowledge gap that's accumulated here is pretty big. As per last week's discussion [1], i hope this

Re: [openstack-dev] [EXTERNAL] Re: [TripleO] custom configuration to overcloud fails second time

On 31.5.2017 17:40, Dnyaneshwar Pawar wrote: Hi Ben, On 5/31/17, 8:06 PM, "Ben Nemec" > wrote: I think we would need to see what your custom config templates look like as well. Custom config templates:

Re: [openstack-dev] [TripleO] overcloud containers patches todo

On 5.6.2017 23:52, Dan Prince wrote: On Mon, 2017-06-05 at 16:11 +0200, Jiří Stránský wrote: On 5.6.2017 08:59, Sagi Shnaidman wrote: Hi I think a "deep dive" about containers in TripleO and some helpful documentation would help a lot for valuable reviews of these contain

[openstack-dev] [tripleo] Containers Deep Dive - 15th June

Hello, as discussed previously on the list and at the weekly meeting, we'll do a deep dive about containers. The time: Thursday 15th June, 14:00 UTC (the usual time) Link for attending will be at the deep dives etherpad [1], preliminary agenda is in another etherpad [2], and i hope i'll be

Re: [openstack-dev] [tripleo] Containers Deep Dive - 15th June

On 9.6.2017 16:49, Jiří Stránský wrote: Hello, as discussed previously on the list and at the weekly meeting, we'll do a deep dive about containers. The time: Thursday 15th June, 14:00 UTC (the usual time) Link for attending will be at the deep dives etherpad [1], preliminary agenda

Re: [openstack-dev] [tripleo] Containers Deep Dive - 15th June

oining etc. Jirka Thanks in advance! On Fri, Jun 9, 2017 at 5:49 PM, Jiří Stránský <ji...@redhat.com> wrote: Hello, as discussed previously on the list and at the weekly meeting, we'll do a deep dive about containers. The time: Thursday 15th June, 14:00 UTC (the usual time) Li

Re: [openstack-dev] [tripleo] Containers Deep Dive - 15th June

On 9.6.2017 16:49, Jiří Stránský wrote: Hello, as discussed previously on the list and at the weekly meeting, we'll do a deep dive about containers. The time: Thursday 15th June, 14:00 UTC (the usual time) Link for attending will be at the deep dives etherpad [1], preliminary agenda

Re: [openstack-dev] [deployment][kolla][openstack-ansible][openstack-helm][tripleo] ansible role to produce oslo.config files for openstack services

On 15.6.2017 19:06, Emilien Macchi wrote: I missed [tripleo] tag. On Thu, Jun 15, 2017 at 12:09 PM, Emilien Macchi wrote: If you haven't followed the "Configuration management with etcd / confd" thread [1], Doug found out that using confd to generate configuration files

Re: [openstack-dev] [tripleo] Containers Deep Dive - 15th June

On 15.6.2017 18:25, Jiří Stránský wrote: On 9.6.2017 16:49, Jiří Stránský wrote: Hello, as discussed previously on the list and at the weekly meeting, we'll do a deep dive about containers. The time: Thursday 15th June, 14:00 UTC (the usual time) Link for attending will be at the deep dives

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 9.6.2017 18:51, Flavio Percoco wrote: A-ha, ok! I figured this was another option. In this case I guess we would have 2 options: 1. Run confd + openstack service in side the container. My concern in this case would be that we'd have to run 2 services inside the container and structure things

Re: [openstack-dev] [tripleo] Install Kubernetes in the overcloud using TripleO

On 20.9.2017 10:15, Bogdan Dobrelya wrote: On 08.06.2017 18:36, Flavio Percoco wrote: Hey y'all, Just wanted to give an updated on the work around tripleo+kubernetes. This is still far in the future but as we move tripleo to containers using docker-cmd, we're also working on the final goal,

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On 21.9.2017 12:31, Giulio Fidente wrote: On 09/20/2017 07:36 PM, James Slagle wrote: On Tue, Sep 19, 2017 at 8:37 AM, Giulio Fidente wrote: On 09/18/2017 05:37 PM, James Slagle wrote: - The entire sequence and flow is driven via Mistral on the Undercloud by default.

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On 22.9.2017 13:44, Giulio Fidente wrote: On 09/21/2017 07:53 PM, Jiří Stránský wrote: On 21.9.2017 18:04, Marios Andreou wrote: On Thu, Sep 21, 2017 at 3:53 PM, Jiří Stránský <ji...@redhat.com> wrote: [...] That way we could run the whole thing end-to-end via ansible-pl

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On 22.9.2017 15:30, Jiri Tomasek wrote: Will it be possible to send Zaqar messages at each deployment step to make the deployment process more interactive? If we go the way of allowing the wrapping playbook to execute per step, i think we could send messages to Zaqar after each step. Mistral

Re: [openstack-dev] [TripleO] TripleO/Ansible PTG session

On 21.9.2017 18:04, Marios Andreou wrote: On Thu, Sep 21, 2017 at 3:53 PM, Jiří Stránský <ji...@redhat.com> wrote: On 21.9.2017 12:31, Giulio Fidente wrote: On 09/20/2017 07:36 PM, James Slagle wrote: On Tue, Sep 19, 2017 at 8:37 AM, Giulio Fidente <gfide...@redhat.com> wrote

Re: [openstack-dev] [tripleo] Repo structure for ansible-k8s-roles-* under TripleO's umbrella

On 9.10.2017 11:29, Flavio Percoco wrote: Greetings, I've been working on something called triple-apbs (and it's respective roles) in the last couple of months. You can find more info about this work here[0][1][2] This work is at the point where I think it would be worth start discussing how

  1   2   >