Opened 5 years ago
Last modified 5 years ago
#6082 new task
Cloud resource keys
Reported by: | minondoa | Owned by: | minondoa |
---|---|---|---|
Priority: | major | Milestone: | DRM4G-X.X.X |
Component: | DRM4G | Keywords: | drm4g, configuration, cloud, setup, keys, resources |
Cc: | antonio, carlos |
Description
Here are listed all the changes that we decided to make in the Meeting 2016-12-14
- in resources.conf change “cloud” to “cloud_provider” (ticket #6056)
- change the key “nodes” to “instances”, as in the number of instances (VMs) that will be created
- add a new value for the key “vm_communicartor” called “pk_ssh” (ticket #6051)
- we will consider changing the names for the keys “vm_communicator” to something that will reflect that it will be used for creating cloud resources
- remove the "fedcloud" value from the lrms
- instead of "fedcloud", to encompass all of the clouds that use the rOCCI API, it's now going to be called "rocci", since the implementation would be the same
- add a new key called "cloud_connector" - depending on what protocol the cloud, the user chose, will be using the possible values will be:
- “rocci”
- “ec2” - “cloud_auth” is always “basic” (by default)
Depending on the cloud's protocol, some new keys will have to be added.
Values when using "rocci":
- “cloud_auth” - this will indicate what type of authentication the user will be using to access the cloud services. Its possible values will be:
- “x509” - the user will use a x509 proxy certificate to identify himself
- the user will have to run the command “drm4g id <resource_name>” init”
- the user can specify the key “myproxy_server” if he knows what he's doing, but it won't be necessary since it's value will be set to “myproxy1.egee.cesnet.cz” by default
- “x509” - the user will use a x509 proxy certificate to identify himself
- “basic” - the user will use a previously created account to identify himself. In this case, two more keys will have to be specified:
- “access_key” and “secret_key” (so the user must have an account with the provider he wishes to use)
Values when using "ec2":
- add a key called “billing” - to define what type of payment method you'll be using
- “on-demand”
- “on-spot”
- “on-reserved”
- we will try to get the information about the billing prices depending on what the user wants
- add a key called “region”
- its values will be the same as the ones found in the Amazon Web Services web page
Change History (6)
comment:1 Changed 5 years ago by minondoa
comment:2 Changed 5 years ago by minondoa
The resource configuration key "cloud" has been changed to "cloud_provider".
comment:3 Changed 5 years ago by minondoa
The resource configuration key "nodes" has been changed to "instances".
comment:4 Changed 5 years ago by minondoa
The DRM4G package "fedcloud" has been renamed to "rocci".
comment:5 Changed 5 years ago by minondoa
The library Libcloud is going to be used to manage all cloud resources.
comment:6 Changed 5 years ago by minondoa
The resource configuration key "ssh" has been restored. The key "pk_ssh" still works as well.
Note: See
TracTickets for help on using
tickets.
The resource configuration key "ssh" has been changed to "pk_ssh".
The resource configuration key "ssh" should be restored. The key "pk_ssh" could also be added.