| jwysogla | Hi, I'm thinking about adding new integration jobs for the ceilometer and python-observabilityclient projects. We want to use Prometheus for storage of metrics and "sg-core" to help transport the metrics from ceilometer to Prometheus. My idea is, I'd use ansible to run an sg-core or Prometheus container, configure everything to work together and then either use tempest or ansible to run some queries | 09:56 |
|---|---|---|
| jwysogla | and check that everything works. I'd like to ask if that sounds doable and reasonable with our CI. Especially pulling and running third-party (sg-core and Prometheus) container images to test openstack projects. | 09:56 |
| dulek | Hey folks! I'm a mentor of one of the OpenStack projects in the current edition of Outreachy. The initial phase is contribution and I already have some participants that could try doing more advanced tasks, but some lack hardware to be able to run DevStack. I don't want to favore those that have a better hardware. Is there some way to get a few VMs that could work as | 12:10 |
| dulek | devel/testing env for them? | 12:10 |
| *** elodilles is now known as elodilles_afk | 12:17 | |
| frickler | dulek: how many would "a few" be for you? I can see if I can get some quota from my local cloud deployment. otherwise maybe one of our testing capacity donors like mnaser or amorin might be able to help | 12:26 |
| dulek | Currently I have one participant that could use it. Another one seems to be okay with using his own resources. 3 DevStack-grade VMs would probably be enough at this stage. I want to have a spare to make sure there's a fair competition if someone else requests a VM. | 12:29 |
| fungi | dulek: in the past, ovh has also donated free accounts with limited quota for students to use in training classes and such | 12:39 |
| fungi | jwysogla: sure, we have lots of jobs that download container images from quay or dockerhub and start them on job nodes to test things, it's as straightforward as it sounds. you can also get a lot more complex, rebuilding the images yourself with patches applied, separating image build and image consumption into different jobs which communicate with each other through an ephemeral image | 12:42 |
| fungi | registry that's part of your buildset, doing depends-on to pull requests on github for proposed changes to someone's container configuration or software that's embedded in external container images you're rebuilding with that, and so on | 12:42 |
| opendevreview | Merged openstack/project-config master: Replace 2023.2/Bobcat key with 2024.1/Caracal https://review.opendev.org/c/openstack/project-config/+/896944 | 15:25 |
| *** elodilles_afk is now known as elodilles | 15:37 | |
| jwysogla | fungi: Thank you for the answer. | 16:04 |
| fungi | of course. if you have more specific questions when you start designing your job, feel free to ask in here | 16:07 |
| -opendevstatus- NOTICE: The Gerrit service on review.opendev.org will be offline momentarily while we restart it for a combined runtime and platform upgrade | 16:33 | |
| opendevreview | Clark Boylan proposed openstack/project-config master: Update the jeepyb gerrit build jobs to match current base image https://review.opendev.org/c/openstack/project-config/+/897710 | 17:47 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!