Short summarize of discussion in email thread and IRC:
1. We plan to add follow information for property/attribute in release
notes.
- Deprecated in Juno
- Announce planned removal in Kilo release notes
- Remove in "J" (I.e. we will return validation error on all templates
with this p
On 19 January 2015 at 05:13, Angus Salkeld wrote:
> On Fri, Jan 16, 2015 at 11:10 PM, Sergey Kraynev
> wrote:
>
>> Steve, Thanks for the feedback.
>>
>> On 16 January 2015 at 15:09, Steven Hardy wrote:
>>
>>> On Thu, Dec 25, 2014 at 01:52:43PM +0400, Sergey Kraynev wrote:
>>> >Hi all.
>>> >
On Fri, Jan 16, 2015 at 11:10 PM, Sergey Kraynev
wrote:
> Steve, Thanks for the feedback.
>
> On 16 January 2015 at 15:09, Steven Hardy wrote:
>
>> On Thu, Dec 25, 2014 at 01:52:43PM +0400, Sergey Kraynev wrote:
>> >Hi all.
>> >In the last time we got on review several patches, which rem
On Sat, Jan 17, 2015 at 5:01 AM, Georgy Okrokvertskhov <
gokrokvertsk...@mirantis.com> wrote:
> Hi,
>
> Murano uses Heat templates with almost all available resources. Neutron
> resources are definitely used.
> I think Murano can update our Heat resources handling properly, but there
> are at leas
Hi,
Murano uses Heat templates with almost all available resources. Neutron
resources are definitely used.
I think Murano can update our Heat resources handling properly, but there
are at least two scenarios which should be considered:
1) Murano generated stacks are long lasting. Murano uses stack
Steve, Thanks for the feedback.
On 16 January 2015 at 15:09, Steven Hardy wrote:
> On Thu, Dec 25, 2014 at 01:52:43PM +0400, Sergey Kraynev wrote:
> >Hi all.
> >In the last time we got on review several patches, which removes old
> >deprecation properties [1],A
> >and one mine [2
On Thu, Dec 25, 2014 at 01:52:43PM +0400, Sergey Kraynev wrote:
>Hi all.
>In the last time we got on review several patches, which removes old
>deprecation properties [1],A
>and one mine [2].
>The aim is to delete deprecated code and redundant tests. It looks simple,
>but t
Hi all.
In the last time we got on review several patches, which removes old
deprecation properties [1],
and one mine [2].
The aim is to delete deprecated code and redundant tests. It looks simple,
but the main problem, which we met, is backward compatibility.
F.e. user has created resource (FIP)
