Joshua Powers (powersj)

About Me

I work on the Canonical Server team as the QA engineer. I swap my time between the cloud-init and curtin development team where I work on the testing and quality of those projects and the Server team where I work on bug triage, SRUs, git-ubuntu, and general distribution test efforts.

I have an MSc. in Computer Science from Georgia Institute of Technology where I did work in artificial intelligence and data science and I completed my undergraduate work at the Colorado State University in Economics and Computer Science.

Before joining Canonical in 2016, I spent 9 years at HP, where I lead a team developing a small Debian derivative, enabled and tested Linux I/O (network, SAS, fibre channel, and infiniband) on x86_64 and IA64 based-servers, and completed network performance work on scale-up x86_64 systems. My experience with Linux began in high school when I helped to convert my school systems to an all Linux-based system.

Contributions

Bugs Work and Meetings

• Complete daily triage of the Ubuntu Server related package defects; I have developed a set of response templates based on previous responses used by the server team

• Rotate as chair of the weekly Ubuntu Server Meeting

• Write each week's server team development summary

Ubuntu Server ISO Testing

• I am responsible for the automated Ubuntu Server ISO testing for amd64, i386, powerpc, and ppc64el
• I maintain the automated ISO tests that we use to gate the promotion of new daily ISOs, testing before any new release or point release, report results to the ISO tracker, monitor ISO size, and report defects as necessary

Packaging

• Related Packages + various MIR and seed changes

• Investigate dep8 status on server packages

• Setting up automated proposed testing of server packages (in progress)
• Archive rebuild of supported releases for FTBFS (in progress)

Testing

• Make the Ubuntu Server Jenkins is now publicly available and add additional slaves: an s390x LPAR, bare metal ppc64el Power8, an arm64 development board, and Xeon-based amd64 system. Also have an i386 virtual machine to be able to simulate an i386 environment

• All jobs, tests, and deployment scripts are kept in a public repo organized for re-use

• Working to start getting individual server-specific package level testing. Worked with cpaelzer to get virtualization and live-migration related tests added to our infrastructure.

cloud-init

• Design and impliment CI and integration test suite with KVM and LXD, working on cloud-based testing
• Participating in daily new bug responses and triage

Future Goals

• More packaging work to expand my experience with different types of source packages and learn additional cases for packaging
• Continue to share knowledge learned via blog posts (e.g. commands, processes, etc.)
• Get more automated tests (via dep8) in place for specific packages with high importance and impact
• Help users to restore system when they reach specific error messages. For example, if a package is badly misconfigured and should be reconfigured before doing anything else, help them do that. If a bug gets reported enough, even if it ends up due to user error, have a set of commands ready to go to recover from that. Looking at the community forums or other internet forums for the most often visited results may assist with this. Adding additional bug patterns would be good here.
• Availability of some features is not always clear. The best example I can give is the availability of the HWE kernels. I can see how many enterprise customers might have more interest in this, however, providing a better list to new users, or reminders to get those getting interested for the first time a list of relatively new things or a list of “Have you tried these cool things in Ubuntu yet?”. ZFS and LXD are other examples.
• There is a lot of institutional knowledge as well as decision tree paths to making the best decision sometimes. There are many different wiki pages for knowing how to get started with packaging, some of it with details from long-ago supported releases that is irrelevant now and some that has expired content. For new users, this can be frustrating. As we continue to grow new users do not want to push them away or turn them off with bad documents.

Testimonials

Note: If you have anything nice to say about this person, please do add it below along with @ SIG @ (no spaces). The @ SIG @ command will sign your name and date/time it after you "Save Changes".