Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes

On Fri, 2018-11-30 at 10:31 +0100, Bogdan Dobrelya wrote: > On 11/29/18 6:42 PM, Jiří Stránský wrote: > > On 28. 11. 18 18:29, Bogdan Dobrelya wrote: > > > On 11/28/18 6:02 PM, Jiří Stránský wrote: > > > > > > > > > > > > > Reiterating again on previous points: > > > > > > > > > > -I'd be fine

Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes

On Wed, 2018-11-28 at 13:28 -0500, James Slagle wrote: > On Wed, Nov 28, 2018 at 12:31 PM Bogdan Dobrelya > wrote: > > Long story short, we cannot shoot both rabbits with a single shot, > > not > > with puppet :) May be we could with ansible replacing puppet > > fully... > > So splitting config

Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes

On Wed, 2018-11-28 at 15:12 +0100, Bogdan Dobrelya wrote: > On 11/28/18 2:58 PM, Dan Prince wrote: > > On Wed, 2018-11-28 at 12:45 +0100, Bogdan Dobrelya wrote: > > > To follow up and explain the patches for code review: > > > > > > The "header&q

Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes

On Wed, 2018-11-28 at 12:45 +0100, Bogdan Dobrelya wrote: > To follow up and explain the patches for code review: > > The "header" patch https://review.openstack.org/620310 -> (requires) > https://review.rdoproject.org/r/#/c/17534/, and also > https://review.openstack.org/620061 -> (which in

Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes

ple above is still > usable without k8s? > > Thanks, > Kevin > > From: Dan Prince [dpri...@redhat.com] > Sent: Tuesday, November 27, 2018 10:10 AM > To: OpenStack Development Mailing List (not for usage questions); > openstack-disc...@lists.openst

Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes

On Tue, 2018-11-27 at 16:24 +0100, Bogdan Dobrelya wrote: > Changing the topic to follow the subject. > > [tl;dr] it's time to rearchitect container images to stop incluiding > config-time only (puppet et al) bits, which are not needed runtime > and > pose security issues, like CVEs, to

Re: [openstack-dev] [TripleO] PSA lets use deploy_steps_tasks

On Mon, Nov 5, 2018 at 4:06 AM Cédric Jeanneret wrote: > > On 11/2/18 2:39 PM, Dan Prince wrote: > > I pushed a patch[1] to update our containerized deployment > > architecture docs yesterday. There are 2 new fairly useful sections we > > can leverage with Tripl

[openstack-dev] [TripleO] PSA lets use deploy_steps_tasks

I pushed a patch[1] to update our containerized deployment architecture docs yesterday. There are 2 new fairly useful sections we can leverage with TripleO's stepwise deployment. They appear to be used somewhat sparingly so I wanted to get the word out. The first is 'deploy_steps_tasks' which

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Wed, Oct 17, 2018 at 11:15 AM Alex Schultz wrote: > > Time to resurrect this thread. > > On Thu, Jul 5, 2018 at 12:14 PM James Slagle wrote: > > > > On Thu, Jul 5, 2018 at 1:50 PM, Dan Prince wrote: > > > Last week I was tinkering with my docker config

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Thu, Oct 25, 2018 at 11:26 AM Alex Schultz wrote: > > On Thu, Oct 25, 2018 at 9:16 AM Bogdan Dobrelya wrote: > > > > > > On 10/19/18 8:04 PM, Alex Schultz wrote: > > > On Fri, Oct 19, 2018 at 10:53 AM James Slagle > > > wrote: > > >> > > >> On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz >

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On Wed, Aug 15, 2018 at 5:49 PM Jay Pipes wrote: > > On 08/15/2018 04:01 PM, Emilien Macchi wrote: > > On Wed, Aug 15, 2018 at 5:31 PM Emilien Macchi > > wrote: > > > > More seriously here: there is an ongoing effort to converge the > > tools around

Re: [openstack-dev] [tripleo] ansible roles in tripleo

On Tue, Aug 14, 2018 at 1:53 PM Jill Rouleau wrote: > > Hey folks, > > Like Alex mentioned[0] earlier, we've created a bunch of ansible roles > for tripleo specific bits. The idea is to start putting some basic > cookiecutter type things in them to get things started, then move some >

Re: [openstack-dev] [tripleo] Patches to speed up plan operations

Thanks for taking this on Ian! I'm fully on board with the effort. I like the consolidation and performance improvements. Storing t-h-t templates in Swift worked okay 3-4 years ago. Now that we have more templates, many of which need .j2 rendering the storage there has become quite a bottleneck.

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Thu, Aug 2, 2018 at 5:42 PM Steve Baker wrote: > > > > On 02/08/18 13:03, Alex Schultz wrote: > > On Mon, Jul 9, 2018 at 6:28 AM, Bogdan Dobrelya wrote: > >> On 7/6/18 7:02 PM, Ben Nemec wrote: > >>> > >>> > >>> On 07/05/2018

Re: [openstack-dev] [tripleo] Stein blueprint - Plan to remove Keepalived support (replaced by Pacemaker)

feedback, I've made a quick PoC: > > > https://review.openstack.org/#/q/topic:bp/undercloud-pacemaker-de > > > fault > > > > > > And I'm currently doing local testing. I'll publish results when > > > progress is made, but I've made it so we have the choice t

Re: [openstack-dev] [tripleo] Stein blueprint - Plan to remove Keepalived support (replaced by Pacemaker)

On Fri, Jul 13, 2018 at 2:34 PM Emilien Macchi wrote: > > Greetings, > > We have been supporting both Keepalived and Pacemaker to handle VIP > management. > Keepalived is actually the tool used by the undercloud when SSL is enabled > (for SSL termination). > While Pacemaker is used on the

Re: [openstack-dev] [tripleo] New "validation" subcommand for "openstack undercloud"

On Mon, Jul 16, 2018 at 11:27 AM Cédric Jeanneret wrote: > > Dear Stackers, > > In order to let operators properly validate their undercloud node, I > propose to create a new subcommand in the "openstack undercloud" "tree": > `openstack undercloud validate' > > This should only run the different

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Thu, 2018-07-05 at 14:13 -0400, James Slagle wrote: > > I would almost rather see us organize the directories by service > name/project instead of implementation. > > Instead of: > > puppet/services/nova-api.yaml > puppet/services/nova-conductor.yaml > docker/services/nova-api.yaml >

[openstack-dev] [TripleO] easily identifying how services are configured

Last week I was tinkering with my docker configuration a bit and was a bit surprised that puppet/services/docker.yaml no longer used puppet to configure the docker daemon. It now uses Ansible [1] which is very cool but brings up the question of how should we clearly indicate to developers and

Re: [openstack-dev] [tripleo] Status of Standalone installer (aka All-In-One)

On Mon, Jun 4, 2018 at 8:26 PM, Emilien Macchi wrote: > TL;DR: we made nice progress and you can checkout this demo: > https://asciinema.org/a/185533 > > We started the discussion back in Dublin during the last PTG. The idea of > Standalone (aka All-In-One, but can be mistaken with all-in-one

Re: [openstack-dev] [tripleo] Containerized Undercloud deep-dive

We are on for this tomorrow (Thursday) at 2pm UTC (10am EST). We'll meet here: https://redhat.bluejeans.com/dprince/ and record it live. We'll do an overview presentation and then perhaps jump into a terminal for some live questions. Dan On Tue, May 15, 2018 at 10:51 AM, Emilien Macchi wrote:

Re: [openstack-dev] Fwd: [tripleo] PTG session about All-In-One installer: recap & roadmap

On Thu, Apr 5, 2018 at 12:24 PM, Emilien Macchi <emil...@redhat.com> wrote: > On Thu, Apr 5, 2018 at 4:37 AM, Dan Prince <dpri...@redhat.com> wrote: > >> Much of the work on this is already there. We've been using this stuff >> for over a year to dev/test the conta

Re: [openstack-dev] [Ironic][Tripleo] ipmitool issues HP machines

Sigh. And the answer is: user error. Adminstrator != Administrator. Well this was fun. Sorry for the bother. All is well. :) Dan On Thu, Apr 5, 2018 at 8:13 AM, Dan Prince <dpri...@redhat.com> wrote: > On Wed, Apr 4, 2018 at 1:27 PM, Jim Rollenhagen <j...@jimrollenhagen.c

Re: [openstack-dev] [Ironic][Tripleo] ipmitool issues HP machines

On Wed, Apr 4, 2018 at 1:27 PM, Jim Rollenhagen <j...@jimrollenhagen.com> wrote: > On Wed, Apr 4, 2018 at 1:18 PM, Jim Rollenhagen <j...@jimrollenhagen.com> > wrote: >> >> On Wed, Apr 4, 2018 at 8:39 AM, Dan Prince <dpri...@redhat.com> wrote: >>> >&

Re: [openstack-dev] [Ironic][Tripleo] ipmitool issues HP machines

On Wed, Apr 4, 2018 at 1:18 PM, Jim Rollenhagen <j...@jimrollenhagen.com> wrote: > On Wed, Apr 4, 2018 at 8:39 AM, Dan Prince <dpri...@redhat.com> wrote: >> >> Kind of a support question but figured I'd ask here in case there are >> suggestions for workarounds for

Re: [openstack-dev] [Ironic][Tripleo] ipmitool issues HP machines

sue. Tried it with and without newlines even and no success. Dan > > Get Outlook for Android > > ________ > From: Dan Prince <dpri...@redhat.com> > Sent: Wednesday, April 4, 2018 3:39:00 PM > To: List, OpenStack > Subject: [openstack-dev] [Ironic

Re: [openstack-dev] [Ironic][Tripleo] ipmitool issues HP machines

On Wed, Apr 4, 2018 at 8:52 AM, Sanjay Upadhyay <supad...@redhat.com> wrote: > > > On Wed, Apr 4, 2018 at 6:09 PM, Dan Prince <dpri...@redhat.com> wrote: >> >> Kind of a support question but figured I'd ask here in case there are >> suggestions for workaroun

[openstack-dev] [Ironic][Tripleo] ipmitool issues HP machines

Kind of a support question but figured I'd ask here in case there are suggestions for workarounds for specific machines. Setting up a new rack of mixed machines this week and hit this issue with HP machines using the ipmi power driver for Ironic. Curious if anyone else has seen this before? The

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

On Tue, Apr 3, 2018 at 10:00 AM, Javier Pena wrote: > >> Greeting folks, >> >> During the last PTG we spent time discussing some ideas around an All-In-One >> installer, using 100% of the TripleO bits to deploy a single node OpenStack >> very similar with what we have today with

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

On Tue, Apr 3, 2018 at 9:23 AM, James Slagle <james.sla...@gmail.com> wrote: > On Mon, Apr 2, 2018 at 9:05 PM, Dan Prince <dpri...@redhat.com> wrote: >> On Thu, Mar 29, 2018 at 5:32 PM, Emilien Macchi <emil...@redhat.com> wrote: >>> Greeting folks, >&

Re: [openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

On Thu, Mar 29, 2018 at 5:32 PM, Emilien Macchi wrote: > Greeting folks, > > During the last PTG we spent time discussing some ideas around an All-In-One > installer, using 100% of the TripleO bits to deploy a single node OpenStack > very similar with what we have today with

Re: [openstack-dev] [yaql] [tripleo] Backward incompatible change in YAQL minor version

Thanks for the update Emilien. A couple of things to add: 1) This was really difficult to pin-point via the Heat stack error message ('list index out of range'). I actually had to go and add LOG.debug statements to Heat to get to the bottom of it. I aim to sync with a few of the Heat folks next

Re: [openstack-dev] [TripleO] Proposing Ronelle Landy for Tripleo-Quickstart/Extras/CI core

+1 On Wed, Nov 29, 2017 at 2:34 PM, John Trowbridge wrote: > I would like to propose Ronelle be given +2 for the above repos. She has > been a solid contributor to tripleo-quickstart and extras almost since the > beginning. She has solid review numbers, but more importantly

Re: [openstack-dev] [tripleo] Updates on the TripleO on Kubernetes work

On Thu, Nov 16, 2017 at 11:56 AM, James Slagle wrote: > > > When we consume these ansible-role-k8s-* roles from t-h-t, I think > that should be a stepping stone towards migrating away from having to > use Heat to deploy and configure those services. We know that these >

Re: [openstack-dev] [tripleo] Updates on the TripleO on Kubernetes work

On Fri, Nov 17, 2017 at 4:43 AM, Steven Hardy wrote: > > > In the ansible/kubernetes model, it could work like: > > 1. Ansible role makes k8s API call creating pod with multiple containers > 2. Pod starts temporary container that runs puppet, config files > written out to

Re: [openstack-dev] [all] Community managed tech/dev blog: Call for opinions and ideas

On Mon, Nov 27, 2017 at 8:55 AM, Flavio Percoco wrote: > Greetings, > > Last Thursday[0], at the TC office hours, we brainstormed a bit around the > idea > of having a tech blog. This idea came first from Joshua Harlow and it was > then > briefly discussed at the summit too. >

Re: [openstack-dev] Nominate chem and matbu for tripleo-core !

+1 On Thu, Nov 9, 2017 at 3:44 AM, Marios Andreou wrote: > Hello fellow owls, > > I would like to nominate (and imo these are both long overdue already): > > Sofer Athlan Guyot (chem) and > > Mathieu Bultel (matbu) > > to tripleo-core. They have both made many many core

Re: [openstack-dev] [tripleo] Proposing John Fulton core on TripleO

+1 On Wed, Nov 8, 2017 at 5:24 PM, Giulio Fidente wrote: > Hi, > > I would like to propose John Fulton core on TripleO. > > I think John did an awesome work during the Pike cycle around the > integration of ceph-ansible as a replacement for puppet-ceph, for the > deployment

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Tue, 2017-10-17 at 11:46 +, milanisko k wrote: > > How about the shared container? Wouldn't it be better not have to > rely on t-h-t especially if we're "scheduling" (and probably > configuring) the services as a single logical entity? The containers architecture for Pike and Queens is

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Tue, 2017-10-17 at 10:06 +, milanisko k wrote: > > Does it mean dnsmasq was run from a stand-alone container? Yes. There are separate containers for the ironic-inspector and dnsmasq. > > Could you please point me (in the patch probably) to the spot where > we configure inspector

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

ontainer. Dan > > Dmitry > > On 10/04/2017 03:00 PM, Dan Prince wrote: > > On Tue, 2017-10-03 at 16:03 -0600, Alex Schultz wrote: > > > On Tue, Oct 3, 2017 at 2:46 PM, Dan Prince <dpri...@redhat.com> > > > wrote: > > > > > > > > >

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

been tested at all, and > the iptables magic we do may simply not be containers-compatible. Milan > would appreciate any help with his ironic-inspector rework. > > Thanks Dmitry. Exactly the update I was looking for. Look forward to syncing w/ Milan on this. Dan > Dmitry > > >

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Tue, 2017-10-03 at 16:03 -0600, Alex Schultz wrote: > On Tue, Oct 3, 2017 at 2:46 PM, Dan Prince <dpri...@redhat.com> > wrote: > > > > > > On Tue, Oct 3, 2017 at 3:50 PM, Alex Schultz <aschu...@redhat.com> > > wrote: > > > > > > On

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Tue, Oct 3, 2017 at 3:50 PM, Alex Schultz <aschu...@redhat.com> wrote: > On Tue, Oct 3, 2017 at 11:12 AM, Dan Prince <dpri...@redhat.com> wrote: > > On Mon, 2017-10-02 at 15:20 -0600, Alex Schultz wrote: > >> Hey Dan, > >> > >> Thanks for sendi

Re: [openstack-dev] [TripleO] containerized undercloud in Queens

On Mon, 2017-10-02 at 15:20 -0600, Alex Schultz wrote: > Hey Dan, > > Thanks for sending out a note about this. I have a few questions > inline. > > On Mon, Oct 2, 2017 at 6:02 AM, Dan Prince <dpri...@redhat.com> > wrote: > > One of the things the Tr

[openstack-dev] [TripleO] containerized undercloud in Queens

One of the things the TripleO containers team is planning on tackling in Queens is fully containerizing the undercloud. At the PTG we created an etherpad [1] that contains a list of features that need to be implemented to fully replace instack-undercloud. Benefits of this work: -Alignment:

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

On Thu, Sep 21, 2017 at 8:53 AM, Jiří Stránský 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 >>> wrote: >>> On 09/18/2017 05:37 PM, James

Re: [openstack-dev] [tripleo] TripleO UI and CLI feature parity

On Tue, Sep 12, 2017 at 9:58 PM, Jiri Tomasek wrote: > Hello all, > > As we are in the planning phase for Queens cycle, I'd like to open the > discussion on the topic of CLI (tripleoclient) and GUI (tripleo-ui) feature > parity. > > Two years ago, when TripleO UI was

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

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 primary patches are listed below here [1]

Re: [openstack-dev] [tripleo] Role updates

On Fri, 2017-06-09 at 09:24 -0600, Alex Schultz wrote: > Hey folks, > > I wanted to bring to your attention that we've merged the change[0] > to > add a basic set of roles that can be combined to create your own > roles_data.yaml as needed.  With this change the roles_data.yaml and >

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

Thursday still. If that's too short > of  > a notice for several folks or if i hit some trouble with preparation, > we  > might move it to 15th. Any feedback is welcome of course. Nice Jirka. Thanks for organizing this! Dan > > Have a good day, > > Jirka > > >

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

Hi, Any help reviewing the following patches for the overcloud containerization effort in TripleO would be appreciated: https://etherpad.openstack.org/p/tripleo-containers-todo If you've got new services related to the containerization efforts feel free to add them here too. Thanks, Dan

Re: [openstack-dev] [TripleO][Kolla] default docker storage backend for TripleO

>   > overlay2 is documented as a Technology Preview graph driver in the > Atomic Host 7.3.4 release notes: > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linu > x_atomic_host/7/html-single/release_notes/ >   >   >   > _

[openstack-dev] [TripleO][Kolla] default docker storage backend for TripleO

TripleO currently uses the default "loopback" docker storage device. This is not recommended for production (see 'docker info'). We've been poking around with docker storage backends in TripleO for almost 2 months now here: https://review.openstack.org/#/c/451916/ For TripleO there are a

Re: [openstack-dev] [tripleo][logging] oslo.log fluentd native logging

On Mon, 2017-04-24 at 07:47 -0400, Joe Talerico wrote: > Hey owls - I have been playing with oslo.log fluentd integration[1] > in > a poc commit here [2]. Enabling the native service logging is nice > and > tracebacks no longer multiple inserts into elastic - there is a > "traceback" key which

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Thu, 2017-05-04 at 14:11 -0400, Emilien Macchi wrote: > On Thu, May 4, 2017 at 9:41 AM, Dan Prince <dpri...@redhat.com> > wrote: > > On Thu, 2017-05-04 at 03:11 -0400, Luigi Toscano wrote: > > > - Original Message - > > > > On Wed, 2017-05-

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Thu, 2017-05-04 at 03:11 -0400, Luigi Toscano wrote: > - Original Message - > > On Wed, 2017-05-03 at 17:53 -0400, Emilien Macchi wrote: > > > (cross-posting) > > > > > Instead of running the Pingtest, we would execute a Tempest > > > Scenario > > > that boot an instance from volume

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Wed, 2017-05-03 at 17:53 -0400, Emilien Macchi wrote: > (cross-posting) > > I've seen a bunch of interesting thoughts here. > The most relevant feedback I've seen so far: > > - TripleO folks want to keep testing fast and efficient. > - Tempest folks understand this problematic and is willing

Re: [openstack-dev] [tripleo] container jobs are unstable

On Thu, 2017-04-06 at 15:32 -0400, Paul Belanger wrote: > On Thu, Mar 30, 2017 at 11:01:08AM -0400, Paul Belanger wrote: > > On Thu, Mar 30, 2017 at 03:08:57PM +0100, Steven Hardy wrote: > > > To be fair, we discussed this on IRC yesterday, everyone agreed > > > infra > > > supported docker

Re: [openstack-dev] [tripleo][kolla] extended start and hostpath persistent dirs (was: kolla_bootstrap for non-openstack services)

On Tue, 2017-04-04 at 18:03 +0200, Bogdan Dobrelya wrote: > On 03.04.2017 21:01, Dan Prince wrote: > > On Mon, 2017-04-03 at 16:15 +0200, Bogdan Dobrelya wrote: > > > Let's please re-evaluate configuration of containerized non- > > > openstack, > > > like dat

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

On Tue, 2017-04-04 at 16:01 -0400, 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

Re: [openstack-dev] [tripleo][kolla] kolla_bootstrap for non-openstack services

On Mon, 2017-04-03 at 16:15 +0200, Bogdan Dobrelya wrote: > Let's please re-evaluate configuration of containerized non- > openstack, > like database, message queue, key value, web, services for tripleo > heat > templates and Kolla. Here is an example containerized etcd patch [0]. > > tl;dr use

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

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 puppet world, we consider this very > important because since puppet is all about ensuring a desired state > (ie. a

Re: [openstack-dev] [tripleo] container jobs are unstable

oco <fla...@redhat.co > > > m> wrote: > > > > On 23/03/17 16:24 +0100, Martin André wrote: > > > > > > > > > > On Wed, Mar 22, 2017 at 2:20 PM, Dan Prince <dprince@redhat.c > > > > > om> wrote: > > > > > >

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

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 puppet modules (along with hiera) to drive

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

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 folks, > > > > > > So after looking at the backlog of patches to review across all >

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

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 noticed we have a bunch of really old stale > patches. I think it's time we address when we can abandon these stale > patches. >

Re: [openstack-dev] [tripleo] container jobs are unstable

On Wed, 2017-03-22 at 13:35 +0100, Flavio Percoco wrote: > On 22/03/17 13:32 +0100, Flavio Percoco wrote: > > On 21/03/17 23:15 -0400, Emilien Macchi wrote: > > > Hey, > > > > > > I've noticed that container jobs look pretty unstable lately; to > > > me, > > > it sounds like a timeout: > > >

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

Hi Heidi, I like this one a good bit better. He might looks a smidge cross-eyed to me... but I'd take this one any day over the previous version. Thanks for trying to capture the spirit of the original logos. Dan On Fri, 2017-03-10 at 08:26 -0800, Heidi Joy Tretheway wrote: > Hi TripleO team, 

Re: [openstack-dev] [TripleO][Containers] Containers work tracking, updates and schedule

On Tue, 2017-03-07 at 12:08 +0100, Flavio Percoco wrote: > Greetings, > > We've been organizing the containers work for TripleO in a more > consumable way > that will hopefully ease the engagement from different squads and > teams in > OpenStack. For reference as a lot of the initial services

Re: [openstack-dev] [tripleo] A sneak peek to TripleO + Containers

omething like > that. One > interesting thing is that running[2] will leave you with an almost > entirely > clean host. It still writes some stuff in `/var/lib` and > `/etc/puppet` but that > can be improved for sure. > > Anyway, after all the disclaimers, I hope you'l

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

On Thu, 2017-02-16 at 19:54 +, Jeremy Stanley wrote: > On 2017-02-16 14:09:53 -0500 (-0500), Dan Prince wrote: > [...] > > This isn't about aligning anything. It is about artistic control. > > The > > foundation wants to have icons their way playing the "communit

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

On Thu, 2017-02-16 at 06:36 -0600, Monty Taylor wrote: > On 02/15/2017 07:54 PM, Dan Prince wrote: > > At the high level all of this sounds like a fine grand plan: "Help > > projects create mascots" with a common theme. On the ground level I > > can > >

Re: [openstack-dev] The end of OpenStack packages in Debian?

Nice work on the packages Thomas. I've always admired that you got the Debian packages upstream first :). Best wishes. Dan On Wed, 2017-02-15 at 13:42 +0100, Thomas Goirand wrote: > Hi there, > > It's been a while since I planed on writing this message. I couldn't > write it because the

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

On Thu, 2017-02-16 at 08:36 -0500, Emilien Macchi wrote: > I'll shamelessly cross-post here, I didn't know where to reply. > I agree with Monty and Flavio here. > > Heidi has been doing an excellent job in helping OpenStack community > about $topic, always in the open, which has been very

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

On Thu, 2017-02-16 at 06:36 -0600, Monty Taylor wrote: > On 02/15/2017 07:54 PM, Dan Prince wrote: > > At the high level all of this sounds like a fine grand plan: "Help > > projects create mascots" with a common theme. On the ground level I > > can > >

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

se mascots—that you’ll > enjoy them as much as I do. (Fun fact: Why did QA chose a little > brown bat as its mascot? Because that creature eats its weight in > bugs every day!) It’s been a real pleasure working with the community > on this project.  > > —Heidi Joy > > &g

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

2017-02-15 at 21:12 +, Jeremy Stanley wrote: > On 2017-02-15 15:52:30 -0500 (-0500), Dan Prince wrote: > > The fact that the foundation is involved in "streamlining" team > > logos > > just kind of makes me a bit sad I guess. I mean, what value is this &g

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

The fact that the foundation is involved in "streamlining" team logos just kind of makes me a bit sad I guess. I mean, what value is this really adding to the OpenStack projects? Devs on many projects spend their own time on creating logos... that they like. I say let them be happy and have their

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

On Tue, 2017-02-14 at 13:30 +0100, Carlos Camacho Gonzalez wrote: > I'll vote also for option 1 if we can keep it. > > One thing, you can see how designers have iterated over ironic's logo > http://lists.openstack.org/pipermail/openstack- > dev/attachments/20170201/a016f685/attachment.png to fit

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

Option #1 keep it. Dan On Mon, 2017-02-13 at 21:38 -0500, Emilien Macchi wrote: > Team, I've got this email from Heidi. > > I see 3 options : > > 1. Keep existing logo: http://tripleo.org/_static/tripleo_owl.svg . > > 2. Re-design a new logo that "meets" OpenStack "requirements". > > 3.

Re: [openstack-dev] [tripleo] tripleo-heat-templates, vendor plugins and the new hiera hook

On Wed, 2017-01-25 at 14:59 +0200, Marios Andreou wrote: > Hi, as part of the composable upgrades workflow shaping up for Newton > to > Ocata, we need to install the new hiera hook that was first added > with > [1] and disable the old hook and data as part of the upgrade > initialization [2]. Most

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

+1 from me. Dan On Fri, 2016-11-04 at 13:40 -0400, Emilien Macchi wrote: > MIchele Baldessari (bandini on IRC) has consistently demonstrated > high > levels of contributions in TripleO projects, specifically in High > Availability area where's he's for us a guru (I still don't > understand > how

Re: [openstack-dev] [tripleo] Setting up to 3rd party CI OVB jobs

On Fri, 2016-10-07 at 09:03 -0400, Paul Belanger wrote: > Greetings, > > I wanted to propose a work item, that I am happy to spearhead, about > setting up > a 3rd party CI system for tripleo project. The work I am proposing, > wouldn't > actually affect anything today about tripleo-ci but

Re: [openstack-dev] [tripleo] website update

On Tue, 2016-10-11 at 18:08 -0500, Ben Nemec wrote: > > On 10/11/2016 02:42 PM, Dan Prince wrote: > > > > A quick update on the tripleo.org website outage today. We are in > > the > > process of moving the server to a new host location. Until DNS > > upda

[openstack-dev] [tripleo] website update

A quick update on the tripleo.org website outage today. We are in the process of moving the server to a new host location. Until DNS updates please use the following URL if you want to access the CI status report: http://66.187.229.219/cistatus.html Dan

Re: [openstack-dev] [TripleO] TripleO Core nominations

On Thu, 2016-09-15 at 10:20 +0100, Steven Hardy wrote: > Hi all, > > As we work to finish the last remaining tasks for Newton, it's a good > time > to look back over the cycle, and recognize the excellent work done by > several new contributors. > > We've seen a different contributor pattern

Re: [openstack-dev] [TripleO] Easier way of trying TripleO

On Fri, 2016-08-19 at 15:31 -0400, Dan Prince wrote: > On Tue, 2013-11-19 at 16:40 -0500, James Slagle wrote: > > > > I'd like to propose an idea around a simplified and complimentary > > version of > > devtest that makes it easier for someone to get

Re: [openstack-dev] [TripleO] a new Undercloud install driven by Heat

in fact. I don't think we'd force the idea on anyone though and if it takes some time for people to warm up to the latter use case that is fine. The primary points in doing all this are to help benefit the TripleO undercloud via code and template re-use. I think this stands on its own. Dan >   > Ar

Re: [openstack-dev] [TripleO] Easier way of trying TripleO

On Tue, 2013-11-19 at 16:40 -0500, James Slagle wrote: > I'd like to propose an idea around a simplified and complimentary > version of > devtest that makes it easier for someone to get started and try > TripleO.   > > The goal being to get people using TripleO as a way to experience the >

Re: [openstack-dev] [TripleO] Network Template Generator

On Mon, 2016-08-08 at 15:42 -0500, Ben Nemec wrote: > This is something that has existed for a while, but I had been > hesitant > to evangelize it until it was a little more proven.  At this point > I've > used it to generate templates for a number of different environments, > and it has worked

Re: [openstack-dev] [tripleo] HA with only one node.

On Sat, 2016-08-06 at 13:21 -0400, Adam Young wrote: > As I try to debug Federaion problems, I am often finding I have to > check  > three nodes to see where the actual requrest was processed. However, > If  > I close down to of the controller nodes in Nova, the whole thing just > fails. > > >

Re: [openstack-dev] [TripleO] a new Undercloud install driven by Heat

On Fri, 2016-08-05 at 13:56 +0200, Dmitry Tantsur wrote: > On 08/05/2016 01:21 PM, Steven Hardy wrote: > > > > On Fri, Aug 05, 2016 at 12:27:40PM +0200, Dmitry Tantsur wrote: > > > > > > On 08/04/2016 11:48 PM, Dan Prince wrote: > > > > > >

Re: [openstack-dev] [TripleO] a new Undercloud install driven by Heat

On Fri, 2016-08-05 at 13:39 +0200, Thomas Herve wrote: > On Thu, Aug 4, 2016 at 11:48 PM, Dan Prince <dpri...@redhat.com> > wrote: > > > > Last week I started some prototype work on what could be a new way > > to > > install the Undercloud. Th

Re: [openstack-dev] [TripleO] a new Undercloud install driven by Heat

On Fri, 2016-08-05 at 12:27 +0200, Dmitry Tantsur wrote: > On 08/04/2016 11:48 PM, Dan Prince wrote: > > > > Last week I started some prototype work on what could be a new way > > to > > install the Undercloud. The driving force behind this was some of > > th

[openstack-dev] [TripleO] a new Undercloud install driven by Heat

is working with the patches above: https://www.youtube.com/watch?v=y1qMDLAf26Q Thoughts? Would it be cool to have a session to discuss this more in Barcelona? Dan Prince (dprince) __ OpenStack Development Mailing List (not

[openstack-dev] [TripleO] CI package build issues

After discovering some regressions today we found what we think is a package build issue in our CI environment which might be the cause of our issues: https://bugs.launchpad.net/tripleo/+bug/1595660 Specifically, there is a case where DLRN might not be giving an error code if build failures

Re: [openstack-dev] [tripleo] all CI jobs are failing: error: seed_2.qcow2 not in qcow2 format

Thanks Emilien, I marked the bug below as a duplicate of this issue I had filed earlier  with this title "CI jobs failing, mirror-server is down (192.168.1.101)": https://bugs.launchpad.net/tripleo/+bug/1594161 The root cause of the issue seemed to be that the mirror server was unresponsive. I

Re: [openstack-dev] [UX] [TripleO] TripleO UI Initial Wireframes

I left some comments on the wireframes themselves. One general concept I would like to see capture is to make sure that things across the UI and CLI have parity. Specifically things like if I register nodes on the CLI we use a JSON file format:

Re: [openstack-dev] [TripleO] Proposed TripleO core changes

On Thu, 2016-06-09 at 15:03 +0100, Steven Hardy wrote: > Hi all, > > I've been in discussion with Martin André and Tomas Sedovic, who are > involved with the creation of the new tripleo-validations repo[1] > > We've agreed that rather than create another gerrit group, they can > be > added to

  1   2   3   >