CB‐Tumblebug Features

Features of the CB-Tumblebug system

Namespace Management

The CB-Tumblebug provides functionalities for creating, viewing, and deleting namespace objects. When a namespace object is created, it includes the name requested by the user and a system-generated UUID. Users can list all namespaces and determine the ID associated with a namespace name, which is essential for querying and controlling *MCIR and *MCIS. Deleting a namespace requires that all associated MCIR and MCIS must first be removed to ensure no resources are left within the namespace.

• MCIR (Multi-Cloud Infrastructure Resource): Cloud infrastructure resources used to create and operate MCIS across multiple clouds. This includes VM images, VM specifications, networks, and access resources. In CB-Tumblebug, MCIR refers to the types of objects used to manage these resources.
• MCIS (Multi-Cloud Infrastructure Service): A logically managed group of cloud infrastructure services (such as VM infrastructures) distributed across various regions, interconnected for specific purposes (applications, services, etc.). In CB-Tumblebug, MCIS refers to the object type used to manage the integrated infrastructure as a whole.

Multi-Cloud Infrastructure Resource Management

CB-Tumblebug provides management functions for creating, registering, viewing, and deleting various types of MCIR, including VM images, VM specifications, networks, and access resources. The detailed functionalities are as follows:

1. VM Image Management

   • Manage VM images that can be included in MCIS.
   • Register VM images with CB-Tumblebug, where each image gets a unique ID.
   • Use registered images as parameters when creating VMs.
   • Provide functionalities to register, view, and delete VM images.

2. VM Specification Management

   • Manage VM specifications that can be included in MCIS.
   • Register VM specifications defined by CSPs with CB-Tumblebug.
   • Use registered specifications as parameters when creating VMs.
   • Key specification elements include the number of vCPUs, memory size, and storage size.

3. Network Management

   • Manage virtual network resources that can be included in MCIS.
   • Register virtual network resources provided by CSPs with CB-Tumblebug.
   • Use registered network resources as parameters when creating VMs.
   • Provide functionalities to register, view, and delete network resources.

4. Access Management

   • Manage resources for accessing VMs in MCIS, including network security groups and SSH key pairs.
   • Provide functionalities to register, view, and delete access resources.

Multi-Cloud Infrastructure Service Provisioning Management

This feature manages all processes involved in creating an MCIS. It includes creating and configuring VMs and integrating them into a logical MCIS object. The detailed functionalities are as follows:

1. Verification of MCIS Placement Requirements

   • Verification the placement requirements for MCIS requested by users.
   • Check for errors and determine if provisioning is possible based on CB-Tumblebug’s managed information.
   • Notify users if the requested requirements cannot be provisioned.

2. Collection of MCIS Placement Information

   • Collect necessary information for optimal MCIS placement, including static information (e.g., specifications, location, price) and dynamic information (e.g., performance data).
   • Use collected information as the basis for optimal MCIS placement scheduling algorithms.

3. Optimal MCIS Placement and Scheduling

   • Perform optimal placement scheduling based on various factors.
   • Support optimal placement for MCIS units, considering factors like network latency between VMs.
   • Provide algorithms for placement based on VM specifications, location, price, and performance.

4. MCIS Provisioning

   • Create MCIS objects and include VMs by leveraging CB-Tumblebug’s VM creation functionalities.
   • Return the creation and access information of the VMs to the user after creation.
   • Manage the lifecycle of newly created MCIS.

Multi-Cloud Infrastructure Service Lifecycle Management

This feature manages and controls the lifecycle of an MCIS after it has been provisioned to the user. It includes managing the operational state, suspended state, terminated state, and ensuring synchronization with the actual lifecycle of VMs managed by CSPs. Detailed functionalities include:

• Managing the lifecycle states of MCIS and ensuring synchronization with CSPs.
• Handling user control requests related to the lifecycle.

Multi-Cloud Infrastructure Service Automatic Control

This feature automatically controls the quality of MCIS based on user-defined rules. Users can specify state conditions and corresponding actions to be triggered when these conditions are met or unmet. The detailed functionalities are:

1. Management of MCIS Automatic Control Requirements

   • Support registering, viewing, and deleting user requests for automatic control of MCIS.
   • Manage automatic control requirements as policies referenced by the scheduler.

2. Determining MCIS Control Conditions

   • Continuously monitor the current state of MCIS to determine if it meets user-requested conditions.
   • Trigger automatic control actions if conditions are met.

3. Execution of MCIS Control Actions

   • Execute user-requested actions when automatic control is triggered.
   • Extendable to include various types of actions.

Multi-Cloud Infrastructure Service Specialized Services

MCIS specialized services address the challenges of managing geographically distributed VMs in a multi-cloud environment. These services include "MCIS Unified Subnet Environment (MC-VPN)" and "MCIS Load Balancing (MC-LB)" and can be expanded as needed.

1. MCIS Unified Subnet Environment (MC-VPN)

   • Set up a unified subnet environment for VMs across different clouds using VPN technology.
   • Enhance communication security and allow certain distributed applications to operate seamlessly.
   • Assign private IPs in the same subnet to all VMs in the MCIS.

2. MCIS Load Balancing (MC-LB)

   • Provide load balancing for VMs that are geographically dispersed across a multi-cloud environment.
   • Improve response time and availability by distributing workloads among VMs.
   • Automatically include new VMs in the load balancing pool as they are added to the MCIS.