Difference between revisions of "22.05.2013 Accounting and Policy portlets"

From D4Science Wiki
Jump to: navigation, search
(→‎Requirements for the policy management portlet)
(→‎Requirements for the policy management portlet)
Line 6: Line 6:
 
*Participants: Andrea Manieri (ENG), Andrea Manzi (CERN), Antonio Savini (ENG), Ermanno Travaglino (ENG), Pasquale Pagano (CNR), Luigi Fortunati (CNR).
 
*Participants: Andrea Manieri (ENG), Andrea Manzi (CERN), Antonio Savini (ENG), Ermanno Travaglino (ENG), Pasquale Pagano (CNR), Luigi Fortunati (CNR).
  
−
====Requirements for the policy management portlet====
+
====Policy management portlet====
 +
 
 +
=== Requirements ===
  
 
* We need to display the information related to the serviceClass and the serviceName in the form "serviceClass:serviceName" pair, because serviceClass includes serviceName. Then Antonio and Ciro we'll need to assess the portlet usability when the number of services increase (order of 50-60 as baseline, up to three times more).
 
* We need to display the information related to the serviceClass and the serviceName in the form "serviceClass:serviceName" pair, because serviceClass includes serviceName. Then Antonio and Ciro we'll need to assess the portlet usability when the number of services increase (order of 50-60 as baseline, up to three times more).
Line 15: Line 17:
 
* During the create policy process will be not available the Servive field selection, because if the services number grows the services list will be not readable. In order to reduce the number of (defined) policies that are displayed, it might be useful to filter (through a search bar) on some fields (such as serviceClass, serviceName and host).
 
* During the create policy process will be not available the Servive field selection, because if the services number grows the services list will be not readable. In order to reduce the number of (defined) policies that are displayed, it might be useful to filter (through a search bar) on some fields (such as serviceClass, serviceName and host).
 
* We need to allow the portlet's user to show info based on user role scope and consider Service2Service policies.
 
* We need to allow the portlet's user to show info based on user role scope and consider Service2Service policies.
 +
 +
=== Actions ===
 +
 +
* ENG will circulate a document describing the portlet functionalities and the usage flow (by the EOW) to Lino and Andrea in order to produce an (internal) validation about the requirements and usability of the current implementation of the portlet.
 +
* Next week will be a conference call to discuss the preliminary validation results and to define possible corrective actions.
  
 
====Next actions====
 
====Next actions====

Revision as of 15:04, 23 May 2013

Details

  • Description: Meeting notes on Resource Accounting and Policy portlets
  • Date: 22-May-2013
  • Topics: Policy management, Resource accounting, portlets, requirements
  • Participants: Andrea Manieri (ENG), Andrea Manzi (CERN), Antonio Savini (ENG), Ermanno Travaglino (ENG), Pasquale Pagano (CNR), Luigi Fortunati (CNR).

Policy management portlet

Requirements

  • We need to display the information related to the serviceClass and the serviceName in the form "serviceClass:serviceName" pair, because serviceClass includes serviceName. Then Antonio and Ciro we'll need to assess the portlet usability when the number of services increase (order of 50-60 as baseline, up to three times more).
  • We need to understand and evaluate the portlet usability when the number of services increase.
  • Up to now it's not possibile to remove/edit simultaneously multiple policies. Antonio to evaluate options to allow this when the same action - e.g. activation or deactivation is foreseen for many of them (it would suggest to consider a "cloning function").The item should be renamed as "gHN".
  • It's necessary to add the port number to distinguish between different services on different hosts.
  • During the create policy process will be not available the Servive field selection, because if the services number grows the services list will be not readable. In order to reduce the number of (defined) policies that are displayed, it might be useful to filter (through a search bar) on some fields (such as serviceClass, serviceName and host).
  • We need to allow the portlet's user to show info based on user role scope and consider Service2Service policies.

Actions

  • ENG will circulate a document describing the portlet functionalities and the usage flow (by the EOW) to Lino and Andrea in order to produce an (internal) validation about the requirements and usability of the current implementation of the portlet.
  • Next week will be a conference call to discuss the preliminary validation results and to define possible corrective actions.

Next actions

  • action 1
  • action 2
  • ...
Retrieved from "https://wiki.d4science.org/index.php?title=22.05.2013_Accounting_and_Policy_portlets&oldid=12550"