IMHO, as the tag 2.0.2 and 2.0.3 are both Mitaka release based tag with minor fixes, it should support and work to the same release legacy images. But then, the built image tag needs to be specified before/during the "kolla-ansible prechecks/deploy" process. This is the experience that I tried with Liberty release with the tag 1.x.x. Hope it also works for your situation. Br, Chao > -----原始邮件----- > 发件人: hu.zhijiang at zte.com.cn > 发送时间: 2016年8月11日 星期四 > 收件人: openstack-dev at lists.openstack.org > 抄送: > 主题: [openstack-dev] [kolla] Question about kolla git tag > > Hi > > The image we built before is tagged automatically as 2.0.2. and now the > kolla code has been upgrade to 2.0.3. I would like to ask if it is OK to > use code 2.0.3 do deploy images 2.0.2, or we'd better to sync the version > by using "git tag" command according to the image version? > > B.R., > Zhijiang > > > __________________________________________________________________________ > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160811/fdb71096/attachment.html>