Build VS Purchase: Does the vendor meet the needs of cloud providers?

The cloud service market is growing rapidly, but some cloud providers say their vendors cannot keep up with the needs of service providers.

In general, building and purchasing are quite common. It is not a shame for many service providers, especially those who do research and development resources themselves. Self-developed technologies are a kind of innovative and different resources. But some providers say they are forced to do more simple development in the enterprise, because the vendors do not meet their requirements for cloud hardware and software.

"If you cannot develop many intellectual property rights for building, operating, and managing the cloud on your own, you will never be able to maintain a long-term competitive advantage, because it is very simple that there are no commercial tools available to meet this demand, "Jeff Deacon said he is the chief cloud strategist at Miami Terremark." No one tries to tell you that different people are not using the business and are trying to run on the public cloud."

Over the past year, telecom operators are increasingly dissatisfied with the vendor's monetization strategy, including products that support cloud services. He said he is the president of CIMI. Over the past few years, Nolle has asked telecom operators how well manufacturers can support them in this particular field. They can choose to be satisfied, satisfied, neutral, less satisfied, or not satisfied.

"Five years ago, most of the respondents lingers on the neutral layer. What happened? It keeps them so passive that they know that all the surveys were completed in March, only one of the 47 carriers chose to be neutral, "Nolle said." year by year, it is getting worse and worse."

Building vs. purchasing: Technical Considerations

Cloud providers prefer building rather than purchasing, mainly because of the vendor's technical and cost-related dependencies. According to Deacon, he is a participant in the Carrier Cloud Forum service provider, the Carrier Cloud Forum (Carrier Cloud Forum) is a provider seminar unit of Interop 2012 in New York.

Some vendors have basically failed to build cloud products at the partner level. Deacon said: "commercial software is out of the service provider (OSS ), BSS and even hypervisor and hypervisor management tools are not extended, "he said. "They are designed for enterprises but sold to operators ."

Douglas Smith is the Chief Information Security Officer and VP of the NTT U.S. IT system. He did not complain about the vendor, but admitted that the operating support system and business support system products need to be updated to support cloud providers. During the discussion on OSS/BSS on the telecom operator cloud Forum, Smith said he hoped that the vendor would be able to process the cloud with a higher focus on software-oriented architecture.

"The OSS systems we used were designed and released 20 to 30 years ago, and they were doing well under that challenge. But unfortunately, technology and the market are moving forward, "Smith said." One of the keys is to reuse components, but they have also created these general components, this flexibility does not exist in the systems built in the past. They are built to solve yesterday's scenario ."

Major hardware vendors have not made any better progress in cloud provider products. As the operator said, manufacturers seem to be more concerned with and pleasing shareholders, rather than continuing to solve technical problems, Nolle said. Network vendors seem to have given up in particular. They are mainly enough to focus on next-generation network technologies, such as software defined networks (SDN), he added.

"When the operator asked the vendor about the cloud strategy, the vendor said," Yes, we are in progress. But how many boxes can my colleagues put in? '"Nolle said," The operator feels that the vendor is so opportunistic to push forward his/her financial goals, which make the vendor forget that while complying with their own goals, they are asking operators to compromise with them."

Juniper Networks recently announced two new telecom carrier-level routers added to its MX series products, MX 210 and MX 220, and boast that the latter can be expanded to 80 Tbps in a single rack. However, Juniper emphasizes that MX210 and 220 are not a larger box.

Both products contain a lot of software-based performance to support cloud services, says Wendy Cartee, vice president of Juniper market. The vro supports the MX Virtual Chassis of JunosV App Engine and Juniper. These two virtualization platforms collaborate to promote service delivery, service creation, and network management. This vro also supports Path Computation Element, which can be used for Automated Traffic Engineering in SDN.

"We believe that in addition to capacity and performance, it is also important to provide these software features," Cartee said. "That's why we introduced these breakthrough features, however, only software services are provided."