Power Development Platform (PDP)
PartnerWorld provides how to setup for an evaluation of POWER7 technologies for RHEL 5.5 installed on your VLP system. By upgrading the Linux kernel, and adding a handful of updated tools, the operating system can easily exploit the POWER7 system.
For details go here:
Jwestern 110000974Y 1,048 Views
The system that the web-facing part of VLP runs in will be undergoing some maintenance this weekend. This means that the VLP Web End User Interface (EUI) only will be down for an hour, from 0900 - 1000 CDT on May 31rst. Users will still have access to their reserved systems, since these are not going to be taken down. Also, any reservation that was scheduled to start during this time will start normally.
When we plan downtime, we post a message on the VLP 'Reservation Management' tab. You have to log in to VLP to see these messages, which are rather terse. You can always consult this blog for more details.[Read More]
Software Product Compatibility Reports is an innovative new tool designed to allow customers to easily generate custom reports about compatible IBM software combinations, product end-of-service dates and product translations. Using this tool, customers may create reports about a product's compatibility with operating systems, prerequisite software or virtualization environments. Customers may also use the tool to create tailor-make graphical reports about a set of product's end of service dates. Lastly, using the Software Product Compatibility Reports tool a customer can create reports about the translations available for a product or all the products that have been translated into a specific language.
The tool is now available for use here http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html
Use Promo code 35678 when making a reservation with the IBM Virtual Loaner Program and receive an extra week for your engagement. Instead of the normal two week engagement you will get three weeks. You can always save your reservations and come back again, but this allows more time to get those important projects completed. Just a little something extra from your place for Power systems, AIX, Linux and IBM i. And of course all of this is for no charge. World-wide remote access to the resources you need!
In VLP, there are two ways of backing up your reserved partition. You can save the state of the system immediately (save now) and you can save the state of the system automatically when the reservation ends (save on exit). In both cases, behind the scenes the VLP automation makes mksysb backups of AIX partitions, tarballs of Linux partitions, and backup images of IBM i reservations. I'm very fuzzy on IBM i things, so forgive/correct me if I got the IBM i-specific name for operating system backups wrong. We call operating system backups images in VLP. Once you've saved an image and your reservation that you used to save the image has ended, you can create a new reservation using that saved image. You can view your saved images by looking at the 'Images' tab in the VLP web application.
Now, I just told you how image saving/restoring is supposed to work. Please leave a comment with your image saving/restoring experiences. I'd like to know your opinions of how this works for you, how useful it is, and about any errors you have encountered.[Read More]
Jwestern 110000974Y 1,061 Views
Recently, VLP passed the 10,000 reservation mark. This means lots of IBM Partner World members have used our free service and gained access to IBM hardware. This is what everyone on the VLP development team likes to see. Keep up the good work and please get us to 20,000 as quick as you can.[Read More]
Jwestern 110000974Y 1,459 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 15.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, I found two 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.
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
The IBM Industry Application Platform (IAP) pre-configured stack on the Virtual Loaner Program is now available with AIX 7.1 in addition to AIX 6.1 and AIX 5.3 systems. We have also updated the software components and user guide.
The IBM Industry Application Platform is a pre-configured instance of IBM WebSphere Application Server, IBM DB2 and WebSphere MQ that is available for your IBM AIX 7.1, AIX 6.1 and AIX 5.3 operating- system images on the IBM Virtual Loaner Program (VLP). You can use VLP to develop, test and validate applications by using these products. After reserving your VLP partition, which includes choosing the hardware configuration and operating system, install the IBM Industry Application Platform on that partition. This is a great way to reduce middleware setup time for ISVs!
For details on how to use the IAP on VLP, see the user guide - www.ibm.com/partnerworld/wps/static/pdf/IBM_Industry_Application_Platform_VLP_Guide_v1.pdf
The IBM Industry Application Platform contains the following software components:
WebSphere Application Server v188.8.131.52
DB2 Workgroup Server Edition 9.7.3a
WebSphere MQ 184.108.40.206
IBM Rational Agent Controller v8.3
Users can reference the IAP user guide from the VLP How To page - www.ibm.com/partnerworld/wps/pub/systems/vlp/howto
Jwestern 110000974Y 323 Views
The PDP now offers Ubuntu 15.10 beta image
Try it out today!
Test and develop on the JS22 POWER6 blade
Users are now able to reserve LPARs on JS22 Power6 blade hardware for development. If you prefer to develop on the blade hardware or simply want to test/validate your solution simply select the POWER Blade JS22 hardware architecture when filling out the resource reservation.
Learn more about IBM Bladecenters and Power blades:
The Virtual Loaner Program now has a Group on the new My developerWorks. The VLP Group has Message Boards, Feeds and Links to help you get the most out of your VLP experience. So please join us and explore all that the new My developerWorks has to offer.
The VLP Group on My developerWorks
The newly updated VLP FAQ is now on IBM developerWorks, everything you wanted to know and weren't afraid to ask!
Virtual Loaner Program FAQ on IBM developerWorks - General
Virtual Loaner Program FAQ - AIX
VLP System Users,
There was a catastrophic failure at the electric power substation which supplies power to the data center housing the IBM Virtual Loaner Program, the morning of 24-Feb. The VLP data center has a fully functional and frequently tested backup electrical power system which includes diesel generators. However, the erratic nature of the failure at the substation resulted in the loss of part of the backup configuration. As such, the entire remote access computing environment was shutdown in an abrupt but organized fashion rather than expose the equipment to a shutdown caused by the sudden and total loss of electric power.
Most of you experienced an outage from about 0930 CT to about 1900 CT. With a few exceptions, the VLP is again fully functional. If you are still having trouble, please contact VLP Support via the Support tab on our website or Live Chat so we can help you resolve the issue.
The VLP team, Dallas sincerely regrets the inconvenience caused by this failure. The events and associated logs will be carefully reviewed and appropriate preventative measures will be implemented.
Thanks for using the VLP
Virtual Loaner Program: www.ibm.com/systems/vlp
The Partition Mobility function requires a promotional code - 213068. Please reference the VLP LPM User Guide to get started.
IBM Smart Business