Skip to content

Split generation of the config to make it more independant #13

Description

@Cybertinus

The generation of the config should be more modular. This has as advantage that when 1 part fails, the other parts are generated without problems. For instance: when the generation of the eBGP filter fails, the static routes towards our members should be generated just fine.

Parts that could be made separate, as a quick idea:

  • eBGP filter en session config
  • Transit config
  • OSPF en iBGP config
  • static routes toward the members
  • BGP sessions toward the members
  • Misc stuff in the config generation

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    All vendorsIf something needs to be done for all supported platformsenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions