Thanks
Jirka
Thanks,
Kevin
____
From: Jiří Stránský [ji...@redhat.com]
Sent: Thursday, November 29, 2018 9:42 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers
for security and size of images (maintenance) sakes
On 28.
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 removing systemd. But lets do it properly and not via 'rpm
-ev --nodeps'.
-Puppet and Ruby *are* required for configuration. We can certai
Reiterating again on previous points:
-I'd be fine removing systemd. But lets do it properly and not via 'rpm
-ev --nodeps'.
-Puppet and Ruby *are* required for configuration. We can certainly put
them in a separate container outside of the runtime service containers
but doing so would actual
On 15. 11. 18 16:54, Wesley Hayutin wrote:
On Thu, Nov 15, 2018 at 8:52 AM Sagi Shnaidman wrote:
Hi,
I'd like to propose Quique (@quiquell) as a core reviewer for TripleO.
Quique is actively involved in improvements and development of TripleO and
TripleO CI. He also helps in other projects inc
Yes I know, but based on the deployment details we have for networking-ovn
it should be enough, we will have to update those documents with the new
changes anyway, because surprisingly this change has came for "Rocky" last
minute. Why did we have such last minute change? :-/
I understand the val
On 03/10/2018 10:14, Miguel Angel Ajo Pelayo wrote:
Hi folks
I was trying to deploy neutron with networking-ovn via tripleo-quickstart
scripts on master, and this config file [1]. It doesn't work, overcloud
deploy cries with:
1) trying to deploy ovn I end up with a 2018-10-02 17:48:12 | "201
Hi Steve,
On 25/09/2018 10:51, Steven Hardy wrote:
Hi all,
After some discussions with bandini at the PTG, I've been taking a
look at this bug and how to solve it:
https://bugs.launchpad.net/tripleo/+bug/1792613
(Also more information in downstream bz1626140)
The problem is that we always run
On 11.9.2018 18:53, Alex Schultz wrote:
Thanks everyone for coming and chatting. From the meeting we've had a
few items where we can collaborate together.
Here are some specific bullet points:
- TripleO folks should feel free to propose some minor structural
changes if they make the integratio
On 4.9.2018 08:13, Janki Chhatbar wrote:
Hi
I am looking to automate role file generation in TripleO. The idea is
basically for an operator to create a simple yaml file (operator.yaml, say)
listing services that are needed and then TripleO to generate
Controller.yaml enabling only those services
On 30.8.2018 16:28, Honza Pokorny wrote:
Hello!
Over the last few months, it seems that tripleo-quickstart has evolved
into a CI tool. It's primarily used by computers, and not humans.
tripleo-quickstart is a helpful set of ansible playbooks, and a
collection of feature sets. However, it's bec
On 14.8.2018 15:19, Bogdan Dobrelya wrote:
On 8/13/18 9:47 PM, Giulio Fidente wrote:
Hello,
I'd like to get some feedback regarding the remaining
work for the split controlplane spec implementation [1]
Specifically, while for some services like nova-compute it is not
necessary to update the co
On 16.8.2018 07:39, Cédric Jeanneret wrote:
On 08/16/2018 12:10 AM, Jason E. Rist wrote:
On 08/15/2018 03:32 AM, Cédric Jeanneret wrote:
Dear Community,
As you may know, a move toward Podman as replacement of Docker is starting.
One of the issues with podman is the lack of daemon, precisely
On 15.8.2018 11:32, Cédric Jeanneret wrote:
Dear Community,
As you may know, a move toward Podman as replacement of Docker is starting.
One of the issues with podman is the lack of daemon, precisely the lack
of a socket allowing to send commands and get a "computer formatted
output" (like JSON
On 16.8.2018 10:38, Steven Hardy wrote:
On Wed, Aug 15, 2018 at 10:48 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 mailto:emil...@redhat.com>> wrote:
More seriously here: there is an ongoing effort to converge the
+1!
On 1.8.2018 13:31, Giulio Fidente wrote:
Hi,
I would like to propose Lukas Bezdicka core on TripleO.
Lukas did a lot work in our tripleoclient, tripleo-common and
tripleo-heat-templates repos to make FFU possible.
FFU, which is meant to permit upgrades from Newton to Queens, requires
in d
Hi folks,
i want to raise attention on remaining patches that are needed to
prevent losing Ceph updates/upgrades in Rocky [1], basically making the
Ceph upgrade mechanism compatible with config-download. I'd call this a
semi-FFE, as a few of the patches have characteristics of feature work,
b
+1!
On 20.7.2018 10:07, Carlos Camacho Gonzalez wrote:
Hi!!!
I'll like to propose Jose Luis Franco [1][2] for core reviewer in all the
TripleO upgrades bits. He shows a constant and active involvement in
improving and fixing our updates/upgrades workflows, he helps also trying
to develop/improv
Thanks for the feedback, John and Emilien.
On 13.7.2018 01:35, Emilien Macchi wrote:
+1 for Option A as well, I feel like it's the one which would give us the
more of flexibility and also I'm not a big fan of the usage of Anchors for
this use case.
Some folks are currently working on extracting
Hi,
with the move to config-download deployments, we'll be moving from
executing external installers (like ceph-ansible) via Heat resources
encapsulating Mistral workflows towards executing them via Ansible
directly (nested Ansible process via external_deploy_tasks).
Updates and upgrades sti
On 19.6.2018 16:29, Lars Kellogg-Stedman wrote:
On Tue, Jun 19, 2018 at 02:18:38PM +0100, Steven Hardy wrote:
Is this the same issue Carlos is trying to fix via
https://review.openstack.org/#/c/494517/ ?
That solves part of the problem, but it's not a complete solution.
In particular, it doesn
+1
On 13.6.2018 17:50, Emilien Macchi wrote:
Alan Bishop has been highly involved in the Storage backends integration in
TripleO and Puppet modules, always here to update with new features, fix
(nasty and untestable third-party backends) bugs and manage all the
backports for stable releases:
htt
On 12.6.2018 15:06, James Slagle wrote:
On Mon, Jun 11, 2018 at 3:34 PM, Wesley Hayutin wrote:
Greetings,
I wanted to let everyone know that we have a keystone only deployment and
upgrade job in check non-voting. I'm asking everyone in TripleO to be
mindful of this job and to help make sure i
Hi,
this is mainly for CI folks and whom-it-may-concern.
Recently we came across the topic of how to enable/disable zuul repos at
various places in the CI jobs. For normal deploy jobs there's no need to
customize, but for update/upgrade jobs there is. It's not entirely
straightforward and the
+1!
On 19.4.2018 19:01, Emilien Macchi wrote:
Greetings,
As you probably know mcornea on IRC, Marius Cornea has been contributing on
TripleO for a while, specially on the upgrade bits.
Part of the quality team, he's always testing real customer scenarios and
brings a lot of good feedback in his
On 5.4.2018 21:04, Alex Schultz wrote:
On Thu, Apr 5, 2018 at 12:55 PM, Wesley Hayutin wrote:
FYI...
This is news to me so thanks to Emilien for pointing it out [1].
There are official tags for tripleo launchpad bugs. Personally, I like what
I've seen recently with some extra tags as they cou
On 6.2.2018 19:58, Wesley Hayutin wrote:
Greetings,
The TripleO-CI team has added a recreate / reproduce script to all the
tripleo upstream ci jobs as an artifact [1-2] much like the devstack
reproduce.sh script. If you find yourself in need of recreating a tripleo
ci job please take a look at
+1
On 6.12.2017 16:45, Emilien Macchi wrote:
Team,
Wes has been consistently and heavily involved in TripleO CI work.
He has a very well understanding on how tripleo-quickstart and
tripleo-quickstart-extras work, his number and quality of reviews are
excellent so far. His experience with testin
On 21.11.2017 12:01, Jiří Stránský wrote:
Kubernetes on the overcloud
===
The work on this front started with 2[0][1] patches that some of you might have
seen and then evolved into using the config download mechanism to execute these
tasks as part of the undercloud tasks
+1
On 29.11.2017 20:34, 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 has always
done quality reviews. She al
Kubernetes on the overcloud
===
The work on this front started with 2[0][1] patches that some of you might have
seen and then evolved into using the config download mechanism to execute these
tasks as part of the undercloud tasks[2][3] (Thanks a bunch, Jiri, for your work
+1!
On 8.11.2017 23:24, 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 of Ceph in containers.
I think John has goo
+1!
On 9.11.2017 09:48, Marios Andreou wrote:
Hello fellow owls,
(appologies for duplicate, forgot to add the tripleo in subject so worried
it would be missed)
I would like to nominate (and imo these are both long overdue already):
Sofer Athlan Guyot (chem) and
Mathieu Bultel (matbu)
to tri
On 7.11.2017 23:29, Wesley Hayutin wrote:
Greetings,
I'd like to propose we remove the upgrade jobs that are consistently
failing from the upstream infrastructure and instead focus our efforts in
RDO Software Factory.
The jobs listed in https://review.openstack.org/#/c/518405/ are
consistently
+1!
On 6.11.2017 15:32, Honza Pokorny wrote:
Hello people,
I would like to nominate Ana Krivokapić (akrivoka) for the core team for
tripleo-validations. She has really stepped up her game on that project
in terms of helpful reviews, and great patches.
With Ana's help as a core, we can get mor
On 6.11.2017 11:17, Jiří Stránský wrote:
On 6.11.2017 10:52, Marios Andreou wrote:
On Mon, Nov 6, 2017 at 11:09 AM, Marius Cornea wrote:
On Sat, Nov 4, 2017 at 2:27 AM, Emilien Macchi wrote:
Since we've got promotion, we can now properly test upgrades from ocata
to pike.
It's n
On 6.11.2017 10:52, Marios Andreou wrote:
On Mon, Nov 6, 2017 at 11:09 AM, Marius Cornea wrote:
On Sat, Nov 4, 2017 at 2:27 AM, Emilien Macchi wrote:
Since we've got promotion, we can now properly test upgrades from ocata
to pike.
It's now failing for various reasons, as you can see on:
ht
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
we
On 5.10.2017 22:40, Alex Schultz wrote:
Hey folks,
So I wandered across the policy spec[0] for how we should be handling
unbranched repository reviews and I would like to start a broader
discussion around this topic. We've seen it several times over the
recent history where a change in oooqe or
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 c
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ý wrote:
[...]
That way we could run the whole thing end-to-end via
ansible-playbook, or
if needed one could
On 21.9.2017 18:04, Marios Andreou wrote:
On Thu, Sep 21, 2017 at 3:53 PM, 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 Slagle 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 Slagle wrote:
- The entire sequence and flow is driven via Mistral on the Undercloud
by default. This preserves the API la
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, whi
On 30.8.2017 06:54, Emilien Macchi wrote:
On Tue, Aug 29, 2017 at 4:17 PM, Emilien Macchi wrote:
We are currently dealing with 4 issues and until they are fix, please
do not approve any patch. We want to keep the gate clear to merge the
fixes for the 4 problems first.
1) devstack-gate broke us
On 29.8.2017 17:12, Emilien Macchi wrote:
On Tue, Aug 29, 2017 at 2:14 AM, Jiří Stránský wrote:
[...]
the CI for containerized deployments with Pacemaker is close! In fact, it
works [1][2] (but there are pending changes to merge).
Really good news, thanks for the update!
The way it&#
On 29.8.2017 14:42, Giulio Fidente wrote:
On 08/29/2017 02:33 PM, Jiří Stránský wrote:
A bit of context: Currently our only upgrade check job is non-OVB -
containers-multinode-upgrades-nv. As of late we started hitting
timeouts, and the job only does mixed-version deploy + 1 node AIO
overcloud
On 29.8.2017 13:22, Giulio Fidente wrote:
On 08/29/2017 11:14 AM, Jiří Stránský wrote:
Hi owls,
the CI for containerized deployments with Pacemaker is close! In fact,
it works [1][2] (but there are pending changes to merge).
cool :D
I also spotted this which we need for ceph
https
Hi owls,
the CI for containerized deployments with Pacemaker is close! In fact,
it works [1][2] (but there are pending changes to merge).
The way it's proposed in gerrit currently is to switch the
centos-7-containers-multinode job (featureset010) to deploy with
Pacemaker. What do you think a
On 18.8.2017 17:25, Marios Andreou wrote:
On Fri, Aug 18, 2017 at 4:22 PM, Jiří Stránský wrote:
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
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 and
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: https://review.rdopro
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
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
separate
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 pr
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
+ kubernet
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, Op
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 i
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 c
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
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
all
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 wouldn't work for the C
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
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
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
setup / joining etc.
Jirka
Thanks in advance!
On Fri, Jun 9, 2017 at 5:49 PM, 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 atte
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
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 a
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
container
pa
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
On 31.5.2017 17:40, Dnyaneshwar Pawar wrote:
Hi Ben,
On 5/31/17, 8:06 PM, "Ben Nemec"
mailto:openst...@nemebean.com>> wrote:
I think we would need to see what your custom config templates look like
as well.
Custom config templates: http://paste.openstack.org/show/64/
Hello Dnyaneshwar,
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: https://bluejeans.com/4113567798/
Full min
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 r
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 som
On 12.5.2017 15:30, Emilien Macchi wrote:
On Wed, May 10, 2017 at 9:26 AM, Jiří Stránský 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 patches we need to lan
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
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
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
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 s
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
docs [1], just 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ý" wrote:
On 30.3.2017 14:58, Dan Prince wrote:
There is one case tha
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 imag
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 pup
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 o
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 th
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 instack-undercloud for a long
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 add
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
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 core
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 curren
+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 wh
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",
"overcloud-
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
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 quest
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", "
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 se
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
stable/liberty for upgrades. We have been discussing qu
+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
+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 pat
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 thr
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 i
1 - 100 of 148 matches
Mail list logo
