Uploaded image for project: 'ONAP Architecture Committee'
  1. ONAP Architecture Committee
  2. ONAPARC-495

MultiCloud K8s Multi Tenancy

    XMLWordPrintable

Details

    • Epic
    • Status: Closed
    • Medium
    • Resolution: Duplicate
    • None
    • None
    • MultiCloud K8s Multi Tenancy

    Description

      All the details captured in the ONAP proposal -<link will be provided>

      Requirement

      1. For a service provider, a tenant is basically a group of end-user sharing the same cluster, we have to make sure the end user resources are tracked and accountable for their consumption
      2. In a few cases, admin or end-user application is shared among multiple tenants, in such case application resource should be tracked across the cluster
      3. Centralization resource quota or the allocation limits for requirements 1 and requirement 2
      4. In Edge use case, the service orchestration like ONAP should get the resource details across multiple clusters through resource orchestration, should set the resource allocation for the cluster and decide the scheduling mechanism
      5. User credential centralization with application orchestration

      Divide the Req 1 to Req. 5 as the story for the Multi Cloud K8s Tenancy

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            r.kuralamudhan Kuralamudhan Ramakrishnan
            r.kuralamudhan Kuralamudhan Ramakrishnan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: