List of striker-install switches

From AN!Wiki
Jump to: navigation, search

 AN!Wiki :: How To :: List of striker-install switches

Below are the switches available to customise the Striker stage-2 install.

Switch Value Description
--autostart-dhcpd <none> By default, Striker will not run its "Install Target" feature on boot. This is done to avoid an accidental conflict with your site's main DHCP server(s). Ideally, the BCN will be isolated from the main network. If so, the DHCP server on the dashboard can safely run all the time, avoiding the need to manually enable the "Install Target" when needed.

If you know that your BCN is VLAN or hard isolated, then you can usethis switch to auto-start the "Install Target" feature on boot.

-b <ip_address/netmask> This sets the IP address and subnet mask to be assigned to the Back-Channel Network interface.
-c <customer/owner> This sets the name of the customer/owner of the Anvil!. This is used by the web browser at the top of the input box when asking the user for their login credentials. If this is not set, "Striker Dashboard" will be used alone.
--custom-config /path/to/striker.conf This is an optional way to specify a custom striker.conf file to use instead of the default example striker.conf provided by the installer. Note that the file name does *not* have to be 'striker.conf'. It must have all core variables set though. That is, the specified file must be complete because it will be used instead of, not appended to, the default configuration file.
--ethtool-opts <options> If you need to pass any special 'ethtool' configuration options to your network devices, you can do so using this option. If you want to pass multiple options, be sure to use double-quotes to contain the options.

Note: These options will be applied to both/all ifn_linkX and bcn_linkX interfaces.

-h, -?, --help Show the built-in help dialog. Possibly more up to date than this document.
--host-uuid <uuid> If you want to use a set UUID to identify this machine in ScanCore, you can do so using this switch. This will only make sense if you are rebuilding or replacing an old UUID. To record a machine's existing host UUID, back up:

/etc/striker/host.uuid

In it will be the UUID used to identify each Anvil! machine (Striker dashboards and Anvil! nodes). Note that the Install Manifest records the UUIDs assigned to nodes as well. So replacing a node using the previous manifest automatically re-uses the previous host UUID.

-i <ip_address/netmask>,dg=<ip_address>[,dns1=<ip_address>,dns2=<ip_address>] This sets the IP address and subnet to be assigned to the Internet-Facing Network interface. Unlike -b switch, this switch requires a default gateway be specified after the IP address via:

dg=<ip_address>

IPv4 address of the default gateway.

Optionally, one or two DNS servers may be specified via:

dns1=<ip_address> dns2=<ip_address>

IPv4 addresses of the first and/or secondary DNS server. If these are not set, they will not be used! This disables DNS on the DHCP server as well!

--ipmi-user <user:password> If specified, and if an IPMI BMC is found, the installer will set the IPMI BMC password for the specified user.

Note: This will not create a user! If the specified user is not found in the IPMI user list, the password will not be set and an error will be printed.

--ipmi-ip <ip_address/netmask>[,gw=<ip_address>] If specified, and if an IPMI BMC is found, the installer will set the IPMI BMC to have the specified IP address and network mask/subnet.

Optionally, if 'gw' is set, the BMC's gateway will also be set.

--use-lsi If your dashboard machine uses an LSI-brand storage controller, and if you accepted Avago's license agreement when you created the Anvil! ISO, the LSI 'storcli' and 'MegaCli' RPMs, then they will be installed and configured.
--mtu <byte_size> If your network can handle jumbo frames, you can use this switch to set the MTU byte size. This will be assigned to both/all interfaces.

Note: If you are not certain that your network can handle large packets, do not set this.

-n <hostname> This sets the host name of the Striker dashboard.
--no-os-updates By default, the operating system will be updated if there is Internet access. You can disable this behaviour with this switch.
--no-striker-configure-vmm By default, the 'striker-configure-vmm' will be used to configure Virtual Machine Manager so that Anvil! systems added via Striker are automatically added to and removed from VMM. In some cases, this can cause login trouble (though that is a bug and should be reported, please).

Using this option prevents the automatic management of Striker dashboard to Anvil! node access and Virtuam machine Manager configuration.

--no-reboot By default, the installer will reboot the system when it is finished. This option prevents this from happening. If you are installing over an ssh connection, using this switch is recommended.
--ntp <ip[,ip]> If one or more network time server IPs are passed, they will be added to Striker's NTP configuration file. Multiple NTP servers can be specified using commas to separate the IPs.
-p <start_ip:end_ip> This sets the DHCP range that this Striker dashboard will offer IPs on for new machines being installed off of the local PXE server. If set to 'none', PXE will not be configured.

NOTE: This lease range must be in the BCN subnet. We do not want to interfere with existing DHCP servers on the IFN!

--peer-dashboard <hostname=x,bcn_ip=y> This allows you to tell this Striker dashboard about its peer. When set, the installer will configure the other dashboard as a ScanCore database host and record its data to the peer as well.

NOTE: This only works if the ScanCore database configuration and Striker password is the same as this dashboard! If you have a differing configuration or password, please manually add the peer information to striker.conf and /etc/hosts after the install completes.

--rhn <user:password> When installing on a RHEL server, these credentials can be passed to add the machine to yout RHN account.

NOTE: This uses Red Hat's subscription-manager, NOT the legacy RHN tools.

--router-mode When Striker is configured to be an install target, using this switch tells Striker to run as a router, providing Internet access on the BCN to the machines getting DHCP IPs from it on the BCN.

If '-p' is not set, this option will be ignored.

NOTE: This will expose the BCN to the IFN! Care has been taken to block all traffic from the IFN to the BCN, but no program is perfect. If you are particularly concerned about this, audit the code before using this. In any case, it is a good idea to disable the "Install Target" feature in Striker when not needed. That will tear down the bridge as well.

--run-rc-local In some cases, some users have customisation in '/etc/rc.local' that can be clobbered by the --gui install. Using this switch causes the installer to call 'sh /etc/rc.local' just prior to the end of the install process.
-u <user:password> This is the user name and password to set for Striker. This will be used for the web interface, ScanCore database and the dashboard's console (root user) interface, so keep it secure!
-vvvv, -vvv, -vv, -v This sets the debug level to 4, 3, 2, or 1 respectively.
-y Automatically answers "yes" to prompts. Specifically, this prevents confirmation request for network remapping, so it should only be used by scripts.

Back to:

 

Any questions, feedback, advice, complaints or meanderings are welcome.
Us: Alteeve's Niche! Support: Mailing List IRC: #clusterlabs on Freenode   © Alteeve's Niche! Inc. 1997-2019
legal stuff: All info is provided "As-Is". Do not use anything here unless you are willing and able to take responsibility for your own actions.
Personal tools
Namespaces

Variants
Actions
Navigation
projects
Toolbox