@scottalanmiller said in Fedora 26 Failing Salt Update:

@tim_g said in Fedora 26 Failing Salt Update:

Will that uninstall yum-utils? Isn't that still needed for a lot of things?

dnf-utils replaces it.

https://bugzilla.redhat.com/show_bug.cgi?id=1478593

@emad-r One of the main points of using configuration management tools is that when using them properly you create idempotent operations (getting the same result no matter the number of times the operation is executed).

Instead of using cmd.run to execute the install, you could as others have mentioned the chocolatey module, or if you don't want to install chocolatey on your computers you could use the win_pkg which requries a repo created on the salt-master. Both of those modules are idempotent, so once you reach the desired state no matter how many times you run them they will not make any more changes.

https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.win_pkg.html
https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html

The software available in the official windows git repo.
https://github.com/saltstack/salt-winrepo-ng

Creating a windows software repository:
On your salt master run

salt-run winrepo.update_git_repos

Sync the repo on your Windows minions

salt -G 'os:windows' pkg.refresh_db

Now you can use the pkg module in your states, or adhoc commands.

//Example adhoc command (remote execution) salt -G 'os:Windows' pkg.install salt-minion

That last command will always install the latest version of the salt-minion you could add the version parameter to specify the one you require.

My Favorite Ultra-VNC setup:

Not all issues can fixed from command line alas, thus this recipe:

uvnc: file.recurse: - source: salt://uvnc - name: 'c:\salt\uvnc' - makedirs: True cmd.run: - name: 'c:\salt\uvnc\state.cmd' module.run: - name: firewall.disable

remeber to re-enable the firewall of the client when finished. (salt "client" firewall.enable)
you will need to create uvnc folder (get it from UltraVNC portable builds) folder in your Salt master, in /srv/salt

in it :

winvnc.exe

UltraVNC.ini

state.cmd

SecureVNCPlugin32.dsm (Optional Encryption plugin)

Server_ClientAuth.pubkey (Optional Encryption server SSL handshake check)

And in the state.cmd put the following:

taskkill /f /im winvnc.exe sc stop uvnc_service sc delete uvnc_service "c:\salt\uvnc\winvnc.exe" -install "c:\salt\uvnc\winvnc.exe" -startservice sc config uvnc_service start= demand ipconfig | findstr /i "ipv4"

And whenever you want to connect to client, run this in salt master:
salt '172' state.apply uvnc

And you will see the IP of the client, you will need to match the IP and if you made any custom setting like port number/encryption plugin with vnc viewer and connect to client.

Not having used salt yet myself, couldn't you set the contents of that file using the Salt Master?

I'll add a note for clarity given the title... SaltStack does not do authentication like AD does. AD does not do patching of any sort like Salt does. Salt is an alternative to common myths about AD functionality, but not to actual AD functionality. But you can use Salt to do distributed local authentication management, which does replace the need for AD, but is very different than what is being discussed here. In this case Salt is replacing GPO, not AD.

@msff-amman-Itofficer said in Beginner SaltStack Question: Can minions be placed in folders or groups ? (Coming from AD perspective):

@scottalanmiller

ohh shit, how did that get passed me...

Great, thanks again.

:)

@aaronstuder said in SaltStack Use Cases:

@scottalanmiller Why not just rsync directly to the master? You want versioning?

Yes, and multiple users, and a central repository.

This way you can share the config(s) under conf.d between multiple machines using the same roles (or whatever Salt calls them) and have different main NGINX server settings.

@aaronstuder said in Installing Varnish Cache to a LAMP Stack on Fedora 25 with SaltStack:

@scottalanmiller said in Installing Varnish Cache to a LAMP Stack on Fedora 25 with SaltStack:

Varnish Cache cannot handle TLS connections, so Apache will continue to server HTTPS on port 443, for now at least.

That's unfortunate :-/ I use Varnish on Cloudways, but everything is HTTPS... Does that mean Varnish is doing nothing?

It just means that an SSL layer has to be in front of it. Nginx is used on most platforms to handle SSL.

I've added an article on using NGinx to accelerate SSL in front of LAMP: https://mangolassi.it/topic/13177/deploying-an-nginx-reverse-proxy-with-ssl-on-a-lamp-server-with-saltstack/

@emad-r said in Automatically Add New Vultr Fedora Minion to Salt Master:

@scottalanmiller said in Automatically Add New Vultr Fedora Minion to Salt Master:

If you are using Vultr as your VPS or Cloud Computing IaaS platform, then you have some simple tools to make automating a Salt Minion installation even easier. Vultr allows for "boot scripts" which run upon initial VM creation, along with their automatically installed system keys. Adding a tiny script can make all of the difference between needing to set up a new VM and having the entire process be totally automated.

Here is an example script that you can use. Notice that this is for Fedora and uses DNF. You will need a similar script for APT, YUM or other package management systems.

#!/bin/sh dnf -y install salt-minion echo "master: you.salt.master" >> /etc/salt/minion systemctl restart salt-minion systemctl enable salt-minion

That's all that it takes. Select the script when building your VM(s) and look for them to auto-populate in your Salt Master's key request list.

But what will be the ID/name of this Fedora instance in salt master ?

LOL, I got confused. Was thinking we were on Sodium, not salt.

It'll be your hostname.

@JaredBusch said in Install NextCloud 11 on Fedora 25 with SaltStack:

@wrx7m said in Install NextCloud 11 on Fedora 25 with SaltStack:

I am going to blow up my nextcloud vm and start with the Fedora netinstall.

If you are only after Nextcloud, here is my guide for that.
https://mangolassi.it/topic/13573/install-nextcloud-11-03-on-fedora-25-minimal

If you want to learn Salt, then continue with this post as you have been.

I will do both :) Thanks for this.

Just as a comparison, here's what it would look like with Ansible:

name: Recursively own html files file: path: /var/www/html owner: apache group: apache state: directory recurse: yes

learned a new English word today.

@dafyre said in Why Do We Get IP Local Hostnames for Salt Minion Keys:

@scottalanmiller said in Why Do We Get IP Local Hostnames for Salt Minion Keys:

Okay, finally got around to tracking this down. In your minion file, on Linux systems this would be /etc/salt/minion, you need to uncomment the id: field and put in the name that you want to use and restart your minion process. This will update the name as seen in the Salt Master.

Is this separate from the /etc/salt/minion_id file?

It's just in the minion file.

If you ran the Bootstrap script, this is what you would have gotten as the error:

Fetched 1,035 kB in 1s (959 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... ca-certificates is already the newest version (20160104ubuntu1). apt-transport-https is already the newest version (1.3.2ubuntu0.1). apt-transport-https set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded. Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package gnupg-curl * ERROR: Failed to run install_ubuntu_stable_deps()!!!