> > For the past year I have been charming in AWS t1.micro instances. These > have been great resources, and allowed me and others to get started with > charming and knowing the ecosystem. However, I have recently found out that > the support for this instance type has been basically deprecated, and being > replaced by t2.micros. However, I would like to propose getting back to > t1.* as a standard for the following reasons: > > * t2.* instances only allow you to have 10% of the CPU power on the machine > as a basis. They use a credits system, where you can only get 100% CPU use > for a limited period of time, compared to the t1.micro instances, where you > would get 100% CPU usage straightforward, with no credit system. This also > allows you to get more out of the machine, and is ideal for developing > charms. > * t1.micro instances are part of the free tier, and way cheaper than > m1.smalls (which are the Juju default), allowing *anyone* to either get the > free tier and start charming away, or do it for a super low cost. > * When I set the same constraints at bootstrap, it just gives me an error > saying it uses a different HDD type. Could we at least get that fixed? >
Can you please provide the text of the error? > I would like to hear your opinions on getting t1.* back as a default. It > was a great resource, and now I can't even get it by forcing it because it > will throw errors. > We can't use t1.* as the default because depending on one's account and the region used, that instance type is simply not available any more. The default needs to be something that always works out of the box for everyone. We can though look into why you are having trouble using t1 and fix that issue so that at least it is an option for you. -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
