Versions Compared

Old Version 29

changes.mady.by.user Pankaj Goyal

Saved on

compared with

New Version 30

changes.mady.by.user Pankaj Goyal

Saved on

Key

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

...

The Cloud Infrastructure workload onboarding process describes activities needed for the integration of tenants' workloads into the Cloud Infrastructure environment. Typically, this business process consists of the following key phases:

  1.  Tenant Engagement and Workload Evaluation:
    1.  In this phase the request from the tenant to host a workload on the Cloud Infrastructure platform is assessed and a decision made on whether to proceed with the hosting request.
    2. This phase may also involve the tenant accessing a pre-staging environment to perform their own evaluation and/or pre-staging activities in preparation for later onboarding phases.
  2. Workload Packaging:
    1.  The main outcome of this phase is to produce the workload deployable image and  the deployment manifests (such as TOSCA blueprints or HEAT templates or Helm charts) that will define the Cloud Infrastructure service attributes for the workload. 
    2. The workload packaging can be performed by the tenant, through self-service capabilities or by the Cloud Infrastructure Operations team.
  3. Workload Validation and Certification:
    1. In this phase the workload is deployed and tested to validate it against the service design and other Operator specific acceptance criteria, as required.
    2. Workload validation and certification should be automated using CI/CD toolsets / pipelines and Test as a Service (TaaS) capabilities.
  4. Publish Workload:
    1. After the workload is certified the final onboarding process phase is for it to be published to the Cloud Infrastructure  production catalogue from where it can be instantiated on the Cloud Infrastructure platform by the tenant.

...

  • Validate that the Capacity can satisfy the tenant requested quota for vCPU, RAM, Disk, Network Bandwidth
  • Validate that the Cloud Infrastructure can meet tenant's performance requirements (e.g. I/O, latency, jitter, etc)
  • Validate that the Cloud Infrastructure can meet tenant's resilience requirements
  • Validate any requested private flavours
  • For VM-based environments:
    • Verify that any requested private flavours have been created
    • Verify that the metadata for these private flavours have been created
    • Verify that
    he
    • the tenant has permissions to use the requested private flavours
    • Validate that host aggregates are available for specified flavors (public and private)
    • Verify that the metadata matches for the requested new flavours and host aggregates
  • Verify that the networks requested by the tenant exist
  • Verify the metadata: 1. Keypairs must be higher than default 2. Networks must be higher than default
  • Add all Tenant Members and configure their assigned roles in the Enterprise Identity and Access management system (e.g., LDAP)
  • Create Tenant
  • Using a proto- or Tenant provided HEAT-template onboard /Helm-chart for a NF and perform sanity test (e.g., using scripts test creation of VM/container, ping test, etc.)
  • Verify and Validate Tenant Images: virus scan, correct OS version and patch, etc.

...