Modify StaticRoute interfaces to static gateway

StaticRoute interfaces being used implementing IPv6 static gateways
https://gerrit.openbmc.org/c/openbmc/bmcweb/+/62255
Network StaticRoute feature was dropped for OpenBMC, so these static
route interfaces are no longer needed.

This commit modifies exiting static route interfaces to support static
gateway with required properties

Change-Id: Icd94b35098b50376d701ea2e3b03ece9f2f71be7
Signed-off-by: Ravi Teja <raviteja28031990@gmail.com>
5 files changed
tree: c7c9443ab5a890ec2ed5f88fe758e3bdc0a5eea2
  1. gen/
  2. subprojects/
  3. yaml/
  4. .gitignore
  5. .markdownlint.yaml
  6. .prettierrc.yaml
  7. .shellcheck
  8. LICENSE
  9. meson.build
  10. meson.options
  11. OWNERS
  12. README.md
  13. requirements.md
README.md

phosphor-dbus-interfaces

YAML descriptors of standard D-Bus interfaces. The format is described by the sdbusplus binding generation tool sdbus++.

Before defining a new D-Bus interface or modifying an existing one, please read through the documented set of the common requirements and expectations.

Building

This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.

The meson files used to handle the YAML files are automatically generated and found under the gen subdirectory. When adding or removing YAML files, this must be regenerated. This can be done with the helper script found in the gen subdirectory: cd gen && ./regenerate-meson.

Configuration

Only the xyz/openbmc_project and org/freedesktop interfaces are built by default. Other interfaces can be enabled by meson options:

  • com/ibm - -Ddata_com_ibm=true
  • org/open_power - -Ddata_org_open_power=true

Example: meson builddir -Ddata_com_ibm=true && ninja -C builddir

References