rsnt_translations
56,430
edits
Managing your cloud resources with OpenStack: Difference between revisions
Jump to navigation
Jump to search
Managing your cloud resources with OpenStack (view source)
Revision as of 16:31, 15 January 2019
, 5 years agono edit summary
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
OpenStack projects group VMs together and provide a quota out of which VMs and related resources can be created. A project is unique to a particular cloud. All accounts which are members of a project have the same level of permissions, meaning anyone can create or delete a VM within a project they are a member of. You can view the projects you are a member of by logging into an OpenStack dashboard for the cloud(s) you have access to (see [[Cloud#Using_the_Cloud|using the cloud]] for a list of cloud URLs). The active '''project name''' will be displayed in the top left of the dashboard to the right of the cloud logo. If you are a member of more than one project you can switch between active projects by clicking on the drop down menu and clicking a project name. | OpenStack projects group VMs together and provide a quota out of which VMs and related resources can be created. A project is unique to a particular cloud. All accounts which are members of a project have the same level of permissions, meaning anyone can create or delete a VM within a project they are a member of. You can view the projects you are a member of by logging into an OpenStack dashboard for the cloud(s) you have access to (see [[Cloud#Using_the_Cloud|using the cloud]] for a list of cloud URLs). The active '''project name''' will be displayed in the top left of the dashboard to the right of the cloud logo. If you are a member of more than one project you can switch between active projects by clicking on the drop down menu and clicking a project name. | ||
Depending on your allocation, your project may be limited to certain types of VM [[Virtual_machine_flavors|flavors]]. For example, compute allocations will generally only allow "c" flavors, while persistent allocations, will generally only allow "p" flavors. | |||
Depending on your allocation your project may be limited to certain types of VM [[Virtual_machine_flavors|flavors]]. For example, | |||
Projects can be thought of as owned by primary investigators (PIs) and new projects and quota adjustments can only be requested by PIs. In addition request for access to an existing project must be confirmed by the PI owning the project. | Projects can be thought of as owned by primary investigators (PIs) and new projects and quota adjustments can only be requested by PIs. In addition request for access to an existing project must be confirmed by the PI owning the project. | ||