View source for stoney conductor: Lean Provisioning

This page describes how the '''stoney conductor Lean Provisioning''' works.

= Work Flow =
# Create the '''Virtual Machine Profile''':
## Step I: Select a '''Base Profile'''
## Step II: Set the '''Profile Meta Data''':
##: Set the '''Profile ISO File''': <font color="green">Fedora-18-x86_64-netinst.iso</font> or <font color="green">Gentoo_Linux_2013.0.iso</font>
##: Set the '''Profile Name''': <font color="green">Fedora Linux 18 64-Bit Profile</font> or <font color="green">Gentoo Linux 2013.0  64-Bit Profile</font>
##: Set the '''Profile Description''': <font color="green">Fedora Linux 18 64-Bit Profile</font> or <font color="green">Gentoo Linux 2013.0  64-Bit Profile</font>
##: Display the '''Profile Operating System''': <font color="green">Linux</font> or <font color="green">Windows</font> (read only, this information is available from Step I)
##: Set the '''Profile Operating System Type''': <font color="green">Fedora</font>, <font color="green">Gentoo</font> or <font color="green">Server 2008 R2</font>
##: Set the '''Profile Operating System Version''': <font color="green">18</font> (Linux Fedora), <font color="green">2013.0</font> (Linux Gentoo) or <font color="green">Standard</font> (Windows Server 2008 R2)
##: Set the '''Profile Memory''': <font color="green">1 Gigabyte</font>
##: Set the '''Profile Disk Size''': <font color="green">30 Gigabyte</font>
##: Set the '''Profile CPU number(s)''': <font color="green">1</font>
##: Set the '''Profile Clock Offset''': <font color="green">utc</font>
# Create the '''Virtual Machine Template''':
## Step I: Select a '''Profile'''
## Step II: Set the '''Virtual Machine Data''':
##: Set the '''Virtual Machine Pool''': <font color="green">vm-template-virtual-machine-pool-01</font>
##: Set the '''Virtual Machine Node''': <font color="green">foss-cloud-node-01.stepping-stone.ch</font>
##: Display the '''Virtual Machine Name''': <font color="green">kvm-0001.stepping-stone.ch</font> (read only, created by the vm-manager)
##: Set the '''Virtual Machine Description''': <font color="green">Gentoo Linux 2013.0 Template</font>
##: Display the '''Virtual Machine Operating System''': <font color="green">Linux</font> (read only, taken from the virtual machine profile)
##: Display the '''Virtual Machine Operating System Type''': <font color="green">Gentoo</font> (read only, taken from the virtual machine profile)
##: Display the '''Virtual Machine Operating System Version''': <font color="green">2013.0</font> (read only, taken from the virtual machine profile)
##: Set the '''Virtual Machine Memory''': <font color="green">1 Gigabyte</font>
##: Set the '''Virtual Machine Disk Size''': <font color="green">30 Gigabyte</font>
##: Set the '''Virtual Machine CPU number(s)''': <font color="green">1</font>
##: Set the '''Virtual Machine Clock Offset''': <font color="green">utc</font>
# Install the '''Virtual Machine Template''' with the chosen operating system.
#: The administrator can now install the operating system on the virtual machine template.
#: As the last step, the administrator executes the sysprep script in the virtual machine template (this makes sure, that virtual machine template is in a sane state and is shut down).
#: The administrator releases the freshly installed virtual machine template in the vm-manager: <font color="green">ready for use</font>
# Create the '''Persistent Virtual Machine''':
#: Choose the '''Persistent Virtual Machine Pool''': <font color="green">persistent-virtual-machine-pool-01</font>
#: Choose the '''Virtual Machine Node''': <font color="green">foss-cloud-node-02.stepping-stone.ch</font> (this choice depends on the Persistent Virtual Machine Pool)
#: Display the '''Persistent Virtual Machine Name''': <font color="green">kvm-0002.stepping-stone.ch</font> (read only, created by the vm-manager)
#: Set the '''Virtual Machine Description''': <font color="green">Django Server for Customers</font>
#: Set the '''Persistent Virtual Machine Type''': <font color="green">Server</font>
#: Choose the '''Software Stack''': <font color="green">Django (Version 1)</font> or <font color="green">Django (Version 2)</font> (display this field only if one or more software stacks relevant for the chosen operating system, type and version exist, otherwise disable (grey listing))
#: Choose the '''Persistent Virtual Machine Environment''': <font color="green">Test</font>, <font color="green">Development</font> or <font color="green">Production</font> (display this field only if one or more environments exist for the chosen software stack, otherwise disable (grey listing))

= On the technical side =
== Creation of a virtual machine template ==
The attribute '''sstVirtualMachineMode''' must be set to '''first installation''' during the creation of the virtual machine template.

== Releasing a virtual machine template ==
The user must release the virtual machine template:
* This is done by setting the attribute <code>sstVirtualMachineMode</code> from '''first installation''' to '''ready for use'''

Possible values for the <code>sstVirtualMachineMode</code> attribute are:
* '''do not use''': virtual machines can not be created from this virtual machine template. Meaning an undefined state and the administrator must look into the situation.
* '''maintenance mode''': virtual machines can not be created from this virtual machine template. This mode is used to update the virtual machine template.
* '''first installation''': virtual machines can not be created from this virtual machine template, this is the default mode after a fresh virtual machine template creation.
* '''ready for use''': the administrator can not start this virtual machine. If he wants to start the virtual machine template, he must set the mode to '''maintenance mode'''.
If the <code>sstVirtualMachineMode</code> attribute does not exist, this must have the same meaning as '''do not use'''. To achieve a '''self healing''' effect, the [[VM-Manager]] must set <code>sstVirtualMachineMode</code> to '''do not use'''.

== Further reading ==
* Possible operating system choices are stored in the OpenLDAP directory: [[stoney_core:_OpenLDAP_directory_data_organisation#Operating_System | Operating System]].
* Possible software stack choices are stored in the OpenLDAP directory: [[stoney_core:_OpenLDAP_directory_data_organisation#Software_Stack | Software Stack]].
* A [[stoney_conductor:_OpenLDAP_directory_data_organisation#Virtual_Machine:_Operating_System | Virtual Machine Operating System]] example.
* A [[stoney_conductor:_OpenLDAP_directory_data_organisation#Virtual_Machine:_Software_Stack | Virtual Machine Software Stack]] example.

== Notes / Questions ==
Do we make a difference between the first installation and the recurring updates (maintenance)? This question is interesting for providers who want to install a virtual machine automatically, but do not want to be in charge of the recurring updates.

Possible options are:
* Installation through Puppet (no maintenance): initial set up fee, no recurring costs.
* Installation through Puppet (with maintenance): no initial set up fee, with recurring costs.

= Links =

[[Category:stoney conductor]][[Category:Lean Provisioning]]