<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Thanks for summing this up.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">We’ve already merged the client patch so I believe we should merge the dashboard one as well, to keep things consistent among GUI and CLI. Anyway your concerns are as relevant for dashboard as they are for client.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Keeping dependency graph visibility consistent (i.e. forbidding to change visibility of a dependency or at least handling it in some reasonable fashion) right now seems like a very difficult task, but we might be able to do so during migration towards glare-based backend (i.e. this <a href="https://github.com/openstack/murano-specs/blob/master/specs/liberty/artifact-repository-support.rst">https://github.com/openstack/murano-specs/blob/master/specs/liberty/artifact-repository-support.rst</a> spec). I believe it would require some thought and some input from the artifacts team as well. One place we can do this is on our weekly meeting.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">btw, my suggestion is to file a bp for your bug, since it feels like a feature of considerable size to me, what do you think?</div> <br> <div id="bloop_sign_1447157506750072064" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Kirill Zaitsev<br>Murano team</div><div style="font-family:helvetica,arial;font-size:13px">Software Engineer</div><div style="font-family:helvetica,arial;font-size:13px">Mirantis, Inc</div></div> <br><p class="airmail_on">On 4 November 2015 at 15:28:27, Olivier Lemasle (<a href="mailto:olivier.lemasle@apalia.net">olivier.lemasle@apalia.net</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>Hi all,<br><br>Ekaterina Chernova suggested last week to discuss the matter of<br>visibility consistency for murano packages and glance images,<br>following my bug report on that subject [1].<br><br>The general idea is to make sure that if a murano package is public,<br>it should be really available for all projects, which mean that:<br>- if it depends on other murano packages, these packages must be public,<br>- if it depends on glance images, these images must be public.<br><br>In fact, I created this bug report after Alexander Tivelkov's<br>suggesion on a review request [2] I did to fix a related bug [3]. In<br>this other bug report, I focused on images visibility during the<br>initial import of a package, because dependant murano packages are<br>already imported with the same visibility. It seemed to me most<br>confusing that packages are made public if the images are private. So<br>I did a fix in murano-dashboard, which is already merged [4], and<br>another one for python-muranoclient, still in review ([2]).<br><br>What are your thoughts on this subject? Do we need to address first<br>the general dependency issue? Is this a murano, glance or glare<br>subject?<br><br>Do we still need to do something specific for the initial import<br>(currently, dependency resolution for packages and images is done both<br>in murano-dashboard and in python-muranoclient)?<br><br>Thank you for your inputs,<br><br>[1] https://bugs.launchpad.net/murano/+bug/1509208<br>[2] https://review.openstack.org/#/c/236834/<br>[3] https://bugs.launchpad.net/murano/+bug/1507139<br>[4] https://review.openstack.org/#/c/236830/<br><br>-- <br>Olivier Lemasle<br>Software Engineer<br>Apalia™<br>Mobile: +33-611-69-12-11<br>http://www.apalia.net<br>olivier.lemasle@apalia.net<br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></div></div></span></blockquote></body></html>