|
|
| Line 3: |
Line 3: |
| | = Murano Open PaaS = | | = Murano Open PaaS = |
| | | | |
| − | Heat is the main project in the OpenStack Orchestration program. It implements an orchestration engine to launch multiple composite cloud applications based on templates in the form of text files that can be treated like code. A native Heat template format is evolving, but Heat also endeavours to provide compatibility with the [http://docs.amazonwebservices.com/AWSCloudFormation/latest/APIReference/Welcome.html?r=7078 AWS CloudFormation] template format, so that many existing CloudFormation templates can be launched on OpenStack. Heat provides both an [http://developer.openstack.org/api-ref-orchestration-v1.html OpenStack-native ReST API] and a CloudFormation-compatible Query API.
| + | Murano Open PaaS is a collection of Murano application, which allows to provide fast and clear solution for deploying PaaS. It contains such applications like: Gerrit, Jenkins, Zuul, etc. |
| − | | + | These application can be installed as one Meta application, which is consisted of all necessary applications. Also It can be independent application, if user want to use his own Jenkins ans wants to install only Gerrit application. |
| − | Why ‘Heat’? It makes the clouds rise!
| + | Obviously it provides flexible solution for user clouds and can be easily re-used as much as user want. |
| | | | |
| | == How it works == | | == How it works == |
| | | | |
| − | * A Heat template describes the infrastructure for a cloud application in a text file that is readable and writable by humans, and can be checked into version control, diffed, &c. | + | * These applications can be uploaded in Murano and then installed in user environment. |
| − | * Infrastructure resources that can be described include: servers, floating ips, volumes, security groups, users, etc.
| |
| − | * Heat also provides an autoscaling service that integrates with [[Telemetry]], so you can include a scaling group as a resource in a template.
| |
| − | * Templates can also specify the relationships between resources (e.g. this volume is connected to this server). This enables Heat to call out to the OpenStack APIs to create all of your infrastructure in the correct order to completely launch your application.
| |
| − | * Heat manages the whole lifecycle of the application - when you need to change your infrastructure, simply modify the template and use it to update your existing stack. Heat knows how to make the necessary changes. It will delete all of the resources when you are finished with the application, too.
| |
| − | * Heat primarily manages infrastructure, but the templates integrate well with software configuration management tools such as [https://s3.amazonaws.com/cloudformation-examples/IntegratingAWSCloudFormationWithPuppet.pdf Puppet] and [http://www.full360.com/2011/02/27/integrating-aws-cloudformation-and-chef.html Chef]. The Heat team is working on providing even better integration between infrastructure and software.
| |
| − | | |
| − | == Architecture ==
| |
| − | | |
| − | Heat comprises a number of Python applications:
| |
| − | | |
| − | === heat ===
| |
| − | | |
| − | The heat tool is a CLI which communicates with the heat-api to execute AWS CloudFormation APIs. Of course this is not required—developers could also use the Heat APIs directly.
| |
| − | | |
| − | === heat-api ===
| |
| − | | |
| − | The heat-api component provides an [http://developer.openstack.org/api-ref-orchestration-v1.html OpenStack-native ReST API] that processes API requests by sending them to the heat-engine over RPC.
| |
| − | | |
| − | === heat-api-cfn ===
| |
| − | | |
| − | The heat-api-cfn component provides an AWS-style Query API that is compatible with AWS CloudFormation and processes API requests by sending them to the heat-engine over RPC.
| |
| − | | |
| − | === heat-engine ===
| |
| − | | |
| − | The heat engine does the main work of orchestrating the launch of templates and providing events back to the API consumer.
| |
| | | | |
| | == Development == | | == Development == |
| − | * [https://github.com/openstack/heat Source repository] | + | * [https://github.com/openstack/murano-open-paas Source repository] |
| − | * [https://github.com/openstack/python-heatclient Client source repository]
| + | * [https://bugs.launchpad.net/murano-open-paas Bug tracker] |
| − | * [https://github.com/openstack/heat-templates Example templates]
| + | * [https://blueprints.launchpad.net/murano-open-paas Feature tracker] |
| − | * [https://bugs.launchpad.net/heat Bug tracker] | |
| − | * [https://blueprints.launchpad.net/heat Feature tracker] | |
| − | * [http://tarballs.openstack.org/heat/ Tarballs]
| |
| − | * [[Heat/Plugins|Heat Plugin Developer Guide]]
| |
| − | * [[Heat/DevelopmentProcess|Developer Process]]
| |
| − | * [[Heat/CoreTeam|Core Team]]
| |
| − | * [https://review.openstack.org/#/dashboard/?foreach=%28project%3Aopenstack%2Ddev%2Fheat%2Dcfnclient+OR+project%3Aopenstack%2Fheat+OR+project%3Aopenstack%2Fheat%2Dcfntools+OR+project%3Aopenstack%2Fheat%2Dspecs+OR+project%3Aopenstack%2Fheat%2Dtemplates+OR+project%3Aopenstack%2Fpython%2Dheatclient+OR+project%3Aopenstack%2Ftripleo%2Dheat%2Dtemplates+OR+project%3Aopenstack%2Fheat%2Dtranslator+OR+project%3Aopenstack%2Fpuppet%2Dheat%29+status%3Aopen+NOT+owner%3Aself+NOT+label%3AWorkflow%3C%3D%2D1+label%3AVerified%3E%3D1%2Cjenkins+NOT+label%3ACode%2DReview%3E%3D0%2Cself&title=Heat+Review+Inbox&Proposal+Bot+Proposals=owner%3A%22OpenStack+Proposal+Bot+%3Copenstack%2Dinfra%40lists.openstack.org%3E%22&Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1+limit%3A50&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A5d&You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=NOT+label%3ACode%2DReview%3C%3D2%2Cself+reviewer%3Aself&Passed+Jenkins%2C+No+Negative+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1+limit%3A50&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+label%3ACode%2DReview%3C%3D2+age%3A2d&Negative+Feedback=label%3ACode%2DReview%3C%3D%2D1+limit%3A10 Code Review Dashboard]
| |
| − | | |
| − | == Getting Started Guides ==
| |
| − | There are getting started guides for several distributions in the [http://docs.openstack.org/developer/heat/getting_started/index.html Heat Documentation]
| |
| − | * The installation guides on http://docs.openstack.org
| |
| − | * [http://docs.openstack.org/developer/heat/getting_started/on_fedora.html Getting Started With Heat on Fedora]
| |
| − | * [http://docs.openstack.org/developer/heat/getting_started/on_ubuntu.html Getting Started With Heat on Ubuntu]
| |
| − | * [http://docs.openstack.org/developer/heat/getting_started/on_devstack.html Heat and Devstack]
| |
| − | * [http://docs.openstack.org/user-guide/content/heat_client_commands.html Heat chapter] of the [http://docs.openstack.org/cli/quick-start/content/index.html OpenStack Clients Guide]
| |
| − | | |
| − | == Other Links ==
| |
| − | * [http://docs.openstack.org/developer/heat/template_guide/hot_guide.html Heat Orchestration Template (HOT) Guide]
| |
| − | * [[Heat/ApplicationDeployment|How Heat uses CloudFormation and cloud-init for application deployment]]
| |
| − | * [[Heat/BotoCompatibility|Boto Compatibility Matrix]]
| |
| − | * [[Heat/VPC Resources Support|VPC Resources Support]]
| |
| − | * [https://wiki.openstack.org/w/index.php?title=Special%3APrefixIndex&prefix=Heat&namespace=0 All topics in the Heat Wiki Namespace]
| |
| − | | |
| − | == [https://review.openstack.org/#/admin/groups/114,members heat-core] Blogs & Presentation Material ==
| |
| − | * Steve Baker [http://blog.stevebaker.org/ Blog]
| |
| − | * Zane Bitter [http://www.zerobanana.com/tags/OpenStack Blog] & [https://github.com/zaneb/presentations/releases Presentation Material]
| |
| − | * Steve Dake [https://sdake.wordpress.com/ Blog] & [https://github.com/sdake/slides Presentation Material]
| |
| − | * Steve Hardy [https://hardysteven.blogspot.co.uk/ Blog] & [https://github.com/hardys/presentations Presentation Material]
| |
| − | * Angus Salkeld [http://ahsalkeld.wordpress.com/ Blog]
| |
| | | | |
| | = Get involved = | | = Get involved = |
| | == IRC == | | == IRC == |
| | | | |
| − | The developers use IRC in <code>#heat</code> on [http://freenode.net/ Freenode] for development discussion. | + | The developers use IRC in <code>#murano-open-paas</code> on [http://freenode.net/ Freenode] for development discussion. |
| | | | |
| | == Meetings == | | == Meetings == |
| | | | |
| − | Meetings are held on IRC in <code>#openstack-meeting</code> on [http://freenode.net/ Freenode]. See the [http://wiki.openstack.org/Meetings/HeatAgenda Heat agenda page] for times and details.
| + | Currently project has not regular IRC meetings |
| | | | |
| | == Mailing list == | | == Mailing list == |
| | | | |
| − | Discussions about Heat happens on the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev openstack-dev] mailing list. Please use the tag <code>[Heat]</code> in the subject line for new threads. | + | Discussions about Open PaaS happens on the [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev openstack-dev] mailing list. Please use the tag <code>[Murano-Open-PaaS]</code> in the subject line for new threads. |
Murano Open PaaS is a collection of Murano application, which allows to provide fast and clear solution for deploying PaaS. It contains such applications like: Gerrit, Jenkins, Zuul, etc.
These application can be installed as one Meta application, which is consisted of all necessary applications. Also It can be independent application, if user want to use his own Jenkins ans wants to install only Gerrit application.
Obviously it provides flexible solution for user clouds and can be easily re-used as much as user want.
