API work

[John Arbash Meinel]

-----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.

> 
> upgrade-juju: this requires get/set-environment
> 
> deploy, upgrade-charm: These require some way of uploading charms. 
> By the way, what's our maximum size for charms, and for RPC 
> messages?

AFAIK there isn't a maximum size for charms (we know there are ones
that are 100s of MB).
RPC doesn't specifically have a maximum size (AFAICT). Though it
doesn't really do streaming. So user experience uploading 100MB of a
charm is going to be a bit poor.

I know Roger had the idea of switching to a plain HTTP PUT/POST for
uploading charms. However, I don't know that it is actually *easier*
to switch out of the RPC object and do something else.

We could do things like upload in chunks as part of the RPC structure
itself (so each RPC.put is a 1MB upload sort of thing).

> 
> 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.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlJ4w1IACgkQJdeBCYSNAAPz8gCgtceZL3lPy1+/36oX3sw5Ae8h
i0IAoKrz5d/uIAB9AusM6P3mExNZ5D/s
=Pbh7
-----END PGP SIGNATURE-----