Today, HP Launches Industry’s Most Complete Software-defined Network Fabric for Cloud. This network fabric is built on HP FlexNetwork architecture, enabling business agility for clients by delivering two times greater scalability and 75 percent less complexity over current network fabrics while reducing network provisioning time from months to minutes.
This is possible by:
- Improving IT productivity by unifying the virtual and physical fabric with new HP FlexFabric Virtual Switch 5900v software, which, in conjunction with the HP FlexFabric 5900 physical switch, delivers advanced networking functionalities such as policies and quality of service to a VMware environment. Integrated Virtual Ethernet Port Aggregator (VEPA) technology provides clear separation between server and network administrations to deliver operational simplicity.
- Reducing data center footprint with the HP Virtualized Services Router (VSR), which allows services to be delivered on a virtual machine (VM), eliminating unnecessary hardware, by leveraging the industry's first carrier-class software-based Network Function Virtualization (NFV).
As organizations move to software defined networks, some fundamental changes in the approach will be required and these products are a start down that path. Here is a video with a bit more high level discussion and some details:
I wrote a post about what a technologists can do to be relevant a while back and at the time I thought that a list like this would be relatively transient. It turns out that unlike buzzwords, the underlying technologies are usually here for the long haul -- just ask a COBOL programmer. The half-life of the experience is likely much longer than I thought.
I was in a discussion today where we talked about a list of experiences a technologist needs to have in order to talk with some degree of authority about the next big thing in an enterprise context. Naturally, a person can’t know everything to the same level of depth, but there is a basic, useful level for every strategic technologist to have.
Some of the obvious ones I’ve mentioned before were:
- Install a public cloud-based virtual machine and use it for something
- Write an application for a mobile device and get the app listed in the app store
- Take an on-line class (or maybe a couple every year) through a tool like coursera
A couple of those items would have been as applicable 2-3 years ago as they are today. Some have changed quite radically in their capability in that timeframe. I’ve done each of them at least twice for one reason or another and each time I learned something new.
If I were to add a new one that I haven’t touched in a very long time, it would likely be something to do analytics. There is a bit of a problem with this one though, since having enough data to do something useful and interesting may be tough.
I mentioned I was going to experiment with 3D printing. I now need to find something in the Internet-of-Things space as well.
I’ve probably looked at all these things enough to understand what their good for, but actually tackling a project brings that perspective to a whole other level. The hands-on experience doesn’t need to be production ready quality, since the goal is as much generating the exposure to the issues and ideas as it is solving a particular problem.
What other areas should a technologist tackle? And how? I haven’t even mentioned anything in the networking space. Anyone who has looked under the covers of Software Defined Networks probably knows the depth of impact changes in this space will have for the future.
The book Outliers talked about spending 10,000 hours on an area to become great. I wonder how tackling 400 technology domain experiences allows you to be successful - that’s 10 a year for 40 years.
The HP Moonshot System is leap forward in infrastructure design that addresses the speed, scale, and specialization needed for a bold, new style of IT.
HP ProLiant Moonshot servers are designed and tailored for specific workloads to deliver optimum performance. The servers share management, power, cooling, networking, and storage. This architecture is key to achieving 8x efficiency at scale, and enabling 3x faster innovation cycle and bringing thousands of cores on target for projects. It uses 86% less energy, 80% less space, 77% less cost and is significantly, less complex to install and maintain.
After talking with other technologists, I believe that it is a start down a path that will change both how software is written and how solutions are envisioned. When I look at the initial product data sheet, I see a 4.3 U chassis that can hold up to 47 server cartridges. As the processing capability improves so can the cartridges. A full rack of these will replace the computational capability of whole data centers just a few years ago. Granted it excels at certain type of computing needs.
As the HP Pathfinder Innovation Ecosystem improves and continues to bring together leadings partners, a broader set of problems can be addressed:
This means having access to the latest technology and solutions at a groundbreaking, time-to-market pace measured in months rather than years. I can’t wait to see what next big thing will spring forth from this.
I recently came across an HP labs video on the excitement of one of the researchers on next wave developing to compute and gather information.
It shows some of the efforts to be more efficient and yet more powerful. Innovation’s role is in resolving conflicts like this, and that’s exciting.
The whole industry is at a tipping point where new generations of capability will be arriving simultaneously for computing, storage, networking and sensing… which should allow for a novel, innovative dimension of applications and services to take advantage of the new abilities and generate new levels of business value.
I was in a discussion today with some folks that are part of the Service Futures SIG of ISSIP. We were talking about the technology trends that will be shaping our approach to addressing business problems in our organizations. It seems that we may be at a pivot point for our perspective.