Tuesday, 2016-02-02

*** haomaiwang has quit IRC00:01
*** haomaiwang has joined #openstack-meeting00:01
*** ninag has joined #openstack-meeting00:07
*** singhj has quit IRC00:07
*** salv-orl_ has quit IRC00:08
*** emagana has quit IRC00:08
*** ninag has quit IRC00:08
*** emagana has joined #openstack-meeting00:08
*** alop has quit IRC00:09
*** jjmb has joined #openstack-meeting00:10
*** tochi has quit IRC00:10
*** dims has quit IRC00:10
*** jjmb1 has joined #openstack-meeting00:11
*** tochi has joined #openstack-meeting00:11
*** Swami has joined #openstack-meeting00:12
*** emagana has quit IRC00:13
*** jjmb has quit IRC00:14
*** aimon has quit IRC00:14
*** vmbrasseur_ has joined #openstack-meeting00:15
*** tej has quit IRC00:15
*** tej has joined #openstack-meeting00:16
*** dane has quit IRC00:20
*** tej has quit IRC00:20
*** su_zhang has quit IRC00:21
*** su_zhang has joined #openstack-meeting00:21
*** vahidh has quit IRC00:21
*** mtanino_ has joined #openstack-meeting00:22
*** bobh has joined #openstack-meeting00:23
*** mtanino has quit IRC00:24
dolphmthingee: yes, i do believe so00:24
*** raildo-afk is now known as raildo00:25
*** vmbrasseur has quit IRC00:29
*** mudassirlatif has quit IRC00:29
*** vmbrasseur_ is now known as vmbrasseur00:29
*** MarkAtwood has quit IRC00:32
*** ZZelle_ has quit IRC00:32
*** mudassirlatif has joined #openstack-meeting00:32
*** ljxiash has quit IRC00:33
*** xingchao has joined #openstack-meeting00:34
*** jjmb1 has quit IRC00:35
*** bobh has quit IRC00:38
*** xingchao has quit IRC00:38
*** absubram has quit IRC00:41
*** Drago has quit IRC00:42
*** Drago has joined #openstack-meeting00:42
*** ljxiash has joined #openstack-meeting00:43
*** ljxiash has quit IRC00:43
*** ljxiash has joined #openstack-meeting00:43
*** vahidh has joined #openstack-meeting00:45
*** MaxPC has joined #openstack-meeting00:45
*** devananda has quit IRC00:47
*** vahidh has quit IRC00:49
*** stevebaker has quit IRC00:52
*** stevebaker has joined #openstack-meeting00:52
*** unicell has joined #openstack-meeting00:52
*** balajiiyer has joined #openstack-meeting00:53
*** bobh has joined #openstack-meeting00:56
*** SumitNaiksatam has quit IRC01:00
*** MarkAtwood has joined #openstack-meeting01:00
*** haomaiwang has quit IRC01:01
*** annemccormick has joined #openstack-meeting01:01
*** haomaiwang has joined #openstack-meeting01:01
*** unicell1 has joined #openstack-meeting01:02
*** hoangcx has joined #openstack-meeting01:03
*** haomaiwang has quit IRC01:04
*** unicell has quit IRC01:04
*** annemccormick_ has joined #openstack-meeting01:05
*** thorst has quit IRC01:05
*** thorst has joined #openstack-meeting01:06
*** annemccormick has quit IRC01:06
*** annemccormick_ is now known as annemccormick01:06
*** dmacpher has quit IRC01:06
*** shashank_hegde has quit IRC01:07
*** Leom has joined #openstack-meeting01:08
*** ivar-lazzaro has quit IRC01:08
*** Leom_ has joined #openstack-meeting01:09
*** doug-fish has quit IRC01:10
*** Leom has quit IRC01:10
*** doug-fish has joined #openstack-meeting01:10
*** JRobinson__ has quit IRC01:10
*** doug-fis_ has joined #openstack-meeting01:12
*** piet has quit IRC01:12
*** iyamahat has quit IRC01:12
*** Leom_ has quit IRC01:14
*** thorst has quit IRC01:14
*** davechen has joined #openstack-meeting01:14
*** doug-fi__ has joined #openstack-meeting01:14
*** doug-fish has quit IRC01:14
*** markvoelker has joined #openstack-meeting01:15
*** doug-fi__ has quit IRC01:15
*** piet has joined #openstack-meeting01:16
*** doug-fish has joined #openstack-meeting01:16
*** MarkAtwood has quit IRC01:16
*** doug-fish has quit IRC01:16
*** doug-fis_ has quit IRC01:16
*** ricolin has joined #openstack-meeting01:17
*** tej has joined #openstack-meeting01:17
*** balajiiyer has quit IRC01:18
*** markvoelker has quit IRC01:20
*** kjorgens_ has quit IRC01:20
*** kjorgensen has joined #openstack-meeting01:21
*** annemccormick has quit IRC01:21
*** kjorgensen has quit IRC01:22
*** tej has quit IRC01:22
*** bill_az has quit IRC01:23
*** kjorgensen has joined #openstack-meeting01:24
*** MaxPC has quit IRC01:24
*** kjorgensen has quit IRC01:24
*** jjmb has joined #openstack-meeting01:25
*** kjorgensen has joined #openstack-meeting01:25
*** mtanino_ has quit IRC01:27
*** kjorgensen has quit IRC01:29
*** penick has quit IRC01:30
*** JRobinson__ has joined #openstack-meeting01:31
*** ivar-lazzaro has joined #openstack-meeting01:32
*** MaxPC has joined #openstack-meeting01:33
*** xingchao has joined #openstack-meeting01:34
*** garthb has quit IRC01:34
*** kjorgensen has joined #openstack-meeting01:35
*** zhhuabj has quit IRC01:36
*** JRobinson__ has quit IRC01:37
*** balajiiyer has joined #openstack-meeting01:38
*** kjorgensen has quit IRC01:39
*** xingchao has quit IRC01:39
*** angdraug has quit IRC01:39
*** marekd has quit IRC01:40
*** marekd has joined #openstack-meeting01:40
*** leeantho has quit IRC01:41
*** Sukhdev has quit IRC01:41
*** balajiiyer has quit IRC01:42
*** cwolferh has quit IRC01:44
*** cwolferh has joined #openstack-meeting01:45
*** cwolferh has quit IRC01:46
*** baohua has joined #openstack-meeting01:47
*** julim has joined #openstack-meeting01:49
*** zhhuabj has joined #openstack-meeting01:49
*** jgriffith is now known as jgriffith_away01:50
*** Apoorva has quit IRC01:52
*** jgriffith_away is now known as jgriffith01:53
*** tfukushima has joined #openstack-meeting01:54
*** haomaiwang has joined #openstack-meeting01:55
*** Swami has quit IRC01:56
*** raildo is now known as raildo-afk01:59
*** pvaneck has quit IRC01:59
*** kencjohnston has joined #openstack-meeting02:00
*** dmorita has quit IRC02:01
*** haomaiwang has quit IRC02:01
*** dmorita has joined #openstack-meeting02:01
*** haomaiwang has joined #openstack-meeting02:01
*** fzdarsky_ has joined #openstack-meeting02:03
*** ljxiash has quit IRC02:03
*** ljxiash has joined #openstack-meeting02:04
*** n0ano_ has quit IRC02:04
*** Sukhdev has joined #openstack-meeting02:04
*** jgriffith is now known as jgriffith_away02:04
*** Sukhdev has quit IRC02:05
*** piet has quit IRC02:05
*** alexpilotti has joined #openstack-meeting02:06
*** lazy_prince has joined #openstack-meeting02:07
*** fzdarsky|afk has quit IRC02:07
*** itzdilip has joined #openstack-meeting02:09
*** thorst has joined #openstack-meeting02:09
*** alexpilotti has quit IRC02:10
*** su_zhang has quit IRC02:11
*** singhj has joined #openstack-meeting02:11
*** dims has joined #openstack-meeting02:11
*** singhj has quit IRC02:12
*** thorst has quit IRC02:12
*** thorst has joined #openstack-meeting02:13
*** markvoelker has joined #openstack-meeting02:16
*** tej has joined #openstack-meeting02:18
*** markvoelker has quit IRC02:20
*** thorst has quit IRC02:21
*** balajiiyer has joined #openstack-meeting02:22
*** ljxiash has quit IRC02:22
*** bobh has quit IRC02:23
*** singhj has joined #openstack-meeting02:23
*** tej has quit IRC02:23
*** ljxiash has joined #openstack-meeting02:25
*** coolsvap|away is now known as coolsvap02:26
*** s3wong has quit IRC02:27
*** xingchao has joined #openstack-meeting02:28
*** yamahata has quit IRC02:28
*** singhj has quit IRC02:28
*** MaxPC has quit IRC02:30
*** davechen1 has joined #openstack-meeting02:31
*** davechen1 has quit IRC02:31
*** davechen1 has joined #openstack-meeting02:32
*** davechen has quit IRC02:33
*** JRobinson__ has joined #openstack-meeting02:38
*** JRobinso_ has joined #openstack-meeting02:39
*** JRobinson__ has quit IRC02:39
*** ivar-laz_ has joined #openstack-meeting02:41
*** alexpilotti has joined #openstack-meeting02:42
*** haomaiwa_ has joined #openstack-meeting02:44
*** zz_dimtruck is now known as dimtruck02:44
*** ivar-lazzaro has quit IRC02:45
*** haomaiwang has quit IRC02:45
*** bdrich_ has joined #openstack-meeting02:45
*** ivar-laz_ has quit IRC02:45
*** davechen1 is now known as davechen02:46
*** alexpilotti has quit IRC02:46
*** banix has joined #openstack-meeting02:47
*** MarkAtwood has joined #openstack-meeting02:49
*** bobh has joined #openstack-meeting02:57
*** coolsvap is now known as coolsvap|away02:59
*** baojg_ has quit IRC02:59
*** ijw has quit IRC02:59
*** bobh has quit IRC03:00
*** haomaiwa_ has quit IRC03:01
*** haomaiwang has joined #openstack-meeting03:01
*** ljxiash_ has joined #openstack-meeting03:03
*** lazy_prince has quit IRC03:04
*** Daisy_ has joined #openstack-meeting03:05
*** ljxiash has quit IRC03:05
*** bobh has joined #openstack-meeting03:06
*** lazy_prince has joined #openstack-meeting03:07
*** piet has joined #openstack-meeting03:09
*** yamamoto has joined #openstack-meeting03:09
*** Daisy_ has quit IRC03:09
*** amotoki has quit IRC03:10
*** lazy_prince has quit IRC03:12
*** haomaiwang has quit IRC03:12
*** haomaiwang has joined #openstack-meeting03:13
*** bobh has quit IRC03:13
*** jckasper has joined #openstack-meeting03:14
*** tfukushima has quit IRC03:14
*** links has joined #openstack-meeting03:15
*** tfukushima has joined #openstack-meeting03:16
*** davechen1 has joined #openstack-meeting03:16
*** alexpilotti has joined #openstack-meeting03:17
*** davechen has quit IRC03:18
*** thorst has joined #openstack-meeting03:19
*** tej has joined #openstack-meeting03:20
*** yamamoto has quit IRC03:20
*** alexpilotti has quit IRC03:22
*** tej has quit IRC03:24
*** thorst has quit IRC03:26
*** jgriffith_away is now known as jgriffith03:26
*** esheffield has quit IRC03:28
*** zhurong has joined #openstack-meeting03:29
*** esheffield has joined #openstack-meeting03:29
*** tochi has quit IRC03:30
*** itzdilip has quit IRC03:30
*** unicell1 has quit IRC03:31
*** sdake has joined #openstack-meeting03:35
*** amotoki has joined #openstack-meeting03:35
*** haomaiwang has quit IRC03:37
*** harshs has quit IRC03:39
*** achanda has joined #openstack-meeting03:43
*** jrist has joined #openstack-meeting03:43
*** dmorita has quit IRC03:45
*** haomaiwang has joined #openstack-meeting03:45
*** dmorita has joined #openstack-meeting03:46
*** SumitNaiksatam has joined #openstack-meeting03:48
*** dmacpher has joined #openstack-meeting03:52
*** dims has quit IRC03:53
*** tellesnobrega is now known as tellesnobrega_af03:57
*** kencjohnston has quit IRC03:57
*** MarkAtwood has quit IRC03:58
*** haomaiwang has quit IRC04:01
*** amotoki has quit IRC04:01
*** haomaiwang has joined #openstack-meeting04:01
*** bdrich_ has quit IRC04:02
*** armax has quit IRC04:02
*** JRobinso_ has quit IRC04:02
*** xingchao has quit IRC04:02
*** achanda has quit IRC04:04
*** xingchao has joined #openstack-meeting04:05
*** armax has joined #openstack-meeting04:06
*** haomaiw__ has joined #openstack-meeting04:06
*** su_zhang has joined #openstack-meeting04:06
*** coolsvap|away is now known as coolsvap04:07
*** ljxiash_ has quit IRC04:08
*** yamamoto_ has joined #openstack-meeting04:08
*** haomaiwang has quit IRC04:08
*** tochi has joined #openstack-meeting04:09
*** kebray has joined #openstack-meeting04:09
*** xingchao has quit IRC04:10
*** winston-d_ has joined #openstack-meeting04:10
*** davechen has joined #openstack-meeting04:10
*** mrmartin has joined #openstack-meeting04:11
*** achanda has joined #openstack-meeting04:11
*** davechen1 has quit IRC04:12
*** shashank_hegde has joined #openstack-meeting04:14
*** banix has quit IRC04:14
*** kebray has quit IRC04:14
*** kebray_ has joined #openstack-meeting04:14
*** vishwanathj has quit IRC04:16
*** markvoelker has joined #openstack-meeting04:17
*** bdrich_ has joined #openstack-meeting04:17
*** tej has joined #openstack-meeting04:21
*** markvoelker has quit IRC04:21
*** bdrich_ has quit IRC04:22
*** grumpycatt has quit IRC04:23
*** thorst has joined #openstack-meeting04:24
*** grumpycatt has joined #openstack-meeting04:26
*** tej has quit IRC04:27
*** novas0x2a|laptop has quit IRC04:30
*** thorst has quit IRC04:31
*** ljxiash has joined #openstack-meeting04:31
*** JRobinson__ has joined #openstack-meeting04:32
*** ljxiash has quit IRC04:36
*** bdrich_ has joined #openstack-meeting04:37
*** tfukushima has quit IRC04:43
*** kjorgensen has joined #openstack-meeting04:47
*** baojg has joined #openstack-meeting04:49
*** roxanagh_ has joined #openstack-meeting04:49
*** balajiiyer has quit IRC04:50
*** kjorgensen has quit IRC04:51
*** xinwu has quit IRC04:53
*** aukhan has joined #openstack-meeting04:55
*** JRobinso_ has joined #openstack-meeting04:56
*** ricolin has quit IRC04:56
*** JRobinson__ has quit IRC04:59
*** gongysh has joined #openstack-meeting05:00
*** haomaiw__ has quit IRC05:01
*** haomaiwang has joined #openstack-meeting05:01
*** topol has quit IRC05:01
*** harshs has joined #openstack-meeting05:04
*** amotoki has joined #openstack-meeting05:05
*** topol_ has joined #openstack-meeting05:05
*** sdake has quit IRC05:05
*** unicell has joined #openstack-meeting05:07
*** harshs_ has joined #openstack-meeting05:10
*** harshs has quit IRC05:11
*** harshs_ is now known as harshs05:11
*** ricolin has joined #openstack-meeting05:14
*** shashank_hegde has quit IRC05:17
*** Sukhdev has joined #openstack-meeting05:17
*** tej has joined #openstack-meeting05:24
*** alexpilotti has joined #openstack-meeting05:24
*** dmorita has quit IRC05:25
*** lazy_prince has joined #openstack-meeting05:26
*** baojg has quit IRC05:28
*** alexpilotti has quit IRC05:28
*** tej has quit IRC05:28
*** thorst has joined #openstack-meeting05:30
*** baojg has joined #openstack-meeting05:30
*** gyee has quit IRC05:32
*** tfukushima has joined #openstack-meeting05:34
*** neelashah has joined #openstack-meeting05:35
*** xinwu has joined #openstack-meeting05:35
*** thorst has quit IRC05:36
*** novas0x2a|laptop has joined #openstack-meeting05:37
*** harshs has quit IRC05:43
*** AzherKhan has joined #openstack-meeting05:44
*** piet has quit IRC05:44
*** aukhan has quit IRC05:44
*** sileht has quit IRC05:44
*** piet has joined #openstack-meeting05:45
*** harshs has joined #openstack-meeting05:45
*** vahidh has joined #openstack-meeting05:49
*** Swami has joined #openstack-meeting05:49
*** JRobinso_ has quit IRC05:51
*** hoangcx has quit IRC05:52
*** vahidh has quit IRC05:53
*** changbl has quit IRC05:56
*** bvandenh has joined #openstack-meeting05:57
*** vivekd has joined #openstack-meeting05:57
*** dimtruck is now known as zz_dimtruck06:00
*** haomaiwang has quit IRC06:01
*** haomaiwa_ has joined #openstack-meeting06:01
*** hdaniel has joined #openstack-meeting06:03
*** gongysh has quit IRC06:04
*** oomichi has joined #openstack-meeting06:04
*** vgridnev has joined #openstack-meeting06:06
*** ricolin has quit IRC06:07
*** dmacpher has quit IRC06:08
*** neelashah has quit IRC06:09
*** piet has quit IRC06:11
*** fawadkhaliq has joined #openstack-meeting06:11
*** fawadkhaliq has quit IRC06:11
*** harshs has quit IRC06:13
*** jtomasek has quit IRC06:15
*** markvoelker has joined #openstack-meeting06:18
*** bdrich_ has quit IRC06:18
*** bdrich_ has joined #openstack-meeting06:19
*** Drago has quit IRC06:19
*** rcernin has joined #openstack-meeting06:21
*** markvoelker has quit IRC06:22
*** roxanagh_ has quit IRC06:23
*** boris-42 has quit IRC06:23
*** dmacpher has joined #openstack-meeting06:25
*** tej has joined #openstack-meeting06:25
*** dmorita has joined #openstack-meeting06:26
*** shashank_hegde has joined #openstack-meeting06:26
*** Swami has quit IRC06:28
*** tej has quit IRC06:30
*** dmorita has quit IRC06:31
*** neeti has joined #openstack-meeting06:35
*** thorst has joined #openstack-meeting06:35
*** SridharG has joined #openstack-meeting06:37
*** neeti has quit IRC06:39
*** vgridnev has quit IRC06:40
*** vgridnev has joined #openstack-meeting06:41
*** vgridnev has quit IRC06:41
*** thorst has quit IRC06:41
*** baohua has quit IRC06:43
*** baohua has joined #openstack-meeting06:43
*** ttrifonov has quit IRC06:45
*** ttrifonov has joined #openstack-meeting06:45
*** rcernin has quit IRC06:46
*** haomaiw__ has joined #openstack-meeting06:47
*** shashank_hegde has quit IRC06:48
*** haomaiwa_ has quit IRC06:48
*** jprovazn has joined #openstack-meeting06:50
*** amotoki_ has joined #openstack-meeting06:51
*** ttrifonov has quit IRC06:54
*** ttrifonov has joined #openstack-meeting06:54
*** haomaiw__ has quit IRC07:01
*** haomaiwang has joined #openstack-meeting07:01
*** bdrich_ has quit IRC07:01
*** armax has quit IRC07:03
yamamoto_hi07:03
yamamoto_#startmeeting networking_midonet07:03
*** amotoki has quit IRC07:03
openstackMeeting started Tue Feb  2 07:03:46 2016 UTC and is due to finish in 60 minutes.  The chair is yamamoto_. Information about MeetBot at http://wiki.debian.org/MeetBot.07:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:03
*** openstack changes topic to " (Meeting topic: networking_midonet)"07:03
openstackThe meeting name has been set to 'networking_midonet'07:03
yamamoto_#link https://wiki.openstack.org/wiki/Meetings/NetworkingMidoNet agenda07:05
yamamoto_#topic Announcements07:05
*** openstack changes topic to "Announcements (Meeting topic: networking_midonet)"07:05
yamamoto_icehouse and juno will be EOL07:05
yamamoto_#topic Bugs07:06
*** openstack changes topic to "Bugs (Meeting topic: networking_midonet)"07:06
yamamoto_there are a few critical bugs but they seem to be backend issues.07:06
yamamoto_as it seems i'm alone, i guess i'll continue to be bug deputy07:07
yamamoto_#topic Removal of old non-standard branches07:07
*** openstack changes topic to "Removal of old non-standard branches (Meeting topic: networking_midonet)"07:07
yamamoto_we have a list of non-standard branches.  see the meeting wiki for the list.07:08
*** sudipto has joined #openstack-meeting07:08
yamamoto_most (all?) of them seem to be no longer necessary07:08
*** ijw has joined #openstack-meeting07:08
yamamoto_i'm going to request removal of these branches.07:08
yamamoto_#topic  Open Discussion07:09
*** openstack changes topic to "Open Discussion (Meeting topic: networking_midonet)"07:09
*** egallen has joined #openstack-meeting07:09
yamamoto_i don't think we have anything else to discuss.07:09
yamamoto_bye!07:09
yamamoto_#endmeeting07:09
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"07:09
openstackMeeting ended Tue Feb  2 07:09:42 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:09
*** ttrifonov has quit IRC07:09
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-02-02-07.03.html07:09
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-02-02-07.03.txt07:09
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_midonet/2016/networking_midonet.2016-02-02-07.03.log.html07:09
*** hoangcx has joined #openstack-meeting07:10
*** eliqiao has quit IRC07:10
*** dmacpher has quit IRC07:10
*** eliqiao has joined #openstack-meeting07:12
*** ttrifonov has joined #openstack-meeting07:13
*** ttrifonov has quit IRC07:13
*** ttrifonov has joined #openstack-meeting07:14
*** _nadya_ has joined #openstack-meeting07:16
*** coolsvap is now known as coolsvap|away07:16
*** shashank_hegde has joined #openstack-meeting07:18
*** _nadya_ has quit IRC07:20
*** nkrinner has joined #openstack-meeting07:23
*** irenab has quit IRC07:23
*** tej has joined #openstack-meeting07:26
*** egallen has quit IRC07:28
*** zaro has joined #openstack-meeting07:28
*** zul has joined #openstack-meeting07:29
*** sileht_ has joined #openstack-meeting07:29
*** yamahata has joined #openstack-meeting07:29
*** obondarev has quit IRC07:29
*** ianw has quit IRC07:29
*** egallen has joined #openstack-meeting07:29
*** ianw has joined #openstack-meeting07:30
*** egallen has quit IRC07:30
*** iyamahat has joined #openstack-meeting07:31
*** obondarev has joined #openstack-meeting07:31
*** ppetit has joined #openstack-meeting07:31
*** tej has quit IRC07:31
*** scheuran has joined #openstack-meeting07:33
*** arvinc_ has joined #openstack-meeting07:33
*** sileht_ is now known as sileht07:35
*** arvinc_ has quit IRC07:36
*** arvinc_ has joined #openstack-meeting07:37
*** ttrifonov has quit IRC07:37
*** arvinc_ has quit IRC07:38
*** Sukhdev has quit IRC07:38
*** thorst has joined #openstack-meeting07:39
*** comay has quit IRC07:39
*** achanda has quit IRC07:40
*** lekha is now known as lekha|away07:40
*** zul has quit IRC07:41
*** ttrifonov has joined #openstack-meeting07:41
*** ttrifonov has quit IRC07:41
*** ttrifonov has joined #openstack-meeting07:42
*** _RuiChen has quit IRC07:42
*** ijw has quit IRC07:42
*** RuiChen has joined #openstack-meeting07:43
*** achanda has joined #openstack-meeting07:43
*** comay has joined #openstack-meeting07:44
*** belmoreira has joined #openstack-meeting07:44
*** bvandenh has quit IRC07:46
*** paul-carlton1 has joined #openstack-meeting07:46
*** thorst has quit IRC07:46
*** tfukushima has quit IRC07:47
*** tfukushima has joined #openstack-meeting07:49
*** sileht has quit IRC07:50
*** sileht has joined #openstack-meeting07:50
*** su_zhang has quit IRC07:52
*** safchain has joined #openstack-meeting07:53
*** achanda has quit IRC07:55
*** rbowen has joined #openstack-meeting07:58
*** anteaya has joined #openstack-meeting07:58
*** adiantum has joined #openstack-meeting08:00
*** evgenyf has joined #openstack-meeting08:00
anteaya#startmeeting third-party08:00
openstackMeeting started Tue Feb  2 08:00:44 2016 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: third-party)"08:00
openstackThe meeting name has been set to 'third_party'08:00
anteayahello08:00
*** haomaiwang has quit IRC08:01
*** egallen has joined #openstack-meeting08:01
*** kebray_ has quit IRC08:01
lennybanteaya: hi08:02
anteayahey lennyb08:02
*** haomaiwang has joined #openstack-meeting08:02
anteayahow are you?08:02
*** amotoki_ is now known as amotoki08:03
*** arvinc_ has joined #openstack-meeting08:04
*** arvinc_ has quit IRC08:04
lennybfine, thanks. how was your trip to the Britain?08:04
anteayavery good, I learned a lot about British culture, things I couldn't have read in a book08:05
*** sunrenjie has joined #openstack-meeting08:05
anteayaI really like Bristol, it is a nice city08:05
lennybCrossing roads was a challenge for me, there :)08:05
anteayaah, do you mean driving on the left side or when walking getting to the other side of the road?08:06
lennybgetting to the other side. my driving instincts did not let me take 'a risk' to drive there :),08:07
anteayayeah I didn't drive there either for the same reason08:08
anteayaand yes understanding how their footpaths are organized to get where I needed to go was an adventure08:09
lennybbtw, I dont have anything to discuss and I know it's a very late for you, so feel free ...08:09
anteayaha ha ha08:09
anteayathanks08:09
*** ppetit has quit IRC08:09
anteayayeah I don't have anything to discuss today either08:09
anteayabut that is okay, at least I'm not on a bus today08:09
anteaya:)08:09
*** sdake has joined #openstack-meeting08:09
lennyb:) . Was this a business or pleasure visit?08:10
*** agireud has quit IRC08:10
anteayabusiness08:10
anteayathe nova mid-cycle08:10
lennybit's nice too :)08:11
*** topol_ has quit IRC08:12
*** agireud has joined #openstack-meeting08:12
anteayait was a productive meeting08:12
*** paul-carlton1 has quit IRC08:12
*** oomichi has quit IRC08:12
*** ildikov has quit IRC08:13
*** jtomasek_ has joined #openstack-meeting08:13
*** oomichi has joined #openstack-meeting08:13
anteayamany things were discussed and explained08:13
*** topol_ has joined #openstack-meeting08:13
anteayato good effect08:13
*** matrohon has joined #openstack-meeting08:14
*** pbelamge has joined #openstack-meeting08:15
anteayaI'm back in the UK in 2 weeks08:15
anteayafor the operators mid-cycle in Manchester08:15
anteayawill you be there, lennyb?08:15
lennybNo08:16
*** vivekd has quit IRC08:16
*** boris-42 has joined #openstack-meeting08:17
*** markvoelker has joined #openstack-meeting08:18
anteaya:(08:19
anteayawill anyone from your company be there?08:19
*** mrmartin has quit IRC08:19
lennybnope08:19
*** shashank_hegde has quit IRC08:19
lennybon the other hand, might be. Is there anything you need/want to discuss? I can check if someone goes08:20
anteayathat is a shame08:20
anteayawell just to be at the event and included in the discussion08:21
anteayayou never know what comes up in discussion08:21
anteayaand I figured since it is in Europe, European folks would be more likely to attend08:21
*** vivekd has joined #openstack-meeting08:22
*** markvoelker has quit IRC08:22
anteayaI didn't have anything specific08:22
anteayaif I did, I would just ask you :)08:23
lennyb:)08:23
*** zeih has joined #openstack-meeting08:23
*** zeih has quit IRC08:23
*** tlbr_ has quit IRC08:23
*** zeih has joined #openstack-meeting08:24
anteayaokay well thanks for your time today lennyb08:24
anteayaI guess I will close the meeting08:24
anteayaenjoy the rest of your day08:24
anteayaand see you next week08:25
anteaya#endmeeting08:25
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"08:25
openstackMeeting ended Tue Feb  2 08:25:05 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-02-02-08.00.html08:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-02-02-08.00.txt08:25
openstackLog:            http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-02-02-08.00.log.html08:25
*** anteaya has quit IRC08:25
*** bvandenh has joined #openstack-meeting08:25
*** jichen has joined #openstack-meeting08:25
*** mrmartin has joined #openstack-meeting08:26
*** tobe has joined #openstack-meeting08:28
*** tej has joined #openstack-meeting08:28
*** baigk has quit IRC08:32
*** tej has quit IRC08:33
*** irenab has joined #openstack-meeting08:34
*** mrmartin has quit IRC08:34
*** xinwu has quit IRC08:36
*** hashar has joined #openstack-meeting08:38
*** e0ne has joined #openstack-meeting08:38
*** mrmartin has joined #openstack-meeting08:39
*** tlbr has joined #openstack-meeting08:43
*** vivekd has quit IRC08:43
*** sudipto has quit IRC08:45
*** thorst has joined #openstack-meeting08:45
*** adiantum has quit IRC08:48
*** phil__ has joined #openstack-meeting08:48
*** vivekd has joined #openstack-meeting08:48
*** ricolin has joined #openstack-meeting08:49
*** marekd has quit IRC08:50
*** thorst has quit IRC08:51
*** iyamahat has quit IRC08:51
*** marekd has joined #openstack-meeting08:52
*** yamahata has quit IRC08:52
*** iyamahat has joined #openstack-meeting08:53
*** sunrenjie has quit IRC08:55
*** zul has joined #openstack-meeting08:55
*** rossella_s has joined #openstack-meeting08:56
*** numans has joined #openstack-meeting08:57
*** jlanoux has joined #openstack-meeting08:57
*** ndipanov has joined #openstack-meeting08:58
*** tfukushima has quit IRC08:58
*** tfukushima has joined #openstack-meeting08:58
*** ndipanov has quit IRC08:59
*** iyamahat has quit IRC08:59
*** haomaiwang has quit IRC09:01
*** haomaiwa_ has joined #openstack-meeting09:01
*** marekd has quit IRC09:01
*** mbound has joined #openstack-meeting09:02
*** tfukushima has quit IRC09:03
*** dprince has joined #openstack-meeting09:03
*** rbowen has quit IRC09:07
*** vgridnev has joined #openstack-meeting09:10
*** ityaptin has quit IRC09:13
*** tobe has quit IRC09:16
*** mrmartin has quit IRC09:18
*** mrmartin has joined #openstack-meeting09:20
*** ildikov has joined #openstack-meeting09:20
*** yassine__ has joined #openstack-meeting09:21
*** paul-carlton1 has joined #openstack-meeting09:21
*** zhhuabj has quit IRC09:24
*** julen has joined #openstack-meeting09:24
*** achanda has joined #openstack-meeting09:25
*** mhickey_ has joined #openstack-meeting09:26
*** reedip is now known as outofmemory09:27
*** rbowen has joined #openstack-meeting09:28
*** dmorita has joined #openstack-meeting09:29
*** tej has joined #openstack-meeting09:29
*** zhurong has quit IRC09:30
*** drankis has joined #openstack-meeting09:30
*** achanda has quit IRC09:30
*** iyamahat has joined #openstack-meeting09:33
*** vivekd has quit IRC09:33
*** vivekd_ has joined #openstack-meeting09:33
*** vivekd_ is now known as vivekd09:33
*** dmorita has quit IRC09:34
*** tej has quit IRC09:34
*** SridharG has quit IRC09:34
*** zhhuabj has joined #openstack-meeting09:34
*** andymaier has joined #openstack-meeting09:34
*** mrmartin has quit IRC09:35
*** zeih has quit IRC09:37
*** zeih has joined #openstack-meeting09:38
*** neiljerram has joined #openstack-meeting09:38
*** _nadya_ has joined #openstack-meeting09:39
*** ihrachys has joined #openstack-meeting09:40
*** markd_ has joined #openstack-meeting09:40
*** amotoki has quit IRC09:40
*** mdavidson has quit IRC09:41
*** grumpycatt has quit IRC09:41
*** markd_ has quit IRC09:41
*** mdavidson has joined #openstack-meeting09:41
*** zeih has quit IRC09:43
*** xingchao has joined #openstack-meeting09:43
*** _nadya_ has quit IRC09:43
*** hashar_ has joined #openstack-meeting09:44
*** baojg has quit IRC09:44
*** SridharG has joined #openstack-meeting09:45
*** baojg has joined #openstack-meeting09:45
*** adiantum has joined #openstack-meeting09:46
*** grumpycatt has joined #openstack-meeting09:47
*** hashar has quit IRC09:47
*** xingchao has quit IRC09:48
*** ihrachys has quit IRC09:49
*** SridharG has quit IRC09:49
*** thorst has joined #openstack-meeting09:49
*** baojg has quit IRC09:49
*** SridharG has joined #openstack-meeting09:49
*** ppetit has joined #openstack-meeting09:50
*** zeih has joined #openstack-meeting09:51
*** luisfdez has joined #openstack-meeting09:51
*** mbound has quit IRC09:52
*** mbound has joined #openstack-meeting09:52
*** davechen has left #openstack-meeting09:54
*** mrmartin has joined #openstack-meeting09:54
*** mbound_ has joined #openstack-meeting09:55
*** mbound has quit IRC09:55
*** amotoki has joined #openstack-meeting09:55
*** gongysh has joined #openstack-meeting09:56
*** thorst has quit IRC09:57
*** rbowen has quit IRC09:57
*** mrmartin has quit IRC09:58
*** haomaiwa_ has quit IRC10:01
*** haomaiwang has joined #openstack-meeting10:01
*** SridharG has quit IRC10:01
*** rbowen has joined #openstack-meeting10:01
*** rbowen has quit IRC10:01
*** rbowen has joined #openstack-meeting10:01
*** bdrich_ has joined #openstack-meeting10:02
*** vivekd has quit IRC10:03
*** bdrich_ has quit IRC10:07
*** amotoki has quit IRC10:10
*** dprince has quit IRC10:12
*** SridharG has joined #openstack-meeting10:13
*** grumpycatt has quit IRC10:14
*** markvoelker has joined #openstack-meeting10:19
*** xingchao has joined #openstack-meeting10:20
*** markvoelker has quit IRC10:23
*** amotoki has joined #openstack-meeting10:24
*** gongysh has quit IRC10:25
*** huangtianhua has quit IRC10:27
*** tiantian has joined #openstack-meeting10:29
*** amotoki_ has joined #openstack-meeting10:30
*** tej has joined #openstack-meeting10:31
*** _nadya_ has joined #openstack-meeting10:31
*** grumpycatt has joined #openstack-meeting10:31
*** rossella_s has quit IRC10:31
*** amotoki has quit IRC10:31
*** rossella_s has joined #openstack-meeting10:32
*** hoangcx has quit IRC10:32
*** rbowen has quit IRC10:33
*** vivekd has joined #openstack-meeting10:33
*** tej has quit IRC10:35
*** yamamoto_ has quit IRC10:37
*** AzherKhan has quit IRC10:42
*** ricolin has quit IRC10:42
*** amotoki_ has quit IRC10:42
*** amotoki has joined #openstack-meeting10:45
*** rfolco has joined #openstack-meeting10:47
*** rbowen has joined #openstack-meeting10:48
*** ildikov has quit IRC10:51
*** electrofelix has joined #openstack-meeting10:53
*** thorst has joined #openstack-meeting10:56
*** ppetit has quit IRC10:58
*** egallen has quit IRC10:58
*** ociuhandu has quit IRC10:58
*** haomaiwang has quit IRC11:01
*** haomaiwang has joined #openstack-meeting11:01
*** thorst has quit IRC11:01
*** dims_ has joined #openstack-meeting11:02
*** _nadya_ has quit IRC11:03
*** aysyd has joined #openstack-meeting11:03
*** _amrith_ is now known as amrith11:05
*** vahidh has joined #openstack-meeting11:11
*** alexpilotti has joined #openstack-meeting11:13
*** alexpilotti has quit IRC11:15
*** vahidh has quit IRC11:15
*** alexpilotti has joined #openstack-meeting11:18
*** ildikov has joined #openstack-meeting11:19
*** adahms has joined #openstack-meeting11:19
*** xingchao has quit IRC11:19
*** kjorgensen has joined #openstack-meeting11:22
*** jlanoux_ has joined #openstack-meeting11:27
*** kjorgensen has quit IRC11:27
*** agireud has quit IRC11:27
*** kashyap has joined #openstack-meeting11:27
*** jlanoux has quit IRC11:28
*** amakarov has joined #openstack-meeting11:28
*** rodrigods has quit IRC11:29
*** achanda has joined #openstack-meeting11:29
*** agireud has joined #openstack-meeting11:29
*** rodrigods has joined #openstack-meeting11:29
*** rbowen has quit IRC11:30
*** amotoki has quit IRC11:30
*** dmorita has joined #openstack-meeting11:30
*** tej has joined #openstack-meeting11:32
*** ociuhandu has joined #openstack-meeting11:34
*** achanda has quit IRC11:34
*** dmorita has quit IRC11:35
*** tej has quit IRC11:37
*** MarkAtwood has joined #openstack-meeting11:38
*** zeih has quit IRC11:39
*** reedip has joined #openstack-meeting11:42
*** fzdarsky_ has quit IRC11:47
*** fzdarsky has joined #openstack-meeting11:47
*** gus_ is now known as gus11:47
*** scinawa has quit IRC11:53
*** jlanoux_ has quit IRC11:55
*** cdent has joined #openstack-meeting11:57
*** jlanoux has joined #openstack-meeting11:58
*** gmann_ has joined #openstack-meeting11:59
*** baohua has quit IRC11:59
alex_xu#startmeeting nova api12:00
openstackMeeting started Tue Feb  2 12:00:02 2016 UTC and is due to finish in 60 minutes.  The chair is alex_xu. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: nova api)"12:00
openstackThe meeting name has been set to 'nova_api'12:00
alex_xuwho is here today?12:00
cdento/12:00
gmann_hi12:00
oomichihi12:00
eliqiaoo/12:00
*** thorst has joined #openstack-meeting12:00
johnthetubaguyo/12:00
* alex_xu found he have slow network12:00
alex_xuwelcome back everyone!12:01
*** haomaiwang has quit IRC12:01
alex_xulet's run the meeting12:01
alex_xu#topic content patches up for review12:01
*** openstack changes topic to "content patches up for review (Meeting topic: nova api)"12:01
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/complete-todo-in-api-concept-doc,n,z12:01
*** haomaiwang has joined #openstack-meeting12:01
alex_xuthanks for the review about microversion!12:01
alex_xuthe last few concept about server we left12:01
alex_xuI think we can finish them in Mitaka12:02
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/api-site+branch:master+topic:fix-compute-api-ref,n,z12:02
jicheno/12:02
sdagueo/12:02
alex_xujichen: still thanks for all your work on the api ref :)12:02
*** Kevin_Zheng has joined #openstack-meeting12:02
jichenalex_xu: :)12:03
Kevin_Zhengo/12:03
alex_xuAnd as we have a lot of feature merged, so I think we should keep eye on some feature may need update api concept doc, we should ask people help us keep the doc update to date.12:03
alex_xuSo happy when I saw this patch https://review.openstack.org/#/c/273376/312:03
oomichialex_xu: all TODOs can be removed with current patches from api-ref? or need more new patches?12:03
alex_xuoomichi: need more patches, there are few in servers concept12:04
oomichialex_xu: ok, I see12:04
alex_xuwait, I remember there are some about network and volume api, but I think servers concept is more important12:04
*** lazy_prince has quit IRC12:04
* sdague stars all these reviews to come back to later12:04
johnthetubaguythere was a discussion about network APIs this morning12:04
*** toscalix has joined #openstack-meeting12:04
alex_xujohnthetubaguy: discuss at where?12:05
johnthetubaguyit would be good to describe our preference for configuring ports outside of Nova12:05
alex_xujohnthetubaguy: +112:05
johnthetubaguyjust in the nova channel, a few hours back12:05
alex_xucool, I will scrollback later12:05
johnthetubaguyalso the get me a network, that is on its way, makes the "do the default networking" think work for more use cases12:06
johnthetubaguybut anyways, just an aside, it would be nice to get that into the docs12:06
alex_xuand a little describe about image api also, about user should use glance api instead of image api in nova12:06
sdaguejohnthetubaguy: I can't wait for that, I have some weird code in grenade to smooth over the nova-net / neutron differences12:06
gmann_johnthetubaguy: +1 for documenting those12:06
sdaguealex_xu: right, I think a piece of that is we're going to need to start returning imageRef links directly back to glance, which we only do on the image proxy today12:07
*** thorst has quit IRC12:07
johnthetubaguysdague: ack seems like loads of folks are feeling that pain12:07
alex_xucool, let us finish the concept doc in Mitaka, and we should begin to ask people update doc when there patch merged12:08
sdagueI think we're probably at the point in the cycle where we should get up a wish list for things we think should change in the API in the next cycle, and start prioritizing12:08
sdagueso we can hit the ground running12:08
alex_xusdague: +112:08
jichen+112:08
*** jdob has joined #openstack-meeting12:08
sdagueI think structured errors in json would be one of the best adds, but it going to take a lot of people working together on it.12:08
alex_xusdague: how can we start that? create an etherpad first, then people begin put the idea in?12:09
sdaguealex_xu: yeh, I think etherpad12:09
sdagueyou want to start one? and we can discuss during open discussion at the end of meetings over the next month12:09
alex_xusdague: yes12:09
alex_xu#link https://etherpad.openstack.org/p/newtown-nova-api-idea12:09
alex_xucreate one is fast :)12:09
johnthetubaguyI think its newton?12:09
gmann_sdague: alex_xu structured errors in json ?12:10
alex_xuoops, sorry...12:10
*** maishsk has joined #openstack-meeting12:10
johnthetubaguybut top idea to collect those now12:10
johnthetubaguyI think that should include the policy discovery work12:10
sdaguejohnthetubaguy: ++12:10
alex_xu#link https://etherpad.openstack.org/p/newton-nova-api-ideas12:10
alex_xu^ the new one...12:10
johnthetubaguymore documentation around the "find my external IP" workflows, and other interop like things12:10
sdagueyep, sounds great12:10
alex_xuand swagger one12:11
alex_xujohnthetubaguy: thanks, you already begin to edit it :)12:11
* oomichi knows the next version is newton now12:12
alex_xudo we want to discuss idea now, or leave it to next few weeks, just put the idea into the etherpad now?12:12
*** raildo-afk is now known as raildo12:12
johnthetubaguylets just revisit at the next meeting?12:13
johnthetubaguywhile folks type ideas over the week?12:13
gmann_+112:13
* johnthetubaguy needs to remember to talk about the ML thread about policy12:13
*** dmacpher has joined #openstack-meeting12:13
sdaguejohnthetubaguy: ++12:13
alex_xucool12:13
alex_xubad news is Chineses new year in next week...12:14
alex_xubut I may try to attend the meeting12:14
alex_xuanyway let's move on12:14
alex_xu#topic remove project id12:14
*** openstack changes topic to "remove project id (Meeting topic: nova api)"12:14
sdaguethat code has landed12:14
sdagueit's microversion 2.1812:15
alex_xusdague: all of them?12:15
*** andymaier has quit IRC12:15
sdagueit was only one change at the end of the day12:15
alex_xuoh, I remember that, I +w...12:15
sdaguethere are some test cleanups that would be nice12:15
jichensdague: do we need changes in python-novaclinet?12:15
johnthetubaguyalex_xu: lets say the week after for the deeper discussion, that seems OK12:15
sdaguejichen: those are already in12:15
*** yamamoto has joined #openstack-meeting12:15
jichensdague: ok,12:15
sdaguethis devstack change would use this in normal runs - https://review.openstack.org/#/c/233079/12:15
alex_xujohnthetubaguy: ok12:16
sdaguehowever, there is a tempest negative test class that fails under that scenario, I've suggested we remove it12:16
sdaguehttps://review.openstack.org/#/c/271467/12:16
*** _nadya_ has joined #openstack-meeting12:16
alex_xuok, sounds good12:18
*** zeih has joined #openstack-meeting12:18
johnthetubaguysdague: good point, they are testing odd things really12:18
sdagueyeh, we just need to realize that sometimes the tests are no longer appropriate12:18
sdaguehonestly, I'd like to drop all the negative testing out of tempest and only do it in our functional stack. Especially as it's all supposed to be caught by jsonschema now for the most part12:19
johnthetubaguyyeah, agreed with that general direction12:20
*** markvoelker has joined #openstack-meeting12:20
oomichisdague: yeah, agree. but refstack is using some negative tests, so we need to take care for tempest consumers12:20
johnthetubaguyits tempting to make defcore test certain error cases, but I am not quite sure how to deal with that12:20
*** amotoki has joined #openstack-meeting12:20
sdagueoomichi: I didn't think refstack was supposed to be using negative tests12:21
oomichito be honest, I cannot find any merit why refstack is using them12:21
gmann_sdague: oomichi i agree refstack should not tests so much negative testing at low level12:21
*** amakarov has quit IRC12:21
johnthetubaguyI think its where a client needs to know how to recover from particular errors, but that probably isn't want most of those tests are doing anyways12:21
gmann_its all component can make sure those.12:21
sdaguethis test was a bad choice for compatibility for sure12:21
*** iyamahat has quit IRC12:22
oomichisdague: yes12:22
*** yamamoto has quit IRC12:22
*** novas0x2a|laptop has quit IRC12:22
*** edleafe_ has joined #openstack-meeting12:23
alex_xuok, so sounds goods for now12:23
*** yamamoto has joined #openstack-meeting12:23
alex_xulet's move on?12:23
* edleafe_ yawns12:23
sdaguealex_xu: ++12:24
alex_xu#topic API futures - patches for approved specs12:24
*** openstack changes topic to "API futures - patches for approved specs (Meeting topic: nova api)"12:24
alex_xu#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/api-sample-tests-with-all-extensions12:24
*** weshay_xchat has joined #openstack-meeting12:24
alex_xuwe merged part of those patches12:24
alex_xulooks like we track the work have effect12:24
alex_xusdague: I saw you -1 one of them12:24
*** markvoelker has quit IRC12:24
gmann_alex_xu: yea, server things are making more clean12:24
gmann_sdague: https://review.openstack.org/#/c/243396/12:24
alex_xubut I think it is ok, as we deprecated extension for legacy v2 api also12:24
gmann_sdague: actually for v2 also extensions are deprecated12:25
sdaguealex_xu: we deprecated it, we didn't drop it12:25
sdagueif we drop these tests, we're going to break it12:25
sdaguedeprecated still means it needs to work12:25
gmann_sdague: but same thing for v2.1 also12:25
sdagueI'm fine if we don't test this on v2.112:25
sdaguebut on the legacy v2 stack, I think we still need this12:25
alex_xusdague: emm...good point, deprecated != drop12:25
alex_xuactually we already merge some sample tests for merge legacy v2 and v2.1 tests12:26
alex_xuok12:26
johnthetubaguyits good for the v2.1 tests to always test with all extensions on, but yeah, v2.0 probably should keep the existing stuff12:26
sdaguemy feeling is that extensions go away for real once we actually delete v2 legacy12:26
gmann_yes, tests are shared among them and some are merged12:26
*** bnemec has joined #openstack-meeting12:26
sdagueright, that's a bit problematic for what we want here12:26
johnthetubaguysdague: I think thats the truth12:26
alex_xuok, if we really feel uncomfortable for now, let wait for drop legacy v212:27
johnthetubaguysdague: about the extensions being tied to legacy v2 that is12:27
johnthetubaguyfor v2.1 tests, I really would like them only to work with all extensions on12:27
johnthetubaguythat might confuse things12:27
sdaguealex_xu: yeh. Also auggy is working through adding some test cases to the api samples testing engine, which might let us go both ways12:27
gmann_johnthetubaguy: sdague so in that case we should keep doc too?12:27
*** yamamoto has quit IRC12:27
sdaguehonestly, I think we need to write down what we expect here12:28
alex_xusdague: that sounds cool, hope to see auggy's patch12:28
johnthetubaguyyeah, it feels like we are confused12:28
sdaguemaybe a spec or etherpad or something, just so we figure out where we are trying to get to12:28
johnthetubaguy+1 for a quick etherpad12:28
johnthetubaguymaybe use that newton one we just created?12:28
alex_xusdague: +112:29
sdaguejohnthetubaguy: sure, though I think a bunch of this can still happen in mitaka, as it's test / doc fixes12:29
johnthetubaguysdague: yeah, totally, thats a bit confusing I guess12:29
*** toscalix has quit IRC12:29
sdaguegmann_: can you start an etherpad for this? and we can make sure we're all on the same page before we move forward12:29
*** toscalix has joined #openstack-meeting12:29
gmann_sdague: sure, will create separate one and link that to newton one12:30
sdaguegmann_: great, thanks12:30
gmann_sdague: ll be creating tomorrow morning12:30
johnthetubaguycools12:30
gmann_i will hold current patches till then12:30
sdaguegmann_: works for me, just send a ping or an ML thread with the link and I'll put comments in it12:31
gmann_sdague: sure.12:31
alex_xugmann_: thanks for all test merge works :)12:31
gmann_alex_xu: np :)12:31
alex_xuok, cool, I think we can move on12:31
alex_xu#topic open12:31
*** openstack changes topic to "open (Meeting topic: nova api)"12:31
alex_xuthere is one open in the agenda12:32
alex_xuNOTE about support "OS-SCH-HNT:scheduler_hints" as a subset of server dict in scheduler_hints.py:https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/scheduler_hints.py#L34-L37 "OS-DCF:diskConfig" is now a subset of server dict, quite strange to have scheduler_hints at top level. Question: should we do it in Newton? If do it, should we do it with microversion or not?12:32
alex_xuKevin_Zheng: ^ are you here12:32
Kevin_Zhengyes12:32
Kevin_ZhengI'm heare12:32
Kevin_Zhenghere12:32
alex_xuKevin_Zheng: cool, your turn12:32
Kevin_ZhengHi, a;;12:32
sdagueI think that probably needs a spec, because the fallout of who we might break is unclear to me12:32
Kevin_Zhengsorry12:32
gmann_I think we definitely need microversion12:33
sdaguebut it seems pretty sane12:33
*** ljxiash has joined #openstack-meeting12:33
sdagueyeh, definitely a microversion, which means it needs a spec12:33
gmann_sdague: +1 for spec first12:33
oomichialex_xu: nice point. From the client viewpoint, that makes difficult to implement client code.12:33
alex_xu+1 for microversion12:33
Kevin_ZhengOK then12:33
Kevin_ZhengI will prepare a spec first12:33
oomichialex_xu: I faced the problem on tempest side also before12:33
*** tej has joined #openstack-meeting12:33
Kevin_ZhengAnd I have another question12:33
gmann_yea even while v2.1 also12:34
Kevin_Zhengor idea12:34
*** sudipto has joined #openstack-meeting12:34
Kevin_ZhengI saw this tag-instance bp was in the list12:34
alex_xuoomichi: ok, I just say +1, then I got a nice point :)12:34
*** julim_ has joined #openstack-meeting12:34
Kevin_Zhengcan we talk about it ?12:34
alex_xuKevin_Zheng: yes12:34
*** j_king_ has joined #openstack-meeting12:35
Kevin_ZhengWe want to use this feature in or productr12:35
Kevin_Zhengproduct12:35
Kevin_Zhengand we have a usecase like this12:35
alex_xuactually I found a problem in tag instance bp, I don't think '/' works in our wsgi framework, we may return that is back to api-wg, to define a better tag-name schema.12:35
*** numan_ has joined #openstack-meeting12:35
Kevin_Zhengwe want some tags only available for the admin12:35
*** jlanoux_ has joined #openstack-meeting12:36
*** nug has quit IRC12:36
*** j_king has quit IRC12:36
*** cFouts is now known as nug12:36
*** numans has quit IRC12:36
*** julim has quit IRC12:36
*** DuncanT has quit IRC12:36
*** paul-carlton1 has quit IRC12:36
*** links has quit IRC12:36
*** anthonyper has quit IRC12:36
*** ptoohill has quit IRC12:36
Kevin_Zhengbut we don't want to change the policy file, because then the normal user couldn't use this feature12:36
Kevin_Zhenghow about add a column, admin_only to the table12:36
*** nug is now known as Guest6779512:36
*** jlanoux has quit IRC12:36
*** bswartz has quit IRC12:36
Kevin_Zhengand only admin can change this field12:37
Kevin_Zhengif it is admin only, then non-admin cant see it12:37
sdaguehmmmm12:37
*** DuncanT has joined #openstack-meeting12:37
johnthetubaguyit feels like the protected properties that glance has12:37
sdagueit almost feels like tags should namespace to roles12:37
*** paul-carlton1 has joined #openstack-meeting12:37
johnthetubaguyhmm, maybe12:37
sdaguerole:tag12:38
alex_xuor just record the owner of tag12:38
sdagueand you can only see the tags for the roles12:38
*** ptoohill has joined #openstack-meeting12:38
sdaguethat you are in12:38
johnthetubaguyso we haven't yet merged the current tags blueprint, it needs more review12:38
*** tej has quit IRC12:38
*** anthonyper has joined #openstack-meeting12:38
*** gnarld_ has joined #openstack-meeting12:38
johnthetubaguysdague: hmm, but when you add them, which role gets them? you always need the prefix?12:38
sdagueyeh, I do get the idea of different views on that though. Maybe we should debate that one in the spec12:38
Kevin_Zhengyes it will be very useful to do ops12:38
sdaguedo we have default role construct?12:38
johnthetubaguyfeels like a good spec debate12:38
sdagueyeh, this should also get a slot at summit I think12:39
johnthetubaguysdague: not AFAIK12:39
*** cschulz has joined #openstack-meeting12:39
Kevin_ZhengHm, just want to raise this up12:39
sdaguebecause this is one of those things that 40 minutes face to face would help resolve12:39
johnthetubaguysdague: +112:39
*** links has joined #openstack-meeting12:39
Kevin_ZhengHm, thanks alot12:39
alex_xucool12:39
sdagueKevin_Zheng: in the mean time, please put your thoughts into the existing spec12:39
johnthetubaguysdague: actually, it might be member, or just being in the tenant, that is the default12:39
*** banix has joined #openstack-meeting12:40
sdaguejohnthetubaguy: sure, but there is a visibility thing which is interesting12:40
johnthetubaguysdague: +112:40
Kevin_Zhengsdague: sure I will do that12:40
johnthetubaguyso I think we have merged the current spec, so its probably a new newton spec12:40
*** banix has quit IRC12:41
alex_xuI also will check '\' case, then feedback to author, hope he can fix the schema early if there is a problem.12:41
johnthetubaguyhttp://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/tag-instances.html12:41
sdaguealex_xu: ++12:41
alex_xuok, cool, the last thing12:42
*** thorst has joined #openstack-meeting12:42
*** sudipto_ has joined #openstack-meeting12:42
alex_xuappreciate who can chair this meeting in next week, I may not there for Chineses new year12:42
edleafe_Too early for me, sorry12:43
sdaguealex_xu: I can do it12:43
*** boris-42 has quit IRC12:43
alex_xusdague: thanks :)12:44
*** sudipto has quit IRC12:44
alex_xuanymore open today?12:44
* alex_xu pokes edleafe_ multiple times, help him get wakeup12:44
sdaguenothing from me12:44
alex_xu3...12:44
alex_xu2..12:45
alex_xu1.12:45
alex_xuthanks all!12:45
alex_xu#endmeeting12:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"12:45
edleafe_Thanks!12:45
openstackMeeting ended Tue Feb  2 12:45:20 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:45
gmann_Thanks all12:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-02-02-12.00.html12:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-02-02-12.00.txt12:45
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_api/2016/nova_api.2016-02-02-12.00.log.html12:45
oomichithanks :)12:45
Kevin_Zhengbye12:45
jichenthanks~12:45
*** MaxPC has joined #openstack-meeting12:46
johnthetubaguyoops, I forgot my topic12:46
johnthetubaguynext time12:46
*** yamamoto has joined #openstack-meeting12:46
*** dencaval has joined #openstack-meeting12:46
*** cdent has left #openstack-meeting12:47
*** gmann_ has quit IRC12:48
*** deva_ has joined #openstack-meeting12:49
*** MaxPC has quit IRC12:50
* eliqiao testing...12:52
*** baoli has joined #openstack-meeting12:53
*** andymaier has joined #openstack-meeting12:53
*** yamamoto has quit IRC12:56
*** erlon has joined #openstack-meeting12:57
*** tiantian has quit IRC12:57
*** deva_ has quit IRC12:58
*** haiwei has joined #openstack-meeting12:58
*** tiantian has joined #openstack-meeting12:58
*** MaxPC has joined #openstack-meeting12:58
*** anteaya has joined #openstack-meeting12:59
*** lxsli has joined #openstack-meeting12:59
*** amotoki has quit IRC13:00
*** haomaiwang has quit IRC13:01
*** haomaiwa_ has joined #openstack-meeting13:01
*** vikram_ has joined #openstack-meeting13:03
*** egallen has joined #openstack-meeting13:03
*** oomichi has quit IRC13:05
*** ayoung has quit IRC13:05
*** anteaya has quit IRC13:06
*** lxsli has quit IRC13:06
*** doug-fish has joined #openstack-meeting13:07
*** jjmb1 has joined #openstack-meeting13:07
*** jjmb has quit IRC13:08
*** Shrews has left #openstack-meeting13:09
*** ygbo has joined #openstack-meeting13:10
*** bobh has joined #openstack-meeting13:11
*** maishsk_ has joined #openstack-meeting13:12
*** ebagdasa has quit IRC13:12
*** maishsk has quit IRC13:12
*** maishsk_ is now known as maishsk13:12
*** hashar_ is now known as hashar13:13
*** balajiiyer has joined #openstack-meeting13:16
*** amotoki has joined #openstack-meeting13:16
*** ihrachys has joined #openstack-meeting13:16
*** MarkAtwood has quit IRC13:17
*** grumpycatt has quit IRC13:18
*** balajiiyer has quit IRC13:18
*** haomaiwa_ has quit IRC13:19
*** adrianofr has joined #openstack-meeting13:20
*** markvoelker has joined #openstack-meeting13:21
*** davidlenwell has quit IRC13:24
*** grumpycatt has joined #openstack-meeting13:24
*** xyang1 has joined #openstack-meeting13:25
*** gongysh has joined #openstack-meeting13:25
*** bobh has quit IRC13:26
*** markvoelker has quit IRC13:26
*** markvoelker_ has joined #openstack-meeting13:26
*** haiwei has quit IRC13:26
*** yamamoto has joined #openstack-meeting13:27
*** yamamoto has quit IRC13:27
*** yamamoto has joined #openstack-meeting13:28
*** tellesnobrega_af is now known as tellesnobrega13:28
*** davidlenwell has joined #openstack-meeting13:29
*** FallenPegasus has joined #openstack-meeting13:30
*** vivekd has quit IRC13:31
*** dmorita has joined #openstack-meeting13:32
*** achanda has joined #openstack-meeting13:33
*** topol_ is now known as topol13:33
*** vivekd has joined #openstack-meeting13:33
*** zeih has quit IRC13:33
*** hoangcx has joined #openstack-meeting13:34
*** tej has joined #openstack-meeting13:35
*** RuiChen has quit IRC13:36
*** pradk has joined #openstack-meeting13:36
*** pradk has quit IRC13:36
*** gnarld_ is now known as nug13:37
*** tlbr has quit IRC13:37
*** RuiChen has joined #openstack-meeting13:37
*** sudipto_ has quit IRC13:38
*** achanda has quit IRC13:38
*** dmorita has quit IRC13:38
*** tej has quit IRC13:39
*** tej has joined #openstack-meeting13:40
*** bill_az has joined #openstack-meeting13:41
*** su_zhang has joined #openstack-meeting13:41
*** andymaier has quit IRC13:42
*** pradk has joined #openstack-meeting13:43
*** pradk has quit IRC13:43
*** regXboi has joined #openstack-meeting13:45
*** zul has quit IRC13:45
*** tochi has quit IRC13:46
*** zeih has joined #openstack-meeting13:46
*** hichihara has joined #openstack-meeting13:47
*** neelashah has joined #openstack-meeting13:48
*** zeih has quit IRC13:48
*** zeih has joined #openstack-meeting13:49
*** haomaiwang has joined #openstack-meeting13:50
*** krtaylor has quit IRC13:51
*** amrith is now known as _amrith_13:51
*** amitgandhinz has joined #openstack-meeting13:52
*** anteaya has joined #openstack-meeting13:54
*** jtomasek_ has quit IRC13:55
*** ppetit has joined #openstack-meeting13:57
*** longstaff has joined #openstack-meeting13:58
*** jgriffith is now known as jgriffith_away13:58
*** janzian has joined #openstack-meeting13:58
*** zul has joined #openstack-meeting13:58
*** mlavalle has joined #openstack-meeting13:59
ihrachyshi everyone, we'll start in 1 min14:00
yamamotohi14:00
*** pc_m has joined #openstack-meeting14:00
*** Sam-I-Am has joined #openstack-meeting14:00
vikram_hi14:00
hichiharahi14:00
mlavalleo/14:00
Sam-I-Amhello14:00
hoangcxhi14:00
haleybhi14:00
pc_mhi14:00
*** baoli has quit IRC14:00
rtheishi14:00
gongyshhelo14:00
scheuranhi14:00
*** dkranz has joined #openstack-meeting14:00
regXboio/14:00
*** haomaiwang has quit IRC14:01
ihrachysok, I assume everyone grabbed a cup of coffee, so let's do it :)14:01
ihrachys#startmeeting networking14:01
openstackMeeting started Tue Feb  2 14:01:11 2016 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: networking)"14:01
openstackThe meeting name has been set to 'networking'14:01
*** baoli has joined #openstack-meeting14:01
*** salv-orlando has joined #openstack-meeting14:01
HenryGo/14:01
xgermano/14:01
ihrachyshi all, thanks for joining in this early hour (for some of you)14:01
*** rkukura has joined #openstack-meeting14:01
ihrachysas you now probably know, we are back to doing bi-weekly alternating meetings14:01
*** haomaiwang has joined #openstack-meeting14:01
ihrachys#link https://review.openstack.org/#/c/272494/14:01
ihrachysand today is the first Tue meeting in the new year, yay!14:01
*** akuznetsov has joined #openstack-meeting14:02
salv-orlandoaloha14:02
ihrachys(thanks everyone to make it revived)14:02
amotokihi14:02
ihrachysArmando leans toward delegation [or maybe just some more sleep] :), so today I will run this meeting for you.14:02
mhickey_Hello14:02
ihrachysand probably some more in the future. We’ll see.14:02
ihrachysok... so...14:02
ihrachys#link https://wiki.openstack.org/wiki/Network/Meetings Agenda14:02
mhickey_ihrachys: thanks for reviving!:)14:02
xgerman+114:03
ihrachystoday we’ll try to keep the meeting focused, as usual14:03
ihrachysthe main goal for today is to follow up on milestone3 deliverables that we have not managed to cover the previous week14:03
*** MaxPC1 has joined #openstack-meeting14:03
ihrachysI hope other sections won’t take much time. But they always say that. ;)14:03
ihrachysbut first, some announcements14:03
ihrachys#topic Announcements14:03
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:03
ihrachysI remind everyone that we have a neutron mid-cycle in the cold and unforgiving Minnesota end of Feb14:04
*** MaxPC1 has quit IRC14:04
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/084672.html14:04
*** MaxPC1 has joined #openstack-meeting14:04
*** jwarendt has joined #openstack-meeting14:04
Sam-I-Ambrrrr14:04
ihrachysright. I won't go. :P14:04
ihrachysso get some warm clothes and get ready ;)14:04
*** MaxPC has quit IRC14:04
rossella_s:)14:04
*** bdrich_ has joined #openstack-meeting14:04
ihrachysalso, we have a code sprint for rolling upgrades, specifically for getting versioned objects for neutron core resources, in Brno mid March14:05
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/085328.html14:05
ihrachysI will update the sprint etherpad with some travel tips later today14:05
*** krtaylor has joined #openstack-meeting14:05
mhickey_how warmer is Brno?! :)14:05
rossella_sthanks ihrachys14:05
ihrachysthat one:14:05
ihrachys#link https://etherpad.openstack.org/p/code-sprint-neutron-objects-brno14:05
salv-orlandocompared to Minnesota is like hot14:05
*** lblanchard has joined #openstack-meeting14:05
ihrachysmhickey_: it's 12 degrees Celsius right now here, pretty fine for start of Feb :)14:05
*** banix has joined #openstack-meeting14:06
ihrachysnote: it's PLUS ;)14:06
mhickey_ihrachys: sure is! :)14:06
amotoki:)14:06
rossella_sit's pretty warm everywhere in Europe this year14:06
amotokiwarmer than tokyo14:06
*** sbelous_ has joined #openstack-meeting14:06
akamyshnikovahi, sorry for being late :(14:06
*** cdub has joined #openstack-meeting14:06
*** anilvenkata has joined #openstack-meeting14:06
ihrachysin March, sometimes you can walk in shorts. but no guarantees attached ;)14:06
ihrachysakamyshnikova: hi! :)14:06
*** iyamahat has joined #openstack-meeting14:07
ihrachysfinal announcement is: call for papers for Austin is now closed as of yesterday14:07
ihrachysnext stop: voting for talks and actually delivering them for those who will get through the filter. :)14:07
mhickey_ihrachys: closing today14:07
*** amakarov has joined #openstack-meeting14:07
amotokiit was extended 1day14:07
reedipihrachys its open till today14:07
ihrachysmhickey_: oh? I missed the extension.14:07
mhickey_amotoki: yes, thanks14:07
*** changbl has joined #openstack-meeting14:07
mhickey_ihrachys: there was an issue yesterday14:07
salv-orlandoihrachys: some issues with the submission website apparently14:07
*** FallenPegasus has quit IRC14:08
ajolate o/ (sorry)14:08
ihrachysok, then we are still good to do final update.14:08
ihrachysok. it's all from me. no more announcements anyone?14:08
*** diltram has joined #openstack-meeting14:08
mhickey_FYI: The new deadline to submit a talk is February 2 at 11:59pm PST (February 3 at 7:59 UTC)14:09
ihrachysok, let’s move on14:09
ihrachysmhickey_: thanks14:09
ihrachys#topic Bugs14:09
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:09
mlavallehi14:09
*** alexpilotti has quit IRC14:09
ihrachysmlaville, the stage is yours. anything worth team attention from the previous week?14:09
*** jtomasek__ has joined #openstack-meeting14:09
ihrachyssorry, mlavalle14:10
mlavalleit was a relatively quiet week.... Many bugs as usual, but not very many of importance14:10
*** bdrich_ has quit IRC14:10
mlavalleworth highlighting: https://bugs.launchpad.net/neutron/+bug/154041114:10
openstackLaunchpad bug 1540411 in neutron "kilo: ValueError: git history requires a target version of pbr.version.SemanticVersion(2015.1.4), but target version is pbr.version.SemanticVersion(2015.1.3)" [Critical,In progress] - Assigned to Dave Walker (davewalker)14:10
mlavallewe have this critical one. It affects many projects, it is well known an a solution is being worked on14:10
ihrachysI think we struggle to merge https://review.openstack.org/271396 now14:10
ihrachysbecause there are some issues with linuxbridge job in both stable branches lately14:11
ihrachysI need to look at specific causes14:11
ihrachysnjohnston_: I see you are the bug deputy for this week. thanks!14:11
ihrachyswe need more volunteers for the upcoming weeks. anyone willing to cover for the week starting Feb 8? Feb 15?14:11
njohnston_ihrachys: my pleasure!14:11
*** tlbr has joined #openstack-meeting14:11
mhickey_ihrachys: I can do the week after njohnston_14:11
*** sdake has quit IRC14:11
ajomhickey_++14:12
*** njohnston_ is now known as njohnston14:12
ihrachysmhickey_: ok, please put your name in the Agenda page14:12
*** drankis has quit IRC14:12
ihrachys#link https://wiki.openstack.org/wiki/Network/Meetings14:12
ajonjohnston++14:12
ajo:)14:12
*** phil_h has joined #openstack-meeting14:12
ihrachysspecifically, https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy14:12
mhickey_ihrachys: sure. I am green so may need some help?14:12
njohnstonmhickey: I'm green too, I'll share what notes I have14:12
ihrachysmhickey_: that's fine, let's talk during the week on the way forward. :)14:12
rossella_smhickey_, we can help, no worries. Thanks for stepping up14:12
ajomhickey_, I recommend you syncing with the exiting bug deputy by the end of the week :D14:12
amotokinjohnston covers the week of Feb 1. mhickey_ will cover Feb 8.14:12
ihrachysanyone for the week starting Feb 15?14:13
*** thomasem-away is now known as thomasem14:13
rossella_sI can take it ihrachys14:13
ihrachysrossella_s++14:13
ihrachysthanks folks, now we are packed for some more weeks!14:13
mhickey_njohnston, ihrachys, rossella_s, ajo: thanks14:13
mlavallemhickey_: There is a nice document in devref that works you through the process. Ping me14:13
ihrachysthanks to all volunteers. let’s move on to the juicy bits.14:13
ihrachys#topic Docs14:13
*** openstack changes topic to "Docs (Meeting topic: networking)"14:13
mhickey_mlavelle: ok, sure, thanks14:14
*** eezhova has joined #openstack-meeting14:14
ihrachysSam-I-Am: anything we should be aware of?14:14
Sam-I-Amhey14:14
ihrachyshey14:14
Sam-I-Amthe ongoing mtu stuff14:14
*** drankis has joined #openstack-meeting14:14
Sam-I-Amnot necessarily a docs thing, but its what i was working on for a while14:14
Sam-I-Amsomething we should probably solve for mitaka14:15
ihrachysSam-I-Am: ok, I guess we proceed in mailing thread for now and then we'll see what's the way out of the maze, right?14:15
*** ityaptin has joined #openstack-meeting14:15
ihrachysSam-I-Am: depending on the scope of the changes. if it's just enforcing same mtu for the whole data path in compute hosts, it may be fine for Mitaka.14:15
Sam-I-Ami think we know how to fix it for the built-in drivers, it just a matter of... do we need a spec? who does the work? etc14:15
*** MaxPC has joined #openstack-meeting14:15
*** lazy_prince has joined #openstack-meeting14:15
ihrachysfor the reference, it's around14:16
Sam-I-Amthere was a spec from a couple releases ago that wasnt fully implemented14:16
ihrachys#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/084241.html14:16
*** piet has joined #openstack-meeting14:16
*** MaxPC has quit IRC14:16
*** MaxPC2 has joined #openstack-meeting14:16
ihrachysSam-I-Am: ok cool, anything else?14:16
Sam-I-Amyeah14:16
Sam-I-Amfor the folks that werent at last weeks meeting, the networking guide is now versioned14:17
Sam-I-Ammeaning people can go back to versions for prior releases of openstack14:17
ajoSam-I-Am, : very nice14:17
ihrachyspiece of cake14:17
*** MaxPC1 has quit IRC14:18
*** jckasper has quit IRC14:18
amotokimitaka version of networking guide is found at http://docs.openstack.org/draft/draft-index.html14:18
Sam-I-Amother than that, currently working on updates for mitaka, which includes debating the best way to add provider network support to the existing scenarios14:18
amotokiThe draft index is not linked from the top page of docs.o.o14:18
*** achanda has joined #openstack-meeting14:18
*** zz_dimtruck is now known as dimtruck14:18
Sam-I-Amseems like a lot of people want "hybrid" options - boot VMs on provider networks and self-service/private networks14:18
*** jckasper has joined #openstack-meeting14:18
Sam-I-Amright now the classic scenarios only support booting VMs on private networks14:19
ajoSam-I-Am, yes, I've listened to that kind of feedback too14:19
Sam-I-Amthe hybrid scenario gets a bit more complex for first-timers... just another set of diagrams for attaching VMs to provider nets14:19
ihrachysSam-I-Am: some people don't take on the new tenant-y thing real quick14:19
Sam-I-Amthe other option is making another set of scenarios, but then they just proliferate :/14:20
*** jckasper has quit IRC14:20
*** dneary has joined #openstack-meeting14:20
mlavalleSam-I-Am: I am also working on a chapter for the new external DNS integration functionality. I will push first version for review later this week14:21
Sam-I-Ammy thinking now is just add on to the existing scenarios, sort of like we do with the install guide... one option built on another or somesuch14:21
*** jckasper has joined #openstack-meeting14:21
*** sgordon` is now known as sgordon14:21
ihrachysmlavalle: cool14:21
ihrachysok, I guess we need to move. thanks Sam-I-Am. and now for the most juicy part...14:22
ihrachys#topic Blueprints14:22
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:22
ihrachysprev week, we started walking thru the BPs targeted for M3. we have not completed the list though.14:22
ihrachysso let’s do it. :)14:22
ihrachys#link https://launchpad.net/neutron/+milestone/mitaka-314:22
ihrachysand the first one is14:22
ihrachys#link https://blueprints.launchpad.net/neutron/+spec/vm-without-l3-address14:22
ihrachysajo: can you update us on ^?14:23
ihrachysI see some pieces are merged14:23
ajoihrachys, give me a sec, you got me off guard :)14:23
*** jichen has quit IRC14:23
ajocan we move on, and get back to this one in a minute? :)14:23
ihrachysok, let's move. we'll get back to it.14:24
*** alexpilotti has joined #openstack-meeting14:24
*** edtubill has joined #openstack-meeting14:24
*** hynekm has joined #openstack-meeting14:24
ihrachys#link https://blueprints.launchpad.net/neutron/+spec/ml2-lb-ratelimit-support14:24
*** RuiChen has quit IRC14:24
ihrachysit's on me (and slawek)14:24
*** banix_ has joined #openstack-meeting14:24
*** RuiChen has joined #openstack-meeting14:24
ihrachysI think we are still waiting for fullstack resources for linuxbridge, but apart from it, the qos patch itself is good to go. so hopefully we get it in M.14:24
ihrachysthe next is...14:25
ihrachys#link https://blueprints.launchpad.net/neutron/+spec/add-tags-to-core-resources14:25
ihrachysamotoki: ^ any update?14:25
*** rbak has quit IRC14:25
*** banix__ has joined #openstack-meeting14:25
amotokihichihara volunteered for implementations.14:25
hichiharaYes. I guess that the spec will be merged soon.14:25
amotokiI need to do the final review on -spec.14:25
hichiharaI have posted PoC patch14:25
*** peristeri has joined #openstack-meeting14:26
ihrachysdo we think we get it in M?14:26
hichiharaihrachys: Of cource.14:26
amotokiI think we can.14:26
ihrachysthat's cool.14:26
*** rbrady has joined #openstack-meeting14:26
*** rbrady has left #openstack-meeting14:27
ihrachysnote everyone M3 is sometime start of March, so we have a month to get clear on all deliverables for M.14:27
ihrachys#link https://blueprints.launchpad.net/neutron/+spec/add-timestamp-attr14:27
*** banix has quit IRC14:27
*** banix__ is now known as banix14:27
amotokiwe can revisit the status two weeks later14:27
*** achanda has quit IRC14:27
ihrachysI suspect kevinbenton is not here.14:27
*** alexpilotti has quit IRC14:27
ihrachysanyone has the status for the bp?14:27
*** alexpilotti has joined #openstack-meeting14:28
ihrachysI see some 3 patches in review at https://review.openstack.org/#/q/topic:bp/add-port-timestamp,n,z14:28
anteayaweek of feb 29 is m3: http://docs.openstack.org/releases/mitaka/schedule.html14:28
*** banix_ has quit IRC14:28
ajoanteaya, thanks for the reminder14:28
ihrachysanteaya: thanks for the correction! so yeah, even less time to push code in.14:28
anteayaor review patches, depending on how you look at it14:29
* ajo tightens his seatbelt14:29
*** pbelamge has quit IRC14:29
ihrachysok, I guess we don't have anyone here to update on the add-port-timestamp spec. let's move on.14:29
ihrachys#link https://blueprints.launchpad.net/neutron/+spec/network-ip-usage-api14:29
*** piet has quit IRC14:29
ihrachysthat's also on kevinbenton14:29
ihrachysthe patch is under active review14:30
ihrachys#link https://review.openstack.org/#/c/212955/14:30
*** grumpycatt has quit IRC14:30
ihrachysand I see the right folks shaving it :)14:30
*** kebray has joined #openstack-meeting14:30
ihrachysok, next14:30
ajoyaks gotta be shaved14:30
ihrachys#link https://blueprints.launchpad.net/neutron/+spec/improve-dvr-l3-agent-binding14:31
ihrachyscarl_baldwin: obondarev: what's on that one? ^14:31
obondarevimplemented14:31
obondarevlast patch was merged yesterday14:31
obondarevthanks to reviewers14:31
mesteryo/14:31
*** rossella_s has quit IRC14:31
amotokigood to hear that :)14:31
*** dane has joined #openstack-meeting14:31
ajo:)14:32
*** pbelamge has joined #openstack-meeting14:32
ihrachysobondarev: what's the https://review.openstack.org/#/c/143169/ then?14:32
mesteryyay!14:32
mestery:)14:32
ihrachysit has the topic referring to the bp14:32
*** rossella_s has joined #openstack-meeting14:32
obondarevihrachys: it's by mistake I guess14:32
obondarevit was based on dvr refactiring14:32
ihrachysthat's great news actually. thanks to reviewers and obondarev for driving it.14:33
*** zul has quit IRC14:33
haleybobondarev: that was re-based on top of yours, so maybe picked up the tag14:33
amotokiobondarev: could you update the topic of 143169?14:33
ihrachysyeah, probably. better clear the topic not to confuse.14:33
obondarevamotoki: sure14:33
ihrachysok cool. we have stuff delivered woot.14:33
ihrachys#link https://blueprints.launchpad.net/neutron/+spec/address-scopes14:34
ihrachysI guess carl_baldwin is not here, but salv-orlando is ;)14:34
ihrachyssalv-orlando: are we far for ^ ?14:34
*** grumpycatt has joined #openstack-meeting14:35
*** piet has joined #openstack-meeting14:35
amotokithe whiteboard is too long....14:35
*** thangp has joined #openstack-meeting14:35
salv-orlandoWe are at the stage where the patches are good to go in14:35
salv-orlandoand I thought they were already in honestly as they fell off my review dashboard14:35
ihrachyssalv-orlando: do we have a single topic for all of them? as amotoki noted, the whiteboard is a graveyard14:35
haleybhttps://review.openstack.org/#/q/topic:bp/address-scopes,n,z shows 3 left, we're pretty close14:36
salv-orlandoihrachys: yes, there is ^14:36
ihrachysthat's an impressive list of patches already merged. I bet you get it in M. :)14:36
ihrachysthanks for everyone driving it14:36
salv-orlandohaleyb: that's 4 actually but besides th3 l3 agent support they're all little things14:37
*** dandruta has joined #openstack-meeting14:37
salv-orlandoand on the other hand without the l3 agent support the feature is quite... non-existent ;)14:37
ajo:)14:37
haleybah yes, one in merge conflict, the first one is the last big one really14:37
haleybgerrit seems to not be cooperating to look further14:38
ajogerrit--14:38
haleybit's back14:38
ihrachys#link https://blueprints.launchpad.net/neutron/+spec/lbaas-l7-rules14:39
ihrachysI am surprised it's not on dougwig! :) mestery, ^14:39
xgermanproceeding nicely14:39
mestery:)14:39
mesteryihrachys: For that one, I know that sbalukoff was telling me lovely stories abouti t last week14:39
mesteryxgerman likely also knows the tale I speak of14:40
*** ninag has joined #openstack-meeting14:40
ihrachysthat's a huge list of things to merge though:14:40
xgermanyeah, we have the code - need to review14:40
ihrachys#link https://review.openstack.org/#/q/topic:bp/lbaas-l7-rules,n,z14:40
amotokiI have to comment one thing on l7-rules. it should be implemented as a separate extension14:40
xgermanit is14:40
xgermanas an extension of LBaaS14:41
ihrachyshttps://review.openstack.org/#/c/148232/42/neutron_lbaas/extensions/l7.py14:41
xgermanyou mean top-level?14:41
*** dimtruck is now known as zz_dimtruck14:41
amotokixgerman: let me check later.14:41
xgermanok14:41
*** absubram has joined #openstack-meeting14:41
ihrachysok, next14:41
ihrachys#link https://blueprints.launchpad.net/neutron/+spec/rbac-qos14:42
ihrachyshdaniel posted a new lovely metaclass-y patch for db models and objects for RBAC QoS Policy14:42
*** absubram_ has joined #openstack-meeting14:42
ajocode looks lovely IMHO :)14:42
ihrachysbut I suspect it's not enough to land it? is it ajo?14:42
*** zz_dimtruck is now known as dimtruck14:42
ihrachys#link https://review.openstack.org/#/c/250081/14:43
*** pradk has joined #openstack-meeting14:43
ajoihrachys, I need to do a final pass of review, my initial pass was good14:43
ihrachysok, but do we have client and API covered?14:43
ajoihrachys, I'm unsure if API or clients needed changes, let me check,14:44
amotokinote that the client release deadline is earlier than server projects14:44
ihrachysI think so. otherwise how would it know which objects support RBAC?14:44
ihrachysamotoki: oh. any specific date?14:44
amotokiplease make sure to land patches before requirement deadline14:44
*** sbelous_ has quit IRC14:45
amotokino specific date14:45
amotokibut from past experience it is a bit earilier than X-3 cut.14:45
*** johnbelamaric has joined #openstack-meeting14:45
ihrachysajo: I think that may actually postpone the thing to N. we need to get everything in place in time or we slip forward.14:45
ihrachysamotoki: thanks for the heads-up14:45
ihrachysajo: can you work with hdaniel to get it all set?14:46
ajoihrachys, , yes, but we even have API tests14:46
ajoso I guess that's all good14:46
*** absubram has quit IRC14:46
*** absubram_ is now known as absubram14:46
ajoand I think the neutron client is independent, it will just check the object type through the api request14:47
ajoI will double check all that with hdaniel btw14:47
*** wanghao_ has joined #openstack-meeting14:47
ihrachysajo: ok we need to check, especially the client.14:47
ihrachysthanks ajo and hdaniel14:47
ihrachysnext is...14:47
ajoI'm quite sure that's right, but will double check14:47
amotokiclient support for qos-rbac would be simple, and I have no concern.14:47
ihrachys#link https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms14:47
ihrachysrossella_s: I bet you can update on vlan awareness14:48
*** Daisy has joined #openstack-meeting14:48
*** rbak has joined #openstack-meeting14:48
ajowho's aware of vlan awareness? O:)14:48
rossella_sihrachys, spec was approved14:48
rossella_sihrachys, it took quite some time14:49
*** pbelamge has quit IRC14:49
ihrachysI suspect it's not M deliverable since only the spec is merged and it sounds like it will require a lot of code changes.14:49
ihrachysrossella_s: amirite?14:49
rossella_sihrachys, I think so too14:49
ihrachysI wonder whether we should start pushing things like that to N without waiting for M314:49
ihrachysneed to check with armax14:50
ihrachysok, back to ajo's bp14:50
ihrachys#link https://blueprints.launchpad.net/neutron/+spec/vm-without-l3-address14:50
ihrachysajo: give us some hope :)14:50
ajoyeah :)14:51
*** adahms has quit IRC14:51
ajook, the neutron side looks much better after a rearrangement of the limit-portsec field14:51
ajoIt's in merge conflict state, but yalie addressed all my comments so far, I need to check the latest patch14:52
ajoso, the neutron side of things probably will go in M14:52
ihrachysdo we have client?14:52
ajobut, the nova side wasn't accepted for this cycle14:52
*** edleafe_ has quit IRC14:52
ajoyes: https://review.openstack.org/#/c/218388/14:52
ajobeing worked out14:53
ihrachys I guess that -2 from armax is obsolete?14:53
*** _amrith_ is now known as amrith14:54
amotokiif server side patch is good enough from secrutiy point of view, I believe he can drop his -214:54
ajocorrect, I agree with amotoki14:54
ajobut we need to consider his point of view14:54
ihrachysok, I will leave you to push for M3 then :) good luck.14:55
ihrachysand... that's about it for bps14:55
ihrachys#topic Open Discussion14:55
*** openstack changes topic to "Open Discussion (Meeting topic: networking)"14:55
ihrachyswe have 5 mins only, but if someone has anything to bring up, you are welcome14:55
anilvenkatacan someone set milestone for prefix delegation bug https://bugs.launchpad.net/neutron/+bug/150531614:55
openstackLaunchpad bug 1505316 in neutron "compute port lose fixed_ips on restart l3-agent if subnet is prefix delegated" [Medium,In progress] - Assigned to venkata anil (anil-venkata)14:55
*** dimtruck is now known as zz_dimtruck14:55
amotokiwe have now keystone v3 devstack http://lists.openstack.org/pipermail/openstack-dev/2016-February/085497.html14:56
ihrachysamotoki: v3 only?14:56
*** MaxPC2 has quit IRC14:56
ihrachysanilvenkata: why do we need a specific milestone? it's not a High prio bug, right?14:56
ihrachys(at least not in LP)14:56
amotokiit is ongoing. i see problems in some other projects (not neutron)14:56
*** zul has joined #openstack-meeting14:57
*** keedya has joined #openstack-meeting14:57
amotokii don't know the full status on this...14:57
anilvenkataihrachys: prefix delegation is broken, that patch will fix it14:57
jckasperFYI:  As far as the mid-cycle meetup in Rochester, MN.   I live there.  Any questions on the location ... can contact me offline.14:57
ihrachysanilvenkata: ok, let's raise its Importance then to High I guess14:57
anteayajckasper: thank you14:57
njohnstonihrachys: Because this now has the 2 dependencies explicitly listed as dependencies, is the DSCP work eligible for lifting the -2?  https://review.openstack.org/#/c/25173814:58
amotokiIIRC now we have keystone v3 by default14:58
anilvenkataihrachys: thanks Ihar14:58
mhickey_jckasper: is it as cold as they say?! :)14:58
ihrachysjckasper: you can post your name in the etherpad for the event suggesting help there.14:58
anteayaI have something I would like to share14:58
ihrachysnjohnston: it is. I will remove it.14:58
njohnstonihrachys: Thanks!14:58
ihrachysanteaya: shoot14:58
anteayathank you14:58
anteayaI'm concerned with what I percieve to be the splintering of communication14:59
reedipamotoki : Yes, v3 is by default enabled.14:59
anteayaboth within this project and with this project's relationships with other projects14:59
*** MaxPC has joined #openstack-meeting14:59
*** mdavidson has quit IRC14:59
*** balajiiyer has joined #openstack-meeting14:59
anteayaI was surprised to see this meeting take place in this time slot14:59
anteayaas well as no mention of items covered in last week's nova mid-cycle14:59
amotokianteaya: why?14:59
ihrachysanteaya: why? we had it before at that same time right?14:59
*** angdraug has joined #openstack-meeting14:59
anteayaas well as a new mid-cycle announced for march15:00
anteayayou are welcome to disagree with me15:00
amotokiand we had a good announcement on -dev list15:00
ihrachysanteaya: which March midcycle?15:00
*** esker has joined #openstack-meeting15:00
anteayabut I think neutron is drifting farther and farther away from other projects15:00
anteayaihrachys: how many march mid-cycles were mentioned at this meeting?15:00
ihrachysanteaya: ok let me bring it up to armax15:00
*** haomaiwang has quit IRC15:01
anteayaI have voiced my concerns15:01
anteayathanks for listening15:01
ihrachysanteaya: that's code sprint, it's a bit different in its scope.15:01
amotokiit is not mnid-cycle. it is just code sprint for a specific topic15:01
ihrachysthanks folks! time to end the meeting15:01
ihrachys#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
salv-orlandoaideuuuu15:01
openstackMeeting ended Tue Feb  2 15:01:21 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-02-02-14.01.html15:01
xgermano/15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-02-02-14.01.txt15:01
*** pc_m has left #openstack-meeting15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2016/networking.2016-02-02-14.01.log.html15:01
njohnstono/15:01
*** haomaiwa_ has joined #openstack-meeting15:01
rossella_sthanks ihrachys, bye all15:01
*** rkukura has left #openstack-meeting15:01
diltrambye all15:01
amotokithanks ihrachys15:01
hichiharaihrachys: thank you for your leading15:01
hichiharabye15:01
*** regXboi has left #openstack-meeting15:01
jwarendtbye15:01
hoangcxthanks! bye15:02
*** janzian has left #openstack-meeting15:02
mhickey_bye, thanks15:02
*** jwarendt has quit IRC15:02
*** Sam-I-Am has left #openstack-meeting15:02
*** longstaff has left #openstack-meeting15:02
ajothanks ihrachys !!15:02
*** diltram has left #openstack-meeting15:02
*** hoangcx has quit IRC15:02
*** bobh has joined #openstack-meeting15:02
*** krtaylor has quit IRC15:03
*** merooney has joined #openstack-meeting15:03
*** bryan_att has joined #openstack-meeting15:03
*** phil_h has quit IRC15:03
*** vikram_ has quit IRC15:03
*** hynekm has left #openstack-meeting15:04
*** sanghai has joined #openstack-meeting15:04
*** radek_ has joined #openstack-meeting15:04
*** kencjohnston has joined #openstack-meeting15:05
*** RuiChen has quit IRC15:06
*** _RuiChen has joined #openstack-meeting15:06
*** irenab has quit IRC15:07
*** piet has quit IRC15:08
*** mbound_ has quit IRC15:08
*** zul has quit IRC15:10
*** singhj has joined #openstack-meeting15:10
*** sigmavirus24_awa is now known as sigmavirus2415:10
*** ppetit has quit IRC15:11
*** zul has joined #openstack-meeting15:11
*** rajinir has joined #openstack-meeting15:11
*** links has quit IRC15:11
*** SridharG has quit IRC15:12
*** hichihara has quit IRC15:13
*** ihrachys has quit IRC15:14
*** reedip has quit IRC15:14
*** xingchao has joined #openstack-meeting15:14
*** krtaylor has joined #openstack-meeting15:15
*** eharney has joined #openstack-meeting15:15
*** baoli has quit IRC15:17
*** ajmiller has joined #openstack-meeting15:18
*** zz_dimtruck is now known as dimtruck15:18
*** zul has quit IRC15:18
*** bswartz has joined #openstack-meeting15:20
*** ayoung has joined #openstack-meeting15:20
*** merooney has quit IRC15:21
*** wwriverrat_ has quit IRC15:21
*** kebray has quit IRC15:21
*** mbound has joined #openstack-meeting15:23
*** amotoki has quit IRC15:24
*** timcline has joined #openstack-meeting15:26
*** merooney has joined #openstack-meeting15:26
*** mtanino has joined #openstack-meeting15:27
*** ljxiash has quit IRC15:28
*** radek_ has quit IRC15:28
*** iyamahat has quit IRC15:29
*** vahidh has joined #openstack-meeting15:29
*** zul has joined #openstack-meeting15:30
*** emagana has joined #openstack-meeting15:32
*** bdrich_ has joined #openstack-meeting15:32
*** dmorita has joined #openstack-meeting15:35
*** barrett has joined #openstack-meeting15:36
*** zul has quit IRC15:36
*** kebray has joined #openstack-meeting15:37
*** baoli has joined #openstack-meeting15:38
*** vijendar has joined #openstack-meeting15:39
*** piet has joined #openstack-meeting15:39
*** dmorita has quit IRC15:40
*** numan_ has quit IRC15:43
*** MaxPC2 has joined #openstack-meeting15:43
*** MaxPC has quit IRC15:44
*** pradk_ has joined #openstack-meeting15:44
*** pradk has quit IRC15:44
*** pradk_ is now known as pradk15:44
*** MaxPC2 has quit IRC15:44
*** MaxPC has joined #openstack-meeting15:45
*** galstrom_zzz is now known as galstrom15:46
*** bill_az has quit IRC15:47
*** baoli has quit IRC15:47
*** phil_h has joined #openstack-meeting15:47
*** baoli has joined #openstack-meeting15:48
*** lazy_prince has quit IRC15:49
*** lazy_prince has joined #openstack-meeting15:50
*** ilyashakhat has joined #openstack-meeting15:50
*** akuznetsov has quit IRC15:50
*** vijendar has quit IRC15:51
*** kebray has quit IRC15:51
*** ihrachys has joined #openstack-meeting15:51
*** bill_az has joined #openstack-meeting15:52
*** zeih has quit IRC15:53
*** ygbo has quit IRC15:54
*** MaxPC1 has joined #openstack-meeting15:54
*** MaxPC has quit IRC15:54
*** _nadya_ has quit IRC15:54
*** dims has joined #openstack-meeting15:54
*** dims_ has quit IRC15:54
*** lazy_prince has quit IRC15:55
*** jlanoux_ has quit IRC15:55
*** lazy_prince has joined #openstack-meeting15:56
*** kebray has joined #openstack-meeting15:56
*** ihrachys has quit IRC15:58
*** maishsk has quit IRC15:58
*** cebruns has quit IRC15:59
*** garthb has joined #openstack-meeting15:59
phil_hadam_g: does anyone have any notes about setting up ha, load balancers or pez?15:59
*** devananda has joined #openstack-meeting16:00
*** clenimar has joined #openstack-meeting16:00
*** cebruns has joined #openstack-meeting16:00
*** n0ano has joined #openstack-meeting16:00
*** haomaiwa_ has quit IRC16:01
*** tellesnobrega is now known as tellesnobrega_af16:01
*** cznewt has joined #openstack-meeting16:01
jasondotstar#startmeeting #openstack-salt16:01
openstackMeeting started Tue Feb  2 16:01:24 2016 UTC and is due to finish in 60 minutes.  The chair is jasondotstar. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: #openstack-salt)"16:01
openstackThe meeting name has been set to '_openstack_salt'16:01
*** 6JTAAC8GZ has joined #openstack-meeting16:01
*** anilvenkata has left #openstack-meeting16:01
jasondotstar#topic Roll Call16:01
*** openstack changes topic to "Roll Call (Meeting topic: #openstack-salt)"16:01
jasondotstaro/16:01
cznewto/16:01
*** david-lyle has joined #openstack-meeting16:02
jasondotstarhi cznewt :-)16:02
jasondotstarGM16:02
jasondotstaranother 60secs16:02
cznewthello salters16:02
jasondotstarto see who else joins us :-)16:02
jasondotstarsalters unite!16:03
*** vijendar has joined #openstack-meeting16:03
jasondotstarok....16:03
jasondotstar#topic Introduction16:03
*** openstack changes topic to "Introduction (Meeting topic: #openstack-salt)"16:03
jasondotstarthis is the second irc meeting for the openstack-salt team16:03
jasondotstarIf you're interested in contributing to the discussion, please join #openstack-salt16:04
*** nkrinner has quit IRC16:04
jasondotstarMeetings are Weekly on Tuesdays at 1600UTC  <-now16:04
jasondotstar#link http://eavesdrop.openstack.org/#OpenStack_Salt_Team_Meeting16:04
jasondotstar#link     https://wiki.openstack.org/wiki/Meetings/openstack-salt16:04
*** garthb has quit IRC16:04
jasondotstar#topic Review past action items16:05
*** openstack changes topic to "Review past action items (Meeting topic: #openstack-salt)"16:05
*** yamamoto has quit IRC16:05
jasondotstarfirst order of business:16:05
jasondotstarcznewt to finish out the chapter on local dev environment (i.e vagrant)16:05
*** ygbo has joined #openstack-meeting16:05
*** kebray has quit IRC16:05
cznewtyes, the documentation is now up-to-date, how to provision vagrant16:05
jasondotstarso I think this is completed16:05
jasondotstarthanks cznewt - I'll try this out16:06
cznewtsingle node deployment, meaning 1 config, 1 control 1 compute node16:06
*** merooney has quit IRC16:06
jasondotstardo you have that link handy to post here?16:06
*** kebray has joined #openstack-meeting16:06
* jasondotstar looks16:07
*** genunix has joined #openstack-meeting16:07
jasondotstar#link http://openstack-salt.tcpcloud.eu/develop/quickstart-vagrant.html16:07
jasondotstarany other comments on this?16:07
cznewtUntil the official documentation is built use the preceding link16:07
*** yamamoto has joined #openstack-meeting16:07
cznewtthanks, jasondotstar16:07
jasondotstar+116:07
*** su_zhang has quit IRC16:08
*** irenab has joined #openstack-meeting16:08
cznewtthis is ok, well discuss heat in next topic16:08
jasondotstarcool..16:08
jasondotstarnext: cznewt to report on the completion of the core set of salt formulas16:08
*** yamamoto has quit IRC16:08
cznewtthe core formulas have been reviewed and all required parts are there16:09
jasondotstarany news here?16:09
cznewtwe've added tests16:09
jasondotstarnice16:09
cznewtfor the code style and metadata validity16:09
jasondotstar+116:10
cznewtwe've cought several errors by this mechanism already16:10
jasondotstarone question about the last topic16:10
jasondotstari just thought about16:10
jasondotstarfor the AIO deployment16:10
jasondotstarwould it be beneficial to have a aio script to run all the tasks required?16:10
jasondotstarthe puppet guys do something similar16:11
jasondotstarah...16:11
cznewtthe question is the other needed formulas are to be included in the openstack as well16:11
jasondotstari see you have something there already for booting up the salt formulas...16:11
genunixYou mean something like Salt orchestrate? Or Fabric in eg. opencontrail case?16:11
jasondotstarsalt master i mean16:11
cznewtyes there's a script to bootstrap salt-master from packages or git16:11
cznewtand for AIO deploy it's just matter of highstating the nodes16:12
jasondotstargotcha.16:12
genunixjasondotstar: basically this - https://github.com/tcpcloud/heat-templates/blob/master/templates/salt_single_public.hot#L12016:12
cznewtyes16:13
*** su_zhang has joined #openstack-meeting16:13
jasondotstari haven't looked at the details of this script but16:13
cznewtI've cleaned that up a little but basically that's it16:13
*** gokrokve has joined #openstack-meeting16:13
jasondotstarthere's a modular way that the puppet guys do it16:13
jasondotstaryou can add remove modules at will.16:13
jasondotstarim wondering if that's implemented here for the salt states...16:14
jasondotstarforgive me if it's there, and i just haven't seen it yet.16:14
*** vgridnev has quit IRC16:14
cznewtyou mean librarian?16:14
jasondotstarwell16:14
cznewtdependencies among modules?16:14
cznewtversions and so on16:14
jasondotstaryes16:14
jasondotstarthey've got the Puppetfile16:15
jasondotstarwith the list of modules in it16:15
cznewtwe had to do this for the testing purpose16:15
jasondotstartagged with version numbers and such.16:15
jasondotstarok16:15
genunixjasondotstar: there are nothing like puppetfiles in salt, but we have done this for testing dependencies - https://github.com/openstack/salt-formula-heat/blob/master/metadata.yml16:15
jasondotstarok16:15
jasondotstargotcha.16:15
cznewtdefine the dependencies, but it is not official16:15
genunixjasondotstar: anyway we prefer deployment using debian packages which can handle these things16:15
jasondotstari see.16:15
jasondotstarmakes sense16:16
jasondotstarok16:16
cznewtbut we could propose something like that to the salt community16:16
*** vhoward has joined #openstack-meeting16:16
cznewtif there's demand16:16
*** shihanzhang has quit IRC16:16
*** Drago has joined #openstack-meeting16:16
jasondotstar#agreed Perhaps proposing a dependency tool to the salt community is a good idea based on demand16:17
*** shihanzhang has joined #openstack-meeting16:17
cznewtalso that's another topic to adress: how to contribute to salt community as well16:17
jasondotstarcznewt: go for it16:17
jasondotstar#topic Contributing to the Salt communit16:17
*** openstack changes topic to "Contributing to the Salt communit (Meeting topic: #openstack-salt)"16:17
jasondotstar#topic Contributing to the Salt community16:17
*** openstack changes topic to "Contributing to the Salt community (Meeting topic: #openstack-salt)"16:17
*** Daisy has quit IRC16:17
jasondotstari've yet to do that.... thoughts?16:18
*** gongysh has quit IRC16:18
cznewtthe testing mechanisms for salt formulas16:18
cznewtthe formula dependencies16:18
cznewtthese are the things that might be valuable to salt community as well16:19
*** Daisy has joined #openstack-meeting16:19
genunixwe should discuss with salt community some standarized way to do this and possibly help with implementation16:19
genunixmaybe the same for debian packaging of formulas which we have already done16:19
jasondotstar+116:19
*** lazy_prince has quit IRC16:20
cznewtthe salt-linters out in the wild are outdated and need to be cleaned.16:20
*** bdrich_ has quit IRC16:20
jasondotstarso upstream from us might be work in the salt project itself16:21
*** sdake has joined #openstack-meeting16:21
jasondotstarand where it makes sense we should push those items up there.16:21
cznewtyes i think so16:21
genunix#agreed work with salt community - agree on standard for versioning and satisfying formula dependencies (aka Puppetfile) and for packaging16:21
jasondotstarvery well.16:22
jasondotstarany other thoughts on this?16:22
cznewti think this is aggreed16:22
jasondotstarif not, we'll move on.16:22
jasondotstarcznewt: sounds good.16:23
jasondotstar#topic Today's Agenda16:23
*** openstack changes topic to "Today's Agenda (Meeting topic: #openstack-salt)"16:23
jasondotstarok, first: setup core/release teams:16:23
*** wwriverrat has joined #openstack-meeting16:23
jasondotstarcznewt, genuing, pupapaik, Jay_Clark, majklkcz anyone else?16:24
cznewtgenunix16:24
jasondotstar+116:24
genunix+116:24
cznewtnow nothing block the team creation?16:24
*** ilyashakhat has quit IRC16:24
jasondotstarthat was my next question16:25
jasondotstarwe need to go back to -infra and make sure you are added, cznewt16:25
jasondotstarif we haven't already16:25
*** belmoreira has quit IRC16:25
cznewtyes, I'll after the meeting16:25
jasondotstargood deal.16:26
*** ilyashakhat has joined #openstack-meeting16:26
jasondotstarnext: development guideline16:26
jasondotstarproposal - repositories imported under github.com/openstack16:26
cznewtthe repositories are under the openstack  nameespace now16:26
*** ilyashakhat has quit IRC16:27
jasondotstarcznewt: ok. how do we keep the github project(s) and the openstack project(s) in sync?16:27
*** shihanzhang has quit IRC16:27
*** Leo_ has joined #openstack-meeting16:27
cznewtand in the openstack git, is the infromation here correct?16:27
cznewt#link http://openstack-salt.tcpcloud.eu/develop/extending-contribute.html16:27
*** Leom has joined #openstack-meeting16:28
*** shihanzhang has joined #openstack-meeting16:28
*** bdrich_ has joined #openstack-meeting16:28
cznewtgithub - the tcpcloud namespace - the repos will be removed16:28
genunixjasondotstar: our repos in tcpcloud namespace will be removed so there's no need for sync16:28
*** barrett has quit IRC16:28
jasondotstar+116:28
genunixthe question is about building packages16:28
cznewtas they are being added to the openstack16:28
*** jlanoux has joined #openstack-meeting16:29
genunixit's currently done in our Jenkins and uploaded to our PPA16:29
*** barrett1 has joined #openstack-meeting16:29
genunixbut I would like to do this in openstack way16:29
jasondotstarthat has to be moved over16:29
jasondotstarright16:29
genunixso these packages may reach ubuntu cloud and debian once16:29
genunixbut I don't know how it works for openstack packages so this is probably action item to me16:29
*** mdenny has quit IRC16:29
*** fesp has joined #openstack-meeting16:30
genunixalso maybe do some cleanup on packaging, specify dependencies for some formulas, etc.16:30
*** ddecapit has joined #openstack-meeting16:30
jasondotstar#action genunix to research how to openstack packaging works16:30
*** wwriverrat has quit IRC16:30
*** ddecapit is now known as DuaneDeC716:30
*** spotz_zzz is now known as spotz16:31
cznewtThe integration setup of the launchpad needs to be checkedd16:31
*** Leo_ has quit IRC16:31
*** garthb has joined #openstack-meeting16:32
*** wwriverrat has joined #openstack-meeting16:32
*** edtubill has quit IRC16:32
jasondotstaragreed16:32
cznewtI think the openstack access is not well configured there16:32
jasondotstarI can take a look at that one16:33
jasondotstar#action jasondotstar to look at the integration of launchpad with our repos16:33
cznewtjasondotstar: can we go over the complete process of contributing together? I'd like to evangelise further, but i want to certain that i do it right16:33
jasondotstarof course16:34
jasondotstarthe contributor guidelines16:34
jasondotstarlet's take a quick at that16:34
jasondotstarsee if there is any feedback16:35
jasondotstar#link http://openstack-salt.tcpcloud.eu/develop/extending-contribute.html16:35
*** zhhuabj has quit IRC16:35
jasondotstar(again)16:35
*** adiantum has quit IRC16:36
*** dmacpher is now known as dmacpher-afk16:36
*** agireud has quit IRC16:36
*** ilyashakhat has joined #openstack-meeting16:36
*** kebray has quit IRC16:36
*** iyamahat has joined #openstack-meeting16:36
cznewtyes, I'll do it after the meeting to see how it works from both sides16:36
*** DuaneDeC7 has quit IRC16:37
cznewtI'd like to16:37
jasondotstar+116:37
*** agireud has joined #openstack-meeting16:37
*** ilyashakhat has quit IRC16:38
cznewtget the heat stack for development of salt stack tested16:38
cznewtand ready16:38
*** ilyashakhat has joined #openstack-meeting16:38
jasondotstar+116:38
cznewtwe provide labs for openstack-salt creating to the customers so we can do it to the community as well16:38
cznewtjasondotstar: there'a account for you ready already and it will be open for openstack-salt team members16:39
jasondotstarnice16:39
cznewtyes, the full scale HA deployment lab takes about 20 cores and 60gb of ram16:40
cznewtit's out of scope of vagrant testing :)16:40
jasondotstarhehehe16:40
jasondotstari think so16:40
jasondotstarunless you've got an entire LAB16:40
jasondotstarhowever, that might be a point to discuss16:40
jasondotstarperhaps we can get talk to -infra about a dev environment16:41
jasondotstaror have someone sponsor some resources16:41
jasondotstarso that we can fully test HA16:41
cznewtyes, this is for further discussion16:41
cznewtit would be nice to get more sponsors16:42
*** esker has quit IRC16:42
cznewt+116:42
*** harshs has joined #openstack-meeting16:42
jasondotstar#agreed Further research is needed on how we acquire resources for HA testing16:42
*** fesp has quit IRC16:42
jasondotstarI can ask around16:42
jasondotstarmy company *might* have something we can leverage, but don't quote me on that :-)16:43
jasondotstarI've known rackspace to sponsor some lab space IIRC16:43
cznewtSuper, the openstack environments are preferrable16:43
jasondotstar+116:43
*** ianw has quit IRC16:43
*** intr1nsic has quit IRC16:44
jasondotstar#action jasondotstar to look into dev environment sponsorship16:44
jasondotstarother items on collaborative efforts.....?16:45
cznewt#action newt test the aio/ha openstack-salt heat setup16:45
cznewtjust the salt community involvement16:45
jasondotstar+116:45
cznewtit has been already put into action, I think16:45
jasondotstargood deal16:45
*** jdob has quit IRC16:45
*** wwriverrat has left #openstack-meeting16:45
jasondotstarwe touched on this, but are we good on building formula packages under openstack?16:46
jasondotstarRHEL needs love16:46
jasondotstaryes?16:46
cznewtwe are good for debian, and the packages are not very complicated, just copying around16:47
*** gibi_ is now known as gibi16:47
*** dims_ has joined #openstack-meeting16:47
cznewtso i think we can provide rhel packages as well in short time16:47
jasondotstarcool.16:48
*** paul-carlton1 has quit IRC16:48
*** evgenyf has quit IRC16:48
*** harshs has quit IRC16:48
jasondotstaroh.... the contributor license16:48
*** Swami has joined #openstack-meeting16:49
jasondotstarApache License, Version 2.016:49
*** vahidh has quit IRC16:49
*** dims has quit IRC16:49
jasondotstaris that the license we're using?16:49
jasondotstarare there comments about that?16:50
*** DuaneDeC7 has joined #openstack-meeting16:50
cznewtthe formulas use the apache2 all of them16:50
*** rderose has joined #openstack-meeting16:50
cznewtand what about the contributor's license, which one applies16:50
jasondotstar#link https://review.openstack.org/static/cla.html16:51
cznewtyes, thank you16:52
jasondotstari think mainly this means that the code you contribute is originated by you16:52
*** armax has joined #openstack-meeting16:52
*** su_zhang has quit IRC16:52
jasondotstaronce you offer it16:52
jasondotstarit goes under the apache license at that point16:52
jasondotstarIIUC16:52
jasondotstari can't take closed-source code from IBM, and offer it as a patch16:53
jasondotstarfor example.16:53
*** bnemec has quit IRC16:53
cznewtyes i get it even better now :)16:53
jasondotstarso both kinda come into play16:53
*** absubram has quit IRC16:55
*** reed_ has joined #openstack-meeting16:55
jasondotstar"I offer MY (and I mean MY code - as stated in the Contributor license) code to this project, which is then protected by the Apache License"16:55
*** clenimar has quit IRC16:55
*** e0ne has quit IRC16:55
jasondotstarsomething to that affect16:55
jasondotstarok we've got 5 mins left16:56
jasondotstar#topic Open Discussion16:56
*** openstack changes topic to "Open Discussion (Meeting topic: #openstack-salt)"16:56
*** jdurgin1 has joined #openstack-meeting16:56
*** mbound has quit IRC16:56
jasondotstarno additional comments from me. we've got a few things to look int.16:57
cznewtwell i'm out of topics, I'll be here to help you with the install16:57
jasondotstars/int./into.16:57
*** achanda has joined #openstack-meeting16:57
*** matrohon has quit IRC16:57
cznewtwhich ones?16:57
*** wanghao_ has quit IRC16:57
*** scheuran has quit IRC16:57
jasondotstarjust the action items16:57
jasondotstarim saying nothing else besides what we've already talked about :-)16:57
jasondotstaroh... summit16:58
jasondotstaryou guys going?16:58
cznewtyes, most probably16:58
jasondotstaryep, I'll be there16:58
*** rlrossit has joined #openstack-meeting16:58
jasondotstarwe can talk more about that later16:58
*** speller has joined #openstack-meeting16:59
cznewtyes, looking forward to summit :)16:59
jasondotstarcool. if nothing else, i think we can close16:59
cznewtlet's continue on #openstack-salt16:59
jasondotstarthx guys16:59
*** baoli has quit IRC16:59
cznewtthx all16:59
jasondotstaruntil next week16:59
jasondotstar#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Feb  2 17:00:00 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/_openstack_salt/2016/_openstack_salt.2016-02-02-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/_openstack_salt/2016/_openstack_salt.2016-02-02-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/_openstack_salt/2016/_openstack_salt.2016-02-02-16.01.log.html17:00
*** vivekd has quit IRC17:00
*** baoli has joined #openstack-meeting17:00
*** rlrossit_ has joined #openstack-meeting17:00
gibi#startmeeting nova notification17:00
openstackMeeting started Tue Feb  2 17:00:48 2016 UTC and is due to finish in 60 minutes.  The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: nova notification)"17:00
openstackThe meeting name has been set to 'nova_notification'17:00
*** 6JTAAC8GZ has quit IRC17:01
gibihi everyone!17:01
rlrossit_hi gibi!17:01
*** drankis has quit IRC17:01
*** haomaiwa_ has joined #openstack-meeting17:01
gibirlrossit_: hi! I'm happy that you found the new place and time as I screwed up the mail on the ML twice. :)17:01
*** vivekd has joined #openstack-meeting17:02
*** kebray has joined #openstack-meeting17:02
*** xingchao has quit IRC17:02
gibiit seems just two of us today17:03
gibi#topic open reviews17:03
*** openstack changes topic to "open reviews (Meeting topic: nova notification)"17:03
gibiactually we have merged everything that was open!17:03
rlrossit_woo17:03
gibi:)17:03
spellerhi there :)17:03
gibispeller: hi!17:03
*** rlrossit has quit IRC17:03
gibi#topic midcycle summary17:04
*** openstack changes topic to "midcycle summary (Meeting topic: nova notification)"17:04
*** ilyashakhat has quit IRC17:04
gibiso last week we had a fruitfull midcycle in the sunny Bristol17:04
gibimost of the info are collected on https://etherpad.openstack.org/p/mitaka-nova-midcycle17:04
gibithe notification part is starts at L4317:05
*** timcline has quit IRC17:05
gibiI did updated the our todo list etherpad with the outcome https://etherpad.openstack.org/p/nova-versioned-notifications17:05
*** achanda has quit IRC17:06
gibiI think the biggest result was that we agreed that no new legacy notification is allowed in nova any more17:06
rlrossit_+117:06
*** kjorgensen has joined #openstack-meeting17:06
gibiwhich is now documented in the code-review.rst17:07
gibione of our task for Mitaka-3 is related to this17:07
gibiwe have to find a way to automatically detect if somebody proposing a patch with a new legacy notification17:07
rlrossit_hacking maybe?17:08
rlrossit_but that seems hard17:08
gibihacking and grep is hard as the notifier coming from rpc.get_notifier is passed along in multiple calls and also somethime the get_notifier is wrapped in a partial17:09
gibianother possibility is monkey patching get_notifier in the base test case17:09
gibibut some test mocks get_notifier itself17:09
gibiand it could only catch new notifications if there is a test for it as well17:10
*** mbound has joined #openstack-meeting17:10
gibianother way is configure tempest to use the Log driver for notifications and post process logs after tempest17:10
gibibut that is also problematic17:10
gibihttps://etherpad.openstack.org/p/nova-versioned-notifications L51 contains my understanding17:11
rlrossit_I would like this to get caught in UT, not tempest17:11
gibirlrossit_: agree17:11
gibiif we mix the mockey patch and the hecking rule solution then we might catch most of the new notifications17:12
*** samueldmq has joined #openstack-meeting17:12
gibisome would be catched by the hacking rule some by the mockey patc17:12
gibih17:12
gibiand I think we cannot aim for catching everything17:13
rlrossit_yeah like if they patch get_notifier, use hacking, otherwise trust monkey patch?17:13
rlrossit_+1. we can't catch everything, or else we would put cores out of their job :)17:13
gibirlrossit_: something like that, yes17:13
*** safchain has quit IRC17:13
gibiahh we need cores for +2 :)17:13
*** mlavalle has left #openstack-meeting17:14
*** salv-orlando has quit IRC17:14
gibiI think I will looking into this hacking rule + mockey patch tomorrow and put up a patch for it17:15
*** tellesnobrega_af is now known as tellesnobrega17:15
rlrossit_you may want to separate them as 2 patches, though not sure how dependent they'll be17:15
*** sdake has quit IRC17:15
*** paul-carlton1 has joined #openstack-meeting17:15
rlrossit_wait... won't you need to blacklist existing legacy notifications until we get them changed over?17:16
*** drankis has joined #openstack-meeting17:16
*** baoli has quit IRC17:16
*** Daisy has quit IRC17:16
*** tshtilma has joined #openstack-meeting17:17
gibirlrossit_: I can split it to two patches sure. I think they are not dependent on each other17:17
gibirlrossit_: if you have free time we can even split the work :)17:17
rlrossit_I probably am too busy for the next week or so :(17:17
*** mdenny has joined #openstack-meeting17:17
rlrossit_IBM internal whatnot17:17
gibirlrossit_: no worries I will dig in :)17:17
*** zul has joined #openstack-meeting17:18
*** bdrich_ has quit IRC17:18
*** spotz is now known as spotz_zzz17:19
gibirlrossit_: regarding the blacklist, yes we need one until we transform the existing legacy notifications. This list will serve us as a guide what we need to do17:19
*** iyamahat has quit IRC17:19
gibirlrossit_: I might be generate that list into the notification devref as a 'list of legacy notifications'17:19
*** henar has joined #openstack-meeting17:20
*** henar has left #openstack-meeting17:20
*** vahidh has joined #openstack-meeting17:20
*** paul-carlton1 has quit IRC17:21
gibianyhow I see the way forward with this which is good :)17:22
*** baoli has joined #openstack-meeting17:22
gibianother task possible for Mitaka-3 is moving the notification_format config option from nova.rpc into the config subtree17:23
gibibut that is an easy piece17:23
*** alop has joined #openstack-meeting17:24
*** reed_ has quit IRC17:24
gibifor Newton I will put up a new spec to transform instance.update and api_17:24
gibi... and api_fault17:25
*** reed_ has joined #openstack-meeting17:25
*** yamahata has joined #openstack-meeting17:25
gibiwe agreed that no spec is needed for the transformation of the other legacy notifications so that will be an ongoing work after these two17:25
rlrossit_So it will be like mitaka-objects, where it's just a big umbrella of changing?17:26
*** salv-orlando has joined #openstack-meeting17:26
gibirlrossit_: yes, I imagine so17:26
*** Daisy has joined #openstack-meeting17:26
*** maishsk has joined #openstack-meeting17:27
*** ygbo has quit IRC17:27
gibiwe also agreed that we will provide a jsonschema for the notification payload, that will be a separate spec for Newton17:28
*** MaxPC1 has quit IRC17:28
gibiI mean schema per payload type17:28
*** MaxPC has joined #openstack-meeting17:28
gibiI think that was all from the midcycle17:30
*** ljxiash has joined #openstack-meeting17:30
*** Daisy has quit IRC17:31
*** reed_ has quit IRC17:31
gibi#topic open discussion17:31
*** openstack changes topic to "open discussion (Meeting topic: nova notification)"17:31
gibianything else to discuss?17:32
*** bdrich_ has joined #openstack-meeting17:32
rlrossit_nope17:32
*** jdurgin1 has quit IRC17:33
gibithank thanks for joining. next meeting will be held two weeks from now according to the new schedule17:33
*** maishsk has quit IRC17:34
*** phil__ has quit IRC17:34
gibi#endmeeting17:34
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:34
openstackMeeting ended Tue Feb  2 17:34:31 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_notification/2016/nova_notification.2016-02-02-17.00.html17:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_notification/2016/nova_notification.2016-02-02-17.00.txt17:34
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_notification/2016/nova_notification.2016-02-02-17.00.log.html17:34
*** rlrossit_ has left #openstack-meeting17:34
*** Apoorva has joined #openstack-meeting17:35
*** leeantho has joined #openstack-meeting17:36
*** Daisy has joined #openstack-meeting17:37
*** SridharG has joined #openstack-meeting17:37
*** dmorita has joined #openstack-meeting17:37
*** paul-carlton1 has joined #openstack-meeting17:38
*** xinwu has joined #openstack-meeting17:39
*** dmorita has quit IRC17:40
*** dmorita has joined #openstack-meeting17:40
*** Daisy has quit IRC17:41
*** leeantho has quit IRC17:41
*** unicell has quit IRC17:41
*** mbound has quit IRC17:42
*** jichen has joined #openstack-meeting17:44
*** ljxiash has quit IRC17:44
*** sanghai has quit IRC17:45
*** SumitNaiksatam has quit IRC17:46
*** keedya has left #openstack-meeting17:46
*** balajiiyer has quit IRC17:46
*** cdub has quit IRC17:47
*** keedya has joined #openstack-meeting17:47
*** keedya has left #openstack-meeting17:47
*** sdake has joined #openstack-meeting17:48
*** sdake has quit IRC17:50
*** salv-orl_ has joined #openstack-meeting17:50
*** rderose has quit IRC17:50
*** keedya has joined #openstack-meeting17:51
*** keedya has left #openstack-meeting17:51
*** marekd has joined #openstack-meeting17:51
*** ivar-lazzaro has joined #openstack-meeting17:52
*** tsymanczyk has joined #openstack-meeting17:53
*** rderose has joined #openstack-meeting17:53
*** salv-orlando has quit IRC17:54
*** edtubill has joined #openstack-meeting17:55
*** zul has quit IRC17:56
*** balajiiyer has joined #openstack-meeting17:57
*** iyamahat has joined #openstack-meeting17:59
*** tidwellr has left #openstack-meeting17:59
stevemarcourtesy ping: ajayaa, amakarov, ayoung, breton, browne, davechen, david8hu, dolphm, dstanek, ericksonsantos, geoffarnold, gyee, henrynash, hogepodge, htruta, jamielennox, joesavak, lbragstad, lhcheng, marekd, morganfainberg, nkinder, raildo, rodrigods, roxanaghe, samueldmq, shaleh, stevemar, tsymanczyk, topol, vivekd, wanghong, claudiub, rderose, samleon, xek, MaxPC, tjcocozz17:59
lbragstadstevemar o/17:59
dolphm\o/17:59
htruta\o17:59
raildoo/17:59
tjcocozzo/17:59
samueldmq\o/18:00
amakarovo/18:00
ayoungstevemar, ping pong ping pong18:00
* notmorgan doesn't claim to be here18:00
stevemaro/18:00
tsymanczyk\o18:00
*** mhickey_ has quit IRC18:00
dstanekhi18:00
ayoungnotmorgan claims to be not here18:00
*** keedya has joined #openstack-meeting18:00
rderoseyo18:00
keedyahello18:00
rodrigodso/18:00
*** yamahata has quit IRC18:00
bknudsonhi18:00
keedya\o/18:00
*** roxanaghe_ has joined #openstack-meeting18:00
*** haomaiwa_ has quit IRC18:01
MaxPCo/18:01
stevemar#startmeeting keystone18:01
openstackMeeting started Tue Feb  2 18:01:20 2016 UTC and is due to finish in 60 minutes.  The chair is stevemar. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
*** merooney has joined #openstack-meeting18:01
stevemar#link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting#Main_Agenda18:01
*** haomaiwang has joined #openstack-meeting18:01
stevemarlight-ish agenda today18:01
stevemar#topic DocImpact18:01
*** openstack changes topic to "DocImpact (Meeting topic: keystone)"18:01
marekdo/18:02
*** lhcheng has joined #openstack-meeting18:02
stevemarthere's going to be a change in the way docImpact works now18:02
notmorganoh good i wont ever use it now >.>18:02
notmorganoh wait...18:02
stevemarwe'll be opening bugs against the keystone project, not the docs team18:02
notmorganj/k18:02
lbragstad\o/18:02
*** rossella_s has quit IRC18:02
ayoungwill we be responsible for the docs repo?18:02
notmorganstevemar: does it auto tag the bug as "Doc"?18:03
bknudsonare we supposed to clean it up and reassign it to docs?18:03
*** henrynash has joined #openstack-meeting18:03
notmorganstevemar: because if it just randomly create doc bugs, i think they'll get lost-ish18:03
henrynash(hi)18:03
*** sigmavirus24 is now known as sigmavirus24_awa18:03
stevemari figured there were going to be a bunch of questions, i dont have the answers, but i can forward to lana18:03
notmorganbknudson: no we're supposed to do the documentation i think or verify... it18:03
notmorganbut to be fair, i don't see a benefit for a docimpact bug.18:03
notmorgannever did see the benefit18:03
bknudsonyes, who needs accurate docs.18:04
stevemarnotmorgan: bknudson i think the plan is have them auto tagged with 'docs'18:04
stevemaror doc18:04
*** rossella_s has joined #openstack-meeting18:04
ayoungbknudson, just buy the O'Reilly book18:04
notmorganbknudson: opening a random bug that says "hey this is a docimpact" vs before merging require the docs to be written18:04
*** dandruta has quit IRC18:04
stevemarnotmorgan: which is what we've been doing18:04
*** barrett1 has quit IRC18:04
bknudsonI could write my own orieilly book to cash in on the lack of community involvement in docs.18:04
notmorganbknudson: if the bug was in a team not keystone, it made sense, but this seems like it's pointless.18:05
*** kencjohnston has quit IRC18:05
*** barrett1 has joined #openstack-meeting18:05
notmorgananyway, just my $0.02, if we already enforce docs written, the DocImpact flag is fine... but i wouldn't wnat it to open a bug18:05
stevemarnotmorgan: plus, we've been enforcing reno now, which is nice18:05
notmorgani can see the flag as useful to look at the log and see what was doc impacting. but anyway... i've voiced my opinion18:06
*** timcline has joined #openstack-meeting18:06
ayoungnotmorgan, so, I could see there being a benefit if the workflow was something like this:18:06
*** neiljerram has quit IRC18:06
ayoung1. Docimpact, assign bug to origianly developer18:06
*** breton has joined #openstack-meeting18:06
*** rfolco has quit IRC18:07
ayoung2.  Dev fills in the necessary info into the bug and assignes to the doc team to integrate in the right place18:07
stevemari think the only question is the identity upgrade and install bits that are owned by the docs team18:07
notmorganayoung: i don't think anything goes to the doc team here.18:07
ayounglets try it for a while and see what happens.  I've never built the docs myself.18:07
topolo/18:07
ayoungmaybe we'll like it.  We seem to enjoy writing anyway18:07
bknudsonI think at the last summit (or maybe last 2 summits) the docs team was saying they'd like to move the docs to the dev teams.18:07
notmorganbknudson: right.18:07
*** johnbelamaric has left #openstack-meeting18:08
bknudsonBut I haven't heard that that's happened18:08
notmorganbknudson: hence the reason i don't see a benefit for a bug to be opened. but *shrug*18:08
notmorganbknudson: and if the bug is opened and the docs team still owns it all, i don't see a win for us to have bugs against keystone.18:08
stevemarnotmorgan: i think it's just a way to migrate for folks that were using the tag in the first place18:08
samueldmqbknudson: what docs ? api-ref ?18:08
notmorganstevemar: anyway my $0.02 of input18:09
bknudsonsamueldmq: all the docs -- admin guide, user guide, config guide, install guide, ... whatever else we have18:09
stevemaryep18:09
notmorganonce it's all over to us i'd like to revisit disabling the "auto open a bug against keystone".18:09
samueldmqbknudson: got it18:09
notmorganand just make sure we have docs when we merge the stuff.18:09
henrynash(has always thought we should be writing our docs anyway, but hey….)18:09
ayoungWhere are our docs anyway?18:09
*** yamahata has joined #openstack-meeting18:09
notmorganayoung: almost 100% in our repo atm18:10
stevemarhenrynash: your wish is now coming true18:10
notmorganjust not the admin/upgrade guides18:10
ayoungnotmorgan, openstack/keystone/docs18:10
lbragstadfwiw the thing i like about have docs owned by a separate team is that it ends up being more consistent across projects18:10
notmorganayoung: yeah.18:10
bknudsonhttp://docs.openstack.org/18:10
henrynash(oh yes, I remember the saying now: be careful for what you wish for….)18:10
ayoungrepo?18:10
notmorganayoung: in the main keystone repo.18:10
*** jtomasek__ has quit IRC18:10
notmorganand specs repo for the cannonical specification [as you know]18:10
*** timcline has quit IRC18:11
henrynashlbragstad: I think that’s a good point…I’ve also though that sperate team should craete the style, order etc….but not the content18:11
stevemarayoung: tox -e docs!18:11
notmorganlbragstad: i think we'll see a drastic reduction in doc consistency and quality, but i know the doc team doesn't scale18:11
*** anteaya has quit IRC18:11
ayounghttp://git.openstack.org/cgit/openstack/openstack-manuals/18:11
notmorganayoung: that is all being shuffled around afaik18:11
ayounghttp://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/keystone.rst18:11
notmorganayoung: so, let steve ask lana18:11
*** samleon has joined #openstack-meeting18:11
ayoung++18:11
lbragstadnotmorgan agreed - but from an u-x perspective, it's nice to see the consistency when referencing docs from different projects18:11
ayoungput a follow up item for next weeks meeting...next topic?18:12
stevemaryep18:12
*** anteaya has joined #openstack-meeting18:12
stevemar#topic ISO27001 Compliance18:12
*** openstack changes topic to "ISO27001 Compliance (Meeting topic: keystone)"18:12
stevemarayoung: g'head18:12
*** iyamahat has quit IRC18:12
bknudsonI can't afford access to ISO standards18:12
*** keedya has left #openstack-meeting18:12
ayoungOK...so,  do we need to comply ?18:13
notmorganbknudson: lol18:13
notmorganayoung: long term, yes18:13
ayoungAnd is there any way to avoid it18:13
dstanekbknudson: me either18:13
ayoungI think I agree18:13
notmorganayoung: but this will follow into the HIPPA/PCI-DSS type convos18:13
ayoungI think we need to have a set of requirements for the SQL backend, because you cannot deploy without them18:13
*** intr1nsic has joined #openstack-meeting18:13
notmorganwhich i'm headed to Seattle to start collecting info on thursday.18:13
*** Swami has quit IRC18:14
ayoungthere will always be service users in the SQL backend, and I think a best p[ractice there is to try and not do password for those users18:14
notmorganit's all similar vein and requires concerted effort to move that way/document/etc18:14
bknudsonwhy can't service users go in the LDAP backend?18:14
dstaneknotmorgan: PCI stuff Thursday?18:14
ayoungthe use case, though, that I think clinches it is Public Cloud Customers18:14
ayoungbknudson, for some cases, you don't have write access18:14
*** gibi has quit IRC18:14
notmorgandstanek: going to talk w/ bluebox on what they're doing18:14
ayoungbknudson, but they could go in a deployment specific LDAP18:14
notmorgandstanek: and what they've had to change / are changing to meet the requirements18:14
dstaneknotmorgan: nice, i can't wait to hear18:15
*** rfolco has joined #openstack-meeting18:15
ayoungso, could we do a deployment with all users in LDAP, only if we don't care about adding new customers, I think18:15
*** ianw has joined #openstack-meeting18:15
*** gibi has joined #openstack-meeting18:15
ayoungso,  let me throw this in the Lap of the RAX folks:  how do you need this to look?18:15
dolphmbknudson: many enterprises are not willing / able to let you touch their LDAP server just to deploy openstack18:15
*** pvaneck has joined #openstack-meeting18:16
ayoungMy assumption has been that provisioning on new customers is done through a systemn outside OPenStack.18:16
ayoungdolphm, so, two distinct things.  You are right about Corporate LDAP, but if a place need compliance today, they could run a separate LDAP server (with compliance guaranteees) just for service users18:16
*** unicell has joined #openstack-meeting18:16
ayoungYOu could, in theory, run OpenStack with no users in SQL at all.18:17
bknudsonlazy customers are king, I guess.18:17
ayoungbut that avoids a real use case:  how do  I add customers to my cloud?18:17
*** merooney has quit IRC18:17
*** harshs has joined #openstack-meeting18:17
bknudsonif somebody signs up to do the work then let's go ahead.18:17
*** SumitNaiksatam has joined #openstack-meeting18:17
ayoungbknudson, well, I am more asking from a "it was proposed and Adam kneecapped it.  Was Adam right?"18:17
ayoungperspective18:18
bknudsonI think you are right, doesn't mean we can't support it now.18:18
ayoungwhat I am saying is, I think I am not longer opposing compliance in the SQL backend, provided we can show it is required....18:18
bknudsonjust for fun18:18
*** vijendar has quit IRC18:18
ayounggyee is not here, this was his issue.  Lets move on.18:19
bknudsonI also agree. We tried pushing onto ldap / saml but that didn't work.18:19
*** achanda has joined #openstack-meeting18:19
henrynashayoung: ++ agreed, I think we look at the requirements…if it is needed to hel to continue accelerating momentum of OpenStack, we shoudl do it…..it is perspiration, not inspiration to do this18:19
*** adiantum has joined #openstack-meeting18:19
bknudsonwho's signing up to do the work?18:19
stevemaradding users to a sql backend, in the same of a public cloud, doesn't seem outrageous18:19
dstanekwhat has to be done to support it?18:19
*** fzdarsky is now known as fzdarsky|afk18:19
ayoungstevemar, the thing is, the user abstraction in Keystone does not seem to be sufficient for an actual user database18:20
bknudsonsince nobody can afford the standard it's tough to tell.18:20
ayoungThere is no contact info ,etc18:20
*** su_zhang has joined #openstack-meeting18:20
dolphmdstanek: ++ is there a spec that outlines the impact on / proposed changes to keystone?18:20
ayoungbknudson, forget the actual standard, I'm also referring to the request for passwrod rotation etc18:20
marekddolphm: true, at cern our ldap is a single source of truth about users, shared accross many services. our cloud is just one of many.18:21
*** dimtruck is now known as zz_dimtruck18:21
dstaneki like the SQL backend and don't want it to become a forgotten step child18:21
ayoungmarekd, and you do not add new users via Horizon18:21
*** yamahata has quit IRC18:22
*** su_zhang has quit IRC18:22
marekdayoung: not really18:22
stevemardstanek: a lot of people like the sql backend, and i think would just like to see more capability in it18:22
*** su_zhang has joined #openstack-meeting18:22
dstanekayoung: most of the password "features" are trivial to implement and maintain18:22
ayoungdstanek, So I think that it has the potnetial to be "used because it is there" which is not a great option18:22
notmorganso i have a real case I was asked about18:22
notmorgandomain admin in SSO / IDP18:22
dstaneki wrote many of them in 2014 :(18:22
notmorganeach user for the domain after that is SQL based18:22
marekdayoung: users will have projects created given they are in a specific e-group but it requires manual interaction (somebody validating request and running the script)18:22
ayoungdstanek, do you guys need that?18:23
* lbragstad thanks dstanek 18:23
stevemardstanek: restore patch18:23
bknudsonis this for M? We could probably get it done.18:23
bknudsonif dstanek has the code all ready18:23
dstanekstevemar: sure. was planning on doing that on to of rderose's work18:23
notmorgandstanek: how does this play witht he shadowusers18:23
*** clenimar has joined #openstack-meeting18:24
stevemarnotmorgan: looks like dstanek has already thought about that :)18:24
dstanekbknudson: lots of rut, but should not be terrible to revive18:24
notmorganhehe18:24
ayoungI'm less worried about the complexity of the Password code than giving the wrong impression.  I think a lot of people use SQL because they think they are supposed to, and then have this silo of identity.  My real question is whether there is a must have use case for SQL Identity, and, if so, what are the requiremetns18:24
lbragstaddstanek https://review.openstack.org/#/q/status:abandoned+project:openstack/keystone+branch:master+topic:bp/password-rotation18:24
henrynashayoung: I’m not so sure they use it because they think they are supposed to….18:25
stevemarayoung: if we run a public cloud, and have customers that aren't huge enterprises, how do they sign up?18:25
dstaneklbragstad: there are a few other patches too that i showed Ron at the Midcycle18:25
bknudsonIdentities as a Service18:25
ayoungstevemar, and that is the $1000000 question18:25
henrynashayoung: if they have a corpaorate directory already, they’ll use that18:25
ayoungbecause you can't bill from Horizon18:25
*** baoli has quit IRC18:25
lbragstaddstanek gotcha - those seemed to be the ones with a common topic18:25
henrynashayoung: if they don’t, then they’ll use SQL18:25
ayounghenrynash, and yes to that, too18:25
dstanekpublic cloud seems to be the use case18:26
henrynashayoung: setting up LDAP is hard compared to our SQL backend18:26
*** vijendar has joined #openstack-meeting18:26
*** xinwu has quit IRC18:26
stevemarayoung: they don't want to federate, and they dont have an ldap handy... sql is the only option18:26
*** tellesnobrega is now known as tellesnobrega_af18:26
*** timcline has joined #openstack-meeting18:26
henrynashayoung: there are a lot more sql admins than there are LDAP admins in enterproses18:27
bknudsonthere will be bugs and they'll probably be security vulnerabilities, but whatever.18:27
ayoungstevemar, we show how to do LDAP with devstack.  THat is not a real barrier to acceptance18:27
notmorganand SQL is already needed for most of openstack18:27
*** tellesnobrega_af is now known as tellesnobrega18:27
*** vijendar1 has joined #openstack-meeting18:27
notmorganand keystone18:27
notmorganso, it's a tech they have the resources to maintain internally18:27
notmorganand consume18:27
ayounghenrynash, but the SQL admins know nothing about passwords or compliance ,either\18:27
notmorganadding LDAP or SSO is often harder.18:27
bknudsonseems like any org already has a way to do identities18:27
bknudsoncan I just create users with POST /v3/users on rackspace?18:27
*** toscalix_ has joined #openstack-meeting18:27
notmorganbut public cloud tends to be the main driving use-case18:27
dolphmbknudson: yes18:28
henrynashayoung: no….but they are comforatble running and maintaining an SQL server…and backing it up, restoring it when disaster strikes etc.18:28
*** salv-orl_ has quit IRC18:28
ayoungMy position thus far has been SQL for Proof of concept, LDAP for enterprise deployments18:28
*** paul-carlton1 has quit IRC18:28
stevemarkeystone now has three difficulty levels, easy:sql, medium:ldap and hard:sso18:28
*** keedya has joined #openstack-meeting18:28
ayoungnow, with Writable LDAP gone, we have no story for secure creation of new identities18:28
notmorganstevemar: med-hard, multi-ldap with SQL18:28
*** salv-orlando has joined #openstack-meeting18:28
stevemarhehe18:28
henrynashnotmorgan: :-)18:28
stevemarayoung: i think public cloud has a use case here18:29
*** vivekd has quit IRC18:29
ayoungstevemar, I suspect that it is the case, but I also suspect that, if you push at it, they are really using a more complex customer management system18:29
*** speller has quit IRC18:29
notmorganthis is mostly a public cloud use case... or an org that uses cloud-local users except for domain admin18:29
*** merooney has joined #openstack-meeting18:29
*** gokrokve has quit IRC18:29
notmorganwhere domain-admin is locked down to things like LDAP or SSO18:29
dolphmand isolated private clouds18:29
stevemarayoung: like a different ldap?18:29
samueldmqhenrynash: this is basically what domain-specific backends support in a context of public cloud18:30
ayoungstevemar, there are CRM apps out there,  Some LDAP, some SQL18:30
ayoungsome opensource, and many, I suspect, custom18:30
samueldmqhenrynash: you can attach an LDAP server if you have one, or just share SQL if you don't have anything18:30
henrynashsamueldmq: yep18:30
ayoungCRM= Customer Relationship Management18:30
*** vijendar has quit IRC18:30
bknudsonok... does anyone think we must not improve the identity SQL backend to support stronger passwords/etc.?18:31
ayoungMy unstated assumption thus far is CRM is another WebSSO integration18:31
samueldmqhenrynash: maybe we should allow mapping SQL backends (vc only LDAP backends ) ?18:31
bknudsonIt would be nice if there was a spec saying all that was being added.18:31
ayoungbknudson, I'm still not sold18:31
notmorganbknudson: there was a spec18:31
*** angdraug has quit IRC18:31
stevemarbknudson: dolph has a spec up18:31
*** salv-orlando has quit IRC18:31
notmorganbknudson: "make SQL a full Identity manager" or some such18:31
lbragstadbknudson wouldn't that fall under the pci-dss spec?18:31
ayoungso, in that spec, please justify Why the SQL backend needs to be improved18:31
notmorganwas abanded a while ago...or something18:31
dolphm#link https://review.openstack.org/#/c/272396/2/specs/newton/pci-dss.rst18:31
samueldmqwhy not allowing mapping SQL backends (for domain-specific backends) as we do for LDAP ?18:31
ayoungbecause I need to that to turn around and explain it to my org, which is very Enterprise Focused18:31
samueldmqayoung: ^18:32
henrynashsamueldmq: I’d love to support mapping multiple SQL backends, but our current sqlamlchemy support doesn’t support it (last time I checked)18:32
*** salv-orlando has joined #openstack-meeting18:32
samueldmqhenrynash: I think that should be doable18:32
ayounghenrynash, I bet we can make that happen18:32
notmorganhenrynash: i have some improvements around that i plan on working on shortly18:32
dolphmhenrynash: true18:32
*** hurricanerix has left #openstack-meeting18:32
*** ilyashakhat has joined #openstack-meeting18:32
*** timcline has quit IRC18:32
henrynashayoung, samueldmq: me too….and I think we should try and do that18:32
ayoungOK...lets move on to policy18:32
stevemarayoung: send your org this link: https://review.openstack.org/#/c/272396/2/specs/newton/pci-dss.rst18:32
notmorganhenrynash: it's all based around moving to the new-sql-[non-old-style] facades18:32
stevemar#topic Policy and RBAC18:32
*** openstack changes topic to "Policy and RBAC (Meeting topic: keystone)"18:32
stevemarayoung is on a tear today!18:33
samueldmqhenrynash: ayoung: yes and if we get it, no need to make our sql schema more powerful right ?18:33
*** Swami has joined #openstack-meeting18:33
stevemartyping up a storm18:33
samueldmqwe provide the basics and if you want more power, make your own and map it to keystone18:33
ayoungOK...so,  jamielennox and dolphm have been moving the discussion along on a standard set of roles18:33
stevemari need to make a tally for all the times we've talked about policy in keystone meetings :)18:33
ayoungplease read the X proj spec,18:33
notmorganstevemar: every meeting always18:34
*** DuaneDeC7 has quit IRC18:34
samueldmq#link https://review.openstack.org/#/c/24562918:34
*** amitgandhinz has quit IRC18:34
samueldmqthe spec in X proj ^18:34
ayoungThanks18:34
ayoungso...I want to talk about the ramifications of this and the is_admin_project change18:34
*** ilyashakhat has quit IRC18:34
dolphmand then i threw together an example to show the impact on keystone's policy, which needs some work:18:35
dolphm#link https://review.openstack.org/#/c/274168/18:35
ayoungI tried adding an is_admin_project check to cloudsample, no problem18:35
*** ilyashakhat has joined #openstack-meeting18:35
ayoungdolphm, thanks.18:35
henrynashayoung: yep, and it works…I added tests to show that it does (test_v3_protection)18:35
*** amitgandhinz has joined #openstack-meeting18:35
ayoungand you can see that our unit tests will need tsome massaging to accept dolph's changes18:36
ayounghenrynash, so the question is, what do we do about default policy18:36
ayoungand samueldmq had an ideaa.....18:36
henrynash(drum roll)18:36
samueldmqmove scope checks to the code18:36
samueldmqand only leave role checks in the policy, i.e true RBAC there18:36
stevemar(readies the gong for the big finale)18:36
henrynashsamueldmq: ok, so can you be more explicit….18:37
samueldmqhehe18:37
*** gyee has joined #openstack-meeting18:37
ayoungSo, this will work for Keystone, because in the code we can read the keystone config18:37
*** DuaneDeC7 has joined #openstack-meeting18:37
*** sudipto_ has joined #openstack-meeting18:37
ayoungso we could check in code to see if admin_porjecr_id is even set18:37
ayoungbut this won't work for, say, Nova or Glance18:37
ayoungand for that...18:37
henrynashsamuedlmq, ayoung: I still want some more clarity on this…even for keystone18:37
samueldmqhenrynash: project_id:%(project_id)s is removed from policies, they will live in the code, when a request arrives, always check scope18:37
ayounghttps://review.openstack.org/#/c/242852/18:37
ayounghenrynash, agreed, but I think the short is that is clarification, but all the options are technically feasable18:38
samueldmqhenrynash: if you need global, use project_admin option ayoung implemented18:38
*** zz_dimtruck is now known as dimtruck18:38
ayoungso thingee just pinggedmee with a request to be at the X proj meeting abouit that18:38
henrynashsamuedlmq, ayoung: so how does a policy line like:  rule:cloud_adomin or (role:xyz and project_id:%(project_id)s) work in this new arrangemnt?18:38
*** shashank_hegde has joined #openstack-meeting18:38
ayounghenrynash, so, lets define cloud_admin first18:39
ayoungI think that is18:39
ayoungrole:admin and proejct_id=admin_project_id right?18:39
henrynashayong: ok18:39
ayoungso we would be checking a separate role based on the scope of the token?18:39
bknudsonthe last comment on the spec from dhellmann indicated he expected to have a global administrator18:39
samueldmqif we want global admin, use admin_project18:40
ayounghenrynash, yeah, global admin is kindof a firm requirement18:40
ayoung I've been told that a few times18:40
*** ivar-lazzaro has quit IRC18:40
henrynashayoung: but the scope might be different in the different clauses of the poliy line….matched to a different role18:40
ayoungright..18:40
dolphmi wish we had named it root18:40
henrynashayoung: I don’t understand how we do that in code and not lose flexibility18:40
ayounghenrynash, How about this18:40
*** haomaiwang has quit IRC18:40
stevemardolphm: then you've have people asking for a sudo command18:40
ayoungwe perform the role check only on the proejct specific18:40
samueldmqhenrynash: define something like global_roles=[], those ignore scope checks ?18:40
dolphmstevemar: fine by me18:41
notmorgandolphm: hehe18:41
ayoungwhen we get to the scope check, we can say "don't care if the role check failed"  and then make that check both is_admin+_proejct and role18:41
*** ilyashakhat has quit IRC18:41
ayoungrole:admin18:41
*** ilyashakhat has joined #openstack-meeting18:42
ayoungactually, the scope check could also accept and "is_cloud_admin" param set earlier, and we could do the whole cloud_admin check in the role layer18:42
ayoungthat probably makes more sense18:42
henrynashsamuedlmq, ayoung: and this makes it all easier?18:42
ayounghenrynash, it makes it easier to customiZE AND TO SCALE18:42
samueldmqhenrynash: I think this makes our policy more consistent with what others do (eg nova)18:42
*** AJaeger has joined #openstack-meeting18:43
*** salv-orlando has quit IRC18:43
henrynash(remains unconvinced until sees examples of v3cloudsample, not our niddy policy.json)18:43
*** novas0x2a|laptop has joined #openstack-meeting18:43
samueldmqhenrynash: and is a necessary step towards policy18:43
ayounghenrynash, we 've coded what "cloud_admin" means in the policy file, but that has to be run after the database call to fetch objects.  I'd like the role check to preceed that, and be customizable by end deployers18:43
ayoungso cloud_admin could be soemthing that we check in the role, still, and we then just need to let the scope check have enough information to process either with or without cloud admin18:44
bknudsonif you could put names in the policy file you wouldn't need to update cloud_admin.18:44
ayoungbknudson, what kind of names?18:44
ayoungusenames?18:44
ayounguser18:45
henrynashayoung, samueldmq: you guys probably have this all thought out, but I’m not sure we even agree on the nomenclature in the things you are describing18:45
*** zul has joined #openstack-meeting18:45
stevemarhenrynash: ++18:45
bknudsoncloud_admin uses admin_domain_id -- so domain name18:45
ayounghenrynash, so...I think we can duplicate the cloud_admin check in the role check and scope check and it will work.18:45
ayoungbknudson, yeah, that was henrynash '18:45
henrynashwhat’s a role check? what’s a scope check?18:45
samueldmqhenrynash: btw I thought we didn't want cloud_admins to be able to touch a given project without rescoping right ?18:45
*** salv-orlando has joined #openstack-meeting18:45
ayoungs origianl approach18:45
*** rvasilets has quit IRC18:45
ayoungand that still works18:45
*** jlanoux has quit IRC18:46
ayoungbut people have asked us not to force them to edit upon deployment18:46
samueldmqhenrynash: only the global admin which is available using the admin_project should be enough, shouldn't it ?18:46
*** absubram has joined #openstack-meeting18:46
ayoungso we need 1) backwards compatible, 2)non editing 3)secure18:46
bknudsonif you're doing more than 1 deployment then automate it.18:46
ayounghenrynash, I think for startes we duplicate the check18:46
ayoungso,  for, say,  compute:create_server18:46
samueldmqhenrynash: role check is 'role:service', scope check is 'project_id:%(project_id)s'18:47
*** adiantum has quit IRC18:47
*** numan_ has joined #openstack-meeting18:47
ayoungthe role check would be role:compute_server_write or rule:cloud_admin18:47
ayoungand the scope check would be18:47
ayoungproject_id:server.project_id or rule:cloud_admin18:47
samueldmqyes, and in nova the check is in the code18:47
ayoungif we can find a way to make that clean....18:47
lbragstad12 minute warning18:48
samueldmqdeployers can only change the role part of the check, which is in the policy18:48
*** vijendar1 has quit IRC18:48
ayoungthe scope checks are likely to move into the code, as samueldmq suggested,.  The Nova team is already moving this way18:48
stevemarthanks lbragstad18:48
samueldmqayoung: I think they've been always this way18:48
stevemargotta cut this one off in 218:48
henrynashayoung: still don’t see how this works for complex ploicy rules where more than one role check is involved and needs to be matched top a specific scope check18:48
*** sbelous_ has joined #openstack-meeting18:49
henrynashayoung: we need a real spec, with real reasons of why to do this, and explaining how we are not losing the flexibility we give deployers today18:49
samueldmqperhaps ayoung and I should work more with henrynashon this and come back next week18:49
samueldmqas we're running out of time18:49
stevemarprobably18:49
samueldmqand we still have another topic to cover18:49
stevemarlets switch gears to devstack18:49
samueldmqhenrynash: ++18:49
*** angdraug has joined #openstack-meeting18:50
stevemar#topic Devstack, identity v3, and breaking the world18:50
*** openstack changes topic to "Devstack, identity v3, and breaking the world (Meeting topic: keystone)"18:50
henrynashsamueldmq, ayoung: happy to18:50
samueldmq++18:50
stevemarso, we broke a lot of things on friday18:50
ayounghenrynash, I can write that up.  I only know realized the solution was to duplicate the admin override check at both layers, and I need to think through the ramifications18:50
stevemarsdague covered it here: http://lists.openstack.org/pipermail/openstack-dev/2016-February/085497.html18:50
bknudsonI like the responses in the email that said "tough"18:50
henrynashayoung: ok18:50
stevemarbknudson: yeah, gordc was representing :]18:50
ayoungone last thing:  please approve the Implied Role Spec18:51
ayoungOK, I'm done18:51
stevemarayoung: thanks18:51
bknudsonI guess it's difficult to write scripts that work with v2 and v3.18:51
*** bdrich_ has quit IRC18:51
bknudsonsince apparently things broke when the v3 change was reverted.18:51
*** samueldmq has quit IRC18:51
notmorganbknudson: almost all was clients [aka novaclient] and things that use tempestlib18:51
stevemarbknudson: yeah - i was wondering / hoping, folks had any bright ideas on how we could make sure this doesn't happen again18:51
*** garthb_ has joined #openstack-meeting18:52
stevemari created an etherpad to jot down ideas: https://etherpad.openstack.org/p/v3-only-devstack18:52
bknudsonif we never change anything it'll never happen again.18:52
*** garthb has quit IRC18:52
htrutadoesn't a try v3, fail and fallback to v2 make sense?18:52
dolphmso, let's require v3 every friday in the gate until people adapt?18:52
notmorganbasically we need to make changes (use http://codesearch.openstack.org/ ) to fix the issues18:52
raildothe first problem is that the tempest tests doesn't covered that behavior18:52
*** sbelous_ has quit IRC18:52
notmorganand set a date where we flip over, knowing we'll have fallout/cleanup18:52
stevemarbknudson: oh we'll keep that as a backup idea18:52
ayoungbefore that change (and after the revert) do we even produce a V3 rc file?18:52
stevemarayoung: yep18:52
stevemarwe do so now18:52
htrutaayoung: we did18:53
htrutain the reverted change18:53
bknudsondevstack creates a cloud.yaml file18:53
bknudsonwith different clouds -- one of them is v318:53
notmorganalmost everything that broke is stuff not on KSA or things that encode bad habits directly18:53
notmorganif we set a date for change over [early N?]18:53
bknudsonshould be --os-cloud devstack-admin-v318:53
notmorganknowing we will break things, and will do clenaup18:53
notmorgani think that is correct18:53
notmorganand we do our best to cleanup the last things between now and then18:54
notmorgancoordinate with sdague and mtreinish on that front.18:54
stevemarwe should try and fix all the projects now so the switch over in early N is less kablamo18:54
ayoungSo, what was the actual change made?18:54
*** changbl has quit IRC18:54
ayoungcloud.yaml is like, newish18:54
notmorganayoung: devstack defaulting to v3.18:54
notmorganthere are a number of things not using OCC/KSA18:54
stevemarayoung: https://review.openstack.org/#/c/271508/18:54
notmorgangetting everyone off ksc.session will be a big win18:55
stevemarnotmorgan: how is the migration to ksa going for all the projects?18:55
htrutanotmorgan: ++18:55
*** Sukhdev has joined #openstack-meeting18:55
notmorgangetting the clients to use OCC/KSA for constructing is the other hurdle18:55
stevemari think some folks were interested in helping out?18:55
notmorganso. nova is on KSA, neutron is on ksa,18:55
*** changbl has joined #openstack-meeting18:55
htrutastevemar: I've senn magnum, for example, and it has a bug saying that it should use ksa18:55
htrutaseen*18:55
notmorganhtruta: assume the projects can't/wont do that change18:56
*** yolanda has joined #openstack-meeting18:56
notmorganbecause largely they don't have the bandwidth or time to ramp up on the internals to know how to make the change over non-painful18:56
stevemarhtruta: yeah, the other projects may not have the knowledge to do the change, we may have to do it for them18:56
notmorganhttp://codesearch.openstack.org/?q=from%20keystoneclient%20import%20session&i=nope&files=&repos=18:56
*** banix has quit IRC18:56
notmorganthat is everything using keystoneclient.session18:56
notmorgan#link http://codesearch.openstack.org/?q=from%20keystoneclient%20import%20session&i=nope&files=&repos=18:56
*** garthb_ has quit IRC18:57
bknudsonthis is all pretty ridiculous -- why do you need to specify the version.18:57
htrutastevemar, can't we teach them too? Some blog post or stuff like that18:57
raildoironic are doing this now.... https://review.openstack.org/#/c/236982/18:57
notmorganhtruta: we've tried. if we want this, we need to do this18:57
*** pabelanger has joined #openstack-meeting18:57
notmorganourselves.18:57
stevemarhtruta: what he said ^18:57
notmorgansome projects are going to beat us to the punch18:57
*** barrett1 has quit IRC18:58
htrutanotmorgan: heh. makes sense18:58
stevemarbknudson: we can look into that18:58
notmorganso, getting us to KSA everywhere and using OCC for client construction will mean version specification will become less of an issue18:58
*** merooney has quit IRC18:58
stevemarwe're at time18:59
stevemarthanks for attending everyone18:59
notmorganand that will help aleviate problems excpet in cases like heat where the project needs v3 keystone APIs18:59
notmorganbut heat isn't a problem18:59
*** olaph has joined #openstack-meeting18:59
notmorgan(vs. just auth)18:59
stevemar#endmeeting18:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:59
lbragstado/18:59
*** barrett1 has joined #openstack-meeting18:59
openstackMeeting ended Tue Feb  2 18:59:31 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-02-02-18.01.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-02-02-18.01.txt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2016/keystone.2016-02-02-18.01.log.html18:59
*** igorbelikov has joined #openstack-meeting19:00
*** garthb_ has joined #openstack-meeting19:00
fungieverybody know what time it is?19:00
AJaegeryeah...19:00
Zara\o/19:00
Clintpeanut butter jelly?19:00
*** electrofelix has quit IRC19:00
*** bhunter71 has joined #openstack-meeting19:00
crinkleo/19:00
fungii was going for a howdy doody feel, but sure19:00
SotKo/19:01
*** prometheanfire has joined #openstack-meeting19:01
*** DuaneDeC7 has quit IRC19:01
* dougwig lurks19:01
*** merooney has joined #openstack-meeting19:01
prometheanfireluks19:01
* angdraug pretends not to be here19:01
ClintIT'S HOWDY DOODY TIME19:01
*** harshs has quit IRC19:01
clarkbohai19:01
yolandao/19:02
* persia fails to find Unicode for jumping up and down excitedly while screaming incoherently19:02
*** barrett1 has quit IRC19:02
Clintpersia: you have 58 minutes19:02
fungipleia2: jeblair: jhesketh: mordred: SergeyLukjanov: nibalizer: thomasem: dimtruck: krotscheck: annegentle: infra meeting starting now19:02
*** bbzhao has joined #openstack-meeting19:03
jeblairo/19:03
*** barrett1 has joined #openstack-meeting19:03
*** shz has joined #openstack-meeting19:03
dimtrucko/19:03
fungi#startmeeting infra19:03
openstackMeeting started Tue Feb  2 19:03:20 2016 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
cody-somerville\o19:03
*** openstack changes topic to " (Meeting topic: infra)"19:03
*** whydidyoustealmy has joined #openstack-meeting19:03
openstackThe meeting name has been set to 'infra'19:03
*** dmorita_ has joined #openstack-meeting19:03
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:03
*** numan_ has quit IRC19:03
*** weshay_xchat is now known as weshay19:03
fungi#topic Announcements19:03
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:03
ianwo/19:03
*** vahidh_ has joined #openstack-meeting19:03
*** sudipto_ has quit IRC19:04
*** DuaneDeC7 has joined #openstack-meeting19:04
*** matrohon has joined #openstack-meeting19:04
*** henrynash_ has joined #openstack-meeting19:04
olapho/19:04
*** lhcheng has left #openstack-meeting19:04
*** jjmb has joined #openstack-meeting19:04
fungihrm, i thought i'd saved a link for this, just a sec19:04
*** Swami_ has joined #openstack-meeting19:04
*** alop_ has joined #openstack-meeting19:05
*** jdurgin has quit IRC19:05
*** esker has joined #openstack-meeting19:05
fungiokay, here we go. sorry about that19:05
*** asselin_ has joined #openstack-meeting19:05
*** crinkle_ has joined #openstack-meeting19:05
fungi#info Mentors needed for GSOC19:05
*** jdurgin has joined #openstack-meeting19:05
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2016-February/085508.html19:05
*** thangp_ has joined #openstack-meeting19:05
*** xinwu has joined #openstack-meeting19:05
fungiwe've had some great infra interns/mentees in the past, and it's a great way to get in touch with potential new additions to the team, to openstack, and to free software in general19:06
fungii encourage people to give it a try, especially if they've never mentored. it's a rewarding experience19:06
*** dencaval has quit IRC19:06
fungianyway, no other announcements lined up. anything important i should mention before we move on to action items?19:06
*** crinkle has quit IRC19:06
*** timcline has joined #openstack-meeting19:07
*** crinkle_ is now known as crinkle19:07
fungi#topic Actions from last meeting19:07
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:07
fungi#link http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-01-26-19.02.html19:07
*** mrmartin has joined #openstack-meeting19:07
fungicody-somerville to draft and send HPE Cloud shutdown notice+impact to openstack-infra and openstack-dev19:07
fungi#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/085141.html19:07
*** egon_ has joined #openstack-meeting19:07
*** doffm_ has joined #openstack-meeting19:07
fungithanks cody-sommerville for sending that!19:07
cody-somervilleNo problem.19:08
fungithanks everyone who worked on maintaining the former hewlett-packard cloud for our use and abuse!19:08
anteayathanks cody-somerville19:08
fungiand thanks to the rest of the infra team for making the removal well-planned, quick and painless!19:08
*** [1]tshtilma has joined #openstack-meeting19:08
anteayayes thank you19:08
cody-somervilleWe've gotten some folks who are interested in donating resources. Is someone following up with them?19:08
anteayawho did you contact about that?19:08
fungithere was one which emerged form the infra ml moderation queue yesterday, and i was planning to reply but haven't had time yet19:08
fungis/form/from/19:08
anteayaobviously I have backscroll to read19:09
*** jdurgin has quit IRC19:09
clarkbI am currently working with osic for credentials19:09
anteayayay19:09
clarkbharlowja says they will have internal disucssion and may have something for us19:09
anteayawonderful19:09
harlowjaclarkb yup19:09
harlowjagonna go poke the SE guy here who said he wanted to chat with me about this19:09
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2016-January/003707.html19:09
fungi"safebrands"19:09
fungithough odd that the offer came from their head of marketing19:10
*** vishwanathj has joined #openstack-meeting19:10
*** leeantho has joined #openstack-meeting19:10
anteayayay safebrands19:10
jeblairwe have logos on a marketing page now :)19:10
anteayayay19:10
fungiyes we do!19:10
fungianyway, no need to eat up meeting time with this one19:10
anteayaso much progress19:10
*** itsuugo_ has joined #openstack-meeting19:10
*** lbragstad_ has joined #openstack-meeting19:11
*** bknudson_ has joined #openstack-meeting19:11
funginibalizer release gerritlib 0.5.019:11
*** htruta` has joined #openstack-meeting19:11
*** dmowrer has joined #openstack-meeting19:11
fungi#link https://pypi.python.org/pypi/gerritlib19:11
zaroo/19:11
*** pabelanger_ has joined #openstack-meeting19:11
fungithanks nibalizer for picking that up after i promised to do it and then dropped it on the floor!19:11
*** miguelgrinberg_ has joined #openstack-meeting19:11
*** coreycb` has joined #openstack-meeting19:11
*** _nonameentername has joined #openstack-meeting19:11
*** wbhuber_ has joined #openstack-meeting19:11
yolandayay gerritlib!19:11
fungii didn't see any fallout from the gerritlib release, so smooth sailing there i guess19:11
*** mrodden_ has joined #openstack-meeting19:11
fungi#topic Specs approval19:11
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:11
*** Swami has quit IRC19:12
*** henrynash has quit IRC19:12
*** dmorita has quit IRC19:12
*** alop has quit IRC19:12
*** vahidh has quit IRC19:12
*** tshtilma has quit IRC19:12
*** shihanzhang has quit IRC19:12
*** n0ano has quit IRC19:12
*** bswartz has quit IRC19:12
*** thangp has quit IRC19:12
*** jjmb1 has quit IRC19:12
*** luisfdez has quit IRC19:12
*** whenry has quit IRC19:12
*** hogepodge has quit IRC19:12
*** barra204 has quit IRC19:12
*** bzhao has quit IRC19:12
*** trozet has quit IRC19:12
*** pabelanger has quit IRC19:12
*** asselin has quit IRC19:12
*** akuznetsova has quit IRC19:12
*** kbyrne has quit IRC19:12
*** mordred has quit IRC19:12
*** bknudson has quit IRC19:12
*** mrunge has quit IRC19:12
*** htruta has quit IRC19:12
*** wbhuber has quit IRC19:12
*** itsuugo has quit IRC19:12
*** coreycb has quit IRC19:12
*** dmowrer- has quit IRC19:12
*** egon has quit IRC19:12
*** nonameentername has quit IRC19:12
*** doffm has quit IRC19:12
*** thingee has quit IRC19:12
*** lbragstad has quit IRC19:12
*** mrodden has quit IRC19:12
*** miguelgrinberg has quit IRC19:12
*** lbragstad_ is now known as lbragstad19:12
fungiPROPOSED: Unified Mirrors (krotscheck, jeblair)19:12
*** miguelgrinberg_ is now known as miguelgrinberg19:12
*** thangp_ is now known as thangp19:12
*** [1]tshtilma is now known as tshtilma19:12
fungi#link https://review.openstack.org/25267819:12
*** henrynash_ is now known as henrynash19:12
*** krotscheck1 has joined #openstack-meeting19:12
*** mrodden_ is now known as mrodden19:12
*** pabelanger_ is now known as pabelanger19:12
fungilooks like this was discussed as i'd hoped last week, though council voting was deferred for an additional week19:12
*** itsuugo_ is now known as itsuugo19:12
fungi#info Voting is open on the "Unified Mirrors" spec until 19:00 UTC Thursday, February 4.19:12
*** alop_ is now known as alop19:12
krotscheck1\o/19:12
*** vijendar has joined #openstack-meeting19:12
fungiwe've got a status update on the agenda for this already, so i'll avoid spending much time on the spec announcement19:12
jeblairi have also pushed up the afs modification of that https://review.openstack.org/27367319:12
*** maishsk has joined #openstack-meeting19:12
*** neiljerram has joined #openstack-meeting19:12
*** penick has joined #openstack-meeting19:12
*** matrohon has quit IRC19:13
*** mrunge has joined #openstack-meeting19:13
fungicool. everyone let's vote on that too by thursday if possible19:13
jeblair(which is what's actually in production now)19:13
fungi#link https://review.openstack.org/27367319:13
fungi#topic Adding a new node to nodepool to support libvirt-lxc testing in Nova (thomasem, dimtruck)19:13
*** openstack changes topic to "Adding a new node to nodepool to support libvirt-lxc testing in Nova (thomasem, dimtruck) (Meeting topic: infra)"19:13
fungiany chance thomasem or dimtruck are around this week to discuss what they wanted here?19:14
thomasemfungi: So, this turned out to be a bug that was filed here: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/153628019:14
openstackLaunchpad bug 1536280 in linux (Ubuntu) "domain shutdown fails for libvirt/lxc" [Medium,Confirmed]19:14
*** htruta` is now known as htruta19:14
fungi#link https://launchpad.net/bugs/153628019:14
*** akuznetsova has joined #openstack-meeting19:14
thomasemWe're disabling the tests affected right now to just get some testing for LXC working, and I'm iterating tests here: https://review.openstack.org/#/c/274792/1 and investigating the other failures.19:14
thomasem#link https://review.openstack.org/#/c/274792/119:15
*** vijendar1 has joined #openstack-meeting19:15
*** trozet has joined #openstack-meeting19:15
clarkbI wouldn't make a special new node just for this. If newer kernel fixes it we can use that across the board for example19:15
*** luisfdez has joined #openstack-meeting19:15
clarkbor use centos/fedora until ubuntu can fix19:15
*** etoews_ has joined #openstack-meeting19:15
*** mordred has joined #openstack-meeting19:15
anteayathomasem: so from the nova mid-cycle last week I got that you want to use a specific kernel for your test19:15
*** kbyrne has joined #openstack-meeting19:15
*** harshs has joined #openstack-meeting19:15
fungiyeah, trying on centos 7 was one of my earlier suggestions as well19:15
fungior fedora 2319:16
*** spzala has joined #openstack-meeting19:16
fungithe latter should have a pretty bleeding-edge kernel i think19:16
thomasemclarkb: fungi: Good call, I wasn't sure what our options are regarding that, but if we can just specify a different kernel, I would be amenable to that. I haven't tried on other OSes19:16
*** whenry has joined #openstack-meeting19:16
*** n0ano has joined #openstack-meeting19:16
thomasemI'm using 3.18.x in my environments and that works great19:16
clarkbthomasem: ubuntu LTSs have the hardware support kernels which we havne't had to use previously but are available to us19:16
fungii'm a little iffy on having our test environment for ubuntu 14.04 lts use a nonstandard kernel, and having jobs rely on that19:17
clarkbfungi: its "standard"19:17
clarkbfungi: it just isn't default19:17
fungibut if it's a packaged kernel in updates that's fine19:17
fungiyep, no disagreement from me on that19:17
thomasemSo, you would prefer a different OS entirely? I think that's why we were considering a different node at the time. That's not the biggest problem right away, though. The biggest problem is the other intermittent failures that I don't have a root cause for yet.19:17
cody-somervilleIs there a specific kernel patch that is needed? Maybe we can get them to include it in the LTS kernel.19:18
fungias long as it doesn't also come with new and improved blow up all our other jobs support19:18
thomasemHahaha, yeah19:18
clarkbfungi: right that is the risk and why centos7/fedora23 would be preferable to start probably19:18
*** vijendar has quit IRC19:18
thomasemTo avoid Ubuntu node kernel changes affecting everything else?19:18
ianwthomasem: centos is 3.10 ... but probably heavily modified ... f23 is 4.3.319:18
clarkbthomasem: yes19:18
thomasemGotcha19:18
*** dencaval has joined #openstack-meeting19:18
ianwthomasem: i can help you with setup of either19:18
clarkbthomasem: ovs, qemu, etc19:19
*** boris-42 has joined #openstack-meeting19:19
*** bookwar_ has joined #openstack-meeting19:19
*** annegentle has joined #openstack-meeting19:19
thomasemianw: Gotcha. At the moment I'm trying to just get this thing passing consistently for the tests that aren't affected by the kernel problem, if that makes sense. But, once we get that part solved, I would be happy to explore other node types that can open up the breadth of tests we can run on LXC reliably.19:20
thomasemclarkb: fungi ^^19:20
thomasemdoes that all seem reasonable?19:20
*** neiljerram has quit IRC19:20
fungiokay, so sounds like there are at least a couple of good paths forward without adding a special "ubuntu with seasoning" node type19:20
fungimakes sense19:20
clarkbthomasem: yup makes sense19:20
thomasemOkay, awesome. ianw, I will hit you up if I run into snags, does that sound good? I really appreciate the aid.19:21
fungithomasem: need anything else debated in the meeting, or does this transition to the infra channel/ml and code review next?19:21
thomasemfungi: Nope. I think we have a path forward, and if anything starts going wrong, I'll start screaming again.19:21
thomasem:D19:22
fungiexcellent! we can finally get this off our meeting agenda backlog ;)19:22
thomasemwoot woot19:22
fungi#topic Scheduling a Gerrit project rename batch maintenance (SergeyLukjanov)19:22
anteayaI don't think this constitues as screaming19:22
*** openstack changes topic to "Scheduling a Gerrit project rename batch maintenance (SergeyLukjanov) (Meeting topic: infra)"19:22
fungii do enough screaming for all of us19:22
anteayaI've never seen that happen19:22
fungiokay, last week it was decided to kick the ball down the road because lots of people were travelling19:22
anteayaanyway sorry to derail19:22
anteayais SergeyLukjanov here?19:23
*** rderose has quit IRC19:23
*** kencjohnston has joined #openstack-meeting19:23
anteayaI'm not excited about this, I'll play along but can't drive19:23
fungithere are a couple of pending renames for official repos. SergeyLukjanov was offering to run the maintenance as long as there are at least some of us around in case something goes awry19:23
*** ijw has joined #openstack-meeting19:23
*** hogepodge has joined #openstack-meeting19:24
clarkbthis weekend is an unofficial holiday in this country19:24
fungifoosball tournaments19:24
anteayaI can be around this weekend but again not in a hurry19:24
clarkbso I am mostly not around19:24
fungii will not be partaking in said tournament mania so can be available...19:24
*** kencjohnston has quit IRC19:25
fungibut also these renames don't seem terribly urgent and there aren't many of them19:25
anteayaI'm here if you need me19:25
fungialso this would be our first renames since the gerrit upgrade, right?19:25
anteayayes19:25
jeblairoh, so probably worth a bit more attention than usual19:25
fungiso might be best to defer yet another week and have more people available19:25
anteayagood point19:25
fungiyeah19:25
*** salv-orlando has quit IRC19:25
yolandai can be around on mornings in my timezone, that will be the same as Sergey. But cannot be around in the afternoons19:26
*** kencjohnston has joined #openstack-meeting19:26
*** thingee has joined #openstack-meeting19:26
fungiyolanda: thanks, good to know19:26
anteayaI'm off again the weekend of the 12th19:26
anteayauntil the end of Feb19:26
anteayaso not available for rename things19:26
fungii guess i'll try to circle back around with SergeyLukjanov about a possible window for next week, and we can pick a time when we meet again19:27
anteayayup19:27
fungi#topic Mirror update (jeblair, krotscheck)19:27
*** openstack changes topic to "Mirror update (jeblair, krotscheck) (Meeting topic: infra)"19:27
jeblairyou're all afs admins now19:27
anteayaha ha ha19:27
krotscheck1WOOO19:27
krotscheck1Wait19:27
krotscheck1sadpanda19:27
anteayaall == infra-root, yes?19:27
fungiafs administration as code! old meets new!19:28
jeblairthe pypi mirrors are in production and on afs19:28
jeblairwe're still keeping the old ones around for just a bit in case something goes terribly wrong19:28
fungianteaya: all == anyone contributing patches and looking at whatever we can expose on dashboards and graphs19:28
krotscheck1Wheel mirror work is still in progress.19:28
anteayafungi: ah okay thanks19:28
*** jesusaurus has joined #openstack-meeting19:28
jeblairin general, the theory about it being fast by serving from local cache seems to be holding19:29
AJaegeranything special we need to know when reviewing?19:29
jeblairit does turn out that trans-atlantic udp is quite slow19:29
clarkbjeblair: are we going to set up a replica in europe?19:29
jeblairso when the ovh mirrors fetch something from the fileserver, it takes a bit longer19:29
jeblairclarkb: if we did, it may improve that ^19:30
fungiAJaeger: probably for now, being aware that pip is installing from a cached backend for the pypi mirrors in our jobs is a good place to start19:30
*** bswartz has joined #openstack-meeting19:30
jeblairbut also, even within the us, when we transfer hundreds of gb between data centers to make the read-only replicas, that turns out to be quite slow too19:30
*** deva_ has joined #openstack-meeting19:30
fungiin theory there should be no impact, but be on the lookout for oddities in jobs which could be explained by stale caches, cold caches, cache misses19:31
Clintwe need faster-than-light packets19:31
anteayathanks, good question AJaeger19:31
AJaegerfungi, ok, we learn as we go ;)19:31
jeblairour initial sync of the pypi mirror to a new read-only site took much longer than i guessed, and ended up getting aborted19:31
*** tshtilma has quit IRC19:31
jeblairi started another initial sync last night in a safer manner, and expect it to finish wed night19:31
*** jdurgin has joined #openstack-meeting19:31
jeblairi'm going to manually release it after that a few times until i'm happy that the deltas are reasonably small and fast19:32
*** su_zhang has quit IRC19:32
jeblairthen we can switch back to automated releases19:32
*** su_zhang has joined #openstack-meeting19:32
jeblairand then, some time in the future, maybe we can look into whether there's anything we can tune to make this faster19:32
jeblair(cern measures their afs throughput in gbps)19:32
clarkbjeblair: the expectation is that only the initial sync is slow right?19:32
jeblairclarkb: yeah, it's an incremental system so should speed up considerably19:33
fungidoesn't seem terrible as a startup cost, really19:33
fungiconsider that bootstrapping a pypi mirror from scratch with bandersnatch takes a similarly long amount of time19:33
jeblair[end of my report]19:33
jeblairindeed :)19:33
*** su_zhang has quit IRC19:34
fungiexcept in this case we (in theory) incur that cost once now instead of for every new mirror server we create19:34
cody-somervilleIf we start doing replication clones, I assume we'll cluster a couple together to avoid having to repay that setup cost in event of failure of one of the nodes?19:34
*** toscalix has quit IRC19:34
*** su_zhang has joined #openstack-meeting19:34
*** toscalix has joined #openstack-meeting19:34
jeblairright now we have 2 fileservers, in rax dfw and ord19:34
*** ppetit has joined #openstack-meeting19:34
jeblairi don't think that needs to change in the immediate future19:35
*** sriram has joined #openstack-meeting19:35
jeblairas it's actually the mirror servers (which are afs clients) that are doing the real local caching19:35
jeblairand they are in each region we have nodepool slaves19:35
* krotscheck1 is more or less done with the wheel_mirror patches, excepting some typos and cleanup.19:35
*** jesusaurus has quit IRC19:35
* krotscheck1 is waiting for local tests to pass before uploading a (hopefully final) patchset19:36
*** deva_ has quit IRC19:36
jeblairyeah, i think those are ready once we get the incantation right :)19:36
*** vgridnev has joined #openstack-meeting19:36
fungiawesome19:36
jeblairi created the first wheel volume in afs and mounted it19:36
* krotscheck1 is fresh out of goats, will be switching to tofu sacrifices.19:36
jeblairso all the externalities have been satisfied19:37
anteayakrotscheck1: its squishy19:37
*** TestPanda has joined #openstack-meeting19:37
krotscheck1Most of the system-config patches should be ready though.19:37
*** TestPanda has quit IRC19:37
krotscheck1It's only the job defenitions that are pending.19:37
krotscheck1jeblair: Do we already have a wheel slave?19:37
*** SridharG has quit IRC19:37
jeblairkrotscheck1: no19:37
jeblairfungi: right?19:37
clarkband we will need one for each platform19:38
clarkbor otherwise chroot/container19:38
jeblairclarkb: right, though we're starting with only ubuntu for simplicity19:38
fungino wheel slave built yet afaik19:38
fungiso yes, that's an upcoming step19:38
*** toscalix has quit IRC19:39
clarkbjeblair: that makes sense19:39
fungiso thrilling progress with afs in production! this also makes for a great segue into our next topic19:39
fungiunless there are more afs/wheel mirror questions19:39
anteayanone here19:40
*** vijendar1 has quit IRC19:40
fungi#topic Swift for docs publishing (annegentle, fungi)19:40
*** openstack changes topic to "Swift for docs publishing (annegentle, fungi) (Meeting topic: infra)"19:40
fungi#link http://specs.openstack.org/openstack-infra/infra-specs/specs/doc-publishing.html19:40
fungithere was some renewed interest from the docs team in recent weeks/months on this spec19:41
jeblairi have prepared thoughts on this, sorry for the bomb.19:41
jeblairnote that the spec also has an afs alternative section:19:41
jeblairhttp://specs.openstack.org/openstack-infra/infra-specs/specs/doc-publishing.html#afs19:41
jeblairit says to do this, we'd have to set up an afs cell which is a lot of work19:41
jeblairbut we have an afs cell now19:41
jeblairso it's probably worth revisiting19:41
jeblairoriginally, i imagined that to have it work securely on throwaway nodes, we would need zuul to do some complicated stuff with creating principals, pts entries, etc19:41
jeblairthat's still more work than i'd like to do in zuulv2, but it's possible, and may be less work than the rube-goldberg approach in the spec19:41
jeblairhowever, if we are willing to be a little less paranoid, and trust doc build jobs with afs creds on long lunning slaves (like we chose to do with mirror wheel builds), we could get docs into afs with rsync _really quickly_19:41
fungireally what it's mostly lacking now is some available hands to work through implementation19:41
fungioh, heh. reading19:41
fungiand yes, basically what i was about to say19:41
fungithanks for saving me the typing!19:42
jeblair:)19:42
fungiso the takeaway there is... if there are people who are really amped about afs, this is a great spec to jump on19:42
*** sudipto_ has joined #openstack-meeting19:43
*** maishsk has quit IRC19:43
*** su_zhang has quit IRC19:43
cody-somervilleWould it really need AFS credentials? Or just normal prived ssh key to do the build+publish workflow?19:43
*** su_zhang has joined #openstack-meeting19:43
SpamapSwow, nobody wanted to just teach sphinx how to upload things to swift?19:43
fungii would expect to see a revision of the current approved spec which takes the afs details into account of course, but aside from that i agree the work is much simplified if we go down that path now19:43
*** krotscheck1 has quit IRC19:44
*** _nadya_ has joined #openstack-meeting19:44
SpamapSand proxy docs.openstack.org to swift?19:44
jeblaircody-somerville: logs are simpler, so i proposed doing that for that spec.  docs are _much harder_ because of the layout19:44
jeblairSpamapS: see above19:44
*** maishsk has joined #openstack-meeting19:44
fungiSpamapS: i was equally shocked ;)19:44
*** hanzhang has joined #openstack-meeting19:44
*** huangtianhua has joined #openstack-meeting19:45
cody-somervilleAlso, wondering if there is benefit to dogfooding OpenStack service instead of relying on custom infrastructure here (though the point about layout is definitely fair)19:45
*** timcline_ has joined #openstack-meeting19:45
jeblairwe have different branches writing into basically the same tree (in a predictable/structured manner), so it can not simple be copied, or even blindly rsynced19:45
*** merooeny_ has joined #openstack-meeting19:46
* annegentle waves19:46
jeblairbasically, the only way i know to get what we need is a careful rsync (copy is right out because you can't be smart about deletions)19:46
fungiour dogfooding of said storage solution for log publication has run into some snags, mostly around the browsing experience and need for real filesystem-like metadata too. while i agree we should avoid reinventing the wheel, this wheel was invented decades ago and is still nice and round19:46
annegentleyeah it's the "blindly rsynched" that's tough here19:46
*** balajiiyer has quit IRC19:46
*** su_zhang has quit IRC19:46
*** balajiiyer has joined #openstack-meeting19:47
*** su_zhang has joined #openstack-meeting19:47
cody-somervilleWhat if each build is published in unique location/namespace/whatever and then there is an atomic "update to point at latest"?19:47
* annegentle catches up on afs cell stuff...19:47
SpamapSYeah, for an immediate solution, seems like just "better things behind the current solution" is going to have to win out over "making swift better"19:47
*** tsymanczyk has left #openstack-meeting19:48
jeblaircody-somerville: that's vaguely what the spec accomplishes -- it's sort of "build this as a unit, and try to drop the unit in place (with rsync)"19:48
annegentlecody-somerville: I'd have to think about that... we only "release" the install guides and config refs to a known /relname/ URL right now, and then the contrib dev docs also have "releases"19:48
SpamapSOne should be able to build a site entirely hosted in swift. But if there's time pressure, sounds like can't dogfood it.19:48
*** zxiiro_ has joined #openstack-meeting19:49
annegentlecody-somerville: then guides like Ops Guide, Security Guide, those are namespaced to cover multiple releases...19:49
*** prometheanfire has left #openstack-meeting19:49
*** bobh has quit IRC19:49
fungiwell, the docs and logs use cases turned out to differ in a couple of key areas. logs: huge volume, need to track and possibly prune by age, need to generate indexes on the fly; docs: (comparatively) small quantity of data, comes with own indexing pregenerated19:49
*** bobh__ has joined #openstack-meeting19:49
annegentlecody-somerville: so yeah it's vaguely like that :)19:49
jeblairSpamapS: that's where we started with this, but the actual requirements are almost completely opposite of what swift provides19:49
SpamapSjeblair: how disappointing. :(19:49
annegentleSpamapS: ha. Yeah I wondered how much the reality had moved on with a 1.5 year old spec jeblair19:49
SpamapSThat may explain why I am always puzzled as to why somebody didn't use swift. Maybe it just isn't for what I think it's for.19:49
annegentleso that's also a point to discuss, is that spec reflecting reality?19:50
annegentleHonestly, it comes up mostly when Google finds an outdated doc that's still on the server because we don't delete.19:50
jeblairannegentle: i think the spec could still be implement as written; my personal feeling is that we'd get it done faster if we pivoted to afs (which is the big thing that has moved on since the spec was written)19:50
annegentlethe other big win is HTTPS on docs. and developer.19:50
SpamapSLike, I also think anything that is "a mirror" should be hostable in a thing like swift. But nobody seems to do that, so there must be something about it that just makes that really hard.19:50
*** dkranz has quit IRC19:50
annegentlejeblair: ok, that's good to know and exactly why I'm asking :)19:50
SpamapS++ on https for docs19:51
*** timcline has quit IRC19:51
*** zxiiro has quit IRC19:51
*** shz has quit IRC19:51
*** tiantian has quit IRC19:51
*** merooney has quit IRC19:51
annegentleSpamapS: IKNOW :)19:51
annegentlekidding on the shout :)19:51
AJaegerSpamapS: noone disagrees ;)19:51
fungiSpamapS: well, the docs "site" is built in bits and pieces with different processes modifying overlapping parts of the tree at different times19:51
cody-somervilleI'm just concerned with AFS becoming a hard dependency of the CI system.19:51
jeblairand i think either way, we can add https19:51
*** esker has quit IRC19:51
*** zxiiro_ is now known as zxiiro19:51
annegentlejeblair: true19:51
fungiso persistence and malleability are needed for the current state of docs.o.o19:51
clarkbSpamapS: no public access except via cdn and rudimentary indexing ability are the two killers for us19:52
fungialso swift doesn't seem to be designed as a filesystem, rather as a filestore, and you still need to maintain external indexing (which is where we're still struggling with the log storage effort)19:52
*** maishsk has quit IRC19:52
*** vuntz has quit IRC19:52
*** su_zhang has quit IRC19:53
fungilack of hierarchical indexing, specifically (or any built-in hierarchy at all really)19:53
*** whydidyoustealmy is now known as barra20419:53
*** su_zhang has joined #openstack-meeting19:53
*** amrith is now known as _amrith_19:53
*** vuntz has joined #openstack-meeting19:53
jeblairif folks aren't sick of hearing about afs, i can propose a spec update and describe what that would look like19:54
*** _amrith_ is now known as amrith19:54
fungiand here i was just about to ask who wanted to take that as a next step19:54
anteayajeblair: I'd like to see your spec update proposal19:54
*** Sukhdev has quit IRC19:54
jeblairi'd like to know whether we're comfortable with semi-trusted doc build jobs19:54
*** neiljerram has joined #openstack-meeting19:54
*** resker has joined #openstack-meeting19:54
anteayaI'd like to read about what makes them semi-trusted19:54
SpamapSyeah we can discuss swift's flaws another time. +1 on afs from me, but with the caveat that I'm just a curious party, not a working party, in this context.19:54
jeblairi can also write it up both ways i guess19:54
fungiit's no worse, trust-wise, than the status quo so no objection from me for now19:54
annegentlespec update is progress to me, and ensures we're still moving towards https and decent synch19:55
annegentle"good enough synch"19:55
jeblairok, i'll do that, and we can accept or reject that approach19:56
annegentlejeblair: thanks19:56
jeblairnp19:56
fungiexcellent! and also a timely topic in conjunction with afs usage recently going into production for our mirroring19:56
fungi#topic Open discussion19:56
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:56
*** maishsk has joined #openstack-meeting19:56
cody-somervillejeblair: will doc publishing have access to the vos command?19:56
*** gyee has quit IRC19:57
fungipabelanger: any last-minute updates on the upstream development presentations ideas for the summit? did you get anything submitted? cfp deadline is in a few hours19:57
jeblaircody-somerville: not directly, too high priv.  possibly as a follow-up job like we're doing for wheels19:58
AJaegerFYI: The new Translation is nearly finished, the unified approach works fine. Now amotoki and myself are cleaning up and reenabling all repos again. Then it's figuring out horizon.19:58
AJaegerCurrent set of changes: https://review.openstack.org/#/q/status:open%20%20branch:master%20topic:translation_setup19:58
AJaegerOnly project-config ones are mandatory - reviews are welcome19:58
*** barrett1 has quit IRC19:59
AJaegerfungi, pabelanger sumitted the lightning talks for sure19:59
dougwigAJaeger: yay.  :)19:59
*** gordc has joined #openstack-meeting19:59
fungithanks pabelanger!19:59
*** harshs has quit IRC19:59
*** harshs has joined #openstack-meeting19:59
*** bdrich_ has joined #openstack-meeting20:00
fungiokay, we're out of time20:00
*** merooeny_ has quit IRC20:00
fungithanks all20:00
fungi#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Feb  2 20:00:10 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-02-02-19.03.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-02-02-19.03.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2016/infra.2016-02-02-19.03.log.html20:00
fungitake it away, ttx20:00
crinkleo/20:00
ttxrussellb, mestery, annegentle, lifeless, mordred, flaper87, dtroyer, markmcclain, jeblair, jaypipes, sdague, dhellmann: around ?20:00
*** yolanda has left #openstack-meeting20:00
flaper87o/20:00
russellbhi20:00
sdagueo/20:00
mesteryo/20:00
dhellmanno/20:00
markmcclaino/20:00
keedyaHi All20:00
*** ppetit has left #openstack-meeting20:01
ttxAlright that makes 7 of us20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Feb  2 20:01:21 2016 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
*** jaypipes has joined #openstack-meeting20:01
ttxHi everyone!20:01
annegentleo/20:01
ttxHere is our agenda for today:20:01
devanandao/20:01
ttx#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee20:01
*** drankis has quit IRC20:01
ttx#topic Adds the Poppy CDN project to the Governance Repository20:02
*** openstack changes topic to "Adds the Poppy CDN project to the Governance Repository (Meeting topic: tc)"20:02
ttx#link https://review.openstack.org/27375620:02
*** Sukhdev has joined #openstack-meeting20:02
ttxPoppy has been around for some time, including some presence in past summits20:02
ttxThey hold regular meetings on IRC and sometimes used the ML for discussion20:02
ttxflaper87: you raise two points20:02
dhellmannthe only part of this that worried me was not finding anything about a ptl election, did they have one?20:03
*** olaph has left #openstack-meeting20:03
jaypipeso/20:03
mesterydhellmann: ++, and flaper87 raised that in the review20:03
ttxWe don't mandate that they had an election for the initial ptl tbh20:03
*** Sukhdev has quit IRC20:03
dhellmannok, that's fair, I just wasn't sure how the current ptl was selected at all20:03
flaper87dhellmann: I seem to remember they did but I could be wrong. FWIW, I think they know the "openstack way"20:03
ttxonce in they are included in the election runs, but they can announce a ptl for the initial cycle20:03
dtroyero/20:03
*** banix_ has joined #openstack-meeting20:03
*** ivar-lazzaro has joined #openstack-meeting20:03
anteayafor new projects it mostly is by aclaimation even if they do go through the motions20:03
*** malini has joined #openstack-meeting20:04
flaper87Most (all) of them used to be part of Zaqar in the past and I'm confident they won't have issues adopting elections and other tools they perhaps haven't used enough20:04
*** aysyd has quit IRC20:04
ttxas far as the tag goes, it should really be applied by us20:04
*** Sukhdev has joined #openstack-meeting20:04
flaper87ttx: happy to do it myself20:04
*** reed_ has joined #openstack-meeting20:04
*** egallen has quit IRC20:04
ttxwould be the occasion to refresh all of them20:04
*** rfolco has quit IRC20:04
ttxso in summary i wouldn't block on those issues20:05
* dims_ lurks20:05
dhellmannagreed20:05
flaper87++20:05
*** barrett1 has joined #openstack-meeting20:05
flaper87happy to remove my -120:05
*** mkmad has joined #openstack-meeting20:05
*** ilyashakhat has quit IRC20:05
ttxany other objection / remark ?20:06
mesteryAlso agreed, and commented as such in the review20:06
ttxIt certainly is a small project20:06
*** su_zhang has quit IRC20:06
ttxbut it feels integrated enough, using Designate for stuff20:06
jeblairare there any open source cdns poppy could interface with?20:07
annegentlejeblair: hm, none I can think of20:07
ttxjeblair: good question, I don't think there is such a thing ?20:07
dhellmannyeah, their presentation to our meetup group a while back was quite impressive in terms of the amount of upstream integration they had and were planning20:07
*** vijendar has joined #openstack-meeting20:07
* ttx looks at deps20:07
jeblairi'm wondering if this is a case of a project that we can not fully test because it exists solely to interface with proprietary services20:07
jeblairdhellmann: can you elaborate?20:08
dhellmannoh, just that they were using oslo, relying on designate, etc.20:08
jeblairah gotcha20:08
dhellmannthey were trying to focus their layer and work with the other existing projects20:08
dhellmannnot reinvent things20:08
flaper87++20:08
ttxhmm, they seem to have a pretty weird directory layout20:08
ttxsee the requirements directory20:09
annegentlelet's have them not make a separate client and plug into osc :)20:09
dtroyerthey would still need a lib for that20:09
dhellmannannegentle : ++20:09
jaypipesjeblair: that is my concern as well.20:09
ttxI wonder how they can gate with such a setup20:09
flaper87annegentle: that's their plan already20:09
lifelesshi, @lca so can't really pay attention here20:09
annegentledtroyer: flaper87: cool20:09
flaper87we can have them make that explicit in the review20:09
flaper87I believe they've talked w/ dtroyer already20:09
ttxoh, just a very specific tox.ini20:09
*** ociuhandu has quit IRC20:10
dhellmannyeah, I wonder if their dist has good metadata20:10
dhellmannwe might need to work with them on that20:10
flaper87yup20:10
*** merooney has joined #openstack-meeting20:10
* edleafe wanders in late20:10
flaper87mmh, not sure if they're syncing with upstream g-requirements given their requirements structure20:11
ttxhmm, I wonder about the licenses of those deps20:11
dhellmannflaper87 : no, they aren't20:11
flaper87amitgandhinz: around ?20:11
amitgandhinzflaper87: hi20:11
flaper87It'd be cool if you could help us clarify some things20:11
flaper87amitgandhinz: ^20:11
flaper87backlog :D20:11
*** achanda has quit IRC20:11
flaper87amitgandhinz: basically, we noticed you folks are not syncing with global requirements20:12
*** mrmartin has quit IRC20:12
dhellmannttx: we should be able to clear a lot of that up by converting the separate files to extras20:12
flaper87and there might be some dependencies that don't have a license that works well with OpenStack20:12
amitgandhinznot currently.  we in general have tried to follow the general requirements but have not enforced it.  i think there are a few that arent20:12
flaper87amitgandhinz: are you folks working on getting there?20:12
ttxAbstaining until I can check the licenses on deps20:12
*** merooney has quit IRC20:12
ttxdhellmann: sure, but maybe we should wait until that's clarified before approving ?20:13
*** mkmad has quit IRC20:13
*** egon_ is now known as egon20:13
amitgandhinzwe can.  it hasnt been a priority right now to remove the stuff that is not part of general reqs but we can prioritize that if needed20:13
jeblairamitgandhinz: is there an open source cdn system that poppy could integrate with?20:13
dhellmannttx: maybe20:13
amitgandhinzjeblair: nothing that is active.  there have been a few that fizzled like OpenCDN etc, but nothing that has stayed and matured20:14
dhellmannamitgandhinz : we need it to be clear that you're meeting the requirement "Project must have no library dependencies which effectively restrict how the project may be distributed or deployed"20:14
* flaper87 abstains as well...20:14
flaper87looking forward to clarify the requirements bit, otherwise it looks good20:14
amitgandhinzim pretty sure everything is apache licensed but would need to confirm it20:14
flaper87amitgandhinz: happy to help with guidance on that front if necessary20:14
flaper87amitgandhinz: requirements, tox, etc.20:14
thingeeamitgandhinz: without an open source solution there's not really a reference implementation to verify things work from a testing perspective.20:15
ttxI couldn't spot any blatant issue with the licensing in the deps20:15
* jroll notices the tests use mimic to mock CDN provider APIs20:15
thingeeamitgandhinz: recommend reading the discussion on where mimic has been going in the openstack community http://lists.openstack.org/pipermail/openstack-dev/2016-January/083510.html20:16
ttxcertifi is ISC, but we might need to add that to the mix anyway20:16
maliniFYI - mimic is just used in the docker support, but the tests are independent of mimic20:17
flaper87malini: oh, that's good input.20:17
jrollah, neat20:17
ttxOK, we have enough votes to pass this20:17
*** banix_ has quit IRC20:17
jeblairjroll: yeah, it's probably as good as can practically be in this case.  i'm struggling with it because when i talk about our stance on open core, i say we leave the door open for plugins for proprietary systems but our open-source implementations are first-class.20:17
*** xinwu has quit IRC20:17
sdagueI guess it's just whether an orchestrator for commercial services that has no open implementation is really openstack. Seems a little odd to me personally. Especially given that no open core issue.20:17
thingeejeblair: +100020:18
jeblairsdague: i think we just said very similar things20:18
jrolljeblair: yeah, agree20:18
*** banix has joined #openstack-meeting20:18
jrolljust wanted to note that, for better or worse20:18
ttxsdague, jeblair: yes, that's a good point.20:18
sdaguejeblair: yes20:18
thingeejeblair: however like I spoke to you about open core and openstack, I don't think it's exactly accurate stance we currently have.20:19
sdaguei'm -1 for that reason honestly, I just don't think we want that to be our pattern20:19
jeblairi recognize the complexity introduced by not having a viable open source implementation of a thing though.  thus the struggle.20:19
*** merooney has joined #openstack-meeting20:19
dhellmannyeah, this isn't a case of a project ignoring an open source option20:19
sdagueopenstack doesn't have to be the home for all software20:19
ttxI propose we think a bit more about it over the week and make a final call next week20:19
annegentlejeblair: yeah... it's such a physical thing too, these networks and geographies20:19
ttxwould be interesting to have a discussion about the "no open core" principle and where that leads us wrt: Poppy20:20
*** tellesnobrega is now known as tellesnobrega_af20:20
mesteryttx: Seems reasonable20:20
thingeettx: +120:20
*** banix has quit IRC20:20
flaper87ttx: ++20:20
thingeeto both points of waiting and open core discussion20:20
ttxThe brokering-to-commercial-serviuces aspect was also hitting some nerves on my side20:20
*** mhickey_ has joined #openstack-meeting20:20
*** banix has joined #openstack-meeting20:20
*** egallen has joined #openstack-meeting20:21
annegentlethe struggle is that it provides a better user story20:21
ttxAlright, let's put it back on agenda next week, and have interesting discussion in the mean time20:21
annegentlebut yeah, I get it. it's a struggle20:21
jeblairannegentle: agreed20:21
ttx#topic Rescheduling bug-smash event20:21
*** openstack changes topic to "Rescheduling bug-smash event (Meeting topic: tc)"20:21
jeblairannegentle: if i had to use a cdn, i'd like to do so with an openstack api :)20:21
ttxannegentle: it's not an easy call, otherwise we'd had made it already20:21
annegentlejeblair: ++20:21
*** jgriffith_away is now known as jgriffith20:21
ttxit's neither completely wrong nor completely fine.20:22
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/085196.html20:22
ttxdhellmann: care to introduce this topic ?20:22
dhellmannsure20:22
dhellmannsome folks from intel, ibm, and a bunch of other companies are trying to organize an even to encourage working on bugs20:22
dhellmannin the past these have resulted in some new contributors, and obviously new contributions20:23
dhellmannin principle I like the idea, but they have picked dates that correspond exactly with our feature freeze deadline this cycle20:23
dhellmannso, I have asked them to reschedule it20:23
ttxwhich is basically the worst possible date20:23
ttxit was a pretty bad date already last cycle iirc20:23
sdaguethis has also happened the last two cycles in similar ways20:24
dhellmannno one has said "no", but shane wang, who seems to be the main organizer, has asked the TC to weigh in20:24
dhellmannafter we get this one moved, as sdague says, we keep having this problem so I would like to brainstorm ideas for addressing that separately20:24
annegentlewhat's the offset?20:24
ttxWell, my view on it is that if they want some attendance to that event they should definitely avoid that week20:24
annegentlea week?20:24
dhellmannapparently the "marketing folks" picked these days, and I'm not sure how to communicate with them20:24
russellbyes, i think it should be rescheduled.20:24
dhellmannannegentle : yes, one week later20:24
mesteryDefinitely needs to be rescheduled20:24
anteayado folks know we have a release schedule? http://docs.openstack.org/releases/mitaka/schedule.html20:24
russellbi can't imagine why anyone would disagree with that20:24
dhellmannthat's still not ideal for finding a bunch of mentors, but it's better than FF date20:25
flaper87I'd probably recommend rescheduling it the week after or even 2 weeks after20:25
jeblair#link http://docs.openstack.org/releases/mitaka/schedule.html20:25
dhellmannflaper87 : 2 weeks puts us close to RC120:25
ttxand in general move that in the first tier of the cycle if they want more attendance, like sdague suggested on thread20:25
mesteryanteaya: The folks scheduling these types of things apparently don't, we need to advertise that better I think20:25
flaper87right but 1 week is still a bit hard for other folks to attend20:25
anteayamestery: I can support that20:25
*** krotscheck1 has joined #openstack-meeting20:25
flaper87mmh20:25
sdaguewell, my understanding is feedback was given during the early discussions, but it was not taken20:25
anteayasdague: :(20:26
dhellmannflaper87 : my argument for moving it from the FF date is that it jeopardizes landing features in the release. doing it on the RC1 date would have the same effect.20:26
*** ivar-lazzaro has quit IRC20:26
flaper87sdague: any reference for that?20:26
ttxdhellmann: +120:26
annegentlelast week of feb. would be better?20:26
dhellmannflaper87 : shane's email to me indicated they were aware fo the issue20:26
flaper87dhellmann: ++20:26
ttxi think the date you suggested is the less worse20:26
ttxannegentle: not really20:26
*** dmorita_ has quit IRC20:26
flaper87dhellmann: oh, ok.20:26
dhellmannannegentle : after the next summit is the best time, frankly20:26
sdaguedhellmann: ++20:26
anteayacan the tc schedule global bug smash days? and the companies can then market it?20:27
ttxhttp://docs.openstack.org/releases/mitaka/schedule.html20:27
jrollI'm curious why getting a bunch of folks together to work on bugs would be bad during RC time20:27
flaper87dhellmann: ++ to that as well. I wonder if it'd be better, as bad as it sounds given the time some folks have put into this, to just do it in N-120:27
ttxR-7 is an option, otherwise R-420:27
*** tellesnobrega_af is now known as tellesnobrega20:27
jrollisn't that when we should be really focused on hammering out bug fixes?20:27
annegentlebut these bug fixes, are they more for stable releases?20:27
sdaguejroll: because it is being advertised as a great way to onboard new folks during that window20:27
ttxjroll: it's not optimal. But better than hitting FF week20:27
annegentleI mean, honestly, onboarding more stable fixers would be a nice goal.20:27
*** salv-orlando has joined #openstack-meeting20:28
dhellmannjroll : doing it on the day we're trying to spin the release means a fix you want might not get in because of the extra load on the gate20:28
*** piet has quit IRC20:28
sdaguewhen teams are getting to a very narrow view of what needs to be solved20:28
dhellmannjroll : also what sdague said20:28
jeblairand the extra load on people :)20:28
dhellmannjeblair : yes20:28
sdaguejeblair: ++20:28
jrollfair enough20:28
flaper87it's not necessarily bad for OpenStack but for ppl getting onboard20:28
jrollb 5720:28
jrolloops20:28
amrithas a general matter, what time in the release schedule does the TC feel would be good for such a bug smash day?20:28
dhellmannbasically, we're all focused on things other than the goal of this, which will either distract us or fail because of lack of support from the rest of the community20:28
thingeedoesn't help with the sunsetting of public cloud infra was using20:29
anteayaamrith: m120:29
amrithanteaya, thx20:29
dhellmannamrith : between summit and M120:29
thingeeresources are in an all time low20:29
barrett1amrith: excellent question!!20:29
dhellmannamrith : never *on* a deadline week20:29
jrollI do find it odd that we're opposed to new contributors joining or people fixing bugs at any point in the cycle, but I do understand the points here20:29
amrithdhellmann, amen to that ;)20:29
flaper87and as early in the cycle as possible20:29
flaper87I'd add20:29
ttxdhellmann: I would just go with your suggestion that R-4 (the week after the one originally planned) is at this stage the less worse place to make it happen, otherwise next cycle20:29
thingeejroll: maybe discouraged if you don't really have something merged for first timers?20:29
amrithI was looking to direct the conversation towards anteaya's point of the TC proposing a date and then companies marketing that for the coming cycle.20:29
amrithSo, N1 or before ...20:30
dhellmannjroll : to be clear, I'd love to have a bunch of bugs fixed. My issue is the expectations of the organizers with respect to new contributors does not mesh with that week, and that week is not a good time to introduce a *lot* of changes all at once.20:30
mesteryjroll: I think it's more of a timing thing, and the results of crushing the system from new contributors during a critical release week.20:30
sdaguejroll: well, it's more about setting expectations. If you are coming in as an expert you can land whenever20:30
ttxAlso first part of the cycle is a great time to push backports to the recent release20:30
jeblairjroll: for me, i'm not opposed, it's just that i think it will not be nearly as good an experience for all involved compared to the alternative times20:30
barrett1amrith: Agree - suggest that we reframe the "future" discussion to be more about identifying optimal times for these activities and then recruiting people/companies/geos/verticals to run them and work with TC to define focus areas.20:30
annegentleI do have empathy for procuring physical space. It's a scramble sometimes.20:30
david-lylejust throwing this out, but why does/should the TC have a say in when people in the community want to fix bugs at all?20:30
jeblairdavid-lyle: because we were asked :)20:30
dhellmannttx: ok. I'm not sure how to make that clear to Shane. Maybe we can vote? or use #agreed to put it in the minutes at least?20:30
flaper87david-lyle: because they asked for20:30
sdaguehowever, bootstrapping new folks, that's just not a great time20:30
annegentleI'd still like bug fixes and doc fixes :)20:30
ttxdavid-lyle: we don't, they asked20:30
annegentleany week20:30
david-lyleok, missed the asking, thanks20:30
anteayadavid-lyle: gate load20:31
dhellmannactually, as release managment PTL, I raised the issue20:31
amrithI would also like it if there were some support to actively dissuade this event (at the time proposed). it will be bad for two reasons. one as indicated is the load on the infrastructure and 2 the bad impression that a newbie may get ...20:31
ttxAll in agreement with suggesting R-4 or next cycle ?20:31
dhellmannyes20:31
flaper87++20:31
dtroyer++20:31
jeblairttx: ++20:31
sdagueyeh, next cycle even better20:31
mestery++20:32
ttx#agreed Suggest that they use R-4 week, or just defer to early next cycle20:32
jokke_In pricipal I like the idea of bugsmashing event between FF and RC1 or right after RC120:32
*** piet has joined #openstack-meeting20:32
ttxok, next topic20:32
ttx#topic Follow-up on last weeks applications20:32
*** openstack changes topic to "Follow-up on last weeks applications (Meeting topic: tc)"20:32
dhellmannok, thanks everyone, I'll email shane back and we can move on20:32
ttxI wanted to get next actions on the projects that were considered last week20:32
flaper87dhellmann: thanks for raising this20:32
ttx* EC2API (https://review.openstack.org/268774)20:33
ttxAlexandre did post a small wording update, hoping that matches what you expected20:33
ttxWe now have 4 +120:33
sdagueI just added my +120:33
sdaguethat team has been doing a pretty solid job20:33
ttxso if you would consider reposting yours we can probably pass that one today20:33
* flaper87 does that20:33
ttx* Add new Repo(shovel) to the Governance Repository (https://review.openstack.org/269417)20:33
ttxUnless there is an objection I will abandon this one as "needs to start existing first"20:34
flaper87oh, mine is there already20:34
ttx* Adding SaltStack to OpenStack (https://review.openstack.org/269556)20:34
ttxSame here, I propose to abandon this one until the project team gets some mileage20:34
flaper87++20:34
dhellmann++20:34
flaper87We've done that before and we've agreed abandoning is the way to go20:34
ttxok, we have 8 now on ec2api20:34
ttxI'll proceed with approving20:34
ttxit's in!20:34
*** cdent has joined #openstack-meeting20:35
ttx#topic Open discussion20:35
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:35
ttxThere were a few topics I wanted to discuss...20:35
ttx* Service type vs. project name for use in headers, and about the role of the API WG20:35
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/085145.html20:35
ttxThis thread has a few interesting insights and questions20:35
ttxOne of them being how directive we should be wrt. API guidelines20:35
ttxTraditionally we have considered that the API WG guidelines were mostly informative20:36
* cdent is here for that20:36
* devananda lurks with increased interest for this topic20:36
ttxBut with our increased focus on end user experience I think it might make sense to push for more API consistency20:36
ttxand therefore give the guidelines a bit more teeth20:36
ttx(or at least some of them=20:36
ttx)20:36
ttxwhat is your take on that ?20:36
sdaguewell, the API WG was also forward looking, as to the way things should become20:36
thingeesdague: yeah, but what about new projects forming?20:37
ttxyeah, maybe there is a split between the desired end state and a few low-hanging-fruit UX targets20:37
sdaguein this specific case, nova is one of the offenders, mostly because we did a thing before anyone else here, and just been trying to sort the right moment to bring things back to compliance without ruining the world20:38
edleafeFor new work, going against the WG standards should be a negative factor. We can't do much about existing APIs20:38
*** reed_ has quit IRC20:38
annegentlepart of the user experience consideration is of course what's already in the field. but yes, the API WG should have enough authority to say "this is how it's done"20:38
annegentleso if teeth=consideration and authority I'm good with it20:39
thingeeedleafe: so that's the point I made in the thread. We look at this impossible for existing because we don't have a grasp of who are the offenders and what are they.20:39
jeblairthis looks like the sort of thing where there is very little value in project differentiation aside from making it hard and confusing for developer-users.  it seems like the tc putting some teeth behind the recomendation may prevent bikeshedding and make things just a little less terrible for folks that use multiple openstack services.20:39
thingeeI think it would be productive to collect that information.20:39
annegentlelots of the work to date has been "what do we have here"20:39
edleafethingee: it20:39
dhellmanndo we need an assert:complies-with-api-guidelines tag?20:39
ttxor "this is how you should do it if you start a new one" ?20:39
edleafethingee: it's also because the APIs are already in use20:39
annegentlejeblair: ++20:39
sdaguedhellmann: probably20:39
thingeeedleafe: people like to wave hands about micro versioning nowadays20:39
jeblairit's also seemingly non-critical enough that if we say "this is the way" and nova takes 3 years to get there, we'll survive.20:40
*** gordc has left #openstack-meeting20:40
annegentleI've worked with this group and they are super considerate and user-thinkers.20:40
anteayaannegentle: how nice20:40
edleafethingee: well, they are doing a *little* more than just hand-waving :)20:40
jbrycedhellmann: i like that idea20:40
dhellmannI'm sure all of the guidelines are fine, I just wonder how we "enforce" it20:40
jrollthingee: well, this thread has a good example of where microversioning doesn't help, because it aims to change the headers used for those versions20:40
edleafejeblair: ++20:40
annegentledhellmann: yeah, and that tag could cover "beyond defcore" that we run into all the time20:40
thingeeedleafe: I say that to avoid people attacking me on that being the end all solution for us to evolve in having consistent apis20:40
ttxyeah, I don't mind slow progress as long as it's going in the right direction. Creating a new API from scratch that deliberately ignores guidelines would be the opposite of progress.20:40
jrollthingee: which breaks *everything* :)20:40
sdaguewell, I actually don't like the experimental guideline at all. :)20:40
dtroyernova being different because it was first is really a non-issue.  things were learned and that knowledge being formed for further use is the important part20:40
jeblairdtroyer: ++20:41
markmcclainrights seems like we should formally grant exceptions to existing code, but push a requirement and expectation that new APIs be compliant20:41
devanandanova isn't the only one - some other services followed nova's lead already20:41
jrolldevananda: yep20:41
edleafethingee: there are no magic pills that will cure all ills. But adding microversions will at least allow for sane growth20:42
devanandaand as jroll said, changing the header name for an existing service breaks things badly. {micro}versions don't help20:42
thingeettx: if the TC was to police this, we're going back to involving the TC having to dig deep into api design, which I think was part of the benefits of big tent20:42
jeblairit will take a long time to get horses back into the barn, but in the mean time, maybe close the door so any more don't get out.20:42
*** krotscheck1 has quit IRC20:42
*** zeih has joined #openstack-meeting20:42
flaper87jeblair: ++20:42
edleafedevananda: true - that's where parallel headers will be needed if we want to change20:42
markmcclainjeblair: ++20:42
jbrycejeblair: i like horse and barn analogies20:42
thingeeor perhaps the api wg wouldn't mind informing the tc of the state new applications' current apis20:42
annegentlethingee: I saw the API WG formation as helping the TC with API design -- offloading and spreading the detailed work.20:42
*** reed_ has joined #openstack-meeting20:42
thingeeannegentle: +1 :D20:42
dhellmannannegentle : ++20:42
ttxthingee: Ideally we would not police, if we go the assertion route, it would be the project opting in,  into compliance20:43
edleafeannegentle: yes!20:43
cdentthat's pretty much exactly how we think of it (within the group)20:43
annegentlecdent: yep20:43
ttxand likely the API WG telling us about projects not living up to their tags20:43
annegentlecdent: heh do we imagine becoming a tagging force tho?20:43
dhellmannttx: it seems like the API WG should manage the tag application20:43
dhellmannttx: teams that want the tag can ask them to add it?20:44
ttxdhellmann: then it would be some tag maintained by the WG, not a project assertion about themselves20:44
cdentannegentle: elmiko and I discussed at summit about being able to come up with a compliance test, and had some ideas, but didn't make a lot of progress20:44
dhellmannwhich triggers a review of the api20:44
dhellmannttx: exactly20:44
elmikoo/20:44
thingeeOk, so as I said in the thread, it would be great if TC could take a stance on this with new applications. And yes, use the api wg for being informed on new projects.20:44
ttxdhellmann: I'm fine with that20:44
dhellmannttx: so a different name?20:44
*** spzala has quit IRC20:44
thingeeexisting projects, it would be great if we can understand the problem space.20:44
dhellmannapi-wg:complies-with-guidelines20:44
devanandaedleafe, thingee: any service that would be asked to change the header name will need to carry both headers until such time as they are willing to completely drop support for today's client libraries.20:44
thingeeotherwise it's just looked at as an impossible problem20:44
ttxdhellmann: yeah, same as vulnerability:managed or release:managed20:45
devanandaas far as guidelines for new projects, I think what's being discussed here is great20:45
dhellmannttx: right20:45
ttxdhellmann: +120:45
*** spzala has joined #openstack-meeting20:45
dtroyerdhellmann: some guidelines?  all guidelines?  which?  that gets messy20:45
thingeedevananda: so support both headers, deprecate.20:45
sdaguedevananda: right, and I think that's going to be nova's plan, just add the additional headers20:45
thingeesdague: +120:45
dhellmanndtroyer : I don't think we want one tag per guideline, but I see your point.20:45
elmikocdent: (assuming you are referring to the example project stuff) i have setup a github repo for the example project and started creating an impl locally20:45
dtroyerme either20:45
edleafedevananda: a service might *want* to change its header. The old one may be dropped in the future, or it may hang around forever20:45
sdaguethingee: the deprecate is weird, you kind of have to keep them all forever20:45
ttxdtroyer: they should probably have a pack of minimal requirements that they would tie to the tag20:45
thingeesdague: sure, just don't document it anymore then20:46
thingeepeople will forget, but yeah that seems fair20:46
sdaguethingee: you have to20:46
sdaguethere are liberty clouds20:46
sdaguethat only work with it20:46
thingeefair20:46
dhellmannttx: right, or if they can be categorized in some useful ways maybe a small number of more descriptive tags20:46
edleafethingee: people may forget, but exiting tools won't20:46
thingeeedleafe: how active are these tools then?20:46
ttxok so we should recommen20:46
sdaguebut not only that, there are deployed public clouds. We need the API to work with any cloud, that was kind of the point :)20:47
ttxd the API wg comes up with their own tag or set of tags to describe levels of compliance20:47
edleafethingee: no one really knows.20:47
*** dmorita has joined #openstack-meeting20:47
*** edtubill has quit IRC20:47
edleafeThey don't all self-identify20:47
annegentletag:has-awful-mulitple-POST-request-bodies20:47
devanandasdague: exactly. keep both headers indefinitely is the only path that makes sense to me here20:47
sdaguedeciding to break that for the sake of consistency isn't a valid trade off, just when we are making gains on interop20:47
dhellmannannegentle : +220:47
*** sdake has joined #openstack-meeting20:47
*** spzala_ has joined #openstack-meeting20:47
edleafethingee: when I was at Rackspace I had a hell of a time getting usage metrics for the SDKs20:47
jeblairgenerous in what you accept and strict in what you send20:48
sdagueanyway, is there a particular ask here?20:48
dhellmanndevananda, edleafe, thingee, sdague : I don't think we need or want to solve the specific issue in this meeting20:48
ttxthingee: to answer your question ideally we would look at this before approving new service projects20:48
*** resker has quit IRC20:48
sdaguedhellmann: yeh, I was trying to regroup about what the ask or concern is for us to address20:48
edleafedhellmann: sure, but it is helpful to air the concerns of the different approaches20:48
*** reed_ has quit IRC20:48
annegentledhellmann: yeah. I think the ask is of the API WG if they see tags as a decent way to measure/apply standards adherence20:48
dhellmannsdague : you hit enter before I did :-)20:48
annegentlewas that even a sentence?20:48
thingeedhellmann: you're right. I only cared about this being something the TC takes a stance on going from recommending to enforcing. If it's just new projects, sure that's a great step20:48
dhellmannedleafe : the API WG can deal with the details20:49
*** timcline_ has quit IRC20:49
ttxbut it's really easier for the API WG to keep track of their set of rules and judge how far a project is20:49
*** _nadya_ has quit IRC20:49
*** spzala has quit IRC20:49
ttxthingee: it's also about not regressing in existing projects20:49
dhellmannright, we have people looking at this already, and we have a system for tracking the results in the governance repo. let's use them.20:49
cdentthe issue, from the standpoint of the group is how to have some teeth20:50
cdentan "official tag" is probably the hammer we have at the moment20:50
ttxOK, let's continue on that thread, I had a few other points to touch on20:50
ttx* Competition vs. user experience20:50
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/085041.html20:50
ttxJay raises a number of interesting points about how allowing competition without any restriction resulted in a crappy user experience20:50
ttxI'd like us to think about ways to fix that20:51
*** ijw has quit IRC20:51
*** dmorita has quit IRC20:51
dhellmannnow?20:51
*** novas0x2a|laptop has quit IRC20:51
ttxoh no :)20:52
sdaguecdent: honestly, I expect teeth are less likely to drive consistency than helping hands20:52
dhellmann:-)20:52
ttxI think it's a great topic though20:52
anteayasdague: I think a combination is useful20:52
cdentsdague: I think it depends a great deal on where in a project's lifecycle any project is20:52
*** Sukhdev has quit IRC20:52
ttxand wouldn't mind a temperature read from the room on it20:52
*** spzala_ has quit IRC20:52
*** achanda has joined #openstack-meeting20:52
thingeesdague: would you agree the guidelines the api wg have created are helping hands? Is it working?20:52
*** ijw has joined #openstack-meeting20:52
* flaper87 replied to that thread20:52
anteayattx: user experience is important20:52
flaper87I think it's a good one20:52
ttxI'm fine with competition as long as it doesn't result in unnecessary duplication of effort, and crappy user experience20:53
flaper87we should add it for next week's meeting. Hopefully Jay will be around20:53
* annegentle ponders20:53
annegentleyeah I'd like some think time on that20:53
dhellmannttx: I've been struggling to find a way to say that projects have to have completely unique APIs that don't include their project name in them. As soon as we drop to generic terms, we get back into the "who owns $feature_space" question20:53
sdaguethingee: helping hands as in hands helping get the code in line20:53
jaypipesflaper87: sorry, I am around now...20:53
cdentI spoke with jay about this topic some over the weekend20:53
jaypipesin London at hotel...20:53
cdentah there he is now20:53
sdaguettx: right, so the backups service type issue is a real issue20:53
ttxdhellmann: no I agree it's a tricky balance20:53
ttxsdague: the /alarms example is pretty appalling too20:54
thingeesdague: sure. I don't think know if the api wg liaisons help organize that for their respected projects.20:54
sdaguewe kind of need a registered namespace20:54
dtroyerwe have this problem in other areas too, and we have to… sdague, yes, that20:54
dhellmannis this something for a new group to manage? or the api-wg?20:54
*** raildo is now known as raildo-afk20:54
sdaguethis, honestly, starts really getting into the service catalog space20:55
jaypipesdhellmann: I think the API-WG is the correct group for this20:55
ttxI don't think we need competition that much. I think we need ways to replace projects with better alternatives over the long run20:55
*** fzdarsky|afk has quit IRC20:55
devanandattx: ++20:55
sdaguewhich could be api-wg, or not. But our own ianal is going to be important20:55
cdentsdague: I think it is definitely a service catalog issue20:55
sdaguethat being said...20:55
barrett1ttx: +120:55
annegentlecdent: so we're already working on reserved names in the service catalog20:55
flaper87ttx: fwiw, that's exactly what I've been pushing for since we started talking about the big tent. +120:55
sdaguewe don't freak out about .../action20:55
ttxthe easy way to do that is to allow competition, but that opens a whole can of UX worms20:55
thingeedhellmann: +1 very similar to the cross-project spec liaisons. They may not be the person to do the work, but they work with their respected group to prioritize things20:55
cdentannegentle++20:55
annegentlecdent: with extra data if you really need it as a provider20:56
*** jgriffith is now known as jgriffith_away20:56
annegentlebut the actual resources, I have to think on that. Endpoint+resource.20:56
*** dkranz has joined #openstack-meeting20:56
thingeedhellmann: I don't know if this works though. cp-spec liaison is so new, and getting volunteers for cross-project efforts is , well..20:56
jaypipessdague: /action is under a sub-resource, not a top-level resource endpoints overlap.20:56
*** keedya has left #openstack-meeting20:56
dhellmannjaypipes , sdague : who owns the service catalog registry?20:56
*** keedya has joined #openstack-meeting20:56
flaper87ttx: or mmh, probably I misread you :P20:56
sdaguedhellmann: that's a very good question20:56
dhellmannthingee : I suspect we'll also end up adding a new project requirement that they have their endpoint registered20:57
*** ijw has quit IRC20:57
sdagueit could be either the api-wg or the tc directly20:57
jeblairwe do?  or we delegate a group?20:57
annegentlehow do we enable an ecosystem if the experience sucks, I get it. but who gets to "keep" generic resources like alarms, meters, backups, archives, and so on20:57
*** garthb_ has quit IRC20:57
dhellmannjeblair : ultimately we own it, but who's going to actually do the work?20:57
jeblairwe can put a yaml file in governance20:57
*** garthb__ has joined #openstack-meeting20:57
*** malini has quit IRC20:57
sdagueso, something to consider, we have service types20:58
sdaguewhich is already a namespace20:58
annegentlejeblair: that's what we have for service catalog20:58
ttxI think it's a hard problem, and we definitely won't solve it in the next 2 min.20:58
*** timcline has joined #openstack-meeting20:58
annegentleright:)20:58
sdagueand that I think we can have a real register for (we don't quite yet)20:58
jaypipesheh, tru nuf20:58
dhellmannsdague: good point. so all URLs need to start with the servide type?20:58
ttxBut we should definitely think and talk about it more over the coming weeks20:58
sdaguedhellmann: they would if they were on the same web server20:58
ttxLast topic I wanted to quickly mention, the mission statement situation20:59
dhellmannsdague : might as well always do it20:59
ttxrussellb started a thread on the foundation ML, which turned a bit into bikeshedding as expected20:59
russellbindeed20:59
ttx#link http://lists.openstack.org/pipermail/foundation/2016-February/002263.html20:59
sdaguedhellmann: that breaks 100% of our ecosystem ...20:59
ttxPlease chime in if you care.20:59
russellbwe did say in the board meeting that if we can't decide on anything, we'll just approve what the TC already proposed20:59
* russellb shrugs20:59
devanandattx: if endpoint registration becomes the new blessing of officialdom, then the TC ends up where we were pre-big-tent20:59
flaper87russellb: ++20:59
dhellmannsdague : all in? :-)20:59
*** dmorita has joined #openstack-meeting20:59
annegentlerussellb: heh nice20:59
*** mhickey_ has quit IRC20:59
ttxdevananda: yeah, I'm not sold on that solution either20:59
*** mhickey_ has joined #openstack-meeting21:00
sdaguedevananda: to get a service type? I don't see how that's incompatible with the big tent21:00
*** ivar-lazzaro has joined #openstack-meeting21:00
*** merooney has quit IRC21:00
*** sgundur has joined #openstack-meeting21:00
ttxsdague: at the very least you would get some first mover advantage21:00
*** j_king_ is now known as j_king21:01
ttxanyway, we are past time21:01
*** DuaneDeC7 has quit IRC21:01
*** sgundur has left #openstack-meeting21:01
ttxThanks everyone!21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Feb  2 21:01:20 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-02-02-20.01.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-02-02-20.01.txt21:01
barrett1ttx: On the mission topic, I don't see bikeshedding. Rather discussion to insure the mission can be understood by someone without a long OpenStack History21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2016/tc.2016-02-02-20.01.log.html21:01
*** AJaeger has left #openstack-meeting21:02
*** s3wong has joined #openstack-meeting21:02
*** qwebirc49992 has joined #openstack-meeting21:03
*** qwebirc49992 has quit IRC21:03
ttxbarrett1: Let me correct myself, I mean "a large number of slightly different suggestions with none of them gathering enough support"21:03
*** clenimar has quit IRC21:03
ttxyet21:03
*** iyamahat has joined #openstack-meeting21:03
*** vgridnev has quit IRC21:04
*** cdent has left #openstack-meeting21:04
*** salv-orl_ has joined #openstack-meeting21:04
*** salv-orlando has quit IRC21:04
*** ivar-lazzaro has quit IRC21:04
dims_Since a lot of movers and shakers are here on this channel :) - Here' vkmc's call for ideas and mentors for GSoC if you missed the email - http://markmail.org/message/vzvwwbct2pa6fjst21:04
*** DuaneDeC7 has joined #openstack-meeting21:06
*** vijendar has quit IRC21:07
*** toscalix_ has quit IRC21:07
*** rbowen has joined #openstack-meeting21:07
*** salv-orl_ has quit IRC21:08
*** salv-orlando has joined #openstack-meeting21:08
*** ihrachys has joined #openstack-meeting21:09
*** Apoorva has quit IRC21:09
*** spotz_zzz is now known as spotz21:11
*** dane has quit IRC21:11
*** qwebirc89909 has joined #openstack-meeting21:12
*** qwebirc89909 has quit IRC21:12
*** sudipto_ has quit IRC21:13
*** dkranz has quit IRC21:13
*** suhani has joined #openstack-meeting21:13
*** annegentle has quit IRC21:14
*** yamahata has joined #openstack-meeting21:15
*** reed_ has joined #openstack-meeting21:15
*** dkranz has joined #openstack-meeting21:16
*** spzala has joined #openstack-meeting21:16
*** novas0x2a|laptop has joined #openstack-meeting21:17
*** Abhijith has joined #openstack-meeting21:17
*** amrith is now known as _amrith_21:18
harlowjai only shake21:18
*** dane has joined #openstack-meeting21:18
*** cgoncalves has quit IRC21:20
*** bhunter71 has quit IRC21:20
*** su_zhang has joined #openstack-meeting21:20
*** spzala has quit IRC21:20
*** spzala has joined #openstack-meeting21:21
*** gyee has joined #openstack-meeting21:22
*** esker has joined #openstack-meeting21:22
*** gyee has quit IRC21:22
*** ubuntu has joined #openstack-meeting21:23
*** ubuntu is now known as Guest4084821:23
*** su_zhang has quit IRC21:25
*** cgoncalves has joined #openstack-meeting21:27
*** esker has quit IRC21:28
*** sdake has quit IRC21:29
*** neelashah has quit IRC21:29
*** neelashah has joined #openstack-meeting21:30
*** su_zhang has joined #openstack-meeting21:32
*** zaro has quit IRC21:32
*** Apoorva has joined #openstack-meeting21:32
*** tiantian has joined #openstack-meeting21:33
*** jprovazn has quit IRC21:33
*** jichen has quit IRC21:33
*** zul has quit IRC21:35
*** huangtianhua has quit IRC21:36
*** spotz is now known as spotz_zzz21:36
*** gyee has joined #openstack-meeting21:37
*** baoli has joined #openstack-meeting21:38
*** rbowen has quit IRC21:40
*** zeih has quit IRC21:40
*** reed__ has joined #openstack-meeting21:40
*** zaro has joined #openstack-meeting21:41
*** dkranz has quit IRC21:41
*** ihrachys has quit IRC21:42
*** spotz_zzz is now known as spotz21:42
*** reed__ has quit IRC21:43
*** haomaiwang has joined #openstack-meeting21:44
*** zeih has joined #openstack-meeting21:44
*** reed_ has quit IRC21:44
*** vishwana_ has joined #openstack-meeting21:46
*** ijw has joined #openstack-meeting21:47
*** sputnik13 has joined #openstack-meeting21:48
*** vishwanathj has quit IRC21:48
*** achanda has quit IRC21:48
*** haomaiwang has quit IRC21:49
*** vishwana_ has quit IRC21:49
*** speller has joined #openstack-meeting21:50
*** ayoung has quit IRC21:51
*** dane has quit IRC21:51
*** esker has joined #openstack-meeting21:53
*** ivar-lazzaro has joined #openstack-meeting21:53
*** ivar-lazzaro has quit IRC21:53
*** ijw has quit IRC21:54
*** xinwu has joined #openstack-meeting21:55
*** erlon has quit IRC21:56
*** neil_ has joined #openstack-meeting21:57
*** sdake has joined #openstack-meeting21:57
*** barrett1 has quit IRC21:58
*** DuaneDeC7 has quit IRC21:58
*** barrett1 has joined #openstack-meeting21:58
*** neil__ has joined #openstack-meeting21:59
*** achanda has joined #openstack-meeting21:59
*** dmorita has quit IRC21:59
*** sriram has quit IRC22:00
*** shashank_hegde has quit IRC22:00
*** neiljerram has quit IRC22:00
*** dmorita has joined #openstack-meeting22:00
*** doffm_ is now known as doffm22:01
*** neil_ has quit IRC22:01
*** esker has quit IRC22:01
*** Sukhdev has joined #openstack-meeting22:01
*** esker has joined #openstack-meeting22:02
*** kencjohnston has quit IRC22:02
*** rossella_s has quit IRC22:02
*** rossella_s has joined #openstack-meeting22:03
*** vhoward has quit IRC22:03
*** shashank_hegde has joined #openstack-meeting22:03
*** JRobinson__ has joined #openstack-meeting22:04
*** thangp has left #openstack-meeting22:05
*** suhani has quit IRC22:06
*** ivar-lazzaro has joined #openstack-meeting22:06
*** dkranz has joined #openstack-meeting22:07
*** egallen has quit IRC22:07
*** vijendar has joined #openstack-meeting22:09
*** vijendar has quit IRC22:09
*** piet has quit IRC22:10
*** vijendar has joined #openstack-meeting22:11
*** banix has quit IRC22:13
*** barrett1 has quit IRC22:14
*** edtubill has joined #openstack-meeting22:14
*** kencjohnston has joined #openstack-meeting22:16
*** esker has quit IRC22:16
*** aimon has joined #openstack-meeting22:18
*** lblanchard has quit IRC22:19
*** barrett1 has joined #openstack-meeting22:20
*** timcline has quit IRC22:21
*** rfolco has joined #openstack-meeting22:22
*** sdake has quit IRC22:24
*** piet has joined #openstack-meeting22:24
*** markmcclain has quit IRC22:25
*** aimon_ has joined #openstack-meeting22:26
*** sdake has joined #openstack-meeting22:26
*** markmcclain has joined #openstack-meeting22:26
*** kencjohnston has quit IRC22:27
*** dane has joined #openstack-meeting22:28
*** aimon has quit IRC22:28
*** zul has joined #openstack-meeting22:29
*** mhickey_ has quit IRC22:30
*** mhickey_ has joined #openstack-meeting22:30
*** achanda has quit IRC22:30
*** e0ne has joined #openstack-meeting22:31
*** dmorita has quit IRC22:31
*** hashar has quit IRC22:31
*** dmorita has joined #openstack-meeting22:32
*** aimon_ has quit IRC22:32
*** kebray has quit IRC22:34
*** shashank_hegde has quit IRC22:35
*** eharney has quit IRC22:35
*** zeih has quit IRC22:37
*** rtheis has quit IRC22:38
*** kencjohnston has joined #openstack-meeting22:39
*** thorst has quit IRC22:39
*** thorst has joined #openstack-meeting22:41
*** MaxPC has quit IRC22:41
*** winston-d_ has quit IRC22:42
*** zul has quit IRC22:42
*** dmorita has quit IRC22:43
*** e0ne has quit IRC22:43
*** armax_ has joined #openstack-meeting22:44
*** bvandenh has quit IRC22:45
*** armax has quit IRC22:45
*** armax_ is now known as armax22:45
*** thorst has quit IRC22:46
*** edtubill has quit IRC22:47
*** neil__ has quit IRC22:47
*** neiljerram has joined #openstack-meeting22:48
*** aimon has joined #openstack-meeting22:48
*** balajiiyer has left #openstack-meeting22:48
*** bhunter71 has joined #openstack-meeting22:50
*** amitgandhinz has quit IRC22:51
*** ijw has joined #openstack-meeting22:51
*** tej has quit IRC22:51
*** piet has quit IRC22:53
*** JRobinson__ has quit IRC22:53
*** dmorita has joined #openstack-meeting22:53
*** piet has joined #openstack-meeting22:53
*** ayoung has joined #openstack-meeting22:53
*** ijw has quit IRC22:55
*** dimtruck is now known as zz_dimtruck22:56
*** tellesnobrega is now known as tellesnobrega_af22:57
*** hdaniel has quit IRC22:57
*** shashank_hegde has joined #openstack-meeting22:58
*** yassine__ has quit IRC22:58
*** aimon has quit IRC22:58
*** neiljerram has quit IRC22:58
*** aimon has joined #openstack-meeting22:59
*** vijendar has quit IRC23:00
*** thorst has joined #openstack-meeting23:00
*** neelashah has quit IRC23:03
*** adahms has joined #openstack-meeting23:04
*** aimon has quit IRC23:04
*** aimon has joined #openstack-meeting23:04
*** dkranz has quit IRC23:05
*** thorst has quit IRC23:05
*** wbhuber_ is now known as wbhuber23:07
*** JRobinson__ has joined #openstack-meeting23:07
*** neiljerram has joined #openstack-meeting23:07
*** peristeri has quit IRC23:09
*** unicell1 has joined #openstack-meeting23:09
*** dmorita has quit IRC23:10
*** unicell has quit IRC23:10
*** thorst has joined #openstack-meeting23:10
*** speller has quit IRC23:10
*** Leom has quit IRC23:11
*** Leo_ has joined #openstack-meeting23:11
*** thorst_ has joined #openstack-meeting23:11
*** su_zhang has quit IRC23:11
*** tej has joined #openstack-meeting23:11
*** dmorita has joined #openstack-meeting23:11
*** su_zhang has joined #openstack-meeting23:12
*** kencjohnston has quit IRC23:12
*** tej has quit IRC23:12
*** Leom has joined #openstack-meeting23:12
*** mhickey_ has quit IRC23:13
*** salv-orlando has quit IRC23:13
*** salv-orlando has joined #openstack-meeting23:13
*** mhickey_ has joined #openstack-meeting23:14
*** neiljerram has quit IRC23:14
*** neiljerram has joined #openstack-meeting23:14
*** thorst has quit IRC23:15
*** Leo_ has quit IRC23:16
*** Leom has quit IRC23:17
*** thorst_ has quit IRC23:17
*** thorst has joined #openstack-meeting23:18
*** e0ne has joined #openstack-meeting23:19
*** aimon_ has joined #openstack-meeting23:19
*** baoli has quit IRC23:20
*** rfolco has quit IRC23:20
*** shashank_hegde has quit IRC23:21
*** aimon has quit IRC23:22
*** aimon_ has quit IRC23:23
*** xyang1 has quit IRC23:25
*** etoews_ has quit IRC23:26
*** thorst has quit IRC23:27
*** bobh__ has quit IRC23:28
*** etoews_ has joined #openstack-meeting23:28
*** e0ne has quit IRC23:28
*** JRobinson__ has quit IRC23:28
*** mhickey_ has quit IRC23:29
*** aimon has joined #openstack-meeting23:29
*** outofmemory is now known as reedip23:31
*** haomaiwang has joined #openstack-meeting23:33
*** shashank_hegde has joined #openstack-meeting23:35
*** etoews_ has quit IRC23:36
*** Drago has quit IRC23:36
*** neiljerram has quit IRC23:37
*** haomaiwang has quit IRC23:37
*** JRobinson__ has joined #openstack-meeting23:39
*** tochi has joined #openstack-meeting23:39
*** JRobinson__ has quit IRC23:40
*** JRobinson__ has joined #openstack-meeting23:40
*** ivar-lazzaro has quit IRC23:41
*** ivar-lazzaro has joined #openstack-meeting23:42
*** shashank_hegde has quit IRC23:44
*** galstrom is now known as galstrom_zzz23:44
*** Sukhdev has quit IRC23:45
*** sdake has quit IRC23:48
*** roxanaghe_ has quit IRC23:49
*** shashank_hegde has joined #openstack-meeting23:49
*** Sukhdev has joined #openstack-meeting23:49
*** Leo_ has joined #openstack-meeting23:49
*** su_zhang has quit IRC23:51
*** su_zhang has joined #openstack-meeting23:51
*** ijw has joined #openstack-meeting23:51
*** boris-42 has quit IRC23:53
*** Leo_ has quit IRC23:54
*** aimon has quit IRC23:54
*** ijw has quit IRC23:57

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