On Tue, Nov 5, 2013 at 6:22 PM, William Reade
wrote:
> On Tue, Nov 5, 2013 at 10:25 AM, Andrew Wilkins <
> andrew.wilk...@canonical.com> wrote:
>
>> As I've been looking for things to bite off, here's some comments from me
>> (excluding things others are already looking into).
>>
>> api-endpoints:
New instance type, high GPU: g2.2xlarge: 15 GiB memory, 26 EC2 Compute
Units, 1 x NVIDIA GRID GPU (Kepler GK104), 60 GB of local instance storage,
64-bit platform
http://phx.corporate-ir.net/phoenix.zhtml?c=176060&p=irol-newsArticle&ID=1872208&highlight=
Also, m3 instances dropped in price:
htt
Hi all,
Pursuant to discussions at the sprint on how to make implementing
interfaces easier for charm authors, I have written an initial
document for the mysql charm:
https://docs.google.com/a/canonical.com/document/d/1WTws_k5K__NAsfZwxf-oKHYqZnZYvrg7K58MvOHFpAY/edit#
It would be very cool if peop
Thank you for the updates, Andrew. When you have a chance, would you mind
talking with me about debug-log, uploading a charm, and the associated
changes to deploy and upgrade-charm? The GUI definitely cares about those
and I'd like to make sure we have talked through the design to make sure we
can
On Tue, Nov 5, 2013 at 4:25 AM, Andrew Wilkins wrote:
> I thought I'd summarise where things are at now, in case anyone else
> starts looking for work to do. Ignoring the DONE's, we have the following
> remaining (see below for commentary):
>
> api-endpoints: TODO
> [axwalk] debug-hooks: INPROGRE
On Tue, Nov 5, 2013 at 10:25 AM, Andrew Wilkins <
andrew.wilk...@canonical.com> wrote:
> As I've been looking for things to bite off, here's some comments from me
> (excluding things others are already looking into).
>
> api-endpoints:
> (I don't recall why we put this in the list at all? What n
> > status: haven't looked into in detail, looks like a big task.
> > don't forget filters :)
>
> Well, we don't support filters today, so we don't have to do all the
> design in the first pass.
>
We do - I added it to fix a pyjuju parity bug. It shouldn't be difficult to
handle, anyway.
Cheers,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
> api-endpoints: (I don't recall why we put this in the list at all?
> What needs to be done here?)
"juju api-endpoints" is a CLI command, seems like it should use
APIAddresses via the API so that it can return all possible API servers.
>
> up
I thought I'd summarise where things are at now, in case anyone else starts
looking for work to do. Ignoring the DONE's, we have the following
remaining (see below for commentary):
api-endpoints: TODO
[axwalk] debug-hooks: INPROGRESS
[axwalk] debug-log: INPROGRESS
deploy: TODO
destroy-environment:
