Friday, August 22, 2014

Hot Topics Newsletter - Issue 28

The good part : there's a new Hot Topics newsletter and it's stuffed with good articles. The bad part : it's clear now that there will be only one release per year. Be tempted, good people of the newsletter, to give us a February release again as well ! You can download the new issue over here and although I see Facebook more as a medium for private matters, Hot Topics thinks otherwise and you can keep up to date with them on Facebook as well.

As I said, it's stuffed with good articles. The focus is on z/OS 2.1 and on the role of the mainframe in the world of CAMS(S) : Cloud, Analytics, Mobile, Social and Security. Let me pick out just a few, but by all means, do read the rest as well.
There's a good summary about 'System z in a mobile world' with particulary also a closer look on the role of CICS and DB2.
z/OSMF seems like it's here to stay : we learn about some APIs like e.g. the z/OSMF Jobs Interface (aka SubmitAPI) and there's a good introduction to 'z/OSMF Resource Monitoring-Reloaded'.
'Not all quiet on the consoles front' tells us about the possibility "to allow consoles to be dynamically added and deleted".
There's an intriguing (to me at least) article on z/OS Fixed Block Architecture services with z/OS Distributed Data Backup (ZDDB). Let me give you a little quote
z/OS Distributed Data Backup (zDDB) is a no-charge licensed feature. When you install zDDB on DS8000 devices, distributed host systems that are attached through Fibre Channel connection (FICON®) interfaces can access logical unit number (LUN) devices containing fixed block data. Typically, FBA LUN devices are connected to Linux®, Windows®, and UNIX® operating systems.
With zDDB, two views of the disk devices are presented, one for z/OS and one for the distributed system, as shown in Figure 2.
Here's this Figure 2

There's also a great deal of attention to the new z/OS 2.1, its migration and to recent innovations like zAWARE, zEDC, the RoCE card and so on.

So, as I always say, just check it out !

Monday, August 18, 2014

Red Alert - z/OS 2.1 DFSORT records out of sequence

I know I'm a bit late with this one but I still want to mention it, just in case you might've missed it.

Red Alert : z/OS 2.1 DFSORT records out of sequence

Abstract:

There is a potential exposure for out of sequence records with DFSORT for users on release z/OS 2.1.

Description:

At z/OS 2.1 code levels, DFSORT is intermittently returning records out of sequence. There is no data loss, but records may be returned out of sequence to the DFSORT output file. If VERIFY=YES is set at the installation level, out of sequence conditions are already being detected. This problem only occurs in z/OS 2.1. No prior releases of DFSORT are affected.

Please see APAR PI22817 for more details and latest information.

Users affected :

All z/OS 2.1 DFSORT (HSM1L00) users who SORT data with DFSORT using the performance path may be affected if there is insufficient virtual storage below the line at the time of execution. In other words the potential for error exists for all users of DFSORT SORT function on z/OS 2.1, but not all users will experience the problem.

Recommended Actions:

Enable VERIFY=YES at the installation level to detect out of sequence conditions. Affected jobs can be rerun with DEBUG $NOPFP$ to circumvent the issue.

In addition, a ++APAR is available to disable the affected performance path, as a temporary circumvention, using a new DFSORT installation option.

See APAR PI22817 for details. 


If you haven't signed up to the Red Alerts by now, you really should do it. Just go over here.

Wednesday, July 16, 2014

Get started with the IBM Mobile Workload Pricing for z/OS

A couple of months ago I wrote about the announcement of the new Mobile Workload Pricing mechnanism for z/OS. I also told you that this was going GA in July but so far I didn't see much of it on the IBM Software Pricing page I usually turn to when I'm looking for information on z/OS pricing.

So I started asking about a bit and David Chase from IBM who gave such a clarifying presentation about the topic during the System z Technical University in Budapest pointed me in the right direction. And yes, the Users Guide and the tool itself are already online. You can find the 'IBM Mobile Workload Tool' (mwrtool.exe) over here. And the 'IBM Mobile Workload Reporting Tool Users Guide' can be found over here. The Users Guide explains step by step how you have to set up the tool (on a Windows 7 64-bit), how you collect the necessary input, how you use the tool and how you submit your report to IBM.

Of course there's a bit more to this. Before you can start submitting the report be sure that you fulfill the requirements. Have a look at my previous post and the announcement to refresh your memory. And then there remains one more question : how do you separate the mobile workload from the rest. This will of course be different per customer. As a matter of fact, you are the only one who knows your shop and can determine this. And this is exactly how it will be done. You will make up a list of your mobile workload and how you can trace it. This will be the basis for an agreement you sign with IBM after a meeting with your IBM representative.

Then one more thing : what will be the benefits ? This is how I understand it for the moment. Suppose you have an LPAR running z/OS and CICS reporting 400 MSU for billing purposes. You will measure the CICS usage and let's say this is 200 MSU. The mobile part of that is e.g. 50% of that 200 MSU. You can subtract 60% from that mobile use. 60% of 100 MSU is 60 MSU so you keep 40 MSU for you mobile workload. 100 MSU plus 40 MSU means you keep 140 MSU of the original 200 MSU. But here comes the beautiful part of the system. You can subtract the 60 MSU from your billing total. So, of the originally reported 400 MSU you only keep 340 MSU for that partition. So where SCRT calculated the Rolling 4-Hour Average, MWRT will make an adjustment to that. As a matter of fact, MWRT will make this adjustment by the hour and then calculate a new Rolling 4-Hour Average. This also implies that it's not only e.g. CICS that benefits from this pricing but z/OS and other softwares as well.

So, as I said in the title of the post : Get Started !

Thursday, June 26, 2014

Exit Lifecycle Extension - Enter Extended Support

In our last newsletter I already mentioned that after z/OS 1.11 there would no longer be the possibility to get Lifecycle Extension support. And you also know that z/OS 1.12 is Out of Support by the end of September. Up to now we only saw some graphs indicating that after the End of Support, you would immediately get into 'Extended Support', as you can see below.

Click on image for larger version

Now there's an announcement making this official 'IBM Software Support Services - service extension offers defect support for IBM z/OS V1.11 and V1.12 beyond the z/OS end-of-service date (ZS14-0025)'. It's a "fee-based corrective service to users who have not completed their migration to a newer z/OS release" for a period of 3 years. z/OS 1.11 is an exception as it gets only 2 years after the Lifecycle Extension period.

As for the content : "IBM Software Support Services - service extension provides corrective service (a fix, bypass, or restriction to a problem) for your z/OS V1.11 and V1.12 operating systems". The ordering pretty much resembles that of the Lifecycle Extension : "Service extension support for both V1.11 and V1.12 requires a minimum three-month purchase and offers flexibility in support of your individual migration plans, either for single machines or for machines configured within a Parallel Sysplex".

Wednesday, June 18, 2014

BMC Intelligent Capping for zEnterprise and MLC pricing

I don't really have a habit of putting third party software in the spotlights but this one caught my attention, so I thought I might give you the heads up as well. I don't think I have to tell you a lot about the challenges companies are facing when it comes to MLC pricing - on whatever level through the organisation.

There's a nice video about the product but I don't know how to embed a FlashPlayer video, so click here to go and see it. It's actually quite nice with references to some sci-fi series I kind of like. A clue about the series ? If you implement this you'll live long and prosper. But let's get back to the product itself. I quote the description from the datasheet.
"BMC Intelligent Capping for zEnterprise dynamically automates and optimizes defined capacity settings to help lower mainframe MLC costs by 2 percent to 5 percent or more, while mitigating risk to the business. The solution analyzes, simulates, and automatically manages changes to defined capacity settings based on workload profiles, enabling IT staff to confidently lower costs. BMC Intelligent Capping for zEnterprise removes the manual effort from managing capping limits, while optimizing capacity usage across LPARs. The solution dynamically aligns workload allocations based on utilization needs, workload importance, and customer policy profiles".
Some features to make it a bit clearer ?
  • "Capacity management – Adjusts capacity across LPARs and WLM capacity groups intelligently and automatically
  • Zero balancing – Balances any increase in a capping threshold necessitated by a high-priority workload with an equivalent decrease in other LPARs or WLM groups with excess capacity
  • Minimal implementation risk – Offers gradual automation and control of capacity settings with three modes: Observe, Message, and Manage
  • Audit logs – Enable you to see exactly what changes are recommended and actions that are implemented over time"
Looks like an interesting product to me. If you want more information you can start over here or contact your local BMC representative. And before you ask, no, I have no commercial links to BMC. Just passing on information of which I think might be interesting to System z shops . . .

Monday, June 16, 2014

Tapeless initial installation of z/VSE

If I'm not blogging that much about z/VSE, then there's a good reason for that. There's some one doing such a great job in this area I barely or rather I cannot add anything useful to it. I said this before, you have the retweet function in Twitter but there should be something like a reblog function too. I'd reblog quite a few of Ingolf's z/VSE Blog. If you haven't discovered this one yet, add it to your must follow blogs now.

This is how I came across this next Live Virtual Class or Webcast on z/VSE. It's on June 24, 2014 at 9AM Brussels time.
"This LVC provides an overview on how to perform tapeless initial installation of z/VSE - a feature introduced with z/VSE 5.2. It covers how to create a z/VSE installation disk in LPAR and under z/VM and how to perform initial installation from such a installation disk in both environments".
I'm mentioning this nonetheless because you should also take a look at the future Live Virtual Classes. There's a 'Z/VSE for beginners' planned at a later date, so be sure to stay tuned.

And while I'm at it, I would also like to mention another event : the 8th European GSE/IBM Technical University for z/VSE, z/VM and Linux on System z which is taking place in Dresden, Germany from October 20 until October 22, 2014. You can find more information over here.

Wednesday, June 11, 2014

Sampling Techdocs - up to May 2014

Here I am again with an overview of interesting TechDocs documents I came across while browsing through the latest publications. If you're completely unfamiliar to Techdocs, here's an introduction to it.
  • FAQ : z/OS 2.1 Frequently Asked Question
    This FAQ is a collection of questions that were raised by customers during several presentations on z/OS 2.1 that have been answered by subject matter experts. Too many diverse topics to sum them all up, so just have a look.
  • Technical Document : IBM drives to Storage Systems cheat sheet
    I'm sure I mentioned this one before but here's an update on this one-pager showing the currently offered drive types for current IBM Storage Systems including of course DS8000 and XIV.
    • Tool : IBM Storage Tier Advisory Tool Charting Utility
      You surely know about the DS8000 Storage Tier Advisor Tool (STAT). Data from the monitoring process by Easy Tier  is included in a summary report that you can download to a Windows system. The STAT application allows you to view the data when you point your browser to that file. Now - on top of this - the Charting Utility does exactly what its name says. This Utility will format some of the data provided and create charts like
      • Skew Chart - Workload activity by percentage of capacity
      • Movement Chart - Easy Tier data movement activity
      • Workload Chart - Capacity utilization by extent pool 
    • Technical Document : IBM System Storage Easy Tier Quick Start
      Ok, ok, I'm cheating a bit here, this one is not on Techdocs but I came across it while following a link on the charting utility. "This publication introduces the IBM® System Storage Easy Tier Quick Start, which helps you get started with Easy Tier functions using the IBM System Storage DS Storage Manager". If you have to set up Easy Tier, this is a document you're surely going to like.
    Well that's it for now. And, as I always say : just check them out !

    Friday, June 6, 2014

    Upcoming GSE meetings Belgium

    You know it's difficult to report on each and every interesting meeting that passes by, so I sureley missed some in the past but here are three upcoming GSE meetings with very promising agendas :

    • Weddnesday June 11, 2014 :  z/OS Working Group Meeting at RealDolmen Huizingen
      This is an all day event with also a couple of customer testimonials and that we always like of course. Topics are OMEGAMON @ Colruyt by Geert Lips (Colruyt), Access the Mainframe: Anywhere, Anytime, Any Device by SysperTec with customer testimonial from P&V Verzekeringen, Fulfilling Retail Expectations with Mobile - a UK costomer case by Bart Gyselinck (IBM), The Evolution of Analytics and Big Data Integration on System z by Eric Michiels (IBM)
      Information and registration
    • Thursday June 12, 2014 : DB2 Working Group Meeting at IBM Forum Brussels
      This is also an all day event with a track for DB2 on z/OS and one for DB2 LUW.
      "During the DB2 for z/OS break-out sessions  we explore some of the topics that DB2 11 is bringing. Some of  the changes with the biggest impact will be thoroughly explained by DB2 expert Timm Zimmermann, and our own Bart Steegmans.
      In the DB2 for LUW break-out sessions, Dirk Coppieters and Frederik Engelen present on migrating from Orable to DB2 and using Ansible for DB2 configuration management. You also have the opportunity to get answers to all your burning questions from the DB2 for LUW Experts panel.
      Is the next stage of Information Technology one without SQL? Kris Van Thillo lets you take the first plunge into NOSQL databases during our closing session."
      Registration here or here.
    • Friday June 20, 2014 : Enterprise Systems Security z/OS meeting at KBC Brussels
      Several sessions about/by The Rocket Software Company, Improving the Integration between Distributed Security and CICS (Nigel Williams - IBM), Secrets of IMS Security and Surviving an IMS Security Audit (Maida Snapper - IBM). Scroll down to the end of the registration page to find the agenda in .pdf.
      Information and registration

    Tuesday, May 27, 2014

    IBM Benelux System z Study Tour USA 2014 Edition

    Hans Deketele from IBM Belgium is planning another IBM Benelux System z Study Tour USA. The tour usually takes you to Poughkeepsie and the agenda contains Lab visits, Reference companies, Premium speakers, Cutting edge technology, System z trends & directions ...

    Here's his invitation to the Benelux customers
    "Dear customer,

    In the year of the Mainframe 50 event the focus is heavily on the IBM System z and of course we are again planning a System z Study Tour to the US, probably in early October.
    Maybe you already joined us in one of the previous tours or maybe you always wanted to but never did: this is an early message that we have started planning for the next edition of this event.

    Please reply to this email before May 30 if you are interested to join us. Of course this is by no means a commitment that you will actually be able to join.

    We plan the tour to be all about System z and the relevant software that you need to generate success in the areas of Cloud, Analytics, Mobile, Social, Security, Linux, Storage...
    So, just send an email to Hans if you're interested or you can always contact me too of course.

    Friday, May 23, 2014

    Reminder : Hardware End of Marketing for z196 and z114

    I wrote about this in a previous post along with the announcement of the zBC12, but I think a quick reminder may be in place. Last year IBM announced the two-phase end of marketing dates for the z196 and the z114.

    A little recap
    • June 30, 2014
      Past this date any upgrades towards a z196 or a z114 will no longer be possible. Nor will you be able to do any model conversions or hardware MES features. Roughly speaking this means that any upgrade which involves hardware changes will no longer be possible. The practical consequences mainly involve connectivity cards and memory. Up to June 30, 2015 you will still be able to activate that zIIP or an IFL or do a microcode upgrade (as long as you don't need an extra book) or even a downgrade. But if that involves adding memory, FICON- or OSA-cards, which is not that imaginary, then you must add them before June 30, 2014. 
    • June 30, 2015
      "Field install features and conversions that are delivered solely through a modification to the machine's Licensed Internal Code (LIC) will continue to be available until June 30, 2015" meaning that everything which is already in the machine will be able to be activated during the next year like, as I already said, zIIPs, IFLs and Plan ahead Memory.
      Capacity on Demand and CBU offerings will be usable until their expiration date. Something to keep in mind when you're planning to use a z196 or z114 after June 2015.
    So, if you are not immediately planning an upgrade and you might have some extra workload(s) in the future, do your planning carefully in order to avoid any unpleasant surprises.

    Monday, May 19, 2014

    DS8870 announcement - Flash optimization II

    This is an announcement from last week : 'IBM DS8870 next-generation flash systems deliver high availability and better performance for critical environments (ZG14-0119)'. However last week I was at the IBM Technical University for System z in Budapest and I wanted to have a closer look at the announcement before writing about it. And, by sheer coincidence, this is the first time in my life that I actually saw the real machine before I even read the announcement as we visited the DS8000 plant while in Hungary.

    IBM fulfills an earlier statement of direction about the use of a "new high-density flash storage module for selected IBM disk systems, including the IBM System Storage DS8000". Now you might say : didn't they already announce an all flash box last year. Well, yes and no. They announced an all SSD box. Now you may argue again : isn't SSD the same as flash. Well, yes and no. It's more or less the same type of disks, or let's say, flash cards. Let's make a little detour to get a better understanding of this.
    IBM has its FlashSystem 840 for open systems which comes from a recent acquisition of Texas Memory Systems. It aims purely at performance and promises extremely high performance and extremely low latency. How does it reach that : well, by concentrating solely on getting the data as fast as possible without any software functionality or storage controller in between that does e.g. compression, deduplication . . . And that's, to me at least, the main distinction between what IBM calls Flash and SSD. As a result the announcement says "it will help to increase IOPS by up to 4 times as compared to SSDs and up to 30 times as compared to spinning drives".

    This is realized with new High Performance Flash Enclosures (HPFEs). This "high-performance flash enclosure is directly attached to the PCIe fabric, enabling increased bandwidth and transaction processing capability. The 1U enclosure contains a pair of powerful redundant RAID controllers".

    Here's a configuration with just HPFEs in the box.


    To the left side, you can see that 4 HPFEs fill the empty slot that was intentionally there from the beginning of the DS8870. ("Intentionally left blank" you might say). One enclosure contains 30 1.8'' flash drives of 400GB giving you a raw capacity of 12TB. If you only use the upper left slot for HPFEs, they can be combined with other types of disks in the regular disk slots.

    The box you see here is an "all-flash, single rack system configured with only flash and up to 96 TB of capacity (73.6 TB of usable capacity) in a 8U of space". This all flash box also "provides twice as many I/O enclosures and up to twice as many host adapters as the standard DS8870 single frame configuration" See the extra host adapters in the green square.

    Let me also give you a brief summary of the other functionalities that were announced :
    General availability : June 6, 2014. Some field availability is only in September.

    Tuesday, May 6, 2014

    IBM Mobile Workload Pricing for z/OS

    Today IBM officially announced the pricing mechanism it already revealed during the April 8 z Anniversary event : 'IBM Mobile Workload Pricing for z/OS can reduce the cost of growth for mobile transactions (ZP14-0280)'. Before giving you the details I'd like to share this video about the First National Bank of South Africa because it illustrates so clearly what mobile is all about.



    Combining mobile and mainframe is answering some real concerns or requirements of companies and people using the applications. Mobile is a rapidly growing market generating lots of transactions on lots of data. And as you could see in the video the data must always be up to date. We can no longer afford to offer copies of data, so what's better than to incorporate mobile with the company's primary data. Data that's residing on the mainframe . . . where it always has been.

    Now, this new pricing mechanism makes sure you're not penalized for following just that strategy. "This enhancement to sub-capacity reporting can mitigate the impact of mobile workloads on sub-capacity license charges, specifically in the cases where higher mobile transaction volumes may cause a spike in machine utilization. This can normalize the rate of transaction growth and reduce the reported peak capacity values used for sub-capacity charges".

    There are some prerequisites of course : it's limited to AWLC and AEWLC pricing which means to zEC12 and zBC12 or environments that have at least one zEC12 or zBC12. You also need to install a new reporting tool that will, in this case, replace SCRT : Mobile Workload Reporting Tool (MWRT). It's use, data collection and timing of reporting is very similar to SCRT. What's the difference ?
    "MWRT will calculate the 4-hour rolling average of the reported mobile transaction general purpose processor time consumed by the Mobile Workload Pricing Defining Programs and subtract 60% of those values from the traditional sub-capacity MSUs for all sub-capacity eligible programs running in the same LPAR(s) as the mobile workloads, on an hour-by-hour basis, per LPAR. The program values for the same hour are summed across all of the LPARs (and any z/OS guest systems running under z/VM®) in which the program runs to create an adjusted sub-capacity value for the program, for the given machine, for each hour. MWRT will determine the billable MSU peak for a given program on a machine using the adjusted MSU values".
    You can find all additional details in the announcement itself. And . . . you have some time to figure out how things work as MWRT becomes available on June 30, 2014 and the first report can be submitted as of July 2, 2014.

    Monday, May 5, 2014

    Openstack and System z

    Openstack and system z ? ? ?


    I wrote a piece on Openstack in our System z Newsletter a couple of weeks ago. I thought I might share it over here as well.

    People who read my blog know that I’ve mentioned Openstack already a couple of times. By the end of last year it was becoming quite clear that OpenStack is going to play an important role in the overall IBM strategy on Cloud ├ánd also in the System z world. So I started wondering : what is it ? What makes it so special ? And quite specifically : what does it mean for System z ? So I thought, let me try and understand this for myself and then make an attempt to explain this to my readers as well. And I can start by telling you that at te beginning I was quite sceptical about it. But therefore, let me take you a couple of years back.

    It started out when I saw this chart for the first time at one or other mainframe presentation talking about System z Unified Resource Manager or zManager. It must’ve been somewhere halfway 2012 around the announcement of zEC12. The zManager part was clear to me, but why dragging in the Flex Systems, System x, Power and even VMWare for heaven’s sake ? Why sure, yet another layer on top of the rest ! And why this tight interlink with the distributed environments. No, this will never happen.


    But then, as I mentioned already, in 2013 the name OpenStack popped up time and again. With the announcement of the zBC12 the graphic had undergone some changes : the OpenStack layer was added, z/VM was no longer under the umbrella of zManager but was put directly under OpenStack. And IBM told us that z/VM, as of z/VM V6.3, would be “the first System z operating environment that can be managed with these open cloud architecture-based interfaces”. Hey, where’s this going at ? Did I miss something ?


    Let me tell you what we were missing : we’re looking at it from the wrong angle. We’re taking the bottom – up look. I have my own mainframe and I’m managing it. I’m managing its storage as well. And yes, perhaps zManager was a step forward : I could now manage several aspects from one, let’s call it, dashboard. But another layer on top of that ? That’s surely overkill. But you know what, take a step back and take a look at this from a business perspective instead. That’s just the opposite : you’re now looking from the top to the bottom. And frankly, at that point, you don’t even care whether you see the bottom. It’s like swimming in the sea : you just know there’s water all the way down. You won’t fall into some or other empty space and that’s exactly what OpenStack is going to do for you. You must be thinking in terms of business, resolving problems, analyzing data, getting ahead of the competition and all of this with more or less reliability, performance or security depending on what kind of workload you want to run. And let the technical guys take care of all the rest.

    Switching roles again, as a technical guy, you can also make that step upwards. The constructors will take care of pretty much everything that’s underneath the OpenStack layer. You can move up to get close to the business people. You won’t be talking about LPARs or SSDs or Hypervisors. You’ll be talking their language about solutions and you’ll be implementing them on a totally different level. But it’ll work !

    How on earth will that be possible ? Well, I think it’s time to tell a little bit more about OpenStack and IBMs (and lots of other companies’) commitment to it.

    Openstack

    But first let me explain where OpenStack is actually playing within the entire Cloud spectrum where anything can be delivered as a Service (AAAS - Anything As A Service).

    For those who are completely unfamiliar with this we usually see these four levels presented : At the bottom we have the hardware, next up are the Infrastructure Services (IAAS – Infrastructure As A Service), then come the Platform Services (PAAS – Platform As A Service) and at the top level we have the Business Applications as Compononts (SAAS – Software As A Service).


    Below you see how these levels can be filled in :

    Click on the image in order to see a larger version
    I deliberately chose illustrations with no specific vendor products as we’re talking open source here. Each of those layers has significant open source elements driving out a coherent way of approaching cloud computing today : private, public or hybrid. The objective is to help build out this open cloud architecture from the hardware all the way up to how people access it on any device interacting with an application. This leads the way to build out an architecture in such a way that it is open, that allows for innovation but also allows us to move the workloads where appropriate and to have a choice of application infrastructure as we start to build these things out.

    Coming to OpenStack : OpenStack plays at the IAAS level. “OpenStack is a global collaboration of developers and cloud computing technologists that seek to produce a ubiquitous Infrastructure as a Service (IaaS) open source cloud computing platform for public and private clouds. The idea is to have portability of a workload, a VM image … across different types of infrastructures.

    OpenStack was founded by Rackspace Hosting and NASA jointly in July 2010. IBM joined Openstack in February 2011. By now IBM is a Platinum member meaning that it is a part of the body responsible for OpenStack governance. But why such a dedication to an open cloud software ?

    Just as operating systems and virtualization technology come in both proprietary and open source versions, so does cloud platform software. The main reasons open source operating systems and virtualization technology have taken hold in the data center are usually cited as avoiding any vendor lock-in while at the same time optimizing on cost and performance. This trend has continued with cloud software technology solutions, where several proprietary and open source solutions are available on the market. However, without an open-standards approach, organizations will be locked in to a proprietary or point solution that doesn’t interoperate well or that is too costly over the long term. That’s why IBM is investing significantly in sponsoring and supporting open source solutions like OpenStack.

    The lifeblood of any open source project is the community that contributes to it. This is important in terms of the basic usefulness of the project (and hence, product!) and the rate at which the project group accelerates new functionality.

    The OpenStack community has close to 300 companies working together to develop an open source platform that is rich with cloud services. As an example, the latest release—Havana—had some 400 new features added by over 900 individuals from 145 different companies. These features include the core infrastructure-as-a-service layers (compute, network, and storage) and other key capabilities, which include automation, security, and a portal, just to name a few. (* - For this part of my text, I borrowed heavily from the ESG White Paper ‘IBM Storage with OpenStack Brings Simplicity and Robustness to Cloud’ from Mark Peters, Senior Analyst and Wayne Pauley, Senior Analyst)

    This whole idea is reflected in the following illustration of OpenStack with the three core infrastructure-as-a-service layers (compute, network, and storage).

    So, where does that all come together ? And how does it fit in with System z and its related Storage.

    Openstack and System z . . . and more ! ! !

    Therefore we go back to where we started : Openstack and System z. The starting point to me was z/VM 6.3 managed through OpenStack. In an article by Daniel Robinson System z Director Kelly Ryan commented on this : "Whatever cloud computing layer the client is running, whatever tools are pushing down on OpenStack, they can now push down on to z/VM and do the provisioning through it. You can envision a picture where you have your System z pieces, your PowerVM pieces, some VMware pieces, anything that ties up to OpenStack, available in a consistent manner".

    The illustration below shows how that complete picture, including System z, will then look like. As you can see, it’s not only System z, it’s not only IBM distributed platforms, but it’s also 3rd party hypervisors and hardware. You can now service your business or let your business service itself from the grey layer. As a matter of fact all these companies contributing to the OpenStack project make sure that OpenStack is the one communicating with the lowest layer taking care of the provisioning of compute, networking and storage resources  . . . as I promised in the beginning.


    We’ve seen how this already works for z/VM, but let me give you another example with the DS8870. You can find all the details about it in this redbooks Solutions Guide ‘Using the IBM DS8870 in an OpenStack Cloud Environment’ that you can find over here. It also contains some more technical details on OpenStack.

    IBM wrote an IBM Storage Driver for OpenStack enabling OpenStack clouds to access the DS8870 storage system. This OpenStack driver provides an infrastructure for managing volumes and is the interface to the DS8870.
    The dashboard provides a web-based user interface for managing OpenStack services for both users and administrators. So, the OpenStack cloud connects to the DS8870 storage system over an iSCSI or Fibre Channel connection. Remote cloud users can issue requests for storage volumes from the OpenStack cloud. These requests are transparently handled by the IBM Storage Driver. The IBM Storage Driver communicates with the DS8870 storage system and controls the storage volumes on it. Functionalities include such abilities as provisioning, attaching, snapshotting, basic backup, encryption, and quality of service (QoS). In the future, it will grow to include replication management and the changing of service level agreements (SLAs).
    I describe this for the DS8870 but this is also already applicable to the XIV and the StorWize family.

    Is OpenStack visionary, is it already reality ? As you can see for the moment it’s a bit of both but I’m nevertheless convinced that it’s becoming a reality that’s here to stay.

    Thursday, April 17, 2014

    (Not) affected by the heartbleed vulnerability

    Let me start by quoting Wikipedia to define what the heartbleed vulnerability is about : "Heartbleed is a security bug in the open-source OpenSSL cryptography library, widely used to implement the Internet's Transport Layer Security (TLS) protocol. This vulnerability is due to a missing bounds check in the handling of the Transport Layer Security (TLS) heartbeat extension. A fixed version of OpenSSL was released on April 7, 2014, at the same time as Heartbleed was publicly disclosed. At that time, some 17 percent (around half a million) of the Internet's secure web servers certified by trusted authorities were believed to be vulnerable to the attack, allowing theft of the servers' private keys and users' session cookies and passwords. The Electronic Frontier Foundation, Ars Technica, and Bruce Schneier all deemed the Heartbleed bug "catastrophic". Forbes cybersecurity columnist Joseph Steinberg wrote, "Some might argue that [Heartbleed] is the worst vulnerability found (at least in terms of its potential impact) since commercial traffic began to flow on the Internet."

    Does it have any impact on our mainframe or IBM storage environments ?
    Well, if you do a search on the Support site, you get more than a hundred hits on 'heartbleed'. I see that practically all indicate 'not affected by the OpenSSL heartbleed vulnerability'. Let me give some of them :
    • TS7650, TS7650G, TS7680
    • TS7700, TS7720, TS7740
    • TS3500, TS11x0, 3592-C07
    • XIV Gen2
    • CICS Transaction Server for VSE/ESA 1.1.1, CICS Transaction Server for z/OS 
    • DS8100, DS8300, DS8700, DS8800 and DS8870 prior to Release 7.2 
    • OpenSSH for z/OS
    The only one I found so far that is affected is XIV Gen3.
    "XIV management and CIMOM uses SSL to provide confidentiality and integrity of management communications. This vulnerability means that an attacker can potentially compromise management communication, gaining access to user credentials and thereby to unauthorized management access of an exposed system. Since storage management is usually on an internal and separate network, exposure to this vulnerability is limited to users with access to the management network.
    The impact is limited to management communication only, as XIV does not use SSL encryption in the data path".

    Affected products and versions are : "XIV Gen3 systems running microcode versions 11.4.1 or 11.4.1.a are vulnerable via management and CIMOM ports. Versions 11.3.0, 11.3.0.a and 11.3.1 are vulnerable only via the CIMOM port. XIV Gen3 systems running older microcode versions are not affected. XIV Gen2 systems are not affected".

    You can find all additional information for XIV Gen3 over here.

    Tuesday, April 8, 2014

    RealDolmen System z e-zine 21 : Anniversary edition #mainframe50

    The 21st issue of our RealDolmen System z Newsletter was sent out yesterday. You can download it over here. Just like the last time, there's just one English version. No more Dutch or French versions. Do go and take a look at it. There's some contect that hasn't been on the blog. perhaps I'll put my contribution on OpenStack here as well in the coming days.

    The content : here's the introduction that was sent along :
    Today we celebrate the 50th anniversary of the mainframe. IBM announced the S/360 mainframe on this very day emerging from a 5 billion dollar investment initiated by its former president Thomas Watson Jr. And just like with any anniversary you can do two things. On the one hand you can reminisce about the past, celebrate important achievements and tell heroic stories. On the other hand it’s always the perfect moment to look towards the future and determine future strategies in order to hold your place in a competitive world. Of course today we will do a bit of both since one can learn a lot from the past and we need to keep an open mind towards the future. You can read all details in this newsletter.

    We’ll give you an overview of some sites, happenings and social media which are giving a lot of attention to this anniversary. But we will also point out a couple of solutions and trends that are definitely positioning the mainframe in the future. One of those items we already mentioned a couple of times in our blog is OpenStack. This is also becoming a very relevant platform for our mainframe. Next to that we’ll also introduce IBM Wave for z/VM to you. These solutions point towards some future accents like ease of use, bridging the knowledge gap and open standards with software defined environments.

    Finally, we still have our usual entries with recent announcements, interesting blog entries, EOS dates, hints and tips and our agenda.

    Enjoy the reading !