This repository has the files/tools for building a Razor Microkernel based on Alpine Linux for the ppc64le architecture. The resulting discovery image is used by the Razor server to take inventory of new machines.
This section describes how to build an image on a CentOS system.
This will produce a tar file microkernel.tar. To deploy this on
an existing Razor server, extract it in the server's repo_store_root that
you set in config.yaml:
> tar xf microkernel.tar -C $repo_store_root
To log into the microkernel, use the root password thincrust. Also
note that logging information will be sent to tty2.
- bug/issue tracker: RAZOR project in JIRA
- on IRC:
#puppet-razoron freenode - mailing list: puppet-razor@googlegroups.com
The microkernel client has been broken out into several small, focused scripts intended to perform one task, well. They are designed to be fired off through cron, or through a process scheduling supervisor.
The entry point is the binary:
razor-submit-factswill discover and send facts about the node to Razor- this will also act on the command returned during that action
Configuration is created by overlaying multiple sources, based on this priority map -- lower numbers are "more important" and override higher numbers. The intent is that more dynamic sources of data override less dynamic sources of data.
Sources are:
- Kernel command line (as read from
/proc/cmdline) - DHCP "next server" option (@todo danielp 2013-07-26: not implemented yet)
- Static, on-disk configuration file (
/etc/razor-mk-client.json) - A default DNS assumption that
razorwill point at your Razor server.
Any of these configuration options can be omitted with no ill effects.
In practice, the kernel command line is the place that almost all configuration will come from. This is set by the Razor server during boot, automatically, to help clients that boot from it to rendezvous correctly.
The static, on-disk configuration file is not expected to be used in most cases: this is provided as a convenience for users who, for some reason, want to boot statically from local media rather than through the Razor server, but still want to use the Razor MK image. (eg: through a virtual CD device, etc.)
Configuration options are:
ipthe IP address of the Razor server.serverthe DNS name of the Razor server.
If supplied, the ip value is preferred to the server value for locating
the server. Both are supported since correctly functioning DNS is not assured
during the early boot process; in general, you should strongly prefer to use the server value.
We supply a "hardware ID" value to the Razor server to help identify the specific hardware that is currently running: this is based on the MAC addresses of network adapters found in the current system.
Presently that is limited only to adapters with a visible name matching
/^eth/, following the default naming convention for Linux wired
Ethernet adapters.
@todo danielp 2013-07-26: we should fix that, because it is too limited, and will no longer work once F19 or F20 roll out their new "purpose and physical location" naming convention for network adapters.