Blogging about Cloud, AI/ML and Programming
I have created a Fedora 23 image for Hummingboard/Cubox-i. I will also create a Fedora 24 image as soon as it is released.
wget https://googledrive.com/host/0B1Z2aFriRL5PUGpzMHRVbDBNYU0 -O Fedora-Minimal-armhfp-cubox-i_hb-23-10-sda.raw.xz
The MD5 hash of this file is aa854909d5e3c9f76a964635b9c4f790
I have created 2 Fedora 21 images for the HummingBoard and Cubox-i.
http://vps1.mkreder.com/Fedora-Mate-armhfp-21-5-sda.raw.xz
MATE
http://vps1.mkreder.com/Fedora-LXDE-armhfp-21-5-sda.raw.xz
LXDE
I will create a XFCE based image too, soon.
In order to extend the root filesystem on this image, you need to run:
fdisk /dev/location-of-your-fedora-arm-media << EOF
d
3
n
p
2001954
w
EOF
partprobe /dev/location-of-your-fedora-arm-media
e2fsck -f /dev/location-of-your-fedora-arm-media3
resize2fs /dev/location-of-your-fedora-arm-media3
More information about Fedora on these boards can be found on this github page
A month ago (or so) we decided to start organizing an event focused on Fedora here in Buenos Aires. The objectives for the event were:
The organization was good, we thought of all the required tasks and we assigned owners for each one. Eduardo Echeverria (echevemaster) helped a lot by setting up the event’s website. Leo, Rino, Mariela (our new ambassador) and myself divided the remaining tasks.
We met Leo and Fabio who came from Brasil on Wednesday night for an organizational dinner. We had a great time at “La Casa Del Queso”, talking and sharing ideas about the Fedora Day and the bid we are going to present for FUDCon 2015.
On Saturday, the day of the event, we went to the UTN early in the morning to set everything up.We met with Matias Maceira and Valentin Basel who came from Cordoba, Julio Sanchez who came from Tierra del Fuego and Adrian Soliard who came from Entre Rios.
I also have to mention that Oscar Perez from the UTN has been very kind and helpful since the days prior to the event. He did all the paper work on the university to request the rooms and the equipment that we needed. The day of the event he also showed a very professional aptitude, I like that we can count with someone as him to organize events there.
The event was great, we did a short introduction about how to contribute and then I gave a talk for new ambassadors while Fabio was giving a talk about Fedora QA and Rino another one about packaging.
Then we had a short interval for lunch on the UTN buffet and then we continue with the talks that were scheduled.
At the end of the day we picked up a winner of a blue Fedora that I brought. The winner very happy with her new Fedora.
At night we went to o a local pub to celebrate the success of the day.
Some facts about this event:
I also want to thank Fabio and Leo who came from Brasil and all the guys who came from all different Argentinian provinces.
Some pictures
Organizational dinner
Fedora Day
Release Party on the pub
Last week I attended CISL. The event was good, several people came to our stand to talk about Fedora and ARM (I brought a HummingBoard and a Raspberry Pi).
I had the pleasure of meeting with Jon “maddog” Hall, director of Linux International. We took a picture together and then he told me about the community effort of translating assembler code into C or ASM compatible with ARMv8+ (aarch64).
Two candidates to the ambssadors team also came to talk and learn more about FOSS events.
Español
La semana pasada estuve en la CISL. El evento estuvo bueno, bastante gente se acerco a nuestro stand a hablar sobre Fedora y ARM . (Yo lleve una HummingBoard y una Raspberry Pi)
También tuve la oportunidad de conocer a Jon “maddog” Hall, director de Linux International. Nos tomamos una foto juntos y después me contó de la iniciativa de traducir código ensamblador a C o código ensamblador compatible con ARMv8+ (aarch64).
Dos candidatos a embajadores también vinieron a charlar y aprender más sobre eventos de software libre.
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:
El mes pasado fui gratamente sorprendido por un correo electrónico desde Alemania, donde me comentaban que habían visto mi blog y que estaban interesados en mandarme un dispositivo Cubox-i o HummingBoard gratis.
Fue difícil la decisión pero opte por la HummingBoard ya que incluye un socket GPIO (General Purpose Input-Output) el cual permite conectar diferentes componentes electrónicos para hacer cosas con robotica, gomotica, etc.
Después de varios meses de espera y varias horas en la aduana, finalmente la recibí. En comparación con la Raspberry Pi, la HummingBoard tiene más memoria RAM (1GB contra 512MB), más CPU (2 cores, contra 1) y entre cosas trae salida de audio SPDIF.
Muy agradecido con el nuevo chiche, ya pude correr Fedora en él. Para poder hacerlo tuve que descargar una imagen de GitHub. En el mismo repo de GitHub se pueden encontrar instrucciones para compilar la imagen desde cero.
Hace algunos días, Peter Robinsion posteo en su blog que la HummingBoard sera uno de los dispositivos principales para Fedora ARM en Fedora 21. Por lo cual, va a ser uno de los dispositivos mas testeados y seguramente voy a ser parte de ello.
Fedora ya soporta desde hace varias versiones la arquitectura de la HummingBoard (armhfp), por lo cual todo el software de Fedora y hasta de algunos repositorios de terceros como RPMFusion están completamente disponible para descargar. Eso es algo que lamentablemente falta ver para la Raspberry Pi con Pidora.
Les dejo algunas imágenes de la HummingBoard:
La agencia de noticias TELAM realizó este video cobertura de la FLISOL. Se puede ver en el mismo el impacto que tuvo Fedora en la FLISOL este año.
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.
Ayer 26 de Abril, se llevó a cabo la FLISOL 2014. Estoy orgulloso de poder decir que Fedora tuvo un éxito rotundo este año.
Por primera vez, contamos con un stand donde la gente se pudo acercar para consultar e instalar Fedora. Gracias a los esfuerzos de Marketing como el banner, los DVDs y las chombas, Fedora demostró mucha más presencia en el evento y despertó mucho más interés en la gente.
Quiero agradecer a dos excelentes contribuidores (ezq y valentin) de Fedora que hicieron el esfuerzo de venir desde sus provincias para participar y aportar muchísimo en el evento.
Algunas fotos del evento:
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:
El Sabado 26 de Abril de 10 a 18 hs se celebrara el FLISOL 2014 en la UTN de Medrano.
Este año vamos a estar dando las siguientes charlas:
– Fedora y Su Comunidad
– Virtualización en Fedora
– A Jugar con Pidora
Además, por primera vez en la historia de la FLISOL, vamos a contar con un stand donde estaremos asistiendo a todas aquellas personas que quieran instalar Fedora.
No te lo pierdas!
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!
Encontré un problema tratando de instalar OpenStack en Fedora 19 con esta guía
# 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.
Mirando el archivo .keystorerc, parecía estar bien.
[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
La solución fue hacer que el usuario, rol e inquilino estén asociados.
1. Obtener el ID para el usuario admin:
[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. Obtener el ID inquilino para admin, si no existe, lo creamos:
[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. Obetener el ID del rol:
[root@localhost ~]# keystone role-list
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+----------------------------------+----------+
| id | name |
+----------------------------------+----------+
| 9fe2ff9ee4384b1894a90878d3e92bab | _member_ |
| 9b4b3ec7153b4b48bf381db829108646 | admin |
+----------------------------------+----------+
Por ultimo, los asociamos:
[root@localhost ~]# keystone user-role-add --user 4738e8d8819a47a5b0cd7b72db3f3fa6 --role 9b4b3ec7153b4b48bf381db829108646[root@localhost ~]# keystone user-role-add --user 4738e8d8819a47a5b0cd7b72db3f3fa6 --role 9b4b3ec7153b4b48bf381db829108646 --tenant-id 4aec780fe3374e46b4cea0de602c19c5
Después de esto, el error de las credenciales desapareció. De todos modos, encontré otro error que decía que Nova no era capaz de firmar el token de autenticación.
Finalmente instale OpenStack utilizando RDO. Este método es mucho mas sencillo.
English
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.
La semana pasada asistimos al CISL 2013. Tuve la oportunidad de dar una charla sobre virtualización y me impresionó lo interactiva y participativa que fue. Mucha gente tiene experiencia en este tema hoy en día y es muy bueno poder compartir experiencias.
English
Last week we attended the CISL 2013 event. I gave a talk about Virtualization and was very impressed by how interactive and participative it was. A lot of people have experience with this topic nowadays and it is nice to share experiences.
Matias *Matt* Kreder 