Hi Charles, If you are looking for the analogues of Juju in OpenStack, you probably may take a look at Murano Project [1]. It is an application catalog backed with a powerful workflow execution engine, which is built on top of Heat's orchestration, but run's at a higher level. It has borrowed lots of idea from Juju (or, more precisely, both took a lot from Amazon's OpsWorks ideas). Also, if you are looking to orchestrate on top of non-openstack clouds, then Murano's DSL may also be an answer: Murano's workflows may be designed to trigger any external APIs, not necessary OpenStack-only, so the technical possibility to orchestrate AWS and GCE exists in Murano's design, yet not present in the current roadmap.
Please feel free to ask for more details either in [Murano] ML or at #murano channel at Freenode. Thanks [1] - https://wiki.openstack.org/wiki/Murano -- Regards, Alexander Tivelkov -- Regards, Alexander Tivelkov On Wed, Feb 26, 2014 at 5:47 PM, Charles Walker <charles.walker...@gmail.com > wrote: > Hi, > > > I am trying to deploy the proprietary application made in my company on > the cloud. The pre requisite for this is to have a IAAS which can be either > a public cloud or private cloud (openstack is an option for a private IAAS). > > > The first prototype I made was based on a homemade python orchestrator and > apache libCloud to interact with IAAS (AWS and Rackspace and GCE). > > The orchestrator part is a python code reading a template file which > contains the info needed to deploy my application. This template file > indicates the number of VM and the scripts associated to each VM type to > install it. > > > Now I was trying to have a look on existing open source tool to do the > orchestration part. I find JUJU (https://juju.ubuntu.com/) or HEAT ( > https://wiki.openstack.org/wiki/Heat). > > I am investigating deeper HEAT and also had a look on > https://wiki.openstack.org/wiki/Heat/DSL which mentioned: > > *"Cloud Service Provider* - A service entity offering hosted cloud > services on OpenStack or another cloud technology. Also known as a Vendor." > > > I think HEAT as its actual version will not match my requirement but I > have the feeling that it is going to evolve and could cover my needs. > > > I would like to know if it would be possible to use HEAT as a standalone > component in the future (without Nova and other Ostack modules)? The goal > would be to deploy an application from a template file on multiple cloud > service (like AWS, GCE). > > > Any feedback from people working on HEAT could help me. > > > Thanks, Charles. > > _______________________________________________ > 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