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
+17-18Lines changed: 17 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -178,7 +178,7 @@ The tutorial database comes with two resources already created. However, when r
178
178
Still on the `ColdFront Administration` page:
179
179
- Scroll to the `Resource` section and click on `Resources`
180
180
- Click on the `Add Resource` button
181
-
- Select `Cloud` for `Resource Type` and enter a description.
181
+
- Select `Cloud` for `Resource Type`, enter a name and a description.
182
182
- Make sure the checkboxes for `Is available`, `Is public`, and `Is allocatable` are checked.
183
183
- Under the `Resource Attributes` section, click `Add another resource attribute`
184
184
- Select the option `quantity_default_value` and enter a number here.
@@ -221,32 +221,22 @@ As the admin, let's configure and activate that allocation:
221
221
- Navigate to the `Admin` menu and click on `Allocation Requests`
222
222
- Click on the `Details` button next to the `Research Cloud` allocation request to configure and activate the allocation:
223
223
click the `Add Allocation Attribute` button and select these allocation attributes from the drop down menu:
224
-
`Core Usage (Hours)` Enter: `10000`
224
+
`Core Usage (Hours)` Enter: `10000`
225
225
`Cloud Storage Quota (TB)` Enter: `10`
226
226
`Cloud Account Name` Enter: `cgray`
227
227
Notice as you add the core usage and cloud storage quota attributes you see usage graphs displayed. These can tie into a plugin such as XDMoD or the OpenStack community developed plugins for usage information.
228
+
- Click the `Approve` button to change the allocation status to `Active` and set the expiration date out one year from now.
228
229
229
230
Now let's go look at and activate the allocation change request submitted by `cgray` for the storage resource.
230
231
- Navigate to the `Admin` menu and click on `Allocation Change Requests`
231
232
- Click on the `Details` button to review and approve the allocation changes requested. 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 `storage_quota` 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.
232
-
- At the bottom of the page, click the `View Allocation` button and notice the `Storage Quota` attribute value has changed from 10000 to 20000.
233
-
234
-
### Staff Member View
235
-
236
-
We have setup the `astewart` account as an example of what a center staff member might see in ColdFront.
237
-
- Login as `astewart` password `ilovelinux` to see what additional menus and functionality this account has access to.
238
-
- Navigate to the `Staff` menu and click through the menu options to get a sense of the access we recommend for staff members.
239
-
- Click on the `User Search` menu option and enter one of the other account names and click the `Search` button. Click on the username and then click on the `View User Projects and Managers` button. You'll see a list of projects the user is a member of and if they are a PI or manager on any of them.
240
-
- Logout
241
-
242
-
For more options on allowing permissions for various types of staff access, see the ColdFront manual: https://coldfront.readthedocs.io/en/latest/manual/users/
233
+
- At the bottom of the page, click the `View Allocation` button and notice the `Storage Quota` attribute value has changed from the origianl 10000 to whatever you set it as.
243
234
244
235
245
236
### Removing Access
246
237
247
238
When an allocation expires or is revoked, the users on that allocation should lose access to the resource. If the allocation has the `freeipa_group` attribute set, all allocation users are removed from the group when the FreeIPA plugin is run. If the allocation is for a Slurm resource, all Slurm user associations and the Slurm account are removed when the Slurm plugin is run. Let's expire a Slurm allocation and then run the `slurm_check` tool.
248
239
249
-
- Login as `hpcadmin` password `ilovelinux`
250
240
- Navigate to the `Admin` menu, click on `All allocations` and click on the allocation for the hpc cluster resource.
251
241
- Change the status to `Expired` and the End Date to today. Click the `Update` button.
252
242
@@ -274,16 +264,25 @@ sacctmgr show user cgray -s list
274
264
```
275
265
There should be no account or association listed any longer
276
266
277
-
That wraps up the full day tutorial but there is a lot more you can do with ColdFront. See the steps we did to [pre-seed the database](#seeding-the-database-for-the-full-day-tutorial) for this tutorial and the [documentation for more info](https://coldfront.io).
267
+
### Staff Member View
278
268
279
-
</details>
280
-
<br>
269
+
We have setup the `astewart` account as an example of what a center staff member might see in ColdFront.
270
+
- Login as `astewart` password `ilovelinux` to see what additional menus and functionality this account has access to.
271
+
- Navigate to the `Staff` menu and click through the menu options to get a sense of the access we recommend for staff members.
272
+
- Click on the `User Search` menu option and enter one of the other account names and click the `Search` button. Click on the username and then click on the `View User Projects and Managers` button. You'll see a list of projects the user is a member of and if they are a PI or manager on any of them.
273
+
- Logout
281
274
275
+
You can see how these different permissions were setup for the tutorial in the [pre-seeding section](#seeding-the-database-for-the-full-day-tutorial) below.
276
+
277
+
For more options on allowing permissions for various types of staff access, see the ColdFront manual: https://coldfront.readthedocs.io/en/latest/manual/users/
282
278
283
279
280
+
That wraps up the full day tutorial but there is a lot more you can do with ColdFront. See the steps we did to [pre-seed the database](#seeding-the-database-for-the-full-day-tutorial) for this tutorial and the [documentation for more info](https://coldfront.io).
0 commit comments