Open Stack

Jay. Do you have a plan to add a Savanna (type: Heat::Savanna) and Trove
 (type: Heat::Trove)  providers to the HOT DSL?


On Thu, Oct 31, 2013 at 10:33 PM, Jay Pipes <jaypipes at gmail.com> wrote:

> On 10/31/2013 01:51 PM, Alexander Kuznetsov wrote:
>
>> Hi Heat, Savanna and Trove teams,
>>
>> All this projects have common part related to software configuration
>> management.  For creation,  an environment  user should specify a
>> hardware parameter for vms:  choose flavor, decide use cinder or not,
>> configure networks for virtual machines, choose topology for hole
>> deployment. Next step is linking of software parameters with hardware
>> specification. From the end user point of view, existence of three
>> different places and three different ways (HEAT Hot DSL, Trove
>> clustering API and Savanna Hadoop templates) for software configuration
>> is not convenient, especially if user want to create an environment
>> simultaneously involving components from Savanna, Heat and Trove.
>>
>> I can suggest two approaches to overcome this situations:
>>
>> Common library in oslo. This approach allows a deep domain specific
>> customization. The user will still have 3 places with same UI where user
>> should perform configuration actions.
>>
>> Heat or some other component for software configuration management. This
>> approach is the best for end users. In feature possible will be some
>> limitation on deep domain specific customization for configuration
>> management.
>>
>
> I think this would be my preference.
>
> In other words, describe and orchestrate a Hadoop or Database setup using
> HOT templates and using Heat as the orchestration engine.
>
> Best,
> -jay
>
>  Heat, Savanna and Trove teams can you comment these ideas, what approach
>> are the best?
>>
>> Alexander Kuznetsov.
>>
>>
>> ______________________________**_________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.**org <OpenStack-dev at lists.openstack.org>
>> http://lists.openstack.org/**cgi-bin/mailman/listinfo/**openstack-dev<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>>
>>
>
> ______________________________**_________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.**org <OpenStack-dev at lists.openstack.org>
> http://lists.openstack.org/**cgi-bin/mailman/listinfo/**openstack-dev<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131101/6f4de6ab/attachment.html>