I feel we are getting off topic. I think the right question would be "How would Ubernetes handle Cloud bursting".
On Wed, May 25, 2016 at 2:28 PM, 'Tim Hockin' via Containers at Google < [email protected]> wrote: > In general, Ubernetes is not about *migrating* apps, it is about > providing localized service whenever possible, replicating across > geographies, and helping ot make the linkages between disparate > clusters. > > If you want migration, you might consider a cluster of multiple zones > (I am confused by you saying "cloud providers" in the same datacenter. > When we say "cloud provider" we mean AWS vs Google. Not > availability-zone A vs availability-zone B. > > On Wed, May 25, 2016 at 2:21 PM, Gilford Fernandes > <[email protected]> wrote: > > Hi Rodrigo, > > > > I forgot to mention that all cloud providers would be residing in the > same > > data center and not across geographical regions. My concern is what would > > the process include to migrate containers between these providers during > > disaster recovery and would it be seamless ? > > > > Thanks, > > Gilford > > > > On Wed, May 25, 2016 at 1:15 PM, Rodrigo Campos <[email protected]> > wrote: > >> > >> On Wednesday, May 25, 2016, Gilford Fernandes <[email protected]> > >> wrote: > >>> > >>> Hi Rodrigo, > >>> > >>> Thanks for the quick reply. I did read the proposal in the git repo and > >>> to be more precise I want to know about the "Vendor lock in" case which > >>> would allow some containers to be migrated onto other clouds. > >> > >> > >> > >> Not sure what is your question, and I'm not sure it's decided in detail > >> the implementation yet. > >> > >> It will be alpha, I think, in kubernetes 1.3 (and not all be implemented > >> in 1.3, iirc), more will come in future versions. > >> > >> -- > >> You received this message because you are subscribed to a topic in the > >> Google Groups "Containers at Google" group. > >> To unsubscribe from this topic, visit > >> > https://groups.google.com/d/topic/google-containers/B1hSSaw4R08/unsubscribe > . > >> To unsubscribe from this group and all its topics, send an email to > >> [email protected]. > >> To post to this group, send email to [email protected] > . > >> Visit this group at https://groups.google.com/group/google-containers. > >> For more options, visit https://groups.google.com/d/optout. > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Containers at Google" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > To post to this group, send email to [email protected]. > > Visit this group at https://groups.google.com/group/google-containers. > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Containers at Google" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-containers/B1hSSaw4R08/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-containers. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
