This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html
Different containerization technologies have a proprietary format and semantics for the storage application to use. The most critical aspect of these for say storage servers has been networking because the nodes often scale-out and the nodes need to be declared to the containers for proper connectivity. NAS storage is not going away if hard drives continue to be nearline storage.
These same containerization technologies allow any storage or networking services to be deployed as images. This is very helpful to run the same image across a variety of hosts without having to recompile and build the package.
Such an image needs to be built with the help of declared dependencies for the service often called custom resources in the containerization parlance and a logic to reconcile the state of the deployment with the intended declarations. This process is often aided by the sdk from the containerization technology.
The sdk from containers can also help with the scaffolding code generation for use with the service to build and deploy the service as an image. This code is called an operator
The operator used to build and deploy the server as an image for the container is usually one per product. The flavors of the product and its releases can be detailed in the definitions for the same operator.
No comments:
Post a Comment