16 FusionSphare OpenStack OM Services Operation
16 FusionSphare OpenStack OM Services Operation
16 FusionSphare OpenStack OM Services Operation
During network planning, determine the VLANs and subnets to be used by the system
management plane, storage plane, and tenant service plane.
After a host is added to a host group, through tag to select the host to create the VM.
The relationship between disk type and backend storage is similar to the relationship
between host groups and hosts.
You can view hosts in a host group and add or delete hosts in the host group.
choose Resources > Computing > Host Groups, and click Host Management.
Before creating a VM image, an image file must be created first and followed by
registering the image file as an image.
Prepare an image file.
If the registered image type is KVM, the image files must meet the following
requirements:
The file format is qcow2, iso, img, or raw.
It is recommended that the UVP VMTools installed in the image. Otherwise, the
VM information monitoring and I/O performance may be affected. The UVP
VMTools can be used in Huawei FusionSphere OpenStack environment only.
Select an appropriate method to register the image file based on the file size.
If the image file size is less than 6GB, the registration methods are “local upload
and register”, “NFS server upload and register”, and “upload and register
through FusionSphere OpenStack”.
If the size of the image file is greater than or equal to 6GB but less than 200
GB, the registration methods are "NFS server upload and register" and "upload
and register through FusionSphere OpenStack".
If the size of the image file is greater than 200 GB, use the FusionSphere
OpenStack to upload and register the image file.
Disk type is the type or tag that can be selected when creating a disk. A disk type
corresponds to the backend storage used by a group of disks. By creating a disk type,
you can associate the disk type with the backend storage so that tenants can create
appropriate disks for VMs based on the disk type.
After a disk type is created, tenants can select an appropriate type of backend storage to
provide disk resources for VMs.
On the FusionSphere OpenStack Management Console, choose Resources >
Storage > Disk Types and click Create.
A backend storage device saves cloud disk resources in OpenStack cloud services. After
deploying an OpenStack resource pool, the administrator can create the name and type
of a backend storage device and configures a mapping between the backend storage
device and the storage device.
An external network is used to connect VMs in the system to networks outside the
system, such as an existing network of the customer, an internal network of business, or
a public network (Internet).
An external network can be used as a direct network in a VPC or an elastic IP address
pool to provide elastic IP address services.
A virtual data center (VDC) is the primary unit of virtual resources managed in
FusionSphere OpenStack OM. For example, an enterprise can assign an independent
VDC for each of its department, and each VDC contains all virtual resources that can be
used by the department, such as computing, storage, and network resources.
Each VDC can contain multiple users, which can be managed by the VDC administrator.
Users can be added to or deleted from VDCs, the available resource ranges and
resource quota can be set.
You can create a VDC and configure a VDC administrator that has permission to manage
resources in the VDC.
A VDC is equivalent to a domain in FusionSphere OpenStack.
Choose VDC > VDCs and click Create VDC.
A VPC provides a secure, isolated network environment for a virtual data center (VDC).
You can customize virtual networks that provide the same functions as traditional
networks in a VPC. The custom virtual networks can also provide advanced network
features, such as elastic IP address and security group, to meet with the service
deployment requirements.
VPCs can only be created by a tenant.
FusionSphere OpenStack OM provides multiple types of VPCs that contain networks by
default. After these VPCs are created, the created networks exist in the VPCs. You can
still create more networks based on the created networks. When creating this VPC, if the
network fails to be created due to insufficient resources or incorrect configurations, the
creation of VPC and other networks are not affected.
A customized VPC is used to create an empty VPC. After the VPC is created, you can
create networks and other network resources.
A VPC is equivalent to a project in FusionSphere OpenStack.
In FusionSphere OpenStack Management Console tenant view, choose VPC > My VPC.
Click Create VPC.
Create a network that meets service deployment requirements in the VPC. The names of
different networks can be the same, tenants can distinguish it by ID or VLAN. To
distinguish different networks more easily, you are advised to plan different names for
different networks.
On the main menu, choose VPC > My VPC. In the My VPC area, click the VPC name.
Choose Network. On the VPC Network tab, click Create.
Three types of networks can be created in a VPC: direct network, internal network, and
routed network to fulfill VM or application deployment.
Direct network: A direct network is discovered from FusionSphere OpenStack
and it cannot be created.
Internal network: An internal network is isolated from other networks and uses
exclusive network resources. Therefore, you can deploy services that have high
security requirements, for example, database server services, on an internal
network to ensure high data security.
Routed network: A routed network provides flexible communication functions
and supports various services. Routed networks in a VPC can communicate
with each other or the Internet.
A virtual machine is like a physical computer which is a virtual computer that runs an
operating system and an application program.
The VM runs on a host and obtains computing resources, such as CPU and memory,
from the host, as well as graphics processing units (GPUs), USB devices, network
connections, and storage access.
Use a VM template to create a VM.
Choose Resources > Computing > VM, and click Create.
For security reason, change the VM password in a timely manner.
Adjust VM flavor, including the number of CPUs and memory size to adjust the VM
performance.
Flavor can be adjusted only when the VM is in the Stopped or Running state. If a VM is in
the Running state, the VM is automatically shut down when adjusting the flavor. After it is
complete, the VM is automatically return to the Running state.
Choose Resources > Computing > VM, expand VM details, and click on Flavor.
Create a common disk for the VM and add it as the data disk of the VM, or add an
existing disk to the VM.
Choose Resources > Computing > VM, expand VM details, click Disk, and click Add Data
Disk.
If the disk type is IDE, the disk can be mounted only when the VM is in the Stop state.
Other types of disks can be mounted to a disk when the VM is in the Running state. After
the disk is mounted successfully, the disk takes effect only after the VM is restarted.