Mark your calendars! IBM plans to have back-to-back Technical University events in Hollywood, Florida:
When I first learned of this, I was not aware there was a city called Hollywood in Florida. The Hollywood in Florida is situated between Fort Lauderdale and Miami, so you can fly into either of those two airports to get to the conference.
(Did you know? The Hollywood most people know in California is no longer its own city, but rather incorporated as a neighborhood district into Los Angeles back in 1910. There are actually thirty different places called "Hollywood" around the world, two dozen in the United States, with the rest scattered in Ireland, Turkey, Russia, Singapore and the Philippines. Not all of these are formally "cities", but in some cases neighborhoods, districts, unincorporated areas, or other populated places. The Hollywood in Maryland claims to be the first, established in 1867!)
I only plan to attend the second week only, October 15-19. Here are some highlights:
I also plan to be at the IBM Technical University events in Johannesburg, South Africa (September 11-13), and Rome, Italy (October 22-26). If you plan to be at any of these events, let me know! If not, you can follow along with Twitter hashtag: #IBMtechU
Last week, in my blog post [IBM announces the new FlashSystem 9100], I mentioned that IBM offered various "Multi-Cloud" solutions to complement the FlashSystem storage system.
Several readers have asked me what is the difference between Hybrid Cloud and Multi-Cloud. The two phrases are used in various contexts, not just by IBM, but also by our competitors, as well as the press and industry analysts.
A hybrid cloud attempts to develop a single platform to run a specific Cloud workload. This single platform combines two or more of the following resources:
A Hybrid Cloud is like the United Nations peacekeeping force. A single force, with a single mission, representing the combined resources of many countries.
A Hybrid Cloud is a deployment model that might offer advantages over just using a Private Cloud, or just using a Public Cloud.
A practical example is Tennis Australia. For three weeks every January, they run the Australian Open, a tennis tournament, with over 4,000 employees, and millions of views to their website each day. For the rest of the year, they have only about 300 employees, and manage quite well to run smaller tournaments for high-school and college students, as well as plan for next year's event.
In this case, a Hybrid Cloud that combines perhaps two racks of an on-premise private Cloud, combined with the incredible power of IBM Cloud, gives them the variability and agility needed to run smoothly without wasting CAPEX on equipment they don't need.
Many "Hybrid Cloud" products focus on being the "glue" that combines two different resources together. This can be at the management layer, the data layer, the application layer, or the infrastructure layer.
In contrast, a Multi-Cloud represents a deployment strategy for different Cloud workloads. One workload might be better served on a Private Cloud, another workload might be better served on a Public Cloud, and a third workload, as we saw above, might benefit from the combined resources of a Hybrid Cloud.
In the past, people felt that all Cloud Service Providers were the same. Just as people buy gasoline from which ever gas station offers the lowest prices, many just chose their Cloud Service Provider based entirely on the costs involved. Loyalty can change the minute new price tables are published.
But today, Cloud Service Providers have made an effort to provide differentiation. For example, your Multi-Cloud might have three Hybrid Clouds. One cloud platform combines your on-premise Private Cloud with IBM Cloud, another combines your on-premise Private Cloud with Amazon Web Services, and a third combines your on-premise Cloud with Microsoft Azure.
In this case, a Multi-Cloud is like the various armed forces. You might deploy the Army for one mission, the Navy for another, and the Air Force or Marines for a third.
Many "Multi-Cloud" products focus on being versatile and multi-purpose. For example, the same FlashSystem 9100 that you deploy in your "Analytics Cloud" platform could also be useful for your "Docker Container Cloud" platform, or your "DevOPS Cloud" platform. IBM's various Multi-Cloud Solutions provide the additional software and services needed to complement the FlashSystem 9100 to pull this off.
Deciding to use a Multi-Cloud strategy is mostly a business decision. Deploying a Hybrid Cloud as one of your Multi-Cloud platforms could be a combination of business and technical decision.
Comments (6) Visits (14114)
Well, it's Tuesday again, and you know what that means? IBM Announcements! After much needed vacation in Cancun Mexico, Lake Havasu and Sedona, Arizona, I am glad to be back at work! This week, I was visiting clients in the Los Angeles area.
IBM is pleased to be on the leading edge of NVMe technology!
At the Viva Technology Conference in Paris, IBM Chairman, President and CEO Ginni Rometty [called on the technology industry to help build a better future], committing IBM technology and $30 million USD over five years in the annual [Call for Code] Global Initiative.
IBM is partnering with [David Clark Cause], the [United Nations Human Rights Office], the [American Red Cross], and the [Linux Foundation]. Celebrities like Andra Day, the GRAMMY-nominated singer and human rights advocate known for her hit song "Rise Up", are also involved.
The Call for Cloud has three objectives:
Each year will have a different focus. This year, the focus is in preventing, responding to and recovering from natural disasters, especially important with 2017 ranked as one of the worst years on record for catastrophic events, including fires, floods, earthquakes and storms.
(Worldwide, [over a million people have died from natural disasters since the year 2000]. Natural disasters are not a new phenomenon, but they have [long-term negative consequences], and are worsened by global climate change and the inept and corrupt governments and charities involved. The crises in [Syria] and [Puerto Rico] are two recent examples of how a natural disaster can become a lot worse.)
Call for Code invites developers to create new applications to help communities and people better prepare for natural disasters. For example, developers may create an app that uses weather data and supply chain information to alert pharmacies to increase supplies of medicine, bottled water and other items based on predicted weather-related disruption. Or it could be an app that predicts when and where the disaster will be most severe, so emergency crews can be dispatched ahead of time in proper numbers to treat those in need.
Can't think of any ideas for an app? Here are some TED videos that might inspire you:
IBM's $30 million USD investment over five years will fund access to developer tools, technologies, free code and training with experts. To raise awareness and interest in Call for Code, IBM is coordinating interactive educational events, hackathons and community support for developers around the world in more than 50 cities, including Amsterdam, Bengaluru, Berlin, Delhi, Dubai, London, New York, San Francisco, Sao Paulo and Tel Aviv.
Call for Cloud is organized as a competition, similar to the crowdsourcing community TopCoder that I mentioned in my now infamous 2012 post [Viggle, Mechanical Turk and the Talent Cloud].
(My earliest memory of using a contest for fresh ideas was back in 1975, after the city of Tucson purchased the Tucson Rapid Transit Company. Rather than hiring an expensive marketing agency to run focus groups or surveys, the City of Tucson published in the local newspaper a "Name that Bus" contest. The winning entry was [Sun Tran], submitted by 25-year-old college student [Benjamin Rios]. He won the grand prize: $150 portable television!)
The winning Call for Cloud team will receive a financial prize and access to long-term support to help move their idea from prototype to real-world application.
Developers can register today at the [Callforcode.org] website. Projects can be submitted by individuals – or teams of up to five people – between June 18, 2018 and August 31, 2018. If you would like me on your team, as an honorary member, technical adviser or mentor, please let me know!
Thirty semi-finalists will be selected in September. A prominent jury, including some of the most iconic technologists in the world, will choose the winning solution from three finalists. The winner will be announced in October 2018 during a live-streamed concert and award event coordinated by David Clark Cause.
Additional details, a full schedule of in-person and virtual events, and training and enablement for Call for Code are available at [www
This month, IBM Tucson Development Lab is celebrating 40 year anniversary! IBM has been operating in Arizona for the past 70 years, and of course IBM has been in the storage business for the past 90 years if you consider "punched cards" as storage on paper.
This year also marks the 40 year anniversary of DFHSM, the first product I worked on when I started here back in 1986. DFHSM stands for the Data Facility Hierarchical Storage Manager, which effectively moves data between disk and tape storage.
IBM put up two banners to celebrate! The first was for IBM Enterprise Tape storage. My first question was "What are punched cards doing on a banner for magnetic tape?"
A bit of history will explain that the first tape storage was non-magnetic. Back in 1725, Basile Bouchon developed the control of a loom by punched holes in paper tape. These were used to create intricate patterns in woven cloth.
In the late 1880s, Herman Hollerith, a young technical whiz at the US Census Bureau, had an idea for a machine that could count and sort census results far faster than human clerks. The bureau funded Hollerith’s work, and the [first tabulating machines] helped count the 1890 census, saving the bureau several years’ work and more than US$5 million.
Hollerith left the bureau to form the Tabulating Machine Company, selling his system to other countries’ census offices and then to businesses such as railroads and retailers. Hollerith had little competition, and his machines and punched cards became the standard for the industry.
In 1911, financier Charles Flint bought the Tabulating Machine Company and merged it with the International Time Recording Company and the Computing Scale Company of America to form the Comp
In 1928, IBM introduced a new version of the punched card with rectangular holes and 80 columns. The 80-character standard was used from everything from the first computer screens, to the first file layouts
It wasn't until 1952 that the first magnetic tape system hit the scene: the IBM model 726. Tape reels were the size of pizzas, and were prominently shown spinning around in various Hollywood movies to represent computers "working" on a problem.
In my now infamous 2007 post [Hu Yoshida should know better], I explain the 3850 Mass Storage System (MSS). In 1974, The IBM 3850 MSS was one of the first hybrid disk-and-tape storage systems. It was an automated tape library pretending to be disk, with tape cartridges stored in hexagonal honeycomb shelves. The tape cartridges were cylindrical, about the size of a can of soda. The spool of 770 feet of tape media held just 5MB of data.
A full IBM 3850 MSS configuration with thousands of tape cartridges was used for the 1980 US Census, holding 102 GB database, representing the data collected about 226.5 million U.S. residents. That's about 450 bytes per resident, enough to fill six punched cards.
In 1984, [IBM re-imagined tape media] again, to square cartridges: the IBM 3480.
Two years later, I joined IBM in 1986, the year IBM introduced "improved data recording capability" capability for the IBM 3480, the first industry use of compression for tape magnetic media.
In 2012, IBM celebrated the [60 year anniversary of Tape Systems].
The second banner was for IBM Enterprise Disk storage.
IBM introduced the IT industry's first commercial disk system in 1956. While the banner says "RAMAC 305", that is the name of the server. The storage system was called the [350 Disk Storage Unit]. It was the size of two refrigerators and held 5 MB of data.
In the early 1990s, I visited a client in Germany that had a 3990 controller with two 3390 disk systems attached, holding 90 GB of data in the size of three refrigerators. They had five storage administrators to manage this configuration.
A few years later at another client, they had roughly 7000 GB (7 TB) of data on their mainframe, and an equal amount across all of their Windows and UNIX servers. I met with their storage administrators, there were two for the mainframe, and about three dozen for the distributed servers.
I had two questions for them. First, why were there two storage admins for the mainframe? The mature policy-based automation on the platform would mean only one person required. Their response: when one of us is on a two-week vacation, the other can handle the workload.
My second question was for the remaining storage admins: When was the last time any of you took a two-week vacation? None had, of course, since the storage administration tools back then meant they were all working overtime on various tedious and manual tasks!
In February 2006, the folks in IBM Germany asked the IBM Storage Marketing team what events or celebration were planned for September 13, 2016, the 50 year anniversary of disk. My marketing colleagues responded, "that is only seven months away, you didn't give us enough lead time notice to plan!"
To help with celebration, I launched this blog in September 2006, and mentioned the [50 year anniversary of Disk Systems] in one of my first posts.
Next month, June 16, to be precise, marks my own 32 year anniversary working on IBM Storage. It is fun to look back at all we have accomplished!