maryvilledev / cnvm Goto Github PK

At enteon.com/cnvm: see, for instance, the Open and Shared sections (but it's all the links). They look like:

https://www.google.com/url?q=http://www.linuxfoundation.org/&sa=D&usg=AFQjCNHe5YcDR6SiZJhb60_toEt-PD8inw

If this is SEO, it's a pretty unsubtle way of doing it.

(reported to me by Andy Latham)

churn (as pertains to p2p networks) - a node entering or leaving the network.

The only piece that I don't see here is that one. I'm going to describe the solution that we have planned for dealing with this below, and would love to hear your thoughts on to what extent this solution

A) Scales
B) Works alongside of what you've got now overall

My initial thought was to centralize storage, but centralization (blah blah blah)

My new thought is to use something like SyncThing to ensure that all of the nodes always have the same registry of images & container diffs. This way, when a node goes down, and something (might want to have a look at the unfinished github.com/superordinate/kdaemon) brings the containers back up, things are exactly as they were. In order for the kinds of use cases I'm pursuing to work out, I've got to create a situation where containers are relaunched when their host goes down, and also must account for the fact that we will not be able to predict nodes departure from the network.

(I should mention that I do not consider this a great or full solution)