![]() ![]() ![]() Allocate tenants to existing deployments or stamps, which is sometimes called tenant placement. ![]() Common maintenance operations include deleting or archiving old data, creating and managing database indexes, and rotating secrets and cryptographic certificates. Perform automated maintenance operations.More advanced control planes might also take on more responsibilities: Your solution's control plane probably needs to interact with the control planes for the services and technologies that you use, like Azure Resource Manager or the Kubernetes control plane. In this scenario, your control plane might have additional responsibilities, like deploying or reconfiguring Azure infrastructure whenever you onboard a new tenant. In contrast, suppose your solution uses a deployment model that requires tenant-specific infrastructure, like the automated single-tenant model. For example, whenever a new tenant signs up to your service, the control plane could update the appropriate records in a database so that the rest of the system is able to serve the new tenant's requests. If you use the fully multitenant tenancy model and don't deploy any tenant-specific resources, a basic control plane might just track tenants and their associated metadata. Consumption metrics might inform your billing systems, or they might be used for resource governance. Measure each tenant's consumption of your system's resources.Track each tenant's use of your features and the performance of the system.Handle tenant lifecycle events, including onboarding, moving, and offboarding tenants.Store and manage the configuration of each tenant.For example, your control plane might configure network routing to ensure that incoming traffic is mapped to the correct tenant's resources. Reconfigure shared resources to be aware of new tenants.Your control plane might invoke and orchestrate a deployment pipeline that's responsible for deployments, or it might run the deployment operations itself. Provision and manage the system resources that the system needs to serve the workload, including tenant-specific resources.In general, a control plane might have many of the following core responsibilities: In other multitenant solutions, the control plane has only basic responsibilities. In some multitenant solutions, the control plane has a wide range of responsibilities and is a complex system in its own right. Your solution's requirements and architecture dictate what your control plane needs to do. ![]() There's no single template for a control plane or its responsibilities. The following sections provide the details you need to scope and design a control plane. When you design multitenant solutions, you need to consider control planes. Almost all software as a service (SaaS) solutions have a control plane to handle cross-tenant tasks. The Kubernetes control plane manages many tasks, like the placement of Kubernetes pods on worker nodes. For example, the Azure control plane, Azure Resource Manager, is a set of APIs, tools, and back-end components that are responsible for deploying and configuring Azure resources. Many complex systems include control planes. Or data plane and control plane tasks would be mixed together, overcomplicating the solution. If the system didn't have a control plane, administrators would need to run many manual processes. The control plane is the component that onboards new tenants, creates databases for each tenant, and performs other management and maintenance operations. Your tenants probably think of it as the way to use the system for its intended purpose. The data plane is likely the primary application component for your solution. When end users access the system to view and enter their financial records, they use the data plane. Multiple tenants store their financial records in the system. This article provides information about the responsibilities of control planes and how to design a control plane that meets your needs.įor example, consider a bookkeeping system for managing financial records. The control plane is the component that manages higher-level tasks across all tenants, like access control, provisioning, and system maintenance to support your platform administrators' tasks. The data plane enables end users and clients to interact with the system. A multitenant solution has multiple planes, and each has its own responsibilities. ![]()
0 Comments
Leave a Reply. |