ACG Research

ACG Research
We focus on the Why before the What
Showing posts with label Software Defined Network. Show all posts
Showing posts with label Software Defined Network. Show all posts

Thursday, June 4, 2015

Access Insights™: Intersection of SP Business Drivers and Emerging Tech

What is “access”? Simply put, it’s about access to the cloud and between people and things.

Access is no longer fixed or wireless. Access is about connecting people and things to each other and to applications and service in “the cloud.” Thus, access is about fixed and wireless. It’s about having the right combined architecture on a neighborhood-by-neighborhood basis. This “combo” trend is having, and will continue to have, major impacts and disruptions in the access market and in the entire service provider ecosystem. New technologies, architectures and business models will emerge. Market realities are forcing carriers to offer (up to) gigabit speeds and incumbents have billions of dollars in deployed assets and architectures. All this makes Access challenging for both technical/architectural and business decision making.

Top Access Insights to Ponder

  • The future of Access is Fixed and Wireless… not “or”;  SPs need to adapt organizations, so do vendors
  • Gigabit Deployment Strategy: Is timing everything? Real strategic implications to the @$# Speed Test.
  • Next-gen Broadband CPE architecture and business models are being disrupted; a. big risk to incumbent SPs and vendors
  • WiFi: The “toy” that grew up; strategic implications abound; Wi-Fi, further proof that the “low end always wins”
  • Voice over Wi-Fi: nothing but upside to cable companies; nothing but threats to MNOs.
  • LTE versus. Wi-Fi: Which one is for off-load?
  • Next Gen Cable Access Networks: PON Greenfield is redundant, DOCSIS Greenfield is an oxymoron
  • CPE vs. Carrier Gear (plastic versus metal): Plastic companies building metal?
  • SDN-NFV in Access:  It’s coming, contemplation begins
  • What’s the value of vendor incumbency at inflection points? Is Access different from any other industry?

Want to discuss these points with the analyst? Contact gwhelan@acgcc.com to schedule some time explore how these insights impact your strategies and how we can create actionable plans to address and exploit them.

Wednesday, May 20, 2015

Carrier SDN: Networks as Agile as the Cloud

Operators need more agile ways to deliver network services if they’re to fully realize the benefits of cloud computing. And many see Carrier Software-Defined Networking as the way forward.


Enabling Carrier SDN
Most of us know that remarkable gains in creating and deploying new services efficiently and at scale have been made in the cloud computing community. But in the network operator community we also know that a significant impediment to delivering new services with the agility of the cloud is the rigidity of the networks we deploy and the processes we use to define and instantiate the services.

Vendors have expended a great deal of effort in recent years to enhance network flexibility. Solutions have begun to appear that address parts of the problem, but they have typically been constrained to a particular function or domain and have not actually solved the overall agile service delivery problem for networks.

I’ve just had the opportunity to study the new Alcatel-Lucent Network Services Platform (NSP) and believe it has attributes that will interest operators who aspire to deliver services in a new way by enabling Carrier SDN.

What it is
The NSP is a unified solution that creates agility in network service delivery. It brings efficiency and flexibility to the front-end problems of new service creation and the immediate downstream problems of operating those services efficiently and intelligently in a multilayer, multidomain, multivendor network. It does so in a unified and holistically designed solution.

What I liked about it
NSP breaks the OSS/BSS logjam in network service creation. It uses open RESTful APIs northbound for OSS and BSS integration and important data modeling standards and templates for network and service representation. Services and networks are represented once to multiple OSS and BSS applications, eliminating the need to define the same service multiple times to different modules so they can talk to a range of vendors’ platforms.

1. NSP associates service policies and tenant contexts with newly defined services, and applies them broadly across the target network infrastructure. We analyzed development of a new bandwidth calendaring service by a representative operator and discovered that NSP brings improvements over 50 percent in both time and resources definition compared to present modes of operation.

2. As service templates travel southbound they’re converted by a versatile mediation engine into the semantics and formats needed to work with each IP/MPLS and optical network platform being managed. This auto-conversion dramatically simplifies and streamlines the provisioning process for service offerings across network layers, vendors, and domains.

3. Communication southbound with NSP is supported by multiple important multivendor standard protocols:
• BGP-LS
• PCEP
• NETCONF
• SNMP
• OpenFlow, future, where used

Special cases for vendor CLI support are also included for simplification.

4. NSP bridges the gap between service automation and network optimization. On-demand service provisioning becomes network-aware and makes best use of available network assets during service placement. Dynamic network optimization uses network and service health to drive changes that ensure ongoing service quality and network efficiency.

5. Alcatel-Lucent has integrated functionality derived from 1,000s of operator deployments in both optical and IP/MPLS layers to enhance NSP’s value. For example, three distinct path computation engines are available to meet operator requirements:
• Packet-oriented PCE (PCE-P) for use with IP/MPLS paths
• Optically-oriented PCE (PCE-T) for use with optical paths
• Multilayer PCE (PCE-X) for use in multilayer path optimization

PCEs define paths in line with service policies at provisioning time, and KPIs are monitored in real time to determine if adjustments of any sort are called for as operations progress.

6. Alcatel-Lucent has incorporated unique and innovative algorithms for resource optimization. For instance, self-tuned adaptive routing for LSPs helps the network adapt allocations in real time according to policies and service delivery needs, producing further efficiencies and revenue-generating capacity.

The NSP seems to supply a missing link in solving the wide area network agility problem by leveraging the benefits of Carrier SDN. service providers will be interested in how its combination of functions has the right attributes for turning WANs into agile service delivery platforms. And it’s likely to be a major contributor to many operators looking to make their networks as agile as the cloud.





Paul Parker-Johnson

Monday, April 20, 2015

Juniper Networks: Converged Supercore, an ACG HotSeat

Paul Obsitnik, vice president of service provider product marketing at Juniper Networks, and Ray Mota, CEO of ACG Research, discuss Juniper’s Converged Supercore announcement, which includes new custom silicon, updates to the PTX Series router and expanded SDN capabilities. Juniper has positioned itself as a thought leader in the service provider routing space, not only by addressing higher capacity requirements, but by also focusing on automation and SDN programmability to enable networks to be more agile and risk adverse. Listen to how the MX and PTX Series together change the router landscape by addressing service router requirements in the edge and transit router requirements in the core, as well as how customers can maximize cost optimization and service delivery.

Click for more information about ACG’s HotSeat videos.

rmota@acgcc.com
www.acgcc.com

Monday, March 23, 2015

Is Tomorrow’s Cloud Operations Manager a Highly Specialized Real Estate Broker?

As the world gets driven more and more by cloud-based services, what do tomorrow’s operations jobs look like? A decade and more ago ops managers were blue chip contractors, assembling custom-tuned components into environments a well-known set of visitors could use for a prescribed set of tasks. In tomorrow’s cloud-based world the picture that’s emerging is one in which a much larger and more diverse set of visitors needs to be accommodated for purposes that vary widely depending on when and why they show up. Their expectation is that the cloud infrastructure makes a wide range of capabilities available when they need it, and that the underlying platform will be dynamically allocated to simply make it possible at that time. In this sense the new operations manager has to be aware of the capabilities of a variety of ‘venues’ (three-tiered applications, web-scale apps, elastic storage pools, etc.) and ready to let them out for exactly what the renter needs, now. The mix is larger. The versatility of functions is greater. And the client mix is constantly expanding.

In this way the operations manager of the future is partly an expert realtor who maintains a pool of properties ready to be leveraged for what each client needs, ready to be reallocated to the next one when the first one is done. The realtor gets known for the quality of the properties that are offered. And the clients get referred because the promptness of service and the versatility to support their many distinct needs has been shown. The realtor simply has to ensure the range of properties on offer continues to be value to the clients who may want to visit.

For more information about ACG’s SDN services, contact sales@acgcc.com.

Click here for more information about Paul Parker-Johnson.


Paul Parker-Johnson
acgcc.com 

Monday, February 23, 2015

Making the Business Case: Network Analytics for the New IP

An analytics offloading use case conducted by ACG Research compares the total cost of ownership of Brocade’s architecture with two PMO alternative architectures. The Brocade architecture has 23 percent to 33 percent lower TCO than the PMO alternatives. Brocade’s advantage is due to its use of virtual network functions hosted on virtual machines and the agility and elasticity achieved though Brocade’s orchestration system. A network monitoring and customer experience management use case compares the TCO of Brocade’s virtual architecture to an appliance-based architecture (PMO) and finds a 43 percent TCO savings for the Brocade architecture.


For more information about ACG's business case analysis services contact info@acgcc.com.


mkennedy@acgcc.com
www.acgcc.com

Wednesday, February 18, 2015

Worldwide Carrier Routing and Switch Market Posted Increases in 4Q

The Worldwide Carrier Routing and Switch market increased year over year q-q 1.5 percent and slightly increased 0.1 percent y-y, with revenues of $2.9 billion. The core routing segment posted revenues of $563 million, increasing 4.8 percent q-q but down 6.9 percent y-y. The edge/switching segment posted increased revenue of $2.3 billion, up 0.7 percent q-q and up 1.9 percent y-y. 

In 4Q14, the EMEA region increased revenue a solid 6.1 percent, and APAC grew revenue 4.7 percent. The Americas posted a decrease of 2.7 percent. 

Disruptive IT market trends continue to challenge the capabilities of networks and propel providers to consider software-defined networking as a vehicle to reduce service delivery costs and increase service velocity. This trend has affected the router and switch markets, resulting in limited spend in router and switch as carriers continue to explore SDN, trial SDN or implement SDN. The fourth quarter is usually an indicator for the coming year. 

TREND and DRIVER HIGHLIGHTS

Carriers’ ARPU is not sustainable and cannot maintain capex over revenues. Some carriers feel that flat revenue is acceptable; however, they do not seem to recognize that flat revenue is a race to the bottom. With capex the problem is not spending; it is about innovation, agility and operational costs and being able to compete more aggressively on deploying services. Explaining the repercussions of flat ARPU and exorbitant revenues ratios of ARUPs to an executive and any SPs with a “wait and see” position is going to be a challenge. Companies must understand that changing mindset is a top-level approach. 

Service providers are making significant investments, and companies such as AT&T, Verizon, Sprint, and T-Mobile are actually seeing solid profits. Sprint, which was late to market, posted profits in the 20 percent to 30 percent range. Verizon posted profits in the high 40 percent to 50s percent range. Most vendors saw decreased revenue in Q4, which can be attributed to the special promotions or end-of-year give-a-ways impacting their profit margins between 5–10 percent. 

Wireless is still a priority because of the revenue it is generating. Carriers’ aggregated ARPU for fixed data is flat. Fixed voice ARPU is starting to decrease. Mobile voice is also decreasing. From an aggregated perspective mobile data is flat. Although some carriers report profit margins most worldwide carriers (67) report that ARPU is flattening or decreasing. 

ACG is projecting the following in capex spending for 2015:
North America  -3%
Latin America  -4%
EMEA         +1.3%
APAC         -5%
China         +6%

2014 has been an interesting year for carrier routing, which has been affected by shifts in capex spending in wireline, mobile, SDN, and NFV. Operators are focused on monetizing their increasing data traffic, which is driving demand for mobile broadband. The need for more control of the network has produced more options available at the higher layers, such as software programmability and network analytics. This is where the long-term value is as hardware becomes simpler and more cost effective. New systems are being built on flexible platform architectures that are intelligent and open to enable programmability. With the creation and delivery of these intelligent platforms, developers and vendors can upgrade and share their systems rather than locking them down.

For information about ACG's router and switching services, contact sales@acgcc.com.



Tuesday, February 17, 2015

Delivering Policy Continuity at Scale in Cloud IT and Managed Network Services

Markets have been busy recently with announcements of solutions to help service providers benefit from powerful innovations in SDN, NFV and cloud computing systems. Solutions are emerging for fixed and mobile network environments, and for business and consumer applications. Pockets of solutions are emerging to address one part or another of an operator’s end-to-end environment, for example, increasing elasticity in mobile packet cores, simplifying business customer premise (CPE) configurations, and instantiating VNFs dynamically into cloud-based IT services.

While progress in pockets is good, designers also have to keep in mind that customer experiences exist on an end-to-end basis, at each point of consumption and across the aggregated performance of each domain involved in the service. Indeed, by embracing the cloud-based paradigm we are pursuing a goal in which services–and the policies that control them–are dynamically managed across the collection of resources that support them.

At its highest level, this is a job for service-level orchestration, for platforms that ‘think’ about a service end-to-end. Domain-specific solutions that optimize for local requirements can be integrated into a total service using northbound plug-ins and APIs. In essence a new design challenge for SPs has emerged: to optimize the mosaic of new virtual elements while still achieving a high-quality operation. How efficient (or complicated) this is depends to a degree on how efficiently the ‘gold vein’ of consistent service policies can be deployed into an end-to-end path at scale. How well an SP can do this will affect both quality of experience for the customer as well as total cost of ownership and return on investment for the SP.

One approach to mastering this challenge is to build using solutions that employ a consistent framework for managing policies across multiple domains, such as end-user CPE, wide area networks, and cloud computing data centers. The overall goal could be approached by focusing on key building blocks of the end-to-end service environment and managing its policies consistently, thereby getting a start on the overall goal. For example, managing networking resources consistently would be one way of achieving continuity at scale, at least for the network underpinning user applications. This approach requires a policy management system that aligns the network ‘northbound’ consistently with the operator’s requirements and propagates policies for enforcing those requirements in a scalable manner to each virtual element that is deployed in multiple domains.
This is an ambitious, some might say, lofty goal. Yet realizing the goal of delivering services for many individual customers on demand and at scale and with consistently orchestrated quality requires just such a far-reaching implementation.

Of the solutions that have arrived to market recently, one that embodies these attributes well is Nuage Networks’ virtualized networking portfolio. Nuage’s VNS solution (Virtualized Network Services for distributed enterprise sites) and VSP (Virtualized Services Platform for cloud-based data center services) use a common policy manager, the Virtualized Services Directory (VSD), to orchestrate policies across all of its domains. At the same time, VSD uses a consistent northbound interface to orchestrators such as OpenStack and CloudStack-based platforms. With this versatility and scale, Nuage is realizing the goal of managing an operator’s policies efficiently, on demand, and at scale to a widely distributed set of resources.

Thus, while it is possible to start transitioning infrastructures to virtualized designs one domain at a time, it is also possible to build on an architecture that consistently spans multiple domains on an end-to-end basis. In this way, an operators may simultaneously increase efficiency and increase the quality of customers’ experiences. In doing so, they would measurably accelerate their progress to delivering cloud-based services on demand across an entirely virtualized service delivery infrastructure with consistent end-to-end policy control.


For more information about Paul Parker-Johnson click here.

For more information about ACG's SDN services, click here.


Paul Parker-Johnson
acgcc.com 

Wednesday, February 11, 2015

Business Process Redesign Is Essential to NFV/SDN Success

Leading telecom operators began the network function virtualization initiative several years ago in recognition of the need to reduce cost increases and increase revenue growth rates to sustain profitability. While much technical process on NFV and related SDN technology has been made, I believe business process redesign is needed to change the organization and people's jobs if the financial benefits are to be realized. 


mkennedy@acgresearch.net
www.acgresearch

New SDN Apps Bring a More Open Lens to the Future of Network Operations

Some vendors are starting to leverage a truly open architecture for optimization of unified fabrics with extensible service control applications.

One of the great opportunities in software-defined networking is to amplify the efficiency of network and service operations teams by allowing them to leverage a powerful set of logically centralized and abstracted control functions for the infrastructures and services they manage.

While this model is simple to articulate it takes great vision and talent to realize in the world of real, deployed solutions that deliver the result.

The goal is only partially realized by the use of SDN controllers themselves. Controllers indeed do help simplify by normalizing and abstracting control plane functions for the given domain. In parallel, though, operators are driving to achieve additional optimizations, efficiencies, and innovations by leveraging what I call SDN Service Control applications that work in tandem with the centralized SDN controller code. Examples of focus for these include traffic analytics, service level monitoring and management, and custom traffic steering design for various operating goals (application performance, service availability, cost optimization, etc.).

The dynamics for how these goals can be pursued vary a bit between internal data center and adjacent wide area network infrastructures. I focus on data center implementations here.

The end game we’re looking at is one where the logically centralized and streamlined controls for the network being managed dynamically serve the needs of the applications and users relying on it for their services. In many data centers this will include a sizable overlay virtual network running in parallel with a high-performance physical underlay network. It will include a blend of control plane and value-adding service control apps to make it all work automatically and with maximum performance, efficiency, security, and stakeholder satisfaction (phew!).

A challenge in getting to this end game is achieving these results in a streamlined, integrated manner for both underlay and overlay networks. As implementing SDN in data center environments has gotten started, we’ve largely had operationally separate deployments of underlay and overlay networks. Services such as VXLAN and virtualized router modules are operating in their own logical scopes, and a sometimes heterogeneous fabric of underlying physical network nodes is implementing its own L2 and L3 functions in parallel. Each piece can do its part on its own, but it doesn’t create an especially streamlined operational model.

Some amount of overlay and underlay integration has occurred. From the open networking point of view, a number of OpenFlow controllers have started to bring a degree of integration of underlay switches with a range of centralized control plane functions. And in a proprietary context, Cisco’s ACI framework and APIC service control system have brought a range of application policy controls to both overlay and underlay network infrastructures—the only glitch from an optimization point of view is it’s not being implemented on a fully open platform.

Neither of these early stage developments has brought a design that unlocks the potential of the open network control environment of SDN with the power of value-add that can be obtained from service control applications running in parallel with the SDN controller that have the ability to optimize both the virtual and the physical network environments according to the operator’s service delivery requirements. Most SDN controllers delivered to date open up control of either a virtual overlay or a physical underlay but not both. And while the APIC is logically elegant within its own technological silo, it’s not opening up the opportunity for streamlining to the same extent—across a heterogeneous SDN infrastructure—as a solution leveraging, say, and Open Daylight-based set of network control plane functions could.

A glimpse into a more open framework for streamlining whole data center networking fabrics has started to appear in a set of recently introduced SDN service control applications from Big Switch and Brocade. Each has the attribute of bringing a distinct set of added value to managing a data center’s SDN deployment, while leveraging the abstraction of the SDN controller as a means of streamlining the deployment of the application’s work. In this manner they have the potential of leveraging the versatility and openness of the SDN control plane for implementation of the service controls they are generating in either a virtual or a physical deployment or both.

Simplifying analytics, traffic engineering, and application policy controls in this way brings an order of magnitude increase in the level of efficiency that an operations and service management team can achieve toward the services they are managing.


Big Switch’s Fabric Analytics module and Brocade’s Volumetric Traffic Management and Path Explorer applications are each pursuing this path. Examples of implementations approaching this design have been developed in wide-area or transport SDN solutions such as Cisco’s WAE and NCS solutions and Ciena’s recently introduced Agility software suite. But in the data center the Big Switch and Brocade applications are early entrants in the market that are starting to leverage a truly open architecture for optimization of unified fabrics with extensible service control applications. Whether additional similar applications arrive in the market using a similar model in the near future will be interesting to see. But in the meantime, kudos to both suppliers for advancing the state of the art in managing open data center fabrics with the versatility and extensibility of their designs.

For more information about ACG's SDN services, contact sales@acgcc.com.


Paul Parker-Johnson
ACGcc.com 

Friday, February 6, 2015

ACG Research Announces SDN Data Center Research Service

ACG’s data center SDN research explores the key use cases and platform categories SPs are using to enhance their data centers with SDN. These include control plane software running in SDN controllers alongside applications that extend services intelligence with other improvements like SLA monitoring and automatic workload placement optimizing. 

ACG examines overlay virtual networks used in SP SDN data centers, and analyzes the nuances of white box and hybrid physical network nodes so central to how well SPs will realize their efficiency and innovation goals. ACG’s analysis evaluates these platforms in use cases from multitenant cloud to web-scale applications to cross-domain network services, and considers which architectural alternatives and vendor solution offerings have the greatest promise for success in these deployments. 


For more information about Paul Parker-Johnson, click here. 


Paul Parker-Johnson
ACGcc.com 

Thursday, September 18, 2014

Infinera’s Cloud Xpress: Impressive Contribution to Cloud Providers’ DCI

Growth of cloud-based services shows no real signs of slowing down. This adoption rate is propelling providers of cloud services to construct new data center capacity, work to make data centers they already have run more efficiently and improve how they network their data centers internally.

In early adoption phases of cloud, there have been two dominant uses of data center interconnection (DCI). First is for connecting enterprise data centers to service providers’ data centers for hybrid and public cloud computing services.  The second use has been to connect providers’ ecosystem partner data centers to SPs’ data centers to mash up applications and federate cloud services.

As usage has grown, though, a new set of DCI requirements has emerged. These involve connecting providers’ own data centers at very high capacities. Two scenarios dominate this trend. The first is in metro or nearby data center connections, and the second is in hyper-scale data centers deployed at great distances from other sites and running at remarkable scale.

In the first use case operators will run out of power or space in existing sites and need to create additional capacity nearby. This can be in a metro area footprint or in an extended campus. DCI is critical in these deployments because many cloud applications work in a highly distributed model. They often need access to resources in neighboring data centers many times over before responding to a single user’s request. Thus, interconnections need to be simple and fast.

In the second deployment scenario, hyper-scale operators such as Google, Facebook and Microsoft search for remote locations where land and power are less expensive and build some of the world’s largest data centers there to run their services. Server counts in these sites range from 200,000 to 500,000 or more. The need for integration with systems in the providers’ other data centers is strong in mega-site deployments as well. This leads to extremely large capacities of DCI bandwidth being deployed both locally in clustered DC locations as well as over long haul transport for sites that are a half a continent or more away.

DCI capacities required in the intra-provider configurations range from 10s of tb/s in medium-to-large scale sites to several hundred tb/s in the largest mega-center locations. Because of the ongoing growth in the use of providers’ services, the unique needs of these DCI deployments have led to the emergence of a new type of high-capacity DCI solution.

Five requirements define the new breed:
  • Efficient and flexible scaling to 100s of tb/s of transport
  • Compact, rackable form factors
  • Low power consumption
  • Simple operation
  • Programmability for integration with service automation 

Underpinnings of these requirements
A dominant aspect of cloud data centers is use of infrastructure such as servers and storage systems that are modest in unit size but able to be pooled in wide ranges of capacity to serve the needs of application or service. This leads to a bias for systems installable in compact, rackable form factors that are easy to install and expand, often leveraging auto-configuration for integration into infrastructures at very large scale.

Form factor compactness demands low power consumption. If an individual server consumes, say, 150 watts in ongoing use, a rack of 40 such servers might consume 6 kilowatts, sustained. A data center with 100,000 such servers might consume 15 megawatts (approximately estimated). It’s easy to understand why cloud providers focus on wringing every possible watt out of solutions they deploy. DCI platforms designed in a more server-like package (versus a telco office orientation) are likely to consume less power, perhaps drawing a third less power per rack than alternatives. Across 10 racks’ worth of devices, if 150-200 kilowatts of power can be saved, a solution is heading in the right direction.

A final objective that fits with the ability to pool resources goal is to support open, programmable software for DCI capacity to be dynamically provisioned according to application needs. A variety of approaches can be taken to achieve this, including plug-ins for service control software rapidly evolving for use in cloud and virtual networking infrastructures as well as API toolkits to let large cloud providers integrate with their own service management platforms. In the end, programmability to support adaptation to providers’ goals for resiliency, path allocation, and application-driven solutions are the key requirements.

This new breed of DCI solution will complement other transport solutions that implement shared network transport of various types in metro and long haul configurations. The two styles will be used by providers for different types of connections. Both will be used to support higher level service requirements for customer, partner, and internal operator data center connections.

The Cloud Xpress family introduced by Infinera is an innovative example of the kind of high capacity, small form factor, programmable DCI platform cloud operators are leaning toward for their internal DCI deployments. Cloud Xpress is initially targeted for metro deployments. Leveraging optical innovations Infinera has previously introduced and engineering them into a platform capable of 20+ tb/s in a single rack, Cloud Xpress is an impressive contribution to the state of the DCI art. If trials prove out successfully, Cloud Xpress has every prospect of helping cloud operators scale out their data center deployments and interconnect them with the capacity and elasticity they desire.


For more information about ACG’s services, contact sales@acgresearch.net.


Paul Parker-Johnson

Metacloud Adds Versatility and Strength to Cisco’s InterCloud

Among the best promises of the cloud are flexibility in workload deployment and efficient, scalable orchestration of deployments regardless of location or underlying infrastructure. 

Cisco’s acquisition of Metacloud for integration into its InterCloud portfolio is an important step toward the InterCloud realizing these promises. Metacloud adds versatility and strength to the InterCloud service offering in at least three ways:

1. Metacloud’s innovative OpenStack as a Service solution allows businesses to deploy private clouds using OpenStack software without needing to invest in developing in-house OpenStack expertise (because their cloud is managed by Metacloud as a service).  This is a very powerful way to open up use of OpenStack software in business private clouds for companies that have not been ready to make that commitment to date. Although OpenStack is very appealing as a service delivery environment because of its rich open source community of technical contributors, it is still relatively young in terms of delivery packaging and integration options for adopters who do not have the resources to develop that expertise. Making the OpenStack environment available on an efficiently managed basis by Metacloud as the manager takes the sting out of adopting OpenStack for many businesses and allows them to concentrate fully on implementing the applications they’re interested in on a powerful open software base.

2. OpenStack as a Service, now from the InterCloud, can be deployed on top of infrastructures other than Cisco’s, in addition to being deployable on Cisco infrastructure systems (such as UCS and Nexus). This opens up access to the InterCloud ecosystem for customers without having to meet the criterion of running on Cisco underlying hardware in every case. In its truest sense, that is a crucial criterion for a serious cloud computing framework to meet: by being able to instantiate virtual compute, network, storage, and related applications in a truly open software environment without regard to specific underlying hardware implementations (other than that they integrate successfully into the OpenStack software framework) the flexibility of adoption paths available to customers for engaging with the InterCloud ecosystem of operators and application suppliers is multiplied by an order of magnitude. It doesn’t prevent the use of parallel ACI-based Cisco infrastructure systems. Rather, it opens up the option of using additional infrastructure environments quickly and efficiently by introducing the managed OpenStack as a Service framework.

3. By bringing a managed OpenStack solution to its InterCloud portfolio in support of private clouds, Cisco is laying the groundwork for extending the InterCloud’s services based on OpenStack to include hybrid and public services leveraging the OpenStack technology base. Making this additional implementation option available to end customers significantly enhances the versatility and appeal of the ecosystem it is developing. 

Time will tell how seamless and robust the OpenStack additions to the InterCloud portfolio will be. Customers will decide. However, if one were looking for signs that the InterCloud fabric might have the versatility and flexibility in deployment options the cloud computing community so highly values, the Metacloud acquisition would appear to be a compelling signal heading in that direction.

For more information about ACG's SDN services, contact sales@acgresearch.net.


Paul Parker-Johnson

Tuesday, January 15, 2013

Join ACG Research at the SDN Precon at ITEXPO Miami


Software-defined networking is considered by many to be one of the most important and potentially disruptive developments in networking since the rise of the Internet. To date, networks and connectivity have come first, and applications have followed. SDN turns this model on its head, approaching networking from an apps-first standpoint. In this SDN preconference at ITEXPO Miami, we (including ACG Research’s Eve Griliches, optical analyst) will:
  • Define SDN
  • Look at the technologies and components involved in SDN
  • Review the use cases of SDN
  • Identify the players involved in moving SDN forward
  • Discuss what this all means for networking as we know it

For more information about this event, visit: http://www.sdnzone.com/conference/

For more information about Eve Griliches, click here.




egriliches@acgresearch.net 
www.acgresearch
 

Wednesday, December 12, 2012

SDN Business Models: Which Will Succeed?

As I see more and more companies enter the software-defined network (SDN) market, my hardware-centric mind struggles to understand the business models of many of these software offerings. After talking to industry experts I have come up with four basic models:

1. Embedded Model. This model is hardware based. System vendors will likely throw in the controller and open APIs for free and price the hardware accordingly; the hardware covers the cost of the software development. This technically obscures the software solution within the hardware price. Benefits of this business approach is that the hardware stays in the network a long time, and additional add-on software features and/or applications and upgrades can be sold at increasing profits. This model will be used by key networking infrastructure vendors as well as SDN start-ups that have hardware-based solutions wrapped together with the controller and applications. This model is likely to be the most successful in the long run, because end users are leaning toward a full software and hardware package versus piecing the components together themselves.


2. Cloud-Based or Application Hosting Model. This model is per virtual machine (VM) and is time based, similar to the Amazon usage-based billing system. Use a number of VMs within a certain period, and the price scales with the usage. There is no tie to specific hardware. It may sound like a low-cost entry approach, but this is likely to be one of the most expensive models because the complexity to evaluate the year-end cost is quite difficult. Additionally, it is likely too expensive for the typical enterprise to embrace given large-scale virtualization deployments are in the very early stages. 

3. Subscription Based. The subscription-based model simplifies things a bit for the customer and enables either a quarterly or annual fee to be attached to the controller and applications purchased. The controller can be separate from the applications or bundled, enabling multiple offerings that are a single price. Upgrades can be priced by quarter or year, which enables up-selling of new applications in a very straightforward format.  

4. Capitalized Model. The capitalized model is where the customer purchases the controller (and/or applications) for a one-time price and capitalizes it over time. This is where you find out where the purchasing power is in the organization. Often the networking team will submit a VM or subscription-based proposal, and the CFO will insist on a one-time price instead.

Several of these business models, in theory, are compelling, but have become extremely complex for the end user to evaluate, specifically, determining what the end cost of the network will be. End users are telling us that the simpler the business model, the more likely the sale, given the CFO influence. Thus, the capitalized model, in many cases, is actually the most popular right now, despite what the market is telling you.

For more information about Eve Griliches, click here.

For more information about ACG Research's SDN services contact sales@acgresearch.net.



egriliches@acgresearch.net 
www.acgresearch
 


Wednesday, September 26, 2012

Europe's First SDN Knowledge Exchange


SDN World is a ground-breaking event addressing the rapidly emerging market of Software-Defined Networking.

Co-hosted by the Open Networking Foundation, this will be the first opportunity in Europe to discover and debate face-to-face the full potential of software defined networks. Join industry leaders, activists, pioneers and market-makers from key functions within the network ecosystem to define and shape the future network.

As delegates to Layer123's first Cloud-Net Summit heard, carriers are moving to define new architectures enabled by the potential of SDN and OpenFlow. This is a huge area of strategic and important debate across the industry.

Aimed principally at carrier and telecoms service provider professionals, but with great relevance to large-scale data centre users, such as large enterprise and content providers, SDN & OpenFlow World Congress is the first opportunity in Europe to meet all of the market-making organisations behind the OpenFlow standard and the development of the SDN industry.

Layer123 is inviting the leaders in the SDN movement from all parts of the industry ecosystem, software specialists, network systems vendors, service providers and carriers, datacentre providers and large enterprise, to Frankfurt this October.

Service and content providers, network and data centre operators and enterprise customers (no vendor organisations please) can gain access to this event free of registration fees, by agreeing to participate in the on-site knowledge exchange activities

Join us and add your experience to the first SDN & OpenFlow industry Knowledge Exchange. 

For more details go to the event website www.layer123.com/sdn.

Thursday, September 13, 2012

Use Cases Define Future Shape of Software Defined Networking


Software Defined Networking (SDN) began as a conceptual extension of data center virtualization and as such its true form has been tough to visualize. Now, as SDN use cases are being revealed on the web and in public forums, it is becoming clearer what SDN is, how it will be implemented and who will benefit or be hurt by its adoption. Read more: http://www.fiercetelecom.com/story/use-cases-define-future-shape-software-defined-networking/2012-09-11.

For more on SDN read Michael's FierceTelecom article  "Building a Case for Software Defined Networks for Metro Networks."  

Read Michael's interview with Carrier Ethernet News to get his thoughts on how SDN technology will make its way into CE networks and when. Click here to read the complete interview. 

For more information about ACG Research's SDN syndicated and consulting services contact sales@acgresearch.net




Michael Kennedy
mkennedy@acgresearch.net
www.acgresearch

Thursday, August 2, 2012

Take Five with Michael Kennedy

Michael Kennedy, principal analyst for ACG Research, worked with the Metro Ethernet Forum when the group was founded. Carrier Ethernet News recently interviewed Michael to get his thoughts on how Software Defined Network technology will make its way into Carrier Ethernet networks and when.  


For more on SDN read Michael's FierceTelecom article "Building a Case for Software Defined Networks for Metro Networks."





Michael Kennedy
mkennedy@acgresearch.net
www.acgresearch

Wednesday, July 11, 2012

Building the Case for Software Defined Networking for Metro Networks


In his FierceTelecom article, Michael Kennedy discusses software defined networks (SDN) and metro network virtualization efforts and how service providers can utilize SDN architecture in their metro networks to reduce OpEx and CapEx and increase service velocity. Click to read the article.

Click for more information about ACG Research's business case analysis service or contact sales@acgresearch.net.






Michael Kennedy
mkennedy@acgresearch.net
www.acgresearch