Differences

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

--- cloud:intro [2020/01/17 11:57] – kauffman
+++ cloud:intro [2020/05/14 09:23] – trim text chudler
@@ Line 1: / Line 1: @@
 === SCOPE OF THIS DOCUMENT ===
-This guide covers the common subset of tasks that users 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.
+This guide covers the common subset of tasks that users 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.
-Some things that are not written about here but perhaps should be covered elsewhere
-  * Theory of operations (everything here is by example)
-  * Accomplishing tasks from the Web Interface
-  * Background and History
-  * Alternative Services within CS and without
-  * Organizational Policy, such as who can do what
-  * Deployment Architecture
-  * Systemic Limitations
-  * Good Practices (because they are nascent, at best)
-  * Cloud init, Fog, Terraform, Heat, and other operational tools
-  * Network and Information Security
-  * Backup and Restore
-The list is not comprehensive.
 === A WORD ABOUT SECURITY ===
-The security of the virtual computers that you launch is __your responsibility__. With this software you are able to create wildly insecure configurations that will be hacked within seconds, with no hope of recovering. This can put all of us at risk. The highest risk that you will encounter is to expose your computers to the Internet. Beware of the dangers associated with doing so!
+The security of the virtual computers that you launch is __your responsibility__. With this software you are able to create insecure configurations that will be hacked, with no hope of recovering. This can put all of us at risk. The highest risk that you will encounter is to expose your computers to the Internet. Beware of the dangers associated with doing so!
 === INTRODUCTION AND NOTES ===
-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:
+This cluster can spring into being computer resources without the involvement of other personnel. The software has some exotic capabilities, but this is a common subset:
   * L2 and L3 Network
@@ Line 34: / Line 19: @@
   * Security groups (firewall service)
-Some want
-  * Distributed/Replicated hash tables (K/V store, Object Storage)
-The cloud can also manage resources on your behalf that are traditionally handled by a human operator. This is less common, and amounts to cognitive debt that you may eventually have to pay:
+The cloud can also manage resources on your behalf that are traditionally handled by a human operator:
   * Load balancer
   * NFS
-  * Rancher Kubernetes (among others)
+  * Hadoop
-  * Lots more
+  * Rancher Kubernetes
+  * Container Runtime
 == Web Access and Certificates ==
 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)
 === 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 Admins can modify the memberships of their own Projects. However, there is __not__ a Role known as Owner.
 == Your Default Project ==
@@ Line 279: / Line 260: @@
 As before, in the Network Gear section, get a campus IP address from our pool.
+Where do you want to create your floating IP?
+<code>
+openstack network list
+</code>
+Use the network from the previous command:
 <code>
-openstack floating ip create
+openstack floating ip create <network>
 </code>
+You now have an IP you can use:
 <code>
-openstack server add floating ip myserver 128.135.37.XX
+openstack server add floating ip myserver <floating_ip_address>
 </code>
@@ Line 331: / Line 319: @@
 Q: What about containers (docker)?
-A: We do not provide any support for them directly. We expect that you will want to manage this from inside the VMs that you create. We have no plans to deploy Magnum right now.
+A: [[ cloud:recipe:docker | Container Docs ]]
 Q: My servers are in ERROR state!!!