Changes between Version 10 and Version 11 of DRM4G/ResourceConfiguration

Ignore:
Timestamp:
Dec 1, 2016 8:26:10 PM (5 years ago)
Comment:

--

Legend:

Unmodified
 v10 '''!FedCloud''' resources are a bit different than the rest. They are not considered to be ''hosts'' so they won't be listed when using the command drm4g host and therefore won't be used to execute jobs. Their only function is to connect to a machine with a cloud proxy certificate ('''X.509 certificates''') capable of giving you access to cloud resources. * vm_communicator:  or  authentication type for the created VMs : - local:       The resource will be accessed directly. * vm_communicator:  or  authentication type for the created VMs : - ssh:         The resource will be accessed through ssh's protocol via Paramiko's API. - op_ssh:      The resource will be accessed through OpenSSH's CLI. Where and how to get the correct values for your cloud configuration file as well as a more in depth explanation of some of these configuration keys can be found in the section [./EGIFedCloud How to configure an EGI FedCloud VM]. ---- A few extra things to take into consideration: * If no vm_communicator is specified, the one in communicator will be used, but if it's set to local, the DRM4G will set it to ssh. * The private key used to access the ''VM'' will be the same as the one used to access the machine that will create it. * So even if you're going to use your local machine to create the VM, you'll have to specify a private_key. == Examples ==