Wednesday, 2015-11-25

*** woodard has quit IRC00:01
*** yamahata has quit IRC00:01
*** Sukhdev has quit IRC00:02
*** sridhar_ram has quit IRC00:03
*** sridhar_ram has joined #openstack-meeting-400:04
*** Sukhdev has joined #openstack-meeting-400:10
*** markvoelker has quit IRC00:26
*** LouisF has quit IRC00:28
*** dims has joined #openstack-meeting-400:30
*** dims_ has quit IRC00:31
*** mfedosin has quit IRC00:33
*** baoli has joined #openstack-meeting-400:42
*** baoli_ has joined #openstack-meeting-400:43
*** yamamoto has joined #openstack-meeting-400:44
*** sridhar_ram has quit IRC00:44
*** Sukhdev has quit IRC00:45
*** yamamoto has quit IRC00:46
*** baoli has quit IRC00:47
*** Sukhdev has joined #openstack-meeting-400:47
*** xingchao has joined #openstack-meeting-400:49
*** sridhar_ram has joined #openstack-meeting-400:50
*** SimonChung1 has quit IRC00:50
*** Swami has quit IRC00:53
*** SimonChung has joined #openstack-meeting-400:53
*** SimonChung has quit IRC00:53
*** SimonChung has joined #openstack-meeting-400:53
*** avarner has quit IRC00:53
*** yamamoto has joined #openstack-meeting-400:55
*** yamamoto has quit IRC00:55
*** SimonChung has quit IRC00:56
*** yamamoto has joined #openstack-meeting-400:56
*** bknudson has quit IRC00:56
*** SimonChung has joined #openstack-meeting-400:56
*** bknudson has joined #openstack-meeting-400:58
*** yamamoto has quit IRC00:58
*** ajmiller has quit IRC00:59
*** salv-orl_ has quit IRC01:01
*** yamahata has joined #openstack-meeting-401:03
*** sridhar_ram1 has joined #openstack-meeting-401:03
*** sridhar_ram has quit IRC01:04
*** qingyu has joined #openstack-meeting-401:06
*** xichengc has joined #openstack-meeting-401:06
*** xingchao has quit IRC01:07
*** xingchao has joined #openstack-meeting-401:07
*** xuhan has joined #openstack-meeting-401:08
*** xingchao has quit IRC01:08
*** QiLiang has joined #openstack-meeting-401:08
*** chenshuai has joined #openstack-meeting-401:08
*** sridhar_ram1 is now known as sridhar_ram01:08
*** wshao has joined #openstack-meeting-401:09
xichengc#startmeeting Compass Weekly Meeting01:10
openstackMeeting started Wed Nov 25 01:10:20 2015 UTC and is due to finish in 60 minutes.  The chair is xichengc. Information about MeetBot at http://wiki.debian.org/MeetBot.01:10
xichengc#info01:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:10
*** openstack changes topic to " (Meeting topic: Compass Weekly Meeting)"01:10
openstackThe meeting name has been set to 'compass_weekly_meeting'01:10
May-meimei#info meimei01:10
kerwin#info baigk01:10
QiLiang#info QL01:11
wshao#info weidong01:11
qingyu#info qingyu01:11
chigang#info chigang01:12
chenshuai#info chenshuai01:12
xuhaninfo xuhan01:12
xuhan#info xuhan01:12
xichengc#topic compass-core related code should be checked in to openstack/compass-core01:12
*** openstack changes topic to "compass-core related code should be checked in to openstack/compass-core (Meeting topic: Compass Weekly Meeting)"01:12
xichengcopenstack/compass-core is up and all other branches/repositories should be out-dated01:13
xichengcplease have future code changes checked in to openstack/compass-core master branch01:13
chigangxichengc: Is it finished?01:13
xichengcchigang yes01:14
*** xingchao has joined #openstack-meeting-401:14
xichengckerwin merged the branches last week01:14
*** Swami has joined #openstack-meeting-401:14
chigangNice,I will change OPNFV repo to openstack/compass-core branch.01:14
xichengcAlso the baigk/compass-web should be changed to openstack/compass-web as well.01:15
chigangWanglei has some patches about compass-core/compass-web, I will let him merge to openstack/compass-core.01:16
chigangWanglei is offline today01:16
xichengc#action all compass-core/compass-web related code will be submitted to openstack namespace under master branch01:16
xichengcthanks.01:16
xichengcif there's no further questions, we will proceed to the next topic01:17
*** vivek-ebay has quit IRC01:17
xichengc#topic Compass on CentOS701:18
*** openstack changes topic to "Compass on CentOS7 (Meeting topic: Compass Weekly Meeting)"01:18
*** baoli_ has quit IRC01:18
*** baoli has joined #openstack-meeting-401:19
xichengcwe are working on installing compass on a CentOS7 host01:19
xichengcneed to update install.sh, now it only works on CentOS-6.x01:19
chigangCentos 7.1?01:19
kerwinchigang: yes01:20
*** woodard_ has quit IRC01:20
*** SimonChung has quit IRC01:20
xichengcchigang: I will work with kerwin on this.01:20
xichengcchigang: do you think it's necessary to write ansible script for installing compass on CentOS-7?01:21
chigangthere is a patch about install ELK on compass base centos-6.x01:21
xichengcwhere's that patch?01:21
xichengcin openstack gerrit?01:21
*** baoli has quit IRC01:21
chigangnot in gerrit, in local repo01:22
xichengcthen we probably need to make it work on 7.1 now01:22
*** baoli has joined #openstack-meeting-401:22
chigangI know you are updating centos, so we kept it in local git repo01:22
xichengcwshao is planning to obsolete CentOS-601:22
xichengcor at least we should maintain one version?01:22
chigangyes , it need some work to update centos701:23
chigangI think it is no need maintain on centos 6.x01:23
xichengcI see. Then we should also switch compass.iso to centos-7 as well.01:24
chigangcentos 6.x  is too out-dated01:24
chigangright, it will make our ISO smaller01:24
xichengcthat's great news.01:25
xichengc#action xichengc to update install.sh to install compass on centos-701:25
xichengc#action kerwin to switch iso from centos6 to centos701:26
chigangwhen will it be ready?01:26
xichengcI am aiming a week after Thanksgiving.01:26
chigangthanks01:26
*** markvoelker has joined #openstack-meeting-401:27
xichengckerwin needs to travel, so it might take longer01:27
chigangtravel for shopping? :)01:28
xichengcchigang any other comments on this topic?01:28
xichengc:)01:28
kerwinchigang: back to shanghai01:28
xichengc#topic update Compass-CI at Santa Clara lab01:29
*** openstack changes topic to "update Compass-CI at Santa Clara lab (Meeting topic: Compass Weekly Meeting)"01:29
xichengc1. wee need to replace some physical servers, the ones we have right now are too old01:29
xichengc2. with Centos being the compass host now, many CI jobs need to be updated accordingly.01:30
xichengcI will take care of this with help from qingyu01:30
xichengcwe might not be able to do much until "compass on centos-7" is successfully supported.01:30
xichengc#action xicheng to fix CI problems and update to CentOS-701:31
xichengc#action xichengc to fix CI problems and update to CentOS-701:31
xichengc#action qingyu to fix CI problems and update to CentOS-701:31
*** markvoelker has quit IRC01:31
chigang xichengc can we  add some CI for Liberty-running and testing.01:31
xichengcchigang: you mean use cases for testing liberty?01:32
chigang reserve some pod for running liberty01:33
chigang reserve some PODs for running liberty01:33
*** baoli has quit IRC01:33
xichengcyes that should be fine. that's the CI May-meimei is working on.01:34
*** baoli has joined #openstack-meeting-401:34
xichengcThe CI i am fixing is in another cluster for openstack/compass-core end to end test01:34
xichengcit's different from May-meimei's.01:34
chigang we plan to finish libery deployment at the end of this month,  I want some PODs reserved for testing patch merge01:35
xichengcOK.01:35
*** iyamahat has joined #openstack-meeting-401:36
xichengcthere should be no problem01:36
chigangnice01:36
xichengc#topic Compass-web driven deployment01:36
*** openstack changes topic to "Compass-web driven deployment (Meeting topic: Compass Weekly Meeting)"01:36
xichengcWe also need to be able to use compass-web UI to install openstack01:36
xichengcWe have almost finished the work.01:37
xichengcPlanning to get it done by next Monday/Tuesday.01:37
chigangwhich version? V2 , V2.5 or both?01:37
xichengcv2.501:37
xichengcbut I think v2 should be OK as well without much extra work01:39
xichengcwhich version is wanglei working on?\01:39
chigangv2.0 , so I think he needs some time to syn some patch.01:40
*** yamamoto has joined #openstack-meeting-401:40
*** xingchao has quit IRC01:40
xichengcOK. we have another guy He ming here.01:41
*** prashantD has quit IRC01:41
xichengcHe knows UI very well. If wang lei wants some discussion, he ming can join.01:41
xichengc#action xichengc and kerwin to make compass-web driven deployment work01:42
*** woodard has joined #openstack-meeting-401:42
xichengcwe can wrap up about the US side.01:43
xichengcchigang any updates/questions from shanghai side?01:43
*** prashantD has joined #openstack-meeting-401:44
chigangwait01:44
chigang#topic Openstack liberty and ONOS deployment01:45
*** wshao has quit IRC01:45
chigang#info Liberty has release, so we need support it in B-release, it is plan to finish it in next week.01:47
*** Swami has quit IRC01:48
chigang#info there are some jira about openstack and sdn config configuration to recheck.01:48
chigang#info we plan to finish it before Dec. 1001:49
xichengcchigang: thanks for the updates.01:49
chigangthat is all01:49
chigangthanks.01:50
xichengcchigang: we will reserve a pod for liberty task cases.01:50
chiganggreat01:51
xichengcThank you everyone.01:52
xichengc#endmeeting01:52
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"01:52
openstackMeeting ended Wed Nov 25 01:52:31 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:52
chigangthank you all , bye01:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/compass_weekly_meeting/2015/compass_weekly_meeting.2015-11-25-01.10.html01:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/compass_weekly_meeting/2015/compass_weekly_meeting.2015-11-25-01.10.txt01:52
openstackLog:            http://eavesdrop.openstack.org/meetings/compass_weekly_meeting/2015/compass_weekly_meeting.2015-11-25-01.10.log.html01:52
*** fitoduarte has quit IRC01:55
*** woodard has quit IRC01:59
*** Sukhdev has quit IRC02:02
*** bobh has joined #openstack-meeting-402:05
*** SimonChung has joined #openstack-meeting-402:05
*** SimonChung1 has joined #openstack-meeting-402:07
*** May-meimei has quit IRC02:08
*** SimonChung has quit IRC02:10
*** kerwin has quit IRC02:10
*** woodard has joined #openstack-meeting-402:14
*** prashantD has quit IRC02:16
*** woodard has quit IRC02:19
*** xingchao has joined #openstack-meeting-402:19
*** bobh has quit IRC02:20
*** vivek-ebay has joined #openstack-meeting-402:25
*** jwagner is now known as jwagner_away02:25
*** markvoelker has joined #openstack-meeting-402:28
*** markvoelker has quit IRC02:33
*** vivek-eb_ has joined #openstack-meeting-402:34
*** vivek-ebay has quit IRC02:37
*** dims has quit IRC02:39
*** Piet has joined #openstack-meeting-402:51
*** sridhar_ram has quit IRC02:54
*** s3wong has quit IRC02:59
*** jmccrory has quit IRC03:02
*** jmccrory has joined #openstack-meeting-403:04
*** salv-orlando has joined #openstack-meeting-403:05
*** woodard has joined #openstack-meeting-403:15
*** vishwanathj has quit IRC03:17
*** woodard has quit IRC03:19
*** markvoelker has joined #openstack-meeting-403:29
*** woodard has joined #openstack-meeting-403:29
*** woodard has quit IRC03:30
*** markvoelker has quit IRC03:34
*** markvoelker has joined #openstack-meeting-403:35
*** harshs has quit IRC03:36
*** xingchao has quit IRC03:37
*** salv-orlando has quit IRC03:38
*** xingchao has joined #openstack-meeting-403:39
*** salv-orlando has joined #openstack-meeting-403:51
*** salv-orlando has quit IRC03:56
*** xingchao has quit IRC04:14
*** ivar-lazzaro has quit IRC04:16
*** vikasc has joined #openstack-meeting-404:40
*** sdake has quit IRC04:42
*** vikasc has quit IRC04:44
*** iyamahat has quit IRC04:46
*** FallenPegasus has joined #openstack-meeting-404:56
*** vikasc has joined #openstack-meeting-405:09
*** vikasc has quit IRC05:14
*** Piet has quit IRC05:15
*** salv-orlando has joined #openstack-meeting-405:18
*** salv-orlando has quit IRC05:24
*** galstrom_zzz is now known as galstrom05:25
*** nate_gone is now known as njohnston05:27
*** galstrom is now known as galstrom_zzz05:41
*** harshs has joined #openstack-meeting-405:42
*** mfedosin has joined #openstack-meeting-405:44
*** FallenPegasus has quit IRC05:48
*** amotoki has quit IRC05:49
*** zehicle has quit IRC05:54
*** amotoki has joined #openstack-meeting-406:01
*** Sukhdev has joined #openstack-meeting-406:02
*** jpekkari has joined #openstack-meeting-406:02
*** kerwin has joined #openstack-meeting-406:08
*** amotoki has quit IRC06:10
*** numans has joined #openstack-meeting-406:15
*** amotoki has joined #openstack-meeting-406:15
*** vivek-eb_ has quit IRC06:16
*** vikasc has joined #openstack-meeting-406:19
*** yamamoto has quit IRC06:22
*** yamamoto has joined #openstack-meeting-406:23
*** nkrinner has joined #openstack-meeting-406:26
*** vishwanathj has joined #openstack-meeting-406:33
*** amotoki has quit IRC06:39
*** sdake has joined #openstack-meeting-406:40
*** vikasc has quit IRC06:41
*** sdake has quit IRC06:43
*** kerwin has quit IRC06:46
*** mfedosin has quit IRC06:48
*** xingchao has joined #openstack-meeting-406:55
*** amotoki has joined #openstack-meeting-406:57
*** javeriak has joined #openstack-meeting-406:58
*** Sukhdev_ has joined #openstack-meeting-406:59
*** Sukhdev has quit IRC07:03
*** javeriak has quit IRC07:05
*** Sukhdev_ has quit IRC07:06
*** armax has quit IRC07:08
*** FallenPegasus has joined #openstack-meeting-407:10
*** qingyu has quit IRC07:11
*** vivek-ebay has joined #openstack-meeting-407:13
*** mfedosin has joined #openstack-meeting-407:17
*** vivek-ebay has quit IRC07:19
*** harshs has quit IRC07:21
*** sdake has joined #openstack-meeting-407:28
*** javeriak has joined #openstack-meeting-407:31
*** lakshmiS has joined #openstack-meeting-407:32
*** harshs has joined #openstack-meeting-407:32
*** dims has joined #openstack-meeting-407:35
*** sdake has quit IRC07:38
*** salv-orlando has joined #openstack-meeting-407:38
*** dims_ has joined #openstack-meeting-407:39
*** dims has quit IRC07:40
*** salv-orlando has quit IRC07:41
*** javeriak has quit IRC07:42
*** mfedosin has quit IRC07:47
*** javeriak has joined #openstack-meeting-407:47
*** ppetit has joined #openstack-meeting-407:49
*** ppetit has quit IRC07:50
*** javeriak has quit IRC07:54
*** javeriak has joined #openstack-meeting-407:54
*** javeriak_ has joined #openstack-meeting-407:57
*** ppetit has joined #openstack-meeting-407:58
*** javeriak has quit IRC07:59
*** sdake has joined #openstack-meeting-408:09
*** matrohon has joined #openstack-meeting-408:17
*** KLuka__ has quit IRC08:19
*** IlyaG has quit IRC08:21
*** IlyaG has joined #openstack-meeting-408:22
*** javeriak_ has quit IRC08:25
*** IlyaG has quit IRC08:26
*** javeriak has joined #openstack-meeting-408:27
*** javeriak has quit IRC08:32
*** sdake has quit IRC08:41
*** subscope has joined #openstack-meeting-408:44
*** lakshmiS has quit IRC08:48
*** dshakhray has joined #openstack-meeting-408:52
*** sridhar_ram has joined #openstack-meeting-408:54
*** sridhar_ram has quit IRC08:59
*** igordcard has joined #openstack-meeting-409:12
*** mfedosin has joined #openstack-meeting-409:13
*** vivek-ebay has joined #openstack-meeting-409:16
*** vivek-ebay has quit IRC09:20
*** tfukushima has joined #openstack-meeting-409:23
*** salv-orlando has joined #openstack-meeting-409:27
*** salv-orlando has quit IRC09:28
*** Prithiv has joined #openstack-meeting-409:28
*** salv-orlando has joined #openstack-meeting-409:29
*** FallenPe_ has joined #openstack-meeting-409:29
*** FallenPegasus has quit IRC09:31
*** dims_ has quit IRC09:34
*** _degorenko|afk is now known as degorenko09:35
*** kbyrne has joined #openstack-meeting-409:42
*** subscope has quit IRC09:46
*** amotoki has quit IRC09:48
*** salv-orlando has quit IRC09:50
*** kbyrne has quit IRC09:50
*** kbyrne has joined #openstack-meeting-409:50
*** IlyaG has joined #openstack-meeting-409:52
*** bapalm has quit IRC09:53
*** bapalm has joined #openstack-meeting-409:55
*** IlyaG has quit IRC09:57
*** salv-orlando has joined #openstack-meeting-409:57
*** baoli has quit IRC10:06
*** yamamoto has quit IRC10:15
*** subscope has joined #openstack-meeting-410:16
*** pbourke has quit IRC10:17
*** harshs has quit IRC10:18
*** pbourke has joined #openstack-meeting-410:20
*** tfukushima has quit IRC10:21
*** javeriak has joined #openstack-meeting-410:30
*** igordcard has quit IRC10:32
*** iyamahat has joined #openstack-meeting-410:39
*** yamahata has quit IRC10:43
*** iyamahat has quit IRC10:46
*** subscope has quit IRC10:47
*** javeriak has quit IRC10:47
*** FallenPe_ has quit IRC10:47
*** xingchao has quit IRC10:51
*** javeriak has joined #openstack-meeting-410:52
*** xingchao has joined #openstack-meeting-410:52
*** yamamoto has joined #openstack-meeting-410:53
*** yamamoto has quit IRC10:56
*** yamamoto has joined #openstack-meeting-410:57
*** xingchao has quit IRC10:57
*** Fdaisuke has joined #openstack-meeting-411:07
*** Fdaisuke has quit IRC11:09
*** yamamoto_ has joined #openstack-meeting-411:11
*** chem has left #openstack-meeting-411:12
*** yamamoto has quit IRC11:15
*** vivek-ebay has joined #openstack-meeting-411:18
*** yamamoto_ has quit IRC11:20
*** vivek-ebay has quit IRC11:23
*** yamamoto has joined #openstack-meeting-411:25
*** ppetit has quit IRC11:26
*** lakshmiS has joined #openstack-meeting-411:27
*** yamamoto has quit IRC11:32
*** javeriak_ has joined #openstack-meeting-411:33
*** ppetit has joined #openstack-meeting-411:34
*** javeriak has quit IRC11:37
*** marcusvrn_ has joined #openstack-meeting-411:47
*** lakshmiS_ has joined #openstack-meeting-411:47
*** lakshmiS has quit IRC11:50
*** amotoki has joined #openstack-meeting-411:54
*** zeih has joined #openstack-meeting-411:57
*** FallenPegasus has joined #openstack-meeting-412:02
*** IlyaG has joined #openstack-meeting-412:02
*** yamamoto has joined #openstack-meeting-412:02
*** subscope has joined #openstack-meeting-412:02
*** FallenPegasus has quit IRC12:06
*** IlyaG has quit IRC12:07
*** jmccrory has quit IRC12:12
*** alexstav has joined #openstack-meeting-412:14
*** zeih has quit IRC12:18
*** jmccrory has joined #openstack-meeting-412:20
*** dshakhray has quit IRC12:24
*** brunograz has joined #openstack-meeting-412:26
*** zeih has joined #openstack-meeting-412:28
*** javeriak has joined #openstack-meeting-412:29
*** javeriak_ has quit IRC12:29
*** xuhan has quit IRC12:32
*** alexstav has quit IRC12:38
*** alexstav has joined #openstack-meeting-412:39
*** alexstav has quit IRC12:41
*** alexstav_ has joined #openstack-meeting-412:41
*** dims has joined #openstack-meeting-412:42
*** jpekkari has quit IRC12:47
*** zeih has quit IRC12:54
*** Prithiv has quit IRC12:59
*** Prithiv has joined #openstack-meeting-412:59
*** javeriak has quit IRC13:00
*** vmahe_ has joined #openstack-meeting-413:01
*** xingchao has joined #openstack-meeting-413:01
*** javeriak has joined #openstack-meeting-413:02
*** yamamoto has quit IRC13:05
*** bzhou has joined #openstack-meeting-413:06
*** david-lyle has quit IRC13:09
*** salv-orlando has quit IRC13:12
*** dshakhray has joined #openstack-meeting-413:13
*** yamamoto has joined #openstack-meeting-413:19
*** vivek-ebay has joined #openstack-meeting-413:20
*** salv-orlando has joined #openstack-meeting-413:23
*** salv-orlando has quit IRC13:24
*** javeriak has quit IRC13:24
*** salv-orlando has joined #openstack-meeting-413:25
*** vivek-ebay has quit IRC13:25
*** acabot has joined #openstack-meeting-413:33
*** baoli has joined #openstack-meeting-413:45
*** wojdev has joined #openstack-meeting-413:49
*** lakshmiS_ has quit IRC13:49
*** FallenPegasus has joined #openstack-meeting-413:50
*** FallenPegasus has quit IRC13:55
*** vtech has joined #openstack-meeting-413:59
*** seanmurphy has joined #openstack-meeting-413:59
*** jwcroppe has joined #openstack-meeting-414:00
acabot#startmeeting watcher14:00
openstackMeeting started Wed Nov 25 14:00:52 2015 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
*** ashavskiy has joined #openstack-meeting-414:00
*** openstack changes topic to " (Meeting topic: watcher)"14:00
openstackThe meeting name has been set to 'watcher'14:00
acabothi14:00
edleafehi14:01
brunograzhi14:01
vtechhi14:01
vmahe_hi14:01
bzhouhi14:01
seanmurphyhi guys14:01
*** ostroverkhov has joined #openstack-meeting-414:01
jwcroppehi14:01
*** dtardivel has joined #openstack-meeting-414:01
acabotour agenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#11.2F25.2F201514:02
*** vincentfrancoise has joined #openstack-meeting-414:02
jed56hi14:02
*** dane_leblanc has joined #openstack-meeting-414:02
dtardivelBonjour14:03
alexstav_o/14:03
vincentfrancoiseHi14:03
ashavskiyo/14:03
jwcroppeo/14:03
*** alexchadin has joined #openstack-meeting-414:03
*** wojdev has quit IRC14:03
alexchadino/14:03
ostroverkhovo/14:03
acabot#topic Announcements14:03
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:03
acabotregarding the mid-cycle meetup, we have to wait for sballe for updates14:04
*** wojdev has joined #openstack-meeting-414:04
*** wojdev has quit IRC14:04
sballeI am here14:04
*** vivek-ebay has joined #openstack-meeting-414:04
sballesorry about that.14:04
acabotho sorry14:04
sballeI haven't heard anything and I cannot get an answer so let's assume he cannot host it14:04
jwcroppesballe: sounds good - do we want to pursue IBM - in Austin, TX?14:05
sballeacabot: I was doing something else and forgotto join on time :-)14:05
acabotok so do we have an alternative in the same area ?14:05
sballejwcroppe: +1-14:05
sballedefinetly14:05
sballeAustin is awesome14:05
sballeespecilly in the winter14:05
acabotAustin is not very easy for us regarding planes...14:06
sballeBoston is a problem in the winter because travel is unpredictable because if the weather14:06
sballeacabot: like Rennes for us ;-)14:06
jwcroppesballe: I had preliminary discussions with my team and that should be possible, but I will confirm14:06
acabotsballe: ok14:06
jwcroppeacabot: the best option is to get to Heathrow and I believe there is a direct flight from there to AUS14:06
jed56sballe : nice catch :)14:06
sballeacabot: CDG --> Boston --> Austin14:07
acabotjwcroppe: ok so lets confirm Austin next week ?14:07
sballejed56: lol14:07
seanmurphyi think it’s unlikely that we would be able to attend a US-based f2f, unfortunately14:07
*** siwos__ has left #openstack-meeting-414:07
jwcroppeacabot: yes, will try - it's US holiday this week so quite empty, but I will have those discussions next week and hopefully have confirmation by week of 12/714:07
*** siwos__ has joined #openstack-meeting-414:08
acabot#action jwcroppe confirm availability for hosting the mid-cycle in Austin by 12/714:08
sballejwcroppe: can we do it the week of Feb 2?14:09
acabotseanmurphy: we will use public etherpad during the meetup so you will be able to follow our discussions14:09
*** dane_leblanc has quit IRC14:09
jwcroppesballe: I had that week and previous week as options14:09
sballejwcroppe: Yeah I have some other travel tentatively planned for the week before in Portland.14:09
acabotwe have a new wiki page related to Watcher architecture v2 #link https://wiki.openstack.org/wiki/WatcherArchitecturev214:10
jwcroppesballe: we can try the week of 2/2... Tue-Thurs14:10
sballeacabot: cool!14:10
jwcroppeacabot: nice14:10
sballejwcroppe: perfect. thx14:10
acabotits a draft14:10
*** ashavskiy has quit IRC14:11
*** dane_leblanc has joined #openstack-meeting-414:11
acabotand the diagram on top is our first diagram using Dia (thx vmahe for doing it) ;-)14:11
*** ashavskiy has joined #openstack-meeting-414:11
acabotvmahe will soon push the source code in watcher doc and we will be able to review and update it14:11
vmahe_right14:12
jwcroppevmahe_: very nice14:12
acabotunfortunately we will have to update the diagram on the wiki manually for now14:12
vmahe_you'll need to install Dia which is available on many systems14:12
sballevmahe_: Great job! the diagram looks great14:12
acabotbut its better than exporting it from ppt ;-)14:12
sballeacabot: +100 lol14:12
jwcroppeso v2 arch is our target arch for Mitaka?14:13
vmahe_the drawback with Dia is that the source code of the diagram is XML and not easily readable14:13
sballeI really like v2! it is a much cleaner architecture14:13
vmahe_but you can also draw sequence diagrams and class diagrams14:13
vmahe_and this is what Nova team uses :-)14:14
sballevmahe_: I am a big fan of sequemce diagram to explain the API interactions14:14
vmahe_right, i'll work on it later14:14
jed56sballe : vhmahe his also a big fan :)14:14
sballe:014:15
sballe:014:15
acabotso of course, feel free to complete this new wiki page14:15
sballe;)14:15
jwcroppev2 arch = mitaka goal?14:15
acabotjwcroppe: yes14:15
jwcroppeacabot: cool - thx14:15
edleafeI'm a little confused on the diagram - where is the input from the monitoring/metering?14:15
acabotedleafe: the idea of putting this picture is just to give you an overview of the output of dia14:16
acabotedleafe: the diagram needs to be updated14:17
*** slaweq_work has joined #openstack-meeting-414:17
vmahe_yes, the diagram needs to be refined and a focus on the metering part must be done14:17
edleafeacabot: ah, thanks. Thought I needed more coffee or something :)14:17
acabotjust to say "OK lets use this tool for our diagrams"14:17
jwcroppeedleafe: lol14:17
jwcroppewhere is the dia source btw?14:17
sballeI think I need more coffee too14:17
acabotjwcroppe: will be in watcher doc folder today14:18
jwcroppegreat, will look - in git?14:18
acabotbefore we review actions, just a quick reminder on code reviews14:18
acabotplease use workflow -1 when your code is a work in progress14:19
acabotand do not review code when the workflow is set to -114:19
acabot#topic Review action items14:19
*** openstack changes topic to "Review action items (Meeting topic: watcher)"14:19
vmahe_jwcroppe: yes, the source code will be in some subfolder of watcher/doc14:19
jwcroppe+114:20
*** dane_leblanc has quit IRC14:20
sballe+114:20
*** wojdev has joined #openstack-meeting-414:20
bzhou+114:20
acabotceilometer integration is now merged (specs and code)14:20
edleafe\o/14:21
*** ashavskiy has quit IRC14:21
sballeo/14:21
*** dane_leblanc has joined #openstack-meeting-414:21
sballeThis is a great step. thanks jed56 acabot dtardivel14:21
sballeand vincentfrancoise14:21
*** ashavskiy has joined #openstack-meeting-414:22
acabotthe code has been merged before the specs (sorry about that), we will do it in the right order next time ;-)14:22
jwcroppeyes - very good.  yeah, need to follow process :)14:22
sballeacabot: no big deal this time14:22
acabotloading strategies is also merged14:22
sballejwcroppe: migth disagree14:22
sballeacabot: +114:23
acabotths to vincentfrancoise and jed5614:23
sballe+114:23
*** yamamoto has quit IRC14:23
acabotthere is a current review on the glossary https://review.openstack.org/#/c/246370/14:23
seanmurphycan we have a one liner on what the ceilometer integration provides?14:23
acabotthis is becoming really important because we need to do code refactoring when we will all agree on this glossary14:24
bzhouthanks b-com team. I am using the new code to setup my environment14:24
acabotseanmurphy: Ceilometer integration allows Watcher to collect metrics from Ceilometer instead of using its own metering chain14:25
vmahe_yes, the glossary is important because we need to make sure everybody shares the same definitions of business objects regarding Watcher and names of the technical components14:25
*** pbourke has quit IRC14:25
jwcroppewill review today14:26
vmahe_we have renamed the ex "State DB" into a more comprehensive word "Cluster Data Model"14:26
sballevmahe_: I will take another pass at it today14:26
acabotso if everybody can review the glossary before end of week it would be great14:26
bzhouwhy we use "cluster" not "cloud"?14:26
seanmurphyacabot: …and puts them in watcher db, right? with some further aggregation/processing, i guess…14:26
edleafebzhou: because everything, including Watcher, is part of the cloud14:27
vmahe_ok, I'm currently taking into account seanmurphy reviews14:27
jed56seanmurphy : the metrics are stored into the ceilometer backend14:27
seanmurphyvmahe_: i will review the glossary - currently working on it14:28
bzhouedleafe: I thought cluster has a specific word and may imply some meaning to people14:28
vmahe_bzhou : because "Cloud" is a too confusing word, it means a lot of things depending on who you talk to14:28
*** pbourke has joined #openstack-meeting-414:28
vmahe_we have defined the word "Cluster" in the Glossary14:28
sballevmahe_: BTW so does Cluster14:28
acabot#action sballe jwcroppe edleafe seanmurphy bzhou alexstav_ acabot review the glossary #link  https://review.openstack.org/#/c/246370/14:29
edleafebzhou: true, but it's impossible to find a word that doesn't have another meaning. That's why a glossary is helpful to learn what is meant within Watcher when we use it14:29
acabotedleafe: +114:30
sballeedleafe: to me as long as we agree on Cluster or Cloud and we define it in the glossary we should be fine14:30
vmahe_I couldn't find an official word hich means an Openstack Controller + some Compute nodes. Is there anu ?14:30
vmahe_any ?14:30
*** ashavskiy has quit IRC14:30
edleafesballe: of course, but we should always try to settle on the term that is less potentially confusing14:30
brunograzvmahe_: Compute cluster I guess14:30
edleafesballe: "cloud" is so overused that most people won't understand14:31
vmahe_and we don't intend to optimize the whole Cloud, right ? :-)14:31
sballeedleafe: so is Cluster because many places people are using Cloud and Cluster for the same ;-)14:31
vmahe_we'll make the Cloud a better place (for those who know the "Silicon Valley serie"14:32
sballevmahe_: The thing is that down the road I can see us optimize storage  or the Datacenter14:32
*** ashavskiy has joined #openstack-meeting-414:32
sballeWe can use Cluster as long as it include storage14:32
acabot+114:33
vmahe_sballe: yes, you're totally right. But today what we put in the Glossary is what is available in Watcher14:33
sballeIntel's interet is beyond the compute cluster14:33
edleafesballe: http://dilbert.com/strip/2011-01-0714:33
vmahe_Once the Intel blueprints are implemented and merged, we can update the Glossary consequently, no ?14:34
sballeedleafe: love it lol14:34
jed56lol14:34
*** pbourke has quit IRC14:34
sballeGlossary will be hard to change once the project is going14:34
sballeI would like the Glossary to be a long term thing14:34
vmahe_I'm not sure because the Glossary may sometimes be related to what features are in Watcher14:34
vmahe_I will be a living document, like the devs, tests, specs, ...14:35
*** Swami has joined #openstack-meeting-414:35
acabotsballe: not sure we can fix long term definitions as the product will evolve, I think we should keep what's working in Watcher in the glossary and update it all the way14:36
sballelike I said as long as Cluster includes storage and is not a compute cluster I can be talked into using the word Cluster14:36
sballeacabot: ^^14:36
edleafejust as long as we don't overload 'aggregate' any more than it is :)14:37
acabotsballe: ok lets continue the discussion on Gerrit ;-)14:37
vmahe_ok, I'll add some words about the storage part in the glossary but note that today Watcher Applier does not control Cinder or Swift, only Nova14:37
jwcroppe+114:37
jed56acabot +114:37
edleafeacabot: yes, Gerrit comments are more useful14:37
acabot#topic Blueprint/Bug Review and Discussion14:37
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:37
acabotas there are now many BP on launchpad, we should define series14:38
acabotto fix deadlines for BP14:38
acabotwe can use the same series as other OpenStack projects like Mitaka-1, 2, 3 every 2 months14:39
*** wojdev has quit IRC14:39
sballeacabot: +114:39
acabotor use any other kind of versioning like 0.22, 0.22.114:39
*** wojdev has joined #openstack-meeting-414:39
acabotdo you want to stick to OpenStack versioning ?14:40
*** wojdev has quit IRC14:40
*** yamamoto has joined #openstack-meeting-414:40
acabotor you dont care... :-)14:41
dtardivelacabot: 0.22.0 0.22.1 are tags, reflecting adding new feature implementation14:42
acabotok, we will use the OpenStack versioning for BP14:42
*** javeriak has joined #openstack-meeting-414:42
dtardivelacabot: Mitaka-1, 2, 3 are targeted releases14:42
acabot#action acabot add series in launchpad with Mitaka-N model14:43
jwcroppe+114:43
dtardivelan we have to define which BP and bugs we want to target for each release I think14:43
acabot+114:43
edleafedtardivel: that's true, but some projects release when the code is ready, while others follow a fixed release14:44
edleafedtardivel: so the question is target dates vs. whenever ready14:44
edleafefor releases14:44
jwcroppei think for where Watcher is now, we target whenever ready14:44
sballe+114:44
bzhoujwcroppe:+114:45
dtardivel+114:45
acabotjwcroppe: and we use only BP priority ?14:45
acabotfor ordering14:45
*** bobh has joined #openstack-meeting-414:45
acabotIntel's BP needs to be split in 4 BPs, sballe am I right ?14:46
sballeyes bzhou is working on it14:47
acabotok great thanks bzhou14:47
sballebzhou: took this over from nishi and I14:47
bzhousballe: got it14:47
sballe:-)14:47
acabotthe BP https://blueprints.launchpad.net/watcher/+spec/well-defined-interfaces is probably to large and we also need to split it for each watcher component14:47
sballebzhou: you are working with junjie on this right?14:48
bzhousballe: yes14:48
sballeperfect thx14:48
tpeoplesacabot:  i can take that14:48
acabotok, great14:48
sballebzhou: and you guys are starting on the watcher-specs. right?14:48
tpeoples#action tpeoples split up https://blueprints.launchpad.net/watcher/+spec/well-defined-interfaces14:48
acabot#action split https://blueprints.launchpad.net/watcher/+spec/well-defined-interfaces for each Watcher component14:48
acabot#action tpeoples split https://blueprints.launchpad.net/watcher/+spec/well-defined-interfaces for each Watcher component14:49
tpeoples:)14:49
acabot#action bzhou split https://blueprints.launchpad.net/watcher/+spec/nishi-ahuja-energy-efficienct-dc is 4 BPs14:49
*** sdake has joined #openstack-meeting-414:49
acabotwe plan to add a BP to display a performance indicator to Watcher14:50
acabotI mean like "this actions plan will allows you to save 10%..."14:51
jed56performance indicator regarding the goal we want to achieve14:51
acabotanyone from create-net today ?14:52
acabotlast point, we should set a priority for this BP https://blueprints.launchpad.net/watcher/+spec/watcher-add-actions-via-conf14:53
*** sdake has quit IRC14:53
bzhousballe: yes, creating specs under watcher-specs. One question is that we may not be able to link more than one specs to one bp. But it's not a big deal anyway.14:54
sballebzhou: do we need that BP for our q4 poc?14:54
sballehttps://blueprints.launchpad.net/watcher/+spec/watcher-add-actions-via-conf14:54
jwcroppespec<-->BP is 1-114:54
*** pbourke has joined #openstack-meeting-414:54
sballebzhou: that is why we are diciding up the big BP into 4 smaller ones14:55
sballes/dividing14:55
acabotsballe: one thing you should keep in mind for your poc is that we dont apply actions today14:55
acabotsballe: you will get an actions plan from Watcher14:56
bzhouthe watcher-add-actions-via-conf could help for our q4 poc, but as I know, currently it only use migrate meta-action14:56
acabotsballe: but we won't run the actions as its really "infrastructure" dependant14:56
sballeacabot: I agree and was going to write that but then had t fix some typos and you text came out first14:57
acabotsballe: ok14:57
bzhouacabot: so it means we only support advisory mode atm?14:57
acabotbzhou: yes14:57
tpeoplesDo I need to write a spec for https://blueprints.launchpad.net/watcher/+spec/devstack-plugin ? it won't be affecting anything public and shouldn't be changing the actual watcher code, so, seems like a candidate for a trivial spec14:58
*** jwagner_away is now known as jwagner14:58
acabottpeoples: not sure you need a spec for that14:58
tpeoplesi don't think i do :P14:59
acabotyou can start working on it, I will set it as started14:59
bzhoutpeoples: it's quite straightforward, so it's ok to just implement it:-)14:59
*** Ng has joined #openstack-meeting-414:59
acabotwe are running out of time14:59
jwcroppeyeah, no spec needed for that14:59
*** Prithiv has quit IRC14:59
acabotopen discussions on our channel if you like15:00
edleafetpeoples: there aren't a number of ways to do that, so no spec is needed15:00
acabotthank you15:00
acabot#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
edleafethanks acabot15:00
openstackMeeting ended Wed Nov 25 15:00:30 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
sballebye15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2015/watcher.2015-11-25-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2015/watcher.2015-11-25-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2015/watcher.2015-11-25-14.00.log.html15:00
jed56bye15:00
Ng#startmeeting vahana15:01
openstackMeeting started Wed Nov 25 15:01:19 2015 UTC and is due to finish in 60 minutes.  The chair is Ng. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: vahana)"15:01
openstackThe meeting name has been set to 'vahana'15:01
*** alexchadin has quit IRC15:01
*** ostroverkhov has quit IRC15:01
jasondotstarGreetings15:01
jasondotstar#topic roll call15:02
NgSorry, I didn't realise that was going to make me the chair :)15:02
jasondotstarhehehe15:02
jasondotstarno worries15:02
jasondotstargo for it15:02
*** alexstav_ has quit IRC15:02
NgI think, for the purposes of future history, we might start with a quick introduction about what Vahana is?15:02
*** nihilifer_mobile has joined #openstack-meeting-415:02
Ng#topic Introduction15:03
*** openstack changes topic to "Introduction (Meeting topic: vahana)"15:03
jasondotstarsure15:03
NgThere might still be room for disagreement about what Vahana is, so this probably shouldn't be seen as set in stone :)15:03
Ngbut we're building an iOS client for OpenStack, in the form of one or more frameworks for interacting with the OS API, and a front end app15:04
jasondotstarThere was an effort put together back in 2010 to achieve a similar goal, but it never took off as a mature project15:05
Ng(and the code hasn't changed for 4 years, making it a bit rough to use with current OpenStack)15:06
*** vincentfrancoise has left #openstack-meeting-415:06
jasondotstar+115:06
Ngso our intention is to start pretty much over15:06
*** bzhou has quit IRC15:06
*** vikasc has joined #openstack-meeting-415:07
Ngalso for the historians of the future, I think jasondotstar is leading this project, unless he objects strongly to that?15:07
jasondotstarI don't object.15:07
Ng\o/15:07
jasondotstarexcited to make the attempt to re-ignite what I believe is a valuable companion client for OpenStack Admins15:08
Ngjasondotstar: anything else on introduction stuff? or shall we move on?15:08
jasondotstarnope, let's keep moving15:08
*** bobh has quit IRC15:08
NgI was thinking we should talk a little about goals for the project and what we want the app to be capable of15:09
jasondotstarsure15:09
Ng(and how we can test those ideas against what users actually want)15:09
Ng#topic Goals and Use Cases15:09
*** openstack changes topic to "Goals and Use Cases (Meeting topic: vahana)"15:09
jasondotstarthis is probably a good time to share the etherpad link?15:09
*** rbak has joined #openstack-meeting-415:09
Nggood point!15:09
Ng#link https://etherpad.openstack.org/p/openstack-mobile-ios-brainstorm15:09
NgI have to admit that I am more interested in, and motivated by, the underlying framework stuff, than the visuals of the app, but if we're making both, it would seem to be sensible to make an app that is useful and compelling :)15:10
jasondotstaragreed. I'm interested in both aspects, but I'm hoping that we get some app designer types to join us15:11
Ngwe should probably have a long-term action to actively try to involve the UX folk, but it might be a little early for that15:11
jasondotstarthat way the under-the-hood guys can work on that exclusively.....15:12
jasondotstar+115:12
Ng#action someone to loop in UX folk15:12
jasondotstarI have a couple of crude attempts to mockup UX but I'd rather see someone else with UX chops tackle that.15:13
Ngjasondotstar: what sort of vision do you have for the app itself? a nice interface to all the features of OpenStack, or more of a dashboard kinda thing? (or both)15:14
*** avarner has joined #openstack-meeting-415:15
jasondotstarI think the near term goal should be a dashboard view15:15
jasondotstarb/c I think that most OpenStack admins would appreciate the ability to get a quick glance of what's going on in their OS deployments15:15
jasondotstarthen in an iterative way15:15
jasondotstarwe can add actionable features15:15
jasondotstarfor each of the components15:16
jasondotstarstarting w/ nova I'd say.15:16
Ng+115:16
jasondotstarlaunching a VM, rebooting a VM, creating a new VM15:16
jasondotstarsimple rest API calls15:16
Ng#agreed early goal to be a simple dashboard view15:16
jasondotstari dont think console access is somethign we should tackle just yet..15:16
jasondotstareventually we move through the core components15:17
jasondotstaradding new networks via neutron15:17
NgThat has the potential to explode complexity in a lot of ways, and there are already very very good apps that just do VNC/SSH/etc, so we might want to look at their URL schemes, so we can do Open With... type functionality15:17
jasondotstaradding storage, etc. etc.15:17
jasondotstar+115:17
jasondotstar+1 on open with...15:18
Ng#agreed console access is likely out of scope, when excellent third party apps exist for doing that, and have URL schemes15:18
*** ashavskiy has quit IRC15:19
jasondotstarthere's also the goal15:19
jasondotstarof making the dashboard view skinnable15:19
Nghuh, talking of URL schemes makes me think that it might be nice if admins could share their current view with each other, so like you're looking at a problem machine and you can do a standard iOS share sheet to send a URL to your colleagues so they can jump straight to the same thing you're looking at15:19
*** bobh has joined #openstack-meeting-415:20
jasondotstarhmmm15:20
jasondotstarinteresting15:20
jasondotstarI like that idea15:21
Ngsince everything has a UUID, it shouldn't be super hard to make a vahana:// URL scheme that can express a location in an infrastructure15:21
jasondotstar+115:21
Ngas for the framework, I think my main goal there is that it grows into something that anyone working on some internal enterprise app, or a public cloud related app, can integrate the framework and easily interact with an OpenStack cloud15:23
Ngjasondotstar: I'm not really sure who we should be reaching out to to talk about what operators/tenants would actually like out of an app, so maybe we have an action item there - figure out who to talk to?15:24
Ng(I'm thinking someone at the foundation, they probably do the most centralised talking to operators at least)15:25
Ngmaybe also some of the folk running large and/or public OpenStack instances?15:25
jasondotstaryes15:26
jasondotstarwe should add that as an action item.15:26
jasondotstarI think having a list of use cases and/or wish list would be valuable15:26
jasondotstarone other thing I wanted to mention: perhaps the project is a set of iOS libraries that we release, as opposed to an actual app15:26
jasondotstarNg:  re: large/public OS instances - yes, something to test against would be good15:26
Ng#action someone to figure out who we should talk to about identifying specific use cases15:26
jasondotstarI can almost see someone using the libraries to create a *very* niche app15:27
Ngjasondotstar: I don't disagree, a single app is likely to be problematic, since many installations of OpenStack differ wildly in their features/versions/etc15:27
jasondotstarright....15:27
jasondotstarwe should look at considering the project as a collection of libraries and/or frameworks15:28
Ng#action someone to start talking to large/public OpenStack installs for testing and use-case-gathering15:28
jasondotstarthat might be more palpable to those who are simply going to take what we have and create something of their own15:28
Ng+115:29
Nga framework of reusable UIView subclasses that use the API framework seems like it would be super useful15:30
jasondotstarright15:30
Nganything else on goals and use cases?15:30
jasondotstarnope, great start I think.15:30
*** harshs has joined #openstack-meeting-415:31
Ngjasondotstar: any particular topic you'd like to do next?15:31
jasondotstarlet's see, we had a couple of questions on the etherpa15:32
jasondotstar*etherpad15:32
jasondotstarlike how early should we start creating blueprints, specs, etc.15:32
jasondotstarare we basically whiteboarding this out on etherpad until we nail down what direction we're taking15:33
NgI think we're still at a whiteboarding stage, yes. I feel like I have a bunch more R&D to do on some core classes and project infrastructure before I'm ready to start proposing solid plans for work15:34
jasondotstaror should we start with the end in mind as far as getting as much documented as we can15:34
jasondotstar+115:34
jasondotstartjat15:34
jasondotstar*that's my feeling as well.15:34
Ng#agreed we're still at whiteboarding/R&D stage, too early for blueprints/specs15:34
jasondotstarthe R&D we're currently doing....15:35
Ng#topic Current R&D15:35
*** openstack changes topic to "Current R&D (Meeting topic: vahana)"15:35
jasondotstarwe're both working using Swift as the pref. lang?15:35
Ngyep15:36
NgI've been working on figuring out a sane way to have a core REST client class that I think most of the API framework will inherit from15:36
Ngcurrently using AlamoFire15:36
Ngmy next intention is to figure out using GYP to generate .xcodeproj files15:36
Ngbut there are so many fundamental tech decisions that we need to make :/15:37
jasondotstaryep15:37
jasondotstarperhaps we start with evaluations15:37
jasondotstarof different ways of delivering this work15:37
Ngthe big one I have at the moment is how to handle the results of the asynchronous REST operations - the options being delegates, blocks, KVO or NSNotificationCenter15:37
NgI'm currently running with blocks for no particularly good reason15:38
*** FallenPegasus has joined #openstack-meeting-415:38
NgI think I want to have some NSNotificationCenter stuff too, so the API framework can emit things like "I have successfully authenticated", for apps to react to15:40
jasondotstarKVO or observation is like the listener pattern15:40
*** matrohon has quit IRC15:41
jasondotstar+1 re: NSNotificationCenter15:41
Ng#agreed API framework should send NSNotifications of important/relevant events15:41
Ngblocks feel like the more "modern Apple" way of doing it, but the modern hispter way would be to use ReactiveCocoa ;)15:42
jasondotstarhehehe15:43
*** FallenPegasus has quit IRC15:43
jasondotstarso is it worth it for us to evaluate a couple different ways to 'do things'15:44
jasondotstarperhaps present the pros/cons15:44
jasondotstarthen agree on which way is best15:44
jasondotstarsorta like how you arrived at using AlamoFire vs. NSHTTP15:44
NgI don't think that would be a bad idea, but I'm not sure we'll know which is best until we get much higher up the stack and discover that <foo> turns out to be painful15:45
*** angdraug has joined #openstack-meeting-415:45
jasondotstar+115:45
NgI think the delegate pattern is probably unsuitable long-term, because you're going to end up with the same sort of mess that happens with UITableViewDelegate/DataSource, where each delegate method first has to figure out which of 18 different operations are being sent to it15:46
jasondotstarYES15:47
Ngand OpenStack has a *lot* more operations than UITableView ;)15:47
Ngjasondotstar: anything else on R&D progress?15:49
jasondotstarwhat are you testing against, btw?15:49
Ngdevstack15:49
jasondotstarok that's cool.15:49
jasondotstarsame here.15:49
Ngbut at this stage I could honestly be testing against any URL that emits JSON ;)15:49
jasondotstarthat's true15:49
jasondotstarok that's it on R&D15:50
jasondotstarI think we can open the floor for general q&a15:50
Ng#topic Q&A15:50
*** openstack changes topic to "Q&A (Meeting topic: vahana)"15:50
jasondotstarwe've got about 10mins left15:50
Nghow are you finding Swift? :)15:51
jasondotstarI like it. it's very javascript like15:51
NgI feel like I'm understanding more than half of the code that I'm writing, but by no means all15:51
jasondotstarbut here's the thing15:51
jasondotstarI dont really like js.15:51
jasondotstarsyntactically it's better than OBJ-c15:52
Ngthere's certainly a lot more native syntax to deal with15:52
jasondotstaryeah15:53
*** numans has quit IRC15:53
jasondotstarI do enjoy the playground15:53
Ngyes15:54
jasondotstarhaving a place to simply run code w/o building an app15:54
Ngdid you discover the trick for having a playground run indefinitely, for async stuff?15:54
jasondotstaris helpful15:54
*** Sukhdev has joined #openstack-meeting-415:54
jasondotstarno..... plz share that one15:54
Ngimport XCPlayground15:55
NgXCPlaygroundPage.currentPage.needsIndefiniteExecution = true15:55
jasondotstarok15:56
*** iurygregory has left #openstack-meeting-415:56
jasondotstarnice!15:56
*** xingchao has quit IRC15:57
jasondotstarI'll give that a shot15:58
Ng:)15:58
NgI don't think I have anything else for today15:58
jasondotstarwell, I think that's it for our first meeting.15:58
Ng\o/15:58
Ng#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
jasondotstarI'm done. nice job chairing15:58
openstackMeeting ended Wed Nov 25 15:58:45 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vahana/2015/vahana.2015-11-25-15.01.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vahana/2015/vahana.2015-11-25-15.01.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/vahana/2015/vahana.2015-11-25-15.01.log.html15:58
jasondotstarNg++++15:58
jasondotstartoo bad there's not karma bot :-)15:59
Nghah15:59
jasondotstars/not/no15:59
jasondotstarthx again15:59
*** Ng has left #openstack-meeting-416:00
*** xingchao has joined #openstack-meeting-416:03
*** daneyon_ has quit IRC16:08
*** dims has quit IRC16:09
*** daneyon has joined #openstack-meeting-416:09
*** armax has joined #openstack-meeting-416:10
*** Piet has joined #openstack-meeting-416:10
*** dims has joined #openstack-meeting-416:11
*** xingchao has quit IRC16:11
*** harshs has quit IRC16:13
*** vikasc has quit IRC16:13
*** xingchao has joined #openstack-meeting-416:13
*** vikasc has joined #openstack-meeting-416:15
*** xingchao has quit IRC16:18
*** bobh has quit IRC16:18
*** IlyaG has joined #openstack-meeting-416:18
*** vikasc has quit IRC16:19
*** Prithiv has joined #openstack-meeting-416:20
*** IlyaG has quit IRC16:23
*** Sukhdev has quit IRC16:23
*** inc0 has joined #openstack-meeting-416:24
*** dane_leblanc has quit IRC16:24
SamYaple#startmeeting kolla16:29
openstackMeeting started Wed Nov 25 16:29:08 2015 UTC and is due to finish in 60 minutes.  The chair is SamYaple. Information about MeetBot at http://wiki.debian.org/MeetBot.16:29
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:29
*** openstack changes topic to " (Meeting topic: kolla)"16:29
openstackThe meeting name has been set to 'kolla'16:29
*** bmace has joined #openstack-meeting-416:29
SamYaple#topic rollcalll16:29
*** openstack changes topic to "rollcalll (Meeting topic: kolla)"16:29
inc0o/16:29
bmacestill a minute early, but here16:29
*** subscope has quit IRC16:29
britthousero/16:29
pbourkehi16:29
*** stvnoyes has joined #openstack-meeting-416:30
*** angdraug has quit IRC16:30
*** jmccarthy has joined #openstack-meeting-416:30
SamYaplemy clock might me a minute off16:30
jmccarthyo/16:30
SamYapleim going to give a few for the checkin16:30
*** seanmurphy has quit IRC16:30
inc0yeah, it doesn't seem we have quorum16:30
inc0I will use this precious moment to announce: oslo.log is broken16:31
SamYapleinc0: just hold up, give it til 163516:31
*** akwasnie has joined #openstack-meeting-416:31
*** rhallisey has joined #openstack-meeting-416:31
rhalliseyhi16:31
*** jwagner is now known as jwagner_away16:32
akwasniehey :)16:32
SamYapleo/16:32
*** jwagner_away is now known as jwagner16:32
SamYaple#topic announcements16:33
*** openstack changes topic to "announcements (Meeting topic: kolla)"16:33
SamYaplenihilifer is now officially a core! w00t16:33
SamYapleits been a 'known' thing but he just got added to the group16:34
SamYapleso congrats16:34
akwasniecongrats once again :)16:34
inc0Michal have became most popular first name in core team16:34
SamYaplei vote we call him Michal2 in person16:34
SamYaplethats all the announcements I know of, anyon have anything to add16:34
rhalliseynada16:34
nihilifer_mobileo/16:34
nihilifer_mobilethanks again for nominating me16:35
SamYaple#topic status of oslo.log16:35
*** openstack changes topic to "status of oslo.log (Meeting topic: kolla)"16:35
SamYapletake it away inc016:35
inc0ok, well, akwasnie was battling logging, I'm battling logging and OSAD guys said they have lots of problems with it as well16:36
SamYaplethe OSA guys arent using syslog though16:36
SamYaplethe write to file then read with external syslog16:36
inc0yeah, because it was broken16:36
inc0they experienced horrible wait conditions as they say16:36
SamYapledetails?16:37
SamYapleinc0: you still there?16:38
inc0odyssey4me> inc0 some services don't use the library in the right way - often causing the service to hang if, for instance, you restart rsyslog16:38
SamYapleinc0: no thats a bug in rsyslog16:39
SamYaplethats been fixed in upstream things16:39
inc0ok, I'll tell them then16:39
SamYaplewe should probably check our versions are good16:39
SamYaplewell there is _a_ bug that will do that should i say16:39
SamYaplethey may well have found a different one, but the bug i know about blocks on rsyslog restart16:40
SamYapleand that probably hangs the service16:40
SamYaplebut we havent experinced that, what we experince is logging doesnt work with errors16:40
SamYapleany progress on that front?16:41
pbourkeI thought akwasnie fixed that recently16:41
akwasniei just repaied keystone errors16:41
pbourkecan the same fix be applied across the rest?16:42
SamYapleno thats apache16:42
akwasniebut tracebacks may not work becouse they are handled as errors16:42
SamYaplethe openstack services that use oslo.log still push stack traces and errors to stderr16:42
akwasnieand the way to log tracebacks is to handle them as exceptions in logging python module16:42
akwasnieand then, they can be logged to rsyslog16:42
*** ajmiller has joined #openstack-meeting-416:43
SamYaplefor the openstack servies, there appears to be an option to do just that16:43
SamYaplewe arent enabling it16:43
inc0SamYaple, which one?16:43
SamYapleuse_stderr16:43
akwasniecan it be used globally or with every logging call?16:44
SamYapleits in the conf for the service16:44
SamYaplelike 'verbose=True' 'stderr=False'16:44
SamYapleor use_stderr=False16:44
akwasnieok16:45
inc0I'll play around it16:45
SamYapleim not sure thats going to do what we want, but im not sure I fully understand the issue16:45
akwasnieinc0 submitted a bug16:45
akwasniehttps://bugs.launchpad.net/kolla/+bug/151938116:45
openstackLaunchpad bug 1519381 in kolla "Tracebacks aren't logged to rsyslog" [Critical,In progress] - Assigned to Michał Jastrzębski (inc007)16:45
inc0because I can't get logging.conf to work16:45
*** Sukhdev has joined #openstack-meeting-416:45
akwasnieneither did i16:45
inc0akwasnie, but you didn't try use_stderr=False right?16:45
akwasnieyes, i missed this one16:46
SamYaple#topic liberty 1.1 release16:47
*** openstack changes topic to "liberty 1.1 release (Meeting topic: kolla)"16:47
SamYapleso we are doing very well with the bugs16:47
SamYaple#link https://bugs.launchpad.net/kolla/liberty/+bugs16:47
SamYapleof those 3, 2 are in-progress upstream16:47
SamYapleif you know or additional bugs that affect liberty, please tag them or file them16:47
SamYaple#link https://launchpad.net/kolla/+milestone/mitaka-116:48
*** javeriak has quit IRC16:48
SamYaplethe Essential blueprints that are not implemented are still outstanding16:48
*** javeriak has joined #openstack-meeting-416:48
*** bobh has joined #openstack-meeting-416:48
SamYapleI may not be able to get to the version tagging one16:49
britthouserI've done some reading on mine (keepalived).  Seems straightfoward, i'm just working on getting a multinode dev setup so I can test it.16:49
*** vinkman has joined #openstack-meeting-416:49
SamYaplebritthouser: no problem! if you need any help hit up the channel.16:49
britthouserWill do, probably first of next week.16:49
*** iyamahat has joined #openstack-meeting-416:49
SamYaplei havent seen sdake around alot, but he has other more important things. would someone like to take over the ovs data container work?16:50
SamYapleit should be a simple fix16:50
*** iyamahat has quit IRC16:50
SamYaplethe fix should actually be entirely ansible code16:50
*** iyamahat has joined #openstack-meeting-416:50
rhalliseySamYaple, it's just using the existing data container, but mounting in the correct dirs right?16:51
rhalliseysounds fine16:51
rhalliseyI can take it if needed16:51
SamYaplerhallisey: correct16:51
*** dane_leblanc has joined #openstack-meeting-416:51
SamYapleyea it should be a quick one16:51
SamYaplewe just want the ovs db in its own volume16:51
*** nihilifer_mobile has quit IRC16:52
rhalliseysure16:52
*** galstrom_zzz is now known as galstrom16:52
*** IlyaG has joined #openstack-meeting-416:52
SamYaple#topic Kolla-rolled docker module16:52
*** openstack changes topic to "Kolla-rolled docker module (Meeting topic: kolla)"16:52
SamYaple#link https://review.openstack.org/#/c/248812/16:52
SamYapleSome background on this:16:52
SamYapleAnsible folks currently control the docker module that we use. This has lead to us waiting on them and forcing new versions of ansible on the users _just_ to get a simple bug fix16:53
*** javeriak_ has joined #openstack-meeting-416:53
SamYaplefor example, the 1.8.2 docker version pin is because of ansible16:53
*** javeriak has quit IRC16:53
SamYapleThey have stated they will not fix the v1 registry pulling for the docker module16:53
inc0SamYaple, this is functional?16:53
SamYapleinc0: no, its WIP16:54
inc0ok16:54
SamYapleright now it just returns a list of all running containers16:54
SamYapleSo the idea with this module is to build our own so we can be in control of bug fixes16:54
*** bobh has quit IRC16:54
inc0but that means we'll also fix the bugs ourselves - more code to maintain16:54
SamYaplethis module is so critical to us we can't wait for a bugfix or new feature upstream and _force_ ansible upgrades locally16:55
SamYapleagreed, but right now i submit bug fixes to ansible upstream16:55
SamYaplethat would just be internalized16:55
nihilifercan't we pick up the docker module from ansible repo instead of writing it from scratch?16:55
SamYapleadditionally we wont be as complicated as the ansible module because we dont need to support all versions of docker and all versions of docker-py16:55
*** dane_leblanc has quit IRC16:56
SamYaplenihilifer: licensing16:56
SamYaplenihilifer: its gplv3 so we cant fork it16:56
nihiliferaww, ok16:56
*** jwcroppe has quit IRC16:56
SamYaplethe good news about this is we will not be forced to upgrade to ansible 2.0 if we continue down this "build-your-own-module" front16:56
SamYaplewe will be running ansible 2.0 in the kolla-ansible container, but not require it on the host16:57
SamYapleany thoughts on doing this?16:57
SamYaple(creating our own module)16:57
rhalliseyhow long will we have to do this?16:58
rhalliseyin other words is there an end for this16:58
britthouserI was thinking along the same lines16:58
rhalliseybecause in a sense it s worries me16:58
britthouserIf there is an end, we should still be submitting fixes to ansible's module too, right?16:58
SamYaplenope. we will carry this for the life of the project, otherwise we are in the same boat again, waiting on ansible to improve kolla16:58
nihiliferis it technically possible to use different ansible modules under some condition? it would be nice to use upstream module when running ansible 2.0 in future16:59
SamYaplenihilifer: what do you mean?16:59
rhalliseysay the ansible community were to listen to us more, would it solve our problem?16:59
SamYapleno16:59
SamYaplethat would still me a forced ansible upgrade to the latest version to improve kolla17:00
inc0they explicitly don't want to fix it in 1.x17:00
nihiliferSamYaple: i mean whether it's possible to call different modules with the same arguments, and pick up module to run by some if conditional17:00
nihiliferto be able to use upstream docker module if someone will run ansible >=2.017:00
SamYaplenihilifer: if the arguemntes match up, you could change the name of the module in ansible, yea17:00
SamYapleoh no17:00
rhalliseycould we have kolla-ansible 2.017:00
*** sambetts has joined #openstack-meeting-417:00
SamYaple-2 on that17:01
rhalliseyand a kolla-anisble 1.x17:01
SamYaplei dont want to maintain twice our code base17:01
SamYapleill maintain this module alone before we duplicate our code base like that17:01
rhalliseywell the opposing view is the maintain a module17:01
inc0SamYaple, maintaining "alone" is not too scallable, we need full community support on this17:01
SamYaplei know17:02
SamYapleso the issue is we are hamstrung right now17:02
nihiliferi don't like the idea of maintaining our own module forever17:02
rhalliseySamYaple, how different is using 2.0 vs what we have now17:02
inc0question tho, did anyone check if there is ready upstream project that is alternative to core ansible?17:02
SamYaplerhallisey: a good bit different17:02
SamYapleits been over a month since the 1.8.2 bug came out, and still no new ansible version17:03
*** dane_leblanc has joined #openstack-meeting-417:03
SamYaplewe can;t fix this even if we wanted to17:03
SamYaplethis is a critical peice of our project17:03
inc0can we at least agree with ansible people on API? so we can create something more-or-less compatible with what they will have on ansible v2?17:03
*** markvoelker has quit IRC17:03
SamYapleadditionally, the v2 registry can take hours and hours to push to, but they wont support the v1 registry17:03
nihiliferinc0: +117:03
nihiliferat lease we should be 100% compatible17:03
nihiliferin arguments we take in module17:04
nihiliferand in behavior17:04
SamYaplei disagree there17:04
nihiliferat least*17:04
inc0yeah, thing is, we will want to switch to upstream at some point17:04
SamYaplei also disagree17:04
rhalliseyinc0, that's what I was thinking17:04
SamYaplewe dont otherwise we will be in the same boat17:04
*** vikasc has joined #openstack-meeting-417:04
rhalliseymaybe in 2.0 that becomes a reality17:04
nihiliferSamYaple probably doesn't want to switch to upstream never ever17:04
inc0SamYaple, ansible may change policy, I'm -2 on burning bridges17:04
SamYapleits not a policy thing17:05
nihiliferSamYaple: what if in future there will be some bugs resolved in upstream ansible?17:05
SamYaplelisten to get this fixes we _must_ upgrade ansible version17:05
*** jmccarthy has left #openstack-meeting-417:05
SamYaplethis is true forever17:05
inc0if we keep more or less compatible, when we decide we're ready to switch back to ansible core modules17:05
inc0we can do it17:05
nihiliferwill you watch are their activities to keep in sync?17:05
SamYaplethe bugs are curerently solved in ansible upstream17:05
inc0another option would be chasing trunk of ansible17:05
nihiliferall their*17:05
inc0we do that with openstack17:06
SamYapleinc0: no we can't chase ansible trunk17:06
*** javeriak has joined #openstack-meeting-417:06
SamYapleits always broken17:06
SamYaplei dont want to switch to ansible 2.0 out of the gate because its so busted (its a full rewrite)17:06
*** javeriak_ has quit IRC17:06
SamYaplebut we _must_17:06
inc0it seems to me it's broken now even tho it's pretty released17:06
SamYapleunless we write our own module17:06
inc0kolla-salt then?17:07
rhalliseyI just don't want to detach here from ansible..17:07
*** galstrom is now known as galstrom_zzz17:07
rhalliseyinc0, lols17:07
SamYapleill speak for sdake since he isnt here, he is 100% behind this and pushing me to do this17:07
*** vmahe_ has quit IRC17:07
inc0this means our own module?17:08
SamYapleyes17:08
inc0I'm ok with our own module, I'm not ok with going oposite to ansible17:08
SamYapledefine opposite?17:08
inc0let's keep API at least simirar17:08
inc0similar17:08
inc0arguments and basic behaviours17:08
britthouserIn the module we right, will the APIs be compatible with upstream?17:08
nihiliferi'm ok with own module as temp solution17:08
nihilifernot forever17:08
SamYapleare you just talking about the args?17:08
britthousermeaning we could drop theirs in, if it ever starts working?17:08
inc0yeah, args17:08
inc0names17:08
*** vtech has quit IRC17:09
inc0that sort of stuff, so we can always come back to ansible with as-little-amount-of-work-as-possible17:09
SamYaplei dont think people realize this inst about a short term solution, but a long term one17:09
SamYaplelets talk about it like a long term one please17:09
rhalliseylong term I don't like it17:09
inc0SamYaple, I'm not ready to commit supporting thing like that forever17:09
SamYaplethen suggest a solution please to the issue presented17:09
inc0I'd rather switch ansible to something more managable17:09
inc0because we'll hit more problems at some point17:10
*** jwagner is now known as jwagner_away17:10
britthouserkeeping the names/args teh same seems like a good middle ground.17:10
inc0not with docker but with core ansible, or other module we happen to use17:10
inc0we won't rewrite ansible then17:10
rhalliseyinc0, interesting point, but I'd like to at least try and work this out with them17:10
SamYaplerhallisey: that won't solve anything. these bugs are fixed upstream17:10
SamYaplei fixed the 1.8.2+ one17:11
inc0then maybe help them keep trunk not-broken17:11
SamYaplethe problem is we are forced to upgrade just for that one little docker-py change17:11
SamYapleinc0: trunk broke because docker upgraded17:11
SamYapleit will happen again17:11
inc0it will happen for us as well17:11
SamYaplesure, but we can fix it17:11
SamYapleits been a month, still no consumable fix from ansible17:12
inc0we can fix it here or in ansible repo17:12
SamYaplei fixed it in the ansible repo a month ago17:12
inc0either way works if we won't be bound to ansible release schedule17:12
SamYaplestill not consumable by us17:12
inc0and chase trunk17:12
britthouserSo if we write our own, but keep it "compatible" with the upstream module, then at any time we could switch in the upstream version.  that gives us teh possible of getting "out" down the road.17:12
SamYaplebritthouser: the arg names dont matter to me17:12
SamYaplesure why not17:12
SamYaplebut the solution to the problems wont ever change with ansible upstream17:13
SamYaplethey arent doing anything _wrong_ they are just thier own project17:13
inc0my suggestion - we start working on local module kept as much compatible with latest ansible as possible17:13
inc0SamYaple, we can hit that problem with EVERY dependency we have, including openstack17:14
SamYaplearg names can be the same, doesnt matter to me17:14
SamYaplebut openstack will affect all of openstack17:14
SamYapleits not the same problem17:14
SamYapleit _will_ get fixed and released in a timely manner17:14
inc0ansible will affect everyone who uses ansible+docker, and that's not just us17:14
SamYaplethats not the case with ansible (its been a month)17:14
inc0chasing trunk then17:14
SamYaplewe will not be chasing trunk ever17:14
inc0why?17:15
SamYaplewhy what?17:15
britthouserI think we have a proposal everyone can agree on?17:15
britthouserwrite our own, keep it compatible.17:15
inc0let's start with our own but compatible, that's my suggesiton17:15
SamYaplebritthouser: agreed, this still needs more discussion, but we can do so later17:15
rhalliseysounds like local module that compatible17:15
SamYapleyup17:15
inc0and we can discuss it on midcycle, its super important17:15
*** amotoki has quit IRC17:15
rhalliseySamYaple, I'm going to look at 2.0 anisble-docker here17:16
britthouserthat's a good idea inc017:16
rhalliseyinc0, agreed17:16
SamYaplerhallisey: the 2.0 docker module?17:16
*** ppetit has quit IRC17:16
SamYapleactually we can discuss this more in the channel, we are running a it out of time.17:16
SamYaple#topic open discussion17:16
*** openstack changes topic to "open discussion (Meeting topic: kolla)"17:16
rhalliseySamYaple, or whatever the module causing the issue.17:16
SamYaplefloor is open17:17
rhalliseydocker-py17:17
britthouserany more details about mid-cycle?17:17
rhalliseySamYaple, do you have a sign up17:17
SamYaplerhallisey: no sdake was putting that up17:17
SamYapleI will get with him if he has not yet17:17
britthouserdo we have dates? want to block off my calendar17:18
SamYaplebritthouser: not anything past febuary-ish in Greenville SC17:18
SamYapleill talk with sdake and get this going17:18
* britthouser blocks the entire month of february17:18
britthouser=P17:18
SamYapledo it!17:18
inc0spend rest of Febuary on reviews17:18
cloudnullSamYaple:  sorry i was lurking in the channel. RE Ansible 2.0 the OSAD team wants to use it in the future however we'll likely wait a few releases because out intial testing reviealed quite a bit of brokeness and bad life choices. sorry for the outburst I just wanted to back up what SamYaple was talking about.17:18
*** dzamboni has joined #openstack-meeting-417:18
SamYaple ill get you guys something on the ML by friday17:19
SamYaplecloudnull: so last topic17:19
cloudnull2.0 will need much love before its production ready17:19
SamYaplecloudnull: yea thats what we want to, but the docker module is pretty crucial to us17:19
SamYapleanyone have anything else they need to talk abbout17:20
cloudnullfor sure. they have some bits we need too, and we're looking at ways to backport (manually) to 1.9.x if we absolutly need17:20
cloudnullanyway cheers17:20
SamYaplecloudnull: thanks :)17:20
*** prashantD has joined #openstack-meeting-417:20
britthouserthanks cloudnull17:20
*** sdake has joined #openstack-meeting-417:21
rhalliseylooks like nothing else17:21
SamYaplesdake has arrived!17:22
sdakeo/17:22
SamYaple#endmeeting17:22
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:22
openstackMeeting ended Wed Nov 25 17:22:05 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:22
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-11-25-16.29.html17:22
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-11-25-16.29.txt17:22
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-11-25-16.29.log.html17:22
*** rhallisey has left #openstack-meeting-417:22
*** ivar-lazzaro has joined #openstack-meeting-417:22
*** ashavskiy has joined #openstack-meeting-417:23
*** vikasc has quit IRC17:23
*** akwasnie has quit IRC17:23
*** ivar-laz_ has joined #openstack-meeting-417:24
*** FallenPegasus has joined #openstack-meeting-417:25
*** ivar-lazzaro has quit IRC17:27
*** david-lyle has joined #openstack-meeting-417:30
*** nkrinner has quit IRC17:30
*** ashavskiy has quit IRC17:31
*** prashantD has quit IRC17:32
*** iyamahat has quit IRC17:32
*** prashantD has joined #openstack-meeting-417:32
*** Swami has quit IRC17:33
*** baoli has quit IRC17:37
*** degorenko is now known as _degorenko|afk17:39
*** Sukhdev has quit IRC17:41
*** Sukhdev has joined #openstack-meeting-417:41
*** Prithiv has quit IRC17:44
*** Swami has joined #openstack-meeting-417:50
*** vtech has joined #openstack-meeting-417:52
*** david-lyle has quit IRC18:00
*** bobh has joined #openstack-meeting-418:05
*** sambetts is now known as sambetts-afk18:07
*** vinkman has left #openstack-meeting-418:09
*** iyamahat has joined #openstack-meeting-418:10
*** bobh has quit IRC18:12
*** harshs has joined #openstack-meeting-418:16
*** iyamahat has quit IRC18:18
*** david-lyle has joined #openstack-meeting-418:20
*** QiLiang1 has joined #openstack-meeting-418:21
*** QiLiang has quit IRC18:21
*** QiLiang1 is now known as QiLiang18:21
*** Kevin_Zheng has quit IRC18:26
*** Kevin_Zheng has joined #openstack-meeting-418:27
*** jwagner_away is now known as jwagner18:27
*** prashantD has quit IRC18:30
*** prashantD has joined #openstack-meeting-418:33
*** vivek-ebay has quit IRC18:33
*** inc0 has quit IRC18:36
*** jwagner is now known as jwagner_away18:36
*** galstrom_zzz is now known as galstrom18:39
*** jwagner_away is now known as jwagner18:39
*** iyamahat has joined #openstack-meeting-418:40
*** yamahata has joined #openstack-meeting-418:42
*** vivek-ebay has joined #openstack-meeting-418:43
*** vivek-ebay has quit IRC18:44
*** bobh has joined #openstack-meeting-418:45
*** galstrom is now known as galstrom_zzz18:51
*** bobh has quit IRC18:57
*** FallenPegasus is now known as MarkAtwood18:57
*** sridhar_ram has joined #openstack-meeting-418:59
*** vivek-ebay has joined #openstack-meeting-419:00
*** stanchan has joined #openstack-meeting-419:05
*** bobh has joined #openstack-meeting-419:09
*** Piet has quit IRC19:10
*** bobh has quit IRC19:10
*** barra204 is now known as shakamunyi19:12
*** jwagner is now known as jwagner_away19:12
*** jckasper has joined #openstack-meeting-419:17
*** salv-orl_ has joined #openstack-meeting-419:19
*** salv-orlando has quit IRC19:22
*** mfedosin has quit IRC19:28
*** dane_leblanc has quit IRC19:36
*** s3wong has joined #openstack-meeting-419:43
*** dane_leblanc has joined #openstack-meeting-419:45
*** IlyaG has quit IRC19:46
*** dane_leblanc has quit IRC19:49
*** dane_leblanc has joined #openstack-meeting-419:56
Jokke_o/20:01
Jokke_#startmeeting log wg20:02
openstackMeeting started Wed Nov 25 20:02:14 2015 UTC and is due to finish in 60 minutes.  The chair is Jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: log wg)"20:02
openstackThe meeting name has been set to 'log_wg'20:02
Jokke_Anyone here for the Log WG meeting?20:02
Jokke_#info meeting cancelled due to lack of participation20:05
Jokke_#endmeeting20:05
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:05
openstackMeeting ended Wed Nov 25 20:05:45 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-11-25-20.02.html20:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-11-25-20.02.txt20:05
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-11-25-20.02.log.html20:05
*** Nikolay_St has joined #openstack-meeting-420:07
*** salv-orl_ has quit IRC20:07
*** javeriak has quit IRC20:08
*** bobh has joined #openstack-meeting-420:11
*** xichengc has quit IRC20:14
*** xichengc has joined #openstack-meeting-420:15
*** bobh has quit IRC20:15
*** qingyu has joined #openstack-meeting-420:15
*** Swami has quit IRC20:22
*** njohnston is now known as nate_gone20:26
*** bmace has left #openstack-meeting-420:31
*** sdake has quit IRC20:40
*** baoli has joined #openstack-meeting-420:40
*** dzamboni has quit IRC20:43
*** salv-orlando has joined #openstack-meeting-420:44
*** baoli_ has joined #openstack-meeting-420:51
*** baoli has quit IRC20:53
*** dtardivel has quit IRC20:57
*** prashantD_ has joined #openstack-meeting-421:06
*** prashantD has quit IRC21:08
*** dims_ has joined #openstack-meeting-421:21
*** dims has quit IRC21:22
*** dims has joined #openstack-meeting-421:26
*** dims_ has quit IRC21:28
*** dshakhray has quit IRC21:32
*** iyamahat has quit IRC21:41
*** prashantD_ has quit IRC21:44
*** bobh has joined #openstack-meeting-421:45
*** bobh has quit IRC21:51
*** jpeeler has quit IRC21:51
*** mfedosin has joined #openstack-meeting-421:52
*** baoli_ has quit IRC21:53
*** dims_ has joined #openstack-meeting-421:53
*** dims has quit IRC21:56
*** Sukhdev has quit IRC21:56
*** Sukhdev has joined #openstack-meeting-422:00
*** vtech has quit IRC22:02
*** IlyaG has joined #openstack-meeting-422:05
*** bobh has joined #openstack-meeting-422:09
*** bobh has quit IRC22:12
*** iyamahat has joined #openstack-meeting-422:12
*** nate_gone is now known as njohnston22:14
*** Sukhdev has quit IRC22:22
*** harshs has quit IRC22:22
*** njohnston is now known as nate_gone22:24
*** Swami has joined #openstack-meeting-422:26
*** bobh has joined #openstack-meeting-422:31
*** david-lyle has quit IRC22:34
*** bobh_ has joined #openstack-meeting-422:36
*** bobh has quit IRC22:38
*** stanchan has quit IRC22:59
*** david-lyle has joined #openstack-meeting-423:07
*** mfedosin has quit IRC23:08
*** sdake has joined #openstack-meeting-423:10
*** med_ has quit IRC23:17
*** rbak has quit IRC23:24
*** david-lyle has quit IRC23:24
*** med_ has joined #openstack-meeting-423:25
*** JRobinson__ has joined #openstack-meeting-423:26
JRobinson__Good morning, from GMT+10 time, we will be starting the User Guide team meeting shortly.23:27
*** bmoss has joined #openstack-meeting-423:29
JRobinson__The User Guide team meeting will begin soon - I'm pushing the start time back slightly.23:35
bmosscool23:35
*** mmedvede has quit IRC23:36
*** darrenc has joined #openstack-meeting-423:39
*** mmedvede has joined #openstack-meeting-423:40
JRobinson__Alright, I think that is enough forestalling.23:44
JRobinson__#startmeeting docuserguides23:44
openstackMeeting started Wed Nov 25 23:44:16 2015 UTC and is due to finish in 60 minutes.  The chair is JRobinson__. Information about MeetBot at http://wiki.debian.org/MeetBot.23:44
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.23:44
*** openstack changes topic to " (Meeting topic: docuserguides)"23:44
openstackThe meeting name has been set to 'docuserguides'23:44
JRobinson__So, properly, good morning all23:44
JRobinson__welcome to the first IRC meeting.23:44
JRobinson__The agenda is short, with some steps forward since last time on the spec.23:45
bmoss\o/23:45
JRobinson__I also wanted to look at using the [user guide] tag in patches.23:45
JRobinson__#topic User Guide Specification23:45
*** openstack changes topic to "User Guide Specification (Meeting topic: docuserguides)"23:45
JRobinson__So at the moment, I have three comments, and I have address two of them.23:46
JRobinson__#link https://review.openstack.org/#/c/238770/23:46
JRobinson__^addressed23:46
bmossJRobinson__, which two have you addressed?23:47
bmoss1. SDK -> api-site23:47
bmoss2. Nova -> neutron23:47
bmoss3. Definition of 'core'23:47
JRobinson__In regards to Nova Networking vs. Neutron content for users, there is a presentation on a survey on which type of networking is workable.23:48
JRobinson__I have spoken to Piet about this, and he is presenting the results in early December23:48
bmossawesome23:48
JRobinson__I have some small content to address here, and more to follow after the results are public.23:48
JRobinson__I also have spoken to the Trove docs liason. There is some trove content that fits into the Cloud admin guide23:49
JRobinson__So a bit of 2. Nova -> neutron, and a bit of 3. Definition of 'core'23:49
bmosscool23:49
JRobinson__#action JRobinson__ to update the spec on points 2 and 3.23:49
bmossfwiw, I like Anne's idea of moving the SDK stuff out of the user guide as well23:50
JRobinson__With that one, that is not a difficult change. If anyone wants to jump in and change it, go ahead.23:50
JRobinson__Depending on time and other project work, etc.23:50
JRobinson__That's all for the spec.23:51
JRobinson__#topic [user guide] tag23:51
*** openstack changes topic to "[user guide] tag (Meeting topic: docuserguides)"23:51
bmossJRobinson__, I can add that to the spec23:51
JRobinson__So this is more of a question. Can we add the [user guide] tag to patches similar to the install guide work.23:51
*** Vinsh has quit IRC23:51
JRobinson__bmoss, awesome, thanks :)23:51
bmoss#action bmoss to update spec on point 123:52
bmossre: tag - I like the idea, as it makes it easier to know what a patch involves when looking at a list of subject lines in gerrit23:52
bmosson the other hand, it eats up subject line characters23:53
*** yasui_ has joined #openstack-meeting-423:53
bmossbut I don't think that is a major problem23:53
JRobinson__So there are limitations to using it.23:53
JRobinson__It might depend on how big the reorg is in the patch. Small patches may not need the team to look over them.23:54
bmossthat's true23:54
*** IlyaG_ has joined #openstack-meeting-423:55
JRobinson__okay, I'll record that as information.23:55
bmossso you envision the tag being used when we want to catch the attention of the speciality team?23:55
JRobinson__#info make use of [user guide] tags in patches with large reorganisation impact. be aware of subject line length.23:55
JRobinson__bmoss, yes that's right.23:55
bmosscool. I think that's a good idea.23:56
JRobinson__That's all I had on the point.23:56
JRobinson__Last item is advertising the meeting more.23:56
JRobinson__#topic Meeting time change advertising23:56
*** openstack changes topic to "Meeting time change advertising (Meeting topic: docuserguides)"23:56
JRobinson__This is basically me not sending out enough reminders. I also did not contact interested people directly.23:56
bmossdo we have funding for a spot on SBS?23:56
JRobinson__I'll fix that for next week.23:57
JRobinson__bmoss, I can talk to the Organisation.23:57
*** IlyaG has quit IRC23:57
bmosslol23:57
JRobinson__If anything, SBS radio would be the least expensive option :)23:58
bmossprobably!23:58
JRobinson__If that's all I might close the meeting up.23:58
bmossthat's all from me23:58
JRobinson__bmoss, thank you :)23:59
JRobinson__#endmeeting23:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:59
openstackMeeting ended Wed Nov 25 23:59:11 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docuserguides/2015/docuserguides.2015-11-25-23.44.html23:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docuserguides/2015/docuserguides.2015-11-25-23.44.txt23:59
openstackLog:            http://eavesdrop.openstack.org/meetings/docuserguides/2015/docuserguides.2015-11-25-23.44.log.html23:59
bmossthanks JRobinson__23:59
JRobinson__np,23:59

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