Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Date
Attendees
Recording
Agenda
- Continue demo of A1-Simulator (A1 Terminator) → RANSIM-Controller Kafka messaging for A1 operations
Notes
| Item | Who | Notes |
|---|
|
| Unfortunately N.K. Shankaranarayanan could not join so we could not use the usual bridge - used different bridge (ONAP OSC Alignment meeting bridge) |
| A1-Simulator (A1 Terminator) → RANSIM Controller Kafka messaging |
| Halil Cakal showed current snapshot of A1-SIM → RANSIM (kafka) - Need configurable lookup table (Map) for
- A1 Policy Type :-: Topics (req & resp)
- Need 2 topics: request and response
- RANSIM will query A1-SIM (adapter) to request lookup table - per A1 Policy Type
- Each message A1-Sim → RanSIM will have a requestID Key - which must be included in the reply RanSIM → A1-SIM to correlate requests & responses.
- Default timeout 30 sec waiting for response.
- Need Near-RT-RIC ID in each message A1 Sim → RanSIM
- Can be ignored by RANSIM - as RANSIM acts as 1 near-RT-RIC, so 1:1:1 mapping A1-SIM : RANSIM : nearRTRIC
- Next week will demo a real A1 Policy Type (prefer the actual use case type) with full end-to-end sequence
- (request) curl/postman → A1(REST) → A1-SIM → kafkaAdapter → kafka broker → RANSIM(stub)
- (response) RANSIM(stub) → kafka broker → kafka adapter → A1-SIM → A1(REST) → curl/postman
|