Power Development Platform (PDP)
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
beckett 060000JRNX Marcações:  isv world 7 power7 partner power vlp systems 2 Comentários 6.866 Visualizações
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.
Jwestern 110000974Y 5.443 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 firstname.lastname@example.org
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 Marcações:  chat blog vlp announcements 3 Comentários 5.367 Visualizações
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]
The Virtual Loaner Program now offers the GA level of AIX 7.1 on POWER7, POWER6 and POWER5 systems. Try out the latest release of AIX at www.ibm.com/systems/vlp
Jwestern 110000974Y Marcações:  local colloborate grow innovation global video onsite centers ibm business 4.690 Visualizações
Would you like to have one-to-one technical assistance from IBM? The IBM Innovation Centers can help. This video gives an overview of the IBM Innovation Centers and how they can help you grow your business.
IBM Innovation Centers -Collaborate today. Innovate for tomorrow.
IBM Virtual Loaner Program Was Cloud before the CloudWith all the attention on cloud computing these days—including the recent architectural metaphors for private cloud solutions—you might be surprised to learn that IBM has been a cloud services provider since 2004. Through IBM’s Virtual Loaner Program (VLP), IBM’s PartnerWorld members can get access to IBM i, AIX, and Linux on POWER, running their very own instance with virtually total control.
Read the whole article - http://systeminetwork.com/article/ibm-virtual-loaner-program-was-cloud-cloud?ref=nf
IBM AIX 5.2 Workload Partitions for AIX 7
Workload partitions (WPARs) are virtualized operating system environments within a single instance of the AIX® operating system. WPARs secure and isolate the environment for the processes and signals that are used by enterprise applications.
Applications running in an AIX 5.2 WPAR use AIX 5.2 commands and libraries. If you have applications that have not been certified on newer versions of AIX, the AIX 5.2 commands and libraries provides a way to run them in an AIX 5.2 environment on top of AIX 7.1. Such a setup allows running those applications on currently available hardware that might not support the use of AIX 5.2 as the base operating system. The AIX 5.2 WPARs are also referred to as versioned WPARs. A versioned WPAR is always a system WPAR, and is not shared. Versioned WPARs own writable /opt and /usr file systems.
Quick how to:
To Create a versioned WPAR on the VLP, make an AIX 7 Open Beta Reservation on Power 7.
After the reservation is active, from the My Reservations page, select that reservation.
Under the Reservation(s) Information section, under the Select a reservation action drop down, choose "Add Versioned WPAR".
A new Versioned WPAR will be created on your AIX 7 system. Once completed, go back to the Reservation info page to see the IP address and the root password for the Versioned WPAR.
You can now ssh to the Versioned WPAR from yor VLP lpar or from the SSH Gateway using your normal VLP user ID and password.
ssh <user id>@<wpar IP address>
You can then "su -" to root for full access to the Version Wpar.
From the AIX 7 host, use the "lswpar" and the "lswpar -L" to see more information about your versioned wpar.
For more details on IBM AIX 5.2 Workload Partitions for AIX 7go here:
The IT landscape is evolving rapidly. Today, IT projects are a key part of business performance. IBM POWER7 can help IT deliver services faster, with higher quality and with superior economics. Learn why "Power is performance redefined."
An historic shift is underway of clients migrating from Sun and HP UNIX® systems to IBM Power Systems™. Over the last four and a half years alone, more than 2,600 businesses have migrated their competitive UNIX systems to Power. With the introduction of POWER7®, that pace has accelerated with over 500 clients migrating in just the 1st half of 2010. In addition, more clients are realizing the benefits of consolidating workloads that have been running on x86 servers onto Power Systems. http://ibm.co/hNgIUN
Jwestern 110000974Y Marcações:  lpm mobility partition aix new powervm live application lam 4.391 Visualizações
Use the VLP to validate your applications as Ready for IBM Power Systems Software. Find out more about this validation program then utilize the VLP to test: