At Impact 2014, Doug Balog and Mark Shuttleworth provided a glimpse of the work completed on POWER8 systems with Ubuntu 14.04 from Canonical.
In a Keynote presentation available on Youtube, Mark Shuttleworth's team does a demo of deploying 8 KVM guests - starting from scratch, installing the OS on each guest, the application software, configuring, running, inter-connecting, and ready for work. JuJu's and Charms are actually pretty slick. Something good to learn in the coming days.
On the Youtube video, fast forward to around 39:45. The demo itself starts around 42:00. The full presentation wraps up around 49:00. Good use of your time!
One of the classic quotes from Mark was that Canonical ported over 40,000 of the packages to Power8 and Little Endian mode over a period of about 5 months. In the vast majority of cases, re-compile and run was easy to accomplish and demonstrate.
Modified on by jscheel
By Jeff Scheel
As you likely have heard, Arvind Krishna, IBM General Manager for Development and Manufacturing in the IBM Systems & Technology Group, announced that Power Systems would be supporting KVM. This is an exciting announcement for numerous reasons that I'll defer for another posting. For this blog entry, I thought I'd do some question/answer session based on common questions I've been asked in the past couple weeks. However, before I do so, I need to remind you that these are our current thoughts at this time: things may change.
Q: When will KVM be available on Power?
A: The outlook for general availability is next year. However, IBM has already started releasing patches to various KVM communities to support the POWER platform.
Q: On what systems does IBM intend to support KVM?
A: IBM intends to initially support KVM on a limited set of models, targeted at the entry end of the system servers. This strategy supports IBM's efforts to capture the largest growing market, x86 Linux servers in the 2-socket and smaller space.
Q: How does IBM plan to position KVM against PowerVM?
A: IBM remains committed to the PowerVM being the premier enterprise virtualization software in the industry. With KVM on Power, IBM will be targeting x86 customers on entry servers but will offer both KVM and PowerVM to meet the varying virtualization needs PowerLinux customers. However, KVM virtualization technology represents an opportunity to simplify customer's virtualization infrastructure with a single hypervisor and management software across multiple platforms.
Q: What Linux versions from Red Hat and SUSE will provide KVM hosts support on Power?
A: The decision to provide KVM on PowerLinux will be made by Red Hat and SUSE. IBM will be working with them in the months to come and would welcome their support.
Q: What management and cloud software will support KVM on Power?
A: For KVM node management, IBM intends to work with multiple vendors, including Red Hat and SUSE to certify KVM on Power into their system management software offerings. Additionally, IBM plans to contribute any patches necessary to OpenStack to extend the KVM driver to Power. Using this foundation, additional IBM and third-party software should provide a diverse set of management software.
Q: What will software providers need to do to support KVM on Power?
A: Most software provides have become comfortable with some form of virtualization such as PowerVM, VMWare, and KVM. Just like with applications on Linux, software providers should find that applications in the KVM environment behave similarly on x86 and Power platforms. As such, each vendor should understand any challenge KVM on Power would provide.
Q: What operating systems will be supported as guests in KVM on Power?
A: Given that KVM is initially targetted to be released on Linux-only servers, only Linux is planned at this time. IBM plans to certify the latest updates of RHEL 6 and SLES 11 as KVM guests.
Q: How will KVM run on the Power Systems?
A: The design goal of KVM on Power is to be just another hardware platform supporting KVM. As such, the KVM on Power will be true to the KVM design point of a KVM host image that supports one or more guests. PowerVM constructs such as the HMC, IVM, and VIOS will not exist in KVM. Management and virtualization will occur through the KVM host image.
Q: Will KVM run in a PowerVM logical partition (LPAR)?
A: While KVM supports a user-mode virtualization that can run on any Linux operating system, KVM on Power is being developed to run natively on the system, not nested in PowerVM. This is done to enable KVM to run optimally using the POWER processor Hypervisor Mode. As such, the system will make a decision very early in the boot process to run KVM or PowerVM. This is envisioned as a selectable option managed by the Service Processor (FSP)?
Q: Will it be possible to migrate from KVM on Power to PowerVM or vice versa?
A: While the virtualization mode will be selectable on systems, the process of migrating from KVM and PowerVM will require additional steps such that frequent migrations will be unlikely. However, in the case where a customer wishes to upgrade to PowerVM to acquire advanced virtualization capabilities, this migration should be supported. Steps to backup and restore the VM image will be required when migrating in either direction.
Q: Will AIX or IBM I run in KVM on Power?
A: Given that KVM initially runs on Linux-only platforms, support for non-Linux operatings systems has not been planned at this time.
Q: Will Windows run in KVM on Power?
A: Windows does not run on Power Systems. As such, supporting it in a KVM guest VM will not work.
Hopefully, these questions were helpful to folks. As usual, follow-up questions/comments appreciated.
Modified on by Bill_Buros
By: Steve Dobbelstein.
On February 22, 2013, IBM® published a new SPECjEnterprise®2010
result on a two socket system. The result was achieved on the new IBM PowerLinux™ 7R2
system using IBM WebSphere® Application Server v8.5 and IBM DB2® 10.1 running on Red Hat® Enterprise Linux® release 6.4. The Linux Technology Center (LTC) team, the WebSphere team, the Java team, and the DB2 team all worked together to analyze and tune the performance of the hardware and software to produce the record-breaking result. A lot of the tuning and analysis has been captured as best practices in a new article, SPECjEnterprise: A performance case study
From the SPEC.org web site, "The SPECjEnterprise2010 benchmark is a full system benchmark which allows performance measurement and characterization of Java EE 5.0 servers and supporting infrastructure such as JVM, Database, CPU, disk and servers." The article contains many general use best practices that can be used on any system. If you are running a workload similar to SPECjEnterprise, the article may be especially helpful.
By: Maynard Johnson and Beth Taylor.
Finding performance bottlenecks in applications that you develop can be a daunting task. But with the right tools and a little guidance, it's easier than you might think. OProfile is a performance analysis tool set for Linux systems. A new collection of topics has been published in the Linux for IBM Systems Information Center to help application developers get started with OProfile on Power Systems™ servers running Linux. Getting started with OProfile on PowerLinux
introduces the new operf
profiler available with OProfile 0.9.8. The topics also give helpful usage tips for OProfile's "legacy" profiling tool, opcontrol
. In most cases, you'll find that operf
is a much simpler alternative to opcontrol
and other profilers available.
The information center topic collection includes the simplest path for installing and setting up OProfile, taking advantage of IBM® Advance Toolchain for PowerLinux™. It also includes basic scenarios for dealing with problems such as lost samples caused by kernel throttling, and buffer overflow.
The SourceForge OProfile project web site
is another good source for getting help and information. Resources there include FAQs, an OProfile user manual, mailing list archives, and the IRC channel. As lead maintainer for the OProfile open source software project, I (Maynard Johnson) am watching the mailing list and IRC channel to make sure that your OProfile questions are being answered. I also review community-submitted patches and handle bug reports. So please be sure to give OProfile a try and keep in touch on the PowerLinux Community message board
with any questions that you have.
Modified on by jerberstark
By: Breno Leitão.
This tutorial explains how to create a RAID device on PowerLinux machines using an array of disks. This step by step tutorial includes identifying the disks, formatting them, combining them in a RAID array, creating a partition and, finally, creating a file system on this partition.
The PowerLinux machines support a RAID (Redundant Array of Independent Disks) card. A RAID card is a device that combines a set of physical disks into a logical unit to achieve a better performance and more data redundancy. A RAID array could also be created by the operating system (known as Software-based RAID), and it consumes some CPU cycles from the machine to manage and control the disk array. On the other side, a RAID card, as the one embedded on PowerLinux machines, offers a Hardware-based RAID, meaning that the operations on the disk array are offloaded to the RAID card, not utilizing CPU cycles managing the disks, thus, being more efficient than Software-based RAID solutions.
The RAID adapters on PowerLinux machines support several different RAID protection levels. Depending of the protection level, you might have different benefits, as potentially achieving a higher data transfer, a smaller latency and data redundancy when compared to a single big disk. You might also want to combine these benefits all together in the same disk array, which is also a possible depending on the RAID protection level.
Using RAID is usually a trade-off between disk space and redundancy, so, depending on the RAID protection level, part of the disk space is used to save redundant data, thus, part of the disk space is not available for general usage. The real space available to the users varies from 50% to 100% of the total disk space.
The RAID protection levels supported by most PowerLinux RAID adapters are:
RAID 0: On this configuration, a block of data is striped in different disks on the array, so, the read/write operations on the disks could happen in parallel on the disks in the array. On this configuration, there is no fault tolerance i.e., if a disk fail, the whole data is lost. This level usually improves the data throughput.
Requires at least 1 disk. In a single disk RAID 0 configuration, no striping occurs.
RAID 1: On this level, the data is written at the same time on 2 disks. As both disks have the same data, a read operation will occur on the disks that has the smaller latency. On this case, if one disk fails, the whole data will continue be preserved on the other disk. Once the other disk is replaced, the RAID would be reconstructed. As expected, this level improves the data redundancy.
Requires at least 2 disks. Note: The PowerLinux RAID adapters refer to this RAID level as RAID 10.
RAID 5: On this level, the data and parity bits are spread all across the disks. If one disk fails, then all the data is still available, once the original data could be reconstructed using parity data from the other disks. If more than one disk fails, then the data will be corrupted. (If a disks fail happen, the operations may happen in a slower fashion, since the data being accessed is on the lost disk, then the data will need to be reconstructed.). One disk's worth of capacity is consumed for redundancy information for the array.
Requires at least 3 disks.
RAID 6: The same as RAID 5, but up to 2 disk can fail, and the data will still be preserved. Two disk's worth of capacity is consumed for redundancy information for the array.
Requires at least 4 disks.
RAID 10: This level combines the best concepts of RAID 1 and RAID 0. On RAID 10, the data is striped on a set of hard disks, and these hard disks are mirror to another set of hard disks. So, you have a very good throughput and also a data redundancy.
Requires at least 2 disks for mirroring and striping. In a two disk RAID 10 configuration, no striping occurs.
RAID card on PowerLinux
The PowerLinux machines come with an embedded RAID controller that supports up to 6 SAS or SDD disks and RAID levels 0, 5, 6 and 10 on machines 7R1
. RAID 1 is also supported as a subset of RAID 10, since the RAID controller allows you do create a RAID 10 with just two disks as part of the array. In this case, since there is no enough disk to mirror and strip, the data just gets mirrored on both disk, instead of striped, which is what a RAID 1 does. So, the cards also supports, in a different form, a RAID 1.
On Linux, the device is listed as a PCI-E device named "IBM Obsidian-E PCI-E SCSI controller ".
In order to manage this controller, there is a set of tools on the packaged called iprutils that helps the system administrator to create, configure and delete disks and arrays using the RAID controller.
The iprutils package provides the iprconfig application. The iprconfig is the tool responsible for configuring the RAID devices on your machine, and will be the tool that will be covered below.
The device driver
The device driver for the PowerLinux RAID controller is named ipr.ko. It's currently part of the Linux kernel and comes with all the supported Linux Distros for PowerLinux. So, it's recommended to always use the last supported kernel version from the distro in order to take the best from you PowerLinux machine.
Using iprconfig tool
The iprconfig tool is a very easy application to use. It's a text-based (TUI) application that helps you to list and configure the RAID controller and the disks on your system. iprconfig also allows you to check the controller log, and upgrade the card firmware. An example of the iprconfig screen could be seen at Figure 1.
Now on, a step-by-step tutorial will show how to format a set of disks, combine them together in a RAID mode, create a partition over this array and, then, create a file system over this partition. This is an easy process that might take less than 30 minutes to be accomplished. For this tutorial, we are going to create a RAID 5 device, meaning that the array will have the data mirrored and striped over the disks arrays.
You can use iprconfig just as a command line option, in this case, you need to pass the parameters you want in the command line. For example, in order to see what are the RAID levels supported on a controller (sg5
), the following command should be used:
# iprconfig -c query-supported-raid-levels sg5
0 5 10 6
Formatting a disk in RAID mode.
In order to use a disk as part of a disk array, it needs to be formatted specifically for being part of RAID, also known as, advanced function
mode. If the disks is not formatted properly, you can not add it to a RAID array. In order to format a disk in advanced function mode, the following steps should be followed:
Launch the iprconfig tool on a console.
Select the menu Work with disk array (as shown in Figure 1)
In order to do it, press 2 and then enter.
Select Format device for RAID function
In order to do it, press 5 and then enter.
Then select the disks you want to format (all of those that are going to take part of the disk array) and continue. (As shown in figure 2)
In order to select the disks, you must use the up/down arrows, and press 1 to select the devices you want to select.
Wait until the disks are formatted as shown in Figure 3. (It takes some minutes until the disks are formatted.)
Figure 3: Disks being formatted
Creating an RAID disk array
As explained above, in order to add a disk into the RAID array, the disk need to be formatted in RAID mode. Once the disks are formatted in RAID mode, they can be available to be added to a disk array, and the RAID device could be created. You might want to create as many RAID devices you want, and give them a set of disks. Let' s go through the process of creating an array device. It is recommended when creating a RAID array to format the devices for RAID as described in the previous step, then create the disk array following the steps below without exiting the iprconfig
tool. Exiting the tool will result in the loss of knowledge that the disks have just been zeroed and it will take longer for the array to initialize.
Launch the iprconfig tool.
Select Work with disk arrays, as shown in Figure 1.
Select Create a disk array.
Select the controller you want (You might have just one controller), as shown in Figure 4.
Select the disk that will be part of the array, as shown in Figure 5
Press '1' over the disks you want to select.
Select the RAID type, as shown in Figure 6.
Go into the Protect Level and press 'c' to change the RAID level.
Select the disks that will take part of that disk array
It may take a while to have the array created.
Figure 4: Selecting the RAID controller
Figure 6: Select the RAID type
Start using the RAID array
Once you had the RAID array created, it becomes a block device as any other block device on the system. You can create a partition on the device, make a file system on it, and start using. The next steps will help you to create a partition and a file system on the array partition. On this tutorial, I will create just one partition using the whole array and format it using EXT4 file system, as shown below:
Figure 8: Creating a EXT4 file system on the partition over the RAID device
Once the file system is created in the partition, you can use this partition as a traditional file system, i.e, mount it on a directory and start using it. All the RAID operation, as managing, striping, checksumming or mirroring the data will be offloaded to the RAID card, and happen transparently.
By: Beth Taylor and Walt Madden.
Several previous blog posts have told of the
advantages of IBM®
Advance Toolchain for PowerLinux for application performance analysis on IBM
servers. Likewise, you've heard about
IBM Software Development Kit for PowerLinux™, which combines C/C++ source
development with the Advance Toolchain and classic Linux debugging and
performance analysis tools like OProfile.
Recently, the IBM InfoSphere Streams development
team has had the positive experience to give credit to these claims with the development and release of their latest IBM InfoSphere Streams v3.0 product.
InfoSphere Streams saw direct performance
gains from using the Advance Toolchain GCC compiler and Power-optimized libraries. Product code changes made as a result of SDK
for PowerLinux application analysis further improved performance. In addition, using Advance Toolchain v5 and the IBM SDK for PowerLinux prompted the InfoSphere Streams team to employ an
alternative string implementation, vstring, which optimizes performance for operations on strings less than 16 bytes.
While results for other products will certainly
vary, the IBM InfoSphere Streams development team has achieved excellent performance gains for their latest product update as a result of using IBM Advance Toolchain and IBM SDK for
PowerLinux. During the development cycle, the InfoSphere Streams V3.0 product
saw improved performance gains of between
26% and 166% compared to the previous product, depending on the internal workloads that were tested. Customers developing new InfoSphere Streams products on Power systems are encouraged to follow the best practice recommendations.
It’s time to check out how you can rev up the
performance of your PowerLinux applications using IBM Advance Toolchain for PowerLinux and IBM SDK for PowerLinux.
By: Rafael Folco.
Practical experiences with setting up a cluster
From these experiences, I created a wiki page
which describes some hints and tips on setting up a cluster for BigInsights.
The BigInsights product provides for serious hadoop-based processing and is available on the PowerLinux base. If you have questions on taking advantage of BigInsights and hadoop on Power systems, ask a question on the PowerLinux message board
By: Rodrigo Fraxino Araujo.
Many software engineering activities rely on the automated support afforded by tools. In order to maximize their benefits, they are often retrofitted to development environments that enable them to capitalize on facilities provided by compilers, debuggers, and profilers.
In this context, focusing on the integration of a set of mainstream C/C++ development tools (Valgrind, OProfile, Autotools, perf, among others) along with several in-house IBM ones (Advance Toolchain, FDPR, and others), we have used Eclipse as a basis to bring together a SDK comprising the necessary tools to assist in the development and analysis of C/C++ programs for Power Architecture, namely, the IBM® Software Development Kit for PowerLinux™
Two development environments are available:
(i) a native one, to run on Power, and
(ii) a client/server that runs on x86 or Power.
Several technical hurdles we ran into porting such tools into plugins, the workarounds to deal with such issues, and a more detailed description of the available tools and functionalities of the SDK can be found in a paper published on the IEEE portal:
By: Beth Taylor.
look at the Linux Information Center for Installing Linux with the IBM Installation Toolkit for PowerLinux, http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/topic/liaan/powerpack.htm.
IBM Installation Toolkit for PowerLinux version 5.2
Installation Toolkit for PowerLinux speeds up the installation of Linux, and
gives you access to the IBM value-added software necessary to fully use the
capabilities of the Power® platform. You
can use the IBM Installation Toolkit on PowerLinux servers, including IBM
PowerLinux™ and IBM Power Systems™ servers running Linux.
use the IBM Installation Toolkit to:
- Install and configure Linux on a non-virtualized Power Systems server.
- Install and configure Linux on servers with previously-configured
logical partitions (LPARs, also known as virtualized servers).
- Install IBM service and productivity tools
on a new or previously installed Linux system. The IBM service and productivity
tools include dynamic logical partition (DLPAR) utilities.
- Upgrade system firmware level on Power Systems servers.
- Perform diagnostics or maintenance operations on previously installed
- Access documentation resources included with IBM Installation Toolkit.
- Migrate a LAMP server (software stack) and application data from a
System x® to a System p® system.
IBM Installation Toolkit version 5.2:
- Support for Red Hat Enterprise Linux 5.8
- Support for SUSE Linux Enterprise Server 11
- IBM Installation Toolkit Simplified Setup Tool
- IBM Electronic
Service Agent for PowerLinux
have comments on the IBM Installation Toolkit documentation, please drop us a
line here, or use the Send Feedback link from any Linux Information Center
check out the IBM Systems Support. IBM Installation Toolkit for Linux landing
About IBM Software Development Kit for PowerLinux
The IBM® Software Development Kit for PowerLinux is a free, Eclipse-based Integrated Development Environment (IDE). The IBM SDK for PowerLinux integrates C/C++ source development with the IBM Advance Toolchain for PowerLinux and classic Linux debugging and performance analysis tools. The IBM SDK for PowerLinux provides you with an all-in-one solution for developing software on PowerLinux servers, including IBM PowerLinux™ and IBM Power Systems™ servers running Linux. It also provides integration of open source and IBM tools into a single graphical user interface.
IBM SDK for PowerLinux integrates the Eclipse IDE with the IBM Advance Toolchain for PowerLinux. IBM Advance Toolchain for PowerLinux provides the latest tested and supported GNU Compiler Collection (GCC) compiler versions for Power Systems servers, and is packaged with a set of processor-tuned runtime libraries. With IBM Advance Toolchain for PowerLinux, you can build and debug applications. You can also take advantage of the tuning assistant, which helps you choose advanced compiler options to tune your application for Power Systems servers running Linux.
IBM SDK for PowerLinux integrates open source tools such as GNU Compiler Collection (GCC), OProfile, Valgrind, and Autotools. In addition, it integrates the IBM tools Feedback Directed Program Restructuring (FDPR®) and Pthread monitoring tool, which are specifically designed to analyze and exploit Power Systems servers. It includes powerful porting and analytic tools, such as Migration Advisor, Source Code Advisor, and Trace Analyzer.
Be sure to let us know what you think of the IBM SDK for PowerLinux documentation by leaving a comment here, or by using the Send Feedback link from any Linux Information Center page.
By: Jeff Scheel.
Two weeks ago, I blogged about my thoughts after attending Power Technical University in Miami. This week, I bring you my thoughts from our event in Copenhagen, Denmark.
It never ceases to amaze me what I learn at these events. While the topics I presented were identical to the session in Miami two weeks ago, I still learned a bundle from the Power Linux customers who attended in Copenhagen.
Here are my thoughts from this week:
- Again, I took a significant number of business cards to Copenhagen and still ran out before the week was over. Interest in Power Linux was definitely greater than Lyon, France last year!!! Power customers are definitely "thinking Linux". I did my best to help extend this to "Think Power Linux". I believe we see this growth reflected here in our new community where our membership continues to grow. We've past the yearly goal of 150. Can we top 200 before year-end?
- If you remember my blog from Miami, I was surprised to meet a customer who taught me that Storix had a solution for Power Linux. In Copenhagen, I met another Storix customer and had more discussions about mksysb type backups. There's a real need for this solution in the market place. While some open source solutions exist, none yet support Power. Having Storix supporting the platform is great because of their deep heritage with in the UNIX marketplace.
- On the theme of surprising solutions, I found an answer to a frequent question: How do I size my Linux partition? Midrange Performance Group provides a Power Navigator product to perform capacity planning on AIX, Linux, and other proprietary operating systems. As I understand this solution, it can help you migrate a Linux workload from x86 to Power using data from the nmon tool. Give it a look if this is a problem with which you've been grappling. Oh, by the way, did I mention that the Linux Installation Toolkit includes nmon?
- I attended a great presentation on the Linux on Power Best Practices in virtualized environments by Dr. Michael Perzl (email@example.com). He did a terrific job of detailing HA configuratoins for Power Linux and comparing showing the similarities/differences with the AIX equivalents. I've posted a PDF export of his presentation to our community. (Please note, the formatting issues in the PDF are a result of my export, not Michael's presentation.) Feel free to reach out to him as one of our many technical experts.
- Finally, the issues in Europe are the same as the United States: How do we differentiate Power Linux from Intel Linux? How do we "sell" Power Linux within an business that believes Linux is x86 only? If you haven't read my approach to answering these questions, feel free to refer back to my blog about Power Tech U. in Miami.
If I met you in Copenhagen and you joined because of presentation, feel free to comment against this blog and provide feedback. Welcome to our community! Help make us better.
If you just follow along and my postings spur any thoughts or comments, feel free to comment as well. Did I spur any thoughts, comments, or questions?
Well, that's all. Thanks for Thinking Power Linux today.
By: Jeff Scheel.
A couple weeks ago, someone sent me a link from the developerWorks PowerVM forum about installing Debian on a POWER7 box. The post was created by Tux11
(Dennis Schneck) who graciously agreed to create a developerWorks wiki.
Here is the new Debian 6 on Power7 LPAR
wiki. I strongly encourage that if you have interest, if you're running Debian today on POWER, or if you would like to doing so in the future, please help Dennis and the community keep this wiki alive and accurate. I cannot THANK him enough for his efforts in creating this and for his willingness to share!!!
One final comment: if you are already a Debian user on POWER or another platform, I'd love to hear more from you as to your motivations and use case. As the Chief Architect for Power Linux, I'm always looking for feedback from our community. Comments here or individual emails would be greatly appreciated.
About the Advance Toolchain:
The Advance Toolchain provides early and easy access to
libraries and the latest compiler technologies for Linux distributions. Over time, these libraries
and latest compiler technologies are integrated into the shipping
distributions. However, the Advance Toolchain contains the latest
tested and supported GNU Compiler Collection (GCC) compiler versions,
tailored for Power systems, and packaged together with an expanding
set of processor-tuned libraries, allowing you to take advantage of
the latest technology without waiting.
Topics covered in the documentation:
Let us know what you think about the Advance Toolchain information by leaving a comment here, or by using the Send Feedback link from any Linux Information Center page.
By: Jeff Scheel.
I hope you "Think" our Power Linux community is starting to come together. It's taking some time to bring the pieces together, but we're making progress. Since Rome wasn't built in a day, hopefully you'll understand if the Think Power Linux community takes a couple months.
Speaking of Rome and building, did you know that IBM's effort with Power Linux is over 10 years old. Yes, I was one of the original team members focused on putting Linux on the iSeries. That mission grew into the ppc64 kernel and glibc that ultimately became the core of today's shipping RHEL and SLES distributions. During that time, I've held lots of leadership roles, including manager, release architect, and various other IBM-speak titles which won't mean much to most people. I even managed to get one patch accepted into the kernel, quite an accomplishment for an IBM Manager. About 5 years ago, the Linux for Power mission merged into IBM's larger Linux Technology Center where we now work. This move combined our team with teams focused on doing platform independent Linux work as well as enabling IBM's System x and System z platforms -- effectively giving us access to a worldwide extended team of over 400 developers in over 40 countries. It's been lots of working getting this far, but also alot of fun working with a terrific team.
I've been with IBM 20 years. I started working on I/O adapters writing microcode for SCSI bus controller chips. Then, I joined the team which brought logical partitions (LPARs) to the iSeries (formerly AS/400) systems. This code base eventually became the design point for what we now call PowerVM on Power Systems. After getting our LPAR function under control, the next logical step was to add Linux to a partition and despite my doubts about the project, it's turned into quite the opportunity to impact the business. With one exception, a 2 year 'sabbatical" where I worked with the Blue Gene team on their Blue Gene /P product, I've been working with Power Linux.
Today, as the Chief Architect, I wear a variety of different hats. I like to tell folks that "architect equals fireman, traffic cop, politician, salesman, referee, switchboard operator, janitor, or as my colleagues affectionately call me, just a 'basic slug.'" Seriously, my day-to-day role is deciding how we spend our resource and setting technical direction. That means I help decide where the code gets written, but not actually writing the code. It also means that you'll find me filling in around the outside of the projects, giving presentations, answering questions, helping out where I can.
My personal focus this year is on our ecosystem. I'm helping where I can to get the Think Power Linux community off and running. Therefore, you'll find me creating wiki pages like the "Knowledge is Power"
topic, writing blogs like this one, and answering posts to the message board
. If you need help, check out the information in the community and then post to the message board if you can't find the needed information. I'm watching all posts and working to ensure that they get answered. If that doesn't work or if you want a more personal dialogue, feel free to drop me an email at the address in my profile
(see the "General info" tab).
In the spirit of "ecosystem", I'd like to leave you with a couple useful Power Linux links:
Hopefully, you'll find at least one to be worthwhile.
Thanks for taking the time to read our blog. Hopefully, I've put a little more of a virtual "face" behind the name. Look for more posting from other Experts in the coming months.
By: Tulio Magno Quites Machado Filho.
Two new update releases for the 5.0 and 6.0 series are now available. Both of these releases are intended to fix security issues on OpenSSL:
For download links, more information and documentation, please refer to our official documentation page.
Please let us know if you have any questions about this release.
About the IBM Advance Toolchain for PowerLinux
The IBM Advance Toolchain for PowerLinux is a set of open source development tools (compiler, debugger and profiling tools) and runtime libraries that allow users to take leading edge advantage of IBM's latest POWER hardware features on Linux.
For more information about it, visit http://ibm.co/AdvanceToolchain.