Posts

Kernel Performance Testing on ARM

Image
This post will be talking about , how you can do kernel regression , stress and performance testing on ARM architecture.

Setup: To set up your ARM device , you need an image to get started. I was intending to test the latest compose(Fedora 26 1.4 Beta on Raspberry Pi 3 Model B). Download the file (Workstation raw-xz for armhfp) or any variant that you want to test.

Once the file is download, all you need to do is to get a SD card and write the img in the card.

There are two ways of doing it using "Fedora Media Writer" which can now burn the image for ARM devices. The other way is the old dd , here is how you do it using dd





Once the dd has executed itself successfully , its time to plug in the SD in ARM device and boot it up. Once the ARM device is booted up all you need to do is to
clone the kernel test suite from here


Dependencies and Execution: You will need 2 packages
1.gcc
2.fedora-python

You can install them by executing "sudo dnf install fedora-python gcc" …

[Restrospection] Fedora QA Global Onboarding Call 2017-06-03

Retrospection
We had a Fedora QA onboarding on 2017-06-03 and it was successful the Agenda and the Feedback can be found on this etherpad. People from different countries and regions found the call useful.

Few changes which made things better 1. Using bluejeans was smooth and better than Hangouts.
2. Starting the doodle 2 weeks before the call and giving enough time to vote.
3. Using a bunch of quick links as reference points and then explaining.

Action Items 1. Consistency is the key to success , doing the onboarding call every 2 months will be more engaging. Also , it gives a sense of assurance to the new contributors to simply plug themselves up in one of these calls and start from there even if they miss one , they would still be able to contribute to the release cycle. The proposal is to create a wiki page and link it up to Fedora QA Join where people will benefit from it.

2. Feedback , FAQ ,Quick Links, Logs and recordings should be marked and kept in a wiki page which will const…

Fedora QA Onboarding Call 2017-06-03 1400-1500 UTC

Image
There is a going to be a Fedora QA On Boarding Call 2017-06-03 1400-1500 UTC over blue jeans, while release validation for Fedora Beta 1.3 is underway , this is good time to get started. In this call we will be talking about how you as a contributor can get started with Fedora QA. The agenda can be found on this etherpad .

Hope to see you all!

Test Day DNF 2.0

Tuesday, 2017-05-09, is the DNF 2.0 Test Day! As part of this planned Change for Fedora 26, we need your help to test DNF 2.0!
Why test DNF 2.0? DNF-2 is the upstream DNF version, the only version actively developed. Currently the upstream contains many user requested features, increased compatibility with yum and over 30 bug fixes. To DNF-1 back porting of patches from upstream is difficult and only critical security and usability fixes will be cherry-picked to Fedora.

With DNF 2.0 in places,users can notice usability improvements of DNF like better messages during resolution errors, showing whether package was installed as weak dependency, better handling of obsolete packages, less tracebacks, etc. One command line option and one configuration option changed semantic so DNF could behave differently in some way (these changes are compatible with yum but incompatible with DNF-1)We hope to see whether it’s working well enough and catch any remaining issues.
We need your hel…

[Fedora Classroom] Fedora QA 101 and 102

This post will be summing up what we will be covering as a part of Fedora QA classroom this season. The idea is to understand how to do things the right way and to increase contributors.

The topics covered will be:

1. Working with Fedora
2. Installing on VM(s)
3. Configuring and Installing fedora
4. Fedora Release Cycle
5. Live boot and Fedora Media Writer
6. Setting up accounts
7. Types of testing
8. Finding Test Cases
9. Writing Test Cases for Packages
10. Github
11. Bugzilla
12. Release Validation Testing 13. Update Testing 14. Manual Testing
14.1 Release validation
14.2 Update Testing


The 102 will cover Automated Testing and How to Host your own test days during the release cycle.

To make the workflow smooth , we have made a book which will act as an reference even after the classrooms are over.

https://drive.google.com/file/d/0Bzphf6h7upukTDlrczVEb0l3TmM/view?usp=sharing

Automating Lights with PIR sensor and Arduino on Fedora

Image
This is POC post about how you can start automating lights or a rooms , staircases and much more smartly and then normal switchboards do. The whole point of illuminating a room is to make sure the people who go in stay fine because , entering a dark room for many people is a task not for the chicken heart.

Lets first start with the requirements:
1. Arduino as basic as UNO should be fine
2. A bunch of wires
3. Couple of LED (in case you fry by ignoring the ground )
4. A PIR sensor

Let's jump right in:
1. First of all , you need an editor/IDE . For Arduino there is Arduino IDE , you can grab a free copy of the same from https://www.arduino.cc/
2. Once you grab the files , you can either extract it manually or just let the File manager on your Fedora handle the situation for you.

3.Once that you are done , you need to install the IDE.

Once the Arduino IDE is installed , just go ahead and check for two most important things under Tools in Arduino IDE

Ports : It should point to Arduino …

Rocket on Fedora

Image
This post is a very small example of how you can start creating small web apps with Rocket which extensively uses Rust under the hood. This post will just give an idea about how to get started if you are totally new to rust.

Rocket is a web framework for Rust that makes it simple to write fast web applications without sacrificing flexibility or type safety. All with minimal code. - rocket.rs
Getting started: Start by installing rust nightly on your system or virtual box:


$ curl -sSf https://static.rust-lang.org/rustup.sh | sh -s -- --channel=nightly




Setting up Project and Dependencies:
Setting up the project is easy cas you can go ahead and execute

cargo new hello-rocket --bin
Once the execution is completes , you will have a binary application created with a Cargo.toml file and src dir with main.rs inside it.

For setting up the dependencies you need to update the Cargo.toml file.




Now,it's time to update the source main.rs file with some values to show up when we run the up. In my c…