The "problem" with Google, is you can actually customize the CPU/Memory arbitrarily per instance. So they have recommended instance types, but you can change those properties. I'm not sure why you're getting an n1-highcpu-4. Default bootstrap for me has been a n1-standard-1
Marco On Tue, Jan 10, 2017 at 4:11 AM John Meinel <[email protected]> wrote: > I'm not sure how we are selecting the instance type on GCE, but I do > believe our default instance type on AWS is 2 CPUs and 2+GB of RAM. > > I believe our old default was something like an m3.medium, (1CPU, 3.75GB > of ram), and we recently switched to target a t2.medium when available > (2CPU, 4GB ram), which is credit based in that you don't get flat-out CPU, > but if you burst a bit, you can use the full cpu speed. > > It certainly sounds like 2-cpu instance type in GCE matches better what > our current expectations are. As always you can use: > juju bootstrap --boostrap-constraints "mem=X cpu-cores=Y" > To set what you want for the bootstrap machine. > John > =:-> > > > On Mon, Jan 9, 2017 at 11:38 PM, Matthew Williams < > [email protected]> wrote: > > Hello Juju Fans, > > I've recently been playing around with Juju on GCE. Google is suggesting > that I could downgrade the instance type to save some money (attached > screenshot) > > I was wondering if anyone else had something similar, and therefore, does > this suggest our default controller instance type on GCE is bigger than we > need? > > (The attached screenshot would be a saving of $47 per month) > > Matty > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev > > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
