Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2024-11-29
19:57:29 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:58:27 gmann sean-k-mooney[m]: did not get. you mean some short url in Topic?
19:59:35 sean-k-mooney[m] in the topic or docs like with the reqirment redirects
19:59:39 ildikov gmann: I'm ok with your link placement, but the process still needs to be outlined
19:59:52 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
20:00:28 gmann ildikov: we do have that right, I mean all detail doc can be linked from contributing.html
20:00:40 gmann contributing.html is also shown as first page on github repo
20:01:06 ildikov sure, that works
20:01:19 sean-k-mooney[m] im fine with just updating it in the doc each release too
20:01:26 sean-k-mooney[m] so we dont have to make it fancy
20:01:57 gmann yeah and this way it can be referred from non-IRC users also
20:03:22 opendevreview Ildiko Vancsa proposed openstack/nova master: Update contributor process documentation https://review.opendev.org/c/openstack/nova/+/936759
20:03:52 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:58 gmann sean-k-mooney[m]: ildikov ^^ like this?
20:04:48 sean-k-mooney[m] if we are going to update the topic then a direct link is beter
20:05:08 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:11 sean-k-mooney[m] i.e. lets not send them to the docs just to send them else where
20:05:35 sean-k-mooney[m] i would personally would be annoyed by that but that just me
20:06:17 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:22 sean-k-mooney[m] we can see what others think next week in the team meeting \
20:06:43 gmann ++
20:06:54 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:07:21 sean-k-mooney[m] well the ehterpad as i said is not required
20:07:22 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:43 sean-k-mooney[m] its just an extra place to help the core reviews to organise some things
20:07:57 sean-k-mooney[m] itis somethign i personally dont partically like
20:08:10 sean-k-mooney[m] but it helps sylvain so we have it
20:08:31 gmann for me, Topic users are more of new people, anyone already know Nova ask core or in meeting
20:09:16 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:45 sean-k-mooney[m] i normally only look at it for the link to the ehterpad
20:09:50 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:58 gmann ohk
20:10:04 sean-k-mooney[m] i.e. form when it used to have the runway etherpad link
20:10:13 gmann i see
20:10:33 sean-k-mooney[m] but thats just mucel memory becuase it used ot be there when we were on freenode
20:10:43 sean-k-mooney[m] most probaly dont
20:10:54 sean-k-mooney[m] the other thing i check it for is is there a meeting currently
20:11:03 sean-k-mooney[m] i.e when joining a differnt channle before talking
20:11:20 sean-k-mooney[m] but ya im not sure new commers would do that
20:11:53 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:13:13 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:55 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:14:24 ildikov I loved IRC when I joined the community, I used it a little bit in high school
20:14:46 ildikov but I joined OpenStack over a decade now...
20:14:51 ildikov crazy to think about it
20:15:03 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:09 opendevreview Artom Lifshitz proposed openstack/nova-specs master: WIP: vTPM live migration https://review.opendev.org/c/openstack/nova-specs/+/936775
20:15:11 ildikov and the chat tool landscape only got crazier since then
20:17: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:53 ildikov oh wow
20:18:35 ildikov I had a few chats with lawyers, but it still wasn't *that* bad
20:19:26 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:20:40 ildikov yeah, I can see how it's hard when there's an internal process that someone could map to code contribution
20:21:38 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:52 sean-k-mooney[m] a lot has changed since 2013
20:22:49 sean-k-mooney[m] it might be worth puthing the link to the contibutor page in the readme of the git repo too
20:23:01 sean-k-mooney[m] honestly that always the first thing i read for any project
20:24:57 sean-k-mooney[m] we kind of do i guess but CONTRIBUTING.rst is not a link to the doc
20:38:11 ildikov one thing to keep in mind though is that the link needs to be updated periodically
20:39:51 ildikov so the more places it appears, the harder the maintenance gets
20:43:51 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:44:28 gmann getting into the ML, IRC is very minimum effort to get in but knowing details about team, contribution etc is not
20:46:32 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:47:54 ildikov what meant was, if someone got into the IRC channel, that likely means that they found the contributors documentation
20:48:14 ildikov whether they found Nova's specific docs or the overall contributor guide, that's still an open question
20:49:09 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
21:54:54 gmann This is nova specific guide not general how-to-contribute docs https://docs.openstack.org/nova/latest/contributor/contributing.html
21:55:11 gmann contributing.html in all project is project specific process guide
22:44:44 opendevreview Merged openstack/nova master: Support rescuing an instance with shares https://review.opendev.org/c/openstack/nova/+/860287
#openstack-nova - 2024-11-30
02:44:52 opendevreview Merged openstack/nova master: Replace distutils https://review.opendev.org/c/openstack/nova/+/936067
02:52:01 opendevreview Merged openstack/nova master: Drop usage of pkg_resources https://review.opendev.org/c/openstack/nova/+/931312
02:55:02 opendevreview Merged openstack/nova master: Fix broken link https://review.opendev.org/c/openstack/nova/+/931663
04:02:32 opendevreview Merged openstack/nova master: api: Add response body schemas for host aggregate actions API https://review.opendev.org/c/openstack/nova/+/924584
15:09:49 opendevreview Takashi Kajinami proposed openstack/nova master: Deprecate [wsgi] secure_proxy_ssl_header https://review.opendev.org/c/openstack/nova/+/817927
19:22:29 gmann sean-k-mooney[m]: base jobs are now migrated to Noble, can you check these two https://review.opendev.org/c/openstack/osc-placement/+/935579 https://review.opendev.org/c/openstack/placement/+/935581
20:14:17 sean-k-mooney[m] gmann: done
20:14:38 gmann thanks
22:01:02 opendevreview Merged openstack/placement master: Update gate jobs as per the 2025.1 cycle testing runtime https://review.opendev.org/c/openstack/placement/+/935581
23:15:35 opendevreview Merged openstack/nova master: Update gate jobs as per the 2025.1 cycle testing runtime https://review.opendev.org/c/openstack/nova/+/932648
#openstack-nova - 2024-12-01
07:31:33 kevko sean-k-mooney[m]: I fixed rebuild for volume backed root volume I've asked you :) -> https://paste.openstack.org/show/bviZuXSaoTdCdrbtekRx/
07:31:46 kevko sean-k-mooney[m]: thank you for discuss
#openstack-nova - 2024-12-02
10:40:43 s3rj1k sean-k-mooney: Hi, where you able to tackle that change you proposed about distributed discovery?
10:43:03 sean-k-mooney i didnt actully start on a real implemantation beyond the psudo code we discussed. i dont think it would be particallary hard to do im just not sure ill have time to do it
10:43:48 s3rj1k I am interested to test it out, just in case :)
10:45:17 sean-k-mooney if i can find an hour or two this week i may throw up a poc and you can let me know if it works for you, im going on pto for the rest of the year wednesday next week so there are a few things i need to do before then
10:46:20 s3rj1k sounds good, thanks
13:05:14 opendevreview Balazs Gibizer proposed openstack/placement master: WIP: Round-robin candidate generation https://review.opendev.org/c/openstack/placement/+/936832
13:14:04 opendevreview Merged openstack/nova master: Deprecate [wsgi] secure_proxy_ssl_header https://review.opendev.org/c/openstack/nova/+/817927
14:36:13 sean-k-mooney bauzas: Uggla: comments left on https://review.opendev.org/c/openstack/nova-specs/+/936407, im kind of furstrated that many of the things i requested durign the ptg dicsssion where not done. with that said reading back over the ptg note we did not recored all the thigns we agreed and some of the things that were "agreed" are wrong so i can understand where some of the
14:36:15 sean-k-mooney confution comes form
14:37:06 sean-k-mooney if i recall correctly i joined that topic about 10 mins in and wehn i did the direction changed significanlty
14:37:24 sean-k-mooney it looks like we didnt remove the previosu agrrements that happend before i was involved
15:02:16 bauzas sean-k-mooney: thanks for your comments, as a reminder, this was a WIP but once the spec is updated, we'll tell you
15:02:34 bauzas sean-k-mooney: if you think we missed a specific action item on the PTG etherpad, please tell me
15:04:04 sean-k-mooney there are 3 points that seam to have been missed. 1.) i asked that the spec not be GPU specific, 2 that the live migration and general supprot be called out spereatly in tow differnt sections, 3.) that pci in placment should be optional
15:04:04 opendevreview Merged openstack/nova master: api: Add response body schemas for host aggregate APIs https://review.opendev.org/c/openstack/nova/+/924585
15:05:32 sean-k-mooney the spec does not yet cover the live mgiration changes, yet the usecase refence it so i was expecting the current draft to cover the non live migration usecases/constrains and then for the live migration aspect to be added leater
15:07:24 sean-k-mooney im fine with discussing the generic enabling and live migration at the same time but given i expect those to be delvier potentiall in diffent relases i want to make sure we are clear on what is required for each case
15:07:38 sean-k-mooney i would hope we can do both in epoxy
15:07:53 sean-k-mooney but i dont want to require both to merge anything

Earlier   Later