Exactly what problem will this solve?

The project monitor page is currently based on a table with search and filter. This rudimentary interface is basically just exposing the data we have, not helping the User to make sense of it.

For whom do we solve that problem?

Especially for power users as most of the problems with this view occur if you have many Repositories and/or Packages in your Project.

What could be done?

We are interested in new ideas. So a mock-up, prototype or even a PR are welcome

Join this project Leave this project

Looking for hackers with the skills:

bootstrap ux obs

This project is part of:

Hack Week 19

Activity

7 months ago: kennaanna started this project.

about 5 years ago: mkubecek liked this project.

about 5 years ago: Pharaoh_Atem liked this project.

about 5 years ago: vpereirabr added keyword "ux" to this project.

about 5 years ago: vpereirabr added keyword "obs" to this project.

about 5 years ago: vpereirabr added keyword "bootstrap" to this project.

about 5 years ago: david_kang liked this project.

about 5 years ago: vpereirabr originated this project.

Comments

Be the first to comment!

Similar Projects

obs

Learn obs/ibs sync tool by xlai

Description

Once images/repo are built from IBS/OBS, there is a tool to sync the image from IBS/OBS to openqa asset directory and trigger openqa jobs accordingly.

Goals

Check how the tool is implemented, and be capable to add/modify our needed images/repo in future by ourselves.

Resources

https://github.com/os-autoinst/openqa-trigger-from-obs
https://gitlab.suse.de/openqa/openqa-trigger-from-ibs-plugin/-/tree/master?ref_type=heads

Learn about OSB and contribute to `kustomize` and `k9s` packages to add ARM arch by dpock

Description

There are already k9s and kustomize packages that exist for openSUSE today. These could be used as the source for these binaries in our rancher projects. By using them we would benefit from CVE fixes included in our distribution of the packages not in cluded upstream. However they are not providing arm package builds which are required.

Goals

[ ] Update the kustomize package in OBS to use the newest version and send change request

Resources

k9s: https://build.opensuse.org/package/show/openSUSE:Factory/k9s
kustomize: https://build.opensuse.org/package/show/openSUSE:Factory/kustomize
Learning Docs: https://confluence.suse.com/display/packaging/Training%2C+Talks+and+Videos

Git CI to automate the creation of product definition by gyribeiro

Description

Automate the creation of product definition

Goals

Create a Git CI that will:

automatically be triggered once a change (commit) in package list is done.
run tool responsible to update product definition based on the changes in package list
test the updated product definition in OBS
submit a pull request updating the product definition in the repository

NOTE: this Git CI may also be triggered manually

Resources

https://docs.gitlab.com/ee/ci/
https://openbuildservice.org/2021/05/31/scm-integration/
https://github.com/openSUSE/openSUSE-release-tools

Testing and adding GNU/Linux distributions on Uyuni by juliogonzalezgil

Join the Gitter channel! https://gitter.im/uyuni-project/hackweek

Uyuni is a configuration and infrastructure management tool that saves you time and headaches when you have to manage and update tens, hundreds or even thousands of machines. It also manages configuration, can run audits, build image containers, monitor and much more!

Currently there are a few distributions that are completely untested on Uyuni or SUSE Manager (AFAIK) or just not tested since a long time, and could be interesting knowing how hard would be working with them and, if possible, fix whatever is broken.

For newcomers, the easiest distributions are those based on DEB or RPM packages. Distributions with other package formats are doable, but will require adapting the Python and Java code to be able to sync and analyze such packages (and if salt does not support those packages, it will need changes as well). So if you want a distribution with other packages, make sure you are comfortable handling such changes.

No developer experience? No worries! We had non-developers contributors in the past, and we are ready to help as long as you are willing to learn. If you don't want to code at all, you can also help us preparing the documentation after someone else has the initial code ready, or you could also help with testing :-)

The idea is testing Salt and Salt-ssh clients, but NOT traditional clients, which are deprecated.

To consider that a distribution has basic support, we should cover at least (points 3-6 are to be tested for both salt minions and salt ssh minions):

Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
Onboarding (salt minion from UI, salt minion from bootstrap scritp, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator)
Package management (install, remove, update...)
Patching
Applying any basic salt state (including a formula)
Salt remote commands
Bonus point: Java part for product identification, and monitoring enablement
Bonus point: sumaform enablement (https://github.com/uyuni-project/sumaform)
Bonus point: Documentation (https://github.com/uyuni-project/uyuni-docs)
Bonus point: testsuite enablement (https://github.com/uyuni-project/uyuni/tree/master/testsuite)

If something is breaking: we can try to fix it, but the main idea is research how supported it is right now. Beyond that it's up to each project member how much to hack :-)

If you don't have knowledge about some of the steps: ask the team
If you still don't know what to do: switch to another distribution and keep testing.

This card is for EVERYONE, not just developers. Seriously! We had people from other teams helping that were not developers, and added support for Debian and new SUSE Linux Enterprise and openSUSE Leap versions :-)

Pending

FUSS

FUSS is a complete GNU/Linux solution (server, client and desktop/standalone) based on Debian for managing an educational network.

https://fuss.bz.it/

Seems to be a Debian 12 derivative, so adding it could be quite easy.

[W] Reposync (this will require using spacewalk-common-channels and adding channels to the .ini file)
[W] Onboarding (salt minion from UI, salt minion from bootstrap script, and salt-ssh minion) (this will probably require adding OS to the bootstrap repository creator) --> Working for all 3 options (salt minion UI, salt minion bootstrap script and salt-ssh minion from the UI).
[W] Package management (install, remove, update...) --> Installing a new package works, needs to test the rest.
[I] Patching (if patch information is available, could require writing some code to parse it, but IIRC we have support for Ubuntu already). No patches detected. Do we support patches for Debian at all?
[W] Applying any basic salt state (including a formula)
[W] Salt remote commands
[ ] Bonus point: Java part for product identification, and monitoring enablement

Fix RSpec tests in order to replace the ruby-ldap rubygem in OBS by enavarro_suse

Description

"LDAP mode is not official supported by OBS!". See: config/options.yml.example#L100-L102

However, there is an RSpec file which tests LDAP mode in OBS. These tests use the ruby-ldap rubygem, mocking the results returned by a LDAP server.

The ruby-ldap rubygem seems no longer maintaned, and also prevents from updating to a more recent Ruby version. A good alternative is to replace it with the net-ldap rubygem.

Before replacing the ruby-ldap rubygem, we should modify the tests so the don't mock the responses of a LDAP server. Instead, we should modify the tests and run them against a real LDAP server.

Goals

Goals of this project:

Modify the RSpec tests and run them against a real LDAP server
Replace the net-ldap rubygem with the ruby-ldap rubygem

Achieving the above mentioned goals will:

Permit upgrading OBS from Ruby 3.1 to Ruby 3.2
Make a step towards officially supporting LDAP in OBS.

Resources

Replace ruby-ldap rubygem with net-ldap