New SUSE R&D Employee workstation/laptop auto-installer
a project by dmacvicar
Updated over 5 years 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 hackers with the skills:

salt saltstack autoyast boot linux

This project is part of:

Hack Week 15 Hack Week 16

Activity

  • over 7 years ago: okurz liked this project.
  • almost 8 years ago: jbyers left this project.
  • almost 8 years ago: dmaiocchi liked this project.
  • almost 8 years ago: TBro liked this project.
  • almost 8 years ago: ancorgs liked this project.
  • almost 8 years ago: mlin7442 liked this project.
  • almost 8 years ago: paper318 liked this project.
  • almost 8 years ago: paper318 joined this project.
  • about 8 years ago: jbyers joined this project.
  • about 8 years ago: jbyers liked this project.
  • about 8 years ago: dmaiocchi disliked this project.
  • over 8 years ago: teclator liked this project.
  • over 8 years ago: dmacvicar joined this project.
  • over 8 years ago: dmaiocchi liked this project.
  • over 8 years ago: dmaiocchi liked this project.
  • over 8 years ago: dmaiocchi liked this project.
  • over 8 years ago: dmaiocchi liked this project.
  • over 8 years ago: dmaiocchi liked this project.
  • over 8 years ago: dmaiocchi liked this project.
  • over 8 years ago: dmaiocchi disliked this project.
  • over 8 years ago: dmaiocchi liked this project.
  • over 8 years ago: mbologna started this project.
  • over 8 years ago: joachimwerner liked this project.
  • over 8 years ago: diegoakechi liked this project.
  • over 8 years ago: mbologna liked this project.

    • All Activity

    Comments

    • joachimwerner
      over 8 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 8 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 8 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

    pudc - A PID 1 process that barks to the internet by mssola

    Description

    As a fun exercise in order to dig deeper into the Linux kernel, its interfaces, the RISC-V architecture, and all the dragons in between; I'm building a blog site cooked like this:

    • The backend is written in a mixture of C and RISC-V assembly.
    • The backend is actually PID1 (for real, not within a container).
    • We poll and parse incoming HTTP requests ourselves.
    • The frontend is a mere HTML page with htmx.

    The project is meant to be Linux-specific, so I'm going to use io_uring, pidfs, namespaces, and Linux-specific features in order to drive all of this.

    I'm open for suggestions and so on, but this is meant to be a solo project, as this is more of a learning exercise for me than anything else.

    Goals

    • Have a better understanding of different Linux features from user space down to the kernel internals.
    • Most importantly: have fun.

    Resources