summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRatan Gupta <ratagupt@in.ibm.com>2017-03-24 18:01:48 +0530
committerPatrick Williams <patrick@stwcx.xyz>2017-04-25 16:18:24 +0000
commit7e175e12b1b0bf6e40914682656ea60e7cf72168 (patch)
tree91578023bb00b2a13e8de482c0d7a1ea4d3d1e40
parent632b80b9e9b513d5fd07e70d082eeed2304266f5 (diff)
downloadphosphor-dbus-interfaces-7e175e12b1b0bf6e40914682656ea60e7cf72168.tar.gz
phosphor-dbus-interfaces-7e175e12b1b0bf6e40914682656ea60e7cf72168.zip
Document overview and usage of the network d-bus interfaces
Resolves openbmc/openbmc#1284 Change-Id: I0f57ea9d48485f8bc54e6f65795fd76507e4ea81 Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
-rw-r--r--xyz/openbmc_project/Network/README.md59
1 files changed, 59 insertions, 0 deletions
diff --git a/xyz/openbmc_project/Network/README.md b/xyz/openbmc_project/Network/README.md
new file mode 100644
index 0000000..9cf6101
--- /dev/null
+++ b/xyz/openbmc_project/Network/README.md
@@ -0,0 +1,59 @@
+ Network Management
+ ==================
+Overview
+=========
+A Network Manager is a daemon which handles network management operations.
+It must implement the xyz.openbmc_project.Network.SystemConfiguration.interface
+and org.freedesktop.DBus.ObjectManager.
+
+When the network manager daemon comes up, it should create objects
+implementing physical link/virtual interfaces such as
+xyz.openbmc_project.Network.EthernetInterface or
+xyz.openbmc_project.Network.VLANInterface on the system.
+
+IP address(v4 and v6) objects must be children objects of the
+physical/virtual interface object.
+
+Interfaces
+==========
+
+1. SystemConfiguration: This describes the system specific parameters.
+2. EthernetInterface: This describes the interface specific parameters.
+3. IP: This describes the ip address specific parameters.
+4. IPProtocol: This describes the IP protocol type(IPv4/IPv6).
+5. VLANInterface: This describes the VLAN specific properties.
+6. Bond: This describes the interface bonding parameters.
+
+DbusObjects:
+
+Interface Objects
+=================
+Interface objects can be physical as well as virtual.
+
+If the object is physical interface, it can't be deleted,
+but if it is a virtual interface object it can be deleted.
+
+eg:
+/xyz/openbmc_project/network/<interfacename>:
+
+IPAddress Objects
+=================
+There can be multiple ip address objects under an interface object.
+These objects can be deleted by the delete function.
+
+IPv4 object will have the following dbus object path.
+
+eg:
+/xyz/openbmc_project/network/<interface>/<ipv4>/0/
+
+IPv6 object will have the following dbus object path.
+
+eg:
+/xyz/openbmc_project/network/<interface>/<ipv6>/0/
+
+Conf Object
+===========
+This object will have the system configuration related parameters.
+
+eg:
+/xyz/openbmc_project/network/conf
OpenPOWER on IntegriCloud