User Tools

Site Tools


cloud:intro

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
cloud:intro [2020/05/14 14:00] chudlercloud:intro [2021/04/15 17:50] (current) chudler
Line 8: Line 8:
  
   * L2 and L3 Network   * L2 and L3 Network
-  * Router (SNAT and DNAT devices, etc) 
   * Compute, such as RAM, CPU, Disk, in the form of Virtualized, Container, or Hyrbid (Kata)   * Compute, such as RAM, CPU, Disk, in the form of Virtualized, Container, or Hyrbid (Kata)
-  * Additional Block Storage (volume mounts)+  * Block Storage (volume mounts)
   * Security groups (firewall service)   * Security groups (firewall service)
  
Line 21: Line 20:
   * Kubernetes   * Kubernetes
   * VPN   * VPN
-  * Lambda Functions+  * "LambdaFunctions Service
   * DNS   * DNS
   * Relational Database - as a service   * Relational Database - as a service
Line 33: Line 32:
  
 ======Getting and Using Access====== ======Getting and Using Access======
-Please write techstaff@cs.uchicago.edu and let us know that you saw this document. Allow us time to create your private project within the cloud. Then you can proceed with the rest of our documentation.+Please write techstaff@cs.uchicago.edu and let us know that you saw this document. Allow us time to create your private project within the cloud. Then you can proceed with the rest of our documentation, or try out the [[ cloud:cli | Command Line ]]
  
  
 === PROJECTS === === PROJECTS ===
  
-Openstack requires Users and their cloud resources to belong to a Project. Users have pre-defined Roles within that Project, such as Member or Admin. The Role, Project, and User together constitute in-context access control. So, when a user is in a certain Project, that User can read, modify, destroy the cloud resources in that Project, or even create new resources. All actions depend on the precise Role of the User in the project. Non-members of a project are not able to do anything with cloud resources of the project to which they are a non-member, including View Access. Users can belong to any number of Projects, and with potentially different Roles. Project Admin is not a permission we can grant at this time. Note that there is __not__ a Role known as Owner.+Openstack requires ''Users'' and their cloud resources to belong to a ''Project''. Users have pre-defined ''Roles'' within that ''Project'', such as ''Member'' or ''Admin''. The Role, Project, and User together constitute in-context access control. So, when a user is in a certain Project, that User can read, modify, destroy the cloud resources in that Project, or even create new resources. All actions depend on the precise Role of the User in the project. Non-members of a project are not able to do anything with cloud resources of the project to which they are a non-member, including View Access. Users can belong to any number of Projects, and with potentially different Roles. Project Admin is not a permission we can grant at this time. Note that there is __not__ a Role known as Owner.
  
 == Your Default Project == == Your Default Project ==
/var/lib/dokuwiki/data/attic/cloud/intro.1589482829.txt.gz · Last modified: 2020/05/14 14:00 by chudler

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki