Download the document - Support

Huawei FusionSphere 5.1
Technical White Paper on
Advanced Operation Functions
Issue
V1.0
Date
2015-04-15
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.
Address:
Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://enterprise.huawei.comhttp://www.huawei.com/
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
i
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
About This Document
About This Document
Purpose
This document describes advanced operation functions of FusionSphere.
Intended Audience
This document can be used by Huawei marketing and sales engineers, and FusionSphere
distributors in their market development projects.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, could result in death or serious injury.
Indicates a potentially hazardous situation which, if not
avoided, may result in minor or moderate injury.
Indicates a potentially hazardous situation which, if not
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and
tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
ii
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
About This Document
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue V1.0 (2015-04-15)
This issue is the first official release.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
iii
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
Contents
Contents
About This Document .................................................................................................................... ii
1 Overview......................................................................................................................................... 1
1.1 Challenges Facing Data Center Management ............................................................................................................... 1
1.2 Design Concepts and Principles for FusionSphere Management ................................................................................. 2
2 Global Resource Management ................................................................................................... 5
2.1 Multi-DC Resource Management ................................................................................................................................. 5
2.2 Zone Management ........................................................................................................................................................ 6
2.3 SLA-based Resource Scheduling .................................................................................................................................. 6
2.4 Centralized Resource Monitoring ................................................................................................................................. 7
3 Service Management .................................................................................................................... 9
3.1 Service Definition ......................................................................................................................................................... 9
3.2 Service Catalog ............................................................................................................................................................. 9
3.2.1 Out-of-the-Box Service Catalog .............................................................................................................................. 10
3.2.2 Orchestration Service Customization ...................................................................................................................... 11
3.3 Service Operations ...................................................................................................................................................... 11
3.4 Application Form Management .................................................................................................................................. 11
4 Application Life Cycle Management ...................................................................................... 13
4.1 Application Summary ................................................................................................................................................. 14
4.2 Application Template Orchestration ........................................................................................................................... 14
4.3 Automatic Application Deployment ........................................................................................................................... 16
4.4 Application Monitoring............................................................................................................................................... 16
4.5 Elastic Scalability ....................................................................................................................................................... 18
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
iv
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
1 Overview
1
Overview
1.1 Challenges Facing Data Center Management
REF _Ref423705734 \r \h Figure 1-1 lists challenges facing data center management.
Figure 1-1 Challenges facing data center management
Poor Service Quality
IT problems are difficult to locate and rectify. Over 20% faults can be rectified in more than
one day.
Traditional data centers (DCs) have no unified and open management platform. As a result,
resources cannot be managed in a centralized manner to support diversified applications.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
1
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
1 Overview
Inefficient Service Management
The service deployment of a traditional DC usually starts from the underlying layer. The
hardware installation phase is long and basic configuration is complicated. Therefore, the
service rollout usually takes more than 90 days, resulting in slow response to service
development requirements.
Complex Management and High Costs
Traditional DCs have no unified standards and planning. As a result, hardware resources
cannot be managed or shared in a centralized manner.
Network systems become increasingly complex. Therefore, a large number of professional
O&M personnel are needed to meet customers' requirements.
System maintenance consumes a large amount of resources. According to statistics, more than
70% of IT budgets are used for system maintenance, instead of deploying new IT systems.
Three or more management tools are adopted in 70% DCs, which raises customer
requirements for O&M personnel.
DCs are developed based on the cloud computing technology. Lacking of O&M experience,
traditional enterprises can improve their capabilities only after countless practices.
Low Resource Utilization
Resource usage in traditional DCs is generally less than 20%, which indicates that a large
number of resources are left idle. In addition, these idle servers constantly consume energy,
undermining customer profitability.
Global resource coordination and scheduling cannot be implemented in distributed DCs,
leading to unbalanced resource utilization in different sites. In this case, many unavailable
resource fragments are created.
1.2 Design Concepts and Principles for FusionSphere
Management
Easy to Use
The system provides graphical user interfaces (GUIs) on which users can easily find desired
operations and information. Operations steps are arranged based on a human-centered design,
and detailed help information is provided.
Information displayed on the GUI varies depending on roles assigned to users. Advanced
features that are seldom used are displayed by options.
More than 90% tasks require less than three steps. A wizard-based guide is provided for tasks
requiring more than five steps.
The system responds to users' operations in less than 3 seconds.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
2
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
1 Overview
Heterogeneous Compatibility
FusionSphere centrally manages hardware devices from different vendors using internal
information buses, unified open interfaces, and flexible adapter plug-ins. Plug-ins are used to
integrate third-party management systems to support traditional devices.
FusionSphere also manages virtualization platforms that are provided by various
manufacturers. Virtualization platforms that are provided by various vendors, such as
VMware and Huawei FusionSphere, are managed in a unified manner.
Unified Portal
The unified management portal (UMP) provides a single sign-on (SSO) entry for various
management subsystems and also integrates the entries to customers' existing management
systems. In addition, the UMP provides diversified customizable dashboards, on which users
can view desired data center management indicators.
Centralized Management
Physical and virtual resources in a single or multiple distributed data centers can be managed
in a centralized manner.
Flexible Customization
Plug-ins are used to extend southbound interface capabilities, allowing customers' existing IT
systems to connect to the FusionSphere system.
Customers can self-define service catalogs, resource models, resource views, and scheduling
policies. Plug-ins are used to extend scheduling policies and service types.
Resources and services can be flexibly orchestrated to implement unified scheduling of
computing, storage, and network resources.
Visualized processes are designed, and process nodes are extended using plug-ins, meeting
various users' service needs.
Smooth Expansion
Designed with high performance and large capacity, the system is scalable and supports a
large number of concurrent users.
Open Standards
The system adopts the service oriented architecture (SOA) and provides the open application
programming interface (API) to connect to third-party systems. The system designed based on
an open architecture complies with international and industry standards and accommodates
mainstream OSs, web middleware, and databases in the industry. These features ensure that
the system can be updated and migrated at any time.
Componentization and Loose Coupling
Components in the system are loosely coupled. Upgrades and changes of a component do not
affect other components.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
3
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
1 Overview
High Reliability
The system features high availability and reliability. The system uses high-availability
two-node cluster technology and traffic control and overload protection mechanisms. The
system also adopts the system reliability architecture design at all levels from the hardware,
network, and software. In this case, the system can provide high-performance data processing
and application response capabilities, ensuring the efficient running of all types of
applications and databases and supporting the access of a large number of users.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
4
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
2
2 Global Resource Management
Global Resource Management
The global resource management platform supports automatic cloud service management and
intelligent resource operation and maintenance. It aims at providing simple and agile
management of cloud data centers for users.
Figure 2-1 shows the page for global resource management.
Figure 2-1 Global resource management page
2.1 Multi-DC Resource Management
Figure 2-2 shows the management functions of multi-DC resources.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
5
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
2 Global Resource Management
Figure 2-2 Multi-DC resource management

Multiple cloud resource pools in multiple data centers can be added to the system. The
resource pool type can be OpenStack or FusionCompute.

FusionManager sets up a unified model for various resource pools. The upper-layer
applications are not aware of the supporting physical devices or virtualization platforms.

The system discovers the managed physical devices and networking, and manages the
resource pools.

The system improves device resource utilization and deployment flexibility, and reduces
O&M costs.

The system uses the southbound plug-in mechanism to allow rapid and flexible device
deployment.
2.2 Zone Management
In a physical layer 2 network where computing and storage resources are shared, the
administrator can divide the computing, storage, and network resources into multiple
availability zones (AZs) based on the usage. An AZ can contain one or multiple resource
clusters (or host aggregates).

The virtual data centers (VDCs) are defined using the software and created across
physical data centers.

The networks are isolated from each other. The organization function enables various
departments to use cloud resources independently.

AZs are securely divided based on user rights and domains.
2.3 SLA-based Resource Scheduling
A resource pool can contain computing and storage resources of multiple service level
agreement (SLA) levels. The SLA level can be specified when a VM or disk is applied for.
For example, multiple RAID levels (RAID2, RAID 5, RAID 10) of storage pools can be
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
6
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
2 Global Resource Management
created. Tenants can specify the RAID level of disks. Figure 2-3 shows the SLA-based
resources in FusionSphere.
Figure 2-3 SLA-based resources in FusionSphere
2.4 Centralized Resource Monitoring
The resource utilization (total capacity, used capacity, and usage) of each availability zone
(AZ) is monitored in a centralized manner. Figure 2-4 shows the usage of each resource.
Figure 2-4 Usage of each resource
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
7
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
2 Global Resource Management

FusionManager monitors cluster performance and allows administrators to view cluster
performance monitoring results by week, month, year, or a specified period of time. The
performance indicators include the average CPU usage trend comparison, average
memory usage trend comparison, average network traffic trend comparison (outgoing
flow), average network traffic trend comparison (incoming flow), and alarm statistics.

Server: FusionManager monitors the performance of CPU usage, memory usage,
incoming and outgoing network traffic, and disk input/output (I/O) read and write. You
can query performance measurement results by year, month, week, or a specified period
of time. You can also query the alarm statistics, including status, network ports, power
supplies, and fans of a server.

VM: FusionManager monitors VM performance and allows administrators to view VM
performance monitoring results by week, month, year, or a specified period of time. The
performance indicators include the CPU usage, memory usage, network flow rate, and
disk I/O.

Switch: FusionManager monitors switch status and traffic on switch ports.
FusionManager also monitors port connection status, transmit rates, packet loss rates,
and packet error rates in both the sending and receiving directions.

Storage device: FusionManager monitors total capacity, available capacity, remaining
traffic, mounted data, and alarm statistics of storage devices.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
8
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
3
3 Service Management
Service Management
3.1 Service Definition
Services are resource templates provided for users, including VDCs, elastic cloud servers
(ECSs), application instances, and disks.
Domain Service Manager defines service catalogs as required. The following items can be
defined:

Service name, description, and icon

Service parameters that can be customized when users apply for services (For example,
users can customize VM specifications when applying for VM services.)

Service parameters that can be configured during administrator approval (For example,
an administrator can configure a static IP address for the VM that a user applies for.)

Service parameters that are locked (For example, if Windows 7 is locked for a VM, the
user cannot customize the OS type for the VM.)

Service approval policy: Service approval is required or not.
3.2 Service Catalog
The service catalog is a set of services, including pre-defined and customized services. Figure
3-1 shows the service catalog page.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
9
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
3 Service Management
Figure 3-1 Service catalog page
3.2.1 Out-of-the-Box Service Catalog
The service catalog pre-defined in the FusionSphere system is an out-of-the-box one and
allows users to quickly deploy resources and applications based on service requirements. The
pre-defined service catalog includes:

VDC
A VDC provides user experience equivalent to what provided by a physical data center.
Users can rapidly apply for a VDC and flexibly adjust the VDC specifications online as
required. In a VDC, users can centrally manage computing, storage, and network
resources just like managing a real data center.

ECS
ECS services provide on-demand VM services for users. Users can apply for CPUs,
memory, hard disks, and NICs, as well as ECSs of various OS types to fulfill all kinds of
computing requirements.
Compared with traditional physical server services, ECS services enjoy advantages of
easy deployment, demand-oriented application and expansion, and high resource usage
rate.

EVS
Combined with ECS, elastic volume service (EVS) provides persistent block storage
services. The life cycle of a cloud hard disk is independent from that of the ECS. A cloud
hard disk can be attached to an ECS of the same AZ or detached from the ECS. Users
can specify the specifications and storage SLA when applying for an ECS. For example,
users can specify the storage media, which can be SATA, SAS, and SSD or Any. Storage
SLA options are defined by the administrator during the resource pool configuration.

Dedicated server
Some applications that cannot run on ECSs run on dedicated servers, such as some big
data analysis services, which require shorter network I/O delay than services on the
ECSs. A user can directly apply for dedicated servers on the service catalog, and the
administrator assigns the dedicated server that is configured to the users.

Issue V1.0 (2015-04-15)
Elastic IP address
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
10
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
3 Service Management
An elastic IP address is a static public IP address. You can associate an elastic IP address
with an ECS. Users can access the ECS through the Internet using the elastic IP address.
If the associated ECS is faulty or needs to be upgraded, you can quickly associate its
elastic IP address with another ECS that is running properly without modifying the ECS
configurations, thereby ensuring service continuity.
3.2.2 Orchestration Service Customization
The system pre-defines the VDC, VMs, disks, applications, and physical servers. It also
provides the backup, VPC, network, LB, router, firewall, VPN, and ACL functions. In some
cases, customers may require a new type of service such as midrange computers, or their own
service processes cannot meet their actual needs. To meet these requirements, advanced
operation functions of FusionSphere 5.1 provide the service process orchestration tool and
service development guide to help expand resource management services for customization
developers. For example, customers' existing IT systems can be integrated with the service
provisioning process.
3.3 Service Operations

Service application
Tenants can view services on the service catalog, submit the service application, specify
the validity duration when applying for services, and specify service specifications. The
application progress can be tracked using the application form.
Tenants can select a service template based on application requirements and configure
the network and administrator. These operations enable rapid application deployment.
Tenants can create an application by performing a one-click operation and query the
deployment report and creation progress.

Service change
Tenants can submit applications to change the service validity duration and the service
specifications.

Service release
Tenants can release services that are not required any more. The VDC Service Manager
or Domain Service Manager can also release resources after the services expire.

Service approval
The VDC Service Manager can approve the service applications submitted by users in
the VDC. The Domain Service Manager can approve the VDC service application
submitted by the VDC Service Manager. The approver can not only select approval or
refusal, but also set some service parameters, such as the network used by the VMs (the
parameters that can be set are configured in the service customization phase).

Service maintenance
Tenants can maintain the services that have been applied for, such as logging in to a VM
using VNC, powering on or powering off a VM, binding the elastic IP address to a VM.
3.4 Application Form Management
Tenants and managers can query the application status and requested applications. Figure 3-2
shows the page for querying the application status and request.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
11
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
3 Service Management
Figure 3-2 Application status and request querying page
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
12
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
4
4 Application Life Cycle Management
Application Life Cycle Management
FusionSphere provides a service-centered automatic orchestration platform to manage the
entire lifecycle of applications after provisioning resources for the applications. The
orchestration platform is able to automatically manage data center resources by performing a
whole series of orchestration actions, including application development, modeling,
monitoring, and elastic scaling.
Figure 4-1 Application life cycle management
FusionSphere provides an easy-to-use application template, in which you can define your
custom SDN network, physical server, VM, software, and database settings based on the
service requirements. The template can be used to create an application instance to provide
the services defined in the template. You can build a test environment that provides Oracle
database services or build a small-sized branch office environment that provides ERP and OA
services.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
13
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
4 Application Life Cycle Management
4.1 Application Summary
On the Application Summary page, you can view the deployment details of application
instances and application templates in a VDC, or create an application template or application
instance according to the instructions.
Figure 4-2 Application summary page
4.2 Application Template Orchestration
Administrators can orchestrate complex, multi-tier applications using a graphical application
template editor. A tested application template can be used to publish a service catalog.
An application template is a combination of VM templates, software packages, scaling groups,
and script resources, enabling rapid application instance deployment. Administrators drag the
software packages and scripts to a VM template when editing an application template. When
creating the VM during application deployment, the system automatically uploads and
executes the scripts in the VM template.
An application template includes a VM template and a service template.

Issue V1.0 (2015-04-15)
VM template: Administrators can create various VM templates and customize the OSs,
specifications, and software deployed on the VMs. Figure 4-3Figure 4-3 shows the page
for creating VM templates.
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
14
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
4 Application Life Cycle Management
Figure 4-3 VM template creation page

Service template: Administrators can publish an application using a service template, or
design an application template using the service template design tool to drag the required
icons and drop them into the template, as shown in Figure 4-4.
Figure 4-4 Service template editing page
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
15
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
4 Application Life Cycle Management
4.3 Automatic Application Deployment
An application template can be used to deploy multi-node complex applications using one
click. During the deployment process, the system automatically creates an ECS, installs the
OS and application software, and configures virtual networks and application scaling policies,
as shown in Figure 4-5.
Figure 4-5 Application deployment process
The following operations can be automatically executed by one-click application deployment
using an application template:
1.
Create an ECS.
2.
Configure storage for the ECS.
3.
Configure networks for the ECS.
4.
Install software packages on the ECS.
5.
Run the initial scripts on the ECS.
6.
Automatically create a scaling group and add the ECS to the scaling group.
7.
Automatically create a load balancer and add the ECS to the scaling group.
4.4 Application Monitoring
After creating an application, users need to perform routine maintenance for the application to
ensure that the application stably provides services. FusionManager supports application
process and ECS monitoring, which enables tenants to learn application running information
in real time, so they can handle exceptions in a timely manner to ensure that the services run
stably.
An agent is not required when the ECS on which the applications are running is monitored.
The system collects the CPU, memory, disk I/O, and network I/O information of the ECS
during the monitoring process. When application processes are monitored, users need to
deploy the Hyperic HQ Agent on the ECS. REF _Ref425502598 \r \h Figure 4-6 shows the
application monitoring solution.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
16
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
4 Application Life Cycle Management
Figure 4-6 Application monitoring solution
The application process monitoring supports the capabilities listed in Table 4-1, and the
plug-ins must be customized and developed to support new capabilities.
Table 4-1 Default objects supported by application monitoring
SN
Object Type
Object
1
OSs
AIX, HP-UX, Solaris, Linux, Windows, Mac OS X, and
FreeBSD
2
Application
servers
BEA WebLogic, IBM WebSphere, JBoss, Apache,
Macromedia ColdFusion, Macromedia JRun, Microsoft .NET
Framework Runtime, Tomcat, Glassfish, and Caucho Resin
3
Information
middleware
RabbitMQ and WebSphere MQ
4
Microsoft
products
MS Exchange, MS Active Directory, and Microsoft .NET
Framework
5
Network
management
products
Alfresco, Bind, MemCached, Nagios, and NTP
6
Application
platforms
LAMP and J2EE
7
Web servers
Apache, Microsoft IIS, and Sun ONE Web Server
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
17
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
4 Application Life Cycle Management
SN
Object Type
Object
8
Databases
IBM DB2, Microsoft SQL Server, MySQL, Oracle,
PostgreSQL, and Sybase
9
Virtualization
product
XenSource
10
Mail server
Postfix
11
Integrated
applications
ColdFusion and Alfresco
The monitored KPIs of the objects mainly process event-related statistical indicators. For
details, see the KPI information of the in-use plug-ins.
4.5 Elastic Scalability
Administrators can configure resource scheduling policies for different application instances.
FusionManager automatically adjusts resources for the application instances based on the
policies. After automatic scheduling policies are configured, the system scales applications up
or down based on the configured policies and application resource usages, thereby achieving
optimal resource utilization. Automatic scaling policies include intra-group scaling policies
and scheduled task policies.

Automatic intra-group scaling policies
Intra-group scaling policies apply to only one application. The system automatically adds
ECSs for an application instance if the following indicators of the application instance
are high: CPU usage, memory usage, disk write speed, disk read speed, network inbound
flow rate, or network outbound flow rate. The system also installs application software
for the ECSs to reduce the overall resource load of the application instance and ensure
proper running of the applications. When detecting that the resources of an application
instance are underused, the system automatically removes ECSs from the application
instance to release resources.

Scheduled task policies
Scheduled task policies apply to a scaling group. The time-based scheduling policies
allow resources to be assigned to different application instances at different time periods.
Users can set scheduled task policies so that different applications use system resources
in different periods. For example, ECSs for daily office work use resources in the
daytime, and the resources are allocated to public ECSs at night. Table 4-2 lists the
scheduled task capabilities supported by the system.
Table 4-2 Scheduled task capabilities
Parameter
Description
Startup time
Specifies the time when a policy is started.
End time
Specifies the time when a policy is stopped.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
18
Huawei FusionSphere 5.1
Technical White Paper on Advanced Operation Functions
4 Application Life Cycle Management
Parameter
Description
Execution mode
Specifies the mode of executing a scaling task. A scaling
task can be executed only once, multiple times, or
periodically.
Execution times
Specifies the number of times for executing a scaling
task. This parameter takes effect only when the task
execution mode is set to multiple times.
Interval
Specifies the interval at which the system executes the
specified scaling task. The interval can be set to daily or
weekly. This parameter takes effect only when the
interval is set to periodically.
Task ID
Specifies the ID of the task for executing a scaling task.
Issue V1.0 (2015-04-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
19