XMLWordPrintable

      2019-06-04 ArchCom

      Gill presented: https://wiki.onap.org/download/attachments/50202249/Allotted%20Resources%20-%20190602.pdf?api=v2 covering the problem statements to be addressed.  There are:

      1. How To Model (Onboarding and Design Time) a Dedicated NF (e.g.,
        Dedicated_FW)
      2.  How to Model (Design Time) and LCM a Service with Dedicated NF (e.g., Firewall
        Service A)
      3. How To Model (Onboarding and Design Time) and LCM a Shareable NF (e.g.,
        Shareable_FW)
      4. How to Model (Design Time) ana CM  Service with Shareable NF (e.g., Firewall
        Service B)
        1. Two scenarios: "Buld it and tehy will come" vsi "instantiate on the fly".
      5. How to Model (Design Time) a “consuming” Service that doesn’t care
        whether it gets a Shareable or Dedicated NF (e.g., SD-WAN Service)?

      Gills work is not addressing #5 (in red), but addressing 1-4.

       

      Analysis:

      When goingover it there was feedback on the analysis, however it seems that the questions to answer hold.

       

      ----------

       

       

      2019-05-28 ArchCom

      Gill presented xxxxx:

      Breaking this down into smaller points:

      • Abstract capability resolution at runtime. (where a service can desing the need for the abstract "service" that maps down to either a dedicated or shared capability.
      • Alloted Resource is how to model a service that contains a sharable VNF.
        • Onboarding questions:  How do we onboard the VNF, do we need supplementary information.  What information is required from the vendor.  What has to be set to perform the sharing, what is the difference of the experience.
        • Modelling question.  How is it modelled?  At both design time (SDC) and run time (AAI)
          • how do model the resource
          • What are the service indications of modelling
      • Scaling or modifytin a service that was designed using the "abstract capability".

       

      Gil is clarify that he is specifically addressing the "allotted" resource part above.

      • When going in the details, Gil first described the simple case.
      • Then the shared resources has two capabilities.  One repreasenting the VNF as an infrastructure, but one that representes the allocation of the NF capabilities to a service.

      Continue discussion next ArchCom

      The slides that Gil presented were workedon during/post meeting and can be found here: https://wiki.onap.org/download/attachments/50202249/Allotted%20Resources%20-%20190605.pdf?api=v2 

       

       

      2019-04-01 ArchCom F2F

      Gil presented the following https://wiki.onap.org/download/attachments/53248195/Allotted%20Network%20Function%20Presentation%20-%202019%2004%2001.pptx?version=1&modificationDate=1554145767349&api=v2

      • The terminology allocated resource or alloted network function were used synomously.
      • Proposed a definition
      • The question is how ONAP should work with the shared resources
      • Proposes that the shared VNF comes from a VNF not a service
      • There were questions on what the TOSCA representation was
      • There were comments on the relation to ETSI
      • Some corncern regarding the VNFD implications
      • Questions on what a shared resource really is (offline)
      • Relates to discussions ongoing in the resource description
      • Suggestion to bring back into Archcom into 2 weeks.

            Unassigned Unassigned
            auztizza auztizza
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: