-
Story
-
Resolution: Done
-
Medium
-
None
-
None
- re-factor current code-base into three entities
- osdf/lib-base (compile-time, all the common libraries - logging, rest calls)
- osdf/lib-base - make it into PyPy package imported
- osdf/runtime (Minizinc + CRUD)
- osdf/apps/placement (APP API + data transforms)
osdf/apps/CM
osdf/apps/PCI
- osdf/lib-base (compile-time, all the common libraries - logging, rest calls)
- osdf/runtime:
- build the lib —> solver API
- build user —> solver CRUD API
- package and build Minizinc runtime
- repo as a DB (common ONAP galera, maria-DB) - make it a part of the plug and play
- osdf/apps:
- refactor current app specific code+ data transforms into osdf/apps
- build the layered image with:
- osdf/apps/* (1 image for each app, so long as it doesn't become bulky)
- osdf/runtime (with mini zinc)
- CI/CD modify ONAP build process to use new images, release new artifacts. Off the top of my head, I’m guessing there will be one image per app, and one runtime.
- modify current CSIT
- unit-tests to retain 70.6% coverage
- modify helm to new architecture/images
- No repo-level change. Have hierarchical folder structure with master pom and individual pom.
- Bump up to oparent-2.2.0
1.
|
Re-factor current code-base |
|
Closed | Unassigned |
2.
|
Build osdf runtime |
|
Closed | Unassigned |
3.
|
Build osdf/apps |
|
Closed | Unassigned |
4.
|
Build OSDF images |
|
Closed | Unassigned |
5.
|
Modify CI/CD to new architecture |
|
Closed | snarayanan |
6.
|
Modify SONAR to new architecture |
|
Closed | Unassigned |
7.
|
Modify CSIT to new architecture |
|
Closed | vrvarma |
8.
|
Create unit-tests to retain current coverage |
|
Closed | Unassigned |
9.
|
Modify helm to new architecture/images |
|
Closed | Unassigned |
10.
|
Bump up to oparent-2.2.0 |
|
Closed | snarayanan |