Entries from Eric Sloof

Do your IT security and compliance policies seem positively medieval?  Watch this painstakingly researched overview of the Rise of Security and Compliance to find out why... then be thankful that we live in a time with VMware security and compliance solutions for the Cloud.

VMware vCloud Director 1.5 (vCloud Director) gives enterprise organizations the ability to build secure private clouds that dramatically increase datacenter efficiency and business agility. Coupled with VMware vSphere (vSphere), vCloud Director delivers cloud computing for existing datacenters by pooling vSphere virtual resources and delivering them to users as catalog-based services. vCloud Director helps build agile infrastructure-as-a-service (IaaS) cloud environments that greatly accelerate the time to market for applications and increase the responsiveness of IT organizations.

Resiliency is a key aspect of any infrastructure—it is even more important in infrastructure-as-a-service solutions. This case study was developed to provide additional insight and information as to how to increase availability and recoverability of a vCloud Director–based infrastructure using VMware vCenter Site Recovery Manager (SRM) as well as common disaster recovery methodologies and tools. SRM facilitates fast and reliable recovery and enables you to meet your recovery time objectives (RTOs) by automating the failover process of your vCloud Director management environment.

Technical Paper - VMware vCloud Director Infrastructure Resiliency Case Study

The virtual machines in a vApp can connect to vApp networks (isolated or routed) and organization networks (direct or fenced). You can add networks of different types to a vApp to address multiple networking scenarios. Select the Networking tab in a vApp and select the Show networking details check box to view a list of the networks that are available to the vApp. Virtual machines in the vApp can connect to these networks. If you want to connect a virtual machine to a different network, you must first add it to the vApp.

A vApp can include vApp networks and organization networks. A vApp network can be isolated by selecting None in the Connection drop-down menu. An isolated vApp network is totally contained within the vApp. You can also route a vApp network to an organization network to provide connectivity to virtual machines outside of the vApp. For routed vApp networks, you can configure network services, such as a firewall and static routing.

There's also a possibility to connect a vApp directly to an organization network. If you have multiple vApps that contain identical virtual machines connected to the same organization network and you want to start the vApps at the same time, you can fence the vApp. This allows you to power on the virtual machines without conflict, by isolating their MAC and IP addresses.

It's also possible configure certain vApp networks to provide firewall services. Enable the firewall on a vApp network to enforce firewall rules on incoming traffic, outgoing traffic, or both. When you enable the firewall, you can specify a default firewall action to deny all incoming and outgoing traffic or to allow all incoming and outgoing traffic. You can also add specific firewall rules to allow or deny traffic that matches the rules to pass through the firewall. These rules take precedence over the default firewall action.

Eric Siebert over at vsphere-land has managed to calculate all the votes and has put together the Top Blog 2012 results. NTPRO.NL has ended up at the third place in the Top VMware Bloggers 2012. My website was also chosen as number one at "Best Videos used in a Blog" and I'm the most "Favorite Independent Blogger" :-) Congratulations go out to all the other bloggers and I want to thank everyone for casting their vote. I promise the keep up the good work.



In this vChat episode (#25) of vChat Eric, David, Simon and special guest John Troyer (VMware) announce the Top 25 Virtualization Blog awards.

You will learn about the latest new technical features and benefits of the just released
Nexus 1000V v1.5. Also check out this video Video - Cisco Nexus 1000V v1.5 Installation.

The Cisco Nexus 1000V is compatible with any upstream physical access layer switch that is Ethernet standard compliant, including the Catalyst 6500 series switch, Cisco Nexus switches, and switches from other network vendors. The Cisco Nexus 1000V is compatible with any server hardware listed in the VMware Hardware Compatibility List (HCL). Cisco and VMware jointly designed APIs that produced the Cisco Nexus 1000V. The Cisco Nexus 1000V is a distributed virtual switch solution that is fully integrated within the VMware virtual infrastructure, including VMware vCenter for the virtualization administrator. This solution offloads the configuration of the virtual switch and port groups to the network administrator to enforce a consistent data center network policy. In this release Java applications are introduced for VSM and VEM installation.

For the Virtual Supervisor Module (VSM)—The control plane of the switch and a virtual machine that runs Cisco NX-OS, just download the Nexus1000v.4.2.1.SV1.5.1.zip file and enter the following command from a Windows, Linux, or Mac command prompt:

java -jar zip_file_location/Nexus1000v.4.2.1.SV1.5.1/VSM/Installer_App/Nexus1000V-install.jar VSM

For the Virtual Ethernet Module (VEM)—A virtual line card embedded in each VMware vSphere (ESX) host. The VEM is partly inside the kernel of the hypervisor and partly in a user-world process, called the VEM Agent. Enter the following command from a Windows, Linux, or Mac command prompt:

java -jar zip_file_location/Nexus1000v.4.2.1.SV1.5.1/VSM/Installer_App/Nexus1000V-install.jar VEM

Cisco Nexus 1000V Series Switches - Configuration Guides

Cisco Virtual Security Gateway for Cisco Nexus 1000V Series Switches Data Sheet

Scripted installation is an efficient way to provision multiple ESXi host. This video explains how to use a kickstart file to install or upgrade ESXi. Both Shift-O invocation and PXE boot are supported.