# /srv/salt/configure-esxi.sls configure-host-ssh : esxi.ssh_configured : - service_running : True - ssh_key_file : /etc/salt/ssh_keys/my_key.pub - service_policy : 'automatic' - service_restart : True - certificate_verify : True configure-host-coredump : redump_configured : - enabled : True - dump_ip : '' configure-host-syslog : esxi.syslog_configured : - syslog_configs : loghost : ssl://localhost:5432,tcp://10.1.0.1:1514 default-timeout : 120 - firewall : True - reset_service : True - reset_syslog_config : True - reset_configs : loghost,default-timeout configure-host-ntp : esxi.ntp_configured : - service_running : True - ntp_servers : - 192.174.1.100 - 192.174.1.200 - service_policy : 'automatic' - service_restart : True configure-vmotion : esxi.vmotion_configured : - enabled : True configure-host-vsan : esxi.vsan_configured : - enabled : True - add_disks_to_vsan : True configure-host-password : esxi.password_present : - password : 'new-bad-password' Running Remote Execution Commands section below for an example. Need to provide these parameters when you execute the commands. Passed through to the function via the proxy process that is already running. These parameters are contained in the Pillar files and You'll notice that most of the functions in the vSphere module require a host, Out over the network and communicate with the ESXi host. Version of pyVmomi and ESXCLI are installed, and that machine would reach You could run functions from this module on any machine where an appropriate Through pyVmomi or ESXCLI against the local machine. When credentials and a host aren't passed, Salt runs commands The module takes credentials ( username and password) and a target hostĪrgument. If you pull up the docs for it you'll see that almost every function in Standard Salt execution module that does the bulk of the work for the ESXi Proxy This allows you to use any number of potential fallback passwords. Host until the password is updated in Pillar and the Proxy Minion process is Or states that run after the password change will not be able to run on the If you only have one password option,Īnd if you have a state changing the password, any remote execution commands You know that you'll be changing this password during your initial setupįrom the default to a new password. Use-case/reasoning for using a list of passwords: You are setting up anĮSXi host for the first time, and the host comes with a default password. Password to the front and retire the unused ones. 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. This tutorial assumes basic knowledge of Salt.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |