...
We are creating projects using a strict naming scheme. All projects should be named using one of the following schemes:
| Naming scheme | Example | Purpose |
|---|---|---|
| <Course-code>_<Term>_<GroupName> | IMT3441_V17_Group1 | Projects related to a specific course. Term should reflect when the project is created, and is built up by "H" for autumn and "V" for spring, and then two digits signalizing the year. |
| <Department>_<DescriptiveName> | IIK_AssuranceTestingLab | Project related to a certain project not course-specific. |
| PRIV_<username> | PRIV_eigilo | Single-user private project, not associated with any real courses or projects. Employees only. Similar student projects are prefixed "STUDENT". |
| MISC | MISC | Project with misc instances for "people who just wants a server" |
| STUDENT_<username> | STUDENT_olanordm | Private projects which a student requests for own learning. |
| STUDPROJ_<shortname> | STUDPROJ_cognita | Project assigned to a group of students for a project that is not directly associated with any courses. |
Any projects not following this naming scheme might be deleted without warning. Projects created before December 2016 will be renamed instead of deleted.
...
Assigning NTNU groups to a project
List groups assigned to a project
| Code Block |
|---|
openstack role assignment list --project <prjectname> --names |
A group from BAS can be assigned to a project using the following command:
...