more later, but trust me…this is FANTASTIC!

image (c) by SwitchLightingco.com; used by permission

Since I’ve made a few public promises (on Twitter, no less) stating that I’d actually post something by the end of the year (2011; last post was in June 2011), I’ve decided to actually KEEP that promise.  To that end, here’s my quick ‘n dirty post for the end of the 2011.

This is one of those strange years that I hope you’ll never have to experience.  To recap:

• I left EMC in October of 2010 for a small startup called Cirtas Systems which promised to fundamentally change the process of getting data to the cloud from your SAN environment.
• In April of 2011, after some long & hard fought victories with customers and our own engineering/development, Cirtas folded up shop.  Maybe next year I’ll delve into the specifics there but, suffice it to say, customers WANTED the product but we couldn’t provide everything they NEEDED.  This left me without a job but with a lot of promise out there.
• From April until August 2011, I interviewed with:  VMware, EMC (Education and Green Plum), DataDirect Networks,  BlueArc, Hitachi (HCAP, Parascale, et al.), Riverbed, Nasuni, Panzura, and Juniper Networks before finally landing at Symantec Corporation on August 1st.
• During this interview process, I did a small 2-3 week contract gig with ESG working on a VPLEX article.
• Met a lot of great people in the process and while I did disappoint a few folks who offered, I believe the ultimate landing choice was actually quite the good one.

So, that’s my year in review.  I would LOVE to talk more about the Symantec gig but as I’m still trying to figure out some of their social media policies, it’ll need to wait a few more weeks.

see you in 2012!!

Image via Wikipedia

One benefit of being gainfully under-employed is having those brief bursts of inspiration that allow you to get on paper (or blog) those streaming bits of ideas that could change your destiny.  Perhaps there’s a bit of hyperbole worked in there (ok, a whole lot) but the fact remains, when the mind is allowed to roam a bit, inspiration comes.  Given my background in cognitive sciences and such, this is either one of the most dangerous things to allow or one of the most precious.  Having gone through close to 30 interviews (that’s counting people, not companies) since Cirtas let myself (and 20 odd others) go on April 15th, 2011, I can tell you that one of the most commonly asked questions has been: “If you could do anything, what would it be?”  (For comparison, the most asked question is: “Explain the switch from psychology to enterprise IT.”)  It can be relatively hard to nail down what exactly I view a dream job to be, but given the relatively wide variety of experiences I’ve had over the years, I’ve come to rely on a few common characteristics which I’ll highlight in the following paragraphs.  However, along the way, newer ideas and concepts have come into view and for your enjoyment (and to annoy my wife who’s trying to sleep while I type this) I’ll try to drag them into the light.  With all the precursors aside, then, let’s get into the meat of what this post is about: designing my dream job.

Dream Job: The Components

Here’s my global plan for what I’d love to do followed by some careful unpacking (knowing that I’m in process on a few things as I sit here and write this).

Skunkworks

In what is perhaps one of the most overused quotes on earth, Thomas Alva Edison noted that “genius is one percent inspiration, ninety-nine percent perspiration.” I’ve somewhat taken this to heart in my life in that I’m admittedly not the sharpest tool in the shed.  I make up for it, however, in attempting to be the most useful and to a certain extent, I nail that 99% perspiration mark pretty bang on. That being said, I’ve always had a vision for creating my own little “skunkworks” team dedicated to finding, breaking, designing, manipulating, etc. technology. Part of this vision has always been on emerging technology but grounded in what is available today.  This truly becomes a fulfillment of Edison’s credo mentioned previously.  This skunkworks team would operate free of a type of technology and would seek innovation through perspiration to hopefully inspire genius.  I see this as being a chartered group INSIDE of a larger enterprise, not just a small consultancy tied to linecards.  So, let’s tear this apart a bit more, shall we?

The Core

Having read about the humble beginnings of Dell, HP, Apple, Microsoft, et al., I have noticed a dogged pursuit of an idea (and much more) tends to be their overarching focus.  As I envision the core of this skunkworks team, I want to ensure that I create an atmosphere that allows ideas, however conceptual or nascent, to have their full voice.  Consistently, this usually requires voices that aren’t just engineers but practitioners as well.  The functional aspects of the team are to create from something (not often from nothing) so, having folks that have keen insights into technology in general are important.  I’d probably class the team membership as functional engineers rather than process or systems engineers.

The core also needs to be agile.  I don’t give a flying rip about ITIL, Scrums, etc. but flexibility in thinking outside the box is vital.  I don’t envision this as the frenzied reality of a startup but rather a nuanced understanding that even at 1130pm (when I’m writing this post) innovation happens.  Living outside the confines of a 9-5 become vital and in a global economy, it also becomes worthwhile to have an international team.

The Gear

Any skunkworks team, whether aerospace or marketing, needs gear.  I can write on the back of napkins all I want to capture the germination of an idea, but if I have nothing to start working against, that idea can die pretty quickly.  I know my attention span and I know what is needed to tease the most out of it.  To capture ideas relies on more than mind mapping, Evernote, Dropbox, Facetime, and a napkin.  It relies on an environment that allows for quick exploration and easy clean-up.  I’ll leave this section vague for now, but considering I’m interested in technology, a few racks of servers, storage, and fabrics shouldn’t hurt.

Summing it up

Wrapping the sections above up into a tidy package results in the following:

My dream job would consist of being part of (or leading) a small, agile team of technologists chartered to develop creative solutions to customer problems.  This would be a combination of customer facing solicitations (e.g. the “problems”) along with formative lab and personnel access.  This team would be chartered and equipped to operate outside the political bounds of an enterprise “host” (defined as the parent company) in order to free itself from artificial and unnecessary political dalliances and structures.  This team would be measured on innovation and the ability to solve extant problems, not based on sales.  It would truly be an incubation tank for innovation with productization a distant objective.

Dream Job: The Characteristics

So, I’ve put a few components of my dream job on paper (core team and gear) and summed them up nicely.  However, the physical assets of a team are only part of the equation.  I’m going to attempt to unpack a few more intangibles.

Challenging

I wouldn’t have waxed poetic on my skunkworks team if I didn’t believe there were real challenges to be solved.  In this emerging cloud world, there are plenty of opportunities that present themselves and solutions to be wrought.  Half of the battle in determining value is answering current challenges while proactively seeking to head off future “threats.”  There is challenge in sustaining a product for sure but there is also a feedback loop that needs to take sustaining activities and feed them into a proactive engine that seeks to remedy the same while looking ahead to variants.  Any job that I step into needs to encompass this value; that is, challenges feed both the proactive and the reactive. Any job I evaluate, then, needs to embrace those roles as distinct but interdependent functions and seek to maximize the knowledge that can be gained from each.

Accidents

While I was working for EMC, I had the privilege of running a small lab in Hopkinton.  This was truly the “mad scientist” think tank for me and allowed for a lot of trial and error testing all in the name of productization.  This where I shot the Cisco C200 M1 unveiling video (see it here) and had a lot of fun with testing new technologies (some that I can’t talk about).  Getting back to the point, this lab offered a chance to grow by allowing room for failure.  Any job that I step into needs to understand the role of failure as a learning process and weight its value accordingly. I (along with everyone else on this glorious planet) are human and we make mistakes.  Mistakes are valuable as learning tools and when they happen within appropriate bounds, they can be formative and powerful.  I am in NO WAY advocating that a job should have a built-in “mistake factor” but that acceptable risk and reward must be present.  To offer anything else is frankly working against the nature of mankind.

Personalities

Since I’ve already mentioned “agile” above, I felt I should clarify things a bit more.  Classic business has always existed with the idea that strong, measurable goals equate to the best performance. However, as organizational psychologists have been quick to point out, maintaining this type of environment invariably leads to a squelching of capabilities since there are such a wide variety of personalities and capabilities.  Any job that I step into needs to have an understanding that I am not a cookie cutter individual or personality.  My “gift” (if it can truly be called that) is that I’m another lens that you view your product through.  I’m Dave Graham and I see… <insert pun of your choice here; “dead people” was my personal favorite>.  Point being, I’m going to be unique and I very well can be that missing perspective you need.

Fluid

Just because the business has “always done it that way” doesn’t mean it’s the best way.  Albert Einstein was quoted as saying “insanity [is] doing the same thing over and over again and expecting different results.”  Applying this to organizations, rigidity has always been “the same thing” and enterprises have constantly tried to turn what they have always done into something new.  I’d argue that some of the products that are being introduced in the converged space today match this criteria perfectly.  Consequently, any job that I step into needs to understand that the old way of doing things isn’t necessarily the best and that sometimes, new perspective is needed.  Putting lipstick on a pig results in a pig with lipstick; patently useless to anyone except for the Miss Universe pageant and perhaps, Donald Trump.  Then again, sometimes the old way is best. Let’s find that out together, shall we?

Summary

This may seem like a 1500 1672 word op-ed piece that isn’t worth your time but, as you work through your career, if you’ve not considered who you are and what you want to be doing, you’re missing a golden opportunity.  Learning what works and what doesn’t is a constant challenge and finding an environment that fosters this type of introspection and growth is hard to come by.  What I hope I’ve been able to do (outside of keeping my own prospects intact) is to get you thinking and to use that thinking as a springboard to greater things.  Comments and feedback welcome.

Image via CrunchBase

This morning, Dave Cahill (@dcahill8) posted a rather in-depth look at Carbonite and provided a counter to their business model by including Dropbox.  While Dave is a conservative guy, I’m really not, so, I took the challenge to hopefully expound upon what I think is Dropbox’s COGS model.  The original article is here: The Economics of Carbonite and I’d STRONGLY advise you to read it prior to coming here.

In my mind, there are two different scenarios:
a.) DevPay – in which each user is given their own Amazon identity but superimposed over their account is Dropbox’s metadata thus giving them a “slice” of revenue that Amazon makes off of data.
b.) Superuser – in which Dropbox simply provisions “buckets” for customers underneath their master account thus allowing them to tap into Amazon’s tiered pricing structure.

Scenario A makes SOME sense but I’m unsure if Dropbox can programmaticly sign up end-users for discrete S3 accounts without some sort of machinations with Amazon’s data and privacy policies. Consequently, what I’ll discuss is scenario B.

In scenario B, if a user signs up for trials, Dropbox provisions a “bucket” underneath their US Standard region S3 account and obfuscates the bucket name (randomizing using alphanumeric characters). By creating the bucket underneath their account, Dropbox can now actualize a cheaper scale than if they went with scenario A.

For a working example, let’s assume several things.
a.) Dropbox has 500TB of data stored in S3
b.) Dropbox is paying rates listed HERE: http://aws.amazon.com/s3/#pricing for US STANDARD region only (not US West which is more expensive)
c.) Dropbox uses Standard (4 replica; 2 DC) storage. I’ll provide metrics for RRS as well.

So, for 500TB of storage, Dropbox is paying:
storage (standard) per month: $0.095
storage (RRS) per month: $0.063
transfer (IN): $0.10
transfer (OUT): $0.08
-
Storage Total for 500TB (500,000 GB)
standard: $47,500
RRS: $31,500
-
transfer (IN): $50,000 (this # is skewed as they’re not transferring 500TB per month but this provides a wholistic ingest #)
transfer (OUT): $40,000 (this # is again skewed but would show what it’d cost to shove 500TB downstream from Amazon S3)

As you can tell, Dropbox is in a rather perfect position to cover their expenses without much effort and with minimal investment in infrastructure (I’m assuming they’re using some level of EC2 involvement for control plane, etc.) they’re on a perfect trajectory for profitability @ scale.

What do you think?

cheers,

Dave

Related articles

• Weekly Poll: Will Apple Compete With Dropbox? (appreaders.com)
• Weekly Poll: Will Apple Compete With Dropbox? (mac.appstorm.net)
• Dropbox Users Save 1 Million Files Every 5 Minutes (mashable.com)
• Dropbox Interview (ghacks.net)
• Dropbox Faces Security Controversy (appreaders.com)
• The Economics of Dropbox (w2lessons.com)
• At Dropbox, Over 100 Billion Files Served – And Counting (gigaom.com)
• Dropbox Security (schneier.com)
• Amazon Cloud Drive Is Not Dropbox (stream.thisisapipe.com)
• Dropbox Users Save 1 Million Files Every 5 Minutes (fakeiitian.com)
• Cloud Storage Faceoff: Windows Live SkyDrive vs. Dropbox vs. Amazon Cloud Drive (mjou812.wordpress.com)

Since it’s been roughly (i don’t know) several months since i last wrote (and yes, i’m doing the e.e. cummings thing by only using lower case letters), i decided it was time to motivate the sedentary gray matter between my ears and actually put finger to keyboard to…pontificate, really over the recent events in the Iron Mountain stepping-out-of-the-cloud debate.  Coupled to that was a challenge from Val B @ NTAP to expound upon my assertion that Iron Mountain, Nirvanix, and Nasuni were all stratified differently in the cloud space.  So, without further ado, here’s my thoughts.

(brief editor’s note here:  I’m really not doing a ton of research into specific features/functionality here.  just reporting what my end users are seeing and what reality, as unfortunate as it may be, dictates)

Nasuni.  Nasuni is a MSO offering where the “manager” is Nasuni and the offering is a limited scale scalable, semi-SMB 2.0 compliant set of virtual machines.  I’m not trying to disparage what they’re doing because honestly, it’s a great product when positioned correctly.  However, if you’re looking for performance (e.g. speeds/feeds), you’re going to be out of luck.  Classically, this is a Small-Medium business product. The decoupling of Nasuni from the backend service is an interesting question to ask them;  typically, a customer runs their Amazon account directly through the service, paying “all in” to Nasuni.

Nirvanix.  Nirvanix is a hybrid of a cloud offering plus perimeter edge (or gateway style) deployment model.  As such, Nirvanix most CLOSELY mirrors what IRM was trying to do, but they’ve been moderately more successful.   I say “moderately” in that I’ve run across exactly 0 (zero, for those who need it spelled out) folks who actually use their product.  Moderately from the sense that, in my not-so-humble-opinion, their CloudNAS is a wasted effort when compared to Nasuni.  So, with Nirvanix, you’ve got backhaul (e.g. the “public” cloud portion) via their SDN and on-premises via hnodes and/or CloudNAS.

Iron Mountain. Iron Mountain approached the cloud like another business model to be tackled.  as a “master” of backup, the assumption was made that the same model could be made to work using the existing customer base plus some on-premise hardware that would accelerate the writing to the cloud for digital asset management (assets being loosely defined as backup/archive). to further ‘extend’ functionality here, Iron Mountain brought to bear two discrete clouds; one for their archiving services and one for the backup services.  The problem here is in the approach; rather than create a SOA-based architecture, IRM went for the retrofit…and lost.  It’s unfortunate, to be sure, but certainly not unexpected given the momentum in the cloud storage space.  With application level “integration” (albeit loosely), IRM essentially looked like a scaled-down version of Nirvanix with software capabilities.  Target market here was everyone, SMB, Commercial, Enterprise with (my opinion) the biggest folks involved being commercial and enterprise, not SMB.

Conclusion

The cloud is constantly evolving and frankly, we’re only at the tip of the “cloud darwinism” cycle.  many more CSSPs will be subject to closure and it’ll be the strongest that will survive, both from standpoint of application integration and perimeter reach.

UPDATE:  it’s also important to look at who controls the data.  IRM was on-pre + cloud w/applications.  Nirvanix is application agnostic but self contained.  Nasuni is on-prem with no owned cloud but multiple backends…

Related articles

• Nasuni solves tricky cloud storage problems (zdnet.com)
• Report: Iron Mountain to Shutter Cloud Storage Service (pcworld.com)
• Front Porch Digital Reaches for the Nirvanix Cloud (prnewswire.com)
• Bruised Iron Mountain gives up on storage cloud (go.theregister.com)
• Nirvanix Announces New Webcast: Stop Your Backup Pain with Cloud Storage (prnewswire.com)

I know, I know.  This post isn’t about my work @ Cirtas Systems nor is it about the fundamental shift in storage technologies away from on-premise to cloud. Rather, it’s about the adventures I’ve had since getting my iPhone and attempting to make it a worthwhile replacement for my old Blackberry Bold 9700.

The Basics

I grabbed a 16GB iPhone 4 from my local AT&T reseller friend (let me know if you want one…he’s a killer guy) as my starting canvas.  From there, utilizing the Greenp0ison jailbreak, I installed Cydia and, here’s where it gets interesting.  I’m going to break out my applications by Jailbroken (via Cydia) vs. normative (AppStore).  Let’s start with Jailbroken.

Jailbroken Apps

One of the things that you have to consider is that jailbreaking (for me at least) is being utilized as an EXTENSION of the iPhone capabilities, not as an abject “rage against the man” type thing.  I did it specifically to extend functionality that I expected to be there from the get-go as well as to optimize my day-to-day business experiences.  Here’s what I’ve installed:

1. SBSettings.  Above all else, this allows for quick toggling of major phone features such as 3G, EDGE, Processes, Brightness, Bluetooth, 3G Unrestrictor (more on this guy in a moment), WiFi, and SSH.  You can add additional settings as you go along.
2. 3G Unrestrictor.  Some apps require being on WiFi else you can’t download or use them.  AppStore apps above 20Mb and FaceTime are two such offenders.  3G Unrestrictor tricks these apps into thinking that they’re on WiFi when in actuality, you’re not. Good times here.
3. AptBackup.  You nuke your jailbreak install and you lose your apps (or so I’m told).  AptBackup preserves the essence of these apps and allows you to re-install them.
4. Winterboard.  themes and Springboard manipulator.
5. Intelliscreen.  At-a-glance data gathering from your lock screen.  Some irritation with the configuration here (i want to lose the weather report but i can’t lose it), but the ability to look quickly at your latest emails and SMS messages without having to unlock every single time is quite refreshing.
6. MyWi 4.0.  If you travel you need this. This tool allows you to use your iPhone as a WiFi hotspot and route the data over 3G.  So far, haven’t gotten nailed for tethering charges on this so, hopefully it pans out.  WARNING:  i’d STRONGLY suggest that you leave your phone plugged in as this sucker eats battery.
7. Iconoclasm.  Instead of 4 icons per line, I prefer a higher density.  This tool allows me to have up to six icons a line which, in my opinion, cleans up my interface and allows for greater density.
8. Action Menu.  This is a more robust version of the “press/hold” action menu that Apple ships with iOS 4.1.  Allows for better interaction with source/destination.
9. Shrink.  This app allows me to shrink the text and image of an application on Springboard such that, when combined with Iconoclasm, I can get legible text + iconography for my apps.  Huge UI difference here.
10. Infiniboard.  Technically, Infiniboard allows me to vertically scroll a dock screen.  Haven’t installed enough applications to test this out yet, but the promise is huge.

Paid/Free Applications from Appstore:

1. Google.  Enough said here.  You need it, you want it, and it’s FREE.
2. Foursquare.  Yes, I use this.
3. TripIt.  I’m a TripIt Pro user.  The information you can gain here is absolutely critical if you travel frequently.
4. Engadget.  Yup, I’m a “Gadget Head”  Can’t live without this one.
5. Pandora.  Sometimes you just need tunes on the go.
6. Financial Apps:
   1. Liberty Mutual.  Great app for getting ahold of my insurance agent.
   2. myWireless (from AT&T).  Good to have for those times when you absolutely need to know how far over your monthly SMS volume you are.
   3. Mint.com.  If you’ve used this, you’ll realize this is critical for keeping track.
   4. Receipts.  Paid App that allows you to capture receipt information for travel expenses, photograph them, send them to Evernote, Google Docs, Bonjour (via Wifi), or email.  Very good app with some small issues with Evernote.
7. Echofon.  I prefer this to Tweetdeck but I’m not necessarily sold vs. Twitteriffic.  YMMV.
8. Starbucks and Starbucks Mobile Card.  Enough said here.
9. Evernote.  One of the KILLER iPhone/iPad apps.  This is almost a requirement for me to keep my data synced up in my ADHD moments.

Got any other suggestions? Let me know and I’ll be happy to give them a whirl!

Cheers,

Dave

Related articles

• 10 Best Apps For Jailbroken iPhone (mademan.com)
• Install FaceTime To Your Jailbroken iPhone 3GS With FaceIt-3GS (cultofmac.com)
• FaceTime now works on (jailbroken) iPhone 3GS (geek.com)
• Jailbroken iPhone 3GS gets FaceTime… sort of (tuaw.com)
• You Can Now Use FaceTime On The iPhone 3GS (macstories.net)
• Guide to Cydia Themes (brighthub.com)
• Top Ten Cydia Apps for the iPhone (chris.pirillo.com)
• New Cydia Layout Coming To iOS 4.2 (pocketnow.com)

So, it appears that I’ve been relatively successful in casting some level of intrigue around where I’m going after EMC. I’ve heard everything from VMware to Acadia to heaven-knows-what and while each of these companies are AWESOME for what they do, they’re not what’s grabbing my attention.

When I started into the cloud space, I was amazed at the capabilities that “the cloud” offered. Whether you choose to use the public, private, or (dare I say it?) hybrid monikers for how you implement a cloud ecosystem, one fact still remains: data needs to moved. Obviously, EMC has spent a considerable amount of time and effort into making solid product set in vBlock and Atmos and the recent acquisitions of Bycast by NetApp, the partnerships with Caringo and Cleversafe by others, et al. all serve to drive this point home. Face it, the cloud is here and it’s not going away.

With that in mind, I decided (and it wasn’t an easy decision) to look at some of the technologies that are being developed in the cloud space and jump in with both feet. The initial brush with this was Atmos. As one of the guys responsible for the development and sustaining of Atmos Virtual Edition (I won’t claim this was my idea by any stretch…there’s a LOT of talent wrapped up in the Atmos group that had input here), I recognized early on that easing transitions to the cloud by “re-using” hardware that was already present was a good thing. Virtualization made this even easier as everyone these days is thinking along those lines…Once I saw the impact that Atmos Virtual Edition had, the next logical step was the migration of block assets to the cloud, whether this be Atmos, S3, Iron Mountain Digital or another technology. To that end, on October 25th, 2010, I will become a Senior Systems Engineer at Cirtas Systems, Inc.

I’ll be writing more on Cirtas and their exciting Bluejet appliance later (as I get into the thick of things) but I’m very impressed with the capabilities that they offer and look forward to working with you (EMC, NTAP, HP, Dell, et al) in this exciting space!

See you on the other side…

cheers,

Dave

Related articles

• Time for something new…. (flickerdown.com)

After 3.5 years at EMC, I’ve decided it’s time for a change. During my time at EMC, I’ve been able to participate in some really cool stuff (Atmos, V-Max, CX4, some upcoming technologies you’ll be sure to hear about, etc.) and really felt valued both as an employee and as a friend (to some).

I’m going to miss my friends at EMC but, lest you think I’m going to disappear off the face of the earth, you’ll soon see me in another role that is very complementary to something that is near and dear to my heart: the cloud.

I’ll save the announcement of where I’m going for another day but effective October 22nd, 2010, I’ll be ending my tenure at EMC.

cheers,

Dave

Contrary to what it appears, I’m actually alive (and typing this from the Blogger’s Lounge @ EMC World 2010)…

Been a busy month or so and lots of stuff going on (that I can/can’t talk about) so, i’ll keep this post brief.

Suffice it to say, I’m here, have no intention of going away, and will continue to try to bring my sense & perspective on things at EMC.

cheers,

Dave

Just a quick note from the field (as it were).  If you’ve been blessed enough to get a Cisco C-series server, there’s a nifty new Cisco Integrated Management Controller (CIMC) release available as of today’s writing.

Version 1.0(1e) was the shipping release as of January 2010.

Version 1.0(2) is the latest point release available as of March 2010.

To update your CIMC (this assumes you’re using either TFTP or the Browser upload function):

a.) Download the “c200-m1-cimc.1.0.2.zip” file from Cisco’s Support Site (you need to be registered on the Cisco site to do this)

b.) Unpack the archive to it’s own directory and find the “upd-pkg-c200-m1-cimc.full.1.0.2.bin” file. This will be used for your update. (Note: Previously, you would just upload the entire *.zip file via the browser. However, there is a known issue with this process so, you can use the “full” bin file for the CIMC updates.)

c.) Go to the “Admin” tab in CIMC and select “Firmware Management.”  Your screen should look like this:

d.) The upload and install process should begin relatively quickly and look like:

e.) Once complete, you should see the following:

Click on “Activate CIMC Firmware” and you’ll be presented with this screen:

Click on “Activate Firmware” and the CIMC will reboot immediately.

Differences in the CIMC Interfaces between the versions

So, what changed?

Here are the changes I’ve been able to see so far:

Splash Screen:

vs.

Can you spot the difference?

Server Summary Screen:

vs.

Addition of PID, BIOS version, and updated boot order iconography.

Firmware Management:

vs.

Addition of BIOS section, the Recover Corrupt BIOS Action, and the Last Firmware Install section.

Overall Status *(found in the upper left hand corner of the CIMC screen):

vs.

Change from Server Health to Server Status

Overall, some very subtle changes but definitely ones that refine the end-user experience.

Hopefully this helps people out.

Cheers,

Dave G

Related articles by Zemanta

• EMC, VMware and Intel to Deliver Cloud Computing Compliance (apache.sys-con.com)