+1 on making him tripleo-ci core.
Great work!
On 11/15/18 5:50 PM, 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
There will be no meeting for the security squad next Tuesday 13th of November
since there's the
OpenStack summit.
Best Regards
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
There will be no meeting next Tuesday 13th of November since there's the
OpenStack summit.
Best Regards
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hello folks,
Please do not attempt to merge or recheck patches until we get this
sorted out.
We are dealing with several issues that have broken all jobs.
https://bugs.launchpad.net/tripleo/+bug/1801769
https://bugs.launchpad.net/tripleo/+bug/1801969
Thanks! We have been slow to update our docs. I did put up a blog post
about these sections of the templates [1], in case folks find that useful.
[1] http://jaormx.github.io/2018/dissecting-tripleo-service-templates-p2/
On 11/2/18 3:39 PM, Dan Prince wrote:
> I pushed a patch[1] to update our
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 wrote:
>>> Additionally I took a stab at combining the puppet/docker service
>>> definitions for the aodh services in a similar structure to start
>>>
Hello!
I would like to propose Bob Fournier (bfournie) as a core reviewer in
TripleO. His patches and reviews have spanned quite a wide range in our
project, his reviews show great insight and quality and I think he would
be a addition to the core team.
What do you folks think?
Best Regards
Hi all!
I'll be out starting from Oct 15th, coming back on Oct 19th.]
The upstream meeting will be led by Alex Schultz (mwhahaha).
Best Regards
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
We've been having a lot of timeouts and the gate is stacking up. I'm
purging out patches from the gate in order to reduce used resources
while this is sorted out.
Please do not merge patches until this issue is sorted out.
BR
On 09/14/2018 09:01 AM, Alex Schultz wrote:
> On Fri, Sep 14, 2018 at 6:37 AM, Chandan kumar wrote:
>> Hello,
>>
>> As Ocata release is already EOL on 27-08-2018 [1].
>> In TripleO, we are running Ocata jobs in TripleO CI and in promotion
>> pipelines.
>> Can we drop it all the jobs related to
Hey folks!
It's time to come up with topics to discuss on the forum in Berlin[1]!
There is an etherpad for us to bring up ideas:
https://etherpad.openstack.org/p/tripleo-forum-stein
We need to submit by September 12.
Here's is also the link to the wiki:
Due to folks being at the Denver PTG (including myself) there won't be
the weekly meeting next week.
BR
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Hello!
The Denver schedule is now available, still at the same link:
https://etherpad.openstack.org/p/tripleo-ptg-stein
And I also made a Google Calendar that folks can follow:
https://calendar.google.com/calendar?cid=MjdqZmUwNmN1dWhldDdjYm5vb3RvaGRyZTRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ
In
Logging is a topic that I think should get more love on the TripleO side.
On 08/24/2018 12:17 PM, Juan Badia Payno wrote:
> Recently, I did a little test regarding fluentd logging on the gates
> master[1], queens[2], pike [3]. I don't like the status of it, I'm
> still working on them, but
Logging is a topic that I think should get more love on the TripleO side.
On 08/24/2018 12:17 PM, Juan Badia Payno wrote:
> Recently, I did a little test regarding fluentd logging on the gates
> master[1], queens[2], pike [3]. I don't like the status of it, I'm
> still working on them, but
Thanks, merged the topics.
On 08/30/2018 07:10 PM, Giulio Fidente wrote:
> On 8/28/18 2:50 PM, Juan Antonio Osorio Robles wrote:
>> Hello folks!
>>
>>
>> With the PTG being quite soon, I just wanted to remind folks to add your
>> topics on the etherpad: https:/
FWIW, instead of barbican, castellan could be used as a key manager.
On 08/30/2018 12:23 PM, Adrian Turjak wrote:
>
>
> On 30/08/18 6:29 AM, Lance Bragstad wrote:
>>
>> Is that what is being described here ?
>>
>>
This is not the case. Barbican requires users and systems that use it to
use keystone for authentication. So keystone can't use Barbican for
this. Chicken and egg problem.
On 08/29/2018 08:08 PM, Waines, Greg wrote:
>
> My understanding is that Keystone can be configured to use Barbican to
>
Hello folks!
With the PTG being quite soon, I just wanted to remind folks to add your
topics on the etherpad: https://etherpad.openstack.org/p/tripleo-ptg-stein
Also, please vote for the topics you're the most interested in, so we
can add them to the agenda. I'll submit a potential agenda by
___
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Juan Antonio Osorio R.
e-mail:
Yeah! +1 Moisés has been doing a great job there
On Wed, 1 Aug 2018, 16:27 Doug Hellmann, wrote:
> Moisés Guimarães (moguimar) did quite a bit of work on oslo.config
> during the Rocky cycle to add driver support. Based on that work,
> and a discussion we have had since then about general
ward and get developers easier ways to bring up testing
environments for them to work on and to be able to reproduce CI jobs.
Thanks!
Juan Antonio Osorio Robles
IRC: jaosorior
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail
Sounds good to me. Even if pacemaker is heavier, less options and
consistency is better.
Greetings from Mexico :D
On Fri, 13 Jul 2018, 13:33 Emilien Macchi, wrote:
> Greetings,
>
> We have been supporting both Keepalived and Pacemaker to handle VIP
> management.
> Keepalived is actually the
It is unfortunately a known issue and is present in queens and master as
well. I think Michele (bandini on IRC) was working on it.
On Thu, 21 Jun 2018, 06:45 Lars Kellogg-Stedman, wrote:
> I've noticed that when updating the overcloud with 'overcloud deploy',
> the deploy process does not
+1 I dig
On Fri, 15 Jun 2018, 17:41 Dave McCowan (dmccowan),
wrote:
> +1
> This is a great time.
>
> On 6/14/18, 4:30 PM, "Ade Lee" wrote:
>
> >The new time slot has been pretty difficult for folks to attend.
> >I'd like to propose a new time slot, which will hopefully be more
> >amenable to
Hello,
A lot of folks are in the OpenStack summit, so we'll cancel the Security
Squad meeting today.
BR
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
__
OpenStack Development Mailing List (not for usage questions
you folks
think?
[1] https://review.openstack.org/#/c/567200/
BR
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
+1 :D hell yeah!
On Thu, 19 Apr 2018, 20:05 John Fulton, wrote:
> +1
>
> On Thu, Apr 19, 2018 at 1:01 PM, Emilien Macchi
> wrote:
> > Greetings,
> >
> > As you probably know mcornea on IRC, Marius Cornea has been contributing
> on
> > TripleO for a
gt; __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> _
Correct, only public endpoints.
On Wed, Mar 14, 2018 at 1:52 PM, Dmitry Tantsur <dtant...@redhat.com> wrote:
> Just to clarify: only for public endpoints, right? I don't think e.g.
> ironic-python-agent can talk to self-signed certificates yet.
>
>
> On 03/14/2018 07:03 AM
/undercloud.conf.j2#L117
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
https://etherpad.openstack.org/p/tripleo-security-squad
And here's the patch adding the Security Squad to the list
https://review.openstack.org/#/c/550001/
Feel free to join if you're interested.
BR
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
tment, we have plenty of room
> for it.
>
> Thanks!
> --
> Emilien Macchi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.
On 4 Jan 2018 23:35, "Alan Bishop" wrote:
Has there been any previous discussion on providing a mechanism for
transferring ownership of a secret from one user to another?
For castellan there isn't a discussion AFAIK. But it sounds like something
you can enable with
By using the ssl_overcloud flag in your configuration and setting it to
true.
On 6 Dec 2017 17:33, "Moshe Levi" <mosh...@mellanox.com> wrote:
> How do I tell quickstart to generate certs and enable tls?
>
>
>
> *From:* Juan Antonio Osorio [mailto:jaosor...
+1
On 6 Dec 2017 18:25, "Harry Rybacki" wrote:
On Wed, Dec 6, 2017 at 11:19 AM, mathieu bultel wrote:
> On 12/06/2017 04:45 PM, Emilien Macchi wrote:
>> Team,
>>
>> Wes has been consistently and heavily involved in TripleO CI work.
>> He has a very well
recommend using that. Rather generate your own certs or tell
quickstart to do it for you by using the appropriate flag.
So maybe the is an issue with tripleo or just these config files
*From:* Juan Antonio Osorio [mailto:jaosor...@gmail.com]
*Sent:* Wednesday, December 6, 2017 12:36 PM
*To:* OpenS
>From the node you're running the nova command, do you have access to the
10.0.0.0 network (external)?
In virtual environments, quickstart will leave an overcloud-prep-network.sh
script that will create a vlan interface that gives the undercloud access
to that network. So, if it's a virtual
ubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
__
OpenStack Development Mailing L
On 21 Nov 2017 01:19, "Alex Schultz" <aschu...@redhat.com> wrote:
On Thu, Nov 16, 2017 at 12:01 AM, Juan Antonio Osorio
<jaosor...@gmail.com> wrote:
> Hello folks!
>
> A few months ago Dan Sneddon and me worked in an ansible role that would
> enable IPSEC for
TripleO composable
service.
Any input and contributions are welcome!
[1] https://github.com/JAORMX/tripleo-ipsec
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
__
OpenStack Development Mailing List (not for usage
> Thanks in advance.
> Best regards.
>
> 2017-11-09 9:05 GMT+01:00 Juan Antonio Osorio <jaosor...@gmail.com>:
>
>> Alright,
>>
>> So, first question. What do you actually want to do? Do you need to
>> authenticate with the heat endpoint with TLS (using cli
want to use use it in to call python-heatclient API in order
>> to create stacks (Openstack address is based on https).
>> I am wondering, where to copy this pem file and how to refer it ?
>>
>> Thanks in advance.
>> Best regards.
>>
>>
>>
>> 2017-11
ubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
__
OpenStack De
ubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
__
OpenStack De
ubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
__
OpenStack De
Proposed a patch to be able to enable the JSON formatter via an oslo.log
configuration parameter:
https://review.openstack.org/#/c/517882/
On Mon, Nov 6, 2017 at 9:43 AM, Cédric Jeanneret <
cedric.jeanne...@camptocamp.com> wrote:
> On 11/06/2017 08:36 AM, Juan Antonio Osorio wrote:
&
file. The aforementioned option is something that we're using for
containerized openstack services.
I'll look into adding the ability to turn that handler on/off from oslo.log.
On Mon, Nov 6, 2017 at 8:34 AM, Juan Antonio Osorio <jaosor...@gmail.com>
wrote:
>
>
> On Mon, Nov 6,
he usage of this advanced
configuration. Taking it into use doesn't look that bad; If you look at the
file where the options are being set (_options.py), you will see that there
are several options that get ignored once we start usi
On 3 Nov 2017 19:59, "Doug Hellmann" wrote:
Excerpts from Cédric Jeanneret's message of 2017-11-01 14:54:34 +0100:
> Dear Stackers,
>
> While working on my locally deployed Openstack (Pike using TripleO), I
> was a bit struggling with the logging part. Currently, all logs
;
>>
>> ¹
>> https://github.com/openstack/oslo.log/blob/master/oslo_log/f
>> ormatters.py#L166-L235
>> ²
>> http://eavesdrop.openstack.org/irclogs/%23openstack-oslo/%
>> 23openstack-oslo.2017-11-01.log.html#t2017-11-01T13:23:14
>> ³ https://github.com/openstack/puppet-nova/blob
Thanks for the postmortem; it's always a good read tp learn stuff :)
On 28 Oct 2017 00:11, "Ben Nemec" wrote:
Hi all,
As you may or may not have noticed all ovb jobs on rh1 started failing
sometime last night. After some investigation today I found a few issues.
k Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
_
try to run FreeIPA on a container [1] (which wasn't available when I
started working on this).
[1] https://hub.docker.com/r/freeipa/freeipa-server/
On Sat, Aug 26, 2017 at 2:52 AM, Emilien Macchi <emil...@redhat.com> wrote:
> On Sun, Aug 20, 2017 at 11:45 PM, Juan Antonio Osorio
...@lists.openstack.org
>>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
>>> k-operators
>>> >
>>>
>>> ___
>>> OpenStack-operators mailing list
>>> openstack-operat..
Nice!! Congrats Gibi!!
On 23 Aug 2017 11:19, "Stephen Finucane" wrote:
> On Tue, 2017-08-22 at 20:18 -0500, Matt Riedemann wrote:
> > I'm proposing that we add gibi to the nova core team. He's been around
> > for awhile now and has shown persistence and leadership in the
>
On Mon, Aug 21, 2017 at 5:48 PM, Ben Nemec <openst...@nemebean.com> wrote:
>
>
> On 08/21/2017 01:45 AM, Juan Antonio Osorio wrote:
>
>> The second option seems like the most viable. Not sure how the TripleO
>> integration would go though. Care to elaborate on what y
but will be to be documented).
> - Create a composable service that will deploy FreeIPA service(s),
> part of TripleO Heat Templates. The way it works *now* will require
> you to have a puppet-freeipa module to deploy the bits but we're
> work
+1!!!
On 21 Jul 2017 22:32, "Alex Schultz" wrote:
On Fri, Jul 21, 2017 at 12:58 PM, Pradeep Kilambi wrote:
> On Fri, Jul 21, 2017 at 1:36 PM, Brent Eagles wrote:
>>
>>
>> On Fri, Jul 21, 2017 at 12:25 PM, Emilien Macchi
I actually like the idea of moving to kolla-kubernetes. I guess there would
be a bunch of work towards giving folks an upgrade path and reaching
feature parity; but this would happen anyway eurgh the switch to
kubernetes. And this would have the added value of merging two
communities, thus more
+1
He's a great reviewer
On 7 Jul 2017 8:40 pm, "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
+1
On 5 Jul 2017 19:57, "Emilien Macchi" wrote:
> After reading http://lists.openstack.org/pipermail/openstack-dev/2017-
> June/118899.html
> - we might want to collect TripleO's community feedback on doing
> weekly meetings on #tripleo instead of #openstack-meeting-alt.
>
>
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
_
-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
__
OpenStack Development Mailing List (no
master/
> nodepool/builder.py
>
> Thanks
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev
to inject
extra ansible roles into the overcloud nodes? If not, maybe a dedicated
hook to do this kind of thing would be something useful for others as well.
Any thoughts?
[1] https://github.com/JAORMX/tripleo-ipsec
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
rds,
> Rabi Mishra
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/opens
by responding with +1.
>
> --Dave
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-mistralclient/commit/83b3d0d39cb8072682fac74f6a40877030e91c18
And this is the commit that's attempting to migrate to keystone v3 in
tripleo: https://review.openstack.org/#/c/446752/
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
b
>
> thoughts?
>
> --
> Best regards
> Sagi Shnaidman
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mail
Why not drive the post-config with something like shade over ansible?
Similar to what the kolla-ansible community is doing.
On 30 Mar 2017 16:42, "Jiří Stránský" wrote:
> On 30.3.2017 14:58, Dan Prince wrote:
>
>> There is one case that I was thinking about reusing this piece
On Fri, Feb 3, 2017 at 5:31 PM, Ben Nemec <openst...@nemebean.com> wrote:
>
>
> On 02/02/2017 06:27 PM, Juan Antonio Osorio wrote:
>
>> Hello,
>>
>> I would like to request an FFE to properly support the novajoin
>> vendordata plugin in TripleO. Most of
On Fri, Feb 3, 2017 at 4:54 PM, Emilien Macchi <emil...@redhat.com> wrote:
> On Thu, Feb 2, 2017 at 7:27 PM, Juan Antonio Osorio <jaosor...@gmail.com>
> wrote:
> > Hello,
> >
> > I would like to request an FFE to properly support the novajoin
> vendordata
it
makes it easier to populate the required field's in the CA (which in our
case is FreeIPA). I'm currently working on a patch to add it to the
fakeha-caserver OVB job; which, after this is done, I hope to move from the
experimental queue, to the periodic one.
BR
--
Juan Antonio Osorio R.
e-mail: jaosor
uestions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
_
> primarily in the puppet manifest so it's not a huge stretch to add him.
> >
>
> +1 as well.
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:uns
quicker.
Best Regards,
--
Juan Antonio Osorio R.
jaosorior
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
(not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not
I don't have a strong opinion about any option, as long as we have
something in place I'm happy.
But regarding option 1.A: what would be done for newton once these
templates are moved to t-h-t. Would they be backported? What about mitaka?
On 24 Nov 2016 17:55, "Carlos Camacho Gonzalez"
g/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi
+1
On 7 Nov 2016 17:18, "Dave McCowan (dmccowan)" wrote:
>
> Arun has been a long-time terrific reviewer and contributor to Barbican.
>
> 100% +1
>
>
> --Dave
>
> On 11/7/16, 9:37 AM, "Ade Lee" wrote:
>
> >Hi everyone,
> >
> >I'd like to nominate Arun Kant
+1 :D
On 4 Nov 2016 20:16, "Jiří Stránský" wrote:
> +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
>>
?
>
> Thanks
> -dant
>
> --
>
> P.S. and full disclosure: I'm biased towards the third option.
>
>
> ______
> OpenStack Development Mailing Lis
, but did not get
enough time to figure out some parts of it. So that work will not be
included here.
BR
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
__
OpenStack Development Mailing List (not for usage questions
t
> productive cycle, and I'm looking forward to reaching our final newton
> release! :)
>
> Thanks,
>
> Steve
>
> __________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: ope
Adam, that should be fixed by https://review.openstack.org/#/c/341354/
which merged not too many days ago. Before that commit we had another
configuration which was already deprecated in keystone upstream.
On 6 Aug 2016 05:04, "Adam Young" wrote:
> On 08/05/2016 06:40 PM,
On Tue, Jun 21, 2016 at 10:51 PM, Adam Young <ayo...@redhat.com> wrote:
> On 06/21/2016 02:42 PM, Juan Antonio Osorio wrote:
>
> Adam, this is pretty much the proposal for TLS for the internal services
> (which you were added already as a reviewer for the spec)
> https://rev
where they need some confirmation from the deployment
> process that the data in the CSR is valid and should be signed.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsub
+1 on my side.
On 9 Jun 2016 18:10, "Emilien Macchi" wrote:
> On Thu, Jun 9, 2016 at 10:03 AM, 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
ubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
__
OpenSt
oker. Since Rabbit seems to be the tool
> > of
> > choice, we would use X509 authentication and TLS for
> > encryption. ACLs,
> > for now, would stay in the flat file format. In the future, we
> > might
> > chose to use the LDAP backed ACLs for Rabbit, as they
around. :/
>
> We need to really discuss this problem at the summit and get a viable path
> forward. Its just getting worse. :/
>
> Thanks,
> Kevin
> ----------
> *From:* Juan Antonio Osorio [jaosor...@gmail.com]
> *Sent:* Tuesday, April 05, 2016 5
6PM +0300, Juan Antonio Osorio wrote:
> >On Tue, Apr 5, 2016 at 11:36 AM, Steven Hardy <sha...@redhat.com>
> wrote:
> >
> > On Sat, Apr 02, 2016 at 05:28:57PM -0400, Adam Young wrote:
> > > I finally have enough understanding of what is going on wit
mechanism for
this means, but it was deprecated recently. So bummer :/
>
> Nova instance user spec again?
>
> Thanks,
> Kevin
>
> ------
> *From:* Juan Antonio Osorio
> *Sent:* Tuesday, April 05, 2016 4:07:06 AM
> *To:* OpenStack Development Mailing Lis
> > When we did the Rippowam demo, we used the Proton driver and Kerberos for
> > securing the message broker. Since Rabbit seems to be the tool of
> choice,
> > we would use X509 authentication and TLS for encryption. ACLs, for now,
> > would stay in the flat file format.
e might chose to use
> the LDAP backed ACLs for Rabbit, as they seem far more flexible. Rabbit
> does not currently support Kerberos for either authentication or
> encryption, but we can engage the upstream team to implement it if desired
> in the future, or we can shift to a Proton based depl
___
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
+1
--
Juan Antonio Osorio R.
e-mail: jaosor...@gmail.com
___
+1
On 20 Mar 2016 20:27, "Dan Prince" wrote:
> I'd like to propose that we add Emilien Macchi to the TripleO core
> review team. Emilien has been getting more involved with TripleO during
> this last release. In addition to help with various Puppet things he
> also has
>
So then, would it be acceptable to come up with a blueprint trying to
formalize
the interfaces for the hooks, and make those standard (and better tested and
documented)? We could base the deprecation on the outcome of that blueprint.
I think everybody agrees that the current solution is not ide
>> we can collect use cases for things that are currently using hooks that
>> we may want to support in other ways in Newton.
>>
>> -Sean
>>
>>
> I think you should probably also post this to the operators mailing list
> before we actually deprecate hooks.
I agree with Matt, I think this should ge
1 - 100 of 115 matches
Mail list logo