code-update: simplified interface for code update
Current code update invocation flow has no explicit interface but
rather rely on discovery of a new file in tmpfs. This makes it more
involved and hard to use. The intent of this proposal is to define an
explicit interface which is easy to use. For more details, please refer
to design doc -
https://gerrit.openbmc.org/c/openbmc/docs/+/65739
Change-Id: I65f186856c446cf7d957591c213054dc2d5c3861
Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>
diff --git a/yaml/xyz/openbmc_project/Software/Version.interface.yaml b/yaml/xyz/openbmc_project/Software/Version.interface.yaml
index ee4d5ac..58fe2b5 100644
--- a/yaml/xyz/openbmc_project/Software/Version.interface.yaml
+++ b/yaml/xyz/openbmc_project/Software/Version.interface.yaml
@@ -42,3 +42,24 @@
- name: PSU
description: >
The version is a version for a PSU.
+
+associations:
+ - name: running
+ description: >
+ This indicates the current running version for the associated
+ inventory item.
+ reverse_names:
+ - ran_on
+ required_endpoint_interfaces:
+ - xyz.openbmc_project.Inventory.Item
+ - name: activating
+ description: >
+ This indicates the current activated version for the associated
+ inventory item. There can be more than one active version associated
+ with the same inventory item. In such a case, RedundancyPriority
+ interface will help to decide the correct priority order for the
+ active version transition to running.
+ reverse_names:
+ - activated_on
+ required_endpoint_interfaces:
+ - xyz.openbmc_project.Inventory.Item