cloud:intro
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:intro [2019/12/13 08:54] – floating ip wont work for people chudler | cloud:intro [2020/05/14 09:25] – move the naq chudler | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| === SCOPE OF THIS DOCUMENT === | === 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 === | === A WORD ABOUT SECURITY === | ||
| - | The security of the virtual computers that you launch is __your responsibility__. With this software you are able to create | + | 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 === | === 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, | + | This cluster can spring into being computer resources without the involvement of other personnel. The software has some exotic capabilities, |
| * L2 and L3 Network | * L2 and L3 Network | ||
| Line 34: | Line 19: | ||
| * Security groups (firewall service) | * Security groups (firewall service) | ||
| - | Some want | ||
| - | * Distributed/ | ||
| - | 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 | * Load balancer | ||
| * NFS | * NFS | ||
| - | * Rancher Kubernetes | + | |
| - | * Lots more | + | |
| + | * Container Runtime | ||
| + | |||
| + | More notes can be found at [[ cloud:naq | Frequently Asked Questions ]] | ||
| == Web Access and Certificates == | == Web Access and Certificates == | ||
| The cloud is named **Overcloud**. The web interface uses a non-public certificate authority and can be reached at [[https:// | The cloud is named **Overcloud**. The web interface uses a non-public certificate authority and can be reached at [[https:// | ||
| - | |||
| - | NOTE: Our cloud DNS service might not meet your needs. Please test it anyway if you know how (TODO: document) | ||
| === 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 Admins can modify the memberships of their own Projects. However, 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 Admins can modify the memberships of their own Projects. However, there is __not__ a Role known as Owner. | ||
| - | |||
| == Your Default Project == | == Your Default Project == | ||
| Line 82: | Line 65: | ||
| Use your favorite package manager on your own computer. Pip is preferred because the upstream packages it for themselves and it is in pure python. The general CS infrastructure will become a managed client for you to use in the near future (e.g., linux.cs.uchicago.edu). However, our experience has been that the software installs cleanly and is free from dependency problems. | Use your favorite package manager on your own computer. Pip is preferred because the upstream packages it for themselves and it is in pure python. The general CS infrastructure will become a managed client for you to use in the near future (e.g., linux.cs.uchicago.edu). However, our experience has been that the software installs cleanly and is free from dependency problems. | ||
| - | Try: < | + | Try: < |
| == PRELIMINARY SETUP == | == PRELIMINARY SETUP == | ||
| Line 146: | Line 129: | ||
| You are free to use the Network called __cloud__, if you don't need your hosts to be L2 isolated from other people, and you would like to proceed directly to creating servers. | You are free to use the Network called __cloud__, if you don't need your hosts to be L2 isolated from other people, and you would like to proceed directly to creating servers. | ||
| Using the __cloud__ network cuts down your complexity significantly, | Using the __cloud__ network cuts down your complexity significantly, | ||
| - | < | + | |
| + | < | ||
| + | openstack network list | ||
| + | </ | ||
| [EDITOR NOTE: This section should be isolated from the main body] | [EDITOR NOTE: This section should be isolated from the main body] | ||
| Line 153: | Line 139: | ||
| Should you want to create a network of your own that your hosts will be on, not all of these options are necessary | Should you want to create a network of your own that your hosts will be on, not all of these options are necessary | ||
| - | < | + | < |
| + | openstack network create mynet \ | ||
| + | | ||
| + | | ||
| + | | ||
| + | </ | ||
| Now create a subnet for your network. This is mandatory for launching instances in the network that you just created. | Now create a subnet for your network. This is mandatory for launching instances in the network that you just created. | ||
| Line 163: | Line 154: | ||
| You are now advised that there is no " | You are now advised that there is no " | ||
| - | < | + | < |
| + | openstack subnet create | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | </ | ||
| After creating your own network and subnet(s), a router is also needed. However, a router is **not** needed if your instances only talk to each other. The router will take the gateway of your subnet automatically, | After creating your own network and subnet(s), a router is also needed. However, a router is **not** needed if your instances only talk to each other. The router will take the gateway of your subnet automatically, | ||
| - | < | + | |
| - | openstack router add subnet myrouter mysubnet</ | + | < |
| + | openstack router create --enable myrouter | ||
| + | </ | ||
| + | < | ||
| + | openstack router add subnet myrouter mysubnet | ||
| + | </ | ||
| With the router created and attached to your own subnet, develop it further. You need to obtain a free IP address on the UC Campus. We call this network __campus37__. The Internet-connected subnet on that network is called __public37__. | With the router created and attached to your own subnet, develop it further. You need to obtain a free IP address on the UC Campus. We call this network __campus37__. The Internet-connected subnet on that network is called __public37__. | ||
| Line 176: | Line 181: | ||
| < | < | ||
| - | openstack router set myrouter --external-gateway campus37 --enable-snat | + | openstack router set myrouter |
| + | | ||
| + | | ||
| </ | </ | ||
| Line 192: | Line 199: | ||
| Like other openstack activities, creating a server has __many__ complex options and scenarios. This is a simple and ordinary depiction, creating one server | Like other openstack activities, creating a server has __many__ complex options and scenarios. This is a simple and ordinary depiction, creating one server | ||
| - | < | + | |
| + | < | ||
| + | openstack server create | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | </ | ||
| The command executed asynchronously, | The command executed asynchronously, | ||
| - | < | + | < |
| - | openstack server show myserver</ | + | openstack server list --name myserver |
| + | </ | ||
| + | < | ||
| + | openstack server show myserver | ||
| + | </ | ||
| Here's an example for creating 10 of them, as promised (only the change at the end of the command) | Here's an example for creating 10 of them, as promised (only the change at the end of the command) | ||
| - | < | + | < |
| + | openstack server create | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | myserver | ||
| + | </ | ||
| Here's a nasty thing I use to determine what the security group is for a server (it can be determined also by looking at security groups directly) [ITS BRITTLE, BEWARE] | Here's a nasty thing I use to determine what the security group is for a server (it can be determined also by looking at security groups directly) [ITS BRITTLE, BEWARE] | ||
| - | < | + | < |
| + | SEC_GROUP=$(openstack port list \ | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | sed ' | ||
| + | </ | ||
| If I learned the security group successfully, | If I learned the security group successfully, | ||
| - | < | + | < |
| + | openstack security group rule create | ||
| + | | ||
| + | | ||
| + | | ||
| + | </ | ||
| In actual fact, all of the servers you create will be in the same security group. The above was attempting to suggest effective use of the tools, in combination. | In actual fact, all of the servers you create will be in the same security group. The above was attempting to suggest effective use of the tools, in combination. | ||
| Line 216: | Line 261: | ||
| You could also use the web interface to access the console, but that's not quite the same. | You could also use the web interface to access the console, but that's not quite the same. | ||
| As before, in the Network Gear section, get a campus IP address from our pool. | As before, in the Network Gear section, get a campus IP address from our pool. | ||
| - | < | + | |
| - | openstack server add floating ip myserver | + | |
| + | Where do you want to create your floating IP? | ||
| + | < | ||
| + | openstack network list | ||
| + | </ | ||
| + | Use the network from the previous command: | ||
| + | < | ||
| + | openstack floating ip create | ||
| + | </ | ||
| + | You now have an IP you can use: | ||
| + | < | ||
| + | openstack server add floating ip myserver | ||
| </ | </ | ||
| Line 236: | Line 292: | ||
| Your author uses cloud init extensively and does not imagine a life without it. It is optional. The file used in these examples is available on request, but you should develop your own if you use it at all. | Your author uses cloud init extensively and does not imagine a life without it. It is optional. The file used in these examples is available on request, but you should develop your own if you use it at all. | ||
| - | |||
| - | === NAQ (Never Asked Questions) === | ||
| - | |||
| - | Q: Why does it use a self-signed certificate? | ||
| - | A: This is a loose end that might be addressed in the future. Let us know if it overburdens you. Note: we are unlikely to acknowledge security concerns associated with this. | ||
| - | |||
| - | Q: What are all of the services enabled? | ||
| - | A: | ||
| - | * cinder-backup | ||
| - | * heat | ||
| - | * barbican | ||
| - | * mistral | ||
| - | * ironic (we *do* support baremetal instances!) | ||
| - | * octavia | ||
| - | * sahara | ||
| - | * manila | ||
| - | * ganesha | ||
| - | * ceph (that is, ceph as a service. Your instances can be ceph clients in a software-defined manor if you wish, directly accessing RBD) | ||
| - | * MDS/ | ||
| - | * swift | ||
| - | * designate | ||
| - | * DVR/HA | ||
| - | * Full Blown OVN, as you desire | ||
| - | * nova | ||
| - | * placement (standalone) | ||
| - | * glance | ||
| - | * gnocchi (as-a-service. Hundreds of metrics are collected for everything in your project) | ||
| - | |||
| - | 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. | ||
| - | |||
| - | Q: My servers are in ERROR state!!! | ||
| - | A: If the servers had been running previously, this is bad and may not be recoverable. Talk to us ASAP about anything that you know. We'll troubleshoot. The upside is that the servers might be gone but the volumes and anything else associated with them (ports, etc) can be attached to entirely new servers, as is often done in clouds. | ||
| - | |||
| - | Q: How fast is it? | ||
| - | A: We haven' | ||
| - | |||
| - | Q: Is my data safe? | ||
| - | A: PROBABLY NOT AT THIS STAGE! | ||
| - | |||
| - | Q: How does the SSH key injection work? | ||
| - | A: Cloud-init. You won't be able to do this unless you are using a " | ||
| - | |||
| - | Q: What operating systems are supported? | ||
| - | A: We are prepared to run any workload if you are willing to put in requisite work also. We know it to be compatible with all major Unixes and Windows. Building an image is required before an instance can be launched and this is usually done with image building tools (chroot, et al). | ||
| - | |||
| - | Q: What about limitations? | ||
| - | A: The following quotas are set on your account and projects, only for the safety of the cloud. We will lift these easily if you need it (values are unspecified here, as yet, sorry): | ||
| - | * gigabytes | ||
| - | * volumes | ||
| - | * secgroups | ||
| - | * secgroup-rules | ||
| - | * server-groups | ||
| - | * ram | ||
| - | * instances | ||
| - | * fixed-ips | ||
| - | * server-group-members | ||
| - | * cores | ||
| - | * per-volume-gigabytes | ||
| - | * backup-gigabytes | ||
| - | * snapshots | ||
| - | * volumes | ||
| - | * backups | ||
| - | * subnetpools | ||
| - | * ports | ||
| - | * subnets | ||
| - | * networks | ||
| - | * floating-ips | ||
| - | * routers | ||
| == URLS == | == URLS == | ||
/var/lib/dokuwiki/data/pages/cloud/intro.txt · Last modified: 2021/04/15 17:50 by chudler