I recently got access to the Minicloud, a Free OpenPower Cloud hosted by Unicamp, one of the most prominent universities in Brazil. This cloud is a good way to ensure that your application provides good support for the Power architecture.
Having access to this cloud, I can help ensure that some of the projects I am interested about can be ran and supported on this architecture. Additionally, it offers me a Power environment to test the messaging-related packages I maintain on Fedora and CentOS – entirely on my free time.
To start with this cloud, I decided to go big and deploy Maestro there. Having only 4Gb, it means that I need to adjust very well the resources of my VMs so that I can maximize the usability of the cloud environment. I will write some posts about this.
The other project that I am interested in playing with in the Minicloud is Paho C, the MQTT client from Eclipse Foundation. As the Fedora maintainer for the package, having access to this environment means that I have a personal environment where I can ensure the quality of the packages.
Fedora is a rock-solid stable, with a good selection of official and non-official packages. Just like many other distros, it still gives you the flexibility to adjust the system to your workflow. Here’s my basic steps to adjust it to my needs:
Here’s a tip if you are using Fedora and trying to use one of the Google Sanitizers with clang and is having problems doing so. One of the common problems is not being able to find libclang_rt.asan-x86_64.a:
/usr/bin/ld:cannot find/usr/bin/../lib64/clang/3.8.0/lib/linux/libclang_rt.asan-x86_64.a:No such file ordirectory
This can be resolved by simply installing the compiler-rt package:
There’s, probably, a better way to do this. Per documentation, it should be possible to set it up permanently by creating a file on /etc/X11/xorg.conf.d however I did not manage to create a file that works so far.
I have created Fedora packages for OpenPHT, a community-driven fork of the Plex Home Theater client. The packages can be download from this link (I plan to propose adding the RPM specs to the main project, but before doing so, I would like to make sure they are working as expected).
The build instructions, for those interested in reviewing or rebuilding the package can be found in this gist or in the RPM spec file.
Just sharing some messaging tools I have been working with recently.
The first one is this performance test tool: msg-perf-tool. There’s no secret here: you run the tool and it does its best to bring your messaging system to its knees (though this may not be the correct way how to test it … check the testing tips on the Github page). For now it supports only AMQP, but Stomp and MQTT support is on the way. You can find rpms for RHEL/Centos (6 and 7) and Fedora (22, 23 and 24) for i686 and x86_64 on my Copr profile here.
The second one is a web page that can display the performance data stored on an ElasticSearch database and present it in a beautiful way. I call it messaging performance center. Here’s how it looks like:
Some bits are still in progress, but it’s functional.
Lastly, there’s litestomp. A C implementation of the Simple (or Streaming) Text Oriented Messaging Protocol. It was built on top of what-seems-to-be the now defunct libstomp project. There’s a couple of bugfixes, a simpler and higher level API for ease of use. Still a work in progress, but you can download the current rpms for RHEL/Centos (6 and 7) and Fedora (22, 23 and 24) for i686 and x86_64 from my Copr project page on this link.
There seem to a be problem with Parallels Tools 10.3 and recent versions of the Linux kernel (4.2, at least, which is used by recent versions of Fedora 22 and Fedora 23, for example). During the installation tools, the installer fails to compile one of the modules. That can lead to problems booting up your virtual machine.
In Fedora, in order to avoid this problem, you can just add the following line to /etc/dnf/dnf.conf file:
After Parallels release an update, you just remove the line, update the system, and it should be fine. As a final reminder, you should always generate a snapshot before upgrading the system.
I have Late 2013 MacBook Pro Retina (MacBookPro11,1 (13″) (A1502)) and I wanted to run Fedora 22 on it. These are just some tips to solve some common problems about running Linux on it:
1. Configure wireless:
First install kernel-devel:
dnf install kernel-devel-y
The follow the steps here (basically: install rpmfusion, then broadcom-wl, then run sudo akmods).
2. How do I switch the Command key and Control key on a MacBook Pro? Check here.
3. Adjust HiDPI settings. If you are running Cinnamon, you can just adjust it in the fonts settings panel. If you are not, you may need to export GDK_SCALE for some applications. You can find additional details in this link.
4. Touch pad: enable the right click on the right bottom area of the touch pad.