Power Development Platform (PDP)
I'm Bob Welgan, and I'm a developer/designer on VLP. I'm very interested in your questions and feedback about how VLP works. I'll try to post regularly about changes we are making to VLP. One of the things we are working on right now is to better represent the convergence of IBM servers into simply POWER5 and POWER6-based systems. Also, we are excited about our recent deployment of IBM i on POWER6 servers. Stay tuned to this blog for more information about that part of the offering.[Read More]
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]
If you are visiting the VLP blog for the first time, please leave us a comment or question. If nothing else just just post a comment to say hello. We would love to hear from you and know who is visiting.[Read More]
Please join us here for a VLP Live Q&A Chat session, Thursday May 28 at 2:00PM-3:00PM Central US Time. The VLP Team will be there to answer your questions. The Live Chat will be here on the VLP Blog, look for the Chat box that Thursday. Please mark your calendars and come join in the discussion.[Read More]
Leveraging IBM's virtual loaner program (VLP) can help you experience the new IBM POWER7, the next generation of Power Systems technology. Starting February 9th, VLP users can reserve POWER7 systems running AIX 6.1 TL4 SP2 or SLES 11. This is a great way to test/port/evaluate/demo your solutions on the all new POWER7 AT NO-CHARGE!
Where else can you get a POWER7 system within 2 hours?? Come try it out and let us know what you think - either by filling out the end of reservation survey, responding to the VLP blog or by contacting our VLP support through e-mail or Live Chat. We'd love to hear from you!
IBM PartnerWorld members can enjoy this easy-to-use, fully automated and dedicated environment at no charge. The VLP provides a wide range of operating systems, including AIX, IBM i, Red Hat and SUSE Linux along with POWER7, POWER6 and POWER5 hardware.
Users on the VLP Web site (www.ibm.com/systems/vlp) can use live chat or e-mail via "We're here to help" for answers to questions or help along the way. Visit the site to sign up and reserve a system.
Please join us here for another VLP Live! Q&A Chat session, Thursday, July 9 at 10:00am Central US Time. The VLP Team will be here again to answer your questions. Please mark your calendars and come join in the discussion. The VLP team is looking forward to the Live Chat session and hope to have a good turnout from our users!
What would you like to see in the VLP blog? What information would be the most helpful for you?[Read More]
Membership in the IBM Academic Initiative is the best way to ensure that you have the latest technology and tools to use in your curricula and research, while supporting the culture of open standards throughout the industry.
Who can join? Faculty members and researcher professionals at accredited institutions of learning, all over the globe. Membership is granted on an individual faculty basis. There is no limit on the number of faculty members from an institution that can join.
What does it cost? Your only "cost" to join is the time it takes you fill out the registration forms and get approved. After that, the majority of our offerings are available to you at no-charge. This includes the ability to download all the available IBM technology and courseware, remote access to certain hardware systems, participation in technical webcasts, electronic delivery of our newsletter, and much more.
Why bother to join? Members get access to a wider range of assets, are eligible for additional discounts and assistance, and build collaborative partnerships with IBM and other institutions in the open source community. With the possibility of leadership in your field, prestige for your school, and highly employable students....what's not to like?
The IBM Power Development Platform now has the next generation of Power Systems servers incorporating IBM's POWER8 processor.
For more info:
Please join us here for a VLP Live Q&A Chat session, Thursday May 28 at 2:00PM-3:00PM Central US Time. The VLP Team will be there to answer your questions. Please mark your calendars and come join in the discussion.
The VLP team is looking forward to the Live Chat session and hope to have a good turnout from our users!
We want to keep the discussions general to benefit everyone attending and not dive into issues relating to a particular system/application. If you have a specific question or issue with your VLP reservation please submit those to the VLP support team by going to the VLP support tab.
Examples of topics for the Live Chat include: connectivity/performance, security, VLP usage models, save and restore, using the Software Access Catalog, managing reservations, new virtualization features, etc. These are just examples which do not cover everything - please feel free join us and ask questions. We want to provide useful information for our users and gain your input so we can continue to provide a valuable offering in the VLP.
New in VLP February 2008:
i5/OS V6R1 is available for early access on VLP. Reservations requested for i5/OS V6R1 require a Non-Disclosure Agreement. For access, send your request to "firstname.lastname@example.org", providing your Name, Company and PW id.
VLP provides System p partitions with PowerVM Lx86 enabled RHEL 4, RHEL 9 and SLES 10 Linux, ready for your remote access. IBM PowerVM Lx86 supports the installation and running of most 32-bit x86 Linux applications on any System p model with POWER5™ or later technology. It creates an x86 Linux application environment running on POWER processor-based systems by dynamically translating x86 instructions to Power Architecture instructions. This feature can help you expand your addressable market to Linux on POWER servers at minimal to no cost by allowing you to run your existing x86 Linux applications in a POWER environment. For more information, see http://ibm.com/systems/p/linux/systempave.html, or send an e-mail to LoP@us.ibm.com.[Read More]
Important-- During the AIX 6 Open Beta trial, the System Workload Partitions (WPARs) are not automatically enabled. The automatic WPAR creation feature will be only available later this year when AIX 6 will be released officially.
AIX 6 open beta -- IBM is offering access to a prerelease version of AIX 6 during the no-charge open beta. AIX 6 provides support for the advanced features of the new IBM POWER6 systems and will include significant new capabilities for virtualization, security, continuous availability features and manageability. AIX 6 is fully binary compatible with AIX 5L. For more information on AIX 6 and the open beta program see: AIX6 Open Beta - Early Programs
Now IBM Business Partners can try the AIX 6 open beta preinstalled and ready to use in VLP. With this beta offering, you will receive easy, no-cost access to an AIX 6 image to develop, test or demonstrate your solutions.[Read More]
THE VLP IS MOVING!
The Virtual Loaner Program website and systems will be unavailable from 12:01AM CDT (GMT-06:00) on Friday, July 13, 2007 through 12:01 AM CDT (GMT-06:00) on Tuesday, July 17, 2007 as we move all VLP systems to a new Data Center. Please plan your work accordingly. We apologize in advance for any inconvenience this extended outage may cause, but it is necessary as we continue to grow the VLP. We do not anticipate any major issues during the move -- all VLP systems will simply be shutdown, moved to the new location, and then restarted. Any active reservations that span the move period will be active and available again on Tuesday. If your reservation is scheduled to end during the outage period, it will be removed during the outage. We recommend that you save or backup any critical information on your active VLP reserved systems to a non-VLP repository prior to the move. If you have any concerns or questions, please contact us using the "VLP Support" tab on your reservation page at---> www.ibm.com/systems/vlp
Thank you for your continued interest, usage, and support of the VLP.[Read More]
Jwestern 110000974Y 181 Visits
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 service where you can request containers like they do 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 Ubuntu 14.10 or higher operating system under Select an image.
Once the reservation is available, the next step will be to determine if docker is installed and running.
$ sudo docker info
$ sudo dpkg -l docker.io
If docker is not already installed, you will need to install it.
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 you will not need to add in the ftp.unicamp.br repository.
To check the Docker version installed, issue the command
$ sudo docker version
Client version: 1.4.1-dev
Client API version: 1.17
Go version (client): gccgo (GCC) 5.0.0 20150118 (experimental)
Git commit (client): 7294f26
OS/Arch (client): linux/ppc64le
Server version: 1.4.1-dev
Server API version: 1.17
Go version (server): gccgo (GCC) 5.0.0 20150118 (experimental)
Git commit (server): 7294f26
Installing docker creates a local private network. 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
docker0 Link encap:Ethernet HWaddr 56:84:7a:fe:97:99
eth0 Link encap:Ethernet HWaddr 52:54:00:8c:6a:18
Create initial 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 | docker import - ubuntucore-ppc64le:14.10
$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
registry latest e1aa9e60dcd3 2 weeks ago 576.5 MB
ubuntucore-ppc64le 14.10 37d0bddf58b7 6 weeks ago 211.5 MB
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 /bin/bash
NOTE: flags -i interactive -t allocate pseudo tty
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 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
RUN sudo apt-get update && apt-get install -y mongodb-server
RUN 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
Step 3 : RUN echo 'deb http://ports.ubuntu.com/ubuntu-ports/ utopic-updates universe' | tee /etc/apt/sources.list.d/ubuntu-utopic-updates.list
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 6 : EXPOSE 27017
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
Container Images can be tagged with a label to help identify it. Tags are typically used to specify versioning.
$ sudo docker tag 37d0bddf58b7 ubuntucore-ppc64le:latest
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 an image
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