Re: Upcoming changes for the ec2 provider

[Mark Shuttleworth]

On 06/10/16 16:33, Andrew Wilkins wrote:
> On Fri, Oct 7, 2016 at 7:26 AM Mark Shuttleworth  > wrote:
>
> On 06/10/16 16:14, Andrew Wilkins wrote:
>> On Thu, Oct 6, 2016 at 8:30 PM Rick Harding
>> >
>> wrote:
>>
>> Thanks Andrew, this is great to hear. Can I bug you about
>> details as to how it works? Does this introduce their pricing
>> API as a blocker to deploying with Juju? If they introduce a
>> change to the API we miss or their API goes down is there any
>> sort of cache of the info that users can continue with until
>> service is restored?
>>
>>
>> So I said API because that's what it's called by AWS, but IMO
>> it's a bit of an overstatement. It's just a set of (very large)
>> JSON files in a well defined location. Very large, as in 48M for
>> the one file that we need.
>>
>> Because it's so big, pulling that down each time you go to
>> bootstrap isn't really reasonable. So for now, we're doing that
>> at build time, and the information is still hard coded into the
>> client. The process can be automated, so there shouldn't be a
>> great lag time between updates and bringing them into a Juju release.
>>
>> We intend to update Juju later to periodically pull down the JSON
>> file server-side, asynchronously, so a running controller will
>> get the updates without us having to release a new Juju or you
>> having to upgrade.
>
> Could we not process the file on our side regularly and publish a
> (smaller) just-what-juju-needs bit of json at a well-known
> location ourselves?
>
>
> Yes, we could. There was some discussion about doing that, and someone
> brought up concerns that I can't recall (or find) now. We will explore
> this option further.

This feels to me like it's a simple extension of what we currently
provide to 'update-clouds'. It should be a general thing, not just for
one specific provider.

Mark
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Upcoming changes for the ec2 provider

[Mark Shuttleworth]

On 06/10/16 16:14, Andrew Wilkins wrote:
> On Thu, Oct 6, 2016 at 8:30 PM Rick Harding
> > wrote:
>
> Thanks Andrew, this is great to hear. Can I bug you about details
> as to how it works? Does this introduce their pricing API as a
> blocker to deploying with Juju? If they introduce a change to the
> API we miss or their API goes down is there any sort of cache of
> the info that users can continue with until service is restored?
>
>
> So I said API because that's what it's called by AWS, but IMO it's a
> bit of an overstatement. It's just a set of (very large) JSON files in
> a well defined location. Very large, as in 48M for the one file that
> we need.
>
> Because it's so big, pulling that down each time you go to bootstrap
> isn't really reasonable. So for now, we're doing that at build time,
> and the information is still hard coded into the client. The process
> can be automated, so there shouldn't be a great lag time between
> updates and bringing them into a Juju release.
>
> We intend to update Juju later to periodically pull down the JSON file
> server-side, asynchronously, so a running controller will get the
> updates without us having to release a new Juju or you having to upgrade.

Could we not process the file on our side regularly and publish a
(smaller) just-what-juju-needs bit of json at a well-known location
ourselves?

Mark
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Upcoming changes for the ec2 provider

[Rick Harding]

Thanks Andrew, this is great to hear. Can I bug you about details as to how
it works? Does this introduce their pricing API as a blocker to deploying
with Juju? If they introduce a change to the API we miss or their API goes
down is there any sort of cache of the info that users can continue with
until service is restored?



On Thu, Oct 6, 2016 at 4:52 AM Andrew Wilkins 
wrote:

> Hi folks,
>
> Just a heads up to let you know about some changes made to the ec2
> provider, which will show up in Juju 2.0.
>
> We are now pulling down the Price List API (
> http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/price-changes.html)
> and using that to determine which instance types to launch. This means that
> you will have access to more instance types now, and we should have more
> accurate/up-to-date pricing information, and region availability.
>
> The default constraints for controllers has been modified, so that on ec2
> we will now default controller machines to t2.medium, as long as you have a
> default VPC in your region, or you specify one by ID (--config vpc-id=...).
> We were previously defaulting to m3.medium. The t2.medium instances have a
> little more memory, and 2 CPUs instead of 1. They are burstable instances,
> so they should suit controllers managing a small-to-medium set of
> applications. Controllers are now started with 32GiB root disk, instead of
> 8GiB as they were before.
>
> As before, you can override the defaults by specifying constraints at
> bootstrap time. Also, these changes do not affect non-controller instances.
> If you use "add-machine", you will get an m3.medium if your region supports
> them.
>
> Cheers,
> Andrew
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Upcoming changes for the ec2 provider

[Andrew Wilkins]

Hi folks,

Just a heads up to let you know about some changes made to the ec2
provider, which will show up in Juju 2.0.

We are now pulling down the Price List API (
http://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/price-changes.html)
and using that to determine which instance types to launch. This means that
you will have access to more instance types now, and we should have more
accurate/up-to-date pricing information, and region availability.

The default constraints for controllers has been modified, so that on ec2
we will now default controller machines to t2.medium, as long as you have a
default VPC in your region, or you specify one by ID (--config vpc-id=...).
We were previously defaulting to m3.medium. The t2.medium instances have a
little more memory, and 2 CPUs instead of 1. They are burstable instances,
so they should suit controllers managing a small-to-medium set of
applications. Controllers are now started with 32GiB root disk, instead of
8GiB as they were before.

As before, you can override the defaults by specifying constraints at
bootstrap time. Also, these changes do not affect non-controller instances.
If you use "add-machine", you will get an m3.medium if your region supports
them.

Cheers,
Andrew
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju