Around the third week in April (I realize that it's June), I gave a presentation on infrastructure architecture to the IASA.  I hadn't given a "public" presentation since doing a guest lecture at Baylor a few years ago.  Anyway, this was the opening slide:

Yes, that's me checking out some pipe bends done by the electricians during a data center build-out.  I thought it was funny.  After that, a whirlwind of things occured including a benign tumor, a multi-million dollar disaster recovery implementation, and some other developments.  This would explain the blog not being updated.  The good news is that everyone is okay and that I hope to add some more posts very soon!  And that XNA 3.0 Beta 1 and WorldWide Telescope (see below) are both available for download!  I will be turning the attention of this blog toward more infrastructure-type topics in the future.  Stay tuned!

Worldwide Telescope

XNA 3.0 for Zune

So I downloaded the MSDN RTM of Server 2008 a couple of days back and loaded it up on a nice new HP DL360 G5 that has the built-in Intel virtualization technology.  After installing Server 2008 Enterprise on it (the install is WAY less involved than 2003), I hooked it up to a SAN, added a LUN and added the Hyper-V server "role" to it.  The Hyper-V manager looks about like it did before when Win2K8 was still RC0.  I'm not the biggest fan of the interface and menus (possibly using VMWare ESX has me a little biased), but that could change with the System Center Virtual Machine Manager (SCVMM).

So here's my disclaimer:  I didn't use the "recommended" configuration, i.e. 2 network connections to set up Hyper-V, I used one.  I'll test it later with 2 network connections, but for right now I want to use one because it simulates how I would use Hyper-V in a real world scenario.  Most machines in a production environment have 2 NICs that are teamed in one way or another (usually for failover purposes).  That leaves me with one connection aside from adding another NIC card to the server.  That being said, read on. 

So I joined the server - we'll call it Longhorn3 for reference's sake - to a domain.  I saw that IPv6 was enabled on the NIC, but I turned it off as I'm not running IPv6 on the network.  I gave the network connection a static IP and everything worked great.  I was able to browse network shares, hit the Internet, hit intranet sites, etc.  After this I built a VM, Win2k3 standard using an ISO I copied over from my computer at my desk (BTW copying between Vista and Server 2008 was like lightning).  After installing Server 2003 in a VM I needed to update it.  I tried copying the SP2 package via drag-and-drop but no dice.  I figured I needed to install the "Integration Services" or as I like to call it, Microsoft's VMWare Tools.  Tried that and come to find out you need SP2 installed.  So now I was in a bind, no tools = no copy from host machine, no SP2 = no tools.  Time to get connected to the network.

I went to the Virtual Network Manager to add a network.  I added an external network called "Network 1".  I attached it to the NIC that had connectivity.  Now I was able to go to WindowsUpdate and get service pack 2.  I thought that there was a problem accessing network shares from the VM, but that turned out to be a FQDN issue as the VM was not on the domain yet.  While I was downloading updates from WindowsUpdate, I wanted to grab some other files from my computer at my desk and put them on the desktop of the host server running 2008.  That's where I ran into problems.  I couldn't seem to browse network shares after adding the virtual network to the host 2008 machine.  I started to diagnose this after the updates had completed. 

I first went to manage network connections to look at the NIC and the properties.  That's when I encountered this screen:

It seems that the Client for Microsoft Networks gets disabled as part of the external network creation by Hyper-V.  This explains my network shares access issue.  Try to enable it (checking the box....something I haven't had to do, aside from MSCS creation, since Novell + Win95 interoperability issues) and then you get the following screen:

To which I say, "I'm not disabling it, YOU disabled it! I want to ENable it!."  Something doesn't seem to be right with networking and Hyper-V as far as all of the services that are enabled or disabled due to the creation of a virtual network.  Some other observations on this phenomenon:

1.  Even when I can't browse network shares from the host, the VM can.

2.  When the virtual network is removed, all of the necessary changes are made to the NIC to get it working normally again.

3.  I have no problem pinging, accessing web sites, or authentication issues when the virtual network is enabled/created.  Just accessing shares.

More on this when I test using the recommended method of 2 NICs (one for management, one for VM's).

So the NOAA web service is great.  It is a nice easy way to give forecasts based on LatLong, etc.  The problem that it doesn't conquer is the question that my wife and I (and all Austin mountain bikers) ask before we choose which wonderful Austin trail to ride - when was the last time it rained at the trail?  Once you have the answer to that - you can whittle down your trail choice - or if it's been dry for weeks, have them all to choose from.  Let's take two trails as examples.

If I know that it has rained more than 1.5" at the Barton Creek Greenbelt, then I probably won't want to ride it (or at least the part North of 360) until at least 2 to 3 dry days (depending on sunlight and humidity...it's really wooded) after that rainfall.  On the other hand, the same rainfall amount (or even a little more) could fall at Emma Long Park yesterday and be ok to ride today (Emma Long is more rock/caliche than dirt).  I need a service that will not just give you the forecast for the future, but give you the history of rainfall/sunlight/etc so you can make your decision.  I want to be able to go to a website, look at this data for all of the trails on one page, make the decision as to which one I want to ride that I also CAN ride, then click on the map for a refresher on the route in Virtual Earth.  Today I started looking for a service that would provide historical weather data.  There aren't very many "almanac" data sites that keep this data and provide it in a easily available format (XML).  Also, the data is usually from the airport, a military base, or a weather station not near any of the trails...and I wanted this to be specific.

Enter the PWS or personal weather station.  I never really realized that there is this whole world of personal weather stations.  The place that I found the 2 components I was looking for - detailed historical weather data recorded at a specific LatLong PLUS the XML format was at Weather Underground.  Type in a zip code to get started, then down near the middle of the page you can see a map of all the PWS in the area using Google Maps.  Pretty cool!  Of course there aren't any right smack in the middle of the Greenbelt, but it's better than the airport data, right?  You can even view the current conditions AND the daily observations in XML!  Not all of the PWS have daily observations that go back very far, probably a limitation of the weather station itself or the service that they use to send the data.  So now all I have to do is find the page that shows the WSDL to get me all of this great data.

No dice.  As far as I can tell I don't see that WUnderground has a web services setup.  I wrote them an email to inquire about becoming a member if this were the case.  I looked into it a little further, and what I want IS possible, it just requires too much care and feeding for a site that would be a hobby.  The URL of the daily observations for a weather station don't change.  Every station in Austin has a name that begins with KTXAUSTI followed by a number .  The LatLong is in the data that is returned via XML, so I could map the stations myself.  I would just have to build the list of stations, query the data a few times a day and put that in SQL, add the station location to the maps of the trails using the LatLong returned by the XML query (which is really just a GET on the HTML of the page linked above), summarize the data that I want - precipitation, sunlight, humidity, etc, and add that to a SQL view or table that keeps data for a specified amount of time (probably one week or so) and only return weather data for a set of trails based on the proximity of the weather station location in the database to the trails location in the KML overlay and I suppose that if there were multiple weather stations that contained data that was relevant to the same trail, I would have to aggregate and average the data to give an accurate report.  Not too much work (ha!) and it could all break if WUnderground changes their URL style or subdomains...or they could ban my IP.  They should just offer this as a web service though, I think it would be a great pay web service (not for hobbyists like me of course, but for people who use it commercially) for places like ski areas...many times during the year, the weather at the base is not available because there's ONE weather station - run by a resort - that's broken or needs to be reset, or isn't linking to their website.  You would still be able to get that data (or at least nearby data) from other sources on a ski conditions site.  Just a thought. 

Also, I looked into it a little further and if you take apart the code on the WUnderground site, there is a web service of sorts (not WSDL) already.  There is a cgi-bin call back to the server that uses the corners of the GMap control to return a list of weather stations in the map's visible area.  Pretty sure using that would get you into some sort of trouble though.  For now, I'll wait for a response back instead of going down the aforementioned path, but if I get really bored over a weekend, it could happen.