NetBoot Appliance on SuSE Linux?

[musat]

Hello, We use SuSE Linux for all of our Linux servers, so I was wondering if there is a way to break apart the install to see what gets installed. I am relatively certain that since this will run on Red Hat, installing on SuSE should be fairly straight forward. I am guessing that if I could check the install process it could be modded to install on SuSE.
Thanks, Tim

[Hafiz]

I couldn't really get the Netboot working well on a RHEL/CentOS 7 instance but using a docker container worked well. Here is the method that I posted on another thread, if you wanted to go down that route:-

For netbooting I am about to use CentOS 7 minimal in the company.
Here are the three links that you will need for setting this up on a CentOS 7 minimal install:

https://themacwrangler.wordpress.com/2015/04/24/creating-a-netboot-server-with-centos-7-and-bsdpy/comment-page-1/#comment-113

https://macmule.com/projects/autocaspernbi/

http://www.projectatomic.io/blog/2015/06/notes-on-fedora-centos-and-docker-storage-drivers/

So from those links you should derive the following:-

AutoDMG
Basically, use AutoDMG application to create a never booted DMG of the latest OS X with Updates.

AutoCasperNBI
Start up AutoCasperNBI application and use at least the following settings:
Tick “Will be served from NetSUS or BSDPy".
And make sure to tick “Install modified rc.netboot file".

Start-up your CentOS 7 Minimal system
$ yum -y update
$ systemctl stop firewalld && systemctl disable firewalld
$ sed -i -e 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/selinux/config
$ reboot
$ yum -y install vim docker
$ systemctl start docker
$ systemctl enable docker
$ systemctl restart docker
$ docker pull hunty1/bsdpydocker

$ rm -rf /var/lib/docker/
$ vim /etc/sysconfig/docker-storage
And amend to the following:
DOCKER_STORAGE_OPTIONS= -s overlay
$ systemctl restart docker

run “docker info” to verify that Storage Driver is now called overlay.

$ mkdir /nbi

$docker run --restart=always -d -v /nbi:/nbi -p 69:69/udp -p 67:67/udp -p 80:80 -e BSDPY_IP=Your_CentOS7_IPAddress --name netboot_server hunty1/bsdpydocker

Verify that docker container is running “docker ps -a". Look at docker logs for container: “docker logs -f netboot_server".

$ yum -y install samba samba-client
$ useradd smmbuser

Set the password for smbuser
$ smbpasswd -a smbuser

$ useradd smbuser
$ smbpasswd -a smbuser
$ mv /etc/samba/smb.conf /etc/samba/smb.conf.backup

$ vim /etc/samba/smb.conf
Minimal SMB Conf file for CentOS 7

[global]
workgroup = MYGROUP
server string = Samba Server Version %v
log file = /var/log/samba/log.%m
max log size = 50
security = user
passdb backend = tdbsam
local master = no
create mask = 0744
force create mode = 0744
directory mask = 0755
force directory mode =0755
inherit permissions = yes
============================ Share Definitions ==============================

[nbi]
path = /nbi
available = yes
read only = no
browseable = yes
public = no
writable = yes

$ systemctl start smb
$ systemctl start nmb
$ systemctl enable smb
$ systemctl enable nmb

$ chown smbuser /nbi

Now copy the netboot image set to /nbi that you created with AutoCasperNBI by dropping it into the smb share that you have just created.

$ docker restart netboot_server

Verify the docker container picked up the /nbi by running “docker logs netboot_server", you should see something like:

09/09/2015 04:15:47 PM - DEBUG: [========= Using the following boot images =========]
09/09/2015 04:15:47 PM - DEBUG: /nbi/10.10.5AutoCasperNBI.nbi

Now netboot a MacBook (or on a Mac just use Startup Disk utility to the netboot image being presented).