Re: [openstack-dev] [heat] Need new release of heat-translator library

[Tung Doan]

Hi Doug,
I posted in wrong thread :) Sorry for that. The right one is
http://lists.openstack.org/pipermail/openstack-dev/2018-June/131688.html

Vào Th 5, 21 thg 6, 2018 vào lúc 01:00 Doug Hellmann <
d...@doughellmann.com> đã viết:

> Excerpts from Tung Doan's message of 2018-06-21 00:35:38 +0200:
> >  I agree with Bobh. Considering both Heat Translator and Tosca Parser
> under
> > the management of Tacker could affect other projects. We have recently
> > announced OpenStack Apmec [1] (MEC Orchestration Service) which
> > consumed these two projects as well.
> > In case Heat PTL does not have enough bandwidth to take care of the
> release
> > of these two projects. I just wonder whether it is reasonable to release
> > them when having only the approval of their PTL.
> >
> > [1] https://github.com/openstack/apmec/tree/master/apmec
>
> According to
> https://governance.openstack.org/tc/reference/projects/heat.html the
> Heat PTL *is* the PTL for heat-translators. Any internal team structure
> that implies otherwise is just that, an internal team structure.
>
> I'm really unclear on what the problem is here. The PTL requested a
> release; it looked fine; I approved it; it was completed.
>
> The release team tries to facilitate releases happening as quickly
> as possible so we don't block work anyone else is trying to do.
> There was no apparent reason to wait for this one.  If the teams
> using heat-translator want to coordinate on when releases happen
> for some reason, then please deal with that before requesting the
> releases (and use a W-1 on the patch if you want us to hold off
> until you get approval).  The release team has said we do not want
> to have to keep up with separate liaisons for individual deliverables
> because it's too much to for us to track.
>
> In the mean time, releases are cheap and we can have as many of
> them as we want, so if there are additional features in the pipeline
> that will be ready to be released soon we can just do that when
> they merge.
>
> And if changes are going into heat-translator that might break
> consuming projects, we should deal with that the way we do in other
> libraries and set up cross-project gating to try to catch the
> problems ahead of time. (Maybe that testing is already in place?)
> We can also use the constraint system to block "bad" releases if
> they do happen. But it's generally better for us to be releasing
> libraries and tools as often as possible, so that any breaking
> changes come as part of a small set and so new features are available
> shortly after they are implemented.
>
> Doug
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat] Need new release of heat-translator library

[Doug Hellmann]

Excerpts from Tung Doan's message of 2018-06-21 00:35:38 +0200:
>  I agree with Bobh. Considering both Heat Translator and Tosca Parser under
> the management of Tacker could affect other projects. We have recently
> announced OpenStack Apmec [1] (MEC Orchestration Service) which
> consumed these two projects as well.
> In case Heat PTL does not have enough bandwidth to take care of the release
> of these two projects. I just wonder whether it is reasonable to release
> them when having only the approval of their PTL.
> 
> [1] https://github.com/openstack/apmec/tree/master/apmec

According to
https://governance.openstack.org/tc/reference/projects/heat.html the
Heat PTL *is* the PTL for heat-translators. Any internal team structure
that implies otherwise is just that, an internal team structure.

I'm really unclear on what the problem is here. The PTL requested a
release; it looked fine; I approved it; it was completed.

The release team tries to facilitate releases happening as quickly
as possible so we don't block work anyone else is trying to do.
There was no apparent reason to wait for this one.  If the teams
using heat-translator want to coordinate on when releases happen
for some reason, then please deal with that before requesting the
releases (and use a W-1 on the patch if you want us to hold off
until you get approval).  The release team has said we do not want
to have to keep up with separate liaisons for individual deliverables
because it's too much to for us to track.

In the mean time, releases are cheap and we can have as many of
them as we want, so if there are additional features in the pipeline
that will be ready to be released soon we can just do that when
they merge.

And if changes are going into heat-translator that might break
consuming projects, we should deal with that the way we do in other
libraries and set up cross-project gating to try to catch the
problems ahead of time. (Maybe that testing is already in place?)
We can also use the constraint system to block "bad" releases if
they do happen. But it's generally better for us to be releasing
libraries and tools as often as possible, so that any breaking
changes come as part of a small set and so new features are available
shortly after they are implemented.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [heat] Need new release of heat-translator library

[Tung Doan]

 I agree with Bobh. Considering both Heat Translator and Tosca Parser under
the management of Tacker could affect other projects. We have recently
announced OpenStack Apmec [1] (MEC Orchestration Service) which
consumed these two projects as well.
In case Heat PTL does not have enough bandwidth to take care of the release
of these two projects. I just wonder whether it is reasonable to release
them when having only the approval of their PTL.

[1] https://github.com/openstack/apmec/tree/master/apmec
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat] Need new release of heat-translator library

[Doug Hellmann]

Excerpts from Zane Bitter's message of 2018-06-20 12:07:49 -0400:
> On 20/06/18 11:40, Rico Lin wrote:
> > I send a release patch now https://review.openstack.org/#/c/576895/
> > Also, add Bob Haddleton to this ML who is considering as PTL for 
> > heat-translator team
> 
> Is it time to consider moving the heat-translator and tosca-parser repos 
> from being deliverables of Heat to deliverables of Tacker? The current 
> weird structure dates from the days of the experiment with OpenStack 
> 'Programs' (vs. Projects).
> 
> Heat cores don't really have time to be engaging with heat-translator, 
> and Tacker is clearly the major user and the thing that keeps getting 
> blocked on needing patches merged and releases made.

It sounds like it. I had no idea there was any reason to look to anyone
other than the Heat PTL or liaison for approval of that release. A WIP
on the patch would have been OK, too, but if the Tacker team is really
the one responsible we should update the repo governance.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat] Need new release of heat-translator library

[Zane Bitter]

On 20/06/18 11:40, Rico Lin wrote:

I send a release patch now https://review.openstack.org/#/c/576895/
Also, add Bob Haddleton to this ML who is considering as PTL for 
heat-translator team


Is it time to consider moving the heat-translator and tosca-parser repos 
from being deliverables of Heat to deliverables of Tacker? The current 
weird structure dates from the days of the experiment with OpenStack 
'Programs' (vs. Projects).


Heat cores don't really have time to be engaging with heat-translator, 
and Tacker is clearly the major user and the thing that keeps getting 
blocked on needing patches merged and releases made.


Ben Nemec mailto:openst...@nemebean.com>> 於 
2018年6月20日 週三 下午10:26寫道：




On 06/20/2018 02:58 AM, Patil, Tushar wrote:
 > Hi,
 >
 > Few weeks back, we had proposed a patch [1] to add support for
translation of placement policies and that patch got merged.
 >
 > This feature will be consumed by tacker specs [2] which we are
planning to implement in Rocky release and it's implementation is
uploaded in patch [3]. Presently, the tests are failing on patch [3]
becoz it requires newer version of heat-translator library.
 >
 > Could you please release a new version of heat-translator library
so that we can complete specs[2] in Rocky timeframe.

Note that you can propose a release to the releases repo[1] and then
you
just need the PTL or release liaison to sign off on it.

1: http://git.openstack.org/cgit/openstack/releases/tree/README.rst

-Ben

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
May The Force of OpenStack Be With You,
*/Rico Lin
/*irc: ricolin




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat] Need new release of heat-translator library

[HADDLETON, Robert W (Bob)]

This request had come to me from someone else in the Tacker team and I 
was working on including a couple of other patchsets in the release, but 
this is fine.


Please tag these requests as [heat-translator] in the subject so they 
get flagged to me and I'm happy to work them.


Bob

On 6/20/2018 10:40 AM, Rico Lin wrote:

I send a release patch now https://review.openstack.org/#/c/576895/
Also, add Bob Haddleton to this ML who is considering as PTL for 
heat-translator team


Ben Nemec mailto:openst...@nemebean.com>> 於 
2018年6月20日 週三 下午10:26寫道：




On 06/20/2018 02:58 AM, Patil, Tushar wrote:
> Hi,
>
> Few weeks back, we had proposed a patch [1] to add support for
translation of placement policies and that patch got merged.
>
> This feature will be consumed by tacker specs [2] which we are
planning to implement in Rocky release and it's implementation is
uploaded in patch [3]. Presently, the tests are failing on patch
[3] becoz it requires newer version of heat-translator library.
>
> Could you please release a new version of heat-translator
library so that we can complete specs[2] in Rocky timeframe.

Note that you can propose a release to the releases repo[1] and
then you
just need the PTL or release liaison to sign off on it.

1: http://git.openstack.org/cgit/openstack/releases/tree/README.rst

-Ben

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
May The Force of OpenStack Be With You,
*/Rico Lin
/*irc: ricolin





<>__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat] Need new release of heat-translator library

[Rico Lin]

I send a release patch now https://review.openstack.org/#/c/576895/
Also, add Bob Haddleton to this ML who is considering as PTL for
heat-translator team

Ben Nemec  於 2018年6月20日 週三 下午10:26寫道：

>
>
> On 06/20/2018 02:58 AM, Patil, Tushar wrote:
> > Hi,
> >
> > Few weeks back, we had proposed a patch [1] to add support for
> translation of placement policies and that patch got merged.
> >
> > This feature will be consumed by tacker specs [2] which we are planning
> to implement in Rocky release and it's implementation is uploaded in patch
> [3]. Presently, the tests are failing on patch [3] becoz it requires newer
> version of heat-translator library.
> >
> > Could you please release a new version of heat-translator library so
> that we can complete specs[2] in Rocky timeframe.
>
> Note that you can propose a release to the releases repo[1] and then you
> just need the PTL or release liaison to sign off on it.
>
> 1: http://git.openstack.org/cgit/openstack/releases/tree/README.rst
>
> -Ben
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


-- 
May The Force of OpenStack Be With You,

*Rico Lin*irc: ricolin
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat] Need new release of heat-translator library

[Ben Nemec]

On 06/20/2018 02:58 AM, Patil, Tushar wrote:

Hi,

Few weeks back, we had proposed a patch [1] to add support for translation of 
placement policies and that patch got merged.

This feature will be consumed by tacker specs [2] which we are planning to 
implement in Rocky release and it's implementation is uploaded in patch [3]. 
Presently, the tests are failing on patch [3] becoz it requires newer version 
of heat-translator library.

Could you please release a new version of heat-translator library so that we 
can complete specs[2] in Rocky timeframe.


Note that you can propose a release to the releases repo[1] and then you 
just need the PTL or release liaison to sign off on it.


1: http://git.openstack.org/cgit/openstack/releases/tree/README.rst

-Ben

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [heat] Need new release of heat-translator library

[Patil, Tushar]

Hi,

Few weeks back, we had proposed a patch [1] to add support for translation of 
placement policies and that patch got merged.

This feature will be consumed by tacker specs [2] which we are planning to 
implement in Rocky release and it's implementation is uploaded in patch [3]. 
Presently, the tests are failing on patch [3] becoz it requires newer version 
of heat-translator library.

Could you please release a new version of heat-translator library so that we 
can complete specs[2] in Rocky timeframe.

Thank you.

Regards,
Tushar Patil
Disclaimer: This email and any attachments are sent in strictest confidence for 
the sole use of the addressee and may contain legally privileged,confidential, 
and proprietary data. If you are not the intended recipient,please advise the 
sender by replying promptly to this email and then delete and destroy this 
email and any attachments without any further use, copying or forwarding.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev