See https://github.com/viccuad/salt-configs .

The idea is to apply the Puppet code pattern to create salt config files to setup from a GUIless workstation, to laptop configs, Desktop Environments, and later add NAS, router, media servers, Kodi, etc.

Dotfiles

If you don't want to dive into salt and just want to extract some dotfile config from here, look at: - salt/profile/dotfiles//files/*: a file tree that you could put right on to ~ with stow and the like - salt/profile/dotfiles//files/init.sls: salt state to install dependencies, append environmental variables, aliases, process template and copy them where they correspond, etc - salt/profile/dotfiles//templates/*: files that are processed by salt and copied into place

Salt code pattern

Debug salt on your client (the machine running the salt-minion) via:

salt-call -l debug --state-output=mixed state.apply

The code that describes the infrastructure is implementing the following pattern:

  • Description of the infrastructure:

[] Ids (identity of the machine. Eg: machine02) [] [] Roles (business logic. Eg: workstation, nas) [] [] [] Profiles (Configure whole stack. Eg: dns server) [] [] [] [] Salt formulas (Configure part of the stack. eg: sshd)

  • Data of the infrastructure: separated into the pillars.

This pattern is a best-practices one for Puppet, see 1 and 2.

Building your own Debian Stretch image

Until Debian Stretch is officially released, you can build your own Stretch lxc image (following the official scripts) and use it for the Vagrantfile.

Inside this repo, do:

$ git clone https://anonscm.debian.org/git/cloud/debian-vm-templates.git $ sudo make -C debian-vm-templates/custom-lxc-vagrant stretch $ cp debian-vm-templates/custom-lxc-vagrant/stretch.box . $ vagrant up $ rm stretch.box

Looking for hackers with the skills:

saltstack salt debian dotfiles configs vagrant

This project is part of:

Hack Week 15

Activity

  • about 7 years ago: vcuadradojuan liked this project.
  • almost 8 years ago: vcuadradojuan added keyword "saltstack" to this project.
  • almost 8 years ago: vcuadradojuan added keyword "salt" to this project.
  • almost 8 years ago: vcuadradojuan added keyword "debian" to this project.
  • almost 8 years ago: vcuadradojuan added keyword "dotfiles" to this project.
  • almost 8 years ago: vcuadradojuan added keyword "configs" to this project.
  • almost 8 years ago: vcuadradojuan added keyword "vagrant" to this project.
  • almost 8 years ago: vcuadradojuan started this project.
  • almost 8 years ago: vcuadradojuan originated this project.

  • Comments

    • vcuadradojuan
      almost 8 years ago by vcuadradojuan | Reply

      managed to make a dent into dotfiles, laptop, and destop env setup:

      https://github.com/viccuad/salt-configs/graphs/contributors?from=2017-02-17&to=2017-02-26&type=a

    Similar Projects

    Saline (state deployment control and monitoring tool for SUSE Manager/Uyuni) by vizhestkov

    Project Description

    Saline is an addition for salt used in SUSE Manager/Uyuni aimed to provide better control and visibility for states deploymend in the large scale environments.

    In current state the published version can be used only as a Prometheus exporter and missing some of the key features implemented in PoC (not published). Now it can provide metrics related to salt events and state apply process on the minions. But there is no control on this process implemented yet.

    Continue with implementation of the missing features and improve the existing implementation:

    • authentication (need to decide how it should be/or not related to salt auth)

    • web service providing the control of states deployment

    Goal for this Hackweek

    • Implement missing key features

    • Implement the tool for state deployment control with CLI

    Resources

    https://github.com/openSUSE/saline


    Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil

    Join the Gitter channel! https://gitter.im/uyuni-project/hackweek

    Uyuni is a configuration and infrastructure management tool that saves you time and headaches when you have to manage and update tens, hundreds or even thousands of machines. It also manages configuration, can run audits, build image containers, monitor and much more!

    Currently there are a few distributions that are completely untested on Uyuni or SUSE Manager (AFAIK) or just not tested since a long time, and could be interesting knowing how hard would be working with them and, if possible, fix whatever is broken.

    For newcomers, the easiest distributions are those based on DEB or RPM packages. Distributions with other package formats are doable, but will require adapting the Python and Java code to be able to sync and analyze such packages (and if salt does not support those packages, it will need changes as well). So if you want a distribution with other packages, make sure you are comfortable handling such changes.

    No developer experience? No worries! We had non-developers contributors in the past, and we are ready to help as long as you are willing to learn. If you don't want to code at all, you can also help us preparing the documentation after someone else has the initial code ready, or you could also help with testing :-)

    The idea is testing Salt and Salt-ssh clients, but NOT traditional clients, which are deprecated.

    To consider that a distribution has basic support, we should cover at least (points 3-6 are to be tested for both salt minions and salt ssh minions):

    1. Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
    2. Onboarding (salt minion from UI, salt minion from bootstrap scritp, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator)
    3. Package management (install, remove, update...)
    4. Patching
    5. Applying any basic salt state (including a formula)
    6. Salt remote commands
    7. Bonus point: Java part for product identification, and monitoring enablement
    8. Bonus point: sumaform enablement (https://github.com/uyuni-project/sumaform)
    9. Bonus point: Documentation (https://github.com/uyuni-project/uyuni-docs)
    10. Bonus point: testsuite enablement (https://github.com/uyuni-project/uyuni/tree/master/testsuite)

    If something is breaking: we can try to fix it, but the main idea is research how supported it is right now. Beyond that it's up to each project member how much to hack :-)

    • If you don't have knowledge about some of the steps: ask the team
    • If you still don't know what to do: switch to another distribution and keep testing.

    This card is for EVERYONE, not just developers. Seriously! We had people from other teams helping that were not developers, and added support for Debian and new SUSE Linux Enterprise and openSUSE Leap versions :-)

    Pending

    FUSS

    FUSS is a complete GNU/Linux solution (server, client and desktop/standalone) based on Debian for managing an educational network.

    https://fuss.bz.it/

    Seems to be a Debian 12 derivative, so adding it could be quite easy.

    • [W] Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
    • [W] Onboarding (salt minion from UI, salt minion from bootstrap script, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator) --> Working for all 3 options (salt minion UI, salt minion bootstrap script and salt-ssh minion from the UI).
    • [W] Package management (install, remove, update...) --> Installing a new package works, needs to test the rest.
    • [I] Patching (if patch information is available, could require writing some code to parse it, but IIRC we have support for Ubuntu already). No patches detected. Do we support patches for Debian at all?
    • [W] Applying any basic salt state (including a formula)
    • [W] Salt remote commands
    • [ ] Bonus point: Java part for product identification, and monitoring enablement