| Section | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
In amulti-domain environment with automated provisioning of composite inter-domain services, it is of great importance that the collaborating parties agree to follow a certain minimum set of principles and guidelines. Within the GÉANT community, this multi-domain environment might include GÉANT as an organisation, the NRENs, but also other related parties such as research institutions, universities, etc. In other words, any entity that has its own administrative domain and would like to build an OAV solution to manage its domain and products with their underlying services.
This list of requirements can be used as a checklist of features and capabilities needed to providean efficient, yet highly agile and dynamic environment that supports a vast set of servicesbuilt upon physical and virtual resources, as well as enable collaborative efforts with all partners. Itcan be considered a summary of characteristics or guidelines that should be part of an architecture blueprint or reference architecture for OAV within an organisation, but that at the same time can lay the groundwork for defining a common understanding and common interface between other multi-domain parties. Such an architectureblueprint for OAV is needed to set the foundation for federation, interoperation and collaboration between the separately implemented solutions in the NREN community. Adhering to this minimum set of requirements does not impose any particular restrictions on the manner of implementation of an NREN’s architecture; specifics of local implementation are a matter for each NREN. The requirements call for a technology-and service-agnostic design so that any type of technology can be used for the implementation of separate components of the architecture, and the architecture can be used for the agile, model-driven lifecycle management of any type of digital service an NREN would like to offer.
It must be stressed that the requirements anddesign principles discussed in this section are to be considered as enduring guiding principles that provide a consistent set of rules across the whole organisation and its processes. They are aligned to the standards of The Open Group Architecture Framework (TOGAF) and are based on the TOGAF Architecture Development Methodology [TADM11].
References:
[NFVPLREP] 4th ETSI NFV Plugtests Report V1.0.0 (2019-07), https://portal.etsi.org/Portals/0/TBpages/CTI/Docs/4th_ETSI_NFV_Plugtests_Report_v1.0.0.pdf
[TADM11] TOGAF Architecture Development Methodology, 2011, https://pubs.opengroup.org/architecture/togaf91-doc/arch/chap05.html