This blog is for the open exchange of ideas relating to IBM Systems, storage and storage networking hardware, software and services.
(Short URL for this blog: ibm.co/Pearson )
Tony Pearson is a Master Inventor, Senior IT Architect and Event Content Manager for [IBM Systems for IBM Systems Technical University] events. With over 30 years with IBM Systems, Tony is frequent traveler, speaking to clients at events throughout the world.
Lloyd Dean is an IBM Senior Certified Executive IT Architect in Infrastructure Architecture. Lloyd has held numerous senior technical roles at IBM during his 19 plus years at IBM. Lloyd most recently has been leading efforts across the Communication/CSI Market as a senior Storage Solution Architect/CTS covering the Kansas City territory. In prior years Lloyd supported the industry accounts as a Storage Solution architect and prior to that as a Storage Software Solutions specialist during his time in the ATS organization.
Lloyd currently supports North America storage sales teams in his Storage Software Solution Architecture SME role in the Washington Systems Center team. His current focus is with IBM Cloud Private and he will be delivering and supporting sessions at Think2019, and Storage Technical University on the Value of IBM storage in this high value IBM solution a part of the IBM Cloud strategy. Lloyd maintains a Subject Matter Expert status across the IBM Spectrum Storage Software solutions. You can follow Lloyd on Twitter @ldean0558 and LinkedIn Lloyd Dean.
Tony Pearson's books are available on Lulu.com! Order your copies today!
Safe Harbor Statement: The information on IBM products is intended to outline IBM's general product direction and it should not be relied on in making a purchasing decision. The information on the new products is for informational purposes only and may not be incorporated into any contract. The information on IBM products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for IBM products remains at IBM's sole discretion.
Tony Pearson is a an active participant in local, regional, and industry-specific interests, and does not receive any special payments to mention them on this blog.
Tony Pearson receives part of the revenue proceeds from sales of books he has authored listed in the side panel.
Tony Pearson is not a medical doctor, and this blog does not reference any IBM product or service that is intended for use in the diagnosis, treatment, cure, prevention or monitoring of a disease or medical condition, unless otherwise specified on individual posts.
The developerWorks Connections Platform is now in read-only mode and content is only available for viewing. No new wiki pages, posts, or messages may be added. Please see our FAQ for more information. The developerWorks Connections platform will officially shut down on March 31, 2020 and content will no longer be available. More details available on our FAQ. (Read in Japanese.)
Stephen Colbert, of The Colbert Report, explains the name changes in recent mergers of the Telecommunications industry. A discussion on "changing names" and how that impacts storage seems like a good way to wrap up the week's theme on naming conventions.
Name changes are sometimes painful, but often times done for a purpose, such as to promote a family. In the US, when a man and woman marries, the woman often changes her family name to match her husband, and the kids all adopt the father's family name. I say "often" because there are times where the woman keeps her name, or adds to it in a hyphenated way. ABC News reported that a Man Fights to Take Wife's Name in Marriage. KipEsquire, a lawyer, writes about it in his blogA stitch in haste.
IT industry changes the names of products that people knew as something else. Other times, they re-use an existing name, when really it is or should be different from the original. Last year, I took on the job of helping transition from our brand "TotalStorage" to the "System Storage" product line under the new "IBM Systems" brand. I help decide what stays the same name or what changes, when it should change, and how to announce that change.
On the disk side, IBM renamed Fibre Array Storage Technology, or FAStT, which was pronounced exactly like "fast", to DS4000 series. This was a big improvement, as people couldn't seem to spell it properly, with variations like "FastT". Nor could people pronounce it properly, saying "fast-tee" instead. The advantage of "DS" is that it is both easy to spell, and easy to pronounce. The DS4000 series continues to be "fast", providing excellent performance for its midrange price category.
IBM's Enterprise Storage Server (ESS) line went from model E10, to F20, to 750 and 800. When IBM came out with its replacement, the IBM TotalStorage DS8000, some people asked why it wasn't named the ESS 900, for example. The DS8000 is quite different internally, new hardware design and implementation, but is highly compatible with the ESS line, and shares much of the same functionality from microcode. Last year, it was replaced by the IBM System Storage DS8000 Turbo. Again, newer hardware, so it was easy to justify the new name change from "TotalStorage" to "System Storage".
Renaming a product risks losing its certifications and awards. For example, IBM spent a lot of time and money getting the OS/390 operating system certified as a "UNIX" platform. When it was renamed to z/OS, IBM had to do it all over again. Learning from this experience, IBM decided not to rename the SAN Volume Controllerto a new designation like "DS5750", as it enjoys the "number one" spot on both the SPC-1 and SPC-2 performance benchmarks, and is recognized as the leader in the disk storage virtualization marketplace. Renaming this product would mean losing that collateral.
IBM's "other disk systems" the N series posed another set of challenges. The current DS line already has entry-level (DS3000), midrange (DS4000) and enterprise-class (DS6000 and DS8000) products. The OEM agreement that IBM has with Network Appliance (NetApp) resulted in a new set of entry-level, midrange, and enterprise-class products. But these didn't fit nicely into the DS3000-to-DS8000 continuum. Instead, IBM decided to go with N series, using N3000 for entry-level, N5000 for midrange, and N7000 for enterprise-class. These are different than the numbers used by NetApp for their comparable, but not identical, offerings.
On the tape side, IBM decided to name the tape drives TS1000 and TS2000 range, tape libraries and automation with a TS3000 range, and tape virtualization to the TS7000 range. A lot of tape products already had 3000 numbering that had to change to fit this new scheme. This is why IBM's popular 3592 tape drive was renamed to the TS1120. The replacement to the 3494 Virtual Tape Server was named TS7700 Virtualization Engine.
Obviously, you can't change the names of products that are currently in the field, but what about existing software with minor updates? IBM decided to leave "TotalStorage Produtivity Center" under the "TotalStorage" brand until it has a significant version upgrade. Many people say "TPC" as a convenient acronym when referring to this product, but TPC is a registered trademark of the Professional Golfers Association (PGA) to refer to its "Tournament Players Club".
How can anyone confuse "managing storage" with "playing golf"? One activity is full of frustration that takes years or decades to master, involving the need to understand a variety of equipment and techniques to use each properly to accomplish your goals; and the other is an enjoyable activity, immediately productive in front of a single pane of glass managing all of your DAS, SAN and NAS storage, from reporting on your files and databases to managing storage networks and tape libraries.
A client complained that their tape drives were not compressing data as well as it used to. Investigating further reminded me of a scene from the 1970's television show "All in the family", summarized well inAmerican Scientist:
... in one episode of All in the Family, Archie Bunker's son-in-law, Mike, watches Archie put on his shoes and socks. Mike goes into a conniption when Archie puts the sock and shoe completely on one foot first, tying a bow to complete the action, while the other foot remains bare. To Mike, if I remember correctly, the right way to put on shoes and socks is first to put a sock on each foot and only then put the shoes on over them, and only in the same order as the socks. In an ironic development in his character, the politically liberal Mike shows himself to be intolerant of differences in how people do common little things, unaccepting of the fact that there is more than one way to skin a cat or put on one's shoes.
Both agreed that socks go first, then shoes, but the actual deployment was different.
In the case of this customer, a recent change was the use of "encryption" before the data reached the tape drive. In regards to compression and encryption, you should always compress first, then encrypt. Compression algorithms rely on frequency of data, for example the letter "E" appears more often in the English language than the letter "Z". However, once you encrypt data, those data patterns are randomized, and any attempt to compress the data afterwards is wasted effort.
With IBM tape encryption on either the TS1120 or LTO4 tape drives, we compress, then encrypt, the data when it arrives to the tape drive, so that the compression has some chance of getting up to 3:1 reduction. This compress-then-encrypt process can be done at the host as well, either from the application software or feature of the operating system.
So, just as the case between Archie Bunker and his son-in-law, there are many ways to deploy compression and encryption, just make sure you do them in the right order to get the most benefit.
I use two Cloud-Computing based photo-sharing services, [KodakGallery.com] and [Flickr.com], which serve two completely different purposes.
Formerly, this was Ofoto, but was acquired by Kodak. I started using this service back in 2002, and had over 12,000 photos uploaded over the past 8 years. I was able to share all my photos with my friends and family, and they could simply order whichever prints they want and have them shipped directly to them. They have incredibly high-professional photo-based products, like calendars and coffee table books, that you can produce from your own photos.
Sadly, the fine folks at Kodak Gallery decided they did not want my business anymore, and purged my 36GB of files from their system. To be fair, they did hint that they were having financial problems with an "Archive CD" offering, which would have allowed me to get a set of CDs or DVDs holding the high-resolution graphics of all my uploaded photos. This would have cost $150 or so, and if you uploaded more photos, there was no option to get the "delta" of photos uploaded since your last archive, so it would have cost me $150 every year or so to get an updated "backup" of my files. It seemed expensive and unnecessary at the time, given that I was sure that Kodak was not going out of business anytime soon, and that I was sure they took their own backups of all the photos that people put in their charge.
The problem is that Kodak Gallery was a free service, subsidized by people ordering physical prints and other products. As such, I got lots of email from Kodak every month, offering me free shipping, special promotions, and seasonal discounts. It was so much that I had all email from them automatically routed to a different sub-folder, that I would never look at, unless I was about to make a purchase and needed to find the best coupon code or free shipping option currently offered. This also had the unintended consequence that I missed the following series of notes:
Important: From the Gallery's General Manager (April 17)
Second notice: Our storage policy has changed (April 24)
Final notice: Your stored photos may be deleted (May 8)
We don't want to delete your photos (May 22)
All the notes mentioned the new "Storage Policy", here is a quick excerpt:
"The fact is, we store billions of photos for our 75 million members. The quality storage service the Gallery provides is significant in terms of our business costs.
So that we can provide the highest level of service, we're now asking all Gallery customers to make an annual nominal purchase in exchange for photo storage. We've modified our Terms of Service policy accordingly: if your Gallery photo storage equals 2 gigabytes or less, we're asking you to spend $4.99 annually; if more than 2 gigabytes, $19.99 annually.*
One last thought: We value and appreciate your business, and we want to continue our relationship with you in a spirit of mutual support and benefit. That's always been the Kodak way."
Since they had no response from me, nor saw any purchase activity, my 36GB of files were deleted on June 17. I discovered all of this when I contacted Kodak to find out where my files were last weekend during my "Spring Cleaning". I asked if I could at least get the final set of "Archive CDs", but they told me they were purged completely.
I understand the economy is in a recession, and many free cloud-based services are losing money and going under. I can understand they were faced with tough choices, Kodak opted to switch from a free service to fee-based service.
Albert Einstein defined Insanity as "doing the same thing over and over again and expecting different results." In general, if I am trying to get a hold of someone, and email isn't working, then I try something different, try them by phone, try them by snail mail, and so on. With the deluge of emails, people sometimes declare "email bankruptcy" by deleting everything in their inbox after coming back from vacation, or implement filters to automatically route mail to separate folders. I think it is unrealistic to expect that everybody reads every piece of email that you send them.
I would have liked for Kodak to have done at least one or more of the following, given that I had been such a long time customer, and they had earned hundreds of dollars in revenues from all the purchases, over the years, not just directly from me, but from my friends and family, of photos I uploaded to their website:
Send me a letter after not receiving any response from the first three notices. They sent me promotional materials and offers for 20 percent discounts, so they had my active snail mail address on file correctly. With 75 million users, it would have cost $33 million USD to send out snail mail letters to everyone, but for the subset of power-users who have more than 2GB of files, a snail mail letter might have gotten more $19.99 purchases they needed to stay in business.
Called me on the phone. Yes, they also had my phone number in their database.
Go ahead and charged my credit card on file $19.99 without a purchase, and given me a credit towards a future purchase. Something like: "You have not purchased anything in the last 12 months, so we charged your credit card, per our Terms of Service, but you can use this as a credit towards something in the next 60 days."
On the plus side, my "Spring Cleaning" project was done. You can't organize what you don't have anymore.
Flickr from Yahoo
I started using Flickr back in 2008 to hold photos and graphics for this blog. Flickr holds various sizes of photos that I can use directly with HTML tags. Clicking on the photo in the blog will take you to Flickr's service and allow you to see the large size resolution. The "Lotus Connections" that I have on IBM DeveloperWorks only offers 24MB of photo space, so Flickr was a nice alternative.
Unfortunately, Flickr had adopted a new policy that only the most recent 200 pictures would be visible, and I had already reached 170 photos. Rather than start deleting photos from my older blog posts, I opted to upgrade to the "Flickr Pro" account, with a fee of only $24.99 per year.
Hopefully, by paying an annual fee and choosing a successful and profitable Cloud-Computing company, I won't experience another traumatic loss. However, it does remind me that it is my responsibility to keep my own copies of these photos, just in case.
Fortunately, many "photo product" providers are connected to Flickr. For example, my publisher [<a href="http://www.lulu.com/">Lulu.com</a>] can access my Flickr photos to make photo-based coffee table books. As for my last eight years of memories that were lost, I will just have to treat it as if my house burned down. Rebuild and move on.
Well, it is Tuesday, and that means IBM announcements. This week many of my colleagues are attending Storage Networking World [SNW] conference. Normally, the most exciting announcements are reserved for the weeks these conferences are held, but IBM apparently made an exception this week.
New Factory configurations for XIV
The first announcement is for new [factory configurations] for the IBM XIV disk system. In the past, you could only order a partial 6-module or a full 15-module rack. Today, IBM announced that there will also be 9-, 10-, 11-, 12-, 13- and 14-module configurations orderable as well.
Some FUD out in the blogosphere led some to believe that these partial configurations had to be made full 15 modules within 12 months. That is false. You can order any of these partial rack configurations and leave them as is until you need more capacity. There is no obligation to buy more capacity with these partial rack configurations.
IBM N series N6060 configurations
This second announcement indicates that the N6060 supports[672 drives]. The N6060 is the latest midrange model of IBM N series unified storage.
If you are asking "What is a 672 drive?" don't feel stupid. It actuallyrefers to the number of external drives that can be attached to the N6060. Previously, it was mis-reported that the N6060 could support as many as 840 drives, but this was not correct, and this announcement is to fixthat typo.
IBM Passport Advantage Sub-Capacity Licensing
This last announcement today relates to IBM Passport Advantage[sub-capacity licensing].Pricing products is always a challenge. You want to come up with a pricing methodology such that people who get the most use pay the most, and those who get less pay less, in a manner that everyone thinks is fair. With commodities, it is simple to price rice by the pound, or fabric by the yard, but what about IT solutions?
Some of the IBM software is based on number of processors used, so that people who have the software running on multiple machines, or machines with multiple cores, should pay more because they are getting more value. This makes sense if this software is the only thing running on that server, but today you can also have server virtualization and are running many guest operating systems, each with different applications. The solution is to use "sub-capacity" licensing. If you have a quad-core processor server, but have four guest operating systems using 25 percent of this, then each OS should only pay for one processor's worth of licensing. Since different processors have different clock speeds, IBM has standardized the calculations to a mythical "Processor Value Unit" or PVU, with a corresponding IBM License Metric Tool (ILMT).
Initially, this will cover specific versions of Citrix Xen Server, Microsoft Hyper-V and VMware, but IBM has made as a "statement of direction" that it will extend this sub-capacity licensing and ILMT support to IBM PowerVM capability for its POWER systems.
I have often heard clients complain that their third party software vendor does not support these hypervisors. Sometimes, this means the third party vendor will not fix or provide assistance if the problem occurs in this environment, and other times, it is that the pricing does not favor this environment, you get charged for all the processors, even if your slice of the processor is much smaller.
If you are at SNW this week, stop by and say "Hi" to my fellow IBM collegues for me.
Continuing this week's theme on the z10 EC mainframe being able to perform the workloadof hundreds or thousands of small 2-way x86 servers, I offer a simple analogy.
One car, one driver
If you wonder why so many companies subscribe to the notion that you should only runa single application per server, blame Sun, who I think helped promote this idea.Not to be out-done, Microsoft, HP and Dell think that it is a great idea too. Imaginethe convenience for operators to be able to switch off a single machine and impactonly a single application. Imagine how much this simplifies new application development,knowing that you are the only workload on a set of dedicated resources.
This is analogous to a single car, single driver, where the car helps get the personfrom "point A" to "point B" and the single driver represents the driver and solepassenger of the vehicle. If this were a single driver on a energy-efficient motorcycleor scooter, than would be reasonable, but people often drive alone much bigger vehicles,what Jeff Savit would call "over-provisioning". Chips have increased in processingpower much faster than individual applications have increased their requirements, so as a result,you have over-provisioning.
Carpooling - one bus, one driver, and many other passengers riding along
This is how z/OS operates. Yes, you could have up to 60 LPARs that you could individuallyturn on and off, but where z/OS gets most of its advantages is that you can run many applicationsin a single OS instance, through the use of "Address Spaces" which act as application containers.Of course, it is more difficult to write for this environment, because you have to be a good"z/OS citizen", share resources nicely, and be WLM-compliant to allow your application to beswapped out for others.
While you get efficiencies with this approach, when you bring the OS down, all the apps on that OS image haveto stop with it. For those who have "Parallel Sysplex" that is not an issue. For example, let's say youhave three mainframes, each running several LPARs of z/OS, and your various z/OS images all are able toprocess incoming transactions for a common shared DB2 database. Thanks to DB2 sharing technology, youcould take down an individual LPAR or z/OS image, and not disrupt transaction processing, because theIP spreader just sends them to the remaining LPARs. A "Coupling Facility" allows for smooth operationsif any of the OS images are lost from an unexpected disaster or disruption.
Needless to say, IBM does not give each z/OS developer his or her own mainframe. Instead, we get to run z/OS guest images under z/VM. It was even possible to emulate the next generation S/390 chipsetto allow us to test software on hardware that hasn't been created yet. With HiperSockets, we canhave virtual TCP/IP LAN connections between images, have virtual coupling facilities, have virtualdisk and virtual tape, and so on. It made development and test that much more efficient, which iswhy z/OS is recognized as one of the most rock-solid bullet-proof operating systems in existence.
The negatives of carpooling or taking the bus applies here as well. I have been on buses that havestopped working, and 50 people are stranded. And you don't need more than two people to make thelogistics of most carpools complicated. This feeds the fear that people want to have separatemanageable units one-car-one-driver than putting all of their eggs into one basket, having to scheduleoutages together, and so on.
(Disclaimer: From 1986 to 2001 I helped the development of z/OS and Linux on System z. Mostof my 17 patents are from that time of my career!)
Bicycle races and Marathons
The third computing model is the Supercomputer. Here we take a lot of one-way and two-way machines,and lash them together to form an incredible machine able to perform mathematical computations fasterthan any mainframe. The supercomputer that IBM built for Los Alamos National Laboratory just clockedin at 1,000,000,000,000,000 floating point operations per second. This is not a single operating system,but rather each machine runs its own OS, is given its primary objective, and tries to get it done.NetworkWorld has a nice article on this titled:[IBM, Los Alamos smash petaflop barrier, triple supercomputer speed record].If every person in the world was armed with a handheld calculator and performed one calculation per second, it would take us 46 years collectively to do everything this supercomputer can do in one day.
I originally thought of bicycle races as an analogy for this, but having listened to Lance Armstrong at the[IBM Pulse 2008] conference, I learned thatbiking is a team sport, and I wanted something that had the "every-man-for-himself" approach to computing.So, I changed this to marathons.
The marathon was named after a fabled greek soldier was sent as messenger from the [Battle of Marathon to the City of Athens],a distance that is now standardized to 26 miles and 385 yards, or 42.195 kilometers for my readersoutside the United States.
If you were given the task to get thousands of people from "point A" to "point B" 26 plus milesaway, would you chose thousands of cars, each with a lone driver? Conferences with a lot of people in a few hotels useshuttle buses instead. A few drivers, a few buses, and you can get thousands of people from a fewplaces to a few places. But the workloads that are sent to supercomputers have a single end point,so a dispatcher node gives a message to each "greek soldier" compute node, and has them run it on their own. Somemake it, some don't, but for a supercomputer that is OK. When the message is delivered, the calculation for thatlittle piece is done, and the compute node gives it another message to process. All of the computations areassembled to come up with the final result. Applications must be coded very speciallyto be able to handle this approach, but for the ones that are, amazing things happen.
So, how does "server virtualization" come into play?
IBM has had Logical Partitions for quite some time. A logical partition, or LPAR, can run its own OSimage, and can be turned on and off without impacting other LPARs. LPARs can have dedicated resources,or shared resources with other LPARs. The IBM z10 EC can have up to 60 LPARs. System p and System i,now merged into the new "POWER Systems" product line, also support LPARs in this manner. Depending onthe size of your LPAR, this could be for a single OS and application, or a single OS with lots of applications.
Address Spaces/Application Containers
This is the bus approach. You have a single OS, and that is shared by a set of application containers. z/OS does this with address spaces, all running under a single z/OS image, and for x86there are products like [Parallels Virtuozzo Containers] that can run hundred of Windows instances under a single Windows OS image, or a hundred Linux imagesunder a single Linux OS image. However, you cannot mix and match Windows with Linux, just as all theaddress spaces on z/OS all have to be coded for the same z/OS level on the LPAR they run in.
The term "guests" were chosen to model this after the way hotels are organized. Each guest has a roomwith its own lockable entrance and privacy, but shared lobby, and in some countries, shared bathroomson every hall. This approach is used by z/VM, VMware and others. The z/VM operating system can handle any S/390-chip operating system guest, so you could have a mix ofz/OS, TPF, z/VSE, Linux and OpenSolaris, and even other z/VM levels running as guests. Many z/VM developers runin this "second level" mode to develop new versions of the z/VM operating system!
As part of the One Laptop Per Child [OLPC] development team (yes, I ama member of their open source community, and now have developer keys to provide contributions), I havebeen experimenting with Linux KVM. This was [folded into the base Linux 2.6.20 kernel and availableto run Linux and Windows guest images. This is a nice write-up on[Wikipedia].
The key advantage of this approach is that you are back to one-car-one-driver simplistic mode of thinking. Each guest can be turned on and off without impacting otherapplications. Each guest has its own OS image, so you can mix different OS on the same server hardware.You can have your own customized kernel modules, levels of Java, etc.Externally, it looks like you are running dozens of applications on a single server, but internally,each application thinks it is the only one running on its own OS. This gives you simpler codingmodel to base your test and development with.
Jeff is correct that running less than 10 percent utilization average across your servers is a cryingshame, and that it could be managed in a manner that raises the utilization of the servers so that fewer areneeeded. Just as people could carpool, or could take the bus to work, it just doesn't happen, and data centersare full of single-application servers.
VMware has an architectural limit of 128 guests per machine, and IBM is able to reach this withits beefiest System x3850 M2 servers, but most of the x86 machines from HP, Dell and Sun are less powerful,and only run a dozen or so guests. In all cases, fewer servers means it is simpler to manage, so moreapplications per server is always the goal in mind.
VMware can soak up 30 to 40 percent of the cycles, meaning the most you can get from a VMware-basedsolution is 60 to 70 percent CPU utilization (which is still much better than the typical 5 to 10 percent average utilization we see today!) z/VM has been finely tuned to incur as little as 7 percent overhead,so IBM can achieve up to 93 percent utilization.
Jeff argues that since many of the z/OS technologies that allow customers to get over90 percent utilization don't apply to Linux guests under z/VM, then all of the numbers are wrong.My point is that there are two ways to achieve 90 percent utilization on the mainframe, one is throughz/OS running many applications on a single LPAR (the application container approach), and the other through z/VM supporting many Linux OS images, each with one (or a few) applications (the virtual guest approach).
I am still gathering more research on this topic, so I will try to have it ready later this week.
One of the differences between IBM and the other storage vendors is that IBM is also in the business of middleware, application-aware backup software, and advanced copy services. This allows IBM to put togethersolutions that work to address specific challenges for our clients.
IBM has written a whitepaper on a cleverVSS Snapshot Backup for Exchange using IBM Tivoli Storage Manager and the point-in-time copy capabilities of IBM System Storage disk systems.
A problem in the past was that each vendor's point-in-time copy method had its own unique proprietary interface.Microsoft Developed Volume Shadow Copy Services (VSS) as a common interface front-end to resolve this concern.IBM Tivoli Storage Manager for Mail can invoke standard VSS interfaces, and this in turn can invoke FlashCopyon the IBM System Storage SAN Volume Controller, DS8000 series, or DS6000 series disk system.
You might be thinking: Wouldn't it have been less effort to just have TSM for Mail invoke IBM proprietary interfaces,rather than having to put full VSS support into TSM for mail, and then full VSS support into IBM's various disksystems? Perhaps, but IBM doesn't decide to do things because it is the cheapest way, we focus on what is theright way, and in this case, customers now have more choices, then can use TSM for Mail with IBM or non-IBM disksystems that support the VSS interface, and IBM disk systems can be employed into other uses for VSS snapshot.
Of course, we would like our clients to consider both TSM and IBM System Storage disk systems for a combined solution,not because they are required to make the solution work, but because both are best-of-breed, and whitepapers likethis show how they can provide synergy working together.
Long-time readers of my blog know that typically IBM makes its announcements on Tuesdays, but this week, we had an announcement today, Wednesday!
IBM announced agreements with Brocade, Cisco and Juniper Networks to help build more dynamic infrastructures. An IBM study estimates that the "digital footprint" of each person will grow from 1TB today to 16TB by the year 2020, and all of that data will need bandwidth to get around.IBM’s Data Center Networking (DCN) Initiative is focused on providing clients with solutions to address these three key areas in networking:
Partner for choice of networking products based and open standards to ensure clients can select from a full range of hardware options for data center networks. IBM will build on its strong partnerships with leading networking vendors to provide greater customer choice.
Integrate with IBM Data Center Products and Services. IBM continues to deliver a comprehensive portfolio of services for network design, integration and management from IBM Global Technology Services (GTS).
IBM differentiates itself with Common Data Center Management, where we can bring together software products, such as IBM Systems Director and Tivoli portfolio, to create what we refer to as a "Unified Service Management" software platform.
Here's a sample of what IBM announced:
IBM continues its strategic support for Fibre Channel over Ethernet (FCoE) with a Converged B32 switch, and Converged Network Adapters (CNA) for IBM System x servers. A CNA card does the job of both the Ethernet Network Interface Card (NIC) as well as the Fibre Channel Host Bus Adapter (HBA), reducing the number of cables from each server.
IBM and its Business Partners will resell the Cisco Nexus 5000 Series Switches, a leading family of high-performance, low-latency switches for data center networks supporting lossless 10GbE, Fibre Channel and Fibre Channel over Ethernet (FCoE).
IBM will OEM selected Juniper EX and MX switches and routers. This expands upon IBM and Juniper's long-term relationship that includes a reseller agreement with IBM Global Technology Services, collaboration on Juniper's Stratus Project, and IBM's ten worldwide Cloud Labs.
Continuing my coverage of the ITSO Cloud Social Media Residency, the second day explained the ITSO Residency method of blogging, which was somewhat different than the method I presented on the first day.
Hillary explained how to find commercially-licensed stock photos, clip-art and graphics from various IBM repositories.
I generally use my own photos, drawings and charts, cropped and enhanced using the GNU Image Manipulation Program [GIMP] software tool. Sometimes I find graphics under a [Creative Commons] license.
These additional resources for photos will definitely come in handy!
Caroline Wall, IBM ITSO Copy Editor
While having blog posts with a [few misspelled words] and grammatical errors demonstrates [warts-and-all] authenticity, I make a point to double-check the spelling of proper names: people, companies, brands, locations, products, services and solutions.
Caroline explained the process of submitting blog proposals, and if approved, how to submit the blog post written in MS Word or Lotus Symphony. The ITSO team felt most residents already know how to use these word-processing tools, allowing the residents to focus on what to write. Think of them as training wheels until you learn HTML!
I also started out using [WYSIWYG editors], but have since switched over to writing direclty in native HTML using [Gedit] text editor software, which is available on Linux, Windows and Mac OS.
For half the residents, English is not their native language. When a blog post is submitted, Caroline will then edit for spelling, grammar and style. IBM's style is similar to the [Associated Press (AP) Style] used by many newspaper journalists. The revised posts are then returned to the author for approval or discussion.
While English is not my native language either, I generally act as my own editor. Occasionally, I do enlist the services of Jeff Antley from developerWorks to help with HTML formatting issues.
Kevin Allen, IBM Social Business Manager
Kevin takes the edited blog posts from Caroline, converts them to HTML, and posts them to the group blog [ThoughtsOnCloud.com].
(For those who want to learn HTML, I like Kevin Werbach's [Bare Bones Guide to HTML] for explaining the structure of ordered lists, unordered lists, definition lists, tables and embedded graphics or other rich-media objects. I also use VisiBone's [HTML Color Codes] reference charts when I need to change font or background colors.)
Blog posts need attract attention. Kevin explained how to draw traffic to your blog post by cross-posting links other social media sites like [Facebook], [Google+] and [Twitter]. I comb through the [Snowclones Database] for ideas to write a catchy title and opening paragraph.
Kevin also suggests using appropriate keywords that will enable Search Engine Optimization (SEO). For my SEO, I finalized each blog post with plenty of relevant [Technorati] tags.
There is more than one way to write a blog post! In either case, the end result is educational, entertaining and engaging content that people want to read.
Which "corporate blogs" do you follow regularly? Enter your comments below!
While the rest of Americans were glued to their televisions watching President Obama explain his plan for recovery, my colleagues and Ihad dinner with clients from Canada.
One in particular claimed her father was known as the kingpin of[Flin Flon]. She lives in Ontario now, but she grew up in this smallmining town in Manitoba made famous for winning a government contractto grow crops for medicinal purposes.
Shown at left is the town's mascott, Flinty. Yes, apparently thetown was named after a fictional character of a paperback novel.
Of course, in conversations with clients, it is best to avoid topics like politics or drugs,but the intersection of government health care and implications on IT can't be disregarded.Since Canada has a more efficient healthcare process, the government enjoys a lower costper citizen. President Obama has suggested that the United States should adopt reforms to make the American system more efficient, including electronic medical records.
Not surprisingly, [smarter healthcare] is part of IBM's latest set of strategic initiatives.Digitizing medical information has a variety of benefits:
Information isn't stranded on islands
If there is any situation that needs to deliver the right information, to the right people,at the right time, healthcare is certainly one of them. Having the right information canhelp reduce medical mistakes.
Physicians spend time with their patients, not paperwork
I personally know some doctors here in Tucson, and they are the first to admit that theywould prefer to focus on their core strengths, which they spent many years in medical school,and leave the administrative details to someone else. Focusing on core strengths is acommon theme for successful businesses, and this is no different.
Expertise needs no passport
Medical emergencies do not always happen near the hospital or clinic that your medical records are stored at.An exciting feature of digital information is that it is easy to transport to where it isneeded, unlike paper records or X-ray film.
To learn more about IBM's strategy and vision, see IBM's[Smarter Planet] Web site.
While Bill Gates is personally benefiting from code he wrote 30 years ago, most software engineers don't getroyalties for their creative efforts. Robin Harris on StorageMojo has a great piece on [Why are the writers striking?]The writers in this case are those who write scripts for television programs. They get 4 cents for every$19.99 DVD sold today, and want this bumped up to 8 cents. More importantly, they want the same deal forcontent shown over the internet. Currently, they get nothing when content they wrote for is shown on the internet, and they would like that fixed also.
Paying royalties to creative writers encourages them to write good stuff. The best stuff will result in moreroyalties, and we want to encourage this. What about software engineers? Don't we want them to write the beststuff also? Shouldn't they get royalties too, not just a flat salary and continued employment?