SourceForge : View Wiki Page: InfrastructureTemplates

Search Wiki Pages Project: occi-wg Wiki > InfrastructureTemplates > View Wiki Page

wiki2472: InfrastructureTemplates

Open Issues

please add if you have noted some
A Resource Template is not allowed to be related to an OCCI base type Category by the current version of Core&Models.
need to separate rendering from core
need to specify how to add boot parameters to an OS template

Infrastructure Templates

There are 2 supported infrastructural template types in OCCI.

OS Template

OCCI implementers SHOULD support this, otherwise what they provision will be merely Resources without any execution environment (e.g. operating system). Of the two supported template types, this is the most basic and necessary template category that a provider SHOULD offer. The construction of It consists of a provider specific 'scheme' and a descriptive 'title' detailing the OS. The 'term' value of the template category is a provider specific identifier that corresponds to a particular virtual machine image configuration. A provider-defined OS Template Category MUST be related to the OCCI OS Template Category defined below in order to give absolute type information. The specification of that OCCI OS Template Category is as follows:

term	scheme	title
os_tpl	scheme = 'http://schemas.ogf.org/occi/infrastructure#'	title='The base OS Template Category'

A typical example of such a category is shown below. In the example a provider has defined an OS template which offers the ability to run Ubuntu Linux upon a client's provisioned compute resource.

POST /compute
Category: compute; scheme=''; title='', ubuntu-9.10; scheme=''; title=''
Attribute: occi.compute.memory=0.5, occi.compute.cores=2

How a provider manages their set of OS templates will be determined by themselves and so provider-specific.

Resource Template

The Resource Template Category builds upon the concept of OS Templates. A Resource Template is a provider-defined category that refers to a preset resource configuration. The provider will associate a pre-determined set of Resource Attributes with a particular term identifier. A provider-defined Resource Template Category MUST be related to both the OCCI Resource Tempate Category defined below. Relating the Resource Category defining the Resource type is something that the provider must handle within their own implementation.

term	scheme	title
resource_tpl	scheme = 'http://schemas.ogf.org/occi/infrastructure#'	title='The base Resource Template Category

A typical example of such a Category's use is shown below. In this example, the provider offers Compute Resources based on different sizes (small, medium, large). Each 'size' of Compute Resource corresponds to a predetermined set of OCCI attributes. In the example below a "small" Compute Resource is provisioned. Specifying "small" corresponds to a Compute Resource Attribute set of:

Attribute: occi.compute.cores='2', occi.compute.speed='2.4', occi.compute.memory='1.0', occi.compute.arch='x86'

POST /compute
Category: compute; scheme=''; title='', small; scheme="http://provider.com/templates/compute#"; title="Small Compute Resource Instance", ubuntu-9.10; scheme=""; title=""

How a provider manages from the administrative context their set of Resource Templates will be determined by themselves and so provider-specific.

Hide Details

	Versions		Associations		Attachments		Back Links

Version	Version Comment	Created By
Version 5	removed explicit requirement for the resource template to be linked (via related) to its defining category.	Andy Edmonds - 10/07/2010
Version 4	Issue: Template Category not allowed to be related to base type Category.	Ralf Nyrén - 10/06/2010
Version 3	Define Category relationship using similar wording as in Core.	Ralf Nyrén - 10/06/2010
Version 2		Andy Edmonds - 10/05/2010
Version 1	initial content to infrastructure templates	Andy Edmonds - 10/05/2010