This Page is used Trace the task status of ONAP R11 General Intent Model Requirements.
| Project | Requirement Description | Owner | Status | Remark |
|---|---|---|---|---|
| UUI-Portal | UUI Portal should support the Intent management page. | Closed | 2022/6/20: UUI Portal design Finished. Now checking the structure of the uui portal code to clear the coding work. 2022/7/1: The development for intent manage page is started. 2022/7/8: Intent list, add Intent list pop-up box Local static page has been completed 2022/7/15: Completed adding Expectation pop-up box locally 2022/7/25: No changes 2022/8/1: No changes 2022/8/8: Modify the prototype diagram according to the new intent model data structure 2022/8/29: Modify the front-end code according to the new data structure, and are trying to debug the front-end and back-end 2022/9/5:The front-end static page has been completed, but the front-end and back-end joint debugging is unsuccessful 2022/11/1：finished. | |
| UUI-Intent Analysis Server | 1.Provide the function of decomposition and orchestration of intent. 2. Support general intent model and general intent interface 3. Support translate intent by APEX policy (postpone to next release) 4. Support CLL use case.Create CCVPN instance through SO, create Policy and DCAE rules for assurance. | Closed | 2022/6/20: The brief framework of the intent analysis server is built； New database container needed. share with uui-server and intent analysis server; use mybatis to do the db connection. 2022/7/1: The New repo for intent analysis server is needed.; The design is ongoing and the postgres db part is finished. The logic of the intent API should be further discussed. 2022/7/8: The new repo named usecase-ui/intent-analysis has been created and completed the init step with basic info; All Jenkins jobs for intent-analysis has been created and running; Seed code of intent-analysis framework has been submitting one by one; Currently working on analysing the high level design of the Server. 20227/18: The initial framework has been submitted and merged; Will submit the CRUD APIs and DB Ops today; Working on adding intent-analysis and postgres deployments in OOM which is also a reference for uui server; Continue analysising Intent Detection Service. 2022/7/25: The intent basic CRUD APIs and postgres connections have been submitted and under reviewing; OOM development has been done and waiting for integration testing with the new intent analysis code; Working on reading TMF 921A now. 2022/8/1: The Update API has been updated and some patches are waiting for merging; the new postgres DB could work well and support persistent storage; The OOM team are discussing the update in Slack and haven't comment on that patch yet; Working on adding Log configurations; According to the new Intent Model, the DB schema need some redesign and updates, as well as all CRUD APIs. 2022/8/8: Add exception handling for CRUD services. 2022/8/29: CRUD APIs are almost done, but waiting for merging; Doing the integrating testing between frontend and backend; Waiting to do the SO API integration. 2022/9/5: Complete CRUD APIs and SO, AAI, Policy adapters; Doing the development of parsing intent model into SO and Policy API body; Testing with frontend to communicate with backend. 2022/11/1:finished | |
| AAI | AAI Support the intent models | Closed | 2022/7/1: The discussion with AAI team is ongoing ,and there is some suggestion from AAI team. Need to be finalized. 2022/7/8: We will use the UUI DB instead of AAI to save Intent Models. | |
| Modeling | The Intent modeling standard should be archived to modeling project | Closed | 2022/7/1: We have already present twice to the modeling sub commitee. | |
| DCAE | 1.Provide the solution for intent analysis service to create/delete the monitor rule for the CLL usecase 2.Should do enhancement on the old CCVPN closed loop, so that that can support both increase and decrease the bandwith. | Closed | 2022/6/20: For DCAE rules setting , need further check. For the closed loop, CCVPN already support the most of the work , need to do the code update to support decrease the bandwidth(currently only increase supported). 2022/7/1: Item 2 analysis completed. 30%coding finished. ; Item 1 , use configuration policy to support the monitor rule change. also need to expore. how Policy sent the new Dmaap configuration. 2022/7/8: Item 1 in progress, analysis completed. Item 2 code completed, support both increase and decrease bandwidth in closed loop, test in progress. 2022/7/15: Slice ms runtime configuration code design has made out. Runtime configuration policy type and policy has written and verified success. Currently we are verifing the runtime configuration of dcae ms components on environment. 2022/8/1: Slice ms runtime configuration coding part has finished and verified working well. Policy sync is added as a side car of slicems to provide runtime configuration. Modification on policy sync has been finished, now new polices can be reached in real time. 2022/8/8: Code is committed, and is under review. There is some problem with latest ccvpn use case, probably because of integretion reason. I'm working on trouble shooting at this part, so as to make the use case run successfully. 2022/8/29: CCVPN bug mentioned above has been solved. Another bug of cbs client that exception will happen when policies are retrieved from pdp engine has been solved. Closed loop maintenance feature has been added. Bandwidth adjustment logics is being added, and tested feasible. Currently there is some conflicts in bandwidth ajustment logic, hopefully we can make it out, and complete integration test this week. 2022/9/15: All features are finished. | |
| Policy | 1.Provide the corresponding policies for intent decomposition and intent maaping 2. Provide the APIs to create/delete policy for CLL usecase. 3. Support to listen the event of DCAE and take the action for increase and decrease the bandwith. 4.Suport th APEX policies neede by intent analysis server(Orchestration, Decomposition, Mapping ,Decision to select the 3rd party intent management etc.) | Closed | 2022/6/20: Policy create/delete checked. for the closed loop, CCVPN IBN almost do all works. need to update the DCAE part. for the requirement of item 4, need to check APEX. 2022/7/1: the create/deploy/delete policy api tested and verified success. The learning on APEX engine tutorial has completed. 2022/7/8: Item 2, 3 finished. 2022/8/1: Policies for dcae runtime configuration has finished and verfied working well. Code submmitted. 2022/9/15: All features are finished. | |
| SO | SO support the CLL instance creation APIs to the intent analysis server | Closed | 2022/7/1: No change to SO , SO already support the API. Waiting for test. 2022/7/8: No changes. 2022/7/18: No changes. 2022/7/25: No changes. 2022/8/1: No changes. 2022/8/28：Waiting for UUI intent analysis server to do the pair test. 2022/10/8：SO is ready. | |
| Installation | ONAP Installation | Closed | 2022/7/18: 2022/7/25: CLL service can be created and deleted correctly. The bandwidth and link are shown on tunnel layer. PM can be used to moniter the service. 2022/8/1: Intent analysis and postgre are added in oom and deployed in environment. 2022/8/8: No changes. 2022/8/29: The ONAP env is ready. The CCVPN+ IBN ZSM POC is verified ok, and now we can test our requirements on the env. |