In SUSE Manager we want to offer support for bootstrapping systems that don't have the salt-minion installed and configured yet. This can be done using salt-ssh given just a hostname, username and password. See the docs about salt rosters for even more options. What we are missing: - Support for using salt-ssh in our library

This project is about using Salt SSH for managing systems without the need of an additional agent to be installed (besides sshd). With the SSH protocol the connection is initiated by the management server, thus Salt SSH can be used to even manage systems that are located outside of company firewalls, i.e. machines that cannot access a salt-master due to firewall restrictions. In order to still be able to access resources inside a company network though it would be very helpful if the salt-ssh command supported remote port forwarding (as with the -R parameter of the ssh command) for tunneling other traffic through the existing ssh connection, for instance a package manager might want to install packages from a company internal RPM repository. A patch was therefore contributed to Salt SSH in order to enable this feature (merged into develop):

Yes this project is yet another project for creating a Suse Manager clone. The motivation for that comes mainly from my need for a simple suse manager that i can easily run at home without the massive overhead involved in suse manager setup. Also since i mainly need to manage opensuse machines most of which are tumbleweed, suse managers repository model does not really work well in that case.

If you are now thinking of Salt-SSH, this is not completely wrong, but also not right. What we are talking about here, is an other Transport for Salt, a replacement for ZeroMQ.

Why?

Project Description

SSH key distribution solution that is in comply with POSIX LDAP requirements and UserDB usernames.