Power Development Platform (PDP)
beckett 060000JRNX Marcações:  informationweek ibm powersystems webcast watson 3.561 Visualizações
IBM Watson passed its first test on Jeopardy! in February 2011, but the real test will be in applying the underlying systems, data management and analytics technology in business and across different industries. http://bit.ly/hWjaWw
Moderated by Stephen Baker, author of Final Jeopardy: Man vs Machine and the Quest to Know Everything, and featuring a panel of IBM business and research executives, this webcast will delve into the present and future business implications of the DeepQA technology behind Watson. http://bit.ly/hWjaWw
- Overview of IBM Watson, Jeopardy! The IBM Challenge, and DeepQA technology
- Business implications of Watson in the areas of
Industry transformation, including healthcare
- Data management and analytics
- Workload optimized systems
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:
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 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 v126.96.36.199
DB2 Workgroup Server Edition 9.7.3a
WebSphere MQ 188.8.131.52
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 3.330 Visualizações
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
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.
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!
Please be advised that a planned outage is scheduled for the IBM Virtual Loaner Program website and reserved systems on Wednesday, April 21, 2010, from Noon CST until 6 pm CST. We will be upgrading the hosting environments for these systems as we prepare for exciting new offerings associated with the General Availability of the products and updates announce on April 13th, 2010. Please be aware that the reserved systems will be restarted during this process, and make appropriate plans. A normal system shutdown will be attempted first on all systems, but if that does not shut down a system, then a force power off will be used to shut down the system. The systems will be restarted after the upgrades are complete. We apologize for the inconvenience.
Virtual Loaner Program Administration
Follow us on Twitter at http://twitter.com/ibmvlp
The AIX 7 Open Beta is now available on the Virtual Loaner Program.
When creating a new reservation select the AIX 7 Open Beta.
Welcome to the open beta for IBM’s premier UNIX operating system, AIX 7. AIX 7 is binary compatible with previous releases of AIX including AIX 6, 5.3, 5.2 and 5.1. AIX 7 extends the leadership features of AIX to include exciting new capabilities for vertical scalability, virtualization and manageability.
The open beta for AIX 7 is intended to give our clients, independent
software vendors and business partners the opportunity to gain early
experience with this new release of AIX prior to general availability.
This open beta can be run on any Power Systems, IBM System p or eServer
pSeries system that is based on POWER4, PPC970, POWER5, POWER6, or
For more AIX 7 Open Beta Info:
AIX 7 Open Beta Forum
The Virtual Loaner Program now offers ISVs the ability to instantly connect to VLP support staff using the Live Help Chat function. This feature is a great addition to the existing email based support and will help users get answers to their questions or problems related to VLP.
VLP Live Chat is accessible from all VLP pages once users log on with their PartnerWorld Id. Our staff will be available 17x5 (2AM CDT to 7PM CDT, M-F) and support English only at this point. The page UI is updated automatically to reflect the Chat as unavailable during off hours in which case users can submit their question through the VLP support tab just as before.
In addition, this Chat client is connected to the Virtual Innovation Center (VIC) support team so users can receive platform (HW/SW) support from the same Chat client.
As a reminder, the VLP team provides support for issues related to VLP such as creating a system reservation, connecting to the system, or any program related questions. The VIC team provides technical support for IBM platforms such as installing IBM Middleware or configuring an OS. When initiating a Chat from any VLP page, the user can select VLP or VIC support (with examples to help decide). And the VLP and VIC teams can pass Chat sessions back and forth in case the user needs to be redirected
Active Memory Expansion now available on VLP.
Find out how to use AME from the VLP user guide - http://cot.ag/byaXp6
Active Memory Expansion is an innovative POWER7 technology that allows the effective maximum memory capacity to be up to 100% larger than the true physical memory maximum for AIX 6.1 partitions.
Active Memory Expansion relies on compression of in-memory data to increase the amount of data that can be placed into memory and thus expand the effective memory capacity of a POWER7 system. The in-memory data compression is managed by the system, and this compression is transparent to applications and users.
Active Memory Expansion is configurable on a per-logical partition (LPAR) basis. Thus, Active Memory Expansion can be selectively enabled for one or more LPAR's on a system.
When Active Memory Expansion is enabled for a LPAR, the operating system will compress a portion of the LPAR's memory and leave the remaining portion of memory uncompressed. This results in memory effectively being broken up into two pools - a compressed pool and an uncompressed pool. The operating system will dynamically vary the amount of memory that is compressed based on the workload and the configuration of the LPAR.
Because Active Memory Expansion relies on memory compression, some additional CPU utilization will be consumed when Active Memory Expansion is in-use. The amount of additional CPU utilization needed for Active Memory Expansion will vary based on the workload and the level of memory expansion being used.
More info on DeveloperWorks wiki:
When you are using VLP, you may be tempted to partition your /dev/sdb disk. After all, you've ran a few commands on your reserved system and it looks like you have an extra disk:
172_29_136_133:~ # sfdisk -s
<code>172_29_136_133:~ # df
In this case what you really have is two paths to a single disk. If you partition the second disk /dev/sdb, you will wipe out /dev/sda. This will destroy the root filesystem, a bad thing to do.
As VLP has evolved, we have improved the infrastructure to make it more reliable, but those changes did not keep in synch with the operating systems that we host. So, multipath IO is not enabled in some operating systems. The best course of action in VLP in general is to use the system but do not attempt to alter hardware configuration of the system that you have reserved. We give each user access to root with the understanding that users will use root carefully. But, in this case, even careful Linux root users could get themselves into trouble without this warning about multipath IO.
Be safe! As always, your questions and comments are appreciated.[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 Virtual Loaner Program new offering - IBM i 7.1 early program. Try out the latest IBM i now!
Details about the VLP IBM i 7.1 Early Program
- VLP will offer i 7.1 Beta level code on POWER6, and Beta level i 7.1 will also be available on POWER7 after April 23rd.
- Reservations can be made for up to 21 days duration, 2 CPU / 4 GB RAM / 100 GB of Storage
- VLP will offer new beta images until a GA level image is available, approximately 30 days after GA of IBM i 7.1
- Once the GA image is available, no NEW Beta images will be allowed, but saved Beta images can be restored for 30 days to allow information to be moved from the image to a GA level image.
- A beta image cannot be upgraded to a GA level image.
- VLP will dispose of all IBM i 7.1 Beta saved images 30 days after GA level images are available in the VLP.
- After the 30 day post GA availability period, the beta promo code will be removed to prevent restore of saved images
Please contact Bill Schulz at firstname.lastname@example.org for more details