You can then change pillar at will to move that Restart the proxy minion-it should just pick up the new password This way, after the password is changed, you should not need to May be updating for an ESXi host either via theįunction. It isĬonfigured this way so you can have a regular password and the password you The proxy integration will try the passwords listed in order. Salt's ESXi Proxy Minion was added in the 2015.8.4 release of Salt.Ī list of passwords to be used to try and login to the ESXi host. Proxy Minion section of Salt's documentation. More in-depth conceptual reading on Proxy Minions can be found in the The master does not know or care that the ESXi target is not a "real" Salt Minion. Proxy process that "proxies" communication from the Salt Master to the ESXi host. Proxy Minion functionality enables you to designate another machine to host a Stack, the ESXi host can't run a regular Salt Minion directly. Since an ESXi host may not necessarily run on an OS capable of hosting a Python Salt Minion, without installing a Salt Minion on the ESXi host. Salt's ESXi Proxy Minion allows a VMware ESXi host to be treated as an individual The third assumption that this tutorial makes is that you also have aīasic understanding of ESXi hosts. You're unfamiliar with Salt's Proxy Minion system, please read the This tutorial also assumes a basic understanding of Salt Proxy Minions. Change 'Name' param of present and absent functions to default to the value of name if not provided.This tutorial assumes basic knowledge of Salt. INFRA-4506 - add list_rules() function to boto_cloudwatch module. INFRA-4506 - test=True should not return False on success I'll experiment with this little wrinkle and see if it helps with renaming minions. Rebooting the host/VM after the change seems to work but I'd prefer not to have to do that. We then set the hostname and role of hosts via script but this has been a little painful since salt doesn't seem to readily want to move to the new hostname. All of our hosts start up with a name that looks like "" where macaddr is the macaddress of the primary kickstarted interface (aa-bb-cc-dd-ee-ff). This is an artifact of our kickstart setup. I'm having a lot of trouble with renaming minions (I have the master copy keys and change the contents of the minion file on the minion but a simple service restart of the salt-minion doesn't seem to be sufficient to get the master talking to the minion with the new minion hostname). Does that mean you specify the contents of the minion file for every host/vm? Are you just pulling the fqdn from the environment for the contents of that file or doing something else? Now you mentioned you guys watch your minion file as well. I'm unlikely to upgrade again until I can figure out how to do this Woah cool. Unfortunately, I didn't think to run the upgrade packages command in verbose mode at the time.ĭo I need to find some external remote-execution method to restart all of the minions post-upgrade (mussh/omnitty, etc.)? This is probably not a bug but it's still very frustrating. The packages were upgraded, but the salt-minion services were not restarted as a part of the upgrade process (for both minion VMs - one is RHEL5 and the other is RHEL6). You'll notice that the upgrade proceeded correctly. I restart the master and minion on my master ~]# salt -versions-report Tzdata-java.noarch 2013g-1.el6 rhel-localrepo Salt-minion.noarch 0.17.1-1.el6 epel-testing Salt-master.noarch 0.17.1-1.el6 epel-testing
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |