To start this presentation, let’s look at how industry trends are creating some real networking challenges There is a virtualization wave sweeping across Data Centers. A few years ago a small % of servers were running hypervisors. Today many servers are running hypervisors and supporting multiple applications. When it comes to the use of cloud services, business today is actually outpacing IT. Business users have been quick to recognize the cloud’s advantages in speeding innovation, accelerating business processes, and reducing time to revenue. But the management of a private cloud, or a mixed environment – hybrid/public cloud is presenting some major challenges like orchestrating the movement of the load.How people in this room have phones and other devices that are not approved or supported by your IT organization? The consumerization of IT is another trend adding to the challenges of networking. Changes in the workforce, an increasingly mobile and remote workforce are placing the same demand on wireless networks as there are for wired networks.The pace of change is accelerating.These trends leading to greater complexity and to requirements for increasing security.Management today are discreet separate components for servers, storage and networking. They are not federated. This causes complexity and drives up cost of delivering services and extends the time to deliver new applications to users.The bottom line: Changing networking begins with listening to your customers, and these changes are unique opportunities to introduce the richness of our data center offering.
HP’s Virtual Application Networks are our vision for Software Defined Networks. Virtual Application Networks enable businesses to spend less time managing infrastructure and more on connecting users to applications.
Virtual Application Networks is a game changer. It is one you will feel comfortable with because it is similar to server virtualization.HP Virtual Application Networks will transform the networking industry the way hypervisors transformed the server industry.The end-to-end control plane is similar to a hypervisor. And Virtual Application Networks are similar to Virtual Machines (VMs).
Let’s focus on the amount of time it takes to connect an application to the network. A system administrator uses tools that allow him to manage with policies rather than command lines. His policy-based tools enable speed, consistency and reliability. But, when he needs to connect to the network, it’s a very different story for the network administrator. Legacy network administrators are forced to use a command line interface, which is based on 40-year old technology. Rather than managing with policies, he has to ask the system admin a series of low-level questions before he even begins configuring the network with the CLI. In a recent meeting with a CIO, he told me he believes “If you’re using the CLI and scripts, you’ve already lost the battle for cloud.“According to analyst data, a typical data center may have 500 servers with each of them running 20 virtualized workloads. That’s 10,000 workloads! Each workload requires at least 6 network attributes. The network admin has to use over 250,000 command line entries to configure these 60,000 network attributes on a port-by-port basis across dozens of switches! Imagine, even if someone is a really good typist, they are probably bound to make a mistake once every few thousand entries. That’s is still 250 errors AND you have to find them! That’s what makes this manual processlong, inconsistent and unreliable.
Tie the Virtual and the Physical Network Together
What we have done is allowing the server and networking guy to continue operating indpendanly, each one defining asnd setting up there services, and then using a “subscription” model to connect then while breaking the serial dependency, and thus reduced dramatically the time and complexity to get on networkPolitical and procedural problem at the server edge, is amplified, System Admin waiting for Networking Admin for IP address/Vlan etc So…what we are proposing…Template driving model that allows each admin to maintain there domain of controlCreate connection types in template – which detailes what a Application of particular type needs from Server and Network By doing that, you can publish in a self service portal , what is available and allow sys admin to choose
Let’s go back to our original example of deploying an exchange instance and its virtual machines. Click #1: With Virtual Application Networks, the first step is to characterize the application delivery requirements for Exchange in the IMC VAN Manager Module. Click #2: Here, we build a connection profile from a preconfigured template. Click #3: The second step is to virtualize the server to network connectivity in VMware vCenter with a plug-in that comes with the IMC VAN Manager module. Click #4: Here, the sys admin simply chooses the connection profile for Exchange. Every time a new Exchange instance is deployed, the same profile is selected, ensuring speed, consistency and reliability. Click #5: The third step is to orchestrate the network with the IMC VAN Manager module where the Exchange VMs are visible after selecting the connection profile. Click #6: By simply “powering them on,” IMC will automatically configure the switches based on the connection profile. Click #7: The application is deployed in three easy steps! And I never had to touch the command line interface!