No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

eSight V300R010C00 Maintenance Guide 07

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
3rd Party OpenStack Configuration files

3rd Party OpenStack Configuration files

List of configuration files related to 3rd Party OpenStack.

NOTE:

V300R010C00SPC500 does not support virtualization management (3rd Openstack).

Configuration File for eSight 3rd Party OpenStack

List of configuration files present in eSight Server related to 3rd Party OpenStack.

openstack.as.properties

File stores all the startup configuration information of eSight 3rd Party OpenStack components.

Function

File stores all the startup configuration information of eSight 3rd Party OpenStack components.

Path

/opt/eSight/AppBase/etc/openstack/

Description

Description on key parameters of openstack.as.properties

Parameter

Description

Default Setting

Effective Method

virtual.as.keystone.protocol

https/http support for keystone

https

Restart

virtual.as.keystone.version

Supported versions v3/v2.0

v3

Restart

virtual.as.keystone.protocol.query.token.uri

Url is case sensitive used to query keystone information Update as Below based on virtual.as.keystone.version parameter

v3 : /v3/auth/tokens

v2.0 : /v2.0/tokens

/v3/auth/tokens

Restart

virtual.openstack.alarm.check.thread.interval

Default alarm check thread interval in seconds. Thread runs continuously at the given interval

1

Restart

openstack.adapter.rabbitmq.nrOfKeepAliveConsumers

RabbitMQ number of keep alive consumers configuration

3

Restart

openstack.adapter.rabbitmq.nrOfChkResultConsumers

RabbitMQ number of check result consumers configuration

3

Restart

openstack.adapter.rabbitmq.connectionTimeOut

Rabbit MQ connection time out configuration

10

Restart

openstack.adapter.rabbitmq.connectionMonitorInterval

Rabbit MQ connection monitoring interval configuration

20

Restart

openstack.adapter.keepalive.monitorinterval

Rabbit MQ keepalive monitoring interval configuration

30

Restart

openstack.adapter.keepalive.criticalthreshold

Rabbit MQ keepalive critical threshold for keep alive failure configuration

180

Restart

openstack.alarm.keepAlive.monitor.interval

Rabbit MQ alarm keepalive monitoring interval configuration

1

Restart

openstack.adapter.rabbitmq.connection.flag

RabbitMQ connection check while adding redhat configuration

true

Restart

openstack.adapter.rabbitmq.certExpiryWarningDays

Alarm days of RabbitMQ certificate expiry

90

Restart

openstack.adapter.rabbitmq.maxMsgSizePerQueue

Maximum number of messages to be stored in eSight message queue

412000

Restart

virtual.as.hostmetric.flag

Used to control the host historical performance metric,if true it will display all ,if false it will display only below metrics (cpuUsage, memoryUsage, diskUsage)

false

Restart

openstack.redhat.cert.trustFlag

Used to trust all the redhat certificates true: system doesn't downloads the redhat certificates false: system downloads the certificates from red-hat servers

false

Restart

openstack.tls.connction.version.executeRequest

Red Hat OpenStack TLS communication protocol version.

Values:TLSv1.1,TLSv1.2.

TLSv1.2

Restart

openstack.pm.performance.resync.task

This field is used to determine if the performance resync task should run or not.

0 – No Run.

1 –Run

1

Restart

openstack.pm.performance.resync.task.runtime

Time of the performance resync task run. Configured in HH:mm format.

01:00

Restart

openstack.pm.performance.resync.nrBackDays

Determines how many days old data the performance resync task will try to retrieve.

2

Restart

openstack.pm.gnocchi.performance.enable

Determines if the performance should be collected using Gnocchi.

0 – Do not use Gnocchi

1 – Use Gnocchi

0

Restart

Precautions

Do not change the configuration file unless necessary

Configuration Example
#redhat keystone configurations
#https/http supprot
virtual.as.keystone.protocol=https
#supported versions v3/v2.0
virtual.as.keystone.version=v3
#url format is /v3/auth/tokens or /v2.0/tokens . Case sensitive
virtual.as.keystone.protocol.query.token.uri=/v3/auth/tokens

#default alarm check thread interval in seconds. Thread runs continuously at the given interval
virtual.openstack.alarm.check.thread.interval=1

#RabbitMQ configurations
openstack.adapter.rabbitmq.nrOfKeepAliveConsumers=3
openstack.adapter.rabbitmq.nrOfChkResultConsumers=3
openstack.adapter.rabbitmq.coreThreadsPerRMQConn=3
openstack.adapter.rabbitmq.maxThreadsPerRMQConn=10
openstack.adapter.rabbitmq.keepAliveTimeRmqThreadPool=10000
openstack.adapter.rabbitmq.connectionTimeOut=10
#thread to monitor status of rabbit mq connections
openstack.adapter.rabbitmq.connectionMonitorInterval=20
openstack.adapter.rabbitmq.certExpiryWarningDays=90
#Alarm processing parameters
virtual.openstack.alarm.process.max.queue.size=100000
virtual.openstack.alarm.process.max.thread.size=150
openstack.alarm.db.pushInterval.minutes=1
openstack.alarm.fm.syncInterval.seconds=30

#Sensu Adapter configurations
#Keepalive data monitor interval(in seconds)
openstack.adapter.keepalive.monitorinterval=30
#Keepalive critical alarm threshold(in seconds)
openstack.adapter.keepalive.criticalthreshold=180000

#keepalive monitor interval in seconds
openstack.alarm.keepAlive.monitor.interval=1

#rabbit mq connection flag,where true represent resource connection with rabbitmq connection check
openstack.adapter.rabbitmq.connection.flag=true

openstack.adapter.rabbitmq.maxMsgSizePerQueue=412000

openstack.pm.gnocchi.performance.enable=0

#Length configurations for parameters
openstack.length1=100
openstack.length2=200
openstack.length3=500
openstack.length4=1000
openstack.length5=5000
openstack.length6=10000
openstack.alarm.checkresult.output.maxlength=12000

#used for storing the red-hat certificates in trust-store,its same as ssl.keystore.password key at the eSight installation directory/AppBase/etc/oms.ros/ros.xml file ,ensure both the places same encrypted value is configured
openstack.ssl.keystore.password=9d7961bc8af54d05ce509e03b13ffce3abc7587373e7719b62555fd5aff9908d
#used to trust all the redhat certificates true: system doesn't downloads the redhat certificates false: system downloads the certificates from red-hat servers
openstack.redhat.cert.trustFlag=false

#openstack TLS connection version values TLSv1.1 or TLSv1.2 default value TLSv1.2
openstack.tls.connction.version.executeRequest=TLSv1.2

#used to control the hystorical performance metric,if true it will display all ,if false it will display only metrics(cpuUseRatio, memoryUseRatio, diskUseRatio)
virtual.as.hostmetric.flag=false

#Max allowed VM which can be added for a single resource
openstack.max.allowed.vm=20000

# Default pagination length
openstack.default.page.length=50000

#Run the resync task or not. 1-Run. 0-No run.
openstack.pm.performance.resync.task=1
#Time to run the resync task. HH:mm format.
openstack.pm.performance.resync.task.runtime=01:00
#Number of days the task will check for missing data in past. (Range:1-5).
openstack.pm.performance.resync.nrBackDays=2
#Number of seconds the performance resync task will pause between sensu requests. (Range:1-60)
openstack.pm.performance.resync.timeBetweenRequestsSec=5
openstack.http.param.xml

This file is used for southbound configuration.

Function

openstack.http.param.xml is used to set southbound HTTPS parameters of openstack in eSight, including the maximum number of connections, Socket timeout interval, and connection timeout interval. Default configurations of the configuration file can be applied to most conditions. It is recommended that you keep the configuration file unchanged.

Path

/opt/eSight/AppBase/etc/openstack/

Description

Description on key parameters of openstack.http.param.xml

Parameter

Description

Setting

Effective Method

httpExecutor

Southbound configurations. Each cloud platform has a type ID, which cannot be changed.

Data type: character string

Restart the server to make the configuration take effect.

httpExecutor>maxConn

Maximum number of connections

Data type: numeral

Value range: 1 to 20

Default value: 10

Unit:-

Restart the server to make the configuration take effect.

httpExecutor>socketTimeout

Socket timeout interval

Data type: numeral

Value range: 3000 to 300,000

Default value: 60,000

Unit: millisecond

Restart the server to make the configuration take effect.

httpExecutor>connTimeout

Connection timeout interval

Data type: numeral

Value range: 1000 to 180,000

Default value: 6000

Unit: millisecond

Restart the server to make the configuration take effect.

Precautions

Do not change the configuration file unless necessary

Configuration Example
<?xml version="1.0" encoding="UTF-8"?>
<!--
maxConn:[1, 20]
socketTimeout:[3000, 300000]
connTimeout:[1000, 180000]
-->
<httpExecutors>
<httpExecutor type="RedhatOpenStack">
 <maxConn>10</maxConn>
 <socketTimeout>60000</socketTimeout>
 <connTimeout>6000</connTimeout>
</httpExecutor>
</httpExecutors>
rhos.pm.collect.period.xml

rhos.pm.collect.period.xml is used to set the performance collection parameters for openstack in eSight, including the base period, and period of each child task.

Function

Performance indicator configurations of the configuration file have been optimized, so the configurations can be applied to most conditions. It is recommended that you keep the configuration file unchanged.

Path

/opt/eSight/AppBase/etc/openstack/

Description

Description on key parameters of rhos.pm.collect.period.xml

Parameter

Description

Setting

Effective Method

Period

Base period

Data type: integer

Value range: 5, 10, 15, 30

Default value: 5

Unit: minute

NOTE:
  • if the eSight topology connect to U2000, set the default Value as 15 or 30 in eSight

Restart the server to make the configuration take effect.

pmTask

Child task, which has an ID. The ID cannot be changed.

Data type: character string

Value range: THIRDPARTYHOST, THIRDPARTYVM, BACKENDSTORAGE,RABBITMQ, HAPROXY, GALERA

Restart the server to make the configuration take effect.

pmTask>period

Period of each child task

Data type: integer

Value range: integral multiple of the base period

Default value: THIRDPARTYHOST (5), THIRDPARTYVM (5), BACKENDSTORAGE(5), GALERA(5), RABBITMQ(5),

HAPROXY(5)

Unit: minute

NOTE:
  • if the eSight topology connect to U2000, set the default Value as 15 or 30 in eSight.

Restart the server to make the configuration take effect.

gnochhiRules

These rules are for communication with GNOCCHI. This should not be modified unless confirmed by R&D team.

Data type: Complex

Value range: text

Default value: NA

Restart the server to make the configuration take effect.

backperiodtimes

Backperiodtimes is the number of back window times(period minutes*backperiodtimes) that the historical data wil be collected for from Sensu clients.

Data type: numeral

Value range: 1 to 5

Restart the server to make the configuration take effect.

Precautions

Do not change the configuration file unless necessary

Configuration Example
<?xml version="1.0" encoding="UTF-8"?> 
<rhosPmRules> 
 <rhosPmRule resource-type="RedhatOpenStack"> 
  <!-- nThreads: [1,5] --> 
  <nThreads>3</nThreads>
		<!-- Period: [5,10,15,30] -->
		<period>5</period>
		<backPeriodTimes>1</backPeriodTimes>
		<pmTasks>			
			<pmTask id="BACKENDSTORAGE">
				<period>5</period>
			</pmTask>
			<pmTask id="RABBITMQ">
				<period>5</period>
			</pmTask>
			<pmTask id="HAPROXY">
				<period>5</period>
			</pmTask>
			<pmTask id="GALERA">
				<period>5</period>
			</pmTask>
			<pmTask id="THIRDPARTYVM">
				<period>5</period>
			</pmTask>
			<pmTask id="THIRDPARTYHOST">
				<period>5</period>
			</pmTask>
		</pmTasks> 
  <gnochhiRules>    
   <gnochhiRule id="VM.CPU_USAGE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/cpu_util/measures?granularity=#GRANULARITY&start=#GNOCHHISTART&stop=#GNOCHHISTOP</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="VM.MEMORY_USAGE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/memory.usage/measures?granularity=#GRANULARITY&start=#GNOCHHISTART&stop=#GNOCHHISTOP</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="VM.MEMORY_TOTAL"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/memory/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="VM.MEMORY_RESIDENT"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/memory.resident/measures?granularity=#GRANULARITY&start=#GNOCHHISTART&stop=#GNOCHHISTOP</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="VM.DISK_CAPACITY"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/disk.capacity/measures?granularity=#GRANULARITY&start=#GNOCHHISTART&stop=#GNOCHHISTOP</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="VM.DISK_ALLOCATION"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/disk.allocation/measures?granularity=#GRANULARITY&start=#GNOCHHISTART&stop=#GNOCHHISTOP</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="VM.DISK_READ_REQ_RATE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/disk.read.requests.rate/measures?granularity=#GRANULARITY&start=#GNOCHHISTART&stop=#GNOCHHISTOP</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="VM.DISK_WRITE_REQ_RATE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/disk.write.requests.rate/measures?granularity=#GRANULARITY&start=#GNOCHHISTART&stop=#GNOCHHISTOP</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="VM.DISK_READ_BYTES_RATE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/disk.read.bytes.rate/measures?granularity=#GRANULARITY&&start=#GNOCHHISTART&stop=#GNOCHHISTOP</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="VM.DISK_WRITE_BYTES_RATE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/disk.write.bytes.rate/measures?granularity=#GRANULARITY&start=#GNOCHHISTART&stop=#GNOCHHISTOP</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="VM.NETWORK_OUTGOING_BYTES_RATE"> 
    <method>post</method> 
    <url>/v1/aggregation/resource/instance_network_interface/metric/network.outgoing.bytes.rate?aggregation=sum&needed_overlap=0&granularity=#GRANULARITY&start=#GNOCHHISTART&stop=#GNOCHHISTOP</url> 
    <data>{"=":{"instance_id": "#GNOCHHIRESID"}}</data> 
   </gnochhiRule> 

   <gnochhiRule id="VM.NETWORK_INCOMING_BYTES_RATE"> 
    <method>post</method> 
    <url>/v1/aggregation/resource/instance_network_interface/metric/network.incoming.bytes.rate?aggregation=sum&needed_overlap=0&granularity=#GRANULARITY&start=#GNOCHHISTART&stop=#GNOCHHISTOP</url> 
    <data>{"=":{"instance_id": "#GNOCHHIRESID"}}</data> 
   </gnochhiRule> 

   <!--Host Measures configuration starts--> 
   <gnochhiRule id="HOST.CPU_USAGE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/hardware.cpu.util/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.MEMORY_USAGE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/hardware.memory.used/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.MEMORY_TOTAL"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/hardware.memory.total/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.DISK_CAPACITY"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/cpu_util/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.DISK_ALLOCATION"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/cpu_util/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.DISK_READ_BYTES_RATE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/cpu_util/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.DISK_WRITE_BYTES_RATE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/cpu_util/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.NETWORK_OUTGOING_BYTES_RATE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/hardware.network.outgoing.bytes.rate/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.NETWORK_INCOMING_BYTES_RATE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/hardware.network.incoming.bytes.rate/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.NETWORK_OUTGOING_PKT_RATE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/cpu_util/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.NETWORK_INCOMING_PKT_RATE"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/cpu_util/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.NETWORK_INPUT_BANDWIDTH_TOTAL"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/cpu_util/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.NETWORK_INPUT_BANDWIDTH_USED"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/cpu_util/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.NETWORK_OUTPUT_BANDWIDTH_TOTAL"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/cpu_util/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

   <gnochhiRule id="HOST.NETWORK_OUTPUT_BANDWIDTH_USED"> 
    <method>get</method> 
    <url>/v1/resource/generic/#GNOCHHIRESID/metric/cpu_util/measures?granularity=#GRANULARITY</url> 
    <data></data> 
   </gnochhiRule> 

  </gnochhiRules> 
 </rhosPmRule> 
</rhosPmRules>
rhos.pm_export.xml

This file is used for northbound configuration.

Function

The rhos.pm_export.xml configuration file is used to configure the export polices for the northbound function of virtual resource historical performance. Resource types, indicator groups, and indicators can be configured.

Path

/opt/eSight/AppBase/etc/openstack/

Description

Description on key parameters of rhos.pm_export.xml

Parameter

Description

Setting

Value&Effective Method

resourceType

Indicates the resource type.

Mandatory

Data type: character string

Value range: character string that adheres to the naming convention

Effective Method:Restart

measUnit

Indicates the indicator group.

Mandatory

Data type: character string

Value range: character string that adheres to the naming convention

Effective Method:Restart

measType

Indicates the indicator.

Mandatory

Data type: character string

Value range: character string that adheres to the naming convention

Effective Method:Restart

resourceType: indicates the resource type, for example, ThirdPartyVM. This parameter cannot be left empty. If the value is empty or invalid, this resource type cannot be exported. One or multiple resource types can be set in the configuration file.

measUnit: indicates the indicator group. The key attribute is the indicator group name. This parameter cannot be left empty. If the value is empty or invalid, this indicator group cannot be exported. One or multiple indicator groups can be set in the configuration file. (Currently, VMs only support the ThirdPartyVmPerfStat indicator group, indicating historical performance statistics of VMs.)

measType: indicates the indicator. The key attribute is the indicator name. This parameter cannot be left empty. If the value is empty or invalid, this indicator cannot be exported. One or multiple indicators can be set in the configuration file. The following table lists the supported indicators.

Precautions

Do not change the configuration file unless necessary

Performance Indicators Supported by Openstack Virtual Resources

KPI Group Name

KPI Counter name

KPI Description

Unit Measure

Hosts

CPU Usage (User)

CPU usage on the host OS (User mode)

%

CPU Usage (System)

CPU usage on the host OS (System)

%

CPU Usage (Idle)

CPU usage on the host OS (Idle)

%

CPU Usage (I/O Wait)

CPU usage of CPU I/O Wait Time

%

CPU Usage (Interrupts)

Time the CPU has spent servicing interrupts

%

CPU Usage (Steal)

CPU Usage by the Steal

%

CPU Frequency

CPU Frequency

MHz

CPU Time Usage

User+ System cpu time usage consumed by the Host

%

Memory Usage (Total)

Memory usage on the host OS (Total)

MB

Memory Usage (Used)

Memory usage on the host OS (Total - Available)

MB

Memory Usage (Available)

Memory usage on the host OS (Available)

MB

Virtual Machines

CPU Usage

Average CPU utilisation

%

Number of vCPUs

Number of virtual CPUs allocated to the instance

Number

Memory (Total)

Volume of RAM allocated to the instance

MB

Memory Resident

Volume of RAM used by the instance on the physical machine

MB

Memory Used

Volume of RAM used by the instance from the amount of its allocated memory

MB

Disk IOPS

Average disk iops

Req/Sec

Disk Read Rate

Average rate of reads

B/s

Disk Read Frequency

Average rate of read requests - DiskIoReadFrequency

Req/Sec

Disk Write Rate

Average rate of writes

B/s

Disk Write Frequency

Average rate of write requests - DiskIoWriteFrequency

Req/Sec

Ceph Backend Storage

Storage Utilization

Storage Utilization For Ceph backend Storage

%

Storage Read Speed

Read speed for Ceph backend Storage

B/s

Storage Write Speed

Write speed for Ceph backend Storage

B/s

Storage Operation Frequency

Operation for Ceph backend Storage

Req/Sec

Storage Apply Latency

File system apply latency for Ceph backend Storage

ms

Storage Commit Latency

File system commit latency for Ceph backend Storage

ms

Used Storage

Used Storage for Ceph backend Storage

GB

Avail Storage

Avail Storage for Ceph backend Storage

GB

Total Storage

Total Storage for Ceph backend Storage

GB

OSD UP Rate

OSD UP Rate for Ceph backend Storage

%

OSD IN Rate

OSD IN Rate for Ceph backend Storage

%

HAProxy

HAProxy.Frontend Request Rate (req_rate)

Requests per second on the frontend

Number/sec

HAProxy.Frontend Request Errors (ereq)

Number of requests terminated in error at the frontend

Number/sec

HAProxy.Backend Current Sessions (scur)

Current open sessions to the backend

Number

HAProxy.Backend Max Queued Requests (qmax)

Max queued session to the backend

Number

HAProxy.Backend Queued Requests (qcur)

Current queued sessions to the backend

Number

HAProxy.Backend Max Sessions (smax)

Max sessions to the backend

Number

RabbitMQ

RabbitMQ.Node Number Of Connections

Number of connections in the server

Number

RabbitMQ.Node Number Of Exchanges

Number of exchanges in the server

Number

RabbitMQ.Node Number Of Consumers

Number of consumers in the server

Number

RabbitMQ.Node Number Of Queues

Number of queues in the server

Number

RabbitMQ.Node Used File Descriptors

Used File Descriptors

Number

RabbitMQ.Node Used Memory

Used Memory

MB

RabbitMQ.Queue Number Of Ready Messages

Number of messages ready to be delivered (queued) in the queue

Number

RabbitMQ.Queue Number Of Published Messages

Number of published messages by the queue

Number

RabbitMQ.Queue Number Of Delivered Messages

Number of delivered messages by the queue

Number

RabbitMQ.Queue Memory

Memory used by the queue

MB

Galera

Galera.Connected Threads

Number of thread Connection with MariaDB

Number

Galera.Running Threads

Number of running thread with MariaDB

Number

Galera.Inserts

Number of inserts in MariaDB

Number

Galera.Updates

Number of updates in MariaDB

Number

Galera.Selects

Number of selects in MariaDB

Number

Galera.Deletes

Number of deletes in MariaDB

Number

Galera.Commits

Number of commits in MariaDB

Number

Galera.Queries

Queries-Number of Queries in MariaDB

Number

Galera.Wsrep Replicated Bytes

Number of wsrep_replicated_bytes in MariaDB

Bytes

Galera.Wsrep Received Bytes

Number of wsrep_received_bytes in MariaDB

Bytes

Galera.Database Size

Data base Size of Galera Cluster [MariaDB]

GB

Usage

Number of Users

Number of Users

Number

Number of Tenants

Number of Tenants

Number

Number of Running VMs

Number of Running VMs

Number

Total vCPU Number

Total vCPU Number

Number

Number of Used vCPU

Number of Used vCPU

Number

Number of Available vCPU

Number of Available vCPU

Number

Total Memory

Total Memory

MB

Used Memory

Used Memory

MB

Available Memory

Available Memory

MB

Number of Images

Number of Images

Number

Number of Volumes

Number of Volumes

Number

Total Volume Size

Total Volume Size

GB

HostNetwork

Network Octets In

Receive byte rate on the Network

B/s

Network Octets Out

Transmit byte rate on the Network

B/s

Network Incoming Packet Rate

Incoming packet rate on the Network

Packets/s

Network Outgoing Packet Rate

Outgoing packte rate on the Network

Packets/s

Network Incoming Errors

Incoming error packets rate on the Network

Packets/s

Network Outgoing Errors

Outgoing error packets rate on the Network

Packets/s

Indicators Supported by Different NEs

Currently, the Redhat 10 devices do not support all indicators of the same indicator group. Y indicates that the indicator is supported, while N indicates that the indicator is not supported. If an unsupported indicator is configured in the configuration file, the return value is blank by default.

Resource Type

Indicator

Redhat openstack 10

Hosts

CPU Usage (User)

Y

CPU Usage (System)

Y

CPU Usage (Idle)

Y

CPU Usage (I/O Wait)

Y

CPU Usage (Interrupts)

Y

CPU Usage (Steal)

Y

CPU Frequency

Y

CPU Time Usage

Y

Memory Usage (Total)

Y

Memory Usage (Used)

Y

Memory Usage (Available)

Y

Virtual Machines

CPU Usage

Y

Number of vCPUs

Y

Memory (Total)

Y

Memory Resident

Y

Memory Used

Y

Disk IOPS

Y

Disk Read Rate

Y

Disk Read Frequency

Y

Disk Write Rate

Y

Disk Write Frequency

Y

Ceph Backend Storage

Storage Utilization

Y

Storage Read Speed

Y

Storage Write Speed

Y

Storage Operation Frequency

Y

Storage Apply Latency

Y

Storage Commit Latency

Y

Used Storage

Y

Avail Storage

Y

Total Storage

Y

OSD UP Rate

Y

OSD IN Rate

Y

HAProxy

HAProxy.Frontend Request Rate (req_rate)

Y

HAProxy.Frontend Request Errors (ereq)

Y

HAProxy.Backend Current Sessions (scur)

Y

HAProxy.Backend Max Queued Requests (qmax)

Y

HAProxy.Backend Queued Requests (qcur)

Y

HAProxy.Backend Max Sessions (smax)

Y

RabbitMQ

RabbitMQ.Node Number Of Connections

Y

RabbitMQ.Node Number Of Exchanges

Y

RabbitMQ.Node Number Of Consumers

Y

RabbitMQ.Node Number Of Queues

Y

RabbitMQ.Node Used File Descriptors

Y

RabbitMQ.Node Used Memory

Y

RabbitMQ.Queue Number Of Ready Messages

Y

RabbitMQ.Queue Number Of Published Messages

Y

RabbitMQ.Queue Number Of Delivered Messages

Y

RabbitMQ.Queue Memory

Y

Galera

Galera.connected threads

Y

Galera.running threads

Y

Galera.Inserts

Y

Galera.Updates

Y

Galera.Selects

Y

Galera.Deletes

Y

Galera.Commits

Y

Galera.Queries

Y

Galera.wsrep_replicated_bytes

Y

Galera.wsrep_received_bytes

Y

Galera.Database Size

Y

Usage

Number of Users

Y

Number of Tenants

Y

Number of Running VMs

Y

Total vCPU Number

Y

Number of Used vCPU

Y

Number of Available vCPU

Y

Total Memory

Y

Used Memory

Y

Available Memory

Y

Number of Images

Y

Number of Volumes

Y

Total Volume Size

Y

HostNetwork

Network Octets In

Y

Network Octets Out

Y

Network Incoming Packet Rate

Y

Network Outgoing Packet Rate

Y

Network Incoming Errors

Y

Network Outgoing Errors

Y

Configuration Example
<?xml version="1.0" encoding="UTF-8"?>  
<indexes>  <!-- CEPH Backend storage -->
    <index resourceType="ThirdPartyBackendStore">
           <measUnit key="ThirdPartyBackendStorePerfStat">
               <measType key="BackendStorageUsage"/>
                  <measType key="BackendStorageDiskIoOutputSpeed"/>
                  <measType key="BackendStorageDiskIoInputSpeed"/>
                  <measType key="BackendStorageDiskIoReqSpeed"/>
                  <measType key="BackendStorageApplyLatency"/>
                  <measType key="BackendStorageCommitLatency"/>
                  <measType key="BackendStorageUsedStorage"/>
                  <measType key="BackendStorageAvailStorage"/>
                  <measType key="BackendStorageTotalStorage"/>
                  <measType key="BackendStorageOSDUpRate"/>
                  <measType key="BackendStorageOSDInRate"/>
           </measUnit>
    </index>
    <!--Host -->
    <index resourceType="ThirdPartyHost">
           <measUnit key="ThirdPartyHostPerfStat">
                  <measType key="HostCpuUsageUser"/>
                  <measType key="HostCpuUsageSystem"/>
                  <measType key="HostCpuUsageIdle"/>
                  <measType key="HostCpuUsageIOWait"/>
                  <measType key="HostCpuUsageInterrupts"/>
                  <measType key="HostCpuUsageSteal"/>
                  <measType key="HostCpuFreq"/>
                  <measType key="HostCpuUsageTime"/>
                  <measType key="HostCpuMemoryTotal"/>
                  <measType key="HostMemoryUsageUsed"/>
                  <measType key="HostMemoryUsageFree"/>
           </measUnit>
    </index> 
    <!-- VM -->
    <index resourceType="ThirdPartyVM">
           <measUnit key="ThirdPartyVmPerfStat">
               <measType key="VmCpuUsage"/>     
               <measType key="Vmvcpus"/>
                  <measType key="VmMemoryTotal"/>
                  <measType key="VmMemoryResident"/>
                  <measType key="VmMemoryUsed"/>
                  <measType key="VmDiskiops"/>
                  <measType key="VmDiskIOOutputSpeed"/>
                  <measType key="VmDiskIoReadFrequency"/>
                  <measType key="VmDiskIOInputSpeed"/>
                  <measType key="VmDiskIoWriteFrequency"/>
           </measUnit>
    </index>
    <!-- Openstack Galera -->
    <index resourceType="ThirdPartyOSPGalera">
           <measUnit key="ThirdPartyOSPGaleraPerfStat" >
                  <measType key="ControllerGaleraConnThread"/>
                  <measType key="ControllerGaleraRunThread"/>
                  <measType key="ControllerGaleraInserts"/>
                  <measType key="ControllerGaleraUpdates"/>
                  <measType key="ControllerGaleraSelects"/>
                  <measType key="ControllerGaleraDeletes"/>
                  <measType key="ControllerGaleraCommits"/>
                  <measType key="ControllerGaleraQueries"/>
                  <measType key="ControllerGaleraWresRepliBytes"/>
                  <measType key="ControllerGaleraWresRecvBytes"/>
                  <measType key="ControllerGaleraDBSize"/>
           </measUnit>
    </index>
    <!--Openstack HAProxy -->
    <index resourceType="ThirdPartyOSPHAProxy">
           <measUnit key="ThirdPartyOSPHAProxyPerfStat" >
                  <measType key="ControllerHAreqrate"/>
                  <measType key="ControllerHAereq"/>
                  <measType key="ControllerHAscur"/>
                  <measType key="ControllerHAqmax"/>
                  <measType key="ControllerHAqcur"/>
                  <measType key="ControllerHAsmax"/>
           </measUnit>
    </index>
    <!-- Controller plane RabbitMQ -->
    <index resourceType="ThirdPartyController">
           <measUnit key="ThirdPartyControllerPerfStat">
               <measType key="ControllerRbMqConnections"/>     
               <measType key="ControllerRbMqExchanges"/>
                  <measType key="ControllerRbMqConsumers"/>
                  <measType key="ControllerRbMqQueues"/>
                  <measType key="ControllerRbMqUsedFileDesc"/>
                  <measType key="ControllerRbMqUsedMemory"/>
                  <measType key="ControllerRbMqMsgReady"/>
                  <measType key="ControllerRbMqMsgPublish"/>
                  <measType key="ControllerRbMqMsgdelivered"/>
                  <measType key="ControllerRbMqQueMemory"/>
           </measUnit>
        </index>
  </indexes> 
nbi_cbb_openstack.xml

File stores configuration information is used to configure the OpenStack performance northbound file saving policy, including information such as file retention period.

Function

File stores configuration information is used to configure the OpenStack performance northbound file saving policy, including information such as file retention period.

Path

/opt/eSight/AppBase/etc/esight.nbi.cbb

Description

Description on key parameters of nbi_cbb_openstack.xml

Parameter

Description

Default Setting

Effective Method

businessId

Business unique identifier (can only consist of English, numbers and English half-width dots. The length does not exceed 32).

openstack

Restart

dirName

The storage path of the performance northbound file.

ThirdPartyPmFiles

Restart

period

Delete the northbound performance file interval period.

Unit: second

Value range: 30~86400.

86400

Restart

scope

File save period.

Unit: hour

Value range: 1~168,when the deleteMode is dirTime, the scope must be a multiple of 24.

168

Restart

deleteMode

Delete mode.

if fileName it will express according to the last modification time of the document to delete ,if dirTime it will express delete by the corresponding subdirectory (subdirectory is named according to yyyyMMdd),then scope must be a multiple of 24.

dirTime

Restart

Precautions

Do not change the configuration file unless necessary

Configuration Example
<?xml version="1.0" encoding="UTF-8"?>
<policies>
	<policy businessId="openstack">
		  <dirName>ThirdPartyPmFiles</dirName>
		  <period>86400</period>
		  <scope>168</scope>
		  <deleteMode>dirTime</deleteMode>
	</policy>
</policies>

Configuration files in RabbitMQ Node

List of configuration files present in RabbitMQ node for the 3rd Party OpenStack.

openssl.cnf file

File stores all the open SSL parameter which are used for SSL connections.

Function

File stores all the open SSL parameter which are used for SSL connections.

Path:

/opt/rabbitmq/scripts

Description

Description on key parameters of openssl.cnf

Parameter

Description

Setting

Effective Method

ca

The "ca" section defines the way of CA acts when using the ca command to sign certificates

NA

Restart

certificate_extensions

These extensions are automaticaly added when 'ca' signs a request

NA

Restart

req

Define the default size, the name of the keyfile, the section that defines how to form the DN, what attributes to put in the request

NA

Restart

root_ca_distinguished_name

This specifies the section containing the distinguished name fields to prompt for when generating a certificate or certificate request. The format is described in the next section

NA

Restart

root_ca_extensions

This specifies the configuration file section containing a list of extensions to add to the certificate request. It can be overridden by the -reqexts command line switch

NA

restart

Precautions

Do not change the configuration file unless necessary.

Configuration Example
[ ca ]
default_ca = testca
[ testca ]
dir = .
certificate = $dir/cacert.pem
database = $dir/index.txt
new_certs_dir = $dir/certs
private_key = $dir/private/cakey.pem
serial = $dir/serial
default_crl_days = 7
default_days = 365
default_md = sha256
policy = testca_policy
x509_extensions = certificate_extensions
[ testca_policy ]
commonName = supplied
stateOrProvinceName = optional
countryName = optional
emailAddress = optional
organizationName = optional
organizationalUnitName = optional
domainComponent = optional
[ certificate_extensions ]
basicConstraints = CA:false

[ req ]
default_bits = 2048
default_keyfile = ./private/cakey.pem
default_md = sha256
prompt = yes
distinguished_name = root_ca_distinguished_name
x509_extensions = root_ca_extensions
[ root_ca_distinguished_name ]
commonName = hostname
[ root_ca_extensions ]
basicConstraints = CA:true
keyUsage = keyCertSign, cRLSign
[ client_ca_extensions ]
basicConstraints = CA:false
keyUsage = digitalSignature
extendedKeyUsage = 1.3.6.1.5.5.7.3.2
[ server_ca_extensions ]
basicConstraints = CA:false
keyUsage = keyEncipherment
extendedKeyUsage = 1.3.6.1.5.5.7.3.1

rabbitmq-env.conf

File contains RabbitMQ initialization parameter, these parameters will override the default configuration during startup.

Function

rabbitmq-env.conf file contains RabbitMQ initialization parameter, these parameters will override the default configuration during startup.

Path

/opt/rabbitmq/rabbitmq_server-3.7.9 /etc/rabbitmq

Description

Description on key parameters of rabbitmq-env.conf

Parameter

Description

Setting

Effective Method

HOSTNAME

The host name of the current machine

NA

Restart

COMPUTERNAME

The compute node name of the current machine

NA

Restart

NODENAME

The node name should be unique per erlang node and machine combination

NA

Restart

CONFIG_FILE

If the configuration file is present it is used by the server to configure RabbitMQ components

The config extension is automatically appended by the Erlang runtime

This file is also used to auto-configure RabbitMQ clusters

NA

Restart

MNESIA_BASE

The directory where Mnesia database files should be placed.

NA

Restart

LOG_BASE

Log files generated by the server will be placed in this directory.

NA

Restart

PLUGINS_DIR

Plugins will be found in this directory

NA

Restart

ENABLED_PLUGINS_FILE

File records explicitly enabled plugins

NA

Restart

Precautions

Do not change the configuration file unless necessary.

Configuration Example
HOSTNAME=BLR1000020122
COMPUTERNAME=BLR1000020122
NODENAME=rabbit@BLR1000020122
CONFIG_FILE=/opt/rabbitmq/rabbitmq_server-3.7.9/etc/rabbitmq/rabbitmq
MNESIA_BASE=/opt/rabbitmq/rabbitmq_server-3.7.9/var/lib/rabbitmq/mnesia
LOG_BASE=/opt/rabbitmq/rabbitmq_server-3.7.9/var/log/rabbitmq
PLUGINS_DIR=/opt/rabbitmq/rabbitmq_server-3.7.9/plugins
ENABLED_PLUGINS_FILE=/opt/rabbitmq/rabbitmq_server-3.7.9/etc/rabbitmq/enabled_plugins

rabbitmq.config

rabbitmq.config file contains the values for RabbitMQ configuration parameters.

Function

rabbitmq.config file contains the values for RabbitMQ configuration parameters.

Path

/opt/rabbitmq/rabbitmq_server-3.7.9 /etc/rabbitmq

Description

Description on key parameters of rabbitmq-env.conf

Parameter

Description

Setting

Effective Method

cacertfile

The cacertfile option specifies the certificates of the root Certificate Authorities that we wish to implicitly trust

NA

Restart

certfile

The certfile is the client's own certificate in PEM format

NA

Restart

keyfile

The keyfile is the client's private key file in PEM format.

NA

Restart

Precautions

Do not change the configuration file unless necessary.

Configuration Example
[
{ssl, [{versions, ['tlsv1.2', 'tlsv1.1']}]},
{rabbit, [
{tcp_listeners, [ ]},
{ssl_listeners, [5671]},
{ssl_options, [
{versions,'tlsv1.2','tlsv1.1'},
{cacertfile,      "/opt/rabbitmq/rabbitmq_server-3.7.9/ssl/cacert.pem"},
{certfile, "/opt/rabbitmq/rabbitmq_server-3.7.9/ssl/server/cert.pem"},
{keyfile,          "/opt/rabbitmq/rabbitmq_server-3.7.9/ssl/server/key.pem"},
{verify,               verify_peer},
{fail_if_no_peer_cert, true}]}
]}
]

Sensu Client Node

List of configuration files present in sensu client node for 3rd Party OpenStack.

conf.txt

conf.txt file contains the values for Sensu Client deployment. This file is on the Redhat OpenStack undercloud/director node.

Function

The configuration parameters in the configuration file conf.txt are required for sensu-client installation.

Path

/home/stack/eSight/sensu/Deploy/conf/conf.txt

Description

Description on key parameters of conf.txt

Parameter

Description

controllers

Used to identify the controller nodes in the nova list output

computes

Used to identify the compute nodes in the nova list output

cephs

Used to identify the ceph nodes in the nova list output

stackrc_file

Indicates the location of the stackrc file

overcloud_username

Indicates the username of the overcloud user configured to access the overcloud nodes

host-IP1

IP address for the rabbitMQ node1

host-IP2

IP address for the rabbitMQ node2

rabbitmqport

Port configured in the rabbitmq installation

rabbitmquser

The username configured in the rabbitmq installation.This value is used to configure connection between sensu client and rabbitmq server. Default value of user is sensu

rabbitmqvhost

The vhost name configured in the rabbitmq installation. This value is used to configure connection between sensu client and rabbitmq server. Default value of vhost is sensu

Precautions

Update the configuration file before performing any deployment tasks

Configuration Example
[NodeType]
controllers=controller
computes=compute
cephs=ceph
[Overcloud]
stackrc_file=/home/stack/stackrc
overcloud_username=heat-admin
[RabbitMq] 
host-IP1=10.18.21.172 
host-IP2=10.18.20.49 
rabbitmqport=5671 
rabbitmquser=sensu 
rabbitmqvhost=sensu

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 25066

Downloads: 74

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next