Power Development Platform (PDP)
Jwestern 110000974Y 1,629 Views
Jwestern 110000974Y 4,099 Views
New on the the Power Development Cloud! (PDP)
- Updated Ubuntu 16.04 and 14.04 now includes at10.0, xlc fp5 and xlf fp5 pre-installed
- RHEL 6.9 BE has now been upgraded from beta level to GA
Jwestern 110000974Y 4,865 Views
The IBM SDK for Linux on Power 1.10 is now available!
Get it here:
Support for ppc64, ppc64le and x86 64/amd64
Updated support for the three supported architectures and the following operating systems: Ubuntu 14.04 and 16.04, RHEL 7.2 and later, SLES 12 SP1, CentOS7 and Fedora 22.
New Migration Wizard
The new Migration Wizard simplifies the migration process by automatically locating issues within a project, such as source code that might produce different results when run on Power. The wizard also provides an issues report and may fix potential migration problems automatically.
New Integration with IBM POWER9 Functional Simulator
The SDK provides support for the simulator of the next generation of IBM’s processor. The simulator is designed to provide enough POWER9 processor complex functionality to allow the entire software stack to execute, including loading, booting and running big and little endian Linux environments.
New Integration with Advance Toolchain 10.0
The new Advance Toolchain 10 provides a set of updates on GCC, Glibc, Binutils and includes support for IBM Power 9 processor.
New Integration with IBM XL C/C++ Community Edition Compiler
IBM XL C and C++ compilers offer advanced compiler and optimization technologies. The SDK now includes a native support (tech-preview) for the new Community Edition version of IBM XL C/C++ Compiler.
New Docker Management Tooling
The new Docker Tooling plug-in allow users to manage Docker Images and Containers located in a remote machine using the client SDK running on your laptop.
New Suggestions on Build Advisor
The Build Advisor plugin now offers suggestions on the main set of flags for Advance Toolchain and IBM XL C/C++ Community Edition Compiler.
New Quick-fixes on Source Code Advisor
Two new quick-fixes in the Source Code Advisor plugin for ”TOC store in loop optimization”and ”Killed registers”events.
Increased built-in detection on Migration Advisor
In this new release, we have added support for more than two hundred SSE built-ins, making the MA 1.10 capable of detecting and migrating automatically about four hundred Intel® intrinsics to altivec.
Updated Installation Resources
The simplified installation procedure with a single script to download and perform the installation of the SDK, Advance Toolchain, and IBM® Power Tools repository was updated to include the IBM XL C/C++ Community Edition Compiler.
New visualization graphics and drill down on IBM Power Systems Performance Advisor
The Performance Advisor plugin easy the profiling results visualization by using bar charts. In addiction it includes a new drill down feature which allows visualizing the source code line which might be problematic.
Built on Eclipse Neon
The SDK leverages the latest stable version of Eclipse Neon (4.6.0).
Updated Eclipse Components
The SDK bundles the latest stable versions of Eclipse CDT, Eclipse PTP and Eclipse Linux Tools.
New resources on Cheat Sheets
The Cheat sheets provide a quick help inside the Eclipse IDE (Help > Cheat Sheets). Each cheat sheet is designed to help completing a specific task, listing the sequence of steps required to achieve that goal.
Jwestern 110000974Y 5,115 Views
RHEL 7.3 beta image now available on the Power Development Platform.
Jwestern 110000974Y 4,607 Views
The Power Development Platform (PDP) is planning an upgrade and migration of our storage infrastructure which will allow us room for additional growth. As part of this migration, we will need to drop support for restoration of older IBM i saved images (IBM i6.1.1 and i7.1 prior to TR8). Please backup or migrate critical data from your systems prior to this upgrade which is planned to occur on June 3rd 2016. We appreciate your patience and understanding.
For more details and to ask questions:
Jwestern 110000974Y 4,826 Views
We now have the Ubuntu 16.04 LTS beta image in PDP.
http://ibm.com/partnerworld/pdp … #IBMPower #Ubuntu
Release notes: https://wiki.ubuntu.com/XenialXerus/ReleaseNotes
IBM i 7.3 release is available on the PDP - http://www.ibmsystemsmag.com/Blogs/You-and-i/April-2016/IBM-i-7-3-Announce/
New on the Power Development Platform:
The IBM Data Engine for NoSQL - Power Systems Edition creates a new tier of memory by attaching up to 57 Terabytes of auxiliary flash memory to the processor without the latency issues of traditional I/O storage. This system is configured with software in a development EMULATION mode, and does not contain real CAPI Flash accelerators. It is intended as a development platform and is suitable for software development, unit testing, and code integration tasks.
For more information, refer to the following resources:
- http://ibm.biz/capiflash - Technical Whitepaper about the IBM Data Engine for NoSQL, including best practices
- https://github.com/open-power/capiflash/ - Complete source for Data Engine for NoSQL enabling software, including test cases
- /opt/ibm/capikv - Software installation on this system, which includes example code, sample applications, headers, and shared libraries, compiled in a development "FILE MODE."
To get started with key-value layer APIs (libarkdb) pass a NULL "file" string to ark_create(...). The database will automatically allocate key/value pairs in system RAM instead of flash.
To get started with block-layer APIs (libcflsh_block) create a temporary block file on the local file system (this is for development purposes only, e.g. "fallocate -l 2G ~/blockfile"), then pass that file path to cblk_open(...). The block APIs will read / write data to this test file instead of a real flash accelerator.
Once software is ready for testing on real systems, dynamically or statically-link to production CAPI Flash shared libraries which are available on the system with real accelerators, or available on IBM FixCentral (search for the EJ16 feature code).
Jwestern 110000974Y 5,866 Views
Red Hat Enterprise Linux 7.2 (little endian) Beta is now available on the IBM PDP
More info from Red Hat
IBM Linux Power Community Blog Post
Docker images for ppc64le are making their way onto Docker Hub!! https://hub.docker.com/u/ppc64le/
The repository contains base images that are commonly used to create a number of popular images.
As an example, the official docker repository for Java is built from the buildpack-deps image.
We can use the image ppc64le/buildpacks-dep to create a Java image using the same Dockerfile (with slight modification) that is used for x86_64
Check out our previous blog post on requesting a Virtual Server instance with Docker pre-installed to test out the steps below...
From your pp64le system running docker....
$ sudo apt-get install -y git
$ git clone https://github.com/docker-library/java.git
$ cd java/openjdk-7-jre
Now edit the Dockerfile, substituting 'FROM buildpack-deps:jessie-curl' with 'FROM ppc64le/buildpack-deps:jessie-curl' and initiate the build
$ sudo docker build -t java-ppc64le:openjdk-7-jre .
Once the build is complete we can see the new image in our local repository
$ sudo docker images
Running the image we can see that java 1.7.0_85 was installed
$ sudo docker run -it java-ppc64le:openjdk-7-jre /bin/bash
root@f69dff8037e1:/# java -version
Jwestern 110000974Y 5,082 Views
The PDP now offers Ubuntu 15.10 beta image
Try it out today!
Jwestern 110000974Y 6,816 Views
AIX 7.2 Beta is available on the Power Development Platform.
As always with AIX, Binary Compatibility continues with the AIX 7.2 release, so if your applications run on AIX 6.1 or 7.1, they'll also run on AIX 7.2. For more on Binary Compatibility, go here.
You can access the Beta in one of several ways:
Note: To participate through the ESP, you will need an activation key. To obtain a key, fill out the form.
At a glance, the AIX 7.2 release includes the following new function:
• AIX Live Update for Interim Fixes.
• Cluster Aware AIX (CAA) automation with repository replacement mechanism.
• SRIOV-backed Virtual Network Interface Card (VNIC).
• RDSv3 over RoCE adds support of the Oracle RDSv3 protocol over the
Mellanox Connect RoCE adapters.
• CAPI (Coherently Accelerator Processor Interface) infrastructure and support
for CAPI attached flash storage.
• Flash caching. Workloads can take advantage of a read-only cache.
Jwestern 110000974Y 6,530 Views
POWER8 is the first processor designed for Big Data, Analytics and Cloud.
There are plenty of reasons why Power Systems are the top choice of clients for scalable systems and the market place data proves it. IBM is the 8-socket and above revenue leader, according to IDC, and used by 10 of the top 10 banks, 10 of the top 10 telcos, 8 of the top 10 Insurers, and 8 of the top 10 retailers. When you add in the bold, unprecedented OpenPOWER initiative, the path for even greater collaborative innovation is unlimited.
Want to hear more? Attend a Linux on Power workshop at one of the worldwide IBM Innovation Center where industry experts will talk about the competitive advantage of IBM Power Systems.
Come hear the latest announcements and news on the OpenPower Foundation and IBM Power Systems.
IBM Power Systems Scale-up and Scale-out Offerings including the addition of the E850 and up to 192 cores and 16TB memory in the E880 and new Operating System support.
IBM Power Systems Cloud Offerings including Docker on Power support in Ubuntu 15.04, the new Cloud Manager with OpenStack 4.3 Kilo release and a preview of POWER8 in SoftLayer which GAs in 2Q
IBM Power Systems Big Data & Analytics Solutions including Power Systems Solution Editions for SAP HANA (Up to 40 cores and 2TB of memory) and hear about perfect linear scaling of IBM DB2 with BLU Acceleration up to 192 cores
Still skeptical? Try it to believe it. Bring your Linux code and try it on systems provided by the Power Development Platform (PDP) Cloud and the IBM Innovation Centers (IICs). At the end of this workshop, you'll be able to access a POWER8 virtual server anytime and anywhere to develop, test, tune, proof of concept or demonstrate your application. Get hands on with a pre-built LAMP or WebSphere/DB2 stack. Check out the capability of Docker on Power!
Article by John Jacobson
Jwestern 110000974Y 13,557 Views
Testing Docker on the IBM Power Development Cloud
By John Jacobson, IBM Cloud Technical Specialist
There have been a few other blog posts written about Docker on Power (see references at the end of this article) so while this is not the first article written about this topic, this is my account of leveraging the IBM Power Development Cloud (PDP) to test and gain familiarity with this container technology on IBM Power Systems....for free.
The Virtual Server Request
The PDP currently provides Virtual Server access for Power Systems. This is not a Container as a Service like they offer in Bluemix. However, this does not mean you cannot request a virtual server and get Docker running yourself.
To request Virtual Server access on the PDP, follow the easy steps in the Create reservation user guide https://public.dhe.ibm.com/partnerworld/pub/pdp/create_pdp_reservation_guide.pdf
When making your request, be sure to specify the 'Ubuntu Linux' as the Image category and 'Docker on Ubuntu 16.04' under Select an image.
Once the reservation is available, you can run a few commands to see that docker is installed
$ sudo docker version
$ sudo dpkg -l docker.io
Check to see if if the docker service is started
$ sudo service docker status
Jun 11 10:05:27 sys-5920 docker: time="2015-06-11T10:05:27-04:00" lev...)"
If docker is not started issue the following command and check the status again
$ sudo service docker start
$ sudo service docker status
The Docker installation creates a local private network on the virtual server instance. This means by default you won't be able to access your containers unless you expose the particular port. I found a couple different ways to do this. One using the Dockerfile (EXPOSE) as well as deploying the container with -p PORT:PORT. There is an example of this further down in this article.
docker0 Link encap:Ethernet HWaddr 56:84:7a:fe:97:99
eth0 Link encap:Ethernet HWaddr 52:54:00:8c:6a:18
If you did not request the Docker image above or you are testing in your own environment here are the steps to install Docker...
Looking at various blogs, there are multiple methods to install docker.
$ sudo dpkg -i docker.io-1.4.1-dev_ppc64el.deb
$ sudo echo deb http://ftp.unicamp.br/pub/ppc64el/ubuntu/14_10/docker-ppc64el/ utopic main >> /etc/apt/sources.list
$ sudo apt-get update
$ sudo apt-get install docker.io
NOTE: As of Ubuntu 15.04 Vivid Vervet, Docker version 1.5 is included. Therefore the apt repository ftp.unicamp.br is not required.
$ sudo apt-get update
$ sudo apt-get install docker.io
Check the the installation and status of the docker status using the commands that were previously covered.
Create and Run your own initial base image
There are a couple different methods to get a base image up and running. I tested only the first one as it seemed to be the easiest to get things up and running.
$ cat ubuntu-core-14.10-core-ppc64el.tar.gz | sudo docker import - ubuntucore-ppc64le
$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
NOTE: Other ubuntu-core images can be found here ubuntu-core images can be found here http://cdimage.ubuntu.com/ubuntu-core/
Since I didn't test Method 2, I don't have any notes to share. If you want to try it, its described in Step 2 here https://www.ibm.com/developerworks/library/d-docker-on-power-linux-platform/
Once I had the image created, I issued the following command to run it. This created the container and allows an interactive shell.
$ sudo docker run -t -i ubuntucore-ppc64le:latest /bin/bash
NOTE: flags -i interactive -t allocate pseudo tty
Container Images can be tagged with a label to help identify it. Tags are typically used to specify versioning.
$ sudo docker tag c2511a3aafad ubuntucore-ppc64le:14.10
$ sudo docker images
Run Registry images
One of the features of Docker is the portability of images. Docker hub and private registries are services that enable the sharing of images. So I went to http://hub.docker.com, clicked on Browse & Search and entered 'ppc64le'. This returned a number of images, so I thought I would download and test.
Here's a list of what I found!
Pull and run image
To test pulling and running an existing registry image, issue the following commands
$ sudo docker pull schabrolles/odoo_psql_ppc64le
$ sudo docker run -d -p 8069:8069 schabrolles/odoo_psql_ppc64le
To see that the container is running issue the command
$ sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
We can see port 8069 is mapped/exported to the docker host IP:port so you can visit http://<IP_ADDRESS_OF_VIRTUAL_SERVER_RESERVATION>:8069
Create and run your own Container Image (Dockerize) So we've seen how an existing container image was pulled from the registry so let's look at how a container image is built. Container images are built using a Dockerfile. More details on Dockerfile can be found here https://docs.docker.com/reference/builder/
On the Virtual Server issue the following commands
$ mkdir -p ~/dockerize/mongodb
$ cd ~/dockerize/monogdb
$ touch Dockerfile
Then add the following to the Dockerfile
MAINTAINER John Jacobson email@example.com
RUN echo "deb http://ports.ubuntu.com/ubuntu-ports/ utopic universe" | tee /etc/apt/sources.list.d/ubuntu-utopic.list && \
sudo apt-get update && \\
mkdir -p /data/db
NOTE: Consider the use of $(lsb_release -sc) instead of hardcoding the ubuntu release name. This allows portability of your Dockerfile across different versions of the Distro.
i.e. RUN echo "deb http://ports.ubuntu.com/ubuntu-ports/ $(lsb_release -sc) universe" | tee /etc/apt/sources.list.d/ubuntu-$(lsb_release -sc).list
Build the container
To build the container, issue the following command from the directory ~/dockerize/monogdb
$ sudo docker build -t mongodb-ppc64:latest .
Sending build context to Docker daemon 2.56 kB
deb http://ports.ubuntu.com/ubuntu-ports/ utopic-updates universe
paring to unpack .../libpcap0.8_1.6.2-1_ppc64el.deb ...
Setting up mongodb-clients (1:2.6.3-0ubuntu5) ...
Adding system user `mongodb' (UID 101) ...
Processing triggers for libc-bin (2.19-10ubuntu2) ...
Step 3 : EXPOSE 27017
---> Running in 90b960218f64
Some of the bulid steps have been omitted but in the end you should see a message indicating that the container was successfully built
List new container image
To see our new container image issue the following command
$ sudo docker images | grep mongodb
NOTE: We use grep as to filter our the list of images to just ones containing mongodb
Run the container
To run the newly created mongodb container, issue the following command
$ sudo docker run mongodb-ppc64le
usr/bin/mongod --help for help and startup options
Additional Container Tasks
To remove an image, issue the following command
$ sudo docker rmi <image id or name>
NOTE: You may have an issue removing an image if you deployed a container. Even if the container is no longer running, you will get this error. You need to remove the container first OR use -f i.e. $ sudo docker rmi -f
To remove a container, issue the following command
$ sudo docker rm <container id or name>
Push a container image to a Repository
So once I had my mongodb container image, I thought I would try pushing it to Docker hub. However, when I tried to push it, I got a message about buffering to disk and then it failed. This was with version 1.4.1. Interestingly enough, I was able to push images with the prior version of 1.3.0 (but this is pretty old). Instead I created my own local registry to test the push capability. I used the local registry setup instructions documented in Step 3 here https://www.ibm.com/developerworks/library/d-docker-on-power-linux-platform/
Once my local registry was setup, I was then able to proceed to pushing my image
First you need to tag your current local image appropriately
$ sudo docker tag c608a51dc0ce localhost:5000/mongodb-ppc64le
Then you can push
$ sudo docker push localhost:5000/mongodb-ppc64le
$ sudo docker images | grep mongodb
Remove all exited containers
$ sudo docker ps -a | grep Exit | cut -d ' ' -f 1 | xargs sudo docker rm
Jwestern 110000974Y 5,617 Views
The PDP will be taking a scheduled outage from November 2 until November 6. This includes all current user systems and the PDP Programs Access Web Page. The outage is to migrate the complex to another location to facilitate room for future expansion. We will update via Twitter and this blog when the PDP is available.
Follow our Twitter @ibmpdp.
Thanks for your patience and understanding.