Thursday, 2013-08-22

*** sarob_ has joined #openstack-meeting-alt00:01
*** jcru has quit IRC00:02
*** sarob has quit IRC00:04
*** dina_belova has joined #openstack-meeting-alt00:28
*** dina_belova has quit IRC00:33
*** chmouel has quit IRC00:36
*** iccha has quit IRC00:36
*** westmaas has quit IRC00:36
*** iccha has joined #openstack-meeting-alt00:36
*** westmaas has joined #openstack-meeting-alt00:36
*** chmouel has joined #openstack-meeting-alt00:37
*** juice has quit IRC00:37
*** juice has joined #openstack-meeting-alt00:37
*** NehaV has joined #openstack-meeting-alt00:46
*** sarob_ has quit IRC00:51
*** NehaV has quit IRC01:06
*** NehaV has joined #openstack-meeting-alt01:06
*** markmcclain has quit IRC01:07
*** grapex has quit IRC01:09
*** NehaV has quit IRC01:10
*** arborism has quit IRC01:18
*** dina_belova has joined #openstack-meeting-alt01:28
*** dina_belova has quit IRC01:33
*** dhellmann is now known as dhellmann_01:48
*** vkmc has quit IRC01:48
*** esker has joined #openstack-meeting-alt01:52
*** NehaV has joined #openstack-meeting-alt02:06
*** amytron has quit IRC02:17
*** esker has quit IRC02:22
*** NehaV has quit IRC02:28
*** dina_belova has joined #openstack-meeting-alt02:29
*** dina_belova has quit IRC02:33
*** esker has joined #openstack-meeting-alt02:38
*** esker has quit IRC02:58
*** esker has joined #openstack-meeting-alt02:59
*** markmcclain has joined #openstack-meeting-alt03:00
*** esker has quit IRC03:03
*** dina_belova has joined #openstack-meeting-alt03:29
*** dina_belova has quit IRC03:34
*** HenryG_ has joined #openstack-meeting-alt03:54
*** HenryG has quit IRC03:57
*** anteaya has quit IRC04:03
*** sballe_ has quit IRC04:23
*** mberwanger has joined #openstack-meeting-alt04:24
*** dina_belova has joined #openstack-meeting-alt04:30
*** markmcclain has quit IRC04:33
*** markmcclain has joined #openstack-meeting-alt04:33
*** dina_belova has quit IRC04:35
*** boris-42 has joined #openstack-meeting-alt04:36
*** akuznetsov has joined #openstack-meeting-alt04:40
*** SergeyLukjanov has joined #openstack-meeting-alt04:53
*** sacharya has quit IRC05:08
*** akuznetsov has quit IRC05:13
*** mberwanger has quit IRC05:16
*** akuznetsov has joined #openstack-meeting-alt05:18
*** dina_belova has joined #openstack-meeting-alt05:30
*** dina_belova has quit IRC05:35
*** dmakogon_ has joined #openstack-meeting-alt05:58
*** SergeyLukjanov has quit IRC06:15
*** HenryG_ has quit IRC06:30
*** dina_belova has joined #openstack-meeting-alt06:31
*** dina_belova has quit IRC06:36
*** SergeyLukjanov has joined #openstack-meeting-alt07:05
*** markmcclain has quit IRC07:18
*** dina_belova has joined #openstack-meeting-alt07:32
*** dina_belova has quit IRC07:36
*** SergeyLukjanov has quit IRC07:40
*** akuznetsov has quit IRC07:41
*** boris-42 has quit IRC07:58
*** akuznetsov has joined #openstack-meeting-alt08:18
*** dmakogon_ has quit IRC08:26
*** ruhe has joined #openstack-meeting-alt08:30
*** dina_belova has joined #openstack-meeting-alt08:32
*** dina_belova has quit IRC08:37
*** dina_belova has joined #openstack-meeting-alt09:33
*** dina_belova has quit IRC09:37
*** boris-42 has joined #openstack-meeting-alt09:37
*** yportnova has left #openstack-meeting-alt09:43
*** enikanorov_ has joined #openstack-meeting-alt09:47
*** tattabbum has joined #openstack-meeting-alt09:58
*** tattabbum has quit IRC10:00
*** ruhe has quit IRC10:15
*** ruhe has joined #openstack-meeting-alt10:26
*** ruhe has quit IRC10:30
*** dina_belova has joined #openstack-meeting-alt10:33
*** dina_belova has quit IRC10:38
*** openstack has joined #openstack-meeting-alt15:12
-hobana.freenode.net- [freenode-info] channel trolls and no channel staff around to help? please check with freenode support: http://freenode.net/faq.shtml#gettinghelp15:12
*** ChanServ sets mode: +o openstack15:12
eskerbswartz: here15:13
bswartzshamail: no everyone from netapp has been heads down on havana-3 stuff15:13
bswartzrob did you want to share the wiki links?15:13
shamailbswartz: thanks15:13
eskerhttps://wiki.openstack.org/wiki/Shares_Service15:13
eskerNeeds work... good thing it's a wiki so others can help improve it ;-)15:14
bswartzif dowillia is here, feel welcome to file BPs -- let me know if you have problems15:14
bswartzI want to get BPs for the network plumbing stuff entered, and linked to functional specs15:14
bswartzeven if we don't have people or dates for that work15:15
vbellurbswartz: dowillia has a conflict today, I will pass on the message to him.15:15
*** KenD_EMC is now known as KDurazzo15:15
bswartzthe network plumbing will be the most interesting and fun work probably15:15
bswartzhowever it will probably require much discussion15:15
shamailbswartz: agreed.15:15
bswartzwe won't have any formal sessions scheduled at the conference in November, but we should definitely create 1 or 2 unconference sessions to get together and hammer out plans15:16
vbellurbswartz: agree15:16
bswartzand anything we can get written up and shared w/ the group between now and Hong Kong is good -- please share it at these meetings15:17
eskerDesign summit sessions haven't been established yet to the best of my knowledge15:17
*** ruhe has quit IRC15:17
bswartzesker: I know15:17
bswartzokay so by next week we'll have some names of people we can assign BPs to15:18
bswartzand I'll have the rest of the BPs up15:18
shamailbswartz: Is now the time to start discussing/submitting other potential BPs besides quotas, networking plumbing or getting these entered is good enough until the conference? (new to this process overall)15:18
vbellurbswartz: sounds like that, i'll also try putting together some BPs15:18
eskerAlso, wrt the Summit: http://www.openstack.org/rate/Presentation/file-share-services-for-openstack15:18
bswartzshamail: yes we can never have too many BPs15:18
shamailbswartz: thanks for the info.15:19
bswartzworse case they won't get targetted or assigned15:19
eskervotes would be appreciated15:19
*** jmontemayor has joined #openstack-meeting-alt15:19
bswartzhowever it's good to capture all the ideas in one place15:19
bswartzesker: thanks for posting that15:19
bswartzalso if you're not familiar with Launchpad or BPs, BPs tend to be short -- a few paragraphs about an idea15:20
bswartzif possible it's good to link to a full-length functional spec on the openstack wiki15:20
shamailbswartz: thanks15:20
bswartzso if you can describe your ideas in detail then there's an easy place to go find them and we can discuss15:20
bswartzhttps://launchpad.net/manila/15:20
bswartzthat's our LP page for any that don't have the link15:21
*** tanisdl has quit IRC15:21
*** tanisdl has joined #openstack-meeting-alt15:21
bswartzalso, please join in #openstack-manila if you're haning out on IRC and interested in the project15:22
shamailbswartz: will do15:22
vbellurbswartz: what might be a good time to propose manila for incubation in havana?15:22
bswartzvbellur: I would like to be ready to propose it by the havana release time -- so late October15:23
bswartzthat means we need to have the code all cleaned up and working, and hosted on stackforge by that time15:23
vbellurbswartz: right15:23
bswartzthen we can run icehouse like a normal release, albeit as an incubated project not an official one15:23
SamFis that realistic, was it all working under cinder?15:24
bswartzSamF: yes absolutely15:24
bswartzall of the APIs are working and the manager/driver code are working15:24
bswartzI expect some things to blow up during the refactoring15:24
bswartzbut we can get those fixed in the next 2 months15:25
SamFthen that seems like a good goal.15:25
bswartzSamF: the main limitation to the existing code is that it assumes a flat network, or it assume that network plumbing is an exercise for the user15:25
*** lpabon has joined #openstack-meeting-alt15:25
KDurazzoare there any specific milestones that absolutely need to be completed prior to the havana meeting?15:25
vbellurlpabon: hey there15:26
KDurazzoto ensure success for project approval15:26
lpabonvbellur: hi, sorry for coming in late15:26
bswartzKDurazzo: I'm not sure if there's a technical requirement that we have to be a certain state by a certain date to become an incubated project15:26
bswartzI think projects can get on the incubation track any time15:26
vbellurlpabon: np, we are right now discussing the process involved for incubating manila15:27
lpabongreat15:27
bswartzhowever it's in our best interest to line up with the havana release, so icehouse can be run like a normal release15:27
KDurazzobswartz: thanks for the clarification15:27
bswartzany other questions or topics?15:28
vbellurbswartz: nothing more on that, looks good to me.15:28
shamailbswartz: just one question since I'm just joining... what are the use cases?15:28
bswartzfor those of you who joined late, I apologize the bot didn't record this meeting15:28
shamailbswartz: generic shared folders or are we assuming shared app files as well?15:28
bswartzshamail: take a look at the wiki page https://wiki.openstack.org/wiki/Shares_Service15:29
lpaboni will like to introduce myself - I will be one of the Red Hat engineers working on Manila project15:29
gkleimanwhat is the next step on the name?15:29
bswartzlpabon: welcome!15:29
shamailbswartz: thanks, I'll probably see you in the openstack-manila room too.15:29
vbellurlpabon: I alluded to that before you joined in :)15:29
lpabonvbellur: Great! :-)15:30
*** ruhe has joined #openstack-meeting-alt15:30
bswartzshamail: the goal of this project is to create the management interface necessary to allow cross-vendor NAS services to be managed and attached to openstack tenants/instances15:30
*** dkoryavov_ has joined #openstack-meeting-alt15:31
bswartzwhat the end user does with them after they're connected is mostly out of scope for us, but we want to enable as wide a set of use cases as possible15:31
eskerregarding name, we ran through several possibilities... all of which ran afoul of trademark sensibilities15:32
shamailbswartz: understood, i'll read through the wiki use cases tonight.15:32
eskermanila is a working name, but is increasingly likely to be what we settle on15:32
bswartzgkleiman: regarding the name, we're sticking w/ manila until someone sues us15:32
eskertrademark search not yet complete though15:32
eskerAny objections?15:33
gkleimanbswartz: love it15:33
KDurazzoesker: none here15:33
bswartzyeah I'll ask if anyone knows of specific problems with the name manila15:33
SamFworks for me15:33
vbellurmanila++ from me15:33
*** dkoryavov has quit IRC15:33
lpabon+115:34
bswartzI like it because it's the same number of letters as cinder and the global find/replace operation will not change any line lengths15:34
bswartzplus it's a proper noun, and less likely to run into trademark issues because of that15:35
bswartzokay if there are no more topics, I'll end this meeting and see you all in #openstack-manila15:35
*** dina_belova has joined #openstack-meeting-alt15:35
shamailNice to meet everyone, take care!15:35
bswartzand again, this meeting was not recorded by the openstack bot, but I have the logs if anyone needs them15:35
eskerlikewise, thanks!15:35
vbellurshamail: good meeting you too!15:35
lpabontake care15:35
*** markwash has quit IRC15:36
SamFbye15:36
*** shamail has quit IRC15:36
vbellurSamF: bye15:36
KDurazzobye15:36
*** KDurazzo has quit IRC15:36
gkleimanbswartz: will the next meeting be on openstack-manila or stay on meeting-alt?15:36
*** SamF has quit IRC15:36
vbellurgkleiman: the plan is to continue having meetings here afaik.15:37
bswartzgkleiman: these weekly meeting will always be in this room, but only at 1500UTC thursdays15:37
bswartzwe're in #openstack-manila all day every day15:37
*** djohnstone1 has joined #openstack-meeting-alt15:53
*** djohnstone1 has quit IRC15:53
*** djohnstone1 has joined #openstack-meeting-alt15:53
*** bswartz has left #openstack-meeting-alt15:53
*** dkoryavov_ has quit IRC15:54
*** dkoryavov_ has joined #openstack-meeting-alt15:54
*** djohnstone has quit IRC15:56
*** alexpecoraro has joined #openstack-meeting-alt15:58
*** dina_belova has quit IRC15:58
*** bdpayne has joined #openstack-meeting-alt15:58
*** dkoryavov_ has quit IRC15:59
*** dkoryavov_ has joined #openstack-meeting-alt15:59
*** akuznetsov has quit IRC16:04
*** apecs has joined #openstack-meeting-alt16:07
*** alexpecoraro has quit IRC16:07
*** apecs is now known as alexpecoraro16:07
*** ruhe has quit IRC16:11
*** SergeyLukjanov has quit IRC16:14
*** ruhe has joined #openstack-meeting-alt16:19
*** ruhe has quit IRC16:19
*** SergeyLukjanov has joined #openstack-meeting-alt16:28
*** dina_belova has joined #openstack-meeting-alt16:29
*** dkoryavov_ has quit IRC16:30
*** amytron has quit IRC16:33
*** amytron has joined #openstack-meeting-alt16:33
*** pdmars has quit IRC16:37
*** markwash has joined #openstack-meeting-alt16:40
*** apecs has joined #openstack-meeting-alt16:41
*** alexpecoraro has quit IRC16:43
*** apecs has quit IRC16:43
*** alexpecoraro has joined #openstack-meeting-alt16:43
*** Sriram has joined #openstack-meeting-alt16:45
*** Sriram has quit IRC16:46
*** dina_belova has quit IRC16:57
*** esp2 has joined #openstack-meeting-alt16:57
*** esp2 has left #openstack-meeting-alt16:57
*** djohnstone1 has quit IRC17:00
*** SergeyLukjanov has quit IRC17:00
*** esp2 has joined #openstack-meeting-alt17:05
*** SergeyLukjanov has joined #openstack-meeting-alt17:05
*** esp2 has left #openstack-meeting-alt17:05
*** vbellur has left #openstack-meeting-alt17:10
*** SergeyLukjanov has quit IRC17:22
*** arborism has joined #openstack-meeting-alt17:24
*** boris-42 has joined #openstack-meeting-alt17:25
*** nadya has joined #openstack-meeting-alt17:25
*** arborism has left #openstack-meeting-alt17:27
*** pcm_ has quit IRC17:28
*** venkatesh has joined #openstack-meeting-alt17:29
*** pcm_ has joined #openstack-meeting-alt17:32
*** markmcclain has quit IRC17:33
*** venkatesh has quit IRC17:36
*** nadya has quit IRC17:42
*** vkmc has quit IRC17:45
*** sreshetnyak has joined #openstack-meeting-alt17:45
*** dina_belova has joined #openstack-meeting-alt17:45
*** SergeyLukjanov has joined #openstack-meeting-alt17:46
*** ruhe has joined #openstack-meeting-alt17:48
*** key2 has quit IRC17:50
*** jmontemayor has quit IRC17:53
*** dmitryme has joined #openstack-meeting-alt17:54
*** akuznetsov has joined #openstack-meeting-alt17:55
*** vkmc has joined #openstack-meeting-alt17:57
*** vkmc has joined #openstack-meeting-alt17:57
*** aignatov has joined #openstack-meeting-alt17:58
*** nadya has joined #openstack-meeting-alt17:58
SergeyLukjanovsavanna team meeting will be here in 5 mins17:58
*** NikitaKonovalov has joined #openstack-meeting-alt17:59
*** jmontemayor has joined #openstack-meeting-alt18:00
*** mattf has joined #openstack-meeting-alt18:01
*** pdmars has joined #openstack-meeting-alt18:03
*** eankutse has quit IRC18:04
ogelbukhSergeyLukjanov: o/18:04
SergeyLukjanovogelbukh, howdy18:04
SergeyLukjanovare there anyone from Hortonworks?18:06
SergeyLukjanovok, it's time to start the meeting18:07
SergeyLukjanov#startmeeting savanna18:07
openstackMeeting started Thu Aug 22 18:07:36 2013 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.18:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:07
*** openstack changes topic to " (Meeting topic: savanna)"18:07
openstackThe meeting name has been set to 'savanna'18:07
aignatovhi18:07
rnirmalhi18:07
ruhehello18:07
SergeyLukjanovo/18:07
SergeyLukjanov#topic Agenda18:08
SergeyLukjanov#info News / updates18:08
SergeyLukjanov#info Roadmap cleanup / update18:08
SergeyLukjanov#info Action items from the last meeting18:08
SergeyLukjanov#info PTL election results18:08
*** openstack changes topic to "Agenda (Meeting topic: savanna)"18:08
SergeyLukjanov#info REST API refactoring discussion18:08
SergeyLukjanov#info EDP discussions18:08
SergeyLukjanov#info General discussion18:08
SergeyLukjanov#topic News / updates18:08
*** openstack changes topic to "News / updates (Meeting topic: savanna)"18:08
sacharyahi18:08
SergeyLukjanovfolks, let's share news18:08
SergeyLukjanovfirst of all, we merged conductor code18:09
SergeyLukjanovand migration to the new db layer has been completed18:09
SergeyLukjanov#info conductor code merged, migration to the new db layer completed18:09
akuznetsovOn edp part we have a REST API for data source, job and job origin creation18:10
aignatovit's me with Oozie18:10
aignatovagain18:10
SergeyLukjanov#info first part of UI code for EDP merged18:10
nadyain edp part we have a prototype that successfully works with pig-workflow creation and running18:10
mattf#info savanna-image-elements (savanna-extra) and python-savannaclient packages have been accepted into Fedora 19. https://bugzilla.redhat.com/show_bug.cgi?id=998702  and https://bugzilla.redhat.com/show_bug.cgi?id=9987021 respectively.18:10
SergeyLukjanov#info integration tests for HDP plugin added18:10
aignatovi've updated vanilla plugin to be able to start oozie service with needed heap size18:11
akuznetsovI hope tomorrow we have a first draft for scheduling job on demand cluster18:11
*** tmckay has joined #openstack-meeting-alt18:12
SergeyLukjanovsounds great18:12
mattftopic for general discussion - for 0.3, should we plan to release to Fedora & EPEL at the same time as OpenStack or should Fedora & EPEL happen after?18:12
SergeyLukjanovany other news/updates?18:12
SergeyLukjanovmattf, ok, let's discuss it in the general section18:12
nadyaguys from RedHat began to work with binaries18:13
aignatovalso we've backported some fixes related to hdp plugin18:13
*** dmakogon_ has joined #openstack-meeting-alt18:13
aignatovto stable/0.218:13
SergeyLukjanov#info EDP support partially added to the client18:13
SergeyLukjanovok, let's move on18:13
SergeyLukjanov#topic Roadmap cleanup / update18:14
*** openstack changes topic to "Roadmap cleanup / update (Meeting topic: savanna)"18:14
SergeyLukjanovare there any thoughts about adding/updating points to the Roadmap?18:14
SergeyLukjanovok, great :)18:14
SergeyLukjanov#topic Action items from the last meeting18:14
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)"18:14
SergeyLukjanov#info there are no action items from the last meeting18:14
mattfnothing from me for this week. i did notice a blog post about savanna that identified us as planning to incubate for 1.0, source was the roadmap.18:15
ruhecan you give us a link?18:16
mattfi'll try to dig it up later18:16
ruhethanks18:16
SergeyLukjanovok, let's move on18:16
SergeyLukjanov#topic PTL election results18:17
*** openstack changes topic to "PTL election results (Meeting topic: savanna)"18:17
mattf#info Congrats to SergeyLukjanov, who won the PTL election 14-0 - https://wiki.openstack.org/wiki/Savanna/PTL18:17
SergeyLukjanovmattf, please18:17
ruhecongrats Sergey18:17
mattfi'll post the results to os-dev as well18:17
SergeyLukjanovmattf, good news ;)18:17
rnirmalcongrats..18:17
SergeyLukjanovmattf, thank you for preparing and driving election process!18:17
mattfthe electorate contained 20 voters, so SergeyLukjanov got over 50%, which is nice given he was uncontested18:17
rnirmalnice "Sergey Lukjanov (14) won against None (0)"18:18
tmckaywow, 14-018:18
aignatovgreat news18:18
tmckayNone got None18:18
mattfSergeyLukjanov, you're all welcome, and congrats to you Sergey18:18
SergeyLukjanovthanks :)18:18
SergeyLukjanov#info REST API refactoring discussion18:18
SergeyLukjanovrnirmal, please18:19
rnirmal#link https://blueprints.launchpad.net/savanna/+spec/refactor-v1api18:19
rnirmalthat's the blueprint. I have some notes at #link https://etherpad.openstack.org/savanna_refactor_v1_api18:19
mattfruhe, http://bighadoop.wordpress.com/2013/08/18/openstack-savanna-fast-hadoop-cluster-provisioning-on-openstack/18:20
rnirmalIt may seem a whole lot to tackle at once...but I'd like to discuss each item before I or someone else can proceed to implement those changes18:20
ruhemattf, thanks again18:20
rnirmalhow do you'll want to proceed.. can I talk about one or 2 items today ?18:20
rnirmalI'm trying to put some high level points here #link https://wiki.openstack.org/wiki/Savanna/ApiUpdates18:21
SergeyLukjanovrnirmal, maybe it'll be more useful to start a thread in ML about it to involve more folks to it? btw we can discuss several items today18:21
rnirmalSergeyLukjanov: yes I'll do that as well, that may be more helpful for a better conversation18:22
*** yogesh has joined #openstack-meeting-alt18:22
ruhernirmal, so the goal is to separate the concerns for a Deployer and User. Is it a common practise in other OS components?18:22
rnirmalruhe: yes thru making parts of the extensions or api as admin_only18:23
*** djohnstone has joined #openstack-meeting-alt18:23
rnirmalI don't think any other project other than Trove that has a separate admin api18:23
SergeyLukjanovrnirmal, yep, we're thinking about adding admin_only apis18:23
sacharyaAnd also, only mandatory features thats common between all plugins should be in core.. so users can theoretically switch between providers18:24
rnirmala separate admin api would be nice... but making some admin_only extensions will be a good place to start18:24
rnirmaltrue that as well... I think so far both the plugins are on par18:24
SergeyLukjanovrnirmal, we have some plans on updating REST API code from flask to more OS common solutions18:24
rnirmalSergeyLukjanov: yeah there's been some discussions on using a common solution, but don't think one has emerged18:25
SergeyLukjanovcurrently there is no ability to add extensions easily18:25
SergeyLukjanovI don't think that it could be done in 0.3 version18:25
rnirmalsorry I'm not too familiar with flask..18:25
tmckayI think keystone is an example of an api split between admin and user, iirc18:26
rnirmalwhich maybe fine18:26
SergeyLukjanovbut it's a good time to discuss how the 2.0 API whould looks like18:26
rnirmalthank tmckay yeah keystone has that18:26
* tmckay loves flask18:26
rnirmalso I guess before we start off... 2.0 is how you'll want it to go rather than updating 1.0 ?18:26
SergeyLukjanovcurrently the are a lot of code done that depends on API - client, dashboard, etc, so we don't want to break it18:27
SergeyLukjanovrnirmal, currently we have now plans for the 2.0 REST API, but it looks like that it's a great candidate to be the next REST API polished and more functional than current one18:28
rnirmalSergeyLukjanov: would you consider that as the primary API we could say go to incubation with ?18:28
*** mattf is now known as _mattf18:29
*** sarob has joined #openstack-meeting-alt18:29
SergeyLukjanovrnirmal, I think we have no time to rework the API from scratch before the 0.3 release18:29
*** _mattf is now known as mattf18:29
rnirmalSergeyLukjanov: agree it's going to take some effort.. when is 0.3 slated for ?18:30
SergeyLukjanovmid of Oct18:30
sacharyaand when is the plan to apply for incubation?18:30
SergeyLukjanovwe'll send an incubation application in several weeks18:30
rnirmalhmm we could depending on the extent of the changes...18:30
*** sarob has quit IRC18:31
rnirmalbut I think a 2.0 api will give us a little more freedom to work things out18:31
*** sarob has joined #openstack-meeting-alt18:31
SergeyLukjanovrnirmal, yep, it could be discussed and designed much better if we'll have much time to do it18:31
*** eankutse has joined #openstack-meeting-alt18:31
*** eankutse has quit IRC18:32
*** eankutse has joined #openstack-meeting-alt18:32
*** yogesh has quit IRC18:33
rnirmaltotally agree... do we have a consensus there18:33
SergeyLukjanovany objections for moving API improvements to the next release?18:34
crobertsrhMakes sense to me18:34
nadyarnirmal, do you think that migration to new API may be done gradually?18:34
rnirmalnadya: as in not make it too drastically different from the current 1.0?18:35
SergeyLukjanov#info move API improvements to the next release (REST API v. 2.0 ?)18:35
*** sarob has quit IRC18:35
SergeyLukjanovany other thoughts?18:36
rnirmalit's going to change some existing workflows in how the current api is getting used. so from that case there would be a migration18:36
rnirmalbut hopefully most of the backend will remain close to what it is now18:37
SergeyLukjanov#action rnirmal to start thread in ML to discuss REST API improvements18:39
SergeyLukjanovrnirmal, thank you18:39
SergeyLukjanov#topic EDP discussions18:39
*** openstack changes topic to "EDP discussions (Meeting topic: savanna)"18:39
rnirmalthanks SergeyLukjanov I'll create a new blueprint for 2.0 and work from that18:39
rnirmaland delete the existing one18:39
ruhernirmal, i'd suggest to announce such blueprints in the mailing list, since IRC is not a reliable channel18:39
aignatovagreed with ruhe18:40
SergeyLukjanov+118:40
SergeyLukjanovopen discussion for EDP questions18:40
rnirmalruhe: ok will do.. yeah I figured it was so.. I've been trying to talk about it on irc for the past 2 weeks :)18:40
rnirmalI've got an EDP question18:40
rnirmalwhy 1.1 api for EDP? should be look at keeping the EDP and provisioning api's separate18:41
rnirmalwith it's own versioning?18:41
rnirmalI wasn't involved early on so not sure what the thought process was like18:42
SergeyLukjanovrnirmal, we have no plans for doing it now, it should be discussed too18:42
rnirmalok18:42
SergeyLukjanovcan't see any pros and cons now for doing it18:42
rnirmalyeah don't want to change it now, but just wondering18:42
SergeyLukjanovbut I think that EDP depends on the main API18:42
ruhemy opinion - let's keep things simple for now. if we'll see that separate versioning is really necessary, then make it's own versioning18:43
akuznetsovrnirmal  EDP can add some feature to main API for example transient cluster18:43
rnirmalok looks like there's some reason to keep it layered than separate18:44
rnirmalcool thanks.18:44
tmckayI have a minor question related to EDP rest API.  I've noticed that we don't have a good handler for "duplicate" errors from the db.18:45
tmckay    "error_code": 500,18:45
tmckay    "error_message": "Internal Server Error",18:45
tmckay    "error_name": "INTERNAL_SERVER_ERROR"18:45
tmckayis typical18:45
tmckayThis suggests to me a "check_not_exist" validation on the urls.  I chatted with nadya about this yesterday.  Thoughts?18:46
tmckay(for create calls, that is)18:46
SergeyLukjanovtmckay, there are some problems with handling several errors...18:46
rnirmalhmm that should be a 400 bad request, suggesting duplicate information.18:47
rnirmalnot sure if 409 would be applicable in this case18:47
rnirmalsince the resource does not exist yet18:47
SergeyLukjanovrnirmal, yep, 400 looks better18:47
SergeyLukjanovtmckay, could you please create an issue for it?18:47
tmckayyes.  Should it be blueprint, or just an issue?18:48
aignatovjust an issue18:48
rnirmaljust looks like a bug18:48
tmckaywill do18:48
ruhei like everything which would help users to understand the reason of error, and provide more information to us developers in the logs18:48
tmckayabsolutely18:48
SergeyLukjanovany other questions/thoughts?18:50
SergeyLukjanov#action tmckay to create an issue about incorrect handling of "duplicate" errors18:50
aignatovI think we should have an validation logic to check if Oozie service presents on existing cluster running for EDP purposes18:51
aignatovif doen't present18:51
aignatovstop runing jobs18:51
*** yogesh has joined #openstack-meeting-alt18:51
aignatovstarting job)18:51
*** NikitaKonovalov has quit IRC18:51
SergeyLukjanovsounds reasonable18:52
akuznetsovyes we should add this check18:53
SergeyLukjanov#action aignatov to create an issue about lack of the validation while starting job (check for Oozie before it)18:53
SergeyLukjanovok, let's move on18:53
SergeyLukjanov#info General discussion18:53
nadyawill we support several swifts: one for input data and one for output?18:53
mattfwhen we do a release we produce tarballs for the openstack community. i'd like opinions on if (a) we should try to synchronize release of packages to fedora+epel or (b) we should have fedora+epel lag the openstack community release18:54
nadyaI mean one swift from other clour e.g.18:54
nadya*cloud18:54
rnirmalmattf: b18:55
ruhemattf, what shall we do when we have ubuntu packages? (b) is the only option imho18:55
SergeyLukjanovabsolutely agree with ruhe18:55
akuznetsovalso i think there is also valid use case for copy data from one tenant to other18:55
mattfruhe, what makes you say that?18:56
SergeyLukjanovand additionally it's not a common process for other OS projects18:56
mattfSergeyLukjanov, yup18:56
ruhewell, if we choose (a) we'll sync with fedora+epel. then we'll create ubuntu packages and we'll want to sync with ubuntu part. it looks too complex to me18:57
aignatovrnirmal, do you have plans to finish your bugfix patch https://review.openstack.org/#/c/42005/18:57
rnirmalaignatov: yes added more more check will push that out soon18:57
mattfruhe, (a) is only about pushing packages to fed+epel, not synchronizing our release with theirs18:57
ruheoh, i see now18:58
mattfthe impact of (a) would be some time window to do release engineering work to prepare the push before official release18:58
aignatovrnirmal, ok, great18:58
rnirmalaignatov: added the fix for your comment.. just went back and looked at where all it was used18:59
aignatovok18:59
ruhemattf, since you're the only person who can do that, i think it might be a SPOF for release of Savanna18:59
SergeyLukjanovmattf, you mean to try to release packages to fed+epel at the same time w/o moving savanna release date?19:00
aignatovit seems we are out of time in this channel19:00
mattfcould be, that power can be expanded tho19:00
SergeyLukjanovaignatov, yep19:00
mattfSergeyLukjanov, yeah19:00
*** yogesh has quit IRC19:00
SergeyLukjanovthank you folks, let's move to the #savanna channel19:00
mattfoops, ok19:00
SergeyLukjanov#info JFYI you can always use openstack-dev@lists.openstack.org mailing lists and #savanna irc channel to find us and ask your questions19:00
SergeyLukjanov#endmeeting19:00
*** openstack changes topic to "OpenStack meetings (alternate)"19:00
openstackMeeting ended Thu Aug 22 19:00:54 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-08-22-18.07.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-08-22-18.07.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-08-22-18.07.log.html19:00
*** mattf has left #openstack-meeting-alt19:01
*** crobertsrh has left #openstack-meeting-alt19:01
*** tmckay has left #openstack-meeting-alt19:01
*** sarob has joined #openstack-meeting-alt19:02
*** aignatov has quit IRC19:06
*** akuznetsov has quit IRC19:07
*** nadya has quit IRC19:08
*** sarob has quit IRC19:10
*** jmontemayor has quit IRC19:11
*** SergeyLukjanov has quit IRC19:23
*** yogesh has joined #openstack-meeting-alt19:24
*** NikitaKonovalov has joined #openstack-meeting-alt19:27
*** yogesh has quit IRC19:27
*** ruhe has quit IRC19:27
*** dmitryme has quit IRC19:30
*** hemanth_ has joined #openstack-meeting-alt19:30
*** vipul is now known as vipul-away19:32
*** nadya has joined #openstack-meeting-alt19:34
*** jmontemayor has joined #openstack-meeting-alt19:34
*** amytron_ has joined #openstack-meeting-alt19:35
*** amytron has quit IRC19:36
*** amytron_ is now known as amytron19:36
*** HenryG has quit IRC19:36
*** sarob has joined #openstack-meeting-alt19:37
*** sarob has quit IRC19:41
*** nadya has quit IRC19:44
*** djohnstone has quit IRC19:48
*** SergeyLukjanov has joined #openstack-meeting-alt19:51
*** zhiyan has joined #openstack-meeting-alt19:51
*** sarob has joined #openstack-meeting-alt20:00
*** pcm_ has quit IRC20:00
markwasho/20:01
nikhilo/20:01
markwashglance folks?20:01
zhiyanhey20:01
icchahey20:01
markwash#startmeeting glance20:02
openstackMeeting started Thu Aug 22 20:02:04 2013 UTC and is due to finish in 60 minutes.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: glance)"20:02
openstackThe meeting name has been set to 'glance'20:02
* markwash is a chair!20:02
icchai though markwash is human20:02
*** esheffield has joined #openstack-meeting-alt20:02
markwashmy cats contend that my human-ness is secondary to my chair-ness20:02
brianrhowdy20:03
markwashAs we all know, the H-3 merge deadline is looming.20:03
*** dina_belova has quit IRC20:03
markwashSo I'd like to focus for the first half of this meeting (if it takes that long) on scheduling all the appropriate followups to merge our outstanding blueprints20:03
*** dina_belova has joined #openstack-meeting-alt20:04
markwash#link https://launchpad.net/glance/+milestone/havana-320:04
markwashLet's talk scrubber refactoring first20:05
markwashoh, I should highlight folks to for proper summoning20:05
zhiyanmarkwash: yes, currently IMO the change is ready to you/team review.20:05
*** jbresnah_ has joined #openstack-meeting-alt20:06
markwashIt looks like this is pretty close to ready20:06
markwashzhiyan: I just want to sit down with you and walk through what's going on in some of the core scrubber changes20:06
zhiyanmarkwash: thanks, actually i'd like this part refactoring can be landed firstly, then to location-status part if i'm not wrong.20:06
markwashso can we schedule that for sometime soon?20:06
zhiyanmarkwash: sure, of cause20:07
markwashzhiyan: are you available at 14:00 UTC tomorrow?20:07
markwashoh wait, that's terrible for jbresnah20:07
markwashjbresnah_ that is20:07
*** jbresnah_ is now known as jbresnah20:07
jbresnahsorry i am late!20:08
zhiyanmarkwash: ok, 14:00UTC tomorrow.20:08
jbresnahwhat is the topic of the meeting?20:08
markwashjbresnah: we are talking broadly about landing h-3 bps, and right now glance-scrubber20:08
jbresnahi mean the meeting tomorrow20:08
markwashzhiyan: sorry, I realized that's a bad time. would later today work?20:08
markwashjbresnah: final review of the glance-scrubber refactoring20:08
zhiyanmarkwash: that's ok to me also :)20:09
jbresnaheven just 1500 is a lot better for me20:09
jbresnahif possible20:09
markwashsorry, I realized I actually can't tmrw (sigh!)20:10
markwashlet's just. .20:10
markwash#action zhiyan and markwash to meet for a walkthrough-review of glance scrubber refactoring, others are welcome, time will be announced in #openstack-glance after this meeting20:10
jbresnahcool20:10
markwashnow20:10
markwash#topic basic quotas20:10
jbresnahif it has to be at 1400 i can try to make it20:10
*** openstack changes topic to "basic quotas (Meeting topic: glance)"20:10
markwashjbresnah: aiming for today rather than tmrw morning20:11
jbresnahand if i cannot i will jsut submarine everything you agreed upon in email later20:11
markwashhaha :-)20:11
jbresnahnot really20:11
markwashfor basic quotas, review is here: https://review.openstack.org/#/c/37993/20:12
markwashI started to wade in again, but didn't make it through the current patchset20:12
markwashit looks like there's been considerable back and forth. . does it look like we're getting close?20:12
jbresnahi think so20:13
jbresnah2 big issues that people might not like20:13
*** vkmc has quit IRC20:13
jbresnah1) my handling of multiple locations20:13
jbresnah2) the quota is checked before the upload, and again after20:13
jbresnahi can explain both20:13
zhiyanjbresnah: i like them all since i know the root causes ...20:14
jbresnah#1 is basically the usage is all of a users images times their size20:14
jbresnah...not worded well20:14
jbresnahuseage is sum([image.size * len(image.locations) for image in all_users_images])20:15
jbresnahwhich has some drawbacks20:15
jbresnahbut i think the current feeling is that once a location is added to glance, the associated store 'owns' it20:16
*** sreshetnyak has quit IRC20:16
jbresnahthis discussion came up when talking about delete20:16
jbresnahand if that is true, i think it should could20:16
jbresnah#2 has to happen because we do not always know the size upfront20:16
jbresnahwe could ONLY check after the upload and be safe20:16
jbresnahthe check before is really just an optimization20:17
jbresnahmarkwash: make sense?20:17
markwashyes, thanks for the extra info20:17
markwashI notice there isn't any enforcement on adding a location, yet, do you agree?20:17
jbresnahother than that it is just a simple matter of code ;-)20:17
*** ashwini has joined #openstack-meeting-alt20:17
zhiyanzhiyan: yes, those are not perfect, but it's workable and do the right things, it's trade off20:17
jbresnahmarkwash: that is probably true20:18
zhiyanzhiyan: oh, seems i'm talking to myself.20:18
jbresnahmarkwash: ...it seems so obvious when you say it20:18
jbresnahsigh20:18
zhiyanmarkwash: +120:18
jbresnahi should be able to run that through the quota proxy20:19
jbresnahi think20:19
markwashjbresnah: yes, it might get a little ugly though, fair warning20:19
zhiyanbtw, from the change i fixed a potential image data leak issue: https://review.openstack.org/#/c/42896/20:20
markwashokay, so it sounds like a little bit more dev is needed there, though more review won't hurt with the current patch20:20
markwashlet's move on to the other outstanding bp20:20
markwash#topic protected properties20:20
*** openstack changes topic to "protected properties (Meeting topic: glance)"20:20
markwashiccha: o/20:20
icchamarkwash: /o20:21
icchahemanth_: and me have been working on it20:21
icchawe uploaded first patch yesterday. will do some more refactoring and uplaod more patches today evening/tomorrow20:21
*** NikitaKonovalov has quit IRC20:21
icchaearly review and feedback will be much appreciated20:21
icchamight need some iteration20:21
markwashiccha okay cool, so the bp should be in "Needs Review" now?20:22
icchayes probably20:22
markwashdone20:22
*** NikitaKonovalov has joined #openstack-meeting-alt20:22
markwashall right then20:22
zhiyaniccha: also could you pls attach the review link to bp page?20:23
markwashI think it would also be great to talk a little bit about async processing20:23
markwash#topic async processing20:23
*** openstack changes topic to "async processing (Meeting topic: glance)"20:23
*** NikitaKonovalov has quit IRC20:23
markwashI'm a little worried because I've seen two conflicting patches show up from venkatesh and from flwang20:23
markwashI'm also pretty eager to avoid landing this feature halfway in havana20:24
*** NikitaKonovalov has joined #openstack-meeting-alt20:24
markwashI guess maybe we don't have venkatesh or flwang present20:24
nikhilmarkwash: yes, was working there with fie and venkat to push on these fronts20:24
nikhilnone20:24
nikhili've talked with both today morning20:25
*** dina_belova has quit IRC20:25
zhiyanmarkwash: could you pls paste those two review link to here?20:25
nikhilhowever, dont think flwang knows about venkat's patch20:25
markwashnikhil: I see two ways we could move forward on this20:25
*** SergeyLukjanov has quit IRC20:25
markwashwe can have WIP gerrit reviews, that depend on each other20:25
*** vkmc has joined #openstack-meeting-alt20:25
*** vipul-away is now known as vipul20:25
markwashor if you want more flexibility (but also more overhead) you can set up a branch in one of your own github repos20:26
markwashand manage the commits in there20:26
nikhilmarkwash: actually, that's what i'd intended20:26
nikhilad my commits up in persnal repo was a ref point20:26
nikhilfor both fei and venkat20:26
markwashnikhil: okay, cool. . so then I guess to follow up on that, fei and venkat should either put those reviews as WIP or Abandoned for now20:27
nikhilhowever, fei seems to have submitted the patch so venkat did as well20:27
markwashlol20:27
nikhilmarkwash: gotcha20:27
markwashnikhil: thanks for working with them20:27
markwashzhiyan: I don't have the links on hand one sec20:27
nikhiland thanks for the clarification!20:27
brianrmarkwash: i have a question about our decision to use json blobs in the task objects20:28
markwashbrianr: go for it20:28
brianrhttps://etherpad.openstack.org/LG39UnQA7z20:28
brianrlines 38-4320:28
harlowjasorry, guys, in my other meeting right now, will look over after i think :)20:29
harlowjajust fyi20:29
brianrharlowja: thanks20:29
ameadebrianr: i think we knew jays concern going it right?20:29
markwashbrianr: it is our intention to disallow search20:29
*** sarob_ has joined #openstack-meeting-alt20:29
ameadein**20:29
markwashbrianr: if we need search, we can add it and just change the schema as needed20:30
nikhilmarkwash: i think the intent is to allow search on random string20:30
brianrok, if we think it's not a big deal up front, fine20:30
brianri just had DB migrations20:30
brianr*hate20:30
markwashbrianr: fair20:31
ameadethis would certainly be a terrible migration20:31
markwashdoes there seem to be a need to search for tasks based on their input arguments?20:31
markwashameade: I dunno, there have been several similar keystone migrations, and I'm not sure they were the end of the world20:31
nikhilwe thought it would help searching for tasks markwash20:32
brianrwell it's got to do with idempotence, i guess20:32
*** sarob_ has quit IRC20:32
nikhilin case of multi-tenant20:32
nikhilor rather multi-user in single tenant20:32
*** sarob_ has joined #openstack-meeting-alt20:32
*** sarob has quit IRC20:33
*** ashwini has left #openstack-meeting-alt20:33
markwashI guess I don't follow20:34
brianrdon't know whether we care about 5 imports of the same image or not, really20:34
markwashit seems like the number of tasks wouldn't be very large in general? since we expire them. . .20:34
nikhils/image/image data/20:34
markwashwell, okay… we might need to sync up again20:35
brianrwell, maybe not, the only reason i'm worried is DB migration20:35
nikhilmarkwash: yes, actually fei also wanted to20:35
markwashseveral issues here seem to be pushing back against generalizing imports/exports/clones to generic tasks20:35
nikhilwe need to sync up on interface between async and tasks api20:36
markwashbut OTOH, taskflow generalized much more to tasks20:36
brianrok, well better to talk than not talk20:36
brianrso josh had to leave, but what do you think about taskflow?20:36
brianrfor image import, i mean20:36
markwashI think it looks very relevant, the question is where is the seam for integration?20:36
brianrexactly20:37
nikhil+120:37
markwashwe should find a time to meet about that where we can include harlowja20:37
brianrmy thought is to do import, see what taskflow delivers in havana, and reconsider when we do export and clone20:37
harlowja:)20:37
markwashbecause I want to make sure we're incorporating the correct spirit of taksflow20:37
nikhilup for it20:37
brianrwe should have more domain knowledge at that point20:37
harlowjawho scheduled taskflow weekly meeting and glance one at same time, haha20:37
* markwash hides20:37
markwashokay, there's another bp I wanna talk about quickly20:38
markwashcan you guys coordinate another meeting?20:38
markwashI wanna be there. . but my mother in law is coming to town too. . so20:38
markwash:-)20:38
markwashmy schedule is a bit uncertain right now20:38
markwashbrianr: ^^20:39
brianrso is tomorrow out of the question?20:39
markwashI can't do morning20:39
markwashI could swing this time, but that probably doesn't work for fei20:39
nikhilfei and i wanted to sync up with some of the folks here20:40
nikhilsometime probably early next week20:40
markwashokay let's just coordinate through email then20:40
nikhilwho is doing that?20:40
nikhili meant20:40
brianrok, maybe monday at 15:00 again?20:40
nikhilanyone doing that or shoud i?20:40
nikhilbrianr: that may be  tricky for fei20:41
markwashone of you two should :-)20:41
nikhilbut sure if you think :)20:41
nikhilmarkwash: ok sure20:41
markwash#topic openstack common notifier20:41
*** openstack changes topic to "openstack common notifier (Meeting topic: glance)"20:41
brianri meant whatever time we met the other day, it worked for fei20:41
markwashso, this has come back up, again for support of ha rabbit setups20:41
markwashreview https://review.openstack.org/#/c/37511/20:41
markwashand a followup https://review.openstack.org/#/c/43319/20:42
markwashI'd just like to request more eyes on that20:42
markwashit looks like we can land this in H-3 without being disruptive20:42
markwashbut in particular I want some review of the config changes--want to make sure it won't cause problems for deployers20:43
jbresnahthere is something about patches that port to oslo that make me afraid to review20:43
jbresnahi will take a look at them soon20:43
markwashI walk into those with some concerns as well20:43
jbresnahisnt flavio core on oslo now?20:44
markwashin light of a recent ML discussion, I think it makes sense to be very careful about oslo-incubated libraries until they're released on their own20:44
jbresnahlets make him do it :-P20:44
markwashbasically, it looks like the kind of refactorings that make me really happy don't happen until the oslo libs are released :-)20:44
jbresnahoh right, that brings up that one issue of adding an oslo aphpa to requirements20:44
jbresnahit seems to me that it makes sense to only use them after release20:45
markwashso I just want glance-core to keep in mind that its a totally viable strategy to adopt common code once its refactored and re-released. . we don't always have to be early adopters on oslo-incubator20:45
jbresnahan i really dont like the copy-code-in model20:45
markwashjbresnah: as a default, I agree, but I do think it makes sense to participate early sometimes20:45
markwashand it can save some effort20:45
jbresnahyeah i see that20:45
ameadethat code has to get used somewhere before it's a library20:45
jbresnahi am just giving all of my excuses as to why i am bad about oslo reviews20:46
markwashjbresnah: I checked on the oslo alpha dependency in the project meeting this past week20:46
ameadebut i agree20:46
markwashand its  apparently all good20:46
markwashjbresnah: I was doubly reassured by markmc that its not a problem at all20:46
markwashlets' talk client!20:46
markwash#topic glance-client20:46
*** openstack changes topic to "glance-client (Meeting topic: glance)"20:46
ameadei bugged one of our deployment guys and he said it shouldn't be an issue, esp since it's already in nova20:46
markwashameade: cool good to know!20:47
*** jrodom has joined #openstack-meeting-alt20:47
markwashthat fact probably translates to just about everybody else too, if its already in nova20:47
*** jrodom has quit IRC20:48
markwashI'd like to release a new client20:48
markwash0.11.020:48
markwashthis will pick up the PBR changes, which might mean packaging changes for some folks working on a fork20:48
jbresnahis create in the CLI for v2 yet?20:48
markwashjbresnah: there is a review for that20:49
esheffieldI have a patch for that20:49
jbresnahcool20:49
esheffieldhttps://review.openstack.org/#/c/4274120:49
jbresnahonce that is in i would love to see a release20:49
markwashjbresnah: I agree. . but it might be 0.12.020:49
markwashand then shortly after that, I'd love to release 1.0.020:49
jbresnahok20:49
ameademarkwash: but 1.0.0 means bugs actually count!20:50
markwashthis is something folks need to be thinking about, because its a rare opportunity to delete old stuff we don't want to support20:50
jbresnahif they can be done quick and easy then no sense waiting20:50
markwashameade: lol20:50
nikhilmarkwash: the packaging chanegs might not affect us (not 100% on this though)20:50
jbresnahheh ameade20:50
markwashso, things I know to be on the chopping block for 1.0.0 compatibility breaking20:50
jbresnahmarkwash: can we get ride of everything deprecated then?20:50
markwashjbresnah: +120:50
jbresnahnice20:50
markwashalso, the legacy shell20:50
ameadelets get rid of v120:50
ameadelol20:50
jbresnahheh20:50
icchait ll be good to get eyes on esheffield 's patch20:51
icchaesp with the way its dealing with schemas20:51
markwashiccha: I think this is the right opportunity to change the default # of results per list20:51
jbresnahiccha: I will do that for sure20:51
jbresnahiccha: i need to make the client reviews part of my day also20:51
esheffieldthe whole time I've been working on it I kept seeing stuff I wanted to delete ;-)20:51
nikhilmarkwash: not sure what you mean20:51
markwashnikhil: hmm. about what exactly?20:52
nikhildefault # results for list?20:52
nikhilhope that does not have to do with page size20:52
jbresnahi have to run a bit early20:52
ameadethat patch taht was reverted right?20:52
markwashnikhil: earlier, there was a change in glanceclient to go from 20 to 100 on the page size20:52
nikhilyes20:52
markwashand I thought that change would break backwards compatibliity, so I pulled it from the 0.10.0 release20:52
nikhiland we've a new patch up in nova20:52
markwashokay cool20:53
nikhilwhich will send it as a param to glance client20:53
markwashso maybe you're not worried about this anymore. . fine by me :-)20:53
icchabut still i think it ll be good to up the limit anyways20:53
nikhilmarkwash: yes, saw your ping on the channel and we noted it. thanks!20:53
nikhili thought it broke stuff for people20:53
nikhilif the release help then it's okay20:54
markwashagain, so the takeaway is just "Think about the things you want to see removed from glanceclient, because we get the chance to break (some) backwards compatibiity soon!"20:54
markwashto be clear, we need to keep the basic interfaces of the v1 and v2 client in place20:54
ameadedarn20:55
markwash:-)20:55
markwash#topic open discussion20:55
*** openstack changes topic to "open discussion (Meeting topic: glance)"20:55
markwashimportant bugs20:55
markwashhttps://review.openstack.org/#/c/40619/20:55
markwashhttps://review.openstack.org/#/c/42896/20:56
markwashthere might be others, but those are the high importance ones I see target to H-320:56
ameade3.5 pages on glance + glanceclient reviews....and this is esp my bad for not reviewing much lately20:56
*** jbresnah has quit IRC20:57
markwashits my bad as well20:57
markwashbut we have to consider stability important at this later stage20:57
nikhilwe might get help from some ghosts20:57
nikhilthink ameade knows what i mean20:57
markwashso if a review comes in with a feature change, at this point it might make sense to -2 defer to Icehouse20:58
markwashokay thanks everybody20:58
markwash#endmeeting20:58
*** openstack changes topic to "OpenStack meetings (alternate)"20:58
openstackMeeting ended Thu Aug 22 20:58:57 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-08-22-20.02.html20:59
zhiyanPoor fellow20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-08-22-20.02.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-08-22-20.02.log.html20:59
*** zhiyan has left #openstack-meeting-alt21:01
*** NikitaKonovalov has quit IRC21:04
*** cweid has quit IRC21:06
*** sarob_ has quit IRC21:08
*** sarob has joined #openstack-meeting-alt21:08
*** sarob_ has joined #openstack-meeting-alt21:12
*** sarob has quit IRC21:13
*** sarob_ has quit IRC21:13
*** sarob has joined #openstack-meeting-alt21:13
*** amytron has quit IRC21:14
*** vipul is now known as vipul-away21:22
*** boris-42 has quit IRC21:23
*** dina_belova has joined #openstack-meeting-alt21:25
*** dina_belova has quit IRC21:28
*** lpabon has quit IRC21:32
*** dina_belova has joined #openstack-meeting-alt21:35
*** dina_belova has quit IRC21:40
*** esker has quit IRC21:41
*** vipul-away is now known as vipul21:42
*** apecs has joined #openstack-meeting-alt21:42
*** alexpecoraro has quit IRC21:45
*** apecs is now known as alexpecoraro21:45
*** eankutse has quit IRC21:49
*** dmakogon_ has quit IRC21:54
*** NikitaKonovalov has joined #openstack-meeting-alt22:05
*** NikitaKonovalov has quit IRC22:10
*** amytron has joined #openstack-meeting-alt22:16
*** sacharya has quit IRC22:23
*** vkmc has quit IRC22:28
*** dina_belova has joined #openstack-meeting-alt22:36
*** dina_belova has quit IRC22:41
*** rnirmal has quit IRC23:03
*** notmyname has quit IRC23:04
*** notmyname has joined #openstack-meeting-alt23:04
*** NikitaKonovalov has joined #openstack-meeting-alt23:05
*** notmyname has quit IRC23:08
*** notmyname has joined #openstack-meeting-alt23:09
*** NikitaKonovalov has quit IRC23:10
*** gkleiman has quit IRC23:18
*** markwash has quit IRC23:19
*** amytron has quit IRC23:20
*** alexpecoraro has quit IRC23:21
*** jmontemayor has quit IRC23:23
*** alexpecoraro has joined #openstack-meeting-alt23:24
*** jmontemayor has joined #openstack-meeting-alt23:24
*** sacharya has joined #openstack-meeting-alt23:25
*** jmontemayor has quit IRC23:31
*** alexpecoraro has quit IRC23:31
*** alexpecoraro has joined #openstack-meeting-alt23:33
*** pdmars has quit IRC23:33
*** tanisdl has quit IRC23:34
*** dina_belova has joined #openstack-meeting-alt23:36
*** dina_belova has quit IRC23:41
*** jmontemayor has joined #openstack-meeting-alt23:42
*** jmontemayor has quit IRC23:42
*** jmontemayor has joined #openstack-meeting-alt23:44
*** jmontemayor has quit IRC23:57

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