| opendevreview | Michael Still proposed openstack/nova master: libvirt: direct SPICE console object changes https://review.opendev.org/c/openstack/nova/+/926876 | 04:22 |
|---|---|---|
| opendevreview | Michael Still proposed openstack/nova master: libvirt: direct SPICE console database changes https://review.opendev.org/c/openstack/nova/+/926877 | 04:22 |
| opendevreview | Michael Still proposed openstack/nova master: libvirt: allow direct SPICE connections to qemu https://review.opendev.org/c/openstack/nova/+/924844 | 04:22 |
| opendevreview | Michael Still proposed openstack/nova master: libvirt: Add extra spec for sound device. https://review.opendev.org/c/openstack/nova/+/926126 | 04:22 |
| opendevreview | Michael Still proposed openstack/nova master: libvirt: Add extra specs for USB redirection. https://review.opendev.org/c/openstack/nova/+/927354 | 04:22 |
| r-taketn | Hello. We are planning to contribute a new feature for building Arm-Confidential Computing Architecture(CCA)-enabled instances. Could you please review the following e-mail? (sorry, mail title is bad) https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/244U52T3HINVWUFSMPMA45A67BUPAQGK/ I'm not sure it is acceptable for OpenStack because Arm-CCA enabled hardware is not yet available to our knowledge. | 10:35 |
| r-taketn | Your feedback on the acceptance of this contribution would be greatly appreciated. | 10:35 |
| opendevreview | Merged openstack/nova master: Add helper methods to rescue/unrescue shares https://review.opendev.org/c/openstack/nova/+/860286 | 14:47 |
| kevko | Hi folks, trying to snapshot whole instance (which will produce 0 bytes glance image with metadata + cinder volume snapshot) ...i am using ceph, when i want to rebuild the server with openstack server rebuild --reimage-boot-volume --image ${server_snapshot} --os-compute-api-version 2.93 ${server_id} it is failing with something like this | 14:50 |
| kevko | https://paste.openstack.org/show/bMAK9nICw823XtdGaFaG/ | 14:50 |
| kevko | any help please ? | 14:51 |
| kevko | I can see that it's trying to process 0 bytes image from glance ... | 14:51 |
| kevko | what i am doing bad ? | 14:51 |
| kevko | some ceph settings ? copy on write ? what :( ? | 14:51 |
| kevko | can anybody help ? thank you very much | 14:51 |
| sean-k-mooney | kevko: this is a boot form volume instance correct | 14:54 |
| sean-k-mooney | the boot form volume image rebuild was mainly implemeted for rebuilding form a normal image not a snapshot | 14:56 |
| sean-k-mooney | not both shoudl be supprotable | 14:56 |
| sean-k-mooney | but im not sure how well tested this is and if it works today. | 14:56 |
| sean-k-mooney | im not sure if https://review.opendev.org/c/openstack/nova/+/930754 would adress this or not | 14:58 |
| kevko | sean-k-mooney: this is my script to test | 14:58 |
| kevko | https://paste.openstack.org/show/bpEXTVEN6E6Jc0ZTnXta/ | 14:59 |
| sean-k-mooney | ok so you takign the server create form precreated volume flow | 14:59 |
| sean-k-mooney | which is one of the two boot form volume workflows | 15:00 |
| sean-k-mooney | then your creating a normla snapshot and then rebuildign to that | 15:00 |
| kevko | sean-k-mooney: yeah, that should work no ? | 15:00 |
| kevko | it's kinda a new feature to rebuild with cinder backed volume ...from 2.93 microversion | 15:01 |
| kevko | I will be very grateful if you help me :) | 15:01 |
| sean-k-mooney | so the reason im hesitating is i dont know if that supprot the special optimiation that we do when cinder and glance share the same storage backend | 15:02 |
| sean-k-mooney | cidner and glance need to be configured in a spefic way in general to allwo them to do thing snaphosts when creatign new voluems form an image/snapshot for example | 15:04 |
| sean-k-mooney | the main testing around https://specs.openstack.org/openstack/nova-specs/specs/zed/implemented/volume-backed-server-rebuild.html i belive was done with out ceph | 15:04 |
| sean-k-mooney | so glance on file/swirft and cidner on lvm | 15:05 |
| kevko | sean-k-mooney: i was able to catch incoming files with rsync in infinity loop | 15:05 |
| kevko | sean-k-mooney: https://ibb.co/KK2KzfR | 15:05 |
| kevko | sean-k-mooney: so i was wondering if there is some bug maybe ? because there is a 0 bytes image and also bigger one (cirros) | 15:05 |
| sean-k-mooney | so what the cinder backend shoudl be doing in this case is the volume snapshot shoudl be creating a snapshot in ceph | 15:06 |
| kevko | sean-k-mooney: https://ibb.co/F4NJDhB | 15:07 |
| sean-k-mooney | and hten the rebuidl on the cider driver side should be just askign ceph to restore it | 15:07 |
| sean-k-mooney | there should be no data trasfer in either code path in this case | 15:07 |
| kevko | https://ibb.co/48gFG7f << attempt to import 0 bytes image into volumes pool | 15:07 |
| sean-k-mooney | yep which impleis that you have an issue in how you have configred cinder an glance to tlak to each other | 15:08 |
| sean-k-mooney | you are using the same ceph cluster for glance and cinder correct? | 15:08 |
| kevko | sean-k-mooney: sure, I'm not an expert ... but at least I'm trying to follow the threads and I'm getting further and further ... and it's strange that internal Ceph isn't used ... and that the data is being copied... That also seemed strange to me. | 15:09 |
| kevko | sean-k-mooney: yes, same cluster ... | 15:09 |
| sean-k-mooney | https://docs.openstack.org/cinder/latest/admin/volume-backed-image.html | 15:10 |
| kevko | sean-k-mooney: what do you think how i configured glance<->cinder to talk each other ? | 15:10 |
| sean-k-mooney | have you confiugred glance ot supprot volume backed images | 15:10 |
| sean-k-mooney | kevko: this is really not a nova issue by the way the error is on the cinder side | 15:10 |
| sean-k-mooney | i belvie you need to configure that for https://specs.openstack.org/openstack/cinder-specs/specs/liberty/clone-image-in-glance-cinder-backend.html to work | 15:12 |
| kevko | sean-k-mooney: this is my conf https://paste.openstack.org/show/bc0ZzJIdENRaizbJR1vG/ | 15:13 |
| sean-k-mooney | part of me hopes SECRET_OMMITED is the acutal password and your are just trolling peopel :P | 15:14 |
| kevko | :D | 15:14 |
| kevko | that's not my pass :P | 15:14 |
| kevko | hahaaha | 15:15 |
| sean-k-mooney | it would make me sad if it was becasue now you woudl have to change it | 15:15 |
| kevko | sean-k-mooney: i know what i am doing :) | 15:15 |
| kevko | only this snapshots i am debuggign 2 days and dont' know what else i can try | 15:15 |
| sean-k-mooney | so im not an expert ofn this but looking at your config, glance is not configured to show "show_multiple_locations" | 15:15 |
| sean-k-mooney | which mean that cidner cant detect that its the same ceph cluster | 15:16 |
| sean-k-mooney | and it can jsut ask ceph to do the restore | 15:16 |
| sean-k-mooney | the issue with show_multiple_locations is that it has security implciations | 15:16 |
| sean-k-mooney | it makes the ceph storage url "rbd://..." visable n the responce to a normal user | 15:17 |
| kevko | sean-k-mooney: oh god, please say to me that i just made a mistake and kolla is somehow merging those two files in bad way :D | 15:18 |
| kevko | sean-k-mooney: https://paste.openstack.org/show/b6A2uTpzPSWzs0EOl5iE/ | 15:18 |
| kevko | sean-k-mooney: yeah i know what is the option ..i had it ... | 15:18 |
| kevko | sean-k-mooney: but add raw formats to another file ..so wondering if it is not owervwiting | 15:18 |
| sean-k-mooney | i have a backup of my kolla config somewher let me see where i set that | 15:19 |
| sean-k-mooney | my most recent install currently does not have cinder for reasons | 15:19 |
| kevko | let me reconfigure and test | 15:23 |
| sean-k-mooney | oh the host with that backup is currently booted inot windows | 15:23 |
| sean-k-mooney | i think /etc/kolla/config/glance-api.conf is correct | 15:23 |
| kevko | sean-k-mooney: yeah, but you can also store into /etc/kolla/config/glance.conf | 15:24 |
| kevko | then it's applied to all glance configs | 15:24 |
| sean-k-mooney | right i was going to check the precedence | 15:24 |
| kevko | and i don't have cache ..so ..it doesn't matter where it is .. | 15:24 |
| kevko | yes | 15:24 |
| kevko | this is btw disabled in kolla by default ..because then the locations are visible for users ..which is not good | 15:25 |
| kevko | i need to implement the fix | 15:25 |
| sean-k-mooney | https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/glance/tasks/config.yml#L61-L76 | 15:25 |
| sean-k-mooney | its looking for "{{ node_custom_config }}/glance/glance-api.conf" | 15:26 |
| sean-k-mooney | not /etc/kolla/config/glance-api.conf | 15:26 |
| kevko | yeah i know :) | 15:26 |
| kevko | that's the reason why I ve said oh god :D | 15:26 |
| kevko | i've spotted it | 15:26 |
| sean-k-mooney | ah | 15:26 |
| kevko | my test is running now | 15:27 |
| sean-k-mooney | i have done that before... | 15:27 |
| sean-k-mooney | forgot to create the service folder | 15:27 |
| sean-k-mooney | one of the things i like most about kolla is its config system | 15:28 |
| sean-k-mooney | but i woudl be lying if i said i never put the file in the worng place | 15:28 |
| kevko | sean-k-mooney: yeah i like it also, but i've also find some bugs in past ... especially with merge ini files | 15:29 |
| * kevko is eagerly waiting and quickly goes for a cigarette. | 15:29 | |
| sean-k-mooney | the ini merging was there before i got invovled but the yaml merging is my fault :) although i did take insperation form the ini version | 15:32 |
| kevko | sean-k-mooney: error :) | 15:44 |
| kevko | sean-k-mooney: same error | 15:44 |
| opendevreview | Ildiko Vancsa proposed openstack/nova master: Update contributor process documentation https://review.opendev.org/c/openstack/nova/+/936759 | 15:51 |
| ildikov | sean-k-mooney: bauzas: I created the patch to update the contributor docs ^^ | 15:55 |
| sean-k-mooney | kevko: with a newly created vm | 15:55 |
| sean-k-mooney | ildikov: yep i just saw eamil notificaton come in, thansk for takign the time to start on that | 15:56 |
| sean-k-mooney | ill be finishing soso but ill try and take a look before i leave for today | 15:56 |
| ildikov | sean-k-mooney: bauzas: I deleted the parts we said are outdated, but I don't know how people are supposed to find the tracking etherpad and interact with it, so I wasn't able to write that part myself | 15:56 |
| ildikov | sean-k-mooney: no rush, thank you for adding it to your todo list | 15:56 |
| sean-k-mooney | ildikov: the delete look correct but ya we shoudl add a short paragah on how to use the etherpad | 15:57 |
| ildikov | sean-k-mooney: great! And yes, I'm hoping to rely on you and bauzas to type up that paragraph. | 15:58 |
| sean-k-mooney | its basiclly add you reivw by addign a new bullet under the correct section with a link to the bug/bluepirnt in lanchpad then under that add either a link to the gerrit topic or each patch | 15:58 |
| sean-k-mooney | you can also addd a short note like needs second +2 or simlar | 15:59 |
| sean-k-mooney | we dont actully have a copypaste template to use but we proably can add one | 15:59 |
| sean-k-mooney | the last thing i woudl suggest peopel do is ping use on irc (via matrix bride if that is easier) to let us know but lests see what bauzas things | 16:00 |
| ildikov | 'copypaste template' to easily add a new entry you mean? | 16:00 |
| sean-k-mooney | *thinks | 16:00 |
| sean-k-mooney | ildikov: yep | 16:01 |
| ildikov | ok, cool | 16:01 |
| sean-k-mooney | you can see that each itme is basiclly just this | 16:01 |
| sean-k-mooney | https://blueprints.launchpad.net/nova/+spec/openapi-2 | 16:01 |
| sean-k-mooney | https://review.opendev.org/q/topic:%22openapi%22+project:openstack/nova | 16:01 |
| sean-k-mooney | awaiting reviews | 16:01 |
| sean-k-mooney | i.e. the lauchpad tarcker, followed by a gerrit link and then a note | 16:02 |
| sean-k-mooney | https://etherpad.opendev.org/p/nova-2025.1-status#L33 | 16:02 |
| ildikov | oh yeah, that can make sense to template | 16:02 |
| ildikov | how can people find the etherpad? | 16:03 |
| sean-k-mooney | i tend to also add teh title after the bug link in teh case of a bug so you know what it is before you click | 16:03 |
| ildikov | if we add the link to the doc, then it needs to be updated at the beginning of every release cycle | 16:03 |
| sean-k-mooney | ildikov: so we can add a link to the current release | 16:03 |
| sean-k-mooney | ya | 16:03 |
| sean-k-mooney | also i might be going senile in my mid 30s but i tought it used to be in the topic or the irc channel | 16:04 |
| sean-k-mooney | when we used runways it definatlly was | 16:04 |
| sean-k-mooney | but i think when we moved form freenode to oftc we lost the ablity to have per channel topics in the same way | 16:05 |
| sean-k-mooney | so i would like to add it to the channel topic if we can i just dont know where/host to do that | 16:05 |
| ildikov | yeah, that would be great to have it in the IRC channel header as well | 16:06 |
| sean-k-mooney | i dont have op here but maybe we can ask infra about htat | 16:07 |
| sean-k-mooney | basically somethign liek "This channel is for Nova development https://etherpad.opendev.org/p/nova-2025.1-status. For support of Nova deployments, please use #openstack" | 16:07 |
| sean-k-mooney | or "This channel is for Nova development | development-planning: https://etherpad.opendev.org/p/nova-2025.1-status" | 16:08 |
| ildikov | I'll try to figure that out | 16:16 |
| ildikov | apparently you don't need op to make that change, but I wasn't able to | 16:16 |
| ildikov | I think my nick name is not registered anymore, which might be the issue | 16:17 |
| sean-k-mooney | i had the same issue but my nic is defintly registered | 16:39 |
| sean-k-mooney | i get "#openstack-nova: You're not channel operator" | 16:41 |
| sean-k-mooney | when i try | 16:41 |
| sean-k-mooney | bybe we need to message ChanServ to do this instead of using /topic | 16:45 |
| sean-k-mooney | *maybe | 16:45 |
| ildikov | could be | 16:52 |
| ildikov | can check with OpenDev folks next week | 16:52 |
| sean-k-mooney | i tried setting it via chanserve and the TOPIC comamnd is not availbale | 16:53 |
| ildikov | yeah, I got to that point too | 16:56 |
| sean-k-mooney | we do not have autoop enabled iether but most of the infra folks are listed as channle masters so we can always ask them to change it | 16:56 |
| sean-k-mooney | but ya let leave them enjoy there break | 16:57 |
| ildikov | +1 :) | 16:57 |
| sean-k-mooney | #topic "This channel is for Nova development | development-planning: https://etherpad.opendev.org/p/nova-2025.1-status" | 17:00 |
| ildikov | I have an appointment, I'll add the paragraph we talked about to the docs patch afterward | 17:01 |
| sean-k-mooney | :( i was wondering if meetbot was listing outside of meeting but i guess i cant hack the system tyat way | 17:01 |
| sean-k-mooney | ack no rush thanks for doing this o/ | 17:01 |
| ildikov | good try though! :) | 17:01 |
| ildikov | sure thing, happy to help! | 17:02 |
| ildikov | if you're not around by the time I'm back, have a nice weekend! | 17:02 |
| *** ChanServ changes topic to "This channel is for Nova development | development-planning: https://etherpad.opendev.org/p/nova-2025.1-status" | 18:03 | |
| *** ChanServ changes topic to "This channel is for Nova development | development-planning: https://etherpad.opendev.org/p/nova-2025.1-status | this channel is logged at https://meetings.opendev.org/irclogs/%23openstack-nova/" | 18:06 | |
| frickler | sean-k-mooney: ildikov: ^^ like that? | 18:10 |
| ildikov | frickler: Thank you for the update! | 18:27 |
| ildikov | There was one note about using the #openstack channel, prolly for ops questions. Not sure if the team wants to keep that over logs. | 18:28 |
| ildikov | Other than that the change looks good to me | 18:29 |
| gmann | sean-k-mooney: ildikov I think instead of cycle specific etherpad in topic, we should add this page https://docs.openstack.org/nova/latest/contributor/contributing.html | 19:31 |
| gmann | and etherpad of every cycle can be updated in this page. The main goal of this page is to 'have everything what new contributors need or current status of Nova processs/tasks' | 19:32 |
| opendevreview | Ildiko Vancsa proposed openstack/nova master: Update contributor process documentation https://review.opendev.org/c/openstack/nova/+/936759 | 19:41 |
| opendevreview | Artom Lifshitz proposed openstack/nova-specs master: WIP: vTPM live migration https://review.opendev.org/c/openstack/nova-specs/+/936775 | 19:43 |
| opendevreview | Artom Lifshitz proposed openstack/nova-specs master: WIP: vTPM live migration https://review.opendev.org/c/openstack/nova-specs/+/936775 | 19:44 |
| opendevreview | Artom Lifshitz proposed openstack/nova-specs master: WIP: vTPM live migration https://review.opendev.org/c/openstack/nova-specs/+/936775 | 19:44 |
| opendevreview | Ghanshyam proposed openstack/nova master: Add current release task tracking etherpad in contributing.html https://review.opendev.org/c/openstack/nova/+/936776 | 19:52 |
| gmann | sean-k-mooney: ildikov ^^ something like this and then add this page in channel Topic as a single place to get all information https://docs.openstack.org/nova/latest/contributor/contributing.html | 19:55 |
| sean-k-mooney[m] | gmann: the spec repo supprts redirect so maybe we could have a short like or something to the current on | 19:57 |
| gmann | sean-k-mooney[m]: did not get. you mean some short url in Topic? | 19:58 |
| sean-k-mooney[m] | in the topic or docs like with the reqirment redirects | 19:59 |
| ildikov | gmann: I'm ok with your link placement, but the process still needs to be outlined | 19:59 |
| gmann | sean-k-mooney[m]: cinder channel use https://tiny.cc/ to short the url but I am not sure if that is good idea and how long tiny.cc can hold/support url | 19:59 |
| gmann | ildikov: we do have that right, I mean all detail doc can be linked from contributing.html | 20:00 |
| gmann | contributing.html is also shown as first page on github repo | 20:00 |
| ildikov | sure, that works | 20:01 |
| sean-k-mooney[m] | im fine with just updating it in the doc each release too | 20:01 |
| sean-k-mooney[m] | so we dont have to make it fancy | 20:01 |
| gmann | yeah and this way it can be referred from non-IRC users also | 20:01 |
| opendevreview | Ildiko Vancsa proposed openstack/nova master: Update contributor process documentation https://review.opendev.org/c/openstack/nova/+/936759 | 20:03 |
| gmann | channel topic as "This channel is for Nova development | development process, planning: https://docs.openstack.org/nova/latest/contributor/contributing.html | this channel is logged at https://meetings.opendev.org/irclogs/%23openstack-nova/ " | 20:03 |
| gmann | sean-k-mooney[m]: ildikov ^^ like this? | 20:03 |
| sean-k-mooney[m] | if we are going to update the topic then a direct link is beter | 20:04 |
| gmann | contributing.html is more consistent across all the openstack projects so it will be easy to have i fill/link with all required info | 20:05 |
| sean-k-mooney[m] | i.e. lets not send them to the docs just to send them else where | 20:05 |
| sean-k-mooney[m] | i would personally would be annoyed by that but that just me | 20:05 |
| gmann | sean-k-mooney[m]: but etherpad as direct link is just a one information to them but to know complete process of team/contact detail/how to merge patch etc are in contributing.html | 20:06 |
| sean-k-mooney[m] | we can see what others think next week in the team meeting \ | 20:06 |
| gmann | ++ | 20:06 |
| ildikov | it depends on whether the assumption is that most people who got to this channel already know some of the basics and would benefit from the direct link to development planning | 20:06 |
| sean-k-mooney[m] | well the ehterpad as i said is not required | 20:07 |
| ildikov | or if we expect more people popping up here still being in need of the top-level doc for how to contribute | 20:07 |
| sean-k-mooney[m] | its just an extra place to help the core reviews to organise some things | 20:07 |
| sean-k-mooney[m] | itis somethign i personally dont partically like | 20:07 |
| sean-k-mooney[m] | but it helps sylvain so we have it | 20:08 |
| gmann | for me, Topic users are more of new people, anyone already know Nova ask core or in meeting | 20:08 |
| gmann | For example, how many of us who are active in IRC/project read the Topic. I have not for many channel I am active in | 20:09 |
| sean-k-mooney[m] | i normally only look at it for the link to the ehterpad | 20:09 |
| gmann | this is more of new people who want to join this channel can know about what this channel is for and how to get involved | 20:09 |
| gmann | ohk | 20:09 |
| sean-k-mooney[m] | i.e. form when it used to have the runway etherpad link | 20:10 |
| gmann | i see | 20:10 |
| sean-k-mooney[m] | but thats just mucel memory becuase it used ot be there when we were on freenode | 20:10 |
| sean-k-mooney[m] | most probaly dont | 20:10 |
| sean-k-mooney[m] | the other thing i check it for is is there a meeting currently | 20:10 |
| sean-k-mooney[m] | i.e when joining a differnt channle before talking | 20:11 |
| sean-k-mooney[m] | but ya im not sure new commers would do that | 20:11 |
| ildikov | getting into this channel is not trivial for a newcomer, so my assumption is that they probably already got through some contributor documentation before getting here | 20:11 |
| sean-k-mooney[m] | its funny becuase this was actully one of the eaiser things to get invovled in when i first stated | 20:13 |
| sean-k-mooney[m] | i had nver used irc before working on openstack and i remember that being one of the eaiser things to get set up | 20:13 |
| ildikov | I loved IRC when I joined the community, I used it a little bit in high school | 20:14 |
| ildikov | but I joined OpenStack over a decade now... | 20:14 |
| ildikov | crazy to think about it | 20:14 |
| sean-k-mooney[m] | getting my company to approve the icla, removing the email fotter on all company emails or allow code submition took months | 20:15 |
| opendevreview | Artom Lifshitz proposed openstack/nova-specs master: WIP: vTPM live migration https://review.opendev.org/c/openstack/nova-specs/+/936775 | 20:15 |
| ildikov | and the chat tool landscape only got crazier since then | 20:15 |
| sean-k-mooney[m] | no joke when i first started working on openstack intel required me to email a set of virus scan reulst to a qe person before ei could submit a patch to gerrit…. | 20:17 |
| ildikov | oh wow | 20:17 |
| ildikov | I had a few chats with lawyers, but it still wasn't *that* bad | 20:18 |
| sean-k-mooney[m] | it took 6 months to explain why that was entirly unworkable. at the time they site i was working on didnt really have expirnce with doing code contibutions to upstream and condierd each a release as if we were putting the contibution on intel.com to download | 20:19 |
| ildikov | yeah, I can see how it's hard when there's an internal process that someone could map to code contribution | 20:20 |
| sean-k-mooney[m] | we had to do the full secure software development lifecyle review and get leagal sign off on the licene and icla terms ecta. so anyway thats all in the past | 20:21 |
| sean-k-mooney[m] | a lot has changed since 2013 | 20:21 |
| sean-k-mooney[m] | it might be worth puthing the link to the contibutor page in the readme of the git repo too | 20:22 |
| sean-k-mooney[m] | honestly that always the first thing i read for any project | 20:23 |
| sean-k-mooney[m] | we kind of do i guess but CONTRIBUTING.rst is not a link to the doc | 20:24 |
| ildikov | one thing to keep in mind though is that the link needs to be updated periodically | 20:38 |
| ildikov | so the more places it appears, the harder the maintenance gets | 20:39 |
| gmann | ildikov: maybe but not 100% true. In upstream training we used to tell this is IRC and how you can join it but that does not mean they know about team, its process and details | 20:43 |
| gmann | getting into the ML, IRC is very minimum effort to get in but knowing details about team, contribution etc is not | 20:44 |
| ildikov | I did not mean to say that it is harder to get into IRC than all the other things people need to contribute code, docs, etc | 20:46 |
| ildikov | what meant was, if someone got into the IRC channel, that likely means that they found the contributors documentation | 20:47 |
| ildikov | whether they found Nova's specific docs or the overall contributor guide, that's still an open question | 20:48 |
| ildikov | but, they likely found where some of the how-to-contribute docs lives and can use those to get into the process side of things | 20:49 |
| gmann | This is nova specific guide not general how-to-contribute docs https://docs.openstack.org/nova/latest/contributor/contributing.html | 21:54 |
| gmann | contributing.html in all project is project specific process guide | 21:55 |
| opendevreview | Merged openstack/nova master: Support rescuing an instance with shares https://review.opendev.org/c/openstack/nova/+/860287 | 22:44 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!