Multi-Domain Orchestration for the Deployment and Management of Services on a Slice Enabled NFVI

This paper presents a unique and new scenario where services are deployed across distributed domains, and each domain MANO (for VNF Management and Orchestration) requests and creates an on-demand Data Center slice to run those service elements. Whilst each domain has its own MANO, the MANOs are configured in a north-south way creating a hierarchy of service provision capabilities, rather than configured in the more common peer-to-peer approach. This approach works particularly well where each domain, from the mobile edge, to the core DC, can be managed independently of the others, but needs to be combined to form slices. End-to-end slices across the whole infrastructure provide a more effective resource management and also better support the customers’ mobility requirements. The details of the architecture to support this scenario are described

Dynamic Monitoring of Data Center Slices

Slicing is a move towards segmentation of resources and deployment of NFV for the purpose of enhanced services and applications on globally shared resources. The slicing approach in this paper considers Data Center slicing and the VIM on-demand model. We focus on the monitoring of Data Center slices, showing what is needed from the monitoring perspective and how the monitoring should be done. The proposed monitoring approach is validated on a platform that supports the on-demand creation of lightweight VIM instances

Multi-Domain Orchestration for the Deployment and Management of Services on a Slice Enabled NFVI

This paper presents a unique and new scenario where services are deployed across distributed domains, and each domain MANO (for VNF Management and Orchestration) requests and creates an on-demand Data Center slice to run those service elements. Whilst each domain has its own MANO, the MANOs are configured in a north-south way creating a hierarchy of service provision capabilities, rather than configured in the more common peer-to-peer approach. This approach works particularly well where each domain, from the mobile edge, to the core DC, can be managed independently of the others, but needs to be combined to form slices. End-to-end slices across the whole infrastructure provide a more effective resource management and also better support the customers' mobility requirements. The details of the architecture to support this scenario are described

Orchestration in the Cloud-to-Things compute continuum: taxonomy, survey and future directions

IoT systems are becoming an essential part of our environment. Smart cities, smart manufacturing, augmented reality, and self-driving cars are just some examples of the wide range of domains, where the applicability of such systems have been increasing rapidly. These IoT use cases often require simultaneous access to geographically distributed arrays of sensors, heterogeneous remote, local as well as multi-cloud computational resources. This gives birth to the extended Cloud-to-Things computing paradigm. The emergence of this new paradigm raised the quintessential need to extend the orchestration requirements (i.e., the automated deployment and run-time management) of applications from the centralised cloud-only environment to the entire spectrum of resources in the Cloud-to-Things continuum. In order to cope with this requirement, in the last few years, there has been a lot of attention to the development of orchestration systems in both industry and academic environments. This paper is an attempt to gather the research conducted in the orchestration for the Cloud-to-Things continuum landscape and to propose a detailed taxonomy, which is then used to critically review the landscape of existing research work. We finally discuss the key challenges that require further attention and also present a conceptual framework based on the conducted analysis