Helion 1.1 depoly

Helion is delivered as a set of images plus a configuration utility:

Seed Cloud Image - A bootable image that is deployed into a VM
Undercloud Image - An image that is deployed by the Seed cloud onto a single physical server to create the Undercloud
Overcloud Images - Images that are deployed onto physical servers by the Undercloud. Overcloud images have specialised roles:   Mgmt., Swift, and Compute
Users are not able to (re)build the images.  Direct editing of the heat templates is possible but not supported.  Configuration is limited to those items supported by the configuration tool and Horizon.

Community Edition releases will follow the upstream Milestones (Icehouse, Juno.1, Juno,2, etc).  Not all images will change for every release; Seed and Undercloud images (being simple, single purpose systems) may remain on earlier versions.

Helion used the standard TripleO deployment model:

A seed cloud (a sealed bootable image provided as part of Helion) is deployed in a VM.  This image contains a small but operational OpenStack cloud.  The user adds a single bare-metal node to the SeedCloud and provisions it with the Undercloud Image.    This server then becomes the Undercloud.
The Undercloud image is also a complete OpenStack Cloud running on a single physical server, which will be used to deploy and update the Overcloud (the general purpose,.multi-node cloud that will host customers VMs and applications)
Physical servers are added to the Undercloud and then provisioned with Overcloud images.   Image deployment includes post-deployment configuration via Heat.