On 02/03/2017 10:21 AM, Juan Antonio Osorio wrote:
On Fri, Feb 3, 2017 at 5:31 PM, Ben Nemec > wrote:
On 02/02/2017 06:27 PM, Juan Antonio Osorio wrote:
Hello,
I would like to request an FFE to properly support
On Fri, Feb 3, 2017 at 5:31 PM, Ben Nemec 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 the work has landed, however, we
>> still
On Fri, Feb 3, 2017 at 4:54 PM, Emilien Macchi wrote:
> On Thu, Feb 2, 2017 at 7: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 the work
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 the work has landed, however, we
still need to add it to TripleO's CI in order to have it officially
supported.
This is crucial for
On Thu, Feb 2, 2017 at 7: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 the work has landed, however, we still need to
> add it to TripleO's CI in order to have it
On Thu, Feb 2, 2017 at 10:22 PM, Michael Still wrote:
> What version of nova is tripleo using here? This wont work quite right if
> you're using Mitaka until https://review.openstack.org/#/c/427547/ lands and
> is released.
TripleO Ocata will use Nova Ocata, using the release
What version of nova is tripleo using here? This wont work quite right if
you're using Mitaka until https://review.openstack.org/#/c/427547/ lands
and is released.
Also, I didn't know novajoin existed and am pleased to have discovered it.
Michael
On Fri, Feb 3, 2017 at 11:27 AM, Juan Antonio
Hello,
I would like to request an FFE to properly support the novajoin vendordata
plugin in TripleO. Most of the work has landed, however, we still need to
add it to TripleO's CI in order to have it officially supported.
This is crucial for TLS-everywhere configuration's usability, since it