MOC-ESI
New User Sign-up
New users must first register for an MGHPCC Account.
Next, they can access the ESI OpenStack dashboard login page and choose the OpenID Connect authentication method. Then you will be redirected to a page to select a login provider. After choosing a login method, follow the steps provided.
Note that during the first login, you will receive an error message like this: Login failed: You are not authorized for any projects or domains
. If this occurs, please contact ESI admin to add your user account to a proper project and assign roles to your account.
After your account has been properly configured, you can follow the same steps to log in and successfully authenticate, getting access to the ESI Horizon dashboard.
Accessing the CLI
Once new users have signed up using Horizon WebSSO, they can use the CLI tool to access the ESI OpenStack APIs.
Creating an Application Credential
Log in to ESI dashboard using your account credentials.
Select the project for which you want to create an application credential from the dropdown menu.
In the sidebar, navigate to Identity > Application Credentials.
Click the Create Application Credential button.
Provide a name for your credential and select all available roles. All other fields are optional.
After creation, you will be prompted to download an RC file or a clouds.yaml file. Download the file and use it to run OpenStack command-line clients. You can find more information about OpenStack Client usage here.
Installing the CLI Clients
It is recommended that you install the CLI clients within a Python virtual environment:
python3 -mvenv .venv source .venv/bin/activate
Run the following to install the needed clients:
pip install python-esiclient pip install python-esileapclient
Leasing Nodes
The MOC admins may have already granted you long-term leases on nodes. You can also obtain short-term one day leases on available nodes. To see the list, run:
openstack esi offer list
To claim an offer, run:
openstack esi offer claim <offer uuid>
Using Nodes
Please consult the New User Guide section for more information on how to configure, provision and access your leased nodes.
Node Naming Convention
Node names indicate their physical location at the MGHPCC. For example, MOC-R4PAC21U25-S1
is in Row 4, Pod A, Cabinet 21, Unit 25, Slot 1.
Contact
If you have any questions about ESI functionality, the specifications of the nodes, or anything else, please contact us in the #esi
channel within the MOC Alliance Slack.