Federated Cloud OCCI to IM Migration
Overview | For users | For resource providers | Infrastructure status | Site-specific configuration | Architecture |
This page gives instructions on how to migrate from OCCI to IM for using EGI FedCloud resources
Setup of IM
Getting information about available images/flavors
While OCCI had the possibility to query the mixins at the site, the returned information is limited and does not include the needed details to determine which mixing is relevant for a given application. IM does not provide a way to query the images or flavors at the site, instead you should use AppDB, either via the browser or using AppDB IS APIs, to discover site capabilities.
Creating a VM
Creation of a VM using OCCI requires a PUT
request to the /compute
URL of the service with the right templates as mixins and a title. With IM you need to define a RADL description of the VM that includes similar information. See the comparison below:
OCCI | IM |
---|---|
occi --endpoint <ENDPOINT> --auth x509 --user-cred $X509_USER_PROXY --voms \ --action create --resource compute --attribute occi.core.title="<TITLE>" \ --mixin <OS_TPL> --mixin <RES_TPL> |
network public (outbound = 'yes' ) system vm ( instance_type = '<RES_TPL>' and net_interface.0.connection = 'public' and net_interface.0.dns_name = '<TITLE>' and disk.0.os.name = 'linux' and disk.0.image.url= ['<ENDPOINT>/<OS_TPL>'] and disk.0.os.credentials.username = 'cloudadm' ) deploy vm 1; |
IM uses RADL language to describe resources. Gi