RETIRED, Heat salt formula
Go to file
Simon Pasquier 1eb7c8d09c Fix notification configuration
The 'notification_driver' parameter was set to
oslo.messaging.notifier.Notifier which isn't supported anymore for
Liberty and Mitaka. Also the configuration files for these 2 releases
didn't honor the server.notification flag.

Change-Id: I77ae4ea18c87cf93a8d5fee4c492a345833fa004
2016-12-14 15:35:25 +01:00
_modules Initial commit 2015-10-06 16:40:56 +02:00
_states Initial commit 2015-10-06 16:40:56 +02:00
doc/source Add doc dir 2016-01-26 11:59:31 +01:00
heat Fix notification configuration 2016-12-14 15:35:25 +01:00
metadata/service Merge remote-tracking branch 'upstream/master' into merge-branch 2016-11-18 11:46:59 +01:00
tests Merge "Revert "introduce test-kitchen"" 2016-09-20 14:21:36 +00:00
.gitignore add testing/add heat-stack-domain to metadata 2016-01-25 22:22:46 +01:00
.gitreview License and links fixes 2016-02-04 14:13:16 +01:00
CHANGELOG.rst New release, debian packaging moved 2016-04-19 09:12:05 +02:00
FORMULA SPM packaging metadata 2016-06-15 18:44:17 +02:00
LICENSE License and links fixes 2016-02-04 14:13:16 +01:00
Makefile Revert "introduce test-kitchen" 2016-09-20 13:54:11 +00:00
README.rst Revert "introduce test-kitchen" 2016-09-20 13:54:11 +00:00
VERSION New release, debian packaging moved 2016-04-19 09:12:05 +02:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 21:16:05 +02:00
metadata.yml New release, debian packaging moved 2016-04-19 09:12:05 +02:00

README.rst

Heat

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 AWS CloudFormation template format, so that many existing CloudFormation templates can be launched on OpenStack. Heat provides both an OpenStack-native ReST API and a CloudFormation-compatible Query API.

Sample pillars

Single Heat services on the controller node

heat:
  server:
    enabled: true
    version: icehouse
    region: RegionOne
    bind:
      metadata:
        address: 10.0.106.10
        port: 8000
      waitcondition:
        address: 10.0.106.10
        port: 8000
      watch:
        address: 10.0.106.10
        port: 8003
    cloudwatch:
      host: 10.0.106.20
    api:
      host: 10.0.106.20
    api_cfn:
      host: 10.0.106.20
    database:
      engine: mysql
      host: 10.0.106.20
      port: 3306
      name: heat
      user: heat
      password: password
    identity:
      engine: keystone
      host: 10.0.106.20
      port: 35357
      tenant: service
      user: heat
      password: password
    message_queue:
      engine: rabbitmq
      host: 10.0.106.20
      port: 5672
      user: openstack
      password: password
      virtual_host: '/openstack'
      ha_queues: True

Heat client with specified git templates

heat:
  client:
    enabled: true
    source:
      engine: git
      address: git@repo.domain.com/heat-templates.git
      revision: master

Heat system definition of several stacks/systems

heat:
  control:
    enabled: true
    system:
      web_production:
        format: hot
        template_file: /srv/heat/template/web_cluster.hot
        environment: /srv/heat/env/web_cluster/prd.env
      web_staging:
        format: hot
        template_file: /srv/heat/template/web_cluster.hot
        environment: /srv/heat/env/web_cluster/stg.env

Ceilometer notification

heat:
  server:
    enabled: true
    version: icehouse
    notification: true

Client-side RabbitMQ HA setup

heat:
  server:
    ....
    message_queue:
      engine: rabbitmq
      members:
        - host: 10.0.16.1
        - host: 10.0.16.2
        - host: 10.0.16.3
      user: openstack
      password: pwd
      virtual_host: '/openstack'
    ....

Usage

Install Contrail Heat plugin for additional resources

pip install git+https://github.com/Juniper/contrail-heat.git@R1.30

Things to improve

Documentation and Bugs

To learn how to deploy OpenStack Salt, consult the documentation available online at:

https://wiki.openstack.org/wiki/OpenStackSalt

In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:

http://bugs.launchpad.net/openstack-salt

Developers wishing to work on the OpenStack Salt project should always base their work on the latest formulas code, available from the master GIT repository at:

https://git.openstack.org/cgit/openstack/salt-formula-heat

Developers should also join the discussion on the IRC list, at:

https://wiki.openstack.org/wiki/Meetings/openstack-salt