This week, I was in beautiful Melbourne, Australia for IBM Systems Technical University. On Wednesday evening, we had a poster session.
(I have so many photos that I will split this post up into topics. This post will focus on posters related to IBM Power systems. See my other posts for storage and IBM Z.)
Ding! IBM i Systems Management redefined with SQL
A poster presentation should trigger question-and-answer sessions, and the exchange of ideas and information regarding your topic.
Scott Forstie, IBM Db2 for i Business Architect, coined the phrase "Scott's Query Language", focused on Data Services for Db2 database on IBM i operating system. His design took several charts, printed in landscape mode, and organized in 3 columns of four charts each. His "title" page was printed twice, and placed on the left and right sides.
Scott explained GROUP_PTF_CURRENCY, LICE
IBM Spectrum Scale with Hortonworks Data Platform
Chris Maestas, IBM Global Senior Solutions Architect, IBM and Par Hettinga, IBM Global SDI Enablement Leader, created this poster.
Hortonworks is a leading innovator in the industry, creating, distributing and supporting enterprise-ready open data platforms and modern data applications. They focus on driving innovation in open source communities such as Apache Hadoop, NiFi, and Spark. Their product, Hortonworks Data Platform (HDP), runs on both x86 and Power systems.
The poster design was clean, with basically three enlarged presentation slides. On the top, it explains that Hortonworks now supports IBM Spectrum Scale for storage of files and objects to be analyzed by Hadoop. On the bottom left, it shows how Spectrum Scale eliminates the ingest-and-discard approach used by other HDFS-based systems. On the bottom right, an architecture diagram to build your own "data lake".
Optimizing Power Performance with Affinity Groups – Real World 40Gbit LPM Results / Lessons Learnt
This poster employed a unique 1-6-6 design. Top slide was for title and author: Stephen Diwell, Senior Power Systems Engineer, DXC Technologies
In the middle, the poster had six traditional text-only presentation slides, arranged in two rows of three. LPAR Affinity Groups provides you the ability to give the Hypervisor a hint that you would like this group of LPARs to be located on processor Chips that are closer to each other. Use Affinity Groups to help the Hypervisor place LPARs nearer to the VIO Servers. LPARs that share common resources, like the Fibre Channel and Ethernet adapters within a VIO servers will obtain better performance and adapter throughput the closer they are. The lighting on some of these posters was really poor, and perhaps too dark to read small fonts like this.
At the bottom were performance bar chart results, in three rows of two. I like the use of color for the graphs. For a network job with 8 threads, Stephen achieved a 54% increase in network bandwidth for LPARs communicating on the same Chip to those communicating between Nodes in the E800 frame.
Sundata Power Server Cloud offering
Leave it to the marketing department of a local cloud service provider to turn their poster into an advertising billboard! This one was presented by Kon Kakanis, Managing Director, Sundata Pty Ltd
The Sundata poster encouraged people to move their AIX, IBM i and Linux on POWER workloads to their "PowerCloud" platform. They summarized their advantages into four bullet points:
Founded in 1986, Sundata is an Australia-based organization to help their clients transform into the Cloud, select and deploy IT hardware and keep the lights on with ongoing support and managed services. They have over 100 corporations, government departments and schools enjoying a close and ongoing relationship.
The large fonts, simple design, and the cute cat-in-a-cape logo in the lower right corner captured peoples attention!
In between reading posters and talking to everyone, it was good to take a quick look out the floor-to-ceiling windows. At 297 meters, Eureka Tower has some amazing views. Here is one of the Yarra river and Central Business District.
technorati tags: IBM, #IBMtechU, #IBMstu2017, Scott Forstie, Chris Maestas, Par Hettinga, Kon Kakanis, IBM Db2, IBM i, Hortonworks, Hortonworks Data Platform, HDP, Spectrum Scale, Poster Session, IBM Power, Affinity Groups, Sundata, PowerCloud, AIX, Linux on Power, Brisbane, Sydney, Eureka Tower, Yarra River
I am back from China, and now glad to be back in the old USA. Last week, someone asked me what would it take to add a specific feature to the IBM System Storage DS8300. The what-would-it-take question is well-known among development circles informally as a "sizing" effort, or more formally as "Development Expense" estimate.
For software engineering projects, the process was simply that an architect would estimate the number of "Lines of Code" (LOC) typically represented in thousands of lines of code (KLOC). This single number would convert to another single number, "person-months", which would then translate to another single number "dollars". Once you had KLOC, the rest followed directly from a formula, average or rule-of-thumb.
More amazing is that this single number could then determine a variety of other numbers, the number of total months for the schedule, the number of developers, testers, publication writers and quality assurance team members needed, and so on. Again, these were developed using a formula, developed and based on past experience of similar projects.
Earlier in my career, I was the lead architect for DFSMS for the z/OS operating system, and later for IBM TotalStorage Productivity Center, performing these sizing efforts. A famous IBM architect, Frederick P. Brooks, wrote a now-classic book that was requiredreading when I started at IBM, which just was re-released as Mythical Man-Month: Essays in Software Engineering, 20th Anniversary Edition. In addition to sound advice, he alsooffered a formula or two that helps with these estimating tasks.
Hardware design introduces a different set of challenges. When I was getting my Masters Degree in Electrical Engineering, it took myself and four other grad students a full semester just to design a six-layer, 900 transistor silicon chip, which could only perform a single function, multiply two numbers together.At IBM, another book that I was given to read was Soul of a New Machine, documenting six hardware engineers, and six software engineers, working long hours on a tight schedule to produce a new computer for Data General.
So why do I bring this up now? IBM architects William Goddard and John Lynott are being inducted posthumously this year into the prestigious National Inventors Hall of Fame for their disk system innovation.
Under the leadership of Reynold Johnson, the team developed an air-bearing head to “float” above the disk without crashing into the disk. Imagine a fighter airplane flying full speed across the country-side at 50 feet off the ground. If you every heard the term "my disk crashed", it was originally referring to the read/write head touching the disk surface, causing terrible damage.
A uniformly flat disk surface was created by spinning the coating onto the rapidly rotating disk, leaving many wearing lab coats covered with disk liquid at waist level. Developing disk-to-disk and track-to-track access mechanisms proved more challenging, and nearly halted the project. The team, however, was adamant that this problem could be solved, and customers were increasingly asking for random access technology. The result was the "350 Disk Storage Unit" designed for the "305 RAMAC computer", which I have talked about a lot last year as part of our "50 years of disk systems innovation" celebration.
Neither Goddard nor Lynott had computing experience prior to joining IBM. Goddard was a former science teacher who briefly worked in aerospace. Lynott had been a mechanic in the Navy and later a mechanical engineer. They didn't have a nice formula based on past experience, they didn't have the benefit of Fred Brooks' advice, or the rules-of-thumb or averages now used to estimate the size of projects. They had to break new ground.
Now that's innovation!
technorati tags: IBM, DS8300, disk, KLOC, sizing, estimate, DFSMS, z/OS, TotalStorage Productivity Center, Frederick Brooks, William Goddard, John Lynott, Mythical Man-Month, Reynold Johnson, RAMAC, 305, 350,[Read More]
Last week, fellow IBM blogger Barry Whyte Barry pointed out that my recent post on [Cognitive University for Watson Systems SmartSeller] was my 1,000th blog post. After 10 years of blogging, I have reached the 1,000 mark!
(As IBM is focused on its transformation from a "Systems, Software and Services" company to a "Cognitive Solutions and Cloud Platform" company, it seems appropriate to highlight my 1,000 blog post on the concept of cognitive solutions.)
A lot of people ask me to explain what exactly does IBM mean by "cognitive", which is a fair question. Let's start with the [Dictionary definition]:
What exactly does IBM mean by Cognitive? IBM has taken this definition, and focused on four key strategic areas:
IBM is exploring the use of Cognitive Solutions in a variety of different industries, from Healthcare to Retail, Financial Services to Manufacturing, and more.
Last week, I opined that Monday's IDC announcement "IBM #1 in combined disk and tape storage hardwaresales for 2006" was in part because of a resurgence of interest in tape, with four specific examples. There was a lot of reaction and reflection fromboth sides.
technorati tags: IBM, IDC, combined, disk, tape, storage, announcement, EMC, dead, LiveVault, video, John Cleese, JWT, DrunkenData, Sun, StorageTek, STK, Randy Chalfant, TotalStorage, Productivity Center, Fathers Day, Big, Green, initiative[Read More]
Comment (1) Visits (6777)
Well, it's Tuesday again, and you know what that means? IBM Announcements!
(OK, yes, today is Friday, but I was busy getting married on Tuesday, so IBM pushed the announcements out one day to Wednesday, and technically I am writing this blog post during my honeymoon vacation, so the IBM marketing team and my new wife both cut me some slack. Work/Life balance is all about compromises, right?)
By now, there are multitude news articles on these announcements, so I recommend you go look for them.
technorati tags: IBM, DS8880, DS8884, DS8886, High Performance Flash Enclosure, HPFE, DSCLI, FICON, Spectrum Virtualize, Data-at-Rest Encryption, Spectrum Copy Data Management, Transparent Cloud Tiering, SAS, NL-SAS, LFF, SFF, FDWP, FlashSystem V9000, DeepFlash 150, DeepFlash ESS, Elastic Storage Server, Erasure Coding, Widows, Linux, AIX, BSSD
It's official! IBM System Storage TS1120 tape drive takes home the gold award, the product of the year, announced by Storage magazine.
I spent 18 hours traveling from Australia to China yesterday, and we were partially delayed due to weather, but felt that it was necessary to discuss the innovative use of encryption on this drive.
While most consider the TS1120 an "Enterprise-class" tape technology for the mainframe, it is also attachable to the smallest distributed systems running Windows, Linux, or various flavors of UNIX. Rather than limit users with an Encryption Key Manager that only ran on z/OS, IBM instead chose to implement it in Java, that can be run on anything from z/OS to Linux, Unix and Windows platforms, giving clients choice and flexibility in their deployment.
The design is quite clever and elegant. In the encryption world, there are two ways to encrypt.
So, let's say that Green, Inc. wants to send a tape to Blue, Co. Blue has already provided its public "encryption" key to Green, so Green does the following:
If the super-secret private key is ever compromised, all you have to do is mount the tape, unlock the red key with the old private key, and re-lock the red key with a new public key. Since the red key doesn't change, the rest of the data can be left in tact. The whole process takes less than 5 minutes, compared to Sun Microsystems method, which could take 1-2 hours per cartridge, having to decrypt and re-encrypt the entire data stream.Read More]
I will wrap up this week's theme on travel, conferences and Japan discussingGroundhog day, celebratedtoday (Feb. 2) in the US.
I thought of this because there was a 2003 movie called"Lost in Translation", the title of yesterday's post. This movie is about an American actor, played by Bill Murray, coming to Tokyoto film a whisky commercial. I first saw it with my sister and father, and we musthave been the only three who have actually been to Japan, as we were laughing hysterically,while the rest of the audience was utterly confused. If you have never been to Japan, see the movie before you go, then see it again after you get back home.
Ten years earlier, Bill Murray also played the lead role in another movie called"Groundhog day".In the movie, Bill Murray's character is TV newsman "Phil Connors" who travels to a small townwhere they bring out a small groundhog. If the groundhog can see his shadow, it predictsat least six more weeks of winter. If it does not, winter will end sooner. The nextday, Phil wakes up to realize that he is re-living the same day, over and over, like a modern-day Sisyphus or Promethius. Howhe handles himself in this situation, is what makes the movie so memorable.
When I explain what I do for IBM, to people I meet at home and abroad, I get asked the same set of questions.
The amount of information stored and available today is astounding. Consider the following:
...a weekday edition of The New York Times contains more information than the average person was likely to come across in a lifetime in seventeenth-century England.
Shawn Callahan mentions this in his great presentation on how work really gets done.
Mark Nelson covers this in more detail inWe Have the Information You Want, But Getting It Will Cost You: Being Held Hostage by Information Overload.
To help address this challenge of organizing finding the right information at the right time, Web 2.0 technologies have emerged. You can read the 16-page paper What Is Web 2.0? -- Design Patterns and Business Models for the Next Generation by O'Reilly.
Or better yet, watch the quick 4-minute video Web 2.0 ... The Machine is Us/Ing Us.Read More]
I didn't really have a theme this week, still recovering from jet-lag from my travels through Japan, Australia, China.
Gary Diskman has an amusing blog entry about a Funny disaster recovery job posting. It is not clear if he is being completely tongue-in-cheek, or a bit cynical. However, it rings true that you get what you measure, and some managers look for easy metrics, even if there are unintended consequences.
Western medicine works this way. Rather than paying your doctor to keep you healthy, you pay him per visit, to get refills on prescriptions, check-ups on medical conditions, surgeries and so on. While Eastern medicine is focused on keeping people healthy, Western medicine profits more from resolving "situations".
I have seen similar situations on the "health" of the data center. In one case, the admins were measured on how quickly they bring back up their web-servers after a crash. They had this process down to a science, because they were measured on how quickly they resolved the situation. I suggested switching from Windows to Linux, a much more reliable operating system for web-serving, and showed examples of web-servers running Linux that have been up for 1000 days or more. Management changed the metrics to "average up-time in days" and magically the re-boots all but disappeared, thanks to Linux, but also thanks in part to shifting the incentive structure. Perhaps some of those earlier situations were "artificially created"?
Back in the 1980s, I was working on a small software project that was about 5000 lines of code. In those days, testers were measured by the number of "successful" testcases that ran without incident. Testcases that uncovered an error were labeled as "failures" to be re-run after the developers fixed the code. When I declared my code ready for test, the test team ran 110 testcases, all successfully, and they were all rewarded for meeting their schedule. I, on the other hand, did not accept these results, met with them and told them I would give them $100 each if they could find a bug in my code in the next week. Nobody writes 5000 lines of code without some error along the way, not even me. (As one author put it, more people have left earth's gravity to orbit the planet than have written perfect code that did not require subsequent review or testing. It's so true. Good software is difficult to write.)
The test team accepted the challenge, and found 6 problems, more than I expected, but at least I felt more confident of the code quality after fixing these. As I suspected, the unintended consequence of counting "successful" testcases was that testers would write the most simple, basic, leas So, my advice is to determine metrics that have the intended consequences you want, while avoiding any negative unintented consequences that might undermine your eventual success. People will quickly figure out how to maximize the results, and if you can align their goals to company goals, then everybody benefits. Well, I'll be blogging from Mexico next week (yes, it is a business trip!). Enjoy the weekend.
So, my advice is to determine metrics that have the intended consequences you want, while avoiding any negative unintented consequences that might undermine your eventual success. People will quickly figure out how to maximize the results, and if you can align their goals to company goals, then everybody benefits.
Well, I'll be blogging from Mexico next week (yes, it is a business trip!). Enjoy the weekend.
Happy Holidays everyone!
Every December, the "birthday boys" -- Bill, Kris and I -- celebrate our birthdays. For me, it is the big five-0h. According to a recent Harris poll, it is [America's favorite age!] For some people, [fifty is the new thirty]!
From left to right: Melinda Jensen, Bill Terry, Lee Olguin, Kris Keller, Tony Pearson, and Kristy Knight.
The storage, cloud and analytics team celebrated with cake and party hats. None of us "birthday boys" eat chocolate, so this year we chose a new flavor: Strawberry Cream! It was delicious.
It was a good time to reflect on our success and accomplishments. In 2015, I helped close over $270 million USD in revenues for IBM, meaning that I helped close over a million [per day on the job].
The IT industry went through a lot of changes also. Hewlett-Packard [split into two smaller pieces]. Dell started [EMC's fade to non-existence]. Cisco and IBM joined forces to create VersaStack, a converged system that combines the most popular x86 servers with the industry's best storage. Analysts recognized IBM's leadershp in today's [Cognitive Era].
Looking forward to an exciting 2016!