Tuesday, 2018-11-20

*** tetsuro has joined #openstack-placement00:11
openstackgerritJie Li proposed openstack/nova-specs master: Support volume-backed server rebuild  https://review.openstack.org/53240703:46
*** diga has joined #openstack-placement04:00
*** tetsuro has quit IRC04:04
*** tetsuro has joined #openstack-placement05:11
openstackgerritJie Li proposed openstack/nova-specs master: Support volume-backed server rebuild  https://review.openstack.org/53240706:04
*** takashin has left #openstack-placement07:01
*** tssurya has joined #openstack-placement07:46
*** s10 has joined #openstack-placement09:17
*** e0ne has joined #openstack-placement09:24
*** cdent has joined #openstack-placement09:31
openstackgerritChris Dent proposed openstack/placement master: Correct lower-constraints.txt and the related tox job  https://review.openstack.org/61455910:46
*** diga has quit IRC11:16
mnaserjust a heads up11:21
mnaserwe cant really continue adding support for os_placement if the placement-manage command is not there11:21
mnaserhow do we init dbs?11:21
cdentmnaser: it's nearly merged: https://review.openstack.org/#/c/600161/11:30
cdentit's last in a stack of quite a lot of stuff to do database migrations and reviews have been slow to come11:30
cdentbut there was a surge of effort yesterday11:30
cdentI'm working on matt's suggestions on ^ today so it shoud happen before the end of the week11:31
*** s10 has quit IRC11:57
*** s10 has joined #openstack-placement12:04
openstackgerritChris Dent proposed openstack/placement master: Add a placement-manage CLI  https://review.openstack.org/60016112:20
cdentefried, mriedem, edleafe : I add some docs to ^12:20
openstackgerritChris Dent proposed openstack/placement master: Adapt placement fixtures for external use  https://review.openstack.org/61793512:46
belmoreiracdent efried considering the number of requests from the compute nodes to placement is there any other relevant patch that I should have a look? https://review.openstack.org/#/c/615606 https://review.openstack.org/#/c/615646 https://review.openstack.org/#/c/61567713:03
*** s10 has quit IRC13:05
*** s10 has joined #openstack-placement13:21
*** diga has joined #openstack-placement13:22
*** mriedem has joined #openstack-placement13:41
cdentbelmoreira: sorry, was away, the whole stack beginning with https://review.openstack.org/#/c/615606 is the main stuff14:26
mriedemcdent: teeny tiny things in https://review.openstack.org/#/c/600161/414:30
mriedemer https://review.openstack.org/#/c/600161/14:30
cdent14:30
mriedemthat will make life easier when placement-status is added14:30
* cdent shakes fist14:31
mriedemwhich if someone else hasn't started, i can do this morning14:31
cdentIf we must :)14:31
mriedemthere will be a tc spanking if the goal is not accomplished14:32
*** dtantsur has joined #openstack-placement14:32
* cdent drops trou14:32
dtantsurhi folks!14:32
dtantsurI'm trying to understand the Placement API design and how it maps into Ironic stuffs14:33
dtantsurgiven that any Ironic node is represented by exactly one instance of a custom resource class14:33
dtantsurto reserve a node I need: 1. GET /resource_providers?resources=CUSTOM_BAREMETAL:1&required=list,of,traits14:33
dtantsur2. POST /allocations with suitable UUID?14:34
cdentthanks for coming dtantsur14:34
cdentfirst14:34
cdentbefore you keep going on too far14:34
cdentI need to caution you that "reserving" is not a thing that placement officially does14:34
cdentif you make an allocation (usually PUT /allocations/{uuid}) you are saying "I am consuming this"14:34
cdentre high level overview, some of the info at https://docs.openstack.org/placement will help, but it is currently in flux as we move things around14:35
dtantsurcdent: I have hard time understanding reserving vs consuming here14:35
cdentconsuming means: this thing is in use and the resources in its inventory are actually being used14:36
dansmithwell,14:36
efriedbelmoreira: https://review.openstack.org/#/c/615695/ and https://review.openstack.org/#/c/615677/ are going to be the big ones for reducing placement traffic. But they're built on top of14:36
efriedhttps://review.openstack.org/#/c/615646/14:36
efriedhttps://review.openstack.org/#/c/615641/ (merged in master)14:36
efriedhttps://review.openstack.org/#/c/615606/ (merged in master)14:36
cdentreserving means: I expect to want this thing soon, and while I am not using them right now, I don't want any one else to14:36
dansmithit means "we assume you're using it"14:36
dansmithactually consuming those resources would be actively using the memory, if we're being pedantic14:37
cdentdansmith: right, that's why I said officially, because I was coming round to: if you want it to mean "hold", it would work14:37
dtantsurokay, I see the difference in the VM case14:37
*** s10 has quit IRC14:37
dansmithdtantsur: it's not really any different.. in the vm case, we "consume" well before we actually consume, just like the ironic case14:38
dtantsurhow do you avoid the instances landing on a compute that only has space for one of them?14:38
dtantsurah!14:38
dansmithdtantsur: I think the word "reserve" has a time component for a lot of people, which is why it wasn't used in placement terminology14:38
dtantsursure, I don't want it to associate with Blazer :)14:38
cdentyeah, it reminds too much of making a reservation for dinner later14:38
mriedemthe ironic driver does reserve all of the inventory on a node while it's being cleaned14:38
mriedemif that's what you're thinking of14:39
dtantsur(omg, I forgot about it) no, I rather mean "consume" here.14:39
dtantsuractually it would be awesome if somebody could read https://review.openstack.org/#/c/617953/ and tell me how deeply screwed I'll be when I come to a Placement backend for that.14:40
cdentdtantsur: I'll read that later in the day, I need to get this placement-manage stuff doneish14:40
mriedemdtantsur: so that is a proxy to placement?14:41
mriedemoh backends...14:41
dtantsurmriedem: this is one of the cases. the other case is hardcore standalone ironic with nothing else.14:41
mriedemwell,14:42
mriedemit sounds like you're looking for the placement allocations api, which if modeled that way then the backend for placement just works, and the backend for a db just needs to implement the placement api14:42
mriedemyou could also use the PlacementDirect tool for the db backend14:43
mriedem"The conductor creates an *Allocation* object in the database with14:43
mriedem   ``state=allocating`` and ``conductor_affinity=<host name>``."14:43
dtantsurPlacementDirect? any reference to that?14:43
mriedemis where things probably start to break down14:43
dtantsurwhy?14:43
mriedemhttps://github.com/openstack/placement/blob/master/placement/direct.py14:44
mriedemallocations in placement don't have state14:44
mriedemor affinity14:44
cdentdtantsur: I suggest you avoid PlacementDirect unless there's some deep reason you actually need it14:44
mriedemthere are aggregates in placement...14:44
dtantsurmriedem: this affinity thing is for ironic HA bookkeeping, you can ignore it here, I think14:44
dtantsuressentially to say "oh, this allocation was in progress by that conductor.. and now it's dead wut du?"14:45
mriedemwhy can't standalone ironic just depend on placement?14:47
mriedemthe cinder guys said that standalone cinder requiring placement would also be a show stopper for some14:47
dansmithit would need to behave differently if consumed by nova then right?14:47
mriedemi guess standalone is truly standalone14:47
dansmithunless it's just double accounting everything14:47
mriedemthat's noted in the spec, under the nova driver impact section14:47
dtantsurI hear you :( yes, there are people who want ironic and nothing else. some even asked me if we can avoid amqp..14:47
dansmithespecially for the zero day seed case,14:48
dansmithcompletely standalone ironic makes a lot of sense I think14:48
dtantsurdansmith: I guess we'll need a configuration option for who reports to Placement: nova-compute or ironic14:48
dtantsurah, you're not talking about reporting14:48
dansmithdtantsur: I guess I missed what the use case is here14:48
dtantsurdansmith: an example that comes up very often is cluster API in k8s14:49
dtantsursome folks want to have a bm provisioning tool supported, and it may be ironic14:49
dtantsurbut they don't want a lot of openstack14:49
* dansmith stares wide-eyed at that spec14:50
dansmithI guess I need to read14:50
mriedemso the k8s cluster API ~= nova?14:50
dtantsurmriedem: I'm not expert at all, but I think it's kind of "give me a cluster" API. the Nova backend is in progress, but some folks are also interested in a pure BM thing.14:52
mriedemnova backend for k8s?14:52
dtantsurmriedem: it's k8s installer, not k8s itself. i.e. a way to install k8s on openstack (= nova)14:53
mriedemoh14:53
* dtantsur needs to polish his knowledge of k8s before it becomes no longer hypeish14:53
mriedemsure, if there is one marketing message i got from the summit it's that k8s on ironic is getting people all excited14:54
cdentrather14:55
mriedemthat and if i put 'edge' in any of my talks they will be accepted14:55
dtantsur++14:55
cdentk8s on ironic @ the edge14:55
dtantsurI'm doing it now for 2 conferences, let's see how it goes14:55
mriedemheh14:55
openstackgerritChris Dent proposed openstack/placement master: Add a placement-manage CLI  https://review.openstack.org/60016114:56
cdentmriedem: I think that ^ gets it14:56
mriedemcome on steve get it14:57
openstackgerritChris Dent proposed openstack/placement master: Adapt placement fixtures for external use  https://review.openstack.org/61793514:58
cdentah, go me, le sigh14:59
openstackgerritChris Dent proposed openstack/placement master: Add a placement-manage CLI  https://review.openstack.org/60016115:00
openstackgerritChris Dent proposed openstack/placement master: Adapt placement fixtures for external use  https://review.openstack.org/61793515:00
mriedem+215:01
cdentdansmith, efried : your eyes on https://review.openstack.org/600161 would be great15:01
*** efried is now known as efried_pto15:02
efried_ptocdent: ^ (back this afternoon)15:02
cdentaye aye15:02
mriedemadded stephenfin to the bottom on15:02
mriedem*one15:02
mriedemi forgot to do that last night15:02
belmoreiraefried cdent: thanks. Will add them when they move to master.15:07
mriedemmy dad: "i sent a video to your mother and she can't open it. if i send it to you and you send it to her, will she be able to view it then?"15:11
mriedemyes dad, that's how file type conversion works15:11
cdenttell him to print it15:12
mriedemcdent: did you see the comment on https://review.openstack.org/#/c/600162/ about changing the depends-on to the changeid so the 3rd party CI using zuulv2 will work15:12
mriedem?15:12
cdentyes, but I hadn't got around to doing it because there's something like 3 or 4 different patches that would need to be updated15:13
cdentand that was enough effort to cause me to "later" and then "forget"15:14
mriedemi think it's just the devstack patch that needs updating?15:14
cdentit depends on which bit of third party ci we're caring about. I was also thinking in terms of the nova changes to use the placement fixture: https://review.openstack.org/#/c/617941/ . Oh, I guess I fixed that one already15:15
cdentI'll change the devstack one now15:15
* cdent wants everyone (especially vmware) to move to zuulv315:17
dtantsurzuulv3 ftw. absolute awesomeness.15:49
*** tssurya has quit IRC15:55
mriedemwhy isn't requirements.txt in the deps for tox targets in placement?16:06
mriedemhmm i guess it's not in nova's tox.ini either...16:08
cdentmriedem: usedevelop=True makes sure that python setup.py develop is called and pbr makes sure that requirements.txt is installed16:10
cdent(when setup.py develop is called)16:10
cdentso if requirements.txt was listed explicitly we'd try to install twice16:11
cdentthis bit me while fixing the lower-constraints stuff16:11
cdent(where "this" is pbr doing things)16:11
mriedemsorry was arguing about the merits of traditional stuffing with my wife16:13
mriedemhmm, guess i need to figure out why oslo.upgradecheck isn't getting installed them16:14
mriedem*then16:14
cdenttraditional stuffing versus?16:16
cdentI don't think that tox is aware of changes to requirements.txt all by itself, did you -r?16:17
mriedemversus some spinach/artichoke/cream cheese abomination16:17
mriedemit'll be like the turkey has a urinary tract infection16:17
mriedemi did -r yeah16:17
mriedemlisten, if i can't do away with mashed potatoes in place of roasted yukon goldies, i'll be damned if i'm not getting traditional stove top style stuffing16:18
*** e0ne has quit IRC16:21
cdenti agree16:22
cdentit's not thanksgiving without sagey bready stodgy yumness16:22
mriedemit's what the pilgrims would have wanted16:23
mriedemwe're hosting this year which is rare, and i don't particularly care for a dried out bird, so i suggested we just make steaks and stuff people actually like to eat16:26
mriedembut was shot down16:26
openstackgerritMatt Riedemann proposed openstack/placement master: Add placement-status upgrade check command  https://review.openstack.org/61903516:30
openstackgerritMatt Riedemann proposed openstack/placement master: Consider root id is None in the database case  https://review.openstack.org/61904117:01
mriedem^ is the proper cherry pick of that bug fix from nova17:03
edleafemriedem: yeah, mine was a placeholder until the nova patch merged so we didn't forget it17:04
*** dtantsur is now known as dtantsur|afk17:19
*** e0ne has joined #openstack-placement17:31
*** e0ne has quit IRC17:44
openstackgerritChris Dent proposed openstack/placement master: Allow placement to start without a config file  https://review.openstack.org/61904917:48
openstackgerritChris Dent proposed openstack/placement master: WIP: Optionally migrate database at service startup  https://review.openstack.org/61905017:48
cdentmriedem: pep8 issues on https://review.openstack.org/619035 otherwise very nice17:54
*** e0ne has joined #openstack-placement17:57
openstackgerritArtom Lifshitz proposed openstack/nova-specs master: Re-propose numa-aware-live-migration spec  https://review.openstack.org/59958718:22
*** efried_pto is now known as efried18:28
mriedemsob18:42
openstackgerritMatt Riedemann proposed openstack/placement master: Add placement-status upgrade check command  https://review.openstack.org/61903518:53
cdent+2 to that. get efried on that stuff and we be stylin18:56
efriedI'm doing what, reviewing ---^ ?18:56
cdentand its parent and cousin18:57
cdentMany, if not most, of the things on https://etherpad.openstack.org/p/placement-extract-stein-4  are at least started. Might be time to refactor to a -5 soon19:20
*** e0ne has quit IRC19:22
efriedcdent: https://review.openstack.org/#/c/600161/ +A, with a question inline for a fup if relevant.19:38
efriedcdent: what else specifically?19:38
* cdent looks19:38
cdentefried: both of the two above that19:39
efried...19:39
cdentof the two the 'fixtures' one is probably more immediately useful, but then after that you'll probably want to go see: https://review.openstack.org/#/c/617941/19:41
cdentgetting the cli merged will allow a big cascade of other stuff to merge and test, so is a major step forward. go us.19:45
openstackgerritMerged openstack/placement master: Add a placement-manage CLI  https://review.openstack.org/60016119:51
* cdent drinks19:53
openstackgerritJack Ding proposed openstack/nova-specs master: Flavor Extra Spec and Image Properties Validation  https://review.openstack.org/61854219:54
efriedcdent: https://review.openstack.org/#/c/618708/ - see note, please -2.20:00
cdentroger20:01
efriedcdent: Questions in https://review.openstack.org/#/c/617935/ if you please.20:12
* cdent pleases20:13
efriedcdent, mriedem: question in https://review.openstack.org/#/c/619035/20:19
efriedcdent: one more question in https://review.openstack.org/#/c/617935/ but +W.20:22
* cdent defers to mriedem on 619035, I'm not clear20:22
mriedemreplied20:23
mriedem(py35) osboxes@osboxes:~/git/placement$ pip show openstack-placement20:24
mriedemName: openstack-placement20:24
mriedemVersion: 0.0.1.dev1083220:24
mriedemwhen we release, that will become 1.0.020:24
openstackgerritMerged openstack/placement master: Adapt placement fixtures for external use  https://review.openstack.org/61793520:31
cdentyay20:32
efriedcdent: Do you agree with mriedem that we should start placement at 1.0.0? I would say there's an argument to start it at <version it was the last time it existed in nova>+1. Thoughts?20:35
cdentyes 120:35
cdentit's the pattern other extracted things have followed20:35
efriedSo basically the placement service will go from 18.0.0 to 1.0.0, sort of.20:35
efriedokay, fair enough.20:36
cdentI think it's more sensible to people who will be coming to placement fresh20:36
efriedI guess. Seeing 19.0.0 they be like, where are the previous versions?20:36
cdentright20:37
openstackgerritMerged openstack/placement master: Add placement-status upgrade check command  https://review.openstack.org/61903520:52
*** efried is now known as efried_back_mond22:43
*** efried_back_mond is now known as efried_back_mon22:43
cdentmriedem: you care to speculate why this is now happening on the devstack change: http://logs.openstack.org/07/619107/3/check/devstack/6e59b7f/job-output.txt.gz#_2018-11-20_22_48_36_17340723:01
cdentI can't figure out which thing has changed23:01
mriedemhmm23:05
mriedemno changes to devstack-gate https://github.com/openstack-infra/devstack-gate/commits/master23:05
mriedemnot seeing anything recent or related in openstack-zuul-jobs https://github.com/openstack-infra/openstack-zuul-jobs/commits/master23:06
cdentyeah, I did a similar search around and was bewildered23:06
mriedemi'd ask in infra23:07
cdentheading that way shortly23:08
mriedemhmm https://github.com/openstack-dev/devstack/blob/master/.zuul.yaml#L26223:11
mriedemmaybe something changed in zuul and how it handles required-projects overrides23:12
mriedemthe devstack-gate change doesn't take effect on this job i don't think since it doesn't use devstack-gate23:12
mriedemso my guess would be we need to add placement to that required projects list in the devstack job...23:12
mriedembut then why did i need to add it to openstack-zuul-jobs,23:13
mriedemoh that was the legacy base job template though23:13
mriedemhttp://git.openstack.org/cgit/openstack-infra/openstack-zuul-jobs/tree/zuul.d/jobs.yaml#n95723:13
mriedemso how the devstack change was working before, idk23:13
mriedembut my guess is that's the problem23:13
cdentyeah, that's what's bewildering23:13
cdenti'll try it23:14
*** takashin has joined #openstack-placement23:34
cdentmriedem: " i think it's because previous patchsets had a depends-on on a change in placement, so it was being pulled in.", said corvus23:36
mriedemah23:40
mriedemwell that makes sense at least23:40
openstackgerritChris Dent proposed openstack/placement master: Clean up use of Database fixture  https://review.openstack.org/61912123:41
mriedemteeny mistake in the devstack change commit message23:42
mriedemit's nearly midnight for you, want me to update this?23:42
cdentwell it wouldn't be me if I didn't make some of those23:42
cdentyes, please, that would be great23:42
cdentI've just started yet another fup on something else23:43
openstackgerritChris Dent proposed openstack/placement master: Allow placement to start without a config file  https://review.openstack.org/61904923:56
openstackgerritChris Dent proposed openstack/placement master: WIP: Optionally migrate database at service startup  https://review.openstack.org/61905023:56
* cdent waves goodnight23:58
*** cdent has quit IRC23:59

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