Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Exposing FRR's config to host FS and adjusting build-infra accordingly. #2008

Closed
wants to merge 1 commit into from
Closed

Exposing FRR's config to host FS and adjusting build-infra accordingly. #2008

wants to merge 1 commit into from

Commits on Sep 1, 2018

  1. Exposing FRR's config to host FS and adjusting build-infra accordingly. 

    [ PR not for merging purposes. My intention here is to simply answer the various questions that we have been getting from SONiC community concerning the approach we (Linkedin) follow to interact with FRR stack. Hope it helps. ]

Functionally speaking, these are the changes being introduced in this patch:

  * FRR's config is now exposed to the host FS.
  * FRR is now relying on the unified-configuration model -- one single config file for all the FRR daemons -- frr.conf
  * FRR is now bypassing all minigraph.xml/config_db.json parsing logic, so FRR's docker entry-point logic is considerably simplified.
  * A new 'sonic' user is created to allow critical applications to operate with non-root privileges.
  * Corresponding 'uid-gid' is being exposed in rules/config to allow users to define their desired values.
  * FRR applications now run as 'sonic:sonic'.

Signed-off-by: Rodny Molina <rmolina@linkedin.com>
    Rodny Molina committed Sep 1, 2018
    Configuration menu
    Copy the full SHA
    922b7b6 View commit details
    Browse the repository at this point in the history