HummingBoard, my new toy.

August 14th, 2014

Last month I was gratefully surprised by an email from Germany. Someone  had seen my blog (yay!) and was interested in sending me a Cubox-i or a HummingBoard for free (double yay!).

It was hard to make the call, but I decided to request a HummingBoard, mainly because of the GPIO socket (General Purpose Input-Output). GPIO allows you to connect different electronic components to play with them and do robots and other cool things.

After several months and several hours doing paperwork in Customs, I finally got it. Compared with the Raspberry Pi, the HummingBoard has more RAM  (1GB versus 512MB), and more CPU (2 cores versus 1) and it also includes a SPDIF audio output.

Very grateful with the new toy I already could run Fedora on it. In order to do that, I had to download an image from this GitHub repo. There are also instructions to build the image from scratch and I am going to try that later.

A few days ago, Peter Robinsion mentioned on his blog that the HummingBoard will be one of the primary devices for Fedora ARM on Fedora 21. This basically means, that there will be a lot of testing on this device and I will be part of it for sure.

Fedora has supported the architecture of the HummingBoard (armhfp), for several releases. All the Fedora repositories and some third party ones like RPMFusion have a lot of software that can be easily installed on this device. That is something I noticed that unfortunately is missing on the Raspberry Pi with Pidora.

These are some of the pics I took of the HummingBoard:

Video sobre la FLISOL 2014

April 28th, 2014

The TELAM news agency created this video about the FLISOL in Buenos Aires. If you take a look at it, you can see the impact of Fedora on this event.

Flisol 2014

April 27th, 2014

Yesterday, April 26th, we attended the FLISOL 2014. I am proud to say that Fedora rocked this year!
For the first time, we had our own stand and a lot of people came to discuss and install Fedora.
This year we were able to make more Marketing work (banner,DVDs,shirts) and that showed a very good presence in the event.
I also want to thank two great Fedora contributors (ezq and valentin) who came from their provinces to contribute to this event.

Some pictures of the event:

Fedora Argentina will be attending the FLISOL 2014

April 13th, 2014

On Saturday April 26th from 10 to 18 we will be attending the FLISOL 2014 in UTN Medrano.
This year we will be hosting the following talks:
– Fedora and the community around it
– Virtualization
– Playing with Pidora
Moreover, for the very first time on this event, we will have a special stand where we will be helping people to install Fedora.
If you are near Buenos Aires, don’t miss this chance!

ERROR: Invalid OpenStack Nova credentials.

October 27th, 2013

I faced a problem while trying to configure OpenStack on Fedora 19 following this guide

# nova --debug flavor-list
REQ: curl -i http://127.0.0.1:5000/v2.0/tokens -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-novaclient" -d '{"auth": {"tenantName": "admin", "passwordCredentials": {"username": "admin", "password": "verybadpass"}}}'

INFO (connectionpool:236) Starting new HTTP connection (1): 127.0.0.1
DEBUG (connectionpool:330) "POST /v2.0/tokens HTTP/1.1" 401 116
RESP: [401] CaseInsensitiveDict({'date': 'Fri, 11 Oct 2013 23:24:41 GMT', 'vary': 'X-Auth-Token', 'content-length': '116', 'content-type': 'application/json'})
RESP BODY: {"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Not Authorized"}}

DEBUG (shell:768) Invalid OpenStack Nova credentials.
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/novaclient/shell.py", line 765, in main
OpenStackComputeShell().main(map(strutils.safe_decode, sys.argv[1:]))
File "/usr/lib/python2.7/site-packages/novaclient/shell.py", line 697, in main
raise exc.CommandError("Invalid OpenStack Nova credentials.")
CommandError: Invalid OpenStack Nova credentials.
ERROR: Invalid OpenStack Nova credentials.

Checking my .keystorerc file it looked good.

[root@localhost ~]# cat .keystonerc
export ADMIN_TOKEN=49ac57278d318dc7bb61
export OS_SERVICE_TOKEN=49ac57278d318dc7bb61
export OS_USERNAME=admin
export OS_PASSWORD=verybadpass
export OS_TENANT_NAME=admin
export OS_AUTH_URL=http://127.0.0.1:5000/v2.0/
export SERVICE_ENDPOINT=http://127.0.0.1:35357/v2.0/
export SERVICE_TOKEN=$ADMIN_TOKEN

The solution was to make sure that the user, role and tenant are associated.
1. Get the ID from the admin user:

[root@localhost ~]# keystone user-list
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+----------------------------------+--------+---------+-------+
| id | name | enabled | email |
+----------------------------------+--------+---------+-------+
| 4738e8d8819a47a5b0cd7b72db3f3fa6 | admin | True | |
| 157da897546e4ac8a98eaf6240683457 | ec2 | True | |
| 3819652ea963416a99aa6bc6dd1cd83c | glance | True | |
| 12c7844b7dc24aa3a7e704b49e026f33 | nova | True | |
| 8313970d7d524ef59983a062711916e8 | swift | True | |
+----------------------------------+--------+---------+-------+

2. Get the tenant admin id, if not there, create it:

[root@localhost ~]# keystone tenant-list
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+----------------------------------+---------+---------+
| id | name | enabled |
+----------------------------------+---------+---------+
| afd9af7cd2604311be27646b4111f8d4 | demo | True |
| 9c85743eee994e28af10ea7b9d215af0 | service | True |
+----------------------------------+---------+---------+

[root@localhost ~]# keystone tenant-create --name admin
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+-------------+----------------------------------+
| Property | Value |
+-------------+----------------------------------+
| description | |
| enabled | True |
| id | 4aec780fe3374e46b4cea0de602c19c5 |
| name | admin |
+-------------+----------------------------------+

3. Get the role id:

[root@localhost ~]# keystone role-list
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+----------------------------------+----------+
| id | name |
+----------------------------------+----------+
| 9fe2ff9ee4384b1894a90878d3e92bab | _member_ |
| 9b4b3ec7153b4b48bf381db829108646 | admin |
+----------------------------------+----------+

Associate them all together.

[root@localhost ~]# keystone user-role-add --user 4738e8d8819a47a5b0cd7b72db3f3fa6 --role 9b4b3ec7153b4b48bf381db829108646[root@localhost ~]# keystone user-role-add --user 4738e8d8819a47a5b0cd7b72db3f3fa6 --role 9b4b3ec7153b4b48bf381db829108646 --tenant-id 4aec780fe3374e46b4cea0de602c19c5

After this, the credentials error disappeared. However, I faced a new error message saying that Nova wasn’t able to sign the token.

I’ve finally installed OpenStack trough RDO. This method is simpler.