NSX-V 6.2 introduced the Cross-NSX feature to allow for NSX logical networking and security across multiple vCenter domains. The ability to apply consistent networking and security across vCenter domains provides for mulitple use cases for Cross-VC NSX: workload mobility, resource pooling, multi-site security, ease of automation across sites, and disaster avoidance/recovery. With the recent release of NSX-V 6.3, several enhancements have been added to the Cross-VC NSX feature to provide for additional capabilities and overall robustness of the solution. In this blog post I’ll discuss the new Cross-VC NSX security enhancements in NSX-V 6.3. For additional information on Cross-VC NSX check-out my prior Cross-VC NSX blog posts.
The security enhancements for Cross-VC NSX can be grouped into two categories:
Active/Active and Active/Standby above refers to if the application is active at both sites or if it is active at one site and standby at another site (ex: disaster recovery). Enhancements for both of these respective categories are discussed in more detail below.
1.) General Enhancements (Apply Across both Active/Active and Active/Standby deployment models)
Figure 1: Cross-VC NSX Active/Standby and Continue reading
What's Pensando working on? Not hard to guess
The post Worth Reading: Dynamics on emerging spaces appeared first on 'net work.
Introducing oVirt virtual machine management via Vagrant.
In this short tutorial I'm going to give a brief introduction on how to use vagrant to manage oVirt with the new community developed oVirt v4 Vagrant provider.
Vagrant is a way to tool to create portable and reproducible environments. We can use it to provision and manage virtual machines in oVirt by managing a base box (small enough to fit in github as an artifact) and a Vagrantfile. The Vagrantfile is the piece of configuration that defines everything about the virtual machines: memory, cpu, base image, and any other configuration that is specific to the hosting environment.
$ vagrant plugin install vagrant-ovirt4To start off, I'm going to use this Vagrantfile:
Vagrant.configure("2") do |config|
config.vm.box = 'ovirt4'
config.vm.hostname = "test-vm"
config.vm.box_url = 'https://github.com/myoung34/vagrant-ovirt4/blob/master/example_box/dummy.box?raw=true'
config.vm.network :private_network,
:ip => '192.168.56.100', :nictype => 'virtio', :netmask Continue reading
But couldn't Cisco have spent less than $3.7B? Questions remain.
The Packet Pushers explore the next chapter of SDN evolution with Big Switch founder Kyle Forster in this sponsored episode, including how SDN can make networks more resilient and responsive. The post Show 326: Big Switch & The Next Chapter Of SDN (Sponsored) appeared first on Packet Pushers.
DockerCon 2017 is for the hackers, the makers and those who want to build tools of mass innovation. In April, 5,000 of the best and brightest will come together to share and learn from different experiences, diverse backgrounds, and common interests. We know that part of what makes DockerCon so special is what happens in the hallways, not just the main stage. Those spontaneous connections between attendees, and the endless networking and learning opportunities, are where the most meaningful interactions occur.
If you haven’t been to a DockerCon yet, you may not know what you are missing. To try to explain why DockerCon 2017 is a must attend conference, we took the liberty of putting together the Top 5 reasons to join us April 17-20 in Austin, Texas.