Difference between revisions of "EGI-InSPIRE:Jra2 2014-06-04"

From EGIWiki
Jump to: navigation, search
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{Template:EGI-Inspire menubar}}
 
[[Inspire_JRA1_weekly_reports| << JRA1 weekly reports main page]]  
 
[[Inspire_JRA1_weekly_reports| << JRA1 weekly reports main page]]  
  
Line 5: Line 6:
  
 
== 1. Critical Issues  ==
 
== 1. Critical Issues  ==
 
+
* Nothing new to report
  
 
== 2. Major work done during the past week by task  ==
 
== 2. Major work done during the past week by task  ==
  
 
=== 2.1 TJRA2.1 SAM ===
 
=== 2.1 TJRA2.1 SAM ===
 
+
* No report received
  
 
=== 2.2 TJRA2.2 Accounting  ===
 
=== 2.2 TJRA2.2 Accounting  ===
  
 
==== 2.2.1 Accounting Repository  ====
 
==== 2.2.1 Accounting Repository  ====
 
+
* No report received
  
 
==== 2.2.2 Accounting Portal  ====
 
==== 2.2.2 Accounting Portal  ====
 
+
* No report received
  
 
=== 2.3 TJRA2.3 AppDB  ===
 
=== 2.3 TJRA2.3 AppDB  ===
Line 29: Line 30:
 
*discussion with Owne Synge about vmcaster/vmcatcher open items:<br>
 
*discussion with Owne Synge about vmcaster/vmcatcher open items:<br>
  
&nbsp;&nbsp;&nbsp; - vmcaster: default expiration date<br>&nbsp;&nbsp;&nbsp; - vmatcher: new images in an image lists that RP has also subscribed<br>&nbsp;&nbsp;&nbsp; - vmcaster: switch for not using x509 certs<br>&nbsp;&nbsp;&nbsp; - vmatcher: does the vmcatcher script retrieves the Personal Access Token (PAT) from the db?<br>&nbsp;&nbsp;&nbsp; - vmatcher: enrich the db metadata (mpuri in separate db field? + json output)<br>
+
&nbsp;&nbsp;&nbsp; - vmcaster: default expiration date<br>&nbsp;&nbsp;&nbsp; - vmcatcher: new images in an image lists that RP has also subscribed<br>&nbsp;&nbsp;&nbsp; - vmcaster: switch for not using x509 certs<br>&nbsp;&nbsp;&nbsp; - vmatcher: does the vmcatcher script retrieves the Personal Access Token (PAT) from the db?<br>&nbsp;&nbsp;&nbsp; - vmatcher: enrich the db metadata (mpuri in separate db field? + json output)<br>
  
=== 2.4 TJRA2.4 e-GRANT   ===
+
=== 2.4 TJRA2.4 e-GRANT ===
  
 +
*analysis of possibility to use e-GRANT as tool for pay-per-use<br>
 +
*analysis of feature needed for implementation of requesting for FedCloud resources
 +
*analysis of feature needed for implementation of pool management for FedCloud resources
 +
*improvement of notifications&nbsp;
 +
*implementation of "approximate" pool matching&nbsp;
  
 
== 3. Next Meetings  ==
 
== 3. Next Meetings  ==
 
+
* AppDB PY5 roadmap: 11th June
[[Category:JRA1_weekly_report]]
+
* JRA2 monthly meeting: 27th June

Latest revision as of 12:42, 6 January 2015

EGI Inspire Main page


<< JRA1 weekly reports main page



1. Critical Issues

  • Nothing new to report

2. Major work done during the past week by task

2.1 TJRA2.1 SAM

  • No report received

2.2 TJRA2.2 Accounting

2.2.1 Accounting Repository

  • No report received

2.2.2 Accounting Portal

  • No report received

2.3 TJRA2.3 AppDB


  • Monitoring the AppDB::Cloud Markeplace: a special VA has been registered (https://appdb.egi.eu/store/vappliance/fedcloud.monitoring.va) that gets updated every hour. A nagios probe will be implemented that checks the produced VA image list creation date
  • VO Notification: we are working on the VO notification mechanism, according which, the user will be able to notify one or more VOs for his newly registered VA in order to be included/endorsed into the VO-wide image list. In case of update of an already endorsed VA by one or more VOs, the VOs in respect will be notified automaticaly.
  • investigation on ELIXIR project support
  • discussion with Owne Synge about vmcaster/vmcatcher open items:

    - vmcaster: default expiration date
    - vmcatcher: new images in an image lists that RP has also subscribed
    - vmcaster: switch for not using x509 certs
    - vmatcher: does the vmcatcher script retrieves the Personal Access Token (PAT) from the db?
    - vmatcher: enrich the db metadata (mpuri in separate db field? + json output)

2.4 TJRA2.4 e-GRANT

  • analysis of possibility to use e-GRANT as tool for pay-per-use
  • analysis of feature needed for implementation of requesting for FedCloud resources
  • analysis of feature needed for implementation of pool management for FedCloud resources
  • improvement of notifications 
  • implementation of "approximate" pool matching 

3. Next Meetings

  • AppDB PY5 roadmap: 11th June
  • JRA2 monthly meeting: 27th June