<div dir="ltr">Bogdan <div><br></div><div>I do no think that this is confusing as we should have actually a place where we tie roles to particular tasks. How do you expect our orchestrator to generate a graph without knowing which tasks to execute on which node?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 29, 2016 at 2:59 PM, Bogdan Dobrelya <span dir="ltr"><<a href="mailto:bdobrelia@mirantis.com" target="_blank">bdobrelia@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 29.01.2016 10:58, Sergii Golovatiuk wrote:<br>
> Hi,<br>
><br>
><br>
> On Fri, Jan 29, 2016 at 9:55 AM, Julia Aranovich<br>
</span><span class="">> <<a href="mailto:jkirnosova@mirantis.com">jkirnosova@mirantis.com</a> <mailto:<a href="mailto:jkirnosova@mirantis.com">jkirnosova@mirantis.com</a>>> wrote:<br>
><br>
> Hi folks,<br>
><br>
> Our team has started a redesign of node roles panel [1] on Add<br>
> Nodes/Edit Roles screens in Fuel UI.<br>
> Currently, node roles panel takes a big part of the screen and User<br>
> have to scroll down to node list to check nodes and then scroll up<br>
> again to check roles. This becomes more actual for desktops with a<br>
> small screen.<br>
><br>
> And we faced with the question of grouping new role containers in<br>
> the panel. There is out initial suggestion [2]:<br>
><br>
</span>> role-list-grouping-1.png<br>
><br>
> * the first group (the first line on the screenshot) is roles<br>
<span class="">> which are required or recommended for deployment (controller,<br>
> compute, cinder, etc.).<br>
><br>
> It's not true. There can be deployments without Controllers or without<br>
> computes or without Storage.<br>
><br>
</span>> * the second group is optional roles which are not mandatory for<br>
> deployment (base-os, virt, etc.)<br>
> * the last group is roles which are unavailable at the moment<br>
<span class="">> because of some restrictions. For example, mongo role can not be<br>
> assigned to a node if ceilometer setting is not enabled on<br>
> Settings tab<br>
><br>
> BUT there is also a suggestion [3] (see comment #6) to add a new<br>
> role 'category' attribute into its yaml description [4] that will<br>
> reflect the role function.<br>
> For example, cinder, ceph-osd, cinder-vmware roles are from Storage<br>
> category; compute, ironic are Compute and so on.<br>
> This new 'category' attribute will also allow proper calculating of<br>
> an environment capacity: it does not make sense to count CPU and RAM<br>
> of non-compute nodes or HDD of non-storage nodes.<br>
><br>
> So, we have an initial proposal for such a grouping by a role category:<br>
><br>
> CONTROLLER: controller<br>
> COMPUTE: compute, virt, compute-vmware, ironic<br>
> STORAGE: cinder, cinder-block-device, cinder-vmware, ceph-osd<br>
> OTHER: base-os, mongo<br>
><br>
> And we ask your help to review this grouping, i.e. to define the<br>
> list of possible role categories and to distribute the roles between<br>
> these categories.<br>
><br>
><br>
> We removed role as abstraction from library. It's very very artificial<br>
> abstraction. Instead we use tasks, grouping them to different<br>
> combinations. That allows plugin developers to adjust reference<br>
> architecture to their needs.<br>
<br>
</span>That seems *very* confusing as all role labels are still sitting at<br>
their places in task definitions. See for 'primary-controller',<br>
'controller', 'compute' etc. We can say we "dropped" only once we:<br>
- get rid of them in *all* places<br>
- update task schema docs [0] lagging far behind, which is the most<br>
critical thing to remove confusion, see related topic [1]<br>
<br>
[0]<br>
<a href="https://docs.mirantis.com/openstack/fuel/fuel-7.0/reference-architecture.html#task-based-deployment" rel="noreferrer" target="_blank">https://docs.mirantis.com/openstack/fuel/fuel-7.0/reference-architecture.html#task-based-deployment</a><br>
[1]<br>
<a href="http://lists.openstack.org/pipermail/openstack-dev/2016-January/085208.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2016-January/085208.html</a><br>
<span class=""><br>
><br>
><br>
><br>
> Best regards,<br>
> Julia<br>
><br>
> P.S. We also should take into account, that Fuel plugins can also<br>
> provide their own roles.<br>
><br>
> [1] <a href="https://blueprints.launchpad.net/fuel/+spec/redesign-of-node-roles-panel" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/fuel/+spec/redesign-of-node-roles-panel</a><br>
> [2] <a href="http://s22.postimg.org/x8ry0lm1t/Screenshot_from_2016_01_26_17_49_24.png" rel="noreferrer" target="_blank">http://s22.postimg.org/x8ry0lm1t/Screenshot_from_2016_01_26_17_49_24.png</a><br>
> [3] <a href="https://bugs.launchpad.net/fuel/+bug/1375750" rel="noreferrer" target="_blank">https://bugs.launchpad.net/fuel/+bug/1375750</a><br>
> [4] <a href="https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/fixtures/openstack.yaml#L9-L142" rel="noreferrer" target="_blank">https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/fixtures/openstack.yaml#L9-L142</a><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe:<br>
> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
</span>> <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<span class="im HOEnZb">><br>
><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
</span><span class="HOEnZb"><font color="#888888">--<br>
Best regards,<br>
Bogdan Dobrelya,<br>
Irc #bogdando<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Yours Faithfully,<br>Vladimir Kuklin,<br>Fuel Library Tech Lead,<br>Mirantis, Inc.<br>+7 (495) 640-49-04<br>+7 (926) 702-39-68<br>Skype kuklinvv<br>35bk3, Vorontsovskaya Str.<br>Moscow, Russia,<br><a href="http://www.mirantis.ru/" target="_blank">www.mirantis.com</a><br><a href="http://www.mirantis.ru/" target="_blank">www.mirantis.ru</a><br><a href="mailto:vkuklin@mirantis.com" target="_blank">vkuklin@mirantis.com</a></div></div></div></div>
</div>