- I am tasked with setting up a Chef server on our Azure Cloud for a new DevOps automation project.
- We are using the Resource Manager model for Azure, in case it's relevant.
- We will likely use free versions of Chef i.e. Chef Automate is not an option.
I am new to Chef and Azure, but I would like to try to do it the "right" way from the start. Specifically: Given the Chef server will eventually become an indispensable part of the DevOps infrastructure I want to make it provisionable through code.
To move toward achieving these objectives I have explored the following options.
Option 1: Chef to provision Chef Server
Use Chef Server cookbooks and Chef solo to provision Chef server.
In such a scenario, my main question is: how do I create the Chef server VM and make Chef Solo discover it?
Option 2: Use Azure CLI + RM Templates
- Manually create Azure VM
- Manually install Chef server
- Save it as an image and Azure RM template
- Use Azure CLI to provision from the RM Template and Image.
I am angling toward this option, but I have some anecdotal opinions from teammates, that Azure RM Templates wll not be declarative. Are they?
Option 3: Use Vagrant + Azure Provider + Chef Solo
- (This option is primarily because I am comfortable with Vagrant)
- The main advantage of this option is that I think it will eliminate the question I had in Option 1. Is my assumption here correct?
- However, I think this option does not work for a permanent infrastructure like Chef Server, I think Vagrant is more useful when you have disposable cloud-based virtualized environments. Is my understanding here correct?
Note: Obviously these are not the only 3 options. Please help with any strategies I might have missed.