Wednesday, 2015-02-18

*** carl_baldwin has quit IRC00:08
*** carl_baldwin has joined #openstack-meeting-400:27
*** VW_ has quit IRC00:28
*** banix has joined #openstack-meeting-400:28
*** banix has quit IRC00:35
*** markvoelker has quit IRC00:37
*** markvoelker has joined #openstack-meeting-400:37
*** banix has joined #openstack-meeting-400:39
*** markvoelker has quit IRC00:42
*** david-lyle has quit IRC00:44
*** banix has quit IRC00:46
*** banix has joined #openstack-meeting-400:52
*** ivar-lazzaro has quit IRC01:08
*** ivar-lazzaro has joined #openstack-meeting-401:09
*** ivar-lazzaro has quit IRC01:10
*** Rockyg has quit IRC01:11
*** ivar-lazzaro has joined #openstack-meeting-401:11
*** banix has quit IRC01:32
*** banix has joined #openstack-meeting-401:35
*** sigmavirus24 is now known as sigmavirus24_awa01:38
*** salv-orlando has quit IRC01:58
*** markvoelker has joined #openstack-meeting-401:59
*** banix has quit IRC02:07
*** banix has joined #openstack-meeting-402:11
*** david-lyle has joined #openstack-meeting-402:11
*** SridharRamaswamy has quit IRC02:11
*** mwang2 has quit IRC02:17
*** s3wong has quit IRC02:42
*** salv-orlando has joined #openstack-meeting-402:59
*** carl_baldwin has quit IRC03:07
*** yamahata has quit IRC03:13
*** sarob has quit IRC03:26
*** david-lyle has quit IRC03:35
*** david-lyle has joined #openstack-meeting-403:35
*** david-lyle has quit IRC03:40
*** salv-orlando has quit IRC03:51
*** sarob has joined #openstack-meeting-404:16
*** sarob has quit IRC04:16
*** fnaval has quit IRC04:17
*** david-lyle has joined #openstack-meeting-404:22
*** david-lyle is now known as david-lyle_afk04:23
*** klamath has quit IRC04:45
*** fnaval has joined #openstack-meeting-404:52
*** jckasper has joined #openstack-meeting-405:02
*** jckasper has quit IRC05:02
*** jckasper has joined #openstack-meeting-405:02
*** banix has quit IRC05:09
*** ajmiller has joined #openstack-meeting-405:18
*** jckasper has quit IRC05:23
*** ajmiller has quit IRC05:24
*** belmoreira has joined #openstack-meeting-405:31
*** jckasper has joined #openstack-meeting-405:33
*** yamahata has joined #openstack-meeting-405:33
*** salv-orlando has joined #openstack-meeting-405:36
*** jckasper_ has joined #openstack-meeting-405:42
*** jckasper has quit IRC05:46
*** markvoelker has quit IRC06:03
*** markvoelker has joined #openstack-meeting-406:04
*** markvoelker has quit IRC06:08
*** ivar-laz_ has joined #openstack-meeting-406:33
*** ivar-lazzaro has quit IRC06:37
*** fnaval has quit IRC06:37
*** ivar-laz_ has quit IRC06:38
*** markvoelker has joined #openstack-meeting-406:53
*** markvoelker has quit IRC06:58
*** pkoniszewski has joined #openstack-meeting-407:09
*** sarob has joined #openstack-meeting-407:26
*** salv-orlando has quit IRC07:51
*** markvoelker has joined #openstack-meeting-407:54
*** markvoelker has quit IRC07:59
*** evgenyf has joined #openstack-meeting-408:11
*** mwang2 has joined #openstack-meeting-408:13
*** yamahata has quit IRC08:15
*** yamahata has joined #openstack-meeting-408:16
*** kobis has joined #openstack-meeting-408:16
*** mwang2 has quit IRC08:18
*** wojdev has joined #openstack-meeting-408:35
*** wojdev has quit IRC08:36
*** dvorak has quit IRC08:38
*** dvorak has joined #openstack-meeting-408:39
*** nfedotov has joined #openstack-meeting-408:46
*** salv-orlando has joined #openstack-meeting-408:48
*** evgenyf has quit IRC08:49
*** markvoelker has joined #openstack-meeting-408:55
*** markvoelker has quit IRC09:00
*** salv-orlando has quit IRC09:01
*** matrohon has joined #openstack-meeting-409:01
*** salv-orlando has joined #openstack-meeting-409:01
*** salv-orlando has quit IRC09:10
*** asselin has quit IRC09:10
*** salv-orlando has joined #openstack-meeting-409:10
*** asselin has joined #openstack-meeting-409:11
*** asselin has quit IRC09:14
*** asselin has joined #openstack-meeting-409:14
*** sarob has quit IRC09:22
*** salv-orlando has quit IRC09:32
*** salv-orlando has joined #openstack-meeting-409:32
*** salv-orlando has quit IRC09:35
*** salv-orlando has joined #openstack-meeting-409:36
*** salv-orlando has quit IRC09:45
*** salv-orlando has joined #openstack-meeting-409:46
*** kobis has quit IRC09:49
*** salv-orl_ has joined #openstack-meeting-409:49
*** kobis has joined #openstack-meeting-409:50
*** salv-orl_ has quit IRC09:51
*** salv-orlando has quit IRC09:51
*** salv-orlando has joined #openstack-meeting-409:51
*** salv-orlando has quit IRC09:56
*** markvoelker has joined #openstack-meeting-409:56
*** salv-orlando has joined #openstack-meeting-409:56
*** evgenyf has joined #openstack-meeting-409:58
*** markvoelker has quit IRC10:02
*** numan has joined #openstack-meeting-410:10
*** yamahata has quit IRC10:15
*** numan has quit IRC10:16
*** numan has joined #openstack-meeting-410:28
*** evgenyf has quit IRC10:32
*** kobis has quit IRC11:02
*** kobis has joined #openstack-meeting-411:02
*** kbyrne has quit IRC11:09
*** kbyrne has joined #openstack-meeting-411:13
*** pkoniszewski has quit IRC11:13
*** evgenyf has joined #openstack-meeting-411:24
*** bobmel has quit IRC11:31
*** bobmel has joined #openstack-meeting-411:31
*** rfolco has joined #openstack-meeting-412:08
*** salv-orlando has quit IRC12:20
*** pkoniszewski has joined #openstack-meeting-412:26
*** galstrom_zzz is now known as galstrom13:03
*** fwdit has joined #openstack-meeting-413:07
*** fwdit has quit IRC13:10
*** markvoelker has joined #openstack-meeting-413:11
*** VW_ has joined #openstack-meeting-413:14
*** VW_ has quit IRC13:14
*** VW_ has joined #openstack-meeting-413:14
*** zigo has quit IRC13:18
*** zigo has joined #openstack-meeting-413:20
*** salv-orlando has joined #openstack-meeting-413:25
*** bobmel has quit IRC13:42
*** bobmel has joined #openstack-meeting-413:42
*** klamath has joined #openstack-meeting-413:47
*** krtaylor has quit IRC13:50
*** VW_ has quit IRC13:51
*** krtaylor has joined #openstack-meeting-413:56
*** VW_ has joined #openstack-meeting-413:57
*** jckasper_ has quit IRC14:00
*** galstrom is now known as galstrom_zzz14:05
*** jckasper has joined #openstack-meeting-414:26
*** evgenyf has quit IRC14:27
*** VW_ has quit IRC14:28
*** pkoniszewski has quit IRC14:33
*** VW_ has joined #openstack-meeting-414:41
*** kobis1 has joined #openstack-meeting-414:45
*** kobis has quit IRC14:46
*** krtaylor has quit IRC14:54
*** krtaylor has joined #openstack-meeting-414:55
*** patrickeast has joined #openstack-meeting-414:56
*** lennyb has joined #openstack-meeting-414:58
*** salv-orlando has quit IRC15:00
*** ja_ has joined #openstack-meeting-415:00
krtaylor#startmeeting third-party15:01
openstackMeeting started Wed Feb 18 15:01:00 2015 UTC and is due to finish in 60 minutes.  The chair is krtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: third-party)"15:01
openstackThe meeting name has been set to 'third_party'15:01
krtaylorHi everyone15:01
patrickeasthey15:01
ja_moin moin15:01
mmedvedehi15:01
omrimHello15:01
krtaylortime for another Third Party CI WG meeting15:01
lennybhi15:02
lennybhi15:02
*** salv-orlando has joined #openstack-meeting-415:02
krtaylorlooks like we have a good group today15:02
rfolcoo/15:02
krtaylorhere is the agenda:15:03
krtaylor#link https://wiki.openstack.org/wiki/Meetings/ThirdParty#2.2F18.2F15_1500_UTC15:03
krtaylor#topic Announcements15:03
*** openstack changes topic to "Announcements (Meeting topic: third-party)"15:03
*** evgenyf has joined #openstack-meeting-415:03
*** asselin_ has joined #openstack-meeting-415:04
asselin_hi15:04
krtaylorI'll start off by reminding everyone of gerrit being upgraded March 21st15:04
krtaylorhi asselin15:04
ja_what is the "impact" of the upgrade to users?15:05
asselin_ja_, for those with firewalls blocking the port, it means firewall updates15:05
krtaylorja_, really only if your CI system needs some kind of firewall egress configuration15:05
ja_ok thx15:05
krtaylorasselin beat me to it15:05
krtaylorok, any other quick announcements before we move on?15:06
krtaylor#topic Third-party CI documentation15:07
*** openstack changes topic to "Third-party CI documentation (Meeting topic: third-party)"15:07
krtaylorok, so we still have some work to do here, especially in running-your-own15:07
krtaylorand I am thinking that it is slowed due to the need to walk through it15:08
krtaylorwe have some patches, which reminds me15:09
krtaylorrfolco, can you change your topic to 'third-party-ci-documentation' on your patch15:09
krtaylorthat is for everyone  - so we can track all with one query15:10
krtaylor#link https://review.openstack.org/#/q/topic:third-party-ci-documentation,n,z15:10
rfolcokragniz, summary line ?15:10
rfolcokrtaylor, ^15:10
rfolco(sorry)15:10
krtaylorrfolco, you should have a little writing pad next to Topic in the upper left of your patch review15:11
krtayloryou can edit the topic in gerrit15:11
rfolcotopic is master, is that one ?15:12
krtaylorrfolco, just below Branch15:12
rfolcodone https://review.openstack.org/#/c/155864/15:13
krtaylorthanks15:13
krtaylorlennyb, since you are getting started, any comments on the running-your-own doc would be helpful as well15:13
krtaylorja_, your continued input is appreciated too15:14
krtaylorok, onward15:14
krtaylor#topic Spec for in-tree 3rd party ci15:15
*** openstack changes topic to "Spec for in-tree 3rd party ci (Meeting topic: third-party)"15:15
lennybkrtaylor, thanks I will try to document15:15
krtaylorasselin, you have a new rev on the spec15:15
asselin_so I updated the spec a bit yesterday15:15
krtaylor#link https://review.openstack.org/#/c/139745/15:15
asselin_yes, it is now a 'priority effort' for openstack-infra15:15
krtaylorI haven't had a chance to review it yet, will today15:16
krtayloryea!15:16
asselin_yes, very excited about that! :)15:16
*** numan has quit IRC15:16
*** sigmavirus24_awa is now known as sigmavirus2415:16
krtaylorasselin, it will enable a lot of goodness15:17
rfolcoasselin, is the refactor a override on infra puppet, a fork or what ? could you please clarify ?15:17
asselin_rfolco, the refactor is to allow the puppet scripts to be more easily reused15:18
asselin_rfolco, there are lots of sections in system-config that are needed, but not easily resuable15:19
rfolcoI read the spec and I had the impression it was a fork from infra scripts15:19
asselin_that today's solution15:20
asselin_rfolco, could you comment on the specific sections? I will try to clarify15:20
rfolcoasselin, wil ldo thx15:21
krtayloryes, and just like the puppet module split-out, a great opportunity for third-party WG to get involved and help out15:21
asselin_#link https://review.openstack.org/#/c/137471/15:21
asselin_^^ this is a related spec that will help a lot as well15:21
krtaylorany other questions on in-tree ?15:23
krtayloran action for everyone, please go read the spec15:23
krtaylorthanks for the overview asselin15:24
krtayloroops asselin_15:24
asselin_np :)15:24
krtaylorok, next15:24
krtaylor#topic Repo for third party tools15:24
*** openstack changes topic to "Repo for third party tools (Meeting topic: third-party)"15:24
krtaylorlike last week, I am socializing the idea of creating a repo15:25
krtaylora place for ci teams to share their scripts and other goodies that make their job easier15:25
asselin_+1 I like the idea15:26
krtaylorif the consensus is that it is a good idea, I'll see about getting that setup15:26
patrickeasti like this idea, you thinking a openstack repo or just a public github kind of thing?15:26
krtaylorthere are several tools available, but unless you know about someone's github account, you don't know they exist15:26
krtayloractually, a stackforge repo15:27
patrickeastgotcha15:27
krtaylorwe'd have to discuss the organization of it, etc15:27
* krtaylor wonders if we'd need a spec to propose the idea formally15:28
patrickeastthat might be a good idea, or at least a wiki page or something to capture what we decide for organization15:28
krtaylorwell, I haven't found anyone that hated the idea...yet15:29
asselin_A wiki or etherpad might be good to start.15:29
krtaylorI know we have tools internally that we could share, scripts, dashboards, etc15:29
* krtaylor agrees15:29
krtaylor#action krtaylor to set up wiki for third-party CI WG repo, and/or etherpad15:30
krtaylorok, goodness, thanks everyone for the input15:31
krtaylorlets move on15:31
krtaylor#topic Restart monitoring dashboard effort15:31
*** openstack changes topic to "Restart monitoring dashboard effort (Meeting topic: third-party)"15:32
krtaylorsweston, ping?15:32
krtaylorthere is an effort to have a public monitoring dashboard, basically a new/nicer/more featured radar15:32
krtaylorsome good comments here:15:33
krtaylor#link https://review.openstack.org/#/c/135170/15:33
krtaylorit would replace the need to change status on ThirdPartySystems, at least eventually15:34
krtaylorsweston has been swamped with work from his dayjob, but everything is available, just needs input, reviews, ideas to converge15:35
krtaylorok, we can come back to that if time permits, but I want to get to the next bit15:36
krtaylor#topic Highlighting Third-Party CI Service15:36
*** openstack changes topic to "Highlighting Third-Party CI Service (Meeting topic: third-party)"15:36
krtaylorcontinuing on the success of rfolco 's discussion of PowerKVM CI15:37
krtaylorthis week we have Pure Storage CI15:37
krtaylorpatrickeast, can you share a brief intro on your system15:38
patrickeastyep15:38
krtaylormaybe some problems you had and how you solved them15:38
patrickeastso, first off i made some stuff to share15:38
patrickeasthttp://ec2-54-67-119-204.us-west-1.compute.amazonaws.com/ci_stuff.svg15:38
patrickeasthttps://github.com/patrick-east/os-ext-testing-data15:38
patrickeasta poorly drawn diagram of our setup15:38
patrickeastand what we use for our data repo15:39
krtaylor#link http://ec2-54-67-119-204.us-west-1.compute.amazonaws.com/ci_stuff.svg15:39
krtaylor#link https://github.com/patrick-east/os-ext-testing-data15:39
patrickeastas of a month (almost 2) ago i have switched our system over to using asselin’s https://github.com/rasselin/os-ext-testing scripts15:39
krtaylornice15:40
patrickeastprior to that we had started with the instructions on jay pipes blog post and cobbled together a system without nodepool15:40
patrickeastwe ran into all kinds of issues with re-using static slaves though15:40
asselin_nice pic15:40
krtayloryep, without nodepool due to setup requirements?15:40
patrickeastwe went that way originally just due to lack of knowing any better15:41
krtaylorah, ok15:41
asselin_patrickeast, what's "RDO"15:42
krtaylorRedHat Repo?15:42
patrickeasthttps://openstack.redhat.com/Main_Page15:42
patrickeastits like their open source version of the redhat openstack stuff15:42
patrickeastsimilar to centos vs rhel15:42
patrickeastit made it very very easy to get setup with openstack15:43
patrickeastso, as you may have noticed on the diagram we have the nice high speed data connections that are currently not used… thats on my list of todo’s15:44
patrickeastwe are testing our cinder driver15:44
krtaylorpatrickeast, so I take it you are only testing cinder patches15:44
patrickeastcorrect15:44
patrickeastright now we are only listening for openstack/cinder changes on master15:44
patrickeastand run the volume api tempest tests15:44
*** carl_baldwin has joined #openstack-meeting-415:45
*** carl_baldwin has quit IRC15:45
patrickeastwe are planning to add a FC cinder driver for our array in L-115:45
patrickeastso i’ll be adding support for that into the system early in L15:45
krtaylorwhat was a really tricky part that you had to work through?15:46
*** galstrom_zzz is now known as galstrom15:46
*** carl_baldwin has joined #openstack-meeting-415:46
* asselin_ has fc ci scripts to share in some future repo tbd15:46
patrickeastprobably the hardest part was figuring out how to properly configure everything… all told there are like 50 config files involved between the openstack provider and ci system15:47
patrickeastthis is where that documentation push is really going to shine15:47
asselin_patrickeast, does rdo help out with the openstack provider configs? or are those the ci config to point to the provider?15:48
patrickeastit does get everything setup and working, but we’ve had to go back through and customize things a bit15:48
patrickeastlike where nova stores intances, and glance keeps images15:49
patrickeastdue to partitioning on the system15:49
patrickeastand we had to delete all of its automatic network setup and do our own15:49
krtaylorpatrickeast, we had a similar situation, but as we worked through everything, we found ways to use upstream as-is and have less delta15:49
patrickeastyea my goal is to try and reduce that when we add in the FC testing15:50
patrickeastright now its only a single initiator we test with15:51
patrickeasti’ve got 2 more even bigger ones on the rack next to it waiting to be hooked up with the array15:51
patrickeastfor those ones i’m hoping to improve upon the current setup a bit15:51
krtaylorpatrickeast, have you automated any other parts of the system for your testing?15:52
patrickeastnothing significant, we’ve added in some scripts to cleanup the array once it is done testing15:52
krtaylorcreated any monitoring framework?15:53
patrickeastactually yea, a little one15:53
patrickeasthttps://github.com/patrick-east/os-ext-testing-data/tree/master/tools/server_monitor15:53
patrickeastso15:53
* asselin_ looki ng15:53
patrickeastwe ran into a few times where the system would start failing for X reason15:53
* krtaylor looks too15:53
patrickeasteither disk out of space15:53
patrickeastor the job was unregistered15:53
patrickeastor the array went down15:54
patrickeastso i made a little script that sits on the master and sends email alerts whenever something like that happens15:54
* patrickeast doesn’t know how to use nagios15:54
krtaylorhehheh15:54
krtaylorwe are looking at using nagios also15:54
krtaylorhm, something else to share with the community...15:55
patrickeastmy companies IT and internal ci teams use nagios quite a lot, so i’m hoping to get their help one day to make this integrated with all their dashboards and stuff15:55
asselin_what does -infra use?15:55
patrickeastbut for now its nice to get an email instead of checking in and seeing it failed the last 50 builds15:56
krtaylorasselin_, eyeballs :)15:56
asselin_I configured zuul to send me e-mails on job status. I check the results periodically.15:56
asselin_also a good way to fill up your mailbox15:57
krtaylor+1000, yeah we did that, then turned it off15:57
asselin_but looking for something better. thanks patrickeast :)15:57
krtaylorexcellent, thanks for sharing that15:57
patrickeastoh, also, not sure if anyone else is interested but https://github.com/patrick-east/os-ext-testing-data/blob/master/tools/clean_purity.py is the cleaning script, it parses the cinder logs for any volumes/hosts/whatever from that particular test run and wipes out any left over15:57
patrickeastwe have a relatively small max volume limit on our arrays so it becomes an issue if we aren’t agressive about it15:58
krtaylor#link https://github.com/patrick-east/os-ext-testing-data/tree/master/tools/server_monitor15:58
*** yamahata has joined #openstack-meeting-415:58
krtaylor#link  https://github.com/patrick-east/os-ext-testing-data/blob/master/tools/clean_purity.py15:58
lennybyou can also query Jenskins with json api to see last jobs status15:58
patrickeastyep, we thats all the server_monitor script does, although i dialed it back to just alerting when things hit the fan (health score of 0)15:59
patrickeastsince i was tired of emails for actual failures on bad patches15:59
krtaylorwell, we are close to time15:59
lennybyeah,  we are getting now emails only after N failed jobs16:00
krtaylorthank you patrickeast for sharing this info about your system16:00
patrickeastnp16:00
asselin_big thanks!16:00
patrickeastlet me know if you guys have more questions16:00
krtaylorthanks everyone, great meeting!16:00
mmedvedepatrickeast: thank you, very good16:00
asselin_patrickeast, a few. will ask offline16:00
krtaylor#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Wed Feb 18 16:01:01 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-02-18-15.01.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-02-18-15.01.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-02-18-15.01.log.html16:01
*** rm_work|away is now known as rm_work16:04
*** evgenyf has quit IRC16:10
*** ja_ has quit IRC16:10
*** fnaval has joined #openstack-meeting-416:12
*** carl_baldwin_ has joined #openstack-meeting-416:19
*** carl_baldwin has quit IRC16:19
*** carl_baldwin_ is now known as carl_baldwin16:19
*** fnaval has quit IRC16:20
*** nfedotov has quit IRC16:25
*** asselin__ has joined #openstack-meeting-416:25
*** ajmiller has joined #openstack-meeting-416:27
*** david-lyle_afk is now known as david-lyle16:28
*** asselin_ has quit IRC16:29
*** fnaval has joined #openstack-meeting-416:32
*** sarob has joined #openstack-meeting-416:37
*** banix_ has joined #openstack-meeting-416:46
*** asselin__ has quit IRC16:53
*** sarob has quit IRC16:55
*** sarob has joined #openstack-meeting-416:56
*** kobis1 has quit IRC16:57
*** kobis has joined #openstack-meeting-416:57
*** banix_ is now known as banix17:01
yamahatahello17:02
*** s3wong has joined #openstack-meeting-417:02
yamahata#startmeeting servicevm-device-manager17:04
openstackMeeting started Wed Feb 18 17:04:06 2015 UTC and is due to finish in 60 minutes.  The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot.17:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:04
*** openstack changes topic to " (Meeting topic: servicevm-device-manager)"17:04
openstackThe meeting name has been set to 'servicevm_device_manager'17:04
s3wonghello17:04
*** mwang2 has joined #openstack-meeting-417:04
yamahatas3wong: hello17:04
*** belmoreira has quit IRC17:05
yamahataseems only two.17:05
yamahata#topic Announcement17:05
*** openstack changes topic to "Announcement (Meeting topic: servicevm-device-manager)"17:05
s3wongyamahata: bobmel is online, but he hasn't been attending Tacker meetings for a while17:05
yamahatasummit topic vote has started17:05
*** SridharRamaswamy has joined #openstack-meeting-417:06
yamahata#link https://www.openstack.org/vote-vancouver/17:06
SridharRamaswamyhi17:06
yamahataSridharRamaswamy: hi17:06
yamahataour session link is https://www.openstack.org/vote-vancouver/presentation/tacker-virtual-network-function-life-cycle-management-for-openstack17:06
yamahata#link https://www.openstack.org/vote-vancouver/presentation/tacker-virtual-network-function-life-cycle-management-for-openstack17:06
s3wongSridharRamaswamy: hello17:06
SridharRamaswamys3wong: hi17:07
yamahataany other announcement?17:08
s3wongyamahata: no17:08
yamahata#topic Open Discussion17:08
*** openstack changes topic to "Open Discussion (Meeting topic: servicevm-device-manager)"17:08
yamahata#chair s3wong SridharRamaswamy17:08
openstackCurrent chairs: SridharRamaswamy s3wong yamahata17:08
s3wongyamahata: I would like to ask --- you have a section on oslo proxy, what is the intent of oslo proxy for Tacker?17:09
*** patrickeast has quit IRC17:09
yamahatas3wong: it was proposed for Juno cycle, but was rejected by oslo project.17:10
s3wongyamahata: was the intention health check on VM?17:10
yamahataSo it's suspended.17:10
yamahatathe intention is to introduce side communication channel instead of provide net.17:11
yamahatacommunication between openstack servers and service inside VM.17:11
s3wongyamahata: so this was supposed to run in the context of the VM?17:12
yamahataYes.17:12
s3wongyamahata: interesting, not in hypervisor / host-OS context like all the other agents then17:13
*** SridharRamaswamy has quit IRC17:13
yamahataYea, but it was though of backdoor and big security flaw. So it was rejected.17:14
s3wongyamahata: OK17:14
s3wongyamahata: what communication did you expect Tacker to have with service VM besides health monitoring?17:15
*** dannywilson has joined #openstack-meeting-417:15
*** SridharRamaswamy has joined #openstack-meeting-417:16
SridharRamaswamyfolks - sorry got disconnected :(17:16
yamahatacontrol communication. push/pull configuration/event notification17:16
*** sarob has quit IRC17:17
s3wongyamahata: OK. Since Tacker manages the VMs, we need to identify which set of config to push in case we restart a VM17:18
*** sarob has joined #openstack-meeting-417:18
SridharRamaswamys3wong: yamahata: are we are imagining a "friendly" ServiceVM where you can put tacker-agent in ?17:19
SridharRamaswamyto do these health / config push & pull ?17:19
s3wongSridharRamaswamy: is that even possible? that we ask the service VM to include tacker-agent during launch?17:19
yamahataRight.17:20
yamahataIt's possible with providernet now.17:20
s3wongor can we have Tacker agent in hypervisor / host OS to do these?17:20
SridharRamaswamyNo. Mostly likely not and thats what we need to design for...17:20
s3wongyamahata: how is that accomplished with providernet?17:21
yamahataWe can create providernet which is connected openstack management network.17:22
yamahataThen openstack servers and VMs can communicate freely by assigning the providernet to VMs.17:22
yamahataI heard some cloud providers do so.17:22
s3wongyamahata: Tacker has management interface abstraction --- so previously Tacker just creates such mgmt intf without plugging it into some mgmt network?17:23
yamahatawe need to write driver to connect the intf into mgmt network.17:25
s3wongyamahata: but the mgmt network needs to be created outside of Tacker?17:25
yamahatas3wong: Right.17:26
s3wongyamahata: OK17:27
SridharRamaswamywhat is the relation of this providernet to the actual tenant network ? At the end the traffic from tenant VMs need to be steered to one of these providernet towards the ServiceVM17:27
SridharRamaswamyI'd assume that would be different from the tacker-mgmt-network17:28
s3wongSridharRamaswamy: sounds like yamahata was saying Tacker should leverage provider-net as the mgmt network for all Tacker managed VMs17:29
yamahatas3wong: exactly.17:30
s3wongyamahata: is it possible that Tacker an auto-create such provider-net? to ease up operators' work?17:30
yamahataWith some information from admin, it's quite possible.17:31
s3wongyamahata: OK17:32
s3wongyamahata, SridharRamaswamy: as mentioned in the email, my friend and I will be spending some 20% of time on Tacker, so we will be looking for things to do to shape Tacker into VNF Manager17:33
SridharRamaswamySorry, I missed the part why we are using provide-net ... i've always seen scenarios where ServiceVMs have it own mgmt-network17:33
SridharRamaswamys3wong: +217:34
*** matrohon has quit IRC17:34
yamahatas3wong: +2. I'm surely willing to help17:34
SridharRamaswamysame here17:34
s3wongSridharRamaswamy: yeah... sounds like this new provider-net unifies the VM mgmt network interface17:35
*** dannywilson has quit IRC17:35
s3wongyamahata: that said, so now all VMs would be launched with a vport connecting to the provider-net, in addition to having another vport connecting to Neutron network?17:35
yamahataYes.17:36
s3wongyamahata: interesting, so this is a Nova thing then?17:36
*** ivar-lazzaro has joined #openstack-meeting-417:37
yamahataRight. That's the reason why a driver which talks to nova is needed.17:37
s3wongyamahata: I see17:37
s3wongyamahata: good to know17:37
s3wongwe can certainly try this as the communication channel between Tacker and VMs17:39
*** ivar-laz_ has joined #openstack-meeting-417:39
yamahataany other topics?17:40
s3wongyamahata: that17:40
s3wongthat's it for me17:40
SridharRamaswamyregarding the talk, are we going to demo some of these concepts ?17:41
s3wongSridharRamaswamy: well, we will know if our talk will be voted in in two week :-)17:41
*** ivar-lazzaro has quit IRC17:42
s3wongSridharRamaswamy: so, if it is, then we can meet f2f to see if and what we want to demo17:42
yamahatawe will see. I'll afraid after it's accepted...17:42
yamahatas3wong: +117:42
s3wongSridharRamaswamy, yamahata: until then, we march along to build Tacker without worrying too much about the talk first :-)17:42
yamahataokay, thank you everybody.17:44
s3wongThanks!17:44
yamahatalet's vote for summit talk.17:44
yamahata#endmeeting17:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:44
openstackMeeting ended Wed Feb 18 17:44:43 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2015/servicevm_device_manager.2015-02-18-17.04.html17:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2015/servicevm_device_manager.2015-02-18-17.04.txt17:44
openstackLog:            http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2015/servicevm_device_manager.2015-02-18-17.04.log.html17:44
s3wongwell, voting is only an "input" to the talk decision :-)17:44
*** s3wong has quit IRC17:47
SridharRamaswamys3wong: yamahata: bye, already voted :)17:47
*** simon-AS5591 has joined #openstack-meeting-417:50
*** Rockyg has joined #openstack-meeting-417:54
*** kobis has quit IRC17:57
*** SumitNaiksatam has joined #openstack-meeting-418:00
*** pkoniszewski has joined #openstack-meeting-418:06
*** sarob has quit IRC18:07
*** bobmel has quit IRC18:10
*** ivar-laz_ has quit IRC18:10
*** bobmel has joined #openstack-meeting-418:10
*** ivar-lazzaro has joined #openstack-meeting-418:10
*** yamahata has quit IRC18:12
*** vishwanathj has joined #openstack-meeting-418:15
*** krtaylor has quit IRC18:16
*** dboik_ has joined #openstack-meeting-418:18
*** dboik_ has left #openstack-meeting-418:18
*** Salman_ has joined #openstack-meeting-418:19
*** dannywilson has joined #openstack-meeting-418:27
*** simon-AS5591 has quit IRC18:41
*** SridharRamaswamy has quit IRC18:43
*** s3wong has joined #openstack-meeting-418:43
*** krtaylor has joined #openstack-meeting-418:53
*** simon-AS559 has joined #openstack-meeting-419:01
*** simon-AS559 has quit IRC19:06
*** VW_ has quit IRC19:08
*** SridharRamaswamy has joined #openstack-meeting-419:09
*** carl_baldwin has quit IRC19:11
*** dannywilson has quit IRC19:12
*** SridharRamaswam1 has joined #openstack-meeting-419:31
*** ivar-lazzaro has quit IRC19:32
*** SridharRamaswamy has quit IRC19:32
*** ivar-lazzaro has joined #openstack-meeting-419:33
*** Rockyg has quit IRC19:35
*** sarob has joined #openstack-meeting-419:41
*** sarob has quit IRC19:46
*** Aish has joined #openstack-meeting-419:53
*** ivar-laz_ has joined #openstack-meeting-419:55
*** sarob has joined #openstack-meeting-419:56
*** ivar-lazzaro has quit IRC19:58
*** ivar-laz_ has quit IRC20:04
*** ivar-lazzaro has joined #openstack-meeting-420:05
*** vishwanathj has quit IRC20:06
*** sarob has quit IRC20:25
*** sarob has joined #openstack-meeting-420:25
*** Salman_ has quit IRC20:26
*** dannywilson has joined #openstack-meeting-420:27
*** sarob has quit IRC20:29
*** yamahata has joined #openstack-meeting-420:40
*** qwebirc13590 has joined #openstack-meeting-420:55
*** rfolco has quit IRC20:59
*** VW_ has joined #openstack-meeting-421:00
*** banix has quit IRC21:03
*** matrohon has joined #openstack-meeting-421:08
*** GavinPratt has joined #openstack-meeting-421:10
*** VW_ has quit IRC21:12
*** VW_ has joined #openstack-meeting-421:13
*** SumitNaiksatam has quit IRC21:21
*** SumitNaiksatam has joined #openstack-meeting-421:22
*** carl_baldwin has joined #openstack-meeting-421:31
*** banix has joined #openstack-meeting-421:32
*** pmesserli has joined #openstack-meeting-422:13
*** jckasper has quit IRC22:31
*** pkoniszewski has quit IRC22:32
*** banix has quit IRC22:44
*** qwebirc13590 has quit IRC22:46
*** matrohon has quit IRC22:47
*** asselin_ has joined #openstack-meeting-422:50
*** yamahata_ has quit IRC22:51
*** isq has joined #openstack-meeting-422:51
*** asselin_ has quit IRC22:55
*** matrohon has joined #openstack-meeting-423:01
*** VW__ has joined #openstack-meeting-423:02
*** carl_baldwin has quit IRC23:05
*** VW_ has quit IRC23:05
*** dttocs has joined #openstack-meeting-423:07
*** matrohon has quit IRC23:09
*** qwebirc86514 has joined #openstack-meeting-423:10
*** rolandchan has joined #openstack-meeting-423:10
*** sarob has joined #openstack-meeting-423:17
*** SumitNaiksatam has quit IRC23:20
*** matrohon has joined #openstack-meeting-423:23
*** GavinPratt_ has joined #openstack-meeting-423:27
*** bobmel has quit IRC23:31
*** bobmel has joined #openstack-meeting-423:31
*** Aish has left #openstack-meeting-423:34
*** pmesserli has quit IRC23:38
*** pmesserli has joined #openstack-meeting-423:39
*** krtaylor has quit IRC23:40
*** VW__ has quit IRC23:42
*** pmesserli has quit IRC23:43
*** shamail has joined #openstack-meeting-423:46
shamailSorry all, I am on vacation this week and forgot about this meeting. :(  Is the Product meeting wrapped up?23:47
*** rolandchan has left #openstack-meeting-423:48
s3wongshamail: looks like it is happening at #openstack-meeting now23:50
*** matrohon has quit IRC23:53
*** ivar-laz_ has joined #openstack-meeting-423:58
*** ivar-laz_ has quit IRC23:58
*** galstrom is now known as galstrom_zzz23:58
*** ivar-laz_ has joined #openstack-meeting-423:58
*** ivar-lazzaro has quit IRC23:59

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