| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Resolves openbmc/openbmc#1390
Change-Id: Id25c1d5b0752b510260932e39194538d7126ab86
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
|
|
|
|
|
|
|
|
| |
This new element will be used to allow the user
to disable any kind of automatic reboot.
Change-Id: I30bfec142d6ece35bd3e38a745551a1da71da489
Signed-off-by: Michael Tritz <mtritz@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
| |
A backslash in regex in settings.yaml causes a failure.
Add double-escape before a backslash so it will be
treated as a character.
Change-Id: Icb11579986d261b562e965c871bf5da9ca2b8763
Signed-off-by: Sergey Solomin <sergey.solomin@us.ibm.com>
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Presently, the settingsd code will statically create objects 'host0',
'bmc0' and 'bmc0/clock' from top-level categories Host and Bmc
in the YAML file. This code provides a 1-to-1 mapping between
YAML categories and inventory objects and changes filename format
to correspond to an inventory object.
Resolves openbmc/openbmc#638
Change-Id: I462cf4c7b7cf042b37e1006a73b36bf11fa52b43
Signed-off-by: Sergey Solomin <sergey.solomin@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, the properties defined under /org/openbmc/settings/host0 can take any
value and it is upto the consumer daemons to act only if the valid data was
given.
This patch will provide a validation logic for all the properties and will raise
an exception in the case of invalid inputs. Only on a valid input, will the data
gets written and saved.
Validation methods and types per property are provided in the configuration file
and used by the manager whenever a particular property is changed.
Change-Id: I0731ce6e00ab3cb4e11deb98c03fda8d5adad913
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
| |
time manager daemon needs 3 new properties namely:
- time_mode : For setting the mode to NTP or MANUAL
- time_owner : For setting the owner to BMC/HOST/SPLIT/BOTH
- use_dhcp_ntp : Updating UseNtp= field in network files
Change-Id: I50ef4ef32f5555044c7722519f6c0dd26bd3c83a
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
|
|
|
|
|
|
|
| |
Adding the network config data
Fixes openbmc/openbmc#267
Change-Id: If6973c04714d6357e5da9887e3ec5f0c1aa04900
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The REST interface is not a reflection of IPMI. It is its own
design. The 0's as the default was because that is what the
you could think of as the IPMI bytes indicating default. The
OpenBMC REST interface should not have a direct relationship
with IPMI. That is a general tenent
|
|
|
|
|
|
|
|
|
|
|
| |
Add system_state property to keep track of the system
state across reboots.
Include the generated settings_file.py since some build
machines cannot have the yaml python module installed. This
file will be removed once the code is ported to C in the next rework.
Add the path where the settings will be stored in bmc:
/var/lib/obmc/
Address review comments from the initial commit.
|
|
Host settings are specified in a yaml file.
Parser converts the yaml file into a dictionary.
The settings manager runs on the BMC and uses the dictionary to
create the dbus properties and save the values in the BMC so that
the values persist.
|