Giter VIP home page Giter VIP logo

kayak's Introduction

Using Kayak

Building

  • Set PKGURL to be the source of the OmniOS bits we wish to install with kayak, in case it's not the default "omnios" publisher for whatever release branch you have checked out.

  • zfs create rpool/kayak_image

  • gmake {PREBUILT_ILLUMOS=} BUILDSEND=rpool/kayak_image

BUILDSEND must be specified.

PREBUILT_ILLUMOS should point to an already-built illumos-omnios of the version you wish to construct an installer. It is optional, but the build will warn you if you do not specify it. The build uses "svccfg-native" if possible to manipulate SMF on target images without conversing with the host machine's SMF services.

must be specified.

install-http: Builds the .zfs.bz2 file, which is what Kayak uses for any install it does. Independent target.

install-tftp: Builds the miniroot.gz file, which is what PXE Kayak feeds to GRUB or Loader to boot itself on a PXE boot. Independent target.

install-iso: Builds both install-{http,tftp} and then proceeds to construct .iso using components from both.

install-usb: Builds install-iso, and then proceed to construct .usb-dd based on the ISO image.

Operation

DHCP server:

  • your server should be set to PXE boot
  • the DHCP server must return and IP, a nextserver and a bootfile
  • the boot file should be the file {{{/boot/grub/pxegrub}}} or {{{/boot/pxeboot}}} from an existing OmniOS system

TFTP server:

  • menu.lst.01<macaddr_just_hex_caps> based on the template provided in this directory should be placed in /tftpboot/ if using grub, or put loader.conf.local in /tftpboot/boot
  • /boot/grub/pxegrub or /boot/pxeboot should be placed in /tftpboot/
  • /platform/i86pc/kernel/amd64/unix should be placed in /tftpboot/omnios/kayak/
  • the miniroot.gz file should be placed in /tftpboot/omnios/kayak/

HTTP server:

  • The system install images should be placed an accessible URL
  • The target system kayak config should be placed at a URL path with the filename <macaddr_just_hex_caps>

kayak's People

Contributors

danmcd avatar esproul avatar hal9k-illumos avatar lotheac avatar postwait avatar

Stargazers

avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

hal9k-illumos cypromis synetostorageos esproul cloudxtreme v-a-b sunsparc64 lotheac jbrnfnd wiedi omniosorg dagbrown

kayak's Issues

Want nvme support in Kayak

I'm stashing this here because I'll soon have test h/w and will probably end up doing it myself. If someone else gets to it sooner, so much the better.

We should support installing to nvme devices. Since Kayak does not use libdiskmgmt, we don't need to wait for https://www.illumos.org/issues/6232 .

Add support for creating initial net config

Hi all,

I think it is not very easy for new users coming to Omnios from various other distros to make the initial network configuration so I have written a small tool in Python to remedy this obstacle. The script is tested and runs on all Omnios as of r151014. I have tested on r151014 and r151022

The script is not ment to be the swiss army knife for configuring networks on Omnios so there is no support for vnic, vlan, and aggregates. It will only support configuring a single nic given the
user the option for dhcp and static setup. The user is also asked whether to configure dns in which case the user is asked for an IP.

Currently it will only handle ethernet but IPoIB is on my todo list. The script can be downloaded here: http://git.datanom.net/netconf.git/

SMF issue during install with utmp

Noticed that during an r151014 Kayak install, svc:/system/utmp:default went into maintenance because the utmpd executable (/usr/lib/utmpd) was missing. SMF reported an exit status of 96 from the start method. The relevant code is here:

http://src.illumos.org/source/xref/illumos-gate/usr/src/cmd/utmpd/svc-utmpd#29

http://src.illumos.org/source/xref/illumos-gate/usr/src/cmd/svc/shell/smf_include.sh#240 shows that SMF_EXIT_ERR_CONFIG is indeed 96.

This wasn't fatal to the installed system (the install was already done) but it did stall Kayak and force a maintenance login.

It looks like we toss the utmp SMF manifest in build_image.sh though, so I'm not sure what the correct fix is. Maybe we just keep utmpd, or maybe we don't need utmp at all in the miniroot/breakfix environment?

DNS does not seem to work in kayak

It seems DNS is not working within kayak.
I had a quick look by setting NO_REBOOT but it seems even if you configure resolv.conf and nsswitch.conf it still doesn't work. I think libresolv is missing?

AutoHostname does not pad with 0

AutoHostname is pretty neat, but I noticed it does not pad with 0 like SmartOS does.

Not sure this is by design or not. At the very least it is not consistent with the other stuff like cfg naming.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.