Skip to main content

the avatar of YaST Team

Digest of YaST Development Sprint 117

It’s time for more development news from the YaST Team. In this occasion, most of the work has gone into improving features already implemented in previous sprints and, thus, presented in former blog posts. That includes:

  • Improvements when writing wireless security settings for NetworkManager
  • Fixes in the new management of hibernation
  • Possibility to tweak the I/O device autoconfiguration in the installed system
  • Usability improvements regarding nested items in the table widget
  • Better LibYUI packaging including a revamped CMake build system
  • Enhancements in the YaST Autoinstallation module regarding partitioning
  • Many other improvements and fixes here and there

As you surely remember, in the previous sprint we added support for writing basic NetworkManager configuration during installation. But it was quite limited regarding wireless, so it only was capable to translate WPA-PSAK and open wireless configuration. During this sprint, we enhanced the NetworkManager config writers to support the same wireless setups that are currently supported by wicked (WEP, WPA-EAP…). In addition, some UI problems were found and fixed.

In the previous sprint we also improved the hibernation support by tuning the scenarios in which YaST adds the resume= parameter to the bootloader configuration. While testing that improved behavior, some problems were detected both by ourselves and by the awesome QA team at SUSE. Now all those inconvenients are fixed: the bootloader proposal is properly recalculated when needed, the resume parameter is not longer added for small swap devices and we improved the detection of virtual setups in which traditional hibernation is not wanted.

But not all the features we polished during this sprint are so recent. For several months, we have been describing the different steps in the implementation of support in YaST for I/O devices auto-configuration on s390 mainframes. The latest reference was on our blog post of sprint 105 (time flies!). But we still had one more thing in our TO-DO list and, since we recently had to modify the YaST2 Tune module to remove some obsolete settings, we decided to take the opportunity and also add the I/O device autoconfig checkbox to that module. See details and screenshots at this pull request.

We also improved the usability of our most recent LibYUI feature. In the YaST partitioner, which is so far the only application using the new feature to have nested rows in a table, the [Space] key did not only open or close tree branches in the ncurses text-mode interface. It also sent an “Activated” event (the counterpart of double-clicking an item in the Qt graphical user interface), resulting in a quite confusing behavior. See the fix for more detailed information.

And talking about LibYUI, we also decided it was time to tackle one big problem that we have been dragging for too long. The structure of our development repositories and our over-complicated CMake build environment was making too hard to add new features to LibYUI without risking breakage in the distributions. Every change implied a lot of extra synchronization work, which also was an obstacle for external contributions and maintaners of additional plugins and backends. After several weeks of work, we have now walked the first step out of that mess with the new CMake build system for LibYUI

And there is no YaST Team sprint without some news about AutoYaST. This time we have improved the part of the YaST Autoinstallation module that can be used to create and tweak the <partitioning> section of the AutoYaST profile. Apart from several small fixes (like improved visualization or fixes in the fstopt field), it’s now possible to manage <drive> sections to describe NFS and tmpfs file systems.

As usual, there would be much more to report like usability improvements and speedups in YaST Network, fixes in hwinfo or important updates in the documentation… but we need to go back to coding at some point!

So see you again in a couple of weeks with more news about YaST and, if everything works as expected, some reflections about the long-term future. Stay safe and have a lot of fun!

a silhouette of a person's head and shoulders, used as a default avatar

Juega al ajedrez en el servidor lichess en tu dispositivo móvil

Puedes descargar la aplicación libre oficial para jugar al ajedrez en el servidor lichess.org

imagen: Chema Madoz

Empezaba el año 2021 publicando en el blog un artículo sobre el servidor lichess.org para jugar al ajedrez. Puedes leer el artículo en este enlace:

Lichess.org es un servidor libre, y gratuito en el que registrarte y poder jugar al ajedrez y estudiar, aprender y retar a otras personas a jugar al ajedrez en multitud de variantes.

Pero no siempre estamos delante de nuestro equipo ¿entonces tenemos que dejar en modo pausa nuestros retos ajedrecísticos? ¡No! Conéctate a lichess.org desde tu dispositivo móvil.

Para conectarte a lichess.org puedes utilizar la aplicación oficial. Una aplicación para Android y Apple publicada bajo una licencia libre GPL v3, desarrollada en GitHub.

La única pega que podemos ponerle, es que no está disponible desde repositorios de aplicaciones libres como f-droid.

Así que únicamente la podremos instalar desde la tienda de Google y App Store. Aunque también podemos descargar la apk e instalarla en nuestro dispositivo.

Es una aplicación libre, gratuita y con todas las funcionalidades que nos ofrece lichess.org disponibles en nuestra palma de la mano.

Una buena opción a la hora de hacer tiempo en salas de espera y practicar nuestros mejores movimientos al ajedrez.

Dale jaque al rey, ¡tu mueves!

Enlaces de interés

a silhouette of a person's head and shoulders, used as a default avatar

Chinese Lunar Calendar – Plasmoides de KDE (169)

Hoy me complace presentar Chinese Lunar Calendar el plasmoide de KDE número 169 de la gran serie de los mismos mostrados en el blog y que nos ofrece la posibilidad de tener el calendario lunar chino en nuestro escritorio.

Chinese Lunar Calendar – Plasmoides de KDE (169)

Tenemos muchos plasmoides estilo reloj para Plasma, pero pocos para calendarios. Haciendo un rápida búsqueda por el blog me aparecen Calendar WL, Event Calendar (del cual hay que reconocer que es una bestia parda difícil de igualar), el reciente Weekday Grid y Persian Calendar, un plasmoide muy parecido al que os presento hoy.

Y es que si quieres tener el Calendario Linux Chino en tu escritorio éste es tu plasmoide, una alternativa al calendario tradicional de Plasma (DigitalClock applet).

Su instalación no es sencilla, así que os remito a su páginas de la KDE Store para obtener las instrucciones precisas.

Chinese Lunar Calendar - Plasmoides de KDE (169)

Y como siempre digo, si os gusta el plasmoide podéis “pagarlo” de muchas formas en la nueva página de KDE Store, que estoy seguro que el desarrollador lo agradecerá: puntúale positivamente, hazle un comentario en la página o realiza una donación. Ayudar al desarrollo del Software Libre también se hace simplemente dando las gracias, ayuda mucho más de lo que os podéis imaginar, recordad la campaña I love Free Software Day 2017 de la Free Software Foundation donde se nos recordaba esta forma tan sencilla de colaborar con el gran proyecto del Software Libre y que en el blog dedicamos un artículo.

Más información: KDE Store

¿Qué son los plasmoides?

Para los no iniciados en el blog, quizás la palabra plasmoide le suene un poco rara pero no es mas que el nombre que reciben los widgets para el escritorio Plasma de KDE.

En otras palabras, los plasmoides no son más que pequeñas aplicaciones que puestas sobre el escritorio o sobre una de las barras de tareas del mismo aumentan las funcionalidades del mismo o simplemente lo decoran.

the avatar of Nathan Wolf
the avatar of Santiago Zarate

Perl binaries are mismatched - the revenge of the lazy person

The uninvited eldrich terror

You use local::lib, and the pain unfolds: A shell is started, and you find a dreaded:

Cwd.c: loadable library and perl binaries are mismatched (got handshake key 0xdb00080, needed 0xdb80080)

Pennywise, because I could not find the right gif, from the Uninvited, of Sabrina's netflix

Which means: that the module (Cwd in this case) is not compatible (Because it’s an XS module) with your current version of perl, installed on your system: Likely it was compiled for a previous version, leadin to those binaries mismatching

Don’t panic!

I wrote about this however, I left out how to get to the point where you have already an usable Perl again?

The light

Instead of downloading local::lib from git as I used to do… this time I decided to do it on a much simpler way: use perl-local-lib from my distribution, and let it do the magic, I mean that’s why I run openSUSE Tumbleweed

 zypper in perl-local-lib
 rm -rf perl5-old || echo "First time eh?"
 mv perl5 perl5-old
 perl -MCPAN -Mlocal::lib -e 'CPAN::install(App::cpanminus)'
 cpanm App::MigrateModules
 perl-migrate-modules --from ~/perl5-old/lib/perl5 /usr/bin/perl

Et voilà, ma chérie!

It's alive!

the avatar of openSUSE News

Reducing the scope of software.opensuse.org

We have some exciting news to share regarding the consolidation of our web pages.

We’ve decided to drop functionality behind https://software.opensuse.org/distributions and instead provide a redirect to https://get.opensuse.org. Submit request can be found here https://github.com/openSUSE/software-o-o/pull/943.

Both sites were offering similar functionality for downloading install media. Both sites had to be updated with every Alpha, Beta, or changes to media descriptions. The new reduced scope of software-o-o will be purely browsing of available software. The scope of get-o-o won’t change. It will be media downloads and pointers to relevant documentation such as installation or upgrade instructions. We believe that these changes will help to keep it small and simple.

We’re happy to reduce duplication of efforts while not introducing further fragmentation as get.opensuse.org has been around for quite some time already.

Efforts to make the changes were discussed as part of the Web Development Sprint last week. There are descriptions for each distribution on get.opensuse.org to better let new users understand the difference in each openSUSE Distribution. Changes to software-o-o are also expected to be revamped in the future.

The next Web Development Sprint will take place on March 4 at 18:30 UTC on https://meet.opensuse.org/websprints. Notes from the sprint can be accessed at https://etherpad.opensuse.org/p/websprints.

the avatar of Chun-Hung sakana Huang

openSUSE Leap 15.2 as GitLab runner in Azure 小記

openSUSE Leap 15.2 as GitLab runner in Azure 小記


OS: openSUSE Leap 15.2 in Azure

GitLab: 使用 gitlab.com


最近開始學 GitLab

先感謝 陳正瑋 的鐵人賽文章以及 和艦長一起30天玩轉 GitLab 書籍

入門多了很多的資訊


今天要來寫的是把 openSUSE Leap 15.2 當成 gitlab runner 來執行

爲何要寫這篇呢? 當然是因為官方的文件上沒有列出 openSUSE 安裝方式 :)


那就只好自己嘗試, 然後記錄下來了 (攤手)


實作前提

  • 在 gitlab.com 有帳號 ( 免費的就可以, 有付錢的功能更多  )


確認自己的 GitLab project / Group CI / CD Runner 設定與 Token 

  • 在 GitLab.com 登入自己帳號

  • 在 Project / Group 內 的 Settings -- > CI / CD

  • 展開 Runners 就會看到 Token




接下來開始建立實驗


建立 openSUSE Leap 15.2 in Azure

  • 我是用  Cloud Shell in VS code 然後透過 ansible 建立的 ~ 開心



回到 gitlab 身上來

如果在 software.opensuse.org 上面搜尋 gitlab-runner



  • 這邊其實就有看到實驗性套件了


使用 ssh 連入剛剛的 openSUSE Leap 15.2 in Azure


使用 yast  repositories 新增套件庫


#yast  repositories


新增套件庫 (Alt + A)

方式選取 指定 URL



點選下一步 (Alt + N)

套件庫的名稱可以自行取

URL 的部分指定 



點選下一步 (Alt + N)

有遇到 GnuPG Key 可以 Trust 一下



確認 GitLab 套件庫有被加入

點選 OK (Alt + O)



接下來新增相關套件


# zypper   install  gitlab-runner


Loading repository data...

Reading installed packages...

Resolving package dependencies...


The following 5 NEW packages are going to be installed:

  dash gitlab-common gitlab-runner libruby2_6-2_6 ruby2.6


5 new packages to install.

Overall download size: 12.6 MiB. Already cached: 0 B. After the operation, additional 52.3

MiB will be used.

Continue? [y/n/v/...? shows all options] (y): y



註冊 gitlab-runner


# gitlab-runner  register


輸入 https://gitlab.com

輸入 Gitlab-runner token

輸入 這個 runner 的敘述

輸入 這個 runner 的 tag ( 這個很重要 )

輸入 這個 runner 的 executor ( 一般都是 docker or shell, 請見官方文件 )



啟動 gitlab-runner

# gitlab-runner  start


Runtime platform                                    arch=amd64 os=linux pid=3192 revision=1b659122 version=12.8.0


觀察相關資訊

# gitlab-runner  status


Runtime platform                                    arch=amd64 os=linux pid=3210 revision=1b659122 version=12.8.0

gitlab-runner: Service is running!


Notes:

  • Runner 的 config 會存放在 /etc/gitlab-runner/config.toml

  • 要成為 gitlab-runner 也要安裝 git 不然執行會出現錯誤

  • 執行的時候相關工作目錄會在 /srv/gitlab-runner/builds/GITLAB-RUNNER-TOKEN/ 下


在 GitLab.com 上面確認 runner 有設定成功



找時間要看的文件

Disable SKEL 說明

https://docs.gitlab.com/runner/install/linux-repository.html#disable-skel


Gitlab runner 安裝說明

https://docs.gitlab.com/runner/install/linux-repository.html



這樣算是又向 GitLab 前進一步了

~ enjoy it



Reference:




the avatar of Kubic Project

Using Rancher and RKE with MicroOS and Kubic

Intro

Since SUSE acquired Rancher Labs, it’s time to explain how to run Rancher on MicroOS and how to import a Kubic cluster.

I used Rancher 2.5.5 for this, newer versions my have different requirements.

Rancher with MicroOS

The good news is: Rancher works out of the box on MicroOS.

The necessary steps are:

  1. Install MicroOS as base OS (no Container Host system role is necessary)
  2. Install docker: transactional-update pkg install docker
  3. Reboot: systemctl reboot
  4. Enable and start docker: systemctl enable --now docker

From here you can follow the standard Rancher documentation and install Rancher: docker run -d --restart=unless-stopped -p 80:80 -p 443:443 --privileged rancher/rancher

Rancher with RKE and MicroOS

Rancher offers the possibility to setup a new kubernetes cluster using RKE on an existing, running OS. This section explains how to do that using MicroOS as the host OS.

While in general, RKE works fine on MicroOS, there could be two pitfalls:

  1. MicroOS is using a read-only root filesystem while RKE tries to write to /usr/libexec/kubernetes
  2. Rancher reports an error that the API is not reacheable.

The second problem is most likely a docker problem. I suggest to start with openSUSE MicroOS Build 20210205 or newer, I have never seen this problem with docker 20.10.3ce introduced with this build. In my case, the reason for the error message was that IP forwarding didn’t got fully enabled by docker. Please make sure that IP forwarding is enabled for all devices:

# sysctl -a |grep \\.forward
net.ipv4.conf.all.forwarding = 1
net.ipv4.conf.default.forwarding = 1
net.ipv4.conf.docker0.forwarding = 1
net.ipv4.conf.eth0.forwarding = 1
net.ipv4.conf.lo.forwarding = 1

There are the steps to setup MicroOS for this:

  1. Install MicroOS as base OS (no Container Host system role is necessary)
  2. Install docker: transactional-update pkg install docker
  3. Reboot: systemctl reboot
  4. Enable and start docker: systemctl enable --now docker

On the Rancher GUI select “Existing Nodes” of “Create a new Kubernetes cluster With RKE and existing bare-metal servers or virtual machines” and follow the documentation for Flatcar Container Linux.

Rancher with Kubic

Importing an openSUSE Kubic cluster can be simple or difficult, depending on which kubernetes version your cluster is running. openSUSE Kubic currently comes with kuberenetes 1.20.2 as default. Rancher only works with kuberenetes up to 1.19.7, it does not work with 1.20.2 as of today. So if you haven’t updated your cluster yet to 1.20.x, you can go to Register an existing Kubernetes cluster, select Other Cluster and follow the workflow.

At the end, Rancher will come up with two errors:

  1. Alert: Component controller-manager is unhealthy.
  2. Alert: Component scheduler is unhealthy.

You can ignore this errors: Rancher uses a deprecated interface, which kubeadm disables by default.

a silhouette of a person's head and shoulders, used as a default avatar

Pop+, un tema de iconos clásico para Plasma

Sigo con los temas de iconos en el blog, y es que debo reconocer que me fascina la variedad que tenemos a nuestra disposición, tanto de forma , estilo o colores. Hoy tengo el gusto de presentaros un tema de iconos llamado Pop+, un tema de iconos que retoma el concepto clásico de estos avatares y que me recuerda a entornos del pasado.

Pop+, un tema de iconos clásico para Plasma

Para el escritorio Plasma de la Comunidad KDE hay cientos de temas de todo tipo disponibles para los usuarios: iconos, cursores, emoticones, etc, Y como me gusta cambiar de vez en cuando, en el blog le he dedicado muchos artículos a cada uno de los packs.

No obstante, como suelo decir, cambiar el tema de iconos de un escritorio es una de las formas de adaptación más personal que puedes realizar sobre tu PC, ya que modifica totalmente el aspecto del mismo a la hora de interaccionar con tus aplicaciones, documentos y servicios.

Hoy os presento Pop+, un tema de iconos clásico creado Herma y que utiliza un diseño colorido, muy claro y limpio, con estilo semi-plano con detalles en 3D. El tema está inspirado en el pack de Adwaita para GNOME Icons.

Pop+, un tema de iconos clásico para Plasma

Y como siempre digo, si os gusta el pack de iconos podéis “pagarlo” de muchas formas en la nueva página de KDE Store, que estoy seguro que el desarrollador lo agradecerá: puntúale positivamente, hazle un comentario en la página o realiza una donación. Ayudar al desarrollo del Software Libre también se hace simplemente dando las gracias, ayuda mucho más de lo que os podéis imaginar, recordad la campaña I love Free Software Day 2017 de la Free Software Foundation donde se nos recordaba esta forma tan sencilla de colaborar con el gran proyecto del Software Libre y que en el blog dedicamos un artículo.

Más información: KDE Store

the avatar of Alessandro de Oliveira Faria

Livro: Como implementar IA na sua empresa (Gratuito)

Não foi fornecido texto alternativo para esta imagem
Boa leitura…

É com muito orgulho que compartilho o livro “Como implementar IA na sua empresa” . Uma iniciativa escrita de maneira colaborativa através do Comitê de Inovação da I2AI ( Associação Internacional de Inteligência Artificial ), no qual participei como co-autor nos capítulos de visão computacional e segurança da informação.

Escrito com o propósito de explicar de forma sucinta o que é Inteligência Artificial e inspirar muitas pessoas a elaborar projetos de IA. Neste volume do ebook, encontraremos casos de uso, ferramentas para auxiliar na implementação, dicas para idealizar um piloto, estratégias recrutar um time e uma série de referências para que possa ampliar seus conhecimentos no mundo de IA.

I2AI International Association of Artificial Intelligence,

Um dos temas mais relevantes pra qualquer profissional atualmente é tecnologia. Muito se fala sobre como estas novas tecnologias podem mudar o mundo como conhecemos: viagens para Marte, automatização de trabalhos repetitivos, manipulação e geração de vídeos e imagens, impressão de órgãos e comida. A realidade em muitos aspectos imita o que há de melhor (e as vezes de pior) na ficção científica.

Agora, além do Buzzword, termos e palavras diferentes em nosso vocabulário, há também muito desconhecimento e confusão sobre o que são estas novas tecnologias e o que elas são capazes de fazer. Foi pensando nisso que a I2AI International Association of Artificial Intelligence, através da brilhante coordenação de Marco Antonio Lauria e a contribuição de diversos autores do nosso comitê de Inovação, lançou e disponibilizou para todos os interessados, de maneira gratuita e eletrônico um fantástico e-book que apresenta em mais detalhes uma das estrelas desta nova geração de tecnologias disruptivas: A Inteligência Artificial (IA).

Se você quer saber um pouco mais sobre os conceitos ligados a IA através de uma linguagem fácil e acessível, este e-book foi feito pra você. Entre em nosso site, e baixe agora o 1o volume deste material incrível, Acesse o link e faça o download: https://conteudo.i2ai.org/entendendo-ia