(21 intermediate revisions by the same user not shown)
Line 1:
Line 1:
{{header}}
{{header}}
'''Striker''' is the [[Anvil!]] dashboard and node monitoring software.
{{warning|1=This is an in-progress document. Do not expect anything here to be accurate or correct. This warning will be removed when the guide is completed. You can track the progress on [https://github.com/digimer/striker Striker's Github] page.}}
* The Dashboard loads onto monitoring devices and is used to control one or more Anvil! clusters and it's servers.
''Striker'' is the [[Anvil!]] web-based dashboard.
* The Monitor loads onto Anvil! nodes and monitors an individual node's hardware, it's view of the cluster software and shared foundation pack devices.
= Dashboard =
It's goal is to reduce the potential for human errors causing availability interruptions by simplifying the interface as much as possible. With it, you can build, maintain and replace other dashboards and ''Anvil!'' nodes, as well as build ''Anvil!' systems from scratch.
To come later
''Striker'' dashboards also act as a ''[[ScanCore]]'' database. Two or more ''Striker'' dashboards will work together to make the ''ScanCore'' data resilient by handling replication of the data and n-way resync automatically to update new or rebooted dashboards.
== Install Striker ==
* [[Build an Anvil! - Detailed]] - or - [[Build an Anvil! - Cookbook]]
=== Requirements ===
= Manual =
* A machine with two wired network interfaces, one to the [[BCN]] and one to the [[IFN]].
* Version [[Striker v2.0|2.0]]
* [[RHEL]], [[CentOS]] or similar version 6.x (6.5 or higher recommended).
** Minimal install is sufficient, provided you install <span class="code">perl</span>.
** The installer will install everything else it needs.
<syntaxhighlight lang="bash">
yum install perl
</syntaxhighlight>
<syntaxhighlight lang="text">
<yum output>
</syntaxhighlight>
This install document will be using a fresh, minimal install of CentOS 6.5.
=== Getting the Install Script ===
The Striker installer needs to be downloaded. To account for minimal installs where <span class="code">wget</span> is not available, we'll use <span class="code">curl</span> instead which is always available.
The install script works by taking command line switches. You can get a better explanation of the switches by running <span class="code">./striker-installer -h
</span>.
The Striker installer configures the system as well as load the striker software. So we're going to tell it what host name, IP addresses and credentials to use.
In this tutorial, I am building a new Striker dashboard machine I will call <span class="code">an-m03.alteeve.ca</span>. I will be setting the following values:
|Sets the [[IFN]] IP address, subnet mask, default gateway and DNS servers.
|-
|Host name
|class="code"|-n
|class="code"|an-m03.alteeve.ca
|Sets the host name of the Striker dashboard machine.
|-
|Dashboard Owner
|class="code"|-c
|class="code"|Alteeve's Niche!
|This sets the name used on the password prompt when connecting to the dashboard. It reflects the owner/manager of the dashboard and is usually a company or organization name.
|This is the email account user name and password that will be used later when sending alert emails from nodes.
|-
|Mail server details
|class="code"|-m
|class="code"|mail.example.com:587
|This is the mail server address and port that will be used later when sending alert emails from nodes. It is against this server that the user name and password defined in <span class="code">-e</span> will be used.
|-
|Striker user and password
|class="code"|-u
|class="code"|admin:another secret password
|This sets the user name and password that users will use when connecting to the dashboard. {{note|1=The password defined here will be used to set the <span class="code">root</span> user's password on the Striker dashboard itself. If you want these passwords to be different, please be sure to change it when the installer finished running.}}
|}
{{note|1=If you have already configured the network, please skip the <span class="code">-b</span> and <span class="code">-i</span> switches. If you have already configured the host name, please skip the <span class="code">-n</span> switch.}}
{{note|1=This is a standard <span class="code">[[bash]]</span> call, so please be sure to quote anything with spaces and to escape special characters like <span class="code">!</span>.}}
The monitor application is based around a "[[Striker API]]". The monitor itself acts as a daemon that calls scanner agents it finds inn the <span class="code">cgi-bin/scan.d</span> directory.
Warning: This is an in-progress document. Do not expect anything here to be accurate or correct. This warning will be removed when the guide is completed. You can track the progress on Striker's Github page.
It's goal is to reduce the potential for human errors causing availability interruptions by simplifying the interface as much as possible. With it, you can build, maintain and replace other dashboards and Anvil! nodes, as well as build Anvil!' systems from scratch.
Striker dashboards also act as a ScanCore database. Two or more Striker dashboards will work together to make the ScanCore data resilient by handling replication of the data and n-way resync automatically to update new or rebooted dashboards.
