Wednesday, 2016-02-24

*** piet has joined #openstack-meeting-400:01
*** FallenPegasus has quit IRC00:02
*** sdake has quit IRC00:04
*** darrenc_afk is now known as darrenc00:05
*** yamamoto_ has joined #openstack-meeting-400:05
*** _sarob has joined #openstack-meeting-400:07
*** LouisF has quit IRC00:08
*** _sarob has quit IRC00:11
*** yamamoto_ has quit IRC00:14
*** markvoelker has quit IRC00:15
*** Sukhdev has quit IRC00:16
*** Sukhdev has joined #openstack-meeting-400:17
*** Sukhdev has quit IRC00:18
*** prashantD has quit IRC00:19
*** SimonChung1 has quit IRC00:19
*** prashantD has joined #openstack-meeting-400:22
*** vhoward has joined #openstack-meeting-400:31
*** prashantD has quit IRC00:31
*** SimonChung has joined #openstack-meeting-400:33
*** bobh has quit IRC00:34
*** sridhar_ram has quit IRC00:38
*** SimonChung1 has joined #openstack-meeting-400:45
*** SimonChung has quit IRC00:45
*** markvoelker has joined #openstack-meeting-400:46
*** xingchao has joined #openstack-meeting-400:48
*** bpokorny_ has joined #openstack-meeting-400:51
*** bpokorny_ has quit IRC00:51
*** britthouser has quit IRC00:51
*** xingchao has quit IRC00:53
*** britthouser has joined #openstack-meeting-400:54
*** bpokorny has quit IRC00:54
*** prithiv has quit IRC00:56
*** britthouser has quit IRC00:57
*** blahRus has quit IRC01:00
*** minwang2 has quit IRC01:04
*** minwang2 has joined #openstack-meeting-401:06
*** dtardivel has quit IRC01:08
*** gongysh has joined #openstack-meeting-401:08
*** britthouser has joined #openstack-meeting-401:12
*** SimonChung1 has quit IRC01:13
*** Sukhdev has joined #openstack-meeting-401:14
*** yamamoto_ has joined #openstack-meeting-401:14
*** baohua has joined #openstack-meeting-401:14
*** britthou_ has joined #openstack-meeting-401:16
*** britthouser has quit IRC01:17
*** pmesserl_ has quit IRC01:18
*** yamamoto_ has quit IRC01:19
*** yamamoto_ has joined #openstack-meeting-401:20
*** vhoward has quit IRC01:21
*** armax has joined #openstack-meeting-401:21
*** minwang2 has quit IRC01:24
*** yifei has quit IRC01:27
*** v1k0d3n_ has joined #openstack-meeting-401:35
*** sridhar_ram has joined #openstack-meeting-401:35
*** severion has quit IRC01:37
*** iceyao has joined #openstack-meeting-401:49
*** xingchao has joined #openstack-meeting-401:49
*** sridhar_ram has quit IRC01:51
*** sdake has joined #openstack-meeting-401:51
*** piet has quit IRC01:53
*** xingchao has quit IRC01:55
*** sdake_ has joined #openstack-meeting-401:55
*** sdake has quit IRC01:56
*** baoli has joined #openstack-meeting-401:58
*** iyamahat has quit IRC01:58
*** Sukhdev has quit IRC01:59
*** dims has quit IRC01:59
*** yamamoto_ has quit IRC02:00
*** yamahata has quit IRC02:00
*** Sukhdev has joined #openstack-meeting-402:01
*** xingchao has joined #openstack-meeting-402:01
*** vishwanathj has quit IRC02:06
*** zhurong has joined #openstack-meeting-402:06
*** pcaruana has quit IRC02:07
*** sdake_ has quit IRC02:10
*** woodard_ has quit IRC02:11
*** xingchao has quit IRC02:17
*** pcaruana has joined #openstack-meeting-402:19
*** xingchao has joined #openstack-meeting-402:20
*** sdake has joined #openstack-meeting-402:20
*** britthou_ has quit IRC02:22
*** britthouser has joined #openstack-meeting-402:23
*** xingchao has quit IRC02:25
*** lakshmiS has quit IRC02:25
*** vishwanathj has joined #openstack-meeting-402:26
*** iceyao_ has joined #openstack-meeting-402:26
*** vishwana_ has joined #openstack-meeting-402:28
*** iceyao has quit IRC02:30
*** vishwanathj has quit IRC02:31
*** tfukushima has joined #openstack-meeting-402:33
*** emagana has joined #openstack-meeting-402:41
*** sdake has quit IRC02:43
*** yamamoto_ has joined #openstack-meeting-402:47
*** xingchao has joined #openstack-meeting-402:54
*** xingchao has quit IRC02:54
*** xingchao has joined #openstack-meeting-402:55
*** jmcbride has joined #openstack-meeting-402:56
*** sridhar_ram has joined #openstack-meeting-402:59
*** s3wong has quit IRC03:00
*** pcaruana has quit IRC03:01
*** gongysh has quit IRC03:02
emaganaHI!03:04
emaganaI was expecting a User Committee Meeting, anyone attending the same?03:05
*** baohua has quit IRC03:12
*** sdake has joined #openstack-meeting-403:13
*** dims has joined #openstack-meeting-403:13
*** emagana has quit IRC03:13
*** baohua has joined #openstack-meeting-403:13
*** avarner has quit IRC03:14
*** baohua_ has joined #openstack-meeting-403:15
*** pcaruana has joined #openstack-meeting-403:16
*** sdake_ has joined #openstack-meeting-403:16
*** baohua_ has quit IRC03:16
*** baohua has quit IRC03:17
*** bobh has joined #openstack-meeting-403:17
*** baohua has joined #openstack-meeting-403:17
*** sdake has quit IRC03:18
*** gongysh has joined #openstack-meeting-403:19
*** rob__ has quit IRC03:20
*** rob__ has joined #openstack-meeting-403:23
*** iyamahat has joined #openstack-meeting-403:23
*** salv-orlando has joined #openstack-meeting-403:26
*** tfukushima has quit IRC03:27
*** tfukushima has joined #openstack-meeting-403:28
*** salv-orlando has quit IRC03:28
*** salv-orl_ has quit IRC03:29
*** sridhar_ram has quit IRC03:33
*** unicell has quit IRC03:33
*** tfukushima has quit IRC03:39
*** watanabe_isao has quit IRC03:53
*** bobh has quit IRC03:53
*** iyamahat has quit IRC03:54
*** baoli has quit IRC03:55
*** yifei has joined #openstack-meeting-403:57
*** irenab has quit IRC03:59
*** irenab has joined #openstack-meeting-404:00
*** pcaruana has quit IRC04:01
*** sdake_ has quit IRC04:01
*** gongysh has quit IRC04:02
*** baoli has joined #openstack-meeting-404:03
*** neelashah has joined #openstack-meeting-404:04
*** jmcbride has quit IRC04:14
*** pcaruana has joined #openstack-meeting-404:15
*** thorst has joined #openstack-meeting-404:16
*** fnaval has quit IRC04:16
*** thorst has quit IRC04:20
*** thorst has joined #openstack-meeting-404:20
*** baohua has quit IRC04:21
*** baohua_ has joined #openstack-meeting-404:21
*** thorst has joined #openstack-meeting-404:21
*** baohua_ has quit IRC04:22
*** baohua has joined #openstack-meeting-404:23
*** baoli has quit IRC04:28
*** baoli has joined #openstack-meeting-404:29
*** thorst has quit IRC04:30
*** fnaval has joined #openstack-meeting-404:30
*** spzala has joined #openstack-meeting-404:37
*** baoli has quit IRC04:39
*** xingchao has quit IRC04:46
*** piet has joined #openstack-meeting-404:52
*** neelashah has quit IRC04:55
*** SimonChung has joined #openstack-meeting-404:59
*** sdake has joined #openstack-meeting-404:59
*** amotoki has joined #openstack-meeting-405:05
*** SimonChung1 has joined #openstack-meeting-405:06
*** SimonChung has quit IRC05:08
*** spzala has quit IRC05:09
*** minwang2 has joined #openstack-meeting-405:09
*** sdake has quit IRC05:14
*** unicell has joined #openstack-meeting-405:20
*** iyamahat has joined #openstack-meeting-405:25
*** thorst has joined #openstack-meeting-405:27
*** minwang2 has quit IRC05:28
*** thorst has quit IRC05:34
*** salv-orlando has joined #openstack-meeting-405:36
*** pcaruana has quit IRC05:38
*** Jeffrey4l has joined #openstack-meeting-405:44
*** dims has quit IRC05:48
*** salv-orlando has quit IRC05:49
*** pcaruana has joined #openstack-meeting-405:53
*** v1k0d3n_ has quit IRC05:53
*** v1k0d3n has joined #openstack-meeting-405:53
*** piet has quit IRC06:00
*** emagana has joined #openstack-meeting-406:00
*** dshakhray has joined #openstack-meeting-406:02
*** gongysh has joined #openstack-meeting-406:02
*** galstrom_zzz is now known as galstrom06:05
*** gongysh has quit IRC06:05
*** v1k0d3n_ has joined #openstack-meeting-406:06
*** v1k0d3n has quit IRC06:07
*** minwang2 has joined #openstack-meeting-406:14
*** irenab_ has joined #openstack-meeting-406:14
*** baohua has quit IRC06:15
*** baohua has joined #openstack-meeting-406:15
*** gongysh has joined #openstack-meeting-406:15
*** fawadkhaliq has joined #openstack-meeting-406:15
*** gongysh has quit IRC06:16
*** cemmason has joined #openstack-meeting-406:16
*** nkrinner has joined #openstack-meeting-406:16
*** irenab has quit IRC06:17
*** irenab_ is now known as irenab06:17
*** numans has joined #openstack-meeting-406:19
*** v1k0d3n_ has quit IRC06:20
*** xingchao has joined #openstack-meeting-406:21
*** openstack has joined #openstack-meeting-413:22
*** ChanServ sets mode: +o openstack13:22
*** dgonzalez has joined #openstack-meeting-413:22
*** Guest65788 has quit IRC13:25
*** rods has joined #openstack-meeting-413:26
*** dslevin has joined #openstack-meeting-413:29
*** dslevin has quit IRC13:29
*** dslevin has joined #openstack-meeting-413:31
*** dslevin has quit IRC13:31
*** dslevin has joined #openstack-meeting-413:33
*** javeriak_ has joined #openstack-meeting-413:33
*** javeriak has quit IRC13:34
*** ninag has joined #openstack-meeting-413:34
*** ninag has quit IRC13:37
*** ninag has joined #openstack-meeting-413:38
*** ninag has quit IRC13:39
*** dims has joined #openstack-meeting-413:40
*** ninag has joined #openstack-meeting-413:40
*** ninag has quit IRC13:44
*** ninag has joined #openstack-meeting-413:44
*** amotoki has joined #openstack-meeting-413:44
*** vhoward has joined #openstack-meeting-413:44
*** xingchao has joined #openstack-meeting-413:54
*** acabot_ has joined #openstack-meeting-413:54
*** acabot__ has joined #openstack-meeting-413:59
*** gampel has quit IRC13:59
acabot__#startmeeting watcher14:00
openstackMeeting started Wed Feb 24 14:00:09 2016 UTC and is due to finish in 60 minutes.  The chair is acabot__. 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: watcher)"14:00
openstackThe meeting name has been set to 'watcher'14:00
acabot__hi14:00
edleafe\o14:00
seanmurphyhi all14:00
*** gzhai has joined #openstack-meeting-414:00
jed56(O_O)14:00
brunograzhi14:00
*** vtech_ has joined #openstack-meeting-414:00
tkaczynskihi14:00
*** vincentfrancoise has joined #openstack-meeting-414:00
acabot__meeting agenda #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#02.2F24.2F201614:00
vtech_o/14:00
vincentfrancoiseo/14:00
tpeopleso/14:01
*** brunograz has quit IRC14:01
gzhaihi14:01
*** salv-orlando has joined #openstack-meeting-414:01
*** bruno_ has joined #openstack-meeting-414:01
*** bruno_ is now known as brunograz14:01
acabot__#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:01
dtardivelhi14:02
*** acabot_ has quit IRC14:02
acabot__#info dtardivel nominates vincentfrancoise as a Watcher core contributor14:02
acabot__we had a couple of +1 on the ML14:02
jed56even a +214:03
jed56:)14:03
gzhai+114:03
acabot__does anybody "dont want" vincentfrancoise as a core ? :-)14:03
gzhaivincent did a great job.14:03
acabot__I also think so14:04
tpeoples+114:04
*** piet has joined #openstack-meeting-414:04
acabot__#action dtardivel set vincentfrancoise as core contributor on watcher, python-watcherclient & watcher-dashboard14:04
dtardivelacabot__: done :)14:05
acabot__#info mid-cycle highlights have been shared through the ML14:05
vincentfrancoiseI was already core on watcher-dashboard since I was the one creating the project :)14:05
acabot__if I missed something important in the list please reply to it14:05
acabot__#link http://lists.openstack.org/pipermail/openstack-dev/2016-February/087174.html14:06
*** neelashah has joined #openstack-meeting-414:06
vincentfrancoiseBTW, maybe we should discuss on who is to be core on watcher-dashboard at some point14:06
acabot__true, do we have any candidate to become core on watcher-dashboard ?14:07
acabot__or we can do it through the ML14:07
acabot__today we only have vincentfrancoise right ?14:07
vincentfrancoiseFYI, dtardivel and I are the only core on watcher-dashboard14:07
acabot__ok14:07
*** salv-orlando has quit IRC14:08
acabot__tpeoples gzhai : do you want to be part of the watcher-dasboard core ?14:08
acabot__we can wait for more contributors related to horizon stuff14:09
gzhaiI want more time for watcher...14:09
tpeoplesdoubtful, i'm not all that interested in UI side / JS. let me have more of a look and get back to you14:09
*** vtech_ has quit IRC14:09
acabot__ok lets continue with vincentfrancoise & dtardivel as core for now14:10
acabot__any other annoucement from the team ?14:11
*** avarner_ has joined #openstack-meeting-414:11
vincentfrancoiseIt's just that we need to make sure we take this new project into account whenever writing new BPs14:11
*** avarner has quit IRC14:11
tpeoplesfor sure vincentfrancoise14:12
gzhaiI'll attend openstack hackathon in Chengdu, China. And ask for a slot for watcher presentation:)14:12
acabot__gzhai : great !14:12
*** bobh has joined #openstack-meeting-414:12
*** vmahe has joined #openstack-meeting-414:12
gzhaiWill use some previous slides to introduce watcher to China openstack community.14:13
vmahehi14:13
dtardivelwatcher-dashboard tagged 0.0.1 available  ( + online doc, + docker container image watcher/dashboard)14:13
tpeoplesi apologize for my lack of activity in the past week and a half. that is going to change.. jfyi if you were wondering where the heck i've been :(14:13
acabot__#info gzhai will try to introduce Watcher to an openstack hackathon in Chengdu, China14:13
*** pmesserl_ has joined #openstack-meeting-414:14
acabot__tpeoples : yes we thought you were in vacation :-D14:14
dtardivelgzhai: +114:14
*** pmesserl_ has quit IRC14:14
*** bobh has quit IRC14:14
*** pmesserl_ has joined #openstack-meeting-414:14
tpeoplesi had to move offices, lots of other stuff going on. like i said, it will change14:14
tpeoplesif not kick me out14:15
tpeoples:)14:15
acabot__dtardivel shouldn't we align versions between watcher, watcher-pythonclient and watcher-dashboard at some point ?14:15
*** julim has joined #openstack-meeting-414:15
tkaczynskitpeoples: no worries, I did the code review in the meantime and added some comments14:15
*** piet has quit IRC14:15
*** sdake has joined #openstack-meeting-414:15
*** piet has joined #openstack-meeting-414:16
dtardivelgzhai: what will be the number of your attendees ?14:16
gzhai30~40 in last year.14:16
acabot__#topic Review Action Items14:16
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:16
gzhaibig company in china, like Huawei, 99cloud.14:16
dtardivelacabot__: not necessary ...14:17
vincentfrancoisegzhai: nice!14:17
acabot__gzhai : I'm on the Huawei booth right now at Mobile World Congress ;-)14:17
gzhai:)14:17
tpeoplesdtardivel: because they should be able version agnostic? e.g., python-watcherclient should be able to interact with a watcher backend of a different version?14:17
gzhaiHuawei put a lot of resources for openstack.14:17
*** seanmurphy has quit IRC14:18
*** itisha has quit IRC14:19
*** seanmurphy has joined #openstack-meeting-414:19
acabot__tpeoples : as think that until we are in version 0.x, you need to get the latest version of each component to run Watcher, right ?14:20
dtardiveltpeoples: python-watcherclient should support different version of watcher API.14:20
vincentfrancoisetpeoples: I guess we just need to stabilize watcher-dashboard a little more before aligning the versions14:20
acabot__vincentfrancoise ok14:20
acabot__lets move on watcher specs14:20
tpeoplesacabot__: i think that is only true in these early stages where we aren't worrying about backwards compatibility. in the future that shouldn't be necessary14:21
jed56vincentfrancoise : we don't have to align the version14:21
tpeoples+1 vincentfrancoise14:21
vincentfrancoiseThe 0.0.1 tag was put just so we can generate the docker containers, otherwise we wouldn't have tagged it14:21
jed56we can but this is not mandatory14:21
jed56since we have the api compatibility14:21
acabot__i'm just concerned about the distance between 0.0.1 & 0.23 :-)14:21
jed56this is a problem ? :)14:22
*** severion has quit IRC14:22
*** iceyao_ has joined #openstack-meeting-414:22
vincentfrancoiseI reckon we can deal with in Newton if needed14:22
*** severion has joined #openstack-meeting-414:22
acabot__jed56 : not really, just that 0.1 could have been better ;-)14:22
dtardivelacabot: watcher, python-watcherclient and watcher-dashboard are independent project, with independent life-cycle. We just implemented and pushed a beta PROD version of the dashboard, so this is the reason of version 0.0.1 today.14:23
jed56yes but our 0.1 is quite stable14:23
jed56:)14:23
*** severion has quit IRC14:23
acabot__jed56 dtardivel : Ok i'm fine with that guys14:23
jed56one commit => 0.0.1  : )14:24
*** iceyao has quit IRC14:24
*** baohua has quit IRC14:24
jed56two commit 0.114:24
jed56lol14:24
*** v1k0d3n has joined #openstack-meeting-414:24
acabot__#info Efficacy indicators specs has been merged too fast and we realized that it needs improvements14:24
jed56three commit 1.0 stable14:24
gzhai:)14:25
acabot__so there is a new review open https://review.openstack.org/#/c/283449/, sorry for the confusion14:25
acabot__we have 2 specs open for a long time now (ZHAW strategy & workload balance strategy)14:25
gzhaiacabot__: I'm looking at this.14:25
*** evgenyf has quit IRC14:26
acabot__I suggest to merge them by EOW14:26
acabot__seanmurphy vtech : what do you think ?14:26
seanmurphyto merge the 2 strategies?14:26
seanmurphyi saw this in the agenda14:26
seanmurphywe are doing our implementation as you might have seen14:26
seanmurphythere is the point that they seem to be contradictory14:27
seanmurphyat least at the initial glance14:27
acabot__no no sorry14:27
seanmurphyone focused on consolidation and one focuses on even distribution of load iiuc14:27
acabot__not merge the 2 strategies into one but having both specs merged in gerrit :-)14:27
seanmurphyok14:28
acabot__my sentence is confusing :-)14:28
seanmurphyi don’t understand the advantages/disadvantages of this tbh14:28
*** cemmason1 has joined #openstack-meeting-414:28
seanmurphyi did not read the spec for the workload balance strategy14:28
gzhaiWho can help to review workload balance?14:29
acabot__seanmurphy : could you have a look at it by EOW ?14:29
seanmurphyform our selfish perspective, we would say ‘what is the benefit of this?'14:29
seanmurphyand also ‘does it mean we would have to change our implementation14:29
seanmurphyfor sure i can look14:29
*** cemmason has quit IRC14:30
acabot__seanmurphy : not sure to follow you, are you taking about the process of merging the spec in watcher-spec repo ?14:30
seanmurphynot that we don’t want to be constructive, but i’m just unclear on what the point is/what the benefit is14:30
seanmurphyah - sorry14:30
seanmurphyconfusion - my bad14:30
seanmurphyso you’re not talking abt merging them into each other14:30
seanmurphyright14:30
seanmurphyok - if it’s just a q of whether our strategy can be merged by eow14:31
seanmurphythen this is doable14:31
acabot__seanmurphy: ok back on our feet14:31
jed56woah I was lost :)14:31
vincentfrancoise+114:31
seanmurphyregarding the workload balance issue - we can provide a review of this14:32
acabot__#action seanmurphy acabot review specs https://review.openstack.org/#/c/271028/ & https://review.openstack.org/#/c/276586/ by EOW14:32
jed56you can add me14:33
acabot__gzhai : I think we need more reviews on https://review.openstack.org/#/c/274688/, what do you think ?14:34
acabot__#action jed56 review specs https://review.openstack.org/#/c/271028/ & https://review.openstack.org/#/c/276586/ by EOW14:34
gzhai+114:34
*** vhoward has quit IRC14:34
acabot__vmahe I think we should look at the impact we discussed on efficacy indicators on the input parameters specs14:36
jed56+114:36
vmahe+14:37
vmahe+114:37
acabot__#action vmahe review https://review.openstack.org/#/c/274688/14:37
*** vhoward has joined #openstack-meeting-414:37
acabot__we have a couple of BPs with high priority that needs specs14:37
acabot__tomasz is setting up devstack before starting the scoring module14:38
acabot__tpeoples: what about the objects wrapper ?14:38
*** gampel has joined #openstack-meeting-414:38
jed56tomasz: did you success to setup devstack ?14:38
tpeoplesacabot__: i *will* get a spec for that in next 2 days14:38
*** vhoward_ has joined #openstack-meeting-414:38
tpeoplesi saw tomasz' comments on the devstack review... i will make a few more updates there14:39
acabot__#action tpeoples submit a drafted spec for https://blueprints.launchpad.net/watcher/+spec/cluster-model-objects-wrapper14:39
acabot__thx14:39
dtardiveltpeoples: I will review it after14:40
acabot__I will submit a spec for https://blueprints.launchpad.net/watcher/+spec/select-destinations-filter14:40
*** jmcbride has joined #openstack-meeting-414:40
tkaczynskijed56 I'm very close. I have controller + compute nodes, able to boot vm, but live migration is not working. troubleshooting it now, got some help from other openstack contributors here in Gdansk14:40
acabot__#action acabot submit a drafted spec for https://blueprints.launchpad.net/watcher/+spec/select-destinations-filter14:40
dtardiveltkaczynski: maybe, we can help you on live migration. Is it on NFS setup ?14:41
tpeoplestkaczynski: are you using multiple virtualbox VMs? just curious14:41
acabot__we can jump to devstack doc improvements ;-)14:41
*** vhoward has quit IRC14:42
tkaczynskiyes, NFS is working fine. there was some unclear error in the n-cpu logs, we suspect libvirt or qemu problem, but need to investigate14:42
tpeoplestkaczynski: did you set up SSH keys?14:42
tkaczynskiyes, of course. and confirmed with ssh to/from stack/root14:43
tpeopleshmm ok14:43
tkaczynskiand yes, using 2 virtualbox VMs14:43
tpeoplescool14:43
acabot__#info 17 bug fixes are in review, so we need reviewers14:44
tkaczynskionce I have it configured, I plan to setup the whole thing again and document it, so I can repeat that process14:44
tpeoples#action tpeoples review14:44
acabot__I assume that with vincentfrancoise as core it will be easier to merge them14:44
tpeoplestkaczynski: that would be awesome if we add that to our docs14:44
acabot__tpeoples: +114:45
acabot__nothing new on python-watcherclient14:46
acabot__#info initial commit for watcher-dashboard has been merged14:46
acabot__#action acabot set-up launchpad for watcher-dashboard14:46
acabot__#topic Blueprint/Bug Review and Discussion14:47
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:47
*** armax has quit IRC14:47
brunograztkaczynski: we have an old blog post about setting live migration in Openstack - it might be helpful #link https://blog.zhaw.ch/icclab/setting-up-live-migration-in-openstack-icehouse/14:48
acabot__we need to start implementing workload balance strategy if we want to demonstrate it in Austin14:48
acabot__gzhai : do you have any update on junjie stuff ?14:48
tkaczynskibrunograz thanks, I'll definitely have a look there14:48
*** jmckind has joined #openstack-meeting-414:49
gzhaiacabot__: He is working on the specs.14:49
gzhaiwe are preparing the algothm to start working on workload migration spec.14:49
acabot__did he starts implementing or not yet ?14:50
gzhaiacabot__: not yet. We will start soon.14:51
gzhaiAnd want to more review for the spec to avoid unnecessary work:)14:52
jed56gzhai i will14:52
gzhaijed56: thanks14:53
*** acabot_ has joined #openstack-meeting-414:54
jed56ping acabot_14:54
acabot_back14:54
acabot_sorry wifi disconnection14:54
acabot_#topic Open Discussion14:54
acabot_#topic Open Discussion14:54
*** acabot__ has quit IRC14:55
acabot_ping jed5614:55
seanmurphywe have a blog post which we’re writing in which we mention watcher and the fact that we’re contributing to it - it’s for an eu proj14:55
acabot_seanmurphy: looks great14:56
acabot_#info seanmurphy will write a blog post mentionning Watcher contributions14:56
seanmurphyyep - it’s already drafted - it will go out this week14:56
dtardivelacabot_: is implementation of Watcher policy.json file mandatory for m3 ?14:56
acabot_dtardivel: no its not14:57
acabot_not in my mitaka-3 list...14:57
acabot_you mean this one https://blueprints.launchpad.net/watcher/+spec/watcher-policies ?14:57
acabot_its not targeted yet so Newton14:58
*** rbak has joined #openstack-meeting-414:58
dtardivelacabot_: yes I do14:58
*** dslevin has left #openstack-meeting-414:58
*** sigmavirus24_awa is now known as sigmavirus2414:58
acabot_thank you guys14:59
tpeoplesttyl14:59
*** blahRus has joined #openstack-meeting-414:59
seanmurphyttyl14:59
acabot_bye14:59
brunograzbye14:59
dtardiveladiós Antoine14:59
vincentfrancoisebye14:59
gzhaibye14:59
jed56bye14:59
edleafebye14:59
acabot_#endmeeting14:59
tkaczynskibye14:59
*** gzhai has left #openstack-meeting-415:00
*** armax has joined #openstack-meeting-415:01
edleafeacabot_: you have to #endmeeting with the same nick you started it with15:01
edleafee.g., 'acabot__' (two underscores)15:01
acabot_right15:02
*** krtaylor has quit IRC15:02
*** acabot_ is now known as acabot__15:02
acabot__#endmeeting15:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:02
openstackMeeting ended Wed Feb 24 15:02:55 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-02-24-14.00.html15:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-02-24-14.00.txt15:03
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2016/watcher.2016-02-24-14.00.log.html15:03
acabot__edleafe : thx15:03
edleafeacabot__: no worries15:03
*** tkaczynski has quit IRC15:03
*** pmesserli has joined #openstack-meeting-415:06
*** acabot__ has quit IRC15:06
*** acabot__ has joined #openstack-meeting-415:06
*** pmesserl_ has quit IRC15:07
*** salv-orlando has joined #openstack-meeting-415:08
*** acabot__ has quit IRC15:08
*** iceyao_ has quit IRC15:08
*** pmesserli has quit IRC15:09
*** pmesserli has joined #openstack-meeting-415:10
*** Swami has joined #openstack-meeting-415:14
*** krtaylor has joined #openstack-meeting-415:14
*** avarner_ has quit IRC15:15
*** avarner_ has joined #openstack-meeting-415:15
*** numans has quit IRC15:16
*** avarner__ has joined #openstack-meeting-415:18
*** avarner_ has quit IRC15:18
*** vincentfrancoise has left #openstack-meeting-415:18
*** brunograz has left #openstack-meeting-415:20
*** haleyb has joined #openstack-meeting-415:22
*** avarner_ has joined #openstack-meeting-415:23
*** avarner_ is now known as avarner15:23
*** avarner__ has quit IRC15:23
*** iyamahat has joined #openstack-meeting-415:23
*** spotz_zzz is now known as spotz15:24
*** dims has quit IRC15:29
*** salv-orlando has quit IRC15:29
*** dims has joined #openstack-meeting-415:30
*** zeih has quit IRC15:33
*** ninag has quit IRC15:34
*** dims has quit IRC15:34
*** krtaylor has quit IRC15:34
*** yamahata has joined #openstack-meeting-415:39
*** zeih has joined #openstack-meeting-415:39
*** avarner has quit IRC15:42
*** avarner has joined #openstack-meeting-415:42
*** nkrinner has quit IRC15:44
*** dslevin has joined #openstack-meeting-415:44
*** dslevin has quit IRC15:44
*** dslevin has joined #openstack-meeting-415:45
*** dslevin has quit IRC15:46
*** dslevin has joined #openstack-meeting-415:46
*** dslevin has quit IRC15:47
*** krtaylor has joined #openstack-meeting-415:47
*** dslevin has joined #openstack-meeting-415:47
*** dslevin has quit IRC15:48
*** dslevin has joined #openstack-meeting-415:49
*** galstrom_zzz is now known as galstrom15:50
*** dslevin has quit IRC15:50
*** gampel has quit IRC15:52
*** dslevin has joined #openstack-meeting-415:52
*** Sukhdev has joined #openstack-meeting-415:52
*** dslevin has quit IRC15:52
*** dslevin has joined #openstack-meeting-415:53
*** dslevin has quit IRC15:54
*** dslevin has joined #openstack-meeting-415:55
*** matrohon has quit IRC15:56
*** qwebirc38287 has joined #openstack-meeting-415:57
*** baoli has quit IRC15:58
*** baoli has joined #openstack-meeting-415:59
*** dims has joined #openstack-meeting-416:03
*** hdaniel has quit IRC16:05
*** jmckind has quit IRC16:07
*** jmcbride1 has joined #openstack-meeting-416:07
*** seanmurphy has quit IRC16:07
*** jmckind has joined #openstack-meeting-416:08
*** jmcbride has quit IRC16:08
*** salv-orlando has joined #openstack-meeting-416:08
*** yamahata has quit IRC16:10
*** cbouch has joined #openstack-meeting-416:14
*** FallenPegasus has joined #openstack-meeting-416:22
*** inc0 has joined #openstack-meeting-416:23
*** rockyg has joined #openstack-meeting-416:23
*** banix has joined #openstack-meeting-416:24
*** bpokorny has joined #openstack-meeting-416:24
*** jmckind_ has joined #openstack-meeting-416:28
*** ajmiller_ has joined #openstack-meeting-416:29
*** akwasnie has joined #openstack-meeting-416:29
*** ajmiller has quit IRC16:29
sdake#startmeeting kolla16:30
openstackMeeting started Wed Feb 24 16:30:11 2016 UTC and is due to finish in 60 minutes.  The chair is sdake. 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
sdake#topic rollcall16:30
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:30
SamYapleo/16:30
pbourkeo/16:30
akwasniehi :)16:30
britthouser0/16:30
sdakeyo folks16:30
pbourkeso close to being first16:30
pbourkecheers SamYaple16:30
pbourke:p16:30
inc0o/16:30
dave-mccowano/ hola16:30
SamYapleso you know what they call almost winning pbourke ?16:30
SamYaplelosing16:30
pbourkelol16:30
sdakeage before beauty pbourke  ;)16:30
*** belmoreira has quit IRC16:31
*** rhallisey has joined #openstack-meeting-416:31
rhalliseyhello16:31
*** jmckind has quit IRC16:31
jpeelerhi16:32
sdake#topic announcements16:32
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:32
*** prashantD has joined #openstack-meeting-416:32
*** carolbarret has joined #openstack-meeting-416:32
sdake1. meeting times have changed, even weeks are 16;30, odd weeks are 23:0016:32
carolbarret#openstack-meeting16:32
carolbarret#openstack-meetings16:32
sdakeISO weeks - to find the week run date "+%V"16:32
akwasnie1630 timezone?16:32
akwasnieah, ok16:33
SamYapleakwasnie: UTC16:33
*** ihrachys has quit IRC16:33
sdakecarolbarret is there an issue with meeting conflct?16:33
*** jmckind_ has quit IRC16:33
*** vhoward_ has quit IRC16:33
sdakethe meetings are staying in the channel openstack-meeting-416:33
sdakethe irc channel gate sorts out conflicts and -1's the patch if its wrong ;)16:34
*** zeih has quit IRC16:34
sdake2. we need to get cracking on our austin summit sessions - ttx has requested the info in the next few weeks16:35
*** vhosakot has joined #openstack-meeting-416:35
sdakeso the next two meetings, we need to sort that out16:35
vhosakotsorry, I'm late16:35
vhosakoto/ :)16:35
sdake3. mitaka releases between 2nd-4th of march, 1 week to go - and we got a ton of work to do16:35
*** xingchao has quit IRC16:35
sdake4. I am going to kick all medium/low blueprints to newton if they are not in the good progress stage, so please make it so in launchpad - if you dont' have permissions ping me and i'll add you to the drivers group to change your blueprint states16:35
SamYaplesdake: you mean mitaka-3 right?16:36
sdakeSamYaple yes mitaka-316:36
sdakethen we have 1 month for stablization via rcs16:36
sdakethe final date I believe is aprril 13th, but not certain - i'll double check and get backt o folks that want o know our actual release date16:36
sdakeany announcements from community folk?16:37
sdake#topic Kolla Austin Summit topics [timebox 15 minutes]16:38
*** openstack changes topic to "Kolla Austin Summit topics [timebox 15 minutes] (Meeting topic: kolla)"16:38
*** fawadkhaliq has joined #openstack-meeting-416:38
sdake#link https://etherpad.openstack.org/p/kolla-newton-summit16:38
*** jmckind has joined #openstack-meeting-416:38
*** xionglingfeng has joined #openstack-meeting-416:39
*** cbouch has quit IRC16:40
*** SimonChung1 has quit IRC16:40
*** cbouch has joined #openstack-meeting-416:40
*** 32NAAC6RR has quit IRC16:42
*** iyamahat has quit IRC16:43
elemoine_o/16:43
xionglingfenghi everyone :-)16:43
elemoine_sorry for being late, I thought there was no meeting16:43
*** qwebirc38287 has quit IRC16:44
dave-mccowanwe're collaborating in  https://etherpad.openstack.org/p/kolla-newton-summit16:44
xionglingfengSo this conference is only about the design of Newton cycle?16:45
*** baoli_ has joined #openstack-meeting-416:46
vhosakotdave-mccowan: add your name under "Contributors" at the top16:47
xionglingfengme?16:48
*** baoli has quit IRC16:48
vhosakotxionglingfeng: you too :)16:49
*** sridhar_ram has joined #openstack-meeting-416:49
xionglingfengI am still thinking what shall I write on the pad LOL16:49
*** akwasnie has quit IRC16:49
sdakewheee :)16:49
rhalliseyxionglingfeng, anything you want to discuss16:49
sdakeok lets keep going until the hour mark or until we run out of ideas ;)16:50
xionglingfengIm struggling about the cinder NFS thing :-(16:50
xionglingfengsince nova_compute and nova_libvirt r split into two component, it is really difficult to make cinder NFS working16:51
*** piet has quit IRC16:51
xionglingfengany suggestions on this?16:52
*** piet has joined #openstack-meeting-416:52
*** FallenPegasus has quit IRC16:53
*** akwasnie has joined #openstack-meeting-416:54
*** akwasnie has quit IRC16:54
*** akwasnie1 has joined #openstack-meeting-416:54
*** Guest51435 is now known as mgagne16:56
*** mgagne has quit IRC16:56
*** mgagne has joined #openstack-meeting-416:56
*** Sukhdev has quit IRC16:57
*** lbragstad has quit IRC16:58
*** lakshmiS has joined #openstack-meeting-416:59
*** dims has quit IRC17:00
*** iyamahat has joined #openstack-meeting-417:00
sdakeok folks17:00
sdakewe went past our timebox and our extended timebox17:00
*** amotoki has quit IRC17:00
sdakelets finish this up next meeting17:00
sdake#topic risk item status17:00
*** openstack changes topic to "risk item status (Meeting topic: kolla)"17:00
sdakehttps://etherpad.openstack.org/p/kolla-mitaka-midcycle-roadmap17:01
*** FallenPegasus has joined #openstack-meeting-417:01
sdakeelemoine_ akwasnie1 diagnostics status?17:02
sdakeI know heka is msotly merged17:02
akwasnie1elasticsearch is merged17:02
*** ninag has joined #openstack-meeting-417:02
elemoine_what remains is integrating the two17:02
akwasnie1we will start integration this week, i think17:02
*** thorst has quit IRC17:02
akwasnie1yup :)17:02
elemoine_I created a wip CR for that17:02
*** lbragstad has joined #openstack-meeting-417:03
elemoine_I hope akwasnie1 and I can collaborate on it17:03
*** galstrom is now known as galstrom_zzz17:03
xionglingfengquick question: since we already have ELK and heka for logs, why we still keep rsyslog?17:03
akwasnie1sure :)17:03
*** thorst has joined #openstack-meeting-417:03
*** thorst has quit IRC17:03
akwasnie1rsyslog is removed17:03
xionglingfengcool17:03
*** dims has joined #openstack-meeting-417:03
sdakewe have EHK - special snowflakes ftw ;)17:04
xionglingfengLOL17:04
xionglingfengWhat is the time schedule for kolla release?17:04
sdakeJeffrey4l reconfig17:04
xionglingfengI mean, what time is feature freeze, something like this?17:04
elemoine_makes me wonder if we should rename the enable_elk var to something else17:04
sdakefeature freeze is theoretically march 2nd-4th17:04
sdakei say theoretically because we are on releease-indepndent schedule17:04
elemoine_I guess it could just be enable_elasticsearch in fact17:05
xionglingfengokok got u17:05
sdakeso we set our own schedules and release criteria17:05
xionglingfengok. Is there any page for the schedule?17:05
sdakehowever, i'd like to follow upstream release-managed as much as possible17:05
xionglingfengsure17:05
sdakexionglingfeng google for openstack mitaka schedule17:05
elemoine_sdake: makes sense to me17:05
sdakeJeffrey4l ping re reconfig17:05
sdakeinc0 your up on infrastructure upgrades17:05
inc0HAProxy is up for review17:06
xionglingfengI have OS time schedule. Because you mentioned kolla has own schedule so I just wondering if it is documented.17:06
*** rockyg has quit IRC17:06
inc0rabbitmq is inprog17:06
*** yamahata has joined #openstack-meeting-417:06
inc0mariadb is on SamYaple17:06
sdakekeepalived is also in the haproxy review17:06
*** belmoreira has joined #openstack-meeting-417:06
sdakeceph remains17:06
inc0we need upgrades of logging stuff, but that's lower priority17:06
*** avarner has quit IRC17:06
sdakewhat  else?17:06
xionglingfengwhat about n-1 support?17:06
*** avarner has joined #openstack-meeting-417:07
SamYaplexionglingfeng: that is unlikely to ever happen17:07
xionglingfenglol17:07
xionglingfengkk17:07
sdakexionglingfeng add to the etherpad for austin summit discussion17:07
inc0but elemoine akwasnie1 you might want to check on this one, hopefully is as simple as rebuild containers17:07
sdakeits not going to happen in mitaka - mitaka needs more capacity or less features17:07
elemoine_inc0: I can have a log at upgrade of logging stuff, although I am not sure what that implies at this point17:07
sdakesounds like diags is not really in risk any longer17:08
inc0elemoine_, at very least implement naive redeploy with serial plz17:08
sdakesounds like infrastructure upgrades is not at risk any longer17:08
inc0ceph is still for the taking17:08
*** fnaval has quit IRC17:08
inc0ceph upgrades17:08
SamYaplenah ceph is fine17:08
sdakemigration path - pbourke ?17:08
SamYapleim working on it now17:08
SamYapleits not doing storage infrace properly17:08
sdakeSamYaple can you assign the blueprint to yourself17:08
SamYaplei did at one point...17:08
*** fnaval has joined #openstack-meeting-417:09
sdakeand set the state to started or good progress17:09
elemoine_inc0: I can have a look, but I need to get more familiar with the exact needs17:09
sdakei unset them at midcycle because we moved around who was working on what17:09
inc0elemoine_ I'm here to help17:09
*** blakec has joined #openstack-meeting-417:09
sdakevm functional testing no longer at risk17:09
sdakeso that leaves reconfig17:09
elemoine_inc0: ok, I'll ping you on IRC then17:09
sdake#info reconfig is at risk and essential blueprint for mitaka17:09
elemoine_inc0: any container I should look at as a model?17:10
inc0elemoine_, keystone is the simpliest, nova is most complex17:10
elemoine_is reconfig related to upgrade?17:10
inc0not really17:10
sdakeelemoine_ sort of but not really17:10
elemoine_or are the two independent?17:10
sdakethey are two seprate actions17:10
xionglingfengreconfig?17:10
elemoine_ok, I'll figure it out17:10
xionglingfengdo u mean that modify the configuration files then redeploy the containers?17:11
elemoine_xionglingfeng: reconfig == restart container after config change17:11
SamYaplehey i really dont like "reconfig" is there opposition to "reconfigure"?17:11
xionglingfengOr i misunderstood17:11
xionglingfengokok got u17:11
inc0reconfig means I want to keep my containers as they are but change config files17:11
*** prithiv has quit IRC17:11
elemoine_SamYaple: reconfiguration, sorry :)17:11
SamYapleelemoine_: i meant for the name17:11
elemoine_SamYaple: I agree with you17:11
sdakereconfigure is a bit long but i dont care as long as it works ;)17:11
inc0updtading_configuration_files_to_the_latest_version_based_on_what_is_currently_in_ansible_templates17:11
SamYaplereload17:11
elemoine_we don't have short names elsewhere17:12
SamYaplei dont care, just the partital short name is annoying17:12
xionglingfeng reconfig==write new version of configuration files and restart containers, isn't it?17:12
SamYaplexionglingfeng: yes17:12
xionglingfengSo the risk is?17:12
elemoine_that it's not finished before mitaka I guess17:12
sdakethe risk is there is only one patch in the queue to do the job and it ahsn't been updatedd in 5 days17:12
sdakeand there needs to be  a role for every service17:13
sdakei'll speak to Jeffrey4l offline about it, he must be asleep ;)17:13
sdakeok, any questions, or shall I move on?17:13
elemoine_sounds worrying…17:13
SamYaplesdake: its been updated...17:13
SamYapleits fairly active right now17:13
sdakeSamYaple cool - i'll check it out17:13
SamYaplelooks good17:13
rhalliseywell once there's a template the rest should fly up there17:13
sdakeSamYaple I haven't looked at the queue this morning yet17:13
rhalliseywe told him to make sure one merges first17:14
xionglingfenghav to leave   meeting conflict17:14
xionglingfengsee u guys :-)17:14
rhalliseysee ya17:14
sdakexionglingfeng ttyl17:14
SamYaplethanks xionglingfeng17:14
elemoine_xionglingfeng: bye17:14
sdake#topic essential blueprint status17:14
*** openstack changes topic to "essential blueprint status (Meeting topic: kolla)"17:14
*** fnaval_ has joined #openstack-meeting-417:15
sdakehttps://launchpad.net/kolla/+milestone/mitaka-317:15
sdake#link https://launchpad.net/kolla/+milestone/mitaka-317:15
xionglingfengBTW, I think I have some spare time working on both core components and trove/murano in the following months. So if anything I can help, just let me know17:15
xionglingfeng:-)17:15
sdakeessential is looking good17:15
*** fnaval has quit IRC17:15
sdakewe have many in the not started state however17:15
sdakeso lets focus on those first17:15
sdakemariadb lights out recovery17:15
elemoine_xionglingfeng: trove logs are not collected17:16
sdakeSamYaple ^17:16
sdakealso playbook for neutron playbook for openvswitch for upgrades ^^17:16
elemoine_xionglingfeng: it would be good to add that, and that should be pretty straightforward17:16
sdakeare those not started state as well, or are they started?17:16
*** xionglingfeng has quit IRC17:16
SamYaplethey are started17:17
sdakeremember, we have 1 week ;)17:17
SamYaplei need to push them up for review17:17
SamYapleim testing multinode neutron17:17
sdakecool, mind i set them to started?17:17
SamYapleit _seems_ to be working17:17
sdakeif they are ready to review, then theyare probably good dprogress17:17
sdakeor ready for review17:17
SamYapleyea in neutrons case its basic service upgrade template17:18
*** pmesserli has quit IRC17:18
sdakeSamYaple would you mind setting the state for those 3 to what you think is appropriate?17:18
SamYaplemariadb is harder, still idempoteizing it17:18
*** pmesserli has joined #openstack-meeting-417:18
sdakenihilifer you ahve several upgrade blueprints in started state17:19
sdakeI see they have reviews up17:19
sdakeand your blocked on multinode testing17:19
sdakefolks - please don't block on mulitnode  testing just test single node and we can sort out multinode qa in the rcs17:19
sdakeiwith qualifier (if you can't test multinode)17:20
sdakethe goal is to get things from not started->started->good progress->ready for review->implemented17:20
*** jmckind_ has joined #openstack-meeting-417:20
sdakeI leave it to you to judge what state your work is in17:20
sdakebut I can't read your minds,  so please set the tracker appropriately so operators don't have a heart attack when they look at our tracker17:21
sdakeupgrade playbook for heat, half done17:21
sdakerest are all good progress17:21
sdakeI'd define good progress as *it will be implemented by march 2nd-4th*17:21
*** jmckind has quit IRC17:21
inc0how are we doing on Grand-Backport?17:22
sdakeinc0 lets get mitaka-3 out of the way first17:22
sdakeI had planned to discuss high prioirrty blueprints17:22
sdakebut there isn't enough  time17:22
sdakeso :)17:22
sdake#topic open discussion17:22
*** openstack changes topic to "open discussion (Meeting topic: kolla)"17:22
sdakeinc0 you have the floor17:22
elemoine_inc0: grand backport == backporting thin containers ?17:22
sdakeelemoine_ no the first part of the proposal17:23
vhosakotI have something to talk in open discussion.. should we add docker version and ansible version as well in requirements.txt ?17:23
elemoine_ah ok17:23
inc0elemoine_ thin containers and named volumes17:23
sdakethe containers backport hasn't hit its voting deadline yet17:23
elemoine_got it17:23
sdakevhosakot one at a time :)17:23
inc0sdake, but I think we have majority already17:23
sdakewhoever has the floor drives discussion in open discussion17:23
vhosakotsdake: got it!17:23
sdakeinc0 cool wedidn't yesterday i'll check ml and make it so17:23
sdakeso inc0 anything to add re grand backport ? :)17:24
inc0ok, I'd love to have 1.1.0 asap tbh...we need to really test this one17:24
rhalliseyya I think we hit the majority17:24
inc0its more important (way more important) than Mitaka-3 imho17:24
inc0I'm done17:24
sdake#action sdake to check for majority on thin container backport and post results on mailing list17:24
SamYaplei agree inc017:24
sdakeinc0 we need to finish the features for mitaka by eadline atleast essential/high17:25
sdakeI don't want features in the rcs if we can help it17:25
sdakewe have 80 bugs in the tracker, which is about 40 too many to handle in the rcs17:25
inc0ok, but I want to say that while noone will deploy mitaka for next few months, 1.1.0 will get deployed as first kolla on prod17:26
sdakevhosakot you have the floor17:26
sdake3 minutes ;-)17:26
vhosakotsdake: thanks :)17:26
vhosakotI have something to talk in open discussion.. should we add docker version and ansible version as well in requirements.txt ?17:26
* SamYaple begs for reviews https://review.openstack.org/#/c/28388717:26
sdakeinc0 ack that, i think we need to do that during rcs17:26
SamYaplethat was holding up ceph upgrades ^17:26
inc0vhosakot, we are separating kolla-ansible from kolla17:26
sdakeSamYaple will review after meeting17:26
*** ihrachys has joined #openstack-meeting-417:26
inc0and we can't add docker version because it's not pip installable17:26
vhosakotinc0: ah, ok.. agreed.. cool17:27
sdakeansible can't be added to requiremetns.txt because of openstack policies17:27
sdakethere is a bug in the tracker on this piont17:27
inc0that too17:27
sdakei'll find it for you later if you want to read up on it17:27
inc0ansible has wrong licence17:27
vhosakotsdake: thats it.. I will ping in #kolla channel about a feature I need to start or help with17:27
SamYapleok im out guys17:27
SamYaplelunch17:27
elemoine_https://bugs.launchpad.net/kolla/+bug/154753317:28
openstackLaunchpad bug 1547533 in kolla "Tech-Debt: Namespace the Docker volumes" [Medium,Confirmed]17:28
sdakeany other open discussion?17:28
elemoine_would love a decision on this17:28
sdakedecision on what17:28
elemoine_https://bugs.launchpad.net/kolla/+bug/154753317:28
sdakeoh you rbug17:28
elemoine_volume naming17:28
sdakei'll tak a look elemoine_17:28
sdakeI think we  dont need namespacing on further thinking17:28
elemoine_thanks, I've added a few ideas in the bug17:28
*** blakec has left #openstack-meeting-417:28
SamYapleelemoine_: i know what youre asking, we can implement that in newton17:29
elemoine_sdake: which means renaming kolla_logs to something else I guess17:29
inc0if docker doesn't support volume rename17:29
SamYaplemesos has this thing17:29
sdakethanks for coming folks17:29
SamYapleinc0: it doesnt need to17:29
sdakeour meeting time is up :)17:29
elemoine_bye17:29
*** ihrachys has quit IRC17:29
sdakelets overflow into #kolla as needed17:29
vhosakotbye :)17:29
sdake#endmeeting17:29
inc0bye17:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:29
openstackMeeting ended Wed Feb 24 17:29:48 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:29
rhalliseybyee17:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-02-24-16.30.html17:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-02-24-16.30.txt17:29
*** rhallisey has left #openstack-meeting-417:29
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2016/kolla.2016-02-24-16.30.log.html17:29
*** vhosakot has left #openstack-meeting-417:29
ajafobye17:29
akwasnie1bye ! :)17:30
*** akwasnie1 has quit IRC17:31
*** akwasnie has joined #openstack-meeting-417:32
*** IlyaG has joined #openstack-meeting-417:33
*** akwasnie has quit IRC17:40
*** fnaval_ has quit IRC17:40
*** spzala has quit IRC17:42
*** spzala has joined #openstack-meeting-417:42
*** IlyaG has left #openstack-meeting-417:42
*** spzala has quit IRC17:43
*** spzala has joined #openstack-meeting-417:43
*** pmesserli has quit IRC17:45
*** pmesserli has joined #openstack-meeting-417:46
*** _sarob has joined #openstack-meeting-417:46
*** yamamoto has quit IRC17:49
*** sambetts is now known as sambetts|afk17:49
*** bobh has joined #openstack-meeting-417:49
*** akwasnie has joined #openstack-meeting-417:54
*** fnaval has joined #openstack-meeting-417:54
*** akwasnie has quit IRC17:56
*** sigmavirus24 is now known as sigmavirus24_awa18:01
*** dshakhray has quit IRC18:02
*** evgenyf has joined #openstack-meeting-418:03
*** julim has quit IRC18:03
*** avarner has quit IRC18:05
*** avarner has joined #openstack-meeting-418:06
*** julim has joined #openstack-meeting-418:07
*** FallenPegasus has quit IRC18:10
*** ajmiller_ is now known as ajmiller18:11
*** avarner has quit IRC18:12
*** thorst has joined #openstack-meeting-418:13
*** SimonChung has joined #openstack-meeting-418:13
*** degorenko is now known as _degorenko|afk18:14
*** gampel has joined #openstack-meeting-418:14
*** belmoreira has quit IRC18:23
*** Jeffrey4l has quit IRC18:29
*** neelashah has quit IRC18:33
*** jmckind_ has quit IRC18:41
*** cloudtrainme has joined #openstack-meeting-418:42
*** irenab_ has joined #openstack-meeting-418:42
*** minwang2 has joined #openstack-meeting-418:42
*** irenab has quit IRC18:44
*** irenab_ is now known as irenab18:44
*** klindgren has joined #openstack-meeting-418:45
*** spzala has quit IRC18:46
*** spzala has joined #openstack-meeting-418:46
*** zeih has joined #openstack-meeting-418:47
*** irenab_ has joined #openstack-meeting-418:48
*** yamamoto has joined #openstack-meeting-418:50
*** irenab has quit IRC18:50
*** irenab_ is now known as irenab18:50
*** paul-carlton1 has quit IRC18:51
*** sdake has quit IRC18:55
*** yamamoto has quit IRC18:56
*** ninag has quit IRC18:59
*** zeih has quit IRC18:59
*** ninag has joined #openstack-meeting-419:00
*** jmckind has joined #openstack-meeting-419:01
raginbajin#startmeeting operators_ops_tools_monitoring19:01
openstackMeeting started Wed Feb 24 19:01:56 2016 UTC and is due to finish in 60 minutes.  The chair is raginbajin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: operators_ops_tools_monitoring)"19:01
openstackThe meeting name has been set to 'operators_ops_tools_monitoring'19:01
klindgreno/19:02
raginbajino/19:02
*** evgenyf has quit IRC19:03
*** neelashah has joined #openstack-meeting-419:04
raginbajinI have an etherpad up and running for today's meeting.  It pulls in the last meeting before the Mid-cycle that we had on 01/24/2016 - https://etherpad.openstack.org/p/osops-irc-meeting-2016022419:04
raginbajin#link https://etherpad.openstack.org/p/osops-irc-meeting-2016022419:04
raginbajinI'll wait some time to see if people like j^2 balajin mdorman rockyg and a few others will be joining19:05
j^2I’ve been informed that my priorities have changed :(19:06
j^2I won’t be able to be as active as i used to be19:06
j^2I fought to keep myself in this community, but it seems that I’m needed other places to work on things for Chef19:07
j^2The last few weeks have been me attempting, and failing, at getting myself involved in both things, but Chef pays my bills so i have to do what they ask19:07
raginbajinGot it. It's not biggie.19:07
raginbajinI'll hit you up offline then. I have some questions and I hope I can fill your shoes going forward.19:08
j^2rock on19:08
raginbajinMaybe you can just help guide me19:08
*** mdorman has joined #openstack-meeting-419:08
j^2absolutely, don’t ever hesitate to reach out19:09
*** sdake has joined #openstack-meeting-419:09
*** balajin_ has joined #openstack-meeting-419:09
balajin_yo19:09
balajin_sorry, am late19:09
mdormansame here, thought meeting was in the ops channel.19:09
*** Sukhdev has joined #openstack-meeting-419:10
*** neelashah has quit IRC19:10
*** sigmavirus24_awa is now known as sigmavirus2419:11
raginbajinNo problem guys..19:11
raginbajinI think this may be as many as we will have so we can get started..19:11
balajin_yup19:11
balajin_soryr about that19:11
raginbajin#topic Previous Business - Operator bits in the Community App Catalog19:11
*** openstack changes topic to "Previous Business - Operator bits in the Community App Catalog (Meeting topic: operators_ops_tools_monitoring)"19:11
raginbajinWe agreed to focus on getting more validated and curated tools into the current repos first, then look for other ways to package and distribute.19:12
raginbajinNot sure if there is anything more on that one. Just going through the etherpad at this point.19:12
raginbajin#topic Previous Business - Mid-Cycle19:13
*** openstack changes topic to "Previous Business - Mid-Cycle (Meeting topic: operators_ops_tools_monitoring)"19:13
raginbajinNot sure how many of us were able to attend the mid-cycle19:13
*** neelashah has joined #openstack-meeting-419:14
raginbajinIt looks like we had some action items related to this that Mr mdorman was going to update the README files, which if I remember correctly was done.19:14
raginbajinWe were going to do the following:19:14
raginbajinEnsuring that we let operators know that it is easy to contribute to the osops-contrib repos and that it is a good first step.19:14
raginbajin Ensuring that we let operators know that osops is out there for their monitors/scripts and other tool additions and consumption19:14
raginbajinUpdate the readme's on the repo's before the midcycle to ensure that people know what these are for.19:14
raginbajinWas anyone able to attend the mid-cycle?19:15
raginbajinI'm assuming that is a no then.19:16
raginbajinI did see some emails come across on the operators list that mentioned the OSOps repos. I also have seen some commits happening as well.19:17
raginbajinDoes anyone have anything for previous business?19:19
*** ninag has quit IRC19:19
*** FallenPegasus has joined #openstack-meeting-419:19
klindgrenI do not19:19
mdormannope19:20
raginbajinThen I open up the floor for new business19:20
*** belmoreira has joined #openstack-meeting-419:20
raginbajin#topic new business19:20
*** openstack changes topic to "new business (Meeting topic: operators_ops_tools_monitoring)"19:20
mdormanyeah we have been getting a few reviews here and there in the repos, so it’s getting more attention.19:20
raginbajinWell that's good.19:23
*** woodard has joined #openstack-meeting-419:23
raginbajinIt seems that we doing a good job with making sure we point out the osops repos as well.19:23
mdormani think so19:23
klindgrenSo I take it noone here was able to go to the mid-cycle would have been interesting to hear feedback from that19:23
*** irenab_ has joined #openstack-meeting-419:23
raginbajinI wasn't able too. Out of country is pretty much a no-go especially for a mid-cycle19:24
*** irenab has quit IRC19:25
*** evgenyf has joined #openstack-meeting-419:25
raginbajinOk.19:25
raginbajinDoes anyone else have any new things they would like to talk about?19:25
raginbajinIf not, it seems that we can end the meeting and work on getting more topics to discuss in two weeks.19:26
*** woodard has quit IRC19:26
*** irenab has joined #openstack-meeting-419:26
*** woodard has joined #openstack-meeting-419:27
*** irenab_ has quit IRC19:28
raginbajinI'll give everyone two more minutes or so and I'll end the meeting for this week.19:28
klindgrenso you guys in two weeks19:29
klindgrens/so/see19:29
balajin_+119:30
raginbajinYep.19:36
raginbajin#endmeeting19:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:36
mdormanfyi there were some upates re: mid cycle in the last LDT meeting.  so you could look up the logs from that.19:36
openstackMeeting ended Wed Feb 24 19:36:39 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-02-24-19.01.html19:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-02-24-19.01.txt19:36
openstackLog:            http://eavesdrop.openstack.org/meetings/operators_ops_tools_monitoring/2016/operators_ops_tools_monitoring.2016-02-24-19.01.log.html19:36
mdormanah, just missed it, haha.   i didn’t have anything else anyway19:36
*** irenab has quit IRC19:39
*** rockyg has joined #openstack-meeting-419:39
*** fawadkhaliq has quit IRC19:40
*** iyamahat has quit IRC19:40
*** irenab has joined #openstack-meeting-419:41
*** mdorman has left #openstack-meeting-419:41
*** yamahata has quit IRC19:41
*** woodard has quit IRC19:43
*** inc0 has quit IRC19:43
*** inc0 has joined #openstack-meeting-419:43
*** inc0 has quit IRC19:45
*** inc0 has joined #openstack-meeting-419:45
*** woodard has joined #openstack-meeting-419:47
*** ninag has joined #openstack-meeting-419:48
*** inc0 has quit IRC19:49
*** dslevin has left #openstack-meeting-419:49
*** neelashah1 has joined #openstack-meeting-419:51
*** ninag has quit IRC19:52
*** neelashah has quit IRC19:53
*** ninag has joined #openstack-meeting-419:53
*** cloudtrainme has quit IRC19:54
*** inc0 has joined #openstack-meeting-419:57
*** neelashah has joined #openstack-meeting-419:57
*** inc0 has quit IRC19:57
*** neelashah1 has quit IRC19:58
*** irenab_ has joined #openstack-meeting-419:58
*** irenab has quit IRC19:59
*** irenab_ is now known as irenab19:59
*** IlyaG has joined #openstack-meeting-419:59
*** acabot_ has joined #openstack-meeting-420:00
*** neelashah1 has joined #openstack-meeting-420:00
*** neelashah has quit IRC20:01
*** irenab has quit IRC20:02
*** IlyaG has quit IRC20:04
*** irenab has joined #openstack-meeting-420:04
*** dslevin has joined #openstack-meeting-420:06
*** dslevin has quit IRC20:06
*** woodard has quit IRC20:07
*** dslevin has joined #openstack-meeting-420:07
*** woodard has joined #openstack-meeting-420:07
*** dslevin has quit IRC20:07
*** jmckind has quit IRC20:08
*** dslevin has joined #openstack-meeting-420:08
*** jmckind has joined #openstack-meeting-420:08
*** jmcbride1 has quit IRC20:08
*** dslevin has quit IRC20:09
*** dslevin has joined #openstack-meeting-420:09
*** dslevin has quit IRC20:09
*** woodard has quit IRC20:11
*** dslevin has joined #openstack-meeting-420:11
*** jmcbride has joined #openstack-meeting-420:12
*** jmcbride has quit IRC20:12
*** jmcbride has joined #openstack-meeting-420:12
*** javeriak_ has quit IRC20:17
*** iyamahat has joined #openstack-meeting-420:20
*** bobh has quit IRC20:21
*** IlyaG has joined #openstack-meeting-420:23
*** irenab_ has joined #openstack-meeting-420:24
*** irenab has quit IRC20:25
*** irenab_ is now known as irenab20:25
*** iyamahat has quit IRC20:26
*** jmcbride has quit IRC20:29
*** irenab_ has joined #openstack-meeting-420:30
*** irenab has quit IRC20:32
*** irenab_ is now known as irenab20:32
*** jmcbride has joined #openstack-meeting-420:32
*** FallenPegasus has quit IRC20:33
*** jmcbride has quit IRC20:33
*** jmckind has quit IRC20:37
*** dtardivel has quit IRC20:38
*** spzala has quit IRC20:40
*** cloudtrainme has joined #openstack-meeting-420:45
*** ihrachys has joined #openstack-meeting-420:47
*** Sukhdev has quit IRC20:48
*** belmoreira has quit IRC20:53
*** iyamahat has joined #openstack-meeting-420:56
rockygo/21:00
*** piet has quit IRC21:00
*** SimonChung has quit IRC21:01
*** SimonChung1 has joined #openstack-meeting-421:01
rockyganyone here for log_wg?21:01
*** rosmaita_ is now known as rosmaita21:02
*** SimonChung has joined #openstack-meeting-421:02
*** SimonChung1 has quit IRC21:02
*** evgenyf has quit IRC21:05
rbradforrockyg, hi21:05
rbradforsorry, had some oslo  things in urgent review21:06
rockyghey!  Well.  I guess I can start the show...21:06
rockyg#startmeeting log_wg21:06
openstackMeeting started Wed Feb 24 21:06:29 2016 UTC and is due to finish in 60 minutes.  The chair is rockyg. Information about MeetBot at http://wiki.debian.org/MeetBot.21:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:06
*** openstack changes topic to " (Meeting topic: log_wg)"21:06
openstackThe meeting name has been set to 'log_wg'21:06
rockygjokke_, !!21:06
rockyg#topic Ops midcycle21:07
*** openstack changes topic to "Ops midcycle (Meeting topic: log_wg)"21:07
rbradforrockyg, so how did it go21:08
rockygGreat midcycle.  Turns out the docs lead for config ref was there21:08
rockygWe talked.  I showed a bunch of ops the config output in the dev docs area.  They were happy21:09
rockyg But most ops are still on icehouse/juno  so doesn't do *as* much for them21:10
*** thorst is now known as thorst_afk21:10
rockygYet.21:10
*** pcaruana has quit IRC21:10
rockygI asked format and presentation questions.  They responded with preferences.  docs lead loved it.21:11
rbradforwhy would it not do as much, because they have not done upgrades?21:11
*** woodard has joined #openstack-meeting-421:12
rockygYeah.  Still on the older stuff.  *but* one of the most important section for ops that have been around a couple of releases is the section on changed opts:  new, deprecated, and who knows, maybed defaults changed21:12
rbradforrockyg, great you mentioned that.21:12
rbradforI'm working on a spec to "Better identify configuration option lifespan"21:13
rockygYeah.  Trying to make upgrades easier, so Reno, and those changes sections are critical.21:13
rbradforso there are Released, Changed, Deprecated, Removal attributes per option, and those sections (expecially changed) are auto generated.21:13
rockygI think we can get you ops comments on a spec like that.21:14
rbradforrockyg, its good meta information that both adds developers and deployers/administrators. It's also a very low development cost when the support exists21:14
*** akwasnie has joined #openstack-meeting-421:15
*** akwasnie has left #openstack-meeting-421:15
rbradforand when it removes manual documentation (including release-notes), you never miss anything.21:15
rockygExcellent.  What would really be cool, but just a nice to have would be a tool that could generate current install's opts and values and a diff of what will change with a selected "upgrade" release.  So, if they skip a release, they can get the info in one place.21:15
rbradforyes, that's a sub-part of it21:16
rockygWow!  cool!  The ops guys will definitely want to read the spec.21:16
*** ihrachys has quit IRC21:17
rockygIt was pointed out in the prod wg meetup that online retailers can't change site code from about August until after the new year.  Except for fixing brokenness.21:17
rbradforas part of removing two deprecated options in oslo.log this lead to talking to docs team about updating.21:17
*** iyamahat has quit IRC21:17
rockygI saw that depracation.21:18
rbradforgood discussion with gpocentek on -doc about how in particular config sections are generated in documentation.21:18
*** gampel has quit IRC21:18
rockygWonderful.21:18
rockygThe syslog deprecations and config opts in oslo.log are very confusing for me.21:19
rbradforit's in the same vein but I can see ways to make it quicker and easier to produce that content, and more closely align with the code that generate developer docs and sample config.    converging the code to a source makes it easier to remove inconsistencies21:19
rockygThe documentation is there, but it doesn't really 'splain it.21:19
rockygYeah.  One truth is more likely correct than multiple sources of truth21:20
rbradforit's all intertwined as I am finding out.21:20
rbradforhaving a means of generating the actual code content consistently, then puts more back on the documentators to format around that, different guides, master sections etc.21:21
rockygYeah.  And those sample configs generated....ops would love that straightened out, too.21:21
rockygPlus, you get quicker feedback from docs folks if something isn't clear to them.21:22
rockygShortens the feedback loop21:22
rockygThat's excellent.  Also, I suspect at least some of what is happening for this release can be used more "standalone" as tools for ops on earlier releases21:24
rbradforso, sample configs is from my work across a few projects, hugely inconsistent.21:24
rbradforI believe there is more a goal to have these as part of docs, instead of in the code base.21:25
rbradforI'm all for that, as it would be a more consistent location.21:25
rockygOh, yeah.  About a year, year and a half ago there was tons of bitching about those.  Problem was the projects needed to update in a different location when they changed something.  So, they were always out of date.21:25
rbradforand as you point out, having it each cycle enables the simple diff command to be your friend.21:26
rbradforit's just yet another thing to want to make consistent and work through projects with it.21:26
rockygHmm.  That's interesting.  Opts located in docs....21:26
*** salv-orl_ has joined #openstack-meeting-421:27
rbradforsample configs in docs21:27
rbradforwhich FYI are linkable (and therefore clickable) in the developer docs.21:27
rbradforhow are they in the manuals now?21:27
rockygOh, wow.  You're gonna get sick of me saying wow.21:28
rbradforits logical. now getting it done, that's political.21:28
rockygThey are mostly just in tables in the manuals.  Just words.  No hyperlinks21:28
rockygYou've gotta have a crossproject session at the summit.21:29
rbradforwhat I'm also  proposing for the docs, it would take zero extra time to also produce a sample config that manuals could injest if wanted.21:29
*** salv-orlando has quit IRC21:29
rockygSo, what's the political part?21:30
rbradforpolitical in having all projects follow a set way of doing things.21:30
rockygThat's what cross project team is for.21:30
rbradforas a side issue for example, projects should have migrated from oslo incubator to oslo libraries (releases ago), a number of (including TC approved projects have not)21:30
rbradforagreed, but saying to do something and seeing it done would from my limited time around be very different things21:31
rockygThe spec goes to them, gets finalized, then we start getting project specs and bps added to it.21:31
*** cloudtrainme has quit IRC21:31
rbradforthat incubator point FWIW, is needed to push through standard logging format strings across projects21:31
*** sridhar_ram1 has joined #openstack-meeting-421:32
rockygOh, yes.  Frinstance:  glance v2 won't make it into nova this release.  I think it's 4-6 releases and counting.  Cinder v2, also.21:32
rockygSo, which projects are still using the incubator oslo_log?21:33
rbradforso, there are several consistency things, they don't result in huge visible wins for operators, but are the foundation for more work.21:34
*** prithiv has joined #openstack-meeting-421:34
*** ekarlso- has quit IRC21:34
*** ekarlso- has joined #openstack-meeting-421:34
rbradforsolum is one of them.  it also lacked oslo.context (the important meaty bits)21:34
*** sridhar_ram has quit IRC21:34
rbradforoslo.context chnage in solum just merged this week, log is getting there.21:34
rockygJust knowing they're in the pipeline will make ops happier.  Many skip a release between each upgrade, so they see the changes faster in some ways.21:35
rbradforthe next is Manila (that uses incubutor oslo context)21:35
rockygAh.21:35
rockygMore important for manila.21:35
rockygSolum is close to single vendor.21:35
*** woodard has quit IRC21:36
rbradforyeah, after the cutoff of oslo libraries for Mitaka (which is today), that's one of my top priorities (as I want it for a logging blueprint I'm working on)21:36
rockygIn fact, some of the TC thought it was dead until the past couple of weeks.21:36
rockygExcellent!  So, I have some good news around that, too.21:37
*** woodard has joined #openstack-meeting-421:37
rockygOslo has not been part of the roadmapping effort.  But, I'm the CPL to get the infor for the roadmap from Oslo.  and it's easy since you guys freeze early.21:38
rockygWe can highlight the efforts/timeline to get all projects onboard/up to date.21:38
*** cloudtrainme has joined #openstack-meeting-421:38
rockygIt might also serve to attract more dev attention through vendors who realize that some things move faster because of it.21:39
rockygSo, should I let you go to deal with deadlines?  The one thing I'd love to see is a better description of what the default logformat gets you by way of an example.  And how you specify syslog format....21:40
*** iyamahat has joined #openstack-meeting-421:40
*** krtaylor has quit IRC21:41
*** iyamahat has quit IRC21:42
*** iyamahat has joined #openstack-meeting-421:43
rbradforrockyg, so for developers I've started to include examples of logging output, see http://docs.openstack.org/developer/oslo.log/usage.html#olso-logging-functions (later example)21:44
rbradforit's a pre-cursor to a more specific example that includes the differ types across nova for example (that passes instance info).21:44
rockygKewl!21:45
*** bpokorny has quit IRC21:45
rbradforthere needs to be more info on the actual possible attributes in the format strings (e.g. %(request_id), %(instance), even %(color).   this is likely better in an operational document.21:46
rockygI've told some folks that I have to get the reqIDs in log message spec out so I'm committed to it.  We'll see if I can get it done before the summit.  Hope to.21:46
rockygAgreed.21:46
rbradforyes, that's an example.21:47
rbradforI'm working on the app agnositic parameters spec/bp. This is needed to provide both a consistency and a flexibility of the options in a logging string.  There are several novaisms (as described in code).21:48
*** cloudtrainme has quit IRC21:48
rbradforsomething to work towards for next cycle to have a operator docs portion (in say config reference) that can actually tell you what you can set and change)21:48
rockygOh, fyi, the ops folks have specifically said they want place holders [-] when an option is not used so parsing can be consistent.  I don't know if that made it anywhere as a bit of lore/knowledge or not21:49
*** SimonChung1 has joined #openstack-meeting-421:49
rbradforI'd like to know more on that.21:49
*** SimonChung has quit IRC21:50
rbradforbecause specifically there are situations of a single [-], or [- - - - -] (5 for unknown user identity, or - for not specified), my earlier link actually shows these21:50
rbradforbut it's only for "context" details, not for all values21:50
rockygMainly, just don't drop a log message field if not in use or not pertinent.  Fill it with - so the message parser doesn't have to be as complex.21:50
rbradforwell, actual examples of messages people see now, makes it easier for me to understand, and then vett if it's a specific release issue and no longer a problem.21:51
rockygThe other thing they bitched about was when a log message was passed inside another and all the duplications that arose in the payload from that, plus really long log messages21:51
*** sdake has quit IRC21:51
*** sdake has joined #openstack-meeting-421:52
rbradforI only have demo devstack environments, and I don't see the worst of these.  Some will be project specific, but you should just start a etherpad and ask for real contributions (minus any company specifics)21:52
rockygI can and will certainly do that.  I have some of that from old summit sessions, but will open up a new etherpad to collect up more.21:53
rbradforalso, with regards to the [-], operators should provide the actual logging_context_format_string value used in the project also, because projects historically are inconsistent here.21:53
rbradforif it was just mentioned, good to get people to be active again.21:54
*** Sukhdev has joined #openstack-meeting-421:54
rockygthere is another big painpoint in that there are certain times when an exception happens that puts megabytes to gigabytes into a single log message.  How to circumvent that from happening may take a bit of digging for more info, but I might be able to track down the specific ops who related the info.21:54
*** krtaylor has joined #openstack-meeting-421:55
rockygYeah.  And with summit coming up, now is the time to get ops' attention and feedback.21:55
rbradforI'm just guessing here, but it's the repetition of the exception trace that's the problem.21:55
rbradforsome error 1000 times with 1000 traces of x lines.21:55
*** reedip_ has quit IRC21:56
*** SimonChung has joined #openstack-meeting-421:56
*** SimonChung1 has quit IRC21:56
rbradforhow do you create a "reasonable threshold" of repeating messages, a lot like linux does (saying  "message" repeated n times) in syslog21:56
*** gmolson_ has joined #openstack-meeting-421:57
rbradforI could only surmise that would be really hard btw.21:57
*** banix has quit IRC21:57
rockygActually, it's not that hard, but the ops guys seemed to think the problem was more like a core dump into the log message rather than repeating.  The repeating ones repeat nicely.21:58
*** woodard has quit IRC21:58
rockygThousands to millions of times.21:58
rbradforsomething to be had sitting with a real operator to see what they see21:59
rockygI've been socializing the idea of take a dev to work21:59
rockygTo the ops community.21:59
rockygWe can make that happen for you...21:59
rbradforI've got a lot of code work ahead of me, I've only been at it full-time for a few months.  lots to learn.22:00
rockygAh! time.  Anything you want to get in quick?  We can make the ops thing happen whenever you're ready.22:00
*** lwilliams_ has joined #openstack-meeting-422:01
rbradforhappy to listen to operators (I was one myself), but I can see without talking to them, some important foundational work needs to be done so I could legitimately say, I see that and I can fix that.22:01
rbradfortime to get back to it!22:01
rockygYup.  Same here.  The more I dig, the more I see missing ;-)22:01
rockygThanks!22:01
rockyg#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
openstackMeeting ended Wed Feb 24 22:01:55 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-02-24-21.06.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-02-24-21.06.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2016/log_wg.2016-02-24-21.06.log.html22:02
*** ninag has quit IRC22:02
*** Sukhdev has quit IRC22:03
*** woodard has joined #openstack-meeting-422:05
*** JRobinson__ has joined #openstack-meeting-422:09
JRobinson__Good morning all22:10
JRobinson__We'll start the User Guide meeting for today22:10
lwilliams_Hi Joseph o/22:10
JRobinson__#startmeeting docuserguides22:11
openstackMeeting started Wed Feb 24 22:11:03 2016 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.22:11
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:11
*** openstack changes topic to " (Meeting topic: docuserguides)"22:11
openstackThe meeting name has been set to 'docuserguides'22:11
JRobinson__lwilliams_, hello! o/22:11
lwilliams_good morning to you!22:11
JRobinson__and good afternoon :)22:11
JRobinson__Apologies for the delay, I had trouble connecting a different computer to this meeting channel22:11
lwilliams_oh no worries!22:12
gmolson_Hi!22:12
JRobinson__gmolson_, good afternoon o/22:12
* rockyg waves from the back22:13
*** sdake has quit IRC22:13
lwilliams_hi rockyg!22:13
JRobinson__#topic Dashboard patches complete, Command Line Chapter goal22:13
*** openstack changes topic to "Dashboard patches complete, Command Line Chapter goal (Meeting topic: docuserguides)"22:13
JRobinson__rockyg, o/22:13
rockygo/22:13
*** Sukhdev has joined #openstack-meeting-422:14
*** dims has quit IRC22:14
*** asalkeld has joined #openstack-meeting-422:15
*** woodard has quit IRC22:15
JRobinson__#link https://review.openstack.org/#/c/282970/22:15
*** SimonChung has quit IRC22:15
JRobinson__^With the two patchs merged, the dashboard giles are copied over now22:15
JRobinson__^files22:15
lwilliams_nice!22:16
*** iyamahat has quit IRC22:16
JRobinson__That leaves the command line chapters in the Admin User Guide to create a space for in the Cloud Admin Guide22:16
gmolson_yay o/22:16
*** Sukhdev has quit IRC22:17
JRobinson__#info Next is create a Command line Chapter with index.rst file22:17
*** Sukhdev has joined #openstack-meeting-422:17
JRobinson__I've written out this as an action item since that seems to be the next logical step - creating cli-index.rst or similar file for tieing all the disparate cli chapters into a new section22:18
*** spzala has joined #openstack-meeting-422:18
gmolson_JRobinson, ok, cool. Are you still thinking of pulling that OpenStack command-line clients section structure in the Admin User Guide, as-is into the Cloud Admin Guide?22:20
*** spzala has quit IRC22:20
JRobinson__gmolson_, yes the first step would be copying as-is. Changing the structure is a goal for the next release cycle, I think.22:20
gmolson_Do you know what the future goal of revising structure is about?22:21
JRobinson__gmolson_, I don't have a clear goal on that yet, no.22:22
gmolson_ok, gotcha. thanks.22:22
JRobinson__It's a bit more nebulous at the moment. The sub step to get to the point of forming a goal on improved structure is finding out how readers actually read and consult the user guides22:23
JRobinson__the OpenStack foundation's User Survey from late last year is a useful starting point for that.22:23
JRobinson__Anyway,22:24
gmolson_right - ok. thanks.22:24
*** acabot_ has quit IRC22:24
JRobinson__#action Copy OpenStack command-line clients section from Admin to Cloud Admin22:24
*** neelashah1 has quit IRC22:25
JRobinson__#action Add the cli related steps to the Task List22:26
JRobinson__^I'll get onto that after the meeting22:26
JRobinson__So that was all I had for this week22:26
JRobinson__#topic Open Discussion22:26
*** openstack changes topic to "Open Discussion (Meeting topic: docuserguides)"22:26
JRobinson__Questions or comments ?22:26
gmolson_I can work on creating the cli-index.rst file22:27
JRobinson__gmolson_, thank you, that's great22:27
gmolson_Sure! I don't have anything else to discuss today...22:28
lwilliams_neither do I...  thanks.22:28
JRobinson__Okay, but any questions for the guides are okay now, or emailing me is fine. I sent a message out to the docs mailing list yesterday on this meeting.22:29
*** Sukhdev has quit IRC22:29
JRobinson__we can call it there then. Thanks everyone o/22:29
lwilliams_sounds good22:29
lwilliams_o/22:29
JRobinson__shorter meeting today.22:29
gmolson_have a great day, Joseph!22:29
rockygbye!22:29
JRobinson__gmolson_, thanks you too o/22:30
JRobinson__rockyg, o/ bye for now22:30
gmolson_o/22:30
JRobinson__#endmeeting22:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:30
openstackMeeting ended Wed Feb 24 22:30:10 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-02-24-22.11.html22:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-02-24-22.11.txt22:30
openstackLog:            http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-02-24-22.11.log.html22:30
*** lwilliams_ has quit IRC22:30
*** JRobinson__ is now known as JRobinson__afk22:31
*** gmolson_ has quit IRC22:31
*** bpokorny has joined #openstack-meeting-422:32
*** julim has quit IRC22:33
*** SimonChung has joined #openstack-meeting-422:34
*** delattec has joined #openstack-meeting-422:34
*** sridhar_ram1 has quit IRC22:36
*** cbouch has quit IRC22:37
*** cdelatte has quit IRC22:37
*** ninag has joined #openstack-meeting-422:37
*** sridhar_ram has joined #openstack-meeting-422:38
*** vishwana_ is now known as vishwanathj22:39
*** woodard has joined #openstack-meeting-422:52
*** SimonChung has quit IRC22:53
*** sigmavirus24 is now known as sigmavirus24_awa22:54
*** woodard has quit IRC22:54
*** woodard has joined #openstack-meeting-422:55
*** harshs has joined #openstack-meeting-422:57
*** harshs has quit IRC22:58
*** mandre has joined #openstack-meeting-423:00
*** spotz is now known as spotz_zzz23:01
*** thorst_afk is now known as thorst23:01
*** IlyaG has quit IRC23:01
asalkeldmandre: SamYaple we are normally in here?23:03
asalkeldshrug, i don't have anything - just the novelty of a meeting I can attend :-O23:04
mandreasalkeld: that's what https://wiki.openstack.org/wiki/Meetings/Kolla says23:04
mandrelet's wait a few more minutes, then we'll cancel it if nobody shows up23:05
*** SimonChung has joined #openstack-meeting-423:05
*** dims has joined #openstack-meeting-423:08
*** yamamoto_ has joined #openstack-meeting-423:08
*** britthouser has quit IRC23:08
*** britthouser has joined #openstack-meeting-423:08
*** klamath has quit IRC23:11
*** berndbausch has joined #openstack-meeting-423:12
*** sdake has joined #openstack-meeting-423:12
*** woodard has quit IRC23:13
*** bobh has joined #openstack-meeting-423:13
*** woodard has joined #openstack-meeting-423:13
*** JRobinson__afk has quit IRC23:14
*** prithiv has quit IRC23:14
*** Sukhdev has joined #openstack-meeting-423:15
*** rockyg has quit IRC23:16
*** asalkeld has left #openstack-meeting-423:20
*** sridhar_ram has quit IRC23:20
*** prithiv has joined #openstack-meeting-423:21
*** Swami has quit IRC23:24
*** sdake has quit IRC23:25
*** armax has quit IRC23:27
*** armax has joined #openstack-meeting-423:28
*** armax has quit IRC23:28
*** JRobinson__ has joined #openstack-meeting-423:29
*** haleyb has quit IRC23:30
*** mestery has quit IRC23:30
JRobinson__Hello everyone, I'll start the APAC user guide meeting in a minute23:31
berndbauschgood morning23:31
*** cloudtrainme has joined #openstack-meeting-423:31
*** mandre has left #openstack-meeting-423:32
JRobinson__berndbausch, good morning o/23:33
JRobinson__#meetingstart docuserguides23:33
JRobinson__#startmeeting docuserguides23:33
openstackMeeting started Wed Feb 24 23:33:49 2016 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.23:33
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.23:33
*** openstack changes topic to " (Meeting topic: docuserguides)"23:33
openstackThe meeting name has been set to 'docuserguides'23:33
*** woodard has quit IRC23:34
JRobinson__^sorry, had the irc bot syntax backwards.23:34
JRobinson__Anyway, good morning all23:34
*** woodard has joined #openstack-meeting-423:34
JRobinson__It's a short agenda today23:34
JRobinson__#topic Dashboard patches are done. Next is create a Command line Chapter with index.rst file23:34
*** openstack changes topic to "Dashboard patches are done. Next is create a Command line Chapter with index.rst file (Meeting topic: docuserguides)"23:34
JRobinson__berndbausch, thanks for completing the second dashboard patch. That merged rapidly23:35
JRobinson__I spoke to the US team members early today, and gmolson is going to create an cli-index.rst chapter23:35
JRobinson__#info copying the cli content from the admin to the cloud admin guide is set to begin within the next few days23:35
*** mestery has joined #openstack-meeting-423:35
*** IlyaG has joined #openstack-meeting-423:36
berndbauschjrobinson: This one? http://docs.openstack.org/user-guide-admin/cli.html23:37
*** yamamoto_ has quit IRC23:38
JRobinson__Yes, the plan is to move that section across.23:38
*** bmoss has joined #openstack-meeting-423:39
JRobinson__berndbausch, Having a new .rst file to copy the items into is a bit easier in this case - there is a target, or a place to copy the filenames into.23:41
*** IlyaG has quit IRC23:45
JRobinson__So that was all for the reorganisation: combining the guides for this meeting23:46
JRobinson__#topic open discussion23:46
*** openstack changes topic to "open discussion (Meeting topic: docuserguides)"23:46
JRobinson__Any questions or comment for this week?23:46
JRobinson__#action JRobinson__ to update the task list23:47
berndbauschmy only question was "what next". It's answered.23:47
berndbauschIf the CLI chapters are as easy to move as the dashboard ones, it's going to be quick.23:48
*** thorst has quit IRC23:48
*** iyamahat has joined #openstack-meeting-423:48
JRobinson__berndbausch, that's good, and after the cli items moved, the final tasks are checking for any files that may have been left over,23:48
JRobinson__and then working through the task list before April 1523:49
JRobinson__^The Cloud Admin Guide has several places that need editing23:49
*** pmesserli has quit IRC23:49
JRobinson__If that's all, I'll call it for this week23:51
berndbauschThanks23:52
JRobinson__np23:53
JRobinson__#endmeeting23:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:53
openstackMeeting ended Wed Feb 24 23:53:36 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-02-24-23.33.html23:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-02-24-23.33.txt23:53
openstackLog:            http://eavesdrop.openstack.org/meetings/docuserguides/2016/docuserguides.2016-02-24-23.33.log.html23:53
JRobinson__berndbausch, thanks again23:53
berndbausch:)23:53
*** woodard has quit IRC23:56
*** rbak has quit IRC23:59

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