Docker and Kubernetes

-
It seems that Docker Inc quest to container orchestration market comes to the end.

Some days ago Solomon Hykes announced that the commercial Docker offering include Kubernetes together (yet) with Swarm: Docker Platform and Moby Project Add Kubernetes
The same at OSS side: Moby and Kubernetes

It was rumored for some time for a reason - Docker Inc alone cannot compete with Google overwhelming marketing power behind Kubernetes as well as with the legacy and user base of Mesos. While for being not alone Docker lost to K8s - after few Docker twists with its products the majority of both development and enterprise communities stopped considering Swarm as an option for container orchestration.

It's somewhat pity because it is becomes one-product market. K8s management learned well the Linux success model and is apparently doing with Mesos the same as Linux did with Unix.

Комментарии

Отправить комментарий

Популярные сообщения из этого блога

How to work with authentication in Zookeeper?

-
Изображение
In this article, I tried to collect all my experience and add links which I used to set up authentication in Zookeeper. First of all, you need to run Zookeeper (ZK) with the password for "super" user. We need to use DigestAuthenticationProvider for this. Need to generate digest of a given password and after that, you can run Zookeeper with option -DSERVER_JVMFLAGS=-Dzookeeper.DigestAuthenticationProvider.superDigest=super:<password digest> How to generate digest of a given password. For generating  digest you need to do next: /bin/java -cp "/opt/zookeeper-3.4.9.jar /opt/lib/slf4j-api-1.6.1.jar" org.apache.zookeeper.server.auth.DigestAuthenticationProvider super:pass (by link , you can find a slightly different way). The output will be: super:CiymZRNkXx0HJFQhdpGmqJqKuHM= Please note: this is example and digest may not match the password. After that, you need to set SERVER_JVMFLAGS and restart Zookeeper: export SERVER_JVMFLAGS="-Dzookeeper....
Далее...

How-to use cUrl for work with ZKUI.

-
Изображение
ZKUI is an open source (under Apache 2.0 license ) a UI dashboard that allows CRUD operations on Zookeeper. But sometimes you can want to upload something to the Zookeeper via ZKUI automatically. And as far as I could understand ZKUI don't have API for this purpose, but you can always use cUrl . First of all, you need to authenticate in the ZKUI using LDAP login/password: curl -c COOKIE --data "username=USERNAME&password=PASSWORD&action= 'Sign In' " https: //ZKUI_ADDRESS/login After that, you can use the COOKIE file to communicate with ZKUI. Use the next commands: To export all data to a file: curl -c COOKIE -b COOKIE -s -S "https: //ZKUI_ADDRESS/export?zkPath=/" > FILE To import data from a file: curl -c COOKIE -b COOKIE -s -S --form scmFile=@FILE --form Import=submit https: //ZKUI_ADDRESS/ import Please note: you can set "--form scmOverwrite=true" if you want to overwrite existing properties. ...
Далее...

Consul-template: how to run exec command, if file changed? Create a "watcher" via consul-template.

-
You can create a "watcher" via consul-template using file function.   But for this function we need to create source and destination files. If you want to simply monitor one file and destination file is unwanted, you can do simple trick using optional command in consul-template, something like this: template {     contents = "{{ file \"$WATCHING_FILE\" }}"     destination = "$DEV_NULL_FILE"     command = "/bin/sh -c 'rm -f $DEV_NULL_FILE'" } In this template we monitor $WATCHING_FILE. If it changed, consul-template creates new $DEV_NULL_FILE  and triggers command  "/bin/sh -c 'rm -f $DEV_NULL_FILE'" which delete this file. So finally we can have exec block, which is triggered after this template.  
Далее...