Earlier  
Posted Nick Remark
#openstack-nova - 2020-04-22
13:31:03 sean-k-mooney bauzas: it makes verioning harder which is the only reason i dont want to defautl to that but we can discuss in the spec later
13:31:20 bauzas sean-k-mooney: we have a couple of versioned objects you know
13:31:26 bauzas and we have versioned libs
13:31:58 sean-k-mooney yes but i want you to be able to say give me hw:profile=realtime-vicoria in W or Z
13:32:03 bauzas but this sounds a rathole to discuss this now :D
13:32:36 bauzas let's draft the UX in the spec ;)
13:32:39 sean-k-mooney where hw:profile woudl be an alias to the latest version of a profile
13:32:44 sean-k-mooney yep
13:32:57 sean-k-mooney anyway this was just an fyi that im starting to draft this
13:33:03 bauzas I'm not an API specialist, but I don't like explicit versioning on the flavor extraspec itself
13:33:09 bauzas but yeah, shoot
13:37:55 gmann gibi: stephenfin updated the policy doc, please re-look - https://review.opendev.org/#/c/720129/12
13:40:30 aarents bauzas: ok thks
13:41:22 bauzas aarents: are you able to attend the virtual PTG ?
13:49:18 aarents bauzas: probably yes
13:49:59 aarents bauzas: I will dig soon the patch you share on bug report, if it can solve the issue
13:50:13 bauzas which one ?
13:50:33 aarents https://review.opendev.org/#/c/609180/
13:56:20 bauzas aarents: ah you mean you'll try to conf setting ? sure, lemme know if this alleviates your issue
13:56:24 lyarwood elod: looking
13:56:31 bauzas you'll try the*
13:56:39 lyarwood elod: btw feel free to add me directly in these reviews in the future or anything really on stable :)
13:57:46 aarents bauzas: yep
13:58:50 elod lyarwood: oh, I forgot to add you to this :S and thanks, will do in the future :)
13:59:52 bauzas lyarwood: this sounds a configuration problem, nope ? 2019-09-05 16:08:30.057 8 ERROR nova.volume.cinder [req-522cbf47-a65a-4d46-8852-01adcfcbda2f - - - - -] The [cinder] section of your nova configuration file must be configured for authentication with the block-storage service endpoint.
14:00:14 bauzas lyarwood: context is https://bugs.launchpad.net/nova/+bug/1843643
14:00:14 openstack Launchpad bug 1843643 in OpenStack Compute (nova) "VM on encrypted boot volume fails to start after compute host reboot" [Undecided,New]
14:00:19 bauzas lyarwood: I'm litterally 2 mins away from closing this bug
14:00:43 bauzas (comment #4 in the stacktrace)
14:02:59 lyarwood bauzas: if having that section configured allows n-cpu during init_host to have a valid admin context for grabbing secrets from barbican then yes
14:03:31 lyarwood bauzas: I think it might, I'd have to dig into the context code again as it has been a while
14:03:32 bauzas lyarwood: refresh the bug and see my comment
14:04:29 bauzas but I'm not a ksa specialist
14:04:57 lyarwood bauzas: yeah so I assume that would allow n-cpu itself to auth correctly, do we set that typically in devstack?
14:05:17 lyarwood yeah we do
14:05:58 bauzas lyarwood: well, if you don't, I don't see how you can get service tokens...
14:06:49 lyarwood bauzas: right
14:07:25 bauzas okay, closing the bug, asking the reporter to reopen the bug if fixing this doesn't help
14:07:27 bauzas done.
14:13:53 bauzas gibi: one day, we'll have to discuss what to do with bugs open since 2 years
14:14:33 gibi bauzas: ack, please add a line to the ptg etherpad and then we can start an ML discusison
14:14:43 gibi before the pt
14:14:43 gibi g
14:14:51 bauzas not sure I wanna be the messenger :D
14:14:57 gibi OK, I will do it :D
14:15:08 bauzas gibi: there is no rush
14:15:30 gibi I mean I will now add a line to the etherpad and later will think about an ML message
14:15:52 bauzas fwiw, we made it once, for example https://bugs.launchpad.net/nova/+bug/1018253/comments/5
14:15:52 openstack Launchpad bug 1018253 in OpenStack Dashboard (Horizon) "No error message prompt during attaching when mountpoint is occupied" [Wishlist,New]
14:17:29 gibi bauzas: yepp
14:17:52 gibi anyhow added a line to the ptg etherpad
14:17:59 bauzas and I just provided this example
14:18:20 bauzas gibi: go back to your downstream work, man !
14:18:24 bauzas :D
14:18:42 gibi :)
14:19:35 lyarwood sigh we need to kill mountpoint in the API
14:19:53 lyarwood now that we have attachments
14:23:32 bauzas lyarwood: feel free to triage this bug, not on my radar yet :)
14:32:07 sean-k-mooney gibi: im hoping that we wont use the mailing list to hevialy for converstaion that are not backed by a spec
14:33:17 sean-k-mooney gibi: we can do that but i think its not a great medium to have those kind of disucssions without a lot of pre work
14:33:50 sean-k-mooney that said we used to have a bot that jsut closed them so we could always just do that again :P
14:34:37 gibi sean-k-mooney: what do you suggest, how to prepare for the limited real time ptg discussion?
14:35:41 sean-k-mooney well im hoping our actul contact hours that are don vitually will not be less then we normally have in person but will just be spread over more days
14:37:06 sean-k-mooney i just think if its a spec we should keep most of the discussion in gerrit. if its a process thing i would prefer to have an etherpad for it with a summary after the ptg slot on the mailing list
14:37:52 sean-k-mooney we can certenly do some disucssion on the mailing list but i fount the plamcnet pre ptg and the nova pre ptg we did last cycle very hard to follow
14:38:21 gibi sean-k-mooney: we won
14:38:28 gibi sean-k-mooney: we won't have that much contact hours
14:38:52 gibi and it will be a lot slower discussion
14:39:02 gibi compared to a face to face discussion
14:39:33 sean-k-mooney then we may need to consider doing a midcyle or other 1:1 session around milesotone 1
14:40:06 sean-k-mooney i guess we can cross that bridge after the ptg to see if there are still things that need more dicussion that would be hard to do via gerrit or ml
14:40:18 gibi agree ^^
14:41:18 sean-k-mooney the reason i prefer etherpads for this type of disucsion by the way is just down to how mailing list thread thend to diverge and its hard to reponed quickly to indivigual quetions without having to respond ot everything
14:41:59 sean-k-mooney with etherpad we can just talk on indiviual lines and keep all the context
14:42:06 gibi sean-k-mooney: OK, so before the virtual ptg I will try to kick peole to start looking at the etherpad
14:42:45 gibi I'm fine if we do the pre-discussion in the etherpad
14:43:02 gibi what I need is to have pre-discussion somehow
14:43:10 dansmith etherpad is really terrible for discussions because it's very easy to end up with stuff that you can't attribute to the author
14:43:14 sean-k-mooney we may want to create topic etherpads linked off the main one to keep it clean
14:43:15 dansmith especially with lots of people
14:43:35 dansmith so I'm very much opposed to *directing* people to etherpad for discussions
14:43:53 sean-k-mooney dansmith: for things with a spec i think gerrit si the place to have the disccssion
14:44:05 dansmith I have a huge difficulty distinguishing the colors, even to assign unattributed text to someone that said something elsewhere
14:44:10 sean-k-mooney but do you think we should be using the mailing list for eveything else
14:44:11 gmann i think ML is better than etherpad discussion for pre-ptg.
14:44:34 dansmith agree that gerrit is the place for anything that is a spec. for non-spec, mailing list for sure
14:44:48 gibi that was my default plan ^^
14:44:49 gmann and where discussion going heavy then mark that for PTG discussion instead of overloading ML
14:44:49 dansmith etherpad also doesn't tell you what things you've read and what things are new
14:44:56 sean-k-mooney gmann: i really hated the pre-ptg ml threads we have done in the past
14:45:08 dansmith gibi: ++
14:45:19 sean-k-mooney but if that is what we are going to do i guess ill have to live with it
14:45:32 gibi sean-k-mooney: I hated that too but maybe it was not because of the ML itself but because of the amount of information I needed to process
14:45:40 sean-k-mooney can i just ask that we do not complete any topic only in the mailing list
14:46:06 gmann sean-k-mooney: i think we tried to conclude the things on ML which got too much. I think we can burn lot of light weight topic discussion there
14:46:10 dansmith how many people that hate divergent ML threads are using a mailer that doesn't actually show threads hierarchically like gmail?
14:46:11 sean-k-mooney gibi: for me its the format not the amount of info
14:46:24 gmann and if any topic is going back and forth then say 'let's discuss in ptg'
14:46:41 gibi gmann: ^^ +1
14:46:42 sean-k-mooney dansmith: i use revesr chronolgical order

Earlier   Later