SECTION: GCC, TFs and SIGs
LEAD: Nicole Harris
DEADLINE: Final report April 28th 2017. All TF and SIG input by 7th April 2017 please.
INFORMATION SEEKING:
o GCC – vision paper on current state of the community and main challenges to be addressed.
o TFs and SIGs – top issues that need to be addressed (i.e. the situation now) and view on what users will need in 5 years (i.e. where we need to be/what we need to be ready for).
OVERVIEW: A PPT with an overview of the process is available, which shows what is needed from the TFs and SIGs. Background from the GPPC perspective is also available, but TF and SIG feedback should not be limited to "stuff we want from the project" but really focus on future trends and requirements.
DOCUMENT STORAGE: Nathalie has created a folder on the Intranet to store all the docs once they are created.
QUESTIONS TO ASK:
The main question we need feedback on is:
- What new service / development requirements do you see for NRENs in the next 3 - 5 years?
Supporting questions to help you guide discussions:
- What are the priorities and specific ideas for innovation in these areas? What services and capabilities not currently offered by GÉANT will be needed i n 3-5 years?
- What is the potential impact of new technologies such as orchestration, automation and controlling applications?
- Do we do enough to bridge the digital divide? If not, how could we make a more effective contribution?
- Any regrets from opportunities not taken from funding sources, or priorities given to funding sources?
- How well do we do at NREN commitments early in the process of service device development? The use of services, facilities and even the network varies a lot from NREN to NREN: Should new services or new service features be developed only after a certain minimal number of NRENs express their commitment to offer/use them for their business?
- Do you think we should make an effort to serve communities outside of the R&E community - following the ECs evolving priorities and flagship projects?
- Do you see any significant future changes in the NREN business models affecting what they want to get from GÉANT Ass/Ltd. E.g Importance of SLAs and KPIs, use of non-commercial software from GÉANT Ass/Ltd, other projects or research groups.
TO DO:
Gather information to feed into this process from the Task Forces and SIGs as follows:
| SIG / TF | How will requirements be gathered? | Feedback |
|---|---|---|
SIG Greenhouse Nicole Harris | Via mailing list and discussion with SC. Nicole to take forward. e-mail sent and awaiting replies. | Developer community waning within the NREN world. Lots of reliance on OSS but no strategy for long-term support for the software, very few NRENS have development strategy in place alongside procurement strategy, difficulties with maintaining developers. Work on Docker recipes and approaches. |
SIG Multimedia (was WebRTC) Peter Szegedi | Open Educational Content: make them accessible and re-usable. In-context based real-time communications. Application development based on the WebRTC protocol. Rel time traffic (audio, video, data). Make the GÉANT TURN Service pilot global (nodes in Americas, Asia Pacific, Africa). | |
SIG SCOPE Nadia Sluer | ||
SIG-ISM / WISE Sigita Jurkynaite, Alf Moens (chair) | Sent the questions out to the SC - asked to provide feedback before 7 April. |
|
SIG-Marcomms and SIG MSP Laura Durnford, Gitte Kudsk (DeIC), Maria Ristkok (EENet), Lonneke Walk (SURFnet - chair)
Laura Durnford / Magda Haver, Walter van Dijk (SURFnet), Mark Tysom (Jisc), Harri Kuusisto (CSC-Funet), Alberto Perez (REDiris), Martin Bech (DeIC - chair) | Planned for upcoming meetings. | Presentation by SURFnet:
Presentation by DeIC
|
SIG-NGN Brook Schofield, Rob Evans (chair) | Question posed to the entire mailing list and the SIG-NGN Slack channel. No comments via email. | Members of SIG-NGN overlap with the APM/STF group and feedback collected by Annabel/Nathalie might be relevant in this context. From discussions on a future NGN meeting the topics raised were:
|
SIG-NOC Charlie van Genuchten, Brian Nisbet (chair) | To be discussed with the SIG-NOC steering committee on April 5 | Input HEAnet
Input CSUC
You already offer most of the services NREN might require now. One idea would be offering Assessment to NREN and its connected entities (I think Jisc already does something). As there are so many different services, so many clouds, so complicated laws...and the network is seen as a commodity, but is more complex than that. Big universities or entities usually have good teams and technicians, but small institutions can't afford to have many people and they need assessment. This assesment could be in many fields, like:
Innovation for e-learning, teaching services to foster online teaching, master classes, e-portfolios. What is the potential impact of new technologies such as orchestration, automation and controlling applications? Applications control everything, but automation and orchestration are essential to keep these applications running and to have all our network and systems equipment (logical and physical) items under control. Monitoring is always healthy, as a key for fast resolution of incidents and to anticipate future issues. Not only for the network.
And this is exactly what reminds me on what we do. We are a consortium of 10 universities. We ask them what they would like to get from us, but before offering a service or even beginning with all the process to offer it, we need at least 3 of them committed to contract or use the service. This means 30%. It works well for us. It could work well for you.
I would involve enterprises if they are related to research and education. We do it here, although these enterprises do nos get their internet connection trough RedIRIS or Géant, but through a commercial provider. They have an excellent connection to the R&E institutions in Catalonia, because they have projects or collaborate with them.
As a philosophical idea, NREN (and GÉANT) should be flexible enough to adapt to the needs of the connected institutions and to the changes on the technology and the network. Sometimes, they may be too tied up because they belong to public sector institutions, and public sector things are usually quite inflexible. NRENs must have the agility to accommodate to changes and be able to offer a good service despite crisis or problems. It has to motivate its customers and users to use the network for research, like a catalyzer. |
SIG-PMV Kurt Baumann | Via mailing list and discussion with SC. Nicole to take forward. e-mail sent and awaiting replies. | |
SIG-TNE Esther Wilkinson, Sigita Jurkynaite | new group, unlikely to be significant feedback at this stage. | |
TF-CSIRT Nicole Harris, Sigita Jurkynaite, Baiba Kasina (chair) | To be discussed with TF-CSIRT Steering Committee at upcoming retreat. | only real requirement is to increase amount of time allocated to TF-CSIRT given its size and ambition of the new TF-CSIRT Strategy. |
TF-RED Sylvia Kuipers + (TBC) | Planned for upcoming meetings. | new group, unlikely to be significant feedback at this stage. |
TF-Storage / SIG-CISS Peter Szegedi, SC members | SIG-CISS work item #2 ;) -- transnational compute-job mobility in the form of docker containers that can be moved at will between different NREN cloud stacks, supervised probably by some sort of meta-orchestrator, and ideally with the collection of already-prepackaged workflow containers available in an "NREN science app store". Federation of data storage with possibilities to run computations close to the data. | |
| TF-MNM / other mobility groups |
| |
| General |
|