![]() ![]() How would this differ from just stacking containers to create this? It would enable further development of seamless integration of the founding layers of what this container carrier is made up of, improving stability and specialization.How would this differ from a setup with a regular VM? You would still have the lightweight, easily transportable qualities of containers.Just like in the analogy with container carriers in maritime logistics, these would be larger founding blocks on which various containers can be stacked. Wouldn’t it be an idea to extend this train of thought and also introduce container carriers? Repeatable, but in a sense also complex, complexity by the sheer number of layers that compromise the stack. For instance, a Webserver is stacked upon an instance of bash, stacked upon it’s dependencies, creating an container stack which is capable of serving http-requests at port 80 of the up-address inherited from the IP-stack underneath the bash-instance. I would want to argue that one can containerize a stack too deep (or too high, depending on your viewpoint).Ī container, typically, is an isolatable element which can be stacked upon another isolatable element. This though is not what I wanted to discuss. I think containerization and micro services, for instance have a lot less in common that some would lead you to believe. In my opinion you should be careful to mix and match too intensively. Obviously there is a lot of confusion about this as well. We have seen and read many good and informative blog-posts and presentations about this. In fact, containers in IT are a concept which is 1-on-1 derived from these physical containers. Sitting in the plane, the following thoughts occurred to me… In maritime logistics containers and container carriers are not really new. ![]() It is safe to promote.įor troubleshooting and checking purposes, there are very informative logs in /var/log/efm-2.1ĮFM truely is a very nice tool to add resilience and flexibility to your PostgreSQL database cluster configuration. efm set-priority efm pg-10 1 makes node pg-10 the first node in the standby priority listĮvery 2.0s: efm cluster-status efm Sun Aug 27 10:02:49 2017.efm promote efm -switchover makes the first slave in the standby priority list the new master and converts the precious master to slave.efm allow-node efm pg-11 allows node pg-11 to join the EFM cluster.Precede this with the linux watch command and you can monitor this nicely. efm cluster-status efm gives you a nice overview of what is happening.The efm-command allows you to manage your cluster. ![]() Systemctl start efm-2.1 and your cluster is running!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |