cloud:cli
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
cloud:cli [2020/05/14 10:39] – [Flavors] chudler | cloud:cli [2021/04/15 16:17] – chudler | ||
---|---|---|---|
Line 9: | Line 9: | ||
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 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. | ||
- | '' | + | '' |
< | < | ||
clouds: | clouds: | ||
Line 16: | Line 16: | ||
auth_url: https:// | auth_url: https:// | ||
username: " | username: " | ||
- | password: " | + | password: " |
project_name: | project_name: | ||
user_domain_name: | user_domain_name: | ||
Line 23: | Line 23: | ||
identity_api_version: | identity_api_version: | ||
</ | </ | ||
- | The [[ cloud: | ||
- | You can also download a customized version of this data after you authenticate to the Web Interface | + | **NOTE** |
+ | The problem here is that you are taking risks by storing your University credentials in a file. Instead, you can use the API or [[ https:// | ||
+ | |||
+ | < | ||
+ | openstack application credential create --secret sekret --role member --expiration 2020-10-10: | ||
+ | </ | ||
+ | |||
+ | See the [[ cloud: | ||
+ | |||
+ | === Download Configuration File === | ||
+ | You can download a customized version of this data after you authenticate to the [[ https:// | ||
+ | |||
+ | For convenience, | ||
+ | < | ||
+ | export OS_CLOUD=openstack | ||
+ | </ | ||
====== USAGE ====== | ====== USAGE ====== | ||
Line 48: | Line 62: | ||
====Images==== | ====Images==== | ||
- | Images are prebuilt | + | Images are prebuilt |
+ | |||
+ | 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 | + | 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, |
< | < | ||
Line 57: | Line 73: | ||
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) | 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) | ||
- | < | + | < |
==== Flavors ==== | ==== Flavors ==== | ||
Line 82: | Line 98: | ||
You now have all of the prerequisites for launching a virtual computer. These are the prerequisites: | You now have all of the prerequisites for launching a virtual computer. These are the prerequisites: | ||
- | * Properly prepared Network -- or use the one called | + | * Properly prepared Network -- or use the one called |
* Flavor Name | * Flavor Name | ||
* Image Name | * Image Name | ||
Line 149: | Line 165: | ||
</ | </ | ||
- | 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 " |
==== Internet Addresses ==== | ==== Internet Addresses ==== | ||
- | If the server' | + | If the server' |
As in [[ cloud: | As in [[ cloud: | ||
Line 181: | Line 197: | ||
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. | 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 ==== | ==== 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 | 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 |
/var/lib/dokuwiki/data/pages/cloud/cli.txt · Last modified: 2021/04/15 16:53 by chudler