Policy requirement in ONIX

[vishi24]

Description

Document the requirement for network policy administration on confluence, it will consist of below components.

1. Creation and maintenance of policies.
2. Downloading and applying the network policies on open networks.

Goals

• [ ] Requirement document for network policy on confluence.
• [ ] Architecture document for implementing network policy.

Expected Outcome

https://fide-official.atlassian.net/wiki/spaces/BBB/pages/238845987/Layering+of+network+policy+on+core+schema

Document containing the requirements and architecture for network policy administration.

Acceptance Criteria

• [ ] Document containing requirements for network policy.
• [ ] Document must contain the architecture for network policy.

Implementation Details

NA

Mockups / Wireframes

NA

---

[Please note that the below section of the ticket has to be in the format as mentioned as it is key to enabling proper listing of the project. Please only choose the options mentioned under the headings wherever applicable.]

Product Name

ONIX

Project Name

ONIX

Organization Name:

NA

Tech Skills Needed:

Decentralized

Complexity

Pick one of [High]/[Medium]/[Low]

Category

Pick one or more of [CI/CD], [Integrations], [Performance Improvement], [Security], [UI/UX/Design], [Bug], [Feature], [Documentation], [Deployment], [Test], [PoC]

Sub Category

Pick one or more of [API], [Database], [Analytics], [Refactoring], [Data Science], [Machine Learning], [Accessibility], [Internationalization], [Localization], [Frontend], [Backend], [Mobile], [SEO], [Configuration], [Deprecation], [Breaking Change], [Maintenance], [Support], [Question], [Technical Debt], [Beginner friendly], [Research], [Reproducible], [Needs Reproduction].

[vbabuEM]

The requirements for this has to be clarified by business.

[mayurvir]

• The issue is not very well written.
• The idea is to create a wizard to create L2 configuration for various domains
• Machine readable l2 configurations is going to be property of the spec itself (with openAPI 3.1)
• Beckn onix to have a feature to ingest this configuration and apply it
• L2 configuration generator to be treated as an independent building block in onix. The deployment could be on any node such as registry or a separate node for hosting this (to be decided later)
• Title is too ambiguous. To fix this, we need to define the requirements in this issue.

[mayurvir]

Suggestion : "Create requirements for L2 configuration manager"