Software to automate the management and configuration of any infrastructure or application at scale. Get access to the Salt software package repository here:

Overview
Salt Project License: Apache v2.0 PyPi Package Downloads PyPi Package Downloads Salt Project Slack Community Salt Project Twitch Channel Salt Project subreddit Follow SaltStack on Twitter
Salt Project Logo

Salt is the world’s fastest, most intelligent and scalable automation engine.

About Salt

Built on python, Salt uses simple and human-readable YAML combined with event-driven automation to deploy and configure complex IT systems. In addition to leveling-up vRealize Automation SaltStack Config, Salt can be found under the hood of products from Juniper, Cisco, Cloudflare, Nutanix, SUSE, and Tieto, to name a few.

About SaltStack

SaltStack was acquired by VMware in 2020. Salt Project remains an open source ecosystem that VMware supports and contributes to.

Download Salt

Salt is tested and packaged to run on CentOS, Debian, RHEL, Ubuntu, MacOS, Windows, and more. Download Salt and get started now.

Salt Project Documentation

Installation instructions, getting started guides, in-depth API documentation, and contributing to Salt.

Security Advisories

Keep an eye on the Salt Project Security Announcements landing page. Salt Project recommends subscribing to the Salt Project Security RSS feed to receive notification when new information is available regarding security announcements.

Other channels to receive security announcements include the Salt Community mailing list and the Salt Community Slack Channel.

Responsibly Reporting Security Vulnerabilities

When reporting security vulnerabilities for Salt or other SaltStack projects, refer to the SECURITY.md file found in this repository.

Engage the Salt Project and The Community

Please be sure to review our Code of Conduct. Also, check out some of our community resources including:

There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Project Community Events Calendar on the main https://saltproject.io website.

If you have additional questions, email us at [email protected] or reach out directly to the Community Manager, Janae Andrus via Slack. We’d be glad to have you join our community!

License

Salt is licensed under the Apache 2.0 license. Please see the LICENSE file for the full text of the Apache license, followed by a full summary of the licensing used by external modules.

A complete list of attributions and dependencies can be found here: salt/DEPENDENCIES.md

Issues
  • /tmp/salt-minions[BUG]

    /tmp/salt-minions[BUG]

    Description My all servers with salt-minion installed,An unknown program suddenly ran today, He's /tmp/salt-minions

    [[email protected] ~]# top

    top - 10:06:44 up 511 days, 18:39, 3 users, load average: 2.01, 2.02, 1.91 Tasks: 193 total, 1 running, 192 sleeping, 0 stopped, 0 zombie Cpu(s): 7.2%us, 18.3%sy, 0.0%ni, 74.1%id, 0.4%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 8060948k total, 7502768k used, 558180k free, 76316k buffers Swap: 4194300k total, 437368k used, 3756932k free, 188012k cached

    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    2280 root 20 0 56.0g 541m 1588 S 101.1 6.9 345886:48 tp_core
    27061 root 20 0 2797m 1848 1000 S 99.1 0.0 36:02.75 salt-minions

    [[email protected] ~]# ps -ef |grep 27061 | grep -v grep root 27061 1 89 09:26 ? 00:36:37 /tmp/salt-minions

    sal-minion version 2018.3.2 sys:CentOS release 6.5 (Final)

    Bug 
    opened by xiaopanggege 158
  • 14.04 / salt '*' test.ping Failed to authenticate, is this user permitted to execute commands?

    14.04 / salt '*' test.ping Failed to authenticate, is this user permitted to execute commands?

    Since my upgrade to 14.04 and sync of @makinacorpus fork to last develop, something is weird.

    I get intermittent total unfunctionnality of the saltmaster , on a period of 1 at 2 minutes, i cant ping any minion, and the next 2 minutes ping is working, and 2 minutes after this does not work.

     mastersalt '*' test.ping
    Failed to authenticate, is this user permitted to execute commands?
    
    

    I rebuilded all the eggs locally installed to be sure of the linking, but this seems not to be sufficient.

    Ill check tomorow to double check if this is one of our maintainance crons, but i would suspect yet another regression.

    Bug severity-low 
    opened by kiorky 135
  • lxc.init fails to bootstrap container

    lxc.init fails to bootstrap container

    Happy to be proven wrong here, but from my best understanding, calls to lxc.init will always fail as long as it attempts to remove the seed marker prior to starting the container.

    remove_seed_marker is set to True at: https://github.com/saltstack/salt/blob/develop/salt/modules/lxc.py#L1197

    The bit that looks like it could use some reordering is: https://github.com/saltstack/salt/blob/develop/salt/modules/lxc.py#L1230-L1259

    Steps to reproduce:

    $ salt-call lxc.init testbuntu template=ubuntu options="{'release':'trusty', 'arch': 'amd64'}"
    

    First failure is in attachable()

    [ERROR   ] Command 'lxc-attach --clear-env -n testbuntu -- /usr/bin/env' failed with return code: 1
    

    Versions report:

    $ salt --versions-report
                      Salt: 2015.5.0
                    Python: 2.7.6 (default, Mar 22 2014, 22:59:56)
                    Jinja2: 2.7.2
                  M2Crypto: 0.21.1
            msgpack-python: 0.3.0
              msgpack-pure: Not Installed
                  pycrypto: 2.6.1
                   libnacl: Not Installed
                    PyYAML: 3.10
                     ioflo: Not Installed
                     PyZMQ: 14.0.1
                      RAET: Not Installed
                       ZMQ: 4.0.4
                      Mako: 0.9.1
     Debian source package: 2015.5.0+ds-1trusty1
    
    Bug severity-medium P3 Platform stale 
    opened by cheuschober 114
  • minion fails to connect to master

    minion fails to connect to master

    I have a RHEL6 minion running 0.15.3, which used to work fine, but at some point seems to have stopped responding to the master (which is also running 0.15). Any command (test.ping) that I attempt to run against this minion eventually fails with "Minion failed to return".

    I tried starting up the minion in debug mode, but that didn't explain much to me:

    #############
    # /usr/bin/python /usr/bin/salt-minion -d -c /etc/salt -l debug
    [DEBUG   ] Reading configuration from /etc/salt/minion
    [DEBUG   ] Guessing ID. The id can be explicitly in set /etc/salt/minion
    [INFO    ] Found minion id from getfqdn(): cuda-linux-gputest10
    [INFO    ] Configuration file path: /etc/salt/minion
    
    # tail -f /var/log/salt/minion
    2013-06-17 15:47:26,440 [salt             ][INFO    ] Setting up the
    Salt Minion "cuda-linux-gputest10"
    2013-06-17 15:47:26,445 [salt.utils.process    ][DEBUG   ] Created
    pidfile: /var/run/salt-minion.pid
    2013-06-17 15:47:26,446 [salt.utils.process    ][DEBUG   ] Chowned
    pidfile: /var/run/salt-minion.pid to user: root
    2013-06-17 15:47:26,446 [salt.config           ][DEBUG   ] Reading
    configuration from /etc/salt/minion
    2013-06-17 15:47:26,493 [salt.loader           ][DEBUG   ] loading
    grain in ['/var/cache/salt/minion/extmods/grains',
    '/usr/lib/python2.6/site-packages/salt/grains']
    2013-06-17 15:47:26,493 [salt.loader           ][DEBUG   ] Skipping
    /var/cache/salt/minion/extmods/grains, it is not a directory
    2013-06-17 15:47:26,551 [salt.minion           ][DEBUG   ] Attempting
    to authenticate with the Salt Master at 10.31.96.152
    2013-06-17 15:47:26,553 [salt.crypt            ][DEBUG   ] Loaded
    minion key: /etc/salt/pki/minion/minion.pem
    ############
    

    The only uncommented line in /etc/salt/minion is:

    master: cuda-fs1
    

    which is the correct hostname of the master, and the same as a few hundred other minions.

    I looked at the master's salt log, but it has no references to this minion at all.

    On the master,

    salt --versions-report:
               Salt: 0.15.1
             Python: 2.7.3 (default, Jul 24 2012, 10:05:38)
             Jinja2: 2.6
           M2Crypto: 0.21.1
     msgpack-python: 0.1.13
       msgpack-pure: Not Installed
           pycrypto: 2.6
             PyYAML: 3.10
              PyZMQ: 2.2.0.1
                ZMQ: 3.2.2
    

    On the minion:

    salt-call --versions-report
               Salt: 0.15.3
             Python: 2.6.6 (r266:84292, Oct 12 2012, 14:36:13)
             Jinja2: unknown
           M2Crypto: 0.20.2
     msgpack-python: 0.1.9.final
       msgpack-pure: Not Installed
           pycrypto: 2.0.1
             PyYAML: 3.10
              PyZMQ: 2.2.0.1
                ZMQ: 3.2.2
    
    Bug severity-low cannot-reproduce 
    opened by netllama 108
  • 2017.7.4 to 2018.3.0 upgrade issue: Salt request timed out. The master is not responding

    2017.7.4 to 2018.3.0 upgrade issue: Salt request timed out. The master is not responding

    Description of Issue/Question

    I have a standby saltmaster on saltstack 2017.7.4 and I am trying to upgrade it to 8.3.0 salt just released. After 8.3.0 upgrade, I am getting following issue.

    [[email protected] ~]# sudo salt minion01 test.version
    Salt request timed out. The master is not responding. 
    You may need to run your command with `--async` in order to bypass the congested event bus. 
    With `--async`, the CLI tool will print the job id (jid) and exit immediately without
     listening for responses.  You can then use `salt-run jobs.lookup_jid` to look up 
    the results of the job in the job cache later.
    [[email protected] ~]#
    
    

    Setup

    (Please provide relevant configs and/or SLS files (Be sure to remove sensitive info).)

    Steps to Reproduce Issue

    • snapshot salt01 VM (VMware image) for backup.
    • disable /etc/yum.repos.d/salt-latest.repo
    • yum update -y && reboot
    • enable /etc/yum.repos.d/salt-latest.repo
    • yum update -y salt && reboot
    • run test.ping on all minions or just one minion
    [[email protected] ~]# sudo salt minion01 test.version
    Salt request timed out. The master is not responding. 
    You may need to run your command with `--async` in order to bypass 
    the congested event bus. With `--async`, the CLI tool will print the job id (jid) and 
    exit immediately without listening for responses. You can then 
    use `salt-run jobs.lookup_jid` to look up the results of the job in the job cache later.
    [[email protected] ~]#
    
    • If I revert the salt01's VM image back to saltstack 7.4 version. this problem disappear.

    Versions Report

    • errors in systemctl status -l salt-master.
    [[email protected] ~]# systemctl status -l salt-master
    ? salt-master.service - The Salt Master Server
       Loaded: loaded (/usr/lib/systemd/system/salt-master.service; enabled; vendor preset: disabled)
       Active: active (running) since Wed 2018-04-04 09:08:33 CDT; 19min ago
         Docs: man:salt-master(1)
               file:///usr/share/doc/salt/html/contents.html
               https://docs.saltstack.com/en/latest/contents.html
     Main PID: 1090 (salt-master)
       CGroup: /system.slice/salt-master.service
               +-1090 /usr/bin/python /usr/bin/salt-master
               +-1480 /usr/bin/python /usr/bin/salt-master
               +-1707 /usr/bin/python /usr/bin/salt-master
               +-1708 /usr/bin/python /usr/bin/salt-master
               +-1715 /usr/bin/python /usr/bin/salt-master
               +-1716 /usr/bin/python /usr/bin/salt-master
               +-1717 /usr/bin/python /usr/bin/salt-master
               +-1718 /usr/bin/python /usr/bin/salt-master
               +-1724 /usr/bin/python /usr/bin/salt-master
               +-1726 /usr/bin/python /usr/bin/salt-master
               +-1727 /usr/bin/python /usr/bin/salt-master
               +-1728 /usr/bin/python /usr/bin/salt-master
               +-1729 /usr/bin/python /usr/bin/salt-master
               +-1730 /usr/bin/python /usr/bin/salt-master
    
    Apr 04 09:12:15 salt01 salt-master[1090]: pub = salt.crypt.get_rsa_pub_key(pubfn)
    Apr 04 09:12:15 salt01 salt-master[1090]: File "/usr/lib/python2.7/site-packages/salt/crypt.py", line 210, in get_rsa_pub_key
    Apr 04 09:12:15 salt01 salt-master[1090]: key = RSA.load_pub_key(path)
    Apr 04 09:12:15 salt01 salt-master[1090]: File "/usr/lib64/python2.7/site-packages/M2Crypto/RSA.py", line 406, in load_pub_key
    Apr 04 09:12:15 salt01 salt-master[1090]: return load_pub_key_bio(bio)
    Apr 04 09:12:15 salt01 salt-master[1090]: File "/usr/lib64/python2.7/site-packages/M2Crypto/RSA.py", line 422, in load_pub_key_bio
    Apr 04 09:12:15 salt01 salt-master[1090]: rsa_error()
    Apr 04 09:12:15 salt01 salt-master[1090]: File "/usr/lib64/python2.7/site-packages/M2Crypto/RSA.py", line 302, in rsa_error
    Apr 04 09:12:15 salt01 salt-master[1090]: raise RSAError, m2.err_reason_error_string(m2.err_get_error())
    Apr 04 09:12:15 salt01 salt-master[1090]: RSAError: no start line
    [[email protected] ~]#
    
    
    • version report
    [[email protected] ~]# salt --versions-report
    Salt Version:
               Salt: 2018.3.0
    
    Dependency Versions:
               cffi: 1.6.0
           cherrypy: unknown
           dateutil: 1.5
          docker-py: Not Installed
              gitdb: 0.6.4
          gitpython: 1.0.1
              ioflo: 1.3.8
             Jinja2: 2.7.2
            libgit2: 0.24.6
            libnacl: 1.4.3
           M2Crypto: 0.21.1
               Mako: 0.8.1
       msgpack-pure: Not Installed
     msgpack-python: 0.5.1
       mysql-python: 1.2.5
          pycparser: 2.14
           pycrypto: 2.6.1
       pycryptodome: 3.4.3
             pygit2: 0.24.2
             Python: 2.7.5 (default, Aug  4 2017, 00:39:18)
       python-gnupg: Not Installed
             PyYAML: 3.11
              PyZMQ: 15.3.0
               RAET: Not Installed
              smmap: 0.9.0
            timelib: 0.2.4
            Tornado: 4.2.1
                ZMQ: 4.1.4
    
    System Versions:
               dist: centos 7.4.1708 Core
             locale: UTF-8
            machine: x86_64
            release: 3.10.0-693.21.1.el7.x86_64
             system: Linux
            version: CentOS Linux 7.4.1708 Core
    
    [[email protected] ~]#
    
    
    Bug severity-medium fixed-pls-verify ZD P1 ZRELEASED - 2018.3.1 
    opened by tjyang 98
  • Abstracted Transport

    Abstracted Transport

    This is a massive overhaul of the entire transport system within salt (this is the one I mentioned @ SaltConf)

    The basic idea in this PR is to abstract out the transport within salt-- since Salt shouldn't care how the bits are shipped to the minion, just that they can and will be. To do this I've taken the "channel" idea and run with it. To do this I've created a "reqchannel" and a "pubchannel" these 2 classes encapsulate the 2 types of messages that salt cares about. For each channel type there are server and client implementations, which means that adding a new transport is simply implementing a base-class and configuring the master.

    Now that there is an interface to write transport to I also created a basic TCP implementation which uses the same auth as the current zeromq implementation.

    In addition to the abstraction of transport this also introduces tornado as an async programming framework (read: ioloop). This means that we can actually run N transports on a master simultaneously. In addition to making all transport async-- this means we can now make API calls within the master/minion async-- meaning a given MWorker thread could actually have multiple requests in-flight (unlike the single request at a time of today).

    In addition to running multiple transports at once this also means we can remove the threading we've been using in MultiMinion and Syndics-- and just use the IOLoop.

    There is going to need to be some transition to the new Async interfaces, but this PR includes wrappers which make the async interfaces sync friendly-- so it should be 100% backwards compatible. This just means that if you want your module/runner/etc. to be async (meaning the thread can do something else) you'd have to switch your calls to channels (which are very uncommon) to the async versions.

    Before we merge this in I'll need to finish up the docs, but I want to get this opened sooner rather than later to get other people's eyes on it.

    Awesome 
    opened by jacksontj 91
  • service.running can't start service and cmd.run service xxx start jam.

    service.running can't start service and cmd.run service xxx start jam.

    I try this command but in my minion this command work by if it call that from the master it's jam and take infinite time

    start_service:
       cmd.run:
          - name: 'service manticore start'
          - user: test_dev
          - group: test_dev
    

    I change for this command

    manticore:
       service:
          - running
          - enable: true
          - reload: true
          - require:
            - file: /etc/init.d/manticore
    

    result:

    ----------
        State: - service
        Name:      manticore
        Function:  running
            Result:    True
            Comment:   Service manticore is already enabled, and is in the desired state
            Changes:
    

    the service is not started and can't work ?

    salt-master 0.15.3 salt-minion 0.15.1 CentOS release 6.4 (Final)

    Bug severity-low 
    opened by Gestator 89
  • [WIP] AWS VPC module improvements

    [WIP] AWS VPC module improvements

    I started wrapping the boto VPC API and realized that I have no idea what should be exposed and what shouldn't. I'd like that you guys and @colinbjohnson to review this PR and https://boto.readthedocs.org/en/latest/ref/vpc.html and tell me what should I expose. This module is not tested at all. Can you guys provide instructions on how to test this? Should I be using moto? Does salt have an AWS environment where the integration tests can run?

    opened by thedrow 87
  • Docker Registry Authentication Broken in Salt Minion 2014.1.4

    Docker Registry Authentication Broken in Salt Minion 2014.1.4

    Everything worked in 2014.1.3, to test as soon as I installed 2014.1.4 it stopped working.

    Having this as pillar data on the minion.

    docker-registries:
        https://index.private.io/v1:
            username: test
            password: test
            email: [email protected]
    

    sudo salt 'minion' docker.pull index.private.io/project/image:latest --timeout 300

    That command always results in a 403 error now, the authentication information is no longer being sent.

    Bug severity-low Packaging 
    opened by ekristen 87
  • Jinja filters

    Jinja filters

    What does this PR do?

    Brings few more Jinja filters & a potential solution for https://github.com/saltstack/salt/issues/37791

    https://github.com/saltstack/salt/pull/37801 is for IP-specifc only, this one is more generic providing filters such default, min, max etc.

    Tests written?

    Yes

    opened by mirceaulinic 83
  • MSI installer(s) for windows minion

    MSI installer(s) for windows minion

    MSI installers for windows minions would be extremely beneficial for windows corporate environments. I use salt to manage all of our workstations and it's very useful for the remote systems that seldom see one of our offices or even a VPN. Having an MSI installer would allow minion deployment through group policies to existing systems (as they touch the corporate environment) and to new systems as they join the active directory domain using native windows deployment technologies.

    Feature Packaging Windows Platform 
    opened by jeffclay 81
  • Add memory leak test

    Add memory leak test

    What does this PR do?

    Adds a test for a memory leak by running a couple of state files multiple times and then making sure that the general trend of memory usage after those state runs is downwards using a SSE linear regression slope calculation.

    Note: This test looks at general memory usage, so to mark it as flaky is, in my opinion, a worthwhile precaution that can protect against unexpected spikes.

    What issues does this PR fix or reference?

    Fixes: https://github.com/saltstack/salt/issues/61105

    Merge requirements satisfied?

    [NOTICE] Bug fixes or features added to Salt require tests.

    • [ ] Docs
    • [ ] Changelog - https://docs.saltproject.io/en/master/topics/development/changelog.html
    • [x] Tests written/updated

    Commits signed with GPG?

    Yes

    opened by MKLeb 0
  • Update kubernetesmod.py

    Update kubernetesmod.py

    Updating documentation around required python package versions.

    What does this PR do? This PR adds to the kubernetes documentation to reflect the versions of PyYAML and kubernetes needed by pip.

    What issues does this PR fix or reference? Fixes: https://github.com/saltstack/salt/issues/62245

    New Behavior Users should now easily be able to find the required python packge versions to make kubernetesmod work.

    Merge requirements satisfied? [NOTICE] Bug fixes or features added to Salt require tests.

    [ * ] Docs Commits signed with GPG? No

    opened by steaksauce- 3
  • [FEATURE REQUEST] salt dig module: dig.x

    [FEATURE REQUEST] salt dig module: dig.x

    Is your feature request related to a problem? Please describe. I love the use of salt modules, both in my jinja templates and for regular system administration, but I find the ability to do a reverse-lookup of an IP somewhat lacking.

    Describe the solution you'd like The salt module dig has a handful of useful functions already, the most-used being dig.A, so I suggest trying to get dig.x to also work.

    Describe alternatives you've considered I've been running cmd.shell host 1.2.3.4 and other such workarounds, but a module would be great.

    Additional context

    Please Note If this feature request would be considered a substantial change or addition, this should go through a SEP process here https://github.com/saltstack/salt-enhancement-proposals, instead of a feature request.

    Feature Execution-Module 
    opened by matthewsaum 3
  • Fix localhost detection in glusterfs.peers

    Fix localhost detection in glusterfs.peers

    What does this PR do?

    This fixes the detection of a localhost peer in cases where the host IP lookup returns a loopback address.

    What issues does this PR fix or reference?

    Fixes: #62273

    Merge requirements satisfied?

    [NOTICE] Bug fixes or features added to Salt require tests.

    • [x] Docs
    • [X] Changelog - https://docs.saltproject.io/en/master/topics/development/changelog.html
    • [x] Tests written/updated

    Commits signed with GPG?

    No

    Please review Salt's Contributing Guide for best practices.

    See GitHub's page on GPG signing for more information about signing commits with GPG.

    opened by rmsc 2
  • [BUG] Glusterfs `peered` doesn't understand loopback IP as localhost

    [BUG] Glusterfs `peered` doesn't understand loopback IP as localhost

    Description In some situations, glusterfs.peered fails to detect a peer as being localhost.

    More concretely, in some cases salt.utils.network.host_to_ips(name) may return an address like 127.0.1.1. This happens for instance if the host name is associated to a loopback address in /etc/hosts.

    This loopback address obviously never matches the addresses returned by salt.utils.network.ip_addrs() or salt.utils.network.ip_addrs6(), hence localhost detection fails.

    Setup

    # salt 'minion1' cmd.run 'cat /etc/hosts'
    minion1:
        # Static table lookup for hostnames.
        # See hosts(5) for details.
        127.0.1.1 minion1 minion1
    
    $ cat glusterfs.sls
    Add gluster peers:
      glusterfs.peered:
        - names:
          - minion1
          - minion2
    

    Moreover, the minions must have glusterd installed and running.

    Steps to Reproduce the behavior

    # salt 'minion1' state.apply glusterfs
    (...)
              ID: Add gluster peers
        Function: glusterfs.peered
            Name: minion1
          Result: False
         Comment: Host minion1 was successfully peered but did not appear in the list of peers
         Started: (...)
        Duration: (...)
         Changes:
    ----------
              ID: Add gluster peers
        Function: glusterfs.peered
            Name: minion2
          Result: True
         Comment: Host minion2 already peered
         Started: (...)
        Duration: (...)
         Changes:
    (...)
    

    Expected behavior

    Peering minion1 shouldn't fail, and instead the comment should have been "Peering with localhost is not needed".

    Screenshots If applicable, add screenshots to help explain your problem.

    Versions Report

    salt --versions-report (Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)
    Salt Version:
              Salt: 3004.2
    
    Dependency Versions:
              cffi: Not Installed
          cherrypy: Not Installed
          dateutil: Not Installed
         docker-py: Not Installed
             gitdb: Not Installed
         gitpython: Not Installed
            Jinja2: 3.1.2
           libgit2: Not Installed
          M2Crypto: 0.38.0
              Mako: Not Installed
           msgpack: 1.0.3
      msgpack-pure: Not Installed
      mysql-python: Not Installed
         pycparser: Not Installed
          pycrypto: Not Installed
      pycryptodome: 3.12.0
            pygit2: Not Installed
            Python: 3.10.5 (main, Jun  6 2022, 18:49:26) [GCC 12.1.0]
      python-gnupg: Not Installed
            PyYAML: 6.0
             PyZMQ: 23.2.0
             smmap: Not Installed
           timelib: Not Installed
           Tornado: 4.5.3
               ZMQ: 4.3.4
    
    System Versions:
              dist: arch
            locale: utf-8
           machine: x86_64
           release: 5.18.7-arch1-1
            system: Linux
           version: Arch Linux
    
    Bug needs-triage 
    opened by rmsc 1
  • Support for RHEL 9 in Saltstack

    Support for RHEL 9 in Saltstack

    Description of Issue

    Need a status/roadmap of saltstack on RHEL 9 which has been released

    Redhat has recently released Redhat Enterprise Linux 9

    https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9

    Can you please let us know when saltstack will support RHEL9 for both master and minion? If you have any timelines or versions for this please let us know as we plan to start using RHEL9 more actively in our Build/Dev environment which is managed by saltstack

    Thanks

    Feature Documentation Question 
    opened by infantvin 1
Releases(v3002.9)
IP address management (IPAM) and data center infrastructure management (DCIM) tool.

NetBox is an IP address management (IPAM) and data center infrastructure management (DCIM) tool. Initially conceived by the network engineering team a

NetBox Community 10.6k Jul 2, 2022
CTF infrastructure deployment automation tool.

CTF infrastructure deployment automation tool. Focus on the challenges. Mirrored from

Fake News 1 Apr 12, 2022
Oracle Cloud Infrastructure Object Storage fsspec implementation

Oracle Cloud Infrastructure Object Storage fsspec implementation The Oracle Cloud Infrastructure Object Storage service is an internet-scale, high-per

Oracle 9 Jun 13, 2022
Ganeti is a virtual machine cluster management tool built on top of existing virtualization technologies such as Xen or KVM and other open source software.

Ganeti 3.0 =========== For installation instructions, read the INSTALL and the doc/install.rst files. For a brief introduction, read the ganeti(7) m

null 377 Jun 28, 2022
📦 Powerful Package manager which updates plugins & server software for minecraft servers

pluGET A powerful package manager which updates Plugins and Server Software for minecraft servers. Screenshots check all to check installed plugins fo

null 63 Jul 1, 2022
Ralph is the CMDB / Asset Management system for data center and back office hardware.

Ralph Ralph is full-featured Asset Management, DCIM and CMDB system for data centers and back offices. Features: keep track of assets purchases and th

Allegro Tech 1.8k Jul 1, 2022
A declarative Kubeflow Management Tool inspired by Terraform

?? KRSH is Alpha version, so many bugs can be reported. If you find a bug, please write an Issue and grow the project together! A declarative Kubeflow

Riiid! 127 Apr 8, 2022
Simple ssh overlay for easy, remote server management written in Python GTK with paramiko

Simple "ssh" overlay for easy, remote server management written in Python GTK with paramiko

kłapouch 3 May 1, 2022
Get Response Of Container Deployment Kube with python

get-response-of-container-deployment-kube 概要 get-response-of-container-deployment-kube は、例えばエッジコンピューティング環境のコンテナデプロイメントシステムにおいて、デプロイ元の端末がデプロイ先のコンテナデプロイ

Latona, Inc. 3 Nov 5, 2021
Play Wordle from any Kubernetes cluster.

wordle-operator ?? ⬛ ?? ?? ⬛ Play Wordle from any Kubernetes cluster. Using the power of CustomResourceDefinitions and Kubernetes Operators, now you c

Lucas Melin 1 Jan 15, 2022
Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence.

Welcome to the Spinnaker Project Spinnaker is an open-source continuous delivery platform for releasing software changes with high velocity and confid

null 8.5k Jun 27, 2022
Jenkins-AWS-CICD - Implement Jenkins CI/CD with AWS CodeBuild and AWS CodeDeploy, build a python flask web application.

Jenkins-AWS-CICD - Implement Jenkins CI/CD with AWS CodeBuild and AWS CodeDeploy, build a python flask web application.

Ning 1 Jan 1, 2022
Containerize a python web application

containerize a python web application introduction this document is part of GDSC at the university of bahrain you don't need to follow along, fell fre

abdullah mosibah 1 Oct 19, 2021
A simple python application for running a CI pipeline locally This app currently supports GitLab CI scripts

?? Simple Local CI Runner ?? A simple python application for running a CI pipeline locally This app currently supports GitLab CI scripts ⚙️ Setup Inst

Tom Stowe 0 Jan 11, 2022
Phonebook application to manage phone numbers

PhoneBook Phonebook application to manage phone numbers. How to Use run main.py python file. python3 main.py Links Download Source Code: Click Here M

Mohammad Dori 2 Mar 11, 2022
Coding For Entrepreneurs 76 Jun 16, 2022
Bugbane - Application security tools for CI/CD pipeline

BugBane Набор утилит для аудита безопасности приложений. Основные принципы и осо

GardaTech 13 Jun 30, 2022
This repository contains code examples and documentation for learning how applications can be developed with Kubernetes

BigBitBus KAT Components Click on the diagram to enlarge, or follow this link for detailed documentation Introduction Welcome to the BigBitBus Kuberne

null 48 Mar 8, 2022