design icon indicating copy to clipboard operation
design copied to clipboard

design how to support component node migration between containers

Open tfoote opened this issue 10 years ago • 2 comments
trafficstars

This was mentioned in #34 but needs it's own discussion. deferred here

tfoote avatar Sep 22 '15 00:09 tfoote

Semantic nitpick:

Could we use a different word than "migration" for this issue? The term is a bit overloaded from the mostly unrelated context of migrating to a new version of an API, etc.

Some other ideas: "transferring" nodes between containers "swapping" nodes between containers

I suppose an argument against these choices, especially "swapping", is that they imply that the process is fast and seamless, while "migration" implies that the process takes time and overhead (copying the node resources to a new container).

jacquelinekay avatar Sep 28 '15 18:09 jacquelinekay

I think the term migration fits this use case very well and does by no mean imply effort. The same term is used for very similar technology: https://en.wikipedia.org/wiki/Live_migration

dirk-thomas avatar Sep 28 '15 18:09 dirk-thomas