<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Vultr on René Moser</title><link>https://www.renemoser.net/tags/vultr/</link><description>Recent content in Vultr on René Moser</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 19 Mar 2018 22:23:30 +0100</lastBuildDate><atom:link href="https://www.renemoser.net/tags/vultr/index.xml" rel="self" type="application/rss+xml"/><item><title>Vultr Firewalling with Ansible</title><link>https://www.renemoser.net/blog/2018/03/19/vultr-firewalling-with-ansible/</link><pubDate>Mon, 19 Mar 2018 22:23:30 +0100</pubDate><guid>https://www.renemoser.net/blog/2018/03/19/vultr-firewalling-with-ansible/</guid><description>This is the second part of a post series What&amp;rsquo;s new in Ansible 2.5. In the previous post we learned the basic steps to deploy a server on Vultr.
In this follow up post, you will see how we can secure our server.
This post was written in 2018 for Ansible 2.5, when the Vultr modules shipped with Ansible itself as vr_*. They were renamed to vultr_* in Ansible 2.8 and today live in the vultr.</description></item><item><title>Begin Vultr With Ansible</title><link>https://www.renemoser.net/blog/2018/03/18/begin-vultr-with-ansible/</link><pubDate>Sun, 18 Mar 2018 15:14:49 +0100</pubDate><guid>https://www.renemoser.net/blog/2018/03/18/begin-vultr-with-ansible/</guid><description>Ansible 2.5 is just around the corner, perfect timing to show some of the new features I was involved with and included in this release. This is the first part of a post series What&amp;rsquo;s new in Ansible 2.5.
This post was written in 2018 for Ansible 2.5, when the Vultr modules shipped with Ansible itself as vr_*. They were renamed to vultr_* in Ansible 2.8 and today live in the vultr.</description></item></channel></rss>