[kwlug-disc] Thoughts in anticipation of container talk

[Mikalai Birukou]

>>>> With Docker Swarm I can't look inside.
>>>> I thought docker was open source?
>> Ups. I meant there is a nice external exposed UI without a need to
>> source-dive. I'll source-dive for a hack to make it work now, and then, may
>> be. But for choosing a long-used subsystem, thinking about coworkers, you
>> tend to look for external surfaces that will be there for a long time, and
>> will be supported in docs.
> I guess I'm still not following you, unfortunately.  Are the
> docker-swarm, docker-service, docker-node commands and others not
> sufficient?
>
> Or are you looking for a programming API as well?

I don't have a particularly articulated concern, just a nagging feeling 
FOMO-k8s cause I never grasped the whole picture with it. That and 
expectation/need to articulate node updating process, may be tailoring 
them to particulars of my set of boxes -- all these prompt to look at k8s.
But, with recent acknowledgement of trippy ui in k8s docs, I am able to 
form an overall picture, and swarm feels better :| .

Nonetheless, let me air scenarios of interest.

Update of node, it goes down then up, may be in a day, and returning all 
running containers to their original places. How can this be done? In a 
swarm? In k8s?