Thursday, 2017-09-28

*** yifei has joined #openstack-meeting-400:01
*** vhosakot has quit IRC00:01
*** iyamahat has quit IRC00:01
*** baoli_ has quit IRC00:05
*** thorst has joined #openstack-meeting-400:07
*** thorst has quit IRC00:08
*** galstrom_zzz is now known as galstrom00:10
*** baoli has joined #openstack-meeting-400:20
*** galstrom is now known as galstrom_zzz00:23
*** slaweq_ has quit IRC00:27
*** woodard has quit IRC00:30
*** slaweq_ has joined #openstack-meeting-400:32
*** bcafarel has quit IRC00:44
*** nikhil has joined #openstack-meeting-400:46
*** dave-mccowan has joined #openstack-meeting-400:47
*** zhurong has joined #openstack-meeting-400:47
*** bcafarel has joined #openstack-meeting-400:51
*** kzaitsev1pi has quit IRC00:52
*** kzaitsev_pi has joined #openstack-meeting-400:54
*** slaweq_ has quit IRC01:05
*** thorst has joined #openstack-meeting-401:09
*** slaweq_ has joined #openstack-meeting-401:13
*** kevzha01 has joined #openstack-meeting-401:20
*** hongbin has joined #openstack-meeting-401:22
*** thorst has quit IRC01:23
*** thorst has joined #openstack-meeting-401:23
*** thorst has quit IRC01:26
*** julim has joined #openstack-meeting-401:34
*** bnemec has quit IRC01:34
*** bnemec has joined #openstack-meeting-401:39
*** dave-mccowan has quit IRC01:41
*** zenirc369 has joined #openstack-meeting-401:42
*** slaweq_ has quit IRC01:43
*** dave-mccowan has joined #openstack-meeting-401:45
*** slaweq_ has joined #openstack-meeting-401:50
*** bcafarel has quit IRC01:51
*** bcafarel has joined #openstack-meeting-401:58
*** dave-mcc_ has joined #openstack-meeting-402:04
*** sdague has quit IRC02:05
*** unicell has quit IRC02:06
*** dave-mccowan has quit IRC02:07
*** liuyulong has joined #openstack-meeting-402:15
*** krtaylor has joined #openstack-meeting-402:20
*** yamamoto has joined #openstack-meeting-402:22
*** yamamoto has quit IRC02:22
*** slaweq_ has quit IRC02:22
*** yamamoto has joined #openstack-meeting-402:22
*** baoli has quit IRC02:24
*** thorst has joined #openstack-meeting-402:26
*** slaweq_ has joined #openstack-meeting-402:27
*** unicell has joined #openstack-meeting-402:31
*** baoli has joined #openstack-meeting-402:34
*** unicell has quit IRC02:35
*** dave-mcc_ has quit IRC02:38
*** baoli has quit IRC02:42
*** baoli has joined #openstack-meeting-402:44
*** Rockyg has joined #openstack-meeting-402:50
*** nikhil has quit IRC02:55
*** slaweq_ has quit IRC03:00
*** janki has joined #openstack-meeting-403:09
*** slaweq_ has joined #openstack-meeting-403:09
*** zenirc369 has quit IRC03:11
*** jamesbenson has joined #openstack-meeting-403:12
*** idan_hefetz has joined #openstack-meeting-403:13
*** idan_hefetz has quit IRC03:14
*** Sukhdev has quit IRC03:15
*** dgonzalez has quit IRC03:16
*** jamesbenson has quit IRC03:16
*** dgonzalez has joined #openstack-meeting-403:21
*** baoli has quit IRC03:21
*** baoli has joined #openstack-meeting-403:22
*** Sukhdev has joined #openstack-meeting-403:24
*** bnemec has quit IRC03:26
*** Mmike has quit IRC03:33
*** baoli has quit IRC03:34
*** Mmike has joined #openstack-meeting-403:38
*** slaweq_ has quit IRC03:41
*** links has joined #openstack-meeting-403:44
*** slaweq_ has joined #openstack-meeting-403:45
*** zhurong has quit IRC04:07
*** slaweq_ has quit IRC04:18
*** slaweq_ has joined #openstack-meeting-404:24
*** hongbin has quit IRC04:31
*** Rockyg has quit IRC04:42
*** psachin has joined #openstack-meeting-404:52
*** slaweq_ has quit IRC04:56
*** slaweq_ has joined #openstack-meeting-405:03
*** zenirc369 has joined #openstack-meeting-405:25
*** Sukhdev has quit IRC05:29
*** aavraham has joined #openstack-meeting-405:30
*** chyka has quit IRC05:31
*** slaweq_ has quit IRC05:33
*** slaweq_ has joined #openstack-meeting-405:43
*** mrunge_ is now known as mrunge06:00
*** iyamahat has joined #openstack-meeting-406:02
*** iyamahat has quit IRC06:16
*** liuyulong has quit IRC06:17
*** pcaruana has joined #openstack-meeting-406:19
*** coolsvap has joined #openstack-meeting-406:20
*** mrunge has quit IRC06:22
*** mrunge has joined #openstack-meeting-406:27
*** markvoelker has quit IRC06:30
*** zhurong has joined #openstack-meeting-406:37
*** slaweq_ has quit IRC06:46
*** jamesbenson has joined #openstack-meeting-406:48
*** jamesbenson has quit IRC06:52
*** slaweq_ has joined #openstack-meeting-406:53
*** makowals has joined #openstack-meeting-406:53
*** idan_hefetz has joined #openstack-meeting-407:00
*** andymccr has quit IRC07:07
*** asettle has quit IRC07:08
*** andymccr has joined #openstack-meeting-407:09
*** asettle has joined #openstack-meeting-407:10
*** asettle is now known as Guest382807:10
*** arcolife has joined #openstack-meeting-407:11
*** reedip has quit IRC07:14
*** iyamahat has joined #openstack-meeting-407:14
*** ralonsoh has joined #openstack-meeting-407:19
*** kevzha01 has quit IRC07:26
*** kevzha01 has joined #openstack-meeting-407:26
*** slaweq_ has quit IRC07:27
*** reedip has joined #openstack-meeting-407:28
*** anilvenkata|AFK is now known as anilvenkata07:29
*** slaweq_ has joined #openstack-meeting-407:30
*** egonzalez has joined #openstack-meeting-407:50
*** yamamoto has quit IRC07:56
*** slaweq_ has quit IRC08:02
*** yamamoto has joined #openstack-meeting-408:03
*** slaweq_ has joined #openstack-meeting-408:09
*** iyamahat has quit IRC08:10
*** eglute has quit IRC08:14
*** eglute has joined #openstack-meeting-408:14
*** alexchadin has joined #openstack-meeting-408:22
*** yamamoto has quit IRC08:25
*** yamamoto has joined #openstack-meeting-408:30
*** markvoelker has joined #openstack-meeting-408:31
*** yamamoto_ has joined #openstack-meeting-408:32
*** yamamoto_ has quit IRC08:34
*** yamamoto has quit IRC08:35
*** yamahata has joined #openstack-meeting-408:36
*** Guest3828 is now known as asettle08:39
*** slaweq_ has quit IRC08:43
*** yamahata has quit IRC08:46
*** yamahata has joined #openstack-meeting-408:47
*** alexchadin has quit IRC08:50
*** alexchadin has joined #openstack-meeting-408:51
*** alexchadin has quit IRC08:51
*** alexchadin has joined #openstack-meeting-408:51
*** slaweq_ has joined #openstack-meeting-408:54
*** yujunz has joined #openstack-meeting-408:57
*** ralonsoh_ has joined #openstack-meeting-409:00
*** alexchadin has quit IRC09:01
*** alexchadin has joined #openstack-meeting-409:03
*** ralonsoh has quit IRC09:03
*** markvoelker has quit IRC09:05
*** yamamoto has joined #openstack-meeting-409:14
*** yamamoto has quit IRC09:17
*** yujunz has quit IRC09:19
*** salmankhan has joined #openstack-meeting-409:20
*** sambetts|afk is now known as sambetts09:24
*** slaweq_ has quit IRC09:26
*** kevzha01 has quit IRC09:27
*** alexchad_ has joined #openstack-meeting-409:28
*** alexchadin has quit IRC09:30
*** alexchad_ has quit IRC09:32
*** alexchadin has joined #openstack-meeting-409:33
*** slaweq_ has joined #openstack-meeting-409:36
*** salmankhan has quit IRC09:39
*** yamahata has quit IRC09:40
*** salmankhan has joined #openstack-meeting-409:40
*** idan_hefetz has quit IRC09:42
*** sdague has joined #openstack-meeting-409:44
*** yifei has quit IRC09:48
*** woodard has joined #openstack-meeting-409:51
*** jamesbenson has joined #openstack-meeting-409:56
*** ltomasbo has quit IRC09:59
*** jamesbenson has quit IRC10:00
*** markvoelker has joined #openstack-meeting-410:02
*** yamamoto has joined #openstack-meeting-410:03
*** ralonsoh__ has joined #openstack-meeting-410:03
*** ltomasbo has joined #openstack-meeting-410:04
*** yamamoto has quit IRC10:05
*** ralonsoh_ has quit IRC10:06
*** slaweq_ has quit IRC10:09
*** reedip has quit IRC10:12
*** chyka has joined #openstack-meeting-410:16
*** slaweq_ has joined #openstack-meeting-410:17
*** janki has quit IRC10:20
*** chyka has quit IRC10:21
*** ralonsoh__ is now known as ralonsoh10:24
*** reedip has joined #openstack-meeting-410:26
*** zhurong has quit IRC10:27
*** yamamoto has joined #openstack-meeting-410:29
*** janki has joined #openstack-meeting-410:30
*** yamamoto has quit IRC10:31
*** idan_hefetz has joined #openstack-meeting-410:32
*** alexchadin has quit IRC10:32
*** markvoelker has quit IRC10:35
*** iyamahat has joined #openstack-meeting-410:35
*** iyamahat has quit IRC10:36
*** iyamahat_ has joined #openstack-meeting-410:36
*** yamamoto has joined #openstack-meeting-410:37
*** yamamoto has quit IRC10:38
*** yamamoto has joined #openstack-meeting-410:40
*** yamamoto has quit IRC10:43
*** yamamoto has joined #openstack-meeting-410:46
*** yamamoto has quit IRC10:49
*** slaweq_ has quit IRC10:53
*** seajay has joined #openstack-meeting-411:08
*** thorst has quit IRC11:16
*** slaweq_ has joined #openstack-meeting-411:23
*** pbourke has quit IRC11:25
*** pbourke has joined #openstack-meeting-411:25
*** yamamoto has joined #openstack-meeting-411:28
*** markvoelker has joined #openstack-meeting-411:32
*** ansmith has quit IRC11:42
*** slaweq_ has quit IRC11:57
*** slaweq_ has joined #openstack-meeting-412:01
*** yamamoto has quit IRC12:03
*** bobh has joined #openstack-meeting-412:03
*** thorst has joined #openstack-meeting-412:03
*** markvoelker has quit IRC12:06
*** iyamahat_ has quit IRC12:06
*** reedip has quit IRC12:07
*** bobh has quit IRC12:07
*** woodard has quit IRC12:11
*** woodard has joined #openstack-meeting-412:12
*** markvoelker has joined #openstack-meeting-412:18
*** reedip has joined #openstack-meeting-412:20
*** pcaruana has quit IRC12:31
*** slaweq_ has quit IRC12:34
*** yifei has joined #openstack-meeting-412:41
*** slaweq_ has joined #openstack-meeting-412:44
*** yifei has quit IRC12:45
*** ansmith has joined #openstack-meeting-412:50
*** dave-mccowan has joined #openstack-meeting-412:54
*** lyan has joined #openstack-meeting-412:55
*** bobh has joined #openstack-meeting-412:56
*** pcaruana has joined #openstack-meeting-413:00
*** belmoreira has joined #openstack-meeting-413:01
*** yamamoto has joined #openstack-meeting-413:03
*** iyamahat has joined #openstack-meeting-413:04
*** iyamahat has quit IRC13:05
*** iyamahat has joined #openstack-meeting-413:05
*** belmoreira has quit IRC13:06
*** belmorei_ has joined #openstack-meeting-413:07
*** belmorei_ has quit IRC13:07
*** belmoreira has joined #openstack-meeting-413:07
*** cleong has joined #openstack-meeting-413:08
*** yamamoto has quit IRC13:09
*** idan_hefetz has quit IRC13:10
*** arcolife has quit IRC13:12
*** pmesserli has joined #openstack-meeting-413:13
*** baoli has joined #openstack-meeting-413:16
*** slaweq_ has quit IRC13:17
*** lyan has quit IRC13:20
*** slaweq_ has joined #openstack-meeting-413:24
*** alexchadin has joined #openstack-meeting-413:28
*** zenirc369 has quit IRC13:31
*** jrist has quit IRC13:31
*** yamahata has joined #openstack-meeting-413:33
*** jrist has joined #openstack-meeting-413:35
*** woodard has quit IRC13:35
*** iyamahat has quit IRC13:35
*** VW has joined #openstack-meeting-413:41
*** smcginnis has joined #openstack-meeting-413:45
*** bnemec has joined #openstack-meeting-413:53
*** alex_xu has quit IRC13:54
*** alex_xu has joined #openstack-meeting-413:54
*** slaweq_ has quit IRC13:56
*** belmoreira has quit IRC13:57
*** shintaro has joined #openstack-meeting-413:58
*** nikhil has joined #openstack-meeting-413:58
*** rosmaita has joined #openstack-meeting-413:59
rosmaita#startmeeting glance14:00
openstackMeeting started Thu Sep 28 14:00:22 2017 UTC and is due to finish in 60 minutes.  The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
rosmaita#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: glance)"14:00
jokke_o/14:00
*** arcolife has joined #openstack-meeting-414:01
*** yamahata has quit IRC14:01
*** gb21 has joined #openstack-meeting-414:01
rosmaitalooks like not a big turnout14:01
gb21Hi @rosmaita14:02
*** alex_xu has quit IRC14:02
arcoliferosmaita, Hello14:02
jokke_moar peoples! :D14:02
*** links has quit IRC14:02
smcginniso/14:02
rosmaitaok, hello everyone14:03
rosmaita#topic updates14:03
*** openstack changes topic to "updates (Meeting topic: glance)"14:03
nikhilo/14:03
rosmaitanikhil!14:03
rosmaitafirst update: spec proposal freeze is now in effect14:03
*** belmoreira has joined #openstack-meeting-414:03
nikhilHa, yes that's me :)14:03
*** slaweq_ has joined #openstack-meeting-414:03
*** spzala has joined #openstack-meeting-414:03
gb21Hi @nikhil14:04
rosmaitai'll put up a patch later opening a 'rocky' directory for new proposals14:04
nikhilOhai gb2114:04
rosmaitaalso, you may have noticed that i'm changing the way we do lite specs14:04
rosmaitai had to put up like 5 of them yesterday, and don't want to deal with merge conflicts14:04
jokke_rosmaita: ref that, if the "copy-from" needs its own, I can get that written over the weekend14:04
jokke_if not we can just point to the IIR spec14:05
rosmaitaso i'll be changing the spec-lite template14:05
rosmaitajokke_ : i was thinking just use the original IIR spec14:05
rosmaitaanyway, the key point is that we all need to review specs so that people can meet the deadline for the spec freeze14:06
belmoreiraHi everyone14:06
jokke_rosmaita: I noticed ... that will still get messy on the spec page so we might want to put them to their own dir and have the page generated from those for specs.openstack.org14:06
rosmaitawhich is next Friday, 5 oct14:06
*** VW has quit IRC14:06
rosmaitajokke_ : let's wait until the spec page actually gets messy14:06
rosmaitai figure "messy" == more than 10 titles14:06
rosmaitaor say, 12, an even dozen14:07
*** VW has joined #openstack-meeting-414:07
rosmaitai think we will be under that14:07
jokke_rosmaita: indeed ^^, thus I +2'd most of yours earlier ;)14:07
rosmaitabut i do see your point, it's an evolving process!14:07
rosmaitaok, that's it for updates ... if people want to discuss specific aspects of some of the specs, we can do that in general discussion14:08
rosmaitawhich we should have plenty of time for, light agenda today14:08
rosmaitanikhil : someone has posted a quotas spec, you might want to take a look14:09
nikhilSure14:09
rosmaita#topic image import testing14:09
*** openstack changes topic to "image import testing (Meeting topic: glance)"14:09
belmoreirarosmaita what's the priority for quotas?14:09
rosmaitabelmoreira: don't know, it really depends on whether the proposers are serious about working on them or not14:10
rosmaitawe are going to be low on reviewer bandwidth, so they'd need to happen early in the cycle14:10
rosmaitabut also, i haven't looked at the proposal yet14:10
rosmaitait needs to be consistent with the plans to eventually store limits in keystone14:11
jokke_so I did poke our QE folks for help. By the looks of it they are quite busy trying to get their queues cleaned before Israel shuts down, so I assume no help from there short term. Abhishek promised to start working on those next week os will sync up with him14:11
rosmaitabecause we don't want to do this twice14:11
*** VW has quit IRC14:11
rosmaitayeah, back to the image import testing14:11
arcolifeI've seen nikhil's video on youtube regarding an interoperable sprint, about 1 year ago.. ?  read the docs and etherpad, have an idea.  is14:12
arcolifedo we have a time for a quick video chat to summarize things for me to get started ?14:12
arcolifehttps://etherpad.openstack.org/p/glance-image-import-tests14:12
belmoreirarosmaita my understanding is that the work in keystone limits is stale.14:12
arcolifethese are what we'd like in there? and there's 0 work regarding that ?14:12
arcolife^^14:12
rosmaitaarcolife: yes, that;'s the initial list of stuff14:12
rosmaitabelmoreira: let's hold off on quotas until open discussion14:13
rosmaitaarcolife: you are interested in working on the import tests, i take it?14:13
arcoliferosmaita, yes, that's what seems available atm ?14:13
arcolifeis there anything else higher priority and starting point ?14:13
jokke_arcolife: what timezone you're on? Abhishek is utc +5.5 IIRC so it would likely be super helpful to catch up with him on the testing work14:14
gb21@rosmaita, I am willing to work along arcolife on the tests14:14
arcolifejokke_, utc+5:3014:14
rosmaitagb21 tha's great14:14
arcolifeyep same14:14
jokke_I'm sure he will be more than happy to have helping hands there and I'll do what ever I can to help out14:14
jokke_arcolife: brilliant. Do you know Abhishek?14:14
arcolifejokke_, we started an email thread :)14:15
rosmaitaarcolife: sorry, did not recognize your nick14:15
jokke_:)14:15
arcoliferosmaita, ah. :D14:15
rosmaitaarcolife why don't you ping abhishek and set up a time to talk with him?14:15
rosmaitathat way you can all talk at a reasonable hour14:16
rosmaitaalso, we should all wish Abhishek's daughter a happy birthday14:16
rosmaita(that's why he's not here)14:16
arcoliferosmaita, thought we'd be doing a thurs knowledge sharing session. realized it's an irc scrum later.14:16
arcolifegoodies. will setup a mtg now14:16
*** jrist has quit IRC14:17
jokke_arcolife: if you schedule something around this with Abhishek and you manage to get it to your afternoon, feel free to count me in, I'll try to make time for it14:17
arcolifejokke_, 3.5 hrs behind 5.5  are we?14:18
jokke_arcolife: I'm in Ireland so 5.5 behind you guys14:18
arcolifegotcha14:18
jokke_and no, I won't be waking up silly-o-clock for that ... but voluteered as I'm sure rosmaita won't either to join us :P14:18
jokke_and I don't want to hold you guys working until super late just to get us all there14:19
rosmaitawell, depends on what time you all agree on :)14:19
arcoliferosmaita, iteroperable image import, there was a discussion an year back on YT in a sprint. we were concerned about not letting too much leeway for people to add non-standardized import formats ?14:19
rosmaitaarcolife right, you can look over the original spec to see all the issues and how they're being addressed for interoperability14:20
rosmaita#link https://specs.openstack.org/openstack/glance-specs/specs/mitaka/approved/image-import/image-import-refactor.html14:20
jokke_arcolife: prepare full pot of coffee ... that will take a while to digest ... good bedtime reading 'though14:20
rosmaitaalso, you can look in the current api-ref to see what's been implemented so far14:20
nikhilLook at the review of the spec too14:20
nikhilThat will help much more14:21
arcoliferoger that 0_014:21
rosmaita#link https://developer.openstack.org/api-ref/image/v2/#interoperable-image-import14:21
rosmaitahere's the review nikhil mentioned:14:23
rosmaita#link https://review.openstack.org/#/c/232371/14:23
rosmaitaand also14:23
rosmaita#link https://review.openstack.org/#/c/278086/14:23
rosmaitaand also14:23
rosmaita#link https://review.openstack.org/#/c/318313/14:23
rosmaitathat should keep you busy for a while!14:24
nikhil;)14:24
rosmaitaalso, there's a section in the glance admin docs about how to turn on image import14:24
rosmaita#link https://docs.openstack.org/glance/latest/admin/interoperable-image-import.html14:25
rosmaitaand then of course there's the code14:25
*** arcolife_ has joined #openstack-meeting-414:25
*** gb21 has quit IRC14:26
rosmaitaanyway, please organize a chat with abhishekk and you can get started ... glad to have you helping us out with testing!14:26
*** arcolife has quit IRC14:26
arcolife_rosmaita, referring to this link (lost you after #link) http://eavesdrop.openstack.org/meetings/glance/2017/glance.2017-09-28-14.00.log.txt )14:26
arcolife_rosmaita, glad to be a part. cheers. will read up and get back14:27
rosmaitaok, cool ... ty~14:27
*** gb21 has joined #openstack-meeting-414:27
rosmaitaok, time for open discussion14:27
rosmaita#topic open discussion14:27
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:27
rosmaitaok, i've got one14:29
rosmaitai need some feedback on https://review.openstack.org/#/c/468179/14:29
* arcolife_ too14:29
rosmaitajokke_ doesn't like it14:29
rosmaitabut i think he is being unreasonable14:29
rosmaitabut that's just me14:29
rosmaitaso it would be good to get some wider opinions14:30
* smcginnis opens tab14:30
rosmaitaand maybe i should take tim bell's advice and do an operator survey14:30
smcginnisrosmaita: Maybe even just an email to openstack-operators to get some feedback?14:30
rosmaitasmcginnis yeah, maybe that would be quicker14:31
belmoreiraopenstack-operators will be good. I need to revive my memory about it14:31
belmoreirajust uploaded https://review.openstack.org/#/c/508133/ few hours ago. Can it be considered for this cycle?14:32
rosmaitaok, i'll do that and we can get some operator feedback14:32
rosmaitabelmoreira yes, you got it in before the proposal freeze14:32
rosmaitai haven't looked it over yet14:33
rosmaitaso not sure what resources it requires14:33
rosmaitabut i'll read and comment later today14:33
rosmaitaand we can continue the discussion on the patch14:33
belmoreiraI think it needs some iterations but it will be great to have feedback and new ideas on it14:34
rosmaitasounds good14:34
rosmaitabelmoreira honestly, i doubt we will have dev resources to do it in queens14:34
rosmaitaunless you have a dev team available?14:34
jokke_belmoreira: that touches very very closely to the Image Lifecycle discussion we had in PTG14:34
rosmaitabut if we can get it refined before the sydney summit, and get feedback at the summit/forum, maybe it can be ready to do early in rocky14:35
belmoreirathis was based in the discussion in the mailing list and the other spec that is as reference14:35
rosmaitaok, well i should shut up and read it14:35
*** hongbin has joined #openstack-meeting-414:35
rosmaitano sense speculating about how much effort it will take without knowing what it's about :)14:36
belmoreiraI think it will be more to trigger discussing than having an implementation immediately. let's see14:37
belmoreiraand about quotas?14:37
*** slaweq_ has quit IRC14:37
rosmaitasure, what are your thoughts about quotas?14:37
jokke_belmoreira: so I'd be pretty confident saying that your proposal will not be done, but that said you might end up with something like "stale":true that is not listed by default14:38
jokke_we will most likely not be filtering by default based on any given property needing to be set14:38
*** dave-mccowan has quit IRC14:39
jokke_but having property, set of properties that is basis for something fitered out of the list is way more likely to go through14:39
belmoreirajokke_ it will be great to have feedback and find a good solution for this problem14:39
belmoreiraabout quotas... I feel that a solution in glance is being postponed for a long time14:39
rosmaitayou are right about that!14:40
*** spotz_ is now known as spotz14:40
jokke_belmoreira: there is light capture of what we were brainstorming in https://etherpad.openstack.org/p/glance-queens-ptg-lifecycle14:40
belmoreiraI agree about the dependencies (limits, hierarchical projects...) but it will be great if we find a compromise14:41
jokke_ok so what comes to quotas, we had some people working on that cycles ago14:42
nikhilMaybe the dependency on hierarchical is gone? rosmaita ?14:42
*** kevzha01 has joined #openstack-meeting-414:43
rosmaitaso this is the spec that was proposed: https://review.openstack.org/#/c/487777/14:43
rosmaitai thought it had been updated, but apparently not14:43
belmoreiraas private cloud that don't charge the users I rely on quotas. Deployments like mine can't control the image utilization. Any user can basically use all our storage for images.14:43
jokke_the work got halted as there was supposed to be first cross project spec how this is done across projects, then it moved to Keystone coordinating it and providing the tools (read storing the actual quotas) and like some of you mentioned earlier it has been pretty quiet lately14:43
nikhilAck ,ty14:44
*** dave-mccowan has joined #openstack-meeting-414:44
*** kevzha01_ has joined #openstack-meeting-414:45
rosmaitabelmoreira there is a user_storage_quota, but i guess that is insufficient for your use case?14:45
*** slaweq_ has joined #openstack-meeting-414:45
jokke_so I'm frankly not interested to talk about Glance specific solution again unless 1) we get OS community agreement that this is not going to be done "ever" as coordinated effort or 2) that coordinated effort moves to the point where we can use it and be aligned14:46
belmoreirain my case needs to be very large because some projects actually need it, but then all projects have that large quota available14:46
rosmaitabelmoreira i understand14:46
rosmaitabelmoreira are you at CERN?14:47
nikhilbelmoreira: what storage backends do you use? Fs, swift, cinder?14:47
*** kevzha01 has quit IRC14:48
*** alexchadin has quit IRC14:48
belmoreirait would be great have a basic quota system (allowed used_space per project). That would solve my problem. And then we can iterate for the common solution with the other projects14:48
belmoreirarosmaita yes, I'm at CERN14:48
belmoreiranikhil we use ceph14:48
nikhilAck14:49
*** makowals has quit IRC14:49
rosmaitabelmoreira is storage your only concern?14:49
belmoreiraat the moment our ceph poll only for images has 200TB14:49
jokke_belmoreira: that actually makes the thing bit more difficult :P14:49
jokke_belmoreira: IIRC your snapshots actually shows up as 0 size images in glance :(14:50
belmoreirarosmaita that is my bigger concern. If I can limit the amount of space that a project can use the number of images/snapshots is not a very big issue14:51
belmoreirajokke_ wow. I didn't noticed14:51
rosmaitayeah, but if jokke_ is correct, we won't be able to enforce it accurately14:51
jokke_belmoreira: not 100% sure about that, but I remember discussion not so long ago. Apparently when Nova uses the ceph backend together with Glance it does not populate the size as the snapshot image is never streamed through glance API14:53
belmoreirabut is that should be the case for nova ephemeral storage with ceph14:53
belmoreirawe use the local storage in the compute nodes14:54
jokke_so implementing quota that can't handle again that special case with Ceph is one of those things that is just security bug waiting to be filed14:54
jokke_belmoreira: oh, so you're not affected by that very specific thing then14:54
belmoreirajokke_ I believe not. I never noticed that snapshots are marked with 0 size. But what you mentioned adds complexity in finding a proper solution14:55
rosmaitawell, i've been thinking as quotas as a broad topic, but if we limit it to storage only, might be a good stopgap (assuming htere's a good way around the 0-size snapshot problem)14:56
jokke_belmoreira: indeed14:56
rosmaitai imagine the 0 size is because nova is using user creds, and not allowed to set size on the image record?14:56
jokke_rosmaita: I think that would need poking the locations code (and I'm not sure how ceph reports the size of snapshots)14:57
jokke_rosmaita: I think that might be the case14:57
jokke_rosmaita: yet another thing that could be solved with the service tokens14:57
rosmaitai was just about to say that14:57
rosmaitawe need to get a good sense of how stable the service token stuff is in keystone14:58
jokke_++14:58
rosmaitabecause there are several improvements we could make if we use them14:58
jokke_but my main point on that was, that as long as we have these kind of "show stoppers" there is really no good way to make that happen14:58
rosmaitawe're running low on time14:58
rosmaitai think the first step would be figuring out what's necessary to get accurate image size reporting in glance14:59
*** jrist has joined #openstack-meeting-414:59
rosmaitaand after that, we can tackle a simple quota for space consumed per tenant14:59
jokke_Also if that quotas need is big enough, it might be good opportunity to get first quota type into keystone and file down how that is going to look like in larger scale14:59
rosmaitano sense going for a quota if we can't accurately measure what's limited14:59
*** belmorei_ has joined #openstack-meeting-414:59
arcolife_rosmaita, the service token thing blew up for >100 tenants w/ CFME https://bugzilla.redhat.com/show_bug.cgi?id=147637114:59
openstackbugzilla.redhat.com bug 1476371 in -- Unknown "CFME has multiple issues adding OSP 8 and OSP 10 as providers with >100 projects/tenants via AD CF User" [Low,New] - Assigned to jhardy14:59
rosmaitaarrrrgh15:00
rosmaitaarcolife_ thanks for that link, will take a look15:00
arcolife_we fixed that partially with new patches of cfme.15:00
jokke_thanks all!15:00
*** belmoreira has quit IRC15:00
rosmaitaok, we are out of time, thanks everyone15:00
nikhilThanks15:00
rosmaitacontinue discussion in glance channel if you want15:00
arcolife_but the fix relies on generating 100k tokens or so, per 24 hrs. it was going much more than that/15:00
arcolife_cool. thanks all15:00
rosmaita#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu Sep 28 15:00:46 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2017/glance.2017-09-28-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2017/glance.2017-09-28-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2017/glance.2017-09-28-14.00.log.html15:00
gb21Thanks15:00
*** gb21 has left #openstack-meeting-415:01
*** arcolife_ has quit IRC15:02
*** shintaro has quit IRC15:02
*** lei-zh has joined #openstack-meeting-415:03
*** smcginnis has left #openstack-meeting-415:05
*** dave-mcc_ has joined #openstack-meeting-415:07
*** sdague has quit IRC15:07
*** jamesbenson has joined #openstack-meeting-415:07
*** lei-zh has quit IRC15:09
*** dave-mccowan has quit IRC15:09
*** sjmc7 has joined #openstack-meeting-415:13
sjmc7#startmeeting openstack search15:13
openstackMeeting started Thu Sep 28 15:13:53 2017 UTC and is due to finish in 60 minutes.  The chair is sjmc7. Information about MeetBot at http://wiki.debian.org/MeetBot.15:13
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:13
*** openstack changes topic to " (Meeting topic: openstack search)"15:13
openstackThe meeting name has been set to 'openstack_search'15:13
sjmc7Sorry I’m so late; got caught up in something15:14
*** spzala has quit IRC15:14
sjmc7Will give it a few minutes to see who’s about. The only news I really have is that we have the dubious distinction of being the first project to go into maintenance mode - https://review.openstack.org/#/c/502849/15:16
*** lei-zh has joined #openstack-meeting-415:17
sjmc7Hopefully activity will pick up and we can reevaluate that, but for now it seems like a good call. Thanks to Brian for sorting that out15:17
lei-zh\o15:17
lei-zhsorry I'm late15:17
sjmc7I was too :)15:18
lei-zhI guess you are talking about maintenance mode15:18
jokke_sjmc7: I'm happy that was option you guys decided to go for instead of letting the project being closed off15:18
*** slaweq_ has quit IRC15:18
*** bobmel has quit IRC15:19
sjmc7yep lei-zh15:19
sjmc7jokke_: yeah, me too. we’re actually using it internally a lot, and my hope is that we can pick back up again15:19
sjmc7so many companies drastically scaled back their commitment to openstack that it hit us pretty hard15:19
jokke_sjmc7: well we were discussing about searchlight with some people during the PTG and the reality is that the problem it's solving has not gone away15:20
sjmc7yeah… one thing that we’ve found it really good for is for delpoyments with lots of regions15:20
jokke_and there's stuff like Lifecycle Management that could utilize lots of the info you're already providing to improve those things15:20
jokke_I can see that!15:21
*** psachin has quit IRC15:21
* jokke_ makes mental note to bring that pointer up15:21
sjmc7yep. the project in the state it’s in works; i’m going to keep an eye on nova so we can hopefully move fully onto just consuming notifications, but i think it’s a good decision to make a note of projects with little activity so consumers aren’t deceived15:22
sjmc7there’re still people who can work on it part time so we can fix bugs etc15:22
jokke_yeah ... and that maintenance mode governance is there for good reason ... not everything needs to be in crazy full blast development all the time15:23
sjmc7yeah. i’m honored we’re the first to use it (i think?)15:23
jokke_as long as the health is monitored/taken care of that's brilliant if you're in the spot you can tell that "Hey, we're done(ish) we keep looking for security bugs and changes on our dependencies to keep the things that way)15:24
sjmc7yeah. there’s stuff i’d like to have got to, but it’s hard if nobody’s being paid to do it :)15:24
jokke_that was like Plan C or D for Glance earlier this year, fortunately we did not need to do it because the reasoning would have been "wrong"15:25
sjmc7well, glance is one of the ‘too big to fail’ projects15:25
jokke_and the interest might surface to do those things more when there is no demand or expectation of tight timelines and big changes every cycle15:26
sjmc7so it is a different scenario. i think with the explosion of projects after the big tent change, there’ll be more that find themselves in our boat15:26
sjmc7yep15:26
jokke_well sorry to take over your meeting time. Just wanted to bring up that the situation did not go unnoticed ;)15:27
*** aavraham has left #openstack-meeting-415:28
*** TravT has joined #openstack-meeting-415:28
TravTo/15:28
sjmc7yeah, appreciate it, and sorry i couldn’t be at the PTG to fight our corner15:28
sjmc7again, i really appreciate brian’s involvement15:29
TravT+215:29
sjmc7hey. we were just wrapping up15:29
TravTsorry, i got pulled into another meeting15:30
*** woodard has joined #openstack-meeting-415:30
*** slaweq_ has joined #openstack-meeting-415:30
sjmc7did anyone have any other topics they wanted to discuss?15:31
sjmc7ok, in that case i guess i’ll end it here15:34
sjmc7thanks everyone. thanks jokke_ for your interest!15:34
*** krtaylor__ has quit IRC15:34
*** jrist has quit IRC15:36
sjmc7#endmeeting15:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:36
openstackMeeting ended Thu Sep 28 15:36:46 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2017/openstack_search.2017-09-28-15.13.html15:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2017/openstack_search.2017-09-28-15.13.txt15:36
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2017/openstack_search.2017-09-28-15.13.log.html15:36
*** mgariepy has joined #openstack-meeting-415:39
*** lei-zh has quit IRC15:42
*** spzala has joined #openstack-meeting-415:44
*** annp has joined #openstack-meeting-415:45
*** kevzha01_ has quit IRC15:47
*** spzala has quit IRC15:48
*** belmorei_ has quit IRC15:51
*** iyamahat has joined #openstack-meeting-415:52
*** chyka has joined #openstack-meeting-415:53
*** egonzalez has quit IRC15:59
evrardjpo/15:59
hwoarango/16:00
spotzHey all16:01
*** sbezverk has quit IRC16:01
evrardjphey16:01
spotz#startmeeting openstack_ansible_meeting16:01
spotz#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:01
spotz#topic Roll Call16:01
openstackMeeting started Thu Sep 28 16:01:50 2017 UTC and is due to finish in 60 minutes.  The chair is spotz. 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_ansible_meeting)"16:01
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:01
*** openstack changes topic to "Roll Call (Meeting topic: openstack_ansible_meeting)"16:01
evrardjpo/16:02
* hwoarang is around16:02
evrardjpin da place even!16:02
*** slaweq_ has quit IRC16:02
spotzLet's see if we get anyone else as it's a short agenda16:03
*** krtaylor__ has joined #openstack-meeting-416:04
evrardjpwell I have things to say, let's hope at least some ppl will listen :p16:04
*** annp has quit IRC16:04
logan-o/16:04
spotz:)16:04
spotzhehe I was getting my reping ready:)16:05
jmccroryo/16:05
evrardjpworks apparently :)16:06
spotz#topic Forum @ Sydney Summit - 6-8 November - Sydney, AU16:06
*** openstack changes topic to "Forum @ Sydney Summit - 6-8 November - Sydney, AU (Meeting topic: openstack_ansible_meeting)"16:06
*** slaweq_ has joined #openstack-meeting-416:06
spotz#link https://etherpad.openstack.org/p/osa-sydney-summit-planning16:06
evrardjpok for the forum, I proposed a generic "ops" session16:06
spotzMakes sense, there going to be onboarding again?16:07
evrardjpplease don't hesitate to add the things you'd like to talk/have a feedback about (whether you can attend or not)16:07
evrardjpI don't know16:07
evrardjpthere is a hackathon before16:07
evrardjpBut it seems it's already organized and I am not sure we can simply join16:08
cloudnullo/16:08
*** prometheanfire has joined #openstack-meeting-416:08
prometheanfireo/16:08
*** lyan has joined #openstack-meeting-416:08
evrardjpI think that's all we can say16:08
evrardjpnext topic?16:09
spotzevrardjp: hackathon is different there is the Upstream Institute before hand which is more open intro and some onboarding as well16:09
spotz#topic Release Planning and Decisions16:09
*** openstack changes topic to "Release Planning and Decisions (Meeting topic: openstack_ansible_meeting)"16:09
spotzthat's you:)16:09
evrardjpyeah that's a big topic16:10
evrardjpat least today16:10
evrardjplet's start with the easy things16:10
*** kbyrne has quit IRC16:10
cloudnullre: sydney, I talked to robin from ansible the other day16:10
*** jrist has joined #openstack-meeting-416:10
evrardjpcloudnull: go ahead16:10
cloudnullthey're planning an ansible day16:10
cloudnullit be good to contribute16:10
evrardjpoh great16:10
evrardjpyes indeed. Let's be present!16:11
cloudnullthey're also going to do a couple talks/meetups16:11
cloudnullitd be good to participate there too16:11
spotzDefinitely16:11
evrardjpthanks for the networking cloudnull! :D16:11
cloudnullI think they're still looking for folks to join pannels etc16:11
evrardjpif you know more, ping me. I will deal with it :)16:12
*** kbyrne has joined #openstack-meeting-416:12
evrardjpok to go back to releases16:12
prometheanfireisn't she still around castle today?16:12
evrardjpI have submitted releases for Pike and Ocata, which are right now stuck in infra/releases limbo. I will track that to get a release soon16:13
evrardjpNewton will get the same treatment16:13
evrardjpthis way we have aligned releases16:13
prometheanfireis this the last newton, or does osa have one more?16:13
spotzWhat are we going to do about newton-EOL, will that affect the COA as it uses our stuff16:13
evrardjp(I will come back to that later)16:13
logan-is the virt type fix in this ocata tag?16:14
evrardjpso, before that16:14
evrardjpP and O have will have a tag that includes libvirt qemu instead of kvm fix16:14
evrardjphowever they won't have the centos fix you included logan-16:14
logan-ok16:15
logan-cool16:15
evrardjpI'd rather leave the patches as is, and if we consider it critical, bump directly in the integrated repo, this way it's included for next release for sure16:15
evrardjpthe current "release" patches as is16:16
evrardjpso it brings me to the big topic I wanted to discuss about releases16:16
evrardjpHow we will do releases in the future16:16
evrardjpIn the future, we'll continue to have 2 week's release schedule16:16
evrardjpand we can continue to submit "emergency" releases in case of security issues16:17
evrardjpbut I'd like this process to be straightforward for anyone16:17
evrardjpso I am cleaning the release process, in order for anyone to be able to submit a release.16:17
evrardjpThis way, no bus factor or anything :p16:17
evrardjpIn the future, the two week schedule should be aligned with the end of month16:18
evrardjpthis way we'll always release before end of month, and people at the beggining of the month can consume a new OpenStack-Ansible16:19
*** corey_ has joined #openstack-meeting-416:19
evrardjpThere will still be room at the community meeting to discuss about the "end of month" release16:19
*** cleong has quit IRC16:20
evrardjpbut these discussions should be fairly limited16:20
*** zenirc369 has joined #openstack-meeting-416:20
evrardjpthe idea behind all of that is:16:20
evrardjp - We have a fixed scheduled train, so we don't ask ourselves questions, it's simple, and no need to think about it16:20
evrardjp- We shouldn't even discuss it because everything is on rails :)16:21
evrardjp(toot toot)16:21
hwoaranghehe16:21
*** iyamahat has quit IRC16:21
evrardjpThere would be sometimes exceptions to this 2 week release train, like next week for newton EOL16:21
evrardjp(or maybe it will be after next week)16:22
hwoarangsounds reasonable to me. so basically you propose some kind of 'automated' 2 week release unless something major blocks it16:22
cloudnull++ that'd be great16:22
evrardjpno it's automated 2 week release train, let's not think about major blocking :)16:23
evrardjpbut we can have extra ones16:23
evrardjpfor special cases16:23
evrardjp(EOL, security)16:23
evrardjpbut also simplified for everyone and documented16:23
hwoarangok16:24
evrardjpwe still need human intervention to qualify what a release is, because we are using semver, and we don't auto bump to a minor instead of a patch with our code16:25
evrardjpanyway, long story short, except mid month and end of month releases, and we discuss those EOM16:25
hwoarangok16:26
evrardjpprometheanfire: so to answer your question, newton will still get one now, and we should have one when the other projects are EOL, to consume EOL projects.16:27
odyssey4methe reason for not doing that and for having the PTL do the release requests has been because the release process is manual and needs human judgment here and there16:27
evrardjpagreed16:27
prometheanfireevrardjp: cool16:27
evrardjpbut that knowledge need to be spread16:27
odyssey4meif we make the scripts less clunky, more reliable, etc then we could probably just automate it16:27
logan-++ sounds great16:27
evrardjpI am working on that already16:27
evrardjpsimple functions, with a documentation that could go to our release guidelines16:28
odyssey4mesounds good16:28
odyssey4medon't work yourself to death ;)16:28
evrardjptechnically only PTL and liaisons should request releases, but this way we have guidelines16:28
logan-i have a python thing that will bump ansible-role-requirements to the head of branches and maintain comments in the format we have like "HEAD of XXXX as of <date>" would be happy to share that evrardjp16:28
evrardjpodyssey4me: well in case of death, you'd have something that help you releasing :p16:28
*** galstrom_zzz is now known as galstrom16:29
evrardjpwe already have some in our code tree too logan-, but definitely worth checking with you16:29
evrardjpI think I quickly drafted this this morning though :p16:29
evrardjplet's move to another topic :)16:29
evrardjp(but thanks logan- :) I will have a look! )16:30
logan-sure16:30
odyssey4melogan- I think you may have meant to refer to the git sources for the service projects, not a-r-r ?16:31
logan-both odyssey4me16:31
odyssey4meoh neat16:31
logan-actually no, I don't think ti would support the service projects yet but it could be made to do so easily16:31
odyssey4meanything to replace my crufty bash script :p16:31
cloudnullyay crufty bash  !16:31
evrardjpodyssey4me: I already wrote something in python that is now handling ordered dict for YAML loading for easier reviews. Works already for A-R-R16:31
logan-#link https://gist.github.com/Logan2211/f8ad9a03502e69971d2eee96049719d716:32
spotzWhen newton goes EOL are they going to still be able to access it for the COA?16:32
*** pbourke has quit IRC16:32
spotz#topic Blueprint work16:32
* cloudnull a fan of cruft bash :D16:32
*** openstack changes topic to "Blueprint work (Meeting topic: openstack_ansible_meeting)"16:32
evrardjpspotz: yeah it's just becoming a tag instead of a branch16:32
spotzevrardjp: ok I'll give Anne a heads up16:32
odyssey4mespotz yes, it will still work for as long as the git repo exists16:32
spotzI figured it would but I know devstack and packstack break when EOL16:33
spotzBlueprints!16:33
evrardjpfor blueprint work, I think there are 4 things that I find very important right now16:33
*** ralonsoh has quit IRC16:33
evrardjpThe first two are odyssey4me and cloudnull's16:34
evrardjpone for hyperconverged16:34
cloudnulli'd like to see https://review.openstack.org/#/c/499882/ get in --cc jmccrory16:34
evrardjpand one (well two basically) to change the build process16:34
evrardjpcloudnull: on the hyper converged stuff, we need to make sure the periodics don't break ;)16:35
evrardjpI trust you!16:35
evrardjpI'd hate revert again...16:35
cloudnulland https://review.openstack.org/#/c/476121/ -- is very interesting from a tech perspective16:35
odyssey4mefrom what I saw this morning, the periodics are still not quite there yet - upgrades are still busted16:35
*** TravT has left #openstack-meeting-416:35
evrardjponly for ceph16:35
cloudnullevrardjp: I would not lie to you16:36
cloudnull:D16:36
evrardjpwell we can discuss the false positives on openstack health dashboard another time :)16:36
odyssey4meevrardjp you may not have seen yet, but cloudnull has revised the spec with the promise to provide upgrade tooling to clean up the inventory16:36
evrardjpso cloudnull and odyssey4me if you need any help16:36
evrardjpjust ping16:36
cloudnullyes i have16:36
*** salmankhan has quit IRC16:37
odyssey4methanks for doing that cloudnull :)16:37
evrardjpyeah. I will review it as soon as possible16:37
cloudnulltyvm16:37
evrardjpI didn't see that16:37
evrardjpso thank you!16:37
evrardjpfor the rest of the blueprints16:37
evrardjpthere are a few interesting ones, like the ovs, the messaging changes but also the inventory cleaning and the uwsgi16:38
odyssey4meI looked through the specs repo this morning - it looked like some needed an update after the PTG... and for the sake of my own sanity I'm staying away from the networking ones. :p16:38
evrardjpI didn't got the chance to work on uwsgi16:38
evrardjphaha16:39
evrardjpok16:39
evrardjpwell like I said, for this cycle, you two have prio16:39
odyssey4mewhoh agreed to put together that uwsgi/load balancing spec? was it jmccrory and logan- ?16:39
spotz20 minute warning with only open discussion left16:39
evrardjpjmccrory: logan- and I16:39
evrardjpwill be working on that16:39
evrardjpbut anyone free to join :)16:39
evrardjpa quick update for the inventory cleaning work16:40
odyssey4meah ok, that'll be interesting although not entirely essential - I think cloudnull might be ineterested to know more about it though so get the spec up soon :)16:40
jmccrorythink andymccr's spec for initial uwsgi+nginx may still be out there, some of that could probably be split out to start this new one16:40
evrardjpI'd rather work on the priorities right now, but yes if logan- or jmccrory could spend some cycles on uwsgi fast router that would be great16:41
evrardjp(according to what we said @ the PTG)16:41
*** krtaylor__ has quit IRC16:41
odyssey4mehmm, that's weird - nothing published since newton apparently: http://specs.openstack.org/openstack/openstack-ansible-specs/16:42
evrardjpwhat we've said at the ptg was discussing the position of LB + uwsgi for "new kind" of apps, and still remain with "old kind" if need be. So we'd need a new spec16:42
*** slaweq_ has quit IRC16:42
evrardjpI am only checking on https://github.com/openstack/openstack-ansible-specs :D16:43
spotzok email heads up sent to Anne at the foundation16:43
logan-yeah my focus was more on replacing our haproxy role with something less rigid. i don't know much about the uwsgi stuff16:44
evrardjpjmccrory: FYI I didn't got the chance to push changes since our last convo about the inventory. But It's very cleanable, and we are close to have an ansible ready static inventory that's generated from our thing.16:44
*** karts has joined #openstack-meeting-416:44
evrardjplogan-: that's great and that's completely appropriate!16:45
evrardjpI heard ppl hoping for that16:45
evrardjpanyone has something to ask about specs?16:45
evrardjpOr to raise?16:45
odyssey4meI have something to raise, but it's not related to specs - more open discussion.16:46
evrardjpodyssey4me: I will not chase this web page. It's not easy to find by contributors anyway :p16:46
evrardjpok16:46
evrardjplet's move to that topic then!16:46
evrardjp#topic open discussion16:46
odyssey4meevrardjp no worries, it looks like the specs pages for other projects are fine so it's likely our job broken or something - I'll check it out16:46
spotz#topic open discussion16:46
*** openstack changes topic to "open discussion (Meeting topic: openstack_ansible_meeting)"16:46
spotz*phhbts*16:46
*** numans has quit IRC16:46
odyssey4me:)16:47
evrardjp:)16:47
odyssey4mealrighty - I've sent http://lists.openstack.org/pipermail/openstack-dev/2017-September/122794.html to the ML related to a little thing I'm doing on the side to try and cut down some of our tech debt16:47
*** karthiks has quit IRC16:47
odyssey4meI'm hoping we get a more positive response from the packagers than previously.16:47
evrardjpoh yes it had an impact on release's toolkit :D16:47
odyssey4meSo far the RDO crew via reviews have been very welcoming.16:48
evrardjp#link http://lists.openstack.org/pipermail/openstack-dev/2017-September/122794.html16:48
*** LouisF has joined #openstack-meeting-416:48
evrardjpI love the effort16:48
evrardjpthank you16:48
spotz#link http://lists.openstack.org/pipermail/openstack-dev/2017-September/122794.html16:48
spotzok no diff:)16:49
odyssey4melooks like gerritbot might be broken or something16:49
*** numans has joined #openstack-meeting-416:49
spotz:(16:49
odyssey4meanyway, I thought I'd just raise it as a heads-up16:49
odyssey4methe hope I have is that we can kill templates and the git sourcing and keep it simpler16:50
odyssey4meif we can't do that, then the build process for packages is going to have to carry it, which isn't nice16:50
evrardjpbut I don't understand how you want to do that, like template it at the destination?16:50
evrardjpor a push pull mechanism?16:51
evrardjppull/push*16:51
evrardjpbut I like the idea of having it uniform and not in three16:51
evrardjptree*16:51
evrardjpso thanks!16:51
*** salmankhan has joined #openstack-meeting-416:52
spotz8 minute warning16:52
logan-thanks odyssey4me16:52
evrardjpOn open discussion I have something to add, I have made a ics (google agenda) with what will happen in this cycle for OSA that's not already in the standard dev calendar16:52
logan-nice to see many projects are merging it16:52
odyssey4meyeah, not sure yet - those details can be figured out once we have the upstream stuff done16:52
*** dianyu has joined #openstack-meeting-416:53
evrardjpodyssey4me: if we build on localhost problem is solved :p16:53
odyssey4meevrardjp not entirely16:53
evrardjpI know ;)16:53
odyssey4meif it's not in the wheel we're forced to git clone - if it's in the wheel, no git clone needed :)16:53
*** VW has joined #openstack-meeting-416:54
evrardjpok on another topic16:55
evrardjpI will appoint liaisons soon, I will send a series of mails next week16:55
spotz5 minute warning:)16:55
evrardjpif you're interested by taking more work, ping me anytime :D16:56
odyssey4mealright, nothing more from me - I'm hoping to find some time to get cracking on revising a role or two based on the specs now that they're merged16:56
odyssey4meany thoughts on milestones we'd like to see major changes stop at ?16:56
odyssey4meM3?16:57
evrardjpI've said a lot today, I'm good16:57
odyssey4meor RC1?16:57
evrardjpit's m3 according to agenda I think16:57
*** vks1 has joined #openstack-meeting-416:57
odyssey4meyes, the standard upstream schedule puts feature freeze at M316:57
evrardjpbut before m3 it's packed with small breaking updates too , so let's play it by ear.16:57
evrardjpLet's focus on m316:57
spotz2 minutes:) We haven't run this long in ages:)16:58
evrardjphttps://docs.openstack.org/openstack-ansible/latest/contributor/contribute.html#development-cycle-checklist16:58
odyssey4meare we holding back on major changes up to M1 to allow easier backports, or are we going ahead straight away?16:58
evrardjpBecause M1 is kinda nice and easy for us, we could move our deliverables from M2 into M1 then do these massive changes16:59
spotz1 minute16:59
evrardjpbut I don't think this should be an objection on your 2 big specs odyssey4me and cloudnull16:59
dianyuHi, I recently hit an error when launch instance on horizon as following: Error: No sql_connection parameter is established with newest networking master and devstack stable/pike. Anyone met the similar problem?17:00
LouisF#startmeeting service_chaining17:00
openstackLouisF: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.17:00
odyssey4meI'd suggest moving all the M2 stuff to M1, and make M2's goal to be features like M317:00
evrardjplet's wrap up!17:00
spotzTimes up gang17:00
spotz#endmeeting17:00
evrardjpodyssey4me: agreed17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu Sep 28 17:00:22 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2017/openstack_ansible_meeting.2017-09-28-16.01.html17:00
*** baoli has quit IRC17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2017/openstack_ansible_meeting.2017-09-28-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2017/openstack_ansible_meeting.2017-09-28-16.01.log.html17:00
spotzSorry LouisF17:00
spotzall yours17:00
LouisFspotz: thx17:00
LouisF#startmeeting service_chaining17:00
openstackMeeting started Thu Sep 28 17:00:41 2017 UTC and is due to finish in 60 minutes.  The chair is LouisF. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: service_chaining)"17:00
openstackThe meeting name has been set to 'service_chaining'17:00
LouisF#topic agenda17:01
*** openstack changes topic to "agenda (Meeting topic: service_chaining)"17:01
*** baoli has joined #openstack-meeting-417:01
LouisFhttps://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting17:01
vks1hi all17:02
igordchi17:02
dianyuhi17:02
LouisFhi all17:02
bcafarelhello17:02
LouisF#topic API reference17:03
*** openstack changes topic to "API reference (Meeting topic: service_chaining)"17:03
LouisFpcarver: what is status?17:03
*** anilvenkata has quit IRC17:04
LouisF#topic Tap SF17:04
*** openstack changes topic to "Tap SF (Meeting topic: service_chaining)"17:04
LouisFvks1: what is status?17:04
*** csun has joined #openstack-meeting-417:04
vks1LouisF: I have debugged the test case with extension. it's failing17:05
vks1talked with amotoki, he said we should do in 2nd week of oct17:05
vks1he is on vacation17:05
LouisFvks1: ok thanks17:05
LouisF#topic SFC graph17:06
*** openstack changes topic to "SFC graph (Meeting topic: service_chaining)"17:06
LouisFigordc: how is SFC graph progressing?17:06
bcafarelI saw a few W+1 here17:06
*** salmankhan has quit IRC17:07
LouisFbcafarel: yes i expect this will merge soon17:07
bcafarelnice17:07
LouisFok moving on17:08
igordcyep just waiting for it to merge17:08
vks1has anyone tried any extension in networking-sfc ?17:08
bcafarelthat means we should start reviewing the NSH patch then?17:08
LouisFigordc: thanks17:08
LouisFbcafarel: yes that is next item17:08
LouisF#topic NSH work17:08
*** openstack changes topic to "NSH work (Meeting topic: service_chaining)"17:08
bcafarel:)17:09
csunWhich version of OVS includes NSH support?17:09
LouisFall please review https://review.openstack.org/#/c/373465/17:09
igordccsun: 2.8, if you use the userspace datapath17:09
csunI see, thinks.17:09
LouisFwe should get ovs with nsh tested to make sure in is in queens17:10
bcafarelack, will try to take a look at it next week17:11
LouisFbcafarel: thanks17:11
igordcthanks bcafarel17:11
igordcwe need to find a nice way of generating nsh packets17:11
*** spzala has joined #openstack-meeting-417:12
igordctho for the networking-sfc esting of it, OVS itself can be the one17:12
csunigordc: Do you have a good example of how to generate nsh packets?17:12
LouisFigordc: if nsh encap is specified the ingress classifier should generate nsh packets - right?17:12
igordcand the SFs can also be running OVS+NSH simply decrementing the index and giving the traffic back17:13
igordcLouisF: yes exactly;, <-- csun this17:13
*** sjmc7 has left #openstack-meeting-417:13
LouisFigordc: nsh-aware sfs is another issue17:13
LouisFdoes your implementation support nsh-aware SFs?17:14
LouisFor does it just implement proxy functionality?17:15
igordcLouisF: both17:15
bcafarelby setting correlation on the PPG I suppose?17:15
igordcLouisF: it will expect packets to come back with a decremented SI17:15
LouisFigordc: how are you testing nsh-aware SFs?17:15
igordcbcafarel: yeah17:15
*** baoli has quit IRC17:16
igordcLouisF: I'm not yet testing that... Daire started working on it during her placement but then it finished17:16
csunAny known issues with nsh support?  I’d like to do some testing about the change.17:16
igordcLouisF: I'm not sure how much and if I will have time to do proper testing with the SFs17:16
LouisFigordc: i see that there will be a lot of interest from SF vendors17:16
igordccsun: would you like to test networking-sfc + nsh-aware VMs?17:17
*** sambetts is now known as sambetts|afk17:17
csunYes, I’d like to give a try.17:17
LouisFcsun: sounds like a good idea17:18
*** nikhil has quit IRC17:18
LouisFcsun: thanks17:18
igordccsun: cool cool, ping me if you need anything17:18
igordccsun: #networking-sfc17:18
csunigordc: I would definitely need your help.17:18
igordccsun: are you Ching Sun?17:19
csunigordc: Yes.17:20
igordcalright17:20
LouisF#topic Transparent SF17:21
*** openstack changes topic to "Transparent SF (Meeting topic: service_chaining)"17:21
LouisFthis work is progressing17:21
LouisF#topic OVN-SFC work17:22
*** openstack changes topic to "OVN-SFC work (Meeting topic: service_chaining)"17:22
LouisFlooks like John is not on the channel17:22
LouisF#topic other items17:23
*** openstack changes topic to "other items (Meeting topic: service_chaining)"17:23
dianyuI have hitten an error when launch a new instance on Horizon as following: Error: No sql_connection parameter is established. Anyone has similar error or idea?17:23
*** baoli has joined #openstack-meeting-417:24
LouisFdianyu: is this on the master?17:24
dianyuwith newest master networking-sfc and devstack stable/pike17:24
*** SumitNaiksatam has joined #openstack-meeting-417:24
*** karts has quit IRC17:25
igordcdianyu: use master devstack17:25
LouisFhas anyone else encountered this?17:25
csunI encountered the same thing.17:26
*** numans has quit IRC17:26
LouisFcsun: on stable/pike?17:26
csunI am using stable/pike devstack.17:26
csunmaster networking-sfc17:26
bcafarelit may be some leftover installed packages from stable/pike run17:26
dianyuigordc: will try17:27
bcafarelwith everything on master I restacked 2-3 days ago and VMS booted fine17:27
csunI will try to use master devstack today.17:27
LouisFigordc: thanks17:27
LouisFdianyu: can you try that17:28
dianyuLouisF: yes, definitely17:28
LouisFdianyu: thanks17:28
bcafarelother topic, I chatted a bit with other people on split tempest plugins ( https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html )17:29
LouisFok, any other items to discuss?17:29
bcafarelwe are indeed expected to be in the "migration done" list :)17:29
*** coolsvap has quit IRC17:29
bcafarelI can take a look (it should mostly be splitting git history and repo gates configuration)17:29
LouisFbcafarel: that would be great, thanks17:30
LouisFok, anything else?17:30
*** VW_ has joined #openstack-meeting-417:30
*** numans has joined #openstack-meeting-417:31
LouisFok thanks all17:31
LouisFbye all17:31
dianyuthanks everyone17:31
csunbye all17:31
bcafarelthanks, and bye!17:31
igordcbye all17:31
*** dianyu has quit IRC17:31
LouisF#endmeeting17:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:31
openstackMeeting ended Thu Sep 28 17:31:57 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-09-28-17.00.html17:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-09-28-17.00.txt17:32
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-09-28-17.00.log.html17:32
*** baoli has quit IRC17:32
*** baoli has joined #openstack-meeting-417:32
*** VW_ has quit IRC17:32
*** VW has quit IRC17:33
*** VW_ has joined #openstack-meeting-417:33
*** karts has joined #openstack-meeting-417:38
*** mgariepy has left #openstack-meeting-417:40
*** vks1 has quit IRC17:42
*** yifei has joined #openstack-meeting-417:43
*** VW_ has quit IRC17:47
*** yifei has quit IRC17:47
*** VW has joined #openstack-meeting-417:47
*** seajay has quit IRC17:55
*** seajay has joined #openstack-meeting-417:56
*** baoli has quit IRC17:56
*** unicell has joined #openstack-meeting-417:56
*** baoli has joined #openstack-meeting-417:57
*** krtaylor__ has joined #openstack-meeting-418:03
*** baoli has quit IRC18:07
*** baoli has joined #openstack-meeting-418:10
*** LouisF has quit IRC18:20
*** baoli has quit IRC18:30
*** baoli has joined #openstack-meeting-418:34
*** janki has quit IRC18:45
*** janki has joined #openstack-meeting-418:48
*** salmankhan has joined #openstack-meeting-418:50
*** bobmel has joined #openstack-meeting-418:54
*** salmankhan has quit IRC18:55
*** rosmaita has quit IRC18:56
*** ansmith has quit IRC18:59
*** slaweq_ has joined #openstack-meeting-419:05
*** bnemec has quit IRC19:07
*** spzala has quit IRC19:10
*** bnemec has joined #openstack-meeting-419:13
*** ansmith has joined #openstack-meeting-419:14
*** spzala has joined #openstack-meeting-419:15
*** bnemec has quit IRC19:16
*** spzala_ has joined #openstack-meeting-419:17
*** spzala__ has joined #openstack-meeting-419:18
*** bobmel_ has joined #openstack-meeting-419:18
*** spzala has quit IRC19:20
*** Sukhdev has joined #openstack-meeting-419:21
*** bobmel has quit IRC19:21
*** spzala__ has quit IRC19:21
*** spzala_ has quit IRC19:22
*** spzala_ has joined #openstack-meeting-419:25
*** nikhil has joined #openstack-meeting-419:27
*** spzala has joined #openstack-meeting-419:27
*** spzala_ has quit IRC19:30
*** pcaruana has quit IRC19:31
*** bnemec has joined #openstack-meeting-419:35
*** spzala has quit IRC19:36
*** prometheanfire has left #openstack-meeting-419:40
*** zenirc369 has quit IRC19:49
*** VW has quit IRC19:51
*** VW_ has joined #openstack-meeting-419:51
*** janki has quit IRC20:02
*** ansmith has quit IRC20:03
*** woodard has quit IRC20:09
*** seajay has quit IRC20:12
*** slaweq_ has quit IRC20:12
*** slaweq_ has joined #openstack-meeting-420:13
*** slaweq_ has quit IRC20:13
*** slaweq_ has joined #openstack-meeting-420:14
*** ansmith has joined #openstack-meeting-420:15
*** spzala has joined #openstack-meeting-420:19
*** thorst has quit IRC20:26
*** krtaylor__ has quit IRC20:30
*** jamesbenson has quit IRC20:35
*** ansmith has quit IRC20:41
*** thorst has joined #openstack-meeting-420:43
*** corey_ has quit IRC20:54
*** yamahata has joined #openstack-meeting-420:58
*** thorst has quit IRC21:00
*** thorst has joined #openstack-meeting-421:00
*** krtaylor__ has joined #openstack-meeting-421:02
*** spzala has quit IRC21:05
*** thorst has quit IRC21:11
*** seajay has joined #openstack-meeting-421:28
*** slaweq_ has quit IRC21:28
*** slaweq_ has joined #openstack-meeting-421:29
*** seajay has quit IRC21:30
*** seajay has joined #openstack-meeting-421:31
*** thorst has joined #openstack-meeting-421:32
*** premsankar has joined #openstack-meeting-421:33
*** nikhil has quit IRC21:36
*** thorst has quit IRC21:36
*** ansmith has joined #openstack-meeting-421:39
*** woodard has joined #openstack-meeting-421:48
*** dulek has quit IRC21:53
*** iyamahat has joined #openstack-meeting-421:53
*** dulek has joined #openstack-meeting-421:54
*** bnemec has quit IRC22:05
*** baoli has quit IRC22:06
*** VW_ has quit IRC22:06
*** VW has joined #openstack-meeting-422:07
*** galstrom is now known as galstrom_zzz22:07
*** iyamahat_ has joined #openstack-meeting-422:07
*** iyamahat has quit IRC22:07
*** iyamahat_ has quit IRC22:08
*** thorst has joined #openstack-meeting-422:13
*** bobh has quit IRC22:16
*** slaweq_ has quit IRC22:17
*** thorst has quit IRC22:17
*** thorst has joined #openstack-meeting-422:23
*** iyamahat has joined #openstack-meeting-422:25
*** seajay has quit IRC22:29
*** thorst has quit IRC22:35
*** thorst has joined #openstack-meeting-422:36
*** thorst has quit IRC22:42
*** thorst has joined #openstack-meeting-422:45
*** lyan has quit IRC22:51
*** thorst has quit IRC22:58
*** thorst has joined #openstack-meeting-422:58
*** hongbin has quit IRC23:07
*** pmesserli has quit IRC23:09
*** VW_ has joined #openstack-meeting-423:29
*** VW has quit IRC23:29
*** thorst has quit IRC23:31
*** markvoelker has quit IRC23:37
*** thorst has joined #openstack-meeting-423:39
*** ltomasbo has quit IRC23:44
*** ltomasbo has joined #openstack-meeting-423:45
*** SumitNaiksatam has quit IRC23:53
*** thorst has quit IRC23:54
*** thorst has joined #openstack-meeting-423:55
*** iyamahat has quit IRC23:56
*** yamahata has quit IRC23:56
*** chyka has quit IRC23:58
*** baoli has joined #openstack-meeting-423:59

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