Monday, 2019-03-18

*** irclogbot_2 has quit IRC02:23
*** edmondsw has quit IRC02:26
*** edleafe has quit IRC02:27
*** ttsiouts has quit IRC03:52
*** e0ne has joined #openstack-placement06:40
*** e0ne has quit IRC07:02
*** belmoreira has joined #openstack-placement07:24
*** rubasov has quit IRC07:59
*** ttsiouts has joined #openstack-placement08:06
*** tssurya has joined #openstack-placement08:36
*** rubasov has joined #openstack-placement08:45
*** belmoreira has quit IRC09:15
*** cdent has joined #openstack-placement09:55
*** e0ne has joined #openstack-placement10:28
openstackgerritChris Dent proposed openstack/placement master: Slightly improve usage documentation  https://review.openstack.org/64391310:35
openstackgerritChris Dent proposed openstack/placement master: Update install docs for single database  https://review.openstack.org/64391510:46
openstackgerritChris Dent proposed openstack/placement master: Rename and restructure install docs  https://review.openstack.org/64391911:08
openstackgerritChris Dent proposed openstack/placement master: Rename and restructure install docs  https://review.openstack.org/64391911:08
openstackgerritChris Dent proposed openstack/placement master: Rename and restructure install docs  https://review.openstack.org/64391911:13
*** ttsiouts has quit IRC11:21
openstackgerritMerged openstack/placement master: Reuse common get_providers_with_resource()  https://review.openstack.org/64372911:30
*** ttsiouts has joined #openstack-placement11:47
*** belmoreira has joined #openstack-placement11:47
*** edmondsw has joined #openstack-placement11:50
*** edleafe has joined #openstack-placement12:21
*** e0ne has quit IRC12:51
*** e0ne has joined #openstack-placement12:52
*** mriedem has joined #openstack-placement12:58
openstackgerritChris Dent proposed openstack/placement master: Update the from-pypi install instructions  https://review.openstack.org/64393813:23
*** ttsiouts has quit IRC13:36
*** ttsiouts has joined #openstack-placement13:41
*** ttsiouts_ has joined #openstack-placement13:42
*** ttsiouts has quit IRC13:46
efriedfinucannot: When you get a chance:13:47
efriedhttps://review.openstack.org/#/c/641497/  <== remove backslashes, edleafe suggested a compromise that is hopefully to everyone's liking13:47
efriedcdent: http://logs.openstack.org/04/641404/5/check/openstack-tox-docs/1d2faee/html/placement-api-microversion-history.html looks fine to me here on my puter.13:47
cdenti've got this: https://tank-binaries.s3.amazonaws.com/a3735085710848c0b3560b0ceb1c82e6.png13:48
cdentwhich I dunno13:48
efriedweird13:49
efrieddo you override fonts in your browser or something?13:49
cdentno13:49
* cdent tries a different browser13:49
efriedIt looks okay to me in chrome & firefox on bionic.13:49
* efried tries Windows...13:49
efriedyeah, it looks about the same for me in all those places. None of them look like yours. Are you on a mac or something?13:51
cdentyup13:51
efriedwell, that must be why it also looked gimpy on my iphone13:51
cdentand its the same across three different browsers13:51
efriedn-sch meeting in 8 minutes in #openstack-meeting-alt13:52
*** tetsuro has joined #openstack-placement13:57
*** e0ne has quit IRC13:58
*** takashin has joined #openstack-placement13:58
*** e0ne has joined #openstack-placement14:05
mriedemfwiw mine looks like cdent's, firefox on windows14:11
mriedemsimilar for firefox on bionic14:12
efriedhm, that's odd, why is my firefox/win and firefox/bionic different?14:12
cdentmissing fancy fonts?14:15
efriedstock installs of both for me.14:19
* cdent shrugs14:19
*** e0ne has quit IRC14:41
openstackgerritOpenStack Release Bot proposed openstack/os-resource-classes stable/stein: Update .gitreview for stable/stein  https://review.openstack.org/64402814:42
openstackgerritOpenStack Release Bot proposed openstack/os-resource-classes stable/stein: Update UPPER_CONSTRAINTS_FILE for stable/stein  https://review.openstack.org/64402914:42
openstackgerritOpenStack Release Bot proposed openstack/os-resource-classes master: Update master for stable/stein  https://review.openstack.org/64403014:42
openstackgerritOpenStack Release Bot proposed openstack/os-traits stable/stein: Update .gitreview for stable/stein  https://review.openstack.org/64403114:42
openstackgerritOpenStack Release Bot proposed openstack/os-traits stable/stein: Update UPPER_CONSTRAINTS_FILE for stable/stein  https://review.openstack.org/64403214:42
openstackgerritOpenStack Release Bot proposed openstack/os-traits master: Update master for stable/stein  https://review.openstack.org/64403314:42
*** e0ne has joined #openstack-placement14:42
openstackgerritOpenStack Release Bot proposed openstack/osc-placement stable/stein: Update .gitreview for stable/stein  https://review.openstack.org/64404314:43
openstackgerritOpenStack Release Bot proposed openstack/osc-placement stable/stein: Update UPPER_CONSTRAINTS_FILE for stable/stein  https://review.openstack.org/64404414:43
openstackgerritOpenStack Release Bot proposed openstack/osc-placement master: Update master for stable/stein  https://review.openstack.org/64404514:43
*** e0ne has quit IRC14:53
*** takashin has left #openstack-placement14:53
*** tetsuro has quit IRC14:54
*** e0ne has joined #openstack-placement14:55
*** e0ne has quit IRC15:05
*** e0ne has joined #openstack-placement15:20
mriedemew, we should add a way to append/add a trait to a provider because 'openstack resource provider trait set' is a full overwrite15:45
mriedemby default, in devstack i've got 11 auto-reported traits on the libvirt compute node15:45
mriedemso adding a custom trait would kind of suck15:45
cdentmriedem: there was a reason for that, not sure I recall15:46
mriedemlack of generations?15:46
cdentbut it was probalby a combination of "restfulness" and other things15:46
mriedemoh there is a generation on traits15:46
mriedemthis would be client-side sugar15:46
mriedemGET /resource_providers/{uuid}/traits15:46
mriedemappend traits to the list,15:47
mriedemPUT /resource_providers/{uuid}/traits with the generation15:47
* cdent nods15:47
* mriedem storyboards15:47
cdentI had misread that you were talking about osc-placement15:47
efriedwait, he *is* talking about osc-placement, not about the API, right?15:48
cdent(correct efried, that's what I mean) I suspect _that_ was simply because of clicking through the microversions, it doesn't feel like there's been that much attention to user experience15:48
mriedemhttps://storyboard.openstack.org/#!/story/200525815:50
mriedemyes CLI15:50
mriedemi'm working on docs for the compute driver capabilities as traits things,15:50
mriedemand have a devstack here where i can give some console examples15:50
mriedemand noticed that to add a new custom trait via the CLI, it means i have to either (1) copy all of the existing traits + the new one or (2) add the new one and then sighup the compute service to get the standard ones back (i think?)15:51
mriedemmaybe not sighup, maybe just wait for update_available_resource to run15:51
* cdent looks at efried15:54
cdentI stayed out of the "how the compute host figures out owning traits" conversation because I had to keep some focus elsewhere and it was tickling my "eh?" button15:54
cdentbut yeah, I agree osc-placement should have an add or something like15:55
cdentugh, I do wish storyboard would do a spinner or something after I click "hey, hey, did you get that?"15:56
efriedmriedem: I think you do have to SIGHUP, yes.15:57
efriedor wait for cache expiry, which may never happen depending on conf15:58
efriedjust having update_available_resource run isn't enough because we don't refresh unless we have some reason to believe the values we already have are stale.15:59
*** ttsiouts_ has quit IRC16:05
*** ttsiouts has joined #openstack-placement16:13
mriedemnot entirely true,16:13
mriedemi wiped out all of the traits using "openstack resource provider trait delete <rp_uuid>" and after 60 seconds they were all back again16:13
mriedemmaybe that's b/c i wiped them all out?16:14
*** e0ne has quit IRC16:14
*** e0ne has joined #openstack-placement16:19
mriedemnope, also overwrite so there were just 2, waited 60 seconds and then they were all back again16:20
*** tssurya has quit IRC16:44
cdentDid we decide that placement-from-stein is 1.0.0?16:47
cdentOr if we didn't decide is there any reason it shouldn't be that?16:47
mriedemi'd expect it should be 1.0.016:53
*** ttsiouts has quit IRC16:57
*** e0ne has quit IRC17:14
cdentblargh. writing docs is hard17:18
edleafeWe should start Stein Placement at 37.18.4 just to mess with people's heads17:21
cdentgood choice17:22
efriedmake the first two parts of the semver match the latest microversion17:23
cdentI actually considered that and was what led me to say what I did in the meeting earlier today about no longer following the standard release cycle17:24
edleafemriedem: https://review.openstack.org/#/c/641497/ has my +117:27
efriedcdent: It's not the worst idea. Adding a microversion is a feature and warrants a major ver bump. And then the minor version is there for bug fixes.17:29
* cdent nods17:29
cdenti think you mean minor and patch?17:30
efriedyeah, I don't know what the semver fields are called.17:30
cdentmajor.minor.patch17:30
efriedx.y.z => x.y is latest microversion, .z is bugs17:30
efriedyeah17:30
cdentmaybe in U?17:31
cdenttoo much change at once we'll honk people17:31
efrieddid we already propose a release?17:31
efriedI'm just sorta wondering if that's going to blow up on us at some point.17:31
cdentnot yet17:32
cdentbut actually if we did want to stick to microversions it would need to be in T17:32
cdentas T would normally be 2.0.017:32
edleafeHow often are we tagging releases? Just once per cycle? Or with each new microversion?17:33
cdentthis cycle we tagged once when the extracted code "worked" and then will tag again this week17:34
cdenttagging each new microversion is an option, nothing prevents it17:35
cdentI definitely think we should do far more intermediate releases than we used to do in the past17:35
cdentbut whether it is by microversion or not is unclear as sometimes we have tons, sometimes not17:35
edleafeI'm trying to imagine it from the consumer POV: will frequent releases make things clearer or more confusing to them?17:36
cdenta new release will be mostly transparent, since microversions are opt-in17:37
edleafeSure, but will they wonder if they are missing out on performance improvements or bug fixes?17:39
cdentwe're still obliged to make releasenotes17:39
cdentand I think the only people who will care are those who chose to install from source or pypi17:39
cdentwhich may be unicorns17:39
edleafeDon't disrespect our unicorn users!17:40
cdentI have the utmost respect for them, which is why I think they can cope17:40
*** mriedem has quit IRC18:45
*** mriedem has joined #openstack-placement18:48
openstackgerritChris Dent proposed openstack/placement master: Upgrade from rocky-nova docs  https://review.openstack.org/64439618:54
cdentedleafe, efried, mriedem : that ^ is a first draft. It's messy and brain hurty enough that i think it best that you give it a good read through before I go any further. besides I'm brain dead and need to go18:56
efriedHave a good evening cdent18:57
edleafecdent: roger that18:57
mriedemack18:59
openstackgerritMerged openstack/placement master: Get rid of backslash continuations in code  https://review.openstack.org/64149719:20
openstackgerritMerged openstack/placement master: Update install docs for single database  https://review.openstack.org/64391519:20
*** cdent_ has joined #openstack-placement19:59
*** cdent has quit IRC20:02
*** cdent_ is now known as cdent20:02
*** irclogbot_2 has joined #openstack-placement20:12
*** dklyle has quit IRC20:14
*** dklyle has joined #openstack-placement20:18
*** irclogbot_2 has quit IRC20:25
*** irclogbot_2 has joined #openstack-placement20:26
*** e0ne has joined #openstack-placement20:28
*** e0ne has quit IRC20:41
*** irclogbot_2 has quit IRC21:05
*** irclogbot_2 has joined #openstack-placement21:06
*** irclogbot_2 has quit IRC21:26
*** irclogbot_2 has joined #openstack-placement21:27
*** cdent has quit IRC21:28
*** mriedem has quit IRC23:20

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!