Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Federated Cloud OCCI to IM Migration

From EGIWiki
Revision as of 15:43, 20 June 2018 by Enolfc (talk | contribs)
Jump to navigation Jump to search
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 [[HOWTO11#How_to_list_the_OS_templates_.28aka_VM_Images.29_in_a_site|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

Command Line Interface