Thursday, 2017-03-09

*** salv-orlando has quit IRC00:05
*** david-lyle has joined #openstack-meeting-400:08
*** hongbin has quit IRC00:14
*** david-lyle has quit IRC00:15
*** kylek3h has joined #openstack-meeting-400:18
*** limao has joined #openstack-meeting-400:23
*** thorst has joined #openstack-meeting-400:25
*** spzala has joined #openstack-meeting-400:25
*** dave-mccowan has joined #openstack-meeting-400:25
*** thorst has quit IRC00:29
*** Julien-zte has joined #openstack-meeting-400:34
*** sshnaidm is now known as sshnaidm|off00:46
*** zhurong has joined #openstack-meeting-400:47
*** rfolco has quit IRC00:48
*** david-lyle has joined #openstack-meeting-400:54
*** david-lyle has quit IRC00:54
*** Syed__ has quit IRC00:55
*** SerenaFeng has joined #openstack-meeting-400:56
*** Jeffrey4l_ has quit IRC01:00
*** dave-mccowan has quit IRC01:02
*** thorst has joined #openstack-meeting-401:02
*** thorst has quit IRC01:02
*** FrankZhang has quit IRC01:11
*** zhubingbing_ has joined #openstack-meeting-401:11
*** stanchan has joined #openstack-meeting-401:15
*** stanchan has quit IRC01:18
*** cjloader_ has quit IRC01:19
*** cjloader_ has joined #openstack-meeting-401:20
*** unicell has quit IRC01:34
*** salv-orlando has joined #openstack-meeting-401:37
*** salv-orlando has quit IRC01:41
*** dave-mcc_ has joined #openstack-meeting-401:50
*** david-lyle has joined #openstack-meeting-401:52
*** thorst has joined #openstack-meeting-402:03
*** tovin07_ has joined #openstack-meeting-402:06
*** thorst has quit IRC02:08
*** spzala has quit IRC02:10
*** cathrich_ has joined #openstack-meeting-402:17
*** trinaths1 has left #openstack-meeting-402:17
*** Kevin_Zheng has joined #openstack-meeting-402:17
*** emagana has quit IRC02:18
*** emagana has joined #openstack-meeting-402:22
*** markvoelker has quit IRC02:23
*** emagana has quit IRC02:27
*** gongysh has joined #openstack-meeting-402:28
*** salv-orlando has joined #openstack-meeting-402:38
*** Jeffrey4l_ has joined #openstack-meeting-402:39
*** salv-orlando has quit IRC02:42
*** galstrom_zzz is now known as galstrom02:48
*** rfolco has joined #openstack-meeting-402:49
*** rfolco has quit IRC02:50
*** dave-mcc_ has quit IRC02:54
*** thorst has joined #openstack-meeting-402:54
*** armax has joined #openstack-meeting-402:54
*** thorst has quit IRC02:54
*** amotoki has joined #openstack-meeting-402:57
*** hongbin has joined #openstack-meeting-403:00
*** amotoki has quit IRC03:09
*** benj_ has quit IRC03:12
*** benj_ has joined #openstack-meeting-403:14
*** thorst has joined #openstack-meeting-403:16
*** thorst has quit IRC03:17
*** zhubingbing_ has quit IRC03:17
*** zhubingbing_ has joined #openstack-meeting-403:18
*** SerenaFeng has quit IRC03:21
*** markvoelker has joined #openstack-meeting-403:24
*** iyamahat has quit IRC03:28
*** markvoelker has quit IRC03:29
*** amotoki has joined #openstack-meeting-403:32
*** yamahata has quit IRC03:34
*** karthiks has quit IRC03:36
*** salv-orlando has joined #openstack-meeting-403:39
*** Julien-zte has quit IRC03:40
*** Julien-zte has joined #openstack-meeting-403:41
*** salv-orlando has quit IRC03:43
*** amotoki has quit IRC03:46
*** karthiks has joined #openstack-meeting-403:49
*** hongbin has quit IRC03:59
*** amotoki has joined #openstack-meeting-404:02
*** tinwood has quit IRC04:05
*** tinwood has joined #openstack-meeting-404:06
*** cjloader_ has quit IRC04:06
*** cjloader_ has joined #openstack-meeting-404:07
*** emagana has joined #openstack-meeting-404:09
*** amotoki has quit IRC04:10
*** SerenaFeng has joined #openstack-meeting-404:12
*** Julien-zte has quit IRC04:12
*** Julien-zte has joined #openstack-meeting-404:13
*** emagana has quit IRC04:14
*** KeithMnemonic has quit IRC04:14
*** links has joined #openstack-meeting-404:17
*** thorst has joined #openstack-meeting-404:17
*** l4yerffeJ__ has joined #openstack-meeting-404:21
*** l4yerffeJ_ has quit IRC04:21
*** thorst has quit IRC04:22
*** amotoki has joined #openstack-meeting-404:24
*** markvoelker has joined #openstack-meeting-404:25
*** l4yerffeJ_ has joined #openstack-meeting-404:26
*** l4yerffeJ__ has quit IRC04:26
*** markvoelker has quit IRC04:29
*** galstrom is now known as galstrom_zzz04:35
*** salv-orlando has joined #openstack-meeting-404:39
*** salv-orlando has quit IRC04:44
*** SerenaFeng has quit IRC04:53
*** psachin has joined #openstack-meeting-404:54
*** l4yerffeJ_ has quit IRC04:59
*** l4yerffeJ_ has joined #openstack-meeting-404:59
*** vks1 has joined #openstack-meeting-405:02
*** emagana has joined #openstack-meeting-405:04
*** l4yerffeJ__ has joined #openstack-meeting-405:07
*** l4yerffeJ_ has quit IRC05:08
*** emagana has quit IRC05:08
*** unicell has joined #openstack-meeting-405:14
*** gongysh has quit IRC05:16
*** unicell1 has joined #openstack-meeting-405:18
*** thorst has joined #openstack-meeting-405:18
*** unicell has quit IRC05:19
*** thorst has quit IRC05:23
*** markvoelker has joined #openstack-meeting-405:25
*** cjloader_ has quit IRC05:28
*** cjloader_ has joined #openstack-meeting-405:29
*** jose-phillips has quit IRC05:30
*** markvoelker has quit IRC05:30
*** SerenaFeng has joined #openstack-meeting-405:35
*** yamahata has joined #openstack-meeting-405:36
*** salv-orlando has joined #openstack-meeting-405:40
*** salv-orlando has quit IRC05:45
*** armax has quit IRC05:50
*** trinaths has joined #openstack-meeting-405:58
*** nkrinner_afk is now known as nkrinner05:59
*** gongysh has joined #openstack-meeting-406:01
*** links has quit IRC06:04
*** karthiks has quit IRC06:14
*** links has joined #openstack-meeting-406:16
*** thorst has joined #openstack-meeting-406:19
*** cjloader_ has quit IRC06:22
*** thorst has quit IRC06:24
*** trinaths1 has joined #openstack-meeting-406:29
*** trinaths has quit IRC06:29
*** salv-orlando has joined #openstack-meeting-406:33
*** vks1 has quit IRC06:35
*** jose-phillips has joined #openstack-meeting-406:38
*** armax has joined #openstack-meeting-406:39
*** vks1 has joined #openstack-meeting-406:47
*** vks1 has quit IRC06:51
*** Julien-zte has quit IRC06:57
*** Julien-zte has joined #openstack-meeting-406:57
*** links has quit IRC06:58
*** janki has joined #openstack-meeting-407:00
*** amotoki_ has joined #openstack-meeting-407:01
*** amotoki has quit IRC07:03
*** armax has quit IRC07:06
*** jose-phillips has quit IRC07:12
*** yamamoto has quit IRC07:14
*** links has joined #openstack-meeting-407:15
*** jose-phillips has joined #openstack-meeting-407:20
*** thorst has joined #openstack-meeting-407:20
*** salv-orl_ has joined #openstack-meeting-407:22
*** niedbalski has quit IRC07:24
*** niedbalski has joined #openstack-meeting-407:24
*** thorst has quit IRC07:24
*** salv-orlando has quit IRC07:25
*** karthiks has joined #openstack-meeting-407:27
*** anilvenkata has joined #openstack-meeting-407:35
*** bogdando has joined #openstack-meeting-407:52
*** SerenaFeng has quit IRC07:53
*** SerenaFeng has joined #openstack-meeting-407:54
*** ralonsoh has joined #openstack-meeting-407:54
*** chigang has joined #openstack-meeting-407:57
*** cartik has joined #openstack-meeting-408:00
*** Julien-zte has quit IRC08:04
*** janonymous has quit IRC08:04
*** matrohon has joined #openstack-meeting-408:04
*** makowals has quit IRC08:06
*** iyamahat has joined #openstack-meeting-408:07
*** makowals has joined #openstack-meeting-408:07
*** ltomasbo|away is now known as ltomasbo08:11
*** l4yerffeJ_ has joined #openstack-meeting-408:17
*** l4yerffeJ__ has quit IRC08:17
*** iyamahat_ has joined #openstack-meeting-408:20
*** thorst has joined #openstack-meeting-408:21
*** iyamahat has quit IRC08:24
*** iyamahat_ has quit IRC08:25
*** thorst has quit IRC08:25
*** janonymous has joined #openstack-meeting-408:30
*** irenab has quit IRC08:33
*** irenab_ is now known as irenab08:33
*** psachin has quit IRC08:35
*** irenab_ has joined #openstack-meeting-408:42
*** markvoelker has joined #openstack-meeting-408:46
*** psachin has joined #openstack-meeting-408:49
*** cartik has quit IRC08:55
*** Julien-zte has joined #openstack-meeting-408:58
*** yfauser has joined #openstack-meeting-409:07
*** yfauser has quit IRC09:14
*** thorst has joined #openstack-meeting-409:22
*** yfauser has joined #openstack-meeting-409:28
*** yfauser has quit IRC09:28
*** sshnaidm|off is now known as sshnaidm09:30
*** thorst has quit IRC09:31
*** sshnaidm is now known as sshnaidm|afk09:33
*** alexchadin has joined #openstack-meeting-409:36
*** anilvenkata has quit IRC09:36
*** joedborg has quit IRC09:36
*** Julien-zte has quit IRC09:38
*** joedborg has joined #openstack-meeting-409:38
*** joedborg has quit IRC09:43
*** joedborg_ has joined #openstack-meeting-409:43
*** yfauser has joined #openstack-meeting-409:45
*** yamahata has quit IRC09:48
*** yfauser has quit IRC09:53
*** psachin has quit IRC09:54
*** joedborg_ has quit IRC09:54
*** joedborg has joined #openstack-meeting-409:57
*** efoley has joined #openstack-meeting-410:00
*** yfauser has joined #openstack-meeting-410:03
*** SerenaFeng has quit IRC10:06
*** psachin has joined #openstack-meeting-410:06
*** SerenaFeng has joined #openstack-meeting-410:08
*** tovin07 has quit IRC10:11
*** tovin07_ has quit IRC10:12
*** yfauser has quit IRC10:16
*** pbourke has quit IRC10:23
*** yfauser has joined #openstack-meeting-410:24
*** pbourke has joined #openstack-meeting-410:25
*** efoley has quit IRC10:33
*** sambetts|afk is now known as sambetts10:35
*** zhubingbing_ has quit IRC10:36
*** Julien-zte has joined #openstack-meeting-410:37
*** gongysh has quit IRC10:44
*** sshnaidm|afk is now known as sshnaidm10:45
*** salv-orl_ has quit IRC11:00
*** salv-orlando has joined #openstack-meeting-411:01
*** salv-orlando has quit IRC11:01
*** salv-orlando has joined #openstack-meeting-411:02
*** thorst has joined #openstack-meeting-411:28
*** yamamoto has joined #openstack-meeting-411:29
*** vishwanathj has quit IRC11:29
*** vishwanathj has joined #openstack-meeting-411:29
*** aarefiev_afk has quit IRC11:32
*** markvoelker has quit IRC11:33
*** thorst has quit IRC11:33
*** yfauser has quit IRC11:33
*** SerenaFeng has quit IRC11:46
*** rfolco has joined #openstack-meeting-411:47
*** rfolco_ has joined #openstack-meeting-411:50
*** rfolco has quit IRC11:53
*** sdague has joined #openstack-meeting-411:53
*** julim has quit IRC11:54
*** rfolco_ has quit IRC11:58
*** rfolco has joined #openstack-meeting-411:59
*** sshnaidm is now known as sshnaidm|lnch12:01
*** SerenaFeng has joined #openstack-meeting-412:05
*** amotoki_ has quit IRC12:07
*** zhurong has quit IRC12:08
*** amotoki has joined #openstack-meeting-412:08
*** amotoki_ has joined #openstack-meeting-412:09
*** aarefiev_afk has joined #openstack-meeting-412:12
*** amotoki has quit IRC12:13
*** amotoki_ has quit IRC12:14
*** rwallner has joined #openstack-meeting-412:19
*** yamamoto has quit IRC12:21
*** yamamoto has joined #openstack-meeting-412:21
*** limao has quit IRC12:22
*** limao has joined #openstack-meeting-412:22
*** amotoki has joined #openstack-meeting-412:26
*** limao has quit IRC12:27
*** sshnaidm|lnch is now known as sshnaidm12:29
*** sdague has quit IRC12:36
*** thorst has joined #openstack-meeting-412:37
*** SerenaFeng has quit IRC12:38
*** salv-orlando has quit IRC12:38
*** Julien-zte has quit IRC12:42
*** Julien-z_ has joined #openstack-meeting-412:43
*** gongysh has joined #openstack-meeting-412:43
*** rwallner has quit IRC12:45
*** dave-mccowan has joined #openstack-meeting-412:57
*** rwallner has joined #openstack-meeting-412:57
*** trinaths1 has left #openstack-meeting-412:58
*** chigang has quit IRC12:59
*** yamamoto has quit IRC13:07
*** alexchadin has quit IRC13:08
*** yamamoto has joined #openstack-meeting-413:13
*** yamamoto has quit IRC13:16
*** alexchadin has joined #openstack-meeting-413:17
*** yamamoto has joined #openstack-meeting-413:17
*** yamamoto has quit IRC13:21
*** yamamoto has joined #openstack-meeting-413:25
*** salv-orlando has joined #openstack-meeting-413:28
*** cleong has joined #openstack-meeting-413:31
*** alexchadin has quit IRC13:33
*** woodard has joined #openstack-meeting-413:35
*** limao has joined #openstack-meeting-413:44
*** klamath has joined #openstack-meeting-413:49
*** klamath has quit IRC13:49
*** klamath has joined #openstack-meeting-413:50
*** julim has joined #openstack-meeting-413:52
*** zhubingbing has joined #openstack-meeting-413:53
*** limao has quit IRC13:53
*** limao_ has joined #openstack-meeting-413:53
*** limao_ has quit IRC13:55
*** limao has joined #openstack-meeting-413:56
*** SerenaFeng has joined #openstack-meeting-413:57
*** cathrichardson has joined #openstack-meeting-413:58
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
*** alexchadin has joined #openstack-meeting-413:58
*** SerenaFe_ has joined #openstack-meeting-413:59
rosmaita#startmeeting glance14:00
openstackMeeting started Thu Mar  9 14:00:02 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
*** SerenaFe_ has quit IRC14:00
openstackThe meeting name has been set to 'glance'14:00
rosmaita#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
rosmaita(that's the agenda)14:00
rosmaita#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: glance)"14:00
*** SerenaFeng has quit IRC14:00
*** cathrich_ has quit IRC14:00
dharinic\o14:00
*** stevelle has joined #openstack-meeting-414:01
*** janki has quit IRC14:01
rosmaitalight turnout, i know jokke_ is around somewhere, though14:01
rosmaitasigmavirus has a conflict this morning14:01
hemanthmo/14:02
rosmaitai decided to take some advice from stevelle and timebox the agenda more clearly14:02
alex_basho/14:02
*** SerenaFeng has joined #openstack-meeting-414:02
*** croelandt has joined #openstack-meeting-414:03
rosmaitai think we've got 35 min of stuff if i don't talk too much14:03
rosmaitaso i'll wait 2 more min to see who else arrives14:03
stevelleso if things run over, we should have time14:03
stevelleand know how much14:03
*** pmesserli has joined #openstack-meeting-414:04
rosmaitaok, let's get started ... agenda link for anyone who missed it earlier: https://etherpad.openstack.org/p/glance-team-meeting-agenda14:05
*** SerenaFeng has quit IRC14:05
rosmaita#topic updates - dates to keep in mind14:05
*** openstack changes topic to "updates - dates to keep in mind (Meeting topic: glance)"14:05
jokke_o/14:05
rosmaita#link https://etherpad.openstack.org/p/glance-pike-ptg-roadmap-prelim14:05
rosmaitayou can look at the dates there, i wont' paste here14:05
rosmaitakey things are spec proposal freeze in 2 weeks14:05
rosmaitaspec freeze 2 weeks later14:05
rosmaitavirtual midcycle - no exact date yet, just a week14:06
rosmaitavirtual operators' midcycle - no exact date yet, just a week14:06
rosmaita#topic updates - docs14:06
*** openstack changes topic to "updates - docs (Meeting topic: glance)"14:06
*** limao has quit IRC14:07
rosmaitaasettle , the docs PTL is working with us to reorganize the glance docs14:07
* asettle enters with a dramatic flourish14:07
asettleYou rang?14:07
rosmaita#link https://etherpad.openstack.org/p/glance-pike-ptg-docs14:07
jokke_\\o \o/ o// o/714:07
asettlehey!14:07
asettleSo, as per my email last week - we need to split up the work14:07
*** limao has joined #openstack-meeting-414:07
*** SerenaFeng has joined #openstack-meeting-414:07
asettleEach that volunteered - me, jokke_ alex_bash stevelle and rosmaita - we should split up the lifting14:07
*** gongysh has quit IRC14:08
asettleSomeone take admin, dev ref, etc etc14:08
jokke_Noo, there's that much of it? :o14:08
asettleWho can volunteer for what?14:08
*** amotoki has quit IRC14:08
asettlejokke_: it's just to split it up and make it go a bit faster :)14:08
rosmaitabefore we do that, i have some questions about the admin guide, operations guide, etc14:09
asettleShoot :)14:09
rosmaitamy key question is who maintains those, and where they exist?14:09
asettle... oh14:09
asettlehttps://github.com/openstack/openstack-manuals/tree/master/doc14:09
asettleWe do :)14:09
rosmaitaand where are they published to, he said ungrammatically14:09
asettlehttps://docs.openstack.org/14:09
asettleHere :)14:09
asettleEnd User Guide - user guide, ADministration Guide (admin guide) Operations Guide (ops guide)14:10
asettleThe docs team looks after this page and everything attached to it14:10
rosmaitaok, that's good14:10
asettleI apologise, when I was referencing all this content in our session I thought we were on the same page14:10
asettleNow, with that14:10
asettleI don't want a 'dump and run' on behalf of the glance team. The CPL ( alex_bash ) will be in charge of ensuring this content is maintained.14:10
jokke_asettle: I think rosmaita was just asleep ... we discussed that there ;)14:11
rosmaitayes, but i want it written down14:11
asettleKeep in mind though, I think you should keep content related to the ADministration Guide in-tree. As you may or may not know, we'll be doing a project-specific admin guide soon14:11
stevelleWhat is the essential difference between Admin / Ops guides? That drives decisions of what goes where.14:11
asettlerosmaita: the openstack-manuals project has always been around, I'm not too sure what you're asking me to write down?14:11
*** cathrichardson has quit IRC14:11
*** efoley has joined #openstack-meeting-414:12
*** cathrichardson has joined #openstack-meeting-414:12
rosmaitaasettle: i am a very simple person, i need the info i outlined on the etherpad14:12
asettlestevelle: yes, so that's an excellent question and one we're trying to address. At the moment, the admin guide is about the 'operational tasks' whereas the operations guide details 'designing and creating' your cloud14:12
rosmaitawhere the stuff is stored, where it's published, what the audience is14:12
rosmaitawe don't see the stuff that's not in our repo14:12
rosmaitaso it's not obvious where there is overlap14:12
rosmaitawhich is what we would like to eliminate14:12
asettleNo problem :)14:13
asettleI'll have it all detailed when I get a spare mo14:13
rosmaitathanks, not trying to rush you14:13
*** jamespage has left #openstack-meeting-414:13
asettleNo not at all :) we're just a bit all hands on deck with some nova stuff today (ughhhh)14:13
stevellerosmaita: we need to fix our dashboard. I made a query to find glance related docs changes we can work into our dash btw14:13
stevellewe can follow that item up later14:13
rosmaitagreat14:14
rosmaitaok, so action items are:14:14
rosmaita#action asettle will update etherpad with some descriptive info about what the docs team maintains14:14
asettle*nods* got it :)14:15
rosmaita#everyone look at the etherpad to see how our docs are being reorganized (or proposed to be re-orged)14:15
rosmaitaok, one more docs topic14:15
rosmaitathe man pages14:15
rosmaitasome distros (ubuntu) package them14:15
rosmaitabut they have tended to languish14:15
asettleWhich is interesting14:16
rosmaitakey problem is that the --help from the tools (like glance-manage) and hte man pages aren't quite in sync14:16
jokke_do we have bug opened for that?14:16
rosmaitaalso, updating for general stuff like what release is out of date too14:16
rosmaitano bug open yet14:16
rosmaitathere's a patch to update the man pages14:17
alex_bashthere would have to be many bugs14:17
rosmaitai am thinking maybe a spec-lite to propose a longer term solution?14:17
asettleQuestion - maybe a silly question - why do the distros use your man pages to package? It doesn't appear that way in other projects.14:17
rosmaitawell, nova has man pages14:17
rosmaitaso there14:18
jokke_asettle: because we and they are special :D14:18
rosmaitabut seriously, if we don't provide them, who will?14:18
asettlehahahha did you just 'so there' me rosmaita ?!14:18
rosmaita:)14:18
asettleTHat doesn't explain anything! It's a genuine question. I don't know why they do that tbh14:18
*** limao has quit IRC14:18
rosmaitawe can ask the packagers14:18
rosmaitai actually emailed some people14:18
asettleIf it comes along the way, that'd be rad to know tbh14:18
*** limao has joined #openstack-meeting-414:19
rosmaitathe RDO group says that they hate the man pages, were not sorry that you deleted them14:19
rosmaitathey prefer the --help text14:19
asettleWell, that's what I would have thought14:19
rosmaitabut, looking at the man pages, they do contain some contextual info that's missing from--help14:19
asettle(using the help text, that is)14:19
asettleWHy is it mising?14:19
asettlemissing* SHould you not be adding it in?14:19
asettle(If htat's a thing)14:19
rosmaitawell, that's an interesting question14:20
rosmaitait is not a simple thing to do given the way the tools are configured ATM14:20
* stevelle whispers "one source of truth"14:20
asettleI mean, if the issue is that the man pages contain information that the help text doesn't, isn't htat a gap you should fix rather than providing two sets of help information?14:20
* asettle is on board with stevelle rn14:20
asettlerosmaita: should that not be a greater long term bug/fix rather than trying to find another way around it?14:20
stevelleI like that answer but hold the opinion lightly right now14:20
*** woodard has quit IRC14:21
jokke_asettle: so before everything turned to wannabe Windows PowerShell the documentation and specially the manpages were used to document the behavior of the software and delivered with the software itself so it was available for those who were operating systems without access to online docs and search engines. I guess we're just old-fashioned14:21
asettleAhhhh!14:21
asettle^^ that's what i Was looking for :)14:21
asettleIt's interesting, no criticisms, promise. Just interested as to why things are they way they are14:21
rosmaitaso here's what i'm wondering14:21
rosmaitaman pages can give you some context about why you would use a tool and maybe some stuff to be aware of14:22
rosmaitalike the implications of using db purge14:22
rosmaitawhereas, --help maybe not14:22
* jokke_ also absolutely hates those 7 screen long --help outputs14:22
rosmaitawhat i'd like to see is to somehow fill in the man pages with --help text14:22
*** yamamoto has quit IRC14:23
rosmaitai agree, too much --help sucks14:23
asettle^^ that I could agree with too14:23
rosmaitabut we do want the single source of truth14:23
stevellehow about a man page that contains a url? (devils' advocate)14:23
rosmaitaok, we will return to this later when i ask if anyone wants to investigate this for a decent solution14:23
rosmaitaurl to ... ?14:24
stevellehtml docs that contain more context14:24
jokke_stevelle: sure as long as that uri is file://<path-to-local-docs> :P14:24
rosmaitaok, we'll talk more about this later14:24
jokke_;)14:24
rosmaita#topic march operators' survey14:24
*** openstack changes topic to "march operators' survey (Meeting topic: glance)"14:24
rosmaitai've got 2 surveys set up, need feedback on the questions and advice on whihc one to do in march, whihc in april14:25
rosmaita#link https://etherpad.openstack.org/p/glance-cache-operator-survey14:25
rosmaitai re-used the etherpad, it actually contains 2 surveys14:25
*** Kevin_Zheng_Hex has joined #openstack-meeting-414:25
rosmaitathe topics are owner_is_tenant=False, who does it, and glance-cache, who uses it14:26
stevellewhat's the deadline for the march survey?14:26
rosmaitai'd like to send the survey out next week, so please look them over14:26
rosmaitaprobably one week after i announce it on the operators' list14:26
rosmaitathis is our glance-specific surevey, so we cna do whatever we want14:27
rosmaitai am interested in owner_is_tenant ATM, but that's just me14:27
rosmaitaso14:27
rosmaita#action everyone feedback on https://etherpad.openstack.org/p/glance-cache-operator-survey14:27
rosmaitaany questions? (i boxed this for 5 min figuring the previous topic might run over)14:28
rosmaitaok, moving along14:28
rosmaita#topic "owned" topics reports14:29
*** openstack changes topic to ""owned" topics reports (Meeting topic: glance)"14:29
rosmaitalast week i asked for volunteers to take on specific tasks to make sure they don't fall through the cracks14:29
rosmaitai'd like to check in, see what people have been up to, and who may need to get some help/someone else to pick up the topic14:29
*** limao has quit IRC14:29
rosmaitafirst up is sigmavirus who is not here14:30
*** limao has joined #openstack-meeting-414:30
rosmaitahe's got a draft of his release czar process and advice that i've seen14:30
rosmaitai guess he'll be putting it up as a patch soon, to live somewhere in the dev docs14:30
rosmaita#topic owned - show_multiple_locations14:31
*** openstack changes topic to "owned - show_multiple_locations (Meeting topic: glance)"14:31
rosmaitanikhil was going to work on a spec for this, didn't see him around this morning, though14:31
rosmaitaspec proposal deadline is 2 weeks away, so i'm not worried yet14:31
rosmaita#topic owned - dev docs for E-M-C db migrations14:32
*** openstack changes topic to "owned - dev docs for E-M-C db migrations (Meeting topic: glance)"14:32
rosmaitahemanthm is working on this one14:32
hemanthmshould have a patch up in a bit14:32
rosmaitaexcellent14:32
jokke_gr814:32
rosmaita#topic owned - list of glance deprecated options14:32
*** openstack changes topic to "owned - list of glance deprecated options (Meeting topic: glance)"14:32
rosmaitahemanthm was working on this, but i think someone else should take it14:33
dharinicI can help hemanthm.14:33
rosmaitasold!14:33
hemanthmthanks dharinic14:34
*** FrankZhang has joined #openstack-meeting-414:34
rosmaitaquestion: the next topic was the deprecated options glance is consuming14:34
rosmaitai guess we decided to combine the two lists?14:34
hemanthmyes14:34
rosmaitaok14:34
rosmaita#topic owned - image import backend14:35
*** openstack changes topic to "owned - image import backend (Meeting topic: glance)"14:35
rosmaitathis one is jokke_ , who just put up a bunch of patches before the meeting14:35
*** links has quit IRC14:35
rosmaitajokke_: any requests, other than that people look over the patches ?14:36
jokke_would be great to get some comments as well14:36
rosmaitasorry, i meant "look over" in the sense of "review"!14:36
rosmaita#everyone review jokke's image import patches14:36
rosmaitai'll put a list in the weekly emial14:37
rosmaita*email14:37
jokke_any ideas how to improve those, but lets keep in mind this is really the MVP ... lets get those merged as soon as they "work" and we have common agreement that the approach is by the spec14:37
jokke_and iterate from that14:37
rosmaitasounds good14:37
jokke_otherwise the patches will just keep existing in my local14:37
rosmaitaand nobody wants that!14:37
jokke_indeed14:38
jokke_also that dependency chain is nightmare to maintain and rebase14:38
stevellethey always are14:38
rosmaitaok, next topic14:39
rosmaita#topic Boston "Forum" planning14:39
*** openstack changes topic to "Boston "Forum" planning (Meeting topic: glance)"14:39
*** baoli has joined #openstack-meeting-414:39
*** Jeffrey4l_ has quit IRC14:39
rosmaitai know we just finished the PTG, but it's Boston summit planning time14:39
stevellefoundation missed an opportunity by not having this premier in Rome14:39
rosmaitaactually, we devs will be at the "Forum"14:39
rosmaitastevelle: ++14:40
*** cjloader_ has joined #openstack-meeting-414:40
*** emagana has joined #openstack-meeting-414:40
* jokke_ has no idea yet if I will be there or not14:40
stevellethe deadline is already passed for talk submittions14:40
rosmaitaanyway, the info about the forum, what it is, and what facilities are available is here:14:40
*** cathrichardson has left #openstack-meeting-414:40
rosmaita#link https://etherpad.openstack.org/p/BOS-Glance-brainstorming14:40
rosmaitaso, what's weird, is that while the summit talk submissions has closed14:41
rosmaitathe forum has not14:41
*** limao has quit IRC14:41
rosmaitaand the TC is asking the community to propose stuff from which they will select14:41
rosmaitawith the proposals being on etherpad, i think14:41
rosmaitayou can read the details, i put links on the etherpad linked above14:41
*** limao has joined #openstack-meeting-414:41
rosmaitaanyway, i don't know if i've got travel support to go yet either14:42
rosmaitabut, don't let not going interfere with proposing some exciting topics!14:42
rosmaitaok, that's all i had there14:43
rosmaitai should take a quick poll, though ... how many people here understand what the "Forum" is?14:43
jokke__o_14:43
stevelleI think I do, but probably not the sanctioned answer14:44
rosmaitayeah, not sure what i meant to ask there14:44
* hemanthm raises hand half-way14:44
rosmaitai guess my question is:14:44
rosmaitaif you had travel support, would you attend the Boston Forum?14:44
* rosmaita not sure14:45
rosmaita(though i guess i'm supposed to, to gather all the feedback from operators and users)14:45
jokke_What is Boston Forum14:45
* stevelle leaning no14:45
alex_bashforum != summit?14:45
jokke_s/Forum/Forum?/14:45
rosmaitajokke_: this explains it a bit: http://lists.openstack.org/pipermail/openstack-dev/2017-March/113115.html14:46
stevellehttps://www.openstack.org/summit/boston-2017/ over May 8-11, 2017 btw14:46
rosmaitait's a part of the summit14:46
hemanthmalex_bash: that's the new name after PTG split14:46
rosmaitasupposed to be non-marketing, allow for feedback to dev teams from ops and users14:46
dharinicSo Forum is more like a dev meeting thing?14:46
rosmaitalike the ptg but with more listening and less design planning14:46
rosmaita(i think)14:47
hemanthmdev-dev is PTG14:47
dharinicahh, cool.14:47
hemanthmdev-ops/users is Forum14:47
rosmaitahemanthm: that's a good one-line description14:47
stevelleforum is one of the tracks at summit14:47
jokke_yes, I'd likely be there if I get travels arranged14:47
stevellethe way I understand it at least14:47
hemanthmstevelle: yeah, possibly. I could be wrong14:48
rosmaitastevelle: my impression was that it's a special thing, not a track14:48
rosmaitabut i could be wrong, too14:48
stevellehttps://www.openstack.org/summit/boston-2017/summit-categories/ there we go14:48
stevelleit's listed on there14:48
rosmaitayep, looks like you're right14:49
hemanthmalex_bash: forget what I said earlier :)14:49
rosmaitahemanthm: i think you're right, it's a summit track for dev-ops/users14:50
stevellepart of the summit is probably most accurate, track can mean something else14:50
dharinicthere is a category for developers seperately too.14:50
rosmaitajust that being held concurrently with everything else ... who knows how it will work?14:50
stevellethose are cloud consumers in this case dharinic14:50
dharinicoops thats for cloud apps14:50
rosmaitaanyway, back on topic ...14:51
rosmaitaplease add stuff to the etherpad so that we've got something to propose14:51
rosmaita#link https://etherpad.openstack.org/p/BOS-Glance-brainstorming14:51
rosmaitaand it looks like if have mis-esstimated time14:51
*** Jeffrey4l_ has joined #openstack-meeting-414:51
rosmaitai wlll postpone looking for new owners to next week14:52
rosmaita#topic open discussion14:52
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:52
*** hongbin has joined #openstack-meeting-414:52
rosmaitastevelle: had a suggestion about dashboards?14:52
*** limao has quit IRC14:52
*** limao has joined #openstack-meeting-414:53
stevellethe glance dashboard should probably include a slice of openstack-manuals related to glance14:53
stevelleI cooked up a query for it last friday I think, I can dig that back out but I would like to see the dashboard folks use updated to include awareness of docs14:53
*** cjloader_ has quit IRC14:54
*** cjloader_ has joined #openstack-meeting-414:54
stevelleany thoughts?14:54
rosmaitastevelle: you mean this dashboard: http://gerrit-dash-creator.readthedocs.io/en/latest/dashboards/dashboard_glance.html14:54
*** nkrinner is now known as nkrinner_afk14:54
stevellerosmaita: pretty sure that's the one, yes14:55
jokke_wasn't that Flavio's gift for us?14:55
rosmaitayes, and i for one have been un-good about using it14:55
stevelleit's the second link in my browser toolbar14:56
stevelledo folks have custom ones?14:56
rosmaita(while we're looking, could someone please take care of https://review.openstack.org/#/c/420038/ ?)14:57
*** lei-zh has joined #openstack-meeting-414:57
alex_bashwhere do these come from: https://review.openstack.org/#/admin/projects/openstack/glance,dashboards ?14:57
rosmaitamy thought is that i agree with stevelle that it would be good to get the docs we are supposed to keep an eye on into this dashboard14:58
rosmaitaalex_bash: i don't know14:58
hemanthm+114:59
rosmaitaok, we are almost out of time ... the ocata postmortem had a split result on whether the priorities emails are worth doing, i will break the tie and continue them14:59
*** sjmc7 has joined #openstack-meeting-414:59
rosmaita30 sec ...14:59
rosmaitaok, thanks everyone!14:59
rosmaita#endmeeting15:00
jokke_thanks all!15:00
*** openstack changes topic to " (Meeting topic: ironic_neutron)"15:00
openstackMeeting ended Thu Mar  9 15:00:01 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-09-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2017/glance.2017-03-09-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2017/glance.2017-03-09-14.00.log.html15:00
*** yingjun has joined #openstack-meeting-415:00
rosmaitasjmc7: all yours15:00
sjmc7merci15:00
*** alex_bash has left #openstack-meeting-415:00
sjmc7#startmeeting15:00
openstacksjmc7: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'15:00
sjmc7#startmeeting openstack search15:00
openstackMeeting started Thu Mar  9 15:00:46 2017 UTC and is due to finish in 60 minutes.  The chair is sjmc7. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
sjmc7haha, good start15:00
sjmc7morning all15:00
*** openstack changes topic to " (Meeting topic: openstack search)"15:00
openstackThe meeting name has been set to 'openstack_search'15:00
rosmaitai wonder how many "marketing committee" meeting logs there are15:01
rosmaitaprobably a lot15:01
sjmc7sounds like a front for a spy agency15:01
*** TravT has joined #openstack-meeting-415:01
yingjuno/15:01
TravTo/15:01
lei-zho/15:01
Kevin_Zheng_Hexo/15:01
sjmc7you have to get up early for the glance one - aren’t you west coast rosmaita ?15:01
sjmc7we’ll get going in one more minute15:03
rosmaitano, virginia15:03
rosmaitaotherwise, i would have moved the meeting time!15:03
sjmc7:)15:03
*** limao_ has joined #openstack-meeting-415:04
sjmc7okey dokey15:04
sjmc7#topic pike open15:04
*** openstack changes topic to "pike open (Meeting topic: openstack search)"15:04
sjmc7Ocata’s now all officially closed15:04
*** armax has joined #openstack-meeting-415:04
*** limao has quit IRC15:04
TravTi noticed that launchpad doesn't have a pike series in it15:05
sjmc7Yeah.. not sure why that is yet15:05
TravTwell, i always created them myself15:05
sjmc7Ah, then that would be why: I’m lazy15:05
TravTincluding ocata15:05
sjmc7So I’ll do that following this15:05
*** alexchadin has quit IRC15:06
rosmaitasounds like TravT volunteered to do it?15:06
TravTnah, i was trying to make sjmc7 feel guilty15:06
sjmc7:)  Mission accomplished! We’ve got a huge laundry list of blueprints at https://blueprints.launchpad.net/searchlightthat needs some curating15:06
TravT;)15:06
*** cjloader_ has quit IRC15:06
*** thorst is now known as thorst_afk15:06
*** stevelle has left #openstack-meeting-415:07
sjmc7Which i’ve also been lazy about. I’m going it curate it a bit today, but if there’s work people want to see in Pike please raise a BP or tag it for Pike15:07
*** cjloader_ has joined #openstack-meeting-415:07
sjmc7We got most of the core stuff in over the last couple of releases so there are fewer big ticket items, which is good15:07
sjmc7The UI could do with some love, and there are some more architectural things in there. I’d definitely like to solidify ES 5 support15:09
sjmc7Dunno if anyone has any ideas for stuff they’d like to add we could discuss?15:09
sjmc7Otherwise mailing list or launchpad is fine15:10
TravTthere was an email this morning from richard15:10
sjmc7Yeah, I was gonna reply to that after this too - I’ll suggest they put that code in horizon which i think was the intent all along15:10
TravTabout moving our registered resource types in the ui into horizon.15:10
TravTyeah, the panel started as a horizon patch15:10
TravTbut since it was following the typical trajectory of taking multiple years to merge there, we broke it into its own panel15:11
*** cjloader_ has quit IRC15:11
TravTbut david-lyle all along said that he thought that was a good way to get code sort of incubated (breaking it out) and then bringing back in when it makes sense15:12
sjmc7ok. this is a good test of that statement :)15:12
sjmc7We’ll need to coordinate a bit so that we don’t duplicate it but that should be fine15:12
TravTyeah, i think it will overall benefit to have some of those resource panels go back into horizon... because we have not had the time to get all the actions finished for some of them.15:13
TravTmoving it into horizon will ironically likely help that now.15:13
sjmc7Yeah. It makes sense generally too, so i don’t think it’s very controversial15:14
sjmc7Ok, if there’s no features/pike things to discuss i’ll move on to the feature/pike thing i wanted to discuss15:14
*** salv-orlando has quit IRC15:14
sjmc7#topic Nova cells15:15
*** openstack changes topic to "Nova cells (Meeting topic: openstack search)"15:15
*** spzala has joined #openstack-meeting-415:15
*** salv-orlando has joined #openstack-meeting-415:15
sjmc7There was a mailing list discussion following the PTG from Matt in Nova - http://lists.openstack.org/pipermail/openstack-dev/2017-February/112996.html15:15
sjmc7They’re serious this release about beginning integration with Searchlight. They have a spec at https://review.openstack.org/441692 and matt’s asked some questions in IRC15:15
TravTyeah, shout out the lei-zh and Kevin_Zheng_Hex for jumping in on that.15:16
sjmc7Yeah, thanks both for that15:16
*** unicell has joined #openstack-meeting-415:16
sjmc7I don’t know if we can exclusively switch to versioned or we’ll have to maintain both; that might be a question for nova, but any changes will only be made to versioned notifications15:16
Kevin_Zheng_Hexturns out many problems occoured15:17
sjmc7Ah.15:17
sjmc7Not entirely unexpected - are there any that’ll require work on searchlight?15:17
*** unicell1 has quit IRC15:17
Kevin_Zheng_Hexnot much, I think the major problem is in Nova15:18
sjmc7Excellent!15:18
sjmc7:)15:18
sjmc7Although i suspect there will be stuff for us later15:18
*** zhubingbing has quit IRC15:18
lei-zhI see Kevin_Zheng_Hex starts to work on a POC15:18
sjmc7I saw the discussion about being able to force list instances to go to the DB15:19
sjmc7Was there anything else?15:19
*** croelandt has left #openstack-meeting-415:19
Kevin_Zheng_Hexwe have to find a way to get trusty data IMO15:19
Kevin_Zheng_Hexotherwise it will be a dead loop15:19
Kevin_Zheng_Hexlei-zh find out this15:20
sjmc7trusty data?15:20
Kevin_Zheng_Hexif we re-sync, nova will call SL15:20
sjmc7Ah, yes15:20
sjmc7My thought was (as i put in the review) if they already need a code path that supports not having searchlight, there should be a flag to force that path15:21
*** yamahata has joined #openstack-meeting-415:21
*** SerenaFeng has quit IRC15:21
*** Kevin_Zheng_Hex_ has joined #openstack-meeting-415:22
sjmc7I don’t know if that makes sense/is possible, but I think it will be necessary not just for initial indexing but for reliability if SL becomes unavailable or needs resyncing/updating15:22
sjmc7Since we’re a secondary data store i would not want nova to be totally reliant on SL15:23
Kevin_Zheng_Hex_oops, disconnected15:23
*** Syed__ has joined #openstack-meeting-415:23
*** yamamoto has joined #openstack-meeting-415:23
Kevin_Zheng_Hex_yeah, according to the current spec, there will be one config to set wheter use SL or not15:24
Kevin_Zheng_Hex_but it will be stop nova -> unset flag -> start nova -> re-sync -> stop nova -> set flag -> start nova15:24
Kevin_Zheng_Hex_very ugly15:24
sjmc7urgh15:24
sjmc7yeah, an API flag seems much more sensible15:24
*** Kevin_Zheng_Hex has quit IRC15:25
Kevin_Zheng_Hex_but seems API sub team don't like it15:25
sjmc7it’s not just at initial openstack deployment we need to sync15:25
sjmc7after major releases we probably will15:25
sjmc7we don’t have the same rolling upgrade capabilities nova does15:25
Kevin_Zheng_Hex_and nova keeps read from it's own DB while listing ... due to its extension mechanism15:26
Kevin_Zheng_Hex_but it's a nova problem15:26
sjmc7Yeah. Anyway, i guess anyone who’s interested keep an eye on that review (https://review.openstack.org/441692)15:27
sjmc7They do seem quite serious about making progress on it15:27
lei-zhyep, if you consider SL as kind of cache for nova DB, a way to refresh at anytime is necessary15:27
sjmc7Our versioned notification BP is at https://blueprints.launchpad.net/searchlight/+spec/nova-versioned-notifications15:27
sjmc7I see Kevin_Zheng has assigned that to himself, but let us know if you need help15:28
sjmc7The ironic plugin uses versioned notifications if you have any trouble getting it set up15:28
*** limao_ has quit IRC15:28
Kevin_Zheng_Hex_ah... I didn't assign it...15:28
sjmc7Hahaha, maybe TravT did in a fit of wishful thinking15:29
lei-zhlol15:29
sjmc7I’ll unassign you for now15:29
*** yamamoto has quit IRC15:29
Kevin_Zheng_Hex_I thought we already adopt versioned noifiation?15:29
sjmc7Not for the nova plugin15:30
lei-zhflavor did?15:30
sjmc7They were still writing them until Ocata15:30
Kevin_Zheng_Hex_flavor versioned notification15:30
sjmc7Ah, yes15:30
lei-zhbut not for instance15:30
Kevin_Zheng_Hex_yeah, thats true15:30
sjmc7Ok, so it may be easy to get set uip15:30
sjmc7The payloads are very different15:30
TravTah, yeah, i did assign kevin.... my bad15:30
Kevin_Zheng_Hex_I don't know I have enough time15:30
Kevin_Zheng_Hex_intergration seems tons of work15:31
Kevin_Zheng_Hex_nova intergration15:31
Kevin_Zheng_Hex_I mean for the versioned notification thing15:32
sjmc7Yeah, it may be. I’ll try to dig out some time to do it15:32
Kevin_Zheng_Hex_But I would help if intergration went smooth :)15:33
Kevin_Zheng_Hex_Just need to figure out the plan and then it might be easier15:33
*** zhubingbing has joined #openstack-meeting-415:34
sjmc7Yep. This cycle’s longer than Ocata so hopefully we’ve got a decent shot at it15:34
lei-zhIs supporting nova delete also on the agenda?15:35
sjmc7The soft delete thing?15:35
lei-zhyep15:35
sjmc7Yeah, that’s a good point.. Apparently nova needs the capability to list “deleted” instances15:35
Kevin_Zheng_Hex_yeah, and there is also soft_delete15:35
Kevin_Zheng_Hex_we should do both15:36
*** Kevin_Zheng_Hex_ has quit IRC15:36
sjmc7Yeah. Historically the problem is that we can add filters to a plugin (“.. AND NOT deleted”) but allowing the user to override it isn’t supported15:36
sjmc7Looking at the code though, it seems like it would be possible to add limited support where we’d look for {“term”: } type query clauses to override default filters like that15:37
sjmc7It wouldn’t apply to RBAC filters, just data ones. This came up with glance a while back for some reason i can’t remember. community images i think15:38
sjmc7I’ll add a blueprint for it15:38
lei-zhyou mean the problem is  for query_string or for all queries15:38
sjmc7yeah, i think we can’t cope with query_string but that’s ok15:39
*** vks1 has joined #openstack-meeting-415:39
*** vks1 has quit IRC15:40
sjmc7if you want to override it, you have to provide a structured query with {“term”: {“deleted”: [true, false]}}15:40
*** vks1 has joined #openstack-meeting-415:40
lei-zhyeah, this seems more complicated than versioned notifications15:41
lei-zhI'm often in trouble fighting with ES queries15:41
sjmc7Yeah, the syntax is a bit overwhelming15:42
*** marst has quit IRC15:42
sjmc7I keep meaning to look to see if they can be simplified a bit15:42
Kevin_Zhengcan we have a easier client?15:43
sjmc7Our client does allow simplified queries15:43
sjmc7We could add a flag for this, although it would be a bit special case15:44
Kevin_ZhengAnd the response looked too nested15:44
sjmc7The hits.[0]._source ?15:45
Kevin_ZhengThat's just what I feel while working on pic15:45
Kevin_ZhengPoc15:45
Kevin_ZhengYeah15:45
Kevin_ZhengBut that no big deal :)15:45
sjmc7Yeah.. I have wondered whether we should have abstracted away from Elasticsearch more15:45
sjmc7There are/were good reasons we did it this way, but can always change15:46
sjmc7Feel free to file BPs or bugs if tehre are things that get in your way15:46
Kevin_ZhengMaybe we could have a param in client15:47
Kevin_ZhengTo choice whether nested result or simple one to return?15:47
sjmc7To transform the result? Yeah15:47
sjmc7That’d be easy to do15:47
Kevin_ZhengGood , I will try tomorrow15:48
sjmc7You’d lose some of the information (like total results, timing)15:48
*** zhubingbing has quit IRC15:48
sjmc7But if all you want is the _source that’s ok15:48
*** zhubingbing has joined #openstack-meeting-415:48
sjmc7Ok, will open it up for a few more minutes15:49
sjmc7#topic open discussion15:49
*** openstack changes topic to "open discussion (Meeting topic: openstack search)"15:49
Kevin_ZhengYeah, feels like do it in nova didn't look nice15:49
*** Julien-z_ has quit IRC15:49
sjmc7Yeah, no objection to making that an option on the client15:49
sjmc7Any more on this issue? Or any others?15:49
Kevin_Zheng:)15:49
*** marst has joined #openstack-meeting-415:49
rosmaitai have a question from out of left field, so i'll wait until we're sure there's no follow-up from the above discussion15:50
sjmc7i’m drooling with anticipatin15:50
rosmaitasounds like one of those new statin drugs15:51
sjmc7hahahaha15:51
sjmc7once there are no more FDA regulations i’ll try marketing it! what was your question?15:51
rosmaitasomeone asked me whether you need keystone to run searchlight, and i said yes because searchlight needs to know your roles so it can expose info appropriately15:51
rosmaitabut nikhil pointed out htat therere's a paste option for noauth15:52
rosmaitaso i was wondering what hte correct answer is15:52
sjmc7you don’t *need* it, but you do need the headers indicating your tenant15:52
sjmc7tenant and/or admin roles15:53
rosmaitaso basically, it's simpler to run with keystone in place15:53
sjmc7so same as any other openstack service15:53
rosmaitagotcha15:53
*** sdague has joined #openstack-meeting-415:53
sjmc7if you handle auth some other way, you can take out keystone15:53
sjmc7but with the noauth middleware you’re saying “anyone can access anything”15:54
sjmc7so you’d need to hide the API behind something15:54
*** cjloader_ has joined #openstack-meeting-415:54
rosmaitaok, thanks15:54
sjmc7i’m somewhat curious now :)15:54
sjmc7our API code is very similar to glance’s since we branched it15:54
*** mjturek has joined #openstack-meeting-415:55
*** cjloader_ has quit IRC15:55
*** iyamahat has joined #openstack-meeting-415:55
rosmaitayeah, it looked pretty familiar15:56
*** cjloader_ has joined #openstack-meeting-415:56
*** mgariepy has joined #openstack-meeting-415:57
sjmc7if he has details on what he wants to do he can come ask15:57
sjmc7ok, gonna call it here. i’ve created the pike series and milestones in launchpad so stuff can be scoped to it15:57
sjmc7thanks everyone!15:57
rosmaitathank you15:57
sjmc7good night/morning/afternoon all15:58
sjmc7#endmeeting15:58
*** openstack changes topic to " (Meeting topic: ironic_neutron)"15:58
openstackMeeting ended Thu Mar  9 15:58:07 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2017/openstack_search.2017-03-09-15.00.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2017/openstack_search.2017-03-09-15.00.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2017/openstack_search.2017-03-09-15.00.log.html15:58
rosmaitasjmc7: i think the question was more along the lines "does searchlight use keystone" more than is "keystone a hard requirement for searchlight"15:58
*** KeithMnemonic has joined #openstack-meeting-415:58
sjmc7ah. then yes :)15:59
*** yingjun has left #openstack-meeting-415:59
mhayden#startmeeting openstack_ansible_meeting16:00
openstackMeeting started Thu Mar  9 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
*** openstack changes topic to " (Meeting topic: openstack_ansible_meeting)"16:00
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:00
mhayden#topic Roll Call16:00
*** sjmc7 has left #openstack-meeting-416:00
*** openstack changes topic to "Roll Call (Meeting topic: openstack_ansible_meeting)"16:00
*** TravT has left #openstack-meeting-416:00
andymccro/16:01
*** lei-zh has quit IRC16:01
andymccrits just me and you major ;)16:02
mgariepyi'm here16:02
mhaydenit is close to spring break in many parts ofthe US16:02
*** mjturek has quit IRC16:02
antonymo/16:02
*** mjturek has joined #openstack-meeting-416:03
evrardjpo/16:03
jmccroryo/16:03
asettleo/16:03
* mhayden will wait til :05 after16:04
evrardjpI still think I should do \o16:04
evrardjpat least it's not o? this time16:04
evrardjpor maybe \o/ because I'm super enthusiastic!16:05
mhayden#topic Review action items16:05
evrardjpit's :0516:05
*** openstack changes topic to "Review action items (Meeting topic: openstack_ansible_meeting)"16:05
mhaydenlooks like we didn't have any16:05
asettleHooray16:05
mhaydenor wait16:06
mhaydenwe need a name for the OSA inventory python package16:06
mhaydenpalendae: any updates there?16:06
palendaemhayden: None yet; I didn't get to sending an email to the mailing list. Last I checked there weren't a ton of votes for anything16:06
palendaeMaybe 1-2 for each name https://etherpad.openstack.org/p/osa-python-package-name16:06
mhaydeni still think openstack-ansible-palendae-inventory-improvement-thing-2017 has a nice ring to it16:07
andymccrhahahahahaha16:07
andymccryeah that is pretty good16:07
mhaydenship it16:07
*** links has joined #openstack-meeting-416:07
palendaeDashes aren't allowed ;)16:07
mhaydenpalendae: could you send a few final candidates to the ML and we can sort it out?16:08
andymccrwith your name on it you'll still be fielding questions for many years to come :P16:08
palendaeAnd I think that goes over the line limit ;)16:08
evrardjppalendae: replace with underscores16:08
asettleosai16:08
asettlereally16:08
asettlewho came up with osai?16:08
*** erikmwil_ has joined #openstack-meeting-416:08
* palendae shrugs16:08
palendaeI proposed none of these fwiw16:08
*** vds has quit IRC16:08
palendaemhayden: Yes, I will try to get that done this week16:08
mhaydenpalendae: woot16:08
mhayden#action palendae to email a list of a few final names to the list for discussion/voting16:08
mhaydenthe other action item was for logan- --> "add ceph_client version bump to development cycle checklist"16:09
logan-o/16:09
logan-still on todo16:09
spotzsorry was trying to catch up on dev list:)16:09
*** galstrom_zzz is now known as galstrom16:09
*** erikmwil_ is now known as erikmwilson16:10
mhaydenhah okay16:11
mhaydenwe'll keep it then16:11
mhayden#action logan- to add ceph_client version bump to development cycle checklist16:11
mhayden#topic Ops Guide - asettle16:11
*** openstack changes topic to "Ops Guide - asettle (Meeting topic: openstack_ansible_meeting)"16:11
* mhayden hands the mic to asettle16:11
asettleNot much!16:12
asettleREviews :)16:12
asettleContent16:12
asettleYou konw the drill hoomans16:12
asettleThose who have signed up for content, add it in16:12
asettleWe have until May16:12
asettleI think that's all mhayden :)16:12
mhaydenasettle: woot!16:13
mhaydennext up is naming the python package -- i think we've covered that16:13
mhaydenmoving along...16:13
mhayden#topic New periodic jobs - odyssey4me16:13
*** openstack changes topic to "New periodic jobs - odyssey4me (Meeting topic: openstack_ansible_meeting)"16:13
* mhayden hands the mic to odyssey4me16:13
odyssey4mehowdy folks16:13
andymccrexcitement inc!16:13
odyssey4meso, we have a periodic upgrade test for xenial which runs once a day16:14
andymccr\o/16:14
odyssey4meit's the first of many periodics planned16:14
odyssey4meI'd like to ask that we try to figure out how we expose the results a little more actively16:14
odyssey4methe results are posted here: http://logs.openstack.org/periodic/16:14
evrardjp#link http://logs.openstack.org/periodic/16:15
odyssey4mewe only have one right now, but once there are more the folder is the job name16:15
mhaydenhttp://logs.openstack.org/periodic/periodic-openstack-ansible-upgrade-aio-master-ubuntu-xenial/16:15
mhaydenodyssey4me: can we get a notification via IRC bot perhaps?16:15
odyssey4meI was thinking maybe that we could add a dev-docs page which shows where they are16:15
odyssey4memhayden not to my knowledge, but I can ask16:15
odyssey4methat's a good idea16:15
odyssey4memake me an action maestro16:16
mhaydenYARLY16:16
odyssey4meI've been bashing in a bunch of fixes to try and make it succeed16:16
mhaydenwe could hack something up, but it wouldn't be as good most likely16:16
odyssey4meideally I'd like to see it exposed in the OpenStack Health Dashboard16:17
mhaydenhttp://status.openstack.org/openstack-health/#/16:17
odyssey4meI've asked cloudnull if he can try and make ARA output subunit streams instead of just junit16:17
* mhayden hasn't looked at this fancy thing in a while16:17
odyssey4menot sure if anyone has some time to sinnk into doing that16:17
odyssey4meour automated upgrade script is a bit of a shambles, to be honest16:18
odyssey4mewe need an overhaul16:18
odyssey4meany volunteers to work with me to work on a conprehensive improvement?16:18
odyssey4me*comprehensive16:18
*** zhubingbing has quit IRC16:18
* odyssey4me looks at logan- and jmccrory 16:19
jmccrorysure16:19
andymccrlogan-: jmccrory when you are finished fighting over who gets to do it :P16:19
evrardjp:D16:19
logan-lol16:19
andymccrvoluntold!16:19
mhaydeninternet just dropped here16:20
mhaydenback now16:20
evrardjpmhayden: we decided that jmccrory would rehaul the upgrade bits16:20
odyssey4meok, logan- and jmccrory I'll setup an etherpad to discuss what we want and break it into pieces16:20
evrardjpyou can help16:20
evrardjplol16:20
logan-ok thanks odyssey4me16:20
mhaydenevrardjp: success!16:20
andymccrbest ever.16:21
odyssey4meno, thank you for volunteering logan- and jmccrory :)16:21
* mhayden goes and orders upgrade fixes for pickup at walmart16:21
mhaydenokay, are we good on this topic ?16:21
odyssey4meright, but back to the periodics16:21
odyssey4meare there any other tests we want to add to the list of periodics?16:21
andymccrodyssey4me: telemetry is the obvious one right now (since we removed it from the integrated build)16:22
odyssey4meI was thinking of backporting the upgrade test to Newton->Ocata as well to prevent further bitrot16:22
odyssey4mealso Ironic16:22
odyssey4mePErhaps some sort of scenario that involves Magnum, Sahara16:22
andymccryeah ironic. smh - i need to try find some time. because this: https://review.openstack.org/#/c/392959/ is now passing so we should be able to reverse engineer that into our ironic gates16:23
odyssey4meok, once the upgrade test is working I'll troll for ideas in channel16:24
odyssey4meI think we're good here.16:24
andymccrboom - and thanks for the work, its awesome to see the upgrade test up and running (and almost passing)16:24
logan-+116:24
andymccrspeaking of - i will be fixing up our in role upgrade tests and making them voting16:25
odyssey4meyeah, there are a bunch of tests that should be promoted16:25
odyssey4meotherwise patches merge which break them16:25
andymccryeah basically16:25
odyssey4methe ceph AIO job should be made voting IMO16:25
andymccrcurrently i think neutron/nova are broken the others are mostly working so going to get that set up16:25
odyssey4methe xenial one I mean16:25
andymccryeah happy with that too16:25
*** yamamoto has joined #openstack-meeting-416:26
andymccrok i think we're good to move on mhayden!16:26
mhaydenwoot16:26
mhayden#topic Release planning and decisions - andymccr16:27
*** openstack changes topic to "Release planning and decisions - andymccr (Meeting topic: openstack_ansible_meeting)"16:27
* mhayden hands it to andymccr16:27
andymccrahh yeah16:27
andymccrso16:27
andymccrdrum roll16:27
andymccrOcata 15.0.0 was released this week!16:27
mhaydenWOOT16:28
andymccri know, i know.16:28
mhayden#success OpenStack-Ansible 15.0.0 Ocata released this week16:28
andymccrbut genuinely, thanks for all the work during the cycle - aside from the rc1 hiccups it really was pretty smooth (and those werent necessarily our messups)16:28
andymccrso onward and upward to Pike!16:28
odyssey4megratz andymccr - it's looking pretty good, we fixed up a lot of upgrade things and should be doing plenty more16:28
evrardjpthanks andymccr16:29
andymccrNewton/Mitaka are being released as usual, so next week will be another released, I'll SHA bump for Ocata but only do a release 15.0.1 2 weeks after (so we can keep them all released at the same cadence)16:29
evrardjp "give back to caesar what belongs to caesar"16:29
* mhayden wants a caesar salad16:30
andymccrahhaha16:30
andymccryeah that!16:30
evrardjpgive that back!16:30
*** yamamoto has quit IRC16:30
andymccrthere are a few critical bugs up still, the keystone one and a high one around mysql upgrades  - so we still have some bits to do16:30
andymccrthat's all i got on releases!16:31
asettle\o/16:31
*** BjoernT has joined #openstack-meeting-416:32
andymccrmhayden: next!16:32
mhayden#topic Blueprints16:32
*** openstack changes topic to "Blueprints (Meeting topic: openstack_ansible_meeting)"16:32
mhaydenxgerman: want to give us a brief on octavia?16:33
xgermansure16:33
xgermanOctavia is an operator grade load balancer… and I put together some playbooks to install it16:34
xgermanthe main advantage is that it is HA as opposed to the previous one which didn;t have redundancy16:34
xgermanI set it up that if Octavia isinstalled Neutron will make it the default load balancer in the system16:35
mhaydennice -- what do you need from us to finish up the work?16:35
xgermanthe missing two patches merged16:35
xgerman#link https://review.openstack.org/#/c/428979/16:36
xgerman#link #link https://review.openstack.org/#/c/422062/1316:36
xgermanthe lat one has some jenkins problem I don't understand16:37
xgermanOnce I have it running on. a multnode cluster I will write up some installation guide16:37
mhaydenthat will be great -- docs on octavia are a little sparse ;)16:37
xgermanit’s a major push for the Octavia team this cycle16:38
asettlexgerman: feel free to tag me in the review, happy to watch your docs :)16:38
asettle'watch' sigh16:38
asettleReview them16:38
xgermanthx16:38
*** Rockyg has joined #openstack-meeting-416:38
xgermanalso I am planning to keep up with the milestone releases16:38
mhaydenxgerman: looks like tempest is angry in the gate16:38
odyssey4mexgerman getting reviews for those is a bit hard because not many people understand networking well enough to review properly16:38
mhaydenhttp://logs.openstack.org/62/422062/13/check/gate-openstack-ansible-openstack-ansible-aio-ubuntu-xenial/9d149ab/console.html#_2017-03-09_15_13_14_90054316:38
xgermanyep16:38
*** thorst_afk is now known as thorst16:38
xgermanbut I couldn;t see why16:38
xgermanthat formatting is crazy16:39
mhaydeni can try to build an AIO from that patch later and see what's happening16:39
odyssey4mexgerman does it work if you test locally?16:39
odyssey4meBinding failed for port 52dd82ba-6e57-45c0-9ae5-bbe3cfe13682, please check neutron logs for more information.16:39
xgermanmmh16:40
xgermanI will run it locally and see if I have more luck16:40
*** efoley_ has joined #openstack-meeting-416:41
xgermanalso do you need Octavia backported to Ocata?16:41
andymccrxgerman: we wouldn't backport a feature16:42
xgermanok, that’s what I thought16:42
odyssey4mea major feature16:42
andymccrsi si :)16:42
odyssey4meespecially with such a small user/dev base16:44
odyssey4meit also is entirely unproven - we need to grow a user base and hopefully pick up more than one maintainer for the role16:44
*** efoley has quit IRC16:44
andymccryeah ideally - that'll happen with time though, so its not really a stress16:45
*** Rockyg has quit IRC16:45
jmccrorythere's interest where i work, i'm pushing to get them to test the patches out there for review now instead of the manual install they've been doing16:45
andymccrjmccrory: sounds awesome16:46
xgerman+116:46
*** spzala has quit IRC16:46
*** uck has joined #openstack-meeting-416:46
andymccrexcellent :)16:46
xgermanI also have some interest from other people in the community - once it works it could be quite popular16:46
odyssey4meexcellent, if we can get more than one org maintaining it then we can encourage its use16:47
odyssey4meit can mature a bit and release in pike properly16:47
mhaydenwoot!16:47
andymccryeah agreed16:47
mhaydensuch collaboration, much happy16:47
xgermanyeah, it’s in early…16:47
evrardjp"once it works" doesn't sound motivating16:47
mhaydenthe glass is half-full, darnit!16:47
*** psachin has quit IRC16:48
xgermanyeah, my installations work but I haven’t tried with everything merged properly16:48
mhaydenin other news, cloudnull and i have been working on the monitoring plugin PoC as part of the monitoring spec16:48
andymccrahh yeah16:48
mhaydenhttps://github.com/major/monitorstack16:48
andymccrawesome16:48
evrardjpmhayden: glass is always full!16:48
mhaydentest coverage is increasing and it's easily buildable in pypi16:48
mhaydeni'd like to bring it under the openstack namespace at some point16:49
andymccrmhayden: yeah i like that idea16:49
mhaydeni've been talking to mrhillsman about that16:49
mhaydenhe said the ops folks would be interested16:49
*** vks1_ has joined #openstack-meeting-416:49
*** vks1 has quit IRC16:50
mhaydenwould it make sense to have it under openstack-ansible's responsibility for a bit until it finds a forever home?16:50
andymccrmhayden: would end goal to test it using OSA (and perhaps vice-versa?)16:50
mhaydenandymccr: yeah16:50
andymccrmhayden: yeah im happy with that16:50
andymccrnot sure if there are any objections16:50
andymccrthe aim would be to have it be generic16:50
andymccrbut we are maintaining it for now, similar to the security role16:50
mhaydeni just called it monitorstack because i couldn't find anything big in Google for that16:50
andymccrmhayden: in OpenStack-Ansible we have a rich tradition of inventing smart and fanciful names - i expect you to uphold that tradition16:51
*** jovon has joined #openstack-meeting-416:52
odyssey4meI'd just suggest that we don't prefix the repo name with openstack-ansible16:52
odyssey4meIt'll need to be a more universal name.16:52
mhaydenhah16:52
odyssey4mePerhaps it should be its own project name, but we curate it initially.16:52
mhaydenodyssey4me: current name is 'monitorstack'16:52
andymccri dont mind either way - if its more work to create a separate project now, then happy to just include it in the openstack-ansible namespace for now16:53
*** vks1__ has joined #openstack-meeting-416:53
mhaydenokay, we can talk on that one later in the channel16:54
mhayden#topic Open floor16:54
*** openstack changes topic to "Open floor (Meeting topic: openstack_ansible_meeting)"16:54
mhaydenanything else?16:54
andymccrall good from my side16:54
*** vks1_ has quit IRC16:54
odyssey4memhayden andymccr I'm suggesting that it just be another repo in our deliverables, but not with our prefix16:54
andymccrahh that works16:55
mhaydenodyssey4me: totally agreed16:55
andymccragreement has been reached!16:55
odyssey4metherefore it can move out of our deliverables at another time without the hassle of renaming the repo16:55
mhaydenwoot16:55
mhaydenokay, i'll close this meeting up16:55
odyssey4meit could possibly actually fit under the oslo umbrella, but let's not even try16:55
mhaydenthanks everyone! :)16:55
mhayden#endmeeting16:56
*** openstack changes topic to " (Meeting topic: ironic_neutron)"16:56
openstackMeeting ended Thu Mar  9 16:56:01 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2017/openstack_ansible_meeting.2017-03-09-16.00.html16:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2017/openstack_ansible_meeting.2017-03-09-16.00.txt16:56
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2017/openstack_ansible_meeting.2017-03-09-16.00.log.html16:56
*** vks1__ has quit IRC16:56
*** efoley__ has joined #openstack-meeting-416:56
*** vks1 has joined #openstack-meeting-416:56
*** mgariepy has left #openstack-meeting-416:56
*** doonhammer has joined #openstack-meeting-416:57
*** LouisF has joined #openstack-meeting-416:58
*** efoley_ has quit IRC16:59
LouisF#startmeeting service_chaining17:00
*** FrankZhang has quit IRC17:00
openstackMeeting started Thu Mar  9 17:00:54 2017 UTC and is due to finish in 60 minutes.  The chair is LouisF. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: service_chaining)"17:01
openstackThe meeting name has been set to 'service_chaining'17:01
pcarverhi17:01
vks1hi17:01
igordcard hi pcarver LouisF vks117:01
LouisFhi all17:01
doonhammerHi17:01
igordcardhi doonhammer17:01
*** galstrom is now known as galstrom_zzz17:02
vks1hi igordcard17:02
*** FrankZhang has joined #openstack-meeting-417:02
LouisF#topic agenda17:02
*** openstack changes topic to "agenda (Meeting topic: service_chaining)"17:02
LouisFhttps://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting#Agenda_for_the_Networking-SFC_Meeting_.283.2F9.2F2017.2917:02
LouisF#topic release compliance17:02
*** salmankhan has joined #openstack-meeting-417:02
*** openstack changes topic to "release compliance (Meeting topic: service_chaining)"17:02
*** galstrom_zzz is now known as galstrom17:03
LouisFCLI in python-neutronclient https://review.openstack.org/#/c/409759/17:03
LouisFstill in review with comments17:03
LouisFmohan may call in later17:03
LouisFAPI reference https://review.openstack.org/#/c/389385 https://review.openstack.org/#/c/411409/17:04
LouisFpcarver: thanks for the new patch17:04
LouisFall please review17:05
igordcardpcarver: very very close, just 2 tiny comments to fix17:05
pcarverigordcard: sure, I just need to fit it in between meetings17:05
igordcardor descriptions17:06
*** vks1 has quit IRC17:06
LouisFlets shoot to get this done by eow17:06
pcarverone question though, if mpls is the only valid value, why even have the parameter?17:07
pcarverI thought we allowed None17:07
*** sshnaidm is now known as sshnaidm|afk17:07
igordcardpcarver: to focus only on the future... it will support nsh too17:07
pcarverok17:07
LouisFin pike?17:08
LouisFwill support nsh soon17:08
igordcardLouisF: I'm aiming at Pike yes17:08
*** markvoelker has joined #openstack-meeting-417:08
LouisF#topic stable/ocata17:09
*** openstack changes topic to "stable/ocata (Meeting topic: service_chaining)"17:09
*** mak_ has joined #openstack-meeting-417:09
*** vks1 has joined #openstack-meeting-417:09
LouisFpulled stable/ocata so master branch work is for pike release17:09
*** mak_ is now known as Guest2133717:09
vks1sry got disconnecte17:09
LouisF#topic pike work17:10
*** openstack changes topic to "pike work (Meeting topic: service_chaining)"17:10
LouisFseveral items: Tap/bitw SF, SFC graph, NSH dataplane, OVN driver17:10
LouisFigordcard: how is sfc graph progressing?17:11
igordcardLouisF: I have temporarily switched to other work but am now getting back to sfc graphs17:11
igordcardI'm aiming at pike-1 for sfc graphs and pike-3 for nsh17:11
*** hieulq has quit IRC17:12
igordcardand if I may, just a heads-up regarding the Pike cycle and networking-sfc:17:12
igordcard#link https://review.openstack.org/#/c/437699/17:12
igordcard#link https://releases.openstack.org/pike/schedule.html17:12
vks1igordcard, thats gud :)17:12
LouisFyes need to keep pike milestones in mind17:13
LouisFdoonhammer: what is status of sfc work in OVN?17:14
*** hieulq has joined #openstack-meeting-417:15
doonhammerGoing to submit another patch set to ovs/ovn next week - got detoured by some other work issues17:15
doonhammerjust need to do some more polish and documentation17:16
LouisFdoonhammer: you had a question about the ovn matching?17:16
doonhammeronce ovs/ovn approves it we can add the networking-ovn layer17:16
LouisFis the ovn classifier to be used?17:16
*** matrohon has quit IRC17:17
LouisFdoonhammer: yes17:17
doonhammerI think I have an approach - yes the ovn classifier can be used optionally17:17
*** l4yerffeJ_ has quit IRC17:17
LouisFwill that be in the next patch?17:18
*** l4yerffeJ_ has joined #openstack-meeting-417:18
igordcarddoes using the ovn classifier change the way we use networking-sfc's API in any way?17:18
doonhammerhopefully a complete solution - but I will still need to add test cases - I have standalone tests but not integrated into the ovs/ovn framework - that will be the hardest task for me17:19
LouisFigordcard: should not17:19
doonhammerI do not think so17:19
doonhammerI tried to make sure it did not17:19
LouisFi favor the ovn classifier as is very rich in matching conditions17:20
doonhammerit works well when you have uni-directional flows but can break in bi-direction flows - e.g. matching on port number etc.17:20
*** vks1 has quit IRC17:21
LouisFdoonhammer: ok17:22
LouisFwill look at the patch17:22
doonhammerthanks17:23
igordcarddoonhammer: where is the nsfc-side patch?17:23
igordcarddoonhammer: or even neutron-side17:23
doonhammerigordcard: not there yet - I have an old version in my git repo https://github.com/doonhammer/networking-ovn17:24
doonhammerbut it uses an old version of ovs/ovn patch17:25
igordcarddoonhammer: thank you17:25
LouisF#topic insertion-mode17:25
*** openstack changes topic to "insertion-mode (Meeting topic: service_chaining)"17:25
LouisFfrom discussion in previous meeting need for tap to a passive SF17:26
*** yamamoto has joined #openstack-meeting-417:26
LouisFadded tap sfc spec https://review.openstack.org/#/c/44219517:27
LouisFthis adds an insertion-mode field to port-pair-group-parameters17:28
LouisFif insertion-mode = tap then data-plane will duplicate packet: send one copy to ingress port of SF and other copy to ingress port of next downstream SF17:29
*** unicell has quit IRC17:29
igordcardhmm now that I think about it.. there should be a default value (different from "tap")17:30
LouisFinsertion-mode is applied to all SFs (port-pairs) in ppg17:30
*** vks1 has joined #openstack-meeting-417:30
LouisFvks1: welcome back - discussing sf tap in port-chain17:30
LouisFigordcard: such as?17:31
vks1LouisF, bad network17:31
LouisFvks1: discussing tap sfc spec https://review.openstack.org/#/c/44219517:31
igordcardLouisF: probably "l3"17:31
vks1LouisF, ok17:31
igordcardLouisF: I'm leaving the same comment there now, and we can continue17:32
*** yamamoto has quit IRC17:32
LouisFigordcard: yes that can be default17:32
LouisFvks1: did you add the "vikash" comments?17:33
vks1LouisF, are we considering possibility of SF to be placed in different network of src and dest ?17:33
LouisFvks1: do mean different subnets?17:34
vks1LouisF, yeah more suitably different network17:35
LouisFvks1: currently do not support cross-subnet steering17:35
igordcardvks1: I thought you were vikash, are you not?17:36
vks1LouisF, yeah thats true, but in term of deployment TAPs are placed on different nw than src & dest. we can discuss after we finish what we have now17:38
vks1igordcard, yeah i am vikash :)17:38
Guest21337LouisF, how about copying all packets going into a port - ingress traffic ? In such a case LSP in FC will be * (ANY)17:38
LouisFvks1: you had comment on L5517:39
vks1LouisF, yeah17:39
LouisFvks1: do you mean that Port Chains can be made of TAP-insertion-mode PPGs only?17:40
vks1LouisF, i guess igordcard also felt the same17:40
LouisFright - the answer is yes17:40
vks1LouisF, then thats fine17:41
LouisFvks1: ok i will add text to clarify17:41
vks1LouisF, thats fine17:42
vks1LouisF, i thought we could have extended the scope of BP17:42
vks1igordcard, what do u say ?17:42
igordcardvks1: what is the scope in that context?17:42
LouisFvks1: i would like to bound the scope of this bp17:43
LouisFand not mix functionality17:43
vks1LouisF, i was feeling so :)17:43
*** bogdando has quit IRC17:43
LouisFvks1: what other functionality are you considering?17:44
vks1igordcard, to address other insertion mode also like L217:44
vks1LouisF, and keep open the scope for hetrogenous chain17:44
LouisFvks1: ok we can create a separate bp to address that17:44
vks1LouisF, OK that would be fine17:44
LouisFvks1: we can add another bp to address l2 insertion-mode17:45
*** Guest21337 has quit IRC17:45
vks1igordcard, do you see any further addition in existing BP ?17:46
igordcardvks1: right it's the same scope I had in mind... but I realized it's better to go type by type, better-sized blocks of effort17:46
LouisFvks1: regarding l2 insertion-mode: what is the behavior of the l2 SF?17:46
vks1igordcard, it would act as forwarder17:47
igordcardthe L2 insertion mode would also be a great addition, you could easily spin a VM with promiscuous interfaces and OVS inside17:47
vks1cand can be dropped transparently anywhere in network17:47
*** KeithMnemonic has quit IRC17:47
LouisFigordcard: agree - make review and merging easier17:47
vks1igordcard, yeah :)17:47
*** mattmceuen has joined #openstack-meeting-417:48
vks1LouisF, can we start on TAP ?17:48
vks1igordcard, LouisF we will keep talking on this L2 mode also17:48
vks1igordcard, as i also feel going type by type would be fine17:49
LouisFvks1: agree let get tap work started and discuss l2 work17:49
igordcardvks1 LouisF, I'd say file LP rfe again?17:49
LouisFigordcard: that is fine17:50
vks1vks1, yeah that should be fine17:50
vks1igordcard, sorry i missed *LP ??17:50
igordcardvks1: sorry LaunchPad17:51
igordcardvks1: Launcha17:51
igordcardLaunchpad*17:51
vks1igordcard, ok17:51
LouisFok i will update the patch17:51
LouisF#topic other items17:52
*** openstack changes topic to "other items (Meeting topic: service_chaining)"17:52
vks1igordcard, do you want any change in existing RFE except our comments getting addressed ??17:52
igordcardvks1: nope, it looks pretty good to me besides the comments17:53
vks1igordcard, :)17:53
igordcardvks1: maybe only clarify that the spec is both about 1) bringing insertion types and 2) supporting the "tap" insertion type and maybe the 3) default insertion type17:54
vks1igordcard, yeah i agree17:54
LouisFigordcard: will add that17:54
igordcardthen the next spec will solely be about supporting the "l2" insertion type17:54
LouisFigordcard: yes17:54
vks1igordcard, yeah17:54
LouisFthanks all on the ocata work17:55
igordcard#link https://docs.openstack.org/releasenotes/networking-sfc/ocata.html17:56
LouisFigordcard: thanks17:56
vks1igordcard, are we doing backporting or not ?17:56
vks1at least bugs ?17:57
vks1sry bugfixes ?17:57
igordcardvks1: those bugfixes are almost like small features so I don't expect so.. LouisF?17:57
LouisFnot unless that are critical17:58
vks1ok17:58
*** doonhammer has quit IRC17:59
LouisFbye all17:59
LouisF#endmeeting17:59
*** openstack changes topic to " (Meeting topic: ironic_neutron)"18:00
openstackMeeting ended Thu Mar  9 17:59:59 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
igordcardbye all18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-03-09-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-03-09-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-03-09-17.00.log.html18:00
*** annak has joined #openstack-meeting-418:00
vks1LouisF, pinging u18:00
*** ralonsoh has quit IRC18:01
*** pbourke has quit IRC18:03
*** julim has quit IRC18:03
*** links has quit IRC18:04
*** SumitNaiksatam has joined #openstack-meeting-418:05
*** doonhammer has joined #openstack-meeting-418:06
*** doonhammer has left #openstack-meeting-418:06
*** ltomasbo is now known as ltomasbo|away18:11
*** julim has joined #openstack-meeting-418:11
*** efoley__ has quit IRC18:12
*** unicell has joined #openstack-meeting-418:15
*** yamamoto has joined #openstack-meeting-418:28
*** yamamoto has quit IRC18:33
*** vks1 has quit IRC18:34
*** armax has quit IRC18:38
*** BjoernT has quit IRC18:40
*** LouisF has quit IRC18:41
*** iyamahat has quit IRC18:41
*** yamahata has quit IRC18:42
*** dharinic is now known as dharinic|lunch18:43
*** rwallner has quit IRC18:47
*** sambetts is now known as sambetts|afk18:52
*** BjoernT has joined #openstack-meeting-418:53
*** s3wong has joined #openstack-meeting-418:57
*** galstrom is now known as galstrom_zzz19:08
*** salmankhan has quit IRC19:13
*** david-lyle has quit IRC19:14
*** armax has joined #openstack-meeting-419:16
*** SumitNaiksatam has quit IRC19:19
*** salv-orl_ has joined #openstack-meeting-419:22
*** salv-orlando has quit IRC19:25
*** sdague has quit IRC19:26
*** sdague has joined #openstack-meeting-419:28
*** alij has joined #openstack-meeting-419:29
*** yamamoto has joined #openstack-meeting-419:30
*** rwallner has joined #openstack-meeting-419:31
*** sneti_ has joined #openstack-meeting-419:33
*** yamamoto has quit IRC19:35
*** dharinic|lunch is now known as dharinic19:36
*** salv-orl_ has quit IRC19:37
*** salv-orlando has joined #openstack-meeting-419:38
*** iyamahat has joined #openstack-meeting-419:51
*** alij has quit IRC19:52
*** david-lyle has joined #openstack-meeting-419:53
*** rockyg has joined #openstack-meeting-419:58
*** vishnoianil has quit IRC19:59
*** salv-orlando has quit IRC20:08
*** yamahata has joined #openstack-meeting-420:09
*** salmankhan has joined #openstack-meeting-420:28
*** dave-mccowan has quit IRC20:30
*** yamamoto has joined #openstack-meeting-420:31
*** salmankhan has quit IRC20:33
*** yamamoto has quit IRC20:35
*** rockyg has quit IRC20:41
*** sdague has quit IRC20:41
*** dave-mccowan has joined #openstack-meeting-420:45
*** dave-mcc_ has joined #openstack-meeting-420:47
*** uck has quit IRC20:47
*** rbak has quit IRC20:48
*** dave-mccowan has quit IRC20:50
*** rfolco has quit IRC21:00
*** rwallner has quit IRC21:00
*** vishnoianil has joined #openstack-meeting-421:01
*** erikmwilson has quit IRC21:02
*** erikmwilson has joined #openstack-meeting-421:03
*** rwallner has joined #openstack-meeting-421:03
*** rwallner has quit IRC21:08
*** salv-orlando has joined #openstack-meeting-421:09
*** mjturek1 has joined #openstack-meeting-421:14
*** mjturek has quit IRC21:14
*** uck has joined #openstack-meeting-421:18
*** yfauser has joined #openstack-meeting-421:23
*** yamamoto has joined #openstack-meeting-421:32
*** l4yerffeJ has joined #openstack-meeting-421:34
*** l4yerffeJ_ has quit IRC21:34
*** ediardo has joined #openstack-meeting-421:34
*** Jeffrey4l_ has quit IRC21:35
*** Jeffrey4l_ has joined #openstack-meeting-421:35
*** dave-mcc_ has quit IRC21:36
*** yamamoto has quit IRC21:38
*** krtaylor has quit IRC21:42
*** erikmwilson has quit IRC21:44
*** dave-mccowan has joined #openstack-meeting-421:45
*** erikmwilson has joined #openstack-meeting-421:47
*** markmcclain has joined #openstack-meeting-421:49
*** julim has quit IRC21:50
*** mjturek1 has quit IRC21:51
*** jose-phi_ has joined #openstack-meeting-421:51
*** mjturek has joined #openstack-meeting-421:51
*** jose-phillips has quit IRC21:52
*** sneti_ has quit IRC21:57
*** rfolco has joined #openstack-meeting-422:08
*** rfolco has quit IRC22:08
*** cleong has quit IRC22:13
*** erikmwilson has quit IRC22:14
*** jose-phi_ has quit IRC22:14
*** rwallner has joined #openstack-meeting-422:16
*** erikmwilson has joined #openstack-meeting-422:17
*** jose-phillips has joined #openstack-meeting-422:20
*** yfauser has quit IRC22:20
*** rwallner has quit IRC22:21
*** yfauser has joined #openstack-meeting-422:34
*** salmankhan has joined #openstack-meeting-422:35
*** thorst has quit IRC22:39
*** yfauser has quit IRC22:39
*** yfauser has joined #openstack-meeting-422:43
*** yfauser has quit IRC22:48
*** galstrom_zzz is now known as galstrom22:48
*** BjoernT has quit IRC22:53
*** iyamahat has quit IRC23:01
*** thorst has joined #openstack-meeting-423:03
*** iyamahat has joined #openstack-meeting-423:03
*** armax has quit IRC23:04
*** Syed__ has quit IRC23:05
*** thorst has quit IRC23:07
*** marok has joined #openstack-meeting-423:15
maroki am facing issue with floating ips23:16
marokpublic floating ips not working23:16
*** baoli has quit IRC23:20
*** baoli has joined #openstack-meeting-423:21
*** baoli has quit IRC23:26
*** yamamoto_ has joined #openstack-meeting-423:35
*** rromans has left #openstack-meeting-423:36
*** marst has quit IRC23:37
*** marst has joined #openstack-meeting-423:37
*** klamath has quit IRC23:37
*** galstrom is now known as galstrom_zzz23:40
*** yamamoto_ has quit IRC23:40
*** dave-mccowan has quit IRC23:43
*** emagana has quit IRC23:46
*** cjloade__ has joined #openstack-meeting-423:48
*** salmankhan has quit IRC23:49
*** cjloader_ has quit IRC23:51
*** cjloade__ has quit IRC23:53

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