vsan-5fd-brocadeIt’s time for a quick update on the VMware Virtual SAN routed network deployments with Brocade white paper! I published earlier this year. By request, the section on Multicast considerations has been expanded and clarified about protocol choices.

The configuration example now includes commands to implement all Multicast functionality in the spine-leaf routed network. Also, we’ve included how to configure a cool Brocade feature named “AutoQoS”.

What this does is a simple-to-implement QoS mechanism to make sure Virtual SAN traffic receives priority should the network experience congestion. With Hyper-Converged Infrastructure the network will most often have to support both the storage and application traffic concurrently, so QoS becomes more important than ever – and being able to configure it in a simple way across the network is incredibly useful and neat.

Download the newly updated paper directly from the link below:

Access the original post – New Virtual SAN Enterprise Networking with Brocade White Paper

For more on the Greatest Storage Platform Ever Created visit the Virtual SAN product page on vmware.com.

VMware Virtual SAN

To learn more about Brocade Data Center Fabrics  please visit the links below:

Brocade Data Center Fabrics

I want to thank the folks at Brocade for their help and collaboration validating and creating this collateral and putting it together for our mutual customers.


For future updates on Virtual SAN (VSAN), vSphere Virtual Volumes (VVol) and other Storage and Availability technologies, as well as vSphere Integrated OpenStack (VIO), and Cloud-Native Applications (CNA) be sure to follow me on Twitter: @PunchingClouds. (edit)


hci-devopsEarlier this summer I had the opportunity to participate in strategic meetings with VMware customers to discuss data center transformation, hyper-converged architectures and the relevance and suitability for large development environments.

These were large customers whose business depends on consistent delivery of services. I reviewed the business value, the transformational capabilities provided by the Software-Defined Datacenter and the use of VMware’s hyper-converged solution as the building block. To address their network and security, we presented NSX and vSphere Integrated OpenStack (VIO) as their development facing infrastructure service. There were consistent questions around accessibility to programmable APIs, as these customers have bought into and adopted DevOps culture within their enterprise. With the exponential growth of DevOps in industry, it is no secret that companies and customers from all verticals are looking to the potential outcomes of this type of operating model.

The importance of programmable APIs has become of extreme value and importance for enterprise customers as they consider the adoption of DevOps operating models. Modern software products and frameworks are expected to be accompanied by a well-defined and fully accessible set of programmable APIs. VMware has an API-first approach to their development lifecycle. In fact, VMware APIs are one of the most utilized sets of programmable APIs in the industry. At VMware, we have a portfolio composed of a multitude of products, solutions, and frameworks. Some of which are partially integrated, others are fully integrated, and some others are not integrated at all. Either way, each solution possesses its deployment and configuration procedures depending on what resource domain they are part of in the data center.

As an advocate of DevOps culture and operating model, I feel that individual functions and procedures for different resource domains of the data center are required and needed. I also believe that VMware products should include and leverage richer operating methods that should also cater to, and facilitate DevOps operating models. Great to hear that VMware’s flexibility was what our customers were looking for: they wanted to manage their infrastructures with a set of tools that matched their DevOps operating model. Essentially, the customers expressed interest in not having to worry about the specific deployments and configuration of infrastructure artifacts but simply to get to their personnel to their development environments. Read Full Article →

logical-diagramHigh availability is always one of the top demanded and desired qualities for all enterprise infrastructure designs. Being a critical infrastructure design requirement regardless of what the resource and functional domain topic of discussion may be (storage, compute, network).

As a one-time enterprise architect in the professional services organization at VMware, I can attest to the challenges presented by the demand to satisfy high availability requirements. Doing so while having to adhere to additional business-critical requirements such as infrastructure cost and complexity reduction as part of the same level of considerations. This is hard to achieve without a lot of compromises.

High availability is obtained through multiple levels of redundancy which means purchasing a multitude of a resource (services or devices). This presents many challenges as the more services or devices required to reach the desired level of high availability, the more complex and expensive the management, and procurement of the infrastructure becomes (CAPEX and OPEX).

Enter Virtual SAN, a hyper-converged solution design to meet the enterprise high availability requirements with cost effectiveness all the way around (CAPEX and OPEX). Below is a demonstration of an hyper-converged enterprise infrastructure that is designed to be highly available, and secured across multiple routed networks powered by vSphere, Virtual SAN, and Brocade networking devices. Observe the simplicity in which Virtual SAN provides high availability comparable to 99.9999% of uptime at a fraction of what it would cost to achieve for a traditional infrastructure design, implementation, and management.

If you are interested in the network configuration details and procedures for deploying Virtual SAN across routed networks select any of the sources below depending on the network hardware vendor you may have:

– Enjoy

For future updates on Virtual SAN (VSAN), vSphere Virtual Volumes (VVol) and other Storage and Availability technologies, as well as vSphere Integrated OpenStack (VIO), and Cloud-Native Applications (CNA) be sure to follow me on Twitter: @PunchingClouds

final-vforum-2016This summer participated in some of the vForum conference events in North America. I had the opportunity to present and demonstrate VMware’s emerging products and technologies as part of the vForum morning main stage keynote. To make things even better, I got to do this with one of my closest friends in the world, Chris McCain, the Director of Product Management in VMware’s Networking & Security Business Unit. Chris was the mastermind behind one of the most successful customer/partner programs ever done at VMware the “NSX Ninja Program.”

Our goal was to do something full of energy, with the passion we share for the emerging products and technologies being developed at VMware. At the same time, we wanted to make sure that all the customers and partners would understand that the data center of tomorrow is not being built on specific pinpoint products, but instead built on platforms. We wanted to demonstrate some of the emerging technologies that are driving the modernization and evolution of the data center.

We wanted to make a case for products like NSX and Virtual SAN, two of the core pillars of the modern software-defined datacenter architecture and how they offer economies of scale, agility, efficiencies, and security at a level that is unprecedented currently in the industry.

We wanted to do all of this, but aimed to deliver it in the most non-scripted or rehearsed of ways, in our signature “Cowboy style, shooting from the hip” approach. The idea was risky, and it would take a lot of guts for someone to trust us and allow us to do what we did. Even Chris Wolf, the VP and VMware CTO of Americas was all in on the idea after we had a brief discussion in Las Vegas at VMworld. The idea was well received by Elaine Morris, “The vForum Lady” and her team, and they officially invited us to participate in the event.

In the end, after receiving much highly anticipated feedback, we managed to pull off what we set out to do. Chris and I delivered a presentation that was full of energy, but most importantly, our customers and partners were captivated, enthusiastic, and reciprocated the energy that we had hoped for. We demonstrated the VMware Cross-Cloud Architecture with Virtual SAN, NSX, vRealize Automation, SPBM and VMware Cloud Foundation.

The vForum shows were a huge success, and I’m so grateful for the team letting us participate and contribute. A special thanks to Chris Waldo, Elaine Morris, Sehra Bremner and every hard-working member of that team for their support.

Below is the recording of our presentation from the very last stop of the vForum conference in Houston.


For future updates on Virtual SAN (VSAN), vSphere Virtual Volumes (VVol) and other Storage and Availability technologies, as well as vSphere Integrated OpenStack (VIO), and Cloud-Native Applications (CNA) be sure to follow me on Twitter: @PunchingClouds.

spbm-cloudA couple of weeks ago I delivered a brief webcast presentation on Storage Policy-Based Management and its use across mixed vSphere storage environments. This has been one of my favorite topics for a couple of years. I have spent a lot of time developing guidelines for different scenarios so that vSphere customers can see and understand the value of what this policy framework introduces for the management, and consumption of storage.

In this brief presentation, I covered some basic concepts of the policy framework and how SPBM is designed to work. Today, all of the Software-Defined Storage technologies supported in vSphere (vSAN, VVols, VAIO) natively support and depend on SPBM as part of their technological value proposition, but more importantly from an operational efficiency standpoint as well.

New features like vSphere Encryption and traditional vSphere storage features like Storage I/O Control (SIOC) are now being delivered via policies.   In the presentation below, I walk through a couple of demonstrations that include building policies for a vSphere infrastructure composed of mixed storage abstractions, vendor solution, and management portals (vSohere Web Client, and vRealize Automation).

In my last point in the demonstration,  I reintroduce the case for SPBM utilized in cloud type of infrastructures with mixed storage self-serve storage offerings.  SPBM can be used with traditional vSphere datastore constructs such as NFS, and VMFS and it can tie it into cloud scale type production environments with vRealize Automation and event OpenStack.


For future updates on Virtual SAN (VSAN), vSphere Virtual Volumes (VVol) and other Storage and Availability technologies, as well as vSphere Integrated OpenStack (VIO), and Cloud-Native Applications (CNA) be sure to follow me on Twitter: @PunchingClouds.