Happy 2015 to everyone!
A new update release for the 8.0 series of the IBM Advance Toolchain for Linux on Power is now available.
This release provides:
For download links, more information and documentation, please refer to our o
Please let us know if you have any questions about this release.
About the IBM Advance Toolchain for Linux on Power
The IBM Advance Toolchain for Linux on Power is a set of open source development tools (compiler, debugger and profiling tools) and runtime libraries that allow users to take leading edge advantage of IBM's latest POWER hardware features on Linux.
Using the IBM Power Development Cloud for Red Hat Enterprise Linux 7.1 (little endian) Beta application testing
Excitement continues to build around Linux on IBM Power Systems from the first Scale-out POWER8 processor-based systems shipped in mid-2014 to the Enterprise POWER8 processor-based systems which began shipping in 4Q2014 and includes the Integrated Facility for Linux support. A big part of that excitement is around the new little endian distributions (Ubuntu and SLES), and their ties to the OpenPOWER Foundation (and the requirements it generates). Now, Red Hat has joined the party with a Red Hat Enterprise Linux 7.1 Beta for Power Systems based on little endian. IBM is making it easy for ISV’s to test their Red Hat Enterprise Linux applications, even before the Red Hat 7.1 general availability! More choice, more flexibility, more POWER8!
To be clear, Red Hat is continuing support for their Power Systems big endian distro – that is also included in the Red Hat Enterprise Linux 7.1 Beta. But for many ISV’s coming from x86, moving straight to little endian may be the right direction to go from the beginning. This means the Linux applications can migrate freely between POWER-based and x86-based systems. To learn more about big and little endian, refer to endian FAQs on developerWorks .
IBM is keeping the party going with the Power Development Platform (Power Cloud) which is offering a Promo Code for ISV’s to port/test their applications even before Red Hat declares general availability of the 7.1 distro. If you are an ISV, you can use Promo Code 8217658 for the Power Development Platform (PDP) (click on the Program Tab). Additionally, IBM will be offering Red Hat Enterprise Linux 7.1 porting and testing at the IBM Innovation Centers (IIC’s). For developers of corporate apps, ask your IBM account rep to help you get access.
ISV’s utilizing the PDP for porting and testing will find each VM including 35 GB of Storage, up to 4 POWER8 vCPU’s, and 8 GB of memory. IIC setup will be customized for the particular partner’s needs, and both PDP and IIC’s will support not only the Red Hat Enterprise Linux VM, but also supply the latest IBM Java and the Advance Toolchain for Linux on Power Systems with Red Hat Enterprise Linux little endian support. The IBM Software Development Kit for Linux on Power Systems (SDK), will be available soon.
For more background on porting from x86 Linux to the Power platform, you can get started here with the Guide to porting Linux on x86 to Linux on Power.Take advantage today, and you’ll be ready for tomorrow…POWER8, Red Hat, and little endian -do I hear Linux for the Enterprise?
rfolco 270004CUW7 Tags:  powerkvm zuul nodepool openstack-infra jenkins ci openstack 3rd-party-ci devstack-gate continuous-integration tempest 10,351 Views
by Rafael Folco <firstname.lastname@example.org>, OpenStack CI Engineer
I've just published an article discussing some basic ideas for building a 3rd party Continuous Integration system. It covers important aspects to plan, install and configure a 3rd party CI environment to test OpenStack upstream patches.
The article also explains how the CI services interact each other and what kind of customization you need to test your platform or driver on OpenStack patches.
For more information about IBM PowerKVM refer to the Redbook.
Bill_Buros 270000QDEP 8,661 Views
A great technical educational video has been posted over on YouTube from the Linux.conf.au 2015 conference.
KVM on IBM POWER8 servers, by Paul Mackerras
Paul Mackerras walks the viewer through how Linux has been extended to open-source firmware, KVM enabling, and the latest Linux-only POWER8 systems.
This is a 45-minute video - Paul's presentation in its entirety.
Interesting discussions points are the KVM handling of the SMT 8 threads per core, and the POWER8 "micro-threading" - which splits the POWER8 core into sub-cores, and the system characteristics when leveraging these modes. Scheduler ramifications are covered, giving the viewer a better sense of the KVM implementation.
The presentation is a fairly deep technical discussion of Power8, Linux kernel, and the implementations. Check it out.
XL C/C++ and XL Fortran for Linux evaluation versions now hosted on public apt-get and zypper repositories!
Dwayne_M 10000005FD 5,890 Views
Now there’s an even easier way to get you started with your evaluation of the latest XL C/C++ (V13.1.1) and XL Fortran (V15.1.1) for Linux compilers for the little endian Linux distributions on Power Systems (Ubuntu 14.04, Ubuntu 14.10, and SLES 12).
We are now hosting the latest evaluation versions on public apt-get and zypper repositories.
You can find everything that you need to get started at http
jscheel 0600025BWM Tags:  jscheel applications linux le power powerlinux 2 Comments 16,959 Views
In June of last year, I started publicly discussing the role that little endian (LE) plays in our Linux on Power strategy with the blog, Just the FAQs about Little Endian. Then, in August I attempted to eliminate uncertainty in my Removing the FUD and Demystifying LE (little endian) article. With the announcement of the Red Hat Enterprise Linux 7.1 beta delivering an LE version, it is time to revisit little endian from the perspective of an application developer.
The release of RHEL 7.1 LE completes the offerings of little endian operating systems. Canonical had Ubuntu 14.04 ready for POWER8 launch in May. SUSE supported the launch with public statements by Michael Miller about SLES 12 being LE in May, and publicly released in October. It is now time for application developers to get busy: little endian Linux on Power is here!
One thing that being a developer by training has taught me, is that “we” often need to be convinced that work is worth doing. Little endian Linux on Power is about reducing the cost of migrating an application AND providing additional value of the end application.
Being able to run Linux on Power in LE mode means that applications have one less thing – data endianness – to worry about in the port. While technical differences such as assembler language, page size, and cache size still exist, developers and architects tend to worry most about data endianness because the finding and fixing all the problems can be very time consuming. By enabling Power to run in the same endian mode as x86 (the defacto Linux platform of choice for developers), applications can simply be recompiled without having to worry about endianness. Further, if one is going to build a solution mixed with x86 and POWER systems, exchanging data on disk or across the network in the same endian mode greatly simplifies the application as well. Then, add in the ability to accelerate Power applications with (inherently little endian) GPUs and the benefits of little endian become “a no brainer”.
So, hopefully, we're past the “why should I do this?” phase and now we address the list of technical resources for migrating to Linux on Power. My favorite list of resources include:
Now let us take a look at “where can I get started?” The answers to this question depend on your role in the software ecosystem. If you are a software provider, my colleague Bob Dick, recently published he thoughts on how to get started in a the Using the IBM Power Development Cloud for Red Hat Enterprise Linux 7.1 (little endian) Beta application testing blog posting. Programs like IBM PartnerWorld provide this and more resources to facilitate porting. Check them out.
If you are a “in house” owner of an application in your enterprise, finding a system on which to port your application could be challenging. Of course, your IBM Sales contact or your business partner can provide alternatives such as try-and-buy or proof-of-concept systems. Do not hesitate to start with them. If you do not know them, or if this does not work out, go to the cloud! Site Ox offers a two week free trial for development purposes. Visit their website for details. As we move forward, I remain hopeful that other vendors will provide public offerings of Linux on Power images. Further, if you do not at first see the particular release for which you are looking, reach out to the service provider and request it. They might just surprise you and have a plan to provide it. If not, it helps them to hear your needs.
For open source developers, the access to free cloud images increases. The Open Source Labs at Oregon State University hosts Power development images (VMs). University of Campinas (UNICAMP) also hosts a minicloud in Brazil. In China, the SuperVessel Cloud provides a similar service to developers. In addition to these three locations, we are hoping to extend our offerings in both Europe and India in the near future. Again, the particular releases hosted at these sites may vary, but will generally include the little endian versions of Fedora, openSUSE, and Debian. If none of these sites or offerings work for you, feel free to reach out to me on Google+ (loaner post) to explore a dedicated loaner system.
With a complete set of little endian Linux on Power distributions, a robust list of technical resources, and plenty of resources for porting applications, the future is here. Take the first step. Seize the moment. Let's see what you can do with Linux on Power!
breno.leitao 270001BNJT 17,128 Views
System administrators are very used to handle several different complex services that run interconnected and in parallel on high availability servers. In this scenario, it is hard to understand all the architecture and application connections in a single server, so you do not break it when trying to fix or update something. It is also common to bump into servers that are not even updated accordingly, because the system administrators are so afraid of architecture the server was build, that they usually prefer not to touch these servers. This is the kind of issue that we will try to solve in this article.
With the advent of virtualization and tools used to handle nested operating system, some engineers realized system administrators' apprehension and tried to decrease it by using containers isolation, pre-installed applications and control version concepts. They eventually came up with Docker, that is a layer over Linux containers, and could be seen as a lightweight virtualization.
On the Docker architecture, each application runs in a single container, and each container supports only one application, meaning that all files in a single container exist solely to support that application. In this scenario, a container is a minimal operating system plus the application it will run. One of the most common minimal operating system is Ubuntu Core, that is based on, as you might expect, Ubuntu.
Ubuntu Core and Docker on an IBM POWER8 server is a good combination for customers looking for an efficient and agile method to deploy complex workloads on the cloud.
What is Ubuntu Core?
Ubuntu Core is the minimal Ubuntu installation ideally for small environments. It contains just the basic OS layer that supports any other software to run over it.
It is basically a 200MB Linux rootfs that contains around 196 packages that can be extended to be a full distro. Since it contains the dpkg and apt tools, you can install whatever you want to tailor it to your needs.
Ubuntu core follows traditional Ubuntu release, and it started to ship for ppc64el architecture at 14.04, and the latest release is 14.10. You can also find daily build for Ubuntu core at Ubuntu Core daily builds website. In this article we are going to use Ubuntu Core version 14.04 on a standanrd 14.10 Ubuntu Docker host.
Ubuntu Core could be used on containers, Docker, chroot and virtualization environments.
What are Linux Containers?
Linux Containers is the basic technology behind Docker. A Linux container is the technology that would enable an operating system virtualization on Linux, providing all the infrastructure to isolate different containers.
Linux containers rely basically on two technologies that enable the existence of containers:
In order to guarantee that Linux Containers work fine on your machine, you can run a script that guarantee that your environment is sane. To do so, as root run:
Figure 1: Verify that your server supports containers.
What is Docker?
Docker is an infrastructure to deploy applications/software inside a Linux container, so, instead of having a full set of applications being used on the same machine, you can have an application per container, and deploy multiple containers.
For each container, you can have a version control for it, which means that you can 'commit' and 'revert' changes, so, you handle a complex set of applications breaking them in easier containers.
Using Docker hub, you can also upload, share and download already pre configured containers for your environment, so, instead of installing a complex application, you can download a container with an already installed application.
Installing Docker in Ubuntu on Power
In order to install docker on Ubuntu 14.10, you should do the following steps as root:
This is a example of the package being installed on a 2-sockets POWER8 S822-L machine.
(you may click on these images to see a larger version of the image)
Figure 2: Docker.io package being installed on Ubuntu 14.10
Creating the Ubuntu Core image in Docker
Figure 3: Listing the fresh installed ubuntucore image
Figure 4: Assuring that the container is running
Using a preloaded Ubuntu Core image
If you want to use a default Ubuntu Core image for ppc64el, you don't need to do the step below, you can just install an already installed image. In order to do so, you need to be registered at Docker Hub website, which is similar to a github for docker images. Once you have registered there, just login using docker and then search for a ppc64el image.
# docker login
Figure 5: Authenticating in Docker hub
# docker pull image.
This is an example that I have been using on my personal registry.
Figure 6: Download Ubuntu Core 14.04 for POWER
This is going to create a Ubuntu core image in your system, which would enable you to play with Docker and Ubuntu Core on POWER. Once you have that, you can list the docker images and you are going to find the image leitao/ubuntucore as part of your images. As always, you can run any command on this image using:
# docker run image <command>
Commiting and reverting changes
Once you have your image running, you can change it as you want, and commit the changes. For example, let's install a package into the my ubuntucore image:
After git is installed you can check that there is a modification, using:
Later, you can see what files were modified after the change, using the container ID, as:
If you like your change, you can commit it using docker commit command and then upload the changed image using docker push command.
Automating container creation
It is possible to automate the image creation using the concept of Dockerfile, which describes how a Docker image is created starting from a base image.
A Dockerfile is generally used to create custom images, as you can execute command and copy files into an already existing image, giving it a personal content.
A Dockerfile is a plain text that uses a small set of commands to create a customized image. In the following example we are going to create an image with mongodb installed, and copy some customized etc files.
This is how the Dockerfile looks like:
from ubuntucore # use the initial image called ubuntu core maintainer "Breno Leitao" # The author for this new image run apt-get install -y mongodb # Run a command to install mongodb into the image copy /srv/mongodb/etc /etc # Copy the directory /srv/mongodb/etc to inside the image /etc
In order to run this Dockerfile, you need to save it and run the following command on the directory that contains this file:
# docker build .
Once you run it, you are going to have a new image that is based on the ubuntucore image, with the package mongodb installed and the files from the 'host' /srv/mongodb/etc copied to the container /etc directory.