tree b7bd5355254c78dd34f0fb3938132ca3f0f5560c
parent d6b4d059fbfbff4c672b3b65266f667548494fb2
author Ninad Palsule <ninadpalsule@us.ibm.com> 1681961125 -0500
committer Patrick Williams <patrick@stwcx.xyz> 1682085473 +0000

Add socket-id for the first console

This drop adds socket-id for first console. This was left out before
but with the new design this parameter is required and enforced by
obmc-console code. It is decided to set "socket-id = console0"
initially because that is the current path used by bmcweb but in future
you can change this value to whatever is appropriate.

The console information is now available through the DBUS interface.
Each console server register it's object path on DBUS. The leaf node of
the object path is used to create a console path. For example in the
following console0 the leaf node "console0" is used to make up the
console path and the GUI will use console path "/console/console0" to
connect to the console.

    busctl tree xyz.openbmc_project.Console.console0
    `-/xyz
      `-/xyz/openbmc_project
        `-/xyz/openbmc_project/console
          `-/xyz/openbmc_project/console/console0

Here is a discord thread where new design was discussed.
https://discord.com/channels/775381525260664832/1083551792094249051

Tested:
    Tested on the rainier system.

Related commits:
    1) phosphor-dbus-interface: https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/61486
    2) obmc-console: https://gerrit.openbmc.org/c/openbmc/obmc-console/+/62496
    3) bmcweb: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/62525

Change-Id: I5fd06f3aac69872a3e5032d592a9b59711795cfe
Signed-off-by: Ninad Palsule <ninadpalsule@us.ibm.com>