As you know, the main virtualization conference VMworld 2016 arranged by VMware is now being held in Las Vegas. On the first day of the conference several interesting announcements were made. For example, VMware Cloud Foundation, which soon will be available on the IBM platform and later with other vendors, as well, was presented. It allows to get a ready-made infrastructure at customer’s site with both necessary software and hardware components and ready, configured and integrated control and automation tools like NSX, Virtual SAN and vRealize:
vSphere Replication has proved to be a great bonus to any paid vSphere license. It is an amazing and simple tool that provides cheap and semi-automated Disaster Recovery solution. Another great use case for vSphere Replication is migration of virtual machines.
vSphere Replication 6.x came with plenty of new useful features:
Network traffic compression to reduce replication time and bandwidth consumption
Linux guest OS quiescing
Increase in scalability – one VRA server can replicate up to 2000 virtual machines
Replication Traffic isolation – that is what we are going to talk today.
The goal of traffic separation is to enhance network performance by ensuring the replication traffic does not impact other business critical traffic. This can be done either by using VDS Network Input Output Control to set limits or shares for outgoing or incoming replication traffic. Another benefit of traffic isolation addresses security concern of mixing sensitive replication traffic with other traffic types.
Many of you know that VMware has a technology called vSphere Integrated Containers (VIC). It involves launch of Docker (and others) virtualized containers in small virtual machines with a lightweight operating system based on Linux distribution.
This operating system is VMware Photon OS 1.0, which has been finally released just recently. This is the first release version of this operating system from VMware, but in the long view it can become the main platform for virtual appliances by replacing the everlasting SUSE Linux.
The QoS policy was a feature included in Windows Server 2012 R2 that enabled to set a minimum and a maximum IOPS on a VHD(X). These policies were not centralized and you had to set the QoS policy on each VHD(X) independently.
In Windows Server 2016, Microsoft has improved this feature because the policy can now be stored in the cluster database. You can create a policy based on a minimum / maximum IOPS and/or a bandwidth. This policy can be applied to a VHD(X) (Dedicated Policy Type) or to a set of VHD(X) (Aggregated policy Type).
In part two of this multi part blog series, we covered the creation and configuration of a GitHub account, to host a GitHub repository for a Quick Start template, and then we examined Visual Studio Code integration with Git and lastly we pushed commits to a remote repository on GitHub.
In the final post, we will modify and deploy sample and custom template and parameter JSON files.
If you missed Part I and Part II, please make sure to check them here Part I and Part II before you continue with the last part. (more…)
If you missed Part I, please make sure to check it here before you continue with this post.
With Windows Server 2012 Hyper-V became truly NUMA aware. A virtual NUMA topology is presented to the guest operating system. By default, the virtual NUMA topology is optimized by matching the NUMA topology of physical host. This enables Hyper-V to get the optimal performance for virtual machines with high performance, NUMA aware workloads where large numbers of vCPUs and lots of memory come into play. A great and well known example of this is SQL Server.
Many of you have heard of Virtual Volumes (VVols) storage technology, which allows essential increasing of storage I/O performance within VMware vSphere environment by using logical volumes for certain virtual machines components and transferring of some storage operations to disk arrays.
In this series of three blog posts, we will show you how to create and deploy Infrastructure as a Service (IaaS) applications using Azure Resource Manager templates.
In this guide, we will explain the benefits of Azure Resource Manager and resource groups, then we will examine and analyze a number of Quick Start Azure Resource Manager templates that are available on GitHub. In the next post, we will create and configure a GitHub account, if you don’t already have one, to host a GitHub repository for a Quick Start template, and lastly we will examine Visual Studio Code integration with Git and push commits to a remote repository. (more…)
Extend Active Directory to Microsoft Azure is a common scenario when you implement hybrid cloud. For example, protected VM with Azure Site Recovery may need access to Active Directory even if On-Premise datacenter is unreachable. You can also extend your Active Directory to Azure when you use production workloads in Azure VMs to avoid to implement a new forest or to avoid to use the VPN connection for all Active Directory workloads. In this topic, we will see how to extend the Active Directory to Microsoft Azure.