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.)
This week, I will be in Auckland, New Zealand for the [IBM System x and System Storage Technical Symposium]. This is a three-day event, with 35 unique sessions and labs. The agenda is organized with a keynote session in the beginning, followed by 12 time slots over three days, each slot offering five different break-out session topics to choose from. Here is a recap of Day 1:
The keynote was led by Phil Tasker, IBM Business Unit Executive (BUE) for STG Education Programs in Growth Markets, then Matt Paterson, General Manager for Sales in New Zealand say a few words. IBM is in the Top 10 Training Hall of Fame, and conducts over 40,000 classes worldwide, resulting in over 1.3 million student days of instructions. IBM Systems Lab and Training technical hosts over three dozen conferences like this one every year. This is the first time that System x and Storage Symposium has been run in New Zealand, and based on the incredibly good turn-out, will probably be a regular event.
Matt Ziegler - HPC
Matt Ziegler, IBM Senior HPC Solutions Architect for the iDataPlex marketing team, gave an introdcution to HPC during the keynote, then provided more details in a break-out session.
In the High Performance Computing (HPC) market, IBM POWER used to be the dominant chipset, with over 200 of the top 500 supercomputers back in June 2001. Today, only about 50 use POWER. Rather, over 350 of the top 500 supercomputers use x86 instead. HPC represents a 6.3 percent growth opportunity for computer, 9.3 percent growth for storage, and 8.6 percent growth for services.
IBM's leadership in energy efficiency applies to HPC as well. In the "Green 500", a ranking based on MFLOPS/Watt, 19 of the top 25 are from IBM. IBM's iDataPlex is the most energy efficient x86 platform, at 401 MFLOPS per Watt.
Overall, x86 is growing. In 2005, x86 had 48 percent of the market, RISC/Itanium had 39 percent, and mainframe had 12 percent. In 2009, x86 grew to 56 percent, RISC/Itanium dropped to 33 percent, and mainframe to 11 percent. By 2014, Matt projects that x86 will be 63 percent, RISC/Itanium will drop to 30 percent, and mainframe to 7 percent.
The most popular form factor for x86 are blades. Growing from 8 percent in 2005, to 20 percent in 2009, and projected to be 33 percent by 2014.
IBM's Storage Strategy in the Era of Smarter Computing
I gave this presentation twice today. It has evolved quite a bit from the version I presented in Orlando last July. Attendees appreciated that my colorful analogies and stories helped them better understand the concepts of Big Data analytics, Workload-Optimized systems, and Cloud Storage offerings.
SONAS Product Review and Demo
Rich Swain presented IBM's Scale-Out Network Attached Storage (SONAS) and provided a live demo connecting to a box here in New Zealand. This is a topic I often present at the Tucson Executive Briefing Center, but it is always good to hear someone else's spin.
Phil Tasker invited everyone to the Welcome Reception after the last sessions. There was food and drink, and prizes! One person won an Xbox-360 game console, and two people won iPads.
The IBM Storwize V7000 was introduced last October, and has proven to be wildly successful. I saw two awesome reviews recently of the IBM Storwize V7000 disk system that I thought I would bring to your attention.
The first review is [IBM Storwize V7000] from Roger Howorth of ZDNet UK. Here are some quotes:
"Under the hood, the Storwize V7000 is built from technologies originally developed for IBM's enterprise-class storage systems, so the V7000 benefits from a comprehensive set of high-end features that have been scaled down for mid-range buyers."
"Initial configuration couldn't be simpler."
"We really liked the layout and functionality of the GUI."
"Storwize V7000 is virtual storage that offers efficiency and flexibility through built-in SSD optimization and "thin provisioning" technologies while enabling users to virtualize and re-use existing disk systems..."
"Storwize V7000 advanced functionality also enables non-disruptive migration of data from existing storage, simplifying implementation and minimizing disruption to users."
"The Storwize V7000 graphical user interface is a browser-based, easy to navigate intuitive GUI."
"ESG Lab found that getting started with the Storwize V7000 disk system was intuitive and straightforward."
"Easy Tier increases the efficiency and simplicity of deploying SSD drives."
Intelligent block-level disk array that virtualizes both internal and external disk storage
8 Gbps FCP and 1GbE iSCSI
IBM Storwize V7000 disk system
Real-time compression appliance for files
10GbE/1GbE CIFS and NFS
Storwize, now an IBM company
IBM Real-time Compression STN-6800 appliance
1GbE CIFS and NFS
IBM Real-time Compression STN-6500 appliance
If you think this is the first time a company like IBM has pulled shenanigans with product names like this, think again. Here are a few posts that might refresh your memory:
In my September 2006 post, [A brand by any other name...] I explain that I started blogging specifically to promote the new "IBM System Storage" product line name, part of the "IBM Systems" brand resulting from merging the "eServer" and "TotalStorage' brands.
In my January 2007 post, [When Names Change], I explain our naming convention for our disk products, including our DS family, SAN Volume Controller and N series.
In my February 2008 post, [Getting Off the Island], I cover how the x/p/i/z designations came about for our various IBM server product lines.
But what about acquisitions? When [IBM acquired Lotus Development Corporation], it kept the "Lotus" brand. New products that fit the "collaboration" function were put under the Lotus brand. I think most people can accept this approach.
But have we ever seen an existing product renamed to an acquired name?
In my post January 2009 post
[Congratulations to Ken on your QCC Milestone], I mentioned that my colleague Ken Hannigan worked on an internal project initially called "Workstation Data Save Facility" (WDSF) which was changed to "Data Facility Distributed Storage Manager" (DFDSM), then renamed to "ADSTAR Distributed Storage Manager" (ADSM), and finally renamed to the name it has today: IBM Tivoli Storage Manager (TSM).
Readers reminded me that [IBM acquired Tivoli Systems, Inc.] in 1996, so TSM could not have been an internally developed product. Ha! Wrong! Let's take a quick history lesson on how this came about:
In the late 1980s, IBM Almaden research had developed a project to backup personal computers and workstations, which they called "Workstation Data Save Facility" or WDSF.
This was turned over to our development team, which immediately discarded the code, and wrote from scratch its replacmeent, called Data Facility Distributed Storage Manager (DFDSM), named similar to the Data Facility products on the mainframe (DFP, DFHSM, DFDSS). As a member of the Data Facility family, DFDSM didn't really fit. The rest processed mainframe data sets, but DFDSM processed Windows and UNIX files. That a version of DFDSM server was available to run on the mainframe was the only connection.
Then, in the early 1990s, there were discussions of possibly splitting IBM into a bunch of smaller "Baby Blues", similar to how [AT&T was split into "Baby Bells"], and how Forbes and Goldman Sachs now want to split Microsoft into [Baby Bills]. IBM considered naming the storage spin-off as ADSTAR, which stood for "Advanced Storage and Retrieval."
Pre-emptively, IBM renamed DFDSM to "ADSTAR Distributed Storage Manager" or ADSM.
Fortunately, in 1993, IBM brought a new sheriff to town, Lou Gerstner, who quickly squashed any plans to split up IBM. He quickly realized that IBM's core strength was building integrated stacks, combining systems, software and services to solve business problems.
In 1996, IBM acquired Tivoli Systems, Inc. to expand its "Systems Management" portfolio, and renamed ADSM over to IBM Tivoli Storage Manager, since "storage management" is an essential part of "systems management". Later, IBM TotalStorage Productivity Center would be renamed to "IBM Tivoli Storage Productivity Center."
I participated in five months of painful meetings to figure out what to name our new internally-developed midrange disk system. Since it ran SAN Volume Controller software, I pushed for keeping the SVC designation somehow. We considered DS naming convention, but the new midrange product would not fit between our existing DS5000 and DS6000 numbering scheme. A marketing agency we hired came up with nonsensical names, in the spirit of product names like Celerra, Centera and CLARiiON, using name generators like [Wordoid]. Luckily, in the nick of time, IBM acquired Storwize for its compression technology, and decided that Storwize as a name was way better fit than any of the names we came up with already.
However, the new IBM Storwize V7000 midrange product had nothing in common with the appliances acquired from Storwize, the company, so to avoid confusion, the latter products were renamed to [IBM Real-time Compression]. Fellow blogger Steven Kenniston, the Storage Alchemist from Storwize fame now part of IBM from the acquisition, gives his perspective on this in his post [Storwize – What is in a Name, Really?]. While I am often critical of the names and terms IBM uses, I have to say this last set of naming decisions makes a lot of sense to me and I support it wholeheartedly.
If you store your VMware bits on external SAN or NAS-based disk storage systems, this post is for you. The subject of the post, VM Volumes, is a potential storage management game changer!
Fellow blogger Stephen Foskett mentioned VM Volumes in his [Introducing VMware vSphere Storage Features] presentation at IBM Edge 2012 conference. His session on VMware's storage features included VMware APIs for Array Integration (VAAI), VMware Array Storage Awareness (VASA), vCenter plug-ins, and a new concept he called "vVol", now more formally known as VM Volumes. This post provides a follow-up to this, describing the VM Volumes concepts, architecture, and value proposition.
"VM Volumes" is a future architecture that VMware is developing in collaboration with IBM and other major storage system vendors. So far, very little information about VM Volumes has been released. At VMworld 2012 Barcelona, VMware highlights VM Volumes for the first time and IBM demonstrates VM Volumes with the IBM XIV Storage System (more about this demo below). VM Volumes is worth your attention -- when it becomes generally available, everyone using storage arrays will have to reconsider their storage management practices in a VMware environment -- no exaggeration!
But enough drama. What is this all about?
(Note: for the sake of clarity, this post refers to block storage only. However, the VM Volumes feature applies to NAS systems as well. Special thanks to Yossi Siles and the XIV development team for their help on this post!)
The VM Volumes concept is simple: VM disks are mapped directly to special volumes on a storage array system, as opposed to storing VMDK files on a vSphere datastore.
The following images illustrate the differences between the two storage management paradigms.
You may still be asking yourself: bottom line, how will I benefit from VM Volumes?
Well, take a VM snapshot for example. With VM Volumes, vSphere can simply offload the operation by invoking a hardware snapshot of the hardware volume. This has significant implications:
VM-Granularity: Only the right VMs are copied (with datastores, backing up or cloning individual-VM portions of hardware snapshot of a datastore would require more complex configuration, tools and work)
Hardware Offload: No ESXi server resources are consumed
XIV advantage: With XIV, snapshots consume no space upfront and are completed instantly.
Here's the first takeaway: With VM Volumes, advanced storage services (which cost a lot when you buy a storage array), will become available at an individual VM level. In a cloud world, this means that applications can be provisioned easily with advanced storage services, such as snapshots and mirroring.
Now, let's take a closer look at another relevant scenario where VM Volumes will make a lot of difference - provisioning an application with special mirroring requirements:
VM Volumes case: The application is ordered via the private cloud portal. The requestor checks a box requesting an asynchronous mirror. He changes the default RPO for his needs. When the request is submitted, the process wraps up automatically: Volumes are created on one of the storage arrays, configured with a mirror and RPO exactly as specified. A few minutes later, the requestor receives an automatic mail pointing to the application virtual machine.
Datastores case #1: As may be expected, a datastore that is mirrored with the special RPO does not exist. As a result, the automated workflow sets a pending status on the request, creates an urgent ticket to a VMware administrator and aborts. When the VMware admin handles that ticket, she re-assigns the ticket to the storage administrator, asking for a new volume which is mirrored with the special RPO, and mapped to the right ESXi cluster. The next day, the volume is created; the ticket is re-assigned to the storage admin, with the new LUN being pointed to. The VMware administrator follows and creates the datastore on top of it. Since the automated workflow was aborted, the admin re-assigns the ticket to the cloud administrator, who sometime later completes the application provisioning manually.
Datastores case #2: Luckily for the requestor, a datastore that is mirrored with the special RPO does exist. However, that particular datastore is consuming space from a high performance XIV Gen3 system with SSD caching, while the application does not require that level of performance, so the workflow requires a storage administrator approval. The approval is given to save time, but the storage administrator opens a ticket for himself to create a new volume on another array, as well as a follow-up ticket for the VMware admin to create a new datastore using the new volume and migrate the application to the other datastore. In this case, provisioning was relatively rapid, but required manual follow up, involving the two administrators.
Here's the second takeaway: With VM Volumes, management is simplified, and end-to-end automation is much more applicable. The reason is that there are no datastores. Datastores physically group VMs that may otherwise be totally unrelated, and require close coordination between storage and VMware administrators.
Now, the above mainly focuses on the VMware or cloud administrator perspective. How does VM Volumes impact storage management?
VM's are the new hosts: Today, storage administrators have visibility of physical hosts in their management environment. In a non-virtualized environment, this visibility is very helpful. The storage administrator knows exactly which applications in a data center are storage-provisioned or affected by storage management operations because the applications are running on well-known hosts. However, in virtualized environments the association of an application to a physical host is temporary. To keep at least the same level of visibility as in physical environments, VMs should become part of the storage management environment, like hosts. Hosts are still interesting, for example to manage physical storage mapping, but without VM visibility, storage administrators will know less about their operation than they are used to, or need to. VM Volumes enables such visibility, because volumes are provided to individual VMs. The XIV VM Volumes demonstration at VMworld Barcelona, although experimental, shows a view of VM volumes, in XIV's management GUI.
Here's a screenshot:
That's not all!
Storage Profiles and Storage Containers: A Storage Profile is a vSphere specification of a set of storage services. A storage profile can include properties like thin or thick provisioning, mirroring definition, snapshot policy, minimum IOPS, etc.
Storage administrators define a portfolio of supported storage services, maintained as a set of storage profiles, and published (via VASA integration) to vSphere.
VMware or cloud administrators define the required storage profiles for specific applications
VMware and storage administrators need to coordinate the typical storage requirements and the automatically-available storage services. When a request to provision an application is made, the associated storage profiles are matched against the published set of available storage profiles. The matching published profiles will be used to create volumes, which will be bound to the application VMs. All that will happen automatically.
Note that when a VM is created today, a datastore must be specified. With VM Volumes, a new management entity called Storage Container (also known as Capacity Pool) replaces the use of datastore as a management object. Each Storage Container exposes a subset of the available storage profiles, as appropriate. The storage container also has a capacity quota.
Here are some more takeaways:
New way to interface vSphere and storage management: Storage administrators structure and publish storage services to vSphere via storage profiles and storage containers.
Automated provisioning, out of the box: The provisioning process automatically matches application-required storage profiles against storage profiles available from the specified storage containers. There is no need to build custom scripts and custom processes to automate storage provisioning to applications
The XIV advantage:
XIV services are very simple to define and publish. The typical number of available storage profiles would be low. It would also be easy to define application storage profiles.
XIV provides consistent high performance, up to very high capacity utilization levels, without any maintenance. As a result, automated provisioning (which inherently implies less human attention) will not create an elevated risk of reduced performance.
Note: A storage vendor VASA provider is required to support VM Volumes, storage profiles, storage containers and automated provisioning. The IBM Storage VASA provider runs as a standalone service that needs to be deployed on a server.
To summarize the VM Volumes value proposition:
Streamline cloud operation by providing storage services at VM and application level, enabling end-to-end provisioning automation, and unifying VMware and storage administration around volumes and VMs.
Increase storage array ROI, improve vSphere scalability and response time, and reduce cloud provisioning lag, by offloading VM-level provisioning, failover, backup, storage migration, storage space recycling, monitoring, and more, to the storage array, using advanced storage operations such as mirroring and snapshots.
Simplify the adoption of VM Volumes using XIV, with smaller and simpler sets of storage profiles. Apply XIV's supreme fast cloning to individual VMs, and keep automation risks at bay with XIV's consistent high performance.
Until you can get your hands on a VM Volumes-capable environment, the VMware and IBM developer groups will be collaborating and working hard to realize this game-changing feature. The above information is definitely expected to trigger your questions or comments, and our development teams are eager to learn from them and respond. Enter your comments below, and I will try to answer them, and help shape the next post on this subject. There's much more to be told.
IBM Storage Architect supporting customers in Canada and the Caribbean
Well, it's Tuesday again, and you know what that means? IBM Announcements! Lloyd and Tony are enjoying 4th of July, so its up to me now that I'm back from Canada Day!
IBM Storage Solutions for blockchain
This week IBM Storage announced an expansion of the IBM reference architecture for on-premise blockchain solutions. This announcements centers around being able to leverage cloud-based and on-premises storage solutions for off-chain data. An example of this would be IBM Cloud Object Storage (COS), which can expand your on-premises off-chain data store for your blockchain peer, regardless where your blockchain peer resides.
For all of us just starting to look at Blockchain, there's a couple things to keep in mind, the environment must provide a reliable platform-as-a-service for its users, it leverages IBM Cloud Private, and the IBM Blockchain Platform for IBM Cloud Private. If you want a good place to start looking into Blockchain there is a good place to start, with the [IBM Blockchain for Dummies] publication that gives a good overview of the general technology. Data for a blockchain solution can either be stored on-chain as part of the core ledger managed by the blockchain protocol, or off-chain, using more traditional data stores. Off-chain data is any non-transactional data that is too large to be stored in the blockchain efficiently, or, requires the ability to be changed or deleted.
What's new in this annoucement which is part of the latest version of the [IBM Storage Solutions for Blockchain Platform Version 1.2], is the ability to leverage IBM Cloud Object Storage as an on-prem storage option and the ability to use the IBM Blockchain cloud peer for test and validation. It leverages the IBM Blockchain Document Store that allows secure sharing of documents across multiple participants on a permissioned-blockchain network. It provides an abstraction for handling documents or unstructured data like text, PDF, JPG files and JSON that uses APIs. It also maintains proof of the existence of the documents by using the immutable property of the blockchain and supports verification and secure sharing of the files.
IBM Storage Solutions for blockchain incorporates elements from across the IBM Storage portfolio, including hardware and software components, ordering and installation instructions and support, and several different expansion options. Pretested blueprints tie each solution together with a set of instructions defining each component and providing configuration details. Plus, IBM subject matter experts (SMEs) are available to help clients through their journey. IBM is also deeply involved in developing and offering IT infrastructure solutions designed to enable enterprises of all types and sizes to implement individualized blockchains that leverage both existing data centers systems as well as new technologies and multicloud architectures. One example of this is leveraging the [IBM LinuxONE] for these deployments
Continuing my romp through Australia and New Zealand, this is city 6 - Wellington, which is the capital of New Zealand. This meant many of the clients in the audience work in government agencies.
Here is my view of Wellington from my hotel room at the Duxton Hotel. I have been to Wellington before, it has that "small town" feel.
The event went smoothly, just like the rest of them. Anna Wells presented IBM's storage strategy and highlighted specific IBM storage solutions.
Replacing Natalie from GPJ Australia is Megan, who coordinated our events in both Auckland and Wellington, NZ.
Next, we had Glen Mitchell again from Telecom NZ, presenting his success story going from an EMC-only environment to a dual IBM-and-EMC mixed environment managed by IBM SAN Volume Controller.
Someone mentioned that my job as public speaker in different cities was akin to "busking". I had no idea what "busking" was, until I was shown two "in the act" in front of a bank. Americans call these "street performers", which shows we appreciate this art form perhaps more than the Kiwis.
Lastly, I covered future trends in storage. This is particularly interesting to government agencies that are particularly interested in reducing costs, managing risks, and improving service delivery.
Lastly, this is Aisel Giumali, IBM storage marketing manager for Australia and New Zealand. She managed my calendar, all of my events and one-on-one client briefings. I could not have handled these past two weeks without her.
Since the first big earthquake on Saturday, there were several smaller aftershocks, including one in Wellington itself. It is a good thing I head back for Australia for the rest of the trip.
In the first two cities, Adam Beames, system administrator for Tennis Australia, presented. Tennis Australia is most known for running the [Australian Open], the first Grand Slam tennis tourney of the year, but they also run some smaller events, such as the Brisbane International, the Sydney International, the Hobart International, the Davis Cup, the Fed Cup and the Pro Tour. They have 150 full time staff, and another 180 staff contributed from their eight member associations they support.
Of these events, the Australian Open is by far the biggest, with over 9 million unique visitors to the website for the few weeks in January every year. For this, Tennis Australia leverages IBM cloud computing services. The rest of the year, they have deployed their own "private cloud" for running the other events. During the month of January, Tennis Australia grows their staff from 300 to 4500 people.
Adam had been there since 2005, and told how back then they were using beige-colored IBM PC 330 tower servers, on a plastic shelf that was sagging from the weight. This server had six hot-swappable drives, 4.5GB each. There was also a mysterious "blue box" that served as their serial distribution panel, operated by a laptop running Windows 95, with a spare laptop just in case for high-availability.
The situation started to improve in 2008, Tennis Australia brought in BladeCenter H with HS20, HS21 and HS22 blade servers, and x3850 M2 machines for VMware virtual machines, and boot over SAN to an IBM XIV disk system. This allows them to run all of the other tennis events throughout the year. It provided N+1 redundancy, and made the process of provisioning servers and storage simple and efficient.
This is the view of Melbourne from the IBM office. The tall 975 foot building on the left with the golden bumblebees at the base is the famous [Eureka Tower], Melbourne's tallest residential building.
As Paul Harvey would say, at Melbourne we got to hear [the rest of the story] from Chris Yates, the CIO of Tennis Australia. He came on board in November 2007, just six weeks prior to the big Australian Open of January 2008. Witnessing how bad the IT was for the infrastructure, he partnered with IBM to deploy all the solutions that Adam mentioned in the first two cities. The transformation over the past two years has been a phenomenal success, with some of the best recognized international tennis organizations crediting Tennis Australia for some of the best run events.
IBM is also using its [cloud computing services to help the US Open] as well. In both the Australian Open and the US Open, IBM provides a cloud computing capability that allows the operation to scale up dramatically for the tournament. IBM rapidly creates and provisions services on a common infrastructure -- services that are mission-critical to the tennis tournament.
Continuing my romp through Australia and New Zealand, today I presented in Hobart, the second city on my seven-city tour. Hobart is on a separate island called Tasmania, just south of the main Australian continent. The island is heart-shaped, and Hobart is in the lower right ventricle.
Hobart boasts the second deepest harbour in the Southern Hemisphere (yesterday's Sydney Harbour being the first). It is quite cold here, but at least the skies are clear.
I stayed in the [Henry Jones Art Hotel], named after the famous owner of the IXL Jam Company. When I arrived, they presented me with a list of 18 known convicts that shared my last name: PEARSON. I checked and made sure I was not on the list. Then it was explained to me that here in Australia, everyone values their criminal ancestors, as this is how the country was formed. The names were from registry archives from the 19th century.
In keeping with the concept of an art hotel, each of the rooms were unique, which is a nice way of saying that they fit whatever they could into the spaces available. It's been a while since I stayed at a hotel with the phone at one end of the room, but the electrical outlet at the other. The thermostat was hidden in the bathroom, and I had to master some 16 different ropes to put down the shades, as the bright light from the [Cenotaph] was keeping me awake. I was able to take pictures of some of the art sculptures from the balcony.
This was a smaller event than Sydney, with only about two dozen attendees. This makes sense, as Hobart population is only about 250,000 people. Tasmania island hold about 1 million people overall, concentrated mostly along the center line of the island.
As we had done in Sydney, Anna Wells presented IBM strategy and products, Adam Beames, system administrator for Tennis Australia (shown here in the picture at left) presented his experiences transforming their datacenter, and I presented the future trends in storage.
In appreciation for Adam's presentations in Sydney and Hobart, I presented him with a copy of my book, [Inside System Storage: Volume I], available from my publisher, Lulu.com, in paperback, hard cover, and now also in eBook format for those with Kindle, Nook or other digital book readers. See panel at right on this blog for ordering information.
Wrapping up my seven-city romp through Australia and New Zealand, the final city was Canberra, which is the capital of Australia. As with Wellington, this meant many of the clients in the audience work in government agencies.
I had not taken any photos of Anna Wells, IBM Storage Sales Leader for ANZ, but I was able to find this caricature of her on a poster from an award she won within IBM.
I also did not have a picture of Robert, my videographer for this trip, who was always behind the camera himself.
The event went smoothly, just like the rest of them. Anna presented IBM's storage strategy and highlighted specific IBM storage solutions.
I had several emails asking if this event was called "Storage Optimisation Breakfast" because it was held in the mornings, or did we actually serve food at these events. The answer is we actually served food, a variation of the [Full English Breakfast], and most of the attendees gobbled it down while Anna spoke.
The fare was quite similar across all seven locations: scrambled or poached eggs, on toast or english muffin, ham/bacon/sausages, potatoes or mushrooms, and half of a baked tomato with bits of something toasted on top.
One morning, for a change, I decided instead to have a bowl of Weet-Bix cereal. Tasted like cardboard. I learned my lesson.
Next, we had Will Quodling, Manager of Infrastructure Operations, at Australia's Department of Innovation, Industry, Science and Research. The Department of Innovation, Industry, Science and Research consists of 3200 staff that strive to encourage the sustainable growth of Australian industries. The Department is committed to developing policies and delivering programs to provide lasting economic benefits ensuring Australia's competitive future, undertakes analysis, and provides services and advice to the business, science and research community. American President, Barack Obama, visited Australia and was interested in adopting a similar concept for the United States.
The department was looking to replace their existing IBM System Storage DS4800 disk systems with something more energy efficient. They selected IBM XIV storage system, with an expected savings of 10kW per year. They are able to run 800 VMware images and 150 VDI workstations using storage on one XIV, replicate the data to a second XIV at a remote location, and have a third XIV for their Web serving environment. They tested out both single drive and full module failures, and experienced better-than-expected rebuild times, with no impact to users, and no impact to performance.
After 17 days without a functioning government, Australia finally selected a prime minister. Her name is Julia Gillard, shown here. She won in part by promising to build a National Broadband Network (NBN) for the entire country, including the rural areas.
[Canberra] is an interesting town, a fully planned community designed in 1913 by Chicago's husband-and-wife architect team of Walter Burley Griffin and Marion Mahony Griffin. The location was selected as being half-way compromise between Australia's two largest cities, Sydney and Melbourne.
I would like to thank all the wonderful people in both Australia and New Zealand for making this a successful trip!
Continuing my romp through Australia and New Zealand, the last Storage Optimisation Breakfast of the week was Brisbane, which the locals here refer to as [Brisvegas], probably for all of the nightlife and casinos here.
The IBM office building is conveniently across the street from my hotel, the [Sofitel Brisbane]. The hotel also sits above central station, which allows quick transportation to the airport.
This time, we had a tag team of two people from James Cook University (JCU) to present their success story. First up was Kent Adams, the Director or Information Technology and Resources. JCU is recognized as one of the top 5 percent of Universities worldwide, and as a result, their data storage requirements are growing at 400 percent per year! Their latest purchase put out for RFP was for at least 40TB that could handle at least 20,000 IOPS. The winning solutions was an IBM XIV disk system.
Behind the scenes at all the events this week here in Australia were, from left to right, Natalie from GPJ Australia, the local subsidiary of the George P. Johnson events management we use in the states; Sonia Phillips, IBM Advisory Marketing Lead for Dynamic Infrastructure Optimisation and Cloud Computing, Demand Programs, for Australia and New Zealand; and Monika Lovgren, IBM Marketing and Execution Lead for Workload Optimised Systems for Australia.
The second speaker was Lee Askew, one of the Storage Administrators. Overall, the JCU team have been amazed at how well this box works. When they started it up, they expected to spend the next 24-36 hours formatting RAID ranks, but not with the XIV. It was ready in 2 minutes and they started provisioning storage right away. Their own tests to fail a drive found they can do a full rebuild to redundancy in 9 minutes. It took 8-36 hours on their previous disk array. Failing a full data module took only 75 minutes to bring back to redundancy.
After a long and tiring week, I was able to relax by walking through this beautiful King Edward park near the IBM building. This had a nice variety of plants and flowers, and with the surprise visit of a lizard about the length of my arm that crossed my path.
JCU also uses Asynchronous Mirror to replicate data to another XIV at distance. Again, as with all aspects of IBM XIV, the solution works as advertised. They are well positioned to grow from the 18,000 students they have today, to their target goal of 25,000 students they want to have by 2015.
Worldwide, IBM has done well with colleges and universities, and this was a great example of how partnering with IBM for your IT infrastructure can make a huge difference!