Wednesday, 2016-01-06

*** rbak has quit IRC00:02
*** sdake has quit IRC00:06
*** baohua has quit IRC00:10
*** piet has quit IRC00:13
*** piet has joined #openstack-meeting-300:13
*** adrian_otto has joined #openstack-meeting-300:17
*** Sukhdev has joined #openstack-meeting-300:22
*** sdake has joined #openstack-meeting-300:32
*** jpomeroy has quit IRC00:36
*** hoangcx has joined #openstack-meeting-300:37
*** Aish has joined #openstack-meeting-300:38
*** bpokorny has joined #openstack-meeting-300:44
*** Aish has quit IRC00:45
*** galstrom is now known as galstrom_zzz00:49
*** Josheee has quit IRC00:55
*** adrian_otto has quit IRC01:00
*** Sukhdev has quit IRC01:08
*** gomarivera has quit IRC01:09
*** bpokorny_ has joined #openstack-meeting-301:16
*** bpokorny has quit IRC01:20
*** bpokorny_ has quit IRC01:21
*** stanchan has quit IRC01:21
*** Sukhdev has joined #openstack-meeting-301:29
*** julim has quit IRC01:30
*** julim has joined #openstack-meeting-301:30
*** tellesnobrega_af is now known as tellesnobrega01:37
*** stanzgy has joined #openstack-meeting-301:38
*** sdake has quit IRC01:40
*** vahidh has quit IRC01:40
*** vahidh has joined #openstack-meeting-301:41
*** baohua has joined #openstack-meeting-301:42
*** vahidh has quit IRC01:46
*** banix has joined #openstack-meeting-301:47
*** shaohe_feng has quit IRC01:48
*** shaohe_feng_ has quit IRC01:49
*** Swami has quit IRC01:56
*** gomarivera has joined #openstack-meeting-302:04
*** mtanino has quit IRC02:07
*** piet has quit IRC02:09
*** hoangcx has quit IRC02:12
*** piet has joined #openstack-meeting-302:15
*** stanchan has joined #openstack-meeting-302:21
*** sdake has joined #openstack-meeting-302:27
*** gomarivera has quit IRC02:29
*** yamamoto has joined #openstack-meeting-302:35
*** piet has quit IRC02:37
*** Sukhdev has quit IRC02:39
*** yamamoto has quit IRC02:48
*** yamamoto has joined #openstack-meeting-302:54
*** yamamoto_ has joined #openstack-meeting-302:57
*** yamamoto has quit IRC02:57
*** dims has quit IRC02:59
*** s3wong has quit IRC03:01
*** Poornima has joined #openstack-meeting-303:03
*** yamamoto_ has quit IRC03:07
*** armax has joined #openstack-meeting-303:26
*** woodster_ has quit IRC03:36
*** Aish has joined #openstack-meeting-303:37
*** Aish has quit IRC03:38
*** gomarivera has joined #openstack-meeting-303:46
*** tellesnobrega is now known as tellesnobrega_af03:50
*** yamahata has quit IRC03:52
*** bpokorny has joined #openstack-meeting-303:52
*** yamamoto has joined #openstack-meeting-303:57
*** banix has quit IRC04:01
*** galstrom_zzz is now known as galstrom04:01
*** coolsvap|away is now known as coolsvap04:06
*** yamamoto has quit IRC04:06
*** Poornima has quit IRC04:10
*** Poornima has joined #openstack-meeting-304:12
*** kebray has joined #openstack-meeting-304:13
*** kebray has quit IRC04:15
*** kebray has joined #openstack-meeting-304:15
*** galstrom is now known as galstrom_zzz04:28
*** coolsvap is now known as coolsvap|away04:29
*** stanchan has quit IRC04:32
*** adrian_otto has joined #openstack-meeting-304:36
*** sdake has quit IRC04:38
*** adrian_otto has quit IRC04:40
*** sdake has joined #openstack-meeting-304:44
*** stanchan has joined #openstack-meeting-304:44
*** hoangcx has joined #openstack-meeting-304:45
*** Poornima has quit IRC04:58
*** Poornima has joined #openstack-meeting-305:10
*** kebray has quit IRC05:13
*** kebray has joined #openstack-meeting-305:18
*** coolsvap|away is now known as coolsvap05:35
*** jrist has quit IRC05:39
*** piet has joined #openstack-meeting-305:49
*** jrist has joined #openstack-meeting-305:51
*** bpokorny has quit IRC05:52
*** irenab has joined #openstack-meeting-305:55
*** coolsvap is now known as coolsvap|away05:55
*** gcb has joined #openstack-meeting-305:56
*** ifat_afek has joined #openstack-meeting-305:59
*** baohua has quit IRC06:00
*** baohua has joined #openstack-meeting-306:01
*** kaz has joined #openstack-meeting-306:06
*** piet has quit IRC06:12
*** hdaniel has joined #openstack-meeting-306:12
*** coolsvap|away is now known as coolsvap06:18
*** dslevin has quit IRC06:20
*** david-lyle_ has joined #openstack-meeting-306:24
*** soichi has joined #openstack-meeting-306:25
*** kaz has quit IRC06:27
*** kaz has joined #openstack-meeting-306:27
*** enowy_ has joined #openstack-meeting-306:31
soichiHi06:33
*** Sukhdev has joined #openstack-meeting-306:37
kazHi06:42
*** nelsnels_ has quit IRC06:42
soichiit seems taas meeting will resume on next week.06:46
soichibye06:46
*** soichi has left #openstack-meeting-306:46
*** kaz has quit IRC06:46
*** nelsnelson has joined #openstack-meeting-306:49
*** vahidh has joined #openstack-meeting-306:53
*** dslevin has joined #openstack-meeting-306:54
*** david-lyle_ has quit IRC06:56
*** vahidh has quit IRC06:58
*** belmoreira has joined #openstack-meeting-306:59
*** kebray has quit IRC06:59
reedipok06:59
reedipso no meeting for TaaS today07:00
reedip?07:00
*** armax has quit IRC07:07
*** baohua has quit IRC07:12
*** numans has joined #openstack-meeting-307:19
*** stanchan has quit IRC07:19
*** klkumar has joined #openstack-meeting-307:19
*** hdaniel has quit IRC07:23
*** e0ne has joined #openstack-meeting-307:25
*** enowy_ has quit IRC07:31
*** baohua has joined #openstack-meeting-307:31
*** ifat_afek has quit IRC07:40
*** ifat_afek has joined #openstack-meeting-307:41
*** Sukhdev has quit IRC07:46
*** Sukhdev has joined #openstack-meeting-307:49
*** itxaka has joined #openstack-meeting-307:52
*** Sukhdev has quit IRC07:57
*** coolsvap is now known as coolsvap|away08:00
*** yamahata has joined #openstack-meeting-308:01
*** JeanBriceCombebi has joined #openstack-meeting-308:03
*** coolsvap|away is now known as coolsvap08:06
*** tfukushima has joined #openstack-meeting-308:06
*** hdaniel has joined #openstack-meeting-308:07
*** stanchan has joined #openstack-meeting-308:26
*** mrmartin has joined #openstack-meeting-308:33
*** dtardivel has joined #openstack-meeting-308:33
*** matrohon has joined #openstack-meeting-308:33
*** idan_hefetz has joined #openstack-meeting-308:35
*** eyalb has joined #openstack-meeting-308:37
*** alexey_weyl has joined #openstack-meeting-308:37
*** circ-user-QKtDY has joined #openstack-meeting-308:37
*** circ-user-QKtDY is now known as inbar_stolberg08:37
*** egallen has joined #openstack-meeting-308:38
*** egallen has quit IRC08:41
*** egallen has joined #openstack-meeting-308:42
*** jlanoux has joined #openstack-meeting-308:43
*** safchain has joined #openstack-meeting-308:44
*** stendulker has joined #openstack-meeting-308:47
*** nadav_yakar has joined #openstack-meeting-308:53
*** emalin has joined #openstack-meeting-308:53
*** ihrachys has joined #openstack-meeting-308:55
*** ayah has joined #openstack-meeting-309:00
*** umargolin has joined #openstack-meeting-309:00
ifat_afek#startmeeting vitrage09:01
openstackMeeting started Wed Jan  6 09:01:09 2016 UTC and is due to finish in 60 minutes.  The chair is ifat_afek. Information about MeetBot at http://wiki.debian.org/MeetBot.09:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:01
*** openstack changes topic to " (Meeting topic: vitrage)"09:01
openstackThe meeting name has been set to 'vitrage'09:01
alexey_weylHello There :)09:01
eyalbhello09:01
ifat_afekHi everyone, welcome back 09:01
*** Ohad has joined #openstack-meeting-309:01
umargolinhi09:01
*** sdake has quit IRC09:02
*** lhartal has joined #openstack-meeting-309:02
lhartalhi all :)09:02
emalinhi09:02
Ohadhi09:02
lhartallong time...09:02
nadav_yakarhi09:02
*** elisha_r has joined #openstack-meeting-309:02
elisha_rhi all09:03
emalinlong time no see09:03
ifat_afekOur agenda:09:06
ifat_afek* Current status and progress09:06
ayahhi09:06
ifat_afek* Review action items09:06
ifat_afek* Next steps09:06
ifat_afek* Open Discussion09:06
ifat_afek#topic Current status and progress09:07
*** openstack changes topic to "Current status and progress (Meeting topic: vitrage)"09:07
ifat_afekA short update about Vitrage documentation: Maty checked this issue, and we cannot place our documentation in the official openstack place (http://docs.openstack.org) until we are accepted under the big tent.09:07
ifat_afekI suggest that for now we add our detailed design diagrams in Vitrage main page09:07
ifat_afekUpdate on what I did: I started working on Nagios plugin for the synchronizer. As a first stage, I’m going to implement the get_all for nagios services (tests).09:07
inbar_stolberghello09:08
ifat_afekFor notifications, we have decided not to register to Nagios event handlers, as it raises security issues (how will Nagios call vitrage). Instead, we will take Nagios snapshots periodically and compare them.09:08
ifat_afekI was also involved in the discussions on the consistency process (with alexey_weyl, elisha_r and Asi), and plan to document the use cases and challenges. We should continue with the design this week.09:08
*** amir_gur has joined #openstack-meeting-309:08
ifat_afekWe worked on the first integration of the synchronizer, processor, graph, api and UI.09:08
ifat_afekalexey_weyl, can you update?09:09
alexey_weylI would love to09:09
amir_gurHi09:09
*** f13o has quit IRC09:09
alexey_weylI have performed the integration of the synchronizer + processor + transformer. Now it works and runs09:09
*** elishar_r has joined #openstack-meeting-309:10
alexey_weylIn addition I have a created an openstack service for "vitrage-graph" which runs the the synchronizer, entity graph, consistency and api handler oslo services09:10
alexey_weylif you want to run it, you can do: "sudo pip install -e."09:11
alexey_weylwhich will install the services, and then you can run "vitrage-graph"09:11
ifat_afekcool!09:11
emalinvery nice09:12
*** elisha_r has quit IRC09:12
ifat_afekOhad, can you update about our discussions with PinPoint?09:12
elishar_rcool!09:12
OhadWe had a meeting with PinPoint – OPNFV project aiming to provide RCA framework for NFVI and VIM layers focusing on network issues.09:12
OhadWe found good alignment between use cases from both projects covering failures from physical and virtual layers. PinPoint are working on gap analysis to find out which information/ data exists in different projects or tools in order to understand root cause of failures and to define the APIs needed for it.09:12
elishar_r@Ohad - can you explain what "aiming" means?09:13
OhadIt looks like Vitrage perfectly match for providing the get physical/virtual topology and mappings APIs and we will keep working together on this.09:13
lhartal@alexey_weyl: cool - lets do next week integration including zones, hosts and instances :)09:14
alexey_weyl@lhartal: sounds great :)09:14
*** gsagie has joined #openstack-meeting-309:15
ifat_afekalexey_weyl: this is great, let's do the full integration next week09:15
ifat_afek#action alexey_weyl continue with the integration, including zones, hosts and instances09:15
OhadElisha: PinPoint is a requirement project09:16
*** efoley has joined #openstack-meeting-309:16
alexey_weylOk :)09:16
ifat_afekOhad, elisha_r: we are in the process of finalizing vitrage API so we can send the definition to PinPoint, and verify it matches their use cases09:17
eyalbI am still working on api09:17
eyalbfirst version was written with a simple filter09:17
eyalbnext we will use a more complex filter09:18
eyalbi did an integration with UI09:18
eyalbthey are using the client and were able to retrieve a mock graph09:18
OhadEyalb: once we have a version, please share it with PinPoint09:19
eyalbstill need to work with dany to call the api handler09:19
eyalbohad sure09:19
eyalbthats it09:19
ifat_afekeyalb, so once Dani is done, we will have an end-to-end integration?09:19
eyalbhopefully yes09:20
ifat_afekgreat09:20
ifat_afeknadav_yakar, can you update about the synchronizer status?09:20
nadav_yakarwe have finalized the synchronizer design which includes hosts, zones and instances snapshotting and notifications propagation. I have checked in the synchronizer's plugin execution framework and worked with Alexey to integrate it with the vitrage graph09:20
inbar_stolbergget_all for host and zone are ready09:22
nadav_yakaryes, the instances snapshotting process is also checked in09:22
*** jlanoux has quit IRC09:22
ifat_afekgreat09:22
ifat_afekwho else wants to update?09:23
*** jlanoux has joined #openstack-meeting-309:24
elishar_rI've started compiling information on how Vitrage will work with Neo4J or Titan (or any other persistant GraphDB) that can replace NetworkX.09:24
emalinI did little research about oslo.service and it's multi-thread support09:25
emalinIt seems that we can use one process with multi-thread of greenlet while working with networkx09:26
emalinAnd multi processes while working with Neo4j09:26
emalinor other graph db that support access from multi processes09:26
alexey_weylSounds great! good solution!09:27
idan_hefetzmy update: currently working to implement the Get Topology query api over NetworkX, so we can request a filtered subgraph of the entity graph.09:27
ifat_afekemaiin, so the design for networkx is finished for now?09:27
*** luisfdez has left #openstack-meeting-309:28
emalinifat_afek: if think is finished09:28
ifat_afekgreat09:28
emalinI think it's finished09:28
*** inbar_stolberg has quit IRC09:28
ifat_afekany other updates? if not, let's move on09:29
ifat_afek#topic Review action items09:29
*** openstack changes topic to "Review action items (Meeting topic: vitrage)"09:29
ifat_afek• ifat_afek check Aodh integration workaround and update Ceilometer blueprints09:29
ifat_afekI sent an email to Aodh mailing list, and specifically to Julien and Ryota. Got no reply, could be because of the holidays. Will try again in a week or two.09:29
*** baohua has quit IRC09:30
ifat_afekI also emailed Aodh and asked them not to remove the ability to send notifications about alarm status changes (they planned to remove it), because we want to register to these notifications.09:30
*** tfukushima has quit IRC09:30
ifat_afek• nadav_yakar checkin a basic synchronizer FW for the vitrage graph to interface with and see that we are on the same page09:30
nadav_yakardone09:30
ifat_afek• ifat_afek check how we should add vitrage documentation09:30
gsagiei have a question, NetworkX is persistent or it has a way to keep the graph in RAM?09:30
gsagiesorry for stepping in :)09:30
nadav_yakarin memory only09:31
gsagiecool, thanks09:31
gsagielooks like an interesting project09:31
*** tfukushima has joined #openstack-meeting-309:31
elishar_rLet me expand a bit on NetworkX09:32
*** gomarivera has quit IRC09:32
elishar_rWe started with NetworkX b/c it's pure python (and the only significant graph DB in python project we could find).09:32
elishar_rIt's in-memory09:33
elishar_rHowever, for good performance we are already working now on a design that will allow using persistant graph-DB, such as Neo4J and Titan, instead.09:33
elishar_rAlready now, in our design, we use a interface called "Graph Driver" that will remain the same even when we replace the graph DB backend in the future.09:34
gsagieelishar_r : why there is a performance problem ? i would assume that in-memory should be faster then persistant one in general09:35
gsagieor the package itself (NetworkX) is not so good?09:35
elishar_rNetworkX itself has reasonable performance, as-is. however, there are a few other performance issues we want to address.09:36
elishar_rfirst of all, it's not persistant. that means that if Vitrage fails, we need to rebuild the DB when it goes back online09:36
elishar_rsecond of all, in pure python there is little support for real multi-threading, while when using a persistant DB like Neo4J we can access it in parallel from different sources.09:37
gsagieelisha_r: thanks for explaining, it make sense09:38
elishar_rfinally, doing things in-memory means we cannot leverage distribution, and limits the graph size as well. Those are the main points09:38
elishar_rsure :)09:38
emalinBut networkx is very use full for dev env09:39
emalinyou don't need to install any 3rd party DB09:39
ifat_afekBTW, we found out that networkx is already in use in openstack (by TaskFlow project if I'm not mistaken)09:40
emalinAnd networkx really fast09:40
ifat_afekok, let's go back to the action items09:41
ifat_afek• ifat_afek check how we should add vitrage documentation09:41
ifat_afekdone, already discussed it09:41
ifat_afek• decide on Vitrage next use cases09:41
ifat_afekWe talked about the second use case. It will include the evaluator for RCA purposes, nagios synchronizer (only snapshots), and physical resources synchronizer09:43
ifat_afek#topic Next Steps09:43
*** openstack changes topic to "Next Steps (Meeting topic: vitrage)"09:43
ifat_afekso we already discussed the integration09:43
ifat_afekand the second use case09:43
ifat_afekanything else?09:43
nadav_yakarI want to adapt our synchronizer framework09:44
emalinWe hope to start working on message bug listener plugin09:44
ifat_afek#action finalize get topology API09:44
emalinfor nova09:44
nadav_yakaradapt our framework per our design changes and oslo conventions09:45
ifat_afek#action ifat_afek update the documentation on vitrage main page with our latest design diagrams (of vitrage graph and the synchronizer)09:45
ifat_afek#topic Open Discussion09:46
*** openstack changes topic to "Open Discussion (Meeting topic: vitrage)"09:46
ifat_afekI had a look yesterday at Telemetry and Monasca IRC meeting logs, to see if they are doing anything that interests us.09:46
ifat_afekMonasca started working on a cassandra time-series DB. This is not related directly to Vitrage, but if they introduce cassandra to Openstack and handle cassandra installation, it might help us in our future “real” graph-database implementation.09:46
ifat_afek#link https://blueprints.launchpad.net/monasca/+spec/monasca-cassandra09:47
ifat_afekAs for Ceilometer, I noticed two interesting issues:09:47
ifat_afekThey want to improve their alarm rules. They will define complex conditions of and/or over several threshold conditions.09:47
ifat_afek#link https://blueprints.launchpad.net/ceilometer/+spec/composite-threshold-rule-alarm09:47
ifat_afekone of their future targets (i.e. not for mitaka?) is application level monitoring09:48
ifat_afek#link https://wiki.openstack.org/wiki/Telemetry/RoadMap09:48
ifat_afekanything else?09:48
*** dedery has joined #openstack-meeting-309:50
*** davidsha has joined #openstack-meeting-309:50
lhartalwe are going to present Vitrage first demo next week09:51
lhartalWe're planing to display the first use case: Vitrage show topology09:51
lhartalincluding zones, hosts and instances09:52
gsagiecool, is this going to be recorded?09:54
lhartalyes09:54
gsagiegreat09:54
lhartalwe will put a link in Vitrage website09:55
*** inbar_stolberg has joined #openstack-meeting-309:55
ifat_afekcool! we will also email it to openstack dev list09:55
lhartal#action: presenting first Vitrage demo09:56
alexey_weylThumbs up!09:56
ifat_afekan update on behalf of Marina: she prepared a dev stack that we can use for our tempest tests09:56
ifat_afeksee you next week then09:57
gsagiecya!09:57
eyalbbye09:57
alexey_weylbye bye :)09:58
elishar_rbye09:58
lhartalbye09:58
*** elishar_r has quit IRC09:58
amir_gurbye09:58
*** nadav_yakar has quit IRC09:58
*** amir_gur has quit IRC09:58
ifat_afek#endmeeting09:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:58
openstackMeeting ended Wed Jan  6 09:58:32 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-06-09.01.html09:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-06-09.01.txt09:58
openstackLog:            http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-06-09.01.log.html09:58
*** eyalb has quit IRC09:59
*** hoangcx has quit IRC09:59
*** dedery_ has joined #openstack-meeting-310:00
*** idan_hefetz has quit IRC10:00
*** dedery__ has joined #openstack-meeting-310:01
*** alexey_weyl has quit IRC10:02
*** alexey_weyl has joined #openstack-meeting-310:02
*** dedery__ has quit IRC10:02
*** Ohad has quit IRC10:02
*** lhartal has quit IRC10:02
*** dedery has quit IRC10:04
*** dedery__ has joined #openstack-meeting-310:04
*** ifat_afek_ has joined #openstack-meeting-310:04
*** dedery_ has quit IRC10:04
*** ifat_afek has quit IRC10:04
*** alexey_weyl has quit IRC10:05
*** gsagie has left #openstack-meeting-310:05
*** ayah has quit IRC10:29
*** dedery has joined #openstack-meeting-310:36
*** dedery__ has quit IRC10:40
*** tfukushima has quit IRC10:44
*** ifat_afek_ has quit IRC10:45
*** dims has joined #openstack-meeting-310:47
*** f13o has joined #openstack-meeting-310:49
*** gcb has quit IRC10:52
*** stanzgy has quit IRC10:52
*** shwetaap has joined #openstack-meeting-310:53
*** gcb has joined #openstack-meeting-310:54
*** klkumar has quit IRC10:59
*** Poornima has quit IRC11:01
*** gcb has quit IRC11:01
*** stendulker has quit IRC11:05
*** ifat_afek has joined #openstack-meeting-311:07
*** klkumar has joined #openstack-meeting-311:12
*** gcb has joined #openstack-meeting-311:21
*** kmb has joined #openstack-meeting-311:23
*** kmb has quit IRC11:24
*** egallen has quit IRC11:30
*** tellesnobrega_af is now known as tellesnobrega11:31
*** emalin has quit IRC11:41
*** klkumar has quit IRC11:47
*** coolsvap is now known as coolsvap|away11:47
*** robcresswell has joined #openstack-meeting-311:52
*** klkumar has joined #openstack-meeting-311:53
*** doug-fish has joined #openstack-meeting-311:59
*** sreshetnyak has quit IRC11:59
robcresswell#startmeeting horizon12:00
openstackMeeting started Wed Jan  6 12:00:09 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. 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: horizon)"12:00
openstackThe meeting name has been set to 'horizon'12:00
robcresswellAnyone around?12:00
doug-fishhi12:00
*** r1chardj0n3s has joined #openstack-meeting-312:01
r1chardj0n3so/12:01
doug-fishwow, small crowd!12:01
robcresswelldoug-fish: Heh, I was thinking that. I'll give it another minute or two then get started.12:01
r1chardj0n3severyone's still on vacation, lucky sods12:01
*** klkumar has quit IRC12:02
robcresswellHa12:02
robcresswellRight, lets get started12:02
*** klkumar has joined #openstack-meeting-312:02
robcresswell#link https://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_2016-01-06_1200_UTC Agenda for this meeting12:02
robcresswell#topic Notices12:03
*** openstack changes topic to "Notices (Meeting topic: horizon)"12:03
*** tsufiev has joined #openstack-meeting-312:04
tsufievhi there12:04
robcresswell#info Midcycle is Feb 23 - Feb 25 in Hillsboro, Oregon. Check the wiki for info on travel, and add your name to the table if you're planning to attend.12:04
robcresswell#linkhttps://wiki.openstack.org/wiki/Sprints/HorizonMitakaSprint12:04
robcresswell#link https://wiki.openstack.org/wiki/Sprints/HorizonMitakaSprint12:05
robcresswellTHats better :p12:05
r1chardj0n3sclicky!12:05
r1chardj0n3sI see all the cool kids are already listed12:05
r1chardj0n3swell except one12:05
r1chardj0n3s(non-cool kid listed)12:05
r1chardj0n3s[this could be a deep hole actually]12:06
doug-fishrobcresswell: tsufiev do you know if you'll be travelling to the mid cycle?12:06
tsufievdoug-fish, there is a good chance, although I need to discuss budget approval once winter holidays in Russia are over12:06
robcresswelldoug-fish: Hoping to. Unsure if I'll get approval yet. Car, hotel and flights adds up :/12:06
doug-fishcool12:06
*** betherly has joined #openstack-meeting-312:07
robcresswellI've updated the weekly bug report, but may add a couple more things to it. M-2 is in two weeks, roughly. As people start coming back we need to up our review pace a bit, Christmas is very disruptive.12:07
robcresswell#link https://wiki.openstack.org/wiki/Horizon/WeeklyBugReport12:07
robcresswellNot as much progress on Angular as I'd like, but still a lot of time this cycle left so lets keep at it.12:08
r1chardj0n3stsufiev: we should try to get that darned webdrivers thing off the bug report so robcresswell doesn't have to keep typing it in <wink>12:08
robcresswellI think a lot of the code is ready, so I'll try and get more reviews going this week.12:08
*** klkumar has quit IRC12:08
robcresswellheh :)12:08
tsufievr1chardj0n3s, well, it already has my +2 :)12:09
r1chardj0n3slove your work!12:09
robcresswellAnother brief notice about reviewing; we've had a few issues recently with tests throwing errors, but not failing. See https://bugs.launchpad.net/horizon/+bug/151770412:09
openstackLaunchpad bug 1517704 in OpenStack Dashboard (Horizon) "Test still passes even with tests failure" [Critical,New]12:09
*** jlanoux has quit IRC12:10
r1chardj0n3syeah, I keep forgetting that :-(12:10
robcresswellSo reviewers, please briefly glance at unit test logs even if they pass. Alternatively, just run the tests locally and ensure there's no crap in the output. It'll be immediately obvious.12:10
robcresswellThat's all from me, and there's nothing else on the agenda.12:11
robcresswell#topic Open Discussion12:11
*** openstack changes topic to "Open Discussion (Meeting topic: horizon)"12:11
tsufievrobcresswell, do we need to do something about domain-scoped warnnings?12:11
robcresswellAnything anyone wants to discuss?12:11
tsufievor is it just about some new warnngs?12:11
doug-fishdomain scoped warnings? is this a new bug?12:12
tsufievdoug-fish, now, it´s the part of unit test glitches which don´t cause tests to fail12:12
tsufiev*no12:12
doug-fishI see12:12
*** klkumar has joined #openstack-meeting-312:13
robcresswellThe issue specifically in this bug report is that UTs can error, but not fail. I'm not entirely sure why. Normally I would say missing assertions, but some don't even seem to complete their assertions and still pass, if the error stops the UT getting to that stage.12:13
tsufievI´d like to step my with my usual portion of integration test patches :)12:13
tsufievrobcresswell, I think that just some changes not yet properly covered with UT12:14
mrungeo/12:14
r1chardj0n3sOh, a reminder that there's another Bug Day next week if everyone's up for it - I am going to take a day out of vacation for it :-)12:14
tsufievhttps://review.openstack.org/#/q/topic:bp/integration-tests-improvements-part1 - that´s a big chain of patches12:14
robcresswellOh, good point r1chardj0n3s12:14
robcresswellLet me find the mail archive12:14
robcresswell#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/083224.html12:15
robcresswellThe proposed date is the 12th of January12:16
mrungesounds good12:17
tsufievbtw I´m still on a vacation this week (which means that I´m either doing interesting things, or easy ones)12:17
*** obondarev_ has quit IRC12:17
robcresswelltsufiev: Understood, I'll avoid pinging you12:17
robcresswell:)12:17
doug-fishtsufiev: Are you calling us easy? or interesting?12:17
doug-fish:-)12:18
tsufievrobcresswell, well, if it´s _interesting_ :)12:18
r1chardj0n3sdoug-fish: lol12:18
r1chardj0n3sI will be on vacation again most of next week also but I won't be doing interesting *or* easy things on my vacation days :-P12:18
tsufievdoug-fish, I meant specific pathes and reviews :)12:18
tsufiev*patches12:18
tsufievhehe12:18
tsufievrobcresswell, doug-fish: you may be interested in this patch https://review.openstack.org/#/c/263455/12:20
r1chardj0n3sjust on the angular side of things: there is movement, it's just slower than it has been previously. The UX team are doing their thing with the Swift interface, coming to terms with it and Swift in general. My angular rewrite of the current interface is already superior in a number of ways, even though it's not even at feature parity yet :-)12:20
betherlyre the bug day. Is there a specific time or just generally all day across the time zones?12:20
tsufievit should allow us to modify test jobs on gate side on our own, without infra team assitance12:20
robcresswellbetherly: Generally across all time zones12:20
tsufievlearn that trick for Sahara devs12:20
r1chardj0n3sbetherly: it's the 12th of January wherever you happen to be12:21
betherlyawesome thanks robcresswell :)12:21
r1chardj0n3susually that means I kick it off in UTC+1112:21
tsufievr1chardj0n3s, nice!12:21
tsufiev*learned trick from Sahara devs12:21
betherlyits in the calendar :) ill be around12:21
r1chardj0n3scool!12:21
* tsufiev needs to get used again to his keyboard12:21
doug-fishtsufiev: I'm looking at the patch you linked - I don't recall what kind of test related infra changes we've needed in the past?12:21
mrungeI'm quite concerned about the size of angular patches12:22
betherlyalmost ready to start pushing the ironic plugin so I will be more generally around soon! Wooooooo12:22
robcresswellr1chardj0n3s: I think a lot of the angular work is a bit more stable nowadays, I meant more that the review pace is lacking a bit on our side. I may be projecting though :)12:22
r1chardj0n3smrunge: indeed, I've been trying to keep them under control, with incremental changes12:22
tsufievdoug-fish, it is for modifying the gate environment - for example, capping the version of Firefox being installed at gate12:22
betherlyrobcresswell: that sounds exciting :D12:22
r1chardj0n3sperhaps we need to re-consider our stance on feature branches - but I'm not even sure how those work in OpenStack ;-)12:22
doug-fishtsufiev: ah okay, got it12:22
mrungeI mean, even a small feature like the images table became easily 5k lines of code and counting12:22
r1chardj0n3srobcresswell: angular is scary to review :-/12:23
robcresswellmrunge: One thing to keep in mind is that since there are a lot of new files, there is a *lot* of boilerplate in the form of code comments and licenses12:23
tsufievdoug-fish, the idea is to make all changes in scripts at horizon repo, then just source them at gate12:23
r1chardj0n3smrunge: yep, it's like Diana's CSS megapatch that I asked her to break up into steps so it wasn't 3k lines of change12:23
mrungerobcresswell, it's lots of code duplication as well12:23
betherlyr1chardj0n3s: tell me about it. I didn't do angular before openstack so the learning process had been fun lol12:23
r1chardj0n3smrunge: code duplication?12:23
mrunger1chardj0n3s, I was referring to .js files, not css12:23
robcresswellmrunge: Yeah, I did ask that to be addressed at the summit, not sure if anything has come out of it yet.12:23
mrungenope, nothing came out12:24
r1chardj0n3sbetherly: yep, so actually you're ideal to review this stuff: if you don't understand what the code is doing, we need to be told so it can be documented better - or just written less "cleverly" :-)12:24
mrungecomparison .js to .py code is at least a factor of 512:24
r1chardj0n3s(sometimes we software developers can get caught up in being too clever)12:24
robcresswellr1chardj0n3s: Things like new workflows etc. I'm finishing create network right now, and there's a couple files where I've primarily just copied a s//g12:24
robcresswellcopied and *12:24
betherlyof course. I will definitely be doing more horizon reviews so I will focus in on the angular12:24
*** pauloewerton has joined #openstack-meeting-312:25
r1chardj0n3sbetherly: thanks!12:25
r1chardj0n3srobcresswell: yep12:25
robcresswellwhich isn't really ideal considering how angular directives are designed to be reused.12:25
r1chardj0n3srobcresswell: copy-paste means you're using the correct patterns!12:25
r1chardj0n3s:-)12:25
r1chardj0n3s(I kid)12:25
betherlytheres got to be a way to create more theming and less duplication within the angular as well as just the styling12:25
r1chardj0n3sthe module files though, yeah, they're just copy-pasted12:26
robcresswellI've no doubt you and rajat will tear it apart when I upload it r1chardj0n3s :)12:26
betherlyits working out how though with the size of whats being accomplished and therefore the amount of code :/12:26
r1chardj0n3srobcresswell: I'm totes a nice reviewer12:26
betherlyhaha12:26
tsufievmrunge, perhaps we need Angular code-generator written in Python ;)?12:26
mrungehahaha tsufiev12:26
r1chardj0n3stsufiev: you should do that!12:26
*** shwetaap has quit IRC12:27
robcresswellso tempted to action that and leave it written in stone12:27
r1chardj0n3s(I think someone proposed that in Paris actually, though it was just Python-Javascript ;-)12:27
tsufievwell, I think Angular directives could do better in terms of reducing boilerplate code12:27
mrungeyes!12:27
r1chardj0n3stsufiev: I think they already are! the action lists ones in particular are great!12:27
robcresswellSome parts are unavoidable, like the licenses and comments12:28
r1chardj0n3swe will just create more as we see the patterns emerge12:28
mrungenot sure if I still find the patches with lots of code looking duplicate or doubled12:28
r1chardj0n3sthe API interface files all look very, very similar, yes12:28
* tsufiev curious how long did it take for Python table pattern to emerge...12:28
mrungetsufiev, that pattern was there since ever12:28
r1chardj0n3stsufiev: I was just about to point out the table directives we've also got ;-)12:28
robcresswellDon't hold up Horizons table code as a shining example of good code :p12:29
tsufievhaha )12:29
*** rtheis has joined #openstack-meeting-312:29
tsufievrobcresswell, totally agree!12:29
r1chardj0n3simplementing the new swift interface has been helped immensely with the table and action list stuff12:29
mrungehehe robcresswell12:29
r1chardj0n3sHorizon's Python table code hurts my head :-(12:29
robcresswellThere is some good angular work. I think we need to reign in the scepticism a little, we've got good people doing good work and we should try to embrace that, IMO.12:29
r1chardj0n3sI'm only concerned about hitting M with any new interfaces12:30
robcresswellconcerned that we won't get there? Or how to execute it?12:30
r1chardj0n3sconcerned the code won't land in time12:30
r1chardj0n3soh, also! the libraries updates!12:31
r1chardj0n3shttps://etherpad.openstack.org/p/horizon-libs12:31
r1chardj0n3s#link https://etherpad.openstack.org/p/horizon-libs12:31
r1chardj0n3seven12:31
robcresswell#link http://lists.openstack.org/pipermail/openstack-dev/2016-January/083365.html12:31
r1chardj0n3sso that's the big list of xstatic and we need to think about which ones we update12:31
r1chardj0n3sI'm on call if we need help with that, especially if it's a pypi access issue12:31
mrungeoh, btw, I came acress direct patches for Xstatic libraries12:32
mrungeI think that was magic-search12:32
r1chardj0n3speople are patching xstatic libraries?12:32
mrungeyes, unfortunately yes12:32
r1chardj0n3swow12:32
robcresswellSo, I thought magic search was being pulled into Horizon?12:32
r1chardj0n3s(also, ouch)12:32
robcresswellOr was that a different lib.12:32
r1chardj0n3srobcresswell: nah, we patch the crap out of it12:32
r1chardj0n3swe should just vendor it though12:32
r1chardj0n3sIIRC we talked a bit about this in Tokyo but didn't make a decision12:33
mrungehttps://review.openstack.org/#/c/263699/12:33
r1chardj0n3sI *think* someone said they'd go and look at alternatives, but I guess that didn't happen12:33
robcresswellSure, I thought at the summit we decided to pull the useful bits into Horizon, or a Horizon-controller section12:33
robcresswellHorizon-controlled*12:33
r1chardj0n3smy memory is obviously hazy on what we decided :-(12:34
mrungeI think we talked about magic-search being a piece of crap12:34
robcresswellha12:34
mrungeand we were fine with forking that one12:34
r1chardj0n3smrunge: don't hold back there ;-)12:34
robcresswellMy recollection is we decided to pull it in12:34
mrungeyes, sounds like that12:35
r1chardj0n3sok12:35
mrungebiut https://review.openstack.org/#/c/263699/ is driven by magnum?12:35
mrungemagnum ui to be precise12:35
robcresswellYeah, I believe magnum UI is broken atm due to an issue with magic search12:36
robcresswellBut I haven't looked into it enough to know if that solution is correct.12:36
mrungeconsensus at the summit was: we need something else12:36
robcresswellmrunge: Lol, we seem to have 3 different ideas what was agreed at the summit.12:37
mrungerobcresswell, iirc, we agreed on pulling it in or better: find something new12:37
mrungeand when pulling in, we should rework most of it12:37
robcresswellSo in the last days meetup etherpad, there is a note to bring in magic-search and remove that requirement12:37
robcresswellBut it isn't owned by anyone.12:38
mrungehah12:38
robcresswellLet's address that. I'll speak with rajat or matt later and see if there is time to work on pulling that in and removing that dependency12:39
robcresswellThere's no point overriding so much of it within Horizon12:40
mrungecould you ask them to fix the issues (in terms of overriding)?12:40
mrungei.e. make our changes the default?12:40
r1chardj0n3swe can't change upstream to match the Horizon needs, no12:40
mrungethat's a better idea12:41
*** atuvenie has joined #openstack-meeting-312:41
r1chardj0n3soh, it's a better idea, but upstream doesn't want our changes12:41
robcresswellYeah12:41
mrungeiirc they already tried12:41
robcresswellIIRC we override the entirety of the styling too12:41
mrungeand they didn't accept changes12:41
robcresswellRight12:41
*** jaypipes has joined #openstack-meeting-312:42
robcresswellSo upstream isn't an option.12:43
robcresswellAnd we're already overriding half the JS and all of the styling.12:43
robcresswellHow big is the lib?12:43
mrunge300 lines of code?12:44
mrunge425 lines12:44
robcresswellSo its feasible to just have that within Horizon, no?12:44
mrunge... creating a fork12:45
mrungejust to be clear.12:45
*** efoley has quit IRC12:45
mrungeshouldn't we name it then differently?12:45
mrungeor something like that12:45
r1chardj0n3swe already have something in a vendor directory, right?12:46
*** tellesnobrega is now known as tellesnobrega_af12:46
*** claudiub has joined #openstack-meeting-312:46
mrungesince our version has nothing to do with the original version, other than the name12:46
robcresswellIt is a fork, but since we're only using a subsection of it, I'm not sure it matters. It would just become a part of Horizons core and we can adapt it fit the openstack ui's properly.12:46
r1chardj0n3sI think it'd be best to retain the name12:46
robcresswellAt the moment its externality is more hindrance than help.12:46
r1chardj0n3ssame name == continuity and some credit to the original authors12:47
mrungesame name, but that's all12:47
r1chardj0n3shorizon/static/horizon/lib is where we currently have the vendored thing, I believbe12:47
r1chardj0n3sno, the functionality is largely the same still too, as is the *idea*12:48
mrungeand we could give credit to the original author anyways12:48
*** primeministerp has joined #openstack-meeting-312:48
r1chardj0n3sbut whatever, I'm not going *argue* for it :-)12:48
mrungehehehe12:48
robcresswellHmm12:48
mrungeugh, I thought we had removed *all* copied code12:49
robcresswellr1chardj0n3s: Would you prefer we maintain the external package and override it?12:49
mrungebut then we have this: https://github.com/openstack/horizon/blob/master/horizon/static/horizon/lib/jquery/jquery.bootstrap.wizard.js12:49
r1chardj0n3srobcresswell: nono, we should vendor it12:49
r1chardj0n3smrunge: yes, the other vendored thing12:49
mrunge:-/12:50
robcresswellSeparate issue, but that should be external. I don't think it even carries any Horizon specific code.12:51
robcresswellJudging from the patch history, that is.12:51
r1chardj0n3sI don't know the history of that, might be pre-xstatic?12:51
robcresswellI think it is12:51
mrungeyepp, me too12:52
robcresswellIn my head magic search would just be adopted as a core directive in Horizon, and we merge our multitude of overrides and customisations with it12:52
*** pauloewerton has left #openstack-meeting-312:52
robcresswellSo we end up with a 400 line "hz-magic-search" or similar.12:52
mrungeI would argue: if we're changing the magnitude on it, we might have it internal12:53
r1chardj0n3syep12:53
mrungebut then we should make it clear it's changed12:53
robcresswell#action robcresswell Investigate vendoring magic search12:53
r1chardj0n3s+1 robcresswell12:54
r1chardj0n3s+bus robcresswell12:54
robcresswellExcellent12:54
robcresswellBack to the XStatic packages as a whole, it would be excellent if people could look into individual lib upgrades and see if they are necessary12:55
*** davidsha has quit IRC12:55
robcresswellWe don't need to update-for-the-sake-of-updating, but some of the packages are >1 year out of date IIRC, which is about a rather long time in web terms12:55
*** sagar_nikam has joined #openstack-meeting-312:56
robcresswellI know hurgleburgler already has workarounds for Bootstrap issues, so that would be a good one to update.12:56
mrungeI would think we should do that asap, since it bears the risk to break us12:56
robcresswellmrunge: Agreed, the sooner we update the sooner we can find issues. I'll be working on it, and I believe Rajat already has some patches out.12:57
tsufievrobcresswell, shouldn´t XStatic packages automatically consume the freshest version of corresponding libjs-* system package?12:58
r1chardj0n3stsufiev: xstatic packages don't consume system packages12:59
*** klkumar has quit IRC12:59
r1chardj0n3ssystem packagers replace xstatic contents with their own when they package xstatic for their systems12:59
mrunger1chardj0n3s, they should12:59
tsufievhmm, I recall I read something like that in our recent doc about XStatic12:59
robcresswellWe're about at time, so we can continue in #openstack-horizon12:59
*** abalutoiu has joined #openstack-meeting-312:59
*** lpetrut has joined #openstack-meeting-312:59
robcresswellIf anyone has questions with xstatic packaging or bug day, please reply on the mailer. It's good to keep the discussion going there for all to see.13:00
robcresswellThanks all!13:00
r1chardj0n3so/13:00
robcresswell#endmeeting13:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:00
openstackMeeting ended Wed Jan  6 13:00:36 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-01-06-12.00.html13:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-01-06-12.00.txt13:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-01-06-12.00.log.html13:00
mrungethanks all13:00
alexpilo_#startmeeting hyper-v13:00
openstackMeeting started Wed Jan  6 13:00:58 2016 UTC and is due to finish in 60 minutes.  The chair is alexpilo_. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: hyper-v)"13:01
openstackThe meeting name has been set to 'hyper_v'13:01
alexpilo_Morning!13:01
primeministerpmorning!13:01
claudiubo/13:01
*** robcresswell has left #openstack-meeting-313:01
sagar_nikamHi All, Happy new year !!!!13:01
claudiubhappy new year. :)13:01
alexpilo_Happy New Year!! :-)13:01
*** kmbharath has joined #openstack-meeting-313:01
*** umargolin has quit IRC13:01
atuvenieo/13:02
*** itoader has joined #openstack-meeting-313:02
alexpilo_up your "hands" folks, let's see who do we have today13:02
alexpilo_lpetrut?13:02
*** r1chardj0n3s has left #openstack-meeting-313:02
alexpilo_sagar_nikam: is sonu joining us?13:02
abalutoiuo/13:02
*** egallen has joined #openstack-meeting-313:03
itoadero/13:03
sagar_nikamyes13:03
sagar_nikamhe said he will join13:03
*** kvinod has joined #openstack-meeting-313:03
lpetruto/13:03
alexpilo_he sent a patch yesterday, we reviewed quickly to be able to discuss it today13:04
sagar_nikamsure13:04
alexpilo_but we can start with the other topics13:04
sagar_nikamkvinod: Sonu joining ?13:04
alexpilo_#topic FC support13:04
*** openstack changes topic to "FC support (Meeting topic: hyper-v)"13:04
alexpilo_lpetrut: any updates?13:04
kvinodSonu will join13:04
lpetrutyep, so, all the os-win FC related patches have merged13:05
*** baoli has joined #openstack-meeting-313:05
lpetrutthe CI and unit tests should be all green on the nova patches once we do an os-win version bump, so we should try to get those merged as soon as possible13:05
*** Sonu has joined #openstack-meeting-313:05
alexpilo_sweet13:06
lpetrutsagar: have you guys looked over those patches?13:06
*** zz_dimtruck is now known as dimtruck13:06
*** baoli has quit IRC13:06
lpetrutsagar: it would be great if you could give it a try on your environment13:06
sagar_nikamsure13:06
sagar_nikami will have somebody check it13:06
sagar_nikamcan you add me as reviewes13:07
lpetrutthanks a lot, please let me know how it works for you13:07
lpetrutsure13:07
sagar_nikamreviewer13:07
*** baoli has joined #openstack-meeting-313:07
alexpilo_#link https://review.openstack.org/#/c/258617/13:08
lpetrutI know this is unrelated to FC, but here's the iSCSI refactoring patch: https://review.openstack.org/#/c/249291/ it's currently marked as WIP because we're currently working on the unit tests, but it would be great if you guys could give us some feedback on this as well13:08
*** kvinod has quit IRC13:09
lpetrutmost probably we'll get this merged today13:09
alexpilo_there's still a -1 by walter here13:09
alexpilo_anybody knows his IRC nic?13:09
alexpilo_hemna, afaik13:10
lpetrutyep, basically, he requested a few more info to be provided. such as whether multipath should be used, and the os_type and platform13:10
lpetrutyep13:10
sagar_nikamlpetrut: this has the fix for CHAP ?13:10
alexpilo_his not on this channel anyway13:10
alexpilo_lpetrut: let's stick to FC13:10
sagar_nikamok13:10
claudiubhemna is on the #openstack-nova channel.13:10
alexpilo_we'll switch topic to iSCSI soon13:10
lpetrutmy bad, sure13:10
sagar_nikamand the fix for rescan ?13:10
alexpilo_sagar_nikam: ^ :-)13:10
sagar_nikamok13:11
lpetrutI guess I'm a bit over enthusiastic about this one :)13:11
lpetrutany other questions related to FC?13:11
*** baoli has quit IRC13:11
alexpilo_there are no HP reviews on all Nova FC patches13:12
sagar_nikamnot from my side13:12
alexpilo_only the last one in the chain13:12
sagar_nikamkurt ?13:12
alexpilo_we need reviews on all of them:13:12
alexpilo_#link https://review.openstack.org/#/c/25861413:12
sagar_nikami thought he did the reviews13:12
alexpilo_#link https://review.openstack.org/#/c/25861513:12
alexpilo_#link https://review.openstack.org/#/c/26098013:12
lpetrutjust a side note: I'll add the vHBA support ASAP13:12
alexpilo_just a quick not on vHBA13:13
*** kvinod has joined #openstack-meeting-313:13
alexpilo_we have two separate options, passthrough and vHBA13:13
alexpilo_vHBA is a more flexible feature and easier to implement as it doesn't require all the hassle required by passthrough13:14
alexpilo_especially for live migration13:14
sagar_nikamyes remember and i think we decided to first implement passthrough13:14
alexpilo_but it has some very hard limitations:13:14
alexpilo_1) no boot from volume13:14
alexpilo_2) guest OS support requirement13:14
lpetrutso we'll implement both, maybe passthrough as default, letting the user opt for vHBA by setting the bus type to FC13:15
alexpilo_so for this reason it will be implemented separately as soon as the current patches merge13:15
sagar_nikamok13:15
alexpilo_Im just recapping this here to make sure we keep focus on passthrough13:15
sagar_nikami think even kurt had suggested pass through... if i remember right13:16
*** baoli has joined #openstack-meeting-313:16
alexpilo_for the rest, priority is on getting Cloudbase and HP +1s13:16
alexpilo_so that we can move the patches to the Nova etherpad queue13:16
sagar_nikamalexpilo_: we have 3 patches ?13:16
sagar_nikamthat needs review ?13:16
alexpilo_413:16
alexpilo_the last one is the first link I posted (the one with hemna's review)13:17
sagar_nikam614,815  abd 98013:17
sagar_nikamok13:17
alexpilo_25861713:17
*** baoli_ has joined #openstack-meeting-313:17
alexpilo_anything else you'd like to add on FC?13:18
alexpilo_sagar_nikam, lpetrut13:18
lpetrutnot on my side13:18
sagar_nikamno, we will start the review, i think we will need Kurt to review all 413:18
alexpilo_sweet, tx!13:18
sagar_nikamwill let him know13:18
alexpilo_#topic iSCSI 3par support13:18
*** openstack changes topic to "iSCSI 3par support (Meeting topic: hyper-v)"13:18
alexpilo_now is the time to get wild on iSCSI :-)13:19
primeministerpbuckwild13:19
sagar_nikam2 issues that we have seen in 3par iscsi, CHAP and rescan13:19
lpetrutheh, so, lun rescanning is in place now13:19
sagar_nikamlpetrut: already merged ?13:19
sagar_nikamlun rescan13:19
lpetrutnope, it's the patch I mentioned before13:20
lpetrutpassing CHAP credentials when logging in portals: not yet. As this was causing issues with other backends, I wanted to test this first.13:20
*** baoli has quit IRC13:20
alexpilo_sagar_nikam: this brings up the topic we discussed on Monday13:20
alexpilo_using the FC 3par array for iSCSI testing as well13:21
primeministerp*nod*13:21
primeministerpWe need hba's for the array13:21
alexpilo_so, as soon as we have the additional HW in place, we will start testing this ASAP13:21
alexpilo_primeministerp would you like to add something here?13:22
primeministerpsagar_nikam, someone on your side was looking into that13:22
*** dslev has joined #openstack-meeting-313:22
*** sagar_nikam_ has joined #openstack-meeting-313:23
primeministerpbasically we're going to need the hba to add the iscsi functionality to the array13:23
primeministerpwe may need additional licensing as well13:23
sagar_nikam_lpetrut: did you see kmbharath: patch13:24
sagar_nikam_on CHAP13:24
sagar_nikam_he had a fix for it many months back13:24
*** sagar_nikam has quit IRC13:24
primeministerphmmm13:24
primeministerphopefully he'l reconnect13:25
lpetrutyep, but I was thinking whether we can save time by not logging in the portal twice (once without CHAP creds, once with CHAP creds), and maybe use a flag on the Cinder side. Like "portals_requires_chap_auth" or something similar13:25
sagar_nikam_i am connected13:25
primeministerp;)13:25
sagar_nikam_kmbharath: your comments ?13:26
sagar_nikam_on lpetrut: suggestion13:26
lpetrutwe could just push this into the volume connection info13:26
*** moshele has joined #openstack-meeting-313:26
alexpilo_sagar_nikam_: as previously discussed we need to ensure that this patch wont cause issues to other backedends13:26
kmbharathYes agreed, if we  have a flag and do it , it would be better13:26
alexpilo_as the 3par one seems to be the only one with this requirement13:26
sagar_nikam_ok13:26
kmbharathwe had tested it on HP LeftHandnetwork and 3par earlier13:26
alexpilo_the option is probably the only way to do that13:27
lpetrutgreat, do you know by any change what backends require this? Is it just 3PAR, are all 3PAR backends requiring this?13:27
alexpilo_but:13:27
sagar_nikam_from our tests, only 3par13:27
alexpilo_what if we have 2 backends, e.g. a 3par and another 3rd party one?13:27
sagar_nikam_LHN/VSA worked without any change13:27
alexpilo_one expecting portal logins and the other one failing?13:27
alexpilo_the flag won't help, as it would force login on all of them13:28
lpetrutno, why?13:28
alexpilo_becuase the other backend would fail13:28
alexpilo_an option (I believe suggested by lpetrut) would be to try the login and silently continue if it fails13:29
lpetrutthe other backend would not set this flag, and we would not use CHAP creds when logging in the portal, so it should not fail13:29
lpetrutplease correct me if I got something wrong13:29
kmbharathcan't we do check for backend type....13:29
alexpilo_that would require changes on the cinder side13:29
kmbharathbecause its only 3par what we had seen needs the portal login13:30
sagar_nikam_lpetrut: who will set the flag ? every cinder driver ?13:30
lpetrutthis can be optional, but the driver would set it when providing the connection info13:30
alexpilo_or we could simply have a list of backends in the Nova driver with the drivers requiring portal login13:30
*** dimtruck is now known as zz_dimtruck13:31
lpetrutalso, the connection info does not include the backend type at the moment13:31
alexpilo_by making it an option, this could be configurable13:31
alexpilo_lpetrut: d'oh, that'sa  blocker13:31
sagar_nikam_alexpilo_:this option looks better13:31
alexpilo_lpetrut sagar_nikam_: let's bring this back to the witheboard and sync again next week13:32
sagar_nikam_having list of backends in nova is better than cinder sending it in connection_info13:32
kmbharaththe target_iqn in connection info could help us to identify the backend13:32
lpetrutkmbharath: umm, is this reliable enough?13:32
*** jlanoux has joined #openstack-meeting-313:33
lpetrutalexpilo_: ok, we can talk about this later so that we don't block the meeting for this13:33
sagar_nikam_lpetrut: i think the iqn had 3par in it13:33
sagar_nikam_ok, let move to next topic13:33
lpetrutsagar_nikam: sure, just wanted to make sure that this happens all the time13:33
sagar_nikam_can we have some networking discussion13:33
kmbharathyes we had seen it everytime13:33
sagar_nikam_sonu: is here i thinl13:34
alexpilo_did sonu join?13:34
SonuI am listening..13:34
sagar_nikam_i saw him joining13:34
alexpilo_great13:34
primeministerpsagar_nikam: yes13:34
alexpilo_#topic SGR RPC patch13:34
*** openstack changes topic to "SGR RPC patch (Meeting topic: hyper-v)"13:34
* alexpilo_ fetches link...13:34
alexpilo_#link https://review.openstack.org/#/c/263865/13:35
alexpilo_first, thanks Sonu for the patch13:35
alexpilo_did you see claudiub's review?13:36
SonuI am reviewing the same.13:36
SonuThanks for the comments. I will fix them and re-post13:36
alexpilo_we prioritized it right away to be sure we could talk about it today13:36
SonuThanks for that13:36
alexpilo_claudiub Sonu: anything to add?13:36
SonuThis patch is dependent on https://review.openstack.org/#/c/240577/13:37
Sonuthere was a bug in base security groups driver, which I have fixed and Review is in progress.13:37
claudiubcould you then add a Depends-On: <change-id> here?13:37
alexpilo_btw we need a BP for this13:37
SonuI will mark the dependency13:37
claudiubcool ty. :)13:37
SonuGot it. I will work on the same.13:37
*** piet has joined #openstack-meeting-313:38
alexpilo_sweet13:38
alexpilo_moving to a broader topic:13:38
alexpilo_#topic networking-hyperv improvements13:38
*** openstack changes topic to "networking-hyperv improvements (Meeting topic: hyper-v)"13:38
*** dslev has quit IRC13:38
alexpilo_let me share some of the design aspects related to this agent13:39
alexpilo_there are a few improvements going on13:39
alexpilo_we already talked about this a while back, when we talked about the multiprocessing patches that HP sent for SGR13:39
alexpilo_we are currently finalizing the results, which will turn into a BP13:40
alexpilo_1) drop the port discovery loop and replace it with WMI events13:40
alexpilo_2) use PyMI13:41
alexpilo_3) replace associator queries with direct WQL queries13:41
alexpilo_4) parallelize all the things :)13:41
*** alexstav has joined #openstack-meeting-313:42
alexpilo_this includes in particular ACL which are a big bottleneck13:42
kvinodalexpilo_ : are you talking about new approach of multiprocessing13:42
alexpilo_unlike the Juno patch that HP is using, this doesnt require multiprocessing13:43
kvinodis this blueprint on multiprocessing going to be different from what we posted?13:43
alexpilo_PyMI (unlike the old WMI + pywin32) is designed to work with multiple threads13:43
alexpilo_kvinod it's quite different, especially in the implementation13:43
alexpilo_this is the reason why it has been kept on hold13:44
kvinodok, then are you saying that HP's patch sets are not required and will not get merged?13:44
sagar_nikam_alexpilo_: how are the tests in a scale environment with this new approach ?13:45
alexpilo_surely not in the current status13:45
claudiubso, I've tested the patchsets you've sent and there are a couple of issues.13:45
alexpilo_kvinod: ^13:45
SonuOne biggest problem that we had encountered during scale was, too many port updates introducing delays in processing of new port additions.13:45
alexpilo_sagar_nikam_: we are testing with Rally on scale13:45
claudiubthere are 2 big issues atm: 1. logging doesn't work, apparently, I've just noticed 30 minutes ago13:45
Sonuthats one reason we separated addition of ports into a different workers scheduled on another CPU13:46
alexpilo_Sonu: you can just use threads for that, no need for multiple processes13:46
claudiubwith the workers patch, logging is only done to stdout, the neutron-hyperv-agent.log is empty13:46
claudiuband second, it seems that the agents die randomly during rally.13:47
claudiubthey freeze, leading to missing to report the alive state, leading to failing to spawn vms, as the neutron agents are considered to be dead and the neutron ports couldn't be bound13:47
*** alexstav has left #openstack-meeting-313:48
Sonuhmm thats a news :)13:48
kvinodclaudiub : we already noticed the logging issue and we solved it by making child process send message to parent process about port binding success or failure and parent process will log into log file13:48
alexpilo_kvinod: that is unnecessary work13:48
claudiuband thirdly, if there is any issue in binding a port over and over and over again, the neutron-hyperv-agent process will consume the whole cpu.13:49
kvinodalexpilo_ : we did it that way due to limitation in logging framework as it doesnot works for multiprocessing13:49
alexpilo_sorry for trinmming the discussion, as we have only 10' left13:49
claudiubkvinod: yeah, i've seen that. if i start the process manually and see the std, i can see what happens in the child processes, including traces and so on. but there's nothing in the log file.13:50
claudiubstdout*13:50
alexpilo_the idea of parallel execution in the agent is of course the common goal here13:50
alexpilo_Python's multiprocessing brings a lot of unnecessary drawbacks and there's no reason to use it13:50
alexpilo_threads / green threads work perfectly fine as long as the underlying WMI calls are non-blocking13:51
alexpilo_(otherwise we'd hit the GIL issue, which is I guess why you opted for multiprocessing)13:51
Sonuyes you got it right13:52
alexpilo_the discussion is anyway much broader, which is why this BP is taking a while13:52
claudiubi'm currently trying out native threads, to see how it's going with those.13:52
SonuVinod had tried all such possibilities13:52
sagar_nikam_Sonu: Can you review the new approach if a patchset is available13:52
*** alexstav has joined #openstack-meeting-313:53
sagar_nikam_and check how it will work13:53
Sonuhe can help you with his findings and observations13:53
claudiubi haven't uploaded the native threads patch yet13:53
sagar_nikam_based on our scale tests run on Juno13:53
alexpilo_Sonu kvinod: that's why we wrote PyMI ;)13:53
Sonugreat13:53
alexpilo_the main aspect here, is that the ACL API are simply terrible and no matter how you look at them they dont scale13:53
SonuI will have a look at the new patch set and try13:53
sagar_nikam_claudiub: patchset not available yet ?13:54
kvinodok, please upload your patches13:54
claudiubsagar_nikam_: native threads, not yet, still working on it.13:54
alexpilo_so all this parallelization work is improving a bit the situation, but a more drastic approach will be needed13:54
alexpilo_kvinod: expect the patches sometimes next week13:54
alexpilo_1) the OVS driver will become the preferred option as soon as conntrack will be available on our Windows port13:55
sagar_nikam_sonu: kvinod: you had seen issues with security groups as well13:55
alexpilo_as this is required for an SGR as well13:55
Sonuhave you seen the development -  https://review.openstack.org/#/c/24933713:55
alexpilo_2) we're evaluating a complete rewrite of the ACL WMI API13:56
*** baohua has joined #openstack-meeting-313:56
alexpilo_Sonu: tep, that's what I'm referring to13:56
Sonuthis is OVS firewall being done once OVS conntrack is available13:56
alexpilo_we need conntrack on Windows for that to work13:56
alexpilo_which is our main goal for OVS 2.613:57
primeministerpSonu: could we have an offline discussion about the HP networking hardware that supports protocol accelleration, I want to see if what it would take to add OVS and Native vswitch testing on the appropriate network hba, the ones we currently have in the HP 3Par ci only support accellerated iSCSI13:57
Sonugot it.13:57
alexpilo_3 minutes to go13:57
Sonusure primeministerp13:57
SonuSagar mentioned about it13:57
sagar_nikam_primeministerp: sure i will connect you and Sonu: on this topic13:58
primeministerpSonu, awesome13:58
alexpilo_changing topic, if you'd like to go on with this topic, please let's move to #openstack-hyper-v13:58
primeministerpthanks sagar_nikam_13:58
alexpilo_#topic PyMI13:58
*** openstack changes topic to "PyMI (Meeting topic: hyper-v)"13:58
alexpilo_so PyMI is feature complete for all OpenStack use cases13:58
alexpilo_it has been tested under heavy load with Rally13:58
sagar_nikam_that is a very good news13:58
primeministerpwoot13:58
alexpilo_sagar_nikam_: do you think you could test it in your environments?13:59
sagar_nikam_yes, we will13:59
alexpilo_we tested, kilo, liberty and mitaka (master)13:59
sagar_nikam_i need to get some slots from scale team to test this13:59
alexpilo_all CIs are now switching to it, including nova, neutron, networking-hyperv, compute-hyperv and the cinder ones13:59
sagar_nikam_most of our environments have also move to Liberty14:00
sagar_nikam_need to find Juno14:00
sagar_nikam_for testing pyMI14:00
*** Poornima has joined #openstack-meeting-314:00
alexpilo_perfect tx!14:00
alexpilo_time's up! :)14:00
alexpilo_#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Jan  6 14:00:40 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
sagar_nikam_thanks all14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-01-06-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-01-06-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2016/hyper_v.2016-01-06-13.00.log.html14:00
Sonuthx bye14:00
*** Sonu has quit IRC14:00
*** vtech has joined #openstack-meeting-314:01
*** kmbharath has left #openstack-meeting-314:01
primeministerpsagar_nikam_, I don't think I have sonu's email could you sent it to me?14:01
moshelehi any neutron qos guys around?14:01
*** JeanBriceCombebi has quit IRC14:01
*** klkumar has joined #openstack-meeting-314:01
ihrachysmoshele: I am here, but I suspect ajo  is not14:01
*** absubram has joined #openstack-meeting-314:02
ihrachyswe can run one nevertheless if we have some quorum14:02
alexstavHi all :)14:02
irenabHi guys14:02
mosheleyes, ihrachys you want to lead this or shall I ?14:02
ihrachysmoshele: go ahead :)14:02
*** absubram_ has joined #openstack-meeting-314:02
moshele#startmeeting neutron_qos14:02
openstackMeeting started Wed Jan  6 14:02:59 2016 UTC and is due to finish in 60 minutes.  The chair is moshele. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:03
openstackThe meeting name has been set to 'neutron_qos'14:03
moshelehi everone14:03
*** alexstav has left #openstack-meeting-314:03
ihrachyso/14:03
mosheleajo is still on PTO so I will replace him today14:03
*** julim has quit IRC14:03
irenabmoshele: I do no think anyone can replace ajo :-)14:04
ihrachysI guess we want to focus on whatever is on https://etherpad.openstack.org/p/qos-mitaka14:04
*** shwetaap has joined #openstack-meeting-314:04
mosheleirenab: I gess you right :)14:04
mosheleyes14:04
* ihrachys just walked thru it several minutes before the meeting, updated a bit14:04
mosheleso I know that ajo is working on the upgrade patches14:04
ihrachysI guess it's not uploaded yet, I haven't seen any14:05
*** vmahe has joined #openstack-meeting-314:05
ihrachysdevref is merged, but that's it14:05
*** davidsha has joined #openstack-meeting-314:05
moshelehe said he will upload it  on  the 8th14:05
mosheleI think14:05
*** atuvenie has quit IRC14:05
ihrachyshe is an optimistic guy ;)14:05
ihrachyswe'll see14:06
*** absubram has quit IRC14:06
*** absubram_ is now known as absubram14:06
mosheleRBAC spec already one  +214:06
mosheleso I guess it close to merge14:06
ihrachyshdaniel: ^14:06
ihrachysmoshele: spec, yeah. code wise, I guess we still have stuff to tinker14:06
*** ifat_afek has quit IRC14:06
ihrachysbut the patch is up for some time: https://review.openstack.org/#/c/250081/14:07
*** sagar_nikam_ has quit IRC14:07
ihrachysit may actually work, but there are some concerns to clear around code decomposition14:07
mosheleand it has -114:07
ihrachysfour -1s :)14:07
mosheleis hdaniel here?14:08
hdanielyep14:08
hdanielthe code cleanups are mostly done - one issue still unresolved - need ihrachys for that14:08
hdanielbut that might require a complete code reshuffle14:09
ihrachyshdaniel: yeah, let's schedule a chat for this week, f.e. tomorrow, so that we can clear it.14:09
hdanielihrachys: sounds solid to /me14:09
ihrachyshdaniel: not complete! just around 80% maybe!14:09
*** sreshetnyak has joined #openstack-meeting-314:10
moshelelet move to the Linux bridge  rate limite14:10
ihrachysyeah!14:10
mosheleis slaweq here?14:10
ihrachysI don't see Slawek here14:10
ihrachysbut anyway, I can probably update14:11
moshelego head14:11
ihrachysso extension manager support is finally in gate or merged: https://review.openstack.org/#/c/250542/14:11
ihrachysSlawek will need to rebase his patch for LB qos on top of it.14:11
ihrachysalso I believe there is some work to do for fullstack framework here: https://review.openstack.org/#/c/248938/14:11
ihrachyswhich is a blocker for the qos patch14:11
*** lblanchard has joined #openstack-meeting-314:11
ihrachysfor what I wonder, Slawek is actively looking at both14:12
ihrachysthat's it14:12
*** luisfdez has joined #openstack-meeting-314:12
*** dslevin_ has joined #openstack-meeting-314:12
moshelecool I will add the fullstack patch to etherpad14:12
ihrachysit's there I think14:13
mosheleyes I just saw it :)14:13
moshelemoving to DSCP Markings14:13
*** kzaitsev_mb has joined #openstack-meeting-314:13
mosheleI didn't see mach activity there14:14
ihrachysyeah. also it has two dependencies14:14
ihrachysone is upgrade thing from ajo, another one the agent uuid for graceful restart from me14:14
davidshaNo, we're waiting on the l2 agent extension api14:14
ihrachys#link https://review.openstack.org/#/c/263819/14:15
davidshaYa ^14:15
ihrachys^ that's the spec for phase1 of my ovs proposal that will allow to unblock qos14:15
ihrachysjust exposing uuid14:15
*** zz_dimtruck is now known as dimtruck14:15
ihrachysand then I will be able to work on remaining table rework in my pace14:15
*** Poornima has quit IRC14:16
ihrachysI plan to start coding the bits this week14:16
mosheleI will review the l2 agent extension api spec14:17
ihrachysthanks. it's tiny.14:17
*** peristeri has joined #openstack-meeting-314:18
mosheleanything else on the DSCP Markings14:18
moshele?14:18
davidshaNo, not at the moment14:18
davidshaThanks.14:18
moshelelet move to bugs14:19
mosheleI didn't see any new bug regrading qos14:19
irenabI added rfe (ajo asked me before he went to PTO)14:20
irenabhttps://bugs.launchpad.net/neutron/+bug/153148514:20
openstackLaunchpad bug 1531485 in neutron "Available device bandwidth report by L2 agent" [Undecided,New]14:20
davidshaI submitted a rfe for priority queueing https://bugs.launchpad.net/neutron/+bug/152767114:20
openstackLaunchpad bug 1527671 in neutron "Neutron QoS Priority Queuing rule" [Wishlist,Confirmed]14:20
ihrachysirenab: well, that one probably also depends on agent API14:21
ihrachysbecause you would need some way to pass data from extension into the agent.14:21
irenabihrachys: I will check the API, but I think its just adding more content to the agent report status14:21
mosheleirenab: how you plane to report the physical device bandwidth information for OVS? it know only the bridges14:22
ihrachysirenab: yeah, but how would your extension talk to the agent? currently it's completely stateless for what agent cares.14:22
ihrachysmoshele: underlying physical devices?14:22
mosheleyes14:23
*** primeministerp has quit IRC14:23
irenabboth SR-IOV and OVS  had mappings  to physical devices, so it should be quite easy14:23
irenabihrachys: Will check your spec to see what will it require to pass details to the agent14:23
ihrachysnot much, just another agent API for just that.14:24
*** kzaitsev_mb has quit IRC14:24
ihrachysnot sure I love passing it through state reports, but I haven't thought it through yet to comment.14:24
irenabthere was some bug reported by vikram on netowrk policy repurposing14:24
*** neelashah has joined #openstack-meeting-314:25
*** kvinod has quit IRC14:25
irenabihrachys: I do not have any strong preferences14:26
irenabhttps://bugs.launchpad.net/neutron/+bug/152119414:26
openstackLaunchpad bug 1521194 in neutron "Qos Aggregated Bandwidth Rate Limiting" [Wishlist,Triaged]14:26
irenabihrachys: would be great if you can check this14:27
mosheleyes so what I didn't understand for his spec is how he plane to implement it14:27
*** jpomeroy has joined #openstack-meeting-314:27
mosheleso there will be to behaviors to network qos14:27
irenabI think we first need to agree on the problem he solves :-)14:27
ihrachysirenab: ack, adding to todo14:28
irenabHe suggested to change the existing network -policy association meaning14:28
mosheleI understood the he want to support both cases14:29
ihrachyswell, you could just divide it to the number of ports :), but that's not what we probably want14:29
ihrachysirenab: api change? meh14:29
*** kzaitsev_mb has joined #openstack-meeting-314:29
*** dimtruck is now known as zz_dimtruck14:29
irenabihrachys: not the api change, but change of the current intention14:29
moshelelet say you have 20GB network and 10 vm so each vm will get 2 GB14:30
ihrachyshm, I did not know that we intended to do aggregation before14:30
ihrachyswhere was the intent captured?14:30
irenabI think its new14:31
davidshaIt was brought up last meeting14:31
davidshaabout 4 weeks ago14:31
ihrachysthe way we designed it, it was always 'the default value to apply to port if no port level policy is attached'. if it's documented in another way, we should fix the docs14:31
irenabihrachys: I think vikram documented it well on this bug report. Let’s see what would be the best way to handle it14:31
ihrachysok, I will check it later with more attention14:32
irenabihrachys: agree, need to verify the documentation14:32
*** baohua has quit IRC14:32
*** baohua has joined #openstack-meeting-314:33
ihrachysmoshele: should we move?14:34
mosheleyes sorry14:34
mosheleI think we are done14:34
mosheleanyone has anything to add ?14:34
ihrachysnot me14:35
irenabno14:35
mosheleok thanks everyone14:35
moshele#endmeeting14:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:35
openstackMeeting ended Wed Jan  6 14:35:49 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-01-06-14.02.html14:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-01-06-14.02.txt14:35
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2016/neutron_qos.2016-01-06-14.02.log.html14:35
ihrachysadieu14:35
irenabthanks, bye14:36
davidshathanks14:36
*** moshele has left #openstack-meeting-314:37
*** Swami has joined #openstack-meeting-314:38
*** piet has quit IRC14:39
*** kzaitsev_mb has quit IRC14:39
*** piet has joined #openstack-meeting-314:39
*** rbak has joined #openstack-meeting-314:41
*** julim has joined #openstack-meeting-314:49
*** shinya_kwbt has joined #openstack-meeting-314:50
*** bklei has joined #openstack-meeting-314:51
*** tellesnobrega_af is now known as tellesnobrega14:51
*** betherly has left #openstack-meeting-314:51
*** rhochmuth has joined #openstack-meeting-314:54
*** fabiog has joined #openstack-meeting-314:55
*** jmckind has joined #openstack-meeting-314:55
*** fabiog has quit IRC14:57
*** fabiog has joined #openstack-meeting-314:58
*** mrmartin has quit IRC14:58
*** sigmavirus24_awa is now known as sigmavirus2414:59
*** ddieterly has joined #openstack-meeting-315:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Jan  6 15:00:17 2016 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmutho/15:00
ddieterlyo/15:00
fabiogHappy New Year!15:00
rbako/15:00
rhochmuthwelcome back everyone15:00
bkleio/15:00
shinya_kwbto/15:01
*** mhoppal has joined #openstack-meeting-315:01
bkleihappy new year!15:01
rhochmuthagenda has been posted at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
*** tgraichen has joined #openstack-meeting-315:01
rhochmuthAgenda for Wednesday January 6, 2016 (15:00 UTC)15:01
rhochmuth1. Mid-Cycle/Meet-up go/no go and proposed agenda (fabiog)15:01
rhochmuth2. What e-mail validator do we use at python monasca-api? (shinya)15:01
rhochmuth  2.1 Voluptuous validator which is used by monsaca-api has no e-mail validator but has url one.15:01
rhochmuth  2.2 lepl.apps.rfc3696 - MPL 1.1 License http://www.acooke.org/lepl/15:01
rhochmuth  2.3 validate_email - LGPL License https://pypi.python.org/pypi/validate_email15:01
rhochmuth  2.4 Regex15:01
rhochmuth3. TWC updates15:01
rhochmuth 3.1 UI update15:01
rhochmuth 3.2 Any progress on caching from HPE?15:01
rhochmuth 3.3 Openstack requirements in 3 files, required for rally tests15:01
rhochmuthAlso, we are a bit backed up on reviews for a number of reasons15:02
rhochmuthMainly, the holidays and the gates are not functioning right now due to changes in the tempest tests15:02
rhochmuthSo, let's start with the mid-cycle meet-up15:02
rhochmuth#topic mid-cycle15:03
*** openstack changes topic to "mid-cycle (Meeting topic: monasca)"15:03
rhochmuthfabiog, this is yours15:03
fabioghere it is the doodle: http://doodle.com/poll/yy4unhffy7hi3x6715:03
fabiogI have 6 people confirmed for Thu 28/2915:03
fabiogand on the 28 we will share the day with Congress15:03
fabiogmeaning fostering integration and collaboration15:04
rhochmuthi thought the congress discussion was going to be on tuesday or wednesday15:04
rhochmuthleaving thursday and friday open for monasca15:04
rhochmuthis that not correct15:05
fabiognope15:05
fabiogCongress is 3 days15:05
fabiogTue to Thu15:05
*** baohua_ has joined #openstack-meeting-315:05
*** baohua has quit IRC15:05
rhochmuthbut i tought the monasca topics were going to be on tues/wed originally15:05
fabiogyes15:05
fabiogthat was the original plan15:05
fabiogbut I am hosting both15:06
fabiogand I cannot be in two places at the same time15:06
fabiog:-)15:06
rhochmuthohh, i see15:06
fabiogI thought that since you guys were coming, we could have a joint session on Thu15:06
rhochmuthi thought you were only attending the monasca related discussions for congress15:06
fabiogno, I am hosting the mid-cycle15:07
rhochmuthso, i can attend the congress related discussions15:07
fabiogyes15:07
rhochmuthbut, i'm concerned now about short-changing monasca15:07
rhochmuthif folks are traveling for a monasca mid-cycle, and thursday is still on congress mainly, that leaves only one day for monasca discussions15:08
*** jobrs has joined #openstack-meeting-315:08
rhochmuthi don't think most of the folks traveling are as interested in congress related discussions15:09
fabiogI can get a second room and have the congress stuff running only in the morning15:09
fabiogbut I will be able to attend either one or the other session15:09
fabiogI think this is doable15:10
rhochmuthok15:10
rhochmuthso let's discuss other topics for the mid-cycle then15:10
rhochmuthmeant agenda15:10
*** zz_dimtruck is now known as dimtruck15:10
rhochmuthwhat else should be on the agenda for the mid-cycle, in addition to congress discussions15:11
*** mhoppal has quit IRC15:11
rhochmuththe logging api would be one area that i'm interested, but we don't have representation from fujitsu15:12
*** mhoppal has joined #openstack-meeting-315:12
rhochmuthat the mid-cycle15:12
bkleii'd like to add an arch discussion about concurrency, and possible solutions15:12
bkleiconcurrent queries, that is15:12
bkleiwe're hitting some hard limits with vertica, not sure if influxdb, cassandra would be better15:13
rhochmuthjust a litle more context then15:13
bkleiwe're working closely with the vertica team, but we're a couple orders of magnitude off from the concurrency we'd like to support15:14
bkleiit may be vertica isn't a great fit for our use case15:14
bkleilike 100 users, all loading a grafana dashboard at the same time :)15:14
bkleiand each dashboard translates to 150 queries15:15
*** mhoppal has quit IRC15:15
fabiogso you need to support 1000+ concurrent queries15:15
bkleidon't need to discuss here, just would like as a topic at the meetup15:15
bkleilike 20K15:15
bkleiideally15:15
rhochmuthok, thanks for the context15:15
rhochmuthi'm not sure about cassandra or influxdb either15:15
*** numans has quit IRC15:15
*** mhoppal has joined #openstack-meeting-315:16
rhochmuthpersonllay, i think we need to start considering adding an in-memory time-series database/cache15:16
bkleiright, something15:16
rhochmuthok, other topics then for the mid-cycle15:16
*** baohua_ has quit IRC15:17
bkleimaybe an overview/demo of grafana 2.0?15:18
*** catherineD has joined #openstack-meeting-315:18
rhochmuthhas ryan completed that?15:18
bkleiupdate coming :)15:18
*** leecalcote has joined #openstack-meeting-315:18
rbakI should have it done by the mid-cycle15:19
rhochmuthok15:19
rhochmuththere are other features that we could discuss, such as retention periods15:19
fabiogI am wondering if we want to do a couple of days using webex instead and have people from Europe to attend too15:20
bkleioh yes15:20
bkleioh yes on retention periods rhochmuth15:20
rhochmuthit does seem like the agenda is a bit limited15:21
fabiogrhochmuth: that is my feeling too15:21
*** absubram has quit IRC15:21
fabiogrhochmuth: but we can have a couple of good webex sessions to iron out the issues and see the demos15:21
rhochmuthi think i would push for a webex too, at this point15:21
fabiogand if people in the US are willing to travel anyway we can be in a room with telepresence15:21
tgraicheni think this would be very good - maybe at least one or a few15:21
rhochmuththen i would also suggest that we have the monasca mid-cycle the following week15:22
fabiogrhochmuth: yes15:22
rhochmuththe first week of february sometime15:22
fabiogsure15:22
rhochmuthso as not to overlap with congress15:22
rhochmuthi would like to attend the congress related discussion15:22
fabiogwhat about two mornings15:22
*** jmckind_ has joined #openstack-meeting-315:23
fabiogWed and Thu?15:23
rhochmuthyes, that would work well for me15:23
rhochmuthmornings are best for folks in europe too15:23
fabiogpeople already have time on wed this time15:23
fabiogso we could start the webex at 7am to noon15:23
fabiogso it is kind of feasible for Europe to follow15:23
rhochmuthsure, that would work15:23
fabiogand if needed we will repeat the next day15:23
fabiogok, then is set15:24
fabiogI will send an invite to people and post a note in the monasca dev list15:24
rhochmuthwed/thurs feb 3rd and 4th15:24
fabiogyes15:24
rhochmuth7-12 PST15:24
*** egallen has quit IRC15:25
rhochmuthok, sounds like we should move on to the next topic15:25
*** jmckind has quit IRC15:25
rhochmuth#topic e-mail validator15:25
*** openstack changes topic to "e-mail validator (Meeting topic: monasca)"15:25
shinya_kwbtHello. this is mine.15:26
rhochmuthhi Shinya15:26
*** yamahata has quit IRC15:26
*** tsv has joined #openstack-meeting-315:26
*** mtanino has joined #openstack-meeting-315:26
shinya_kwbtI'm writing python monasca-api notification methods e-mail validator.15:26
*** yamahata has joined #openstack-meeting-315:26
shinya_kwbtJava monasca-api uses apache commons validator and javax.mail validator under review.15:27
rhochmuthyes, i recall there were some problems with this15:27
shinya_kwbtI see. And python momnasca-api uses voluptuous validator. But voluptuous has no e-mail validator but has url one.15:27
*** iyamahat has joined #openstack-meeting-315:28
rhochmuthso, i wouldn't restrict to using voluptuous15:28
*** galstrom_zzz is now known as galstrom15:28
rhochmuthwe've had some disucssion on removing voluptuous15:28
*** iyamahat has quit IRC15:28
rhochmuthand hand-coding15:28
*** egallen has joined #openstack-meeting-315:28
*** iyamahat has joined #openstack-meeting-315:29
shinya_kwbtOh. I see.15:29
rhochmuththeir aren't any immediate plans to remove voluptuous, but if it was in your way15:30
rhochmuththen i would be fine not using it15:30
shinya_kwbtIs hand-coding for example regex better? or use other library?15:32
rhochmuthi don't have experience beyond voluptuous15:32
rhochmuthso, i can't answer that question15:32
rhochmuthbut, i think a regex is ok15:33
rhochmuthin this case15:33
*** leecalcote has quit IRC15:33
shinya_kwbtO.K. I try to write with regex. thank you.15:33
rhochmuthok, thanks15:34
rhochmuththere should be lot's of examples15:34
shinya_kwbtyes.15:34
rhochmuthok, i think we are ready for the next topic15:34
rhochmuth#topic ui update15:35
*** openstack changes topic to "ui update (Meeting topic: monasca)"15:35
rbakI guess that's me15:35
rhochmuthit is15:35
rbakI'm working on the grafana/keystone integration, and I have it partially working.15:35
rhochmuthwhat was your overall design15:36
rbakSo you can log into grafana with keystone creds and it will assign you an org corresponding to your tenant, which shares dashboards.15:36
rbakThis isn't working yet, but the idea is that it will then use your creds to get tokens for the monasca queries so you don't need a token in the datasource.15:37
rhochmuthso, will you login to horizon and grafana?15:38
*** vijendar has joined #openstack-meeting-315:38
rbakI'd like to have horizon pass the necessary information to grafana, but I haven't looked at that yet.15:38
tgraichendo you have keystone v3 support in mind from the beginning?15:38
rbakNo, I haven't thought about v3 support much, but I can look into tha.15:39
rhochmuthtgraichen, this would probably be a good area for you to get input to rbak on15:39
tgraichenok - let me know if you need help or support testing v3 related stuff15:39
rbakwill do15:40
*** Sukhdev has joined #openstack-meeting-315:40
rhochmuthrbak, is your latest code in github15:40
rbakNot yet, I'll put it up once it's tested15:40
rbakBut fair warning, this isn't pluggable15:40
rhochmuthi translated that into this isn't easy15:40
rbakUntil it's merged upstream you'll have to build your own grafana.15:41
rhochmuthhow difficult is it to get going with grafana 315:41
rhochmuthfor example, if you clone the grafana 3 repo, clone your branch when avaialble15:42
rhochmuththen do some configuration15:42
rbakThere's a grafana 3 now?15:42
tgraicheni think he mans 2 :)15:43
rbakOh, good15:43
rhochmuthit's the new year15:43
rbakThat had me worried.15:43
tgraicheni think rbaks point was, that you can't use prebuilt grafana binaries anymore15:43
rbakRight15:43
rbakFor the datasource you can just install and then drop the files in.15:43
rbakFor the keystone integration you have to clone and build.15:44
rhochmuthgot it15:44
rbakIt's not terrible, just some extra work15:44
rhochmuthgrafana 1 was javascipt only15:44
rhochmuthso no compile step15:44
rbakThis work is primarily in go15:44
tgraichendid you already contact the grafana maintainer, if he would be willing to include this upstream when ready?15:44
rbakNot yet.  I wanted to make sure I knew this was possible to implement first.15:45
tgraichensure15:45
rbakI've started looking into that though.15:45
tgraichenmaybe creating an issue in the grafana github when ready15:45
rbakThey seem to suggest just creating a pull request.15:46
tgraichenok15:46
rbakThat's all  I have unless there's more questions.15:47
rhochmuththanks rbak15:47
*** cloudtrainme has joined #openstack-meeting-315:47
rhochmuthlooking forward to this15:47
rhochmuth#topic caching15:48
*** openstack changes topic to "caching (Meeting topic: monasca)"15:48
rhochmuthno updates15:48
rhochmuthi just got back from the break15:48
bkleii figured, with the holiday15:48
bkleion your list?15:48
*** brunssen has joined #openstack-meeting-315:48
rhochmuthi'm not sure15:48
*** devananda has quit IRC15:48
rhochmuthi've got a lot on my plate15:48
bkleiok, maybe it'll be part of the mid-cycle discussion15:49
bkleii don't think i'll get to it between now and then either15:49
rhochmuthsounds like everyone is busy15:49
bkleifor sure15:50
rhochmuthso, table this for the mid-cycle15:50
rhochmuthalong with concurrrent queries15:50
bkleisounds good15:50
rhochmuth#topic openstack requirements in 3 files15:50
*** openstack changes topic to "openstack requirements in 3 files (Meeting topic: monasca)"15:50
bkleithat's me15:50
*** klkumar has quit IRC15:50
bkleiyan is working on rally tests, currently has an issue with incompatible requirements15:51
*** klkumar has joined #openstack-meeting-315:51
bklei Incompatible requirement found; see http://docs.openstack.org/developer/requirements/15:51
*** iyamahat has quit IRC15:51
bkleishe's saying we need to change openstack/requirements repo in global-requirements.txt, projects.txt, and upper-constraints.txt15:51
*** iyamahat has joined #openstack-meeting-315:51
bkleii guess it's in one, not all 315:51
bkleii don't know much about this, but any objections to us just adding monasca client to all 3?15:52
*** egallen has quit IRC15:52
rhochmuthfabiog added this recently, i guess in just the one spot15:52
bkleiRequirement set([Requirement(package=u'python-monascaclient', location='', specifiers='>=1.0.24', markers=u'', comment='', extras=frozenset([]))]) not in openstack/requirements15:52
rhochmuthi don't see any issues adding to all 3 spot15:52
bkleiis her error15:53
bkleiok15:53
fabiogrhochmuth: bklei yes I added to global15:53
bkleiok, if you don't add to the other two, either yan or i will15:53
fabiogrhochmuth: but I was waiting for the change of oslo library15:53
*** cbouch has joined #openstack-meeting-315:53
rhochmuthhmmm, i thought we got the changes for the oslo libraries compleete15:54
fabiogbklei: the client is using an old oslo library that needs to be updated15:54
bkleioh15:54
fabiogonce it is updated we can merge the global and the others15:54
fabiogbklei: that is why is still not merged15:54
bkleiwho's working that?15:54
rhochmuthjoe keen15:54
bkleiok, can follow up with him and watch for changes15:54
fabiogbklei: please keep me in the loop15:55
*** jmckind has joined #openstack-meeting-315:55
bkleiok15:55
rhochmuthi thought he had completed prior to xmas15:55
rhochmuthis this just an issue for tagging again15:55
rhochmuthdo, i just need to apply a tag15:55
fabiogthese are the two related patches15:55
fabioghttps://review.openstack.org/#/c/251674/15:56
fabioghttps://review.openstack.org/#/c/252527/15:56
*** stanchan has quit IRC15:56
rhochmuthi'll check with joe15:56
bkleithx15:56
ddieterlyrhochmuth: looking for a +2 on https://review.openstack.org/#/c/254403/ and https://review.openstack.org/#/c/254425/15:57
*** gema has joined #openstack-meeting-315:57
rhochmuthok15:57
rhochmuthbut i was waiting on the gates working again15:58
*** jmckind_ has quit IRC15:58
ddieterlythe gate is working again15:58
*** ningy has joined #openstack-meeting-315:58
ddieterlyi pushed the changes thru this morning after working with ghansyam last night15:58
rhochmuthok, thanks15:58
*** krtaylor has quit IRC15:58
*** neelashah has quit IRC15:59
ddieterlyhttps://review.openstack.org/#/c/263529/15:59
rhochmuthi'll +2 the other changes and start catching up again15:59
rhochmuthon other reviews15:59
rhochmuthwe'll need to coveer cassandara next week15:59
bkleii think we're out of time, can hold my cassandra question15:59
bkleiyup15:59
*** AlanClark has joined #openstack-meeting-315:59
rhochmuthbye everyone15:59
rhochmuththanks15:59
bkleithx15:59
ddieterlyciao15:59
*** mhoppal has quit IRC15:59
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Jan  6 16:00:10 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-01-06-15.00.html16:00
*** neelashah has joined #openstack-meeting-316:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-01-06-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2016/monasca.2016-01-06-15.00.log.html16:00
*** zehicle_ has joined #openstack-meeting-316:00
eglute#startmeeting defcore16:00
*** rosmaita has joined #openstack-meeting-316:00
zehicle_o.16:00
openstackMeeting started Wed Jan  6 16:00:23 2016 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: defcore)"16:00
openstackThe meeting name has been set to 'defcore'16:00
zehicle_o/16:00
rosmaitao/16:00
eglute#link agenda https://etherpad.openstack.org/p/DefCoreRing.716:00
eglute#topic agenda16:00
*** openstack changes topic to "agenda (Meeting topic: defcore)"16:00
markvoelkero/16:00
hogepodgeo/16:01
egluteHello Everyone! Happy New Year!16:01
AlanClarko/16:01
gemao/16:01
hogepodgeHappy New Year!16:01
*** shinya_kwbt has quit IRC16:01
*** devananda has joined #openstack-meeting-316:01
zehicle_:)16:01
eglutePlease review the agenda, and add things as needed! https://etherpad.openstack.org/p/DefCoreRing.716:01
eglute#topic midcycle16:02
*** openstack changes topic to "midcycle (Meeting topic: defcore)"16:02
*** tgraichen has quit IRC16:02
*** dcarmon has joined #openstack-meeting-316:02
eglutedo not want to spend too much time on this, but how does everyone feel about holding a midcycle16:02
eglute#chair zehicle_16:02
openstackCurrent chairs: eglute zehicle_16:02
*** itxaka is now known as itxaka|afk16:02
*** bklei has quit IRC16:03
markvoelkerI'm game.  They've been productive in the past.16:03
zehicle_looking at the agenda items, it makes sense to me16:03
zehicle_timing will be painful16:03
egluteok, then we will need to send a poll regarding times and locations...16:03
*** cloudtrainme has quit IRC16:03
eglute#action eglute send out poll for midcycle times + locations16:04
*** jobrs has quit IRC16:04
*** ningy has quit IRC16:05
eglutelet me and Rob know if you have any suggestions regarding locations16:05
*** SammyD has joined #openstack-meeting-316:05
egluteWe can start a separate etherpad for work that needs to be done during midcycle16:05
hogepodgeI'm always up for Austin, fwiw16:05
* zehicle_ we have a bias towards central Texas. 16:05
eglutei am ok with Austin, despite its traffic16:06
eglutezehicle_ did you wanted to talk about standalone tests, or leave that for later?16:06
*** cloudtrainme has joined #openstack-meeting-316:07
zehicle_I can introduce - not sure we're ready for a discussion at this point16:07
zehicle_basically, the recent VM vs Zone discussion brought up that it would be helpful for DefCore to had dedicated interop tests16:07
eglutemaybe a quick intro so people can start thinking about it :)16:07
zehicle_that were not also trying to test the function of the code base (aka gate)16:07
*** spotz has joined #openstack-meeting-316:07
zehicle_that dual purpose was making it harder to add/maintain tests.16:07
*** spotz has left #openstack-meeting-316:08
zehicle_so we could split out the tests that we are using (effectively fork)16:08
zehicle_then it would be easier for community to add interop tests16:08
markvoelkerIt was also discussed, though, that having interop tests in the gate was important so interop features don't get broken16:08
zehicle_but it means that DefCore has to maintain them16:08
zehicle_markvoelker, that has been my strong preference for not forking16:09
purpo/16:09
zehicle_markvoelker, do you see people creating interop tests?16:09
brunsseno/16:09
SammyD+1 on not forking. What about a dedicated package inside the standard tempest? I.E. an InterOp package that contains only interop tests, but lives with the rest of tempest tests...16:09
*** galstrom is now known as galstrom_zzz16:09
eglutewould it be worthwhile to have a mailing list discussion on this?16:10
zehicle_SammyD, that's a good middle ground.16:10
gemaprobably, it'd be useful to see what exactly makes a test "interop"16:10
* purp is mostly lurking from a plane waiting for a gate.16:10
zehicle_any dedicated DefCore tests require resources16:10
*** krtaylor has joined #openstack-meeting-316:10
eglutei like SammyD suggestion16:11
zehicle_this was a complex enough topic, that we thought it would be for the Midcycle (instead of regular agenda)16:11
hogepodgeWe can tag tests, although that has not been successful in the past (smoke, gate)16:11
brunssen+1 on SammyD's suggestion16:11
*** Catherine has joined #openstack-meeting-316:11
markvoelkersure, thanks for teeing it up though16:11
zehicle_however, if there's strong interst.  it makes sense to bring people to the Midcycle who can help build the framework to start it16:11
*** Catherine is now known as Guest9459416:12
eglutehow about this- lets start a mailing list discussion and hopefully work on it during midcycle?16:12
markvoelkerI'm not seeing strong interest in the scrollback. =)16:12
*** salv-orlando has joined #openstack-meeting-316:12
hogepodgestarting from scatch is a bad idea, it would take lots of work16:12
* eglute agrees16:12
hogepodgeappropriating (and expanding or modifying) existing tests and identifying holes to fill is better16:13
purp+1 SammyD's separate pkg, +11 on mid cycle topic16:13
eglute#action zehicle_ and eglute start a mailing list discussion regarding defcore tests16:13
SammyD+1 mid cycle16:13
*** vgridnev has joined #openstack-meeting-316:13
purpAnd +aLot to mid cycle not in Austin, as we'll all be there in May.16:14
eglute#topic Austin Summit DefCore submissions16:14
*** openstack changes topic to "Austin Summit DefCore submissions (Meeting topic: defcore)"16:14
purpHPE would be happy to host in Fort Collins. =]16:14
*** sdake has joined #openstack-meeting-316:14
eglutethanks purp will add it to the list!16:14
*** inbar_stolberg has quit IRC16:14
* zehicle_ Ft Collins in mid-Feb actually may work very well for me16:14
* markvoelker wouldn't mind being back in his old stomping grounds in Ft. Collins personally16:15
eglute#info purp HPE would be happy to host in Fort Collins. =]16:15
purpeglute: could also likely manage Houston16:15
eglutecool, lest talk on that later in defcore irc channel16:15
purpSorry, didn't mean to hijack.16:15
egluteAustin summit submissions are now open16:16
egluteso please share ideas and submissions!16:16
markvoelkerOn that note, please remember that only 3 submissions per person (including panels) are allowed under the new submission process.16:16
egluteI think the sessions went well in Tokyo, there is definitely a lot of interest in defcore16:17
eglutemarkvoelker is right! and we want to have defcore submissions16:17
* zehicle_ thinks they've disallowed unicorns and rainbows from titles16:17
markvoelker#link http://superuser.openstack.org/articles/how-to-land-a-successful-openstack-summit-talk details about new submission rules16:17
*** kebray has joined #openstack-meeting-316:17
eglutenext topic!16:18
*** vhoward has joined #openstack-meeting-316:18
* purp waves at kebray 16:18
eglute#topic remove tests for image import16:18
*** openstack changes topic to "remove tests for image import (Meeting topic: defcore)"16:18
egluterosmaita are you around?16:18
rosmaitahi16:18
*** belmoreira has quit IRC16:18
rosmaitamight be best to read the comments on the patch, mark's response, and my response to him16:19
egluteyou had some great comments on #link https://review.openstack.org/#/c/239830/16:19
eglutewould you mind summarizing?16:19
rosmaitasure16:19
rosmaitabasically, glance is working on a new image import workflow for Mitaka16:19
rosmaitaspec was approved last week16:19
egluteeveryone, please read the last 3 comments on the patch :)16:20
rosmaitaso it's kind of early to include image-import as an advisory capability16:20
hogepodgeThe TC is pretty strongly opposed to this, if I understand the patch right https://review.openstack.org/#/c/256438/16:20
*** rockyg has joined #openstack-meeting-316:20
hogepodgeAs the technical leaders of the community, they've taken a stance that image upload is required for interoperability16:20
eglutehogepodge which part is TC opposing?16:20
rockygo/16:21
rosmaitahogepodge: not image upload, but image import16:21
rockyg"bring your own image"16:21
hogepodge“To give up on interoperable image uploads simply because a vendor would like to do one thing that a little bit different isn't just wrong, it would be giving up the ENTIRE effort.”16:22
zehicle_if this is new function, is it something that Defcore can absorb?16:22
*** adrian_otto has joined #openstack-meeting-316:23
*** itxaka|afk is now known as itxaka16:23
egluteso if i understand correctly, import and upload are two different capabilities?16:24
hogepodgeI'm just repeating the TC resolution that's been in the works for weeks, fwiw16:24
rosmaitaeglute: yes, import is end-user facing16:24
rosmaitait allows a deployer to validate the image16:25
rosmaita"upload" is what we currently have, just sticks the image in the glance backend16:25
egluteok16:25
SammyDimport could also potentially give a public cloud provider less heartburn since there is some validation of the image if I understand correctly16:26
rosmaitaSammyD: +116:26
zehicle_is this current or planned function?16:26
rosmaitai think this explained in the "background" section of the import spec: http://specs.openstack.org/openstack/glance-specs/specs/mitaka/approved/image-import/image-import-refactor.html16:27
rosmaitazehicle_: it's planned for Mitaka16:27
eglutehogepodge did TC elaborate between the differences of upload and import?16:27
zehicle_I understand it helps address topics raised lately and in TC position16:27
hogepodgeThe text of the resolution should speak for itself. https://review.openstack.org/#/c/256438/6/resolutions/20151211-bring-your-own-kernel.rst16:28
hogepodgeI'd encourage members of the TC to clarify with respect to the defcore patch in question.16:28
hogepodgeWe're not bound by TC resolutions, as we are a board committee, but we do have feedback from the TC as part of our underlying governance principles.16:29
zehicle_should have start w/ that patch then?  I feel like we're discussing features that are not really ready for DefCore to add to guidelines16:29
rockygand the tc will be bringing it to the board for their support16:30
rosmaitazehicle_: +116:30
markvoelkerzehicle_: I'm not sure that's the case.  The API's being tested have been around for quite some time16:30
egluteright, but then we still have existing tests that rosmaita is suggesting to have removed for reasons listed on the patch16:30
purpOne question, which rosmaita posed in the review and wasn't answered: does DefCore include admin capabilities?16:30
rosmaitathe issue is, if openstack requires direct end-user image upload, it needs to provide a responsible way to do this16:31
egluteDefCore does not currently cover admin capabilities16:31
rosmaitathe current glance upload doesn't do this16:31
zehicle_purp, no16:31
purpBy intention, or circumstance?16:31
markvoelkerpurp: intent16:31
zehicle_early on we omitted admin APIs because they are not exposed on public clouds16:31
*** bpokorny has joined #openstack-meeting-316:31
zehicle_plan was go eventually have a "flavor" of DefCore that would have admin APIs for public16:32
*** tellesnobrega is now known as tellesnobrega_af16:32
*** bpokorny has quit IRC16:32
zehicle_since there are ecosystems that would leverage them16:32
hogepodgerosmaita: from the Foundation's perspective, making a feature available after vetting of a customer is still in the spirit of interoperability. This is based on experience running a public cloud and the amount of fraud public clouds experience16:32
*** tsufiev has left #openstack-meeting-316:32
purpmarkvoelker eglute zehicle_: thanks for clarifying.16:32
eglutehogepodge can you elaborate on the fraud part16:32
*** bpokorny has joined #openstack-meeting-316:32
*** matrohon has quit IRC16:33
hogepodgeeglute: spammers using stolen credit cards to set up bots, for example16:33
*** Guest94594 has quit IRC16:33
egluteah, that kind of fraud16:34
*** dslevin_ has quit IRC16:34
purp... Or getting access and looking to hack/exploit their way into the infrastructure supporting the cloud.16:34
hogepodgeHaving a feature available by request still provides interoperability, as long as the feature is actually reasonably available16:35
egluteso, reading the TC resolution: it does not say that user should allow uploads, but cloud. which could mean admin access, would apply to some other parts of the resolution as well16:35
purpAs written I'm +1 of rosmaita's notion: add import (immediately) after Mitaka lands.16:36
purpWould also favor clarifying this with TC.16:36
rosmaitapurp: +1 on clarification16:36
egluteI am in favor of clarifying16:36
SammyD+1 purp16:37
eglutewe also need to be careful not to force a technical direction for the wrong way to upload/import images16:37
egluteespecially when there are changes in place16:37
egluterather, happening16:37
rosmaitaeglute: +116:37
markvoelker"Cloud MUST allow end user Image Uploads" < So what you're asking for clarificaftion on is whether the new BP meets that bar?  Or...?16:37
zehicle_seems like building the capability to include in the guideline would be a mid-cycle topic16:37
rosmaitamarkvoelker: the new bp will definitely meet that bar16:38
purpI'd suggest we propose it as: if it's upload, not import, then it breaks current model of not defcoring admin functions. If it's import, we need to land it first. We'd like guidance on their preference.16:38
rosmaitabut the current tests don't use that functionality (that doesn't exist yet)16:38
zehicle_I'm trying to bring us back to the process where we have TESTS and ESTABLISHED FEATURE (sorry for yelling) before we add requirements16:38
*** kebray has quit IRC16:38
SammyD+1 purp16:38
* eglute +1 purp 16:38
rosmaitazehicle_: +116:39
SammyD+1 zehicle. :-)16:39
eglutezehicle_ agree... the current question is about removing capabilities that would require admin access16:39
zehicle_we have caps that require admin?16:39
markvoelkerrosmaita: right, I guess that's why I'm asking what we're asking for clarification about. =)  Given a look at the clock, I'd suggest that someone take an AI to frame up an actual question to send to the TC and we move on to the next item in the agenda.16:39
egluteremoving them from 2016.01 so that do not become advisory16:39
zehicle_directly or indirectly?16:39
purpAbout to reach a gate, so will be more lucky than not for rest of meeting, likely. Was supposed to have deplaned just before this meeting; sorry for the wacky logistical pains.16:40
rockygzehicle_, +1 on scoring thresholds16:40
catherineDI don't think we have caps that require admin for testing16:40
purpI'll take the AI.16:40
eglute#action hogepodge rosmaita purp to clarify with TC regarding image import/upload16:40
zehicle_if they are directly requiring admin, then yes.16:40
zehicle_if they are indirectly requiring it then we need to go back to the tests16:41
hogepodgesome tests assume existing resources, which may need admin access to get there. Networks come to mind.16:41
catherineDzehicle_: The tests are not directly requireing admin....16:41
zehicle_we need effort to improve/resolve test issues.16:41
catherineDhogepodge: agree ...16:41
eglutezehicle_ from rosmaita comment "we're dealing with a capability that the community has decided does not need to be exposed to end-users, and hence isn't appropriate for inclusion in DefCore "16:42
*** vishwanathj has quit IRC16:42
eglutezehicle_ +100 on resolving test issues16:42
*** dwalleck has joined #openstack-meeting-316:42
*** armax has joined #openstack-meeting-316:42
hogepodgeno test directly needs admin access. qa is very good at identifying tests that require admin access, so we ignore them (they use a specific class that contains admin credentials, so tests that don't use that class don't need admin)16:42
eglutethis takes us to the next topic16:42
eglute#topic Finalizing 2016.01 guideline16:42
*** openstack changes topic to "Finalizing 2016.01 guideline (Meeting topic: defcore)"16:42
eglutewe have rosmaita comments on the current patch, and also the Oracle patch pending16:43
egluteflags are not time sensitive, so we can deal with them later if needed16:44
zehicle_now I'm confused16:44
*** dslevin_ has joined #openstack-meeting-316:44
zehicle_are we talking about individual tests or the whole capability?16:44
rosmaitazehicle_: sort of both16:45
*** hdaniel has quit IRC16:45
zehicle_I can see that this capability may not be widely deployed or have issues for public clouds16:45
rosmaita"image import" doesn't exist yet16:45
rosmaitaand the current tests test somethighn else16:45
egluteyeah, the whole import/upload naming is confusing16:45
zehicle_so the request here is to remove the capability because of security and control concerns?16:45
zehicle_it also seems like the "future" score may be in question too16:46
rosmaitazehicle_: yes, plus something to satisfy the capability will be introduced in mitaka glance16:46
markvoelkerAt the risk of curtailing discussion by suggesting again that we move on to other agenda items, it might be useful for folks to review the patch that added those tests/capability and then discuss, if you haven't alredy.16:46
markvoelkerThat's in: https://review.openstack.org/#/c/213353/16:47
eglutethanks markvoelker16:47
eglutebesides this issue, are there other items that we need to finalize for 2016.01?16:48
*** adrian_otto has quit IRC16:48
*** dslevin_ has quit IRC16:49
eglute#action everyone reviews 2016.0116:49
*** galstrom_zzz is now known as galstrom16:49
eglute#topic Recurring Testing16:49
*** openstack changes topic to "Recurring Testing (Meeting topic: defcore)"16:49
eglute#link https://review.openstack.org/#/c/232128/16:50
*** ddieterly has quit IRC16:50
hogepodgeI have a conversation with the foundation staff last month, and we're meeting with the lawyers this week about the powered license agreement.16:50
eglutehogepodge can you respond to the comments?16:50
markvoelkerI've started working up a new patchset on this incorporating hogepodge's most recent comments, but I noted that eglute had some questions, so haven't finished. =)16:50
*** piet has quit IRC16:50
hogepodgeWe want to be careful about how we require retesting to not make the contract difficult to sign16:50
eglutemarkvoelker that sounds good16:50
eglutehogepodge that makes sense to me!16:51
dwalleckJust a question, but why is the foundation the one to administer re-testing for public clouds?16:51
hogepodgeProducts that don't change get to keep their status. This allows for long term support of a distro. The license would renew annually with an option to terminate with 30 days notice (this was the previous license, which then became a fixed one year term license, and we want to go back to the previous model)16:52
hogepodgedwalleck: we don't want to administer the testing16:52
hogepodgedwalleck: terrible wording on my part16:52
dwalleckhogepodge: Ahh, maybe I mis-read your last comment16:52
eglutehogepodge for products that dont change, they will be timeboxed by defcore anyways, no?16:53
dwalleckgotcha. thanks!16:53
hogepodgedwalleck: we want to accept test results and inform companies that they need to submit new results or face license termination16:53
zehicle_can we quickly close on the Flag validations tests as OS specific https://review.openstack.org/#/c/244782/ ?16:53
hogepodgeWe're thinking two legal agreements, one for distros and one for public, to capture the subtleties.16:54
eglutehogepodge can you work with markvoelker on the new patch to address all the comments?16:54
eglutezehicle_ +116:54
zehicle_hogepodge, I think that makes sense BTW (two agreements)16:54
*** alexstav has joined #openstack-meeting-316:55
hogepodgeAlso, api or version updated will need new testing for the new products. But if say a company like Canonical or SuSE wants to have an Long Term Supported version, we wouldn't yank the license, just advertise that they pass a much older standard16:55
eglute#action hogepodge and markvoelker will work on a new patch for retesting16:55
markvoelkereglute: Sure, I'll draft up a new patchset based on what hogepodge said and this discussion, he can take first crack at reviewing/suggesting edits. =)16:55
eglutehogepodge that makes sense16:55
hogepodgemarkvoelker: can do16:55
eglutezehicle_ the floor is yours16:55
zehicle_my expectation was that distros would have admin tests required - as mentioned earlier.  future topic FWIW16:55
eglute#topic Flag validation tests as being OS specific16:55
*** openstack changes topic to "Flag validation tests as being OS specific (Meeting topic: defcore)"16:55
markvoelkerhogepodge:I should have something for you to look at late today.16:55
* markvoelker looks at calendar16:55
markvoelkerErr...maybe tomorrow. =)16:55
hogepodgehopefully none of that is controversial, but we want to make it reasonable for vendors and the foundation to implement and also capture the intent of the committee16:56
*** ccarmack has joined #openstack-meeting-316:56
eglutethanks markvoelker and hogepodge!16:56
zehicle_considering community discussion (esp from TC) - we're not going to move forward on that patch16:56
*** sambetts has joined #openstack-meeting-316:56
eglute#link https://review.openstack.org/#/c/244782/16:56
zehicle_should be pretty clear by now16:56
egluteright16:56
zehicle_I don't want to loose the discussion - I know it will come up again16:57
markvoelkerzehicle_: I'd suggest that DefCore Committee members record their final votes as a matter of record and ask the patch to be abandoned.16:57
zehicle_however, I'm ready to workflow -1 on it16:57
zehicle_markvoelker, that was my thinking16:57
rockygworkflow -1 works for me16:57
eglute#action DefCore committee members record final comments and votes on https://review.openstack.org/#/c/244782/16:57
*** shwetaap has quit IRC16:57
*** tellesnobrega_af is now known as tellesnobrega16:57
*** salv-orlando has quit IRC16:57
* zehicle_ add process note that flags are made to approved guidelines, not pending ones16:58
egluteright16:58
eglutewe are almost out of time, sorry we didnt get to rockyg issue16:58
*** salv-orlando has joined #openstack-meeting-316:58
eglutewe can discuss it in defcore irc channel or wait for next week16:58
hogepodgerockyg: had an observation about tests changing over the last few months, I'd like her to send something to the mailing list to expand so we can discuss next week https://etherpad.openstack.org/p/novav2extensionstestchanges16:58
egluteML discussion would also work16:59
eglutethanks everyone! I will be around in the defcore IRC16:59
markvoelkerOh, we actually discussed this issue16:59
eglute#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
markvoelkerI'll throw a link into the etherpad16:59
openstackMeeting ended Wed Jan  6 16:59:30 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-01-06-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-01-06-16.00.txt16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-01-06-16.00.log.html16:59
*** shwetaap has joined #openstack-meeting-316:59
rockygI'll forward the email to the defcore list16:59
rockygand see you on defcore channel!16:59
*** brunssen has quit IRC17:00
*** mrmartin has joined #openstack-meeting-317:00
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Jan  6 17:00:13 2016 UTC and is due to finish in 60 minutes.  The chair is alaski. 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_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
*** dcarmon has quit IRC17:00
*** dslevin_ has joined #openstack-meeting-317:00
alaskianyone around today?17:00
*** rosmaita has left #openstack-meeting-317:01
doffmOne person at least.17:01
doffmo/17:01
alaskiwoo17:01
*** mriedem has joined #openstack-meeting-317:01
mriedemo/17:01
ccarmacko/17:01
alaskitbh I almost messed up with the two odd weeks17:01
*** Sukhdev has quit IRC17:01
alaski#topic Open Reviews17:02
*** openstack changes topic to "Open Reviews (Meeting topic: nova_cells)"17:02
*** kebray has joined #openstack-meeting-317:02
alaskito start I just want to call out https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking which should have open reviews listed17:02
*** dwalleck has left #openstack-meeting-317:02
*** SammyD has quit IRC17:02
*** vineetmenon has joined #openstack-meeting-317:02
alaskiand any that come up should be added there17:02
alaskisecondly mriedem had a thing17:02
alaskiShould we propagate the soft-delete mix-in to the Flavors tables in the API DB? https://review.openstack.org/#/c/201606/17:03
vineetmenono/17:03
*** vahidh has joined #openstack-meeting-317:03
alaskithe primary folks for that code aren't here today17:04
mriedemalaski: so you said there was some api implication to that?17:04
*** itoader has quit IRC17:04
alaskiright17:04
alaskicurrently soft deleted flavors are still visible in the api17:04
mriedemcan you explain that in the change i guess?17:04
alaskiif you know the id17:04
alaskisure17:05
*** Aish has joined #openstack-meeting-317:05
alaskiI think we should strive to not have flavors be soft-deletable in the api db17:05
*** sambetts has left #openstack-meeting-317:05
mriedemi agree,17:05
doffmSounds good.17:05
*** jlanoux has quit IRC17:05
mriedemi don't know the details on the api thing, is it just the flavors api?17:05
alaskiyeah17:06
mriedemmy concern with soft deletable flavors in the api db is we don't have any way to clean them up17:06
mriedemvia nova-manage or other17:06
mriedemi'd like the ops people to be on board with that though since it's a semi api change in behavior17:06
mriedemfor cells v217:06
alaskiyeah17:06
mriedemso maybe a ML is necessary17:06
alaskiit is a bit murky because archived flavors wouldn't show up in the db17:07
alaskiso it's sort of undefined territory17:07
alaskis/db/api/17:07
doffmDoesn't very 'semi' to me. If anyone is accessing via id its kind of using 'hidden' behavior.17:07
mriedemwell, and no soft delete is still murky17:07
mriedemi had a ML thread on that subject which pittled out17:07
mriedemi was trying to figure out how to explain in the nova devref why no soft delete anymore, but never really got there17:07
alaskidoffm: agreed17:07
*** vtech has quit IRC17:07
alaskimriedem: that would be good to have eventually17:08
alaskibut yeah, ML sounds good17:08
alaski#action alaski send out ML post on removing soft-delete from flavors, and implications for API17:09
alaski#topic Open Discussion17:09
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"17:09
alaskilooks like I should send out a ML post about the meeting times, since it's easy to have mixed them up17:10
*** safchain has quit IRC17:10
doffmccarmack: how is https://review.openstack.org/#/c/225199/ coming?17:10
mriedemi see the thing here https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/flavors.py#L5417:10
ccarmackI just had a general question - are there remaining work items for cells v2 or is everything in the etherpad/17:10
*** banix has joined #openstack-meeting-317:10
ccarmackone sec doffm17:10
alaskiccarmack: there are remaining items17:10
mriedemhttps://github.com/openstack/nova/blob/master/nova/compute/flavors.py#L22217:10
mriedemdefaults to read_deleted='yes'17:11
*** rockyg has left #openstack-meeting-317:11
alaskithere's a series started at https://review.openstack.org/#/c/254434/ which is not complete17:11
vineetmenonalaski: on that topic, what is our roadmap?17:11
vineetmenonsince flavors are almost done17:11
*** egallen has joined #openstack-meeting-317:12
alaskimriedem: yeah.  I wonder if we should file a bug for that behaviour?  I'm not sure it's intentional17:12
*** stanchan has joined #openstack-meeting-317:13
alaskivineetmenon: the only open specs currently are the one related to the series I linked above, and one that melwitt is working on re: db connection switching17:13
mriedemalaski: yeah idk, might be worth asking dansmith if he knows/remembers anything17:13
*** vijendar has left #openstack-meeting-317:14
alaskiyeah17:14
mriedemalaski: as noted before, if you archive the nova db, that will return a 404 on a previously deleted flavor anyway17:14
mriedemso i don't really see much of a huge api regression in not having soft deletable flavors in the api db17:15
doffmThat looks like a bug. It would be confusing to get back a flavor that you just deleted.17:15
mriedemwe'll just tell people their admin turned on an archive cron that goes every minute :)17:15
dansmithdoffm: but that's the desired behavior17:15
alaskiheh17:15
dansmithI think a ML discussion to make sure we all understand the consequences is the best we can do17:15
dansmithaside from actually keeping the behavior17:16
alaskimriedem: that's why I think we can make a case to change the behavior, because there's no guarantee that the flavor will be there17:16
*** shwetaap has quit IRC17:16
*** neelashah has quit IRC17:16
alaskieven now17:16
doffm1 delete flavor. 2 show flavor to check its deleted. 3 get it back and look confused.17:16
dansmithalaski: right, admins could be purging flavors any time they delete them now17:17
dansmithdoffm: it's not that simple17:17
*** galstrom is now known as galstrom_zzz17:17
*** piet has joined #openstack-meeting-317:17
dansmithdoffm: the instance contains a permalink to the flavor it was created with, for all time17:17
doffmdansmith: I see.17:18
alaskinow I recall, there was some discussion on whether we need to guarantee that link stays valid.  which is not currently guaranteed17:18
mriedemdo we show that flavor id in the server get call?17:18
dansmithmriedem: yeah17:18
mriedemi'm just trying to figure out the use case17:19
dansmithmriedem: so you can follow the link to the flavor17:19
dansmithwhich is a pretty common api thing, AFAIK17:19
mriedemso boot instance with flavor 1, delete flavor 1, i want to resize/migrate instance and want to know what i'm resizing from17:19
alaskior just know what flavor it is17:19
mriedemso need the old (now deleted) flavor to do so17:19
dansmithmriedem: not only that, I just may want to look at my instance's flavor's extra specs, or do billing or something17:19
mriedemsure17:19
*** salv-orlando has quit IRC17:19
dansmithanyway,17:19
mriedemheh, maybe we shouldn't archive flavors :)17:20
*** shwetaap has joined #openstack-meeting-317:20
dansmithwe know we just have to bite this bullet, I think, so let's cast the net to the ML and see who complains17:20
*** salv-orlando has joined #openstack-meeting-317:20
*** kebray has quit IRC17:20
dansmithI expect nobody17:20
alaskithere is a path forward with flavor data in instance_extra now.  but that would only affect api > some microversion if we expose that17:20
mriedemyeah...17:20
mriedemi was going to just say that :)17:21
alaskibut for now, ML17:21
dansmithalaski: right, we probably need to expose it in the instance itself to satisfy that need17:21
alaskidansmith: yeah.  that may be better in general because it removes an extra api lookup to get at flavor info17:22
dansmithyeah17:23
*** stanchan has quit IRC17:23
alaskiccarmack: did you want to discuss https://review.openstack.org/#/c/225199/ now?17:23
ccarmackalaski:  yea, 2 of the 3 patches have workflow +1, only the tempest patch needs work.17:23
*** mrmartin has quit IRC17:24
ccarmackShould I still work on it?  Its not directly related to cells17:24
ccarmackalaski, willl cells v2 support security groups17:24
alaskiccarmack: yes, cellsv2 will support everything17:25
alaskithat's a primary reason for doing it17:25
mriedemccarmack: it also cleans up the tempest cells rc in nova17:25
*** kebray has joined #openstack-meeting-317:26
mriedemand so that we don't have to blacklist new tests that use security groups and break the cells job17:26
*** cloudtrainme has quit IRC17:26
mriedemsince it would be configurable in tempest17:26
ccarmackalaski: I probably should still finish the patch because it supposed to be a general config option17:26
mriedemthe icky part is how pervasive it is in tempest17:26
mriedemccarmack: you probably have to get with the qa team on that one, probably get it in their meeting agenda17:27
alaskiwas just looking it over, it seems worth having17:27
* dansmith has to run to another meeting17:27
mriedemo/17:27
alaskio/17:27
*** vmahe has quit IRC17:27
ccarmackmriedem: the last set of comments took me aback, as you say I should get with the qa team17:28
mriedemccarmack: http://eavesdrop.openstack.org/#QA_Team_Meeting17:28
ccarmackthanks mriedem17:28
alaskianything else for today?17:29
mriedemya17:30
mriedemis there anything documented for migration plans from v1 to v2? or too early?17:30
mriedemthere was an ops thread from mikal last july17:30
alaskiI don't think there's anything documented yet17:31
alaskiit's not in the devref at least17:31
*** vtech has joined #openstack-meeting-317:31
mriedemdo you have a rough idea?17:31
alaskiit's not too early to get the broad outline of it laid out though17:31
mriedemyeah17:31
alaskiyeah, I have a vision for how it could work17:31
alaskiI'll start writing that down17:32
mriedemanother question,17:32
*** e0ne has quit IRC17:32
alaski#action alaski write down rough migration plan for v1 to v217:32
mriedemat what point do we think we can stand up a deployment with cells v2? like is there a minimum goal that we need to get to, even if there is some missing stuff?17:32
mriedemtrying to figure out the 'roadmap' like was mentioned earlier17:33
*** cloudtrainme has joined #openstack-meeting-317:33
alaskiin my mind after the series at https://review.openstack.org/#/c/254434 (incomplete at the moment) lands we'll be in cellsv217:33
*** alexstav has left #openstack-meeting-317:34
alaskionly for booting an instance, but the basic pieces will be in place17:34
alaskilike the new db needing to be setup17:34
*** vineetmenon has quit IRC17:34
alaskimaybe a better link is https://blueprints.launchpad.net/openstack/?searchtext=cells-scheduling-interaction17:34
mriedemyeah i was going to say, should those all be linked to that bp?17:35
alaskiyes17:35
doffmalaski: Once that series is in place then cell0 will be ready? Or multiple cells?17:35
*** neelashah has joined #openstack-meeting-317:35
alaskineither17:35
alaskiwhich reminds me, we do have the cell0 spec still open17:36
alaskisomehow I keep forgetting that one17:36
doffmOk, i see the work on cell0 spec.17:36
alaskithe series above just starts filling out the instance_mapping for newly created instances17:37
mriedemlink?17:37
alaskiand then queries that when listing/showing instances17:37
*** itxaka has quit IRC17:37
alaskihttps://review.openstack.org/#/c/238665/17:38
mriedemoh merged, i see17:38
alaskiso after the above series Nova will think it is scheduling to a cell17:38
alaskithen we need to build out from there17:38
mriedemok, i'm just updating the review etherpad17:40
mriedemwith notes17:40
mriedemi don't have anything else17:40
alaskicool17:40
alaskiI guess for current roadmap I would say that the goal this cycle is to have instance boots using the cells paradigm17:40
alaskiand the flavor migration17:41
mriedemso https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/cells-scheduling-interaction and https://review.openstack.org/#/c/21304117:41
mriedemalright17:41
alaskiyeah.  and cell0 which is related to the scheduling one17:41
mriedemgonna have this all merged by feb :) ?17:41
*** yamahata has quit IRC17:42
alaskiheh.  as much as I can :)17:42
alaskithe more I work on it the more of a mess I feel I need to untangle to get this working17:42
mriedemi guess i have to start reviewing some code17:42
mriedemwrap up?17:43
alaskiyep17:43
* mriedem is hangry17:43
alaskiunless someone speaks up in the next 5 seconds17:43
alaski#endmeeting17:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:43
openstackMeeting ended Wed Jan  6 17:43:44 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-01-06-17.00.html17:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-01-06-17.00.txt17:43
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2016/nova_cells.2016-01-06-17.00.log.html17:43
alaskithanks all17:43
*** mriedem has left #openstack-meeting-317:43
*** ccarmack has left #openstack-meeting-317:44
*** tsv has quit IRC17:44
*** iyamahat has quit IRC17:44
*** klkumar has quit IRC17:51
*** bharathm has quit IRC17:52
*** cloudtrainme has quit IRC17:53
*** mrmartin has joined #openstack-meeting-317:55
*** cloudtrainme has joined #openstack-meeting-317:56
*** iyamahat has joined #openstack-meeting-317:58
*** davidsha has quit IRC17:58
*** Swami has quit IRC18:00
*** yamahata has joined #openstack-meeting-318:05
*** neelashah has quit IRC18:08
*** salv-orlando has quit IRC18:08
*** salv-orlando has joined #openstack-meeting-318:09
*** ihrachys has quit IRC18:10
*** catherineD has quit IRC18:14
*** dslevin_ has quit IRC18:14
*** stanchan has joined #openstack-meeting-318:16
*** SridarK has joined #openstack-meeting-318:18
*** mrmartin has quit IRC18:19
*** egallen has quit IRC18:19
*** jpomeroy has quit IRC18:20
*** bharathm has joined #openstack-meeting-318:20
*** dslevin_ has joined #openstack-meeting-318:22
*** nelsnelson has quit IRC18:24
*** nelsnels_ has joined #openstack-meeting-318:24
*** Swami has joined #openstack-meeting-318:25
*** absubram has joined #openstack-meeting-318:25
*** mickeys has joined #openstack-meeting-318:26
*** adrian_otto has joined #openstack-meeting-318:27
*** egallen has joined #openstack-meeting-318:30
*** egallen has quit IRC18:32
*** stanchan has quit IRC18:33
*** nelsnels_ has quit IRC18:35
*** nelsnelson has joined #openstack-meeting-318:35
*** Aish has quit IRC18:37
*** bharathm has quit IRC18:38
*** stanchan has joined #openstack-meeting-318:39
*** Aish has joined #openstack-meeting-318:41
*** badveli has joined #openstack-meeting-318:42
*** bharathm has joined #openstack-meeting-318:44
*** e0ne has joined #openstack-meeting-318:44
*** armax has quit IRC18:46
*** rhochmuth has quit IRC18:49
*** krtaylor has quit IRC18:53
*** vhoward has quit IRC18:55
*** vhoward has joined #openstack-meeting-318:56
*** jpomeroy has joined #openstack-meeting-318:56
*** abalutoiu has quit IRC19:04
*** cloudtrainme has quit IRC19:06
*** shwetaap has quit IRC19:06
*** piet has quit IRC19:06
*** bpokorny has quit IRC19:06
*** krtaylor has joined #openstack-meeting-319:07
*** neelashah has joined #openstack-meeting-319:08
*** mrmartin has joined #openstack-meeting-319:08
*** shwetaap has joined #openstack-meeting-319:09
*** galstrom_zzz is now known as galstrom19:10
*** neelashah1 has joined #openstack-meeting-319:13
*** galstrom is now known as galstrom_zzz19:14
*** neelashah has quit IRC19:14
*** cloudtrainme has joined #openstack-meeting-319:16
*** bharathm has quit IRC19:18
*** mickeys has left #openstack-meeting-319:18
*** bharathm has joined #openstack-meeting-319:20
*** piet has joined #openstack-meeting-319:22
*** piet has quit IRC19:23
*** piet has joined #openstack-meeting-319:24
*** lpetrut has quit IRC19:25
*** dedery_ has joined #openstack-meeting-319:28
*** kzaitsev_mb has joined #openstack-meeting-319:29
*** bharathm has quit IRC19:31
*** dedery has quit IRC19:31
*** dedery_ has quit IRC19:32
*** bharathm has joined #openstack-meeting-319:37
*** mrmartin has quit IRC19:41
*** kebray has quit IRC19:43
*** Sukhdev has joined #openstack-meeting-319:46
*** dslevin_ has quit IRC19:47
*** e0ne has quit IRC19:47
*** vgridnev has quit IRC19:48
*** dslevin_ has joined #openstack-meeting-319:52
*** Aish has quit IRC19:54
*** egallen has joined #openstack-meeting-319:55
*** bharathm has quit IRC19:55
*** robcresswell has joined #openstack-meeting-319:55
*** r1chardj0n3s has joined #openstack-meeting-319:57
*** baoli_ has quit IRC19:57
*** bharathm has joined #openstack-meeting-319:59
robcresswell#startmeeting horizondrivers20:00
openstackMeeting started Wed Jan  6 20:00:06 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizondrivers)"20:00
openstackThe meeting name has been set to 'horizondrivers'20:00
robcresswello/20:00
r1chardj0n3so/20:01
r1chardj0n3smy first one as a Driver20:01
*** mrmartin has joined #openstack-meeting-320:01
*** egallen has quit IRC20:01
robcresswellI'll give it a minute see if more people drift in20:01
mrungeo/20:02
*** lpetrut has joined #openstack-meeting-320:02
pieto/20:02
robcresswell#link https://wiki.openstack.org/wiki/Meetings/HorizonDrivers#Agenda_for_2015-01-06_2000_UTC Agenda for today20:03
robcresswellI won't repeat the notices from earlier (saves more time for blueprints)20:04
r1chardj0n3soic, there's homework for these meetings :-)20:04
robcresswellBut if you haven't checked the logs, here you go http://eavesdrop.openstack.org/meetings/horizon/2016/20:04
robcresswellThere's a few things, like the midcycle, that were spoken about.20:04
*** tsufiev has joined #openstack-meeting-320:04
robcresswellNow down to work!20:04
mrungerobcresswell, you forgot the note on checking tests20:05
tsufievo/20:05
mrungesince tests seem to be broken somehow, at least some failures are tolerated20:05
robcresswellSure20:05
mrungereviewers, please be careful and run tests yourself20:05
robcresswellI was going to just let people read the logs to save time :p20:05
robcresswellIn short, tests don't always fail due to errors, so its worth looking at test logs or running them yourselves even if Jenkins says they pass.20:06
mrungerobcresswell, we didn't had that in earlier meeting20:06
mrungeiirc20:06
r1chardj0n3swe did20:06
r1chardj0n3srobcresswell did bring it up20:06
robcresswellI think I mentioned it before you joined perhaps20:06
mrungeoh :-O20:06
mrungemaybe yes.20:06
mrungejust prved I did not read the logs20:07
robcresswellIs your minion around? itxaka?20:07
robcresswellseems not20:07
*** woodm19791 has joined #openstack-meeting-320:07
*** hurgleburgler1 has joined #openstack-meeting-320:07
robcresswell#topic Allow launching an instance with ports attached20:07
*** openstack changes topic to "Allow launching an instance with ports attached (Meeting topic: horizondrivers)"20:07
mrungehe should, but is not :(20:07
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/allow-launching-ports20:07
*** kzaitsev_mb has quit IRC20:08
robcresswellI rather like this change. Seems straightforward.20:08
r1chardj0n3sthat spec could use a link to supporting documentation :/20:09
mrungethere is this reature named SR-IOV20:09
mrungeand this is a prerequisite20:09
robcresswellAh20:09
mrungesome network guys really like this feature, but we don't support it yet20:09
*** badveli has quit IRC20:10
*** baoli has joined #openstack-meeting-320:10
r1chardj0n3swe ran into issues with the SR-IOV patch IIRC because we can't query for whether it's supported20:10
r1chardj0n3sbut that's a distraction from this bp20:10
robcresswellr1chardj0n3s: Agreed on needing more info20:10
robcresswellBut I think not worth blocking over. Approve, and leave comment asking for links to docs?20:11
r1chardj0n3ssounds good to me20:11
*** AlanClark has quit IRC20:11
tsufiev+120:11
mrungeI'm obviously biased here...20:11
*** stanchan has quit IRC20:11
mrungenot voting20:11
tsufievif it cannot be done, we could just change it to Needs Infrastructure, couldn´t we?20:11
mrungebut yes, +1 for requesting more docs20:11
*** bharathm has quit IRC20:12
r1chardj0n3s+120:12
*** ducttape_ has joined #openstack-meeting-320:12
*** woodster_ has joined #openstack-meeting-320:12
r1chardj0n3sjust to be clear20:12
*** krtaylor has quit IRC20:13
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/allow-launching-ports Approved (but needs a little extra detail on blueprint)20:13
robcresswell#topic Allow add/delete networks ports as a tenant20:13
*** openstack changes topic to "Allow add/delete networks ports as a tenant (Meeting topic: horizondrivers)"20:13
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/network-ports-tenant20:14
tsufievI was intially against the idea because I saw no real value - but perhaps I was wrong20:14
ducttape_robcresswell - so default neutron policy file allows this then ?20:14
*** cloudtrainme has quit IRC20:15
tsufievducttape_, https://github.com/openstack/horizon/blob/master/openstack_dashboard/conf/neutron_policy.json#L4320:15
mrungewhy don't we allow this, if policy allows this?20:16
tsufievseems that ´create_port´ is allowed20:16
robcresswellWait, am I supposed to have memorised neutrons policy files?20:16
tsufievbut many other operations are not20:16
tsufievrobcresswell, ^^^20:16
ducttape_yeah, I think this was not done just because this is not a likely thing most _member_ users would utilize20:16
tsufievI´d like to hear feedback from neutron-oriented people20:17
*** dedery has joined #openstack-meeting-320:17
robcresswellIf default policy allows it, it seems we should follow that. At least, there is no reason to block it if the change is written for us to use.20:17
*** bharathm has joined #openstack-meeting-320:17
*** egallen has joined #openstack-meeting-320:17
ducttape_what is the use case for creating a port without the other side (like a vm) ?20:17
*** egallen has quit IRC20:17
* mrunge got the impression, this is another part required for SR-IOV20:17
tsufieviirc, itxaka initial proposal was to enable port creation for regular users - to later use during vm launch20:18
robcresswellIdeally I'd ask the blueprint owner, but they aren't here.20:18
tsufievinstead I suggested to specify a port right during vm launc20:18
tsufievto provide better UX20:18
tsufiev(since the primary use case for port creation is to use for vm)20:19
robcresswellI think, leave a comment asking for more info, and leave to next meeting?20:19
ducttape_deal20:19
tsufiev+120:19
mrungeyepp, +120:19
r1chardj0n3ssounds good +120:19
mrungeand even if it's denied by default policy, we don't even have the action for a normal user20:20
mrungeif it's being enabled in policy20:20
mrungewe should take policy into account. if it's allowed: fine.20:20
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/network-ports-tenant Left comment asking for more info, put to side for now20:20
*** hurgleburgler1 is now known as hurgleburgler20:20
robcresswell#topic Configurable Instance Boot Source list for launch instance20:21
*** openstack changes topic to "Configurable Instance Boot Source list for launch instance (Meeting topic: horizondrivers)"20:21
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/configurable-boot-sources20:21
*** pkarikh has quit IRC20:21
*** belmoreira has joined #openstack-meeting-320:22
mrungethis is a end user request: be able to restrict boot sources to a limited selection20:22
mrungelike preventing to boot from an image, or from volumes20:22
*** itxaka has joined #openstack-meeting-320:22
*** stanchan has joined #openstack-meeting-320:22
ducttape_or a set of images / volumes ?20:22
itxakao/20:22
itxakasorry Im a bit late :(20:22
robcresswellAh20:23
robcresswellNo problem20:23
mrungeitxaka, good to have you here20:23
robcresswellwe'll circle back to the previous BP if there is time at the end20:23
robcresswellCurrently on the third agenda item20:23
itxakaGood :)20:23
mrungethat's my question robcresswell ....20:23
mrungehttps://blueprints.launchpad.net/horizon/+spec/configurable-boot-sources  <- that is20:23
ducttape_so mrunge - would this be a list of images or volumes, like a subset ?20:23
itxakaThis would actually be the source for boot, it being images or volumes or snapshots20:24
tsufievducttape_, should we encourage hardcoding :/?20:24
mrungeducttape_, not in this implementation20:24
robcresswellI think its just the options, not as deep as specific choices20:24
ducttape_ah ok, thanks for clarification20:24
itxakayeah, only the source as a generic option rather than going deeper than that20:24
mrungewe shouldn't list image ids (or so) to prevent booting from them20:24
*** jmckind_ has joined #openstack-meeting-320:24
*** pkarikh has joined #openstack-meeting-320:25
mrungeand for images, there is the bootable flag20:25
ducttape_that bp sounds simple / reasonable20:25
mrungebut that is not useful to prevent booting from images in general20:25
robcresswellThis seems sensible. I'm unaware if there are any conflicting options already available.20:25
robcresswell+1 from me, anyway20:26
r1chardj0n3sI just had a look to see whether nova already had a facility for configuring boot types, and couldn't see anything20:26
r1chardj0n3sso +120:26
*** jmckind has quit IRC20:26
r1chardj0n3s(it seems a shame we're coding this into our side)20:27
robcresswellr1chardj0n3s: two steps ahead of me20:27
robcresswellYeah, I agree, but its a useful option20:27
tsufiev+120:27
ducttape_deployers should realize that this does not prevent the cli from working around this20:27
tsufievr1chardj0n3s, that´s not the first instance of doing things on our side :)20:27
robcresswellbtw I'd prefer something like INSTANCE_SOURCE_OPTIONS than openstack source boot, that sounds too vague20:27
robcresswellIf its specific to launching instances.20:28
r1chardj0n3stsufiev: yep, but I also know what some people default to configuring on Horizon side when the service has a setting we should be using20:28
*** e0ne has joined #openstack-meeting-320:28
r1chardj0n3ss/what/that20:28
mrungerobcresswell, sounds sensible20:28
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/configurable-boot-sources Approved20:29
*** e0ne has quit IRC20:29
robcresswell#topic Performance & convenience improvements to integration tests, part120:29
*** openstack changes topic to "Performance & convenience improvements to integration tests, part1 (Meeting topic: horizondrivers)"20:29
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/integration-tests-improvements-part120:29
tsufievr1chardj0n3s, that´s a shame. Shame for documentation team, of course :)20:29
tsufievso, it´s as simple as it is20:29
tsufievmake integration tests faster (will be more important as number of tests raises), make the internals saner20:30
hurgleburglerthat'd be nice :)20:30
*** e0ne has joined #openstack-meeting-320:30
tsufievI chose ´part1´ suffix because there possibly will be other parts to20:30
tsufiev*to it20:30
robcresswellsomething something premature optimisation :p20:31
r1chardj0n3s^^ ;-)20:31
mrungetsufiev, any chance to stretch that over several releases?20:31
tsufievI think current list of patches https://review.openstack.org/#/q/topic:bp/integration-tests-improvements-part1 is now final, there won´t be more for part120:31
mrungeit might be the case we're not done with mitaka release20:31
robcresswellI don't disagree with the effort, but in the opening paragraph you mention that most of the time is spent on devstack, not the tests20:31
robcresswellBut hey, good patterns are useful.20:32
robcresswellI just wouldn't recommend chasing performance too much over more tests :)20:32
tsufievrobcresswell, the reason I did it so early is because refactoring becomes more expensive at time passes20:32
robcresswelltsufiev: Yep, understood20:32
tsufievespecially with horizon plugins building integration tests on it20:33
mrungeany chance to make integrations tests being run in parallel?20:33
*** e0ne has quit IRC20:33
*** vgridnev has joined #openstack-meeting-320:33
tsufievmrunge, haven´t investigated yet it on my own20:33
*** mrmartin has quit IRC20:33
robcresswellI'm fine with the blueprint itself.20:33
tsufievbut that I would call premature optimization :)20:34
mrungenot sure if that's really feasible20:34
tsufievmrunge, I´m afraid it could them less reliable20:34
mrungeyes, +1 from my side20:34
tsufievcould do*20:34
robcresswellr1chardj0n3s, itxaka, hurgleburgler ?20:34
r1chardj0n3s+120:34
itxaka+1 from me, any test improvements are always welcome20:34
mrungetsufiev, yes. I thought about relying on earlier states during test execution.20:35
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/integration-tests-improvements-part1 Approved20:35
robcresswell#topic Enhance the use of tox20:35
*** openstack changes topic to "Enhance the use of tox (Meeting topic: horizondrivers)"20:35
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/enhance-tox20:35
itxakayay20:35
itxakabasically, lets use tox as its supposed to be used20:35
itxakaand try to deprecate run_tests.sh20:35
itxakalike any other openstack project :D20:36
tsufiev\o/20:36
*** kzaitsev_mb has joined #openstack-meeting-320:36
hurgleburgler+120:36
mrungeiirc, horizon is the only (larger) openstack project, which uses something else other than tox20:36
robcresswellYup20:36
tsufievsounds very nice, I wonder what was the reason to use it in the first time20:36
mrungeI mean, we have our own script20:36
robcresswellI even recommend the plugins to use it20:36
ducttape_so we would eliminate run_tests.sh altogether, or just it's support for running tests / pep8 / etc ?20:37
itxakarobcresswell, you recomend tox or run_tests?20:37
robcresswellitxaka: tox20:37
mrungeducttape_, at the end, we should be removing run_tests20:37
itxakaducttape_, for the moment it replaces run_tests20:37
itxakabut I didnt remove run_tests20:37
robcresswellThere's more external work involved in removing run tests20:37
robcresswelltranslations depends on it, for a start20:37
itxakaas it requires updating docs, maybe some infra changes?20:38
itxakarobcresswell, yep, thats my point20:38
mrungesure20:38
mrungebut we could add a warning20:38
itxakaunfortunately I still dont have enough visibility on what could be affected :S20:38
mrungejust to see, where the warning will show up20:38
ducttape_how do you run a django dev server with tox?  /me looks into our tox options20:38
mrungelike: run_tests is being deprecated20:38
tsufievducttape_, btw, why do we need tox or run_tests to run dev server?20:39
mrungeducttape_, line 169 in the review20:39
itxakatox -e runserver20:39
itxaka:D20:39
robcresswellOr just whatever the actual command is... manage.py runserver?20:39
tsufievducttape_, is ´tools/with_venv.sh ./manage.py runserver´ not enough?20:39
tsufievyep)20:39
itxakayeah but you need a .venv for runniing that directly20:39
itxakawhy not use tox as it sets everything for you :D20:40
ducttape_yeah thats all fine / good.  thanks for the points.  (I'm stuck in my ways)20:40
robcresswellI'm always in a venv :D20:40
* mrunge is running the server without venv20:40
*** armax has joined #openstack-meeting-320:40
tsufievitxaka, because with tox you cannot alter dependenices easily20:40
mrungeI mean devserver20:40
tsufievfor example, django_openstack_auth20:40
robcresswelltsufiev: ?20:40
itxakaoh, but you can, exactly like with venv tsufiev20:41
tsufievrobcresswell, ah, nevermind, on a second thought tox and install_venv are equally bad )20:41
mrungetsufiev, do you mean, you want to use a git checkout of doa and another one of horizon?20:41
woodm19791It would be trivially easy and somewhat nice to add a tiny "run_sev_server.sh" script.  I think people would likely appreciate that.  Even it it's effectively an alias to ./manage.py runserver20:41
woodm19791run_dev_server.sh *20:42
tsufievmrunge, sorry, I was mixed my own experience with install_venv specifics. I personally run both in pycharm and need to uninstall DOA each time I add it to PyCharm env20:42
tsufievso tox doesn´t make it any worse20:43
mrungetsufiev, ah, got you.20:43
*** krtaylor has joined #openstack-meeting-320:43
robcresswellSo, vote time.20:43
robcresswell+120:43
ducttape_tox is fine / wfm20:43
tsufiev+120:43
mrunge+120:43
hurgleburgler+120:43
r1chardj0n3s+120:43
mrungebtw, it's only a single patch to play with: https://review.openstack.org/#/c/259013/20:44
tsufievand don´t forget to read all the logs ;)20:44
mrungewhile playing with tox, you'll immediately see the logs20:45
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/enhance-tox Approved20:45
mrungerobcresswell, time to get back to https://blueprints.launchpad.net/horizon/+spec/network-ports-tenant ?20:45
robcresswellLets loop back round to itxaka other patch20:45
robcresswellyes20:45
tsufievmrunge, unless you go away to fetch some coffee while it´s warming up :)20:45
robcresswellgive me a moment :p20:45
ducttape_./run_test.sh   ->  echo "you really want to use tox -e foo"   ;)20:45
robcresswell#topic Back to "Allow add/delete networks ports as a tenant"20:46
*** openstack changes topic to "Back to "Allow add/delete networks ports as a tenant" (Meeting topic: horizondrivers)"20:46
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/network-ports-tenant20:46
mrungetsufiev, lol20:46
*** rocky has joined #openstack-meeting-320:46
itxakayay o/20:46
robcresswellitxaka: So, policy allows this. The question earlier was what's the use case20:46
*** vtech has quit IRC20:47
itxakathe reasoning for that is we are virtually not allowing users to create their own ports while they can do it trougth the cli20:47
robcresswelland what effort is this building toward; mrunge mentioned sriov20:47
itxakaplus it links with https://blueprints.launchpad.net/horizon/+spec/allow-launching-ports20:47
*** matrohon has joined #openstack-meeting-320:47
ducttape_why is this more useful than just having the port automatically created ?20:47
itxakayeah basically if as an user I want to launch an instance with a port attached, I need an admin to add ports to a network that I created20:47
ducttape_or to use the cli, yes20:48
itxakawhy not allow users to set up their own ports as with the cli20:48
itxakaso they can add ports and then launch an instance attached to those ports20:48
itxaka:)20:48
*** rocky_g has joined #openstack-meeting-320:48
ducttape_I'm just not sure what the use case where a user cares about the port is20:48
*** baoli has quit IRC20:48
robcresswellI don't see much of an issue with Horizon adding the option and letting it be controlled by policy20:48
ducttape_would it be something related to getting the same ip reused?20:49
itxakaducttape_, no idea about that tbh20:49
*** rocky has left #openstack-meeting-320:50
itxakabut I know that adding the port options to be created by the user is not a really big change (99% of the code is the admin one)20:50
itxakabut it allows for advanced configuration to be used afterwards on instance launch20:50
ducttape_It's ok, I don't object to this.... but it's like adding lower level network buttons and actions just because we can.   Not sure if this is more useful or confusing20:51
itxakaand by advanced configuration, I mean selecting ports which could be using SR-IOV for example20:51
ducttape_the few people that will create ports ahead of time, are probably not spending much time in horizon ;)20:51
itxakanot sure if its just because we can20:51
*** woodm19791 has quit IRC20:51
itxakashouldnt we respect that if a user expects to do x in the cli he can do the same trougth GUI?20:51
itxakahopefully, more easily than trougth cli?20:52
robcresswellI think in this case it's not really Horizons job to decide that though. The action can be blocked just as easily with a rule change.20:52
ducttape_perhaps, but there is a usability concern in not confusing or overwhelming the users too20:52
tsufievducttape_, +120:52
mrungebut you could change the policy20:52
mrungeand policy should block that one then20:53
robcresswellTrue, but I don;t think one table action is really overwhelming users, and if the company has a concern, they can just block it with policy20:53
robcresswellI mean, its not like we just sat them down in front of transfer tables for the first time20:53
ducttape_but I might have lots of cli low level options I want technically possible, but I don't want 100% of them in the UI20:53
* robcresswell ducks20:53
robcresswellAnyone else for/against?20:54
r1chardj0n3sit seems like there's a need, even though there's potential UI complexity issues, so I'm happy to +120:54
ducttape_I'm not against btw.  Not really for either.  Is "meh" an option ?20:54
mrungeitxaka, is that required for any of the other blueprints?20:54
r1chardj0n3sducttape_: +0 I believe :-)20:55
* tsufiev abstains20:55
itxakaI do thinks ports are an important part of openstack, after reading more and more about them :)20:55
r1chardj0n3sor -020:55
mrungeif that's a blocker....20:55
robcresswellha20:55
robcresswellI think approve it20:55
ducttape_itxaka - would delete port be an option then too ?20:55
itxakayeah, same options that are on the admin side I believe20:55
ducttape_that becomes a problem then20:55
itxakajust transferred to run under tenant if the policy allows it20:55
*** vishwanathj has joined #openstack-meeting-320:56
tsufievducttape_, according to policy delete_port is for admin or owner20:56
itxakawhy is that a problem ducttape_20:56
*** Aish has joined #openstack-meeting-320:56
ducttape_if you allow delete ports, it is not easy to re-create the same port - and your instance then becomes 100% dead20:56
tsufievhm...20:56
ducttape_this is why it is in the cli, but not in the UI20:56
ducttape_if you are deleting ports, you better know what you are doing20:56
robcresswellPerhaps Add/ Del should be different proposals, itxaka20:56
tsufievducttape_, is it possible to delete a port used by running VM?20:57
mrungeso: create for the user, but delete for admin? that's fine20:57
itxakabut user created port == owner20:57
robcresswellThis is making me think a lot about where Horizon should intervene with default policy...20:57
itxakatif the policy allows for it...?20:57
ducttape_tsufiev - yes, you can delete a port for a running vm.  at that point, the vm has 0 networking20:57
tsufievducttape_, I think we should restrict that in Horizon20:58
mrungeyepp, agree tsufiev20:58
robcresswellWe're almost at time.20:58
robcresswellI think for now the bp needs to be split to at least add/delete as separate proposals20:58
robcresswellAnd then we can revisit it20:58
itxakanice, will do20:58
*** david-lyle_ has joined #openstack-meeting-320:59
robcresswellWe may get more opinions in a couple weeks too. It that okay?20:59
*** david-lyle_ has quit IRC20:59
robcresswells/It/Is20:59
itxakathanks for all the comments, Im not that good with the networking stuff :)20:59
itxakaso its always nice to get good info20:59
robcresswell#info https://blueprints.launchpad.net/horizon/+spec/network-ports-tenant Needs to be split, so that add/delete are separate proposals, and then we will revisit20:59
robcresswellTime! Thanks all21:00
itxakao/21:00
robcresswell#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Wed Jan  6 21:00:20 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-01-06-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-01-06-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizondrivers/2016/horizondrivers.2016-01-06-20.00.log.html21:00
*** baoli has joined #openstack-meeting-321:00
*** ducttape_ has left #openstack-meeting-321:00
*** hurgleburgler has left #openstack-meeting-321:00
*** kzaitsev_mb has quit IRC21:00
*** r1chardj0n3s has left #openstack-meeting-321:00
*** tsufiev has left #openstack-meeting-321:01
*** robcresswell has left #openstack-meeting-321:02
*** stanchan has quit IRC21:03
*** iyamahat has quit IRC21:04
*** Sukhdev has quit IRC21:05
*** bharathm has quit IRC21:06
*** spzala has joined #openstack-meeting-321:08
*** stanchan has joined #openstack-meeting-321:09
*** stanchan has quit IRC21:10
*** stanchan has joined #openstack-meeting-321:10
*** baoli has quit IRC21:12
*** baoli has joined #openstack-meeting-321:13
*** kragniz is now known as {^-^}21:17
*** {^-^} is now known as Guest4635321:18
*** Guest46353 is now known as kragniz21:18
*** bharathm has joined #openstack-meeting-321:21
*** baoli has quit IRC21:24
*** baoli has joined #openstack-meeting-321:25
*** julim has quit IRC21:27
*** ozamiatin has quit IRC21:28
*** belmoreira has quit IRC21:29
*** Aish has quit IRC21:31
*** Aish has joined #openstack-meeting-321:32
*** breton has left #openstack-meeting-321:33
*** baoli has quit IRC21:36
*** baoli has joined #openstack-meeting-321:37
*** kebray has joined #openstack-meeting-321:38
*** bharathm has quit IRC21:40
*** shwetaap has quit IRC21:43
*** alexstav has joined #openstack-meeting-321:43
*** bharathm has joined #openstack-meeting-321:43
*** vhoward has quit IRC21:44
*** peristeri has quit IRC21:46
*** dtardivel has quit IRC21:47
*** itxaka has quit IRC21:48
*** baoli has quit IRC21:51
*** baoli has joined #openstack-meeting-321:53
*** armax has quit IRC21:53
*** matrohon has quit IRC21:53
*** kebray has quit IRC21:54
*** ozamiatin has joined #openstack-meeting-321:54
*** kebray has joined #openstack-meeting-321:55
*** baoli has quit IRC21:55
*** baoli has joined #openstack-meeting-321:55
*** vgridnev has quit IRC21:55
*** bharathm has quit IRC21:56
*** bharathm has joined #openstack-meeting-322:01
*** baoli has quit IRC22:01
*** baoli has joined #openstack-meeting-322:02
*** vishwana_ has joined #openstack-meeting-322:03
*** baoli has quit IRC22:04
*** DuncanT has quit IRC22:04
*** bradjones has quit IRC22:04
*** doffm has quit IRC22:04
*** dimtruck has quit IRC22:04
*** doffm has joined #openstack-meeting-322:04
*** bradjones has joined #openstack-meeting-322:04
*** bradjones has quit IRC22:04
*** bradjones has joined #openstack-meeting-322:04
*** baoli has joined #openstack-meeting-322:04
*** Swami has quit IRC22:04
*** Swami has joined #openstack-meeting-322:05
*** vishwanathj has quit IRC22:05
*** markvan has quit IRC22:05
*** sdague has quit IRC22:05
*** dougwig has quit IRC22:05
*** markvan has joined #openstack-meeting-322:05
*** bharathm has quit IRC22:06
*** absubram_ has joined #openstack-meeting-322:06
*** absubram has quit IRC22:08
*** absubram_ is now known as absubram22:08
*** rtheis has quit IRC22:08
*** lblanchard has quit IRC22:08
*** bharathm has joined #openstack-meeting-322:08
*** ozamiatin has quit IRC22:08
*** Aish has quit IRC22:09
*** lblanchard has joined #openstack-meeting-322:09
*** lblanchard has quit IRC22:09
*** salv-orl_ has joined #openstack-meeting-322:09
*** baoli has quit IRC22:10
*** sdague has joined #openstack-meeting-322:11
*** dimtruck has joined #openstack-meeting-322:11
*** piet has quit IRC22:11
*** salv-orlando has quit IRC22:12
*** dougwig has joined #openstack-meeting-322:17
*** DuncanT has joined #openstack-meeting-322:17
*** jmckind_ has quit IRC22:22
*** baoli has joined #openstack-meeting-322:22
*** dims has quit IRC22:22
*** cbouch has quit IRC22:24
*** dedery has quit IRC22:24
*** Sukhdev has joined #openstack-meeting-322:24
*** ozamiatin has joined #openstack-meeting-322:26
*** baoli has quit IRC22:28
*** neelashah1 has quit IRC22:29
*** jpomeroy has quit IRC22:29
*** jtomasek has quit IRC22:30
*** jpomeroy has joined #openstack-meeting-322:34
*** Aish has joined #openstack-meeting-322:35
*** cloudtrainme has joined #openstack-meeting-322:36
*** dedery has joined #openstack-meeting-322:38
*** ozamiatin has quit IRC22:40
*** alexstav has quit IRC22:42
*** alexstav has joined #openstack-meeting-322:43
*** kzaitsev_mb has joined #openstack-meeting-322:46
*** alexstav has quit IRC22:48
*** jmckind has joined #openstack-meeting-322:49
*** bpokorny has joined #openstack-meeting-322:49
*** krtaylor has quit IRC22:51
*** baoli has joined #openstack-meeting-322:52
*** dims has joined #openstack-meeting-322:53
*** bharathm has quit IRC22:54
*** bklei has joined #openstack-meeting-322:54
*** lpetrut has quit IRC22:55
*** baoli has quit IRC22:56
*** baoli has joined #openstack-meeting-322:57
*** beekhof has quit IRC22:59
*** banix has quit IRC23:01
*** Aish has quit IRC23:01
*** bharathm has joined #openstack-meeting-323:02
*** Aish has joined #openstack-meeting-323:02
*** j^2 has quit IRC23:04
*** dims has quit IRC23:04
*** j^2 has joined #openstack-meeting-323:06
*** bharathm has quit IRC23:07
*** bklei has quit IRC23:07
*** jmckind has quit IRC23:08
*** j^2 has quit IRC23:08
*** j^2 has joined #openstack-meeting-323:09
*** baoli has quit IRC23:09
*** dimtruck is now known as zz_dimtruck23:11
*** bharathm has joined #openstack-meeting-323:11
*** beekhof has joined #openstack-meeting-323:13
*** jpomeroy has quit IRC23:14
*** rocky_g has quit IRC23:14
*** beekhof has quit IRC23:18
*** kzaitsev_mb has quit IRC23:20
*** stanchan has quit IRC23:21
*** sigmavirus24 is now known as sigmavirus24_awa23:25
*** Aish has quit IRC23:25
*** woodster_ has quit IRC23:26
*** beekhof has joined #openstack-meeting-323:27
*** iyamahat has joined #openstack-meeting-323:28
*** dims_ has joined #openstack-meeting-323:29
*** stanchan has joined #openstack-meeting-323:33
*** beekhof has quit IRC23:33
*** beekhof has joined #openstack-meeting-323:34
*** dims_ has quit IRC23:34
*** Aish has joined #openstack-meeting-323:36
*** dims_ has joined #openstack-meeting-323:36
*** pballand has joined #openstack-meeting-323:38
*** baoli has joined #openstack-meeting-323:38
*** kebray has quit IRC23:41
*** baoli has quit IRC23:43
*** alexstav has joined #openstack-meeting-323:44
*** SridarK has quit IRC23:44
*** krtaylor has joined #openstack-meeting-323:45
*** kebray has joined #openstack-meeting-323:46
*** rbak has quit IRC23:48
*** baoli has joined #openstack-meeting-323:49
*** alexstav has quit IRC23:50
*** pballand has quit IRC23:55
*** stanchan has quit IRC23:56
*** spzala has quit IRC23:57
*** Sukhdev has quit IRC23:58
*** ajmiller has quit IRC23:59

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