Open Stack

On 11/01/2013 10:29 AM, Alexander Kuznetsov wrote:
> Jay. Do you have a plan to add a Savanna (type: Heat::Savanna) and Trove
>   (type: Heat::Trove)  providers to the HOT DSL?

Hi Alexander,

No, but I'd be interested in working on them, particularly a Savannah 
provider for Heat. I can start on it once the instance group API 
extension is in Nova and wired into Heat.

Best,
-jay

> On Thu, Oct 31, 2013 at 10:33 PM, Jay Pipes <jaypipes at gmail.com
> <mailto: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
>         <mailto: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
>     <mailto: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
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>