Wednesday, 2018-09-26

*** macza has joined #openstack-meeting-300:47
*** macza has quit IRC00:52
*** iyamahat_ has joined #openstack-meeting-301:01
*** iyamahat has quit IRC01:03
*** yamahata has quit IRC01:03
*** iyamahat_ has quit IRC01:07
*** iyamahat has joined #openstack-meeting-301:19
*** yamahata has joined #openstack-meeting-301:38
*** hongbin has joined #openstack-meeting-301:39
*** macza has joined #openstack-meeting-302:18
*** macza has quit IRC02:22
*** psachin has joined #openstack-meeting-302:39
*** apetrich has quit IRC02:42
*** diablo_rojo has quit IRC03:19
*** jamesmcarthur has joined #openstack-meeting-303:42
*** jamesmcarthur has quit IRC03:48
*** jamesmcarthur has joined #openstack-meeting-303:49
*** hongbin has quit IRC03:59
*** macza has joined #openstack-meeting-304:09
*** pcaruana has joined #openstack-meeting-304:14
*** jamesmcarthur has quit IRC04:21
*** jamesmcarthur has joined #openstack-meeting-304:23
*** jamesmcarthur has quit IRC04:27
*** yamamoto has quit IRC04:31
*** yamamoto has joined #openstack-meeting-304:31
*** pcaruana has quit IRC04:38
*** jamesmcarthur has joined #openstack-meeting-305:05
*** e0ne has joined #openstack-meeting-305:08
*** jamesmcarthur has quit IRC05:10
*** jamesmcarthur has joined #openstack-meeting-305:25
*** macza_ has joined #openstack-meeting-305:28
*** jamesmcarthur has quit IRC05:31
*** macza has quit IRC05:32
*** macza_ has quit IRC05:33
*** pcaruana has joined #openstack-meeting-305:43
*** apetrich has joined #openstack-meeting-305:46
*** jamesmcarthur has joined #openstack-meeting-305:47
*** e0ne has quit IRC05:49
*** jamesmcarthur has quit IRC05:51
*** jamesmcarthur has joined #openstack-meeting-306:08
*** jamesmcarthur has quit IRC06:12
*** diablo_rojo has joined #openstack-meeting-306:27
*** jamesmcarthur has joined #openstack-meeting-306:28
*** jamesmcarthur has quit IRC06:33
*** jamesmcarthur has joined #openstack-meeting-306:50
*** jamesmcarthur has quit IRC06:54
*** alexchadin has joined #openstack-meeting-307:03
*** jamesmcarthur has joined #openstack-meeting-307:10
*** TuanVu has joined #openstack-meeting-307:13
*** jamesmcarthur has quit IRC07:15
*** hoangcx has joined #openstack-meeting-307:15
*** psachin has quit IRC07:21
*** alexchadin has quit IRC07:25
*** psachin has joined #openstack-meeting-307:27
*** jamesmcarthur has joined #openstack-meeting-307:31
*** jamesmcarthur has quit IRC07:37
*** toabctl has joined #openstack-meeting-307:38
*** alexchadin has joined #openstack-meeting-307:51
*** jamesmcarthur has joined #openstack-meeting-307:53
*** alexchadin has quit IRC07:57
*** jamesmcarthur has quit IRC07:58
*** alexchadin has joined #openstack-meeting-307:59
alexchadin#startmeeting watcher08:00
openstackMeeting started Wed Sep 26 08:00:17 2018 UTC and is due to finish in 60 minutes.  The chair is alexchadin. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: watcher)"08:00
openstackThe meeting name has been set to 'watcher'08:00
alexchadino/08:01
TuanVuHi Alex08:01
TuanVuhave a nice day :)08:01
alexchadinTuanVu: you too!08:02
alexchadinTuanVu: how are you?08:02
TuanVuI'm doing fine, thank you very much :D08:02
TuanVuI'm doing some tests for watcher live migration feature in my local environment08:03
alexchadinTuanVu: what strategy do you use?08:03
TuanVuI intend to test the ability to migrate VM from 1 compute node to another when host's workload (eg: CPU) is too high08:05
TuanVuit should be "workload balance migration" strategy, right?08:06
alexchadinTuanVu: I'd recommend you to use workload stabilization strategy08:06
alexchadinTuanVu: we test this strategy on production clusters08:07
TuanVuthank you, Alex08:08
TuanVuhowever, I don't see your mentioned strategy on this list08:08
TuanVuhttps://docs.openstack.org/watcher/latest/strategies/index.html08:08
TuanVucould you please point out exactly it is which one?08:09
alexchadinTuanVu: Workload Overload standard deviation08:09
*** jamesmcarthur has joined #openstack-meeting-308:09
*** e0ne has joined #openstack-meeting-308:10
TuanVuawesome! thanks08:10
TuanVuas I can see, it requires metrics from ceilometer08:11
TuanVuare there anyway for it to work with metric from "Monasca"?08:11
alexchadinTuanVu: that's right, it's recommended to use ceilometer+gnocchi08:11
alexchadinTuanVu: I haven't tested this strategy with Monasca yet, I'm not sure if Monasca provides SNMP metrics08:12
*** jamesmcarthur has quit IRC08:13
TuanVuthanks for your recommendation, I'll test this strategy in my environment08:13
alexchadinTuanVu: do you have any other question regarding Watcher?08:16
TuanVuthat's all I have for now :)08:16
alexchadinTuanVu: you don't use ceilometer+gnocchi in your env?08:17
TuanVuyes, I do use ceilometer+gnocchi, but just want to test out monasca as well08:19
*** e0ne has quit IRC08:20
alexchadinTuanVu: great :) this strategy works with CPU and RAM metrics. You can use them both or separately08:21
TuanVuthank you, that's awesome!08:21
*** jamesmcarthur has joined #openstack-meeting-308:24
alexchadinTuanVu: unfortunately, other core developers haven't come today on meeting08:25
TuanVuso ... we can finish the meeting here, I guess?08:27
alexchadinTuanVu: I suppose so08:29
alexchadinTuanVu: thank you for attending!08:29
*** jamesmcarthur has quit IRC08:29
TuanVuit's my pleasure :) Thanks for your sharing, Alex08:29
TuanVuit means a lot for me, I really appreciate your kindness08:29
TuanVusee you next time :)08:30
alexchadinTuanVu: see you! :)08:30
alexchadin#endmeeting08:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:30
openstackMeeting ended Wed Sep 26 08:30:27 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2018/watcher.2018-09-26-08.00.html08:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2018/watcher.2018-09-26-08.00.txt08:30
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2018/watcher.2018-09-26-08.00.log.html08:30
*** hoangcx has left #openstack-meeting-308:32
*** jamesmcarthur has joined #openstack-meeting-308:40
*** jamesmcarthur has quit IRC08:45
*** apetrich has quit IRC08:49
*** tssurya has joined #openstack-meeting-308:54
*** jamesmcarthur has joined #openstack-meeting-308:56
*** jamesmcarthur has quit IRC09:01
*** e0ne has joined #openstack-meeting-309:04
*** alexchadin has quit IRC09:06
*** jamesmcarthur has joined #openstack-meeting-309:12
*** jamesmcarthur has quit IRC09:17
*** alexchadin has joined #openstack-meeting-309:20
*** pbourke has quit IRC09:22
*** pbourke has joined #openstack-meeting-309:23
*** alexchadin has quit IRC09:25
*** witek_ has joined #openstack-meeting-309:26
*** witek has quit IRC09:26
*** jamesmcarthur has joined #openstack-meeting-309:28
*** jamesmcarthur has quit IRC09:33
*** alexchadin has joined #openstack-meeting-309:42
*** jamesmcarthur has joined #openstack-meeting-309:44
*** jamesmcarthur has quit IRC09:49
*** jamesmcarthur has joined #openstack-meeting-310:00
*** diablo_rojo has quit IRC10:02
*** jamesmcarthur has quit IRC10:04
*** jamesmcarthur has joined #openstack-meeting-310:15
*** jamesmcarthur has quit IRC10:22
*** e0ne has quit IRC10:27
*** jamesmcarthur has joined #openstack-meeting-310:33
*** yamamoto has quit IRC10:35
*** jamesmcarthur has quit IRC10:38
*** Luzi has joined #openstack-meeting-310:42
*** jamesmcarthur has joined #openstack-meeting-310:49
*** alexchadin has quit IRC10:49
*** jamesmcarthur has quit IRC10:53
*** alexchadin has joined #openstack-meeting-310:58
*** yamamoto has joined #openstack-meeting-311:00
*** alexchadin has quit IRC11:03
*** TuanVu has quit IRC11:04
*** jamesmcarthur has joined #openstack-meeting-311:05
*** jamesmcarthur has quit IRC11:09
*** psachin has quit IRC11:13
*** pcaruana has quit IRC11:15
*** jamesmcarthur has joined #openstack-meeting-311:20
*** jamesmcarthur has quit IRC11:25
*** psachin has joined #openstack-meeting-311:27
*** jamesmcarthur has joined #openstack-meeting-311:36
*** jamesmcarthur has quit IRC11:41
*** raildo has joined #openstack-meeting-311:51
*** jamesmcarthur has joined #openstack-meeting-311:52
*** e0ne has joined #openstack-meeting-311:53
*** alexchadin has joined #openstack-meeting-311:57
*** jamesmcarthur has quit IRC11:57
*** witek_ is now known as witek12:06
*** jamesmcarthur has joined #openstack-meeting-312:08
*** apetrich has joined #openstack-meeting-312:11
*** jamesmcarthur has quit IRC12:13
*** jamesmcarthur has joined #openstack-meeting-312:15
*** alexchadin has quit IRC12:17
*** alexchadin has joined #openstack-meeting-312:25
*** jamesmcarthur has quit IRC12:31
*** yamamoto has quit IRC12:35
*** psachin has quit IRC12:41
*** jamesmcarthur has joined #openstack-meeting-312:46
*** liuyulong has joined #openstack-meeting-312:50
*** jamesmcarthur has quit IRC12:52
*** jamesmcarthur has joined #openstack-meeting-312:55
*** alexchadin has quit IRC13:02
*** elmiko has left #openstack-meeting-313:08
*** yamamoto has joined #openstack-meeting-313:13
*** dkrol has joined #openstack-meeting-313:16
*** alexchadin has joined #openstack-meeting-313:17
*** yamamoto has quit IRC13:21
*** yamamoto has joined #openstack-meeting-313:21
*** hongbin has joined #openstack-meeting-313:40
*** alexchadin has quit IRC13:44
*** slaweq has quit IRC13:45
*** alexchadin has joined #openstack-meeting-313:46
*** jamesmcarthur has quit IRC13:49
*** alexchadin has quit IRC13:50
*** jamesmcarthur has joined #openstack-meeting-313:51
*** witek has quit IRC13:52
*** jamesmcarthur has quit IRC13:56
*** mjturek has joined #openstack-meeting-313:59
*** mpiwowarczy has joined #openstack-meeting-314:02
*** yamamoto has quit IRC14:03
*** yamamoto has joined #openstack-meeting-314:04
*** bobh has joined #openstack-meeting-314:08
*** yamamoto has quit IRC14:09
*** slaweq has joined #openstack-meeting-314:11
*** jamesmcarthur has joined #openstack-meeting-314:12
*** bobh has quit IRC14:13
*** slaweq has quit IRC14:15
*** jamesmcarthur has quit IRC14:16
*** Luzi has quit IRC14:27
*** moguimar has quit IRC14:27
*** jamesmcarthur has joined #openstack-meeting-314:28
*** moguimar has joined #openstack-meeting-314:30
*** jamesmcarthur has quit IRC14:32
*** bobh has joined #openstack-meeting-314:35
*** jamesmcarthur has joined #openstack-meeting-314:43
*** jamesmcarthur has quit IRC14:47
*** yamamoto has joined #openstack-meeting-314:52
*** joadavis has joined #openstack-meeting-314:56
*** koji_n has joined #openstack-meeting-314:58
*** jamesmcarthur has joined #openstack-meeting-314:59
*** witek has joined #openstack-meeting-314:59
witek#startmeeting monasca15:00
openstackMeeting started Wed Sep 26 15:00:46 2018 UTC and is due to finish in 60 minutes.  The chair is witek. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
witekHello everyone15:01
*** pandy has joined #openstack-meeting-315:01
*** pcaruana has joined #openstack-meeting-315:01
koji_nhello15:01
witekhi koji_n, hi pandy15:01
pandyHi witek:)15:01
joadavishi15:01
witekhi15:02
*** dougsz has joined #openstack-meeting-315:02
witekthe agenda is pretty full again today15:02
witekthat's nice :)15:02
srwilkerso/15:02
witeklet's start with leftovers15:02
witekhttps://etherpad.openstack.org/p/monasca-team-meeting-agenda15:02
witek#topic pre-upgrade checks15:02
*** openstack changes topic to "pre-upgrade checks (Meeting topic: monasca)"15:02
witekwe have started this actually last week15:03
*** jamesmcarthur has quit IRC15:03
*** bobh has quit IRC15:03
witekthere is a new component in oslo for this15:03
witekhttps://github.com/openstack/oslo.upgradecheck15:03
witekshould we use this one?15:03
joadavisI didn't grab the oslo.upgradecheck code because it was still being worked on last week.  It would be nice to use something consistent, but the code is still developing15:04
joadavisso I thought it would be good to have a very simple start then refactor it later to use the library when it is available15:05
dougszThe library certainly seems very green15:05
joadavisAlso, the code I wrote will likely need to be moved to a good place for deployment15:06
witekMatt has left you some comments in review15:06
*** moguimar has quit IRC15:06
joadavisyes, I've been working some bugs and haven't incorporated his comments yet, but they were good feedback15:07
joadaviss/bugs/unrelated bugs/15:07
witek:)15:07
witekso, you want to continue to work on this, or prefer to come back to this later?15:07
joadavisI don't think it is top priority, but can tinker with it when i have time15:08
joadavisIf someone else is interested they are welcome to take it up15:08
witekok, thanks15:09
*** moguimar has joined #openstack-meeting-315:09
witek#topic monasca-notification clean-up15:09
*** openstack changes topic to "monasca-notification clean-up (Meeting topic: monasca)"15:09
witekthe first change should probably be the schema update15:10
dougszSo we hit some issues configuring plugins via Oslo15:10
dougszYeah - agreed15:11
dougszIt would be nice to push those old patches through15:11
witekyes, we need them15:11
witekI've seen you've added this to our board15:11
witekhttps://storyboard.openstack.org/#!/board/11115:11
dougszI 've got enough feedback from Johannes to fix up the alembic migration15:12
witekgreat15:12
dougszThanks to Johannes  + Amir for the review15:12
dougszSo that's probably it on this for now - I will focus on the old patches in the little time I have at the moment and circle back around to Charana's ones when those are done.15:13
witekis there a particular sequence in which the changes should be merged?15:13
dougszAlso, thanks Witek for taking a look!15:13
dougszI will add a 'depends on' to the commit message15:13
witekthanks15:14
*** jamesmcarthur has joined #openstack-meeting-315:14
witekbtw. during ptg we've agreed to create a second board for tracking bug fixing15:15
dougszah, ok15:15
witekI think the last two changes from your set would be good candidates15:15
witekI haven't created the board yet though15:15
dougszSounds good, I can look at moving it when we have the board15:15
witekwill do tomorrow15:15
dougszthanks15:16
witekthanks Doug for working on this15:16
witek#topic new Grafana image15:16
*** openstack changes topic to "new Grafana image (Meeting topic: monasca)"15:16
dougsznp15:16
dougszpandy?15:17
*** bobh has joined #openstack-meeting-315:17
pandyHi Witek, I have requested two features to be in grafana like getting "OK" & "UNDETERMINED" state in notification and fix "save" in one click15:17
pandyit was fixed by Charana & Dougz verified and pushed to master https://github.com/monasca/monasca-grafana/commit/85b7eb46c1cbb561e6c7737b3ee75271fa83af7b15:17
witekwe have pushed the new image today15:17
witekhttps://hub.docker.com/r/monasca/grafana/15:17
dougszNice - I thought I saw that fly past my inbox15:18
pandyIt will be great if we udpate this grafana enhancement to new image, currently, i did rebuild in my own dockerhub repo15:18
witekpandy: happened today15:18
pandyoh great :)15:18
*** jamesmcarthur has quit IRC15:18
witekhttps://hub.docker.com/r/monasca/grafana/tags/15:18
witek4.0.0-1.5.115:19
pandySure i will check it :) Thats it related to monasca- grafana, let me know can i start my next topic in agend which is lsited at bottom now or will wait ? :)15:19
witeklet's go in the sequence please15:20
witek#topic Stein prios15:20
*** openstack changes topic to "Stein prios (Meeting topic: monasca)"15:20
witekI have put together the results of our priorisation game15:20
*** moguimar has quit IRC15:20
witekas we discussed earlier, I didn't want to put too many tasks15:21
dougszI started writing the Merge APIs spec earlier will have it finished today, then I can add a link to the doc.15:21
witekgreat, I just wanted to ask you folks to add the descriptions :)15:22
dougsz:)15:22
dougszWill do.15:23
witekalso, if you think there is anything important we should add there during the cycle15:23
witekwe're free to do so15:23
witek#topic Kafka config opts in monasca-api15:23
*** openstack changes topic to "Kafka config opts in monasca-api (Meeting topic: monasca)"15:23
dougszIt looks like some refactoring left these behind15:24
dougszJust wanted to check I hadn't missed something before removing them?15:24
witekalso, that will probably change anyway during the work with confluent-kafka client15:24
dougszYeah - envisaged some overlap15:25
witekI want to finish my Kafka spec this week15:25
witekhttps://review.openstack.org/60126815:26
witekso I will go through these options as well15:26
witekand will leave you a comment in story15:26
dougszAwesome, thanks witek.15:26
dougszI guess we could backport any small patch to remove them to avoid confusing people with the generated config file from tox15:27
witekso you mean, remove all of them now to be in sync with auto-generated, and then backport if needed?15:28
dougszYeah15:28
witekyes, it will work as well15:29
*** jamesmcarthur has joined #openstack-meeting-315:29
witek#topic libvirt upgrade15:30
*** openstack changes topic to "libvirt upgrade (Meeting topic: monasca)"15:30
witekjoadavis: have you added this one?15:30
joadavisyes.15:31
joadavisI heard there was a plan for nova to update the libvirt and qemu version for the T release15:31
joadavisI just wanted to raise it as a sanity check here - I don't think it will be a problem15:32
witekdo you have any reference to additional information about this upgrade?15:32
witekthe problem with libvirt plugin is, that we don't have any automated testing included15:33
joadavisthere was an email to the openstack-dev mailing list...15:33
joadavisProposal --------  Looking at the DistroSupportMatrix[2], it seems like we can pick the libvirt and QEMU versions supported by the next LTS release of Ubuntu -- 18.04; "Bionic", which are:      libvirt: 4.0.0     QEMU:    2.1115:34
*** jamesmcarthur has quit IRC15:34
witekshould we add a task to the backlog for this?15:35
joadavisI think the Operating Systems will support it.  It may be good for us to have a task to at least check the release notes for libvirt for any api changes or things that might need an update15:36
joadavisin monasca-agent15:36
witekalso, only partially related, do you know if we could run tempest tests on bionic already?15:37
joadavisI don't know.  Are other projects doing that already?15:37
witekhaven't checked, just came to my mind15:38
joadavisgood thought15:38
witekcould you create a testing task for monasca-agent and add it to the board please?15:39
joadavissure15:39
witekthanks joadavis15:39
witekI'll have a look at running devstack plugin on bionic15:40
witek#topic reviews15:40
*** openstack changes topic to "reviews (Meeting topic: monasca)"15:40
witekrpm-packaging change looks good to me15:41
joadavis:thumbsup"15:41
witek#topic bugs15:42
*** openstack changes topic to "bugs (Meeting topic: monasca)"15:42
witekhttps://storyboard.openstack.org/#!/story/200159315:42
witekto be honest, I haven't looked in detail into it, but don't like the sudoers idea15:43
witekit would make the installation/configuration even more complex15:43
witekother thoughs?15:44
joadavisYeah, I was struggling with a good answer.  Another engineer here is looking at the problem.  It appears that in the rpm-packaging there are already a few programs set up for monasca-agent user which are granted in the sudoers file15:45
*** jamesmcarthur has joined #openstack-meeting-315:45
*** dklyle has joined #openstack-meeting-315:45
*** munimeha1 has joined #openstack-meeting-315:45
joadavisI'm not sure how it works, but if it is possible to grant elevated permission to the monasca-agent user for just the ip command, that might be good.  But as you said, it is a more complex configuration15:46
*** macza has joined #openstack-meeting-315:46
joadavisI wanted to bring it up in case our monasca community has some other great ideas. :)15:46
witekwe'll ping our team about it15:47
witekalso, we'll add it to our new bugs board15:47
joadavisthanks15:47
witekI think we should try to find a nicer solution15:48
witekbut if that doesn't work, we could set up sudoers15:48
witek#topic monasca-agent in large deployments15:49
*** openstack changes topic to "monasca-agent in large deployments (Meeting topic: monasca)"15:49
*** jamesmcarthur has quit IRC15:49
witekpandy: that's yours, right?15:50
pandyHi15:50
pandyyes mine15:50
pandyquick explanation of my environment15:50
pandyInstalled monasca using docker on 3 dedicated baremetals, Please note: used monasca docker images for monasca-api, grafana, notification, mysql, influxdb, where kafka & zookeeper used different version15:50
pandyfor scaling and running on docker swarm mode15:50
pandyIn 500+ compute installed monasca agent and did configuration using monasca-setup as per https://github.com/openstack/monasca-agent/blob/master/docs/Agent.md15:51
pandyWhere added libvirt.yaml plugin to collect VM metrics and here configuration of libvirt.yaml  http://paste.openstack.org/show/730940/15:51
pandyIssue is some of monasca agent is hitting Neutron API very frequently15:51
pandyjust suspected  these parameters are causing issue so disabled it15:51
pandy""vm_network_check_enable: false" "ping_check: false" "vm_ping_check_enable: false""15:51
pandyHere my question: "Would like to know "Which Monasca agent plugins & parameters will hit Neutron API and whats the interval period ?" & "How can control hitting to Neutron API ?""15:51
*** macza has quit IRC15:51
pandysorry i was prepared already, so sent messages in row.15:52
*** macza has joined #openstack-meeting-315:52
witekis libvirt the only plugin, you've enabled on compute nodes?15:52
pandyby default it has given me process, cpu, network and i have added libvirt.yaml to it15:53
pandydefault i have congestion, disk, load, network, process, cpu, memory, ntp. I have added "libvirt" into /etc/monasca/agent/conf.d15:54
pandywould like to know which plugin is hitting Neutron API ?15:54
pandyNeutron.yaml here http://paste.openstack.org/show/730940/15:55
*** tssurya has quit IRC15:55
witeklibvirt plugin communicates with Neutron, but I cannot answer your question about configuration option right now15:55
*** jamesmcarthur has joined #openstack-meeting-315:56
*** eglute has joined #openstack-meeting-315:56
pandylibvirt and ovs plugin only hits neutron15:56
pandyas per my understanding15:56
koji_nat this moment, ovs and libvirt plugin is using neutronclient15:56
pandyi am using libivirt, where disabling "ping_check" will stop hitting neutron API ?15:56
*** jamesmcarthur has quit IRC15:57
*** jamesmcarthur has joined #openstack-meeting-315:57
pandyFYI, we are not using namespace in compute nodes, so i feel "ping_check" no need, other than that what are parameters inside libivirt will hit Neutron API15:57
witekkoji_n: will you be able to check this?15:58
koji_nhttps://github.com/openstack/monasca-agent/blob/819822529422e68614dd4c3b95a9b530795e4bcf/monasca_agent/collector/checks_d/libvirt.py#L186-L19215:58
koji_nprobably, pandy is correct15:58
koji_nneutronclient is used only the above section in libvirt plugin15:58
witekthat was quick, thanks koji_n :)15:59
pandykoji_n,  whether "ping_check" only use neutron API  ?15:59
koji_nnp, but i didn't test it, so maybe it's wrong15:59
pandyHow about "vm_network_check_enable" ""vm_ping_check_enable: false""16:00
witekhave to close the meeting16:00
witekthanks for joining everyone16:00
dougszThanks witek, bye all16:00
joadavisthanks all16:00
witeksee you next week16:00
pandywitek, i need someone from libvirt to help out this16:00
*** dougsz has left #openstack-meeting-316:00
witek#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:00
openstackMeeting ended Wed Sep 26 16:00:55 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2018/monasca.2018-09-26-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2018/monasca.2018-09-26-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2018/monasca.2018-09-26-15.00.log.html16:01
eglute#startmeeting interopwg16:01
openstackMeeting started Wed Sep 26 16:01:09 2018 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: interopwg)"16:01
openstackThe meeting name has been set to 'interopwg'16:01
*** pandy has left #openstack-meeting-316:01
eglute#chair hogepodge16:01
openstackCurrent chairs: eglute hogepodge16:01
eglute#topic agenda16:01
*** openstack changes topic to "agenda (Meeting topic: interopwg)"16:01
eglute#link https://etherpad.openstack.org/p/InteropWhistler.1916:01
egluteHello Everyone!16:01
egluteLet me know if you are here for interop meeting!16:02
eglutehogepodge are you around?16:03
*** markvoelker has joined #openstack-meeting-316:03
markvoelkero/16:03
egluteHello markvoelker!16:03
eglute#chair markvoelker16:03
openstackCurrent chairs: eglute hogepodge markvoelker16:03
eglutelooks like it is just the two of us here today16:04
markvoelker=)  I say we assign all the action items to hogepodge and call it a day then. =p16:04
*** jamesmcarthur has quit IRC16:04
egluteSounds great to me!16:05
eglute#action hogepodge will do all the things16:05
eglute:D16:05
eglutethanks for submitting the nova update16:05
*** jamesmcarthur has joined #openstack-meeting-316:05
eglutei left a comment, i worry it would impact public clouds16:05
markvoelkerHm, I'm curious about that.  The capability isn't backend-specific so disabling it would be a policy decision, right?16:06
markvoelker#link https://review.openstack.org/#/c/601638/ Add compute-servers-create-multiple as advisory16:06
egluteyes, most likely policy? wonder if public clouds allow it16:07
eglutemaybe a non-issue16:07
hogepodgehi!16:07
eglutehello Chris!16:07
markvoelkerDo you know of public clouds that don't?16:07
eglutemarkvoelker i do not. i need to test it on rackspace cloud to see if they allow it16:08
markvoelkerOk, that'd be good...I can try to poke at a few public clouds I have accounts on too but seems like I recall using this before with them.16:09
egluteah ok. i will check and update16:09
markvoelkerhogepodge you mentioned using compter-servers-create-multiple fairly regularly, right?  Mostly on a private setup though?16:10
hogepodgeyeah, I use it in my ironic lab16:10
markvoelkerah, ok16:10
hogepodgeI also use terraform a lot, but I don't know if they do it as a batch or as a loop16:11
markvoelkerSo since eglute raised a concern about whether public clouds support this, I suggest taking a look around at a few and maybe pinging a few contacts we have.  Worst case, it'll be advisory and operators will shout then so we can strike it before it becomes required.16:11
eglutesounds good to me16:12
egluteok, since there are at least 3 of us here, would either markvoelker or hogepodge give a PTG summary?16:13
markvoelkersure16:13
markvoelker#link https://etherpad.openstack.org/p/InteropRefstackPTGDenver_2018 Denver PTG etherpad16:14
markvoelkerMost of the morning we used as a working session to clear our backlog of reviews and discuss a few outstanding items16:14
markvoelkerAs a result, we merged several patches and submitted a few more follow-up patches which have also mostly merged16:14
eglutethanks for that!16:14
markvoelkerThese included some Cinder stuff, the most notable being the deprecation of the v2 API from the required list16:15
markvoelkerWe also decided to target the November BoD meeting for the next guideline approval16:15
eglutesounds good16:15
markvoelkerOnce we decide on the create-compute-servers-multiple patch I'll likely get a patch ready to create the formal document16:16
eglutethanks markvoelker16:16
markvoelkerLater in the day we also chatted with Georg about NFV stuff, and I chatted again with Ildiko over breakfast the next day16:16
*** iyamahat has quit IRC16:17
*** yamahata has quit IRC16:17
markvoelkerNeither Georg or I have had as much time as we'd have liked to work on an NFV program, and we're not currently seeing a lot of noise about from the community side either16:17
egluteok. any other take aways from NFV discussions?16:17
markvoelkerWe are seeing, for example, a lot of telco requirements that have a lot of similarities and could be simplified if we could check a box stating compliance with an interop program, so feels like there's still some demand out there16:18
markvoelkerWe discussed that maybe a formal interop program isn't the way to get started though16:18
markvoelkerPerhaps, for example, we might do some sort of event (imagine, for example, a sort of interop challenge where the workload was a VNF like Clearwater or some such) to drum up interest, then see who's willing to put some further work in16:19
egluteok, so pause on the work on formal NFV program for now?16:20
eglutei do like the idea of an event16:20
markvoelkerHow to go about this would likely be a discussion we need to have with the Foundation folks and/or BoD, so we may want to talk about it at the November meeting16:20
egluteok, that sounds good16:21
eglutethank you16:21
markvoelkerWe also chatted a bit about some different stakeholders that we havent' spent much time with so far...for example, VNF vendors16:21
egluteanything else from the PTG?16:21
markvoelkerI think that's about it...we also chatted with gema a bit about ARM and some questions around image interop16:22
eglutewhat were the image interop questions?16:22
hogepodgecan you call clouds interoperable if they can't boot the same image (arm vs x86)16:23
markvoelkerJust about whether images themselves ought to be part of an interop test...e.g. if I have an x86 cloud, the cirros image I boot on it wont' work on my ARM cloud16:23
markvoelkerBut the API to upload it, boot a server from it, etc do work16:23
markvoelkerCame down to a question of API vs the data you feed to it16:23
egluteright, that makes sense16:23
hogepodgemy opinion is that any api that takes bad data will barf. arm image to x86 cloud is bad data16:24
markvoelker++16:24
eglutehow many clouds are using arm? any idea?16:24
hogepodgeTwo as far as I know so far.16:24
hogepodgeLinaro and Vexxhost16:24
markvoelkerLinaro and vexxhost16:24
markvoelker*jinx16:25
hogepodgeAww, now I can't speak16:25
markvoelker=p16:25
eglutehahah16:25
markvoelkerIt's ok, it's IRC and you can still type16:25
hogepodge#link http://wondermark.com/378/ jinx16:25
egluteso how about VMs? they would face the same issue right, arm vs x86?16:26
markvoelkerNot sure I follow?16:27
hogepodgekvm vs vmware vs xen, for example16:27
eglutetrue... i guess we dont address that right now anyways16:27
hogepodgeWe kind of covered that too. Discovery of expected image types is cloud specific, but there's no API to expose that implementation afaik16:27
hogepodgeSo it's up to the operator to provide that information.16:28
markvoelkerOh, ok....right.  YEah, same deal: the API's work, but you can feed any API parameters that don't make sense and things break.16:28
egluteright16:28
markvoelkerWe actually mentioned things like image conversion that work for the hypervisor case, fwiw.  Not so much for the processor architecture case.16:28
markvoelkerBut the main point was that the API's are available and work and the tempest tests pass.16:29
persiaRegarding architecture: images are supposed to set architecture, and nova scheduler does the right thing.  When folk upload images without architecture hints, they are scheduled on the default architecture for the cloud.  Accidents should only happen for misconfigured cloudds.  Interop probably benefits from setting architecture on images to avoid the problem.16:29
hogepodgeThis is an instance where clouds may behave differently. Some clouds do conversion in the background.16:29
hogepodgeDo tests exist in tempest to exercise that capability persia?16:30
*** iyamahat has joined #openstack-meeting-316:31
persiahogepodge: That I don't know.  Sadly, somewhere between Grizzly and Queens, we lost track of architecture, and all the docs stopped recommending setting it: I don't know if the tempest multiarch tests degraded.  For Rocky we now have the concept of a "default" architecture for a given cloud to work around that bug, but I don't know that any tempest tests were added to test that bit.16:31
eglutei am doing migrations now from old openstack versions to newer ones, and in some cases have to rely on glance images working properly. however, have not had to deal with different architectures. other than that, i must say that openstack is mostly interoperable between different openstack providers/deployers/operators as far as i have seen16:31
eglutei have not been setting architecture for images i dont think. I am not even sure you can pass architecture as a parameter on image create16:34
persiaNote that it *is* possible to construct an UEFI image that can boot for multiple architectures, but I don't think glance supports this (other than by not specifying architecture).16:34
persiaeglute: You very much can pass architecture on image storage in glance: it's one of the core properties.16:35
eglutethanks persia i will need to look a little more into it16:35
eglutepersia i am not seeing it in the api. is that part of glance.conf, or something else? https://developer.openstack.org/api-ref/image/v2/index.html#images16:36
persiaeglute: Feel free to ask me (probably in #openstack-dev) if you have questions about it.16:36
eglutethanks persia16:37
markvoelkereglute: https://docs.openstack.org/glance/latest/admin/useful-image-properties.html16:37
hogepodgeOn my queens cloud arch is required. I did have to set hypervisor type on flavors for baremetal. I wonder if defaults are x86 centric16:38
hogepodgemeant to say arch is not required16:38
eglutethanks markvoelker16:38
*** jamesmcarthur has quit IRC16:38
persiaeglute: Look under "show detail" in GET /v2/schemas/images16:39
markvoelkerSo let's see....past that I think about the only thing open is "make consistency job gating" patch that hogepodge was working on....16:39
markvoelker#link https://review.openstack.org/#/c/601633/ Make consistency job gating16:39
eglutethanks persia!! makes sense16:40
markvoelkerhogepodge:  just chugging along iterating on patchsets, looks like?16:40
eglutethanks hogepodge for creating the patch16:40
hogepodgeOnce this lands (I just sent an update to address the issues this morning), we can add to Tempest. Talked with gmann and they're ok with making it a job in their repo once it's running.16:40
eglutegreat, thanks hogepodge16:41
hogepodgehopefully I got my ansible/yaml variable syntax right16:41
eglutehogepodge do you think there will be keystone or swift updates for the next guideline?16:43
hogepodgeI'm not expecting any, but I haven't given it the attention it deserves.16:43
*** e0ne has quit IRC16:43
egluteok... i expect no major changes, but would be good to check16:44
*** jamesmcarthur has joined #openstack-meeting-316:44
markvoelkeranything else today?16:44
eglutemarkvoelker anything for heat?16:45
markvoelkerNope, not expecting anything.  Chatted with Rico a bit in the hallway.  Since we're not doing resource validation this cycle there's not likely to be any changes.16:45
eglutegreat thank you16:46
eglutei think that is it then unless someone has anything else for today16:46
markvoelkerI should add: no changes in terms of new stuff being added, though we probably do need to promote some of the advisory stuff16:47
markvoelkerI have an AI to do that but didn't get to it before dashing home for the hurricane16:47
eglutethanks16:47
eglutemarkvoelker hopefully no more hurricanes for you this year16:47
eglutethanks everyone!16:48
eglute#endmeeting16:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:48
openstackMeeting ended Wed Sep 26 16:48:32 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interopwg/2018/interopwg.2018-09-26-16.01.html16:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interopwg/2018/interopwg.2018-09-26-16.01.txt16:48
openstackLog:            http://eavesdrop.openstack.org/meetings/interopwg/2018/interopwg.2018-09-26-16.01.log.html16:48
*** joadavis has left #openstack-meeting-316:49
*** yamahata has joined #openstack-meeting-316:50
*** koji_n has quit IRC17:02
*** slaweq has joined #openstack-meeting-317:11
*** slaweq has quit IRC17:15
*** jamesmcarthur has quit IRC17:16
*** jamesmcarthur has joined #openstack-meeting-317:21
*** iyamahat_ has joined #openstack-meeting-317:29
*** iyamahat has quit IRC17:32
*** njohnston has joined #openstack-meeting-317:42
*** slaweq has joined #openstack-meeting-318:12
*** diablo_rojo has joined #openstack-meeting-318:18
*** iyamahat_ has quit IRC18:19
*** iyamahat has joined #openstack-meeting-318:19
*** slaweq has quit IRC18:22
*** pcaruana has quit IRC18:24
*** yamamoto has quit IRC18:26
*** yamamoto has joined #openstack-meeting-318:26
*** jamesmcarthur has quit IRC18:42
*** jamesmcarthur has joined #openstack-meeting-318:47
*** slaweq has joined #openstack-meeting-319:11
*** slaweq has quit IRC19:15
*** e0ne has joined #openstack-meeting-319:15
*** slaweq has joined #openstack-meeting-319:24
*** e0ne has quit IRC19:30
*** jamesmcarthur has quit IRC19:32
*** jamesmcarthur has joined #openstack-meeting-319:41
*** jamesmcarthur has quit IRC19:46
*** jamesmcarthur has joined #openstack-meeting-319:48
*** jamesmcarthur has quit IRC19:52
*** jamesmcarthur has joined #openstack-meeting-319:55
*** bnemec has quit IRC20:10
*** bnemec has joined #openstack-meeting-320:15
*** raildo has quit IRC20:36
*** munimeha1 has quit IRC20:40
*** bobh has quit IRC20:59
*** slaweq has quit IRC21:06
*** slaweq has joined #openstack-meeting-321:11
*** slaweq has quit IRC21:15
*** jamesmcarthur has quit IRC21:18
*** jamesmcarthur has joined #openstack-meeting-321:19
*** jamesmcarthur has quit IRC21:33
*** bobh has joined #openstack-meeting-321:35
*** bobh has quit IRC21:40
*** jamesmcarthur has joined #openstack-meeting-321:54
*** jamesmcarthur has quit IRC21:58
*** dklyle has quit IRC22:02
*** slaweq has joined #openstack-meeting-322:11
*** jamesmcarthur has joined #openstack-meeting-322:14
*** slaweq has quit IRC22:16
*** jamesmcarthur has quit IRC22:19
*** jamesmcarthur has joined #openstack-meeting-322:35
*** jamesmcarthur has quit IRC22:40
*** hongbin has quit IRC22:51
*** jamesmcarthur has joined #openstack-meeting-322:56
*** jamesmcarthur has quit IRC22:57
*** jamesmcarthur has joined #openstack-meeting-322:57
*** macza has quit IRC23:09
*** macza has joined #openstack-meeting-323:10
*** macza has quit IRC23:14
*** jamesmcarthur has quit IRC23:17
*** jamesmcarthur has joined #openstack-meeting-323:19
*** jlvillal has joined #openstack-meeting-323:24
*** dklyle has joined #openstack-meeting-323:26
*** macza has joined #openstack-meeting-323:34
*** macza has quit IRC23:39
*** liuyulong has quit IRC23:47
*** jamesmcarthur has quit IRC23:50

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