<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vmware on www.josephwegner.com</title><link>https://www.josephwegner.com/tags/vmware/</link><description>Recent content in Vmware on www.josephwegner.com</description><generator>Hugo</generator><language>en-us</language><copyright>©2026 Joe Wegner. All rights reserved.</copyright><lastBuildDate>Tue, 04 Aug 2020 02:20:05 -0500</lastBuildDate><atom:link href="https://www.josephwegner.com/tags/vmware/index.xml" rel="self" type="application/rss+xml"/><item><title>RHEL VMware Deployment</title><link>https://www.josephwegner.com/posts/2018/08/rhel-vmware-deployment/</link><pubDate>Mon, 20 Aug 2018 22:38:34 -0500</pubDate><guid>https://www.josephwegner.com/posts/2018/08/rhel-vmware-deployment/</guid><description>&lt;p&gt;Over the last year at work, we have really stepped up our automation efforts.
It started out with OS customization using Ansible, but we quickly ran into the issue of bootstrapping the network configuration.
We were cloning a minimally configured RHEL 7 template to deploy new machines, but we would have to manually login through the remote console to set the IP and also change the VLAN in the admin console.
However, we were on a mission &lt;del&gt;from God&lt;/del&gt; to touch the machines as little as possible in the name of real automation, so even that small amount of manual intervention galled us.&lt;/p&gt;</description></item></channel></rss>