On 09/19/2016 01:25 PM, Steven Hardy wrote:
On Wed, Sep 14, 2016 at 06:32:07PM +0200, Giulio Fidente wrote:
On 09/14/2016 05:59 PM, Giulio Fidente wrote:
On 09/14/2016 02:31 PM, Steven Hardy wrote:
Related to this is the future of all of the per-role customization
interfaces. I'm thinking
On Wed, Sep 14, 2016 at 06:32:07PM +0200, Giulio Fidente wrote:
> On 09/14/2016 05:59 PM, Giulio Fidente wrote:
> > On 09/14/2016 02:31 PM, Steven Hardy wrote:
> > > Related to this is the future of all of the per-role customization
> > > interfaces. I'm thinking these don't really make sense to
On 09/14/2016 05:59 PM, Giulio Fidente wrote:
On 09/14/2016 02:31 PM, Steven Hardy wrote:
Related to this is the future of all of the per-role customization
interfaces. I'm thinking these don't really make sense to maintain
long-term now we have the new composable services architecture, and it
On 09/14/2016 02:31 PM, Steven Hardy wrote:
Related to this is the future of all of the per-role customization
interfaces. I'm thinking these don't really make sense to maintain
long-term now we have the new composable services architecture, and it
would be better if we can deprecate them and
Hi all,
I wanted to draw attention to this patch:
https://review.openstack.org/#/c/367295/
As part of the custom-roles work, I had to break backwards compatibility
for the OS::TripleO::AllNodesExtraConfig resource.
I'm not happy about that, but I couldn't find any way to avoid it if we
want to
