All of the currently available BEACON documents can be downloaded on this page. The D prefix before each stands for 'deliverable'.

Further reports will be available as the project progresses. If you have any queries about these reports please get in touch with us.

D2.1  

BEACON Framework Summary Document D2.1.a is the first deliverable of WP2 titled “Federated Cloud Networking Framework Architecture”. This document describes the use cases that guide the BEACON project, and identifies the main user requirements derived from these use cases.

D2.2

BEACON Framework B Summary Document D2.2 is the second deliverable of WP2, which is an update of previous D2.1 for the second design and development cycle. This document describes the use cases that guide the BEACON project, and identifies the main user requirements derived from these use cases.

The document also describes the main cloud components that will be considered to build the federated cloud network architecture, and defines the main architectures for cloud federation and interconnection that will be considered in the BEACON framework to support the different use cases, such as peer cloud federation, hybrid cloud federation, and brokered cloud federation. 

D2.3

Document D2.3 is an update of previous D2.2 for the third design and development cycle. This document describes the use cases that guide the BEACON project, and identifies the main user requirements derived from these use cases. The document also describes the main cloud components that will be considered to build the federated cloud network framework, and defines the main approachesfor cloud federation and interconnection that will be considered in the BEACON framework to support the different use cases. The document identifies the main software requirements derived from the user requirements, and defines the roadmap for the next six months of the project, including the specification of the scenarios to be addressed in this period, and the definition of the test suite for the verification of these scenarios. The roadmap defined in this document will be the starting point for the third iteration of WP3 and WP4, that will define in more detail the particular component design and testing scenarios to be implemented, in order to satisfy the list of requirements.

D2.4

Interaction with External Related Efforts A: Summary This document reports on the different initiatives and actions taken and planned by the BEACON consortium in order to collaborate at EU and global level, and to share the developments in the potential of cloud computing in Europe.

D3.2

Document D3.2 is the second deliverable of WP3 Federated Cloud Network Management. This document describes in more detail the federated cloud network architecture derived from the software requirements that follow the use cases identified in D2.2 BEACON Framework. D3.2 presents a description of the control and data plane components of BEACON networking architecture, and the APIs that these components shall use for their communication. The document also presents BEACON federated network services extension for SDN environment with the focus on Virtualized Network Functions, as well as a security analysis of the BEACON network federation architecture. The two main BEACON federated network architecture components defined in the scope of WP3 Federated Cloud Network Management, are Federation Agent - responsible for the control plane of the federated network solution; and Federation Datapath - responsible for the dataplane solution. The detailed design of these components and their interaction with federated cloud environment components, such as Cloud Management Platforms (e.g. OpenStack and OpenNebula) and SDN network controller (e.g. OVN) was presented in D3.1. The current document details enhancements developed to these components in the second development cycle of the project. Finally, the document describes the features identified in D2.2 BEACON Framework for development during the second cycle of the project, as well as the research undertaken to define, design and develop these features.

D3.3

Document D3.3 is the third deliverable of WP3 Federated Cloud Network Management. This document describes in more detail the federated cloud network architecture derived from the software requirements that follow the use cases identified in D2.3 BEACON Framework. D3.3 presents a description of the control and data plane components of BEACON networking architecture, and the APIs that these components shall use for their communication. The document also presents BEACON federated network services extension for SDN environment with the focus on Virtualized Network Functions, as well as a security analysis of the BEACON network federation architecture and monitoring services. The two main BEACON federated network architecture components defined in the scope of WP3 Federated Cloud Network Management, are BEACON Network Agent - responsible for the control plane of the federated network solution; and BEACON Datapath - responsible for the dataplane solution. The detailed design of these components and their interaction with federated cloud environment components, such as Cloud Management Platforms (e.g. OpenStack and OpenNebula) and SDN network controller (e.g. OVN) was presented in D3.1. The current document details enhancements developed to these components in the third development cycle of the project. Finally, the document describes the features identified in D2.2 BEACON Framework for development during the third cycle of the project, as well as the research undertaken to define, design and develop these features

D3.4

Software Prototype WP3: Summary Document D3.4 is the second deliverable of WP3 titled “Federated Cloud Network Management”. This document describes the software components developed to address the identified high priority requirements that will satisfy the BEACON use cases. 

D4.1

Scientific Report WP4: Summary Document D4.1 is the first deliverable of WP4 titled “Federated Cloud Infrastructure Management”. This document describes in detail the architecture derived from the software requirements that follows the use cases identified in D2.1, with a description of the components of such architecture, and the APIs that these components shall use for their communication.

The document also describes the features identified for development the first cycle of the project to address the use cases, to be built on top or around the components that will be considered to build the federated cloud network architecture such as OpenNebula, OpenStack and Flexiant Cloud Orchestrator. This deliverable also describes the research undertaken to define, design and develop the features built in the first cycle of BEACON. 

D4.2

Document D4.2 is the third deliverable of WP4 titled “Federated Cloud Infrastructure Management”. This document describes in detail the architecture derived from the software requirements that follows the use cases identified in D2.2, with a description of the components of such architecture, and the APIs that these components use for their communication. The document also describes the features identified for development in the second design and development cycle of the project -those that fulfill the requirements flagged as MEDIUM in D2.2- to address the use cases, to be built on top or around the components that will be considered to build the federated cloud network architecture such as OpenNebula, OpenStack and Flexiant Cloud Orchestrator. This deliverable also describes the research undertaken to define, design and develop the features built in the second cycle of BEACON.

D4.3

Document D4.3 is the fifth deliverable of WP4 titled “Federated Cloud Infrastructure Management”. This document describes in detail the architecture derived from the software requirements that follow the use cases identified in D2.2, with a description of the components of such architecture, and the APIs that these components use for their communication. The document also describes the features identified for development in the second design and development cycle of the project -those that fulfill the requirements flagged as LOW in D2.2 to address the use cases, to be built on top or around the components that will be considered to build the federated cloud network architecture such as OpenNebula, OpenStack and Flexiant Cloud Orchestrator. This deliverable also describes the research undertaken to define, design and develop the features built in the second cycle of BEACON.

D4.4

Software Prototype WP4: Summary Document D4.4 is the second deliverable of WP4 titled “Federated Cloud Infrastructure Management”. This document describes the software components developed to address the identified high priority requirements that will satisfy the BEACON use cases. 

D5.1

Integration and Infrastructure Report - a: Summary Document D5.1‐a is the first deliverable of WP5 titled “Integration and Infrastructure Report” and corresponds to the document uploaded as D5.1. This document describes the logical layout, networking and storage architecture of the testbeds, able to support the different use cases in the BEACON project, such as tightly coupled federated cloud scenario (peer cloud federation), loosely coupled federated cloud scenario (hybrid cloud federation), and multi‐cloud orchestration where several public independent clouds interact (brokered cloud federation).

The document also identifies the main requirements for any project testbed, derived from the development requirements. 

D5.4

Document D5.4 is the result of the first cycle of task 5.3, WP5 - Demo/Test bed/Use cases. The document deals with the verification and the validation of the sites using the use cases. The deliverable briefly describes all the use cases and summarisesthe requirements derived from the user requirements. The verification and validation process is described for all the use cases but UC1 - automated high availability across datacenters and UC5 - Multi-Cloud Deployment of an Airline Scheduling Application, as there are no actions taken for the use case in the first year. The roadmap for the use cases are also included in this document. The results of the next iterations will be described in D5.5 and D5.6 which are scheduled to be delivered in M24 and M30 respectively.

D5.5

Document D5.5 is the result of the second cycle of task 5.3, WP5 - Demo/Test bed/Use cases. The document deals with the verification and the validation of the use cases. The deliverable briefly describes all the use cases and summarises the requirements derived from the user requirements. The verification and validation process is described for all the use cases. The roadmap for the use cases is also included in this document. The results of the next and final iteration will be described in D5.6 which is scheduled to be delivered in M30.