<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">+1 to use wildcards for common tasks like netconfig and setup repositories. This tasks should run on all nodes and it does not matter, the node has role from plugin or core-role.</div><div class="">In my opinion we should one approach for basic configuration of node.</div><br class=""><div class="">
Regards,<br class="">Bulat Gaifullin<br class="">Mirantis Inc.<div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 19 Feb 2016, at 13:36, Kyrylo Galanov <<a href="mailto:kgalanov@mirantis.com" class="">kgalanov@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi,<div class=""><br class=""></div><div class="">So who is voting for the path to be abandoned?</div><div class=""><br class=""></div><div class="">By the way, there is already a task running by the wildcard: <a href="https://github.com/openstack/fuel-library/blob/master/deployment/puppet/osnailyfacter/modular/fuel_pkgs/tasks.yaml#L4" class="">https://github.com/openstack/fuel-library/blob/master/deployment/puppet/osnailyfacter/modular/fuel_pkgs/tasks.yaml#L4</a></div><div class="">However, it this case it might work with plugins.</div><div class=""><br class=""></div><div class="">Best regards,</div><div class="">Kyrylo</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Feb 19, 2016 at 1:09 AM, Igor Kalnitsky <span dir="ltr" class=""><<a href="mailto:ikalnitsky@mirantis.com" target="_blank" class="">ikalnitsky@mirantis.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey Kyrylo,<br class="">
<br class="">
As it was mentioned in the review: you're about to break roles defined<br class="">
by plugins. That's not good move, I believe.<br class="">
<br class="">
Regarding 'exclude' directive, I have no idea what you're talking<br class="">
about. We don't support it now, and, anyway, there should be no<br class="">
difference between roles defined by plugins and core roles.<br class="">
<br class="">
- Igor<br class="">
<div class=""><div class="h5"><br class="">
On Thu, Feb 18, 2016 at 12:53 PM, Kyrylo Galanov <<a href="mailto:kgalanov@mirantis.com" class="">kgalanov@mirantis.com</a>> wrote:<br class="">
> Hello,<br class="">
><br class="">
> We are about to switch to wildcards instead of listing all groups in tasks<br class="">
> explicitly [0].<br class="">
> This change must make deployment process more obvious for developers.<br class="">
> However, it might lead to confusion when new groups are added either by<br class="">
> plugin or fuel team in future.<br class="">
><br class="">
> As mention by Bogdan, it is possible to use 'exclude' directive to mitigate<br class="">
> the risk.<br class="">
> Any thoughts on the topic are appreciated.<br class="">
><br class="">
><br class="">
> [0] <a href="https://review.openstack.org/#/c/273596/" rel="noreferrer" target="_blank" class="">https://review.openstack.org/#/c/273596/</a><br class="">
><br class="">
> Best regards,<br class="">
> Kyrylo<br class="">
><br class="">
</div></div>> __________________________________________________________________________<br class="">
> OpenStack Development Mailing List (not for usage questions)<br class="">
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
><br class="">
<br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</blockquote></div><br class=""></div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></body></html>