Thanks bud. I had Minecraft fully running and accessible in the instance I recently locked myself out of. No loss, was a copy of another environment.
I aspire to getting to the point where I can publish Ansible HowTo’s. Getting there.
(BTW, I haven’t forgotten my other DC Intro article. Wanted to do some hands-on research before publishing, and here we are…)
Related to Ansible, I thought I could add some shell lines in the configuration section of the new launch definition. I was puzzled that it didn’t work as expected at all. For example, I started with the following lines to eliminate some startup errors:
sudo echo "127.0.0.1 test04" > /tmp/temp_hosts
sudo cp /etc/hosts >> /tmp/temp_hosts
sudo cp /tmp/temp_hosts > /etc/hosts
And that resulted in this erorr during startup:
init.py[WARNING]: Unhandled non-multipart (text/x-not-multipart) userdata: ‘b’sudo echo "127.0.0.1 tes’…’
This led to “hey, I should try Ansible”.
What am I missing about that configuration section with a new instance?
(I wrote the above days ago but somehow the response was held in a Discuss buffer, weird. Continuing…)
I’ve spent the last several days entrenched in Ansible. You’ve created a monster. There are thousands of modules and custom roles and playbooks. I believe the appropriate course of action is to build a server manually, noting every required command, then find the Ansible equivalent. After going through the required pain to manually create my own playbook to get everything just right (with a new LAMP server or Minecraft as examples), I’m sure I’ll find some playbook that someone’s already published, making my manual effort somewhat obsolete. Is that the pattern or am I missing something about using these tools more effectively?