Web

We all enjoy a good holiday. Getting the time to take one always seems to be the problem for me however. I think I may have just found the answer...

If you're like me you grew up watching The Wonderful World of Disney at 6:30pm every Sunday. Here we marveled at cartoons of Mickey, Goofy and other great Disney characters. (So much so, many the hostnames on my home network are now named after Disney characters! ).

It also introduced us to classic 'childrens' movies like Herbie, 101 Dalmatians, Mary Poppins and Alice in Wonderland.

It's probably the dream of every child to visit the magical place of Disneyland or DisneyWorld.

With the help of Google you can now explore DisneyLand without leaving your chair!
Google has produced a 3D interactive representation of Disneyland inside Google Earth.

If you've got Google Earth installed try the following:

1. Once Google Earth loads, search for "Disney World".
2. Click on the golden Disney Mickey Ears - This will load an information window.
3. In the info window click on Show Disney World in 3D.

The 3D world contains over 1,500 3D models and will let you explore right through the park. The models are highly detailed and a sight to behold!

It's nearly as good as being there!
Just think - no more queues for rides, no long-haul flight getting there, and the park is now open 24 hours for you.

Have fun exploring!

There are many reasons people are stuck on Windows.

For small businesses the main reason is their accounting software.
Like it or not, since the introduction of GST and BAS the days of the shoe-box accounting have disappeared. Every business that wants to keep accurate financial records requires an computerized accounting system.

In Australia, The introduction of GST and BAS has made it difficult for these same people to move over to Linux.
The two most popular Small Business Accounting packages are MYOB and QuickBooks. Both products support the Australian market and handle submissions to the ATO.

Many small businesses look for software that can handle base accounting (less then 25 invoices a week) and an integrated simple payroll module that can pay their employees (1-5 typically).

Both QuickBooks and MYOB operate as closed-source commercial software that runs on Windows (and on Mac - in the case of MYOB). They also integrate heavily into Microsoft Office.

Both business models expect customers to fork our between $500 - $800 for the initial purchase, and anywhere from $200- $500 annually to get 'updates'. For any small business this is a hefty investment just to keep up with the legal requirements of running their business. Calling for support can also attract additional fees on top of the yearly retainer.

As such, many are fearful to move on, but have a love-hate relationship with their accounting software provider. They feel cheated and ripped off (and rightly so). This duopoly has created a handsome cash-cow for both software makers.

The current extortion model used by MYOB and Quicken is best explained by Turbo Cash's explaination (a GPL Windows Accounting package). Unfortunately TurboCash is Windows software and contains no Australian payroll module.

Unfortunately, I am yet to see an OSS Linux accounting software that handles all the features required for an Australian business:

1. Handles Australian Taxation - including GST and BAS reporting/lodging
2. Handles Australian Payroll - including PAYG and Superannuation

The introduction of both these two options would see thousands migrate off Windows (it's often the only reason cited for not running Linux), and adopt a new accounting package.

There is both Ledger-SQL and LedgerSMB (a fork of the former) that handle accounting and can be customized to handle GST. Yet, they don't do anything to address BAS reporting/lodging or have a payroll module. As such, both are unsuitable for the Australian SMB market without further heavy lifting.

Their is commercial software like SAGE AccPac available, yet it's quite expensive and more geared towards a medium sized business and thus out of the price range for most small businesses.

One OSS project that did look indeed promising was SYMBOL (Surf Your Money Books On Line). It was written by an accountant from Western Australia and licensed under the BSD license.

I have been in Email discussion with the developer Edward Metcalfe, but it appears he has now moved on from the project and as such the project has stalled. Looking at the CVS repository the last update was unfortunately 13 months ago.

However, the software is indeed functional and delivers on the two items listed above (Australian Taxation/Payroll). Whilst you would need to update the PAYG tax tables (no real show-stopper), it should do the job admirably. ComputerWorld actually ran an article on SYMBOL in Februrary 2007.

Those interested in SYMBOL, will find it is a web-based application so accounting can be down via a regular browser (making it suitable on either Mac/Windows/Linux clients) It runs on a PostgreSQL backend and uses Perl/CGI for the front-end. It also is multi-user based. (One thing software like MYOB and Quicken charge an arm and a leg for!)

The fear of running SYMBOL though in it's current form is that it is unmaintained. It's likely the current government or subsequent ones will indeed look at overhauling the payroll and corporate tax systems (as opposed to just an implementation of the Goods and Services Tax). This would mean that any software a small business adopts would need to address these modification.

The ATO has worked to provide great documentation on the complex tax scheme we have in Australia for software developers. Their Software Developers Website gives test case scenarios and formulas to write compliant and competing software.

I'm in two minds:

1. Do I run SYMBOL and either start maintaining it or fork it?
2. Do I use a lot of the program logic, and spawn a completely new project?

Ideally I would love to see a AJAXed based web-version of the application with a modern interface using either the Yahoo UI or the Dojo Toolkit's Dijit and DojoX interfaces.
Either solution would provide an excellent interface and provide the user with an experience that matched a local fat client. Using a web framework like Django and a PostgreSQL database underneath, would make for a solid backend.

I think there is a market for an excellent OSS product to capture the market and knock off this duopoly. However I suspect it will take some committed individuals to pull it off. From the grumblings you hear frequently from small business owners there is a ready market to ditch their over-priced software once a viable and supported solution arises.

Here are some interesting facts about the Australian Small Business Market:

• There are about 1.2 million small businesses in Australia employing around 3.3 million people.
• During the past decade, small businesses have created an estimated 660,000 new jobs.
• 42% of all goods exporters are small businesses.
• 25% of the Australian GDP (estimated in 2006 at $1 trillion dollars) comes from small business.

That's a lot of potential users of an OSS product!

I suspect a lot of OSS developers do a fair amount of moon-lighting and as such require a way to invoice for their work. (Consulting may be your day time job also to pay for the bills, and OSS coding your passion and after hours work!).

So what are your thoughts?
Is there enough interest in getting up an OSS Accounting+Payroll solution for Australian small businesses?

Jeremy Visser recently reported his content was being ripped off by a shady site called MundoSitio[dot]com.

Looking closer at the site it appears that it's not just Jeremy but anyone that gets syndicated on Planet Linux Australia.

It appears my name is being credited to many of the posts -- and their not even mine!

Whilst they do credit the author (well often incorrectly as me!) and link to the original conent, it's a little rich to be making advertising dollars off our posts. Particularly after I deliberately don't run adverts on my own site (by choice).

I suspect it might be prudent for those running Planet Linux Australia to look at blocking the offending IPs.

Anyone able to come up with the offending IPs to block?

Update: Thomas has posted he believes the offending IP ranges are:

• 78.129.0.0/16
• 77.92.0.0/16

(06:34) Someone set the alarm far too early. Jumped out of bed in a panic & twisted ankle. #

(06:44) Jumped in the shower. I missed, landed on the soap. Other ankle now throbbing. #

(07:09) Walked out front door to grab morning newspaper. #

(07:10) Eyelid meet bee. Eye now swelling. #

(07:11) Bastard paperboy has got the paper in the damn bird bath again. #

(07:15) The same someone who fiddled with the alarm clock has now set the toaster to the 'burn like a crisp' setting. #

(07:16) Forgot to buy coffee, will have to settle for water. #

(07:20) Toothbrush is now black from the charcoaled toast. #

(07:25) Where the hell are my keys? #

(07:29) Tackled dog rugby style after chasing him around the coffee table. Have managed to recover them, albeit full of dog saliva. #

(07:30) Apparently keyless entry into your car doesn't work after being chewed into a black ball of plastic. #

(07:31) Hit head when entering car. Maybe this is why keyless entry was invented? #

(07:43) If you are going to have a road-rage episode, choose wisely. Now sporting a growing fat lip to match my bug bee-eye. Note to self: Don't abuse a boxer. #

(08:17) All car-parks now taken due to the time lost with the boxer. Have to park 4 blocks further away from the office. A great workout for sore and swollen ankles. #

(08:33) Remember the umbrella even if the weather report says there is little chance of rain. #

(08:53) Finally in at work. #

(08:56) The company provided International Roast is a poor substitute for coffee. #

(09:05) Coffeeeeee annnndddd keeeyboardddddds donnnnn't mix. #

On Tuesday, Internode announced that they are now mirroring Sourceforge.

This is fantastic news for all OSS lovers down here in Australia.

Whilst we have had the up and down again service from Optus for some time, it's great to have an alternative. (Having said that - I don't see Optus being offered on Sourceforge any more? Has Optus mirroring disappeared again?)

Even better, customers of Internode will actually get those downloads for free now. (Whilst I don't download Gb's of data each month of Sourceforge, I do grab things regularly off it! -- and every little bit helps.) More importantly, having a speedy mirror to grab code off is what counts.

It's great to see Internode -- a company that uses a lot of OSS software in their service delivery give back to the community that makes it happen.

Their range of free mirrored content is quite appealing. They run their own download mirror site and for a Linux lover there is a huge selection of distros, and updates mirrored. Even better it supports rsync so you can grab your updates quickly and easily! Add to it, now Sourceforge and MajorGeeks (for Windows software lovers). I regularly make use of their free streaming radio content. They have stuff also for gamers (who's got the time ?! ) as well as some other content. You can take a peep here.

The Sourceforge content is hosted here: http://internode.dl.sourceforge.net/ but you'll need to use the Sourceforge website to pick a download, then select Adelaide, Australia from the list of download options. (The direct link to the Internode mirror isn't browsable).


After reviewing this post, it does sound like an advert for Internode!
Having said that, I've used a bunch of ISPs over the years, and I haven't been happier than I am now with Internode.

The service is always faultless, 13-NODE (Tech support) is answered always promptly by someone who actually understands technical details (and not a messenger service for a tech team).
I've even had technical staff diagnose and fix routing issues whilst I've been on the phone with them!

So if you're in the market for a new ISP, give them a go. Sure, they aren't the cheapest ISP going around, but they are probably the best technical ISP and have some real added bonuses for OSS fans.

Tip: For those that do wish to sign up with Internode, one way to pickup an ongoing discount of 15% is to register as a SAGE-AU member. Get the benefits of being a SAGE-AU member -- and cheaper Internet access. (You will need a valid SAGE-AU membership number to be entitled to the discount).
For me, the cost of the SAGE-AU membership is less than the discount.. so I come out ahead!

This is a 3 part posting that covers how you can setup 2-way Nagios alerting via SMS.

The series is broken down as such:

1. Part 1: Background and Requirements
2. Part 2: Sending SMS messages from Nagios
3. Part 3: Acknowledging SMS messages (this article)

Review
As we saw in Part 2 we covered setting up Nagios to send out alerts.

Whilst this is great, it's not of great value if we can't do anything with these SMS messages. In addition, if no-one is sitting in front of the actual Nagios web console to acknowledge the issue, then Nagios will continue sending the SMS messages and will quickly fill up your phone's message memory. Not ideal!

The message is quite straight forward as well to read. A service problem message contains:

1. The type of incident: PROBLEM
2. The Host affected
3. The Service affected
4. The Severity of the incident
5. Additional Information about the incident.
6. The Time of the incident
7. A field to Respond/acknowledge the incident

A host problem message is quite similar but does not have a Service or Severity line.

Here is a Host problem message for comparison:Replying to the Nagios Problem SMS
When a problem from Nagios is sent to you via SMS it's quite easy to respond.

All you need to do is reply to the message (and include the text - which most mobile phones on the market provide a feature to do).

Whilst not required, you can append a simple message to your reply. This will be used in the acknowledgment response and add a comment to the service.

Comments don't need to be long, but they do help your other team members or interested parties know what is happening with the issue.

Be careful what you write!
The response you send will also be used in a follow-up SMS to everyone notifying them that someone is looking at the issue. You don't want to send something that might not be appreciated others that recipients

Acknowledging SMS messages
Acknowledging messages from Nagios is quite simple now we have our SMS Daemon setup (see Part 2 for details)
As a result, any incoming SMS messages get stored into our MySQL database.

We just need a process now to read them from the database, interpret them and then update Nagios appropriately.

This is a 3 part posting that covers how you can setup 2-way Nagios alerting via SMS.

The series is broken down as such:

1. Part 1: Background and Requirements
2. Part 2: Sending SMS messages from Nagios (this article)
3. Part 3: Acknowledging SMS messages

Sending SMS messages from Nagios

Introduction

To send messages from Nagios, I'm going to assume you already have a working Nagios environment.

2-way SMS messaging refers to the fact that you can reply to an SMS message and action is taken based on your response to the sender.
In this instance, Nagios will send a SMS (a Nagios alert), and you can reply to the SMS (a Nagios alert acknowledgment).

This part will cover sending out the SMS from Nagios once a host or service problem occurs. Part 3 will deal with how to send the reply and process it within Nagios.

Keep reading!

Due to the large size of this posting (it contains step-by-step instructions on setting up the SMS gateway), you may find your feed reader only contains the post up to here.

If that is the case continue reading the post here.

This is a 3 part posting that covers how you can setup 2-way Nagios alerting via SMS.

The series is broken down as such:

1. Part 1: Background and Requirements (this article)
2. Part 2: Sending SMS messages from Nagios
3. Part 3: Acknowledging SMS messages

For those that wish to setup simple, inexpensive monitoring you will find that it is simpler than first thought. Feel free to grab the code-snippets provided over the series and make use of it in your own environment.

The Nagios SMS alert system has been running here now in production for approximately 6 months and works quite well. The Nagios system manages a range of services/hosts and checks approximately 1,500 items (by no means large); it has however cut down the amount of time I require looking at Nagios alert screens.

Background and Requirements

Background
I like to dabble in web development and have now for around 10 years. As a result I undertake hosting in commercial data centers in order to ensure maximum uptime and good responsiveness. To offset the cost, I now provide hosting/email and web-development services to a number of clients.

As a result, it means one cannot easily look at the diagnostic LEDs, or even the console easily to determine when a problem has occurred. (Whilst I can make use of an IP KVM; it is normally a PITA and best avoided!)

Ideally I was after a monitoring system that alerted me prior to a problem so that I can deal with it before it became a bigger issue.

Nagios was chosen as it provided all the features we required, had support for a large number of items we wished to monitor, and was simple to extend to check custom services based on being written in Perl. Nagios comes with a swag of documentation making it easy to write simple checks or extend on as was seen fit. As I've coded a fair amount in Perl over the years for various System Administration tasks, Nagios was seen as a good fit. Being an Open-Source project ensured that it was an added bonus of both being free-to-use, but also I had access to the source code to understand better how the system worked.

I have used Nagios for years now, and historically have relied on web/email alerts. However, being human means I can't always be in front of my computer 24x7. This worked the majority of the time, though as luck would have it we ended up with a system failure that occurred early one mid-week morning. As a result it was decided we needed to put a system in place that alerted when something occurred when I wasn't in front of the computer.

We already had a working Nagios monitoring environment, so we wanted to make use of this system going forward.

Requirements
I wrote down our requirements for a paging system. I wanted to ensure whatever solution was put in place that it could grow with us, but also that we weren't locked into a solution for years or even worse, that we embarked upon a solution that would ultimately restrict any future requirements we might have.

There were several ways we could be alerted:

1. Telephone: Have the system 'call us'. Possibly play a standard recorded message.
2. Pager: Make use of an alpha-numeric pager.
3. SMS: Send a text message.

We ruled out a telephone, as a recorded message wouldn't provide us any real details of what the issue was, unless we actually started recording exactly what the issue was. It was beginning to look too complicated for a simple requirement. I really thought a Voice-IVR was an overkill for what we required. (Whilst it may of indeed been fun to hack/configure!)

A pager was then looked into. Whilst pagers work well in ensuring a message is delivered we saw this as a drawback, in the sense it meant carrying around another device on us. (We already carried a mobile phone and the prospect of carrying a pager didn't appeal). Also pagers traditionally send one-way messages; and we wanted a system where we could acknowledge an alert.

We settled on a alert delivery system to be used via SMS. Whilst SMS doesn't have the guaranteed delivery system of that of a pager, it did open up the possibility of being able to respond to an alert. It had the added bonus that we already carried our mobiles close by 24x7 so there was no need to carry an additional device. Using a SMS to deliver a text based message also ensured we could then place useful information in the message to assist in the problem diagnosis.

We had now determined our delivery system (SMS), it was time to find technical solutions that would fit in with the existing Nagios monitoring platform.

Nagios by default has the ability to alert via various means. Pagers, SMS and Emails are handled quite easily within the standard configuration that ships with the software.

It would make the integration of SMS quite easily. However, it was only by default a 1-way system. There was no provision to handle a 2-way message. ( Alert Message then acknowledgment message)

A 2-way SMS alert system was preferred as it could be setup to stop alerting us continually via SMS once the alert had been acknowledged. It also had the added benefit that whilst the message was sent to other parties, it could also ensure that they were aware the problem was being investigated and avoid duplication of work.

We also wanted to run the SMS alert system as close as possible to the Nagios monitoring host. This would ensure that if we had a physical network or IP link down, we could still get messages out. This cut out using a 3^rd party SMS service.

Coming Up In the next part of the series...
In the next part, I'll describe the components that make up our 2-way SMS solution using OSS software and some of the scripts we hacked together to 'glue' the solution together.

It's now been running without a hitch now for about 6 months.

We also use it as a Web2SMS gateway locally, as well as being open enough that I can utilize it via the CLI to send out alerts.

Looking back the solution was quite simple, and met all our requirements.

Recently Jeremy Visser blogged about his frustrations that the http:// URI being dropped off addresses.

To be honest, I don't see it as a big problem.

Like it or not the Joe Six-Pack uses the following apps in this order:

1. Web Browser
2. Email Client
3. IM Client

Other items like an IRC client, FTP client or even Gopher or SSH Client are few and far between (Joe Six-Pack that is)

It's not merely web site addresses that have suffered that fate. Take a look at this random string:

user1@host1.com

Is that an SMTP address or the credentials to an SSH server? Could it even be an IM user?
Most people would read it as an Email address.... and most would probably be right.

Context has much to do with addressing.. .we all don't run around writing out mailto:user@host1.com everytime we wish to write down an email address.

Whilst it's fine for completeness, it's unnecessary.

I also note that many sites advertise as www.myhost.com. Notice the www aspect? That's an indication that it's a website address. Much like ftp.somesite.com indicates an FTP site, and mail.host.com or smtp.host.com indicates SMTP.

It is becoming popular to drop the www hostname aspect and just refer to a website via it's domain name (ie: host.com).

This also works and seems to be a defacto now instead of www. (Hey it's 4 less chars to type!).
I find if you give the average person any random Internet string.. it's normally typed into a browser first these days. So dropping the http:// makes sense. (particularly from a marketing/advertising viewpoint -- you can have a larger font for your actual address not the protocol!).