Differences

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

--- cloud:cli [2020/05/14 10:37] – [CONFIGURATION] chudler
+++ cloud:cli [2021/04/15 16:45] – chudler
@@ Line 8: / Line 8: @@
 ===== CONFIGURATION =====
-Use a clouds.yaml file to direct your client. Below is a canonical example, but you __will__ have to modify the variables according to your account.
+Use the ''~/.config/openstack/clouds.yaml'' file to direct your client.
-''$HOME/.config/clouds.yaml''
+=== Generate New Credentials ===
+Instead of taking risks and storing your University credentials in the file, use the [[ https://overcloud.cs.uchicago.edu | Web Interface ]] to create an Application Credential. Click the menu on the left side, Identity→Application Credentials. On the right side of the top of the page, click "Create Application Credential". Complete the form and check the box for ''unrestricted access''. Save the ''clouds.yaml'' file in your configuration directory.
+See the [[ cloud:recipe:coding | Python Examples Document ]] for detailed configuration recommendations.
+==Cloud Name==
+For convenience, export the cloud name to your environment. Otherwise, all commands must include the flag ''--os-cloud=openstack'':
 <code>
-clouds:
+export OS_CLOUD=openstack
-  openstack:
-    auth:
-      auth_url: https://overcloud.cs.uchicago.edu:5000
-      username: "CNetID"
-      password: "sekret"
-      project_name: "CNetID"
-      user_domain_name: "CS_LDAP"
-    region_name: "RegionOne"
-    interface: "public"
-    identity_api_version: 3
 </code>
-The [[ cloud:recipe:coding | Python Examples ]] use the same configuration, please read that document for detailed information about configuration and recommendations.
-You can also download a customized version of this data after you authenticate to the Web Interface (click API Access from the menu and then the button "Download Openstackrc File"). Make sure you read this file carefully in case you want to customize it. Your password is not included in the file by default.
 ====== USAGE ======
@@ Line 34: / Line 29: @@
 </code>
-take note and always use help for guidance <code>--help</code>
+always use help for guidance <code>--help</code>
 For example<code>openstack server create --help</code>
@@ Line 48: / Line 43: @@
 ====Images====
-Images are prebuilt disks that are used to launch instances. They are usually a few GB in size. A copy of the disk image is written into the instance's boot volume just before it starts running.
+Images are prebuilt operating systems that are used to launch instances. It is equivalent to a live CD. They are usually a few GB in size. A copy of the disk image is written into the instance's boot volume just before it starts running.
-There are images that Techstaff provides, some of which are restricted-use. We can build images for you or you can build and upload your own. Our images are generic, bare bones, cloud enabled popular operating systems that are a firm foundation for you to customize from. They are often in RAW format, not qcow2, for performance reasons.
+There are images that Techstaff provides, some of which are restricted-use. We can build images for you or you can build and upload your own. Our images are generic, bare bones, cloud enabled, popular operating systems, that are a firm foundation for you to customize from. They are often in RAW format, not qcow2, for performance reasons.
+Beware of images that are used internally to provide cloud services. You should not usually launch these directly. You do have access to them for the use of a service, and are welcome to customize for advanced usage.
 <code>openstack image list</code>
@@ Line 57: / Line 54: @@
 Openstack can hold a public key in its db, and insert it into instances when told. This is optional (your author does not use this capability)
-<code>openstack keypair create --public-key ~/.ssh/id_rsa.pub mykey</code>
+<code>openstack keypair create --public-key ~/.ssh/id_ed25519.pub mykey</code>
 ==== Flavors ====
 A flavor is a pre-chosen size for resources that make up an instance. It is a mandatory parameter when creating instances. Look at the available flavors, which your admins have created.\\
-Servers can grow after creation. For example, the disk-size attribute merely expresses the **minimum** size of the boot volume, and most cloud-enabled operating systems expand the root volume on first-boot. In spite of this, relying on dynamically resizing instances increases risk, and you should choose a size that is close to what you expect to use.
+Servers can grow after creation. For example, the ''disk-size'' attribute merely expresses the **minimum** size of the boot volume, and most cloud-enabled operating systems expand the root volume on first-boot. In spite of this, relying on dynamically resizing instances increases risk, and you should choose a size that is close to what you expect to use.
 <code>openstack flavor list</code>
@@ Line 81: / Line 79: @@
 You now have all of the prerequisites for launching a virtual computer. These are the prerequisites:
-  * Properly prepared Network -- or use the one called "cloud" if you don't care about the L2 boundary nor the source address of your NAT clients
+  * Properly prepared Network -- or use the one called ''cloud'' if you don't mind sharing a broadcast domain, nor wish to control the source address of your NAT clients
   * Flavor Name
   * Image Name
@@ Line 148: / Line 146: @@
 </code>
-In actual fact, all of the servers you create will be in the same security group.
+In actual fact, all of the servers you create will be in the same security group, so you will not need to "discover" it more than once.
 ==== Internet Addresses ====
-If the server's status shows "Active", you can assign it an additional IP address. When doing networking work, you might wish to connect to web interface to access the console of the virtual machine.
+If the server's status shows ''Active'', you can assign it an additional IP address. When doing networking work, you might wish to connect to web interface to access the console of the virtual machine.
 As in [[ cloud:recipe:networks | Advanced Networking ]] get a campus IP address from our pool.
@@ Line 180: / Line 178: @@
 This section added a floating ip address directly to the server. You must realize that a router was needed on the subnet for that to happen. On default subnets, your cloud admin has pre-created suitable routers. The command will fail if you are creating your own subnets and networks without taking similar steps.
+Mixing and matching these techniques will create hilarious disasters.
 ==== A WORD ABOUT CLOUD INIT ====
 Your author uses cloud init extensively and does not contemplate alternative. It is optional. A minimal cloud-init for a modern Ubuntu cloud OS might look like this