mapsa/iem

Code that makes the Iowa Environmental Mesonet run, or run into the ground.

Iowa Environmental Mesonet

If using this code causes your server to have kittens, it is your own fault.

This monolith drives much of the ingest, processing, product generation, and web presence of the IEM. Hopefully it can be found useful for others to at least look at to see how some of the magic happens.

Limited integration testing is done on Travis-CI:

Where are processes running?!?

The processing load for the IEM is spread over a number of virtual machines. This is an attempt to document what is running where. The backup shown may not be automated, but another system that could be up and running the service in limited time.

Process	Primary	Backup	Monitor
Apache ErrorLog	iem12	None	None
hads-database	metvm4	None	check_hads_ingest.py
iembot	iem6	iem12	nagios checks for twistd processes running
LDM	iem12	None	None
LoggerNet	iem12	None	None
mailman	iem12	None	None
nwningest	iem12	None	cron scripts checks SNET sites for being online
openfire	iem12	None	None
postgres	metvm6	metvm9	None
samba	iem12	None	cron scripts check data availability
SSH	iem12	None	None
RIDGE	iem6	None	inbound file queue, check latency 7 radars
webalizer	iem13	None	None
Webcam Current	iem6	None	cron script monitors for offline webcams
Webcam Lapses	iem6	None	None