cc_staff
1,486
edits
(Marked this version for translation) |
|||
Line 19: | Line 19: | ||
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. | ||
=Availability Zones= | =Availability Zones= <!--T:72--> | ||
Availability zones allow you to indicate what group of physical hardware you would like your VM to run on. On East, West, and Graham clouds, there is only one availability zone, ''Nova'', so there isn't any choice in the matter. However, on Arbutus there are three availability zones: ''Compute'', ''Persistent_01'', and ''Persistent_02''. The ''Compute'' and ''Persistent'' zones only run compute or persistent flavors respectively (see [[virtual machine flavors]]). The two persistent zones allow you to create VMs on two distinct sets of physical hardware helping to ensure greater collective availability between those two VMs. | Availability zones allow you to indicate what group of physical hardware you would like your VM to run on. On East, West, and Graham clouds, there is only one availability zone, ''Nova'', so there isn't any choice in the matter. However, on Arbutus there are three availability zones: ''Compute'', ''Persistent_01'', and ''Persistent_02''. The ''Compute'' and ''Persistent'' zones only run compute or persistent flavors respectively (see [[virtual machine flavors]]). The two persistent zones allow you to create VMs on two distinct sets of physical hardware helping to ensure greater collective availability between those two VMs. | ||