In honor of our 1,000th hit, behold System Z’s answer to Ruby on Rails: COBOL on Cogs!

In all seriousness, the modern mainframe has come a long way towards embracing modern web technologies.  Due to the integration of UNIX into z/OS and the popularity of Linux on the z/VM hypervisor, TCP/IP has become a foundational technology of the zEcosystem.  This is demonstrated by companies such as Marriott making the zEnterpise the heart of their IT infrastructure by adopting a service oriented architecture tied to XML, web technologies, and custom APIs.  Although unimaginable during the era of the S/370 and the Systems Networking Architecture (SNA), companies are adopting APIs as a means to simplify and accelerate the integration of their mainframe and zEnterprise systems into web and mobile apps.  This has the potential to promote the use of the zEnterprise as an Infrastructure/Platform/Software as a Service solution accessible to developers through a standard API.

Even more interesting, it is possible that a private cloud on zEnterprise could follow the steps of Eucalyptus (a public cloud solution) and run an API that matched the syntax of an API stack such as Amazon Web Services (AWS) or IBM’s SmartCloud.  Such a move would allow the instant portability of ubiquitous cloud-based front ends to a private mainframe clouds, potentially following in the footsteps of industry standard technologies (such as TCP/IP, UNIX, Linux, Java) to further open up and promote the mainframe as the centralized “system of systems” of a complex heterogeneous IT environment.  In the web development world, developers have benefited for quite some time from Google and Amazon’s simple yet powerful APIs.  I can’t help but wonder how similar tools could affect the deployment and utilization of the zEnterprise environment in the future.

I challenge you, dear readers, to consider how one could build and deploy an mainframe API that would provide the strengths of flexibility, inter-connectivity, and ease of use without compromising traditional strengths in security and efficiency.  Have you worked with APIs in the past?  Do you think that there is a role for such tools on the mainframe?  What sort of impact would the use of such tools have on the mainframe?  Let’s hear your thoughts in the comments.

Here are some interesting resources related to this idea:
Info on the IBM HTTP Server
Toys and Tools for z/OS UNIX System Services
Guide for Porting POSIX complaint Apps to z/OS UNIX System Services
PHP for z/OS Guide
IBM HTTP Server Cookbook
Porting Apache to z/OS
Coding AJAX Apps on z/OS
System Z APIs
tcACCESS

Happy COBOLing!

Posted in IBM.

With IBM moving towards Cloud Computing and the zEnterprise turning into a “Cloud-in-a-box,” it is increasingly important to track developments in the public infrastructure-as-a-service (IaaS) space.  Most everyone familiar with Cloud Computing knows about Amazon Web Services (AWS).  IBM even offers pre-built images for AWS with many of their software products, including Tivoli and WebSphere.  Despite AWS’ market strength, there are numerous other public cloud providers moving into the IaaS space.  This post will look at some of the other key options for building a public IaaS cloud.

OpenStack

The OpenStack software project started as a cooperative venture between Rackspace and NASA to establish an open-source alternative to Amazon Web Services (AWS). To date, it has released three key components (Compute, Object Storage, and Image Service) under the terms of the Apache License for open-source software. Because this software is open-source and freely available, it can be implemented as either a public cloud (on leased servers offered by Rackspace and others), a private cloud (on a company’s personally-owned hardware), or a hybrid cloud combining public and private elements. Additionally, OpenStack is compatible with numerous full-virtualization and para-virtualization implementations, including VMWare, Xen, and KVM. OpenStack benefits from strong support from its open-source developer community and its numerous industry partners, including AMD, Canonical, Cisco, Citrix, Dell, HP, and Intel. These advantages allow a customer to prototype, test, and deploy a customized cloud infrastructure without fears of vendor or technological lock-in.

Cloud.com

Cloud.com began life as an open-core IaaS package, meaning that it offers two levels of products: a basic open-source community version called CloudStack and a premium Cloud.com enterprise offering that included additional premium features (such as the provisioning of non-virtualized bare-metal hosts). Earlier this year, Citrix purchased Cloud.com and unified the two products as fully open-source software under the GPU GPL v3 license. In addition to CloudStack’s previous support for Xen, KVM, and the latest VMWare products, Citrix has recently announced that CloudStack will soon support the Microsoft Hyper-V hypervisor. A particular strength is that CloudStack can run multiple hypervisors simultaneously. Because of its involvement in the OpenStack project, Citrix is attempted to unify features between OpenStack and CloudStack, but due to licensing differences (Apache vs. GPLv3), CloudStack features cannot be added to OpenStack.

Eucalyptus / Ubuntu Enterprise Cloud

After starting life as a student research project at UC Santa Barbara, Eucalyptus was offered as an open-core IaaS product. The Eucalyptus Enterprise Edition (E3) possesses a number of premium paid features, including SAN integration and advanced VMWare compatibility, that are not yet offered by any of the fully open-source solutions. Like Openstack, Eucalyptus originally partnered with NASA, but frustration over Eucalyptus Systems Inc. refusing to share advanced functionality associated with E3 led this partnership to fall through. Support for Eucalyptus is included in Ubuntu (rebranded as the Ubuntu Enterprise Cloud), but Cannonical has recently announced that OpenStack will be its default Ubuntu cloud solution in future releases. Eucalyptus will nevertheless still be supported by Ubuntu and remains highly compatible with most Linux flavors. A particular advantage for Eucalyptus is its implementation of the Amazon EC2 API stack, which makes it an excellent test bed and development tool prior to uploading to the Amazon Cloud.

Nimbus

Nimbus is an IaaS implementation that specialized in providing cloud solutions for the scientific community. It is compatible with KVM and Xen, and implements most of the Amazon EC2 API. A primary goal of Nimbus is to allow universities and research institutions to share their cloud infrastructures, allowing research projects to access and pool IaaS computer resources as needed. Researchers can submit requests for IaaS resources from a variety of organizations through the scienceclouds.org website. This can be considered an extension of the grid computing concept from batch processing to the cloud, allowing researchers to configure and deploy customized virtual machines on remote resources as needed.

OpenNebula

OpenNebula began as an academic research project on IaaS by Spanish computer science professors Ignacio M. Llorente and Ruben Santiago Montero. Based on the success of their research, these profesors founded the company C12G out of Madrid to promote OpenNebula as an international open-source cloud standard (under the Apache license) and provide commercial support for their open-source commercial offerings. OpenNebula is focused on maximizing compatibility with existing data center resources in creating a private cloud infrastructure. It is able to manage virtual machines across private and public resources to create a hybrid cloud, and it has a greater degree of elasticity and dynamic scalability than Eucalyptus. The OpenNebula standard is increasingly popular in Europe, and it is seeking support from European standardization organizations.

Conclusion

Between all of these non-Amazon IaaS offerings, I believe that OpenStack has the greatest promise to become an important public cloud player due to its fully open-source license, its substantial industry and community support, and its flexibility with various types of hypervisors. An OpenStack implementation would offers the greatest degree of flexibility for shifting virtualized machines across public and private clouds as needed. A customer could rest assured that they would not become locked into a particular cloud provider due to the use of proprietary vendor software or incompatibility between hypervisors. Although not currently the most feature rich offering, OpenStack’s significant industry and community support effectively guarantees that this solution will continue to improve and implement new features over time.

Sources
Posted in Uncategorized.