Resultados 1 a 3 de 3
  1. #1
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    18,473

    [EN] HPE kills off its entire OpenSDN line, effective immediately

    HPE will no longer support the networking platform it has for years pitched as a solution for ISPs and IT service providers.

    Shaun Nichols
    26 Apr 2017


    Its sales staff have been instructed to shut down customer demos and proof-of-concept installations. IT buyers will be told to try other gear if they want to evaluate and roll out software-defined networking.

    HPE workers have also been instructed to pretty much keep the move a secret, with no public announcements, and to simply tell customers and partners the tech giant has "discontinued development of HPE OpenSDN" if they ask what's happening.

    This is according to an internal memo seen today by The Register, which declares HPE will no longer support the networking platform it has for years pitched as a solution for ISPs and IT service providers.

    The email was written by product veep Sarwar Raza and telco sales boss Jacques Rames, who said the decision to pull the plug was "made in light of business and financial considerations."

    The pair also confirmed HPE is getting out of the telco-scale SDN market entirely, admitting that it "will no longer offer a native telco/service provider SDN solution." The enterprise giant notes, however, that the move should not be considered a step away from open platforms.

    The products set to be axed, we understand, include the OpenSDN controller, VPN, and SFC lines. HPE is telling sales staff it will no longer be taking orders for the products or fulfilling orders.

    "Alternative options to HPE OpenSDN include the HPE Distributed Cloud Networking (DCN) products from DCIG networking," the missive reads. "Please note that these products are not perfect substitutes for each other, so you may have to requalify open opportunities based on DCN features."

    The Register asked HPE for comment. A spokesperson would not deny the memo had been sent, and said someone would get back to us with a statement. That was about an hour and half ago, and our inbox is still empty.

    So while we wait, here is the internal notice, including an FAQ for staff, in full:

    Sarwar Raza VP Product Management, Communications Solutions Business Jacques Rames WW Global Industries Communications, Media and Entertainment SDN/NFV Sales

    HPE is advising our sales teams of the End of Sale of the HPE OpenSDN family of solutions, effective immediately. This includes HPE OpenSDN 1.0 Data Center Networking Controller, HPE OpenSDN SD-VPN solution and the HPE OpenSDN SFC solution. Product and service SKUs from these product families are no longer available for order or fulfillment. There are no follow-on releases planned for HPE OpenSDN solutions.

    Why this notification?

    HPE will no longer offer a native telco/service provider SDN solution. We will rely on partners for this capability instead. This decision is made in light of business and financial considerations.

    Will there be an external announcement?

    HPE is not planning any external announcement regarding this change. Communication with affected customers will be coordinated via Account Teams.

    What do we tell industry media and analysts?

    Direct questions to Julia Ochinero.

    What do we tell customers?

    Do not offer any proactive statements to customers. If asked, please share that HPE has discontinued development of HPE OpenSDN and now offers partner solutions in its place. All customer communication must be coordinated via Account Teams.

    What do we tell partners?
    The Worldwide Partner Team is notifying affected partners. All current partner integration activities with HPE OpenSDN will be stopped. If asked, please share that HPE has discontinued development of HPE OpenSDN.

    What alternatives are available?

    Alternative options to HPE OpenSDN include the HPE Distributed Cloud Networking (DCN) products from DCIG Networking. Please note that these products are not perfect substitutes for each other, so you may have to requalify open opportunities based on DCN features.

    My customer is currently running a demo or POC. What are the next steps in light of this advisory?

    All OpenSDN specific POC/Demos will need to be wound down in coordination with the Account Team. We are in the final stages of finalizing and submitting binding bids that include OpenSDN solutions.

    What are our options?

    All current POCs are being reviewed to understand if they are strategic and if we have the opportunity to transfer to a partner to continue the engagement. All OpenSDN specific POC/Demos will need to be wound down in coordination with the Account Team.

    My customer requires an open source based or lightweight SDN solution. What are my options?

    Please refer any such opportunities to Product Management for review in order to determine if any part of our OpenSDN expertise is leverage-able as a potential services offering. Note however that there is no continued product offering in this space.

    Does this signal a move away from Open Source solutions?

    HPE continues to lead the OPNFV open source NFV community and has made significant contributions to major open source projects over the last several years. Our decision is not based on merits or otherwise of open source vs proprietary solutions. HPE continues to support open, standards based solutions as well as best of breed partner solutions depending on specific customer needs.

    Our customer may require a written explanation of our decision. Where can I obtain this?

    Do not forward or re-purpose any part of internal communications for customers. Contact Sarwar if you need a customer-specific statement.

    If you have more information to share, please get in touch with us in confidence via email – or anonymously and securely via Ricochet. Our US office can be contacted using ricochet:m3bnxucau5ishl2h.

    https://www.theregister.co.uk/2017/0..._opensdn_line/

  2. #2
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    18,473

    AT&T Brews In-House SD-WAN

    Wyatt Carlson
    April 26, 2017

    AT&T CEO Randall Stephenson mentioned on the company’s earnings call yesterday that it’s in the process of developing its own software-defined wide area networking (SD-WAN) capabilities. Although he didn’t mention VeloCloud on the call, the vendor did confirm to SDxCentral that AT&T continues to work with it on SD-WAN.

    According to a Seeking Alpha transcript of yesterday’s call, Stephenson said, “On the SD-WAN, yeah, it’s real. It tends to be real down-market…and you should assume that we’re developing the capability ourselves, because it’s a viable offer down-market. We’re seeing some effect from it. It’s not material yet, but we think it’s a legitimate capability. We need to be there; we need to have it. And so up-market, the traditional VPN capability is always, we think, is going to be the enduring capability. But down-market, we’re going to have to be prepared to compete with this kind of offering.”

    The “up-market” refers to large enterprises, for which AT&T offers traditional VPN, via MPLS connections. The “down-market” refers to small-to-midsized businesses (SMBs), which is where AT&T is really going to have to expand its SD-WAN capabilities.

    To help fill in this gap, AT&T will be leveraging an existing partnership with VeloCloud that it announced in October 2016, according to a VeloCloud spokesperson in an email to SDxCentral. In October, the service provider announced it had picked VeloCloud to deliver SD-WAN over multiple types of network connections. AT&T said it would deliver two types of SD-WAN: a network-based system and an on-premises-based system.

    A network-based system could build off a customer’s existing MPLS connections. With the on-premises-based system, customers don’t necessarily need an AT&T MPLS connection. They can use SD-WAN to manage their various wired and wireless Internet connections from third parties.

    “For SD-WAN solutions, AT&T is the first provider in the industry to announce both an over-the-top solution as well as a network-based SD-WAN solution, which couples smart SD-WAN CPE with a smart MPLS network,” wrote the VeloCloud spokesperson. “A typical SD-WAN solution is deployed in an over-the-top manner, i.e., SD-WAN CPE is deployed at every customer site, and tunnels are established over the network transport links among sites.”

    https://www.sdxcentral.com/articles/...-help/2017/04/

  3. #3
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    18,473

    HPE Closes the Door on OpenSDN

    The culling of OpenSDN isn't an encouraging sign for the blending of open source and telecom.

    Craig Matsumoto
    4/27/2017

    One of the earliest entrants in software-defined networking (SDN) has met its demise, as Hewlett Packard Enterprise (HPE) is shutting down its OpenSDN product family, a descendant of the SDN controller built by ConteXtream.

    "HPE has discontinued development of OpenSDN and offers partner solutions in its place," a Hewlett Packard Enterprise spokesperson writes in an email. "We continue to invest and participate in relevant open source efforts to provide industry leadership and acceptance. Our mission has always been to be partner-centric and provide customers with choice and open systems. We continue on that path."

    The Register first reported the news Wednesday night, citing an internal memo declaring End of Life status for OpenSDN.

    Quoting part of the memo as published by The Register: "HPE will no longer offer a native telco/service provider SDN solution. We will rely on partners for this capability instead. This decision is made in light of business and financial considerations."

    The memo goes on to say that HPE was planning no external announcements about the move.

    OpenSDN pertains specifically to the service provider market. "I'm not believing this is spilling over into the data center side of SDN," says Cliff Grossner, an analyst with IHS Markit.

    The company still has its VAN SDN controller for enterprise and campus networks, and Distributed Cloud Networking (DCN) for data centers. The HPE memo quoted by The Register notes that DCN and OpenSDN "are not perfect substitutes for each other."

    While HPE stresses that the decision had nothing to do with the nature of open source software, the culling of OpenSDN isn't an encouraging sign for the blending of open source and telecom. (See Time for a Telecom Reboot.)

    But OpenSDN's downfall seems to have more to do with SDN market starting to settle out, with ACI from Cisco Systems Inc. and NSX from VMware Inc. emerging as two of the predominate options.

    It could also be considered a reflection of HPE's own struggles with the carrier market. In the case of NFV, the company lost its role as the lead vendor in a Telefónica deployment, and Light Reading reported in October that the company was having trouble delivering to Swisscom. (See Telefónica Ditches HPE as Virtualization Lead and HPE Fails to Deliver at Swisscom – Sources.)

    "As a primary integrator, I don't think HPE was leading many projects," Grossner says. "For them, I think that investment to continue versus the return wasn't there. They're placing other bets."

    Grossner also wonders if the spinoff of HPE's services business (a spin-merger with CSC) might have helped prod the decision to back out of OpenSDN and the proofs-of-concept (PoC) it was involved in. "Service providers expect quite a few years of investment from the vendor before there's any revenue," he says.

    OpenSDN originated with ConteXtream, a startup whose birth in 2006 predates SDN. Back then, the rage was around the Grid, and ConteXtream envisioned doing BitTorrent-like things there. (See Grid Startup Takes to the Data Center.)

    ConteXtream eventually turned its attention to SDN instead. Most of the early attention in SDN was on data centers and the enterprise, but ConteXtream -- like Contrail Systems, which was eventually acquired by Juniper Networks Inc. -- chose to focus on service providers, with ConteXtream putting particular emphasis on wireless operators. (See ConteXtream Claims a Carrier SDN Coup.)

    ConteXtream also laid claim to having one of the first commercial SDN controllers to use code from the open source OpenDaylight Project. Hewlett-Packard Co. acquired the company in 2015 for an undisclosed sum. (See HP Acquiring ConteXtream for Carrier SDN.)

    http://www.lightreading.com/carrier-.../d/d-id/732388

Permissões de Postagem

  • Você não pode iniciar novos tópicos
  • Você não pode enviar respostas
  • Você não pode enviar anexos
  • Você não pode editar suas mensagens
  •