Thanks Angus. I think it will suffice.

By persona, though, I was meaning different admins working on the same
orchestration - may be storage admin, VM admin, app admin .. those I meant
as separate personas.


Thanks.
Pradip


On Wed, Nov 12, 2014 at 10:08 AM, Angus Salkeld <asalk...@mirantis.com>
wrote:

> On Wed, Nov 12, 2014 at 1:43 PM, Pradip Mukhopadhyay <
> pradip.inte...@gmail.com> wrote:
>
>> Would like to ask the forum if something has already been considered to
>> make the HOT (Heat Orchestration Template) hierarchical.
>>
>> Basically the template file might consist of different personas putting
>> things together. So from manageability of the templates - it will be a good
>> idea to separate it our based on different personas and have a master file
>> that will 'instantiate' the respective templates.personas.
>>
>>
>> If not considered already - any thought on this?
>>
>>
>> If already considered - any cons that was discussed earlier?
>>
>>
>>
> Hi
>
> I am not sure what you mean about "personas", but you can have
> hierarchical templates.
> see:
> http://docs.openstack.org/developer/heat/template_guide/composition.html
>
> Regards
> Angus
>
>
>>
>>
>> Thanks,
>> Pradip
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to