Versions Compared

Old Version 2

changes.mady.by.user Sastry Isukapalli

Saved on

compared with

New Version 3

changes.mady.by.user Sastry Isukapalli

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Plans to create the test scenarios (we all need to sync up on some minimal cases to cover)
  2. What emulators/mocks are needed for different components?
    1. OSDF needs emulators for Policy, Conductor, and SO-call-back for vCPE use case
      1. May need MultiCloud and A&AI emulators for stretch goals (Ramki to update this)
    2. HAS needs OSDF MultiCloud, A&AI, MUSIC (real/emulator) (Shankar to update this)
      1. Do you plan to do each HAS component as a separate functional test?
      2.  Or, do you plan to club all HAS containers and MUSIC together and test it in an “integration mode”?

...

      1. Shankar/Leo, please update/clarify these
  2. Do we have representative payloads for different scenarios
    1. Policy: Ankit
    2. MultiCloud: Shankar/Ramki
    3. A&AI: Shankar
    4. Request from SO: Ankit/Sastry
    5. Request from CM Portal: Sastry/Ankit
    6. Multiple responses from Conductor: Ankit/Sastry/Leo/Shankar
    7. Request from OSDF to Conductor: Sastry/Ankit
  3. Dockerization requirements for Functional Testing: Ikram/Leo/Ramki/Sastry/Shankar
  4. Plans to start involving the integration team soon (for guidelines, their requirements, tips, etc.)
  5. Any potential bottlenecks (focus only from a functional testing view point)
  6. Do we have some plans for generating and/or using simulated datasets 
  7. If time allows, also sync up on unit test status

Attendees

Goals

Discussion items

Substantial discussion on scaling of the optimizer (we need to think about cloud awareness, aggregates, reservations, etc.) Do these occur at edge cases (heavy resource constraints) or are they expected to be common?
TimeItemWhoNotesArchitecture Review








Action items

  •  Offline Meetings 
    •  Functional testing (Leonardo, Dileep, Ikram, Sastry)
    •  SONAR coverage (Dileep, Amjath, Ikram, Sastry)
    •  Dockerization sync up (Ramki, Ikram, Shankar, Sastry)
      •  Build scripts need to be provided by individual projects (shell script for building)
    •  CMSO-Simple API (Jerry, Ankit, Sastry) – Sastry to pull in someone for CMSO use case
    •  Template for homing (Dileep, Ankit, Ritu, Shankar)
    •  SO API (Ankit, Shankar, Ramki, Dileep, Ritu, Seshu and Shankar) – Ankit/Shankar to reach out to Seshu from SO
    •  

      Multicloud API (Ankit, Ramki, Dileep, Ritu, Sastry, Shankar) – Ramki and some other Multicloud person

     

    A&AI API consuming (Ankit, Ramki, Sastry, Shankar)  – Need to identify contacts from A&AI

    Plan for next steps for Music
  •  Conductor: Pre-requisite is to push the Docker images to Nexus Tree
  •