Tuesday, 2018-07-10

openstackgerritHiroaki Kobayashi proposed openstack/blazar master: Update pylint  https://review.openstack.org/57416604:50
*** masahito has joined #openstack-blazar04:57
openstackgerritMerged openstack/blazar master: Correct the project domain option for authorization  https://review.openstack.org/57802905:05
*** masahito has quit IRC07:00
openstackgerritHiroaki Kobayashi proposed openstack/blazar master: Start to make placement client  https://review.openstack.org/57801707:00
*** hiro-kobayashi has joined #openstack-blazar07:01
openstackgerritVu Cong Tuan proposed openstack/python-blazarclient master: Switch to stestr  https://review.openstack.org/58122407:04
*** hiro-kobayashi has quit IRC07:14
*** masahito has joined #openstack-blazar07:17
openstackgerritMasahito Muroi proposed openstack/blazar master: Change response code when start_date and end_date are invalid  https://review.openstack.org/57364707:51
openstackgerritMasahito Muroi proposed openstack/blazar master: Return 400 Bad Request if an extra capability key is longer than 64  https://review.openstack.org/57569907:51
openstackgerritMasahito Muroi proposed openstack/blazar master: Add release note for response code fixes  https://review.openstack.org/57774707:51
openstackgerritHiroaki Kobayashi proposed openstack/blazar master: Support nova compute-api microversion '2.53'  https://review.openstack.org/57951308:01
*** masahito has quit IRC08:24
*** hiro-kobayashi has joined #openstack-blazar08:47
*** priteau has joined #openstack-blazar08:55
*** masahito has joined #openstack-blazar09:01
openstackgerritPierre Riteau proposed openstack/blazar master: Update pylint  https://review.openstack.org/57416609:12
openstackgerritPierre Riteau proposed openstack/python-blazarclient master: Switch to stestr  https://review.openstack.org/58122409:30
openstackgerritMasahito Muroi proposed openstack/blazar master: Implement list and get allocation method to compute hosts plugin  https://review.openstack.org/58128609:31
masahitoThe placement spec is big and complex. So we should go next.10:01
hiro-kobayashiagree10:02
masahitoThe resource availability API is in same situation with the placement support.10:02
*** tetsuro has joined #openstack-blazar10:02
masahitoSpec: https://review.openstack.org/#/c/574628/10:02
masahitopatch set #1: https://review.openstack.org/#/c/580577/10:02
masahitopatch set #2: https://review.openstack.org/#/c/581286/10:03
masahitoThe patch sets are sample implementation because the spec is not merged yet.10:04
tetsuroThis spec can go now, I think. I haven't reviewed the patches though.10:05
masahitoBut looks no objection to the spec, so I started to push some code on top of the spec.10:05
hiro-kobayashiI'm +2 to the spec but keep +1 not to hide other reviewer's -110:05
hiro-kobayashiI haven't reviewed the following patches10:06
priteauI am reading through the spec now10:06
masahitothanks all.10:06
priteauI would like to make some minor grammar changes if that's ok10:06
masahitopriteau: Thanks. If you find something feel free to add your comment.10:07
masahitoI'll revise it by next meeting and we'll have a chance to talk it again.10:08
priteauI don't quite understand the part about naming10:09
openstackgerritHiroaki Kobayashi proposed openstack/blazar master: Add cleaning time  https://review.openstack.org/57502110:09
priteauYou want to rename it "Resource allocation API"? In this case shouldn't it be the title of the spec?10:09
masahitoI thought it when I started to writing the spec.10:10
masahitoBut resource "availability" API sounds the API returns free periods of the resource.10:11
priteauI think it's better to rename the spec10:12
masahitoBased on the Dublin PTG discussion, this API returns "allocation" of reservation to resources. So I thought "allocation" is much better to its name.10:12
masahitoNow this file name matches to blueprint url to easy track. Either is okay for me.10:14
priteauCan blueprint URL be changed?10:14
priteauAnyway, I wasn't thinking so much about the filename, but about the title header in the file10:15
masahitoI see. I thought you mentioned about file name :-) Okay, change the title.10:16
masahitoIf no more comments, let's move on to next series.10:18
priteauCan I make direct (minor) changes to the files via edit?10:18
priteauJust to make wording clearer10:19
masahitopriteau: Of course, np.10:19
* tetsuro is good with the either title10:19
openstackgerritPierre Riteau proposed openstack/blazar master: Spec: Resource availability API  https://review.openstack.org/57462810:21
masahitoRemaining series are Gabbi, Response Code fix, code structure and Dashboard support.10:21
priteauDashboard support just needs another +210:22
masahitopatch #1: https://review.openstack.org/#/c/580968/10:23
masahitopatch #2: https://review.openstack.org/#/c/58095510:23
hiro-kobayashiOh, I reviewed it and it was okay but forgot to +210:23
masahitoThanks10:24
masahitoCode structure change looks good to me unless it solves merge conflict.10:25
masahitohttps://review.openstack.org/#/c/576028/10:25
hiro-kobayashime, too10:25
tetsuroack will do.10:26
openstackgerritTetsuro Nakamura proposed openstack/blazar master: Fix unit test to have appropriate FakeHost  https://review.openstack.org/58131110:28
masahitoMove on to Gabbi support10:28
masahitopatch #1: https://review.openstack.org/#/c/580537/10:29
masahitopatch #2: https://review.openstack.org/#/c/580563/10:29
openstackgerritPierre Riteau proposed openstack/blazar master: Return 400 Bad Request for extra capability keys longer than 64 chars  https://review.openstack.org/57569910:29
openstackgerritTetsuro Nakamura proposed openstack/blazar master: Fix directory structure  https://review.openstack.org/57602810:30
openstackgerritPierre Riteau proposed openstack/blazar master: Add release note for response code fixes  https://review.openstack.org/57774710:30
masahitoJust one question for Gabbi tests?10:30
tetsurosure10:31
masahitoIsn't some .zuul change required to use gabbi in gate job?10:31
tetsuroI don't think any tempest stuff is now in gate job, am I right?10:32
priteauI believe we run tempest during the gate job10:33
hiro-kobayashi*-dvsm-* uses tempest, right?10:33
priteauYes, otherwise it wouldn't take ~40 minutes :-)10:34
tetsuroOkay, sorry.10:34
masahitoI means the tempest job executes the gabbi test or not.10:35
priteauI don't know how to check that Gabbi tests are run10:35
tetsuroI haven't look into how these api tests are integrated to zuul.10:35
tetsuroNo idea for now.10:35
masahitoBefore separating tempest plugin repo, the gate setting just execute test in blazar/tempest/scenario/test_*.py10:36
priteauWe use a legacy dvsm job, so it's quite possible gabbi isn't integrated into it10:36
masahitoThe directory is different from gabbi's one.10:36
openstackgerritMerged openstack/blazar master: Update pylint  https://review.openstack.org/57416610:37
masahitoAnd looks no execution order between leases.yaml and hosts.yaml. It could fail because of no reservable host.10:38
hiro-kobayashiWe also have to care https://review.openstack.org/#/c/580538/10:39
hiro-kobayashiIt will change API response codes. It affects the gabbi test.10:40
tetsuromasa: leases API works without reservable host if reservation field is empty10:40
tetsurohiro: yes, I'm now working on it.10:41
hiro-kobayashithanks! it's better to add #Depends-on tag to the gabbi patches10:42
masahitogot it.10:42
tetsurohiro: make sense.10:43
masahitoLast series is response code fix.10:43
hiro-kobayashiI didn't know it's possible to create a lease without reservations :-)10:43
masahitopatch #1: https://review.openstack.org/#/c/577747/10:43
masahitopatch #2: https://review.openstack.org/#/c/575699/10:43
masahitoreleasenote: https://review.openstack.org/#/c/573647/10:43
masahitosorry, releasenote: https://review.openstack.org/#/c/577747/10:44
priteauOr the full topic :-) https://review.openstack.org/#/q/topic:fix-response-code+status:open10:44
masahitonice :-)10:44
masahitoThe two patch has already been reviewed by some of you and close to go.10:45
openstackgerritPierre Riteau proposed openstack/blazar master: Change response status code when start_date and end_date are invalid  https://review.openstack.org/57364710:46
masahitoWhat I want to ask you is the releasenote patch should keep on top of response code change patch untile RC1? or Adding new releasenote that includes new response code change and exclude current one.10:47
openstackgerritPierre Riteau proposed openstack/blazar master: Return 400 Bad Request for extra capability keys longer than 64 chars  https://review.openstack.org/57569910:47
openstackgerritPierre Riteau proposed openstack/blazar master: Add release note for response code fixes  https://review.openstack.org/57774710:47
priteaumasahito: Is that for the other response code changes that hiro-kobayashi is working on?10:48
priteauIdeally we would have just one release note for everything10:48
masahitotetsuro will fix some response code.10:49
masahitoRelated to https://review.openstack.org/#/c/580538/10:49
priteauSorry, it was tetsuro, not hiro-kobayashi10:50
tetsuronp10:50
priteauYes, I think we should hold the release note until 580538 is merged10:50
masahitoUpdating merged releasenote needs bit complex work.10:50
hiro-kobayashiagree10:50
tetsuroagreed10:50
priteaumasahito: Can you put a W-1 on it to avoid accidental merge?10:50
masahitoSo I'd like to keep the releasenote patch in gerrit until RC110:50
openstackgerritVan Hung Pham proposed openstack/blazar master: convert py35 jobs to py3  https://review.openstack.org/58131610:51
masahitopriteau: nice idea! :-)10:51
tetsuroI'll rebase my fix in the series before the relnote if I'm ready.10:52
masahitotetsuro: thank you10:52
masahitoany other patches to review?10:53
hiro-kobayashiI think we covered all10:54
masahitoThe patch for blazar-nova fails because of miss config of zuulv3 and invalid constraints. https://review.openstack.org/#/c/555355/10:54
masahitoI'll try to fix it later.10:54
openstackgerritPierre Riteau proposed openstack/blazar master: Return 400 Bad Request for extra capability keys longer than 64 chars  https://review.openstack.org/57569910:55
priteauhiro-kobayashi: Can you please re-add a +2 to https://review.openstack.org/#/c/575699/10:55
priteauI made a couple of minor changes10:56
hiro-kobayashimasahito: thanks!10:56
hiro-kobayashiok10:56
masahitoThis meeting spends one hour and we had good progress.10:56
priteauWell done everyone10:57
priteauLet's revisit patches according to comments and try to merge more before next week?10:57
masahitoyes.10:57
masahitoIf less time to review, we can revisit the patches in next week.10:58
masahitoAlmost 12pm in UK and 8pm in Japan. Let's finish the meeting.10:58
priteauThanks a lot, bye everyone!10:59
masahitoThanks all! see you next week.10:59
masahitobye10:59
hiro-kobayashithank you and good bye all!10:59
tetsurothanks!11:00
*** hiro-kobayashi has quit IRC11:00
*** tetsuro has quit IRC11:00
openstackgerritMerged openstack/blazar master: Support blazar-dashboard installation in DevStack  https://review.openstack.org/58095511:06
*** masahito has quit IRC11:06
openstackgerritMerged openstack/blazar master: Change response status code when start_date and end_date are invalid  https://review.openstack.org/57364712:01
openstackgerritMerged openstack/blazar master: Return 400 Bad Request for extra capability keys longer than 64 chars  https://review.openstack.org/57569912:41
*** r-mibu has joined #openstack-blazar12:58
*** priteau has quit IRC15:36
*** r-mibu has quit IRC20:16
*** priteau has joined #openstack-blazar20:57
*** priteau has quit IRC21:37
*** priteau has joined #openstack-blazar21:37
*** priteau has quit IRC22:13

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