Setting up the l2 config in OAS3.1 for Mobility: Phase2

[rajaneeshk90]

Description

We need to create the layer 2 config for the mobility domain with the domain specific rules added in the config.

This config is used in the Beckn-ONIX provisioned networks to enforce the domain specific rules in the network.

Goals

• Make the layer2 config which has the domain specific network rules.
• The specification should be modular.
• The network rules(policies) should be defined separately from the core spec api and component definition.
• Examples provided in the specification should be defined separately from the core spec api and component definition.
• There should be a way to compile the final layer2 config from the API, component, network rules and examples defined separately.

Expected Outcome

A modular system which allows the creation of the layer2 config for Mobility domain from the API, component, policies, and example definitions. The layer2 config is in open api specification version 3.1

Acceptance Criteria

• [x] The setup should be modular.
• [x] It uses openAPI 3.1
• [x] Layer2 config has network rules and examples.
• [x] The layer 2 config has no issues.
• [x] Adding a new rule is easy.

Component Name

Beckn-ONIX

Domain

Mobility

Tech Skills Needed

• openAPI3.1
• YAML
• API definition

• Complexity

  Medium

Category

Specification

Sub Category

Layer2

[rajaneeshk90]

The commits as part of this task: https://github.com/beckn/mobility/pull/78/commits (commits made in between 15th July and 18th July)

[rajaneeshk90]

• The task involved exploring different approaches to make the layer2 config modular.
• Trying out those approaches, doing a comparative analysis on the pros and cons.
• Making the changes, deploy the final layer 2.
• trying out the final layer2 config changes and making further changes (a cycle of changes)