Cloud Management Systems (CMS) such as OpenStack are commonly used to manage IT resources such as computing and storage in large datacenters. Recently, CMS are starting to offer customers also the possibility to customize their network infrastructure, allowing each tenant to build his virtual network made of elementary blocks such as traffic monitors, switches, routers, firewalls, and more. However, tenants have to choose those network services among the list of services made available by the CMS and have no possibilities to customize the applications they want. This paper examines some of the modifications required in CMS to support a tenant-centric network service model, in which each tenant can install and configure their preferred network functions, without being limited to use only the list provided by the CMS. A prototype implementation validates the proposed approach and demonstrates the extent of the modifications in terms of languages and software components.

Automatic Configuration of Opaque Network Functions in CMS / Spinoso, Serena; Leogrande, Marco; Risso, FULVIO GIOVANNI OTTAVIO; Singh, S.; Sisto, Riccardo. - STAMPA. - (2014), pp. 750-755. (Intervento presentato al convegno 1st International Workshop on Network Virtualization and Software-Defined Networks for Cloud Data Centres (NVSDN 2014) tenutosi a London, UK nel 8-11 December, 2014) [10.1109/UCC.2014.122].

Automatic Configuration of Opaque Network Functions in CMS

SPINOSO, SERENA;LEOGRANDE, MARCO;RISSO, FULVIO GIOVANNI OTTAVIO;SISTO, Riccardo
2014

Abstract

Cloud Management Systems (CMS) such as OpenStack are commonly used to manage IT resources such as computing and storage in large datacenters. Recently, CMS are starting to offer customers also the possibility to customize their network infrastructure, allowing each tenant to build his virtual network made of elementary blocks such as traffic monitors, switches, routers, firewalls, and more. However, tenants have to choose those network services among the list of services made available by the CMS and have no possibilities to customize the applications they want. This paper examines some of the modifications required in CMS to support a tenant-centric network service model, in which each tenant can install and configure their preferred network functions, without being limited to use only the list provided by the CMS. A prototype implementation validates the proposed approach and demonstrates the extent of the modifications in terms of languages and software components.
File in questo prodotto:
File Dimensione Formato  
14NVSDN-ServiceInsertion.pdf

accesso aperto

Tipologia: 1. Preprint / submitted version [pre- review]
Licenza: PUBBLICO - Tutti i diritti riservati
Dimensione 220.97 kB
Formato Adobe PDF
220.97 kB Adobe PDF Visualizza/Apri
Pubblicazioni consigliate

I documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione.

Utilizza questo identificativo per citare o creare un link a questo documento: https://hdl.handle.net/11583/2572147
 Attenzione

Attenzione! I dati visualizzati non sono stati sottoposti a validazione da parte dell'ateneo