Managing your cloud resources with OpenStack: Difference between revisions

Managing your cloud resources with OpenStack (view source)

Revision as of 20:07, 12 June 2023

3 bytes added , 1 year ago

no edit summary

Diane27

rsnt_translations

56,420

edits

@@ Line 14: / Line 14: @@
 =Projects= <!--T:64-->
-OpenStack projects group VMs together and provide a quota out of which VMs and related resources can be created. A project is unique to a particular cloud. All accounts which are members of a project have the same level of permissions, meaning anyone can create or delete a VM within a project if they are a member. You can view the projects you are a member of by logging into an OpenStack dashboard for the clouds you have access to (see [[Cloud#Cloud_systems|Cloud systems]] for a list of cloud URLs). The active '''project name''' will be displayed in the top left of the dashboard, to the right of the cloud logo. If you are a member of more than one project, you can switch between active projects by clicking on the drop-down menu and selecting the project's name.
+OpenStack projects group VMs together and provide a quota out of which VMs and related resources can be created. A project is unique to a particular cloud. All accounts which are members of a project have the same level of permissions, meaning anyone can create or delete a VM within a project if they are a member. You can view the projects you are a member of by logging into an OpenStack dashboard for the clouds you have access to (see [[Cloud#Cloud_systems|Cloud systems]] for a list of cloud URLs). The active <b>project name</b> will be displayed in the top left of the dashboard, to the right of the cloud logo. If you are a member of more than one project, you can switch between active projects by clicking on the drop-down menu and selecting the project's name.
 <!--T:74-->
@@ Line 42: / Line 42: @@
 == Default security group == <!--T:5-->
 [[File:Default_security_group_EN.png|400px|thumb| Default Security Group Rules (Click for larger image)]]
-The '''default security group''' contains rules which allow a VM access out to the internet, for example to download operating system upgrades or package installations, but does not allow another machine to access it, except for other VMs belonging to the same default security group. We recommend you do not remove rules from the default security group as this may cause problems when creating new VMs. The image on the right shows the default security group rules that should be present:
+The <b>default security group</b> contains rules which allow a VM access out to the internet, for example to download operating system upgrades or package installations, but does not allow another machine to access it, except for other VMs belonging to the same default security group. We recommend you do not remove rules from the default security group as this may cause problems when creating new VMs. The image on the right shows the default security group rules that should be present:
 * 2 Egress rules to allow your instance to access an outside network without any limitation; there is one rule for IPV4 and one for IPV6.
 * 2 Ingress rules to allow communication for all the VMs that belong to that security group, for both IPV4 and IPV6.
@@ Line 62: / Line 62: @@
 <!--T:90-->
-'''The first time your instance is launched''', you can customize it using cloudInit. This can be done either
+<b>The first time your instance is launched</b>, you can customize it using cloudInit. This can be done either
 * via the OpenStack command-line interface, or
 * by pasting your cloudInit script in the ''Customization Script'' field of the OpenStack dashboard (''Project-->Compute-->Instances-->Launch instance'' button, ''Configuration'' option).