9ec7cf4447
Change spec and scripts to only use python3 explicitly Verification: 1. Regard as the README，in development docker environment, run ./patch-engtools.sh, it will generate the ENGTOOLS-20.01.patch if we scp the patch to controller， we could sw-patch upload and sw-apply it successfully. 2. The engtools-1.0-4.tis.noarch.rpm is not built into bootimage by default thus if we package it into bootimage when to verify it. 1). Run some bash script, such as ceph.sh, memstats.sh, netstats.sh and so on it will display the collect system resource information. 2). The service of collect-engtools.service could start and stop without problem 3). If we run the modified python which we have changed to python3. python3 buddyinfo.py it will deplay the resource information python3 live_stream.py the log of livestream.log will display collect information This package only be packaged into bootimage when we need it to collect system resource information. Change-Id: I9bd77e34650e200f0c65db966635a8ebcdc584aa Story: 2007106 Task: 39112 Depends-on: https://review.opendev.org/#/c/712218/ Depends-on: https://review.opendev.org/#/c/714072/ Signed-off-by: Long Li <lilong-neu@neusoft.com>
13 lines
665 B
Plaintext
13 lines
665 B
Plaintext
The Engineering tools is meant to be installed as a patch. Therefore, the RPM is generated as part
|
|
of the build but is not included in the image. Assuming your development environment is fully set up,
|
|
simply run patch-engtools.sh to generate the patch:
|
|
|
|
In this directory ($MY_REPO/stx/utilities/tools/engtools/hostdata-collectors),
|
|
enter the command:
|
|
>./patch-engtools.sh
|
|
|
|
This generates ENGTOOLS-X.patch (X is Tis release version) which can be applied via sw-patch.
|
|
|
|
The patch is built with --all-nodes option by default. This can be changed to a combination of the following:
|
|
--controller, --compute, --storage, --controller-compute, and --compute-lowlatency.
|