OCCI Support (experimental)
Roboconf has a target implementation for OCCI (currently experimental, developed under the hood of OCCIWare R&D project).
It supports the creation of VMs, starting from a VM image, and is under developments with tests on top of VMWare and ActiveEon IaaS, and backed by a Erocci OCCI server.
To install the OCCI target, open the DM’s interactive mode and use one of the following options.
With the roboconf:target command:
# The version will be deduced automatically by the DM
roboconf:target occi
Or with the native Karaf commands:
# Here in version 0.9
bundle:install --start mvn:net.roboconf/roboconf-target-iaas-occi/0.9
Sample target.properties.
Just copy / paste and edit.
# Configuration file for OCCI
handler = iaas-occi
id = a unique identifier
name =
description =
# OCCI server location
occi.serverIpPort = 172.16.225.91:8080
occi.image = RoboconfAgentImageName
occi.title = occiware test
occi.summary = test for occiware
# Credentials to connect (if any)
occi.user =
occi.password =
Here is a complete description of the parameters for OCCI.
| Property | Description | Default | Mandatory |
|---|---|---|---|
| handler | Determines the target handler to use | none, must be “iaas-occi” | yes |
| id | A unique identifier for the target properties. | - | yes |
| name | A human-readable name for the target | - | no |
| description | A description of the target. | - | no |
| occi.serverIpPort | The URL to interact with VMWare’s manager. | none | yes |
| occi.user | The user name to connect. | none | no |
| occi.password | The user password to connect. | none | no |
| occi.image | The image to use to create the VM. | none | yes |
| occi.title | A title for the VM. | Roboconf | no |
| occi.summary | A readable summary for the VM. | Generated by Roboconf | no |