Open Stack

warm is just an other client, like we can have for the cli. It does
not claim to do what Heat can. It should be useful to prepare some templates
to be reused in different OpenStack environment without using script
shell or python.

When I said standalone client, I mean there is no need to install services
in your OpenStack cloud to use it.

Regards,
s.

----- Original Message -----
From: "Thomas Spatzier" <thomas.spatzier at de.ibm.com>
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org>
Sent: Thursday, March 20, 2014 9:44:22 AM
Subject: Re: [openstack-dev] [Heat]Heat use as a standalone component for Cloud Managment over multi IAAS

Just out of curiosity: what is the purpose of project "warm"? From the wiki
page and the sample it looks pretty much like what Heat is doing.
And "warm" is almost "HOT" so could you imagine your use cases can just be
addressed by Heat using HOT templates?

Regards,
Thomas

sahid <sahid.ferdjaoui at cloudwatt.com> wrote on 18/03/2014 12:56:47:

> From: sahid <sahid.ferdjaoui at cloudwatt.com>
> To: "OpenStack Development Mailing List (not for usage questions)"
> <openstack-dev at lists.openstack.org>
> Date: 18/03/2014 12:59
> Subject: Re: [openstack-dev] [Heat]Heat use as a standalone
> component for Cloud Managment over multi IAAS
>
> Sorry for the late of this response,
>
> I'm currently working on a project called Warm.
>     https://wiki.openstack.org/wiki/Warm
>
> It is used as a standalone client and try to deploy small OpenStack
> environments from Yzml templates. You can find some samples here:
>     https://github.com/sahid/warm-templates
>
> s.
>
> ----- Original Message -----
> From: "Charles Walker" <charles.walker.37 at gmail.com>
> To: openstack-dev at lists.openstack.org
> Sent: Wednesday, February 26, 2014 2:47:44 PM
> Subject: [openstack-dev] [Heat]Heat use as a standalone component
> for Cloud Managment over multi IAAS
>
> 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 at lists.openstack.org
> 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
>


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev