Earlier  
Posted Nick Remark
#openstack-nova - 2017-11-20
12:40:58 efried cdent So if you're buried under other stuff, I can take it on for the sake of expediency. But if you've got the bandwidth to finish it, you should.
12:41:00 cdent the “those” I meant was the weekly updates
12:41:12 efried Hah. Oh.
12:41:22 efried You're welcome - and yes, please take them back.
12:41:40 cdent roger that. and I’ll take back the symmetric stuff
12:41:47 efried cdent I made sure to leave you #42 :)
12:41:53 cdent so kind
12:42:18 efried cdent And speaking of taking stuff over - you feel like running the scheduler meeting today?
12:42:36 efried edleafe- is out
12:44:14 cdent oh is he now
12:44:23 cdent yeah, I can do it
12:46:17 efried cdent Cool
12:46:44 efried cdent Being an American in the UK, are you going to be out later this week or no?
12:46:46 cdent just to check my calendar it is scheduled for a 1.25 hours from now?
12:46:55 cdent no
12:47:17 cdent Usually I take holiday back to the US to see family, but with sydney just now I couldn’t stand the idea of yet more international travel
12:47:51 efried cdent Okay. Yes, scheduler meeting is 1.25 hours from now if my UTC clock is sane. (DST is stupid)
12:48:01 efried cdent FYI I'll be out W-F
13:27:14 niraj_singh efried: i was going through ( https://review.openstack.org/#/c/512329/ ) this patch. A new exception is cretaed i.e. "ServiceUserTokenNoAuth". But i didn't find where this exception is handled.
13:36:10 openstackgerrit Takashi NATSUME proposed openstack/nova stable/pike: Add 'delete_host' command in 'nova-manage cell_v2' https://review.openstack.org/513717
13:36:41 efried niraj_singh One sec.
13:37:54 efried niraj_singh Okay - what do you mean "handled"?
13:38:17 efried niraj_singh The motivation behind this patch was to make an exception that was easier for the user to understand.
13:38:32 efried niraj_singh So it's not actually supposed to be handled anywhere - it bubbles up to the user.
13:40:33 efried niraj_singh Sorry, by which I mean, it ends up in the logs where the operator can see it.
13:46:49 stephenfin moshele: Done
13:47:20 stephenfin Even though I suggested it, I'm not sure whether we should log an exception message without raising it. I'll let someone else comment on this
13:48:53 niraj_singh efried: I thought it should handle any where. ok thanks for information.
13:54:03 openstackgerrit priyaduggirala proposed openstack/nova master: Rename parameters in call() of nova/image/glance.py https://review.openstack.org/508533
13:57:41 efried Scheduler meeting in three minutes in #openstack-meeting-alt
13:57:46 cdent whoa
13:57:59 efried Did I just read your mind?
13:58:00 cdent I was, like, literally, typing, literally, like, the same, like thing
13:58:14 efried Great minds, and all that.
13:58:36 cdent we are merely expressions of the platonic nova scheduler dev
13:59:01 openstackgerrit Takashi NATSUME proposed openstack/nova master: [placement] Add 'Location' parameters in API ref https://review.openstack.org/521541
14:00:01 efried I had an almost-mother-in-law when I was a youngster who would always know the second half of pithy aphorisms, which was slightly annoying. In this case, "Great minds think alike" apparently concludes, "And fools seldom differ"
14:02:37 stephenfin sean-k-mooney: I'm +2 on this if you want to take a second look https://review.openstack.org/#/c/493082/
14:03:43 stephenfin efried: nested resource providers are on my review radar for this week
14:03:58 stephenfin (RE: the review request you sent at some point last week :))
14:04:06 efried stephenfin That's great to hear. Can you join the sched meeting in -alt ?
14:04:13 stephenfin Now?
14:04:16 efried now
14:05:33 cdent +1
14:13:19 sean-k-mooney stephenfin: just taking a look now
14:13:56 sean-k-mooney ah the printable mixin
14:14:19 stephenfin bauzas: This one's another easy +W, IMO https://review.openstack.org/#/c/466051/
14:15:32 bauzas stephenfin: ack
14:16:46 stephenfin cdent: Seen this? https://review.openstack.org/#/c/511936/ Are we expecting to have a python-placementclient library?
14:17:36 cdent there’s going to be an osc plugin, but no plans for a specific client
14:17:56 cdent in large part because it’s “just json”
14:18:49 cdent stephenfin: https://review.openstack.org/#/q/topic:bp/placement-osc-plugin+(status:open+OR+status:merged)
14:19:45 efried cdent I would be in favor of a client lib that performs useful API calls, like SchedulerReportClient does, and parlays "just json" into useful python objects, like ProviderTree.
14:20:22 cdent I was really hoping we’d keep ProviderTree hidden in the bowels of nova and not make that a thing that people commonly want to use...
14:20:52 cdent But if that’s not the case, then sure, I guess. The deal simply was that until multiple implementations with commonanilities showed up, why bother?
14:21:07 efried It doesn't have to be ProviderTree itself, but in that vein.
14:21:38 openstackgerrit Merged openstack/os-vif master: Add VersionedObjectPrintable mixin https://review.openstack.org/493082
14:21:49 efried cdent Oh, I can answer that one: so that we don't have multiple implementations with commonalities show up, which we then have to reconcile and consolidate.
14:22:14 cdent sigh
14:22:37 cdent reconciliation and consilidation is a _good_ thing. it allows for compare and contrast amongst a variety of thoughts
14:22:41 cdent rather than imposing a single vision
14:23:18 efried But then you wind up with things you can't get rid of because momentum.
14:23:38 cdent The way nova chooses to do things internal to the report client isn’t necessarily right for the rest of the world and vice versa
14:23:56 cdent and if you can’t just use requests for the API when we may as well give up and go home because we’ve failed
14:24:30 efried cdent This is interesting in light of some of the work I did last week. Let's chat after the meeting.
14:25:16 cdent (or at least by 3)
14:25:30 efried cdent Okay, well, if you get a chance, have a look at this: https://review.openstack.org/#/c/521098/4/nova/scheduler/client/report.py
14:26:34 efried A non-trivial method to collate all the information about a group of providers. Call it ProviderTree or whatever, IMO it's conceivably a useful thing to be able to do for any client.
14:27:12 cdent In idealized world mode, the fact that we need a provider tree (or whatever) is a reason to go home
14:27:19 cdent so now isn’t the best time for me to think about that...
14:27:52 cdent if we make it a habit that anything beyond a compute-node/hypervisor needs to know that stuff all the puppies will cry
14:30:12 sean-k-mooney stephenfin: can you take a look at this https://review.openstack.org/#/c/520788/1
14:32:31 openstackgerrit Andrey Kurilin proposed openstack/python-novaclient master: [ci] Use pseudo-random names for new resources https://review.openstack.org/479777
14:33:21 stephenfin sean-k-mooney: I agree with AJaeger there: Sphinx doesn't require you to set the version number and it wouldn't make semantic sense for release notes anyway
14:33:52 sean-k-mooney stephenfin: well i was just about to respond mail thread
14:34:03 stephenfin sean-k-mooney: pbr also overrides the project name and version if built with 'build_sphinx'. I'm not sure if we're using that here but it's probably worth mentioning
14:34:20 stephenfin Cool. I'll hold off on merging so
14:34:34 sean-k-mooney stephenfin: i why are release nots not considerd to be versiond. they are written from the perspective of the release in which they are added
14:34:58 sean-k-mooney i do agree that ideally we should not need to install the projects
14:35:21 stephenfin sean-k-mooney: Because of how they're distributed. At the moment, we don't distribute them at all
14:35:36 sean-k-mooney but i think we have bigger issue if i cant look at just the ocata release nots without seeing the pike release nots if i am upgrading to ocata
14:36:13 stephenfin We "distribute" them only online, via docs.o.o (or is it release.o.o?)
14:39:16 stephenfin sean-k-mooney: As for locally, distribution is via an sdist but you can't currently build release notes from this because you don't have the metadata necessary
14:39:22 stephenfin (because it's not a git repo)
14:40:01 stephenfin reno can export this metadata to a file, but we haven't done this historically. This is changing in the next MAJOR version of pbr, thankfully https://review.openstack.org/#/c/475034/
14:40:47 stephenfin sean-k-mooney: Also, RE: " i think we have bigger issue if i cant look at just the ocata release nots without seeing the pike release nots if i am upgrading to ocata"
14:40:53 stephenfin Isn't this what you want? https://docs.openstack.org/releasenotes/nova/ocata.html
14:42:11 sean-k-mooney stephenfin: yes :) it is. the commit message as written however implies that there is no versioning of release notes at all.
14:42:32 stephenfin sean-k-mooney: Ahh, no no
14:43:06 stephenfin What he's saying is that there'll be no version number provided to Sphinx, because it's no necessary
14:43:17 sean-k-mooney that fine then ill remove my -1 i was fine with the change as long as we could still view it per release
14:44:34 stephenfin Actually, sorry, what he _really_ meant was that version notes are versioned like everything else. E.g. we just have '/releasenotes/{project}' instead of '{series}/releasenotes/{project}'
14:44:41 stephenfin Either way, you have what you want :)
14:45:08 stephenfin bauzas: albeit...?
14:45:56 sean-k-mooney stephenfin: see this is why i ping you on docs changes so i can learn somthing new :)
14:46:35 bauzas stephenfin: oh dammit
14:46:41 bauzas albeit = although
14:47:13 bauzas I thought it was something like "all be it" which sounds to me like "ok, fine, accepted."
14:47:48 stephenfin sean-k-mooney: Anytime, buddy :D
14:48:29 stephenfin bauzas: Not quite, heh. It's pronounced al-bait (like, bait a fish)

Earlier   Later