rsnt_translations
56,420
edits
Managing your cloud resources with OpenStack: Difference between revisions
Jump to navigation
Jump to search
Managing your cloud resources with OpenStack (view source)
Revision as of 16:52, 1 June 2023
, 1 year agono edit summary
mNo edit summary |
No edit summary |
||
| Line 31: | Line 31: | ||
Please see [[Working_with_VMs|this page]] for more information about managing certain characteristics of your VMs in the Dashboard. | Please see [[Working_with_VMs|this page]] for more information about managing certain characteristics of your VMs in the Dashboard. | ||
=Availability | =Availability zones= <!--T:72--> | ||
Availability zones allow you to indicate what group of physical hardware you would like your VM to run on. On East and Graham clouds, there is only one availability zone, ''nova'', so there isn't any choice in the matter. However, on Arbutus there are three availability zones: ''Compute'', ''Persistent_01'', and ''Persistent_02''. The ''Compute'' and ''Persistent'' zones only run compute or persistent flavors respectively (see [[virtual machine flavors]]). Using two persistent zones can present an advantage; for example, two instances of a website can run in two different zones to ensure its continuous availability in the case where one of the sites goes down. | Availability zones allow you to indicate what group of physical hardware you would like your VM to run on. On East and Graham clouds, there is only one availability zone, ''nova'', so there isn't any choice in the matter. However, on Arbutus there are three availability zones: ''Compute'', ''Persistent_01'', and ''Persistent_02''. The ''Compute'' and ''Persistent'' zones only run compute or persistent flavors respectively (see [[virtual machine flavors]]). Using two persistent zones can present an advantage; for example, two instances of a website can run in two different zones to ensure its continuous availability in the case where one of the sites goes down. | ||
=Security | =Security groups= <!--T:3--> | ||
A security group is a set of rules to control network traffic into and out of your virtual machines. To manage security groups, go to ''Project->Network->Security Groups''. You will see a list of currently defined security groups. If you have not previously defined any security groups, there will be a single default security group. | A security group is a set of rules to control network traffic into and out of your virtual machines. To manage security groups, go to ''Project->Network->Security Groups''. You will see a list of currently defined security groups. If you have not previously defined any security groups, there will be a single default security group. | ||
| Line 59: | Line 59: | ||
An example of a CIDR rule is <code>192.168.1.1/24</code>. This looks just like a normal IP address with a <code>/24</code> appended to it. IP addresses are made up of 4, 1-byte (8 bits) numbers ranging from 0 to 255. What this <code>/24</code> means is that this CIDR rule will match the first left most 24 bits (3 bytes) of an IP address. In this case, any IP address starting with <code>192.168.1</code> will match this CIDR rule. If <code>/32</code> is appended, the full 32 bits of the IP address must match exactly; if <code>/0</code> is appended, no bits must match and therefore any IP address will match it. | An example of a CIDR rule is <code>192.168.1.1/24</code>. This looks just like a normal IP address with a <code>/24</code> appended to it. IP addresses are made up of 4, 1-byte (8 bits) numbers ranging from 0 to 255. What this <code>/24</code> means is that this CIDR rule will match the first left most 24 bits (3 bytes) of an IP address. In this case, any IP address starting with <code>192.168.1</code> will match this CIDR rule. If <code>/32</code> is appended, the full 32 bits of the IP address must match exactly; if <code>/0</code> is appended, no bits must match and therefore any IP address will match it. | ||
=Working with | =Working with cloudInit= <!--T:89--> | ||
<!--T:90--> | <!--T:90--> | ||