Scott's Weblog

[...] Welcome to Technology Short Take #39, in which I share a random assortment of links, articles, and thoughts from around the [...] #27 Technology Short Take #33 Technology Short Take #26 [...]

[...] Welcome to Technology Short Take #40. The content is a bit light this time around; I thought I’d give you, my readers, [...] #35 Technology Short Take #4 Technology Short Take #34 [...]

[...] Welcome to Technology Short Take #41, the latest in my series of random thoughts, articles, and links from around the [...] #35 Technology Short Take #30 Technology Short Take #25 [...]

[...] Welcome to Technology Short Take #42, another installation in my ongoing series of irregularly published collections of [...] #38 Technology Short Take #34 Technology Short Take #33 [...]

[...] NSX blog series, in which I continue the discussion around integration between OpenStack and VMware NSX, and in which I’ll provide more details about how exactly to integrate them. If you are [...]

[...] , and service nodes), it’s time to add integration into a cloud management platform. VMware NSX was designed to be integrated into a cloud management platform. Because VMware NSX offers a [...]

[...] again, this time from a more practical perspective of what it looks like to use VMware NSX for logical networking in an OpenStack environment. If you haven’t been keeping up with [...]

[...] Welcome to part 14 of the Learning NSX blog series, in which I discuss the ability for VMware NSX to do Layer 3 routing in logical networks. This post will also include a look at a very cool [...]

[...] , although it means that some values (like the shared public provider network to which the logical router uplinks and the security group) have to be hard-coded in the template. One thing that the [...]

[...] can combine up to 10 gateway appliances together for redundancy and scale-out performance. Logical router: As you might recall from part 14, a logical router is a logical construct within NSX that [...]

[...] you’ve seen so far have involved the use of NAT (specifically, source NAT, or SNAT) on the logical router in order to establish outbound connectivity. You’ve had to use floating IP addresses to [...]

[...] you’ve seen so far have involved the use of NAT (specifically, source NAT, or SNAT) on the logical router in order to establish outbound connectivity. You’ve had to use floating IP addresses to [...]

[...] . Visit the site for more information on virtualization, servers, storage, and other enterprise technologies. Technology Short Take #38 Similar Posts: Technology Short Take #35 Technology [...]

[...] . Visit the site for more information on virtualization, servers, storage, and other enterprise technologies. IDF 2014: Data Center Mega-Session Similar Posts: IDF 2014 Day 1 Keynote IDF 2014 [...]

[...] . Visit the site for more information on virtualization, servers, storage, and other enterprise technologies. Running Arista vEOS on KVM Similar Posts: Working with KVM Guests Connecting LXC [...]

[...] .org. Visit the site for more information on virtualization, servers, storage, and other enterprise technologies. Cloud-Hosted Cloud Management via Platform9 Similar Posts: Sessions at the Fall [...]

[...] the L2 gateway service that will provide the L2 connectivity in and out of a NSX-backed logical network. This process is similar to the process described in part 9 of the series, which showed you [...]

[...] the L2 gateway service that will provide the L2 connectivity in and out of a NSX-backed logical network. This process is similar to the process described in part 9 of the series, which showed you [...]

[...] the Learning NVP/NSX blog series, in which I’ll discuss adding a gateway service to a logical network. If you are just now joining me for this series, let me bring you up to speed real quick: [...]

[...] through the process of adding hypervisors to NVP/NSX. In part 5, I showed you how to create a logical network that could be used to connect VMs to each other independent of the underlying physical [...]

[...] . Docker containers provide a standard, consistent way of packaging just about any application. (At least, that& [...]

[...] of your choice, and then reference that Vagrantfile in the one that creates your Docker containers. Of course, since Vagrant expects the filename to be Vagrantfile, that means the file [...]

[...] partition. All applications run in containers. CoreOS provides out-of-the-box support for Docker containers. In fact, all applications on CoreOS run in containers. This enables separation of [...]

[...] service, and the NSX gateway service hosts one or more logical routers. Neither the NSX gateway appliance nor the NSX gateway service are visible to the consumers of the environment; they are only [...]

[...] service, and the NSX gateway service hosts one or more logical routers. Neither the NSX gateway appliance nor the NSX gateway service are visible to the consumers of the environment; they are only [...]

[...] to adding L2 connectivity to your NSX-powered OpenStack environment: Add at least one NSX gateway appliance to your NSX implementation. (Ideally, you would add two NSX gateway appliances for [...]

[...] to adding L2 connectivity to your NSX-powered OpenStack environment: Add at least one NSX gateway appliance to your NSX implementation. (Ideally, you would add two NSX gateway appliances for [...]

[...] , sharing with all of my readers and followers along the way. And, because I believe that VMware Fusion is the most robust virtualization solution for Mac OS X, I’ll be using Vagrant with VMware [...]

[...] actual virtualization work. A provider could be VirtualBox (included by default with Vagrant), VMware Fusion, Hyper-V, vCloud Air, or AWS, just to name a few. Boxes: At the heart of Vagrant are boxes. [...]

[...] part 2. Virtualization The ability to run nested hypervisors is the primary reason I still use VMware Fusion on my laptop instead of switching to VirtualBox. In this post Cody Bunch talks about how to [...]

[...] -vagrant folder in that repository. What You’ll Need Vagrant (I tested with Vagrant 1.7.2) VMware Fusion (I used Fusion 6.0.5 on OS X 10.9.5) the VMware plugin for Vagrant the CoreOS Vagrant box for [...]

[...] -level overview of the basics on integrating VMware NSX into an OpenStack deployment using OpenStack Neutron. In case you’re just now catching up on this blog series, I encourage you to visit my [...]

[...] the basics of VMware NSX-OpenStack integration, and explains how the various components of OpenStack Neutron and VMware NSX will interact. Once you understand how the different components of Neutron [...]

[...] use the term net-gateway. You can verify that the L2 gateway service is recognized by OpenStack Neutron by running the following command with admin permissions: You should see a single entry in [...]

[...] use the term net-gateway. You can verify that the L2 gateway service is recognized by OpenStack Neutron by running the following command with admin permissions: You should see a single entry in [...]