Uploaded image for project: 'Release Requirements'
  1. Release Requirements
  2. REQ-398

Deploy on demand ONAP through CI per use case


    • ONAP use case integration
    • Best Practice (new code only)
    • Not yet performed
    • Original Scope
    • S

      Before editing please read instructions here.

       Description of Use Case / Requirement:


      Integration project is managing several labs in windriver infrastructure (SB-00, SB-01, SB-02, SB-03, SB-04)

      these labs are shared by the different use cases after RC0 (and sometimes earlier if possible)

      The use cases usually need to use staging dockers which lead to regular reinstallation/update and may be incompatible from one use case to another.

      As these operations are still risky, the labs are frequently broken, which has consequences for the use case that triggers the break but also for the other use cases sharing the lab.


      A solution would consist in setting up a lab per use case, the use case will decide the versions they need and could automatically deploy an ONAP on demand corresponding to their need.

      In guilin we could see how to create such On demand ONAP in windriver for 5-10 use cases (we already have 5 + some daily / robustness not fully used during the release cycle management)


      Owners (one of these should be the Assignee - use @ notation):


      Link to HLD/LLD (if any):


      Dependency Relationships with Other Projects:


      Project (ONAP Component #1) IMPACT: Integration

      • Impact Type: create CI chain per use case
      • Company Engagement: Orange
      • Resources: Integration team + Windriver/intel lab
      • Support Status: S/P/N (Supported/Partially supported/Not supported)



      Integration Leads (use @ notation): 



            mrichomme mrichomme
            mrichomme mrichomme
            0 Vote for this issue
            3 Start watching this issue