GB/T 38633-2020 English PDF (GB/T38633-2020)

GB/T 38633-2020: Information technology - Big data - Functional requirements for system operation and management
Delivery: 9 seconds. Download (& Email) true-PDF + Invoice.
Get Quotation: Click GB/T 38633-2020 (Self-service in 1-minute)
Historical versions (Master-website): GB/T 38633-2020
Preview True-PDF (Reload/Scroll-down if blank)

GB/T 38633-2020
GB
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 35.240
L 67
Information technology - Big data - Functional
requirements for system operation and management
ISSUED ON: APRIL 28, 2020
IMPLEMENTED ON: NOVEMBER 01, 2020
Issued by: State Administration for Market Regulation;
Standardization Administration of the People’s Republic of
China.
Table of Contents
Foreword ... 3 
1 Scope ... 4 
2 Normative references ... 4 
3 Terms and definitions ... 4 
4 Abbreviations ... 5 
5 Overview ... 5 
6 Installation and deployment ... 5 
7 Configuration management ... 6 
8 Tenant management ... 8 
9 Monitoring and alarm management ... 8 
10 Service management ... 9 
Information technology - Big data - Functional
requirements for system operation and management
1 Scope
This Standard specifies the operation, maintenance and management
functional requirements of big data systems.
This Standard applies to the design, development and testing of the operation,
maintenance and management functions of big data systems.
2 Normative references
The following documents are indispensable for the application of this document.
For dated references, only the dated version applies to this document. For
undated references, the latest edition (including all amendments) applies to this
document.
GB/T 35295-2017, Information technology - Big data - Terminology
GB/T 38673-2020, Information technology - Big data - Basic requirements
for big data systems
3 Terms and definitions
Terms and definitions determined by GB/T 35295-2017 and the following ones
are applicable to this document.
3.1 Component service
One or more capabilities that are provided by components in the big data
system.
3.2 Role
A carrier that carries one or more permissions.
3.3 Instance
A specific representation of a service, including one or more resources.
3.4 Node
f) It shall support system deployment (installation/repair/upgrade) failures
and provide repair methods, such as retry, rollback;
g) It shall support the installation/upgrade operation of the system to be fault-
tolerant, and the entire process shall not fail due to the failure of individual
nodes;
h) It shall support the ability to automatically open up private SSH for nodes
in the cluster;
i) It shall support the ability to automatically identify, format, and mount
various types of disks;
j) It shall have the ability to set up quick recovery of service after the power
failure of the computer room is restored;
k) It shall support multiple clusters and multiple services;
l) It shall support the pre-integration of development kits, databases, identity
authentication and other components;
m) It shall support docking with third-party management platforms or provide
open APIs, to facilitate the access of user-defined service components;
n) It shall support the active and standby deployment of management nodes;
the failure of the master node does not affect external functions;
o) It shall support automatic switching between the active and standby nodes;
when the active node fails, the standby node takes the initiative to take
over the services of the active node;
p) It shall provide a data synchronization mechanism for active and standby
nodes;
q) It should support adding and deleting nodes without restarting the cluster;
r) It should support the setting of data balance, to avoid placing the new data
on the new node after adding a new node in the cluster;
s) It should support multiple granular system upgrades or repairs without
interrupting business;
t) It should support the automatic reinstallation of the system.
7 Configuration management
The configuration management functional requirements are as follows:
8 Tenant management
The tenant management functional requirements are as follows:
a) It shall support the management of tenant permissions in the form of roles,
users, and user groups;
b) It shall provide a graphical interface to manage roles, users, and user
groups;
c) It shall support permission control to resources in the service, such as
tables, directories, files and other resources;
d) It shall support tenant management, including deletion, creation;
e) It shall support single sign-on between the system and components, and
single sign-on between the system and third-party systems.
9 Monitoring and alarm management
The monitoring and alarm management functional requirements are as follows:
a) It shall support the monitoring of multi-dimensional operation and
maintenance objects such as clusters, hosts, services, and instances;
b) It shall support the monitoring of cluster size, resource usage, resource
operating status;
c) It shall support the customization of service and service component
monitoring indicators;
d) It shall support the customized functions of monitoring items, including
display methods, visual monitoring items;
e) It shall support various display methods of monitoring items, including
graphics, tables, timelines;
f) It shall support management functions such as exporting, archiving and
cleaning of monitoring data;
g) It shall support the function of generating and exporting monitoring data
visualization reports, including manual and automatic methods;
h) It shall support graphical interface to view monitoring and alarms, and
support to view by different keywords;
h) It shall support the ability to horizontally shrink/expand distributed services;
i) It shall support the availability of testing services and send alerts when
problems are found;
j) It shall support the integration of the native UI of open source components
that are based on open source big data systems;
k) It shall support the upper-layer service linkage to stop or restart together
or give a prompt, when a service is stopped or restarted;
l) It shall support the restart of a single service through various strategies
(such as batches, active and standby in turn, etc.) without interrupting the
business;
m) It shall support the download of service client;
n) It shall support the service and data to be automatically restored to the
newly added or replaced server.
11 Health inspection
The health inspection functional requirements are as follows:
a) It shall support regular automatic inspections and manual inspections;
b) It shall support regular inspections of the health of the network, servers,
operating systems and services;
c) It shall support inspection according to the scenario, such as inspection
before upgrade;
d) It shall support the output of inspection reports;
e) It should provide an interface-based automatic inspection service of the
system operating environment.
12 Log management
The log management functional requirements are as follows:
a) It shall provide the collection and storage functions of various logs, such
as operation logs, operational logs;
b) It shall provide management functions of the log directory, such as the
change of log storage space, the change of log storage directory;
GB/T 38633-2020
GB
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 35.240
L 67
Information technology - Big data - Functional
requirements for system operation and management
ISSUED ON: APRIL 28, 2020
IMPLEMENTED ON: NOVEMBER 01, 2020
Issued by: State Administration for Market Regulation;
Standardization Administration of the People’s Republic of
China.
Table of Contents
Foreword ... 3 
1 Scope ... 4 
2 Normative references ... 4 
3 Terms and definitions ... 4 
4 Abbreviations ... 5 
5 Overview ... 5 
6 Installation and deployment ... 5 
7 Configuration management ... 6 
8 Tenant management ... 8 
9 Monitoring and alarm management ... 8 
10 Service management ... 9 
Information technology - Big data - Functional
requirements for system operation and management
1 Scope
This Standard specifies the operation, maintenance and management
functional requirements of big data systems.
This Standard applies to the design, development and testing of the operation,
maintenance and management functions of big data systems.
2 Normative references
The following documents are indispensable for the application of this document.
For dated references, only the dated version applies to this document. For
undated references, the latest edition (including all amendments) applies to this
document.
GB/T 35295-2017, Information technology - Big data - Terminology
GB/T 38673-2020, Information technology - Big data - Basic requirements
for big data systems
3 Terms and definitions
Terms and definitions determined by GB/T 35295-2017 and the following ones
are applicable to this document.
3.1 Component service
One or more capabilities that are provided by components in the big data
system.
3.2 Role
A carrier that carries one or more permissions.
3.3 Instance
A specific representation of a service, including one or more resources.
3.4 Node
f) It shall support system deployment (installation/repair/upgrade) failures
and provide repair methods, such as retry, rollback;
g) It shall support the installation/upgrade operation of the system to be fault-
tolerant, and the entire process shall not fail due to the failure of individual
nodes;
h) It shall support the ability to automatically open up private SSH for nodes
in the cluster;
i) It shall support the ability to automatically identify, format, and mount
various types of disks;
j) It shall have the ability to set up quick recovery of service after the power
failure of the computer room is restored;
k) It shall support multiple clusters and multiple services;
l) It shall support the pre-integration of development kits, databases, identity
authentication and other components;
m) It shall support docking with third-party management platforms or provide
open APIs, to facilitate the access of user-defined service components;
n) It shall support the active and standby deployment of management nodes;
the failure of the master node does not affect external functions;
o) It shall support automatic switching between the active and standby nodes;
when the active node fails, the standby node takes the initiative to take
over the services of the active node;
p) It shall provide a data synchronization mechanism for active and standby
nodes;
q) It should support adding and deleting nodes without restarting the cluster;
r) It should support the setting of data balance, to avoid placing the new data
on the new node after adding a new node in the cluster;
s) It should support multiple granular system upgrades or repairs without
interrupting business;
t) It should support the automatic reinstallation of the system.
7 Configuration management
The configuration management functional requirements are as follows:
8 Tenant management
The tenant management functional requirements are as follows:
a) It shall support the management of tenant permissions in the form of roles,
users, and user groups;
b) It shall provide a graphical interface to manage roles, users, and user
groups;
c) It shall support permission control to resources in the service, such as
tables, directories, files and other resources;
d) It shall support tenant management, including deletion, creation;
e) It shall support single sign-on between the system and components, and
single sign-on between the system and third-party systems.
9 Monitoring and alarm management
The monitoring and alarm management functional requirements are as follows:
a) It shall support the monitoring of multi-dimensional operation and
maintenance objects such as clusters, hosts, services, and instances;
b) It shall support the monitoring of cluster size, resource usage, resource
operating status;
c) It shall support the customization of service and service component
monitoring indicators;
d) It shall support the customized functions of monitoring items, including
display methods, visual monitoring items;
e) It shall support various display methods of monitoring items, including
graphics, tables, timelines;
f) It shall support management functions such as exporting, archiving and
cleaning of monitoring data;
g) It shall support the function of generating and exporting monitoring data
visualization reports, including manual and automatic methods;
h) It shall support graphical interface to view monitoring and alarms, and
support to view by different keywords;
h) It shall support the ability to horizontally shrink/expand distributed services;
i) It shall support the availability of testing services and send alerts when
problems are found;
j) It shall support the integration of the native UI of open source components
that are based on open source big data systems;
k) It shall support the upper-layer service linkage to stop or restart together
or give a prompt, when a service is stopped or restarted;
l) It shall support the restart of a single service through various strategies
(such as batches, active and standby in turn, etc.) without interrupting the
business;
m) It shall support the download of service client;
n) It shall support the service and data to be automatically restored to the
newly added or replaced server.
11 Health inspection
The health inspection functional requirements are as follows:
a) It shall support regular automatic inspections and manual inspections;
b) It shall support regular inspections of the health of the network, servers,
operating systems and services;
c) It shall support inspection according to the scenario, such as inspection
before upgrade;
d) It shall support the output of inspection reports;
e) It should provide an interface-based automatic inspection service of the
system operating environment.
12 Log management
The log management functional requirements are as follows:
a) It shall provide the c...