TECS Feature List
TECS Feature List
TABLE OF CONTENT
Feature Description
Feature Description
With this feature, TECS can pause and restore VMs. It can pause a VM that is operating
without consuming CPU resources. It can also restore a VM that is paused. The status
of the VM is the same before being paused and after being restored.
Feature Description
This feature is that VM creates image snapshot as a image file to backup the system
and data information. And then to create a new VM via the snapshot image, after the VM
is running, the system and data information is recovery as before.
Feature Description
This feature is used to set the affinity between the VCPUs of a VM and the physical
CPUs of its host.
Feature Description
Feature Description
TECS supports abundant guest Oss, such as Windows2008, Centos6.*, RHEL6.* and
etc..
Feature Description
This feature enables a shared disk to be used by multiple VMs. These VMs can read
and write to the share disk at the same time, but the cluster software in the VMs
guarantees the read and write mutexes.
Feature Description
This feature enables a PCIE device to not only export multiple PCI physical functions,
but also export a group of virtual functions sharing the resources on the I/O device. This
feature enables SR-IOV for physical NICs, allowing VMs efficiently share physical NICs.
Feature Description
VLANs operate in layer 2 and layer 3 of the OSI reference model. One VLAN is a
broadcast domain. VLANs communicate with each other through layer-3 routers. In
contrast to traditional LAN technologies, the VLAN technology is more flexible. It has the
following advantages:
Reduces the management expenses for moving, adding, and modifying network
devices.
The Distributed Virtual Switch (DVS) supports VLAN isolation. To achieve the purpose of
this function, the corresponding VLAN tags can be configured on the ports added to the
DVS or the TAP interfaces of VMs.
Feature Description
The VLAN Trunk function is used to aggregate and bind VLANs, so that multiple VLANs
can share a physical link. The cascading port of two switches is set to the Trunk port.
When a switch sends a packet through the cascading port, it adds a tag to the packet,
so that other switches can identify the VLAN of the packet. After another switch receives
this packet, the switch only forwards the packet to the VLAN specified by the tag,
implementing intra-VLAN data transmission between switches.
In a trunk-type logic network configured on the cloud platform, the DVS can set a VLAN
Trunk list on the added port to implement the VLAN Trunk function.
Feature Description
The DVS provides the packet statistics function based on ports and service flows, and
displays statistical information for users through the network management system
interface.
Feature Description
The DVS periodically detects the statuses of physical ports. When the status of a port
changes from UP to DOWN, the DVS reports an alarm indicating that the port is down.
When the status of the port changes from DOWN to UP, the DVS clears the alarm.
Alarms are reported to TECS network management system.
On the DVS, proper packet loss thresholds are set based on the port statistics
information. When the network traffic is overloaded, which means that a packet loss rate
is greater than the corresponding threshold, an abnormal traffic alarm is raised and sent
to TECS network management system, so that traffic load can be adjusted for services.
The DVS monitors the negotiated rate of each physical NIC in the service network. If the
auto-negotiation rate of a service NIC is less that the maximum rate of the port, an auto-
negotiation rate alarm of the port is raised and reported to TECS network management
system.
Feature Description
Resource configurations include the core resource configuration and flow table amount
configuration. In the default scenario, a DVS occupies three physical CPU cores and
supports a flow table of 1 MB. Resources can be configured for virtual switches in
accordance with the application scenarios, including the number of physical CPU cores
and the number of flow tables.
Feature Description
Users can query basic information about each VM in command line mode or through
Web pages, including the operational status, detailed specifications, IP address,
physical host information and domain information of each VM.
Feature Description
Through the flexible tenant quota management, administrators can query the resource
quota limit and resource usage of each tenant, and set the resource quota of each
tenant based on the requirements and planning. Tenants can only query their own
resource quota limits and resource usage.
Feature Description
This feature helps system administrators normalize VM templates and create VMs
through templates (flavor).
Feature Description
Creating a VM refers to a procedure in which the system creates one Guest OS through
an image, and allocates the corresponding resources to it as needed.
Deleting a VM refers to a procedure in which the system removes the VM and reclaims
the resources occupied by the VM.
Starting, shutting down, and restarting a VM are the basic VM management functions,
which are the same as the basic management operations of physical machines.
After a VM is locked, only administrators can operate this VM. Only administrators can
unlock VMs.
Feature Description
VMs on a host can be migrated to other hosts before host maintenance, reducing
service interruption.
VMs on a busy host can be migrated to idle hosts, improving the VM user experience
and implementing global service balancing.
Feature Description
This feature displays physical devices and their relationships through topologies, and
the status of blades and switches in shelves.
Feature Description
The hypervisor virtualizes the physical CPU of a physical server to several vCPUs for
VMs. When multiple vCPUs are operating, the hypervisor dynamically schedules the
physical CPU among vCPUs.
Feature Description
After a VM is deployed, the processes corresponding to the vCPU of the VM always run
on a logic CPU. The operating system preferentially selects the vCPU-corresponding
local memory for the VM, improving the memory access rate.
Enhancement
After a VM is deployed, the VM is running on a logic CPU, and the operating system
preferentially uses the local memory. Because the VM-corresponding vCPU process is
not bound to a fixed logic CPU, the operating system allocates different logic CPUs to
the vCPU of the VM if load changes, but the memory data of the vCPU process will not
be moved to the local memory corresponding to the new logic CPU. In this case, the VM
may access remote memory. In view of this situation, the vCPU corresponding to the VM
is bound to a fixed logic CPU during the deployment of the VM, so the local memory will
Feature Description
Enhancement
Physical machines provide different sizes of huge pages. The required huge page size
can be selected for a VM during deployment. The VM is preferentially deployed on the
physical machine with the specified page size. If there is no physical machine providing
the specified page size, a physical machine with a different page size is selected for
deploying the VM.
Feature Description
When a physical network is created on TECS system, two physical NICs can be
selected for the physical network, and the link aggregation mode can be set to Backup
mode or ON mode in accordance with the network requirements.
When a port is created, the port type must be set to bond. After a VM is created, two
network interfaces with the same MAC address can be viewed within the VM. After the
two network interfaces are aggregated in the VM, they can be used.
If the status of a physical network interface changes, the network interfaces within the
VM change their statuses automatically.
For the port aggregation function in backup mode, TECS select one physical NIC as the
active NIC. The VM actively queries the current active NIC of TECS.
Feature Description
TECS introduces the concept of virtual subnet. Multiple virtual subnets can be created
on a virtual network. During the creation of a subnet, the subnet mask, subnet IP
address, and the range of IP addresses that can be assigned to VMs can be specified.
If subnets are configured on the network that the interface of a VM is connected to, the
VM interface automatically assigns an IP address within the available IP address range
to the VM. Users can also specify IP addresses to VMs if they do not want to use the
system-allocated IP addresses.
Feature Description
Virtual network creation: creates a new virtual network with the specified
parameters such as the network name and management status.
Virtual network update: edits the attributes of a virtual network, including the
network name and management status.
Virtual network listing: displays all virtual networks. Networks can by queried by
name.
Feature Description
Virtual subnet deletion: removes a virtual subnet. A virtual subnet is removed after
the system withdraws the occupied resources from the subnet.
Virtual subnet update: edits the attributes of a virtual subnet, including the subnet
name, IP address of the gateway, allocation pool, DNS, and host route.
Virtual subnet listing: displays all virtual subnet information of a network, including
the ID, name, network segment, and available address range of each virtual
subnet.
Feature Description
This feature supports the creation and deletion of volumes on disk array storage back-
ends (decided by the cinder volume drive configuration), and volume mounting and
unloading on VMs.
Created from a mirror image: In this mode, a cloud system disk that can initiate a
cloud host is created.
Created from a snapshot: In this mode, a new volume is created from a volume
snapshot. This method is usually used to restore data from a snapshot.
Created from a source volume: also called volume cloning. This method is used to
create a complete copy of the source volume.
Feature Description
A volume type is used to describe some specific attributes of volumes. These attributes
are represented by some key-values pairs. For example, to select a storage back end
from multiple storage back ends, the volume_backend_name attribute of the volume
type needs to be set. The system selects the corresponding storage back end in
accordance with the back end name specified by this attribute. To create volumes with
the same attributes, a volume type with these attributes can be defined first. Users can
specify the volume type when creating volumes, so the volumes have the corresponding
attributes.
Feature Description
This feature can efficiently control the storage resource use of tenants. Users can set,
view, and modify the quota settings. When the storage resources used by a tenant
exceed the upper limit, the tenant fails to create volumes.
Feature Description
The TECS system supports mainstream browsers compatible with HTML5, including
Internet Explorer9 or later, Chrome 21 or later.
Feature Description
TECS system provides centralized management and storage of alarms and alarm
clearing information of each system component, and reports them to the external
network management system in real time by SNMP trap. The current alarms include
computing, storage, and network.
Feature Description
Feature Description
Feature Description
CPU usage of a VM
VM disk IO
VM NIC IO
Feature Description
A PXE server or USB can be made through the version issued by ZTE to install an
operating system for each node.
Feature Description
After an operating system is installed on each node, the configuration and TECS system
installation can be implemented on one node. The system automatically installs required
software packages on other nodes to complete TECS installation.
Enhancement
Feature Description
When a fault occurs, the system can report a hardware alarm to the network
management system, and the alarm can be cleared properly.
For example, when a fan is removed from a ZTE E9000, a hardware alarm indicating the
removal of the shelf fan is reported. When the fan is installed in the slot again, the
previous alarm is cleared from the active alarms and moved to the historical alarms.
Feature Description
Performance tasks can be created by granularity for performance data of blade server
(E9000) and disk array (KS3200).
Feature Description
This feature allows creating users, assigning projects and permissions to users, deleting
users, modifying user attributes, querying all users or part of users by user name or user
ID, disabling users, and activating users.
Feature Description
The system allows control nodes to operate in active/standby two-server mode. The
active node externally provides services through floating IP addresses. The active node
provides the following functions:
Monitors disks through the accessibility of the file system and disks, ensuring that
external users can use the files and storage services.
Monitors the operating system through Watchdog, and resets the current node
when the operating system kernel is crashed or dead, ensuring that each node on
which the operating system is operating properly can externally provide services.
Monitors the service program through the two-server cluster software, and restarts
the service program or switches the service program to another node when the
service program operates improperly, ensuring that the service program can
continuously provide services to the outside.
Feature Description
The feature gets the measurement results of the measurement objects from its
managed cloud environment.
Users can set QoS alarms. If a performance indicator exceeds a preset threshold, the
system raises an alarm.
Feature Description
The feature gets the current status of the computing resources, storage resources,
network resources, and virtual resources from the managed cloud environment. Users
can export historical monitoring data.
Feature Description
Active alarm: Users can browse or query active alarms based on the specified
conditions.
Historical alarm: Users can view cleared alarms and set the number of days to
retain historical alarms.
Alarm clearance: Users can manually clear alarms. Cleared alarms are stored in
historical alarm library, and are not presented as active alarms.
Alarm export: All or selected alarms can be exported to an EXCEL or CSV file.
Feature Description
This feature is easy for users to collect, store, and query logs. It automatically collects
operation and maintenance logs and service logs, and manages all logs through a
project.
4.5 Dashboard
Feature Description
This feature enables users to quickly determine the usage of the system. Users can
select information to display on the dashboard.
Feature Description
This feature displays physical devices and their relationships through topologies, and
the status of blades and switches in shelves.
This feature allows creating users, assigning projects and permissions to users, deleting
users, modifying user attributes, querying all users or part of users by user name or user
ID, disabling users, and activating users.