OpenSDS introduces CSI aims to define an industry standard that enables storage vendors (SP) to develop a plugin once and have it work across several container orchestration (CO) systems. The container orchestration (CO) systems include Kubernetes, Docker Swarm, Cloud Foundry and so on.
Container orchestration platform is especially beneficial when running microservices in containers. Kubernetes and Docker Swarm are the top orchestration production.
Pluggable storage interface (PSI) allowing storage vendors to plugin into systems. Popular container orchestration (CO) or middleware have independently evolved storage interfaces. It causes painful to storage providers because they have to build those different types of interface for different CO’s.
Also, it was causing problem for cost providers because they have to understand different types of standards, eventually causes issues to users.
Existing interfaces creating problems like CLI based interface, lack of Idempotency on API’s, too heavyweight and so forth.
To overcome such issues, Container Storage Interface (CSI) has been introduced which provides interoperability which helps storage vendors to create single plugin and that plugin can be used by system’s that supports CSI. CSI also overcome problems like Vendor neutral, focus on specification and so on.
Container Storage Interface in a cloud native environment have container orchestration system, storage vendors, storage container orchestration systems. Container Orchestrators (CO’s) include the Kubernetes, Docker Swarm, Cloud Foundry, Mesos.
Figure: Container Storage Interface
Pluggable Storage Interface (PSI) allowing storage vendors to plugin into system. CSI provides container orchestrators with following capabilities.
Figure: Lifecycle of a new volume request
The above diagram illustrates the lifecycle of a new volume request.
The create volume and delete volume calls are used to create and delete a volume on the storage platform. Once a volume is created ControllerPublishVolume/ControllerUnpublishVolume ensure that an existing volume is made physically available to a container host.
NodePublishVolume/NodeUnpublishVolume is used to associate a volume with a specific container. All these happens in dynamically provisioned volume.
In case of Pre-provisioned volumes, the plugin simply maps and publishes volumes to a host.
CSI is designed and divided into different architecture diagrams that specifies how the plugins are deployed. The focus of this architecture is between CO and Plugin for a different deployment architecture.
Scenario 1 is an architecture diagram of master/node separate CSI. It shows the plugin runs on all the nodes in the cluster. The controller plugin is available on the master host whereas the node plugin is available on the node host.
Scenario 2 is an architecture diagram of Headless combined CSI. In this, only the CO node host run plugins. The controller plugin and the node plugin split the component plugins separately.
Scenario 3 is an architecture diagram of headless plugin deployment. Here only the CO node host run plugins. The unified plugin component supplies both controller and node service.
Container Storage Interface, its volume and plugins provide a clear benefit for the CO’s and storage vendors. Due to the interfaces, it not only helps developers but also future CO’s to easily implement and test CSI.
Businesses and organizations are moving their workload to the cloud for better agility, performance, and security. Cloud computing is the bellwether of hosting applications and databases to improve the overall efficiency of business processes. The disparity between the on-premise workload and cloud environment workload often results in businesses migrating the workload to the cloud. Cloud technology shows impeccable growth contributing to the adoption of cloud-based computing across many businesses and organizations.
Centaurus, a next-generation cloud for the telecom sector, is an open-source project for building cloud infrastructure platform that can be used to build and manage public or private clouds, edge computing, and edge device datacenter. It is a solution to address key challenges of large-scale clouds such as system scalability, resource efficiency, multi-tenancy, edge computing, and the native support for the fast-growing modern workloads such as containers and serverless functions. Centaurus helps in creating multiple nodes, managing infrastructure, containerizing the environment, managing the pods, and many more.
Cloud computing is picking up the pace replacing the traditional methods of storing the data, accessing, and running the applications. Cloud migration is the process to shift the existing data, applications, and other business elements from data centers or one cloud to other cloud environments for better scaling. Organizations are shifting their businesses on cloud for more speed and agility. Migration to cloud gives the organization limitless computing resources.
Click2Cloud support enterprises throughout their cloud infrastructure deployment process and empowers them with private cloud offerings, a cloud framework for compute, storage, and network services. To get the benefit of hybrid cloud and Edge computing an enterprise can accelerate the use of OpenStack, Apsara Stack, and Azure Stack services to transform technologies into cloud and deep industry growth to deliver abiding value.
This blog will give you a complete understanding on billing, budget, and cloud cost optimization. Cloud cost management is as important as knowing your bills. It is important to know your cloud spends and which cloud offers you a good service at minimal costs. Click2Cloud also offers you a semi-automated assessment platform “ CloudsIntel” to support you with assessment and migration plan
7 Temasek Boulevard, #12-07, Suntec Tower One, Singapore 038987
No 5, 17/f, strand 50 50 bonham strand, Sheung wan, Hong Kong