| priteau | #startmeeting blazar | 15:07 |
|---|---|---|
| opendevmeet | Meeting started Thu Dec 12 15:07:29 2024 UTC and is due to finish in 60 minutes. The chair is priteau. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:07 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:07 |
| opendevmeet | The meeting name has been set to 'blazar' | 15:07 |
| priteau | Hello. I will start the meeting in a moment. | 15:08 |
| priteau | #startmeeting blazar | 15:08 |
| opendevmeet | priteau: Error: Can't start another meeting, one is in progress. Use #endmeeting first. | 15:08 |
| priteau | #topic Roll call | 15:08 |
| priteau | o/ | 15:08 |
| markpowers | o/ | 15:09 |
| darko | hello | 15:09 |
| priteau | Hello darko | 15:10 |
| darko | hello, first time I participate in this meeting, looking for some help | 15:11 |
| priteau | Sure. We will cover our usual meeting items and we can talk after? | 15:11 |
| darko | works for me, thanks in advance | 15:12 |
| priteau | #topic Epoxy release | 15:12 |
| priteau | So far the changes merged in the Epoxy cycle have been mostly related to code maintenance | 15:14 |
| priteau | We're fairly busy at the moment but would like to pick up more feature work in the new year | 15:14 |
| priteau | Anything on your side markpowers? | 15:14 |
| markpowers | Nothing from me at this point | 15:15 |
| priteau | OK. I am also looking into CI issues on stable branches, I don't think the issue is within blazar | 15:17 |
| priteau | This is about https://review.opendev.org/c/openstack/blazar/+/934948 | 15:18 |
| priteau | #topic Next meeting | 15:18 |
| priteau | Our next bi-weekly meeting would fall on December 26. I will be on holiday, I propose we cancel. | 15:18 |
| markpowers | I concur | 15:19 |
| priteau | I will send an email to the list | 15:19 |
| priteau | Next meeting will be on January 9 | 15:20 |
| markpowers | Sounds good to me | 15:20 |
| priteau | I've just sent the emai | 15:21 |
| priteau | 15:21 | |
| priteau | #topic AOB | 15:21 |
| priteau | Anything else to discuss today? | 15:21 |
| markpowers | not from me | 15:22 |
| priteau | darko: Do you have a topic to raise as part of the meeting or should we discuss just after? | 15:22 |
| darko | I think we can discuss just after, its a very simple question | 15:23 |
| priteau | OK. Let's wrap up the meeting. | 15:23 |
| priteau | Thanks for joining. Happy holidays! | 15:23 |
| priteau | #endmeeting | 15:24 |
| opendevmeet | Meeting ended Thu Dec 12 15:24:20 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:24 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/blazar/2024/blazar.2024-12-12-15.07.html | 15:24 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/blazar/2024/blazar.2024-12-12-15.07.txt | 15:24 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/blazar/2024/blazar.2024-12-12-15.07.log.html | 15:24 |
| markpowers | thanks, you too! | 15:24 |
| priteau | darko: How may I help? | 15:24 |
| darko | yes thank you very much, I am quite new to openstack with blazar | 15:25 |
| darko | I have deployed openstack bobcat with juju, and blazar 2023.2. Everything seems to works fine expect that a user see all availability zones (host reservation) from other users too when lauching an instance, even if the users are from different projects. | 15:25 |
| darko | I that the normal behavior? The user are only "member" within there respective project | 15:26 |
| priteau | I believe that Nova availability zones are a global resource, not specific to a particular project | 15:26 |
| priteau | So I would say this is expected behaviour | 15:26 |
| priteau | It should just be a UUID though, with no identifiable information? | 15:27 |
| darko | this is why I do not understand the mechanism, because actually an user without making any reservation can select the availability zone reserved from other user and create instance from that zone | 15:28 |
| priteau | The availability zone is just a cosmetic side-effect, this is not how you launch instances in a reservation | 15:29 |
| priteau | Are you using host-based or instance-based reservation? | 15:29 |
| darko | it is for host-based reservation, instance-basec reservation thourght flavor are working fine | 15:30 |
| priteau | Is the BlazarFilter loaded and enabled in nova-scheduler? | 15:30 |
| darko | yes it is of course | 15:31 |
| priteau | Then you should only be able to launch instances inside a reservation, if you use the corresponding scheduler hint | 15:31 |
| darko | by "inside a reservation", what does that mean exactly? the created aggregate? | 15:32 |
| priteau | The Nova host aggregate is how the reservation is enforced internally, but the actual mechanism that users need to use is the scheduler hint | 15:33 |
| priteau | As described here: https://docs.openstack.org/blazar/latest/cli/host-reservation.html#use-the-leased-resources | 15:34 |
| priteau | openstack server create --flavor <flavor> --image <image> --network <network> --hint reservation=<reservation-id> <server-name> | 15:34 |
| darko | ah ok, and the scheduler hint if from the BlazarFilter? | 15:34 |
| priteau | Yes, it is enforced within the BlazarFilter | 15:35 |
| darko | I did not yet tried the reservation throught command line | 15:35 |
| darko | I was expecting to be able to do that from the horizon dashboard, because this is where we see all availability zone | 15:36 |
| darko | when a user wants to start an instance | 15:36 |
| priteau | Yeah, the availability zones is just a side effect of the fact we declare host aggregates | 15:36 |
| priteau | But this is not how you should select your reservation | 15:37 |
| priteau | In Horizon there is scheduler hint session | 15:37 |
| priteau | Sorry, section | 15:37 |
| priteau | In the launch instance controls | 15:37 |
| priteau | We don't have more integrated launch controls upstream at this point | 15:37 |
| darko | ok, I didn't see the scheduler hint session, this is somewhere in the launch instance panel? | 15:38 |
| darko | *section | 15:39 |
| priteau | It may be optional, let me check | 15:40 |
| darko | ah I found it, there is indeeed | 15:40 |
| priteau | https://docs.openstack.org/horizon/2023.2/configuration/settings.html#enable-scheduler-hints | 15:41 |
| priteau | It is enabled by default | 15:41 |
| darko | the reservation should appear automatically in that section? | 15:42 |
| priteau | I am afraid not. It is manual. | 15:43 |
| priteau | There is no specific integration between blazar and horizon in the launch instance panel | 15:43 |
| priteau | Some deployments have custom Horizon code, for example https://www.chameleoncloud.org | 15:44 |
| darko | yes I tested both, but with chameloncloud we cannot reserve virtual machine :) | 15:45 |
| darko | at least now I understand what was the problem | 15:46 |
| darko | thank you very much, Im gonna try these scheduler hint | 15:47 |
| priteau | May I ask where you are from (your organisation) and what is your use case for blazar? | 15:47 |
| darko | From Switzerland, in an university. We want to use the reservation mechanism as we do not have a lot of hardware resources, and especially for orgasitional purpose | 15:49 |
| darko | To make a fair use of the resources in sort | 15:50 |
| priteau | Have you tried flavor-based reservation? It may be a better fit for your use case and better integrated in Horizon | 15:50 |
| darko | I just read about it today while going throught the docs. This is indeed something I want to try. How do we enable these reservation? | 15:52 |
| darko | I was not sure because of the note: "The implementation of flavor-based instance reservation is still incomplete. Only a limited number of flavor extra specs is supported. Virtual instance reservations and flavor-based instance reservations cannot yet be created on the same resources. Affinity rules and resource traits are not yet supported." | 15:53 |
| priteau | Yes, that's still new, and not available in Bobcat (it was merged in Dalmatian) | 15:54 |
| priteau | But I really meant to ask, did you consider using instance-based reservation (where you can select cpu/ram/disk) | 15:54 |
| darko | yes we want both host and instance based reservation | 15:55 |
| priteau | I see | 15:56 |
| darko | that is why we prefer to use the official blazar instead of the chameloncloud version | 15:57 |
| priteau | Chameleon's fork may support both, it's just that they have disabled instance reservation on their deployment | 15:59 |
| priteau | If you would be interested in commercial support to tune Blazar to your requirements, feel free to contact the company I work for: https://stackhpc.com/pages/contact.html | 16:00 |
| darko | ok, they have at least disabled it from the horizon interface | 16:00 |
| darko | ok I take note of that, I will refer to my hierachy | 16:02 |
| darko | I might come again here otherwise to find help | 16:05 |
| darko | thank you very much for you help | 16:05 |
| darko | I have to go, I wish you happy holidays. | 16:07 |
| priteau | You too, thanks for getting in touch! | 16:10 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!