Thursday, 2017-03-02

*** liangy has quit IRC00:01
*** krtaylor has quit IRC00:08
*** rfolco has joined #openstack-meeting-400:13
*** rfolco has quit IRC00:20
*** Julien-zte has joined #openstack-meeting-400:25
*** BjoernT has quit IRC00:25
*** limao has joined #openstack-meeting-400:27
*** thorst has joined #openstack-meeting-400:31
*** vishnoianil has joined #openstack-meeting-400:32
*** revon has quit IRC00:33
*** rfolco has joined #openstack-meeting-400:35
*** rfolco has quit IRC00:35
*** hongbin has quit IRC00:35
*** thorst has quit IRC00:36
*** sdake has quit IRC00:36
*** tovin07 has joined #openstack-meeting-400:38
*** dtardivel has quit IRC00:40
*** thorst has joined #openstack-meeting-400:41
*** sdake has joined #openstack-meeting-400:42
*** gongysh has joined #openstack-meeting-400:45
*** gongysh has quit IRC00:49
*** krtaylor has joined #openstack-meeting-400:53
*** Syed__ has quit IRC00:55
*** Julien-zte has quit IRC00:58
*** Julien-zte has joined #openstack-meeting-400:59
*** thorst has quit IRC01:01
*** cjloader has joined #openstack-meeting-401:04
*** armax has joined #openstack-meeting-401:06
*** Swami has quit IRC01:06
*** cloudtrainme has joined #openstack-meeting-401:10
*** cjloader has quit IRC01:14
*** uck_ has quit IRC01:17
*** uck has joined #openstack-meeting-401:20
*** zhubingbing_ has joined #openstack-meeting-401:22
*** uck has quit IRC01:25
*** Julien-zte has quit IRC01:43
*** xiaohhui has joined #openstack-meeting-401:43
*** cjloader has joined #openstack-meeting-401:44
*** cjloader has quit IRC01:45
*** Julien-zte has joined #openstack-meeting-401:45
*** tonytan4ever has joined #openstack-meeting-401:47
*** cgoncalves has quit IRC01:57
*** chigang has joined #openstack-meeting-401:58
*** cjloader has joined #openstack-meeting-402:00
*** tonytan4ever has quit IRC02:03
*** cgoncalves has joined #openstack-meeting-402:04
*** cjloader has quit IRC02:08
*** sdake_ has joined #openstack-meeting-402:10
*** sdake has quit IRC02:13
*** unicell has quit IRC02:20
*** cjloader has joined #openstack-meeting-402:22
*** cjloader has quit IRC02:23
*** cjloader has joined #openstack-meeting-402:24
*** sdake_ is now known as sdake02:28
*** woodard has joined #openstack-meeting-402:28
*** cjloader has quit IRC02:29
*** woodard has quit IRC02:32
*** rbak has joined #openstack-meeting-402:40
*** britthouser4 has quit IRC02:49
*** britthouser5 has joined #openstack-meeting-402:50
*** britthouser has joined #openstack-meeting-402:50
*** britthouser has quit IRC02:50
*** britthouser5 has quit IRC02:51
*** britthouser has joined #openstack-meeting-402:51
*** cloudtrainme has quit IRC02:53
*** Sukhdev has joined #openstack-meeting-402:54
*** emagana has joined #openstack-meeting-402:55
*** Sukhdev has quit IRC02:56
*** emagana has quit IRC02:59
*** rbak has quit IRC02:59
*** gongysh has joined #openstack-meeting-403:04
*** dave-mccowan has joined #openstack-meeting-403:07
*** hongbin has joined #openstack-meeting-403:08
*** links has joined #openstack-meeting-403:08
*** vishnoianil has quit IRC03:15
*** gongysh has quit IRC03:16
*** sp_ has joined #openstack-meeting-403:22
*** unicell has joined #openstack-meeting-403:38
*** unicell has quit IRC03:38
*** reedip has quit IRC03:41
*** yamahata has quit IRC03:45
*** iyamahat has quit IRC03:45
*** Julien-zte has quit IRC03:48
*** thorst has joined #openstack-meeting-403:50
*** thorst has quit IRC03:50
*** Julien-zte has joined #openstack-meeting-403:50
*** sneti_ has joined #openstack-meeting-404:13
*** dave-mccowan has quit IRC04:16
*** psachin has joined #openstack-meeting-404:27
*** thorst has joined #openstack-meeting-404:32
*** thorst has quit IRC04:32
*** Jeffrey4l has joined #openstack-meeting-404:32
*** adisky_ has joined #openstack-meeting-404:38
*** sneti_ has quit IRC04:43
*** thorst has joined #openstack-meeting-405:03
*** sdake has quit IRC05:08
*** thorst has quit IRC05:16
*** hongbin has quit IRC05:17
*** janki has joined #openstack-meeting-405:27
*** Kevin_Zheng has quit IRC05:33
*** unicell has joined #openstack-meeting-405:44
*** vishnoianil has joined #openstack-meeting-405:51
*** Sukhdev has joined #openstack-meeting-405:51
*** Sukhdev has quit IRC06:05
*** trinaths has joined #openstack-meeting-406:06
*** chigang has quit IRC06:09
*** armax has quit IRC06:14
*** psachin_ has joined #openstack-meeting-406:18
*** psachin_ has quit IRC06:19
*** joedborg_ has joined #openstack-meeting-406:36
*** joedborg has quit IRC06:36
*** salv-orlando has joined #openstack-meeting-406:45
*** zhurong has joined #openstack-meeting-406:46
*** nkrinner_afk is now known as nkrinner06:48
*** unicell has quit IRC06:51
*** unicell has joined #openstack-meeting-406:51
*** salv-orl_ has joined #openstack-meeting-406:52
*** zhurong has quit IRC06:53
*** salv-orlando has quit IRC06:55
*** yamahata has joined #openstack-meeting-407:07
*** trinaths has quit IRC07:17
*** bhagyashris has quit IRC07:19
*** hwoarang has quit IRC07:28
*** hwoarang has joined #openstack-meeting-407:29
*** yamamoto has quit IRC07:38
*** gongysh has joined #openstack-meeting-407:41
*** limao has quit IRC07:43
*** limao has joined #openstack-meeting-407:45
*** unicell has quit IRC07:53
*** pkoniszewski has joined #openstack-meeting-407:53
*** alexchadin has joined #openstack-meeting-408:01
*** matrohon has joined #openstack-meeting-408:04
*** pcaruana has joined #openstack-meeting-408:13
*** chigang has joined #openstack-meeting-408:14
*** zhubingbing_ has left #openstack-meeting-408:16
*** ltomasbo|away is now known as ltomasbo08:16
*** Kevin_Zheng has joined #openstack-meeting-408:17
*** yamamoto has joined #openstack-meeting-408:17
*** yamamoto_ has joined #openstack-meeting-408:17
*** yamamoto_ has quit IRC08:20
*** yamamoto has quit IRC08:21
*** yfauser has joined #openstack-meeting-408:24
*** gibi_ is now known as gibi08:25
*** dtardivel has joined #openstack-meeting-408:31
*** matrohon has quit IRC08:34
*** DFFlanders has joined #openstack-meeting-408:41
*** trinaths has joined #openstack-meeting-408:41
*** ralonsoh has joined #openstack-meeting-408:46
*** sdake has joined #openstack-meeting-408:51
*** sdake_ has joined #openstack-meeting-408:52
*** sdake has quit IRC08:55
*** thorst has joined #openstack-meeting-409:13
*** yfauser has quit IRC09:13
*** yfauser has joined #openstack-meeting-409:14
*** yamamoto has joined #openstack-meeting-409:17
*** thorst has quit IRC09:18
*** yfauser has quit IRC09:19
*** yamamoto has quit IRC09:22
*** berendt has left #openstack-meeting-409:24
*** Jeffrey4l has quit IRC09:25
*** Jeffrey4l has joined #openstack-meeting-409:25
*** Julien-zte has quit IRC09:30
*** Jeffrey4l has quit IRC09:31
*** aarefiev_afk is now known as aarefiev09:39
*** premsankar has quit IRC09:40
*** sdake_ is now known as sdake09:41
*** Jeffrey4l has joined #openstack-meeting-409:43
*** sp_ has quit IRC09:44
*** alexchadin has quit IRC09:45
*** trinaths has quit IRC09:54
*** sp_ has joined #openstack-meeting-409:56
*** alexchadin has joined #openstack-meeting-409:57
*** yfauser has joined #openstack-meeting-410:00
*** alexchadin has quit IRC10:00
*** yfauser has quit IRC10:05
*** ralonsoh_ has joined #openstack-meeting-410:05
*** ralonsoh has quit IRC10:05
*** ralonsoh_ is now known as ralonsoh10:06
*** pbourke has quit IRC10:09
*** pbourke has joined #openstack-meeting-410:10
*** limao has quit IRC10:11
*** tovin07 has quit IRC10:12
*** sdake has quit IRC10:18
*** yamamoto has joined #openstack-meeting-410:19
*** yamamoto has quit IRC10:22
*** sdake has joined #openstack-meeting-410:22
*** gongysh has quit IRC10:27
*** links has quit IRC10:31
*** sdake has quit IRC10:41
*** yfauser has joined #openstack-meeting-410:47
*** links has joined #openstack-meeting-410:47
*** DFFlanders has quit IRC10:51
*** yamamoto has joined #openstack-meeting-410:53
*** yamamoto has quit IRC10:53
*** tovin07 has joined #openstack-meeting-410:54
*** sambetts|afk is now known as sambetts10:59
*** yamamoto has joined #openstack-meeting-411:04
*** sdake has joined #openstack-meeting-411:12
*** thorst has joined #openstack-meeting-411:14
*** joedborg_ has quit IRC11:15
*** joedborg has joined #openstack-meeting-411:16
*** thorst has quit IRC11:19
*** sp_ has quit IRC11:24
*** yifei has quit IRC11:43
*** yifei has joined #openstack-meeting-411:44
*** sdague has joined #openstack-meeting-411:46
*** sdake has quit IRC11:49
*** sdake has joined #openstack-meeting-411:49
*** links has quit IRC11:51
*** sdake_ has joined #openstack-meeting-411:55
*** sdake has quit IRC11:56
*** yamamoto has quit IRC11:58
*** chigang has quit IRC11:59
*** Kevin_Zheng_Home has joined #openstack-meeting-412:01
*** links has joined #openstack-meeting-412:04
*** ralonsoh_ has joined #openstack-meeting-412:06
*** yifei has quit IRC12:07
*** Kevin_Zheng_Home has quit IRC12:08
*** yamahata has quit IRC12:08
*** sdake_ is now known as sdake12:09
*** ralonsoh has quit IRC12:09
*** yifei has joined #openstack-meeting-412:10
*** sdake_ has joined #openstack-meeting-412:29
*** sdake has quit IRC12:30
*** yifei has quit IRC12:34
*** cloudtrainme has joined #openstack-meeting-412:34
*** tovin07 has quit IRC12:34
*** wznoinsk has quit IRC12:39
*** rwallner has joined #openstack-meeting-412:41
*** cloudtrainme has quit IRC12:45
*** thorst has joined #openstack-meeting-412:45
*** limao has joined #openstack-meeting-412:51
*** salv-orlando has joined #openstack-meeting-412:52
*** salv-orl_ has quit IRC12:55
*** rfolco has joined #openstack-meeting-412:57
*** yamamoto has joined #openstack-meeting-412:59
*** sdake has joined #openstack-meeting-412:59
*** sdake_ has quit IRC13:01
*** matrohon has joined #openstack-meeting-413:02
*** yamamoto has quit IRC13:09
*** yifei has joined #openstack-meeting-413:09
*** janki has quit IRC13:15
*** sdake_ has joined #openstack-meeting-413:16
*** sdake has quit IRC13:19
*** janki has joined #openstack-meeting-413:23
*** rwallner has quit IRC13:30
*** klamath has joined #openstack-meeting-413:31
*** klamath has quit IRC13:32
*** klamath has joined #openstack-meeting-413:32
*** srwilkers has joined #openstack-meeting-413:41
*** ralonsoh_ has quit IRC13:44
*** abhishek_k has joined #openstack-meeting-413:48
*** sp_ has joined #openstack-meeting-413:49
*** cloudtrainme has joined #openstack-meeting-413:49
*** Jeffrey4l has quit IRC13:49
*** alexchadin has joined #openstack-meeting-413:50
*** stevelle has joined #openstack-meeting-413:50
*** alexchadin has quit IRC13:51
*** alexchadin has joined #openstack-meeting-413:52
*** rwallner has joined #openstack-meeting-413:52
*** liangy has joined #openstack-meeting-413:53
*** liuyulong has joined #openstack-meeting-413:54
*** alexchadin has quit IRC13:56
*** croelandt has joined #openstack-meeting-413:57
rosmaitaCourtesy meeting reminder on #openstack-meeting-4: ativelkov, cpallares, flaper87, flwang1, hemanthm, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, ajayaa, GB21, bpoulos, harshs, abhishek, bunting, dshakhray, wxy, dhellmann, kairat, aavraham, alex_bash13:58
*** alex_bash has joined #openstack-meeting-413:58
*** cloudtrainme has quit IRC13:59
jokke_o/14:00
rosmaita#startmeeting glance14:00
openstackMeeting started Thu Mar  2 14:00:21 2017 UTC and is due to finish in 60 minutes.  The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
dharinic\o14:00
rosmaita#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: glance)"14:00
sigmaviruso/14:00
rosmaitahello jokke_ , dharinic : you are too quick!14:00
alex_bash\o14:00
*** yfauser has quit IRC14:01
rosmaitasigmavirus: what was that command we were using for sub-topics? we haven't met for a week and i completely forgot14:01
*** salv-orlando has quit IRC14:01
sigmavirusThere is no command for subtopics =)14:02
*** yfauser has joined #openstack-meeting-414:02
sigmavirusI just tend to do #topic Top-Level :: Sub-Level14:02
asettleo/14:02
rosmaitasigmavirus: we were using something to fake it, i thought14:02
sigmavirusKind of like C++ because who doesn't like C++?14:02
sigmavirus=P14:02
sigmavirusrosmaita: honestly, I've forgotten =/14:02
rosmaitac++ ftw14:02
rosmaitaok14:02
asettleRST! \o/ :p14:02
rosmaitaasettle: thanks for attending!14:02
sigmavirusasettle: ACK14:03
asettleI'm just such an attender14:03
rosmaita#topic updates14:03
*** openstack changes topic to "updates (Meeting topic: glance)"14:03
rosmaita#topic updates :: new spotlight links14:03
*** openstack changes topic to "updates :: new spotlight links (Meeting topic: glance)"14:03
sigmavirusasettle: YOU COULD HAVE BEEN A CONTENDER!14:03
rosmaitaok, just want to point out the updated links on the etherpad14:03
rosmaitagot the openstack pike release schedule14:04
rosmaitaand the preliminary glance pike priorities and milestones:14:04
hemanthmo/14:04
rosmaita#link https://etherpad.openstack.org/p/glance-pike-ptg-roadmap-prelim14:04
rosmaitaalso, the PTG glance schedule etherpad has links to all the etherpads we used at the PTG14:04
rosmaita#link https://etherpad.openstack.org/p/glance-pike-ptg-schedule14:05
*** pmesserli has joined #openstack-meeting-414:05
rosmaitaplease check out the proposed dates and provide any comments, etc.14:05
rosmaitakey thing are the spec proposal freeze and spec freeze for pike14:06
rosmaita#link https://review.openstack.org/#/c/440561/14:06
*** ralonsoh has joined #openstack-meeting-414:06
*** yfauser has quit IRC14:06
nikhilo/14:06
rosmaitathat patch also has the proposed weeks for the virtual midcycle and operators midcycle14:07
rosmaitanikhil has volunteered to organized the operators virtual midcycle for glance14:07
*** breton has quit IRC14:07
rosmaita:)14:07
asettleLucky nikhil14:07
*** ruriryan has quit IRC14:07
rosmaita#topic updates :: ocata postmortem14:07
*** openstack changes topic to "updates :: ocata postmortem (Meeting topic: glance)"14:07
nikhilLol14:08
stevelleits dead, jim14:08
rosmaitawe took a few minutes at the PTG to do a quick postmortem of the ocata cycle14:08
jrollstevelle: don't drag me into this :D14:08
rosmaitai'd like to open it up to people who couldn't attend14:08
rosmaitajroll: i never think of you as "jim", just as "jroll"14:08
jcook:D14:09
rosmaita#link https://etherpad.openstack.org/p/glance-pike-ptg-ocata-postmortem14:09
jroll:P14:09
rosmaitaanyway, there's the link ... please add any comments suggestions etc you may have14:09
asettlerosmaita: that's because his name isn't 'jim' obvs. It's jroll on the birth certificate14:09
asettleJust the same way sigmavirus is *not* Ian14:09
jcookwould have like to have gotten further on Rolling Upgrades, but I'm glad we landed what we did14:09
rosmaitajcook: good point, please add to etherpad14:10
sigmavirusasettle: who's this "Ian"?14:10
rosmaitaDury?14:11
rosmaitabut we digress14:11
rosmaitaanyway, your feedback is welcome, particularly if you have suggestions that would make pike smoother14:11
rosmaitai think stevelle already suggested "don't make any backward incompatible api changes"14:12
*** links has quit IRC14:12
rosmaita#topic updates :: image import virtual meetup14:12
*** openstack changes topic to "updates :: image import virtual meetup (Meeting topic: glance)"14:12
rosmaitai'll send out a doodle poll later today to get a time, but I'm thinking of wednesday14:13
rosmaitapoint of the meetup is to go over the spec update which i will hopefully have posted on monday14:13
stevelle:D14:13
*** janki has quit IRC14:13
rosmaitaand to parcel out work items and discuss open questions14:13
rosmaitaas far as communication medium ... jokke_ you still have bluejeans access?14:14
nikhilDoodle please14:14
jokke_yup14:14
rosmaitabluejeans seems to have worked out the best, any objections (in the form of a suggestion of something better)?14:15
stevelleno idea, never used it14:15
stevellecant be worse than carrier pigeon14:16
rosmaitawell, it14:16
rosmaitas better than webex14:16
sigmaviruslol14:16
sigmavirusbluejeans does work well but we need someone like jokke_ or flaper87 to host it14:16
sigmavirus(typically flaper87 has hosted it)14:16
rosmaitajokke_ handled it last time, i think14:17
rosmaitaok, sounds like bluejeans or carrier pigeon14:17
*** aavraham has joined #openstack-meeting-414:17
rosmaitajokke_: i'll send a doodle poll about time to the ML, can you set up bluejeans access once we have a datetime?14:18
sigmavirus+1 to carrier pigeon14:18
* jcook uses bluejeans for grad school office hours and it works well.14:19
jokke_rosmaita: sure14:19
rosmaitaok, thanks14:19
sigmavirushttp://conferencecall.biz/ might work too14:19
rosmaitapeople who prefer carrier pigeon have to fed ex their pigeons to blacksburg, virginia, before wednesday14:19
sigmavirusasettle: might prefer we communicate via owls14:20
jcookfrom what I can tell bluejeans is a lot like hangouts and you really just need a link14:20
asettleI'm more of a pigeon lady, myself14:20
asettleOwls seems nice14:20
* asettle comes in with the important comments14:20
jcooklol14:20
sigmavirusasettle: what house are you in?14:20
rosmaitai think some owls at least will attack pigeons14:20
rosmaitaso we can't mix communication media here14:21
jcookinb4 ravenclaw14:21
rosmaitaor there will be bad results14:21
asettlesigmavirus: you're clearly referring to HP and it is very obvious that I am a Hufflepuff.14:21
sigmavirus=D14:21
jcook:D14:21
asettleSo, perhaps we communicate using Badger?14:21
* asettle is a thinker14:22
rosmaita#action everyone look for doodle poll in the ML today and respond quickly14:22
rosmaita#topic looking for owners14:22
*** openstack changes topic to "looking for owners (Meeting topic: glance)"14:22
* sigmavirus would propose that everyone learn their house today and include it in the doodle14:22
asettleWow that's a vague topic.14:22
sigmavirusrosmaita: I think asettle just owned you14:22
rosmaitawe've got some pike items that need people to shepherd them14:22
rosmaitaor whatever you do with pigeons14:22
* rosmaita is ignoring the peanut gallery14:22
asettlerosmaita: probably smart :P14:23
stevelleI own a hungry cat14:23
*** trozet has quit IRC14:23
rosmaita#topic owner needed :: remove 'show_multiple_locations'14:23
*** openstack changes topic to "owner needed :: remove 'show_multiple_locations' (Meeting topic: glance)"14:23
rosmaitathis one is going to require a spec14:23
* nikhil feels like watching the Tarzan movie now14:23
rosmaitaremoval will be slightly complicated, and there will be argument over the proper default value for the policies14:24
*** baoli has joined #openstack-meeting-414:24
rosmaita(I favor "!", others favor "role:admin")14:24
*** cleong has joined #openstack-meeting-414:24
rosmaitato get an idea of what's up, here are some things to look at:14:24
sigmavirusrosmaita: if I could just rm show_multiple_locations I would14:24
*** Kevin_Zheng_ has joined #openstack-meeting-414:25
*** cjloader has joined #openstack-meeting-414:25
rosmaita#link http://git.openstack.org/cgit/openstack/glance/tree/releasenotes/notes/deprecate-show-multiple-location-9890a1e961def2f6.yaml14:25
nikhilI will take that item14:25
rosmaita#link http://git.openstack.org/cgit/openstack/glance/tree/releasenotes/notes/update-show_multiple_locations-helptext-7fa692642b6b6d52.yaml14:25
rosmaitasold!14:25
rosmaitathat was easy14:25
rosmaitaok, next item14:25
rosmaita#topic owner needed :: removing deprecated options14:26
*** openstack changes topic to "owner needed :: removing deprecated options (Meeting topic: glance)"14:26
rosmaitathere are several deprecated options who've passed their "remove by" date14:26
rosmaitait would be nice if someone could gather them on an etherpad14:26
alex_bashthese topics are sweet music to my ears14:26
nikhilAnd I've wip review that someone can pick up if they want14:26
rosmaitai think most of them are simpler than the show_mult_locations and can be handled by bugs14:27
rosmaitabut it would be good to see what they all are first so we can check them off14:27
hemanthmI can help14:27
rosmaitasold!14:27
rosmaitai forgot to "action" nikhil14:28
nikhilIt's fine14:28
rosmaita#action nikhil to handle show_multiple_locations option removal14:28
hemanthmno one can action nikhil14:28
nikhilIt is to important for me to forget14:28
nikhilLol14:28
rosmaita#action hemanthm to put together list of deprecated options for removal14:28
rosmaitaok, next one14:28
alex_bashChuck Norris could action nikhil14:28
rosmaita#topic owner needed :: remove usage of deprecated options14:29
*** openstack changes topic to "owner needed :: remove usage of deprecated options (Meeting topic: glance)"14:29
*** Jeffrey4l has joined #openstack-meeting-414:29
hemanthmso, rosmaita is Chunk Norris14:29
nikhil:P14:29
* asettle comes back to the convo14:29
asettleWell that escalated quickly14:29
rosmaitain the macho sense, yes; in the political sense, no14:29
stevellebut is Chuck Norris deprecated?14:29
rosmaitashould be14:29
jokke_stevelle: you can try :P14:30
stevelle+114:30
asettlesigmavirus or stevelle plz print plaque for next summit that says " rosmaita is chuck norris in the macho sense, not hte political sense"14:30
rosmaitai think i need to run this meeting more like chuck norris14:30
sigmavirusasettle: as if You Know Who would send me to the summit14:30
asettlesigmavirus: *gasp* Voldy is back working for Backspace?14:30
asettleI could sense it.14:31
sigmavirus=D14:31
sigmavirusasettle: did your forehead tingle?14:31
asettlesigmavirus: it was actually my upper arm, I have that different from HP14:31
stevellewas there more work to pass out?14:31
sigmavirusoh totes14:31
*** tonytan4ever has joined #openstack-meeting-414:31
asettlestevelle: yes, plaque plz14:31
rosmaitaso we need a new defense against the dark arts instructor14:32
asettle*raises hand*14:32
asettleOh oh oh oh oh14:32
sigmaviruslmao14:32
stevellelast one was eaten by a grue14:32
rosmaitato take on the task of seeing what stuff we're consuming the deprecated options of14:32
asettleI vote nikhil14:32
rosmaitaand stop consuming them14:32
*** breton has joined #openstack-meeting-414:32
* rosmaita pauses to wait for volunteers14:33
sigmavirusI think asettle voluntold nikhil, didn't she?14:33
asettleSure did.14:33
nikhilI vote Mike14:33
asettleOhhhh I see what you did there nikhil14:33
stevellesorry thought that cleaning up was same task as collecting the things to clean up14:33
*** aavraham has left #openstack-meeting-414:33
hemanthmstevelle ++14:33
hemanthmso, I'll do it as a part of my previous todo14:34
nikhilWell you just need to go visit different projects using them14:34
nikhilFor cleanup I mean14:34
asettlehemanthm is the new Defense Against the Dark Arts teacher! \o/14:34
*** Jeffrey4l has quit IRC14:35
rosmaitalet's hope he lasts longer than the last one14:35
* hemanthm should know better14:35
rosmaitaok, that's all i got14:35
rosmaita#topic Automating the current release name in glance code for making maitenance a long term viable reality14:35
*** openstack changes topic to "Automating the current release name in glance code for making maitenance a long term viable reality (Meeting topic: glance)"14:35
rosmaitathis is nikhil14:35
* hemanthm hides14:35
nikhilWell pretty much what the review says14:36
nikhilI just need ideas to see how we can do such things14:36
* nikhil waits for ideas14:37
rosmaitaone suggestion is a checklist of stuff that must be done when a stable branch is cut14:37
rosmaitawhich reminds me14:37
stevelleI feel like having it in setup.cfg would be good enough14:37
hemanthm+114:37
rosmaitai think sigmavirus was working on a release checklist or something like that14:38
sigmavirusIsI am14:38
nikhilI was thinking of the same thing stevelle14:38
sigmavirus*I am14:38
hemanthmeither way, we'd still have to maintain it manually14:38
nikhilstevelle: but you probably know better if that confuses downstream14:38
rosmaitahemanthm is correct, i think14:39
rosmaitabut i guess the advantage is that it's in a more obvious place?14:39
nikhilhemanthm: I think we can request it part of release automation14:39
hemanthmnikhil: yeah, kinda where I was headed as well14:40
nikhilTypically when release is cut we get that flag and set it14:40
nikhilBut today only signs are in git commit messages14:41
rosmaitaso the problem i see is that master doesn't get a name until a stable branch has been cut14:42
rosmaitaand master is where we need the correct name14:42
nikhilYup14:42
hemanthmI don't know enough about release automation, are there any post-release automation that is done currently?14:43
dharinicneutron maintains a release checklisr for few things that needs to be done manually when a stable branch is to be cut.14:43
rosmaitadharinic: ++ , i think we need that even independently of how we fix this14:44
rosmaitasigmavirus: do you have any ideas?14:45
nikhilWell I think that is opposite of where we want to go14:45
rosmaitawe could always mention dhellmann and see what happens14:45
sigmavirushemanthm: nikhil so there is automation around updating upper-constraints, .gitreview, and a few other things14:45
sigmavirusrosmaita: ttx is the release PTL now :)14:45
sigmavirusI think having extra steps that we carry out manually works well too14:46
rosmaitabut those are into the stable branch14:46
nikhilWe were trying to get rid of configs in tree so that release is not blocked on such manual updates14:46
rosmaitawe need this to happen in master14:46
sigmavirusah I see14:46
alex_bashmaybe we can add a gate job for this14:46
nikhilIt would be a horrendous experience for waiting on a zillion patches to cut release14:46
sigmavirusnikhil: currently we don't wait on those patches14:47
sigmavirusI'm not sure what you're expecting to be the problem14:47
sigmavirusalex_bash: the gate job would run every time we merge to a branch. How would that help?14:47
alex_bashfirst patch to merge to master on new release will have to manually update it14:47
nikhilsigmavirus: we need to refresh configs in tree before cutting a branch14:47
sigmavirusSo what is the core of the problem? Our config files have the wrong name?14:47
alex_bashall subsequent patches would pass14:48
hemanthmhttps://github.com/openstack/glance/blob/master/glance/db/migration.py#L5014:48
hemanthmsigmavirus: ^14:48
sigmavirusnikhil: so that's 1 patch to wait on before creating a release?14:48
rosmaitai dont't think any file currently has the name we need14:48
*** alexchadin has joined #openstack-meeting-414:48
nikhilsigmavirus: ha, I don't think so14:48
sigmavirusso what hemanthm linked can be pulled out of a setup.cfg if we watned it to be14:48
hemanthmyeah and I don't know why cutting a branch should get delayed14:49
sigmavirushemanthm: right, we'd update setup.cfg after a branch has been released14:49
nikhilit should not be14:49
nikhilbut it can be14:49
sigmaviruscurrent_release would be set at the start of the cycle and then we'd be done until the next14:49
rosmaitayeah, the new stable branch will already have the corect name14:49
hemanthmwhen cutting the branch that label should have already been updated14:49
*** limao_ has joined #openstack-meeting-414:49
sigmavirusI think we're conflating a lot of things14:49
*** limao has quit IRC14:50
rosmaitasigmavirus: ++14:50
hemanthm+114:50
nikhilI am quite clear on the problem14:50
sigmavirusI think what you're saying is that you want to have automation that hooks into the release automation when we create a release14:50
*** xiaohhui has quit IRC14:50
sigmavirusThat's the basis of everything, yes?14:50
nikhilfor this issue, may be that's the answer14:50
sigmavirusKind of like we have tools/test-setup.sh that will run for our gate jobs14:50
sigmavirusnikhil: if you're clear on the issue, I'm not getting a cohesive picture of it from everyoen else14:51
nikhilsigmavirus: alright, let me be explicit14:51
*** hongbin has joined #openstack-meeting-414:51
nikhilthis is the review :-14:52
nikhil#link https://review.openstack.org/#/c/438736/14:52
stevelleI think automating something that happens 2x per year is a digression derailing the meeting at this point14:52
nikhilit has the var CURRENT_RELEASE hardcoded to the current release name14:52
rosmaitastevelle: good point14:52
*** Julien-zte has joined #openstack-meeting-414:52
rosmaitalet's go with the checklist approach for now14:52
nikhilso you are saying we are not discussing important stuff14:53
rosmaitawe're saying that we're not having open discussion14:53
* nikhil leaves the meeting14:53
rosmaita#topic open discussion14:53
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:53
rosmaita(i got feedback that i should make sure we have open discussion time at each meeting)14:54
rosmaita(and whenever i do ... there's usually no discussion)14:54
jokke_:)14:55
jcookhi14:55
jcook:)14:55
sigmavirus^5 for everyone14:55
rosmaitawe need to get the previous topic settled before August 714:55
jcookI have a question14:56
*** yfauser has joined #openstack-meeting-414:56
jcookDoes anyone know of a deployment that builds thousands of concurrent VMs off an uncached image?14:56
jcookbesides Rackspace Public Cloud users?14:56
*** alexchadin has quit IRC14:56
jcookI'm assuming cern might if not cached on hypervisor or precached in glance, but I hear they are tiny.14:57
rosmaitayes, they tend to be something like 256MB14:57
jcookI think you could have stampeding heard with that size14:58
jcookherd*14:58
jokke_and answer to your question, no I would not know anyone else14:58
*** srwilkers has quit IRC14:58
jcookbut maybe not with their scale, or they cache, or cache completes quickly enough14:58
*** trozet has joined #openstack-meeting-414:58
rosmaitajcook: well, cern uses lots of clouds that aren't theirs14:58
jcookah14:59
rosmaitathey get time donated by various clouds14:59
*** baoli has quit IRC14:59
rosmaitaso it could be a general problem, give all the clouds they use14:59
jcookI wonder if they fail a lot of builds and jsut retry or no14:59
rosmaitabut i haven't heard anyone mention it as a problem14:59
jcookk14:59
*** TxGirlGeek has joined #openstack-meeting-414:59
*** hemanthm is now known as hemanthm|afk15:00
rosmaitaok, we're about out of time ... look for a doodle poll about image import mtg next week15:00
*** sjmc7 has joined #openstack-meeting-415:00
rosmaita#endmeeting15:00
*** openstack changes topic to " (Meeting topic: ironic_neutron)"15:00
openstackMeeting ended Thu Mar  2 15:00:17 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2017/glance.2017-03-02-14.00.html15:00
jokke_they do have lots of resiliency on their process as those donated resources might drop when ever depending of the usage of the cloud they are using15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2017/glance.2017-03-02-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2017/glance.2017-03-02-14.00.log.html15:00
jokke_thanks all15:00
*** alex_bash has left #openstack-meeting-415:00
*** lei-zh has joined #openstack-meeting-415:01
sjmc7#startmeeting openstack search15:01
openstackMeeting started Thu Mar  2 15:01:08 2017 UTC and is due to finish in 60 minutes.  The chair is sjmc7. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
*** TravT has joined #openstack-meeting-415:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: openstack search)"15:01
openstackThe meeting name has been set to 'openstack_search'15:01
*** stevelle has left #openstack-meeting-415:01
sjmc7Morning all15:01
TravTo/15:01
Kevin_Zheng_:)15:01
rosmaitao/15:01
lei-zho/15:01
*** TxGirlGeek has quit IRC15:02
sjmc7I trust everyone is well15:02
*** crushil has joined #openstack-meeting-415:02
*** TxGirlGeek has joined #openstack-meeting-415:02
*** yingjun has joined #openstack-meeting-415:03
sjmc7ok, let’s get started15:03
sjmc7#topic nova cells15:03
*** openstack changes topic to "nova cells (Meeting topic: openstack search)"15:03
sjmc7I saw http://lists.openstack.org/pipermail/openstack-dev/2017-February/112996.html on the mailing list last week15:03
sjmc7It looks like nova is still pretty keen to use searchlight15:03
yingjungood news15:03
sjmc7Kevin_Zheng: i saw you’d replied to that thread15:04
Kevin_Zheng_Yeah15:04
Kevin_Zheng_I will be happy to do it15:04
sjmc7Excellent, thanks15:05
Kevin_Zheng_NP15:05
sjmc7I suspect that the issues with notifications requiring hits on the nova server API may become apparent15:05
sjmc7But maybe that’ll be the impetus needed to make some changes there15:05
*** TxGirlGeek has quit IRC15:06
sjmc7Did you talk to anyone aside from that thread?15:07
*** limao has joined #openstack-meeting-415:07
Kevin_Zheng_Not too much15:08
*** trinaths has joined #openstack-meeting-415:08
Kevin_Zheng_I15:08
Kevin_Zheng_Have a spec about tag notification we talked a little there15:08
sjmc7Yes, I remember that one15:09
Kevin_Zheng_I will start to check the details next week15:09
sjmc7I lost touch with the current state of notifications (versioned or otherwise) so i will try ot catch up15:09
Kevin_Zheng_I mean for the whole thing15:09
sjmc7Ok, great15:09
*** limao_ has quit IRC15:10
*** yifei has quit IRC15:10
*** baoli has joined #openstack-meeting-415:10
sjmc7It’ll be good to see how that works out, though I’m also a little nervous :)15:10
sjmc7Thanks again for taking that on15:10
Kevin_Zheng_I think people are just sum up the ptg15:10
Kevin_Zheng_So maybe next week will be better15:11
Kevin_Zheng_:)15:11
sjmc7Yep :)  They’re always tiring, especially with the travel15:11
sjmc7And a lot of people take holidays afterwards15:11
Kevin_Zheng_Yeah me too, I will ask for help here if needed15:11
sjmc7#topic Other PTG news15:11
*** openstack changes topic to "Other PTG news (Meeting topic: openstack search)"15:11
sjmc7I think only rosmaita was at the PTG from the regular contributors here15:12
sjmc7I know you were busy with glance work, which i hope went well15:12
sjmc7Or at least reached some conclusions15:12
rosmaitapossibly15:12
*** trinaths has quit IRC15:12
sjmc7Did you overhear anything that might be useful for searchlight?15:13
rosmaitano, just that nova is still talking about using it for cells15:13
sjmc7OK. Yeah, the mailing list summaries are very helpful15:13
rosmaitabut nothing specific15:13
sjmc7How was the PTG?15:13
rosmaitathe first 2 days were very disorganized15:14
rosmaitait was hard to figure out who was discussing what when15:14
sjmc7I guess that’s to be expected with a new format15:14
rosmaitayes, hopefully they'll address that next time15:14
rosmaitai think the idea was that the format will evolve organically15:15
rosmaitabut, overall it was good15:15
sjmc7Oh dear :)15:15
rosmaitaabout 600 people, i think15:15
sjmc7Oh, that’s a good turnout15:15
*** crushil has quit IRC15:15
TravTwow, that's pretty good15:15
rosmaitabut not a lot of distractions15:15
sjmc7distractions == big drunken parties?15:15
rosmaitahad a lot more time for discussions than at the typical summit15:15
*** crushil has joined #openstack-meeting-415:15
rosmaitasjmc7: there were zero drunken parties15:16
*** limao has quit IRC15:16
rosmaitabut i was just thinking of all the random people wandering around15:16
sjmc7Yeah, that seemed to be the goal, to allow the dev teams to discuss things without feeling they had to go to talks and do business activities15:16
sjmc7Well, you are a popular guy15:16
rosmaitayes, and it definitely succeeded in that regard15:16
rosmaita?15:17
sjmc7all the people wandering around wanting to talk to you15:17
*** TxGirlGeek has joined #openstack-meeting-415:17
sjmc7Has there been anything going on with the OSIC? I’ve not heard much really since Tokyo15:17
*** baoli has quit IRC15:18
lei-zhyou mean what osic people are doing?15:18
sjmc7yeah15:18
sjmc7At one time we were talking about getting in there but lost steam a bit15:19
rosmaitayeah, they've pulled back a bit on how many projects they pay attention to15:19
rosmaitai think the big think they15:20
rosmaitare pushing are the rolling upgrades stuff15:21
rosmaitaand some operational improvements15:21
sjmc7ah, yes. that’s been a problem for many years15:21
sjmc7ok. moving on then15:21
*** rbak has joined #openstack-meeting-415:21
sjmc7#topic pike goals15:21
*** openstack changes topic to "pike goals (Meeting topic: openstack search)"15:21
sjmc7There are two technical committee goals for pike15:21
*** TxGirlGeek has quit IRC15:21
*** rwallner has quit IRC15:22
sjmc7One is that all services should run in apache via WSGI15:22
sjmc7The other is python 3.5 compliance15:22
*** Julien-zte has quit IRC15:22
sjmc7I think we’re ok on python3.5 and there’s a blueprint for WSGI https://blueprints.launchpad.net/searchlight/+spec/deploy-via-wsgi which i will take for pike15:22
sjmc7take = tag15:23
Kevin_Zheng_cool15:23
sjmc7i think it should be fairly trivial (at which point it will become a massive unpleasant burden)15:23
*** TxGirlGeek has joined #openstack-meeting-415:24
sjmc7#topic Reviews15:24
*** openstack changes topic to "Reviews (Meeting topic: openstack search)"15:24
sjmc7Last thing i had was https://review.openstack.org/#/c/423884/15:24
sjmc7i had meant to merge this for Ocata and i’m a bit annoyed at myself that i missed it15:24
sjmc7There was a comment (from lei-zh i think?) about continuing to support elasticsearch 115:25
*** dave-mccowan has joined #openstack-meeting-415:25
sjmc7given that ES 5 is now out i’m ok dropping support for 1.x in the interests of simplifying code15:25
TravT+1 on dropping ES 5 support15:26
TravTi mean ES 115:26
sjmc7hahaha15:26
TravTLet's also drop ES 2.x support15:26
TravT;)15:26
*** rwallner has joined #openstack-meeting-415:26
sjmc7drop them all!15:26
yingjun;;15:26
lei-zhyeah, ES1 error string really looks weird15:26
yingjuni can't do that15:27
sjmc7that’s why they fixed it in ES 2 :)15:27
clarkbfwiw es 1 appears to still be supported by upstream. we got a new release not too long ago15:27
TravTthat bug could be backported15:27
*** LouisF has joined #openstack-meeting-415:27
sjmc7clarkb: yeah, i think Elastic will support it for some time still15:27
*** srwilkers has joined #openstack-meeting-415:27
sjmc7it was hard to migrate to 2.x for a lot of their users15:27
sjmc7we don’t have any deployments i’m aware of using 1.x (our v1 was post-elasticsearch 1)15:28
sjmc7i guess it doesn’t do any harm to keep the support if that’s the extent of it15:28
sjmc7so maybe it’s ok merging that patch as is15:28
sjmc7drop es 1 next release15:28
sjmc7But i would like ot get that one in so i can backport it15:28
sjmc7And on that note, I will also endeavour to get an elasticsearch 5.x test job running15:29
sjmc7Which i seem to say every week15:29
sjmc7Ok, I didn’t have anything else on the agenda15:30
sjmc7#topic open discussion15:30
*** openstack changes topic to "open discussion (Meeting topic: openstack search)"15:30
sjmc7I shall open the floor15:30
*** nkrinner is now known as nkrinner_afk15:30
*** hemanthm|afk is now known as hemanthm15:30
*** spzala has joined #openstack-meeting-415:30
sjmc7And if nobody stands on it in the next few minutes i’ll call it there and let people get to bed15:31
lei-zhnope15:33
sjmc7Ok then. Thanks everyone!15:33
sjmc7Have a good weekend15:33
rosmaitayou too15:33
sjmc7#endmeeting15:33
*** openstack changes topic to " (Meeting topic: ironic_neutron)"15:33
openstackMeeting ended Thu Mar  2 15:33:44 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:33
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2017/openstack_search.2017-03-02-15.01.html15:33
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2017/openstack_search.2017-03-02-15.01.txt15:33
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2017/openstack_search.2017-03-02-15.01.log.html15:33
*** yingjun has left #openstack-meeting-415:36
*** LouisF has quit IRC15:36
*** sneti_ has joined #openstack-meeting-415:37
*** tovin07 has joined #openstack-meeting-415:37
*** TxGirlGeek has quit IRC15:37
*** TxGirlGeek has joined #openstack-meeting-415:38
*** baoli has joined #openstack-meeting-415:39
*** marst has joined #openstack-meeting-415:40
*** tovin07 has left #openstack-meeting-415:40
*** baoli has quit IRC15:44
*** ativelkov has quit IRC15:44
*** trozet has quit IRC15:44
*** lei-zh has quit IRC15:45
*** ativelkov has joined #openstack-meeting-415:46
*** emagana has joined #openstack-meeting-415:46
*** alextricity25 has joined #openstack-meeting-415:48
*** v1k0d3n has joined #openstack-meeting-415:52
*** TravT has quit IRC15:52
*** galstrom_zzz is now known as galstrom15:53
*** mgariepy has joined #openstack-meeting-415:53
*** TxGirlGeek has quit IRC15:54
*** TxGirlGeek has joined #openstack-meeting-415:54
*** TxGirlGeek has quit IRC15:59
mhayden#startmeeting openstack_ansible_meeting16:00
openstackMeeting started Thu Mar  2 16:00:00 2017 UTC and is due to finish in 60 minutes.  The chair is mhayden. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
xgermano/16:00
*** openstack changes topic to " (Meeting topic: openstack_ansible_meeting)"16:00
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:00
mhaydenright at 16:0016:00
mhaydensuch joy16:00
mhayden#topic Roll Call16:00
*** openstack changes topic to "Roll Call (Meeting topic: openstack_ansible_meeting)"16:00
alextricity25o/16:00
xgermano/16:00
andymccro/16:01
andymccryou are the best at timing mhayden16:01
*** baoli has joined #openstack-meeting-416:01
*** rromans has joined #openstack-meeting-416:01
xgerman+116:01
jmccroryo/16:01
rromanso/16:02
palendaeo/16:02
*** armax has joined #openstack-meeting-416:02
*** sjmc7 has left #openstack-meeting-416:02
mgariepyo/16:02
d34dh0r53o/16:03
* mhayden waits 'til 16:0516:03
spotz\o/16:03
*** TxGirlGeek has joined #openstack-meeting-416:03
*** janonymous has quit IRC16:04
*** galstrom is now known as galstrom_zzz16:04
mhaydenokay, let's get rolling16:05
mhaydenlast week was the PTG, so there were no action items ;)16:05
logan-o/16:05
mhayden#topic Operations Guide Review - asettle16:05
*** openstack changes topic to "Operations Guide Review - asettle (Meeting topic: openstack_ansible_meeting)"16:05
* mhayden hands it over to asettle16:05
asettleHey dueds16:05
asettle... a new version of dudes16:05
mhaydensup dued16:05
asettleWell, first up16:05
*** baoli has quit IRC16:05
asettleTHanks for those that helped out reviewing the guide at the PTG - solid effort16:06
asettleSecondly - there's something I should have made clear during that effort16:06
*** galstrom_zzz is now known as galstrom16:06
asettleAnything that isn't *specific* OSA config and operations content - remove it. But don't delete - we'll move this to docs.o.o16:06
asettleHas anyone been able to see if anyone can help contribute?16:07
asettleI know evrardjp has offered to write a section (thanks man!)16:07
andymccri think i signed up for a section too16:07
*** markvoelker has quit IRC16:07
mhaydenwoot16:07
andymccrall the cool kids are signing up for ops guide sections these days... you should all try it16:08
mhaydenhah16:08
mhaydenasettle: got a link to the remaining work?16:08
evrardjpa new one?16:08
asettleuno momento16:08
asettle#link https://wiki.openstack.org/wiki/OpenStackAnsible#Documentation_planning16:08
evrardjpif all the cool kids are doing it, I'm out.16:08
asettleandymccr: could you put it in the table plz? :)16:09
andymccrevrardjp: you were one of the cool kids16:09
asettleJust so we can track what needs to be done16:09
evrardjpandymccr: that's great!16:09
asettleI appreciate you're not all operators, but, you have that knowledge :)16:09
asettleSo, yay16:09
evrardjp #hasbeenalready16:09
andymccrasettle: im in the table bottom section!16:09
jmccrorywhat's the difference between removing and deleting?16:09
asettleandymccr: oh that guy16:09
asettlejmccrory: removing (commenting out), deleting (out of tree and out of mind)16:09
andymccrhard to figure out based on my irc nick but i am infact "Andy McCrae"16:09
jmccrorygotcha16:10
spotzhehe16:10
crushil\o16:10
crushilsorry I'm late16:10
asettleWow andymccr tell me more16:10
asettleI just... I feel like I don't know you very well16:10
mhaydencrushil: welcome!16:10
asettlecrushil: nobody will every forgive you16:10
asettle... two sides of OSA16:10
asettleever*16:10
crushillol16:10
andymccrcrushil: welcome!16:10
asettlecrushil: are *you* an operator? Do you do operations?16:11
odyssey4meo/16:11
spotzasettle is vicious this week:)16:11
asettlespotz: it's not been a fun week :P16:11
asettleI"M SORRY ILL BE NICER16:11
palendaeasettle: Don't succumb to peer pressure16:11
* asettle runs around in circles16:11
asettleWhat do I do, what do I do16:11
spotzPick on Nova more?:)16:11
asettlespotz: I am like, the last in a very long line of people hatin' on nova this cycle :P16:12
* asettle points of andymccr16:12
asettleat*16:12
asettleFrick I just can't type16:12
asettlemhayden: we are done with the ops update :P16:12
mhaydenwoot!16:12
*** markvoelker has joined #openstack-meeting-416:12
*** rbak_ has joined #openstack-meeting-416:12
*** rbak has quit IRC16:12
spotzIf you couldn't tell...:)16:12
mhayden#topic Python project for inventory code - palendae16:12
*** openstack changes topic to "Python project for inventory code - palendae (Meeting topic: openstack_ansible_meeting)"16:12
* mhayden hands it to palendae16:12
*** psachin has quit IRC16:12
*** sneti_ has quit IRC16:13
crushilasettle, not really. I was an operator in my previous life. Trying to be part of a contributor in multiple projects including OSA16:13
palendaeThere's a review up at https://review.openstack.org/#/c/418076/ to move the inventory code into a Python package. Would appreciate input on naming. stevelle already provided some feedback16:13
palendaeMy main concern with naming it - it may grow to have more than inventory stuff in it, so I'd opt for not referencing only inventory16:14
palendae(and yes, I will fix the merge conflict today)16:14
palendae#link https://review.openstack.org/#/c/418076/16:14
palendaeAnd that's all I have16:14
*** galstrom is now known as galstrom_zzz16:14
asettlecrushil: that's alllll I need ;)16:15
asettlehttps://wiki.openstack.org/wiki/OpenStackAnsible#Documentation_planning16:15
asettlesorry palendae16:15
andymccrpalendae: so the aim is to review that PR once its unmergeconflicted16:15
palendaeandymccr: That and provide names...maybe I should set up a place to vote separately16:15
*** galstrom_zzz is now known as galstrom16:15
*** Syed__ has joined #openstack-meeting-416:15
andymccrpalendae: ok cool16:15
andymccrpalendae: so we'd have to move that out into a separate repo (once it's named) i assume?16:16
odyssey4mepalendae do we intend to move it out into its own repo to become a library?16:16
palendaeI don't intend to move it yet, no16:16
palendaeYou can have more than one package in a repo; glance already does this16:16
*** jovon has joined #openstack-meeting-416:17
*** bgmccollum has joined #openstack-meeting-416:17
*** baoli has joined #openstack-meeting-416:18
andymccrpalendae: i guess once the bits are there we can figure out the details afterwards?16:18
palendaeYeah16:18
*** trozet has joined #openstack-meeting-416:18
andymccrsounds good to me.16:18
palendaeThey don't strictly need to exist in a separate repo to be a pip-installable package16:18
palendaeSo we can get something installable for now and I guess if people really want more repos we can16:18
odyssey4meok cool, keeping it in-repo certaonly makes testing easier16:19
*** cloudtrainme has joined #openstack-meeting-416:19
andymccryeah i think its a future looking thing, we could do at some point if/when it makes sense but for now it doesnt really make sense16:19
andymccr(splitting out into its own repo)16:19
odyssey4meand if we can do more than one package from a single repo, then there is hope for one day doing 'pip install openstack-ansible' and magic happens!16:19
andymccrodyssey4me: magic already happens16:19
cloudnullo/16:19
palendaeodyssey4me: Right. But with a different name :p16:19
andymccrNo matching distribution found for openstack-ansible16:20
andymccrmagic!16:20
andymccrok we good on this topic? palendae mhayden?16:20
evrardjppip install osa16:21
evrardjpshould do everything for us16:21
evrardjpthat's magic.16:21
palendaehttps://etherpad.openstack.org/p/osa-python-package-name for voting I guess16:21
* mhayden yields to palendae if we're done discussing this one16:21
palendaeWith that link, I think we can be :)16:21
andymccr#link https://etherpad.openstack.org/p/osa-python-package-name16:22
evrardjphttps://martinfowler.com/bliki/TwoHardThings.html16:22
andymccr#action vote for a name!16:22
mhaydenwoot16:22
palendaeevrardjp: indeed16:22
mhaydensome voting (and trolling) already underway16:22
*** sp_ has quit IRC16:22
andymccrwe can probably collect a list and have a vote at next meeting?16:23
andymccrunless actual votes go into the etherpad16:23
mhaydensounds good16:23
palendaeandymccr: Works for me16:23
*** TxGirlGeek has quit IRC16:23
mhaydenpalendae: get something out to the ML for that if you can16:23
mhaydenokay, moving right along16:23
mhayden#topic Release Planning & Decisions - andymccr16:23
*** openstack changes topic to "Release Planning & Decisions - andymccr (Meeting topic: openstack_ansible_meeting)"16:23
* mhayden passes it to andymccr16:23
mhaydeni hear there's a big release on the way16:23
mhaydensomething about a deadline16:23
andymccryou heard correctly!16:23
andymccrso next week is the deadline, i'll be doing the release either tomorrow or early next week.16:24
andymccrWhat i need from everybody is16:24
andymccr1. tell me any critical blockers16:24
cloudnullerator for the win  !16:24
cloudnullimo16:24
andymccr2. help review https://review.openstack.org/#/c/439691/ - which is a blocker16:24
spotzIf I'm not about ping for reviews16:24
andymccrjamesdenton raised some upgrade bugs which that should fix and i'd like that in for release16:25
andymccrbut if there are no other blockers i'll do a sha bump once that's in and release straight away16:25
spotzandymccr: Did you verify against the comment from Matt? I looked at it yesterday but wasn't sure you were going to change things again16:25
*** karthiks has quit IRC16:25
*** baoli has quit IRC16:26
andymccrspotz: yeah there is a tricky setup in that new builds vs upgrades have a different process16:26
spotzYou're all approvedL)16:26
*** baoli has joined #openstack-meeting-416:26
andymccrwhich is why the patch is needed :) but yeah16:26
andymccrthanks!16:26
andymccrnewton/mitaka releases - i need to check if it goes out this week or next16:27
*** baoli has quit IRC16:27
andymccri'll keep with the 2 week cadence, so if we released 2 weeks ago this will be the next release week16:27
andymccragain any issues or questions let me know!16:27
andymccrand yeah - key thing - notify me of any blockers for the release!16:27
andymccrok all done on release update.16:28
mhaydenokay, good to move along?16:28
andymccrmhayden: si si16:28
*** baoli has joined #openstack-meeting-416:28
mhaydeni'm going to skip down a little16:28
mhayden#topic ceph_client on 16.0416:28
*** openstack changes topic to "ceph_client on 16.04 (Meeting topic: openstack_ansible_meeting)"16:28
mhaydenanyone want to speak to this item? there was no name on it16:29
*** salv-orlando has joined #openstack-meeting-416:29
andymccrlogan-: perhaps?16:29
logan-wasn't me16:29
mgariepymaybe cloudnull ?16:29
logan-i'm not sure, i'm using it and no huge issues afaik16:29
evrardjpI think the idea16:29
evrardjpwas to have deployer's opinions16:30
cloudnullnot i16:30
evrardjpfor the ceph_client thing. There is supposed to have two links there for the meeting16:30
evrardjptwo weeks ago this was added to the agenda due to a conversation during triage16:30
evrardjplet me give you the links16:30
evrardjpso that's the bug:16:31
evrardjphttps://bugs.launchpad.net/openstack-ansible/+bug/166194816:31
openstackLaunchpad bug 1661948 in openstack-ansible "ceph_client: on ubuntu 16.04 default Ceph version (hammer) causes conflicts " [Undecided,New]16:31
evrardjp#link https://bugs.launchpad.net/openstack-ansible/+bug/166194816:31
evrardjpand that's our conversation16:31
evrardjp#link http://eavesdrop.openstack.org/irclogs/%23openstack-ansible/%23openstack-ansible.2017-02-07.log.html#t2017-02-07T16:15:2416:31
evrardjpwe were waiting two weeks ago for a feedback from Travis IIRC16:32
evrardjpor for any other deployer16:32
*** baoli has quit IRC16:33
evrardjpso do we do this in this "stable" branch ?16:33
andymccrhnn16:33
evrardjpor16:34
evrardjpwe just leave it as is, and wait for another input.16:34
andymccri think we need more input tbh16:34
andymccri know logan- and a few others are actively using ceph - and if we can't re-create the problem it'll be hard to fix it also16:34
evrardjplogan-: what's the version currently deployed?16:34
evrardjpalso keep in mind that now we have uca everywhere, and not only "base xenial repos"16:35
logan-newton is still hammer by default I think16:35
evrardjpI suggest we keep it that way, and wait for more feedback.16:35
evrardjpoh I already said taht16:36
*** tonytan4ever has quit IRC16:36
evrardjpI'm becoming a goldfish16:36
spotzUCA stuff has been rock solid, they put up a working liberasurecode1 for me in netwon-proposed if anyone needs it16:36
logan-hmm actually ceph_stable_release is not defined in newton, that's strange16:36
*** makowals has quit IRC16:36
*** TxGirlGeek has joined #openstack-meeting-416:36
*** tonytan4ever has joined #openstack-meeting-416:36
logan-oh it's in vars16:37
logan-yeah hammer16:37
evrardjpit's in vars16:37
logan-ocata+ is jewel by default, so we should see this problem less over time as we maintain the ceph version better16:37
evrardjpok16:37
logan-i will bump ceph_client to the next ceph LTS in Q so we don't get behind like this again16:38
evrardjpif we see the bug appearing on N, we'll think of a bump of ceph version and a bump of osa version for N branch I guess :)16:38
evrardjplogan-: great!16:38
logan-actually pike might be best, i'm not sure, but depending on the timing of the LTS16:38
evrardjpIf that's a periodic thing, maybe you can add that to our openstack-ansible agenda :)16:39
logan-ok16:39
*** smatzek_ has joined #openstack-meeting-416:39
mhaydenare we good on this topic?16:39
evrardjpI think so16:40
*** dtardivel has quit IRC16:40
logan-yeah16:40
*** cloudtrainme has quit IRC16:41
logan-#action logan- add ceph_client version bump to development cycle checklist16:42
*** pcaruana has quit IRC16:42
evrardjp#link https://docs.openstack.org/developer/openstack-ansible/ocata/developer-docs/contribute.html#development-cycle-checklist16:42
evrardjpthis way it's logged next to action :)16:42
*** joedborg has quit IRC16:42
mgariepythe ceph client version should be compatible with older release no ?16:43
mhaydenokay, movin' along16:43
mhayden#topic Bugs needing attention - evrardjp16:43
*** openstack changes topic to "Bugs needing attention - evrardjp (Meeting topic: openstack_ansible_meeting)"16:43
evrardjpmgariepy: that's a good point16:43
mhaydenevrardjp: anything pressing this week in bug land?16:43
evrardjpoh ok16:43
evrardjpyes16:43
*** bgmccollum has left #openstack-meeting-416:43
evrardjpWe have 2 Critical bugs:16:43
evrardjpVery slow Xenial gate jobs and Rebuilding keystone[0] container breaks credential keys16:44
*** makowals has joined #openstack-meeting-416:44
evrardjpthe first one is sitting for a while, and the second need some love I guess16:44
andymccri'd also like to add this one as a key bug:16:44
andymccrhttps://bugs.launchpad.net/openstack-ansible/+bug/166710316:44
openstackLaunchpad bug 1667103 in openstack-ansible "Error upgrading MariaDB during N->O upgrade" [High,Confirmed]16:44
*** baoli has joined #openstack-meeting-416:44
logan-for the keystone bug, I plan to have a patch up tomorrow and it will need backports and added to releases asap16:44
mhaydenslow xenial jobs are a PITA for sure16:44
evrardjpI was planning to go to high bugs later, but that's fine16:44
evrardjpwe have 4 high level bugs16:45
mhaydencanonical is still working on the xenial perf problems16:45
evrardjpI think these bugs need either work, or re-classification16:45
andymccrlogan-: if its up tomorrow we can perhaps wait for that before releasing?16:45
evrardjpI'd be enclined to wait for the critical to merge before releasing16:46
logan-yep16:46
andymccralthough i guess that impacts other releases so i wouldnt say its a release blocker atm16:46
*** baoli has quit IRC16:47
logan-yeah i wouldn't say it is a blocker but it is something we should get in asap if the fix is accepted quickly16:47
andymccrlogan-: agreed16:47
evrardjpit's not a blocker by itself but it definitely decrease our deployer experience and we may look bad if things are broken are passed into a tag16:48
evrardjpso the faster the fix with a tag, the better, IMO16:48
andymccrit seems it impacts mostly on newton when you would do the OS upgrade16:48
andymccrbut yeah agreed we need that fixed and included16:48
evrardjpoh ok16:48
evrardjpthanks for clarificaiton16:48
evrardjpI think that's all I wanted to say, bugs need more love :)16:49
mhaydenalrighty16:50
mhayden#topic Open Floor16:50
*** openstack changes topic to "Open Floor (Meeting topic: openstack_ansible_meeting)"16:50
mhaydenwe have ~ 9 minutes16:50
jmccrorystarted notes on newton-xenial upgrade here https://etherpad.openstack.org/p/osa-newton-xenial-upgrade16:50
jmccrorystill need to add computes and do more testing16:50
evrardjpthanks jmccrory!16:50
*** cleong has quit IRC16:51
jmccrorybut anyone else that's tried and has input, feel free to add to the page16:51
jmccroryand move to docs whenever it's looking reasonable16:51
andymccrjmccrory: sounds good16:52
andymccrlogan- was going to be adding some notes anyway perhaps collab on that etherpad would be good16:52
evrardjpI think the "fresh install of xenial" is really important, ask mhayden :D16:52
*** cleong has joined #openstack-meeting-416:53
mhaydentrusty -> xenial upgrades are TURRIBLE for me so far16:53
jmccroryyep, ubuntu's script has been finicky16:53
evrardjpmhayden: could you add your comments on point 5 on the etherpad?16:53
evrardjp:)16:53
mhaydencan do16:53
evrardjpcool thanks16:54
mhaydenokay, going to close this up unless there's anything else16:54
andymccrall good this side16:55
evrardjpyup16:58
*** baoli has joined #openstack-meeting-416:58
evrardjpthanks everyone!16:58
mhayden#endmeeting16:59
*** rwallner has quit IRC16:59
*** openstack changes topic to " (Meeting topic: ironic_neutron)"16:59
openstackMeeting ended Thu Mar  2 16:59:04 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2017/openstack_ansible_meeting.2017-03-02-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2017/openstack_ansible_meeting.2017-03-02-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2017/openstack_ansible_meeting.2017-03-02-16.00.log.html16:59
*** ediardo has left #openstack-meeting-417:00
*** rwallner has joined #openstack-meeting-417:02
*** songole has joined #openstack-meeting-417:02
*** sdake has joined #openstack-meeting-417:02
*** mgariepy has left #openstack-meeting-417:04
pcarver#startmeeting service_chaining17:04
openstackMeeting started Thu Mar  2 17:04:44 2017 UTC and is due to finish in 60 minutes.  The chair is pcarver. 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: service_chaining)"17:04
openstackThe meeting name has been set to 'service_chaining'17:04
pcarverwho's here for SFC?17:05
igordcardpcarver: I am17:05
pcarver#link https://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting#Agenda_for_the_Networking-SFC_Meeting_.283.2F2.2F2017.2917:05
*** sdake_ has quit IRC17:06
pcarverCould be a quiet meeting17:06
igordcardpcarver: do you know if cathy or louis are definitely not joining?17:06
*** rwallner has quit IRC17:06
songolepcarver: this is songole17:06
pcarverhi songole17:06
pcarverigordcard: I don't know. But we can quickly run down the agenda and cover what we can17:07
pcarverfirst item https://review.openstack.org/#/c/409759/ which has some +1s but no +2s17:07
*** smatzek_ has left #openstack-meeting-417:07
songolepcarver: I have a few qs for open discussion17:07
*** cloudtrainme has joined #openstack-meeting-417:07
pcarverI haven't reviewed it myself so I will definitely try to, but we're going to need cores from python-neutronclient17:08
*** matrohon has quit IRC17:08
pcarversongole: sure. We should get there pretty quickly17:09
pcarverMoving on to the API reference https://review.openstack.org/#/c/38938517:09
pcarverI think it's almost there. Still nitpicking details but it'll eventually merge.17:09
*** crushil has quit IRC17:10
pcarverI have a question regarding chain_id17:10
igordcardwas checking new patchset now17:10
pcarversee line 40 of https://review.openstack.org/#/c/389385/15/api-ref/source/v2/sfc-port-chains.inc17:11
igordcardyes it's supposed to be known to the user17:11
*** vks1 has joined #openstack-meeting-417:11
igordcard#link https://github.com/openstack/networking-sfc/blob/master/networking_sfc/extensions/sfc.py#L22317:11
igordcardpcarver: it's similar to a Service Path Identifier (IETF)17:12
pcarverI've added a description to https://review.openstack.org/#/c/389385/17/api-ref/source/v2/parameters.yaml17:12
*** dave-mcc_ has joined #openstack-meeting-417:12
pcarverline 486717:12
pcarverAn integer chain identifier. Not to be confused with the UUID chain ID.17:12
pcarverlet me know if you have a better description17:13
pcarverI didn't really know what to write about it.17:13
igordcardpcarver: OK, I'll think about it and write something17:13
*** dave-mccowan has quit IRC17:13
igordcardpcarver: it will be converted to NSP in the path nodes17:13
igordcardpcarver: so "MAX_CHAIN_ID = 65535"17:14
pcarverAs for the API definition, I'm moving slowly but have been copying changes into my local copy based on other changes happening in the networking-sfc repo.17:14
pcarverigordcard: ok, I'll add the max to the description17:14
igordcardwith NSH it could go up to 16M different IDs17:14
*** dave-mccowan has joined #openstack-meeting-417:15
*** TxGirlGeek has quit IRC17:16
*** TxGirlGeek has joined #openstack-meeting-417:16
pcarverFor the API definition I believe the right thing to do is to refactor the "normalize" functions to neutron-lib converters17:17
*** dave-mcc_ has quit IRC17:17
pcarverusing either the existing ones or adding new ones if necessary17:17
pcarverI don't think functions like normalize_chain_parameters should be added to neutron-lib17:17
igordcardpcarver: right... still they would be in neutron-lib, but specifically in the api for sfc file17:18
pcarverperhaps, but if it can be done more generically that would be preferable17:19
*** mohankumar has joined #openstack-meeting-417:19
pcarverneutron-lib has an existing structure for specifying and applying both validators and converters17:19
pcarverunless the validation simply can't be expressed generically17:20
*** LouisF has joined #openstack-meeting-417:21
pcarverbut I'll work through it and figure out what's best and we can discuss via the review17:21
igordcardit would be nice if it could have a method to generate validators and normalizers given a simple dict of possible key/value combinations17:21
*** corey has joined #openstack-meeting-417:21
LouisFhi all17:21
pcarverigordcard: I believe there are17:21
igordcardhi LouisF17:21
igordcardpcarver: great17:21
pcarverhi LouisF17:21
LouisFthanks  for starting meeting17:21
*** corey is now known as Guest5369917:21
pcarverigordcard: I need to see if I can get the same normalize result using the generic converters, either as-is or with modification17:22
*** makowals has quit IRC17:22
pcarvernext on the agenda: Ocata release: SFC graph, NSH dataplane, OVN driver17:22
igordcardpcarver: cool... including per-key defaults17:23
pcarveroh, shoot. I should be setting topics shouldn't I17:23
pcarver#topic Ocata release: SFC graph, NSH dataplane, OVN driver17:23
*** openstack changes topic to "Ocata release: SFC graph, NSH dataplane, OVN driver (Meeting topic: service_chaining)"17:23
*** cleong has quit IRC17:23
pcarverI forgot about the # topic command17:23
songolepcarver: is symmetric chain also part of Ocata?17:24
pcarveris there anything to discuss with regard to these three items?17:24
igordcardyep I symmetric chains are, for ovs at least17:25
igordcardregarding Ocata: NSH dataplane had already been delayed to Pike given the OVS dependency17:25
LouisFigordcard: ok17:25
vks1igordcard, i tested the patch17:25
igordcardalso, I have re-targeted SFC Graphs to Pike too given the right release schedule17:25
pcarver#info NSH dataplane had already been delayed to Pike given the OVS dependency17:25
igordcardand finally, MPLS correlation in port-pairs is the big feature ready for Ocata (just waiting for more reviews now)17:26
songoleigordcard: patch link for mpls?17:26
pcarverigordcard: bleeding over into the next topic on the agenda, but didn't we already cut the stable/ocata branch?17:26
igordcard#link https://review.openstack.org/#/c/420339/17:26
LouisFpcarver: not yet17:26
songolethanks17:26
igordcardstable/ocata for networking-sfc:17:27
igordcard#link https://review.openstack.org/#/c/439200/17:27
pcarver#topic stable/ocata branch17:27
*** openstack changes topic to "stable/ocata branch (Meeting topic: service_chaining)"17:27
pcarverdo we have a target date?17:27
pcarverThis was a topic of concern at the PTG17:28
pcarverstarting with Pike we need to align with rest of the stadium17:28
pcarverFor Ocata it's as soon as possible, already done would have been better17:28
LouisFpcarver: want to pull stable/ocata branch today17:29
*** mohankumar has quit IRC17:29
pcarverLouisF: Great17:29
pcarverigordcard: is that an issue for the MPLS patch?17:30
LouisFpcarver: will post update to https://review.openstack.org/#/c/439200/17:30
igordcardpcarver: well the mpls patch should be merged before the branch is cut17:30
igordcardpcarver: it's not a bugfix...17:30
igordcardthe code has remained unchanged for the past 11 days, only documentation suffered changes17:31
pcarverlooks like I'm a couple patch sets behind, but I was ok with 1917:31
LouisFigordcard: if it merges today i will include it17:31
pcarverI'll look at the changes since 19 in about 2 hours. I have a meeting right after we finish this one.17:32
igordcardcorrection, wrong patchset, for the last 7 days17:32
igordcardpcarver: thank you!17:32
pcarveranything else on stable/ocata topic?17:33
pcarver#topic  Bug scrub17:34
*** openstack changes topic to "Bug scrub (Meeting topic: service_chaining)"17:34
*** ralonsoh has quit IRC17:34
pcarversounds no one has anything to say on bugs17:35
pcarver#topic Open Discussion17:35
*** openstack changes topic to "Open Discussion (Meeting topic: service_chaining)"17:35
pcarversongole: you had some items?17:35
songolepcarver: we are starting to come upto speed on neutron-sfc17:35
pcarversongole: sorry, could you introduce yourself. I'm not sure whether I know you.17:36
songolewe have an use case to insert IPS (inline bump in the wire) and IDS service17:36
pcarverAnd who you're including in "we"17:36
songolepcarver: sure17:36
vks1pcarver, its me also17:36
vks1songole, pls go ahead17:36
songolevikash and muself work closely at One Convergence. We actively participate in GBP project17:37
*** rfolco has quit IRC17:37
igordcardsongole: any interst in using networking-sfc as SFC backend in GBP?17:37
songolemuself -> myself17:37
*** makowals has joined #openstack-meeting-417:38
vks1pcarver, i had talked to igordcard regarding same17:38
songoleigordcard: Not yet with GBP. But, we have a neutron usecase for a customer17:38
songoleRegarding the use case, vks1 tried to insert an IPS device17:40
igordcardsorry I have to go right now, cya all, thank you17:40
vks1igordcard, one sec17:40
igordcardI'll catch up on the meeting log later17:40
vks1igordcard, will send u an email17:40
vks1igordcard, as aggreed17:40
vks1igordcard, ok17:40
igordcardvks1: right now destination mac addresses get rewritten, so you don't get proper BITW17:40
igordcardvks1: yep17:41
vks1igordcard, yeah correct17:41
*** ltomasbo is now known as ltomasbo|away17:41
songoleigordcard: thanks for clarifying..17:41
*** mohankumar has joined #openstack-meeting-417:41
pcarverSo are we considering that a bug?17:42
pcarverOr a new use case?17:42
vks1pcarver, new use case17:42
LouisFpcarver: it would be a new use case17:42
vks1igordcard, i was trying to push this for few days17:42
*** Kevin_Zheng_ has quit IRC17:43
songolepcarver, LouisF: how do we go about addressing this use case?17:43
pcarversongole: are you planning to develop or just write the use case?17:43
LouisFvks1: currently the dest mac is used to steer packets to next hop port-pair17:43
LouisFin the ovs driver that is17:44
vks1LouisF, yeah but that suits only L3 device17:44
pcarverIf it's something that someone isn't already working on I think probably we should follow the Neutron process of starting with an RFE bug17:44
vks1LouisF, I believe I have discussed this in mailing list with you17:44
songolepcarver: ok. I will create one17:45
songoleregarding IDS use case where pkts need to be copied and sent to the port pair17:45
LouisFpcarver: agree this can be handled by indicating that the SF is bitw and mac must not be modified17:46
*** krtaylor has quit IRC17:46
songoleis there a provision in the APIs today..17:46
LouisFvks1: i presume this applies to src mac and dest mac?17:46
vks1LouisF, yeah SFC now rewrite mac as u mentioned but the IPS/IDS use case doesn't require modification17:47
songoleLouisF: I believe just the dest mac17:48
LouisFthere was a patch to add a sf-mode field to the port-pair parameter to handle this17:49
LouisFi think it was abandoned, but that can be re-used17:50
vks1LouisF, can u point me ?17:50
songoleLouisF: could you provide the link?17:50
LouisFvks1: i will check on that17:50
vks1LouisF, ok17:50
LouisFi think pavel wrote the patch17:51
songoleLouisF: thanks. Any suggestions for IDS insertion?17:52
LouisFsongole: elaborate the requirement17:52
songoleok. IDS is not an inline device, but is just an out of band inspection device17:53
songoleIt doesn't forward pkts to the next hop17:53
songolepkts need to be copied and sent to this SF17:54
pcarversongole: that's more of a mirroring than service chaining17:54
pcarverI don't know if we've looked at how networking-sfc interacts with networking-taas17:54
pcarverIdeally you'd be able to use both simultaneously, but I don't know if that works17:54
songolepcarver: ok. is networking-taas part of neutron tent just like neutron-sfc?17:55
pcarversongole: I believe so, more or less17:55
songoleokay. We will explore it further.17:56
pcarverI don't follow networking-taas closely and don't remember whether it passed all the requirements for stadium inclusion17:56
LouisFsongole: this can probably in handled in a similar fashion - a port-pair can be marked as "tap"17:57
pcarverLouisF: Do we support packet copy? They need duplication of packets, not just steering17:57
*** rbak_ has quit IRC17:58
LouisFif so, its behavior it to sent packet to17:58
LouisFSF ingress port and forward packet on to next hop in port chain17:59
pcarvernetworking-taas is specifically targetted at making copies of packets for tap use, but it looks like it's not a Neutron stadium project from the perspective of policy and governance17:59
songolepcarver: thanks for looking17:59
LouisFpcarver: i think this can be added as new port-chain feature without much difficulty18:00
pcarverIt is an OpenStack project and specifically intended to work with Neutron, but doesn't appear to have passed the required criteria to be considered part of "Neutron Stadium"18:00
pcarverlooks like we're out of time18:00
LouisFsongole: these two freatures are independent ?18:00
songoleLouisF: thanks. We can discuss further over email.18:01
pcarverI'm going to end meeting. Suggest that songole: create RFE bug and write up the full details of requirement18:01
vks1LouisF, we can achieve but we need to extend apis18:01
songoleLouisF: yes18:01
LouisFvks1: yes18:01
pcarver#endmeeting18:01
*** openstack changes topic to " (Meeting topic: ironic_neutron)"18:01
*** srwilkers has quit IRC18:01
openstackMeeting ended Thu Mar  2 18:01:28 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-03-02-17.04.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-03-02-17.04.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-03-02-17.04.log.html18:01
LouisFvks1: we can do that18:01
vks1LouisF, will send u an igordcard email regarding same18:01
pcarveryou can also continue discussing in networking-sfc channel. I've got to get to anohter meeting18:02
LouisFpcarver: ok18:02
*** sambetts is now known as sambetts|afk18:02
*** croelandt has left #openstack-meeting-418:03
*** rwallner has joined #openstack-meeting-418:03
*** SumitNaiksatam has joined #openstack-meeting-418:03
*** liangy has quit IRC18:05
*** spzala has quit IRC18:06
*** iyamahat has joined #openstack-meeting-418:06
*** rwallner has quit IRC18:08
*** liangy has joined #openstack-meeting-418:09
*** yamahata has joined #openstack-meeting-418:12
*** woodard has joined #openstack-meeting-418:15
*** TxGirlGeek has quit IRC18:15
*** unicell has joined #openstack-meeting-418:15
*** TxGirlGeek has joined #openstack-meeting-418:17
*** cloudtrainme has quit IRC18:19
*** rwallner has joined #openstack-meeting-418:19
*** TxGirlGeek has quit IRC18:20
*** woodard has quit IRC18:20
*** TxGirlGeek has joined #openstack-meeting-418:21
*** crushil has joined #openstack-meeting-418:25
*** vks1 has quit IRC18:26
*** mugsie has quit IRC18:26
*** TxGirlGeek has quit IRC18:35
*** TxGirlGeek has joined #openstack-meeting-418:37
*** LouisF has quit IRC18:38
*** SumitNaiksatam has quit IRC18:39
*** liangy has quit IRC18:39
*** SarathMekala has joined #openstack-meeting-418:41
*** spzala has joined #openstack-meeting-418:43
*** jose-phi_ has joined #openstack-meeting-418:45
*** rfolco has joined #openstack-meeting-418:46
*** jose-phillips has quit IRC18:46
*** spzala has quit IRC18:51
*** salv-orl_ has joined #openstack-meeting-418:52
*** crushil has quit IRC18:53
*** crushil has joined #openstack-meeting-418:53
*** sdake_ has joined #openstack-meeting-418:54
*** salv-orlando has quit IRC18:55
*** sdake has quit IRC18:55
*** krtaylor has joined #openstack-meeting-419:04
*** s3wong has joined #openstack-meeting-419:05
*** thorst has quit IRC19:09
*** dharinic is now known as dharinic|lunch19:09
*** thorst has joined #openstack-meeting-419:10
*** neiljerram has quit IRC19:10
*** SumitNaiksatam has joined #openstack-meeting-419:11
*** vishnoianil has quit IRC19:12
*** thorst has quit IRC19:14
*** mohankumar has quit IRC19:18
*** armax has quit IRC19:20
*** srwilkers has joined #openstack-meeting-419:23
*** srwilkers has quit IRC19:24
*** sdake_ has quit IRC19:24
*** srwilkers has joined #openstack-meeting-419:29
*** liangy has joined #openstack-meeting-419:31
*** armax has joined #openstack-meeting-419:31
*** Rockyg has joined #openstack-meeting-419:34
*** crushil has left #openstack-meeting-419:34
*** mugsie has joined #openstack-meeting-419:35
*** irenab_ has quit IRC19:35
*** rwallner has quit IRC19:44
*** songole has quit IRC19:46
*** rbak_ has joined #openstack-meeting-419:47
*** dharinic|lunch is now known as dharinic19:50
*** rwallner has joined #openstack-meeting-419:52
*** armax has quit IRC19:58
*** cloudtrainme has joined #openstack-meeting-420:01
*** rbak_ has quit IRC20:04
*** vishnoianil has joined #openstack-meeting-420:05
*** rwallner has quit IRC20:05
*** rwallner has joined #openstack-meeting-420:07
*** rwallner has quit IRC20:07
*** rwallner has joined #openstack-meeting-420:08
*** bobmel has quit IRC20:10
*** liuyulong_ has joined #openstack-meeting-420:11
*** liuyulong has quit IRC20:15
*** bobmel has joined #openstack-meeting-420:18
*** srwilkers has quit IRC20:22
*** TxGirlGeek has quit IRC20:33
*** thorst has joined #openstack-meeting-420:35
*** cloudtrainme has quit IRC20:36
*** rocky_g has joined #openstack-meeting-420:38
*** srwilkers has joined #openstack-meeting-420:42
*** rwallner has quit IRC20:42
*** rwallner has joined #openstack-meeting-420:43
*** DFFlanders has joined #openstack-meeting-420:47
*** rfolco has quit IRC20:51
*** jose-phillips has joined #openstack-meeting-420:51
*** jose-phi_ has quit IRC20:53
*** salv-orl_ has quit IRC20:54
*** rwallner has quit IRC21:03
*** rwallner has joined #openstack-meeting-421:07
*** rwallner_ has joined #openstack-meeting-421:08
*** rwallner has quit IRC21:11
*** rwallner_ has quit IRC21:13
*** emagana has quit IRC21:16
*** emagana has joined #openstack-meeting-421:16
*** TxGirlGeek has joined #openstack-meeting-421:18
*** srwilkers has quit IRC21:19
*** emagana_ has joined #openstack-meeting-421:20
*** joedborg has joined #openstack-meeting-421:20
*** emagana has quit IRC21:21
*** emagana_ has quit IRC21:24
*** yfauser has quit IRC21:25
*** yfauser has joined #openstack-meeting-421:25
*** salv-orlando has joined #openstack-meeting-421:28
*** bobmel has quit IRC21:28
*** yfauser has quit IRC21:30
*** bobmel has joined #openstack-meeting-421:30
*** yfauser has joined #openstack-meeting-421:32
*** TxGirlGeek has quit IRC21:32
*** irenab_ has joined #openstack-meeting-421:35
*** bobmel has quit IRC21:35
*** yfauser has quit IRC21:36
*** dave-mccowan has quit IRC21:44
*** irenab_ has quit IRC21:47
*** irenab_ has joined #openstack-meeting-421:49
*** Guest53699 has quit IRC21:53
*** cjloader_ has joined #openstack-meeting-421:53
*** anteaya has quit IRC21:54
*** cjloader has quit IRC21:57
*** cjloader_ has quit IRC21:58
*** joedborg has quit IRC21:59
*** anteaya has joined #openstack-meeting-422:06
*** thorst has quit IRC22:08
*** SarathMekala has quit IRC22:09
*** SarathMekala has joined #openstack-meeting-422:09
*** krtaylor has quit IRC22:17
*** TxGirlGeek has joined #openstack-meeting-422:17
*** SarathMekala has quit IRC22:21
*** bobmel has joined #openstack-meeting-422:32
*** yfauser has joined #openstack-meeting-422:33
*** rwallner has joined #openstack-meeting-422:34
*** thorst has joined #openstack-meeting-422:36
*** bobmel has quit IRC22:36
*** liuyulong_ has quit IRC22:37
*** yfauser has quit IRC22:37
*** rwallner has quit IRC22:38
*** thorst has quit IRC22:41
*** salv-orlando has quit IRC22:51
*** salv-orlando has joined #openstack-meeting-422:51
*** tonytan4ever has quit IRC22:51
*** yfauser has joined #openstack-meeting-422:59
*** yfauser has quit IRC23:04
*** baoli has quit IRC23:04
*** krtaylor has joined #openstack-meeting-423:04
*** rocky_g has quit IRC23:05
*** uck has joined #openstack-meeting-423:08
*** sdake has joined #openstack-meeting-423:09
*** liangy has quit IRC23:11
*** thorst has joined #openstack-meeting-423:17
*** sdake has quit IRC23:18
*** sdake has joined #openstack-meeting-423:19
*** thorst has quit IRC23:19
*** SarathMekala has joined #openstack-meeting-423:27
*** bobmel has joined #openstack-meeting-423:31
*** marst has quit IRC23:31
*** tonytan4ever has joined #openstack-meeting-423:32
*** baoli has joined #openstack-meeting-423:33
*** bobmel has quit IRC23:37
*** klamath has quit IRC23:37
*** sp_ has joined #openstack-meeting-423:39
*** sdake has quit IRC23:40
*** TxGirlGeek has quit IRC23:41
*** galstrom is now known as galstrom_zzz23:41
*** sdake_ has joined #openstack-meeting-423:41
*** marst has joined #openstack-meeting-423:42
*** bobmel has joined #openstack-meeting-423:52
*** sdake_ has quit IRC23:53
*** bobmel has quit IRC23:56

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