[openstack-dev] [heat] Shared code between server and client

Robert Collins robertc at robertcollins.net
Thu Oct 22 20:35:38 UTC 2015


My 2c - if its a stable API in the client, and can be kept stable,
there's no problem.

-Rob

On 23 October 2015 at 08:49, Jay Dobies <jason.dobies at redhat.com> wrote:
> I'm working on moving the functionality for merging environments from the
> client into the server [1]. I've only superficially looked at
> template_utils.py (in heatclient) but I'm guessing there is stuff in there I
> will want to use server-side.
>
> The server has a requirement on heatclient, but I'm not sure what the
> convention is for using code in it. Can I directly call into a module in
> heatclient/common from the server or is the client dependency only intended
> to be used through the client-facing APIs?
>
> [1] https://blueprints.launchpad.net/heat/+spec/multi-environments
>
> Thanks :)
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud



More information about the OpenStack-dev mailing list