Monday, 2018-12-17

*** tetsuro has joined #openstack-placement00:30
*** tetsuro has quit IRC00:32
*** tetsuro_ has joined #openstack-placement00:32
*** tetsuro_ has quit IRC00:40
*** tetsuro has joined #openstack-placement00:53
openstackgerritTakashi NATSUME proposed openstack/os-resource-classes master: Update author-email in setup.cfg  https://review.openstack.org/62488501:38
*** tetsuro has quit IRC03:30
*** tetsuro has joined #openstack-placement04:25
*** tetsuro has quit IRC05:36
*** tetsuro has joined #openstack-placement06:53
*** tetsuro has quit IRC07:33
*** e0ne has joined #openstack-placement07:35
*** e0ne has quit IRC07:39
*** helenafm has joined #openstack-placement08:08
*** takashin has left #openstack-placement08:31
*** gibi has joined #openstack-placement08:52
*** ttsiouts has joined #openstack-placement09:34
openstackgerritChris Dent proposed openstack/placement master: WIP: Use os-resource-classes in placement  https://review.openstack.org/62355609:40
openstackgerritChris Dent proposed openstack/placement master: WIP: Use os-resource-classes in placement  https://review.openstack.org/62355610:02
*** e0ne has joined #openstack-placement10:02
*** cdent has joined #openstack-placement11:07
openstackgerritChris Dent proposed openstack/placement master: Use os-resource-classes in placement  https://review.openstack.org/62355611:30
*** e0ne has quit IRC11:31
*** jaypipes has joined #openstack-placement11:33
*** helenafm has quit IRC11:57
*** diga has joined #openstack-placement12:20
openstackgerritChris Dent proposed openstack/placement master: Use os-resource-classes in placement  https://review.openstack.org/62355612:26
openstackgerritChris Dent proposed openstack/placement master: Add irrelevant files list to perfload job  https://review.openstack.org/62404712:37
*** e0ne has joined #openstack-placement12:47
guilhermesphello! seems that we have greenfield for our placement role https://review.openstack.org/#/c/618820/12:53
guilhermespbut I'd like to know from you guys how are we testing placement. Do we have a set of tempest tests for it?12:53
guilhermesptesting my role locally, seems that the placement installation is not 100 percent functional, for that reason I'd like to test it with tempest of other tool12:54
cdentguilhermesp: what are you seeing that suggests its not 100%?13:00
cdentthere was discussion last week that a) no there aren't specific placement tests in tempest, b) the compute service tests will exercise placement well13:01
guilhermespfor example, I can't see placement port up in my tests. It's like there's something missing in MY installation process13:01
cdentare you installating it on a port, or on a prefix /placement? That is, what ends up in the service catalog?13:02
guilhermespactually I'm configuring a port ( same as was before when placement was within nova) https://review.openstack.org/#/c/618820/48/defaults/main.yml line 122 that ends up in the service catalog13:04
guilhermespI think I'm missing some step. I was out last week so I'm planning to come back to this work this week to figure out13:05
guilhermespthat's why I was curious about testing13:05
cdentguilhermesp: mnaser, mriedem and I talked about it last week and worked out that the best route for testing via tempest would be to turn on the compute tests13:07
cdentbut if the port isn't coming up, I wonder if the web server is being restarted/reloaded after the config changes have been done13:08
sean-k-mooneywhy are you doing the db setup https://review.openstack.org/#/c/618820/48/tasks/main.yml@55 after you start the service https://review.openstack.org/#/c/618820/48/tasks/placement_install.yml@5213:08
*** e0ne has quit IRC13:11
*** e0ne has joined #openstack-placement13:14
openstackgerritChris Dent proposed openstack/placement master: Document API error codes  https://review.openstack.org/62470513:17
guilhermespsean-k-mooney: actually, the systemd was introduced across all roles with the purpose of this commit https://github.com/openstack/openstack-ansible-os_glance/commit/9eb319c22b5329f78b2b6c3c4f4744793c633744#diff-512247f2612555c70f64504f7c3916a7 ( take as an example )13:18
guilhermespit has not really a side effect to set up db after the execution of this piece of code13:18
guilhermespcdent: thanks for the hint, I'll take a look at this detail13:18
sean-k-mooneyguilhermesp: your assuming that placement will be happy to start without the db configured which may result in it falling back to sqlite13:20
cdentsean-k-mooney: placement won't start without the db explicitly configured, there is no default connection. but I agree, it should be configured and set up before the service starts, if possible13:21
*** helenafm has joined #openstack-placement13:22
guilhermespsean-k-mooney: actually, the task https://review.openstack.org/#/c/618820/48/tasks/placement_post_install.yml is responsible to set up the placement config https://review.openstack.org/#/c/618820/48/templates/placement.conf.j2 that has the correct db path13:22
sean-k-mooneyit look like https://review.openstack.org/#/c/618820/48/handlers/main.yml should restart the services atht he end of the main task13:23
guilhermespyes sean-k-mooney actually that piece of systemd code was placed to refactor a lot of code that was a bit messy before. That's why seems a bit confusing13:24
guilhermespbut I appreciate your questions about it sean-k-mooney and cdent that's very important13:25
sean-k-mooneywell using handeler makses sense for restarting the services actully.13:25
sean-k-mooneyguilhermesp: i would maybe move https://review.openstack.org/#/c/618820/48/tasks/placement_install.yml@52 to https://review.openstack.org/#/c/618820/48/tasks/placement_service_setup.yml@100 but other then that it seam like it would fix it self when you flush the handeler at the end of the role13:28
guilhermespgood point sean-k-mooney I'll bring that discussion into openstack-ansible channel, as it seems we are keep the pattern of code across all roles. Maybe the guys out there has a really good reason to keep this where it is and I'm not able to tell you now. Let me discuss with them and I will give you a feedback about it13:30
sean-k-mooneycdent: could this be related to the the global db context in any way?13:31
sean-k-mooneyguilhermesp: do you run placment under apache?13:32
cdentsean-k-mooney: which "this" do you mean?13:32
sean-k-mooneycdent: placement not startign properly13:32
guilhermespsean-k-mooney: I think that could be the missing part. I didn't configure apache2 and uwsgi there I think13:32
cdentsean-k-mooney: i'm unwilling to speculate. Until I see some logs or something it could be anything.13:33
sean-k-mooneycdent: fair.13:33
cdentbut certainly if apache and uwsgi aren't set up, that would do it13:34
sean-k-mooneylook like uwsgi is being used https://review.openstack.org/#/c/618820/48/defaults/main.yml@15513:35
guilhermesplet me check locally sean-k-mooney and cdent13:38
guilhermespsean-k-mooney: cdent http://paste.openstack.org/show/737484/ that could be one of the reasons13:40
* cdent is having a slow internet day13:40
sean-k-mooneyyep i was just going to point out that i dont see where you create /etc/uwsgi/placement-api.ini13:41
guilhermespyep also there is no placement stuff in there http://paste.openstack.org/show/737485/13:41
*** e0ne has quit IRC13:42
sean-k-mooneyguilhermesp: i woudl guess the systemd service has a file not found error or something similar13:42
guilhermespcould be sean-k-mooney I'd try to find something in the logs locally13:43
sean-k-mooneycdent: is https://github.com/openstack/placement/blob/master/setup.cfg#L47 ment to auto generate the wsgi script on install13:43
sean-k-mooneycdent: specifically /etc/uwsgi/placement-api.ini13:44
cdentyes, it's built into pbr13:44
cdentno13:44
cdentthat's something different13:44
sean-k-mooneyok it generate teh script not the config13:44
guilhermespsean-k-mooney: just a note about systemd piece of code13:44
guilhermespthe service unit files are laid down, but they are not started until the handlers are fired once the role execution is complete - for example: http://logs.openstack.org/43/619343/1/check/openstack-ansible-functional-ubuntu-bionic/9ffd452/job-output.txt.gz#_2018-11-21_20_04_42_84922913:44
*** e0ne has joined #openstack-placement13:45
cdentplacement-api.ini is the uwsgi config script, which is created by the deployment tooling13:45
sean-k-mooneycdent: right in that case guilhermesp if you create the /etc/uwsgi/placement-api.ini file that might fix your issue its a good place to start in anycase13:46
cdentguilhermesp, sean-k-mooney : this is what devstack does, if that's a useful reference: https://github.com/openstack-dev/devstack/blob/master/lib/apache#L23513:47
sean-k-mooney cdent its proably simpler to use a jinja template in ansible but ya that has all the default wsgi options13:48
sean-k-mooneydo they differ from how you run it in you docker dev env for placement13:49
cdentoh sure, I wasn't suggesting _using_ that, but rather pointing it out as the options used13:49
cdentI would guess that osa already has a template/role/task for such things and it just hasn't bee included, as a simple mistake13:50
cdentsean-k-mooney: quite a lot different13:50
guilhermesphum, so which contents should be placed in placement-api.ini? or is it a blank file?13:50
cdentbut the docker stuff I've set up is designed to use uwsgi without apache13:50
cdentguilhermesp: I'd suggest you look at the keystone role and see what it's doing\13:50
cdentsean-k-mooney: so the uwsgi in the docker env is set up to be more robust/complete13:51
guilhermespnice. I will take a look, do the modification and test it locally in a few minutes13:51
sean-k-mooneycdent: so would you recommend https://github.com/cdent/placedock/blob/master/shared/placement-uwsgi.ini as a base for osa13:52
cdentsean-k-mooney: I don't know enough about how osa sets up the other services, but would think it would be important to be consistent with the others (assuming they are doing apache with mod_proxy_uwsgi, then my config is definitely not what they want)13:53
cdentscheduler/placement meeting in #openstack-meeting-alt in 5 minutes if people want one13:54
guilhermespoh great, I will attend the meeting as a guest :)13:56
sean-k-mooneycdent: thats a good point i have not looked at osa before now but ya if they are usign mod_wsgi then ya it should be consitent13:57
guilhermespI agree cdent and sean-k-mooney about keep things like osa does, but would be good just as a proof of concept to follow your suggestion locally, then adapt how osa does in general13:57
*** ttsiouts has quit IRC14:00
*** ttsiouts has joined #openstack-placement14:00
*** takashin has joined #openstack-placement14:01
*** ttsiouts has quit IRC14:04
*** ttsiouts has joined #openstack-placement14:04
*** mriedem has joined #openstack-placement14:08
*** takashin has left #openstack-placement14:08
guilhermespI think this is one example how we set up uwsgi in keystone https://github.com/openstack/openstack-ansible-os_keystone/blob/master/templates/keystone-uwsgi.ini.j2 cdent  sean-k-mooney14:12
cdentguilhermesp: that looks very much like what placement would want, except of cource the template vars would be different14:14
cdentand the virtualenv14:14
guilhermespyep, I'm taking this https://github.com/cdent/placedock/blob/master/shared/placement-uwsgi.ini that sean-k-mooney suggested14:14
cdentedleafe: can you remember of the top of your head the tools you used for trimming nova history to create the placement repo?14:40
edleafecdent: I have a script I used lying around somewhere. Gimme a minute to dig it up14:41
cdentthanks14:43
edleafecdent: ok, it was the `filter_git_histroy.sh` that did the extraction, and another script that ran the filter script with the list of files/directories to preserve.14:49
cdentand that came from oslotools or something like, yes?14:50
* cdent looks14:50
edleafecdent: after that I had a series of scripts to clean up the extracted files to remove the unwanted things14:50
edleafeYeah - I think you were the one who pointed me to it14:50
edleafeI have a copy if you need it14:50
cdentcool, thanks. i had some of the pieces in my head, but not the name of the script14:50
cdentno that's enough, thank you14:51
edleafeYou starting over? :)14:51
*** e0ne has quit IRC15:02
*** e0ne has joined #openstack-placement15:06
*** efried has joined #openstack-placement15:06
cdentedleafe: I responded on your startswith suggestion in the "naw" tone. But I can be convinced otherwise if you disagree with my disagreeing15:47
cdentedleafe: also, I take it your were happy with the locking changes?15:48
edleafeYeah, the locking stuff looked fine15:49
edleafeI'm just curious about the "another namespace" idea. What would be another possible namespace?15:50
cdentthere was discussion in traits (ack they are not the same, but...as an example) (on a spec I can't remember) of using prefixes on traits to mean things15:51
cdentso it just seems like a possibility (albeit one I would resist)15:52
cdentbut since it is conceivable, and the numeric-based solution works, why not?15:52
edleafeIt just is one other mental step to xlate "minimum id" to "able to be deleted"15:53
edleafeNot a big deal at all15:53
cdentk, cuz if it was I would want to direct you to some other mental steps that seem bigger15:55
openstackgerritChris Dent proposed openstack/placement master: Use os-resource-classes in placement  https://review.openstack.org/62355615:58
edleafeHeh, well, those other things aren't being changed in your patch :)15:58
*** diga has quit IRC16:12
gibicdent: sorry I run out of time so I have to push the os-resource-classes to tomorrow16:14
cdentgibi: no worries, at this time of year rushing isn't going to help much of anything16:15
*** N3l1x has joined #openstack-placement16:23
*** N3l1x_ has joined #openstack-placement16:23
* cdent goodnights16:54
*** cdent has quit IRC16:54
*** ttsiouts has quit IRC16:56
*** ttsiouts has joined #openstack-placement16:56
*** ttsiouts has quit IRC17:01
*** efried has quit IRC17:01
*** helenafm has quit IRC17:02
*** e0ne has quit IRC17:46
*** e0ne has joined #openstack-placement18:42
*** e0ne has quit IRC18:46
*** mriedem has quit IRC18:48
*** mriedem has joined #openstack-placement18:51
*** e0ne has joined #openstack-placement19:01
*** N3l1x has quit IRC19:53
*** e0ne has quit IRC22:25
*** mriedem has quit IRC23:40

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