Thursday, 2013-07-11

*** sballe has quit IRC00:03
*** esp has quit IRC00:06
*** grapex has quit IRC00:11
*** arborism has quit IRC00:12
*** sarob_ has joined #openstack-meeting-alt00:15
*** sarob has quit IRC00:18
*** IlyaE has quit IRC00:19
*** sarob_ has quit IRC00:19
*** joe5081 has quit IRC00:24
*** syncking has joined #openstack-meeting-alt00:27
*** bdpayne has quit IRC00:49
*** esp has joined #openstack-meeting-alt00:53
*** syncking has quit IRC01:05
*** saurabhs has quit IRC01:15
*** saurabhs has joined #openstack-meeting-alt01:18
*** cp16net is now known as cp16net|away01:38
*** cp16net|away is now known as cp16net01:40
*** qwerty_nor has quit IRC02:01
*** esp has quit IRC02:17
*** amytron has joined #openstack-meeting-alt02:20
*** saurabhs has quit IRC02:26
*** ZangMing1ie has joined #openstack-meeting-alt02:38
*** plomakin has joined #openstack-meeting-alt02:38
*** ZangMingJie has quit IRC02:43
*** plomakin_ has quit IRC02:43
*** amytron has quit IRC03:27
*** IlyaE has joined #openstack-meeting-alt03:50
*** IlyaE has quit IRC03:52
*** IlyaE has joined #openstack-meeting-alt04:08
*** SergeyLukjanov has joined #openstack-meeting-alt04:09
*** IlyaE has quit IRC04:10
*** markmcclain has joined #openstack-meeting-alt04:13
*** IlyaE has joined #openstack-meeting-alt04:35
*** esp has joined #openstack-meeting-alt05:01
*** bdpayne has joined #openstack-meeting-alt05:30
*** SergeyLukjanov has quit IRC05:40
*** esp has quit IRC05:47
*** markmcclain has quit IRC05:53
*** bdpayne has quit IRC06:16
*** IlyaE has quit IRC06:27
*** IlyaE has joined #openstack-meeting-alt06:52
*** SergeyLukjanov has joined #openstack-meeting-alt07:02
*** IlyaE has quit IRC07:12
*** ivoks_ is now known as ivoks09:09
*** ivoks has quit IRC09:10
*** ivoks has joined #openstack-meeting-alt09:10
*** chmouel has quit IRC09:24
*** chmouel has joined #openstack-meeting-alt09:25
*** chmouel has quit IRC09:27
*** chmouel has joined #openstack-meeting-alt09:29
*** chmouel has quit IRC09:33
*** chmouel has joined #openstack-meeting-alt09:34
*** chmouel has joined #openstack-meeting-alt09:36
*** leizhang has joined #openstack-meeting-alt09:49
*** leizhang has quit IRC10:16
*** demorris has quit IRC11:40
*** HenryG_ has joined #openstack-meeting-alt11:41
*** HenryG has quit IRC11:44
*** HenryG_ has quit IRC11:58
*** djohnstone has joined #openstack-meeting-alt12:20
*** mtreinish has joined #openstack-meeting-alt13:34
*** demorris has joined #openstack-meeting-alt13:52
*** cp16net is now known as cp16net|away14:17
*** Riddhi has joined #openstack-meeting-alt14:27
*** jcru has joined #openstack-meeting-alt14:37
*** demorris has quit IRC14:40
*** jrodom has joined #openstack-meeting-alt14:59
*** IlyaE has joined #openstack-meeting-alt15:01
*** dhellmann_ is now known as dhellmann15:01
*** sballe has joined #openstack-meeting-alt15:04
*** tanisdl has joined #openstack-meeting-alt15:07
*** megan_w has joined #openstack-meeting-alt15:12
*** Riddhi has quit IRC15:16
*** Riddhi has joined #openstack-meeting-alt15:17
*** cp16net|away is now known as cp16net15:24
*** bdpayne has joined #openstack-meeting-alt15:28
*** markmcclain has joined #openstack-meeting-alt15:30
*** demorris has joined #openstack-meeting-alt15:32
*** Riddhi has quit IRC15:33
*** Riddhi has joined #openstack-meeting-alt15:36
*** jculp has quit IRC15:39
*** jculp has joined #openstack-meeting-alt15:42
*** demorris has quit IRC15:48
*** demorris has joined #openstack-meeting-alt15:54
*** sballe has quit IRC15:56
*** SergeyLukjanov has quit IRC15:58
*** tanisdl has quit IRC16:09
*** HenryG has joined #openstack-meeting-alt16:23
*** SergeyLukjanov has joined #openstack-meeting-alt16:34
*** esp has joined #openstack-meeting-alt16:37
*** lastidiot has joined #openstack-meeting-alt16:45
*** dhellmann is now known as dhellmann_16:45
*** demorris has quit IRC16:52
*** Riddhi has quit IRC17:07
*** Riddhi has joined #openstack-meeting-alt17:11
*** nkonovalov_ has joined #openstack-meeting-alt17:12
*** Riddhi has quit IRC17:13
*** lastidiot has quit IRC17:22
*** lastidiot has joined #openstack-meeting-alt17:22
*** arborism has joined #openstack-meeting-alt17:22
*** arborism has left #openstack-meeting-alt17:23
*** sarob has joined #openstack-meeting-alt17:25
*** demorris has joined #openstack-meeting-alt17:29
*** sarob has quit IRC17:29
*** markwash has joined #openstack-meeting-alt17:32
*** HenryG has quit IRC17:32
*** HenryG has joined #openstack-meeting-alt17:34
*** sarob has joined #openstack-meeting-alt17:41
*** sarob has quit IRC17:41
*** sarob has joined #openstack-meeting-alt17:42
*** sarob has quit IRC17:43
*** sarob has joined #openstack-meeting-alt17:43
*** sarob has quit IRC17:48
*** IlyaE has quit IRC17:49
*** akuznetsov has joined #openstack-meeting-alt17:50
*** Sriram has joined #openstack-meeting-alt17:53
*** sarob has joined #openstack-meeting-alt17:55
SergeyLukjanovSavanna meeting will be here in 10 minutes17:56
*** dmitryme has joined #openstack-meeting-alt17:59
*** tanisdl has joined #openstack-meeting-alt17:59
*** Riddhi has joined #openstack-meeting-alt17:59
*** aignatov3 has joined #openstack-meeting-alt18:00
*** dhellmann_ is now known as dhellmann18:01
*** ruhe has joined #openstack-meeting-alt18:02
*** mattf has joined #openstack-meeting-alt18:03
*** jmaron has joined #openstack-meeting-alt18:04
SergeyLukjanovI think that we should start18:05
SergeyLukjanov#startmeeting savanna18:05
openstackMeeting started Thu Jul 11 18:05:37 2013 UTC.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.18:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:05
*** openstack changes topic to " (Meeting topic: savanna)"18:05
openstackThe meeting name has been set to 'savanna'18:05
SergeyLukjanovhi everyone!18:05
jmaronhi18:05
aignatov3Hi18:05
mattfehlo18:06
ruhehowdy18:06
SergeyLukjanov#topic Agenda18:06
SergeyLukjanov#info Savanna core updates18:06
SergeyLukjanov#info REST API validation updates18:06
SergeyLukjanov#info UI updates18:06
SergeyLukjanov#info Documentation updates18:06
SergeyLukjanov#info Releasing updates18:06
SergeyLukjanov#info Other updates18:06
*** openstack changes topic to "Agenda (Meeting topic: savanna)"18:06
SergeyLukjanov#info Action items from the last meeting18:06
SergeyLukjanov#info General discussion18:06
SergeyLukjanov#topic Savanna core updates18:06
*** openstack changes topic to "Savanna core updates (Meeting topic: savanna)"18:06
SergeyLukjanovit's my part :)18:06
SergeyLukjanov#info several bugs has been fixed18:07
SergeyLukjanov#info the new default port for Savanna - 8386 instead of 808018:07
*** sballe has joined #openstack-meeting-alt18:08
SergeyLukjanov#info cinder volumes support is now working with cluster scaling feature18:08
SergeyLukjanov#info btw cluster scaling has been implemented at both savanna core side and vanilla plugin side18:09
SergeyLukjanovI think that's all about core18:10
SergeyLukjanov#topic REST API validation updates18:10
*** openstack changes topic to "REST API validation updates (Meeting topic: savanna)"18:10
aignatov3ok, it's me18:10
SergeyLukjanovaignatov3, please18:10
aignatov3ok, all REST API requests is fully covered by jsonschema checks18:10
aignatov3also we have added a lot of checks which will prevent users to create templates and clusters by incorrect requests18:11
SergeyLukjanovyep, additionally we are working on unit tests to cover validation18:12
aignatov3like wrong topologies, dublicates in node processes, unexisted flavors and images18:12
aignatov3and more)18:12
SergeyLukjanov#info validation for REST API implemented: jsonschemas + checks18:12
aignatov3that's all from validation I think18:13
SergeyLukjanovaignatov3, is it all from your side?18:13
SergeyLukjanovoh, ok18:13
SergeyLukjanovthe next topic is...18:13
SergeyLukjanov#topic Documentation updates18:13
*** openstack changes topic to "Documentation updates (Meeting topic: savanna)"18:13
SergeyLukjanovruhe, please18:13
ruhethere was a lot of work on Savanna docs recently18:13
*** IlyaE has joined #openstack-meeting-alt18:14
ruhenow we have developer guide, user guide, installation instructions, lots of things18:14
ruheand new shiny design, copied from OS docs18:14
ruhe#link https://savanna.readthedocs.org/en/latest/18:14
SergeyLukjanov#link https://savanna.readthedocs.org/en/latest/18:14
SergeyLukjanov:)18:14
ruhei invite everyone interested to skim through the docs and provide feedback18:15
ruhethat's all from my side18:15
SergeyLukjanovok, thx18:15
SergeyLukjanov#topic Releasing updates18:15
*** openstack changes topic to "Releasing updates (Meeting topic: savanna)"18:15
SergeyLukjanovit's my update too18:15
SergeyLukjanovyesterday we released first release candidate of version 0.218:16
SergeyLukjanovcore code freezed for any changes except docs/tests/hot fixes18:16
SergeyLukjanov#link https://launchpad.net/savanna/+milestone/0.2-rc118:16
SergeyLukjanov#info 0.2-rc2 - Friday - July, 1218:16
SergeyLukjanov#info 0.2 - Monday - July, 1518:16
SergeyLukjanovthat's all from my side18:17
SergeyLukjanov#topic Other updates18:17
*** openstack changes topic to "Other updates (Meeting topic: savanna)"18:17
SergeyLukjanovare there any other updates?18:17
mattfi think we're close to merging the hadoop and hadoop_fedora dib elements18:18
ruhecool18:18
aignatov3that's good18:18
SergeyLukjanovmattf, it's great18:18
akuznetsovblueprints for EDP components are added on launchpad18:19
mattfa few more CSs and it should get some serious attention from someone else in the community. i'm testing, but i'm only one person.18:19
akuznetsov#link https://blueprints.launchpad.net/savanna/+spec/job-manager-components18:19
akuznetsov#link https://blueprints.launchpad.net/savanna/+spec/data-discovery-component18:19
akuznetsov#link https://blueprints.launchpad.net/savanna/+spec/job-source-component18:19
akuznetsov#link https://blueprints.launchpad.net/savanna/+spec/methods-for-plugin-api-to-support-edp18:19
ruhemattf, i think Ivan will be happy to test that too18:19
mattfruhe, great18:20
jmaronback from vacation.  trying to address all review comments for HDP plubin by 7/1518:20
jmaronplugin18:20
SergeyLukjanovbtw we have two new contributors - Trevor McKay and Chad Roberts18:20
aignatov3yeah, today have started to test yourchnges, mattf18:20
aignatov3* Ivan has started)18:20
akuznetsovyour comments and suggestions on this blueprints are welcome18:20
SergeyLukjanovmattf, we'll merge your patches after 0.2 release18:21
SergeyLukjanovIvan will test them too18:21
mattfthat's prudent18:21
jmaronis hdp plugin planned as part of 0.2.1 release?  date?18:22
aignatov3jmaron, that's great!18:22
ruheakuznetsov, will you send out an email to the group to start the conversation?18:22
akuznetsovruhe, yes18:23
mattfanother update, we're now primarily using openstack-dev w/ a cc to savanna-all as archive for communication18:23
*** Riddhi has quit IRC18:23
SergeyLukjanovjmaron, yep, I hope that we'll merge HDP plugin in 0.2.1 version18:24
jmaronk18:24
jmaronwhat is the target date for 0.2.1?18:24
SergeyLukjanovit's planned approximately to July, 2918:25
ruheabout 2 weeks after release of 0.218:25
SergeyLukjanovruhe, right18:25
*** Riddhi has joined #openstack-meeting-alt18:25
SergeyLukjanovare there any other updates?18:26
SergeyLukjanov#link https://launchpad.net/savanna/+milestone/0.2.118:26
SergeyLukjanovok, if there are no other updates18:28
SergeyLukjanovlet's move on18:28
SergeyLukjanov#topic Action items from the last meeting18:28
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)"18:28
SergeyLukjanovwe have only one action iten18:28
SergeyLukjanovitem*18:29
SergeyLukjanovruhe to add work items to the white board with assignments for docs bp18:29
ruhedone18:29
ruhe#link https://blueprints.launchpad.net/savanna/+spec/docs-for-v0218:29
SergeyLukjanovyep, thank you18:29
SergeyLukjanov#topic General discussion18:29
*** openstack changes topic to "General discussion (Meeting topic: savanna)"18:29
SergeyLukjanovwe are waiting for feedback around EDP concept and new blueprints18:30
SergeyLukjanov:)18:30
jmarongeneral dev question:  we have some unit tests.  is there a mechanism for integrating those into the savanna build/tox?18:32
SergeyLukjanovyou should just place them to savanna/tests/unit18:32
ruhe#link https://savanna.readthedocs.org/en/latest/devref/development.guidelines.html#testing-guidelines18:32
SergeyLukjanovyou should use unittest2 for base test class18:33
jmaronk.  thx18:35
SergeyLukjanovare there any questions or suggestions?18:36
mattfthanks folks!18:39
SergeyLukjanovmm, I think if there are no other questions, let's finish it18:39
SergeyLukjanov#info JFYI you can always use savanna-all@lists.launchpad.net mailing lists and #savanna irc channel to find us and ask your questions18:39
SergeyLukjanov#endmeeting18:39
*** openstack changes topic to "OpenStack meetings (alternate)"18:39
openstackMeeting ended Thu Jul 11 18:39:33 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-07-11-18.05.html18:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-07-11-18.05.txt18:39
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-07-11-18.05.log.html18:39
*** mattf has left #openstack-meeting-alt18:39
*** rnirmal has joined #openstack-meeting-alt18:46
*** akuznetsov has quit IRC18:49
*** ruhe has quit IRC18:49
*** akuznetsov has joined #openstack-meeting-alt18:52
*** dkehn has joined #openstack-meeting-alt18:56
*** kgriffs has joined #openstack-meeting-alt18:58
*** cppcabrera has joined #openstack-meeting-alt18:58
*** amitgandhi has joined #openstack-meeting-alt18:59
*** malini has joined #openstack-meeting-alt18:59
*** flaper87 has joined #openstack-meeting-alt18:59
*** zyuan has joined #openstack-meeting-alt18:59
*** ametts_ has joined #openstack-meeting-alt18:59
*** bryansd has joined #openstack-meeting-alt19:00
*** rnirmal has quit IRC19:00
*** oz_akan_ has joined #openstack-meeting-alt19:00
*** rnirmal has joined #openstack-meeting-alt19:01
kgriffshi folks19:01
kgriffso/19:01
*** Riddhi_ has joined #openstack-meeting-alt19:01
oz_akan_hey19:02
*** vipul is now known as vipul-away19:02
*** vipul-away is now known as vipul19:02
Sriramhi19:02
malinihello19:02
flaper87hey19:02
* cppcabrera waves19:02
kgriffsok, just a sec and we'll get started19:02
amitgandhihi19:02
flaper87wow, so many new nicknames!19:03
flaper87nice to meet y'all19:03
kgriffs#startmeeting marconi19:03
openstackMeeting started Thu Jul 11 19:03:33 2013 UTC.  The chair is kgriffs. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: marconi)"19:03
openstackThe meeting name has been set to 'marconi'19:03
flaper87\o/19:03
kgriffs#topic review actions from last time19:03
*** openstack changes topic to "review actions from last time (Meeting topic: marconi)"19:03
kgriffs#link http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-27-19.05.html19:03
oz_akan_#idea I liked ideas19:04
*** Riddhi has quit IRC19:04
*** Riddhi_ is now known as Riddhi19:04
kgriffsok, megan_w in da house?19:04
oz_akan_(I need to learn more about irc commands)19:04
megan_wyep19:04
*** jodom has joined #openstack-meeting-alt19:04
*** dmitryme has left #openstack-meeting-alt19:04
kgriffsso, the incubation application got on the wiki, correct?19:04
megan_wyes19:04
* flaper87 read it19:04
kgriffsawesome, thanks19:05
flaper87it looks very good19:05
flaper87megan_w: +119:05
megan_whttps://wiki.openstack.org/wiki/Marconi/Incubation19:05
kgriffsany feedback on it real quick?19:05
ametts_flaper87:  I got you more contributors. :)19:05
maliniif we merge common client lib, Alessio might be a contributor too ;)19:05
flaper87megan_w: I would put "Kombu integration" instead of "Celery Integration"19:06
flaper87ametts_: +1 for you19:06
flaper87:D19:06
megan_wok, i can update19:06
kgriffsgroovy19:06
kgriffsmoving on19:06
SriramThe docs looks great19:06
Sriram*doc19:07
megan_ware more contributors the only thing we need before submittign this?19:07
kgriffsI see that ametts submitted a patch19:07
kgriffsso that takes care of hi action item19:07
kgriffseveryone PLEASE go review that patch19:07
zyuanwhich?19:08
ametts_Yes, please.  I want zyuan to pick it up from here, so it would be good to get my part merged.19:08
flaper87megan_w: I'd say yes19:08
kgriffsI'm a little biased since I helped design some of it (ametts did the heavy lifting, tho) and I would like to get more opinions19:08
*** jodom has quit IRC19:08
cppcabreraLink: https://review.openstack.org/#/c/36572/ (ametts' patch)19:08
flaper87cppcabrera: #link *19:08
*** jrodom has quit IRC19:08
cppcabreraAhh.19:08
cppcabrera#link https://review.openstack.org/#/c/36572/19:08
zyuanoh, the one i'm looking at....19:08
kgriffsright19:09
kgriffsmoving on19:09
flaper87I got some comments on that, we can talk about those afterward19:09
kgriffsitem #319:09
flaper87o/19:09
flaper87ah, you said item #319:10
kgriffsyo19:10
flaper87mine is #219:10
flaper87:D19:10
kgriffsso, I started a wiki page: https://blueprints.launchpad.net/marconi/+spec/ops-stats19:10
flaper87#link https://blueprints.launchpad.net/marconi/+spec/ops-stats19:10
kgriffsthis is low priority, but still really nice to have for ops (and for tuning), so I kept it in Havana19:11
flaper87how are we planing to do that? Middleware ?19:11
kgriffspossibly. That's how swift does it.19:11
flaper87I guess that makes more sense19:11
flaper87oke-doke19:11
amitgandhi+1 i like stats19:12
kgriffsnext up we had some actions for flaper87 to investigate ceilometer19:12
flaper87o/19:12
flaper87yup19:12
flaper87so, I did. The short answer is no, it's not possible to use it right now.19:12
flaper87the long answer is:19:13
flaper87The easiest way to use ceilo right now is to send notifications to some backend (rabbit) and let ceilo pull them from there19:13
kgriffsoic19:13
kgriffsgood to know19:13
flaper87they recently implemented an UDP listener that we could use as well19:13
flaper87not sure how mature it is right now and whether we want to rely on that.19:13
kgriffsok, we can keep an eye on it and revisit when it comes time to implement that bp19:14
flaper87re statsd: No, they don't support it yet. They've talked about it and it'll be supported sometime in the future19:14
flaper87but it hasn't be scheduled yet19:14
kgriffsok19:14
kgriffsthanks! good info.19:15
cppcabrera#info Ceilometer is not appropriate for Marconi stats at this time.19:15
kgriffs#info statsd not supported yet by Ceilometer but is on roadmap19:15
kgriffs#info recommended way to send data to Ceilometer is via a broker19:15
kgriffsmoving on19:15
kgriffs#topic QA cluster remaining TODOs19:16
*** openstack changes topic to "QA cluster remaining TODOs (Meeting topic: marconi)"19:16
kgriffsoz_akan_, malini: ^^19:16
oz_akan_hey19:16
maliniOz & me are running the load tests19:16
*** vipul is now known as vipul-away19:17
flaper87malini: oz_akan_ any numbers? How's Marconi behaving ?19:17
malinioz_akan_ : want to share the story ?19:17
* flaper87 is a bit scared now19:17
oz_akan_ok19:17
* ametts_ snickers19:18
maliniflaper87: dont worry, we are slow and steady19:18
oz_akan_if we have a write concern with 1 and if we read from secondary nodes we get better results19:18
oz_akan_otherwise, a post_claim takes 7 seconds under light load19:19
oz_akan_with all changes we did, it is a little over 1 second now19:19
malinias in 1 user/sec (a user doing ~5 api calls)19:19
oz_akan_main problem is database locks19:19
oz_akan_I think we will have to create lots of databases on each instance19:19
*** esmute_ has joined #openstack-meeting-alt19:19
flaper87wow, that doesn't sound good19:19
*** sarob_ has joined #openstack-meeting-alt19:20
*** lastidiot1 has joined #openstack-meeting-alt19:20
flaper87I mean, the 7 seconds thing19:20
flaper87mmhh, are the indexes being used correctly?19:20
oz_akan_placement service can handle this problem as well, or we can just hash a queue on a database on a mongodb instance19:20
flaper87did you guys enable the query profiler ?19:20
*** HenryG has quit IRC19:21
oz_akan_writes take good amount of time19:21
oz_akan_if I send only one request, it is in milliseconds range19:21
flaper87oz_akan_: The placement service will help but we should definitely improve that timing19:21
oz_akan_to improve the performance 1- we need to check if code if optimal,19:21
amitgandhiis anything whacky going on with the mongodb instances?19:22
oz_akan_I will enable profiler and create a report19:22
kgriffskk19:22
oz_akan_2- we need more databases per instance, as a write, locks all database19:22
kgriffscan you guys get together and dig into this?19:22
flaper87oz_akan_: +119:22
flaper87We should make sure the indexes are being used as expected19:22
oz_akan_flaper87: +119:23
kgriffs#action oz_akan_ and flaper87 to investigate mongo insert performance19:23
oz_akan_almost all call marconi has, has a write operation19:23
oz_akan_so we are very write heavy19:23
flaper87oz_akan_: good point19:23
oz_akan_and delete_queue is unresobavly slow19:23
oz_akan_unreasonably19:24
kgriffswell, the good news is we have a baseline now19:24
oz_akan_22 seconds, under light load19:24
zyuanmongo write is suppose to be fast, since it does not wait disk19:24
kgriffslet's get to work making it better.19:24
zyuan!!!19:24
openstackzyuan: Error: "!!" is not a valid command.19:24
flaper87zyuan: depends on your write concern19:24
flaper87if you expect the record to be journaled, it'll wait for disk19:24
oz_akan_right, and if you have so many of them, reads get slow19:25
zyuanflaper87: mongo has no journal19:25
flaper87zyuan: it does19:25
oz_akan_i see 600 requests in read queue19:25
* kgriffs rings cowbell19:25
zyuani see....19:25
flaper87zyuan: FYI http://docs.mongodb.org/manual/core/journaling/19:25
oz_akan_journal can be disabled, which we did for now to see what is the max we can get19:25
flaper87oz_akan_: ok, we can dig into this afterwards19:25
kgriffsmoving on19:25
oz_akan_flaper87: ok19:25
flaper87malini: oz_akan_ thanks for getting that env up and running19:26
flaper87many apple pies for you guys!19:26
kgriffs#topic •Rebooting python-marconiclient19:26
*** openstack changes topic to "•Rebooting python-marconiclient (Meeting topic: marconi)"19:26
maliniwoohoo19:26
oz_akan_malini: is awesome with her tests19:26
oz_akan_I just run them all day :)19:26
cppcabrera(and all night!)19:26
maliniThanks Oz..I'll give you the cheque19:26
kgriffsso, cppcabrera, wanna talk about the client?19:26
cppcabreraYeah. :)19:27
Sriramcppcabrera, you have the floor.19:27
cppcabreraAlright...19:27
cppcabreraSo there's been a lot going on with regards to the client lately.19:27
cppcabreraPrimarily, brainstorming and setting the foundation for developing it.19:27
cppcabreraAlessio helped bootstrap our installation process by submitting a few patches. We now use pbr.19:28
cppcabreraThe README is in the process of getting a big upgrade.19:28
cppcabreraA HACKING file is also being added, based on Marconi server's own HACKING.rst.19:28
zyuani guess we don't have much freedom on client's API design....19:28
zyuanall openstack clients use same set of .... dump apis19:29
cppcabreraSo what's next - finalizing the deisgn and developing.19:29
cppcabrera*design19:29
flaper87cppcabrera: re Alessio's patch! I don't think it is *ready* but I think we should get it merged and keep working on it19:29
flaper87but, I do want to make sure someone is going to work on that19:30
cppcabreraI don't see that patch on the review queue any more. Where did it go?19:30
flaper87I'm not happy with merging things that are not ready but I realize that's the only way to start working on marconi's client19:30
ametts_flaper87:  Is there a list of what needs to be done?19:30
zyuanhttps://review.openstack.org/#/c/29255/19:30
*** sarob has quit IRC19:30
*** lastidiot has quit IRC19:30
*** jmaron has quit IRC19:30
*** clarkb has quit IRC19:31
*** jesusaurus has quit IRC19:31
*** esmute has quit IRC19:31
flaper87#link https://review.openstack.org/#/c/29255/19:31
*** esmute_ is now known as esmute19:31
cppcabreraThanks.19:31
cppcabreraI'm in favor of merging that, especially since it bootstraps our common libraries effort.19:31
flaper87ametts_: There isn't, I've got some things in my mind, I will write those down19:31
cppcabreraAs far as cleanup, I'll be happy to champion that cause.19:32
*** akuznetsov has quit IRC19:32
zyuanthat patch is ready, it's not the marconi client; it's the commonly used library.19:32
*** aignatov3 has quit IRC19:32
flaper87pls, notice that that patch takes code from several clients and puts it in the same package19:32
flaper87so, there's a lot of cleanup to do there19:32
ametts_kgriffs: You missed your chance to give flaper87 one of your action-thingies ^^^19:32
SriramYes cleanup will be required.19:33
cppcabreraThree action points ^^ (flaper87 comments, merge patch, cleanup)19:33
zyuanoh my, i guess it's a common part.19:33
flaper87holymoly!19:33
kgriffs#action flaper87 to document client cleanup19:33
kgriffs#action flaper87 to merge patches19:33
cppcabreraAlso, finalize client design, distribute development effort.19:34
cppcabreraSo... 5 tasks. :)19:34
flaper87cppcabrera: waaaaaaaaaaaaaaaaaaaaaaaaaaat ?19:34
*** jesusaurus has joined #openstack-meeting-alt19:34
flaper87cppcabrera: dude, -1 Apple pie for ya!19:34
cppcabreraHahaha19:34
kgriffs#action flaper87, cppcabrera to finalize client design19:34
cppcabrera:P19:34
* kgriffs just works here19:34
flaper87LOL19:34
kgriffsok, anything else on that topic?19:34
flaper87not from me19:35
flaper87cppcabrera: shut up!19:35
flaper87:P19:35
zyuanone ques19:35
cppcabreraAlright... that wraps it up for me.19:35
zyuando we really need the apiclient patch?19:35
*** jdprax has joined #openstack-meeting-alt19:35
flaper87zyuan: yes and no, That's an effort we're doing to contribute back to Oslo's apiclient19:35
flaper87it makes sense to unify client's common code and it isn't that simple to migrate existing clients19:36
zyuani definitely like apiclient goes to oslo19:36
flaper87so, we proposed to use marconiclient as incubator for that package19:36
zyuanbut.... don't use marconi as a test field...19:36
flaper87zyuan: before going into Oslo, it needs to have a POC and being used at least in 1 project19:36
zyuanok19:37
flaper87marconiclient is brand new, it makes sense to use it as incubator for it19:37
cppcabrera+119:37
SriramI would also like to have a role in the client development, after finalizing design.19:37
flaper87Sriram: +119:37
ametts_flaper87:  agree  -- marconi is in the best position to be the incubator.19:37
zyuanthen how about do this:19:37
cppcabreraIt's a good place to start hammering in "One way to do it."19:37
zyuanmerge the patch19:37
zyuanwrite marconi client19:37
zyuanafter the client is done19:37
zyuandecide which part of the apiclient goes away19:38
zyuanlike , garbadge collection19:38
flaper87zyuan: that's our plan19:38
amitgandhi+1 cppcabrera and sriram tag team the client dev19:38
zyuanthen just merge the patch... we don't have much energy to design a lib without using it.19:39
flaper87plus, there'll be another cleanup when we'll try to propose it for Oslo19:39
flaper87zyuan: that's what we just said :P19:39
amitgandhilets just make sure we've documented the cleanup well so we dont forget19:39
flaper87cool!19:39
kgriffsok, anything else on that topic?19:40
flaper87not from me19:40
cppcabreraNone from me. I'm happy. :)19:40
Sriramthats it from me.19:40
zyuannext topic?19:40
*** clarkb has joined #openstack-meeting-alt19:40
malinibugs19:40
kgriffs#topic enforcing queue metadata reserved field convention19:41
*** openstack changes topic to "enforcing queue metadata reserved field convention (Meeting topic: marconi)"19:41
malini:(19:41
zyuan...19:41
* ametts_ thinks that's the worst topic name ever19:41
*** IlyaE has quit IRC19:41
flaper87lol19:41
kgriffsagreed, heh19:41
kgriffsso, flaper87 wanted to discuss this real quick19:42
flaper87right, I barely followed the discussion yesterday19:42
flaper87so, what's the plan here?19:43
kgriffsthe proposal is to actually allow clients to create custom field names that start with an underscore, even though those are reserved for future use by the server19:43
zyuanno, there is no, no, NO custom fields19:43
kgriffsum, by custom I mean arbitrary metadata fields. we allow that19:43
*** pycabrera has joined #openstack-meeting-alt19:44
*** Sriram1 has joined #openstack-meeting-alt19:44
amitgandhiwhat future use reserved fields do you envision?19:44
amitgandhiare we violating YAGNI19:45
kgriffsfor example, _default_message_ttl19:45
kgriffsor _message_delay19:45
*** pycabrera has quit IRC19:45
kgriffsthe idea is, we tell people not to use the naming convention of preceding underscore19:45
*** pycabrera has joined #openstack-meeting-alt19:45
zyuanthere are many usage, since it's a per-queue attribute.19:45
*** esp1 has joined #openstack-meeting-alt19:45
flaper87I don't think this is a YAGNI violation, we need to make sure we don't break backward compatibility in the future19:45
zyuanabsolutely, we don't break the reserved fields we already published.19:46
kgriffsif we ever end up wanting to use, say, _message_delay, then we need code or something to protect ourselves from blowing up on queues where a user actually used that field name in spite of us warning them not to19:46
kgriffsso, that's the proposal in a nutshell19:46
kgriffs1. don't enforce19:47
kgriffs2. mitigate name collisions19:47
flaper87I prefer enforcing it, I mean, forbid people to use our reserved convention19:48
amitgandhican we not enforce, but warn and discourage?19:48
maliniflaper87: +119:48
*** ekarlso has joined #openstack-meeting-alt19:48
zyuannot just warn, we told them not to do so19:48
Sriram1+1 for enforcing.19:48
zyuani can't think of a reason to pet them19:48
kgriffsI'll let zyuan argue for his proposal19:48
zyuantake the example i posted yesterday19:49
kgriffsactually, #2 was my contribution, seemed like it is a given if you do #119:49
zyuanopen our python, and see if you can define a method named __a__19:49
*** pycabrera has quit IRC19:49
*** nmakhotkin has joined #openstack-meeting-alt19:49
*** pycabrera has joined #openstack-meeting-alt19:49
malinibut python wouldn't clean up your function names, between version updates19:50
flaper87and this is not python, we're talking about people's data19:50
flaper87we can't just introduce a new keyword and just say: "We told you so"19:50
zyuanpython all programs everything by upgrading from 2 to 319:51
*** pycabrera is now known as cppcabrrera19:51
maliniyeap..the restriction is somewhere deep in our API docs & I am sure most of us wouldnt ever have noticed it19:51
zyuanif we don't want to break backward, we can cleanup19:51
kgriffszyuan: can you speak briefly about client backwards compat?19:52
*** Sriram has quit IRC19:52
*** esp has quit IRC19:52
*** ekarlso- has quit IRC19:52
*** cppcabrera has quit IRC19:52
*** SlickNik has quit IRC19:52
*** westmaas has quit IRC19:52
*** nmakhotkin1 has quit IRC19:52
kgriffsiirc, that was your main driver behind this proposal19:52
zyuanif we publish more _names between revisions19:53
zyuannew clients can immediately use new _names without waiting for servers to be upgraded19:53
*** westmaas has joined #openstack-meeting-alt19:53
*** SlickNik has joined #openstack-meeting-alt19:53
zyuanand the new _names should not change the sematics within 1 API version19:54
*** cppcabrrera is now known as cppcabrera19:54
flaper87mmh, not sure I follow :(19:54
zyuanif a _name does change the semantics, then we upgrade API version19:54
flaper87what do you mean by _name ?19:54
zyuanreserved queue metadata in use19:55
*** westmaas has joined #openstack-meeting-alt19:55
*** westmaas has quit IRC19:55
kgriffs(5 minutes)19:55
malinibugs…..19:56
zyuanlike, today we publish a per-queue attribute, say "_max_payload"19:56
flaper87mmh, I don't see the benefit19:56
zyuanit only affects performance, say19:56
flaper87kgriffs: should we vote?19:56
zyuanthen clients can send it even server does not optimize for it19:56
kgriffs1 minute, then we'll vote19:56
flaper87zyuan: we can enforce it in our client as well19:56
flaper87not just the server19:57
zyuanat least don't do it in server19:57
cppcabreraI vote to defer this discussion, and have zyuan write up his rationale in detail.19:57
cppcabreraFor next time.19:57
flaper87+119:57
kgriffsany opposed?19:57
*** sarob has joined #openstack-meeting-alt19:57
amitgandhibugs?19:58
kgriffs#action zyuan to write up metadata handling proposal and review next time19:58
kgriffs#action bug triage19:58
kgriffsoops19:58
zyuanthey are solved going to be solved19:58
flaper87LOL19:58
kgriffs#topic bug triage19:58
*** openstack changes topic to "bug triage (Meeting topic: marconi)"19:58
malinihttps://bugs.launchpad.net/marconi/+bug/1192196 —> Truncated JSON..I saw this happen on a claim messages as well. So need somebody to look at this one19:58
cppcabrera#link https://bugs.launchpad.net/marconi/+bug/119219619:58
flaper87malini: I tried to replicated it today but didn't get the test running. Can we sync up on that tomorrow ?19:59
malinisure19:59
zyuanthat one is for Havana-219:59
flaper87I honestly have no idea why that's happening but replicating it is a good start19:59
*** westmaas has joined #openstack-meeting-alt19:59
maliniWe have a few minor bugs as well in NEW status19:59
*** westmaas has joined #openstack-meeting-alt20:00
*** westmaas has quit IRC20:00
maliniat least one  of them is a  low hanging20:00
amitgandhiJson Truncation - ive seen it before (in a prior project).  limitations by whatever json parser being used and/or connection being closed before the entire stream has been read20:00
*** jrodom has joined #openstack-meeting-alt20:00
*** jrodom has quit IRC20:00
kgriffsflaper87: this is ready to merge - https://review.openstack.org/#/c/36319/20:00
*** westmaas has joined #openstack-meeting-alt20:01
*** jrodom has joined #openstack-meeting-alt20:01
kgriffsok folks, we are out of time20:01
flaper87kgriffs: cool, will take a look at it20:01
cppcabreraGood meeting.20:01
*** sarob__ has joined #openstack-meeting-alt20:01
ametts_Great meeting, folks.20:01
kgriffsreally quick20:01
flaper87w000t20:01
flaper87thanks everyone20:01
kgriffspriorities for this week are FIX BUGS20:01
kgriffsMAKE IT FASTER20:01
maliniYES!!!!!!20:01
flaper87YES!20:01
*** sarob has quit IRC20:01
*** zhiyan has joined #openstack-meeting-alt20:01
cppcabrera:)20:01
Sriram1Great meeting!20:01
*** sarob_ has quit IRC20:01
ametts_Fix bugs faster? :)20:02
*** Sriram1 is now known as Sriram20:02
flaper87ametts_: in parallel20:02
kgriffswe'll do more fine-grained prioritization next time20:02
*** malini has left #openstack-meeting-alt20:02
kgriffs#endmeeting20:02
*** openstack changes topic to "OpenStack meetings (alternate)"20:02
openstackMeeting ended Thu Jul 11 20:02:33 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-07-11-19.03.html20:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-07-11-19.03.txt20:02
*** amitgandhi has left #openstack-meeting-alt20:02
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-07-11-19.03.log.html20:02
*** cppcabrera has left #openstack-meeting-alt20:02
*** zyuan has left #openstack-meeting-alt20:02
markwasho/ glance folks20:03
flaper87\o/20:03
* markwash waits for flaper87 to switch hats20:03
zhiyano/20:03
markwashzhiyan: o/ hurray20:03
zhiyanmarkwash: hey \o20:03
* flaper87 puts his Glance hat on20:04
markwash#startmeeting20:04
openstackmarkwash: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'20:04
*** akuznetsov has joined #openstack-meeting-alt20:04
markwash#startmeeting glance20:04
openstackMeeting started Thu Jul 11 20:04:16 2013 UTC.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.20:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:04
*** openstack changes topic to " (Meeting topic: glance)"20:04
openstackThe meeting name has been set to 'glance'20:04
zhiyanhi folks~20:04
markwash#link https://launchpad.net/glance/+milestone/havana-220:04
*** westmaas has joined #openstack-meeting-alt20:04
flaper87yo yo20:04
*** ametts_ has left #openstack-meeting-alt20:04
zhiyanmarkwash: yes, i have 320:05
markwashall our blueprints are in "needs code review" which is good, we have about a week left to get them all moved through20:05
zhiyancool20:05
icchahey20:05
zhiyanhi iccha20:05
ameade_here now20:05
Guest10975o/20:05
flaper87markwash: well, I still need to submit another one20:05
markwashduring this meeting, if there are enough folks around, I'd like to cement our plans for getting those in20:05
*** Guest10975 is now known as nikhil20:05
markwashflaper87: true20:05
flaper87Gate isn't helping today20:06
*** westmaas has joined #openstack-meeting-alt20:06
flaper87This one is ready to be reviewed https://review.openstack.org/#/c/36218/20:06
markwash#topic registry database driver20:06
*** openstack changes topic to "registry database driver (Meeting topic: glance)"20:06
zhiyanflaper87: NOD,20:06
markwashflaper87: that review looks straightforward20:06
flaper87So, the registry database driver is almost ready. I still need to submit a new review, which should be the last one20:06
markwashand its passing the gate at this point20:07
*** SlickNik has left #openstack-meeting-alt20:07
markwash36218 seems unlikely to conflict with other changes20:07
*** westmaas has joined #openstack-meeting-alt20:07
flaper87markwash: yeah, that review changes the db_api for properties deletion, though20:07
markwashhow likely do you think the other patch is to have conflicts with the other bps that are currently in review?20:07
*** bryansd has left #openstack-meeting-alt20:08
flaper87markwash: the other patch shouldn't conflict at all20:08
flaper87it is an isolated package under glance/db/registry20:08
flaper87and it has its own tests20:08
markwashflaper87: when do you think your next patch should be ready?20:08
*** kgriffs is now known as kgriffs_afk20:09
*** vipul-away is now known as vipul20:09
flaper87so, unless I find something else that blocks that patch, I think It should be ready tomorrow / Monday20:09
markwashokay great, that should be plenty of time20:09
*** westmaas has joined #openstack-meeting-alt20:09
markwashanyone else have questions about registry db driver?20:09
flaper87and btw, sorry for the delay, I was away the last 2 weeks20:10
markwash#topic multiple locations20:11
*** openstack changes topic to "multiple locations (Meeting topic: glance)"20:11
markwashboth zhiyan and jbresnah have been very active on this one lately20:11
markwashzhiyan, is there just one review left for you? or two?20:11
zhiyanmarkwash: for multiple-locations BP, I have one20:11
zhiyanmarkwash: I have prepared a overall status for you/team, let me paste it here:20:12
zhiyanI have 4 patchs there for 4 BPs: multiple-image-locations (PATCH API part), multiple-locations-downloading, locations-policy and glance-cinder-driver20:12
zhiyanNeed review:20:12
zhiyan[1] https://review.openstack.org/#/c/35134/20:12
zhiyanReady for review (close to merge to me):20:12
zhiyan[2] https://blueprints.launchpad.net/glance/+spec/multiple-locations-downloading (no dependency)20:12
zhiyan[3] https://blueprints.launchpad.net/glance/+spec/locations-policy  (depends on above [1])20:12
zhiyan[4] https://blueprints.launchpad.net/glance/+spec/glance-cinder-driver (depends on above [3])20:12
*** westmaas has joined #openstack-meeting-alt20:13
zhiyanbtw, thanks folks help review my patchs.20:13
markwashzhiyan: I also was thinking https://review.openstack.org/#/c/35741/ was necessary, do you agree?20:13
zhiyanmarkwash: yesyes, it's #[3]20:14
markwashalso, with a simple-seeming rebase, that seems like a patch that could go through fast20:14
markwashzhiyan: okay, cool. . I think maybe multiple locations depends on locations-policy20:15
zhiyan[2] = https://review.openstack.org/#/c/35734/20:15
zhiyan[3] = https://review.openstack.org/#/c/35741/20:15
zhiyan[4] = https://review.openstack.org/#/c/32864/20:15
markwashI'll circle back to those when we talk about glance-cinder-driver, okay?20:15
zhiyanok20:15
*** westmaas has joined #openstack-meeting-alt20:16
*** westmaas has quit IRC20:16
markwashso just to regather all the reviews we think are necessary for multiple locations to be "Implemented"20:16
zhiyanso, for multiple-image-locations part, i think we just on https://review.openstack.org/#/c/35134/ reviewing20:16
markwashhttps://review.openstack.org/#/c/35134/20:16
markwashhttps://review.openstack.org/#/c/35741/20:16
markwashand jbresnahs which is. . .20:16
markwashhttps://review.openstack.org/#/c/34492/20:16
zhiyanhttps://review.openstack.org/#/c/34492/20:16
zhiyanyes20:16
*** westmaas has joined #openstack-meeting-alt20:17
markwashunfortunately jbresnah is out, so I'll have to check back with him20:17
*** westmaas has joined #openstack-meeting-alt20:17
markwashit looks like https://review.openstack.org/#/c/34492/ needs a rebase to resolve merge conflicts20:17
zhiyani have a question on https://review.openstack.org/#/c/35134/ , i saw jbresnah (maybe you also) have a concens on image status mangement/update logic20:17
markwashzhiyan: you had the last -1 on that branch, do you think its getting close to getting your +1?20:17
markwashzhiyan: you said those issues in your -1 were easy to fix, so I figure a rebase is pretty much all that is needed20:18
zhiyani have no -1 on #3449220:18
*** SergeyLukjanov has quit IRC20:19
markwashI see the -1 for PS 18 is gone20:19
zhiyanmarkwash: yes, since ps18 has 3 minor problems...20:19
markwash#action jbresnah rebase https://review.openstack.org/#/c/34492/ and we'll review and land it asap20:19
markwashso, the next one in this series is https://review.openstack.org/#/c/35134/20:20
zhiyanmarkwash: can we talk about #35134?20:20
markwashyup20:20
markwashthe state issues jbresnah pointed out20:20
markwashI think ultimately this is my fault20:20
markwashI didn't understand when writing the domain model the right place to put state management and certain other details20:20
zhiyanso, i personally think it is ok, and we need dedicated BP to cover image status management20:20
markwashcurrently, there is only one piece of state management in the controllers, and that is setting the image.status = 'saving' when you start to upload data20:21
markwashthis patch adds several more locations20:21
markwashzhiyan: I tend to agree that we should have a more comprehensive refactoring of the state management code location20:21
markwashso the blocker here is just to make sure we're doing the *right* state management20:21
markwashthe way I'm imaginging it, basically, if you add a location to an image that is 'queued', it becomes 'active'20:22
markwashand if you delete the last location from an image that is 'active', it becomes 'queued'20:22
markwashdoes that sound right?20:22
zhiyanmarkwash: yup. so, if you have concern current status changing logic in #35134, can we just give a limitation to it on current stage?20:22
flaper87markwash: +120:23
flaper87I guess it's a bit unclear what queued state means20:23
markwashflaper87: its is confusing20:23
markwash'queued' is the state we take on when the image record is created, but before data is uploaded20:23
markwashthere might also be a 'pending' state?20:23
zhiyanmarkwash: the current implement in PS12, i think it just like you said20:24
*** akuznetsov has quit IRC20:24
markwashzhiyan: okay cool, then all I think is needed is more review on my part there20:24
flaper87markwash: Ok, we're on the same page there but, if we put the image back to queued when the last location is deleted, queued will mean something else20:24
markwash#action markwash re-review state management logic in https://review.openstack.org/#/c/35134/20:24
*** Riddhi has quit IRC20:24
markwashflaper87: hmm20:24
zhiyanmarkwash: i meaning, if you think that logic is not much stable for status management, so i think we can give a limitation there, for example, just allow client call patch api on 'active' status image..20:25
flaper87I mean, it can be missleading. Users won't know whether the image was created and no data was uploaded20:25
flaper87or if the image's locations were deleted20:25
*** nkonovalov_ has quit IRC20:26
flaper87I don't think adding a new state will help but, what about renaming it ?20:26
markwash'inactive' ?20:26
flaper87(in a future patch and tracked by a separate blueprint)20:26
flaper87markwash: that makes more sense20:26
markwashflaper87: okay, I buy that. . essentially accept 'queued' for now, but move forward with a state management refactoring in the future?20:27
flaper87markwash: agreed!20:27
markwashare there any other items of state management that are confusing that might be worth mentioning in the initial bp?20:27
zhiyanwhat's the different on 'queued' .vs. 'inactive' ?20:27
markwashzhiyan: to answer your earlier question, I think we need to allow locations to be added to 'queued' images20:27
*** akuznetsov has joined #openstack-meeting-alt20:28
zhiyanmarkwash: for 'replace'?20:28
flaper87markwash: I'll take a deeper look into Glance's states and see if I find something that might be worth considering20:28
markwashzhiyan: both replace and add /locations/-20:28
zhiyan'replace' has two: replace to empty, and non-empty20:29
zhiyanmarkwash: i think you means for replace non-empty list, right?20:29
markwashI'm getting a bit bogged down at this point, zhi yan can you and I discuss this later after I take a quick look at the state management in your patch again? I'll be around for your normal work hours20:30
zhiyanreplace locations list to empty list, means removing, replace locations list to non-empty list means adding..20:30
zhiyanmarkwash: of cuuse20:30
markwashgreat20:30
zhiyanof cause20:30
zhiyanthanks20:30
zhiyanok, move on next20:31
markwash#action markwash create a blueprint for centralizing state management / refactoring20:31
markwashlast one in this series is easy I think20:31
markwashhttps://review.openstack.org/#/c/35741/120:31
zhiyanyes20:31
markwashzhiyan: pretty much just needs a rebase to an up-to-date version of the patch we were just discussing20:31
markwashright?20:31
zhiyanmarkwash: need rebase, and not need change code, it is ok for you/team? right20:32
markwashit seems okay to me, I like it20:32
markwash#action zhiyan rebase https://review.openstack.org/#/c/35741 off more recent patch for review20:33
zhiyancool20:33
markwashglance-cinder-driver is next20:33
markwash#topic glance-cinder-driver20:33
*** openstack changes topic to "glance-cinder-driver (Meeting topic: glance)"20:33
zhiyanyep20:33
markwashhttps://review.openstack.org/#/c/35734/ is first I think20:33
*** Riddhi has joined #openstack-meeting-alt20:33
markwashhttps://review.openstack.org/#/c/32864/ is next20:33
zhiyanok20:34
zhiyanyes20:34
*** jbresnah has joined #openstack-meeting-alt20:34
markwashI think the first one is pretty straightforward20:34
markwashwait, maybe I reversed those20:35
markwashhttps://review.openstack.org/#/c/32864/ is the one that seems easiest to me20:35
markwashyikes my browser stopped acting normal20:35
markwashokay got the order right the first time20:35
markwashso #35734 just needs some approvals I think20:36
zhiyan:)20:36
markwashand I have honestly not gotten around to #32864 yet20:36
jbresnahsorry i am late!20:36
markwashjbresnah: we talked about you in your absence20:37
markwashmostly good thing!20:37
markwashs/thing/things/20:37
jbresnahheh20:37
flaper87I still need to get through those reviews as well20:37
jbresnahsorry i was totally wrapped up in rebase for last patch20:37
flaper87I think I already reviewed the first one20:37
markwashzhiyan: just for context, how terrible would it be if #32864 missed h-2 and showed up early in h-3 ?20:38
*** IlyaE has joined #openstack-meeting-alt20:38
markwashzhiyan: end of the world? end of the universe?20:38
* jbresnah has not yet checked out 3286420:38
zhiyanmarkwash: oh, no, i need it...can we try to address it in h2?20:38
markwashzhiyan: I'm only worried because its last in the list, I think there is likely to be enough time20:39
zhiyanyou know, i prepare above patchs, just want to give cinder-driver support20:39
markwashall right, good to know20:39
zhiyanmarkwash: so a little sad about it....doing some supporting things but lost the key one...20:40
markwashthe stuff you've been doing has been a great help to getting multiple locations off the ground, and I was quite happy when I realized that our "solution" for getting the cinder driver working with multiple locations was exactly what the previous ptl had intended20:40
zhiyani'm pretty sure #32864 is very easy..20:40
markwashthanks to you (and everyone) for all the hard work!20:41
*** sarob__ has quit IRC20:41
zhiyanfor #2864, the key change just here: https://review.openstack.org/#/c/32864/6/glance/store/cinder.py20:41
markwashyeah I suppose it looks pretty straightforward20:41
markwashwell I think we're good20:42
markwashjbresnah, let me circle back to you now20:42
markwashwe talked a bit earlier about https://review.openstack.org/#/c/34492/20:42
markwashI think that just needs a rebase for merge conflicts20:42
markwashhere comes patchset 20!20:42
jbresnahyeah20:43
jbresnahheh20:43
jbresnahit has been an adventure20:43
jbresnahhopefully i will send in for review as soon as tox passes in the window right there ---><20:43
jbresnahhopefully i will send in for review as soon as tox passes in the window right there --->20:43
jbresnahit would be amazing if that merged tody20:43
jbresnahi would make a sizable donation to the charity of the approvers choice20:44
markwashzhiyan: jbresnah flaper87 are all of you going to be with us next week? or planning some time off?20:44
* jbresnah is entirely out of vacation time20:44
jbresnahmarkwash: i have some day job stuff to do but i will be around20:44
zhiyanmarkwash: zhiyan will here20:45
nikhiljbresnah: i was just about to hit +120:45
nikhil:)20:45
jbresnahsorry i have been gone so much20:45
jbresnahi will try to make up for it with timely reviews20:45
markwashwell, I think that covers everything I'm worried about for the project updates20:45
flaper87markwash: I'll be on-line and working20:46
markwash#topic open discussion20:46
*** openstack changes topic to "open discussion (Meeting topic: glance)"20:46
jbresnahugh, i know ihave things to talk about but my brain is failing me20:46
markwashIn two weeks, I want us to reevaluate our h-3 targeted blueprints20:46
* flaper87 gives jbresnah a Red Bull20:46
*** markmcclain has quit IRC20:46
flaper87markwash: +120:47
jbresnahi am trying to figure out the state of quality of service in openstack20:47
jbresnahfrom waht i can tell, there is basically nothing for that in glance, is that a fair statement?20:47
markwashI've also been kind of neglecting non-h2 reviews lately, so I'm hoping to correct that soon20:47
jbresnahthere are workers, is there a simulatanious connection limit that is enforced by glance proper?20:47
markwashjbresnah: I think that's correct20:47
jbresnahmarkwash: cool thanks20:47
jbresnah+1 h3 re-eval20:47
jbresnahmarkwash: what do you think about doing some serious BP clean up?20:48
markwashugh, probably needed again :-)20:48
* markwash hasn't been looking20:48
jbresnahanything that is not relevant for H and for which the submitters cannot be contacted gets cleaned20:48
jbresnahis that a reasonable thing to do?20:49
markwashthe great thing is that we now have "ongoing" and "future" milestones20:49
markwashjbresnah: sounds reasonable20:49
flaper87jbresnah: +120:49
jbresnahcool20:49
jbresnahi had contact with one but failed to give him the time for the meeting today :-(20:50
jbresnahi will correct that this afternoon i hope20:50
jbresnahand https://review.openstack.org/#/c/34492/20:50
jbresnahPS20 is in20:50
markwashany early notice on that would be appreciated, b/c otherwise I might hog all the meeting time with my own concerns20:50
jbresnahmarkwash: cool, maybe i will setup a side time for that20:50
markwashokay, looks like the well might have run dry20:51
markwashthanks to everybody for all the hard work, dealing with the awkward timezone issues, and all the diligent reviews20:52
flaper87+! for everyone20:52
flaper87+120:52
jbresnahyeah, thanks!20:52
jbresnahas a TZ problem child I am really grateful and impressed with the energy glance has lately!20:52
markwashmeeting next week will be the early timeslot20:53
markwash1400 UTC20:53
zhiyanthanks all for review and support!20:53
flaper87markwash: cool, Does that get updated in the ical ?20:54
markwashflaper87: I *think* its supposed to already be up to date there, but I had trouble updating my client when I tried to verify20:54
icchatotslly unrelated note i have a question :) let me kniw whenever there is a window :)20:55
flaper87markwash: oke-doke! Will check that and let you know20:55
flaper87markwash: oh, it is updated20:55
flaper87cool20:55
markwashiccha: nows your chance!20:56
zhiyan4 mins left20:56
*** demorris_ has joined #openstack-meeting-alt20:56
icchamarkwash: do we have a stance on soft deletes? as glance. i have seen emails in openstack mailing list about shadow tables for a bunch of projects incl glance20:57
icchaalso seeing the oslo db pathc up in review. it has lot of great things to offer but we can always pick and choose20:57
flaper87iccha: IMHO, we shouldn't merge those blindly. We should pick the features we want to have in Glance first and then elaborate more the other20:58
markwashI'm open to whatever on shadow tables, they seem better than soft deletes, but I do also worry that its solving the problem at the wrong layer20:58
icchaI am against soft deletes too ftr20:58
*** demorris has quit IRC20:58
*** demorris_ is now known as demorris20:58
flaper87markwash: agreed!20:58
icchajust wanted to make sure we keep thinking about it :)20:58
markwashb/c for example, each driver would need to solve it differently, which maybe is fine, maybe suboptimal though20:58
flaper87we need to think more about that20:59
markwashI've been working with somebody at my company to pursue different drivers20:59
markwashand the conclusion is pretty clear -- db api needs to go, it is abstracting the db at way too high a layer21:00
markwash"go" means "become legacy only used by v1"21:00
markwashfwiw21:00
jbresnah+121:00
markwashnot to invalidate any of the registry db driver stuff, which is invaluable21:00
iccha+121:01
markwashand which i think could be easily ported to a differnt db abstraction21:01
markwashokay, we're out of time!21:01
markwash#endmeeting21:01
*** openstack changes topic to "OpenStack meetings (alternate)"21:01
flaper87+121:01
openstackMeeting ended Thu Jul 11 21:01:21 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-07-11-20.04.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-07-11-20.04.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-07-11-20.04.log.html21:01
icchaseeya everyone!21:01
*** djohnstone has quit IRC21:02
*** zhiyan has left #openstack-meeting-alt21:02
*** vipul is now known as vipul-away21:03
*** vipul-away is now known as vipul21:03
*** sarob has joined #openstack-meeting-alt21:04
*** jbresnah has quit IRC21:09
*** vipul is now known as vipul-away21:18
*** akuznetsov has quit IRC21:20
*** bdpayne has quit IRC21:26
*** akuznetsov has joined #openstack-meeting-alt21:27
*** bdpayne has joined #openstack-meeting-alt21:29
*** megan_w has quit IRC21:29
*** jodom has joined #openstack-meeting-alt21:30
*** akuznetsov has quit IRC21:32
*** jrodom has quit IRC21:34
*** IlyaE has quit IRC21:37
*** vipul-away is now known as vipul21:49
*** Sriram has quit IRC21:50
*** vkmc has joined #openstack-meeting-alt21:52
*** vkmc has quit IRC21:52
*** vkmc has joined #openstack-meeting-alt21:52
*** lastidiot1 has quit IRC21:52
*** demorris has quit IRC22:02
*** rnirmal has quit IRC22:02
*** djohnstone has joined #openstack-meeting-alt22:04
*** djohnstone has quit IRC22:04
*** djohnstone has joined #openstack-meeting-alt22:04
*** djohnstone has quit IRC22:15
*** vipul is now known as vipul-away22:16
*** vipul-away is now known as vipul22:17
*** jodom has quit IRC22:17
*** Riddhi has quit IRC22:21
*** Riddhi has joined #openstack-meeting-alt22:25
*** oz_akan_ has quit IRC22:26
*** mtreinish has quit IRC22:27
*** vipul is now known as vipul-away22:33
*** bdpayne has quit IRC22:33
*** IlyaE has joined #openstack-meeting-alt22:33
*** bdpayne has joined #openstack-meeting-alt22:34
*** vipul-away is now known as vipul22:35
*** jbresnah has joined #openstack-meeting-alt22:41
*** IlyaE has quit IRC22:42
*** vkmc has quit IRC22:58
*** jcru has quit IRC23:03
*** sballe has quit IRC23:07
*** vipul is now known as vipul-away23:18
*** vipul-away is now known as vipul23:22
*** jbresnah has quit IRC23:43
*** esp1 has quit IRC23:44
*** qwerty_nor has joined #openstack-meeting-alt23:45
*** lastidiot has joined #openstack-meeting-alt23:54
*** Riddhi has quit IRC23:54

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