You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: coldfront/README.md
+33-30Lines changed: 33 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
- View `hpc-toolset-tutorial/coldfront/coldfront-nginx.conf` for an example of ColdFront web configuration
6
6
7
7
8
-
## Login to ColdFront website
8
+
###Login to ColdFront, setup account permissions & create resource
9
9
URL https://localhost:2443/
10
10
You'll need to login as some of the users for this tutorial to get things started. Do NOT use the OpenID Connect login option at this point.
11
11
- Login locally as username `hpcadmin` password: `ilovelinux`
@@ -39,17 +39,22 @@ Ensure that the following are checked: `Is available`, `Is public`, `Is allocat
39
39
Under the resource attributes section, click `Add another Resource attribute` and select `slurm_cluster` from the drop down menu. In the `value` field, enter `hpc`
40
40
Click `Add another Resource attribute` and select `OnDemand` from the drop down menu. In the `value` field, enter `Yes`
41
41
- Then click SAVE
42
+
**See more info on the OnDemand plugin at the end**
43
+
44
+
Make an allocation attribute changeable:
45
+
- Under the `Allocation` section, click on `Allocation Attribute Types` Click on `slurm_account_name` check the box next to `Is changeable` and then click the SAVE button.
42
46
- Logout
43
-
**See below for more info on the OnDemand plugin at the end**
44
47
45
-
Request an allocation for the new resource as the PI user:
48
+
### Create a project & request an allocation
49
+
As the PI user: Request an allocation for the new resource:
46
50
- Login as the PI using local account username: `cgray` password: `test123`
47
-
-Create a new project, filling in the name, description, and selecting any field of science
48
-
-Request an allocation for resource: hpc
49
-
- Add a user to the project - search for `csimmons` and add to the HPC cluster allocation
51
+
-Click the `Add a project` button to reate a new project, filling in the name, description, and selecting any field of science
52
+
-Once redirected to the project detail page, request an allocation by clicking on the `Request Resource Allocation` button. Select the `hpc` resource from the drop down menu, provide any justification, and click the `Submit` button
53
+
-Click the `Add Users` button to add a user to the project - search for `csimmons`, select the HPC cluster allocation, check the box next to the username, and click the `Add Selected Users to Project`
50
54
- Logout
51
55
52
-
Activate and setup the new allocation:
56
+
### Activate the allocation request
57
+
As the HPC admin user, activate and setup the new allocation:
53
58
- Login using local account username: `hpcadmin` password: `ilovelinux`
54
59
- Navigate to the `Admin` menu and click on `Allocation Requests`
55
60
- Click on the `Detail` button to configure and activate the allocation:
@@ -60,7 +65,7 @@ click the `Add Allocation Attribute` button and select these allocation attribut
60
65
Set the status to `Active`, set the start date to today, and set the expiration date to the end of this month (you'll see why later)
61
66
Click the `Update` button
62
67
63
-
## Login to OnDemand website
68
+
###Login to OnDemand & test interactive app
64
69
- Login to Open OnDemand https://localhost:3443/ as username: `cgray` password: `test123`
65
70
- Click on the `Interactive Apps` menu and click on `HPC Desktop`
66
71
- Try to launch an interactive Job by clicking on the `Launch` button
@@ -69,7 +74,7 @@ You will get an error message that you do not have permission to run on the clus
69
74
This is because we have not synced the allocation information in ColdFront with Slurm yet.
70
75
71
76
72
-
## Run Slurm plugin to sync active allocations from ColdFront to Slurm
77
+
###Run Slurm plugin to sync active allocations from ColdFront to Slurm
73
78
- Login to the frontend container first, then to the coldfront container:
74
79
`ssh -p 6222 hpcadmin@localhost`
75
80
password: `ilovelinux`
@@ -99,7 +104,7 @@ NOTE: The csimmons user is under the cgray slurm account
99
104
`exit`
100
105
101
106
102
-
## Login (or go back) to frontend container
107
+
###Login (or go back) to frontend container
103
108
NOTE: you should already be on the frontend but just in case you're not:
104
109
`ssh -p 6222 hpcadmin@localhost`
105
110
password: `ilovelinux`
@@ -113,52 +118,50 @@ password: `test123`
113
118
`exit` (logout from cgray account)
114
119
115
120
116
-
##Login to OnDemand website
121
+
### Try interactive app in OnDemand again
117
122
- Login back into or refresh your login to Open OnDemand https://localhost:3443/ as username: `cgray` password: `test123`
118
123
- Try to launch an interactive job again. Does it work this time?
119
124
- Go to the `Jobs` menu and click `Active Jobs` and click on your running jobs to see more details
120
125
- Delete (cancel) the jobs so they show the `completed` status
When the project review functionality is enabled (it is by default) a PI will be forced to review their project once every 365 days. To change this time frame, edit the default in `coldfront.env` We can force a project to be under review in less than a year which is what we'll do for the cgray project.
125
130
126
131
Login as `hpcadmin` password `ilovelinux`
127
132
Navigate to the `Admin` menu and click on the `ColdFront Administration` link. Scroll to the `Project` section and click on `Projects` Then click on the project that we created earlier. Check the box next to `Force Review`
128
133
NOTE: If there is a project you never want project reviews on, uncheck 'Requires review'
129
134
130
-
Logout as `hpcadmin` and login as `cgray` password `test123` and notice the warning banner. Click on the allocation and try to renew it. You should see a warning banner telling you it can't be done because the project review is due. When a project review is required, a PI can't request new allocations or renew expiring allocations. They can, however, add/remove users, publications, grants, and research output. Click on the `renew now` link for the allocation to test this out.
131
-
132
-
Click the `Review Project` link. Provide a reason for not providing grant or publication information, check the box to acknowledge the update and click the Submit button. Now try to renew the expiring allocation.
133
-
134
-
Log out as `cgray`
135
+
- Logout as `hpcadmin` and login as `cgray` password `test123` and notice the `Needs Review` label next to the project. Click on the allocation and try to renew it. You should see a warning banner telling you it can't be done because the project review is due. When a project review is required, a PI can't request new allocations or allocation change requests nor renew expiring allocations. They can, however, add/remove users, publications, grants, and research output. Click on the `renew now` link for the allocation to test this out.
135
136
137
+
- Click the `Review Project` link. Provide a reason for not providing grant or publication information, check the box to acknowledge the update and click the Submit button. Now try to renew the expiring allocation.
136
138
137
-
## Allocation Change Requests
138
-
Allocation change requests are turned on by default. This will allow PIs to request date extensions for their allocations. The date ranges default to 30, 60, & 90 days but can be set changed or disabled completely in `hpc-toolset-tutorial/coldfront/coldfront.env`
139
-
See https://coldfront.readthedocs.io/en/latest/config/#coldfront-core-settings for more information.
139
+
- Click on the allocation `RENEWAL REQUESTED` button or navigate to the Allocation Detail page through the project. Click on the `Request Change` button, select a date extension, enter a new slurm account and provide a justification. Then click the `SUBMIT` button. Logout.
140
140
141
-
If you want PIs to be able to request changes to allocation attributes (i.e. storage quotas, unix group) this needs to be set on the allocation attribute. For this demo, we will allow the PI to request changes on the `slurm_account` attribute.
142
-
- Login as `hpcadmin` password `ilovelinux`
143
-
- Navigate to the `Admin` menu and click on the `ColdFront Administration` link. Under the `Allocation` section, click on `Allocation Attribute Types` Click on `slurm_account_name` check the box next to `Is changeable` and then click the SAVE button. Logout.
144
-
- Login as `cgray` password `test123`
145
-
- Click on the allocation `RENEWAL REQUESTED` button or navigate to the Allocation Detail page through the project. Click on the `Request Change` button, select a date extension, enter a new slurm account and provide a justification. Then click the `SUBMIT` button. Logout.
146
141
- Login as `hpcadmin` password `ilovelinux`
147
142
- Go to the `Admin` menu and click on `Allocation Change Requests`
148
143
- As the admin you have the ability to approve the date extension, change it to another setting or select `no extension` You can remove the `slurm_account_name` request or change it. You can add notes for the PI and users on the allocation to see. Then you can take action such as `Approve` or `Deny` the request. For this demo, let's click the `Approve` button.
149
144
- Next review the pending allocation requests. Navigate to the `Admin` menu and click on `Allocation Requests` Note that the project review status is pending.
150
-
- Click on the `Admin` menu and click on `Pending project reviews`.
145
+
- Logout as the `hpcadmin` user
146
+
**See more info on allocation change requests at the end**
147
+
148
+
### Center Director Role and Permissions
149
+
At the start of the tutorial we configured the user `sfoster` with the 'Staff Status' role and gave permissions to act as the Center Director. This allows `sfoster` to view all projects, allocations, publications, and grants. We've also given permission to view the pending project review list.
151
150
152
-
## Center Director Role and Permissions
153
-
At the start of the tutorial we configured the user `sfoster` with the 'Staff Status' role and gave permissions to act as the Center Director. This allows `sfoster` to view all projects, allocations, publications, and grants. We've also given permission to view the pending project review list. Login as `sfoster` password `ilovelinux` to see what additional menus and functionality this account has access to.
151
+
- Login as `sfoster` password `ilovelinux` to see what additional menus and functionality this account has access to.
154
152
155
-
Navigate to the `Staff` menu and click on `Project Reviews`
153
+
-Navigate to the `Staff` menu and click on `Project Reviews`
156
154
Click the `Email` button to see this functionality. Go back to the `Project Reviews` and click `Mark Complete`.
157
155
158
156
For more options on allowing permissions for various types of staff access, see the ColdFront manual: https://coldfront.readthedocs.io/en/latest/manual/users/
159
157
158
+
### More info on Allocation Change Requests
159
+
Allocation change requests are turned on by default. This will allow PIs to request date extensions for their allocations. The date ranges default to 30, 60, & 90 days but can be set changed or disabled completely in `hpc-toolset-tutorial/coldfront/coldfront.env`
160
+
See https://coldfront.readthedocs.io/en/latest/config/#coldfront-core-settings for more information.
161
+
162
+
If you want PIs to be able to request changes to allocation attributes (i.e. storage quotas, unix group) this needs to be set on the allocation attribute. For this demo, we allowed the PI to request changes on the `slurm_account` attribute.
160
163
161
-
##Integrating OnDemand with ColdFront
164
+
### More info on the OnDemand Plugin
162
165
This is a very simple example of modifying the ColdFront configuration to use a plugin. This plugin allows us to provide a link to our OnDemand instance for any allocations for resources that have "OnDemand enabled"
163
166
164
167
We have already added the OnDemand instance URL to the ColdFront config. You can see this outside the containers in your git directory: See `hpc-toolset-tutorial/coldfront/coldfront.env`
0 commit comments