Icin2012
Upcoming SlideShare
Loading in...5
×
 

Icin2012

on

  • 221 views

 

Statistics

Views

Total Views
221
Slideshare-icon Views on SlideShare
221
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
1

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Icin2012 Icin2012 Presentation Transcript

    • Session 1 "Cloud Opportunities for Telcos"Towards a CAPEX-free Service Delivery PlatformP. Baglietto, M. Maresca, M. Stecca - CIPI University of Genoa and Padua C. Moiso - Strategy Telecom ItaliaCompany logos may appear on this title page
    • Outline• Introduction• Moving Service Platforms In The Cloud• Embracing Open Source Software for the SDP• Open Source Service Platforms in The Cloud• Case Study: An Elastic Open Source Service Orchestrator• Conclusions Session 1 / Towards a CAPEX-free8-11 Oct 2012 Service Delivery Platform 2
    • Introduction• Is it possible to decrease CapEx and to transform part of these expenditures into OpEx? – To reduce costs – To improve efficiency – To reduce the risks related to the launch of a *real* new service• How can we do that? – Open Source Software (OSS) – Cloud Computing (Cloud) – OSS + Cloud In this paper we explore the pros/cons related to these three solutions Session 1 / Towards a CAPEX-free8-11 Oct 2012 Service Delivery Platform 3
    • Moving Service Platforms in the Cloud (1/3)1. Virtualizing SDP (Service Delivery Platform) components in the Cloud – Private/Public Cloud – Hybrid Cloud (e.g., to manage unexpected traffic peaks)2. Virtualizing users’ terminals in the Cloud – To compensate mobile terminals limited on-board resources (see, e.g., the ‘CloudPhone’ and the ‘Virtual Smartphone over IP’ projects by Intel and NTT)  See #1 in next slide – To “reduce the distance” among mobile terminals and the SDP  See #2 in next slide Session 1 / Towards a CAPEX-free8-11 Oct 2012 Service Delivery Platform 4
    • Moving Service Platforms in the Cloud (2/3) #1 #2 Session 1 / Towards a CAPEX-free8-11 Oct 2012 Service Delivery Platform 5
    • Moving Service Platforms in the Cloud (3/4)• Pros – Cost Reduction (e.g., pay-as-you-go model, auto-scaling,…) – From CapEx to OpEx – Improved Time to Market – ‘Green’ approach Session 1 / Towards a CAPEX-free8-11 Oct 2012 Service Delivery Platform 6
    • Moving Service Platforms in the Cloud (3/4)• Pros – Cost Reduction (e.g., pay-as-you-go model, auto-scaling,…) – From CapEx to OpEx – Improved Time to Market – ‘Green’ approach• Cons/Risks – Lock-in (due to lack of standardization) – Licensing problems (e.g., Oracle) – Data privacy (for European users, see the Directive 95/46/EC) – Software/Hardware specific requirements Session 1 / Towards a CAPEX-free8-11 Oct 2012 Service Delivery Platform 7
    • Moving Service Platforms in the Cloud (4/4)• …and pay attention with the Cloud Providers Session 1 / Towards a CAPEX-free8-11 Oct 2012 Service Delivery Platform 8
    • Embracing Open Source Software for the SDP (1/3) The SDP reference architectural model Session 1 / Towards a CAPEX-free 8-11 Oct 2012 Service Delivery Platform 9
    • Embracing Open Source Software for the SDP (2/3) • Examples of Open Source SDP components: – Core Network: Open IMS Core (part of the Open IMS Playground @ FOKUS); – IP PBX systems: Asterisks; – SMS gateway: Kannel; – MMS gateway: Mbuni; – Application Servers: Mobicents (JSLEE + SIP Servlet), JBoss, Glassfish; – Map-Reduce: Hadoop; – NoSQL databases: HBase, MongoDB; – Enterprise Service Bus: Apache ServiceMix; – Service Orchestration: Orchestra, Apache ODE; – … Session 1 / Towards a CAPEX-free 8-11 Oct 2012 Service Delivery Platform 10
    • Embracing Open Source Software for the SDP (3/3) • Pros – cost effective and flexible approach – mitigate the ‘lock-in’ from vendors – increase the level of ‘mastering’ of all the software stack – platform enhancement in a shorter time frame and at lower costs • Cons/Risks – lack of support – risks of infringements of licensing terms – Telcos must adopt new specific procedures for ‘software quality’ control Session 1 / Towards a CAPEX-free 8-11 Oct 2012 Service Delivery Platform 11
    • Open Source Service Platforms in The Cloud (1/2)• Telco might take advantage of both the OSS and the Cloud paradigm.• In order to exploit this opportunity, we defined a table (see next slide) where – The rows represent the Cloud choice (Public vs. Private); – The columns represent the software choice: • OSS; • Vendor software; • Custom software (i.e., developed by the Telco Operator). Session 1 / Towards a CAPEX-free 8-11 Oct 2012 Service Delivery Platform 12
    • Open Source Service Platforms in The Cloud (2/2) Session 1 / Towards a CAPEX-free 8-11 Oct 2012 Service Delivery Platform 13
    • So far… Next: a real example for OSS + Cloud Session 1 / Towards a CAPEX-free8-11 Oct 2012 Service Delivery Platform 14
    • An Elastic Open Source Service Orchestrator (1/4) • We developed a Service Orchestrator using OSS1 • We deployed such a system on a Private Cloud based on the commercial product VMware2 • We finally deployed it on an Open Source Private Cloud 1 Stecca M. et al, “Scalable Orchestration of Telco/IT Mashups”, ICIN 2009 2 Stecca M. et al, “An Architecture for a Mashup Container in Virtualized Environments”, IEEE Cloud 2010 Session 1 / Towards a CAPEX-free 8-11 Oct 2012 Service Delivery Platform 15
    • An Elastic Open Source Service Orchestrator (2/4) Products: • IaaS system: Eucalyptus (Hypervisor: KVM); • Load Balancer: HAProxy; • Orchestrator middleware: JBoss AS messaging system (i.e., JMS). Session 1 / Towards a CAPEX-free 8-11 Oct 2012 Service Delivery Platform 16
    • An Elastic Open Source Service Orchestrator (3/4) • In order to have an elastic system we extended the Eucalyptus IaaS framework with 3 new components: – A Load Balancer: we re-used the Open Source HAProxy Load Balancer; – The Monitor: it monitors the VMs’ resource usage; – The Control Daemon: it knows the entire status of the system and decides whether it is necessary to execute a scaling operation (the user can define some triggers like, e.g., “turn on a new virtual machine if the incoming traffic goes beyond 100MB/s”). Session 1 / Towards a CAPEX-free 8-11 Oct 2012 Service Delivery Platform 17
    • An Elastic Open Source Service Orchestrator (4/4) • A Scale-up operation can be summarized as follows. The Daemon Controller: – detects the need for a new Scale-up operation by comparing the Monitor collected data against the thresholds defined by the user; – chooses the appropriate virtual machine type and image, according to the user preferences; – checks whether there are enough resources to be allocated to the new virtual machine in the Eucalyptus system; – sends a request to the Eucalyptus infrastructure to start a new virtual machine; – waits for the new virtual machine activation and initialization. When the virtual machine is in the ‘running’ status, the system updates the Load Balancer configuration by adding the details of the new virtual machine; – finally the Control Daemon issues the ‘hot-reconfiguration’ command to the HAProxy Load Balancer. Session 1 / Towards a CAPEX-free 8-11 Oct 2012 Service Delivery Platform 18
    • Conclusions• We analyzed the advantages and the potential risks that must be taken into account when moving the SDP’s components to an OSS/cloud-based solution.• It is possible to transform CapEx into OpEx but the 0- CapEx SDP is not a reality yet.• We described an OSS/Cloud-based Service Orchestrator.• We are planning to migrate other SDP’s components to OSS-based/cloud-based systems with particular attention to mobile terminals. Session 1 / Towards a CAPEX-free8-11 Oct 2012 Service Delivery Platform 19
    • The End Michele SteccaFollow me on Twitter: @steccami 20