New SUSE R&D Employee workstation/laptop auto-installer
a project by dmacvicar
Updated 5 months ago. 21 hacker ♥️.

The idea is to create a bootable medium (eg. pendrive) that allows:

  • Selection of either SLES, Leap or Tumbleweed.
  • Autoinstallation of the OS.
  • NIS setup if workstation, unison/sync setup if laptop.
  • Corporate VPN setup in the default desktop (GNOME).
  • Thunderbird setup.
  • IRC setup (eg. X-chat GNOME).
  • Shortcuts.
  • Browser bookmarks, intranet or bookmark page as home-page.
  • Mumble
  • VoIP
  • etc

The goal is to have the employee being to work and participate from day #1. More unusual customisations can be done by the employee later (alternative WMs, mail clients, etc).

Implementation ideas:

  • Create a Salt formula that can be managed as an integral opensource project and enhanced over time.
    • Initial test infrastructure with terraform/vagrant so that it can be run in a VM or dry-run mode.
  • Enhance YaST/AutoYaST to be able to apply the formula at boot/firstboot (a project on its own)

Join this project

Looking for mad skills in:

salt saltstack autoyast boot linux

This project is part of:

Hack Week 15 Hack Week 16

Activity

  • over 1 year ago: okurz liked New SUSE R&D Employee workstation/laptop auto-installer
  • almost 2 years ago: jbyers left New SUSE R&D Employee workstation/laptop auto-installer
  • almost 2 years ago: dmaiocchi liked New SUSE R&D Employee workstation/laptop auto-installer
  • almost 2 years ago: TBro liked New SUSE R&D Employee workstation/laptop auto-installer
  • almost 2 years ago: ancorgs liked New SUSE R&D Employee workstation/laptop auto-installer

    • Show History

    Comments

    • joachimwerner
      over 2 years ago by joachimwerner | Reply

      Duncan, would the YaST/AutoYaST approach be mandatory? I'm thinking of an image-based install (via Kiwi's OEM USB image) plus Salt as an alternative. May be a bit less flexible with detecting all the hardware, but easier to maintain. The image would only have to be minimal, because all other patterns/packages can be installed later from a Salt state.

    • cschum
      over 2 years ago by cschum | Reply

      Mauro also has looked into that topic as part of our setup of developer work stations for Cloud Foundry development. Maybe there is some synergy?

    • lrupp
      almost 2 years ago by lrupp | Reply

      Providing an OBS image should be possible as well as providing the needed autoyast profiles. Just ping the DevOPS team once you finished, so we can populate your results :-)

      Additional topic: think about the differences between our offices ... ;-)

    Similar Projects

    Make "salt-toaster" available to be used outside SUSE by PSuarezHernandez

    The salt-toaster (https://github.com/openSUSE...

    From bare metal to virtualized Kubernetes cluster with just Salt and Redfish by joachimwerner

    My goal is build on Alberto's work on ["yomi"](...

    Run and manage your Ansible cluster using Salt! by PSuarezHernandez

    At SUSE we've implemented a module on Salt call...

    perf-bench ipc by dbueso

    The state of the art of sysv/posix ipc benchmar...

    YES Certification Video Tutorials by dstokes

    The YES Certification Tool Kit has long needed ...