You would think, given my previous blog post, that I would be doing my best to avoid adding to my frustration level, wouldn't you? If you do think that you clearly do not know me at all.
So
At work, the next part of the project is to install a new piece into the already vastly complex and complicated puzzle that this client laughingly calls their E-Business environment. This is the kind of thing that I love. I get great satisfaction from installing new software and making it work. So what's the problem? Well. To do the job right on new hardware, did I mention that we need new hardware even though we have about half of HP's server output for the last three years already? I exaggerate, but we already have 26 Linux servers. 26! And who knows how many NT boxes? I certainly don't. And this is not a Fortune 100 company!
Back to the plot.
To do the job right on new hardware it is normal to obtain said hardware several weeks before it will be deployed into Production, so that it can "burn in". Normal is the operative word in that sentence. Needless to say, that is not the way it's going to be. The new hardware is supposed to be on the dock today, racked and powered tomorrow, and the OS installed next week -- if the temporary System Admin can spare the time ( the one that was on permanent staff left three months ago and hasn't been replaced.) I've been given three days to install the new part of the software. Three days is not enough. But as my protestations fell on deaf ears; that is the way it will be. So as I don't like to make a complete pratt of myself in front of an audience, I went out at the weekend and bought myself a cheap 64-bit PC so that I could practice the install and shake out the problems. And that's just fine. I don't mind that at all.
Brought the new PC home and immediately installed Oracle's version of Linux 4 Update 8 and all was fine… until… until I tried to install Oracle's Virtualization software. The idea was to create two Virtual Machines on my new Linux 64 bit computer so I could emulate the exact environment I'll be using in two weeks. I've struggled for 4 days with it and every day is worse than the last. So now I've given up with that idea and I'm going to install the database and part of the application on 64-bit and the rest of the application on one of my 32-bit computers and link them through my tiny LAN. The really annoying thing is that I could have done this days ago, instead of grinding my teeth and wasting all this time.
And still I haven't written a single new word on Project Tevan. I could have tried to do that instead of pouring out this blather. But at least when I blog I'm writing something other than soul-destroying technical documentation with a blow-by-blow account of what I did which is what I have to do every day. And that is good enough for now.