Ok, I meant the first thing. I don't need it right now but I might need it in the future to scale out my infrastructure. But I suppose I could also just migrate my entire infrastructure to another provider (I'm not sure if this is directly possible without downtime but I can also first build a new cluster and then switch the DNS)
Op vr 18 sep. 2015 om 22:12 schreef Nate Finch <[email protected]>: > It depends on what you mean. If you mean "can I have some machines on AWS > talk to some other machines in Azure inside the same Juju environment" then > the answer is mostly no (you can use a machine's ssh info to "import" that > machine into an existing juju environment, but it's quite different than > full support of more than one cloud provider in the same environment... > like no ability to automatically spin up or destroy the manually added > machines). To do the import, use juju add-machine ssh@ipaddress to add > the machine to the current environment. > > That being said, as Jose said... if you just want to have a collection of > AWS machines talk to each other and a separate collection of Azure (or > whatever) machines talk to each other (without being able to talk Azure <-> > AWS) then you can create them as separate environments and that works fine. > > On Fri, Sep 18, 2015 at 1:06 PM José Antonio Rey <[email protected]> wrote: > >> Yes. Just set up different environments in your environments.yaml file, >> and then you can switch between them using juju switch. >> >> On 09/18/2015 12:28 PM, Herman Bergwerf wrote: >> > Is it possible to run juju across multiple public (/private) clouds? For >> > example, you can run juju on AWS and select different regions but can >> > you also run juju on AWS and GCP? >> > >> > >> >> -- >> José Antonio Rey >> >> -- >> Juju mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju >> >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
