Open Stack

On 10/27/2015 11:09 AM, Jay Dobies wrote:
>> On 23/10/15 05:35, Robert Collins wrote:
>>> My 2c - if its a stable API in the client, and can be kept stable,
>>> there's no problem.
>>
>> +1
>
> Ok, forgive me for sounding dumb here (and changing the topic of the
> thread somewhat), but what do we consider a stable client API? Is it as
> broad as any methods in heatclient that aren't prefixed with _? Or do we


> scope it only to specific areas (e.g. common, RPC client)

Sorry, I merged two concepts in there. I was referring to common in the 
client and rpc_client in the server. It's possible the same answer 
doesn't apply to both; I'm not sure if we'd want to support someone 
using the server's RPC client code.

> else is considered "use at your own risk because we may need to change it"?
>
> My guess is that it's the former given other sentiments I've heard
> around OpenStack, but I wanted to explicitly ask anyway.
>
> Thanks :)
>
>
>>> -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
>>>
>>>
>>>
>>
>>
>> __________________________________________________________________________
>>
>> 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
>>
>
> __________________________________________________________________________
> 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
>