Re: API Changes to AllWatcher / Environment Tags
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18.02.2014 17:03, John Meinel wrote: Can we make the API /uuid/api ? That makes them all peer paths. Sure we can, I like that better in fact! Dimiter John =:- On Feb 18, 2014 7:43 PM, Dimiter Naydenov dimiter.nayde...@canonical.com mailto:dimiter.nayde...@canonical.com wrote: 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. 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. 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). Thoughts, comments are welcome! Regards, juju-core team -- Juju-dev mailing list Juju-dev@lists.ubuntu.com mailto:Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTA4Y3AAoJENzxV2TbLzHwvD8IAKH0GLvSmCx6mBxuTuKiLUsK UlDogXv26jXIFm/rcoXVY1gM6hESbZPBkuFv95ruyvDmc8zQc2471zayD7k7ydaY pWam7GImq/X/QEW9gGkPXx+5RqaBIaimuqbyiASj2I8aUArwBANWAGBKVyZEiud0 c1y7XpkwsyOLzgQLY2LNh+OZwvlIgkl2NxWz8ptGipU17vsBYbcPjwbA9JYfHdnl egASETYLzLyQfP6o9gJeyuU4QtikO5l/JanQfogEgoIk5H/Mm4tUek6MZLYFaYOd K5PFm7ph5DjWwbEtadLb1rX45+mA4bD1ouYDTyAcA21p+Hmay8J+Z7D8je1G8yA= =Gq1Q -END PGP SIGNATURE- -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: API Changes to AllWatcher / Environment Tags
how does the api client know the uuid prior to connection? jenv parsing on cli where applicable? On Tue, Feb 18, 2014 at 11:11 AM, Dimiter Naydenov dimiter.nayde...@canonical.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18.02.2014 17:03, John Meinel wrote: Can we make the API /uuid/api ? That makes them all peer paths. Sure we can, I like that better in fact! Dimiter John =:- On Feb 18, 2014 7:43 PM, Dimiter Naydenov dimiter.nayde...@canonical.com mailto:dimiter.nayde...@canonical.com wrote: 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. 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. 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). Thoughts, comments are welcome! Regards, juju-core team -- Juju-dev mailing list Juju-dev@lists.ubuntu.com mailto:Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTA4Y3AAoJENzxV2TbLzHwvD8IAKH0GLvSmCx6mBxuTuKiLUsK UlDogXv26jXIFm/rcoXVY1gM6hESbZPBkuFv95ruyvDmc8zQc2471zayD7k7ydaY pWam7GImq/X/QEW9gGkPXx+5RqaBIaimuqbyiASj2I8aUArwBANWAGBKVyZEiud0 c1y7XpkwsyOLzgQLY2LNh+OZwvlIgkl2NxWz8ptGipU17vsBYbcPjwbA9JYfHdnl egASETYLzLyQfP6o9gJeyuU4QtikO5l/JanQfogEgoIk5H/Mm4tUek6MZLYFaYOd K5PFm7ph5DjWwbEtadLb1rX45+mA4bD1ouYDTyAcA21p+Hmay8J+Z7D8je1G8yA= =Gq1Q -END PGP SIGNATURE- -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: API Changes to AllWatcher / Environment Tags
That was rather the point of my reply above. I think that in the common case it is useful to be able to address the API given a server name only. On 18 Feb 2014 19:17, Kapil Thangavelu kapil.thangav...@canonical.com wrote: how does the api client know the uuid prior to connection? jenv parsing on cli where applicable? On Tue, Feb 18, 2014 at 11:11 AM, Dimiter Naydenov dimiter.nayde...@canonical.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18.02.2014 17:03, John Meinel wrote: Can we make the API /uuid/api ? That makes them all peer paths. Sure we can, I like that better in fact! Dimiter John =:- On Feb 18, 2014 7:43 PM, Dimiter Naydenov dimiter.nayde...@canonical.com mailto:dimiter.nayde...@canonical.com wrote: 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. 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. 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). Thoughts, comments are welcome! Regards, juju-core team -- Juju-dev mailing list Juju-dev@lists.ubuntu.com mailto:Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTA4Y3AAoJENzxV2TbLzHwvD8IAKH0GLvSmCx6mBxuTuKiLUsK UlDogXv26jXIFm/rcoXVY1gM6hESbZPBkuFv95ruyvDmc8zQc2471zayD7k7ydaY pWam7GImq/X/QEW9gGkPXx+5RqaBIaimuqbyiASj2I8aUArwBANWAGBKVyZEiud0 c1y7XpkwsyOLzgQLY2LNh+OZwvlIgkl2NxWz8ptGipU17vsBYbcPjwbA9JYfHdnl egASETYLzLyQfP6o9gJeyuU4QtikO5l/JanQfogEgoIk5H/Mm4tUek6MZLYFaYOd K5PFm7ph5DjWwbEtadLb1rX45+mA4bD1ouYDTyAcA21p+Hmay8J+Z7D8je1G8yA= =Gq1Q -END PGP SIGNATURE- -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
