Archive

Archive for April, 2009

Test Drives

April 15th, 2009

Back in November of 2008, I was looking to buy a new car due to the unfortunate fate of my previous Civic. I wanted something somewhat fun…not boring. The Civic was certainly a great car; it would never have any mechanical issues, and would last forever, but I thought it was time for something a little better…something more fitting with my infantile mindset.

After some research, I narrowed my list to three sub-$25000 cars, and did some test drives.

Ok, let’s just preface this by saying that my test drives were of varying length, weather condition, time of day, and passenger. I have had the most amount of time driving the Speed3 mostly because Ry has one, and I “borrow” it fairly often. When I test drove the SI, the dude was a bit of a douchebag, and we only went about a mile or two in it due to it being a busy-ish Saturday morning. That does not excuse that dealership’s conduct toward a potential buyer. I drove the GTi the night before, and drove it in the rain when it was dark outside. Took it through some back roads, some highway..dude was pretty cool about letting me get on it.

Anyway, onto my reviews.

2008 Mazda MazdaSpeed3
Pros: It’s a fast car. No matter what gear you are in, it just wants to go. Some noticeable turbo lag, but once it hits about 3000-3500 it goes “hello!”. Braking is awesome, it stops on a dime pretty much. Handling is great…there is very little body roll, but then again, with it not being my car I haven’t really pushed it very hard. Interior is well made, the controls are within easy reach, it’s fairly comfortable, and has a decent amount of room in the back. The glovebox is xbox huge for storing stuff. It’s a four door, so the backseat passengers are happy. It looks good…I mean…really good; from almost any angle.
Cons: It has a hard ride. The suspension is stiff and the tires are low profile, so you feel everything. They overdid the red in the interior. Everything is red, from the dash, to the climate controls, to the radio. Don’t get me wrong, I like red as much as the next guy, but goddamn. The speedo is a bit weird as well (not a big thing, just nitpicking), as the separation takes some getting used to… the 60mph mark is where I’d think 35 is in any other car. Visibility isn’t that great with the way the hatch is, there are a few blind spots, but not too bad. It has a few weird rattles, especially in the hatch and the seats. The hatch cover moves around, and the seats squeak a bit as you move around in them. The backseat isn’t very comfortable, but I wouldn’t be spending much time there.
Other comments:You also can’t really feel speed in the car. Cruising at 90mph, it feels like you’re standing still, which is both good and bad. The steering is very touchy. The slightest movement makes the car change direction…I like feel in my steering, but without having to worry about moving the wheel too much.

2008 Volkswagen GTi
Pros: This is a fun car. Less turbo lag than the Speed3. The DSG transmission is like having god himself shift for you…it’s quite an amazing experience. It’s fun around corners (it was rainy so I took it easy), with very good braking and handling (Although people say it’s worse than the speed3..I wasnt really able to notice the difference due to lack of being able to push both cars hard). The 2 door looks pretty awesome, but not like some of the classic GTIs (not that I care). The one I looked at had a moonroof, premium sound, 6 cd changer with mp3 and sat radio, ipod connector..the works. Hatch is roomy, and contoured well. The interior is also very well put together, no rattles, everything is within easy reach and easy to see. The coloring of the interior is beautiful…when it’s dark and the dash lights up, it just looks amazing. The ride is very comfortable, virtually no road noise, and the bumps are nicely handled by the suspension. Under the hood it is very well designed and clean. Great fuel economy also (yea…dont care). 0% financing for 60 months.
Cons: Not quite as fast as the speed3. As tested, it came out to be a bit more expensive than the speed3 and the SI. The backseat isn’t quite as roomy as either the SI or the 3, but it is also the only 2 door that I tested. With it being a two door as well, passengers might not be all that satisfied. Volkswagen has some weird seat adjustments as well. In most cars, your seat angle is either electrically chosen, or you pull a lever and move the seat backing forward or back; in the GTi, there is a knob. It takes some getting used to. Parts for VWs…Im just kind of expecting them to be more expensive.

2009 Honda Civic SI
Pros: It revs to 8000 rpms and loves being in the high revs. It does about 30mpg with an engine that makes 200HP. The ride is very comfortable for both front and backseat passengers. The clutch and trans are one of the best 6 speed manuals I have ever driven…it is very very smooth. Trunk is roomy…the exterior looks pretty damned good, while still not drawing much attention to itself. It’s a Honda…so it will pretty much never break. Cheapest of the bunch.
Cons: it makes no power down low. It does nothing until you hit 6000 rpms. The interior is ugly…I have no idea who decided that having a dash that is long enough to use as a dinner table was a good idea. That same person probably also thought that having your tach by itself, and then having a digital speedo were a good idea. Guess what…it’s not. The car just wasn’t very fun to drive…unless you’re just revving the shit out of the engine, no instant power if you want to just GO. With the way the gearing is, you’re doing over 3000 rpms just going 60mph on the highway…wtf?!

So…those were my initial impressions of the cars I test drove last year. Did any of them change since then? Did my car of choice turn out to be great or a mistake? Tune in next time.

cars , , ,

Tricking around in ESX VirtualCenter

April 2nd, 2009

Virtualization is great…it’s the current hot item in IT. Everyone is doing it; it’s the future of datacenter consolidation.

…it’s my current project.

After a few days of research, some CBTs, and a few meetings, we finally decided to start implementing our grand master plan. Brand new 16 core server with 128GB RAM…check, ESX licensing…check, sanity…check.

After deciding on our virtual network and disk architectures, we finally went to work. VMware is ungodly easy to setup, it’s almost scary.

Next step was getting our VirtualCenter server up and running, and this is when the fun begins (and by fun, I really mean WTF). In the title of the post, I mentioned something about “tricking” around in this particular portion of the setup process, so allow me to explain.

VirtualCenter is basically just a consolidated ESX host management solution. Instead of connecting to each ESX host individually to manage it, VirtualCenter (VC from now on) allows you to manage all your hosts from one area. In VC, you can make ESX clusters, manage Distributed Resources, manage VMotion, and a whole bunch of other goodies. It runs on top of a basic Windows server, uses Active Directory for authentication, and is supposed to make everything nice and easy. Indeed, it does; the interface is great, and manageability is superb…it makes my job all that much easier.

Installation is pretty straightforward, and after clicking “Next” a few times for the VI Client and for the VC server, you think you’re golden. Of course, there are some steps you have to perform as pre-requisites for VC.
First, you need to create a database for it. Well, I’m lying, you don’t particularly HAVE to create a database for it, since it would offer to install MSDE in the same step, but we have a SQL 2005 Cluster…why not take advantage of it? So, created a database, and assigned a domain user myDomain\esxdb as db_owner to it.
Next, create a system DSN to point to that database using NT Authentication. Make sure you use the SQL Native client since it’s SQL 2005, and you’re ready to roll.
Finally, during install, provide the installer with the DSN name, the username, and the password that it will need to connect to the database.

Wait wait wait…so what about this trickery you keep talking about?
Let me get to that!

Next up…installing the Update Manager and the Converter. Go through those steps…and wait…it tells me that the VirtualCenter server is not running? I JUST INSTALLED THE DAMNED THING…on a brand new clean server, no less.

Ok then…I go to the Services menu and try to start it manually….fail. Fail? FAIL?!

Looking through logs (which are in C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs …yea don’t ask why they are there, they just are), I see this:

[2009-04-01 16:20:21.613 'App' 1784 error] ODBC error: (28000) – [Microsoft][SQL Native Client][SQL Server]Login failed for user ‘NT AUTHORITY\ANONYMOUS LOGON’.
[2009-04-01 16:20:21.613 'App' 1784 error] Failed to intialize VMware VirtualCenter. Shutting down…
[2009-04-01 16:20:21.613 'App' 1784 info] Forcing shutdown of VMware VirtualCenter now

Now wait a minute…why the hell is it trying to login to the SQL server as anonymous when I damned clearly provided a username and password for it, and I’m logged into the VC server as a domain admin, so even if it was passing active credentials, it should work. However, it was not.

So ok…what if I go back to the DSN and specify credentials there. Nope, can’t do that…it’s either NT authentication (which does not let you pass credentials), or SQL authentication (which does). Putting domain credentials into the SQL authentication fields result in a whole bunch of fail.

Ok then, next step: create a local SQL user, and use that instead. So I create a local user called esxlocaldb on the SQL server, make that user the db_owner, and re-run the installer for VC. I give it the credentials of the esxlocaldb user (after changing my DSN to use those SQL credentials, obviously), and it comes back and tells me that the credentials are incorrect. I doublecheck everything, do a test in the DSN config window, and everything is dandy…but the VC installer simply wont work.

So now, the trickery begins. In order to install this F-ing thing, I basically had to have both the esxlocaldb user as db_owner AND the domain\esxdb user as db_owner to the ESX database. For the DSN, I gave it the esxlocaldb credentials using SQL authentication, but for the ESX installer, I gave it the domain account. This seemed to work flawlessly.

I think that the installer is just wacked…it uses the DSN credentials to query the DB, but VirtualCenter actually requires a domain user to have access to it. Really, makes no sense to me, but we basically tried everything else. Every other possible combination of database rights and DSN configurations.

Makes no sense to me, but it works now…if anyone has any comments on what we may have missed, I’m all eyes and ears.

me = geek, work