This page provides specific information about Grid'5000 for Fed4FIRE users.
- 1 Current Status (April 2020)
- 2 Technical detail
- 3 Grid'5000 Accounts
- 4 Contact information
- 5 FAQ
- 5.1 Limits for the duration of an experiment?
- 5.2 Accessing your Grid'5000 homedirs
- 5.3 SSH keys
- 5.4 Adding your certificate key as SSH keys
- 5.5 Adding your ssh key to jFed
- 5.6 Grid'5000 Account Management
- 5.7 Sharing one user account per experiment?
- 5.8 Fed4FIRE experiment sharing and SSH key injection
- 5.9 Public IP Address for Grid'5000 nodes?
Current Status (April 2020)
The Grid'5000 Aggregate Manager (AM) will soon be added to Fed4FIRE's jFed suite. Although integration is not complete yet this will allow users to perform basic tasks using only Fed4FIRE-standard APIs.
- The Grid'5000 Aggregate Manager (am.grid5000.fr) advertises Grid'5000 resources
- Fed4FIRE users can allocate and provision Grid'5000 resources from the Aggregate Manager, using the AMv3 API.
- New Grid'5000 accounts are automatically created by the AM for new users for 1 month. After which Fed4FIRE users will need to complete their account to regain access (see Extending a valid or expired account).
- Fed4FIRE users can login to Grid'5000 frontends and to provisioned resources via SSH using their Fed4FIRE certificate private key.
- Network-level functions, such as internal and external vlans, are not yet available through the AM and require using the Grid'5000 tools. See KaVLAN
- Network-level interconnection using dedicated links with other Fed4FIRE testbed is functional. See Fed4FIRE_VLAN_Stitching. Network interconnection over the public Internet is functional (Grid'5000 nodes can access the public internet).
- Aggregate Manager
- Address: am.grid5000.fr
- Port: 443
- Component managers:
Access to any Grid'5000 resources requires a Grid'5000 account.
Linking Fed4FIRE identity to existing Grid'5000 accounts
Grid'5000 users who already have an account can link it to their Fed4FIRE identity from their account management page:
- go to the External identifiers and press the Add new identifier button,
- select Fed4FIRE as External engine and your Fed4FIRE URN as External identifier.
The Fed4FIRE URN can be found in jFed tools once logged in, or by parsing the Fed4FIRE user certificate using openssl. Please not that for preexisting Grid'5000 account the AM will not add new ssh keys to your account. Users should feel free to add their certificate key as an ssh key to their Grid'5000 account or add their ssh key to jFed experimenter.
Fed4FIRE users without a existing Grid'5000, or that fail to link their existing Grid'5000 account, will have a new one created for them the first time they allocate resources. These new accounts are be valid for a single month. Three emails will inform you of you account's expiry:
- one week before the account's expiry
- on the day of the account's expiry
- on the day of the account's is retired, 1 week after expiry
Extending a valid or expired account Grid'5000 account, created automatically for a Fed4FIRE user
Users are welcomed to request an account extension. To do so:
- Go to Grid'5000 password reset page to create a password for your account.
- Please note that (re)setting your password requires you to input the email associated with your account, which will be the one provided by the Fed4FIRE federation and not your institutional email.
- Login to the account management page.
- Complete your information :
- Use the Action buttons to Edit your Account and Affiliation
- - In the account section you will be asked to provide your name and, if you so wish, your institutional email address.
- - In the affiliation section you will be asked about your work and employer, as well as your intended usage for Grid'5000
- Request access by going to the Groups tab and using the Join a new group button.
- Join the open-access group.
- Your request will be checked by the group manager based on your account and affiliation information, so fill them as correctly.
- INRIA members can try to join a group relevant to their research teams instead of open-access.
- Do NOT request an extension within the Fed4FIRE access group. It will not be granted.
Extending a closed account, created automatically for a Fed4FIRE user
Account that have been expired for more than one week are retired automatically.
Retired accounts can not be accessed from the account management interface and need to be reopened by Grid'5000 staff.
To reopen a closed account you will need to mail the support staff at support-staff @ lists.grid5000.fr.
- Fed4FIRE contact points for Grid'5000:
- Lucas Nussbaum (email@example.com)
- David Margery (firstname.lastname@example.org)
- Luke Bertot (email@example.com)
- Grid'5000 support staff: see the Support page
Limits for the duration of an experiment?
If experiment means project, there is no limit. Accounts are created with a short-term expiration date (one month or two months depending on the process used for account creation) but can be extended at will.
If experiment means resources reservation, the limits are described in the Grid'5000 Usage Policy. The philosophy behind the Usage Policy is that users should be able to find some resources to prepare experiments during the day, and then reserve resources in advance to do large-scale experiments during nights and week-ends. So the effective limits are 10 hours during the day (9h-19h), 14 hours during nights (19h-9h), and 62 hours during week-ends (Friday 19h -> Monday 9h). Users are therefore strongly encouraged to automate the setup of their experiments (using scripts or tools such as Ansible). If an experiment requires a longer reservation, a special request can be made, as described in the Grid'5000 Usage Policy.
Accessing your Grid'5000 homedirs
Grid'5000 provides home directories on every site of the testbed with ssh access. This access requires connecting through ssh gateways as described on this page.
By default accounts created though through tools such as jFed, the ssh key of the account is derived from the user's federation certificate. To connect users must provide the certificate to the ssh client as the identity file.
Users can add additional keys using the Grid'5000 account management interface. These keys will be used to connect to access gateways and nodes.
Adding your certificate key as SSH keys
By default jFed tools will try to connect to nodes using your user certificate key. For this reason the Grid'5000 AM will add this ssh key to all new account it creates, and will update your key every-time your certificate changes. Users who use a pre-existing Grid'5000 account do not benefit from this feature by default. And can instead opt to add their usual ssh-key to jFed.
Users wanting to use their certficate key with ssh can use
ssh-keygen -y -f <path/to/certificate> to derive an ssh public key from their PEM certificate.
Users wanting to benefit from the AM's automatic key update feature should append the
encoded by users-api-ror from rsa cert comment that the end of their key line.
The final result should look like :
ssh-rsa AAAAB3Nyc2EADAQzaC1ABAAAA[...]+sw== encoded by users-api-ror from rsa cert
Adding your ssh key to jFed
By default jFed tools will try to connect to nodes using your user certificate key. Users can if they so wish add an other ssh key to try during ssh connections.
Ssh keys are added in
Preference > SSH Authentication section.
However at the time of writing jFed Experimenter does not recognize the latest openssh prive key format, starting with
-----BEGIN OPENSSH PRIVATE KEY-----.
If you have such a key you can work around the problem by:
- making a copy of your private key
ssh-keygen -p -m PEM -f </path/to/key/copy>
- the command will prompt you for a new password, you are free to reuse the same password or leave the field blank for no password
- the copy should not have the key in the PEM format, starting with
-----BEGIN RSA PRIVATE KEY-----
The copy will now work with jFed.
Grid'5000 Account Management
Grid'5000 keeps user accounts linked to your Fed4FIRE identity. These account will be automatically generated when you first attempt a node allocation for a duration of 1 month. To access Grid'5000's account management interface you will first need to set a Grid'5000 password.
- Resetting your password:
- Go To Special:G5KChangePassword
- You will need to use the email address included in the Fed4FIRE user certificate.
- Accessing your account
- Go to UMS
- From here you can:
- Add new ssh keys to your account.
- Update your affiliation information
- Request account extentions
Sharing one user account per experiment?
Even if several persons are going to collaborate on the same experiment, we strongly prefer that each person uses its own account, for traceability purposes. It is possible to share scripts etc using standard Unix mechanisms (directory permissions), or using an external Git service (which are accessible from Grid'5000 nodes).
Fed4FIRE experiment sharing and SSH key injection
It is possible to share experiments using the corresponding options in jFed. It is also possible to add SSH keys to nodes at provisioning time using the ̀ geni_users` option. However the Grid'5000 has multiple caveats:
- The new ssh keys are only installed on the provisioned node and not on the ssh access gateways. Only keys registered with your account before can be used on the access gateway. Keys registered with your account are always loaded into provisioned nodes.
- To grant access to other users they will need a Grid'5000 account to connect to the access gateway. Like with all other Fed4FIRE users this account can be created by connecting to the Aggregate Manager using the Allocate or Describe calls.
- If you grant another user access to one of the nodes you have allocated, they will gain Read/Write access to your Grid'5000 homedir for the duration of the experiment.
Public IP Address for Grid'5000 nodes?
Grid'5000 nodes are on a private network. Interconnection to the Internet is achieved to a NAT, using a 10 Gbps link to RENATER (the french NREN).
We are in the process of:
- Adding public IPv6 addresses to nodes
- Adding a configurable firewall to allow reaching Grid'5000 nodes from the Internet using IPv6
- Extending this to a set of IPv4 addresses (probably doing NAT from the public IPv4 address to the internal IPv4 addresses)
However, this is still work in progress.