API Changes to AllWatcher / Environment Tags

[Andrew Wilkins]

On Tue, Feb 18, 2014 at 11:34 PM, Dimiter Naydenov <
dimiter.naydenov at canonical.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
>
> This is an announcement / request for comments for upcoming juju-core
> API changes to the way AllWatcher works and also what URIs/paths the
> API server listens to.
>
> Very soon we'll make a few changes to the way AllWatcher work in the
> API, and also will add a different endpoint for the API server.
>
> 1) Annotations changes to the environment entity will no longer be
> returned with the environment tag as "environment-<uuid>", but instead
> with just "environment". This most likely affects the
> GUI/Landscape/CLI that use the API. It's a minor change, and it's
> needed because we are making all API connections specific to a single
> environment (see the related point 2).
>
> The code that depends on having an environment tag with UUID will need
> to change so that it accepts both "environment" and
> "environment-<uuid>" as valid.


Also, environment-<name> for even more backwards-compatibility, which is
what it was until recently.


> We'll change juju-core to send only
> UUID-less environment tags most likely before the next release (1.18),
> but not before juju API clients are notified.
>

Is this just a tidy-up, or is there a more significant downside to
retaining the UUID in the tag?

2) Right now the API server's URIs for websocket and HTTPS connections
> are plain ("/" for the API and "/charms" for HTTPS, soon to have
> "/log" for access to the consolidated "debug" logs). We'll change the
> API server to start accepting URIs in the form "/<uuid>/" for the
> websocket API and "/<uuid>/charms" for HTTPS respectively. The UUID in
> the URL must match the environment that the client wants to connect to
> and will get a 404 if it does not match the one in state. The old URIs
> will still be usable, but deprecated and about to get removed in a
> future release (likely before 14.04).
>

As Roger pointed out, we'll probably still need a way to discover the UUID.
ISTM that "/" should provide a means of listing environments, after which
you are required to go to "/<uuid>/..."

Thoughts, comments are welcome!
>
> Regards,
> juju-core team
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJTA317AAoJENzxV2TbLzHw7oYH/0IcBpMgSW4zMf0AAf70Mj6B
> vVf5mroSCg2t8drj0+kfFn/YVnOSKfHUC/VqKHV5pk4dCjNK3hx2EY5IhwqYi7tl
> Yx2/V4NjraA2edkfVOgKgySshjFoBfqtOReJfrjLbuHU+gyv7jORbkEkOOruNVTW
> omeSkO8qYvcLUzn0alrsq0/sKUC5PdQ42vNxL+T14fT2A2M8HLgb1tzDibRybXEh
> ZcWuxeJtJlgQyohtXByvSNUpF0dPHbRFogObZPZlKulaD85uj/P/TSwydb6PdoEN
> XDa70VctNuyDTz1GfxzCmiGow/S/87hyOG3gbKAOtYYbMzI5/gwT6sxbZvZnIrg=
> =VkWu
> -----END PGP SIGNATURE-----
>
> --
> Juju-dev mailing list
> Juju-dev at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140219/13e5a0e2/attachment.html>