Hide Forgot
Description of problem: Currently it might not always be obvious how configuration changes can be achieved using Node's API. Documentation enhacements can improve the situation.
Hey Yaniwang, could you explain a bit more in depth where you would like to see what documentation?
Hey Fabian Document like the following will helpful for tester Two top category one is corresponding to the TUI another is corresponding to the functions that can't be used through TUI or some other advanced/hidden feature For the first category - Status Inerface ... - Network Interface ... - Logging Interface class Logging() get_logrotate_max_log_size() get_rsyslog_address() For the second category provide the API like - reload TUI with dev/test mode - reset log output level - ...
is this meant as a stable public api? would it survive next-gen efforts?
That is a good question. To not maintain our own API I'd say we use the logic from anaconda to do the basic system configuration. Probably work upstream on anaconda/pykickstart to support currently unsupported topics like snmp and netconsole through the ks directives. But we could also go the other way, and use the API (which this bug is about) and wrap the anaconda parts. In general it is also the question if Node itself should offer an public API. And if so, on what level it should be, a "Node level" (very high, like puppet) or like on the library level. At least I am moving out this bug.
More documentation has been added in the mean time, and even more will be added, closing this bug.