Cloud Networking- Provider & Vendor Perspective- at IEEE ComSocSCV Oct 12 meeting!


In a pure Public Cloud based model, applications reside in a multi-tenant environment and are accessible via the public Internet. Amazon’s EC2  is an example of such a Public Cloud.  Yet there are concerns about security, privacy, failure recovery and performance when using the public Internet to deliver Cloud Compute and Storage services.

In the Private / Hybrid cloud model, best effort Internet performance is not good enough. In many cases, applications must perform just as well across the WAN as they would over an enterprise LAN. Latency, jitter, quality of service, interoperability, performance guarantees, and bandwidth management all become extremely important.

The IEEE ComSocSCV Oct 12 meeting in Santa Clara, CA will address the challenges and opportunities in Cloud Networking.  The Savvis Converged Cloud will be described as a solution.  Juniper Networks and Arista Networks will then provide a network equipment vendor perspective of Cloud Networking.  This will be followed by a lively panel session with both pre-planned and audience questions.  Get your questions ready!

Please arrive by 6pm to particpate in our 1/2 hour networking session.  Juniper and Deutshe Telekom will have a table to discuss their Cloud based initiatives.  IEEE ComSocSCV officers will also be on hand to discuss our November and December meetings on Video Distribution over HANs and Silicon Valley Power’s Outdoor Wireless Mesh Network for Smart Grid.  More info & RSVP instructions:

EXCLUSIVE new article on Deutsche Telekom activities in Silicon Valley by Louis Schreier of T-Labs USA

The Savvis Solution for Cloud Networking

The Savvis Converged Cloud integrates the high performance aspects of cloud services (compute and storage) with high performance networking. The Converged Cloud architecture has been deployed in the financial, voice, video, and SaaS markets. It is targeted at a business requirement where data volumes are high, and the application experience is critical.

There are three major elements in the Savvis Converged Cloud:

  1. A managed virtualized hosting environment.
  2. A secure, low-latency distribution network.
  3. A unique business model that facilitates design of a complete, end-to-end, QoS enabled solution via the offering of standard end-to-end product sets.

These will all be described in detail by the two Savvis speakers. A vendor perspective of Cloud Networking will then be provided by VPs of Juniper Networks and Arista Networks. A lively panel session with audience Q and A will follow the presentations.


  • Michael Cowburn, Sr. Solutions Architect, Savvis
  • Omar Smith, Network Solutions Architect, Savvis
  • Anshul Sadana, VP Customer Engineering, Arista Networks
  • Colin Constable, VP/CTO Strategic Alliances, Juniper Networks

Session Organizer

Alan J Weissberger, IEEE ComsocSCV Chair and Manager of ComSoc Community web site

Session Chair

MP Divakar, IEEE ComsocSCV Secretary

Preliminary list of Oct 12 Cloud Networking panel session questions:

We will consider the following themes for panel session:
  • What’s the impact on users and network equipment vendors in the absence of any definitive cloud networking standards?  Does a vendor have to respond to different cloud SP RFPs with highly tweaked switch/routers or even special purpose gear?
  • Is VPN tunelling thru the public Internet the short term solution for delivery of cloud compute and storage services?  Intermediate and long term solution?
  • What’s the impact of security and privacy vulnerabilities for a public and private cloud network?
  • Is failure recovery an issue with a pure public cloud service?
  • Is using a hybrid network consisting of public Internet and private shared network viable today and long term?
  • What impact does a high performance cloud resident data center place on the cloud delivery network?
  • How will public- private clouds interwork in the absence of standards (IEEE Cloud Interworking WG was supposed to specify this, but they’re not)?.  2 scenarios to consider:  Cloud bursting where “overflow” work loads get dispatched from private to public cloud, and private to public cloud partitioning where some co-ordination may be necessary.
  • Is it possible to build a federated private cloud, ideally with single sign on, to enable collaborative computing among partner companies/ organizations?  What are the functional private inter-networking requirements?  What type of private network-to-private network specification is needed to realize this vision?

TOP READ CLOUD ARTICLES by Alan J Weissberger,  IEEE ComSocSCV Chair and Manager of ComSoc Community web site

0 thoughts on “Cloud Networking- Provider & Vendor Perspective- at IEEE ComSocSCV Oct 12 meeting!

  1. One of the little known facts about cloud networking is there are at least 4 subnetworks that collectively comprise the end to end path between the cloud user and Cloud data center/servers:

    -the campus/workgroup LAN premises network (for fixed line cloud access from an enterprise)

    -the access network to the ISP POP (from either a mobile wireless device or enterprise fixed access line, e.g. bonded DS1/DSL, DS3, OC3, 10M- 1G Ethernet, etc)

    -the cloud service delivery WAN consisting of the public Internet, shared private network (e.g. IP-MPLS VPN) or a combination of these two.

    -the cloud SPs internal data center network (probably with 1-10G Ethernet connections between high performance servers and data center Ethernet switches- hello, Juniper!)

    Each of these subnetworks has its own management domain. Different companies/ organizations are involved in the administration of each of these networks, yet the details must be transparent to the cloud user. This creates quite a challenge in trying to guarantee SLAs, isolate failures and repair them quickly.

    When a user replaces his on premises data center with a Cloud resident data center (public or private cloud), he may still expect LAN like performance from the Cloud service delivery network. But he probably won’t get it unless all the subnetworks are properly matched to provide the performance/ QoS needed!

    How likely is that to happen? What entity will monitor and guarantee SLA compliance? Come to this meeting and ask the speakers directly!

  2. The Oct 12 IEEE ComSocSCV meeting ran late (till 9pm) and not all questions could be answered. Independent of whether or not you attended the meeting, you may email me your questions for Savvis/ Century Link, Juniper, Arista Networks (panelists), as well as the 2 telcos present- Deutsche Telekom and XO Communications (a facility based competitive carrier).
    Note the Cloud taxonomy/ terminology has blurred. For example, what is a Virtual Private Cloud? What is a hybrid cloud?

    -A dedicated private line connection to a public cloud, e.g Amazon EC2, Rackspace, MSFT Azure, etc?

    -An Ethernet Virtual Private Line or VPLS, or IP-MPLS VPN to a public Cloud

    -A dedicated private line, Ethernet Virtual Private Line or VPLS, or IP-MPLS VPN to an off premises Private Cloud?

    This is why I said on Oct 12th that the “network” used to deliver cloud compute, storage, & video/audio services is the MOTHER OF ALL CLOUD CONNUNDRUMS! Again, that “network” consists of multiple interconnected subnetworks that all must work seamlessly to deliver acceptable performance, security/privacy, reliability/availablity, failure and disaster recovery!

    And the cloud network is even more complicated for a hybrid Cloud (both private and public cloud servers/ network). There are no standards for private- public or private- private cloud. What happened to the IEEE WG that was supposed to develop an Inter-Cloud standard?

Leave a Reply

Your email address will not be published. Required fields are marked *

I accept that my given data and my IP address is sent to a server in the USA only for the purpose of spam prevention through the Akismet program.More information on Akismet and GDPR.

This site uses Akismet to reduce spam. Learn how your comment data is processed.