Differences

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

--- cloud:intro [2019/12/06 15:21] – [Annotated Example] chudler
+++ cloud:intro [2019/12/06 15:55] – chudler
@@ Line 1: / Line 1: @@
 === SCOPE OF THIS DOCUMENT ===
-This guide will cover a common subset of tasks that a user would need to perform to have a set of clustered computer instances and associated resources, isolated from others, and accessible to a project for any general purpose, both long-term and short. We are catering heavily to short-term usage, perhaps lasting a few quarters.
+This guide covers a common subset of tasks that a user would need to perform to have a set of clustered computer instances and associated resources, isolated from others, and accessible to a project for any general purpose, both long-term and short. We are catering heavily to short-term and periodic usage, perhaps lasting no more than a few quarters.
-Some things that are not here but perhaps should be covered elsewhere
+Some things that are not written about here but perhaps should be covered elsewhere
-  * Theory of operations (everything is by example)
+  * Theory of operations (everything here is by example)
-  * Tasks accomplished from the Web Interface
+  * Accomplishing tasks from the Web Interface
   * Background and History
-  * Organizational Policy, such as who can do what.
+  * Alternative Services within CS and without
+  * Organizational Policy, such as who can do what
   * Deployment Architecture
-  * Limitations
+  * Systemic Limitations
-  * User management, Group management, and similar concepts
   * Good Practices (because they are nascent, at best)
   * Cloud init, Fog, Terraform, Heat, and other operational tools
-  * Security
+  * Network and Information Security
   * Backup and Restore
@@ Line 26: / Line 26: @@
 === INTRODUCTION AND NOTES ===
-This cluster can spring into being computer resources, easily, and without any involvement of other personnel. The software has some exotic capabilities, but almost everyone will use this common subset:
+This cluster can spring into being computer resources, easily, and without the involvement of other personnel. The software has some exotic capabilities, but almost everyone will use a common subset:
   * L2 and L3 Network
   * Router (SNAT and DNAT devices, etc)
   * Compute, and all that it entails such as RAM, CPU, Disk, ...
-  * Block Storage (volume mounts)
+  * Additional Block Storage (volume mounts)
   * Security groups (firewall service)
@@ Line 42: / Line 42: @@
   * NFS
   * Rancher Kubernetes (among others)
+  * Lots more
 == Web Access and Certificates ==
-The cloud is named **Overcloud**. The web interface at [[https://overcloud.cs.uchicago.edu]] uses a non-public certificate authority. You will have to accept it for all purposes: API, HTTPS, and CLI clients.
+The cloud is named **Overcloud**. The web interface uses a non-public certificate authority and can be reached at [[https://overcloud.cs.uchicago.edu]]. You will have to accept the certificate for all purposes: API, HTTPS, and CLI clients.
 NOTE: Our cloud DNS service might not meet your needs. Please test it anyway if you know how (TODO: document)