Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI-InSPIRE:Amb 2014-02-19"

From EGIWiki
Jump to navigation Jump to search
Line 66: Line 66:
** support to user from Univ. Bradford: potential RP/TP and use case provider
** support to user from Univ. Bradford: potential RP/TP and use case provider
* Start engagement with BSIM2 SME (from PT)
* Start engagement with BSIM2 SME (from PT)
 
* H2020 Data SC telcon
* Planning for NIL meetings
* Engagement strategy discussions with Swiss NIL
* FedCloud:Summary for RNA-analysis use case
* Support of a Greek user to run NAMD and AMBER simulations on EGI
* Follow-up Matlab execution environment setup with Greek and Portuguese NILs


=== ER-flow  ===
=== ER-flow  ===
Line 75: Line 80:
*Getting-started and platform pages for ER-flow website (presenting the available services for the users)  
*Getting-started and platform pages for ER-flow website (presenting the available services for the users)  
*Events table updates
*Events table updates
*Planning for possible follow-up project


=== BioVeL  ===
=== BioVeL  ===
Line 81: Line 88:
* Schedule meeting on how EGI can monitor BioVeL services
* Schedule meeting on how EGI can monitor BioVeL services
* ST-weekly call
* ST-weekly call
* Strategy Workshop - sustainability planning


=== Major Events Planned  ===
=== Major Events Planned  ===

Revision as of 22:46, 18 February 2014


Back to the AMB wiki home page

Activity Reports

NA1

NA2

NA2.2

  1. News Items/Articles
  2. Media mentions
  3. Events
  4. Publications
    • Working on new version of the Why EGI? brochure
    • Working on poster for EGI Solutions Portfolio
  5. Webinars
    • Webinar on Federated Cloud postponed again
  6. Other Projects
    • Compiling list of people to be sent the e-ScienceTalk briefings compendium
    • Planning e-ScienceTalkToo proposal
      • Supplied short description for executive board
  7. Deliverables/Milestones
    • Supplied Communications Team input to QR15
  8. Other
    • Compiled list of 430 scientific papers that used EGI during 2013
      • Six of these are being investigated for use cases
      • Another seven are being confirmed as grid use cases

NA2.3 Strategic Planning and Policy Support

NA2.4 Events

NA2.5 Technical outreach

EGI-InSPIRE

  • Meeting with CENIEH (palenteology) institute
  • Engagement strategy plan: scoping phase
    • Scheduling meetings with NILs for all ESFRIs/Communities with red/yellow code
    • Support DIRAC 4 EGI and Protein Sequencing/NGS prospective VT's
  • EGI Federated Cloud
    • input to weekly meeting
    • schedule meeting with DRIHM: prospective use case
    • support to user from Univ. Bradford: potential RP/TP and use case provider
  • Start engagement with BSIM2 SME (from PT)
  • H2020 Data SC telcon
  • Planning for NIL meetings
  • Engagement strategy discussions with Swiss NIL
  • FedCloud:Summary for RNA-analysis use case
  • Support of a Greek user to run NAMD and AMBER simulations on EGI
  • Follow-up Matlab execution environment setup with Greek and Portuguese NILs

ER-flow

  • Submitted Hackathon abstract for the EGI CF 2014
  • Investigating SSP submission service for using VAPOR white list of resources
  • Investigating job submission failure from SSP using shiwa-workflow.eu VO (works fine from gLite UI, but not from SSP portal)
  • Getting-started and platform pages for ER-flow website (presenting the available services for the users)
  • Events table updates
  • Planning for possible follow-up project


BioVeL

  • Dissemination: OpenModeller @ CloudScape VI (ePoster & demo)
  • Schedule meeting on how EGI can monitor BioVeL services
  • ST-weekly call
  • Strategy Workshop - sustainability planning

Major Events Planned

SA1

https://wiki.egi.eu/wiki/Inspire_sa1_2014-02-18

SA2

SA4

TSA4.1 - Management

  • weekly reporting
  • resolved confusion around mini projects being represented at CF14
  • Connected EGI press team with VAPOR to get a news article out
  • Introduced VAPOR to the idea of becoming a component of the Cloud Infrastructure Platform

TSA4.2 - MOOC

  • Working on certificate for course completion.
  • Creating evaluation questionnaire.

TSA4.3 - Liferay

bi-weekly reporting

TSA4.4 - OCCI for CMF

rOCCI-core
  • bugfix release 4.2.10
rOCCI-api
  • stable release v4.2.0
rOCCI-cli
  • stable release v4.2.0
rOCCI-server
  • beta deployed at CESNET (w/ VOMS authentication)
  • working on installation & configuration docs
ToDo for next week
  • work on additional backends (CloudStack has the highest priority)
  • do quick bug -> bugfix -> another beta release iterations
Problems
  • None (yet :-))
Delays
  • Still approx. one month (== Florian's contribution), no further delay

TSA4.5 - CDMI in CMF

bi-weekly reporting

TSA4.6 - OCCI CompClouds

no report given

TSA4.7 - AppDeployment

Progress

- Update packages at AppDB for FedCloud

  • VM launching with application context from the front-end functional
  • Overall improvement of the front-end design
  • Management of proxies with myproxy
Plans for next week
  • Continue the front-end implementation
Issues
  • Still delayed on the front-end implementation, but we are putting most of our effort there.

TSA4.8 - CloudCapabilities

Progress
  • Published a new blog post about keeping images small from within and thinking about decomposing applications.
  • Supported the PeachNote Community with accessing CDMI after server side changes.
  • Started structuring and discussing the workshop planned at EGI CF14
  • Contacted BNCweb about how to stress test their application to measure our success
Plans for next week
  • work on full contextualization of BNCweb application, i.e. configure mysql-proxy and
  • stress test new BNCweb application
  • cloud-init for Debian Wheezy needs to be tested also in OS to check that it can retrieve a configuration from the metadata service. Also, the basic configuration should be aligned and documented.
Problems we encountered, but can solve in the mini-project

none

Problems and issues we need external help with

none

TSA4.9 - VAPOR

bi-weekly reporting

TSA4.10 - CompReports

bi-weekly reporting

TSA4.12 - AllocateFedRes

no report given

JRA1

Report: Inspire jra1 2014-02-18

Participants

Discussion