Your SlideShare is downloading. ×
Virtualization-based Techniques for Enabling Multi-tenant ...
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Virtualization-based Techniques for Enabling Multi-tenant ...

1,300
views

Published on

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,300
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
36
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Advisor, mentors, manager
  • Network management is a standard service in current enterprise environments. Define front-end, back-end, probe agent, network, etc. Out-sourcing and service business
  • Different NMS software Multiple front-end interface to be dealt with
  • Reduce service delivery cost (smaller infrastructure) Reduce supporting cost (training, management)
  • Triple A Customer data integrity, privacy
  • VPN based Special probing device can also be used
  • Final architecture diagram
  • Transcript

    • 1. Virtualization-based Techniques for Enabling Multi-tenant Management Tools T. J. Watson Research Center Yaoping Ruan Sambit Sahu Anees Shaikh University of Michigan Chang-Hao Tsai Kang G. Shin
    • 2. Typical Network Monitoring Infrastructure Network Agent Management Workstation DB
    • 3. Monitor Multiple Customers Using Typical Infrastructure Customer C Network Customer B Network Customer A Network Agent Mgt WS DB Agent Mgt WS DB Agent Mgt WS DB Service provider Customers
    • 4. Multi-Tenant Network Monitoring Infrastructure Customer A Network Agent Customer B Network Agent Customer C Network Agent DB Management Workstation
    • 5. Issues
      • Significant re-design and re-implementation required
        • New authentication, authorization, accounting system
        • Flexible configurations (specific rules and preferences)
        • Scalability
        • Problematic for legacy software products
      • Network management service isn’t simply convertible
        • Firewall
        • Network address contention between customers
          • Private Internet addresses (10/8, 172.16/12, 192.168/16)
          • Wide use of NAT-router
        • Some functions need L2 network access (DHCP, BOOTP…)
    • 6. Goal : Make Single-tenant Tools Multi-tenant Capable
      • Approach
        • Virtualization
          • Creating containers for each single-tenant instance
        • Consolidation
          • Sharing common infrastructure
      • How?
        • Demonstrate how to make a single-tenant network management system multi-tenant capable
    • 7. Example Tool: OpenNMS
      • Open-source with commercial support
        • www.opennms.org / www.opennms.com
      • Java application
        • Front-end: Java Servlets, JSP
        • Database: PostgreSQL
      • Primary functions
        • Device discovery
        • Service and performance monitoring
        • Event management
        • Asset management
    • 8. Outline
      • OpenNMS architecture and service model
      • Approaches to enabling multi-tenancy
        • Virtualization-based back-end consolidation
        • Database sharing
        • Front-end consolidation
      • Evaluation
        • Workload profile
        • Scalability
      • Conclusion
    • 9. OpenNMS Architecture PostgreSQL Nodes/Services/Events/Outages/ Notifications/SNMP configuration/… JVM OpenNMS (main program) JVM Tomcat OpenNMS UI Customer Network Response Time (RRD files)
    • 10. OpenNMS Service Model Customer Network JVM OpenNMS Network Management Service Provider L2 VPN JVM Tomcat UI 1 PgSQL RRD files
    • 11. Back-end Consolidation
      • Goal: Minimum changes to the original system
      • Requirements
        • Resource (memory, processes) isolation
        • Independent file system
        • Virtualized network layer
      • Virtualization
        • Secure, private
        • Low-overhead (Xen, OpenVZ)
        • Performance isolation
    • 12. Database Sharing and Front-end Consolidation
      • All instances use the same schema
      • Database: one database server
        • Separate database user and database name
        • Database privileges for access control
      • Front-end: one Tomcat server
        • Different paths for different instances
        • HTTP/S authentication
    • 13. Multi-Tenancy Using Virtualization Host OS (Dom 0) Customer 1 Network Customer n Network VM 1 JVM 1 OpenNMS 1 VM N JVM N OpenNMS n Network Management Service Provider VPN JVM Tomcat UI 1 UI n PgSQL RRD files VPN
    • 14. Evaluation
      • Resource profiling
        • Bottleneck identification
        • Scalability with customer network size
        • Software configuration – JVM heap size
      • Multi-tenant scalability
        • Baseline
        • Xen
        • OpenVZ
    • 15. Experiment Setup Host OS (Dom 0) Customer 1 Network Customer n Network VM 1 JVM 1 OpenNMS 1 VM N JVM N OpenNMS n Network Management Service Provider VPN JVM Tomcat UI 1 UI n PgSQL RRD files Apache 192.168.8.1…8.200 9.200 VPN Emulated Customer Network VPN PC Servers: Core 2 Duo E6600, 4GB RAM, (2) 7,200rpm HDD, GbE
    • 16. Resource Profile: Memory & CPU Usage
      • Single-tenant, monitoring 200 hosts
      • Memory is the bottleneck resource
    • 17. Scalability: 200 ~ 1000 Hosts
      • 2MB memory / 200 monitored hosts
      • Minimal incremental cost
    • 18. Impact of JVM Heap Size: 64 ~ 128 MB
      • GC frequency decreases with heap size
      • Live objects take up space and increase GC workload
      • OpenNMS + OpenVPN take 144MB to run
    • 19. Baseline: Simple Consolidation
      • Baseline: complete installation in each VM
      • RRD: disk I/O intensive
      • Benchmark by scripting front-end activities
        • Front-end and database accesses
        • Dynamic web page generation (average response time)
        • Service discovery and monitoring accuracy
    • 20. Multi-tenant Scalability
      • 60% increase for Xen
      • 90% increase for OpenVZ
      • 58% increase for Xen
      • 83% increase for OpenVZ
      With RRD Without RRD
    • 21. Future Work
      • Java class sharing
        • Duplicated class definition, but JVMs are in different VMs
      • Coordinating JVMs
        • JVMs in guest OS are unaware of VM sizing
        • Dynamic JVM sizing
    • 22. Conclusion
      • An approach to enabling multi-tenant capability
        • Virtualize the base platform
        • Share supporting services
      • Increased service density
        • 60-90% more tenants on a single platform
    • 23. Thank you for your attention. Any questions? {chtsai,kgshin}@eecs.umich.edu {yaopruan,sambits,aashaikh}@us.ibm.com