Not that I Don’t Trust You

by Administrator on April 15, 2013

We just completed great editions of our “New Rules:  Backup and Data Protection” seminar in Atlanta and Dallas last week.  (Thank you, Trish, from TechTarget for your great logistics and on-site management, and thanks to all who attended the events.)  At the Dallas event, I was struck by a funny happenstance…

Dallas was the first city, I believe, in which TechTarget loosened its rules and allowed sponsors to sit in the back seats and view the seminar.  Prior to this, they had to stay out of the room and listen with a glass through the wall or something.

Anyway, TechTarget asked me if I would mind letting them in, and I courageously agreed.  Truth be told:  I routinely piss off vendors (well, their marketing droids more than their engineering staff) with what I write; so, why not let them hear the words as they flow “trippingly from my tongue?”  It didn’t dawn on me until after the second hour of my three hour talk, when everyone adjourned to the vendor display area for lunch, that I had said critical things about cloud storage and cloud backup at an event where three of the four vendor sponsors were promoting cloud storage or cloud backup.  Honestly, I don’t naturally think of cloud when I think of IBM, or EMC, or Dell, or whatever.  However, this cloud verbiage was showing up on their signage.

Let me state my current thinking about clouds.

First, the term “cloud” has zero probative value and is a marketing term only — like software-defined networks, software-defined storage, storage area network, enterprise storage, tier zero, etc.  If I had my way, it would be stricken from the vocabulary of technology.

Second, private cloud appears to be a synonym for “managed infrastructure” — at least as it applies to idiotic terms like IaaS (infrastructure as a service), PaaS (no, not the egg coloring kit for Easter, but platform as a service), SaaS (storage, rather than software, as a service — I guess the software guys need another acronym; maybe AaaS).  The “as a service” thing suggests that we provide resources on a contract basis and in some sort of atomic unit of compute with an associated cost.  So, if I want to roll out 50 virtual desktops, I might obtain one unit of DataCore Software’s new virtualization appliance kit; 2 if I want 100, etc.  DataCore provides the software to manage the delivery of performance, capacity and protection in a predictable and manageable way in a private LAN/SAN setting.  To paraphrase Geico, provisioning virtual desktops with their technology is so simple even a neanderthal can do it.

Unfortunately, neither VMware nor other server layer hypervisors are as predictable.  Storage is simpler to virtualize than servers, I guess, due to the complexity of server workload relative to the simplicity of storage I/O.  (I am trying to be generous here.)

Management, ideally, should occur both at the level of plumbing and kit, and also at an abstracted layer that refers to services.  When I provision storage from my virtual storage pool, again enabled by DataCore, I am able to apply appropriate data protection services simply by checking tick boxes for CDP, snapshot, mirroring, etc. — that is, whatever services I want to extend to the data occupying this allocated storage.  The workload in question automatically receives network load balancing, performance improving caching (using DRAM in the server and FLASH if you so desire) and thin provisioning of capacity (across all spindles in the pool, rather than isolated to one stand of disk drives as in on-array thin provisioning).  These are services and their provisioning is theoretically so easy that users could do it themselves.  Very cloud like.

Beneath the services layer, however, I am careful to ensure that I have plumbing and kit management — the best being X-IO’s on array RESTful management.

Because everything happens inside the corporate firewalls, private clouds are thought to be more secure (hmm — or at least less prone to external interference than by inside ne’redowells), more likely to meet SLAs, and more capable of allocating and deallocating resources to workload from shared resource pools (maybe, if it is a mainframe:  x86 tinkertoys?  Not so agile.)

Public clouds, by contrast, could not possibly deliver security or a reliable SLA.  Why?  Because the ability to deliver secure dependable service is outside the hands of the cloud provider’s hands.  Most cloud providers I have spoken to are very earnest souls — meaning, they think they are on the cusp of a new wave of technology and that they are delivering a very valuable service to what few customers they have thus far been able to garner (88% of public storage cloud capacity are serving PaaS and IaaS vendors, not consumers!).

The fact is that the only way to keep data safe in a public network is not to put it there.  Moreover, despite your earnest desire to deliver an SLA, you are at the mercy of WAN connections and last mile connections, which are very much subject to jitter, latency, failure, maintenance downtime, etc.  If I am not mistaken, and please correct me if I am, all of the special QoS guarantees promised by switch vendors fall apart if data routes through a series of hops that include even one off-brand router in path:  so much for your bandwidth optimization and slip-stream technologies to expedite I/O across WAN links.  Moreover, WANs follow their own version of open shortest path first — an invitation to latency given that the “shortest path” refers to # of router hops not physical distance.  Bottom line:  as demonstrated by many problems with Amazon and other cloudies, the network is the boss, not the service provider.  Anyone who tells you anything else is pulling your leg.

Another fact:  IPvAC (IP over Avian Carrier) remains a faster way to deliver large amounts of data over distance than any WAN.

Then we get to another obvious point:  there are few if any real standards in the world of Clouds.  If anything, the momentum in IaaS and PaaS is running against standardization.  Instead, cloudies are teaming up with one server hypervisor stack peddler or another, setting the stage for cloud conflicts.  Clouds are server hypervisor battles writ large.  So much for the ENRON-like dream of sourcing commodity storage or servers from a “futures market” of providers on a spot pricing basis.

Finally, I have a clear recollection of a fellow back in the 70s who was selling hot site contracts for a facility that didn’t really exist.  His rubes never checked to confirm what they were paying for and all wrote checks for $25K or more that he cashed and took with him to a non-extradition country, where he lived happily ever after.  I encourage anyone seeking the services of a cloud provider to actually visit the facility that is being advertised.  Check to see whether the firm consists of a real “tier 1″ data center (or two, or three), or if the infrastructure is a beat up rack of Dell servers purchased on eBay stood up in a cage at some ISP or managed hosting vendor’s shop.  Find out how they are protecting your data while it is in their charge.  Make them restore data as a test.  In short, make sure that they are doing everything (and more) that you would do to platform, protect and archive the data from your systems.  While I can’t cite any independent surveys, I suspect that very few folks are doing  the due diligence that should be done before you outsource your data assets (and your control) to a third party.

Frankly, I hate all of the hype around clouds.  Claims of huge increases in cloud adoption, written by “analysts” who are being paid by the service providers and leveraging surveys of fewer than 20 respondents — half of whom are vendor plants, are finding their way into publications as “editorial” content.  They aren’t.

Lacking is any reference to history:  in the 80s, during a recession, we saw an interest in Service Bureau computing that waned shortly after the associated recession turned over; in the 90s, there was the phenom we called ASP/SSP (application service providers and storage service providers), all of which failed after the associated downturn in the economy (associated with the dotcom meltdown) was replaced by the housing bubble.

Today’s cloud stuff may very well be just another manifestation of the same historical phenomena.  If I am right, it is already starting to fizzle.

Anyway, that is what I had to say about clouds.  No offense to any sponsors, and I hope you will all prove me to be a complete idiot — out of touch with the real world trends that will shape tomorrow’s IT.  I kind of doubt it.

 

{ 0 comments }

Call to Action

by Administrator on April 13, 2013

Some of my friends who read this blog know that I lost my father a month or so ago.  He was aged and infirmed, and has gone to a better place, I’m sure.  But in his final years, we were frequently challenged by our interaction with the VA’s medical claims and records keeping processes.  Dad’s experience was probably much better than the more than 900,000 vets who’s claims today are in limbo with no resolution in sight.

I got so frustrated about this after watching a news broadcast on the subject a few days ago that I went on Twitter and challenged all of the snarky technologists to pony up and volunteer some of their self-vaunted brain power in an effort to help the VA overcome its database conundrums.  To my surprise, several responses were received — all affirmative and all enthusiastic.  If there is a way to build an all volunteer task force to fix the medical claims and records systems at the VA (including an apparent data sharing problem with systems at DoD), I intend to find it.

This starts with a letter to the President and to each of my Senators, which I have written today and will send of via snail mail on Monday.  Here’s the letter.

April 13, 2013

 The Honorable Bill Nelson
716 Hart Senate Office Building
United States Senate
Washington, DC 20510

Dear Senator Nelson:

As a constituent from the State of Florida, I have decided to start by penning this letter to you to begin an initiative that I hope will contribute meaningfully to the well-being of US veterans.

I am a career computer technologist, writer, IT consultant and a citizen who is very concerned about the current debacle that is our Veteran’s Affairs medical claims processing system.  I am not a veteran, but my late father was.  William A. Toigo was a Chief Petty Officer in WWII who, right up to the end of his life last month, experienced many challenges in obtaining promised healthcare services from the VA in St. Petersburg, FL.

In my discussions with representatives of the service, I was told about huge backlogs of claims driven in large part by significant inefficiencies in the computerized systems for patient records and claims management.  I am not an expert on either VA operations or medical claims processing, but databases are databases – and I, together with many of my friends and colleagues, have considerable experience with the underlying technologies.

I recently tweeted out a message to fellow technologists to gauge their interest in volunteering to help the VA fix its database issues, especially as they relate to interoperability difficulties with DoD personnel systems, which news reports suggest to be a key stumbling block in efforts to resolve the claims backlog.  The response was encouraging:  enthusiastic messages were received from many individuals who I regard as the biggest brains in database technology.  They wanted, as I do, to contribute their time and effort to do more for our vets than to simply buy them a beer and thank them for their service.

The question is whether there is a way that a highly qualified task force of technologists, operating on a totally voluntary basis, could work with VA and DoD to fix the technical issues.  If there is a possibility that we could help our Vets get their promised healthcare services, we would very much like to try. Please let us know.

Warm personal regards,

Anyone who is interested in participating in this effort, please let me know.  It is all very preliminary, and may come to nothing.  Doubtless the problems with the backlog are as bureaucratic as they are technical.  But it doesn’t hurt to try to reach out and to be of assistance to those who have served our nation and who now wait in queues for promised and much needed benefits.

{ 0 comments }

The Old In-and-Out

by Administrator on March 24, 2013

Just got back from Brussels and Storage Expo 2013.  Ivo and company did a great job and the event was top notch.  IBM’s storage rock star, Tony Pearson, was there and in great form — doing eight sessions over two days.  (I did the opening keynote on Day 1.)

I hope to see more of Tony at Edge 2013, IBM’s great educational conference, which is focused on storage and happening in Las Vegas on June 10-14.  I presented at Edge last year in Orlando and hope to reprise, but I haven’t heard yet whether there will be room for me at the inn (well, Mandalay Bay).  In any case, hope to see you guys there.   Here’s a link for more info.

Tomorrow morning, I am back in the sky — hopefully without painful flight delays given the weather front — heading up to Philadelphia and my next Storage Decisions Seminar, New Rules for Backup and Data Protection 2013, which happens on Tuesday.  So far, the show has been getting rave reviews from audiences in Toronto and LA.  The acid test is an East Coast audience, of course.  So, Philly, you’re it.  Hope to see readers at the show.  Details for registering for the free event are here.

Once I return to Florida on Tuesday night, I am not traveling again for about a week and a half.  (Yeah!)  So, I will be working on finishing chapters for my next book and developing some additional presentations, including one for a one night show in London later this year that I am thinking of modeling on Les Miserables, which has just returned to the London stage.

My “poster” idea…

 

Sort of derivative of this one, which is copyrighted to somebody else…

I hear they are back in London now…

{ 0 comments }

Low Price, Technically Acceptable

by Administrator on March 8, 2013

Got an email from an old editor of mine, Nick Wakefield of Washington Technology, inviting me to a webcast on Low Price Technically Acceptable Contracts, presumably aimed at Fed contractors.  Here was the invite, which I post as a courtesy to Nick…

Surviving Lowest Price Technically Acceptable IT Projects:
Maximize your Returns and Customer Satisfaction Ratings

Dear Jon,

Register Now for this exclusive roundtable webcast with Nick Wakeman, Editor of Washington Technology, to learn how you can maximize your customer satisfaction ratings, as well as returns on your Lowest Price Technically Acceptable IT projects.

Webcast: Surviving LPTA IT Projects
When: Monday, March 25th at 2pm EST
Location: Your Desktop
Cost: FREE

Join us to learn:

  • Recommendations to maximize customer satisfaction ratings
  • The importance of selecting the right tools to solve government technology challenges, while working within tight budget constraints
  • New approaches for putting together competitive, winning IT solutions for Cybersecurity, Continuous Monitoring and the Cloud
  • Strategies to maximize your returns on Lowest Price Technically Acceptable IT projects

Now, I am not saying that this would be of interest to everyone.  Heck, I may not even have time to attend it myself.  But there was just something about the title that made me think.  If there were a meme to be derived from the current state of affairs in IT in just about every company I visit it is the tendency for business decision-makers to prefer the least expensive approach that still provides what seems to be a technically acceptable outcome.

You could probably argue that it has always been this way, that no one wants to spend more money than they need to on a service or technology in IT.  Yet, as quizzical as it sounds, that is the opposite of what we are doing all the time.

In storage, where is the sensibility to cost in the purchasing that we do?  I am talking strategic costs, not tactical savings.

It wasn’t bad enough that we were paying name brand prices for kit that have exactly the same components as we could buy from no name vendors.  Now, we are repeating this tactical cost-cutting silliness with public “storage clouds” — which appear to drive down labor costs via outsourcing, but impact significantly the availability of data based on a issues with WANs and hosting services and may drive costs much higher for storage over time.

Another example:  We keep throwing storage IO boosters at VMware workload — PCIe Flash cards or Flash SSD or All Flash Arrays to expedite throughput.  But the choke point in the server is not a hardware choke point, it is VMware — something that no one seems to want to acknowledge — and we are just throwing more hardware at the problem, like a brute force attack, in an effort to cope with a symptom (low performance).

We spend all kinds of money to fix problems created originally by a “low price, technically acceptable” technology project (server virtualization a la VMware).

Look, I realize that VMware has its fanboys.  I imagine that there were a lot of shops where servers were inefficiently utilized at the resource level.  That was entirely the fault of server administrators and application developers, IMHO.  I say that with confidence because my servers were highly utilized, whether you are talking about a zSeries mainframe or lots of no name Linux boxes; Windows servers were a little less efficient, mainly because we liked to keep spare capacity available for irregular or unpredictable workload shifts.

I think one part of the problem I am beginning to see in my old age is the lack of elegance in programs I see today…in the coding sense.  When I first started my career, in mainframe data centers, memory was a scarce resource and adding disk space required a new building.  These parameters forced us to be stingy about using machine resources.

When I got my first PC, an Osborne 1, then later an IBM PC running Windows X.X, processors were slow, memory was expensive and hard disks were non-existent.  Again, the situation forced elegance in how we coded programs and used resources.

Today, with all storage capacities on all media growing ever larger, with processors dwarfing the speeds of early x86 chips, with all of the other advances that have made kit bigger, faster and presumably cheaper, all we really seem to have done is discourage anyone from being elegant with their coding and to treat all machine resources like they are limitless.  That is hardly the way to encourage resource utilization efficiency.

I don’t hate on poor VMware, but I do take exception with the narrative that surrounds it, that portrays it as the second coming of Christ that has been needed to drive order and discipline back into computing — in short, its cult appeal.

The fact is that server hypervisors don’t fix inefficiency.  Bad programs are still written.  We just stick them in VMs now.  Resources are still mishandled.  We just ignore that the hypervisor is what is creating the log jam and use the opportunity to sell more memory components into the IT shop, desperate to make their VM-hosted apps perform in an even marginally acceptable way.  We continue to instantiate apps on servers, where they consume electricity waiting for someone to use them — though, I suppose that stacking several in one box does marginally reduce the power consumption of a bunch of smaller servers each hosting their own apps.

Bottom line:  I am thinking a lot about what has become of my chosen profession, and how its core effort — Prometheus bringing fire down to man — has been bent and twisted.  Partly it is vendor marketecture that has created the current infrastruggle, but it is also idiotic consumerism — the idea that you somehow look more attractive on date night if you bask in the blue neon glow of an EMC VMAX or if you can brag about how you used 1900 spindles to get to 450K IOPS.

Yesterday, I had an online chat with a fellow from Tegile, a hybrid storage vendor that also has a pretty interesting blog.  The fellow was ex-3PAR and I asked him how receptive folks were for his kit, which uses far less hard disks augmented with Flash SSD to achieve throughput comparable to HP 3PAR with its very large complement of disk.  He said simply that it is two different approaches to solving the same problem and that marketing execution would determine which platform wins.  True enough, but this idea actually irritates me.  Why would you buy and power a huge array of disk if you could reduce the amount of spinning rust pulling power in your facility and derive the same value?

Bottom line for now:  after years of bent computing, we are having our feet held to the fire to go for the lowest price but still technically acceptable solution to every problem.  But this doesn’t seem to be driving elegance and excellence, only short term fixes to longer term problems — tactical measures that deliver short term cost savings but no long term improvements in cost containment, risk reduction or improved productivity.  What’s the sense in that?

My two centavos.

 

{ 0 comments }

Important Development at CeBIT 2013 That US Readers May Not Have Heard About

March 7, 2013

DataCore Software, a fellow Florida-based company, used CeBIT 2013 to announce the first “productization” of the remarkable work that CTO and Chairman of the Board, Ziya Aral, and his team having been doing with virtual desktop infrastructure.  We have blogged about DataCore’s VDI research here before and even posted some video interviews with Aral. What [...]

Read the full article →

Preparations Under Way for Storage Decisions

March 6, 2013

I get to do a keynote on cutting storage costs…   The other session covers LTFS and other tape technology developments that are driving the technology back to the forefront…   However it all works out, I will see you at SD in Chicago, NYC and San Francisco over the coming months.

Read the full article →

Signal and Noise

March 6, 2013

While I wasn’t in the room to hear the comment directly, IBM’s new storage chief, Ambuj Goyal, is reported by The Register to have stated that his objective was to move transaction storage away from disk to all-flash arrays.  Ultimately, he envisions an IBM that sells less storage. Later in the article, he clarifies that [...]

Read the full article →

Me and Clouds 3

February 19, 2013

Up til now, I have been conflating two ideas and referring to them collectively as clouds.  The two ideas are outsourcing and service provisioning, what some might call a “public cloud.” As the industry has insisted on drilling into our vocabulary, this is only one of three types of clouds:  public clouds (network-based outsourcing services) [...]

Read the full article →

Me and Clouds 2

February 19, 2013

Continuing from part 1… As I was saying earlier, I wrote a book about the progenitor of clouds (ASPs/SSPs, which appeared in the late 1990s) and after about 600 pages concluded that the idea, whatever its merits, would not survive.  The key issues were security (lack thereof), service level predictability (or lack thereof) and sustainability (definitely [...]

Read the full article →

Me And Clouds

February 19, 2013

Those who know me or who have heard me speak from time to time know that I am no advocate of cloud computing.  I’m not just being obstinate or iconoclastic in taking this position.  And I am not hiding under a rock or living in a bubble where news of the real cannot reach me. [...]

Read the full article →