Tangent: I'm curious about HP's hostname taxonomy. I.e. What products or content live under www8 vs www2 or www7. http://www8.hp.com/.. .
The names are (or were) geographic and divisional. Their infrastructure is (or was) pretty old school. While they do have load balancing and such, it is often of the form of redirects based on locality or other information. People in Hong Kong or China starting on HP.com in the US would find themselves bounced over to servers in Hong Kong, based on their language and where their traffic was being routed to/from. They mirrored tons of their data automatically with Squid proxies and just additional web servers. So, once a user gets directed to a local HP site, they'll tend to stay on it...and if content doesn't exist in the local cache, it'll pull it from the origin. HP has tons of public server names not just in the wwwN.hp.com space.
So, while I don't have specific information about www8 vs www2, etc. Based on my own experience with their infrastructure, I would assume it is the most boring explanation. They need several servers to provide good service, so they just give various divisions their own servers. This was the case in Hong Kong, Korea, and China, where my work was deployed. They do have load balancing and content distribution and such (and did even back then), but the actual web services were pretty traditional; they just ran on a server somewhere.