| *** ysandeep|out is now known as ysandeep | 05:36 | |
| mnasiadka | #kolla book liberty-MonB1 | 08:12 |
|---|---|---|
| openinfraptg | mnasiadka: Room liberty is now booked on MonB1 for kolla | 08:12 |
| mnasiadka | #kolla book liberty-MonB2 | 08:12 |
| openinfraptg | mnasiadka: Room liberty is now booked on MonB2 for kolla | 08:12 |
| mnasiadka | #kolla book liberty-MonB3 | 08:12 |
| openinfraptg | mnasiadka: Room liberty is now booked on MonB3 for kolla | 08:12 |
| mnasiadka | #kolla book liberty-MonB4 | 08:12 |
| openinfraptg | mnasiadka: Room liberty is now booked on MonB4 for kolla | 08:12 |
| mnasiadka | #kolla book liberty-TueB1 | 08:13 |
| openinfraptg | mnasiadka: Room liberty is now booked on TueB1 for kolla | 08:13 |
| mnasiadka | #kolla book liberty-TueB2 | 08:13 |
| openinfraptg | mnasiadka: Room liberty is now booked on TueB2 for kolla | 08:13 |
| mnasiadka | #kolla book liberty-TueB3 | 08:13 |
| openinfraptg | mnasiadka: Room liberty is now booked on TueB3 for kolla | 08:13 |
| mnasiadka | #kolla book liberty-TueB4 | 08:13 |
| openinfraptg | mnasiadka: Room liberty is now booked on TueB4 for kolla | 08:13 |
| mnasiadka | #kolla book liberty-WedB1 | 08:13 |
| openinfraptg | mnasiadka: Room liberty is now booked on WedB1 for kolla | 08:13 |
| mnasiadka | #kolla book liberty-WedB2 | 08:13 |
| openinfraptg | mnasiadka: Room liberty is now booked on WedB2 for kolla | 08:13 |
| *** akekane_ is now known as abhishekk | 08:33 | |
| *** ysandeep is now known as ysandeep|afk | 11:51 | |
| *** ysandeep|afk is now known as ysandeep | 12:38 | |
| *** ysandeep is now known as ysandeep|afk | 14:22 | |
| *** ysandeep|afk is now known as ysandeep | 15:21 | |
| *** ysandeep is now known as ysandeep|out | 15:40 | |
| gmann | #openstack-tc book cactus-ThuB3 | 17:21 |
| openinfraptg | gmann: Room cactus is now booked on ThuB3 for openstack-tc | 17:21 |
| gmann | #openstack-tc book cactus-ThuB4 | 17:21 |
| openinfraptg | gmann: Room cactus is now booked on ThuB4 for openstack-tc | 17:21 |
| gmann | #openstack-tc book cactus-FriB3 | 17:22 |
| gmann | #openstack-tc book cactus-FriB4 | 17:22 |
| openinfraptg | gmann: Room cactus is now booked on FriB3 for openstack-tc | 17:22 |
| openinfraptg | gmann: Room cactus is now booked on FriB4 for openstack-tc | 17:22 |
| gmann | diablo_rojo: openstack-tc want to book slot for 17-19 UTC on Thursday and Friday, please let me know how to book it? hope we can open these slots. | 17:23 |
| gmann | #openstack-tc book bexar-MonB3 | 17:25 |
| openinfraptg | gmann: Room bexar is now booked on MonB3 for openstack-tc | 17:25 |
| gmann | #openstack-tc book bexar-MonB4 | 17:25 |
| openinfraptg | gmann: Room bexar is now booked on MonB4 for openstack-tc | 17:25 |
| gmann | diablo_rojo: ttx: TC is coming up the idea of 'Operator Hours' slots in PTG to increase the operator engagement in PTG. With discussion and operator feedbacks, we want to book 'Operator hours' slots (Two slots of 1 hr each every day) and ask project to choose/reserve for their project. | 18:52 |
| gmann | something like TC book 'Operator hours' and projextX can reserve it by tagging 'Operators Hour: projectX' | 18:53 |
| gmann | how we can book those in ptgbot page? | 18:53 |
| gmann | currently all slots are shown as track name not with specific tag, if we can have ability to add tag per slot then we it will be helpful. for example: nova can tag slot with nova-placement: 'Operator Hours' | 18:55 |
| fungi | under the current ptgbot design, i think you'd need to create a new track for that | 18:57 |
| gmann | but with new track too how to show project name for which that operator hour is reserved for | 19:04 |
| fungi | you're asking for an extra dimension of data which the bot currently doesn't have in its data model | 19:07 |
| fungi | you could flatten the 2d array you're imagining into a list of project-ops specific tracks, i guess | 19:08 |
| fungi | so an ops-nova track, an ops-cinder track, and so on | 19:08 |
| fungi | then just unbook whatever placeholder track is used and book the slot for the specific track instead | 19:09 |
| fungi | that's just one idea though, maybe others have alternative suggestions | 19:10 |
| fungi | i would caution against any significant redesign work on the bot though, given it's already effectively in use for the upcoming ptg. if we want a more descriptive data model for scheduling, we should plan that for the first 2023 ptg and work on implementation and testing soon after the upcoming ptg is over | 19:11 |
| gmann | Yeah adding all separate track is one option but I wanted to avoid that if we have tag ability to add per slot | 19:21 |
| gmann | something like trackX book slotX tagX and the ptg bot shows slotX as "trackX: tagX" | 19:23 |
| gmann | basically adding tag in book command and show it in slot box | 19:24 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!