Comment (1) Visits (6007)
Guy Kawasaki is hosting a Web Conference next week on The Art of Evangelism.By this he is referring to promoting products and services, rather than the trad
A few years ago, I myself had the official title of "Technical Evangelist" for the IBM System Storageproduct line. I never liked the title, and asked to use something else, but since I was part of ateam of "Technical Evangelists," I had to keep it. A lot of companies were using this as a title,I was told, and everyone knew that it was not a religious reference, but a marketing one.
Sometimes, words do not translate well into other countries or cultures. Four years ago, on theweek of September 11, 2003, I traveled to Kuwait, Qatar and UAE for a business trip to present thelatest on our storage products. On arrival in Kuwait, I had to fill out my "visa application" to enterthe country, and it asked for my "occupation/title" but there were not enough spaces to write "Technical Evangelist" so I just entered "Evangelist".
The two Kuwaitis behind the desk looked it up in their Arabic/English dictionary, discussed it, andweren't sure if they should shoot me, or take me to the back room to video tape my proper be-heading. Our official hostcame over to ask what was the delay, and they showed her the dictionary translation. She asked me,"Why would you put Evangelist as your title?" So, I gave her my business card, and told herthat my full title of Technical Evangelist did not fit in the space provided.
She explained to the two behind the desk that I had misunderstood the question, and misspelled theactual word intended was "Engineer". She showed them the agenda of the IBM Technical Conference I wasspeaking at, and the list of Oil and Construction companies that were attending. They looked upthe new title "Engineer", and agreed the translation was suitable for entry, and that these two words,Evangelist and Engineer, used enough similar letters they could understand how one might misspell one for the other.
Our limo took a small detour to the middle of the desert so that we could burn and bury the ashes of the remainder of my business cards, before arriving to the hotel. All of my powerpoint slides that listed my title were changed to "Technical Engineer". The events themselves went very well,as IT people are the same all over the world, and had no problem setting aside religious or poli When I got back to the United States, I shared my experience with my fellow team-mates, most of whom never leavethe country, and would never have thought this might happen. Management agreed to let us change our titles.That was good for me, as I had to order a new box of business cards anyways. Last year, I became "Manager of Brand Marketing Strategy" of the IBM System Storage product line.Now on business trips I just write "Manager" on the Occupation/Title line. It fits in every form I have ever had to fill, and translates properly into every language.
When I got back to the United States, I shared my experience with my fellow team-mates, most of whom never leavethe country, and would never have thought this might happen. Management agreed to let us change our titles.That was good for me, as I had to order a new box of business cards anyways.
Last year, I became "Manager of Brand Marketing Strategy" of the IBM System Storage product line.Now on business trips I just write "Manager" on the Occupation/Title line. It fits in every form I have ever had to fill, and translates properly into every language.
Comments (6) Visits (7928)
The Storage Architect writes in his post:
Array-based replication does have drawbacks; all externalised storage becomes dependent on the virtualising array. This makes replacement potentially complex. To date, HDS have not provided tools to seamlessly migrate away from one USP to another (as far as I am aware). In addition, there's the problem of "all your eggs in one basket"; any issue with the array (e.g. physical intervention like fire, loss of power, microcode bug etc) could result in loss of access to all of your data. Consider the upgrade scenario of moving to a higher level of code; if all data was virtualised through one array, you would want to be darn sure that both the upgrade process and the new code are going to work seamlessly...
I would argue that the IBM System Storage SAN Volume Controller (SVC) is more like the HDS USP, and less like the Invista. Both SVC and USP provide a common look and feel to the application server, both provide additional cache to external disk, both are able to provide a consistent set of copy services.
IBM designed the SVC so that upgrades can occur non-disruptively. You can replace the hardware nodes, one node at a time, while the SVC system is up and running, without disruption to reading and writing data on virtual disk. You can upgrade the software, one node at a time, while the SVC system is up and running, without disruption to reading and writing data on virtual disk. You can upgrade the firmware on the managed disk arrays behind the SVC, again, without disruption to reading and writing data on virtual disk.
More importantly, SVC has the ultimate "un-do" feature. It is called "image mode". If for any reason you want to take a virtual disk out of SVC management, you migrate over to an "image mode" LUN, and then disconnect it from SVC. The "image mode" LUN can then be used directly, with all the file system data in tact.
I define "virtualization" as technology that makes one set of resources look and feel like a different set of resources with more desirable characteristics. For SVC, the more desirable characteristics include choice of multi-pathing driver, consistent copy services, improved performance, etc. For EMC Invista, the question is "more desirable for whom?" EMC Invista seems more designed to meet EMC's needs, not its customers. EMC profits greatly from its EMC PowerPath multi-pathing driver, and from its SRDF copy services, so it appears to have designed a virtualization offering that:
A post from Dan over at Architectures of Control explains the anti-social nature of public benches. City planners, in an effort to discourage homeless people from sleeping on benches in parks or sidewalks, design benches that are so uncomfortableto use, that nobody uses them. These included benches made of metal that are too hot or too cold during certainmonths, benches slanted at an angle that dump you on the ground if you lay down, or benches that have dividers sothat you must be in an upright seated position to use.
This is not a disparagement of split-path switch-based designs. Rather, EMC's specific implementation appears to be designed for it to continuevendor lock-in for its multi-pathing driver, continuevendor lock-in for its copy services when used with EMC disk, and only provide slightly improved data migration capability for heterogeneous storage environments. Other switch-based solutions, such as those from Incipient or StoreAge, had different goals in mind.
Sadly, my IBM colleague BarryW and I have probably spent more words discussing Invista than all eleven EMC bloggers combined this year. While everyone in the industry is impressed how often EMC can sell "me, too" products with an incredibly large marketing budget, EMC appears not to have set aside funds for the Invista.
If a customer could design the ideal "storage virtualization" solution that would provide them the characteristics they desire the most from storage resources, it would not be anything like an Invista. While there are pros and cons between IBM's SVC and HDS's TagmaStore offerings, the reason both IBM and HDS are the market leaders in storage virtualization is because both companies are trying to provide value to the customer, just in different ways, and with different implementations.