Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

2016-02-02 Thread Julia Aranovich
I support Vitaly's proposal with 'base' group name instead of 'controller'. So, now we have the following suggestion for role list grouping: BASE: controller, detach-* plugin roles, murano (if it will go to plugin) COMPUTE: compute, virt, compute-vmware, ironic STORAGE: cinder, cinder-block-device

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

2016-02-01 Thread Vitaly Kramskikh
Folks, That's true, Nailgun is still using Role entity - in DB, API, plugins can provide new roles, etc., and it's not going away, at least in 9.0. I'm fine with proposed set of role groups, except the "controller" group. We don't have anything else but "controller" role in this group in the base

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

2016-01-29 Thread Bogdan Dobrelya
On 29.01.2016 13:35, Vladimir Kuklin wrote: >> We removed role as abstraction from library. It's very very artificial >> abstraction. Instead we use tasks, grouping them to different >> combinations. That allows plugin developers to adjust reference >> architecture to their needs. I only replied t

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

2016-01-29 Thread Vladimir Kuklin
Bogdan 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? On Fri, Jan 29, 2016 at 2:59 PM, Bogdan Dobrelya wrote: > On 29.01.

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

2016-01-29 Thread Bogdan Dobrelya
On 29.01.2016 10:58, Sergii Golovatiuk wrote: > Hi, > > > On Fri, Jan 29, 2016 at 9:55 AM, Julia Aranovich > mailto:jkirnos...@mirantis.com>> wrote: > > Hi folks, > > Our team has started a redesign of node roles panel [1] on Add > Nodes/Edit Roles screens in Fuel UI. > Currentl

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

2016-01-29 Thread Julia Aranovich
Sergii, Just to clarify: we rely on a role 'limits' attribute [1] to define is role required for deployment ('min' limit presented in the role description) or recommended for deployment ('recommended' limit). Roles without 'min' or 'recommended' limit are considered as optional for basic deploymen

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

2016-01-29 Thread Vladimir Kuklin
Sergii I disagree with you here a little bit. Role abstraction is a useful thing from high-level standpoint. I would suggest that this list of roles grouping, e.g. which roles are mandatory and which are configured within which group can be specified: 1) in global settings of Nailgun 2) per-plugi

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

2016-01-29 Thread Sergii Golovatiuk
Hi, On Fri, Jan 29, 2016 at 9:55 AM, Julia Aranovich wrote: > Hi folks, > > Our team has started a redesign of node roles panel [1] on Add Nodes/Edit > Roles screens in Fuel UI. > Currently, node roles panel takes a big part of the screen and User have > to scroll down to node list to check nod