Add example of SoftwareDeployments with cirros

Add a really simple work-in-progress example of how
SoftwareDeployment resources could be made to work
with cirros images for test purposes.

Change-Id: I2d3b2670bd9a28dd9de714461cfe9bf132abb485
Do not install pip in heat config element

Since this element depends on os-apply-config and os-refresh-config, and
the two depends on pip-and-virtualenv. pip command has been installed in
pip-and-virtualenv.

If we install pip via install-packages here, for these images which have
no python-pip in repository, the installation will fail.

Change-Id: I4284bdd293213321751439272bad439e2a899005
Closes-Bug: #1352689
Pass signal_data to heat client as dict rather than JSON

This patch removes JSON dump operations of signal_data in
heat-config and passes signal_data to heat client as dict.
This will fix the request body lost issue which causes
output of SoftwareDeployment resources unavailable when
using HEAT_SIGNAL.

Change-Id: I24848a875405a8b89cd629a064f774b7a80d25b8
Closes-Bug: #1355692
Merge "Add example of SoftwareDeployments with cirros"
Merge "Pass signal_data to heat client as dict rather than JSON"
Added simple samples that exercise autoscaling

Added trivial templates that can be used to exercise basic
scaling group functionality: the mechanics of the scaling
actions.  These examples are deliberately spare, to
minimize dependencies.

Change-Id: Iddd63acc629d617f861215c12e20d250c53edd11
Partial-Bug: 1305425
Merge "Do not install pip in heat config element"
  New heat templates for Openshift-Origin deployment using scalability functionality

    New heat templates for Openshift-Origin deployment using scalability functionality.
    Templates are based on the Openshift-Origin template
    (https://github.com/openstack/heat-templates/tree/master/openshift-origin/F19).
    The aim is to add scalability functionality to this template. Metric use
    for the scalability are cpu_util and nbgears. This second metric is
    a custom metric implemented by a bash script calling by cron to get
    from the broker node the number of gears used and the number of node
    connected, to determine when a new node is needed. The data is send to
    the Ceilometer V2 API and used in the heat template.
    To avoid compatibility issues due to changes in this project or
    in Puppet modules it depends, versions parameters are provided in hot templates.

    I implemented 5 templates :
    aws format :
      - openshift (1 node and 1 broker)
    hot format :
      - openshift (1 node and 1 broker)
      - openshift-scalable-cpu (scalable openshift environment using cpu_util metric)
      - openshift-scalable-nbgears (scalable openshift environment using nbgears custom metric)
      - openshift-scalable-cpu-nbgears (scalable openshift environment using cpu_util metric and nbgears custom metric)

Change-Id: Idfdf158ff6176c5ef6902e27a6e764e23171cf4c
Implements: blueprint heat-openshift-templates
Add example of using native waitcondition resources

Adds a simple example of using the native WaitCondition and
WaitConditionHandle resources, which work in a similar way to
the CFN compatible ones, but with more relaxed validation of
data, and some additional helper attributes so you don't need
to remember how to write the curl call in the template unless
you need something unusual in the request.

Change-Id: I2686d07e882781e93949ded9dd260161e4514a3b
blueprint: native-waitcondition
Fix and improve autoscaling.yaml

Fixed a problem: the health monitor's delay was less than its timeout,
which is now disallowed.

Added stack outputs that show and explain the webhooks and a
ceilometer query that selects samples about VMs in the stack.
Also added an output that shows the entry IP address.

Change-Id: I11313f05d885cb0698a904f08725227b03617e0c
Merge "  New heat templates for Openshift-Origin deployment using scalability functionality"
HOT for Windows Active Directory Controller

The template deploys an Active Directory forest domain controller.

As there is the need of a Windows reboot after the install finishes,
exiting from the powershell script with the code 1001 signals to
cloudbase-init to trigger a reboot.

Change-Id: Ie171d55ffa69bb4c4f7381defd70a10d1c83213d
Co-Authored-By: Ionut Balutoiu <ibalutoiu@cloudbasesolutions.com>
Partially-Implements: blueprint windows-instances
Merge "Fix and improve autoscaling.yaml"
Merge "Add example of using native waitcondition resources"
Merge "HOT for Windows Active Directory Controller"
update autoscaling example with floating ip for lb pool

this patch updates autoscaling.yaml to (a) require an
external_network_id parameter and (b) to allocate a floating ip address
and associate it with the loadbalancer pool.

it adds a website_url output to make it consisent with some of the other
Wordpress examples.

Change-Id: I2669f51145fc6fbf20da831995acfa17e9291f66
Merge "Added simple samples that exercise autoscaling"
Merge "update autoscaling example with floating ip for lb pool"