Moving the machine between groups seems a little heavy, but yes, there are probably many approaches.
It may be easier to just have "ansible_ssh_port" in your setup playbook override what is in inventory, or do the bootstrap with "-e ansible_ssh_port=22" to override inventory. Alternatively your kickstart/preseed could possibly use ansible-pull at the end of a run and set it up for later management. I would generally like to see the system running on it's final SSH port at the end of preseed so you never have the interval when it's running elsewhere, but some people also have things like provisioning networks/vlans, etc, so it's all very up to you. On Tue, Dec 31, 2013 at 11:32 AM, Brian Coca <[email protected]> wrote: > I don't know about 'the community' but this is what I do myself, there are > probably 10 ways people deal with this, this one just made sense for me > (and you it seems). > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Michael DeHaan <[email protected]> CTO, AnsibleWorks, Inc. http://www.ansibleworks.com/ -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
