Ansible 1.9.1 Released
Ansible 1.9.1 fixes several bugs, including:
* Fixed a bug related to Kerberos auth when using winrm with a domain account.
* Fixing several bugs in the s3 module.
* Fixed a bug with upstart service detection in the service module.
* Fixed several bugs with the user module when used on OSX.
* Fixed unicode handling in some module situations (assert and shell/command execution).
* Fixed a bug in redhat_subscription when using the activationkey parameter.
* Fixed a traceback in the gce module on EL6 distros when multiple pycrypto installations are available.
* Added support for PostgreSQL 9.4 in rds_param_group
* Several other minor fixes.
As always, this update is available via PyPi and releases.ansible.com now, and packages for distros will be available as soon as possible.
Try on Desktop Button for Docker Hub
We’re excited to announce a new feature on Docker Hub (for Mac users right now) – a button that pulls, configures and runs Docker containers for you on your desktop in a single click. We do this by using an external … ContinuedDocker Selected as Gartner Cool Vendor in DevOps
Docker is pleased to have been included in Gartner’s latest “Cool Vendors in DevOps, 2015 report. In the report, Gartner notes: “As virtualization and cloud applications grow beyond being single images run on premise to being comprised of multiple tiers … ContinuedWINDOWS IS COMING? WINDOWS IS HERE!
Back in June, we told you that Windows was coming. We’ve continued to improve the support, with the help of the outstanding Ansible community, and we’d like to highlight some of the improvements in Ansible 1.9. We now offer additional modules, support for domain authentication, and more.
For more information on Ansible’s Windows support, check out our Windows page, or our Ansible Intro to Windows documentation.
As always, we couldn’t do this without our outstanding Ansible community. Thanks to Chris Church, Jon Hawkesworth, Trond Hindenes, Peter Mounce, Chris Hoffman, Paul Durivage, and more!
Running vSphere on AWS or GCE
By now you’ve probably seen or heard the news about Ravello Systems launching Inception—the ability to run nested VMware ESXi on AWS or GCE, including the ability to run VMs on these nested ESXi instances. (Here’s Ravello’s press release.)
In my opinion, this is pretty cool, and it opens the door to a lot of different possibilities: upgrade testing, automation testing, new feature testing, hosted home labs (aka “Lab as a Service”). Lots of folks are interested in using this new Ravello functionality for “Lab as a Service.” Here’s Andrea Mauro’s take on this topic.
As part of the pre-launch activities, a number of bloggers and community advocates were able to work with Ravello on some very interesting projects:
- William Lam built both a 32-node VSAN cluster (running vSphere 5.5) as well as a 64-node VSAN cluster (running vSphere 6.0). He posted details here, along with a great walkthrough of setting up vSphere on Ravello.
- Mike Preston built out an environment that allowed him to perform a vMotion from AWS to GCE.
I was also engaged with Ravello on a project: building a (reasonably) large-scale vSphere environment on Ravello. The original goal was to Continue reading
Technology Short Take #50
Welcome to Technology Short Take #50, the latest in my series of posts sharing various links and articles pertaining to key data center technologies. I hope that you find something useful here!
Networking
- Tyler Christiansen recently published a post on a network automation workflow that was based on a presentation he gave at the SF Network Automation meetup. The workflow incorporates Ansible, git, Jenkins, and Gerrit. If you’re looking for more examples of how to incorporate these sorts of tools into your own network automation workflow, I’d recommend having a look at this article.
- This post contains a link to a useful presentation on the essential parts of EVPN. It’s quite useful if you (like me) need an introduction to this technology.
- Need to reset the CLI privileged mode password on your NSX Manager instance? Here’s a walkthrough. (Warning: as pointed out in the article, this is most likely not supported. Use at your own risk.)
- This article by Russell Bryant is a great overview and update of the work going on with Open Virtual Network (OVN). I’m really excited about OVN and looking forward to seeing it develop and grow.
- This is kind of cool, and (in my Continue reading
DockerCon15 Website is up, announcing the first speakers!
Today we’re thrilled to announce that the DockerCon website is live with (almost) everything you wanted to know about the conference, including the first batch of speakers! With over 380 submissions this year, the DockerCon Community Committee set to the … ContinuedUbuntu, cloud-init, and OpenStack Heat
In this post I’d like to share a couple of things I recently learned about the interaction between cloud-init and OpenStack Orchestration (aka “Heat”). This may be stuff that you already know, but in the interest of helping others who may not know I’m posting it here.
One issue that I’d been repeatedly running into was an apparent “failure” on the part of Heat to properly apply cloud-init configurations to deployed Ubuntu instances. So, using a Heat template with an OS::Nova::Server resource defined like this would result in an instance that apparently wasn’t reachable via SSH (I’d get back Permission denied (publickey)):
resources:
instance0:
type: OS::Nova::Server
properties:
name: cloud-init-test-01
image: { get_param: image_id }
flavor: m1.xsmall
networks:
- port: { get_resource: instance0_port0 }
key_name: labDeploying an instance manually from the same image worked perfectly. So what was the deal?
The first thing I learned was that, in some circumstances (more on this in a moment) defaults to injecting SSH keys (like the key named lab specified in the template) to a user account named “ec2-user”. Ah! I’d been using the default “ubuntu” account specified in Continue reading
Cisco VIRL NXOSv NXAPI Update
Cisco officially announced the April release of Cisco VIRL the announcement and upgrade instructions can be found here. Some of the highlights from the upgrade are: ISOv is now up to version 15.2(2)T...[[ Summary content only, you can read everything now, just visit the site for full story ]]
Online Meetup: Docker Engine 1.6: labels, logging, builder, and more
In case you missed it, Docker 1.6 has been released last week and we announced major updates to Docker Engine, Registry, Compose, Swarm, and Machine. We released all these projects at the same time so you can test and roll … ContinuedDocker Tutorial 6 – Dockerfile (Part 1)
This is a casual Docker tutorial series. We started out first with very simple sessions on how to install and use the docker run command. In future videos we will hit more advanced topics. In this sixth video we cover … ContinuedRunning Photon on Fusion via Vagrant
Most of you have probably picked up on the news of VMware’s new container-optimized Linux distribution, code-named “Photon”. (More details here.) In this post, I’m going to provide a very quick walkthrough on running Photon on VMware Fusion via Vagrant. This walkthrough will leverage a Vagrant box for Photon that has already been created.
To make things easier, I’ve added a photon directory to my GitHub “learning-tools” repository. Feel free to pull those files down to make it easier to follow along.
I assume that you’ve already installed Vagrant, VMware Fusion, and the Vagrant plugin for VMware. If you haven’t, you’ll want to complete those tasks—and verify that everything is working as expected—before proceeding.
-
Install an additional Vagrant plugin that enables Vagrant to better detect and interact with Photon using this command:
vagrant plugin install vagrant-guests-photonIf you don’t install this plugin, you’ll likely get a non-fatal error about Vagrant being unable to perform the networking configuration. (Review the GitHub repository for this plugin if you want/need more details. Also, note that a PR against Vagrant to eliminate the need for this plugin was opened and merged; this fix should show up in a future release of Vagrant.)
Start contributing to Docker in 5 easy steps
If you write code for a living, you’ve probably heard of Docker by now. You might have played around with it, and if you’re lucky, you may even have had the chance to use it to deploy systems in production. … ContinuedTips for Deploying NGINX (Official Image) with Docker
In the past year alone, the Docker community has created 100,000+ images and over 300+ million images have been pulled from Docker Hub to date. Over 20 million of these pulls came from the 70+ Official Images that Docker develops … ContinuedVMware News and the Expanding Minimalist OS Ecosystem
The Docker community saw expanded capabilities introduced today from VMware who showed support for the open source ecosystem with the announcement of two ecosystem projects – Project Photon, a Linux container OS and Project Lightwave, a container identity and access … ContinuedRunning an etcd-Backed Docker Swarm Cluster
In this post, I’ll build on a couple of previous posts and show you how to build your own Docker Swarm cluster that leverages etcd for cluster node discovery. This post builds on the information presented on how to run an etcd 2.0 cluster on Ubuntu as well as the information found in this post on running a Consul-backed Docker Swarm cluster.
To help you follow along, I’ve created a Vagrant environment that you can use to turn up the configuration described in this blog post. These files are found in the “docker-swarm-etcd” directory of my GitHub learning-tools repository. Feel free to use the files in this directory/repository to help with the learning process.
There are 3 major components to this configuration:
- A cluster of three Ubuntu 14.04 systems running etcd 2.0 (specifically, etcd 2.0.9, the last release as of this writing). This etcd cluster serves as a discovery back-end for Docker Swarm.
- A set of hosts running the Docker daemon (version 1.4.0 or higher, as required by Swarm). In this particular instance, I’m using CoreOS Linux (version 557.2.0 from the stable branch).
- A few containers running on the CoreOS hosts; Continue reading