Wow. What a stupidly technological week. If doing I.T. was like eating fruit, I’d have a severe case of the runs.
Ok, so the first interesting item this week was our Domain Model. A domain model, for all you B Comp. students, is essentially a Class Diagram, its just what the B. Info Systems students call ’em. We needed to prepare our Domain Model as the first step of our design for the vicICT Membership System.
A membership system sounds fine and dandy until said membership system requires you to facilitate group memberships and changing from one membership type to the other. One thing I’ve learnt is that regardless of what walk of life you come from, you will always argue about the database schema.
So, Tuesday morning started with the B Comp students in my team all standing at a whiteboard, arguing about the particulars of cardinalities of relationships and basic stuff to do with ER modelling. Then to assist, along came our tutors, who both disagreed with our approach, and then with each other. Apart from being humorous, in a Schindler’s List sort of way, this was a sign, along with all the other signs encountered in previous group work, that system design and modelling is a great
divider amongst men. I guess that’s why the majority of DBA’s I know are women!
Anyhow, if the torture of the morning wasn’t enough, we decided to press on. Find a meeting room in the uni containing a whiteboard. Tucked away in N block where no IT student normally ventures and after we had some time to think more about the data and problem space, we proceeded to draw our designs. This was followed by a series of drawing over each others design intertwined with a lot of explaining of our thought processes and explaining the basics of some database concepts to other members.
By the afternoon we were all bored and frustrated with each other, but we had learnt an important lesson:
The safest thing when coming up with a DB design is to have each person go away and draw their own models. This way everyone has thought about the perils and at least made a few mistakes in their revisions. They have also tested their schema in their head against different scenarios which can then be used to challenge alternate designs other team members have come up with. They can go and find tools and fill in their own knowledge gaps before we all get together and waste each others time. After that, they can regroup and compare ideas, merge models and go forward. I guess in the real world, a safe analogy would be that someone calls a meeting about a design. In preparation for this meeting you:
- Actually prepare.
- Find your database mojo. If you haven’t had much exposure to databases (ie, you are still a uni student), go and look at your textbooks on databases. Make sure that you don’t come to the meeting proposing silly things that can’t be normalised.
- Have a go with as much of the design as possible. Make sure you challenge it and find a few things wrong with it, then fix those things. If your design comes out smelling like roses on the first go, please go sniff a dogs bum and ensure your nose is in good functional order.
Break the design and find test scenarios to break other peoples designs. Write these scenarios down, they will make the basis for some clever test cases when you are implementing your system.
My new toy this week was the new Microsoft Office. Surprisingly, my 3 year old laptop runs it faster than Office 2003. The user interface redesign in Word, Excel & PowerPoint (among others) was a risk but it certainly paid off. A lot of thought to what controls are used most often and common toolbar icons pop up over your document when you highlight something and right click, so you are closer to the editing controls. Some of my senior colleagues think the interface is shit and the ribbon is too big, but I’m very impressed with it. You can turn it off if you like later anyhow.
One Note is still my fave app, and the extra features show that M$ are certainly pushing it. Some cool new features are the text recognition of pictures and audio recordings so that they can be searched just like typed and handwritten notes.
The best feature so far is the blogging tool though. It can integrate with my two faves, WordPress and Blogger and it’s a great welcome to the new suite.
Office Ultimate is still available at the ridiculous uni student price of $75 per license. You will need one license for each computer you want to install this on (per my reply from M$ when I emailed them about it), but its still a bargain compared to the Academic pricing in the shops for a not so Ultimate version ($250~). All you have to do is go to http://www.itsnotcheating.com.au and mention referral code MSP9.
That Linux Box that’ll run a version control server and upstairs heater
Fun and games on the linux front. The Cobalt Raq4 server is now running Fedora 5. All it took was to upgrade the firmware on the cobalt, pull out the old hard drive, install Fedora on a normal PC, then replace the kernal and modules with premade ones as well as code to run the LCD, configure the serial port and terminals to run on startup and then put the Hard Drive back in the unit, configure the unit to use the hard drive rather than network boot and tell Fedora it’s the /boot partition rather than the / one, I want it to start when it boots from disk.
Yes, I am being sarcastic, it took an age and a day (two of them in fact) to get this thing up and running.
My friend who has provided the hardware, has met with much frustration in linux land, particularly with user and group permissions, but has managed to resolve these, and also install SVN and Apache2 and have them run our repositories nicely.
We have a backup strategy and he has also wrote a script to do an incremental backup of the repository onto a series of large rotated USB disks. One thing that still puzzles us is how to do a backup of both the repository configuration and the files in the repository. svnadmin dump does the first bit, but not the second.
“By the power of SSH tunneling, I am HE-MAN” aka “now I can escape my countries Internet Censorship Proxy by finding an SSH server to bounce off”
We had the box running solo throughout the end of the week while we were at uni/work. Something that was interesting were the amount of connection attempts from overseas. People from China, France and Russia trying a dictionary attack of usernames and passwords. On a bad day we had 600 connection attempts of which only a couple of them legitimate. Thankfully of all the successful logins, they were only done from our own networks in Aus, but its still interesting to see how many people just sniff ports on the web in search of a place they can squat and do all kinds of nasty stuff to. Side note: If we were hacked, the hackers could have gone and edited the logs to make us believe no one ever came in :S
And the winner is Sydney, Australia
As for hosting the server, it was sitting in my house for most of the week but the spare room is small and along with another computer, router, 2 monitors, a laser printer and god knows what else, the room heats up really quick. It’s also not suitable since my partner runs a home business from the same room!
We were going to secure a place in a Sydney datacenter but our contacts advised that the operators of said datacenter had a habit of unnecessarily unplugging things they decided on a whim didn’t belong. My friend on the other hand is keen to host the server at his place, which I’m glad. Its a win / win since my friend has a dedicated internet connection just for the server (big family, 2 internet accounts), a large bedroom and personal tolerance for loud PSU fans, as well as a bedroom that gets really cold.
The only limitation about hosting it there is the bandwidth involved, 64k upload will mean slow checkout times but once a checkout is done, then doing the updates shouldn’t suck too badly. We can consider an upgrade of speed and since it’s a wireless connection the provisioning lead time to upgrade shouldn’t be long at all.
And after all our hard work, I managed to fubar it all up by doing a yum update. In doing so, it updated the kernal and heaps of other software. Great we have patched many known security holes. However it must have installed packages intended for a 686 instead of 386 architecture, and now every command is returning an illegal instruction message. I’ll use this opportunity to reformat the thing as a Raid device, and also set up our repositories using the FSFS type rather than the Berkely DB filesystem. Berkely DB is tried and true, but much less resilient to unexpected shutdowns. I read on one of the cobalt pages how to configure yum / rpm to only look at 386 packages, so I’ll take this on board next time so we can get back together.
I’m am so haX0r. Give me admin rights so I can install developer tools
Good news (I hope), the ‘development managers’ have met with the ‘internal services’ people at Monash and met our requests to install TortoiseSVN on the student labs. The dev managers seem quite happy with the idea. I believe Monday morning (a few hours away) I’ll be meeting with one of the internal services people in charge to run through Tortoise and determine if it can run on the Novell setup and talk to our servers, great and small.
There could be a few issues with this. Tortoise can accept a proxy configuration but the problem is that it will store the said configuration in its configuration file. This means that if another student logged in, they could potentially have the password settings from the previous user. We would need a logout script to clear this value or have Tortoise ask for the password each time and not save user credentials. Or it could be that the students documents and settings where all this stuff is stored, is wiped on logout anyhow, so worrying about this may not be too much of a hassle.
The other issue is that TortoiseSVN appears on every context menu in Windows explorer. This can be switched off I believe, just have to find out how.
It all ends with V
Shit its 1:33AM and I’ve already had my daily recommended intake of V. Time to sign off this stupidly long blog.
Till next time