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.ferdja...@cloudwatt.com wrote on 18/03/2014 12:56:47: From: sahid sahid.ferdja...@cloudwatt.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@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...@gmail.com To: openstack-dev@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@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
Re: [openstack-dev] [Heat]Heat use as a standalone component for Cloud Managment over multi IAAS
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.spatz...@de.ibm.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@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.ferdja...@cloudwatt.com wrote on 18/03/2014 12:56:47: From: sahid sahid.ferdja...@cloudwatt.com To: OpenStack Development Mailing List (not for usage questions) openstack-dev@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...@gmail.com To: openstack-dev@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@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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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...@gmail.com To: openstack-dev@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@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
Re: [openstack-dev] [Heat]Heat use as a standalone component for Cloud Managment over multi IAAS
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 -- Regards, Alexander Tivelkov [1[ - https://wiki.openstack.org/wiki/Murano 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
Re: [openstack-dev] [Heat]Heat use as a standalone component for Cloud Managment over multi IAAS
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
Re: [openstack-dev] [Heat]Heat use as a standalone component for Cloud Managment over multi IAAS
Excerpts from Alexander Tivelkov's message of 2014-02-28 03:52:52 -0800: 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 FYI, Juju existed long before OpsWorks. http://aws.amazon.com/about-aws/whats-new/2013/02/18/announcing-aws-opsworks/ Even my last commit to Juju (the python version..) happened well before OpsWorks existed: http://bazaar.launchpad.net/~juju/juju/trunk/revision/599 Anyway, Heat is intended to be able to manage things at a high level too, just with more of the guts exposed for tinkering. :) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Heat]Heat use as a standalone component for Cloud Managment over multi IAAS
On 02/26/2014 06:47 AM, Charles Walker 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: You will notice at the top of this page, it is clearly labeled Proposal Only. Just a tip, but I'd recommend taking anything on the wiki with a grain of salt (vs what is actually put on docs.openstack.org, which is a more accurate world view). The Heat developers have coalesced around a de-facto standard DSL called HOT instead: http://docs.openstack.org/developer/heat/template_guide/hot_spec.html *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). First, Heat has a hard dependency on keystone. Second, it wouldn't be very useful in this configuration. Heat provides built-in resources for managing things like servers, floating ips, and other types of resources. These resource plugins expect to communicate with openstack nova, neutron, etc. If you were really motivated, you could write bespoke plugins for all of the AWS/GCE services to run a hybrid cloud using Heat. If you were even more motivated, you could get these merged upstream. But hybrid cloud is not in scope for the Orchestration program. We don't stop people from trying to use Heat in this way, but we don't directly enable it in the resources either. In the future, I'd recommend asking general questions like this on ask.openstack.org so the entire community can share and record the experience, rather then being lost on a mailing list. Thanks! -steve 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
Re: [openstack-dev] [Heat]Heat use as a standalone component for Cloud Managment over multi IAAS
On 26/02/14 07:03 -0700, Steven Dake wrote: On 02/26/2014 06:47 AM, Charles Walker 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: You will notice at the top of this page, it is clearly labeled Proposal Only. Just a tip, but I'd recommend taking anything on the wiki with a grain of salt (vs what is actually put on docs.openstack.org, which is a more accurate world view). The Heat developers have coalesced around a de-facto standard DSL called HOT instead: http://docs.openstack.org/developer/heat/template_guide/hot_spec.html *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). First, Heat has a hard dependency on keystone. Second, it wouldn't be very useful in this configuration. Heat provides built-in resources for managing things like servers, floating ips, and other types of resources. These resource plugins expect to communicate with openstack nova, neutron, etc. If you were really motivated, you could write bespoke plugins for all of the AWS/GCE services to run a hybrid cloud using Heat. If you were even more motivated, you could get these merged upstream. But hybrid cloud is not in scope for the Orchestration program. We don't stop people from trying to use Heat in this way, but we don't directly enable it in the resources either. Have a look at the Rackspace plugins in contrib/rackspace/. -Angus In the future, I'd recommend asking general questions like this on ask.openstack.org so the entire community can share and record the experience, rather then being lost on a mailing list. Thanks! -steve 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 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
