Wednesday, 2016-02-03

*** pmesserli has quit IRC00:01
*** Sukhdev has quit IRC00:09
*** Sukhdev has joined #openstack-meeting-400:10
*** Guest80711 is now known as med_00:15
*** med_ has quit IRC00:15
*** med_ has joined #openstack-meeting-400:15
*** DuanKebo_ has joined #openstack-meeting-400:20
*** uck has joined #openstack-meeting-400:23
*** yamamoto_ has joined #openstack-meeting-400:24
*** sdake has joined #openstack-meeting-400:27
*** uck has quit IRC00:28
*** yamamoto_ has quit IRC00:30
*** yamamoto_ has joined #openstack-meeting-400:30
*** spzala has quit IRC00:32
*** spzala has joined #openstack-meeting-400:32
*** jed56 has quit IRC00:33
*** Abhijith has quit IRC00:34
*** yamamot__ has joined #openstack-meeting-400:34
*** yamamoto_ has quit IRC00:34
*** IlyaG has joined #openstack-meeting-400:35
*** spzala has quit IRC00:36
*** banix has joined #openstack-meeting-400:37
*** IlyaG has quit IRC00:37
*** DuanKebo_ has quit IRC00:37
*** bobh has joined #openstack-meeting-400:38
*** DuanKebo_ has joined #openstack-meeting-400:42
*** banix has quit IRC00:43
*** DuanKebo_ has quit IRC00:43
*** yamamot__ has quit IRC00:46
*** bpokorny_ has quit IRC00:50
*** bpokorny has joined #openstack-meeting-400:51
*** spotz is now known as spotz_zzz01:00
*** bobh has quit IRC01:00
*** baigk has joined #openstack-meeting-401:00
*** SumitNaiksatam has quit IRC01:02
*** harshs has quit IRC01:02
*** ninag has quit IRC01:12
*** Swami_ has quit IRC01:12
*** fnaval has quit IRC01:13
*** minwang2 has quit IRC01:14
*** IlyaG has joined #openstack-meeting-401:18
*** gongysh has joined #openstack-meeting-401:22
*** bobh has joined #openstack-meeting-401:22
*** sridhar_ram has quit IRC01:26
*** spzala has joined #openstack-meeting-401:26
*** SimonChung has quit IRC01:30
*** Sukhdev has quit IRC01:39
*** baoli has joined #openstack-meeting-401:42
*** baoli has quit IRC01:43
*** SumitNaiksatam has joined #openstack-meeting-401:44
*** iyamahat has quit IRC01:52
*** avarner has quit IRC01:54
*** kebray has joined #openstack-meeting-401:59
*** lazy_prince has joined #openstack-meeting-401:59
*** kebray has quit IRC02:03
*** kebray has joined #openstack-meeting-402:04
*** sdake has quit IRC02:05
*** baohua has joined #openstack-meeting-402:05
*** banix has joined #openstack-meeting-402:06
*** salv-orl_ has joined #openstack-meeting-402:09
*** bpokorny has quit IRC02:11
*** salv-orlando has quit IRC02:12
*** zhurong has joined #openstack-meeting-402:21
*** acabot_ has quit IRC02:21
*** Jeffrey4l has joined #openstack-meeting-402:22
*** amotoki has joined #openstack-meeting-402:24
*** fnaval has joined #openstack-meeting-402:29
*** angdraug has quit IRC02:32
*** dims_ has quit IRC02:40
*** Jeffrey4l has quit IRC02:42
*** FallenPegasus has joined #openstack-meeting-402:43
*** yamamoto has joined #openstack-meeting-402:46
*** dkushwaha has quit IRC02:47
*** yamamoto has quit IRC02:49
*** daneyon_ has joined #openstack-meeting-402:51
*** daneyon has quit IRC02:54
*** harshs has joined #openstack-meeting-402:57
*** harshs has quit IRC02:59
*** s3wong has quit IRC03:04
*** sdake has joined #openstack-meeting-403:06
*** fnaval_ has joined #openstack-meeting-403:09
*** lazy_prince has quit IRC03:11
*** fnaval has quit IRC03:12
*** banix has quit IRC03:17
*** yamamoto has joined #openstack-meeting-403:34
*** prashantD has quit IRC03:38
*** bobh has quit IRC03:44
*** unicell1 has quit IRC03:46
*** deva_ has joined #openstack-meeting-403:47
*** dkushwaha has joined #openstack-meeting-403:52
*** deva_ has quit IRC03:53
*** tfukushima has joined #openstack-meeting-403:54
*** gongysh has quit IRC04:00
*** FallenPegasus has quit IRC04:00
*** irenab_ has joined #openstack-meeting-404:09
*** sdake has quit IRC04:10
*** irenab has quit IRC04:11
*** irenab_ is now known as irenab04:11
*** spzala has quit IRC04:14
*** spzala has joined #openstack-meeting-404:15
*** tfukushima has quit IRC04:18
*** spzala has quit IRC04:19
*** SimonChung has joined #openstack-meeting-404:23
*** xingchao has joined #openstack-meeting-404:34
*** vishwanathj has joined #openstack-meeting-404:37
*** vishwanathj has quit IRC04:37
*** harshs has joined #openstack-meeting-404:39
*** xingchao has quit IRC04:40
*** FallenPegasus has joined #openstack-meeting-404:41
*** SimonChung1 has joined #openstack-meeting-404:48
*** fnaval_ has quit IRC04:50
*** SimonChung has quit IRC04:52
*** fnaval has joined #openstack-meeting-404:54
*** fnaval has quit IRC04:54
*** fnaval has joined #openstack-meeting-404:54
*** amotoki has quit IRC04:57
*** tfukushima has joined #openstack-meeting-405:02
*** spzala has joined #openstack-meeting-405:15
*** amotoki has joined #openstack-meeting-405:18
*** FallenPegasus has quit IRC05:18
*** spzala has quit IRC05:21
*** Sukhdev has joined #openstack-meeting-405:23
*** amotoki_ has joined #openstack-meeting-405:30
*** amotoki has quit IRC05:33
*** harshs has quit IRC05:35
*** minwang2 has joined #openstack-meeting-405:39
*** nkrinner has joined #openstack-meeting-405:50
*** javeriak has joined #openstack-meeting-405:51
*** amotoki_ has quit IRC05:52
*** emagana has quit IRC05:52
*** minwang2 has quit IRC05:53
*** minwang2 has joined #openstack-meeting-405:56
*** SumitNaiksatam has quit IRC05:57
*** SumitNaiksatam has joined #openstack-meeting-405:57
*** Jeffrey4l has joined #openstack-meeting-406:02
*** javeriak has quit IRC06:02
*** javeriak has joined #openstack-meeting-406:02
*** amotoki has joined #openstack-meeting-406:05
*** harshs has joined #openstack-meeting-406:06
*** armax_ has joined #openstack-meeting-406:11
*** unicell has joined #openstack-meeting-406:11
*** armax has quit IRC06:12
*** armax_ is now known as armax06:12
*** minwang2 has quit IRC06:15
*** FallenPegasus has joined #openstack-meeting-406:17
*** minwang2 has joined #openstack-meeting-406:17
*** spzala has joined #openstack-meeting-406:18
*** amotoki has quit IRC06:18
*** FallenPegasus has quit IRC06:22
*** spzala has quit IRC06:23
*** SumitNaiksatam has quit IRC06:24
*** amotoki has joined #openstack-meeting-406:26
*** numan_ has joined #openstack-meeting-406:27
*** SumitNaiksatam has joined #openstack-meeting-406:28
*** hdaniel has joined #openstack-meeting-406:35
*** numan_ has quit IRC06:45
*** numans has joined #openstack-meeting-406:46
*** amotoki has quit IRC06:46
*** armax has quit IRC06:52
*** amotoki has joined #openstack-meeting-407:06
*** harshs has quit IRC07:07
*** javeriak has quit IRC07:09
*** cemmason has joined #openstack-meeting-407:11
*** javeriak has joined #openstack-meeting-407:11
*** paul-carlton1 has joined #openstack-meeting-407:11
*** IlyaG has quit IRC07:15
*** lbragstad has quit IRC07:16
*** fungi has quit IRC07:17
*** yamahata has quit IRC07:19
*** lbragstad has joined #openstack-meeting-407:21
*** hdaniel has quit IRC07:23
*** minwang2 has quit IRC07:30
*** fungi has joined #openstack-meeting-407:32
*** evgenyf has joined #openstack-meeting-407:32
*** spotz_zzz is now known as spotz07:34
*** spotz is now known as spotz_zzz07:35
*** spotz_zzz is now known as spotz07:35
*** minwang2 has joined #openstack-meeting-407:37
*** javeriak has quit IRC07:39
*** ppetit has joined #openstack-meeting-407:44
*** ppetit has quit IRC07:45
*** wanghua has joined #openstack-meeting-407:45
*** belmoreira has joined #openstack-meeting-407:47
*** minwang2 has quit IRC07:53
*** _degorenko|afk is now known as degorenko07:56
*** vtech has joined #openstack-meeting-407:56
*** spotz is now known as spotz_zzz07:57
*** Sukhdev has quit IRC07:57
*** SumitNaiksatam has quit IRC08:00
*** emagana has joined #openstack-meeting-408:04
*** emagana has quit IRC08:08
*** salv-orlando has joined #openstack-meeting-408:10
*** hdaniel has joined #openstack-meeting-408:12
*** dshakhray has joined #openstack-meeting-408:12
*** salv-orl_ has quit IRC08:12
*** javeriak has joined #openstack-meeting-408:13
*** salv-orlando has quit IRC08:14
*** salv-orlando has joined #openstack-meeting-408:14
*** ihrachys has joined #openstack-meeting-408:15
*** spzala has joined #openstack-meeting-408:20
*** amotoki has quit IRC08:25
*** nikhil has joined #openstack-meeting-408:25
*** spzala has quit IRC08:25
*** nikhil_k has quit IRC08:28
*** ihrachys has quit IRC08:30
*** Jeffrey4l has quit IRC08:33
*** iyamahat has joined #openstack-meeting-408:34
*** ihrachys has joined #openstack-meeting-408:36
*** ihrachys has quit IRC08:38
*** bnemec has joined #openstack-meeting-408:39
*** mbound has joined #openstack-meeting-408:42
*** matrohon has joined #openstack-meeting-408:42
*** ihrachys has joined #openstack-meeting-408:44
*** ihrachys has quit IRC08:46
*** ihrachys has joined #openstack-meeting-408:49
*** salv-orlando has quit IRC08:52
*** zeih has joined #openstack-meeting-408:55
*** ppetit has joined #openstack-meeting-408:55
*** ihrachys has quit IRC08:56
*** zeih has quit IRC08:56
*** zeih has joined #openstack-meeting-408:56
*** zhurong has quit IRC09:01
*** iyamahat has quit IRC09:03
*** ihrachys has joined #openstack-meeting-409:10
*** ihrachys has quit IRC09:10
*** sdake has joined #openstack-meeting-409:15
*** ppetit has quit IRC09:24
*** iyamahat has joined #openstack-meeting-409:28
*** ppetit has joined #openstack-meeting-409:32
*** javeriak_ has joined #openstack-meeting-409:34
*** ppetit has quit IRC09:36
*** javeriak has quit IRC09:38
*** nkrinner has quit IRC09:38
*** tfukushima has quit IRC09:51
*** tfukushima has joined #openstack-meeting-409:51
*** zeih has quit IRC09:53
*** nkrinner has joined #openstack-meeting-410:06
*** zeih has joined #openstack-meeting-410:06
*** tfukushima has quit IRC10:09
*** zeih_ has joined #openstack-meeting-410:10
*** zeih has quit IRC10:11
*** salv-orlando has joined #openstack-meeting-410:16
*** salv-orlando has quit IRC10:21
*** spzala has joined #openstack-meeting-410:22
*** chem has quit IRC10:23
*** xingchao has joined #openstack-meeting-410:27
*** spzala has quit IRC10:27
*** yamamoto has quit IRC10:27
*** xingchao has quit IRC10:36
*** zeih_ has quit IRC10:40
*** javeriak_ has quit IRC10:41
*** d0ugal has quit IRC10:42
*** d0ugal has joined #openstack-meeting-410:42
*** xingchao has joined #openstack-meeting-410:43
*** pbourke_ has joined #openstack-meeting-410:45
*** zeih has joined #openstack-meeting-410:49
*** FallenPegasus has joined #openstack-meeting-410:51
*** spotz_zzz is now known as spotz10:52
*** xingchao has quit IRC10:53
*** zeih has quit IRC11:03
*** salv-orlando has joined #openstack-meeting-411:07
*** spotz is now known as spotz_zzz11:15
*** vtech has quit IRC11:16
*** javeriak has joined #openstack-meeting-411:27
*** yamamoto has joined #openstack-meeting-411:32
*** yamamoto has quit IRC11:33
*** mbound has quit IRC11:35
*** pbourke_ has quit IRC11:47
*** iyamahat has quit IRC11:48
*** pbourke_ has joined #openstack-meeting-411:49
*** ScottMillward has quit IRC11:50
*** ScottMillward has joined #openstack-meeting-411:50
*** zeih has joined #openstack-meeting-411:54
*** vtech has joined #openstack-meeting-411:55
*** pkoniszewski has quit IRC11:56
*** pkoniszewski has joined #openstack-meeting-411:56
*** spotz_zzz is now known as spotz11:57
*** julim_ has quit IRC12:03
*** zeih_ has joined #openstack-meeting-412:07
*** banix has joined #openstack-meeting-412:07
*** spotz is now known as spotz_zzz12:08
*** ihrachys has joined #openstack-meeting-412:10
*** zeih has quit IRC12:11
*** julim has joined #openstack-meeting-412:11
*** ihrachys has quit IRC12:13
*** iyamahat has joined #openstack-meeting-412:17
*** xingchao has joined #openstack-meeting-412:19
*** xingchao has quit IRC12:21
*** spzala has joined #openstack-meeting-412:24
*** zeih has joined #openstack-meeting-412:25
*** schwarzm has quit IRC12:25
*** iyamahat has quit IRC12:27
*** mbound has joined #openstack-meeting-412:28
*** zeih_ has quit IRC12:28
*** spzala has quit IRC12:30
*** dims has joined #openstack-meeting-412:32
*** baohua has quit IRC12:34
*** zeih has quit IRC12:36
*** zeih has joined #openstack-meeting-412:36
*** pbourke_ has quit IRC12:37
-openstackstatus- NOTICE: Infra running with lower capacity now, due to a temporary problem affecting one of our nodepool providers. Please expect some delays in your jobs. Apologies for any inconvenience caused.12:40
*** baoli has joined #openstack-meeting-412:40
*** zeih_ has joined #openstack-meeting-412:40
*** ppetit has joined #openstack-meeting-412:41
*** javeriak has quit IRC12:41
*** zeih has quit IRC12:42
*** pbourke_ has joined #openstack-meeting-412:43
*** baoli_ has joined #openstack-meeting-412:43
*** baoli has quit IRC12:45
*** banix has quit IRC12:48
*** mbound has quit IRC12:49
*** mbound has joined #openstack-meeting-412:51
*** zeih_ has quit IRC12:52
*** mbound has quit IRC12:53
*** zeih has joined #openstack-meeting-412:53
*** julim has quit IRC12:54
*** Jeffrey4l has joined #openstack-meeting-412:55
*** julim has joined #openstack-meeting-412:57
*** bobh has joined #openstack-meeting-412:59
*** bobh has quit IRC13:01
*** iyamahat has joined #openstack-meeting-413:06
*** ihrachys has joined #openstack-meeting-413:08
*** bobh has joined #openstack-meeting-413:11
*** bobh has quit IRC13:12
*** klamath has joined #openstack-meeting-413:13
*** reedip_ has joined #openstack-meeting-413:15
*** bobh has joined #openstack-meeting-413:16
*** zeih has quit IRC13:27
*** ihrachys has quit IRC13:30
*** emagana has joined #openstack-meeting-413:32
*** zeih has joined #openstack-meeting-413:32
*** ihrachys has joined #openstack-meeting-413:33
*** ScottMillward has quit IRC13:33
*** ScottMillward has joined #openstack-meeting-413:34
*** zeih has quit IRC13:34
*** zeih has joined #openstack-meeting-413:34
*** hvprash has joined #openstack-meeting-413:35
*** emagana has quit IRC13:36
*** zeih_ has joined #openstack-meeting-413:36
*** cdelatte has quit IRC13:39
*** zeih has quit IRC13:40
*** mbound has joined #openstack-meeting-413:42
*** baohua has joined #openstack-meeting-413:48
*** Jeffrey4l has quit IRC13:48
*** Jeffrey4l has joined #openstack-meeting-413:49
*** bobh has quit IRC13:53
*** cdelatte has joined #openstack-meeting-413:55
*** amotoki has joined #openstack-meeting-413:57
*** spzala has joined #openstack-meeting-413:58
*** spzala has quit IRC13:58
*** spzala has joined #openstack-meeting-413:58
*** ihrachys has quit IRC14:01
*** julim has quit IRC14:05
*** iyamahat has quit IRC14:05
*** pmesserli has joined #openstack-meeting-414:05
*** ninag has joined #openstack-meeting-414:06
*** Kevin_Zheng has joined #openstack-meeting-414:07
*** zeih_ has quit IRC14:08
*** zeih has joined #openstack-meeting-414:09
*** iyamahat has joined #openstack-meeting-414:09
*** yamamoto has joined #openstack-meeting-414:11
*** woodard has joined #openstack-meeting-414:14
*** amotoki has quit IRC14:17
*** neelashah has joined #openstack-meeting-414:18
*** amotoki has joined #openstack-meeting-414:21
*** cdelatte has quit IRC14:22
*** banix has joined #openstack-meeting-414:22
*** banix has quit IRC14:26
*** evgenyf has quit IRC14:26
*** ihrachys has joined #openstack-meeting-414:32
*** Swami has joined #openstack-meeting-414:36
*** bobh has joined #openstack-meeting-414:36
*** vhoward has joined #openstack-meeting-414:37
*** ihrachys has quit IRC14:37
*** bobh has quit IRC14:38
*** bobh has joined #openstack-meeting-414:38
*** jmckind has joined #openstack-meeting-414:38
*** cdelatte has joined #openstack-meeting-414:40
*** delattec has joined #openstack-meeting-414:42
*** yamamoto has quit IRC14:43
*** hvprash has quit IRC14:44
*** cdelatte has quit IRC14:45
*** yamamoto has joined #openstack-meeting-414:47
*** julim has joined #openstack-meeting-414:48
*** galstrom_zzz is now known as galstrom14:49
*** anteaya has quit IRC14:49
*** reedip_ has quit IRC14:50
*** baohua has quit IRC14:50
*** zeih has quit IRC14:51
*** yamamoto_ has joined #openstack-meeting-414:52
*** yamamoto has quit IRC14:52
*** anteaya has joined #openstack-meeting-414:53
*** mdnadeem1 has joined #openstack-meeting-414:57
*** yamamoto_ has quit IRC14:57
*** Ng has joined #openstack-meeting-414:59
*** avarner has joined #openstack-meeting-414:59
jasondotstar#startmeeting vahana15:00
openstackMeeting started Wed Feb  3 15:00:00 2016 UTC and is due to finish in 60 minutes.  The chair is jasondotstar. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: vahana)"15:00
openstackThe meeting name has been set to 'vahana'15:00
jasondotstar#topic roll call15:00
*** openstack changes topic to "roll call (Meeting topic: vahana)"15:00
jasondotstaro/15:00
Ng.o/15:00
jasondotstarhowdy15:00
jasondotstarpiet: FYI...if you're interested15:00
jasondotstarpiet: the vahana meeting is happening15:01
*** yamamoto has joined #openstack-meeting-415:01
jasondotstar#topic Introduction15:01
*** openstack changes topic to "Introduction (Meeting topic: vahana)"15:01
jasondotstarThis meeting is for the OpenStack Vahana project15:01
jasondotstarWe're building an iOS-based client for OpenStack, in the form of one or more frameworks for interacting with the OS API, and *possibly* front end app15:01
jasondotstar#link https://etherpad.openstack.org/p/openstack-mobile-ios-brainstorm15:01
jasondotstarInterested parties are encouraged to join the #openstack-vahana IRC channel15:01
jasondotstar#topic Action Items from Last Meeting15:02
*** openstack changes topic to "Action Items from Last Meeting (Meeting topic: vahana)"15:02
jasondotstarso i held a solo meeting last week15:02
Ng:)15:02
jasondotstar#link http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-01-27-15.00.html15:02
*** delatte has joined #openstack-meeting-415:03
*** spotz_zzz is now known as spotz15:03
*** delattec has quit IRC15:03
jasondotstarjust went through the motion just to collect a few thoughts in the public I guess15:03
jasondotstarso here goes:15:03
jasondotstarjasondotstar to continue reporting on the local dev documentation15:03
*** dandruta has joined #openstack-meeting-415:03
jasondotstarstatus on this is I've got something worked up.15:03
jasondotstarI'm working on generating the documentation from the openstack templates15:04
NgNice15:04
jasondotstarbut I'll post what I've got on etherpad later today (few other things on my plate rt nw)15:04
*** delatte has quit IRC15:04
jasondotstarit's basically install Xcode. Create a project and incorporate AlamoFire. Create a playground. Profit.15:05
jasondotstartrying to make it 'sexy' as possible15:05
jasondotstarhehehe15:05
Ng;)15:06
*** zeih has joined #openstack-meeting-415:06
jasondotstar#action jasondotstar to publish local dev environment documentation for reviewing15:06
jasondotstarok that's really it from last week15:06
jasondotstar#topic Todays Agenda15:07
*** openstack changes topic to "Todays Agenda (Meeting topic: vahana)"15:07
jasondotstarsince last week, I've been working closely with the openstackux PTL, piet, on conducting interviews with OpenStack operators15:07
jasondotstarwe could really use more interviewees15:07
jasondotstarNg: do you know a group of Ops guys at HP that we can poke?15:08
*** amotoki has quit IRC15:08
jasondotstar#link https://doodle.com/poll/3ehgtqh4kqrtx24y15:08
jasondotstarthis is the link to where interested parties can sign up to be interviewed15:08
Ngjasondotstar: I did, but now that public cloud is shut down, I'm honestly not sure what they're doing15:09
jasondotstarthe process is very relaxed15:09
jasondotstarNg: ack15:09
jasondotstar#action find a few more interviewees to participate in the mobile app use case interviews15:09
jasondotstarso we did have a couple guys that we interviewed on Monday over Google Hangouts15:10
*** numans has quit IRC15:10
jasondotstarone was an Ops guy from Intel15:10
purpNg jasondotstar: reach out to Ulf Baumann. He can get you connected to HP Ops folks.15:10
jasondotstarand the other was from Best Buy15:10
purpOh, and hi. o/15:10
jasondotstarpurp: ohai!15:10
jasondotstarpurp++15:10
jasondotstarthanks15:10
jasondotstarI'll do that15:10
NgHey purp :)15:10
purpHowdy howdy.15:11
jasondotstar#action jasondotstar to reach out to Ulf Baumann to get connected up with the HP Ops folks15:11
Ngjasondotstar: any useful initial feedback from those interviews?15:11
jasondotstaryes15:11
jasondotstarin fact, let's take a look15:11
*** cdelatte has joined #openstack-meeting-415:12
jasondotstar#link https://etherpad.openstack.org/p/mitaka-openstackux-mitaka-mobile-interviews15:12
jasondotstarso piet and i put together a few goals, you can read through those.15:12
jasondotstartwo things right off....15:12
jasondotstarfirst, both interviewees used Android phones :-/15:13
NgHah15:13
jasondotstarsecondly, they both felt strongly that alerting and monitoring are the strongest use case for developing something for mobile.15:13
*** jed56 has joined #openstack-meeting-415:13
jasondotstarone VERY interesting comment15:13
jasondotstarwas regarding visual programming15:14
jasondotstarim paraphrasing here but15:14
jasondotstarhe basically stated that having a visual programming interface could allow mobile devices to better PRODUCE content15:14
jasondotstaras opposed to CONSUMING it.15:15
jasondotstarone felt like his mobile device was purely for consumption15:15
Ngfor programming what?15:15
jasondotstarprogramming was a term he used loosely.15:15
jasondotstarprogramming in my mind, means taking actions from your phone with OpenStack15:15
Ngok15:16
jasondotstarlaunching instances15:16
jasondotstaradding storage15:16
jasondotstarconfiguring networking15:16
*** zeih has quit IRC15:16
jasondotstarthey talked about they return to their workstations (laptop, multi-monitor desktops, etc.)15:16
jasondotstarto take action (look at horizon, console in, etc.)15:16
jasondotstarhe mentioned game programming engines15:17
jasondotstarthat have visual representations for ACTIONS15:17
jasondotstarso having something like that might allow a phone or tablet to perform more actions15:17
jasondotstarinstead of just looking at mobile-ready monitoring dashboards15:17
jasondotstarand receiving alerts15:17
jasondotstars/about they/about how they/15:18
*** banix has joined #openstack-meeting-415:18
Ngso this maybe ties into something that purp suggested last week, which is that we may need a server component to this15:18
jasondotstar+115:18
Ngif we're going to be diving around all over the shape of a cloud, that's a heck of a lot of data for a phone to be round-tripping15:18
jasondotstari can almost see tying an alert to an action15:18
jasondotstarNg: +115:19
*** delattec has joined #openstack-meeting-415:19
jasondotstari thought it was an interesting point that the interviewee brought up on his own15:19
purpVery +1. We found it useful to make a set of aggregation and simplification APIs when we launched the original LinkedIn mobile app.15:20
purpAlso allows you to set up some web views (that aren't Horizon) if you care to.15:20
jasondotstarindeed.15:20
Ngjasondotstar: it is a very interesting idea15:21
jasondotstarI thought so too :-)15:21
purp(web views are very fast to iterate, then client lib can access underlying controller)15:21
* purp ducks back out for a meeting. Yay, meetings!15:21
jasondotstari was impressed. I happen to know about Kismet (the visual programming tool in Unreal Engine)15:21
jasondotstarpurp: thx 4 your input15:21
Ngpurp: thanks for coming :)15:21
*** acabot_ has joined #openstack-meeting-415:21
*** blahRus has joined #openstack-meeting-415:22
*** cdelatte has quit IRC15:22
jasondotstarhe brought that up as an example which is spot on.15:22
NgI do feel like we're now moving slightly further away from having a good idea of what this project is about/for ;)15:22
*** javeriak has joined #openstack-meeting-415:22
Ngbut that is fine at this stage15:22
jasondotstarstill... most of the convo with both of them centered around alerting/monitoring15:22
jasondotstarNg: +115:22
jasondotstarwe talked specifically about how they receive notifications15:23
jasondotstarmost are using email and SMS15:23
jasondotstaror a combination15:23
jasondotstara BIG problem that surfaced15:23
*** ihrachys has joined #openstack-meeting-415:23
jasondotstarwas the problem of finding the right SME to respond15:23
jasondotstarOps are in charge of it all. They're on call15:24
jasondotstarand an alert pops up. sometimes it's obvious what to do.15:24
*** zeih has joined #openstack-meeting-415:24
jasondotstarother times, a better skilled SME and/or a stakeholder needs to be notified of the issue15:24
*** sigmavirus24_awa is now known as sigmavirus2415:24
jasondotstarthey talked about how long it takes sometimes to find the right person to 'wake up'15:25
jasondotstarso having a mobile solution that perhaps knows who the SMEs and/or stakeholders are would be valuable.15:26
Nghmm15:26
jasondotstarthat's not necessarily an OpenStack problem to solve15:26
jasondotstarbut, it could be interesting to add some metadata to the monitoring efforts15:26
jasondotstarthat include a 'persons to alert' field.15:26
Ngyeah I think that's out of scope for us, and probably the wider project - monitoring/alerting is like deployment/orchestration, it's too religious and/or site-specific to make official ;)15:27
*** delatte has joined #openstack-meeting-415:27
jasondotstarthe idea of watch alerting was positive15:27
jasondotstarbut the two we interviewed saw no issue with pulling out a phone in a meeting or at lunch to react to an alert received15:27
Ngbut an app that's surfacing state and offering actions, could have customisable actions that do something like "look up this device/service/object in my runbook/cmdb/etc" that lets people find the information they need from their external resources15:28
*** delattec has quit IRC15:28
jasondotstar+115:28
jasondotstaron that note, it was also mentioned that it 'Would like to be able to monitor the status of an alert' in a custom temporary dashboard via mobile15:29
*** delatte has quit IRC15:29
jasondotstars/Would like/Would be nice/15:29
jasondotstari.e15:29
jasondotstarutilization is high15:30
jasondotstaryou can quickly get a custom UI that pops up on your phone15:30
jasondotstarthat monitors that ONE item temporarily until the issue is gone.15:30
*** harshs has joined #openstack-meeting-415:30
jasondotstari thought that one was interesting as well.15:31
Ngyeah it is. This stuff all needs to live outside of openstack components though, in that if the issue is with Horizon, and your "show me an alert/issue" stuff is happening in Horizon, you're in trouble :)15:32
jasondotstarpiet and I began to think if there were ways to interface with some of the monitoring efforts already in play (ceilometer, monasca, etc)15:32
jasondotstarNg: lol15:32
jasondotstarNg: you're in trouble if your alert system is down15:32
jasondotstarNg: +10015:32
*** Swami_ has joined #openstack-meeting-415:32
jasondotstarwe could already see a slight pattern15:33
jasondotstarbetween the two guys we interviewed15:34
NgI also think we're blurring the boundaries a little between operators and tenants. Tenants will mostly be talking to openstack APIs, operators have a lot of concerns that are outside of openstack and I'm not sure how we can help involve those things. That doesn't mean it can't be done, it's probably just a matter of plugins that speak to different APIs15:34
jasondotstaragreed. baremetal hosts or hypervisors going down15:34
*** zeih has quit IRC15:34
jasondotstarOps care about that moreso than tenants15:35
*** iyamahat has quit IRC15:35
jasondotstarwell they care too15:35
jasondotstarbut the actions taken to resolve it is often coming from the operators15:35
Ngyeah15:35
jasondotstari think that it's apparent that whatever we end up with for this project, it appears to be centered around alerting and notification15:36
*** Swami has quit IRC15:36
*** zeih has joined #openstack-meeting-415:36
jasondotstarand ***maybe*** mapping actions to alerts in a succinct way15:37
*** cdelatte has joined #openstack-meeting-415:37
pietWe're currently running interviews with Ops folks to understand their use cases15:37
pietI'm really excited with the ideas being thrown at us.15:37
jasondotstarpiet: ohai!15:37
pietYep15:37
pietLike Android? ;^)15:37
jasondotstarhehehehe15:37
pietNb Do you know any tenants?15:37
pietSorry Ng15:37
jasondotstari started off with that15:37
jasondotstar:-)15:37
Ngfor operator use cases at least, I'd like to hear what some tenants think, but it does seem like there would be interest in having some kind of stateful openstack proxy client, that mobile interfaces can consume15:38
pietI think the take-away is we need more heads to interview15:38
pietFeel free to recruit people via https://doodle.com/poll/3ehgtqh4kqrtx24y15:38
jasondotstaryes15:38
jasondotstarwe need more. i think that the during the Operators Summit we can get a lot of them done in one fell swoop15:39
jasondotstarbut, the more we can do online, the better.15:39
pietNg Can you describe specifically who the tenants are?  Are these the folks that have a tenant/project within OpenStack?  Likely worried about adding people and quotas?15:39
*** delattec has joined #openstack-meeting-415:40
Ngpiet: yeah so the people who are consuming an openstack installation purely via its APIs. They talk to nova and launch instances of their applications, cinder/swift to attach their storage to instances, or store things, etc, etc.15:40
jasondotstarIMHO, it's customers consuming openstack15:40
Ngthey never get to see behind the curtain of what is powering their cloud, they just consume it15:40
jasondotstarpiet: what he said :-)15:40
jasondotstarperhaps there is a way to spin this15:41
NgI think I had originally envisioned that we'd be of more use to tenants, but that may not be the case at all15:41
jasondotstaras an app for tenants?15:41
jasondotstarNg: damn, we're on the same wavelength15:41
jasondotstar:-)15:41
Ng:)15:41
jasondotstarthat could be interesting15:41
*** Sukhdev has joined #openstack-meeting-415:41
jasondotstarespecially in the spirit of DevOps15:41
jasondotstarhaving an app where tenants can *somewhat* share the responsibility of their compute resources15:42
*** cdelatte has quit IRC15:43
jasondotstarOperators have multiple ways to be nagged by monitoring systems and failed health checks15:43
jasondotstarin addition to providing a metering dashboard to tenants, maybe there's a way to provide alerting directly to the tenants15:43
jasondotstarthinking aloud here...15:43
*** iyamahat has joined #openstack-meeting-415:44
pietNg We kind of make a distinction between end users, tenant admins and DevOps.15:45
Nginteresting15:45
*** iyamahat has quit IRC15:45
*** iyamahat has joined #openstack-meeting-415:46
jasondotstarpiet: true. but in true DevOps fashion, it's about having Devs (end-users consuming openstack) and Ops (admins who maintain the stability of openstack) work together15:46
jasondotstarthe whole 'Make Devs carry pagers' paradigm15:47
pietNg End Users and DevOps are slightly different skillsets.  Also, DevOps seems to be a bit of a unicorn15:47
jasondotstarit is15:47
jasondotstarthere's difference in perception across the board15:48
jasondotstarstill, perhaps theres some merit around offering tenants metering, alerting, and notifications from their resources directly via mobile15:49
pietAlso, Domain Admins typically manage the relationship w the cloud provider and are typically concerned with budget15:49
jasondotstar+115:49
jasondotstarperhaps we've got more questions to add :-)15:50
jasondotstaror another demographic to interview... tenants.15:50
jasondotstarGOOD dialogue here, this is awesome.15:51
jasondotstarlet's move to the final 10 mins of the meeting15:51
jasondotstar#topic Open Discussion15:51
*** openstack changes topic to "Open Discussion (Meeting topic: vahana)"15:51
jasondotstarwe can continue or if there's anything else we need to bring up please... floor is yours15:52
pietI need to sneak out early to get ready to interview someone for another project15:52
NgI have nothing but questions now :)15:52
jasondotstarpiet: hey thx! i'll work on getting a few more ppl b4 ops summit15:53
pietK - we need to hammer on Fifield to get a space15:53
jasondotstarpiet: we DO15:53
pietSent him and email, but he likes to ignore15:54
jasondotstarfollow up today15:54
jasondotstarI will15:54
jasondotstarsorry i sound like yoda15:54
Nghaha15:54
*** salv-orl_ has joined #openstack-meeting-415:54
jasondotstar#action jasondotstar to follow up with fifield on getting some space at the ops summit15:55
jasondotstarcool. I'll give you guys five mins back if nothing else15:55
Ng:)15:55
jasondotstarthanks piet, Ng, purp15:55
Ngthanks all :)15:55
pietCheers15:55
jasondotstar#endmeeting15:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:55
openstackMeeting ended Wed Feb  3 15:55:41 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-02-03-15.00.html15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-02-03-15.00.txt15:55
openstackLog:            http://eavesdrop.openstack.org/meetings/vahana/2016/vahana.2016-02-03-15.00.log.html15:55
*** Ng has left #openstack-meeting-415:55
piethttps://wiki.openstack.org/wiki/OpenStack_Personas_201515:55
*** salv-orlando has quit IRC15:57
*** galstrom is now known as galstrom_zzz15:57
*** nkrinner has quit IRC15:57
*** leecalcote has joined #openstack-meeting-415:58
*** degorenko is now known as _degorenko|afk15:58
*** zeih has quit IRC16:00
*** javeriak has quit IRC16:01
*** emagana has joined #openstack-meeting-416:02
*** minwang2 has joined #openstack-meeting-416:02
*** avarner__ has joined #openstack-meeting-416:02
*** avarner has quit IRC16:02
*** emagana has quit IRC16:02
*** SimonChung1 has quit IRC16:03
*** zeih has joined #openstack-meeting-416:04
*** leecalcote has quit IRC16:04
*** galstrom_zzz is now known as galstrom16:05
*** leecalcote has joined #openstack-meeting-416:07
*** emagana has joined #openstack-meeting-416:08
*** zeih has quit IRC16:09
*** javeriak has joined #openstack-meeting-416:10
*** galstrom is now known as galstrom_zzz16:11
*** mdnadeem1 has quit IRC16:16
*** spzala has quit IRC16:17
*** spzala has joined #openstack-meeting-416:18
*** Guest44587 has joined #openstack-meeting-416:19
*** mdnadeem1 has joined #openstack-meeting-416:19
*** ihrachys has quit IRC16:20
*** spzala has quit IRC16:22
*** spzala has joined #openstack-meeting-416:24
*** matrohon has quit IRC16:24
*** banix has quit IRC16:24
*** daneyon has joined #openstack-meeting-416:24
*** inc0 has joined #openstack-meeting-416:24
*** avarner__ has quit IRC16:25
*** avarner__ has joined #openstack-meeting-416:25
*** dratushnyy has joined #openstack-meeting-416:26
*** akwasnie has joined #openstack-meeting-416:26
*** rhallisey has joined #openstack-meeting-416:27
*** daneyon_ has quit IRC16:27
*** avarner__ has quit IRC16:27
*** avarner___ has joined #openstack-meeting-416:27
*** belmoreira has quit IRC16:28
*** dtardivel has joined #openstack-meeting-416:29
rhallisey#startmeeting kolla16:30
openstackMeeting started Wed Feb  3 16:30:22 2016 UTC and is due to finish in 60 minutes.  The chair is rhallisey. Information about MeetBot at http://wiki.debian.org/MeetBot.16:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:30
*** openstack changes topic to " (Meeting topic: kolla)"16:30
openstackThe meeting name has been set to 'kolla'16:30
*** leecalcote has quit IRC16:30
rhallisey#topic rollcall16:30
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:30
SamYapleo/16:30
rhalliseyhello16:30
akwasnieo/16:30
elemoineo/16:30
SamYapleunicell: ping16:30
dratushnyyo/16:30
Jeffrey4l\o/16:30
pbourke_hi16:30
nihilifero/16:30
mdnadeem1o/16:30
rhalliseyso sdake will be back in ~15 min16:31
*** stvnoyes has joined #openstack-meeting-416:31
rhalliseybut will continue without him for now16:31
jpeelerhi16:31
rhalliseyhey Jeff16:31
Guest44587hi16:32
SamYaplejpeeler: o/16:32
*** Guest44587 has left #openstack-meeting-416:32
rhalliseyinc0, around?16:32
Jeffrey4lhi every one16:32
*** Guest44587 has joined #openstack-meeting-416:32
*** bpokorny has joined #openstack-meeting-416:32
sdakeo/16:32
sdakei am back now16:32
sdakebut go ahead and run the agenda rhallisey16:32
rhalliseykk16:32
sdakebeen going since 3am and i'm beat16:32
rhallisey#topic Announcements16:33
*** openstack changes topic to "Announcements (Meeting topic: kolla)"16:33
rhalliseySo midcycle is right around the corner16:33
rhalliseyjust want to remind everyone it's Feb 9th and 10th16:33
inc0o/16:33
inc0sorry I'm late16:33
rhalliseyinc0, no worries16:33
rhallisey#link https://etherpad.openstack.org/p/kolla-mitaka-midcycle16:33
ajafoo/16:33
rhalliseyjust a reminder as to what is likely to be covered16:34
rhalliseysdake, did you finalize the schedule?16:34
sdakerhallisey no i did not16:34
sdakebut I will do so today16:34
*** ihrachys has joined #openstack-meeting-416:34
rhalliseykk16:34
sdakeits part of my work day16:35
sdakeplease register if you haven't16:35
rhallisey^ yes that too16:35
rhallisey#topic Kolla-ansible config playbooks16:35
*** openstack changes topic to "Kolla-ansible config playbooks (Meeting topic: kolla)"16:35
*** bpokorny has quit IRC16:35
rhalliseySamYaple, go ahead16:35
SamYaplewill do. thanks rhallisey16:35
rhalliseyI'm excited for this topic16:35
SamYaple#link https://review.openstack.org/#/c/271126/16:35
rhallisey#link https://review.openstack.org/#/c/271126/16:36
*** bpokorny has joined #openstack-meeting-416:36
rhalliseyyou might not have perms :)16:36
SamYapleok16:36
*** kproskurin has joined #openstack-meeting-416:36
SamYaplethat patchset is a bit discussing the issue16:36
*** sambetts has joined #openstack-meeting-416:36
SamYaplebasically what do we do when a config file _changes_?16:36
*** sambetts has left #openstack-meeting-416:36
SamYaplewe need to restart services to pull in that change16:36
SamYaplethe purposed patch does it in line, I dont particularly agree with that approach because then you get service restarts out of the blue16:37
sdakeSamYaple  agree16:37
inc0or call sighup on certain16:37
SamYapleinc0: yes on a few we can16:37
sdakeinc0 the filelsystem is readonly16:37
SamYaplebut its still a service shutdown (just a much quicker one)16:37
sdakeonce the config is in the container needs to be restarted16:37
inc0we would need to copy new conf file tho16:37
SamYaplesdake: no, thats for COPY_ONCE only16:38
sdakeSamYaple yes i know16:38
sdakewhich needs to work :)16:38
inc0default is COPY_ALWAYS afair16:38
SamYapleno its COPY_ONCE16:38
sdakedefinately coyp once16:38
inc0ok16:38
inc0my mistake then16:38
sdakewe made that decision long ago16:38
SamYaplebut with the changes to allow sighup the community at large is moving to changing configs so well revisit that later16:38
SamYaplethats not the point of this16:38
SamYapleback on topic16:39
sdakethat was part of the whole blueprint spec thing for ansible - that was required to get people to approve the spec16:39
*** javeriak has quit IRC16:39
SamYaplethe config playbook would be similiar to what we do with upgrades16:39
SamYapleif new config changes are detected it would do a rolling restart to pull in those changes16:39
*** javeriak has joined #openstack-meeting-416:39
inc0action - reconfigure?16:39
SamYaplesure16:39
SamYaplethats a reasonable name16:39
inc0yeah, I'm cool with that16:39
SamYapleso well reuse alot of (not yet written) upgrade code I think16:40
SamYapleto maintain uptime and availability16:40
inc0althouth I'd say we need to find out if config changes and restart only services we need16:40
SamYaplewhich should be easy inc016:40
SamYaplea quick md5sum compare16:40
inc0so if task template == changed then restart corresponding16:40
SamYaplewe do this in the haproxy container16:40
SamYapleno that wont work16:40
SamYaplebecause deploy changes teh files as they are laid down16:40
SamYaplereconfigure would need a direct compare16:41
inc0ok, makes sense16:41
SamYapleso i think we are all on the same page here, just making everyone aware of the issue16:41
inc0still, we need to take that into account16:41
SamYapleno we dont need to track template == changed at all16:41
SamYaplesince we compare running vs current config16:41
sdakeone concern16:41
SamYapleok16:42
sdakei want upgrades16:42
sdakereally really want upgrades16:42
sdakei know they are related16:42
*** javeriak_ has joined #openstack-meeting-416:42
sdakebut i am concerned separating the work will make it harder to implement the ugprades16:42
SamYapleconfig work is going to ride the coatail of upgrades16:42
sdakeshouldn't htis work come after?16:42
sdakeok wfm16:42
sdakethen i'm good16:42
sdakeas long as we aren't rollign it all together16:42
*** julim has quit IRC16:42
SamYapleunicell: ^^ when you see this16:43
SamYapleoops wrong topic unicell16:43
SamYapleok rhallisey im ready to move on16:43
rhallisey#topic Kolla-ansible delegate_to vs run_once16:43
*** openstack changes topic to "Kolla-ansible delegate_to vs run_once (Meeting topic: kolla)"16:43
rhalliseyokie16:43
SamYapleok this one is for unicell16:43
SamYaplethis is a tricky issue ill try to describe quickly16:43
*** Swami__ has joined #openstack-meeting-416:43
SamYaple#link https://review.openstack.org/#/c/271148/16:44
SamYaplethats a related patch16:44
*** javeriak has quit IRC16:44
SamYaple#link https://bugs.launchpad.net/kolla/+bug/152072816:44
openstackLaunchpad bug 1520728 in kolla "fatal: [openstack002] => One or more undefined variables: 'dict object' has no attribute 'stdout'" [Critical,In progress]16:44
SamYaplethats the bug16:44
SamYaplewe have had several bugs on this issue and unicell finally tracked it down16:44
*** julim has joined #openstack-meeting-416:44
*** avarner has joined #openstack-meeting-416:45
SamYapleAnsible 1.9.4 has an issue with multiple host includes and roles and our inventory16:45
*** tonyb has quit IRC16:45
*** sean-k-mooney has joined #openstack-meeting-416:45
SamYapleit is fixed in the 2.0 branch, but until 2.0 it will skip certain tasks even if it shouldnt16:45
SamYaplethis makes certain inventory configs not useable with the bootstrap16:45
*** avarner___ has quit IRC16:45
sdakegroan16:45
SamYapleessentially its broken for certain deploys16:45
sdakeany more detail?16:45
rhalliseyouch16:46
*** armax has joined #openstack-meeting-416:46
SamYapleyea but its technical and time consuming16:46
sdakecan we get some docs on this ansible 1.9.4 deploy problem?16:46
SamYapleill go over the options we have t ofix this16:46
*** tonyb has joined #openstack-meeting-416:46
rhalliseySamYaple, ya that would be good16:46
SamYapledetails can be provided later16:46
*** mugsie has quit IRC16:46
sdakeok options then wfm16:46
*** mugsie has joined #openstack-meeting-416:46
SamYapletwo options, in no particular order of preference16:46
*** Swami_ has quit IRC16:47
SamYaple1) upgrade ansible to 2.0. Lots of software has already made the switch. A 2.0 change is not very painful (ive analyzed the impact) it would just require us to run ansible 2.016:47
SamYaple(we can discuss these options in a minute)16:47
inc01* affects upgrades16:47
inc0but in a way we can handle it I think16:47
SamYaple2) we can force all specific options that encounter this bug to use the first host in the appropriate group. This would fix it! But it would be if the first node is down, you cant run the playbooks at all16:48
sdakeinc0 plan therei s deploy 1.9.4, then deploy liberty, then deploy 2.0.0 then upgrade to mitaka16:48
SamYaplethe second option breaks high-availability in my mind16:48
SamYaplethe first node must always be live or it all breaks16:49
sdakemaybe i'm an old fuddy duddy but i hate adopting brand new 2.0.0 software for anssible 2 months prior to release when their test cases are very very weak16:49
inc0if we upgrade to 2.0...do we still need kolla_docker?16:49
SamYapleinc0: yes16:49
sdakewe are running our own module forever16:49
SamYaple^^16:49
inc0ok16:49
SamYaplefor docker*16:49
sdakeright16:50
SamYapleits just too critical16:50
sdakeits something we need to own16:50
SamYapleok so those are the options we have16:50
SamYapleneither of them are great16:50
inc0wfm, but kinda agree with Steve, upgrading to 2.0 will affect upgrades of kolla and we're awfully close to Mitaka16:50
sdakeok so lets analyze impact of waiting to 2.0.0 to newton16:50
SamYaplewe could also ignore the issue and just have that be the issue for mitaka16:50
rhalliseyhow about option 2, then move to 2.0 later?16:50
sdakeha is slightly degraded?16:50
rhalliseyand fix it properly16:50
SamYaplesdake: if first node is down, you can't run playbooks at all16:50
inc0certain parts of deployment are causing errors16:51
sdakeok highly degraded16:51
sdakethat kind of sucks16:51
sdakeis there a third option16:51
SamYaplenot that I know of16:51
sdakesuch as document what types of deploys will expose this bug16:51
inc0ignore the issue for now?16:51
SamYapleinc0: yea thats the third16:51
sdakeignore is not a option inc016:51
rhalliseyhehe16:51
sdakedocument and ignore would be ok i think :)16:51
jpeelerso is there more background for state of code in ansible 2.0? was it a complete rewrite? (sorry don't know)16:51
*** delattec has quit IRC16:51
Jeffrey4lhow about use the option 1 and add a pre-check to make sure the first node is up.16:52
SamYaplebut its really hitting the ebay bugs and Hui (and other)16:52
sdakejpeeler pretty much green field rwerite16:52
dratushnyywhat if use 2.0 for deploys that exposes bug?16:52
inc0ignore == document and ignore, I mean let's not fix it right now and get this as priority for N16:52
*** prashantD has joined #openstack-meeting-416:52
jpeelerah, that does make the decision tricky then16:52
SamYapledratushnyy: we cant do a 2.0 and 1.9.x compatible structure for kolla16:52
sdakedratushnyy our code can onl yrun on 194 or 2.0.016:52
sdakeif we could we  would have done that already16:52
inc0also I'd really like to have 1 release deprecation for deps...16:52
SamYaplepersonally, i think we should _not_ move to ansible 2.016:53
rhalliseyinc0, I'm also thinking door #3 here16:53
SamYaplebut crippling our multinode is bad too16:53
sdakei agree moving to ansible 2.0.0 prior to newton is a bad bad move16:53
inc0SamYaple, we'll have to at some point16:53
inc0we will only encounter more stuff like that16:53
*** sridhar_ram has joined #openstack-meeting-416:53
SamYapleinc0: in newton i plan to do it immediately after midcycle16:53
rhallisey#1 could ruin upgrades for M #2 is a workaround #3 release with a limiation16:53
SamYapleinc0: so it has time to sit16:53
elemoinesdake, you mean prior to mitaka (not newton)16:54
sdakein newton we could do at start of cycle16:54
inc0SamYaple, wait till we pop newton branch plz16:54
sdakeelemoine yes prior to mitaka sorry16:54
sdakeok lets focus guys16:54
SamYapleinc0: newton branch means we have released newton ;)16:54
sdakeand gals16:54
inc0SamYaple, can you list situations in which problem occurs?16:54
inc0SamYaple, you know what I mean...16:55
sdakeyes w eneed more details16:55
sdakewe can dothis on the mailing list if its too time consuming16:55
SamYaplelet me find unicell bug16:55
sdakeSamYaple lets do it on the mailing list16:55
sdakenad i will schedule 20-30 misn at midcycle for this16:55
sdakeso we can make a decision then16:55
sdakeafter we understand what situations its fails under16:55
sdakebecause that is a critical critical piece of missing information that is needed to make a decision16:56
rhalliseyagreed16:56
SamYapleok16:56
rhalliseySamYaple, you cool with stating a thread?16:56
sdakeSamYaple can you take action to start thread?16:56
*** fitoduarte has joined #openstack-meeting-416:56
SamYapleyea sure16:56
sdakethanks bro16:56
inc0SamYaple, will you start thread? (3 times so you can't refuse)16:56
inc0;)16:56
SamYapleprobably wait for unicell since this is his issue16:56
rhallisey:)16:56
rhalliseyok moving on16:57
rhallisey#topic Logging with Heka (spec and development)16:57
*** openstack changes topic to "Logging with Heka (spec and development) (Meeting topic: kolla)"16:57
rhalliseyelemoine, you have the floor16:57
elemoineok, that's me :)16:57
elemoinethe Heka spec got three +2's16:57
sdakeSamYaple  quick quesiton16:57
elemoineCan I start pushing a patch flow to Gerrit?  Or should I wait for a more official approval?16:57
sdakecould we somehow make thte code conditional to select the "2nd" node16:57
rhalliseyelemoine, excellent16:57
sdakeif the first node was down16:57
*** belmoreira has joined #openstack-meeting-416:57
inc0yeah it's solid imho16:58
rhalliseyelemoine, I think generally we have all the cores for on specs before we +a16:58
sdakelike a config option "damnit select this node"16:58
rhalliseyelemoine, can you link the spec?16:58
sdakeapprently i'm lagged16:58
elemoinehttps://review.openstack.org/#/c/270906/16:58
elemoine#link https://review.openstack.org/#/c/270906/16:58
sdakeele yo uwill get a review from me when this meeting concludes16:58
inc0how about we run heka in pararell to rsyslog - if you run central logging it's heka16:58
rhalliseyelemoine, I don't want to delay it too long waiting on all cores, but would like a little more than 316:58
rhalliseyso all cores please review https://review.openstack.org/#/c/270906/16:59
sdakerhallisey  we require 6 +2 votes16:59
elemoinesure, I'm just wondering if can start working on patches16:59
rhalliseyafter the meeting16:59
elemoineand push my patch stream to Gerrit16:59
sdakespecs require simple majority16:59
elemoinefyi, this is the sort of patch stream I c16:59
elemoineconsider pushing:16:59
elemoinehttps://github.com/openstack/kolla/compare/master...elemoine:heka-gerrit16:59
*** IlyaG has joined #openstack-meeting-417:00
sdakeelemoine dont put it on github get it in the review queue please17:00
rhalliseyelemoine, I'm cool with you start pushing them tbh17:00
sdakeeven if its not ready17:00
sdakeso people dont have to hunt for it17:00
*** avarner has quit IRC17:00
elemoinethat's exactly my question :)17:00
sdakejust mark workflow -117:00
elemoinecan I push that to Gerrit before the spec is fully approved17:00
inc0I'm -1 on removing rsyslog just yet tho17:00
*** avarner has joined #openstack-meeting-417:00
rhalliseyya just -1 it17:00
sdakeelemoine you can push to errit before spec is approved17:00
elemoineinc0, why?17:01
sdakeelemoine i recommend placing a -2 at your top level patch17:01
sdakeor marking it [wip]17:01
sdakeso someone doesn't accidentally merge it during review17:01
inc0elemoine, backward compatibility (I should change name to Michal "backward compatibility" Jastrzebski)17:01
sdakei wnat heka to go in as one big patch stream17:01
inc0I want to lessen impact on upgrades17:01
sdakeinc0 lol17:01
SamYapleinc0: that is never a requirement17:01
SamYaplewe never said anything about backward compatibly17:02
inc0however, old version doesn't have central logging17:02
inc0Liberty17:02
sdakeinc0 we roll forward not back17:02
SamYaplejust like openstack17:02
sdakeinc0 i think that really isn't a problem17:02
SamYaplefor rollback of openstack you need DB restore17:02
inc0so I'd say if you run central logging, its heka17:02
*** yamahata has joined #openstack-meeting-417:02
sdakersyslog didn't work fantastically well in liberty anyway17:02
inc0well, I know17:02
sdakenot criticising17:02
inc0but if someone runs it they might build on it17:03
inc0that's my point17:03
sdakejust indicating - if we can just move it to heka and be done thats one less migration our users have to deal with17:03
inc0we say "rsyslog will disapear completely in N"17:03
*** uck has joined #openstack-meeting-417:03
rhalliseyelemoine, did you have anything else you wanted to go over?17:03
elemoineyes, quick thing17:04
inc0so my personal preference is to have it as default option, but an option for now17:04
inc0for one release17:04
sdakeinc0 leave feedback to that statement in hte review please17:04
inc0sure17:04
elemoineinc0, people asked me if Heka could replace Rsyslog entirely,17:04
*** dims has quit IRC17:04
sdakeright  after meeting17:04
inc0I'm still +2 on spec tho17:04
sdakemight actuallybe a good idea17:04
elemoineand now the request it to keep Rssyslog17:04
sdakeif we had capacity to pull it off17:04
inc0elemoine, just don't change anything with it and put one if statement in configs17:05
inc0rest is the same17:05
elemoineinc0, oh I see17:05
inc0I'm first person to say lets replace rsyslog17:05
elemoineit's also compatible with my patches17:05
elemoineok understood17:05
inc0let's just have at least some deprecation period17:05
elemoinewfm17:05
elemoineso17:05
elemoineanother thing17:05
*** dims has joined #openstack-meeting-417:06
elemoineWe will need specific Lua decoders for parsing OpenStack, MySQL and RabbitMQ logs.17:06
*** vtech has quit IRC17:06
elemoineWe already have these decoders, that we use in other projects (Fuel)17:06
inc0I like lua17:06
elemoineOur plan to distribute these decoders as deb and rpm packages in the future17:06
dratushnyyLua is nice17:06
*** jmckind has quit IRC17:06
elemoineBut if we don't have time to do that by Mitaka 3 (the 4th of March), will it be ok to have these Lua decoders in Kolla, really as a temporary solution?17:06
sdakelicense is whwat elemoine17:06
inc0elemoine, can we do this in our tree?17:06
sdakeneed to know the license on all software17:07
inc0I don't want to introduce new repo dependency for what probably will be less than 200 loc17:07
elemoineinc0, we have another code base that uses these decoders17:07
nihiliferthey will be our custom decoders or some apche license compatibility?17:07
elemoineso we'd like to share them17:07
sdakewhat license17:07
nihilifercompatible*17:07
ppetitLicense of the lua plugins is in Fuel is Apache V217:07
sdakeASL2.0 is what makes my life easy17:07
sdakecool17:08
sdakei dont mind if they hit the repo - 200 lines of bloat for a cycle isnt' bad as long as it doesn't create an upgrade problem down the road17:08
sdakeso eval that17:08
sdakestart a thread on ml elemoine17:08
elemoineit won't be a problem17:08
elemoinesdake, ok I will17:08
sdakeupgrade needs to be top of mind when people make new design changes ;)17:08
elemoinebottom line is17:08
sdakeif you can't upgrade it in some way, then dont do it for mitaka please17:09
sdakenewton wide open17:09
elemoinewe'd like to have the Lua decoders outside Kolla17:09
sdakebut mitaka we are super stretched17:09
elemoinebut maybe not for Mitaka17:09
sdakeok i need 10 mins17:09
*** liyi has joined #openstack-meeting-417:09
inc0elemoine, let's start by having them in tree as it's simplest and then we'll revisit ok?17:09
sdakerhallisey  ^^17:09
elemoineinc0, exactly what I'm suggesting17:09
sdakemaybe 517:09
elemoineIm done17:10
rhalliseysdake, roger17:10
rhalliseycool thanks elemoine.  Nice job on the spec17:10
sdakefolks please review that spec17:10
*** ihrachys has quit IRC17:10
sdakelets get er looking sparkling pretty17:10
rhallisey#topic sdake's announcement17:10
*** openstack changes topic to "sdake's announcement (Meeting topic: kolla)"17:10
sdakelike a diamon instead of lump of coal17:10
sdakenot announcement17:10
sdakejust topic17:10
sdakebut17:10
rhalliseyidk17:10
sdakei wanted to check in on how upgrades are coming along for people17:11
sdakecan i get a rollcall list of where people are at17:11
sdakei'll go first17:11
sdakeglance -> started implementation, will be complete by midcycle, distracted by remodel17:11
sdakeheat -> wont be done by midcycle17:11
inc0nova -> I'll rebase before midcycle17:12
inc0docker -> scares the shit out of me17:12
rhalliseylol17:12
*** dims has quit IRC17:12
nihilifermagnum -> just began the work17:12
SamYapleneutron -> needs thin containers then upgrade. thin containers done and working, but they required docker 1.1017:12
sdake#link https://launchpad.net/kolla/+milestone/mitaka-317:12
SamYapledocker 1.10 is due out next week17:12
SamYaple(or tomorrow017:12
Jeffrey4lhorizon -> done but need some review.17:12
nihiliferrabbitmq -> not started yet, will try to fdo before mid, but without promise17:12
SamYaplenihilifer: there is a rabbitmq patch already17:13
nihiliferoh...17:13
nihiliferi just saw free bp17:13
*** jmckind has joined #openstack-meeting-417:13
SamYapleill handle mariadb17:13
nihiliferbut ok17:13
* rhallisey did not grab an upgrade at devconf this week :(17:13
SamYaplenihilifer: likely someone didnt grab it17:13
inc0do we upgrade ceph?17:13
nihiliferwill pick something else from infra17:13
SamYapleinc0: yup17:13
inc0ceph will be funny17:13
SamYapleceph will be easy17:13
sdakeinc0 we will talk about infrastructure services at midcycle17:13
*** Swami__ has quit IRC17:13
inc0yeah I don't expect problems there17:13
sdakeI think we should jsut ugprade those once per cycle17:13
SamYapleive done real --> kolla ceph migration and the kolla --> real!17:14
sdaketowards the end17:14
sdakebut that is just my opinion17:14
sdakewe can have a more thorough discussion17:14
inc0yeah, all is good apart from qemu17:14
sdakethanks for the roll call folks17:14
sdakelooks like some progress is being made17:14
inc0qemu is so disruptive that I'd like to keep that separated17:14
sdaketry to get atleast one patch in teh queue (and working)17:14
sdakeinc0 ok we can talk about upgrades at midcycle17:14
sdakeI am ging to shcedule copious sessions :)17:15
sdakelets not beat dead horses17:15
sdakeI just want people to be prepapred to discuss it with real-world experiences17:15
SamYaplesdake: but thats the thing me and inc0 do best!17:15
sdakewhich it sounds like we are17:15
sdakerhallisey all done thanks17:15
rhalliseysdake, cool17:15
pbourke_swift -> started but slow, hope to have something up before midcycle17:15
inc0I don't mind if they're close to dead as well17:15
sdakeoh wait17:15
sdakepbourke_ going17:15
pbourke_v. busy this week before I travel for midcycle17:15
pbourke_whats that stake?17:16
rhalliseypbourke_, cool thanks17:16
pbourke_(heh, auto correct)17:16
sdakepbourke_ i meant you were speaking now17:16
sdakemistake ;)17:16
pbourke_ok that's me done :)17:16
sdakethats my other nickname :)17:16
rhalliseyok moving on17:16
rhallisey#topic Open Discussion17:16
*** openstack changes topic to "Open Discussion (Meeting topic: kolla)"17:16
SamYaplei need to bring somehting up here17:16
SamYaplethis patch https://review.openstack.org/#/c/274154/ please comment away on it17:16
SamYapleits had some convterasy already17:17
*** yamamoto has quit IRC17:17
SamYaplethats all for me (i think)17:17
sdakeSamYaple 20 second review i am in favor of a rename17:17
sdakei'll dig more into it17:17
rhalliseyya that wfm17:17
jpeeler+117:17
inc0rename is cool if we provide migration plan17:18
SamYaplewell coment there :P17:18
inc0which shouldn't be hard17:18
*** neelashah has quit IRC17:18
sdakeSamYaple let me properly review it buti will do so after this meeting17:18
SamYapleinc0: thats discussed in the review17:18
inc0just remove old and create new container17:18
*** dims has joined #openstack-meeting-417:18
SamYapleyup17:18
SamYapleidempotent remove FTW17:18
rhalliseycool, anyone have anything else?17:18
inc0this container doesn't do anything anyway, it just sits there after bootstraps and all17:18
nihiliferhow we'll do that removal/creation? by some playbook or wat?17:18
nihiliferwhat*17:18
SamYaplenihilifer: yea in line playbook17:19
SamYapleits idempotent17:19
inc0nihilifer, upgrade play would be my guess17:19
SamYaplenot a sperate playbook17:19
nihiliferk17:19
inc0upgrade will remove old container and add new, easy17:19
inc0deploy will just well...deploy17:19
SamYaplelike sunday morning17:19
elemoineshould it be part of the patch then?17:19
SamYapleno17:19
*** mbound has quit IRC17:19
inc0whatever17:20
inc0as long as it lands in the cycle17:20
SamYaplewe dont have common upgrade playbook yet17:20
SamYaplebut we will17:20
inc0well we kinda do17:20
inc0I mean we will17:20
*** neelashah has joined #openstack-meeting-417:20
sdakeSamYaple  you mean common between mesos and ansible?17:20
inc0and you might as well start;)17:20
elemoineok17:20
inc0sdake, common as common role17:20
SamYaplesdake: common role17:20
sdakegot it17:20
SamYapleoh hey i do have another topic17:20
inc0kolla_ansible, rsyslog17:21
sdakeya17:21
SamYaplekolla-mesos and kolla-ansible and kolla overlap17:21
SamYaplenihilifer: ^17:21
sdakefix upgrades17:21
sdakethen we fix repos17:21
inc0yeah lets move repo shuffling for N please17:21
nihiliferyes, it's not that urgent for me as well17:21
rhalliseyI'd like it for M, but upgrades have prio here17:22
sdakei am not opposed to moving the repos around for mitaka, it can be done we have the capacity, but i absolutely want upgrades done first before any repo movement takes place17:22
jpeeleri don't think anybody can disagree with that17:23
SamYaplethats no the overlap i was tlaking about specifically17:23
SamYaplebut yes to all of that17:23
SamYaplei was talkign about the tool and python code overlap17:23
SamYaplemesos dups _alot_ of code17:23
SamYaplecode that exists in the kolla (not kolla-ansible) repo17:24
sdakeand that is fixed how SamYaple ?17:24
SamYapleimport kolla17:24
SamYaplerather than being its own code17:24
sdakeright, so repo shuffle?17:24
SamYapleno...17:24
SamYapleno need to split repo to do what i say17:24
sdakeok cool then17:24
sdakei'm good with that kind of change17:24
*** dandruta has quit IRC17:24
sdakeas long as it doesn't slow down upgrades :)17:24
SamYaplenihilifer: need your thoughts on this17:24
inc0yeah, this is clean17:24
SamYaplenothing to do with upgrades sdake17:25
sdakei understand17:25
sdakeI just want to be crystal clear on this point folks - if we don't deliver upgrades in mitaka, it won't be pretty for us17:25
sdakethe community will lose trust in our ability to execute which right now the ythink we are rockstars17:25
nihiliferSamYaple: ok, i think we can try with importing kolla17:25
sdakethe operators wont take us seriously17:25
sdakeso upgrades, upgrades, upgrades17:26
nihiliferand in some fat future think about better way of sharing commons17:26
SamYaplenihilifer: cool no rush, i justdon't want to deverge to much17:26
inc0sdake, please do talk to your docker people, that's single biggest issue I have with upgrades now17:26
SamYaplewell if kolla-mesos has a dep on kolla then this should work easy for sharing... no?17:26
inc0I'm ok if that will happen in N cycle for us, noone runs Mitaka from day one anyway17:26
*** pbourke_ has quit IRC17:26
inc0but we need to be able to upgrade docker without restarting qemu imho17:27
nihiliferSamYaple: not exactly - they may be problems with sharing commons between kolla-ansible and ansible just for deploying mesos17:27
nihiliferand in deep N development - for k8s probably17:27
sdakeinc0 i got people working on that17:27
nihiliferbut that's something to think about in N17:27
sdakeinc0 but fwiw its out of our control17:28
SamYaplenihilifer: yea im not sure about that part, i was refering to scripts and common.py and such17:28
nihiliferyep, for strictly pythonic stuff, importing kolla may work17:28
inc0sdake, I know that it will be tricky, I moved some string on my end as well17:28
rhallisey2 minutes guys just an fyi17:28
SamYapleok im out! see you in #kolla17:28
inc0but if we force people to restart vms for upgrade..that will be bad.17:28
inc0imho17:29
Guest44587inc0: +117:29
sdakeok folks thanks for coming :)17:29
inc0I've been on too many ops summit upgrade sessions to say it won't17:29
rhalliseylet's spill over to kolla17:29
sdakeinc0 +0 atm :)17:29
rhalliseythank you everyone17:29
inc0thanks17:29
rhallisey:)17:29
*** pc_m has joined #openstack-meeting-417:29
rhallisey#endmeeting kolla17:29
*** mdnadeem1 has quit IRC17:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:29
openstackMeeting ended Wed Feb  3 17:29:39 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-02-03-16.30.html17:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-02-03-16.30.txt17:29
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-02-03-16.30.log.html17:29
sdakethanks rhallisey17:29
sdakeappreciate it bro17:29
rhalliseysdake, no problem17:29
*** Guest44587 has left #openstack-meeting-417:29
sdakeits fu nto participate in the meeting rather then run it :)17:29
sdakefirst time I've done that I think17:30
rhalliseysdake, heh :)17:30
*** kproskurin has left #openstack-meeting-417:30
rhalliseyI don't mind running it.  It's fun17:30
*** sean-k-mooney has left #openstack-meeting-417:30
*** rhallisey has left #openstack-meeting-417:31
dougwig#startmeeting networking_lib17:31
openstackMeeting started Wed Feb  3 17:31:08 2016 UTC and is due to finish in 60 minutes.  The chair is dougwig. Information about MeetBot at http://wiki.debian.org/MeetBot.17:31
* pc_m on via phone so limited typing.17:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:31
*** openstack changes topic to " (Meeting topic: networking_lib)"17:31
openstackThe meeting name has been set to 'networking_lib'17:31
dougwig#topic Announcements17:31
*** openstack changes topic to "Announcements (Meeting topic: networking_lib)"17:31
*** minwang2 has quit IRC17:31
dougwigJust a reminder of the neutron midcycle...17:31
dougwighttps://etherpad.openstack.org/p/neutron-mitaka-midcycle17:31
*** dratushnyy has left #openstack-meeting-417:31
*** mdnadeem1 has joined #openstack-meeting-417:32
dougwig#topic Open discussion17:32
*** openstack changes topic to "Open discussion (Meeting topic: networking_lib)"17:32
*** inc0 has quit IRC17:32
dougwigsorry, had a cold since sunday, so i didn't update the agenda. does anyone have any issues today?17:32
pc_mWould like to know what open tasks are avail as I have some BW17:33
dougwigahh, yes, sorry. let's talk offline immediately after this ends?17:33
*** julim has quit IRC17:33
*** jmckind has quit IRC17:33
*** IlyaG has quit IRC17:33
pc_mI'm on PTO today. Connecting via phone.17:34
dougwigok, when are you back?17:34
pc_mYou can email, if desired17:34
dougwigok17:34
pc_mTomorrow17:34
dougwiganything else?  otherwise i'll let you get back to pto.17:35
* HenryG walks in late17:35
* dougwig waves.17:35
dougwigHenryG: is your db base review getting an update soon?17:36
pc_mNot from me. Items in the open discussion in agenda can be discussed at some point.17:36
dougwigall of mine are broken with merge conflicts, which will be addressed today.17:36
*** unicell has quit IRC17:36
HenryGI'll try to update the db patch soon17:36
*** vtech has joined #openstack-meeting-417:38
dougwigok, let's recover some of our morning.17:38
dougwignext week, we need to talk about how to deal with the agent goo.17:38
HenryGHow about the lbaas patch? Is it ready?17:38
dougwigwhich one?17:38
pc_mTTYL17:39
HenryGhttps://review.openstack.org/25326317:39
*** Swami has joined #openstack-meeting-417:39
HenryGIt depends on the neutron patch17:39
dougwigit's ready, but it's chained off the neutron patch where you want the constants and exceptions files broken up, and that fix is going to be crazy time consuming. i'm going to try to do it today.17:39
dougwigi've been half wondering if we should two-step the neutron patch.17:40
HenryGAh yes, do my comments make any sense?17:40
HenryGI recall being very tired when reviewing that17:41
*** harshs has quit IRC17:41
dougwigyes... and i've been very torn in my response.  on the one hand, neutron.common can cease to exist.  but... can it? are we lib'ing even things that only neutron itself uses?  is there really nothing "common" that is purely neutron only? i've been going in circles.17:41
dougwigand then i wonder if it's too big a change to do all at once.  and then i wonder if i'm just being lazy and don't want to do it.  and then i'm due for more cold meds.17:42
*** julim has joined #openstack-meeting-417:42
HenryGand them armax will -2 your patch17:42
*** fnaval has quit IRC17:43
pc_m:)17:44
dougwigif we only fired dc on affected constants/exceptions, but left the others in place, would that work as an intermediate step?17:44
dougwigand no, i will *not* list them all individually in that case.17:44
HenryGdougwig: if you can figure out how to do that, I would love to see it17:44
armaxwhat did I do?17:45
*** belmoreira has quit IRC17:45
dougwigyou were just being your lovable self.17:45
dougwigHenryG: you poked the bear. you never poke the bear.17:45
*** iyamahat has quit IRC17:46
*** yamahata has quit IRC17:46
dougwigalright, anything else, or are we done?17:47
HenryGnothing more from me17:47
dougwigok, then let's reclaim some time and update those patches.!  :)17:47
dougwig#endmeeting17:48
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:48
openstackMeeting ended Wed Feb  3 17:48:01 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-02-03-17.31.html17:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-02-03-17.31.txt17:48
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_lib/2016/networking_lib.2016-02-03-17.31.log.html17:48
*** hdaniel has quit IRC17:48
*** SimonChung has joined #openstack-meeting-417:53
*** mdnadeem1 has quit IRC17:53
*** IlyaG has joined #openstack-meeting-417:56
*** Sukhdev has quit IRC17:59
*** pbourke has quit IRC18:00
*** pbourke has joined #openstack-meeting-418:00
*** fnaval has joined #openstack-meeting-418:03
*** fnaval_ has joined #openstack-meeting-418:05
*** bnemec has quit IRC18:05
*** evgenyf has joined #openstack-meeting-418:06
*** minwang2 has joined #openstack-meeting-418:07
*** banix has joined #openstack-meeting-418:07
*** fnaval has quit IRC18:08
*** ppetit has quit IRC18:11
*** uck has quit IRC18:13
*** [1]evgenyf has joined #openstack-meeting-418:22
*** evgenyf has quit IRC18:22
*** [1]evgenyf is now known as evgenyf18:22
*** pmesserl_ has joined #openstack-meeting-418:24
*** Jeffrey4l has quit IRC18:25
*** pmesserli has quit IRC18:27
*** IlyaG has quit IRC18:28
*** IlyaG has joined #openstack-meeting-418:29
*** prashantD has quit IRC18:32
*** unicell has joined #openstack-meeting-418:33
*** iyamahat has joined #openstack-meeting-418:34
*** prashantD has joined #openstack-meeting-418:35
*** unicell1 has joined #openstack-meeting-418:36
*** fitoduarte has quit IRC18:37
*** unicell1 has quit IRC18:37
*** unicell has quit IRC18:37
*** unicell1 has joined #openstack-meeting-418:37
*** unicell1 has quit IRC18:39
*** unicell has joined #openstack-meeting-418:39
*** pmesserl_ has quit IRC18:39
*** pmesserli has joined #openstack-meeting-418:40
*** evgenyf has quit IRC18:43
*** yamahata has joined #openstack-meeting-418:43
*** evgenyf has joined #openstack-meeting-418:47
*** sdake has quit IRC18:47
*** akwasnie has quit IRC18:49
*** akwasnie has joined #openstack-meeting-418:50
*** hvprash has joined #openstack-meeting-418:51
*** deva_ has joined #openstack-meeting-418:51
*** dshakhray has quit IRC18:53
*** iyamahat has quit IRC18:56
*** iyamahat has joined #openstack-meeting-418:56
*** iyamahat has quit IRC18:58
*** deva_ has quit IRC19:00
*** rockyg has joined #openstack-meeting-419:00
*** harshs has joined #openstack-meeting-419:00
*** s3wong has joined #openstack-meeting-419:03
*** julim has quit IRC19:04
*** julim has joined #openstack-meeting-419:06
*** akwasnie has quit IRC19:06
*** TrumpetsHerald has joined #openstack-meeting-419:08
*** kebray has quit IRC19:09
TrumpetsHeraldAm I in the right place for the OsOps meeting?19:10
*** jmckind has joined #openstack-meeting-419:11
*** fnaval_ is now known as fnaval19:12
*** uck has joined #openstack-meeting-419:13
*** Sukhdev has joined #openstack-meeting-419:14
*** kebray has joined #openstack-meeting-419:15
*** deva_ has joined #openstack-meeting-419:16
TrumpetsHeraldIs there no OsOps meeting today?19:17
*** uck has quit IRC19:18
*** lbragstad has left #openstack-meeting-419:20
*** deva_ has quit IRC19:23
*** bpokorny_ has joined #openstack-meeting-419:29
*** bpokorny_ has quit IRC19:30
*** bpokorny_ has joined #openstack-meeting-419:30
*** bpokorny has quit IRC19:32
*** bpokorny_ has quit IRC19:32
*** bpokorny has joined #openstack-meeting-419:34
*** IlyaG has quit IRC19:36
*** ihrachys has joined #openstack-meeting-419:37
*** Sukhdev has quit IRC19:44
*** sdake has joined #openstack-meeting-419:47
*** galstrom_zzz is now known as galstrom19:48
*** galstrom is now known as galstrom_zzz19:48
*** paul-carlton1 has quit IRC19:51
*** javeriak has joined #openstack-meeting-419:57
*** kebray has quit IRC19:57
*** kebray has joined #openstack-meeting-419:59
*** baoli_ has quit IRC19:59
*** javeriak_ has quit IRC20:00
*** sdake_ has joined #openstack-meeting-420:00
*** uck has joined #openstack-meeting-420:02
*** sdake has quit IRC20:03
*** hvprash has quit IRC20:04
*** wojdev has joined #openstack-meeting-420:05
*** wojdev has quit IRC20:05
*** minwang2_ has joined #openstack-meeting-420:06
*** minwang2 has quit IRC20:08
*** minwang2_ is now known as minwang220:08
*** ihrachys has quit IRC20:10
*** javeriak has quit IRC20:11
*** fitoduarte has joined #openstack-meeting-420:23
anteayaTrumpetsHerald: is this the meeting you were looking for? http://eavesdrop.openstack.org/#OpenStack_OSOps/Monitoring_and_Tools_Working_Group20:23
anteayait is an odd week, running date +%V gives me 0520:26
anteayathere should have been a meeting or communication about it20:26
*** Sukhdev has joined #openstack-meeting-420:28
*** galstrom_zzz is now known as galstrom20:31
*** galstrom is now known as galstrom_zzz20:40
*** hvprash has joined #openstack-meeting-420:42
*** stvnoyes has left #openstack-meeting-420:44
*** sridhar_ram has quit IRC20:47
*** dtardivel has quit IRC20:48
*** lbragstad has joined #openstack-meeting-420:53
*** dims has quit IRC20:56
*** hvprash has quit IRC20:59
*** evgenyf has quit IRC21:01
*** kavit has joined #openstack-meeting-421:02
rbradforrockyg, ping21:03
rockygOops, rbradfor, I'm here!21:04
rockygforgot.21:04
rockygGot lost on the internet.  Hhave a cold, so not as sharp as I sometimes am.21:04
rockygjokke_, you here?21:04
rockyg#startmeeting log_wg21:05
*** galstrom_zzz is now known as galstrom21:05
openstackMeeting started Wed Feb  3 21:05:15 2016 UTC and is due to finish in 60 minutes.  The chair is rockyg. Information about MeetBot at http://wiki.debian.org/MeetBot.21:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:05
*** openstack changes topic to " (Meeting topic: log_wg)"21:05
openstackThe meeting name has been set to 'log_wg'21:05
rockyg#topic Ops midcycle - config opts session21:05
*** openstack changes topic to "Ops midcycle - config opts session (Meeting topic: log_wg)"21:05
*** dims has joined #openstack-meeting-421:05
rockygrbradfor, I'm socializing the work you are doing and want to get whatever info you need to help make this both as smooth and as useful as possible21:06
rbradforok, I saw your session proposed in the thread21:06
rockygYeah.  I had proposed it earlier, but it got lost in Tom's mailbox.  He thinks it's a good topic.21:07
* rbradfor looking for that mail again21:07
*** baoli has joined #openstack-meeting-421:07
rockygAlso, did I mention that all the config docs got converted to RST already?  It means we can make the docs happen.21:08
rockygThe problem I see with the docs is that each project does the config opts section differently21:08
rbradforrockyg, do you have reference links of "different"21:09
*** TrumpetsHerald has quit IRC21:09
rockygSo, if you take Oslo as the "default" way to do them, take a look at Nova's section.  Lemme find the link21:10
rbradfor#link http://docs.openstack.org/developer/oslo.log/opts.html21:10
rbradfor#link http://docs.openstack.org/developer/oslo.messaging/opts.html21:11
rbradfor#link http://docs.openstack.org/developer/glance/opts.html21:11
rbradforhere are a few developer examples21:11
rockyghttp://docs.openstack.org/liberty/config-reference/content/section_compute-config-samples.html21:11
rockygAh.  You're looking at the dev docs.  The config ref is the one I was looking at.21:12
rbradforDo you  know how these are generated?21:12
rockygI think it's mostly a cut and paste and someone on the docs team did it.21:13
rockyg*topic Docs for config opts21:13
rockyg#topic Docs for config opts21:14
*** openstack changes topic to "Docs for config opts (Meeting topic: log_wg)"21:14
rockyglemme find the responsible docs sup ptl....21:14
rbradforrockyg, well if you can facilitate who in the team is doing it, and what the source copy is, that helps in validating the differences21:14
*** clayton has quit IRC21:14
rbradforI am all for having the documentation driven from the oslo-config-generator and sphinxext (for RST) version.21:15
rbradforyour example I expect is a hand crafted file21:16
rockygYup.21:16
*** galstrom is now known as galstrom_zzz21:16
*** hvprash has joined #openstack-meeting-421:17
rockygI think we need to connect with the guy in charge of this particular doc and show him how it works.  Some of the docs guys code, some don't.21:17
*** Swami has quit IRC21:17
rbradfori think having an etherpad of what links we are referring to that are configuration option related (across all sources, dev, ops, conf guide) is a start21:17
rbradforthen the source of said information, which may determine cut/paste or duplication21:18
rbradforof producing.21:18
rbradforthe goal of inconsistencies is to have only source of information.21:18
rbradforof removing ..21:18
rockygyou wanna create the etherpad, or should I?  We've got lots of links and I just got the link to the config guide docs team21:20
rbradforI think it should probably be part of your config guide docs.21:20
rbradforagain, identifying all the different sources in documentation, e.g. a projects config21:21
rbradforand then working on reducing the varying versions to be consistent21:21
rockygYah.  But etherpad leads to config guide doc, not part of.....21:21
rockygI can certainly collect all the places I can find, categorize and have it ready for the ops midcycle...21:22
*** Swami has joined #openstack-meeting-421:23
rbradforwell if your trying to present a case to have a config guide, it helps to source the existing versions of document for reference.  you want to justify why each existing docs are incomplete or complex or duplicating21:23
rockygThere already is the config ref.  do we want another doc or just better organize the current, with more info and single source of truth?21:24
rbradforI can certainly help in ensuring configuration documentation (and sample config files) get generated, and hopefully we can get projects to be consistent about it.21:24
rockygBut then, we'd also have to make sure that dev docs match user docs, too.21:25
rbradforI thought you were creating a new config reference. Does it exist now?21:25
*** hvprash has quit IRC21:25
rockygYup.  Thats the first link I pointed you to with the sample configs21:25
rockygAnd here's the link to the team:  https://wiki.openstack.org/wiki/Documentation/ConfigRef21:26
*** julim has quit IRC21:27
rockygIn fact, there's even a todo to get the opts section(s) better.21:27
rbradforso you mentioned "Convert the Configuration Reference from DocBook to RST" is done.21:28
rockygYup.21:28
rockygI saw that in one of the What's Up Doc emails.21:28
rockygWhich means that your generator stuff can just slide in there....21:29
rbradforok, so looking at blueprint at https://blueprints.launchpad.net/openstack-manuals/+spec/config-ref-rst and an example recent review at https://review.openstack.org/#/c/259889/21:29
rbradforwe are in openstack/openstack-manuals repo and config-reference21:30
rbradforI don't see a gate that provides a link to physically show what the changes look like.21:31
rockygHmm.21:31
rbradforlet me give you an example I understand21:31
rbradforAdd Configuration Options to Glance Developer Docs - https://review.openstack.org/#/c/270920/21:32
rbradforYou can see the proposed documentation generated (as in review) at http://docs-draft.openstack.org/20/270920/4/check/gate-glance-docs/0e8ef17//doc/build/html/21:32
rbradforwhen that review is merged, this becomes http://docs.openstack.org/developer/glance/21:32
rbradforI do not know the workflow of openstack-manuals21:33
rockygso, you can see a gate build I think.....gate-openstack-manuals-tox-doc-publish-checkbuild in the list of jobs, but the link is gone21:33
rbradforI saw that21:34
rockygAnd the wiki points to kilo stuff....hmm....Lemme track back to main docs wiki page21:35
rbradforLiberty -- http://docs.openstack.org/liberty/config-reference/content/config_overview.html21:35
rbradformitaka links don't seem to work21:35
rockygSo, there are directions to build the "patch" locally:  http://docs.openstack.org/contributor-guide/docs-review.html21:37
rockygIt's down a bit on the page.  I'm at home so don't have the setup for repos an builds....21:38
rbradfordo Mitaka docs get published on the site before it's officially released?21:39
*** thingee has quit IRC21:41
rockygNo.  Yhey put the links up at release, which is about a week after code release.  But I think they have internal links for devs to review sometime after M321:41
rbradforok, well what can I do from the developer docs perspective to generate docs that are incorporated.21:42
*** clayton has joined #openstack-meeting-421:43
rockygOk.  Also found this note on the docs wiki:  "The Configuration Reference and the Networking Guide are versioned, all other guides are continuously published."21:43
rbradforand as I look back at links, how does this also relate to the Openstack Operations Guide - http://docs.openstack.org/openstack-ops/content/21:43
rbradformaybe that's totally separate21:44
rockygI'll see if I can connect with Gauvain and maybe get some sync up happening.  I'll put togehter an etherpad with all these links, plus others, and let you know....21:44
rbradforThere is a "Configuration Reference" link on the home page ,http://docs.openstack.org/ it goes to http://docs.openstack.org/liberty/config-reference/content/21:44
rockygYup.  That's the versioned copy.21:45
rbradforso, if the conversion to RST is complete, the question is does it look a lot like the Liberty version?21:45
rbradforand if the content is not being generated, how is being sourced, e.g. cut/paste as you proposed21:45
rbradforand how can we then better generate the configuration options and configuration sample files.21:46
rbradforHow it's then ordered or categorized into the configuration guide, e.g. a global logging session is something for the docs team to decide on, hopefully based on your recommendations21:46
rockygHere's an interesting link on the docs wiki:  http://git.openstack.org/cgit/openstack/openstack-doc-tools/tree/autogenerate_config_docs/README.rst21:47
rbradforagain, I'm not familar with the docs team way of doing things.21:48
rockygYeahl  I can use the ops midcycle to find out what besides logging they want in a more "global' chapter.  I'm not enough into docs either.  I fixed a bug or two there,  but I just edited the xml back then and left the rest to the docs team.21:49
rockygI'll hook up with them, show them the dev config doc stuff and see where it goes from there.  Might have the guy for config doc come to one of our meetings.21:50
rockygLike to get this in Mitaka version.21:50
*** FallenPegasus has quit IRC21:51
rockygHow about I put together an etherpad, talk to Gauvain, have him review the etherpad, then you, and see if we can send to the dev mailing list to get comments, get them to do their part in their projects?21:52
*** FallenPegasus has joined #openstack-meeting-421:52
rbradforI think verifying the source of information used in the config guide first is important.21:53
rockygOK.  I'll connect with docs folks.21:53
*** salv-orlando has joined #openstack-meeting-421:54
rockygRight after I put all these links on an etherpad for reference.21:54
*** FallenPegasus has quit IRC21:54
rockyg#action Rocky to collect up config links that reference config opts and circle back to Docs to see how docs generate their config info21:55
rockygGood enough for today?21:55
rbradforsounds good21:55
rockyg#topic Open discussion21:56
*** openstack changes topic to "Open discussion (Meeting topic: log_wg)"21:56
rockygI got nuthin else.21:56
rbradforno, still working on removing some deprecated options (so they get removed from the docs)21:56
*** salv-orl_ has quit IRC21:56
rockygOK.  I'll let you get back to it, then.  It will be nice to see some of them go away.21:57
rockygThanks so much!21:57
rockyg#endmeeting21:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:57
openstackMeeting ended Wed Feb  3 21:57:30 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-02-03-21.05.html21:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-02-03-21.05.txt21:57
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-02-03-21.05.log.html21:57
*** suhani has joined #openstack-meeting-421:57
*** prashantD has quit IRC22:05
*** sdake_ has quit IRC22:06
*** woodard_ has joined #openstack-meeting-422:07
*** woodard has quit IRC22:10
*** woodard_ has quit IRC22:11
rockygrbradfor, you still around?  Got a working link for the draft doc....22:12
*** dims_ has joined #openstack-meeting-422:17
*** hvprash has joined #openstack-meeting-422:20
*** dims has quit IRC22:21
*** uck has quit IRC22:21
*** spzala has quit IRC22:22
*** vhoward has quit IRC22:23
*** spzala has joined #openstack-meeting-422:23
*** prashantD has joined #openstack-meeting-422:24
suhani#openstack-cinder22:26
*** banix has quit IRC22:26
*** dims_ has quit IRC22:27
*** spzala has quit IRC22:28
*** hvprash has quit IRC22:29
*** sdake has joined #openstack-meeting-422:32
*** sdake has quit IRC22:44
*** uck has joined #openstack-meeting-422:52
*** neelashah has quit IRC22:53
*** vtech has quit IRC22:59
*** piet has quit IRC23:01
*** spzala_ has joined #openstack-meeting-423:01
*** jmckind has quit IRC23:04
*** spzala_ has quit IRC23:06
*** ninag has quit IRC23:07
*** ninag has joined #openstack-meeting-423:07
*** Sukhdev has quit IRC23:10
*** pbourke has quit IRC23:11
*** ninag has quit IRC23:12
*** pbourke has joined #openstack-meeting-423:15
*** Sukhdev has joined #openstack-meeting-423:18
*** ninag has joined #openstack-meeting-423:18
*** klamath has quit IRC23:27
*** spotz is now known as spotz_zzz23:29
*** sridhar_ram has joined #openstack-meeting-423:30
*** sigmavirus24 is now known as sigmavirus24_awa23:30
*** baoli has quit IRC23:33
*** bobh has quit IRC23:33
*** docaedo has joined #openstack-meeting-423:36
*** baoli has joined #openstack-meeting-423:36
*** angdraug has joined #openstack-meeting-423:40
*** baoli has quit IRC23:41
*** blahRus has quit IRC23:42
*** FallenPegasus has joined #openstack-meeting-423:45
*** Hunner has quit IRC23:55
*** crinkle has quit IRC23:55
*** mentat has quit IRC23:56
*** Hunner has joined #openstack-meeting-423:56
*** Hunner has quit IRC23:56
*** Hunner has joined #openstack-meeting-423:56
*** crinkle has joined #openstack-meeting-423:57
*** mentat has joined #openstack-meeting-423:57
*** SimonChung1 has joined #openstack-meeting-423:57
*** SimonChung has quit IRC23:57

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