2008-04-05 23:27:56

Downtime communications database ...

Yet another little "somethin' somethin'" I've been putting together in my spare time is a downtimes communications database and web portal for declaring downtimes based on servers, clusters, regions, processes, etc. I know there's quite a few products out there already that can do this, but ... 'eh, this is what I do for fun.

The premise is pretty simple ... my company is all about data. It's a market research company, so if you don't have the data, you don't have a product to sell, in a nutshell. This means that any sort of downtimes impacting the availability of data access has to be minimized as much as possible.

The problem, of course, is the complex issue of data ownership. Who is responsible for what data, and needs to be informed of downtimes. By utilizing a communications manager, you can centralize the communications and focus them away from the engineers performing the work. A comms manager, however, doesn't necessarily have the information regarding data ownership for the impacted services. This situation is further exacerbated by phenomenal growth, introducing new data owners at a very high rate.

In this scenario, you need a normalized database with a high grade of referential integrity, linking servers, services, downtime coordinators, communication managers, clusters, regions, and so forth, together into an easy to manipulate fabric.

For this particular project, I chose fairly standard tools ... Python, MySQL and Apache. The Apache/Python interface allows you to select the type of downtime reports that you want to generate. At the moment, it prints out a simple HTML page with all of the requisite data owner and coordinator information, however, the next iteration of the project will include PDF files. The goal is to produce an output which can be attached to Change Management documentation, and included as part of the official change process.

I love this stuff!

Tags:   web, python     |    Perm Link:   Downtime communications database ...

2007-08-24 10:47:12

Enabling Apache to exec python code

In the httpd.conf file, add the following line in the "AddHandler" area:

AddHandler cgi-script .py

If your index page is going to be a .py file, be sure to also include an index.py in your DirectoryIndex line, as well.

Tags:   python, web     |    Perm Link:   Enabling Apache to exec python code

2007-08-08 12:16:13

Create a dropdown form that changes automatically (HTML, JavaScript)

In the "select" tag of your form, add the following value:


Tags:   web     |    Perm Link:   Create a dropdown form that changes automatically (HTML, JavaScript)

2007-08-07 14:22:41

Import self signed cert into IE 6 and 7

Locate the cert or crt file on the webserver. In the case of this server, it is:

Once you access the cert or crt file via the browser, it will ask if you want to open the file, or save it. Open the file, and then click on the "Import" button and follow the remaining instructions. Once that's done, you will be able to access the website without the annoying IE complaints about invalid site certificates.

Firefox makes this a bit easier and can import the cert permamently without having to actually access the cert or crt file as a seperate process, by simply telling the browser to accept the certificate permanently when the HTTPS site is first contacted.

Tags:   web     |    Perm Link:   Import self signed cert into IE 6 and 7

2007-08-06 23:09:16

Create an SSL Cert (self signed) for Apache

genkey --makeca --days 3560 jamesconner.us
genkey --days 3560 jamesconner.us

vi /etc/httpd/conf.d/ssl.conf and change the following parameters:
SSLCertificateFile /etc/pki/tls/certs/{sitename}.cert
SSLCertificateKeyFile /etc/pki/tls/private/{sitename}.key

Restart the httpd service and SSL will be enabled.

Tags:   linux, web     |    Perm Link:   Create an SSL Cert (self signed) for Apache

2007-08-06 23:09:16

Redirect HTTP to HTTPS via ModRewrite

Place the following code in the body of httpd.conf and restart the httpd service:

RewriteEngine On
RewriteCond %{SERVER_PORT} !^443$
RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [L,R]

Tags:   linux, web     |    Perm Link:   Redirect HTTP to HTTPS via ModRewrite

James Conner