Uploaded image for project: 'Service Design and Creation'
  1. Service Design and Creation
  2. SDC-815

Tenant Isolation - Context Definition [e1802 - TDP Epic 316484]

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Medium Medium
    • Beijing Release
    • None
    • None
    • Tenant Isolation - Context Definition [e1802 - TDP Epic 316484]
    • To Do

      As an SDC TOSCA Model consumer I would like the TOSCA Model to include the following enhancements for the Tenant Isolation context:

      Overview:
      Overall goal: to be able to run revenue and non-revenue (e.g., test) regular tenants (e.g., VNFs)  and platform tenants (ECOMP components) on production AIC.  The solution here is to have new metadata attributes that describe the environment type (e.g, Production, Test, Development), Tenant Type (e.g., Revenue, Non-revenue) and so on that are used to drive the isolation needed to manage and safely run these workloads on the production cloud.  These new metadata attributes are termed as “Tenant Isolation Context”. Tenant Isolation

      The Isolated Context is the combination of the three context values:
      ·        Environment = Where should I deploy                         = General_Revenue-Bearing
      ·        Tenant = For whom will the deployed service be for    = Test
      ·        Workload = Why do I need to deploy                           = E2E-SIT

      Tenant Type: Defined by SSP, value provided to A&AI via RO during "Tenant Creation", selected by VID or Homing from A&AI as part of instantiation

      Environment context: shall be populated in design time and shall not be modified during instantiation (New service metadata field)
      Workload Context:  Wןill be provided part of the SDC distribution event and will always be provided with  the "Production" workload context value.
      In phase 1 (E1802) VID will not modify the value provided in  the model
      In phase 2 (1802) OPS user will be asked to provide production workload context from a pre-defined list of values, to be populated in the distribution event.

       

      Acceptance criteria:

      • Environment new meta data field is part of service generic information UI
      • Environment is exported in TOSCA for servie with conformance level 5 and up

       

            ml636r ml636r
            rb139a rb139a
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: