...
There are three methods of manually editing configurations in STR.
Method 1
Open a configuration file under
MZ_HOME/common/config/cell/default/master
.Edit the file and save.
Run the mzsh command
topo activate
. This is required in order for the changes to become effective.Code Block $ mzsh topo activate
Method 2
Open a configuration by running the
mzsh command
topo open. The configuration opens in vi or the editor specified by the environment variable EDITOR.
Info |
---|
...
Example - Opening a |
...
Cell Configuration
|
...
|
Info |
---|
...
Example - Opening a |
...
Container Configuration
|
...
language | text |
---|
|
Info |
---|
...
Example - Opening a |
...
Pico Configuration
|
...
...
|
or
Code Block | ||
---|---|---|
| ||
$ mzsh topo open container:main1/pico:ec1 |
If the pico name is not unique in the system, you will be prompted to specify the container.
Info |
---|
...
Example - Multiple |
...
Pico Configurations Sharing the Same Name
|
...
...
|
Edit the configuration and save. The mzsh command
topo activate
will be called with the--verbose
option and the saved changes are displayed in a scripted syntax.
Method 3
As an alternative to the command line tool, you can manage pico configurations and start/stop pico instances from the System Administration GUI. For further information, see Managing Picos in Desktop.
Activation and Validation
When you use the mzsh commands topo
set
or topo open
, changes are automatically validated before they are copied to the active registry. If the command and its arguments can be parsed but fails the validation, you can update the configuration or use a reset command to undo the changes.
...
Code Block | ||
---|---|---|
| ||
$ mzsh topo set --no-activation |
Excerpt | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Note | | title | Note!
Apply the ChangesChanges to the STR are not applied on running pico instances or services. |
If you, for example, have updated the properties of the Platform and an EC, both must be restarted after activation. Example, after an mzsh topo activate of ec5, mzsh shutdown and startup needs to be done to apply the changes.
|
Note |
---|
Note! |
...
The sorting and layout of the configuration files may change when it is updated both using manual editing and the commands. That means that the exact ordering of keys, and layout of the file could change. However: this will not affect how the system interprets the configuration at runtime. It is not supported to edit the configuration files using command line utilities (such as sed or awk), all scripted changes must be done via the mzsh topo command, to minimize the risk of invalid assumptions regarding the exact layout of the configuration files. |
For further information about the various sub-commands that are available in the mzsh topo
command, see topo.
For further information about how to manage pico- and service configurations, see Managing Picos with Topo and Managing Service Configurations.
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|
Scroll pagebreak |
---|