-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate nodePrep and masterPrep to playbooks #17
Comments
Ok, I have migrated the nodePrep in commit Id 6562cb6 but the problem now is that I need to be able to deploy ansible scripts into the VMs. Which basically would mean that I need:
|
About #11 I asked @haroldwongms and he said that the plan is to remove NAT on purpose for security reasons. Alternatively, bastion node could be in the same vnet as other nodes so we could just use local addresses without NAT. Pls check this example: This script is to create list of hosts dynamically: And this example is using it: https://github.com/Azure-Samples/ansible-playbooks/blob/master/vmss/vmss-setup-deploy.yml |
actually entire VMSS sample may be useful: https://github.com/Azure-Samples/ansible-playbooks/tree/master/vmss Maybe as a next step we could use scaleset(s) to create nodes. |
I have created issue #19 and suggested the idea that we could have a separate script to prepare images. Then later we could just refer these images in create.yml so additional preparation step and NAT wouldn't be necessary. |
The only concern I have with VMSS is that there was an issue on provisioning disks. You could not select a single VM to deploy one disk, it was all VMs have a disk, or none. |
Let's try to do it all in Ansible Playbooks
The text was updated successfully, but these errors were encountered: