New IAC Wiki - User contributions [en]

Departure Notes - Curtis

2012-06-22T23:00:43Z

Buckminst: Created page with 'To-Do List DRBD documentation virt-install example for VM creation Finish "Edit User Groups" page migration to new layout. Migrate LDAP Administration website from darwin…'

To-Do List
DRBD documentation
virt-install example for VM creation
Finish "Edit User Groups" page migration to new layout.
Migrate LDAP Administration website from darwin to mcp

<pre>Server General Maintenance and Updates

[Hardware]
Server Name | Date Done | OS | Needs Reboot?
------------------------------------------------------------------------------
crick.iac.isu.edu | 06/05/2012 | Ubuntu 10.04 LTS |
watson.iac.isu.edu | 06/05/2012 | Ubuntu 10.04 LTS |
hal.iac.isu.edu | 06/05/2012 | Ubuntu 12.04 LTS |
darwin.iac.isu.edu | 06/05/2012 | Ubuntu 8.04 LTS |
backup.iac.isu.edu (cornwall) | 06/05/2012 | Ubuntu 12.04 LTS |
seattle.iac.isu.edu | 06/05/2012 | Ubuntu 10.04 LTS |
aztec.iac.isu.edu | 06/05/2012 | Ubuntu 10.04 LTS |
tesla.iac.isu.edu | 06/05/2012 | Ubuntu 10.04 LTS |
prague.iac.isu.edu | 06/05/2012 | Ubuntu 12.04 LTS |
pit.iac.isu.edu | 06/05/2012 | Ubuntu 12.04 LTS |
hindenburg.iac.isu.edu | 06/05/2012 | Ubuntu 12.04 LTS |
kludge.iac.isu.edu (87.65) | 06/08/2012 | Ubuntu 10.04 LTS |

[VMs]
Server Name | Date Done | OS | Needs Reboot?
------------------------------------------------------------------------------
codex.iac.isu.edu | 06/05/2012 | Ubuntu 10.04 LTS |
www.iac.isu.edu (choctaw) | 06/05/2012 | Ubuntu 10.04 LTS |
devsource.iac.isu.edu | 06/05/2012 | Ubuntu 12.04 LTS |
wiki.iac.isu.edu | 06/05/2012 | Ubuntu 10.04 LTS |
mcp.iac.isu.edu (3.99) | 06/05/2012 | Ubuntu 12.04 LTS |
#sandbox (xxx.xxx) | 10/17/2011 | Ubuntu 10.04 LTS |

[Tripwire]
Server Name | Date Done
-------------------------------------------
hal.iac.isu.edu | 04/11/2012
codex.iac.isu.edu | 10/17/2011
wiki.iac.isu.edu | 10/17/2011
devsource.iac.isu.edu | 10/17/2011
watson.iac.isu.edu | 04/11/2012
choctaw.iac.isu.edu | 10/17/2011
crick.iac.isu.edu | 04/11/2012

Server Security Update Checklist

Fail2ban
------------

Server Status
--------------------------------------------------------------
crick.iac.isu.edu Done
watson.iac.isu.edu Done
hal.iac.isu.edu Done
darwin.iac.isu.edu Done
cornwall.iac.isu.edu Done
brems.iac.isu.edu Done
seattle.iac.isu.edu Done
aztec.iac.isu.edu Done
tesla.iac.isu.edu Done
codex.iac.isu.edu Done
choctaw.iac.isu.edu Done
devsource.iac.isu.edu Done
wiki.iac.isu.edu Done

Firewalls
------------

Server Status
--------------------------------------------------------------
crick.iac.isu.edu Not Done
watson.iac.isu.edu Not Done
hal.iac.isu.edu Done
darwin.iac.isu.edu Done
cornwall.iac.isu.edu Done
brems.iac.isu.edu Done
seattle.iac.isu.edu Partially Done
aztec.iac.isu.edu Done
tesla.iac.isu.edu Done
codex.iac.isu.edu Done
choctaw.iac.isu.edu Done
devsource.iac.isu.edu Done
wiki.iac.isu.edu Done

Tripwire
------------

Server Status
--------------------------------------------------------------
wiki.iac.isu.edu Done
devsource.iac.isu.edu Done
hal.iac.isu.edu Done
crick.iac.isu.edu Done
watson.iac.isu.edu Done
choctaw.iac.isu.edu Done
codex.iac.isu.edu Done
- - - - - - - - - - - - - - - - - - - - -
darwin.iac.isu.edu Not Done
cornwall.iac.isu.edu Not Done
brems.iac.isu.edu Not Done
seattle.iac.isu.edu Not Done
aztec.iac.isu.edu Not Done
tesla.iac.isu.edu Not Done</pre>

Nerd Group

2012-06-22T22:57:03Z

Buckminst:

[[List of Current Issue]]

[[Airport Network Infrastructure]]

[[Network Problem Log]]

[[Group Meetings]]

[[IAC Network Configurations]]

[[ISU Policies]]

[[Mail Client Settings]]

[[Brems]]

[[Wiki Wishlist]]

[[Pulse Recording Ideas]]

[[Ludlum Rad Monitor Tunneling]]

[[Adding Apache Shares]]

[[LDAP Web Interface Wishlist]]

[[Departure Notes - Curtis]]

----

[[Newegg Wishlist]]

[[BackupPC Notes]]

[[New Mail Server]]

[[Monitoring Server]]

[[KVM Virtualization]]

[[Apt-Proxy]]

----

[https://mail.iac.isu.edu/squirrelmail/ IAC webmail]

Airport Network Infrastructure

2011-12-19T23:24:11Z

Buckminst: /* Hardware */

Proposed structure and hardware for IAC Airport facility, specifically for PITAS accelerator area.

=Structure=
External network access will be routed through a small Atom-based Linux server box which will handle floating and static IP DHCP requests.
* Server box has 2 network interfaces, 1 10/100 Fast Ethernet, 1 10/100/1000 Gigabit Ethernet
* External network will be connected to Fast Ethernet interface
* Internal network will be connected to Gigabit Ethernet interface

Internal network will be split into two zones:
* Control
* Accelerator

Internal network interface will be uplink for the ''Control'' network.

''Control'' network machines will be served by a Dell PowerConnect 5324 24-port Gigabit managed switch. This switch will have a fiber transceiver installed, providing electrical isolation for connection to the ''Accelerator'' network. Fiber will be 1000Base-SX with SC connectors.

''Accelerator'' network will be connected to the Control network via a TRENDnet Fiber Converter, which will serve as uplink for the Netgear ProSafe 16-port Gigabit unmanaged switch. All ''Accelerator'' network machines will be serviced by that switch.

=Hardware=
Proposed networking and server hardware is listed below, with itemized price breakdowns.

Total Implementation Cost: $757 before shipping

==Networking==
* Dell PowerConnect 5324 Gigabit Managed 24-port Ethernet Switch w/Fiber SFP ports (On hand)
* SFP Fiber Transceiver (1000Base-SX SC) - ACP SFPGE-11-AOK (http://www.newegg.com/Product/Product.aspx?Item=N82E16833516039) - $45
* Netgear ProSafe GS116 Gigabit Unmanaged 16-port Ethernet Switch (http://www.newegg.com/Product/Product.aspx?Item=N82E16833122139) - $155
* TRENDnet TFC-1000MSC Multi-Mode Fiber Converter (http://www.newegg.com/Product/Product.aspx?Item=N82E16833156017) - $132
* SC-connector Fiber cable - $150

Networking Hardware Cost: ~$482 before shipping

==Server==
* APEX MI-008 Mini-ITX Computer Case w/250W PSU (http://www.newegg.com/Product/Product.aspx?Item=N82E16811154091) - $40
* Intel BOXD525MW Atom D525 NM10 Mini-ITX Motherboard (http://www.newegg.com/Product/Product.aspx?Item=N82E16813121442) - $85
* Kingston 2GB 204-Pin DDR3-800 SO-DIMM Memory (http://www.newegg.com/Product/Product.aspx?Item=N82E16820139220) - $28 (2ea @ $14)
* OCZ Onyx Series 32GB SATA2 MLC SSD (http://www.newegg.com/Product/Product.aspx?Item=N82E16820227510) - $65
* ASUS DRW-24B1ST SATA 24x DVD Burner (http://www.newegg.com/Product/Product.aspx?Item=N82E16827135204) - $20

Server Hardware Cost: ~$275 before shipping

Airport Network Infrastructure

2011-12-19T23:19:38Z

Buckminst: Created page with 'Proposed structure and hardware for IAC Airport facility, specifically for PITAS accelerator area. =Structure= External network access will be routed through a small Atom-based …'

Proposed structure and hardware for IAC Airport facility, specifically for PITAS accelerator area.

=Structure=
External network access will be routed through a small Atom-based Linux server box which will handle floating and static IP DHCP requests.
* Server box has 2 network interfaces, 1 10/100 Fast Ethernet, 1 10/100/1000 Gigabit Ethernet
* External network will be connected to Fast Ethernet interface
* Internal network will be connected to Gigabit Ethernet interface

Internal network will be split into two zones:
* Control
* Accelerator

Internal network interface will be uplink for the ''Control'' network.

''Control'' network machines will be served by a Dell PowerConnect 5324 24-port Gigabit managed switch. This switch will have a fiber transceiver installed, providing electrical isolation for connection to the ''Accelerator'' network. Fiber will be 1000Base-SX with SC connectors.

''Accelerator'' network will be connected to the Control network via a TRENDnet Fiber Converter, which will serve as uplink for the Netgear ProSafe 16-port Gigabit unmanaged switch. All ''Accelerator'' network machines will be serviced by that switch.

=Hardware=
Proposed networking and server hardware is listed below, with itemized price breakdowns.

Total Implementation Cost: $757

==Networking==
* Dell PowerConnect 5324 Gigabit Managed 24-port Ethernet Switch w/Fiber SFP ports (On hand)
* SFD Fiber Transceiver (1000Base-SX SC) - ACP SFPGE-11-AOK (http://www.newegg.com/Product/Product.aspx?Item=N82E16833516039) - $45
* Netgear ProSafe GS116 Gigabit Unmanaged 16-port Ethernet Switch (http://www.newegg.com/Product/Product.aspx?Item=N82E16833122139) - $155
* TRENDnet TFC-1000MSC Multi-Mode Fiber Converter (http://www.newegg.com/Product/Product.aspx?Item=N82E16833156017) - $132
* SC-connector Fiber cable - $150

Networking Hardware Cost: ~$482 before shipping

==Server==
* APEX MI-008 Mini-ITX Computer Case w/250W PSU (http://www.newegg.com/Product/Product.aspx?Item=N82E16811154091) - $40
* Intel BOXD525MW Atom D525 NM10 Mini-ITX Motherboard (http://www.newegg.com/Product/Product.aspx?Item=N82E16813121442) - $85
* Kingston 2GB 204-Pin DDR3-800 SO-DIMM Memory (http://www.newegg.com/Product/Product.aspx?Item=N82E16820139220) - $28 (2ea @ $14)
* OCZ Onyx Series 32GB SATA2 MLC SSD (http://www.newegg.com/Product/Product.aspx?Item=N82E16820227510) - $65
* ASUS DRW-24B1ST SATA 24x DVD Burner (http://www.newegg.com/Product/Product.aspx?Item=N82E16827135204) - $20

Server Hardware Cost: ~$275 before shipping

Nerd Group

2011-12-19T22:48:26Z

Buckminst:

[[List of Current Issue]]

[[Airport Network Infrastructure]]

[[Network Problem Log]]

[[Group Meetings]]

[[IAC Network Configurations]]

[[ISU Policies]]

[[Mail Client Settings]]

[[Brems]]

[[Wiki Wishlist]]

[[Pulse Recording Ideas]]

[[Ludlum Rad Monitor Tunneling]]

[[Adding Apache Shares]]

[[LDAP Web Interface Wishlist]]

----

[[Newegg Wishlist]]

[[BackupPC Notes]]

[[New Mail Server]]

[[Monitoring Server]]

[[KVM Virtualization]]

[[Apt-Proxy]]

----

[https://mail.iac.isu.edu/squirrelmail/ IAC webmail]

Radiation Monitor Python Script Documentation

2011-03-09T20:02:14Z

Buckminst: /* reload_configuration */

The Radiation Monitor Python script is a DBus-enabled UDP forwarding and reporting script designed to interpret and rebroadcast the information provided by the Ludlum Measurement Inc. 375-9 series Radiation Monitors in use at the IAC and in the ISU Physics building. It utilizes the common ''iac.nagios.'' DBus service and ''/IAC/Nagios/'' service path for statistic reporting to the IAC [[Monitoring_Server|Nagios]] server.
=Configuration And Use=
Before first execution, the following directories will need to be created, with proper permissions for the ''nagios'' user to write to them:
* ''/var/log/iac''
* ''/etc/iac''
These directories will be common for the Radiation Monitoring script as well as the Cluster Room Temperature Monitor script.

Once ''/etc/iac'' exists, you will need to create the ''rad_monitors.cfg'' configuration file within that directory.
The configuration file syntax is described below.

The Radiation Monitor script, if called without a configuration file, uses the following defaults:
* '''Local Address:''' ''None''
* '''Listen Address:''' ''255.255.255.255''
* '''Listen Port:''' ''55555''
* '''Verbose Mode (Non-Daemon):''' ''False''
* '''Debug Mode:''' ''False''
* '''Daemon Mode:''' ''True''
* '''Log Mode:''' ''Append''
* '''Send Clients:''' ''None''

The command to start the Radiation Monitoring script is simply ''rad_monitors.py''. This script will need to be ran by the ''nagios'' user.
==Configuration File==
'''Example Configuration File'''
#local:134.50.87.179:55554
listen:255.255.255.255:55555
sendto:127.0.0.1:54321
#sendto:134.50.87.179:54321
#verbose
#debug
noforward
#nodaemon
#truncate

Lines beginning with # are ignored by the script and may be used for comments on lines seperate from directive lines, or to remove directives from active use. For comments on lines containing directives, please place them at the end and prepend a : before the comment.
===Configuration Directives===
====local====
This directive will allow you to bind to a specific IP address/interface and port number for purposes of UDP packet source information. By default the program will choose whichever interface is needed to talk to the send clients, as well as a random high port. The proper syntax for this directive is as follows:
'''local''':''local_ip'':''local_port''
This directive cannot be changed during run-time.
====listen====
This directive will allow you to specify what interface/IP address and port to listen for packets on. By default this is set for UDP broadcasts on ''255.255.255.255''. The proper syntax for this directive is as follows:
'''listen''':''listen_ip'':''listen_port''
This directive cannot be changed during run-time.

====sendto====
This directive will allow you to specify any number of clients to forward the UDP packets on to, one per directive line. The proper syntax for this directive is as follows:
'''sendto''':''target_ip'':''target_port''
Additional send clients can be added while the script is running by sending SIGHUP or using the DBus ''reload_configuration'' method to reload the configuration file, or by using the DBus ''add_send_client'' method.

====verbose====
This directive sets the Radiation Monitor script into verbose interactive mode (non-daemonized), for the purposes of examining packet flow and diagnostics. This directive needs no arguments and can simply be specified in the configuration file.

This directive cannot be changed during run-time.
====debug====
This directive sets the Radiation Monitor script into a further debugging mode, for program flow and diagnostic purposes.

This directive can be changed during run-time by sending SIGHUP or using the DBus ''reload_configuration'' method to reload the configuration file.
====noforward====
This directive disables packet forwarding for the Radiation Monitor. This can be useful if you wish to run the script just for listening purposes, or for troubleshooting.

This directive can be changed during run-time by sending SIGHUP or using the DBus ''reload_configuration'' method to reload the configuration file.
====nodaemon====
This directive sets the Radiation Monitor script to run in interactive (non-daemonized) mode, but without verbose output. This can be useful for troubleshooting purposes or if you wish to run the process in a
screen session.

This directive cannot be changed during run-time.
====truncate====
This directive requires the Radiation Monitor script to clear its log file at each session start, rather than appending (the default log method).

This directive cannot be changed during run-time.

=API=
==DBus Quick Reference==
'''Service Bus''': ''SystemBus()''

'''Service Name''': ''iac.nagios.radmonitors''

'''Service Path''': ''/IAC/Nagios/RadMonitors''

'''Exposed Methods'''
'''get_active_channels()'''
'''get_active_monitors()'''
'''get_active_monitor_count()'''
'''get_radiation_levels()'''
'''add_send_client('''''string''''')'''
'''reload_configuration()'''

==DBus Interaction==
Before you can interact with the Radiation Monitor's DBus service, you will need to load some prerequisite Python libraries:
import dbus
This is the minimum to connect to DBus. If you wish to do more than connect as a client, you will need to load the following libraries:
import dbus.service, gobject
from dbus import glib
It is also recommend that you initialize threading now if you are planning on performing threaded tasks:
gobject.threads_init()
glib.init_threads()
===Connecting to the Radiation Monitor DBus service===
To interact with the Radiation Monitor DBus service in Python, you will first need to connect to the DBus System bus:
''dbus_bus'' = '''dbus.SystemBus()'''
'''Note:''' The Radiation Monitor script must be run as ''root'' to connect to the System bus.

Once you have successfully connected to the System bus, you will then want to get the DBus service object for the Radiation Monitor. This is done via the '''get_object''' bus method:
''dbus_object'' = ''dbus_bus''.'''get_object('''''service_name'', ''service_path''''')'''
For our Radiation Monitor interface, the proper invocation is as follows:
''dbus_object'' = ''dbus_bus''.'''get_object('''''"iac.nagios.radmonitors"'', ''"/IAC/Nagios/RadMonitors"''''')'''
After this is done, you may choose to call the Radiation Monitor's DBus methods either through the service object itself, or you may create references to specific methods for use:
''dbus_method_ref'' = ''dbus_object''.'''get_dbus_method('''''method'', ''service_name''''')'''
Example:
>>> remote_method = remote_object.get_dbus_method('get_active_monitor_count', 'iac.nagios.radmonitors')
>>> remote_method()
dbus.Int32(7)

===Introspection Schema===
The Radiation Monitor DBus service returns the following schema upon being called with its inherited Introspect() method:
<!DOCTYPE node PUBLIC "-//freedesktop//DTD D-BUS Object Introspection 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd">
<node name="/IAC/Nagios/RadMonitors">
<interface name="iac.nagios.radmonitors">
<method name="reload_configuration">
</method>
<method name="get_active_monitors">
</method>
<method name="get_active_monitor_count">
</method>
<method name="add_send_client">
<arg direction="in" type="v" name="new_client" />
</method>
<method name="get_radiation_levels">
</method>
<method name="get_active_channels">
</method>
</interface>
<interface name="org.freedesktop.DBus.Introspectable">
<method name="Introspect">
<arg direction="out" type="s" />
</method>
</interface>
</node>
===Methods===
====get_active_channels====
This exposed DBus method will return a dbus.Array value representing the active channels the script sees. It is invoked in the following manner:
''dbus_object''.'''get_active_channels()'''
Example output:
>>> remote_object.get_active_channels()
dbus.Array([dbus.Int32(1), dbus.Int32(2), dbus.Int32(3), dbus.Int32(4), dbus.Int32(5), dbus.Int32(6), dbus.Int32(7)], signature=dbus.Signature('i'))
====get_active_monitors====
This exposed DBus method will return a dbus.Array value representing the IP address of all radiation monitors the script sees. It is invoked in the following manner:
''dbus_object''.'''get_active_monitors()'''
Example output:
>>> remote_object.get_active_monitors()
dbus.Array([dbus.String(u'192.168.40.155'), dbus.String(u'192.168.40.154'), dbus.String(u'192.168.40.121'), dbus.String(u'192.168.40.172'),
dbus.String(u'192.168.40.137'), dbus.String(u'192.168.40.159'), dbus.String(u'192.168.40.120')], signature=dbus.Signature('s'))
====get_active_monitor_count====
This exposed DBus method will return a dbus.Int32 value representing the total number of active monitors the script sees. It is invoked in the following manner:
''dbus_object''.'''get_active_monitor_count()'''
Example output:
>>> remote_object.get_active_monitor_count()
dbus.Int32(7)
====get_radiation_levels====
This exposed DBus method will return a dbus.Array value representing the current radiation level of all monitors the script sees. It is invoked in the following manner:
''dbus_object''.'''get_radiation_levels()'''
Example output:
>>> remote_object.get_radiation_levels()
dbus.Array([dbus.String(u'0.0'), dbus.String(u'0.0'), dbus.String(u'0.0'), dbus.String(u'0.0'), dbus.String(u'0.1'), dbus.String(u'0.1'),
dbus.String(u'0.1')], signature=dbus.Signature('s'))
====add_send_client====
This exposed DBus method will add a new send target client to a running instance of the script, allowing for on-the-fly addition of targets without restarting. It is invoked in the following manner:
''dbus_object''.'''add_send_client(''string'')'''
Where ''string'' is a string containing the IP address and destination port number of the send target, formatted as "''ip'':''port''".
The function returns a dbus.Boolean value; ''True'' if the add is successful, ''False'' if not.

'''Note:''' This only adds the new send client to the in-memory send list. If you wish to retain this send client for future use, you will need to edit the configuration file and add
the appropriate ''sendto'' directive for that client.

Example output:
>>> remote_object.add_send_client("134.50.87.179:55555")
dbus.Boolean(True)

====reload_configuration====
This exposed DBus method will cause a running instance of the script to reload its configuration file, as if having been sent signal SIGHUP. It is invoked in the following manner:
''dbus_object''.'''reload_configuration()'''
The function always returns dbus.Boolean ''True'' at this time.

Example output:
>>> remote_object.reload_configuration()
dbus.Boolean(True)

Monitoring Server

2011-03-07T21:14:16Z

Buckminst: /* Physical Science */

The '''IAC monitoring server''' can be found at http://hal.iac.isu.edu/nagios3/

=Monitored Systems and Services=

==Systems & Services Chart==
{| class="wikitable" border="1" style="font-size: x-small;"
|+ Systems and Services Currently Monitored
! System Name !! CPU Temp !! CPU Usage !! Current Load !! # Users !! DRBD !! Disk Space !! HDD Temp !! Heartbeat !! LDAP !! Memory !! # Network Connections !! Network I/O !! RAID !! SMART !! SSH !! # Processes !! HTTP !! MySQL !! Samba !! System Temperature !! PSU !! PING !! Other
|-
! Alan's Desktop
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}}ne
|-
! aztec.iac.isu.edu
| {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}}ne
|-
! brems.iac.isu.edu
| {{no}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || Averaging Test, Cluster Room Temperatures, Slurm Queue, Slave Nodes
|-
! cleanroom.temperatures
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || Clean Room Temperatures
|-
! codex.iac.isu.edu
| {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}}ne
|-
! cornwall.iac.isu.edu
| {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}}ne
|-
! crick.iac.isu.edu
| {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}}ne
|-
! darwin.iac.isu.edu
| {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}}ne
|-
! devsource.iac.isu.edu
| {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}}ne
|-
! iac-gateway
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}}ne
|-
! license.iac.isu.edu
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}}ne
|-
! hal.iac.isu.edu
| {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || Radiation Monitors
|-
! physics-gateway
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}}ne
|-
! seattle.iac.isu.edu
| {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || Radiation Monitors
|-
! tesla.iac.isu.edu
| {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}}ne
|-
! watson.iac.isu.edu
| {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}}ne
|-
! wiki.iac.isu.edu
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}}ne
|-
! vienna.iac.isu.edu
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}}ne
|}

==Systems Monitored (By Building)==

===Physical Science===
* physics-gateway
* aztec.iac.isu.edu
* brems.iac.isu.edu
* brems slave nodes
* cleanroom.temperatures
* codex.iac.isu.edu
* cornwall.iac.isu.edu
* crick.iac.isu.edu
* darwin.iac.isu.edu
* devsource.iac.isu.edu
* hal.iac.isu.edu
* tesla.iac.isu.edu
* watson.iac.isu.edu
* wiki.iac.isu.edu
* vienna.iac.isu.edu

===Idaho Accelerator Center===
* iac-gateway
* alans-desktop
* license.iac.isu.edu
* seattle.iac.isu.edu

==Systems to Monitor==
*Slave nodes (partial)
*Webserver
*Backup server

Radiation Monitor Python Script Documentation

2011-03-07T21:12:50Z

Buckminst: /* Connecting to the Radiation Monitor DBus service */

The Radiation Monitor Python script is a DBus-enabled UDP forwarding and reporting script designed to interpret and rebroadcast the information provided by the Ludlum Measurement Inc. 375-9 series Radiation Monitors in use at the IAC and in the ISU Physics building. It utilizes the common ''iac.nagios.'' DBus service and ''/IAC/Nagios/'' service path for statistic reporting to the IAC [[Monitoring_Server|Nagios]] server.
=Configuration And Use=
Before first execution, the following directories will need to be created, with proper permissions for the ''nagios'' user to write to them:
* ''/var/log/iac''
* ''/etc/iac''
These directories will be common for the Radiation Monitoring script as well as the Cluster Room Temperature Monitor script.

Once ''/etc/iac'' exists, you will need to create the ''rad_monitors.cfg'' configuration file within that directory.
The configuration file syntax is described below.

The Radiation Monitor script, if called without a configuration file, uses the following defaults:
* '''Local Address:''' ''None''
* '''Listen Address:''' ''255.255.255.255''
* '''Listen Port:''' ''55555''
* '''Verbose Mode (Non-Daemon):''' ''False''
* '''Debug Mode:''' ''False''
* '''Daemon Mode:''' ''True''
* '''Log Mode:''' ''Append''
* '''Send Clients:''' ''None''

The command to start the Radiation Monitoring script is simply ''rad_monitors.py''. This script will need to be ran by the ''nagios'' user.
==Configuration File==
'''Example Configuration File'''
#local:134.50.87.179:55554
listen:255.255.255.255:55555
sendto:127.0.0.1:54321
#sendto:134.50.87.179:54321
#verbose
#debug
noforward
#nodaemon
#truncate

Lines beginning with # are ignored by the script and may be used for comments on lines seperate from directive lines, or to remove directives from active use. For comments on lines containing directives, please place them at the end and prepend a : before the comment.
===Configuration Directives===
====local====
This directive will allow you to bind to a specific IP address/interface and port number for purposes of UDP packet source information. By default the program will choose whichever interface is needed to talk to the send clients, as well as a random high port. The proper syntax for this directive is as follows:
'''local''':''local_ip'':''local_port''
This directive cannot be changed during run-time.
====listen====
This directive will allow you to specify what interface/IP address and port to listen for packets on. By default this is set for UDP broadcasts on ''255.255.255.255''. The proper syntax for this directive is as follows:
'''listen''':''listen_ip'':''listen_port''
This directive cannot be changed during run-time.

====sendto====
This directive will allow you to specify any number of clients to forward the UDP packets on to, one per directive line. The proper syntax for this directive is as follows:
'''sendto''':''target_ip'':''target_port''
Additional send clients can be added while the script is running by sending SIGHUP or using the DBus ''reload_configuration'' method to reload the configuration file, or by using the DBus ''add_send_client'' method.

====verbose====
This directive sets the Radiation Monitor script into verbose interactive mode (non-daemonized), for the purposes of examining packet flow and diagnostics. This directive needs no arguments and can simply be specified in the configuration file.

This directive cannot be changed during run-time.
====debug====
This directive sets the Radiation Monitor script into a further debugging mode, for program flow and diagnostic purposes.

This directive can be changed during run-time by sending SIGHUP or using the DBus ''reload_configuration'' method to reload the configuration file.
====noforward====
This directive disables packet forwarding for the Radiation Monitor. This can be useful if you wish to run the script just for listening purposes, or for troubleshooting.

This directive can be changed during run-time by sending SIGHUP or using the DBus ''reload_configuration'' method to reload the configuration file.
====nodaemon====
This directive sets the Radiation Monitor script to run in interactive (non-daemonized) mode, but without verbose output. This can be useful for troubleshooting purposes or if you wish to run the process in a
screen session.

This directive cannot be changed during run-time.
====truncate====
This directive requires the Radiation Monitor script to clear its log file at each session start, rather than appending (the default log method).

This directive cannot be changed during run-time.

=API=
==DBus Quick Reference==
'''Service Bus''': ''SystemBus()''

'''Service Name''': ''iac.nagios.radmonitors''

'''Service Path''': ''/IAC/Nagios/RadMonitors''

'''Exposed Methods'''
'''get_active_channels()'''
'''get_active_monitors()'''
'''get_active_monitor_count()'''
'''get_radiation_levels()'''
'''add_send_client('''''string''''')'''
'''reload_configuration()'''

==DBus Interaction==
Before you can interact with the Radiation Monitor's DBus service, you will need to load some prerequisite Python libraries:
import dbus
This is the minimum to connect to DBus. If you wish to do more than connect as a client, you will need to load the following libraries:
import dbus.service, gobject
from dbus import glib
It is also recommend that you initialize threading now if you are planning on performing threaded tasks:
gobject.threads_init()
glib.init_threads()
===Connecting to the Radiation Monitor DBus service===
To interact with the Radiation Monitor DBus service in Python, you will first need to connect to the DBus System bus:
''dbus_bus'' = '''dbus.SystemBus()'''
'''Note:''' The Radiation Monitor script must be run as ''root'' to connect to the System bus.

Once you have successfully connected to the System bus, you will then want to get the DBus service object for the Radiation Monitor. This is done via the '''get_object''' bus method:
''dbus_object'' = ''dbus_bus''.'''get_object('''''service_name'', ''service_path''''')'''
For our Radiation Monitor interface, the proper invocation is as follows:
''dbus_object'' = ''dbus_bus''.'''get_object('''''"iac.nagios.radmonitors"'', ''"/IAC/Nagios/RadMonitors"''''')'''
After this is done, you may choose to call the Radiation Monitor's DBus methods either through the service object itself, or you may create references to specific methods for use:
''dbus_method_ref'' = ''dbus_object''.'''get_dbus_method('''''method'', ''service_name''''')'''
Example:
>>> remote_method = remote_object.get_dbus_method('get_active_monitor_count', 'iac.nagios.radmonitors')
>>> remote_method()
dbus.Int32(7)

===Introspection Schema===
The Radiation Monitor DBus service returns the following schema upon being called with its inherited Introspect() method:
<!DOCTYPE node PUBLIC "-//freedesktop//DTD D-BUS Object Introspection 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd">
<node name="/IAC/Nagios/RadMonitors">
<interface name="iac.nagios.radmonitors">
<method name="reload_configuration">
</method>
<method name="get_active_monitors">
</method>
<method name="get_active_monitor_count">
</method>
<method name="add_send_client">
<arg direction="in" type="v" name="new_client" />
</method>
<method name="get_radiation_levels">
</method>
<method name="get_active_channels">
</method>
</interface>
<interface name="org.freedesktop.DBus.Introspectable">
<method name="Introspect">
<arg direction="out" type="s" />
</method>
</interface>
</node>
===Methods===
====get_active_channels====
This exposed DBus method will return a dbus.Array value representing the active channels the script sees. It is invoked in the following manner:
''dbus_object''.'''get_active_channels()'''
Example output:
>>> remote_object.get_active_channels()
dbus.Array([dbus.Int32(1), dbus.Int32(2), dbus.Int32(3), dbus.Int32(4), dbus.Int32(5), dbus.Int32(6), dbus.Int32(7)], signature=dbus.Signature('i'))
====get_active_monitors====
This exposed DBus method will return a dbus.Array value representing the IP address of all radiation monitors the script sees. It is invoked in the following manner:
''dbus_object''.'''get_active_monitors()'''
Example output:
>>> remote_object.get_active_monitors()
dbus.Array([dbus.String(u'192.168.40.155'), dbus.String(u'192.168.40.154'), dbus.String(u'192.168.40.121'), dbus.String(u'192.168.40.172'),
dbus.String(u'192.168.40.137'), dbus.String(u'192.168.40.159'), dbus.String(u'192.168.40.120')], signature=dbus.Signature('s'))
====get_active_monitor_count====
This exposed DBus method will return a dbus.Int32 value representing the total number of active monitors the script sees. It is invoked in the following manner:
''dbus_object''.'''get_active_monitor_count()'''
Example output:
>>> remote_object.get_active_monitor_count()
dbus.Int32(7)
====get_radiation_levels====
This exposed DBus method will return a dbus.Array value representing the current radiation level of all monitors the script sees. It is invoked in the following manner:
''dbus_object''.'''get_radiation_levels()'''
Example output:
>>> remote_object.get_radiation_levels()
dbus.Array([dbus.String(u'0.0'), dbus.String(u'0.0'), dbus.String(u'0.0'), dbus.String(u'0.0'), dbus.String(u'0.1'), dbus.String(u'0.1'),
dbus.String(u'0.1')], signature=dbus.Signature('s'))
====add_send_client====
This exposed DBus method will add a new send target client to a running instance of the script, allowing for on-the-fly addition of targets without restarting. It is invoked in the following manner:
''dbus_object''.'''add_send_client(''string'')'''
Where ''string'' is a string containing the IP address and destination port number of the send target, formatted as "''ip'':''port''".
The function returns a dbus.Boolean value; ''True'' if the add is successful, ''False'' if not.

'''Note:''' This only adds the new send client to the in-memory send list. If you wish to retain this send client for future use, you will need to edit the configuration file and add
the appropriate ''sendto'' directive for that client.

Example output:
>>> remote_object.add_send_client("134.50.87.179:55555")
dbus.Boolean(True)

====reload_configuration====
This exposed DBus method will cause a running instance of the script to reload its configuration file, as if having been sent signal SIGHUP. It is invoked in the following manner:
''dbus_object''.'''reload_configuration()'''
Then function always returns dbus.Boolean ''True'' at this time.

Example output:
>>> remote_object.reload_configuration()
dbus.Boolean(True)

Monitoring Server

2011-02-15T01:05:51Z

Buckminst: Inca has been retired.

The '''IAC monitoring server''' can be found at http://hal.iac.isu.edu/nagios3/

=Monitored Systems and Services=

==Systems & Services Chart==
{| class="wikitable" border="1" style="font-size: x-small;"
|+ Systems and Services Currently Monitored
! System Name !! CPU Temp !! CPU Usage !! Current Load !! # Users !! DRBD !! Disk Space !! HDD Temp !! Heartbeat !! LDAP !! Memory !! # Network Connections !! Network I/O !! RAID !! SMART !! SSH !! # Processes !! HTTP !! MySQL !! Samba !! System Temperature !! PSU !! PING !! Other
|-
! Alan's Desktop
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}}ne
|-
! aztec.iac.isu.edu
| {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}}ne
|-
! brems.iac.isu.edu
| {{no}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || Averaging Test, Cluster Room Temperatures, Slurm Queue, Slave Nodes
|-
! cleanroom.temperatures
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || Clean Room Temperatures
|-
! codex.iac.isu.edu
| {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}}ne
|-
! cornwall.iac.isu.edu
| {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}}ne
|-
! crick.iac.isu.edu
| {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}}ne
|-
! darwin.iac.isu.edu
| {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}}ne
|-
! devsource.iac.isu.edu
| {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}}ne
|-
! iac-gateway
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}}ne
|-
! license.iac.isu.edu
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}}ne
|-
! hal.iac.isu.edu
| {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || Radiation Monitors
|-
! physics-gateway
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}}ne
|-
! seattle.iac.isu.edu
| {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || Radiation Monitors
|-
! tesla.iac.isu.edu
| {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}}ne
|-
! watson.iac.isu.edu
| {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{yes}} || {{no}} || {{no}}ne
|-
! wiki.iac.isu.edu
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}} || {{yes}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}}ne
|-
! vienna.iac.isu.edu
| {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{no}} || {{yes}} || {{no}}ne
|}

==Systems Monitored (By Building)==

===Physical Science===
* physics-gateway
* aztec.iac.isu.edu
* brems.iac.isu.edu
* brems slave nodes
* cleanroom.temperatures
* codex.iac.isu.edu
* cornwall.iac.isu.edu
* crick.iac.isu.edu
* darwin.iac.isu.edu
* devsource.iac.isu.edu
* hal.iac.isu.edu
* inca.iac.isu.edu
* tesla.iac.isu.edu
* watson.iac.isu.edu
* wiki.iac.isu.edu
* vienna.iac.isu.edu

===Idaho Accelerator Center===
* iac-gateway
* alans-desktop
* license.iac.isu.edu
* seattle.iac.isu.edu

==Systems to Monitor==
*Slave nodes (partial)
*Webserver
*Backup server

MediaWiki:Sitenotice

2010-12-31T02:20:06Z

Buckminst:

== The IAC Wiki has been migrated to a new server. Wiki user accounts now use the IAC Single Sign-On system (used by IAC email, etc). If you do not already have an IAC Single Sign-On username, request an account [https://mail.iac.isu.edu/glados/glados-submitrequest.php here]. You will need to request the account from an on-campus computer. If you have information on your old user talk pages you need transferred, let Brian or Curtis know. ==

MediaWiki:Sitenotice

2010-12-31T02:16:32Z

Buckminst: /* The IAC Wiki has been migrated to a new server. Wiki user accounts now use the IAC Single Sign-On system (used by IAC email, etc). If you do not already have an IAC Single Sign-On username, request an account here. You will need to request the acc

2010-09-14T07:46:48Z

Buckminst: Protected "Radiation Monitor Python Script Documentation" ([edit=comp] (indefinite) [move=comp] (indefinite) [read=comp] (indefinite))

=Configuration And Use=
==Configuration File==
'''Example Configuration File'''
#local:134.50.87.179:55554
listen:255.255.255.255:55555
sendto:127.0.0.1:54321
#sendto:134.50.87.179:54321
#verbose
#debug
noforward
#nodaemon
#truncate
===Configuration Directives===
====local====
====listen====
====sendto====
====verbose====
====debug====
====noforward====
====nodaemon====
====truncate====
=API=
==DBus Quick Reference==
'''Service Bus''': ''SessionBus()''

'''Service Name''': ''iac.nagios.radmonitors''

'''Service Path''': ''/IAC/Nagios/RadMonitors''

'''Exposed Methods'''
'''get_active_channels()'''
'''get_active_monitors()'''
'''get_active_monitor_count()'''
'''get_radiation_levels()'''
'''add_send_client('''''string''''')'''
'''reload_configuration()'''
==DBus Interaction==
Before you can interact with the Radiation Monitor's DBus service, you will need to load some prerequisite Python libraries:
import dbus
This is the minimum to connect to DBus. If you wish to do more than connect as a client, you will need to load the following libraries:
import dbus.service, gobject
from dbus import glib
It is also recommend that you initialize threading now if you are planning on performing threaded tasks:
gobject.threads_init()
glib.init_threads()
===Connecting to the Radiation Monitor DBus service===
To interact with the Radiation Monitor DBus service in Python, you will first need to connect to the DBus Session bus:
''dbus_bus'' = '''dbus.SessionBus()'''
Once you have successfully connected to the session bus, you will then want to get the DBus service object for the Radiation Monitor. This is done via the '''get_object''' bus method:
''dbus_object'' = ''dbus_bus''.'''get_object('''''service_name'', ''service_path''''')'''
For our Radiation Monitor interface, the proper invocation is as follows:
''dbus_object'' = ''dbus_bus''.'''get_object('''''"iac.nagios.radmonitors"'', ''"/IAC/Nagios/RadMonitors"''''')'''
After this is done, you may choose to call the Radiation Monitor's DBus methods either through the service object itself, or you may create references to specific methods for use:
''dbus_method_ref'' = ''dbus_object''.'''get_dbus_method('''''method'', ''service_name''''')'''
Example:
>>> remote_method = remote_object.get_dbus_method('get_active_monitor_count', 'iac.nagios.radmonitors')
>>> remote_method()
dbus.Int32(7)
===Introspection Schema===
The Radiation Monitor DBus service returns the following schema upon being called with its inherited Introspect() method:
<!DOCTYPE node PUBLIC "-//freedesktop//DTD D-BUS Object Introspection 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd">
<node name="/IAC/Nagios/RadMonitors">
<interface name="iac.nagios.radmonitors">
<method name="reload_configuration">
</method>
<method name="get_active_monitors">
</method>
<method name="get_active_monitor_count">
</method>
<method name="add_send_client">
<arg direction="in" type="v" name="new_client" />
</method>
<method name="get_radiation_levels">
</method>
<method name="get_active_channels">
</method>
</interface>
<interface name="org.freedesktop.DBus.Introspectable">
<method name="Introspect">
<arg direction="out" type="s" />
</method>
</interface>
</node>
===Methods===
====get_active_channels====
This exposed DBus method will return a dbus.Array value representing the active channels the script sees. It is invoked in the following manner:
''dbus_object''.'''get_active_channels()'''
Example output:
>>> remote_object.get_active_channels()
dbus.Array([dbus.Int32(1), dbus.Int32(2), dbus.Int32(3), dbus.Int32(4), dbus.Int32(5), dbus.Int32(6), dbus.Int32(7)], signature=dbus.Signature('i'))
====get_active_monitors====
This exposed DBus method will return a dbus.Array value representing the IP address of all radiation monitors the script sees. It is invoked in the following manner:
''dbus_object''.'''get_active_monitors()'''
Example output:
>>> remote_object.get_active_monitors()
dbus.Array([dbus.String(u'192.168.40.155'), dbus.String(u'192.168.40.154'), dbus.String(u'192.168.40.121'), dbus.String(u'192.168.40.172'),
dbus.String(u'192.168.40.137'), dbus.String(u'192.168.40.159'), dbus.String(u'192.168.40.120')], signature=dbus.Signature('s'))
====get_active_monitor_count====
This exposed DBus method will return a dbus.Int32 value representing the total number of active monitors the script sees. It is invoked in the following manner:
''dbus_object''.'''get_active_monitor_count()'''
Example output:
>>> remote_object.get_active_monitor_count()
dbus.Int32(7)
====get_radiation_levels====
This exposed DBus method will return a dbus.Array value representing the current radiation level of all monitors the script sees. It is invoked in the following manner:
''dbus_object''.'''get_radiation_levels()'''
Example output:
>>> remote_object.get_radiation_levels()
dbus.Array([dbus.String(u'0.0'), dbus.String(u'0.0'), dbus.String(u'0.0'), dbus.String(u'0.0'), dbus.String(u'0.1'), dbus.String(u'0.1'),
dbus.String(u'0.1')], signature=dbus.Signature('s'))
====add_send_client====
This exposed DBus method will add a new send target client to a running instance of the script, allowing for on-the-fly addition of targets without restarting. It is invoked in the following manner:
''dbus_object''.'''add_send_client(''string'')'''
Where ''string'' is a string containing the IP address and destination port number of the send target, formatted as "''ip'':''port''".
The function returns a dbus.Boolean value; ''True'' if the add is successful, ''False'' if not.

'''Note:''' This only adds the new send client to the in-memory send list. If you wish to retain this send client for future use, you will need to edit the configuration file and add
the appropriate ''sendto'' directive for that client.

Example output:
>>> remote_object.add_send_client("134.50.87.179:55555")
dbus.Boolean(True)

====reload_configuration====
This exposed DBus method will cause a running instance of the script to reload its configuration file, as if having been sent signal SIGHUP. It is invoked in the following manner:
''dbus_object''.'''reload_configuration()'''
Then function always returns dbus.Boolean ''True'' at this time.

Example output:
>>> remote_object.reload_configuration()
dbus.Boolean(True)

Buckminst: Created page with '<noinclude>{| class="wikitable" |- |</noinclude>style="background: #90ff90; color: black; vertical-align: middle; text-align: {{{align|center}}}; {{{style|}}}" class="table-yes"|...'

<noinclude>{| class="wikitable"
|-
|</noinclude>style="background: #90ff90; color: black; vertical-align: middle; text-align: {{{align|center}}}; {{{style|}}}" class="table-yes"|{{{1|Yes}}}<noinclude>
|}
{{documentation}}
</noinclude>