Tuesday, 2016-02-09

*** ivar-lazzaro has quit IRC00:00
*** ivar-lazzaro has joined #openstack-meeting-300:00
*** doug-fish has joined #openstack-meeting-300:01
*** banix has joined #openstack-meeting-300:04
*** outofmemory is now known as reedip00:05
*** rpioso has quit IRC00:06
*** rpioso has joined #openstack-meeting-300:07
*** Swami has quit IRC00:18
*** Swami has joined #openstack-meeting-300:18
*** armax has quit IRC00:19
*** armax_ has joined #openstack-meeting-300:19
*** tej has joined #openstack-meeting-300:20
*** doug-fish has quit IRC00:22
*** doug-fish has joined #openstack-meeting-300:24
*** doug-fish has quit IRC00:25
*** rpioso has quit IRC00:26
*** doug-fish has joined #openstack-meeting-300:26
*** doug-fish has quit IRC00:27
*** doug-fish has joined #openstack-meeting-300:30
*** bpokorny_ has quit IRC00:33
*** bpokorny has joined #openstack-meeting-300:33
*** jwang has quit IRC00:39
*** jwang_ has joined #openstack-meeting-300:39
*** doug-fish has quit IRC00:40
*** jwang_ has quit IRC00:43
*** ajmiller has quit IRC00:44
*** doug-fish has joined #openstack-meeting-300:45
*** jwang has joined #openstack-meeting-300:49
*** jwang_ has joined #openstack-meeting-300:53
*** jwang has quit IRC00:53
*** vahidh has joined #openstack-meeting-300:57
*** tej has quit IRC00:57
*** chaustin has joined #openstack-meeting-301:01
*** vahidh has quit IRC01:02
*** chaustin has quit IRC01:06
*** chaustin_ has joined #openstack-meeting-301:06
*** banix has quit IRC01:07
*** FallenPegasus has joined #openstack-meeting-301:07
*** chaustin_ has quit IRC01:11
*** doug-fish has quit IRC01:13
*** banix has joined #openstack-meeting-301:15
*** chaustin has joined #openstack-meeting-301:15
*** stanzgy_ has joined #openstack-meeting-301:16
*** stanzgy has quit IRC01:18
*** banix has quit IRC01:20
*** banix has joined #openstack-meeting-301:20
*** Sukhdev has quit IRC01:20
*** Aish has quit IRC01:24
*** banix has quit IRC01:24
*** banix has joined #openstack-meeting-301:24
*** Aish has joined #openstack-meeting-301:24
*** chaustin has left #openstack-meeting-301:25
*** Aish has quit IRC01:26
*** banix has quit IRC01:31
*** mtanino has quit IRC01:34
*** Sukhdev has joined #openstack-meeting-301:35
*** FallenPegasus has quit IRC01:36
*** tfukushima has joined #openstack-meeting-301:39
*** tfukushima has quit IRC01:42
*** FallenPegasus has joined #openstack-meeting-301:45
*** Sukhdev has quit IRC01:51
*** tfukushima has joined #openstack-meeting-301:54
*** cloudtrainme has joined #openstack-meeting-301:57
*** sc68cal has quit IRC01:57
*** chaustin has joined #openstack-meeting-301:58
*** yamamoto has joined #openstack-meeting-301:59
*** cloudtrainme has quit IRC01:59
*** chaustin has quit IRC02:00
*** chaustin has joined #openstack-meeting-302:00
*** cloudtrainme has joined #openstack-meeting-302:00
*** banix has joined #openstack-meeting-302:07
*** tfukushima has quit IRC02:13
*** doug-fish has joined #openstack-meeting-302:14
*** Swami has quit IRC02:16
*** banix has quit IRC02:18
*** banix has joined #openstack-meeting-302:19
*** banix has quit IRC02:19
*** doug-fish has quit IRC02:19
*** tfukushima has joined #openstack-meeting-302:22
*** cloudtrainme has quit IRC02:23
*** yamamoto has quit IRC02:24
*** doug-fish has joined #openstack-meeting-302:25
*** mrunge has quit IRC02:29
*** bpokorny_ has joined #openstack-meeting-302:30
*** bpokorny_ has quit IRC02:31
*** bpokorny has quit IRC02:33
*** mrunge has joined #openstack-meeting-302:36
*** chaustin has joined #openstack-meeting-302:38
*** chaustin has quit IRC02:43
*** s3wong has quit IRC02:44
*** doug-fish has quit IRC02:45
*** doug-fish has joined #openstack-meeting-302:46
*** fawadkhaliq has joined #openstack-meeting-302:47
*** doug-fish has quit IRC02:50
*** armax_ is now known as armax02:54
*** shwetaap has joined #openstack-meeting-302:55
*** sdake has joined #openstack-meeting-302:55
*** sdake_ has joined #openstack-meeting-303:00
*** sdake has quit IRC03:03
*** ivar-laz_ has joined #openstack-meeting-303:03
*** tellesnobrega is now known as tellesnobrega_af03:04
*** ivar-lazzaro has quit IRC03:06
*** ivar-laz_ has quit IRC03:08
*** yamamoto has joined #openstack-meeting-303:12
*** lblanchard has quit IRC03:26
*** dims has joined #openstack-meeting-303:27
*** dims_ has quit IRC03:28
*** dims has quit IRC03:30
*** FallenPegasus has quit IRC03:32
*** doug-fish has joined #openstack-meeting-303:32
*** ajmiller has joined #openstack-meeting-303:34
*** FallenPegasus has joined #openstack-meeting-303:34
*** ajmiller has quit IRC03:37
*** dims has joined #openstack-meeting-303:43
*** dims has quit IRC03:47
*** Poornima has joined #openstack-meeting-303:50
*** doug-fish has quit IRC03:56
*** doug-fish has joined #openstack-meeting-303:56
*** doug-fish has quit IRC03:57
*** doug-fis_ has joined #openstack-meeting-304:00
*** doug-fis_ has quit IRC04:04
*** doug-fish has joined #openstack-meeting-304:09
*** bpokorny has joined #openstack-meeting-304:09
*** baoli_ has quit IRC04:11
*** armax_ has joined #openstack-meeting-304:18
*** armax has quit IRC04:21
*** armax_ is now known as armax04:21
*** tfukushima has quit IRC04:24
*** mrmartin has joined #openstack-meeting-304:38
*** salv-orl_ has joined #openstack-meeting-304:41
*** fawadkhaliq has quit IRC04:42
*** salv-orlando has quit IRC04:43
*** Sukhdev has joined #openstack-meeting-304:57
*** amotoki has joined #openstack-meeting-305:07
*** hichihara has joined #openstack-meeting-305:07
*** amotoki_ has joined #openstack-meeting-305:09
*** amotoki has quit IRC05:12
*** fawadkhaliq has joined #openstack-meeting-305:14
*** fawadkhaliq has joined #openstack-meeting-305:14
*** amotoki_ has quit IRC05:15
*** tfukushima has joined #openstack-meeting-305:25
*** mrmartin has quit IRC05:30
*** tfukushima has quit IRC05:30
*** tfukushima has joined #openstack-meeting-305:32
*** irenab has quit IRC05:36
*** yushiro has joined #openstack-meeting-305:37
*** yushiro has left #openstack-meeting-305:37
*** vahidh has joined #openstack-meeting-305:46
*** doug-fish has quit IRC05:48
*** NobodyCam has quit IRC05:48
*** amotoki has joined #openstack-meeting-305:49
*** vahidh has quit IRC05:51
*** mrmartin has joined #openstack-meeting-305:55
*** doug-fish has joined #openstack-meeting-305:55
*** Poornima has quit IRC05:56
*** Poornima has joined #openstack-meeting-306:00
*** tej has joined #openstack-meeting-306:02
*** tej has quit IRC06:07
*** doug-fish has quit IRC06:08
*** Poornima has quit IRC06:08
*** sgordon has quit IRC06:09
*** sgordon has joined #openstack-meeting-306:11
*** bpokorny has quit IRC06:12
*** Poornima has joined #openstack-meeting-306:13
*** Poornima has joined #openstack-meeting-306:14
*** irenab has joined #openstack-meeting-306:15
*** numans has joined #openstack-meeting-306:19
*** hdaniel has joined #openstack-meeting-306:40
*** mrmartin has quit IRC06:42
*** shwetaap1 has joined #openstack-meeting-306:48
*** armax has quit IRC06:49
*** hichihara has quit IRC06:49
*** shwetaap has quit IRC06:51
*** amotoki has quit IRC06:56
*** amotoki has joined #openstack-meeting-306:58
*** sdake_ has quit IRC07:00
*** sdake has joined #openstack-meeting-307:01
*** sdake has quit IRC07:03
*** nkrinner has joined #openstack-meeting-307:03
*** Sukhdev has quit IRC07:19
*** hdaniel has quit IRC07:24
*** evgenyf has joined #openstack-meeting-307:37
*** jtomasek__ has quit IRC07:38
*** doug-fish has joined #openstack-meeting-307:38
*** belmoreira has joined #openstack-meeting-307:41
*** doug-fis_ has joined #openstack-meeting-307:42
*** doug-fish has quit IRC07:43
*** doug-fis_ has quit IRC07:47
*** shwetaap1 has quit IRC07:56
*** reed_ has quit IRC07:59
*** reed_ has joined #openstack-meeting-308:00
*** reed_ has quit IRC08:01
*** tej has joined #openstack-meeting-308:03
*** tej has quit IRC08:09
*** mrmartin has joined #openstack-meeting-308:21
*** mkovacik has joined #openstack-meeting-308:24
*** jlanoux has joined #openstack-meeting-308:27
*** tfukushima has quit IRC08:28
*** tfukushima has joined #openstack-meeting-308:30
*** matrohon has joined #openstack-meeting-308:31
*** pattdepanick has joined #openstack-meeting-308:34
*** zz_dimtruck is now known as dimtruck08:37
*** pattdepanick has left #openstack-meeting-308:45
*** e0ne has joined #openstack-meeting-308:49
*** dimtruck is now known as zz_dimtruck08:51
*** egallen has joined #openstack-meeting-308:56
*** hdaniel has joined #openstack-meeting-308:59
*** mbound has joined #openstack-meeting-308:59
*** safchain has joined #openstack-meeting-309:00
*** egallen has quit IRC09:05
*** egallen has joined #openstack-meeting-309:13
*** egallen has quit IRC09:15
*** e0ne has quit IRC09:19
*** ihrachys has joined #openstack-meeting-309:19
*** iyamahat has joined #openstack-meeting-309:19
*** iyamahat has quit IRC09:25
*** kzaitsev_mb has joined #openstack-meeting-309:31
*** egallen has joined #openstack-meeting-309:35
*** rossella_s has joined #openstack-meeting-309:35
*** egallen has quit IRC09:39
*** egallen has joined #openstack-meeting-309:40
*** davidsha has joined #openstack-meeting-309:46
*** fawadkhaliq has quit IRC09:47
*** mbound has quit IRC09:47
*** fawadkhaliq has joined #openstack-meeting-309:47
*** egallen has quit IRC09:50
*** kzaitsev_mb has quit IRC09:53
*** egallen has joined #openstack-meeting-309:54
*** mbound has joined #openstack-meeting-309:55
*** fawadkhaliq has quit IRC10:01
*** egallen has quit IRC10:02
*** itxaka has joined #openstack-meeting-310:04
*** tej has joined #openstack-meeting-310:05
*** tej has quit IRC10:09
*** jtomasek has joined #openstack-meeting-310:11
*** e0ne has joined #openstack-meeting-310:21
*** FallenPegasus has quit IRC10:22
*** FallenPegasus has joined #openstack-meeting-310:28
*** deva_ has joined #openstack-meeting-310:30
*** NobodyCa1 has joined #openstack-meeting-310:33
*** amotoki has quit IRC10:34
*** NobodyCa1 has quit IRC10:38
*** deva_ has quit IRC10:38
*** salv-orlando has joined #openstack-meeting-310:40
*** tfukushima has quit IRC10:42
*** salv-orl_ has quit IRC10:43
*** neiljerram has joined #openstack-meeting-310:44
*** dims has joined #openstack-meeting-310:45
*** dims has quit IRC10:49
*** amotoki has joined #openstack-meeting-310:49
*** dims has joined #openstack-meeting-310:50
*** fawadkhaliq has joined #openstack-meeting-310:50
*** amotoki has quit IRC10:55
*** kzaitsev_mb has joined #openstack-meeting-310:56
*** neiljerram has quit IRC11:02
*** mbound has quit IRC11:02
*** neiljerram has joined #openstack-meeting-311:03
*** yamamoto has quit IRC11:05
*** mbound has joined #openstack-meeting-311:15
*** wojdev has joined #openstack-meeting-311:18
*** wojdev has left #openstack-meeting-311:19
*** fawadkhaliq has quit IRC11:19
*** fawadkhaliq has joined #openstack-meeting-311:19
*** fawadkhaliq has quit IRC11:19
*** fawadkhaliq has joined #openstack-meeting-311:20
*** ihrachys has quit IRC11:20
*** FallenPegasus has quit IRC11:20
*** evgenyf has quit IRC11:24
*** baoli has joined #openstack-meeting-311:36
*** baoli has quit IRC11:37
*** dims_ has joined #openstack-meeting-311:40
*** dims has quit IRC11:40
*** FallenPegasus has joined #openstack-meeting-311:42
*** FallenPegasus has quit IRC11:43
*** yamamoto has joined #openstack-meeting-311:51
*** kzaitsev_mb has quit IRC11:55
*** FallenPegasus has joined #openstack-meeting-312:02
*** FallenPegasus has quit IRC12:07
*** wojdev has joined #openstack-meeting-312:09
*** ihrachys has joined #openstack-meeting-312:10
*** wojdev has quit IRC12:10
*** dims_ has quit IRC12:11
*** davidsha has quit IRC12:11
*** Poornima has quit IRC12:15
*** evgenyf has joined #openstack-meeting-312:17
*** dims_ has joined #openstack-meeting-312:19
*** rtheis has joined #openstack-meeting-312:23
*** mrmartin has quit IRC12:23
*** kzaitsev_mb has joined #openstack-meeting-312:24
*** mtanino has joined #openstack-meeting-312:28
*** fawadkhaliq has quit IRC12:43
*** doug-fish has joined #openstack-meeting-312:45
*** yamamoto has quit IRC12:46
*** doug-fish has quit IRC12:47
*** doug-fish has joined #openstack-meeting-312:48
*** jpomeroy has joined #openstack-meeting-312:57
*** numans has quit IRC13:02
*** yamamoto has joined #openstack-meeting-313:03
*** woodster_ has quit IRC13:06
*** yamamoto has quit IRC13:16
*** sdake has joined #openstack-meeting-313:19
*** sdake_ has joined #openstack-meeting-313:21
*** dedery has joined #openstack-meeting-313:21
*** fawadkhaliq has joined #openstack-meeting-313:22
*** dedery_ has joined #openstack-meeting-313:22
*** yamamoto has joined #openstack-meeting-313:23
*** sdake has quit IRC13:24
*** sdake_ is now known as sdake13:24
*** jlanoux has quit IRC13:24
*** jlanoux has joined #openstack-meeting-313:25
*** tellesnobrega_af is now known as tellesnobrega13:25
*** dedery has quit IRC13:25
*** dedery_ is now known as dedery13:25
*** tej has joined #openstack-meeting-313:28
*** numans has joined #openstack-meeting-313:29
*** paul-carlton2 has joined #openstack-meeting-313:33
*** numans has quit IRC13:34
*** chaustin has joined #openstack-meeting-313:37
*** nelsnels_ has joined #openstack-meeting-313:37
*** nelsnelson has quit IRC13:37
*** ihrachys has quit IRC13:40
*** sdake has quit IRC13:40
*** chaustin has quit IRC13:41
*** sdake has joined #openstack-meeting-313:41
*** jlanoux has quit IRC13:43
*** jlanoux has joined #openstack-meeting-313:43
*** chaustin has joined #openstack-meeting-313:47
*** sdake has quit IRC13:48
*** sdake has joined #openstack-meeting-313:49
*** tdurakov has joined #openstack-meeting-313:51
*** cbouch has joined #openstack-meeting-313:51
*** PaulMurray has joined #openstack-meeting-313:56
*** vgridnev has joined #openstack-meeting-314:00
*** andrearosa has joined #openstack-meeting-314:00
PaulMurray#startmeeting Nova Live Migration14:01
openstackMeeting started Tue Feb  9 14:01:05 2016 UTC and is due to finish in 60 minutes.  The chair is PaulMurray. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: Nova Live Migration)"14:01
openstackThe meeting name has been set to 'nova_live_migration'14:01
PaulMurrayhi - who is here?14:01
*** rdopiera has joined #openstack-meeting-314:01
PaulMurraythe agenda is here: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration14:02
*** rossella_s has quit IRC14:02
*** dims_ has quit IRC14:03
PaulMurray#topic Next meeting14:03
*** openstack changes topic to "Next meeting (Meeting topic: Nova Live Migration)"14:03
PaulMurrayI will not be here next week14:03
*** rossella_s has joined #openstack-meeting-314:03
PaulMurrayis there someone willing to be chair for the meeting on 16th Feb?14:03
*** tej has quit IRC14:03
tdurakovI could14:03
PaulMurraythank you - I will put you down14:04
PaulMurray#info tdurakov to chair meeting on 16th Feb14:04
PaulMurraygreat, that's sorted14:04
pkoniszewskiin case there are some troubles I will also be able to cover14:04
tdurakovcool, will ping you if any happens14:04
PaulMurrayok - thanks pkoniszewski14:04
PaulMurray#topic Priority reviews14:04
*** openstack changes topic to "Priority reviews (Meeting topic: Nova Live Migration)"14:04
PaulMurraythe feature freeze is three weeks away I think14:05
PaulMurraybut we are starting to get some movement14:05
PaulMurraysplit-network-plane-for-live-migration is complete14:05
PaulMurraypause-vm-during-live-migration only needs +W on last patch14:05
pkoniszewskipausing needs API approval14:06
PaulMurrayabort-live-migration has started to get some patches up (well, one)14:06
andrearosa...yet but I am working on the big one14:06
PaulMurraypkoniszewski, mikal asked for alex_xu or similar to approve - I think it will be done pretty soon14:07
*** mtanino has quit IRC14:07
PaulMurrayblock-live-migrate-with-attached-volumes is making good progress14:07
PaulMurraydan +2 first patch14:08
PaulMurrayI think pkoniszewski is going to update second14:08
PaulMurraypkoniszewski, ?14:08
*** dandruta has joined #openstack-meeting-314:08
PaulMurray#link https://review.openstack.org/#/c/234659 - needs minor revision14:08
pkoniszewskiso I'm working actually on second patch as I'm not sure that there is an issue14:09
PaulMurrayis that the one ^^14:09
pkoniszewskiI'm sure that we want to skip config drive ISO because destination host will try to write to readonly device which is not a good idea at all14:09
pkoniszewskinow I'm checking what happens if other readonly device is attached to VM14:10
*** sdake has quit IRC14:10
pkoniszewskiwhich is not config drive14:10
*** dims has joined #openstack-meeting-314:10
PaulMurrayhmmm, did no one think of that?14:10
PaulMurraywe used to migrate the config drive in HP14:10
PaulMurrayI think we did it differently though - paul-carlton2 can you remember?14:11
tdurakovPaulMurray, was it block-migrate?14:11
*** neiljerram has quit IRC14:11
PaulMurraytdurakov, that's what I am trying to remember14:11
paul-carlton2We copied config drive over rcp14:11
tdurakovprior to migration?14:11
PaulMurrayright, which we don't want to do14:12
paul-carlton2same for rescue libvirt xml14:12
paul-carlton2nope, not the upstream way forward14:12
*** numans has joined #openstack-meeting-314:12
PaulMurrayI thought qemu could handle fat config drives ? so it must have worked at some point ?14:13
pkoniszewskiwell, config drive works fine14:13
pkoniszewskiin current implementation14:13
paul-carlton2ah, now I recall, we made config drives vfat which copied ok14:13
pkoniszewskiright, they are not readonly14:14
PaulMurrayI see14:14
tdurakovpaul-carlton2, they works fine14:14
*** baoli has joined #openstack-meeting-314:14
paul-carlton2Yep we got it to work, but using a local patch14:14
paul-carlton2I think14:14
paul-carlton2can't libvirt copy config drives14:15
tdurakovafair vfat works in upstream well too for block-migrate14:15
PaulMurraypkoniszewski, so just to check - vfat config drives already migrate - its only the iso format that is blocked14:15
tdurakovso the issue affects only iso960014:15
PaulMurraythat's why that readonly conditional was there14:15
PaulMurraythe one danpb commented on14:16
paul-carlton2surely at libvirt/qemu  level it should be able to copy any disk device it is told to14:16
paul-carlton2otherwise a readonly device could not be created?14:16
PaulMurrayqemu doesn't create it14:17
*** baoli_ has joined #openstack-meeting-314:17
*** lblanchard has joined #openstack-meeting-314:17
PaulMurraypkoniszewski, what did it mean when iso9600 support was added14:18
pkoniszewskilet me find libvirt release note for this14:18
PaulMurrayok - lets move this discussion to the patch and move on14:18
PaulMurrayor we wont finish the meeting14:18
PaulMurraythe next spec was live-migration-progress-report14:19
*** oetrog has joined #openstack-meeting-314:19
PaulMurraydid this ML thread resolve the write to db question?14:19
pkoniszewskii think so14:20
*** oetrog is now known as omer_etrog14:20
PaulMurrayI wasn't sure if there was an actual conclusion14:20
*** numans has quit IRC14:20
*** baoli has quit IRC14:20
tdurakovheh, I'd prefer to do this reporting online instead of db writes)14:20
pkoniszewskiI think that we will be able to change this once migration progress is saved on compute side14:21
*** yamahata has joined #openstack-meeting-314:21
*** peristeri has joined #openstack-meeting-314:21
*** peristeri has quit IRC14:21
johnthetubaguywhat do you mean by "saved on the compute side"?14:21
*** amotoki has joined #openstack-meeting-314:21
paul-carlton2tdurakov, I disagree the compute process should update db and api calls should get it form there14:22
*** numans has joined #openstack-meeting-314:22
*** vhoward has joined #openstack-meeting-314:22
*** NobodyCa1 has joined #openstack-meeting-314:22
tdurakovjohnthetubaguy,  it's about conductor and compute communication refactoring,  i believe14:22
paul-carlton2that is how it is done everywhere in openstack, certainly in nova14:22
pkoniszewskijohnthetubaguy: during midcycle Nikola had some concerns that in case that compute dies it will need to have data saved locally14:22
pkoniszewskijohnthetubaguy: to recover migration process/cleanup/whatever14:22
johnthetubaguyyes, thats in addition, not instead of14:23
paul-carlton2That is a separate issue to the progress reporting14:23
pkoniszewskithought we can use it for reporting progress online14:23
johnthetubaguyanyways, I think we should keep the nova architecture the same here, at least until we find a real issue folks are hitting14:23
mdboothLong term, the db doesn't seem like the best place for this. If the compute is eventually going to have this information, api can directly query the compute because it has an rpc address.14:23
johnthetubaguypkoniszewski: in summary, we can't, the API reads from the DB only14:23
*** evgenyf has quit IRC14:24
pkoniszewskijohnthetubaguy: got it14:24
johnthetubaguyyeah, lets no go there for now14:24
*** chaustin has quit IRC14:24
pkoniszewskithat's reasonable, i'd stick to writing progress every 5 seconds14:24
tdurakovok, let's move on then14:24
pkoniszewskibut current implementation does not reset it anywhere14:24
pkoniszewskiso i have completed migrations with disk and memory to be transferred, which is weird14:25
johnthetubaguythe API shouldn't be showing progress info for not in progress things, so I am not sure its a big issue14:25
pkoniszewskiwell, currently it can show that VM is paused with a progress of 92%14:26
rdopierajohnthetubaguy: how about for things that were interrupted?14:26
PaulMurraya migration should be running, completed, cancelled or in error - only one of those needs progress report ?14:27
PaulMurrayI'd count paused as running14:27
johnthetubaguyrdopiera: same, once the interruption is spotted, but really I just mean we can clean up that stuff later14:27
johnthetubaguyPaulMurray: that sounds correct14:28
rdopierajohnthetubaguy: it could be useful to know where it finished for cleaning up14:28
johnthetubaguyrdopiera: maybe14:28
rdopierajohnthetubaguy: where it was interrupted, I mean14:28
pkoniszewskirdopiera: +114:28
PaulMurrayrdopiera, isn't that covered by its state?14:28
paul-carlton2the current monitor code dan write calculates the progress every 5 seconds so it will be updated14:28
johnthetubaguyPaulMurray: non-zero progress is in interesting data point though14:28
rdopieraPaulMurray: the state is very large grained14:28
*** stendulker has joined #openstack-meeting-314:29
paul-carlton2progress should be reset to zero when migration ends, be it good or bad outcome14:29
*** NobodyCa1 has quit IRC14:29
johnthetubaguypaul-carlton2: sure, but the API should not report any progress unless its running, so its a nit really14:30
PaulMurrayjohnthetubaguy, pkoniszewski so I think we concluded to write every 5 seconds14:30
*** cloudtrainme has joined #openstack-meeting-314:30
PaulMurraylets move on14:31
paul-carlton2The api as in nova show reports progress all the time14:31
PaulMurrayI mentioned auto-converge on the agenda14:31
*** omer_etrog has quit IRC14:31
paul-carlton2could be zero, should be zero unless live mig or snapshot in progress14:31
PaulMurraybut I think that is out of scope because it didn't have an approved spec14:31
*** amotoki has quit IRC14:31
*** omer_etrog has joined #openstack-meeting-314:32
pkoniszewskiPaulMurray: and it needs newer libvirt, even for a config flag, so let's skip it14:32
PaulMurraypkoniszewski, right, it was on the priority reviews pad so I'm going to remove it14:32
PaulMurrayjust got confused14:32
*** omer_etrog has quit IRC14:32
pkoniszewskisure, go ahead, i forgot to remove it14:32
PaulMurray#topic Bugs14:32
*** openstack changes topic to "Bugs (Meeting topic: Nova Live Migration)"14:32
*** yamamoto has quit IRC14:32
paul-carlton2if we are referring to the new data counters they should be left as is on completion since it may be useful to se how far it got when it stopped/completed and how much data it copied14:33
PaulMurraypaul-carlton2, we've moved on14:33
johnthetubaguypaul-carlton2: yeah, thats what I mean API returns zero if not in progress, regardless of DB, but yeah, lets move on14:33
*** yamamoto has joined #openstack-meeting-314:33
PaulMurraythere are 4 new bugs for triage14:34
PaulMurrayI don't know who is doing the triage but well done to them :)14:34
PaulMurrayI moved some of the bug patches around in the priorities pad14:34
PaulMurraybecause several were stale14:34
*** cloudtrainme has quit IRC14:34
PaulMurraythe rest have had some review and updates recently14:35
*** amotoki has joined #openstack-meeting-314:35
*** omer_etrog has joined #openstack-meeting-314:35
PaulMurrayDoes anyone have any questions ?14:35
PaulMurrayjohnthetubaguy, do you have any comments on bugs - we don't do a great job of turning those over14:36
tdurakov about this one: https://bugs.launchpad.net/nova/+bug/1526642  - it's possible to break anti-affinity rules by providing dest host, right?14:36
openstackLaunchpad bug 1526642 in OpenStack Compute (nova) "Simultaneous live migrations break anti-affinity policy" [Undecided,New]14:36
johnthetubaguyPaulMurray: only that once reviews are ready, lets get them in that etherpad, like the other patches14:36
pkoniszewskitdurakov: no, scheduler breaks anti-affinity policy14:36
mdboothbauzas: ^^^14:36
johnthetubaguyPaulMurray: having a set of stuff you want in mitaka would be no bad thing14:36
pkoniszewskitdurakov: in case of parallel scheduling it might cause rescheduling and instances are spawned on the same host14:36
PaulMurrayanti-affinity is checked for boot14:36
PaulMurrayin claims code14:37
PaulMurrayso if you get a claim you got anti-affinity14:37
PaulMurrayits easier than affinity14:37
johnthetubaguyPaulMurray: there were a heap of buts in the tracker that seemed to be fixed by upcoming blueprints, those are working commenting on, any maybe changing the status somehow14:37
*** amotoki has quit IRC14:37
tdurakovpkoniszewski, if you got aa policy and manually pick up dest node that breaks rules?14:37
pkoniszewskitdurakov: if you force, yes14:37
*** tej has joined #openstack-meeting-314:37
PaulMurrayI think force is allowed to break rules14:37
*** yamamoto has quit IRC14:37
PaulMurrayit overrides14:37
johnthetubaguyyes, thinking about migrating one host to a new host14:38
PaulMurraythere will be a check destinations coming14:38
tdurakovyep, it doesn't asks scheduler14:38
johnthetubaguyyou need to move each VM one by one14:38
*** sdake has joined #openstack-meeting-314:38
johnthetubaguyso you actually have to break affinity = true rules while you do the move14:38
* johnthetubaguy mutters something about great power and great responsibility14:38
* bauzas lurks14:38
PaulMurrayjohnthetubaguy, yes, true - I was thinking about that the other day14:38
PaulMurrayonly moving whole host to whole host works for these kind of policies14:39
mdboothbauzas: Discussion was around anti-affinity during live-migration https://bugs.launchpad.net/nova/+bug/152664214:39
openstackLaunchpad bug 1526642 in OpenStack Compute (nova) "Simultaneous live migrations break anti-affinity policy" [Undecided,New]14:39
johnthetubaguynow eventually, we could do some fancy stuff to work around that, but lets just get it working first14:39
bauzasso, server groups is checked in a semaphore in the compute manager AFAIR14:39
bauzasactually, I wrote that in Kilo14:39
PaulMurraybauzas, yes, in claims14:39
bauzasPaulMurray: probably, I don't remember in which caller I made that14:40
johnthetubaguybauzas: force needs to break these rules quite a few times, and thats the idea, basically14:40
pkoniszewskijohnthetubaguy: it breaks rules even without force14:40
*** amotoki has joined #openstack-meeting-314:41
*** amotoki has quit IRC14:41
tdurakovsame for affinity rules14:41
bauzasit would add another level of verification14:41
bauzasbut fair14:41
bauzasfor the moment, we don't provide the Spec object to the compute manager14:41
bauzasso, there is no way for it to know whether it was forced or not14:42
bauzasI'm discussing about a non-implemented BP14:42
PaulMurraywe can look at this more later14:42
PaulMurrayanything else on bugs?14:43
PaulMurray#topic open discussion14:43
*** openstack changes topic to "open discussion (Meeting topic: Nova Live Migration)"14:43
PaulMurraythe floor is open for anything else?14:43
PaulMurrayI noticed there is movement14:44
mdboothLibvirt storage pools isn't going to happen by the end of the month14:44
PaulMurrayon ploop support for storage groups in libvirt14:44
PaulMurrayer, storage pools14:44
*** zz_dimtruck is now known as dimtruck14:44
mdboothI talked to paul-carlton2 the other day, and there's basically 1 preparatory patch I'd like to get in Mitaka14:44
mdboothWhich would make it easier to migrate between backend storage schemes in Newton14:45
PaulMurraydo you have a link yet?14:45
PaulMurrayor is it coming14:45
mdboothI haven't written it, yet, because I was trying to get there in order. However, I may bodge something out of order for expediency.14:45
PaulMurraywe have less than 3 weeks I think14:46
mdboothBasically, we have a file, disk.info, which currently stores information about which file format a particular disk is using.14:46
mdboothI want to change it to be able to store more than that14:46
mdboothFor example, which backend it's using.14:46
*** stendulker has quit IRC14:46
mdboothHowever, the file is on shared storage14:46
mdboothSo it needs to be able to co-exist with N-114:47
mdboothI'd like to change the parser in M to understand the format I intend to use in N14:47
mdboothAnd not barf14:47
johnthetubaguypkoniszewski: today, yes I think it does break that, thats what bauzas's blueprint is trying to fix14:47
*** omer_etrog has quit IRC14:47
mdboothIn the meantime, I will continue trying to get there more cleanly.14:48
johnthetubaguymdbooth: why not start reporting the new stuff now, but only use the new data later?14:48
*** omer_etrog has joined #openstack-meeting-314:48
mdboothjohnthetubaguy: It's a JSON file mapping disk -> format14:48
mdboothI want it to map disk -> {lots: of, new: things}14:48
*** julim_ has quit IRC14:49
mdboothAlso, if I changed the format now, it would break compatibility with Liberty14:49
johnthetubaguymdbooth: oh, I see, you need to reader to support both before you use both14:49
mdboothIf Liberty and Mitaka computes are on the same shared storage14:49
johnthetubaguymdbooth: thats testable quite easily, so that should be OK14:49
johnthetubaguymdbooth: or just add an additional file? and eventually delete the old one, but that does seem wasteful14:50
johnthetubaguydon't want to hit filesystem limits because of that14:50
mdboothI hoped at one point that the file was redundant, but it turns out it's not14:50
mdboothSo I figured I'd just co-opt it14:51
mdboothAlso, it already took the best name ;)14:51
*** amit213 has quit IRC14:51
*** fawadkhaliq has quit IRC14:52
*** omer_etrog has quit IRC14:52
PaulMurraymdbooth, when you've figured out what you need to land in mitaka you can let us know and we will try and push it14:53
*** neiljerram has joined #openstack-meeting-314:53
mdboothPaulMurray: Sure.14:53
*** mtanino has joined #openstack-meeting-314:54
PaulMurraymdbooth, thanks14:54
PaulMurrayanything else?14:54
*** paul-carlton has joined #openstack-meeting-314:54
mdboothPaulMurray: Amongst other things, it will allow us to know which instances have been moved from the legacy scheme to libvirt storage pools.14:54
PaulMurraymdbooth, are you going to negotiate that between hosts or does it end up in the db?14:55
PaulMurraywhen it comes to a migration I mean?14:56
mdboothIt's on disk on the compute.14:56
*** cbouch_ has joined #openstack-meeting-314:56
*** rbak has joined #openstack-meeting-314:56
mdboothIt uses instance storage, which makes most sense.14:56
mdboothThe other advantage of using the existing file, is that current code should expect it to exist.14:57
mdboothSo fewer dependent changes.14:57
PaulMurrayI get it,14:57
* mdbooth assumes this file would be copied over during non-shared storage migration, for eg14:57
PaulMurraywe're coming to the end of the meeting now14:58
paul-carltonsurely it would be created by the dest compute node, not copied?14:58
PaulMurraytdurakov, or pkoniszewski if anything goes wrong for tdurakov14:59
*** cbouch has quit IRC14:59
mdboothpaul-carlton: Wouldn't surprise me, but that would be a bug.14:59
PaulMurraywill chair next meeting ^^14:59
PaulMurraywe have to close14:59
PaulMurraybye all - and thanks for coming14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Tue Feb  9 14:59:34 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_live_migration/2016/nova_live_migration.2016-02-09-14.01.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_live_migration/2016/nova_live_migration.2016-02-09-14.01.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_live_migration/2016/nova_live_migration.2016-02-09-14.01.log.html14:59
*** andrearosa has left #openstack-meeting-314:59
*** mriedem has joined #openstack-meeting-315:00
mriedem#startmeeting stable15:00
openstackMeeting started Tue Feb  9 15:00:22 2016 UTC and is due to finish in 60 minutes.  The chair is mriedem. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: stable)"15:00
openstackThe meeting name has been set to 'stable'15:00
mriedemwill wait a few minutes for people to show up15:00
*** dimtruck is now known as zz_dimtruck15:02
mriedemtonyb: mtreinish: around?15:02
mriedemmrunge: ?15:02
mrungehey o/15:03
mrungesorry for being late15:03
mriedemnp, we might as well get started15:03
mriedemfirst, i want to thank tonyb for chairing last week while i was out15:03
mriedem#topic status15:03
*** openstack changes topic to "status (Meeting topic: stable)"15:03
mriedemi was following along with the testtools flare up on kilo15:03
mriedemthat's mostly under control as of late last week15:04
mriedem#link issues https://etherpad.openstack.org/p/stable-tracker15:04
mriedemi don't think there is anything new in there really, trove has some problems which people are working on15:04
mriedemtonyb was helping sahara getting their tests running in kilo15:04
bknudson_keystone was also failing -- https://review.openstack.org/#/c/277022/15:05
mriedemoh for testtools?15:05
*** irenab has quit IRC15:05
bknudson_I don't think it was because of testtools, but because of a change in infra master15:06
mriedemok so i guess we're just waiting for jenkins there15:06
*** jmckind has joined #openstack-meeting-315:06
bknudson_y, I'll see if it works15:06
mriedemwere there any other known stable branch issues?15:06
bknudson_I proposed a change to project-config -- https://review.openstack.org/#/c/277550/15:06
*** yamamoto has joined #openstack-meeting-315:07
*** sigmavirus24_awa is now known as sigmavirus2415:07
mriedem#status action items from previous meeting(s)15:07
mriedemmrunge to followup with dhellman re horizon release email15:07
mrungemriedem, I just missed the email15:08
mriedemmrunge: did that happen?15:08
mriedemah, ok15:08
mrungemriedem, there was a automatic email15:08
mriedemyeah this http://lists.openstack.org/pipermail/openstack-announce/2016-January/000944.html15:08
mriedemtonyb check how glance drivers compares to gerrit cores and nagg flaper87 to sync them ;P15:09
mrungebut this mail is basically wrong15:09
mriedemflaper87: are you around?15:09
mrungelast horizon version on pypi is 2012.215:09
mriedemmrunge: yeah i saw that15:09
mrungeand it was released there by accident15:09
mriedemmrunge: was a bug reported to follow up on that? i saw apavec had a post to the -dev list15:09
mrungemriedem, unfortunately, I didn't had the time to report a bug or follow up there15:10
mrungewould you make it an action item for me then?15:10
mriedem#action follow up on server projects (e.g. horizon) being released to pypi from stable branches15:10
openstackRemoving item from minutes: <ircmeeting.items.Action object at 0x98417d0>15:11
mrungeack, thx15:11
mriedem#action mrunge to follow up on server projects (e.g. horizon) being released to pypi from stable branches15:11
mrungethank you15:11
mriedemthere was an action item for the follows-stable-process tag, we'll come back to that15:11
mriedemmriedem to circle back on the list of projects that might need to do a stable/liberty point release15:11
mriedemi see someone updated the agenda with the latest point releases15:11
mriedemi think mistral is then the only one that's not done15:12
mriedemthey have a change up in the release repo https://review.openstack.org/#/c/273223/ but it needs to be updated to include a revert of a feature backport15:12
mriedem#action mriedem to nudge mistral stable CPL to update https://review.openstack.org/#/c/273223/15:12
mriedemwhich reminds me,15:13
mriedemneutron has been backporting A LOT of changes to stable/liberty15:13
mriedemwhich is fine if they are following policy,15:13
mtreinishhow much is a lot?15:13
*** pballand has quit IRC15:13
mriedemi'd have to find the latest release request, but it's like several dozen per month i think15:13
*** neelashah has joined #openstack-meeting-315:13
mtreinishthat is a lot15:14
mriedemanyway, dhellmann had asked that i review the latest neutron stable/liberty point release request and there were so many changes it was hard to review the change log to make sure they weren't leaking something bad in15:14
mriedemso we had pinged mestery to release more often if that's going to be the neutron stable model15:14
mriedem#action mriedem to follow up with mestery and/or ihar on releasing from stable more often if they are going to backport a lot of changes frequently15:15
mriedem#status kilo 2015.1.4 version updates pending15:15
mriedem#link open reviews https://review.openstack.org/#/q/Bump+stable/kilo+next+version+to+2015.1.4+status:open15:15
*** davidsha has joined #openstack-meeting-315:15
mriedemso neutron, neutron-vpnaas and ironic on stable/kilo can't get their version updates in b/c of gate issues15:16
mriedemthe last i looked at ironic, there might need to be a devstack backport for a timeout issue15:16
mriedemadam_g had worked around something in the ironic devstack plugin to fix master/stable/liberty, but that wasn't being used in kilo15:17
mriedemi haven't dug into the neutron* ones15:17
mriedem#topic stuck reviews15:17
*** openstack changes topic to "stuck reviews (Meeting topic: stable)"15:17
mriedemtony brought this up last week but there wasn't much discussion so i'll bring htis up again15:17
mriedemCleanup multipath ISCSI connections when disconnecting volumes - https://review.openstack.org/#/c/229152/15:17
*** ajmiller has joined #openstack-meeting-315:17
mriedemthat is a large change for nova in kilo,15:17
mriedemit essentially backports a bunch of changes from os-brick in liberty to nova in kilo to fix multipath bugs15:18
mriedem~400 LOC net change15:18
mriedemwhich seems too risky for me,15:18
flaper87mriedem: I'm now15:18
mriedemflaper87: there was just an earlier item from tonyb about syncing glance drivers with glance core team in gerrit15:19
mriedemflaper87: sigmavirus24 might have more context, it came up in last week's meeting15:19
mriedemttx: mtreinish: so if you have an opinion on https://review.openstack.org/#/c/229152/ please chime in15:19
mriedemto the review i mean15:19
ttxwill have a look15:20
* sigmavirus24 readss crollback15:20
mriedemfwiw it sounds like this fixes some major issues with multipath storage in kilo, but at this point i think people are going to just have to patch that in15:20
mriedemor upgrade nova/cinder to liberty15:20
bknudson_all the gate failures are unrelated?15:20
mriedembknudson_: yeah probably, we don't test multipath in the gate15:20
*** numans has quit IRC15:20
bknudson_Phase II (6-12 months): Only critical bugfixes and security patches are acceptable15:21
mriedemyeah i know, this was more or less falling under the bug fix tent15:21
mriedemas in critical if you're using multipath, but still, it's a very large change and i'm not really on board for bringing that in15:22
*** piet has joined #openstack-meeting-315:22
bknudson_my understanding of critical is gate-breaking15:22
mriedemat this point15:22
mriedemyeah, or breaks upgrade, etc15:22
ttxit is a significant change indeed15:22
mtreinishmriedem: I think I'm -1 just on the fact it has 7 commits backported in one patch15:22
ttxif that was exactly the code used in liberty/mitaka I guess the risk would be limited15:22
bknudson_from the commit it's a copy of a file from the lib rather than really backporting all the changes15:23
ttxbut I have no idea how much of a snowflake it is15:23
*** numans has joined #openstack-meeting-315:23
mriedemwe can move on, i'm just bringing attention to it15:24
ttxthat said it seems to be isolated to use_multipath enough15:24
mriedemsoftlayer was hitting multipath issues on kilo and i pointed that change out to them, so they were happy to see someone had done it,15:24
mriedembut i told them to just upgrade nova to liberty15:24
mriedemmoving on15:25
mriedem#topic proposed stable:follow-stable-policy tag15:26
*** openstack changes topic to "proposed stable:follow-stable-policy tag (Meeting topic: stable)"15:26
mriedem#link https://etherpad.openstack.org/p/follows-stable-policy-tag15:26
ttxSo here is the tag definition I plan to push15:26
ttxI'd rather have you all agree with it before we try to convince the TC that it would be a good idea15:26
*** JeanBriceCombebi has joined #openstack-meeting-315:27
mriedemok, i need to read through this quick (skim it)15:27
ttxone bikeshed area is on the naming (obviously)15:27
ttxthe stable: prefix is there to mean that it's owned by the stable team15:28
ttxso the second "stable" there is a bit redundant15:28
ttxcould be stable:follows-policy15:28
mriedemi'm fine with that15:29
*** jlanoux has quit IRC15:29
ttxok, renaming then15:29
bknudson_the doc looks good to me.15:29
* mtreinish slowly reads15:31
*** zz_dimtruck is now known as dimtruck15:31
mriedemok, this looks like a good draft to me15:34
ttxSo ... "healthy CI jobs, routinely backporting bug fixes and reviewing them, doing releases" - we should put that in the stable policy itself15:34
*** pavel_bondar has joined #openstack-meeting-315:34
mriedemyeah, i can add that if you want15:34
mriedem#action mriedem to update the stable policy with what it means to be actively maintaining stable branches for a project15:35
ttxLet me include your "rationale" changes15:35
mriedemanything else on this?15:36
mriedemi'll look forward to the governance review if not15:36
mriedemttx: thanks for taking the time to write this up15:36
mtreinishnot from me, looks good to me15:36
ttx#action ttx to propose corresponding governance review15:36
ttxwill push today or tomorrow15:37
mriedemi'm going to skip the tooling section of the meeting agenda since that's a WIP15:37
mriedem#topic open discussion15:37
*** openstack changes topic to "open discussion (Meeting topic: stable)"15:37
mriedemanyone have anything?15:37
mriedemi'll take that as a no and we can end early15:37
mriedemthanks everyone15:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:37
openstackMeeting ended Tue Feb  9 15:37:56 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-02-09-15.00.html15:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-02-09-15.00.txt15:38
*** neelashah has quit IRC15:38
openstackLog:            http://eavesdrop.openstack.org/meetings/stable/2016/stable.2016-02-09-15.00.log.html15:38
*** JeanBriceCombebi has quit IRC15:39
*** neil_ has joined #openstack-meeting-315:40
*** krtaylor has quit IRC15:42
*** neiljerram has quit IRC15:42
*** numans has quit IRC15:43
*** chaustin_ has joined #openstack-meeting-315:45
*** julim has joined #openstack-meeting-315:45
*** woodster_ has joined #openstack-meeting-315:45
*** yamamoto has quit IRC15:48
*** chaustin_ has quit IRC15:49
*** mriedem has left #openstack-meeting-315:49
*** muralia has joined #openstack-meeting-315:54
*** muralia has left #openstack-meeting-315:54
*** nikhil_ has joined #openstack-meeting-315:55
*** nikhil_ is now known as Guest3344915:56
*** Guest33449 is now known as nikhil15:56
*** vahidh has joined #openstack-meeting-315:56
*** rdopiera has left #openstack-meeting-315:57
*** tellesnobrega is now known as tellesnobrega_af15:57
*** tellesnobrega_af is now known as tellesnobrega15:59
*** bswartz has joined #openstack-meeting-315:59
*** Sam-I-Am has joined #openstack-meeting-315:59
*** shwetaap has joined #openstack-meeting-316:01
Sam-I-Amanyone here for the install guide meeting?16:01
bswartzI'm here to observe16:01
bswartznever been to one of these before16:01
Sam-I-Amwell, we'll see if anyone shows up16:02
Sam-I-Amthey've been slim for a while now16:02
bswartzMy interest is in this patch: https://review.openstack.org/#/c/273724/16:02
bswartzI pushed a manila install guide patch but abandoned it after seeing ^16:03
Sam-I-Ami'll probably take a look at it16:04
Sam-I-Amneeds to pass jenkins first16:04
Sam-I-Amlooks like its just us, so we might as well get it on the books16:04
*** stendulker has joined #openstack-meeting-316:05
*** jlanoux has joined #openstack-meeting-316:05
Sam-I-Am#startmeeting docinstallteam16:05
openstackMeeting started Tue Feb  9 16:05:18 2016 UTC and is due to finish in 60 minutes.  The chair is Sam-I-Am. Information about MeetBot at http://wiki.debian.org/MeetBot.16:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:05
*** openstack changes topic to " (Meeting topic: docinstallteam)"16:05
openstackThe meeting name has been set to 'docinstallteam'16:05
bswartzIt's important to me that we get a manila install guide into Mitaka16:05
Sam-I-Amwe'll talk about it in a bit16:05
Sam-I-Am#topic updates for mitaka16:06
*** openstack changes topic to "updates for mitaka (Meeting topic: docinstallteam)"16:06
*** cbouch_ has quit IRC16:06
Sam-I-Amthe spec hasn't been approved yet. please review if you get a chance.16:06
*** kzaitsev_mb has quit IRC16:06
Sam-I-Am#link https://review.openstack.org/#/c/274231/16:06
Sam-I-Amkeep in mind that it only covers updates for existing services16:06
Sam-I-Am#topic testing mitaka16:07
*** openstack changes topic to "testing mitaka (Meeting topic: docinstallteam)"16:07
Sam-I-Amlooks like ubuntu has milestone 1 packages out in the cloud-archive ppa. not terribly useful yet. i'd wait until at least milestone 3.16:07
*** armax has joined #openstack-meeting-316:08
*** fawadkhaliq has joined #openstack-meeting-316:08
Sam-I-Amrdo packages from trunk, so those are up for testing anytime and probably getting close to milestone 316:08
Sam-I-Ami havent looked at suse16:08
Sam-I-Am#topic new services for mitaka16:08
*** openstack changes topic to "new services for mitaka (Meeting topic: docinstallteam)"16:08
Sam-I-Amthis would be you, bswartz16:09
Sam-I-Ami see a blueprint, but not a spec16:09
bswartzyes there is a BP and a proposed change16:09
bswartz#link https://blueprints.launchpad.net/openstack-manuals/+spec/create-manila-install-guide16:09
bswartz#link https://review.openstack.org/#/c/273724/16:10
Sam-I-Ami found those16:10
bswartzboth of these occured without my knowledge16:10
bswartzI'm not sure who Denis Cavalcante is16:10
bswartzbut I want to help ensure this lands16:10
bswartzso I'm asking what do I need to do?16:10
bswartzwhat deadlines exist for this change?16:11
Sam-I-Amgenerally speaking, we need everything for mitaka tested prior to release16:11
*** iyamahat has joined #openstack-meeting-316:11
bswartzif a spec is needed, what should it look like? (I haven't read any documentation specs before)16:11
Sam-I-Amthis includes existing and new services16:11
Sam-I-Amthe spec just says you want to add a service, explains any required architectural changes, limitations, etc.16:12
*** PaulMurray has quit IRC16:12
Sam-I-Amfor example, if manila requires that we add/change the install guide architecture, its a bigger deal than a service that just works16:12
bswartzyes I don't believe we should require any large changes like that16:13
bswartzmanila very much fits in the mold of cinder16:13
Sam-I-Amthis patch contains a 'share node'16:13
Sam-I-Amwhich it piggybacks on the compute node, which we can't do16:13
Sam-I-Amunless the reference architecture for manila deploys share nodes on compute nodes16:13
bswartzwhere do you see that?16:13
Sam-I-Amthis is why we have specs...16:14
*** krtaylor has joined #openstack-meeting-316:14
*** mbound has quit IRC16:14
Sam-I-Amso this stuff gets discussed before someone goes through the effort of writing the patch16:14
bswartzyeah, as I said this whole thing was a surprise to me16:14
Sam-I-Ami've heard on and off about it, but thought i'd see a spec before a patch16:14
Sam-I-Amthe bp isnt approved either16:14
Sam-I-Amthe content is here, so i'm not going to -2 it, but we'll need to address the problems16:15
bswartzI entered the Mitaka release believing that any install guide documentation would need to be somewhere other than the "official" install guide, due to an email thread where loquacities basically said that16:15
Sam-I-Ami think i was around for that thread16:15
*** vahidh has quit IRC16:16
bswartzI prefer the approach dencaval seems to be taking16:16
bswartzbut I haven't yet spoken to him16:16
bswartzso I guess I need to sync up with him first16:16
bswartzand help him address these issues or work on them myself16:16
bswartzto answer your earlier question about the "share node"16:17
bswartzI think he's just referring to the node on which the services are installed16:17
Sam-I-Amthe qualifications for something going into the official install guide are generally these - a) does it work on a minimal amount of hw? b) do all distros package it? c) can we fully test it prior to release?16:17
bswartzit would be no different than cinder16:17
Sam-I-Amwe do have a cinder storage node, so maybe we can re-use that for the share node?16:17
bswartzyes I think so16:17
Sam-I-Amthats something to consider16:18
bswartzwhat does the install guide test procedure look like?16:18
Sam-I-Amusually the big hold up for new services is all distros including packages, followed by sufficient testing on all of them16:18
bswartzsome reads the doc and manually performs all the operations?16:18
*** galstrom_zzz is now known as galstrom16:18
Sam-I-Amfollow the guide to the point where you can install/use your service, try the instructions for your service.16:18
Sam-I-Amits all manual16:18
Sam-I-Ambecause thats what our audience does16:19
bswartzof course16:19
Sam-I-Amso my guess is manila becomes an optional service that references the cinder storage node bits, or something16:19
bswartzokay well my next step will be to sync up with dencaval16:19
Sam-I-Ama spec would be nice for tracking purposes16:20
bswartzcan you link the repo for that spec?16:20
Sam-I-Am#link http://specs.openstack.org/openstack/docs-specs/16:21
Sam-I-Am#link https://github.com/openstack/docs-specs16:21
*** belmoreira has quit IRC16:21
Sam-I-Ami can help with that too16:22
Sam-I-Amyou can take a look at some of the existing install guide spec in there16:22
bswartzyes that's what I'm doing16:22
bswartzI'll find out from dencaval how much help he needs and I'm happy to write the spec if it would help (even though it's a backwards process)16:23
bswartzthat's all I had16:23
Sam-I-Amusually its not backwards :)16:23
bswartzyes i mean backwards in this case16:24
bswartzspec should have come first16:24
Sam-I-Amyeah. i'm not going to hold this patch up because of the spec.16:24
Sam-I-Ami'd just like it there for tracking and historical purposes16:24
bswartzokay anything else I should know about?16:25
bswartzwhat is the deadline for the change to merge?16:26
*** pavel_bondar_ has joined #openstack-meeting-316:26
Sam-I-Amwell, we can test the patch before the majority of it merges16:26
Sam-I-Amthen tweak later as newer versions of packages come out16:26
Sam-I-Amso i'd say we want the main patch to merge between milestone 3 and rc 116:27
Sam-I-Amwhich implies it can be tested on ubuntu, rh, and suse16:27
bswartzand you'd do testing with m-3 versions of the packages?16:27
*** vgridnev has quit IRC16:27
Sam-I-Amthats where i like to start because its feature freeze16:28
bswartzor earlier versions work just as well?16:28
Sam-I-Amthings mostly work by then16:28
Sam-I-Amdepends on how involved you are with the project16:28
Sam-I-Amif you think m1 or m2 works sufficiently, then use it16:28
bswartzwell I'm the PTL for Manila, but not directly involved with packaging or docs16:29
bswartzso I'll have to ping some people16:29
Sam-I-Amwe track testing here - https://wiki.openstack.org/wiki/MitakaDocTesting16:29
Sam-I-Amwe'll need to add row for manila16:29
bswartzbroken link?16:29
*** vhoward has quit IRC16:29
bswartzthere's nothing on that page16:30
Sam-I-Ami submitted that last week16:30
Sam-I-Ami hate wikis16:30
bswartzokay thanks16:31
Sam-I-Amyeah, so thats how we track stuff16:32
Sam-I-Amit should be all green within 1-2 weeks after all distros release final packages16:32
Sam-I-Amwhich is sometimes a couple of weeks after actual release16:32
Sam-I-Amso we don't end up freezing the guide until maybe a month or so after release to facilitate updates without backports16:33
bswartzI see16:33
Sam-I-Amanything else for manila?16:34
Sam-I-Amglad we could chat16:35
bswartzyes thank you16:35
Sam-I-Amguess we can call the meeting since no one else is here16:35
*** thingee has joined #openstack-meeting-316:35
bswartzit's lunch time here anyways16:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:36
openstackMeeting ended Tue Feb  9 16:36:07 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-02-09-16.05.html16:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-02-09-16.05.txt16:36
openstackLog:            http://eavesdrop.openstack.org/meetings/docinstallteam/2016/docinstallteam.2016-02-09-16.05.log.html16:36
*** Sam-I-Am has left #openstack-meeting-316:36
*** egallen has joined #openstack-meeting-316:38
*** hdaniel has quit IRC16:39
*** mbound has joined #openstack-meeting-316:40
*** piet has quit IRC16:40
*** salv-orl_ has joined #openstack-meeting-316:41
*** bpokorny has joined #openstack-meeting-316:42
*** krtaylor has quit IRC16:44
*** salv-orlando has quit IRC16:44
*** neelashah has joined #openstack-meeting-316:44
*** PaulMurray has joined #openstack-meeting-316:44
*** PaulMurray has left #openstack-meeting-316:45
*** bpokorny has quit IRC16:45
*** egallen has quit IRC16:45
*** bpokorny has joined #openstack-meeting-316:45
*** piet has joined #openstack-meeting-316:46
*** yamahata has quit IRC16:47
*** iyamahat has quit IRC16:47
*** egallen has joined #openstack-meeting-316:48
*** vahidh has joined #openstack-meeting-316:49
*** pballand has joined #openstack-meeting-316:51
*** vishwanathj has joined #openstack-meeting-316:51
*** stendulker has quit IRC16:54
*** dandruta has quit IRC16:54
*** neelashah has quit IRC16:54
*** krtaylor has joined #openstack-meeting-316:55
*** devkulkarni has joined #openstack-meeting-316:56
*** ashishjain has joined #openstack-meeting-316:58
*** dimtruck is now known as zz_dimtruck16:58
*** zz_dimtruck is now known as dimtruck16:58
*** Aish has joined #openstack-meeting-316:59
*** jlanoux has quit IRC16:59
devkulkarni#startmeeting Solum Team Meeting17:00
openstackMeeting started Tue Feb  9 17:00:17 2016 UTC and is due to finish in 60 minutes.  The chair is devkulkarni. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: Solum Team Meeting)"17:00
openstackThe meeting name has been set to 'solum_team_meeting'17:00
devkulkarni#topic Roll Call17:00
devkulkarniDevdatta Kulkarni17:00
ashishjainAshish Jain17:00
*** openstack changes topic to "Roll Call (Meeting topic: Solum Team Meeting)"17:00
*** jlanoux has joined #openstack-meeting-317:00
devkulkarniGood evening ashishjain17:00
*** muralia has joined #openstack-meeting-317:00
devkulkarnihi thingee17:00
*** pkovar has joined #openstack-meeting-317:00
ashishjaingood morning devkulkarni17:00
muraliahi all17:01
devkulkarnihi muralia dimtruck17:01
*** egallen has quit IRC17:01
devkulkarnihere is the agenda for today's meeting:17:01
devkulkarni#link https://wiki.openstack.org/wiki/Meetings/Solum17:01
devkulkarniplease take a minute to look over the agenda17:01
*** vijendar1 has joined #openstack-meeting-317:01
devkulkarniplease add to if if you want to discuss anything17:01
devkulkarnihi vijendar117:01
devkulkarni#topic Announcements17:02
*** openstack changes topic to "Announcements (Meeting topic: Solum Team Meeting)"17:02
devkulkarniCongratulations to Vijendar Komalla (vijendar1) on being promoted to core reviewer status.17:02
devkulkarnicongrats vijendar117:02
vijendar1thanks devkulkarni muralia17:02
devkulkarniI had sent an email last week and we received all positive replies17:02
*** d0ugal has quit IRC17:02
ashishjainCongrats vijendar17:02
vijendar1thanks ashishjain17:03
*** ALUvial has quit IRC17:03
devkulkarnivijendar1 is now a core reviewer (and has already exercised his +2 rights :))17:03
ashishjainwow :)17:03
devkulkarnigreat work vijendar1 over last several months17:03
devkulkarniamazing to see your contributions17:03
devkulkarnikeep up the good work17:03
devkulkarniany other announcement from anyone else?17:04
devkulkarniok, lets move to next topic then17:04
devkulkarni#topic Review Action Items17:04
*** openstack changes topic to "Review Action Items (Meeting topic: Solum Team Meeting)"17:04
*** kzaitsev_mb has joined #openstack-meeting-317:04
*** egallen has joined #openstack-meeting-317:04
devkulkarnithere were no action items from last meeting17:05
devkulkarni#topic Blueprint/Bug review and Discussion17:05
*** openstack changes topic to "Blueprint/Bug review and Discussion (Meeting topic: Solum Team Meeting)"17:05
devkulkarniok, so this topic has several things today17:05
devkulkarnilets go over them one by one17:05
devkulkarni1) App parameters17:06
devkulkarni#link https://review.openstack.org/#/c/267182/17:06
devkulkarni#link https://review.openstack.org/#/c/267809/17:06
devkulkarnivijendar1: do you want to provide quick update on these patches?17:06
devkulkarniyou had given context in the last meeting17:06
devkulkarnibut there might be folks who were not there in that meeting17:06
vijendar1devkulkarni: sure17:06
*** neelashah has joined #openstack-meeting-317:07
devkulkarnicool, please proceed. floor is yours17:07
vijendar1These patches enable us to provide custom parameters17:07
*** neelashah1 has joined #openstack-meeting-317:08
vijendar1current parameters file is a flat list of key value pairs17:08
vijendar1with this change, you can group parameters into logical sections17:08
devkulkarni+1 vijendar117:08
muraliai thought i voted +2 on this last time. :) did i not? i remember we discussed this last week and i reviewed the patch.17:08
muraliaim good with the changes.17:08
devkulkarnimuralia: yes, we discussed this last time17:09
devkulkarnibut both the patches need one more +217:09
ashishjainsomehow I am unable to open the links17:09
ashishjain"Proxy Error"17:09
muraliayes, same here17:09
*** iyamahat has joined #openstack-meeting-317:09
devkulkarniashishjain: hmm.. yeah, I have seen gerrit replying that way many times this week17:09
vijendar1muralia: It seems you did not +2  last week17:09
muraliadoing it now17:10
devkulkarniit just opened up for me17:10
devkulkarniafter spinning for a while17:10
vijendar1it opened for me as well17:10
devkulkarniprobably gerrit servers are experiencing lot of load17:10
dimtruckit's an apache redirect error17:10
dimtruckare ya'll logged in?17:10
*** jlanoux has quit IRC17:10
devkulkarnigood question dimtruck17:10
*** piet has quit IRC17:10
muraliai logged in. it logged me out and failed again :)17:11
vijendar1muralia: thanks17:11
*** sdake has quit IRC17:11
dimtruck:) sorry for the tangent17:11
*** neelashah has quit IRC17:11
vijendar1muralia: for +217:11
devkulkarnimuralia: whenever you get a chance today, you can +2 the patches then (probably you already have)17:11
devkulkarniin that case, thanks muralia17:11
devkulkarniso the next one is:17:12
devkulkarni2) App scaling17:12
devkulkarnilet me give an overview about this17:12
devkulkarniand then I can point to the three patches17:12
*** sdake has joined #openstack-meeting-317:13
devkulkarniso the basic requirement is we want to support something like 'solum app scale <app-name> <target>17:13
devkulkarniwhere target is the number of instances of that we want to create for an app17:13
devkulkarniupon receiving such a request, we want to deploy that many instances of the DU17:13
*** yamahata has joined #openstack-meeting-317:14
devkulkarniconsider when we have a backend such as Magnum/Carina17:14
devkulkarniwe will have a deployer which will instantiate as many number of target instances as required.. if the currently deployed17:14
devkulkarniinstances are 3, and the target is 5, we will add 2 more17:15
devkulkarniwhereas if the current number of instances are 5 and the target is 1, we will delete 417:15
*** pkovar has left #openstack-meeting-317:15
devkulkarniwhen we go to multi-service/multi-container apps, the command line might look like17:15
devkulkarnisolum app scale <app-name> <service1:target1> <service2:target2>17:16
devkulkarnibut since we don't have support for multi-container apps yet,17:16
devkulkarnithe current command line is just taking input the app-name and the target17:16
devkulkarniok, so that is the high-level idea17:16
devkulkarniI have three patches which together setup the required infrastructure to implement above17:17
devkulkarnithe first patch on the api side adds a column to the app table named 'scale_config'17:17
devkulkarnithe data structure that is used is a json blob17:18
muraliawhat do you expect to put in there? will that be config for magnum or heat?17:18
devkulkarnimuralia: the content will be three things (which are neither magnum related nor heat related)17:18
devkulkarnithese are: <the specified target, current number of instances, location of the du>17:19
devkulkarnithe specified target is what is sent in as part of the app scale command line17:19
devkulkarnithe current number of instances is basically how many instances we were able to really create17:19
devkulkarniwe need to maintain this as it is possible that while performing the scaling operation, we may fail in between17:20
devkulkarniand may not be able to create all the instances17:20
vijendar1so target is the desired number of instances after executing scale command…correct?17:20
devkulkarnivijendar1: yes, that is correct.17:20
*** egallen has quit IRC17:20
muraliaah i see. this info is not really app related directly, so we put it there.  why the location of DU though, we should already know that right. we are storing that somewhere17:20
devkulkarnimuralia: so the reason to store DU info there is primarily for convenience purpose — that way all the information that is required for scaling is available in a single place17:21
devkulkarnibut you are right, it is available in the Image table as well17:21
vijendar1we may need du info, for example multi service app  may have multiple DUs…17:21
devkulkarnithat too.. although, for multi service apps also we will have the DU locations in the Image table17:22
vijendar1you are right17:22
devkulkarniso technically, we are still duplicating the info17:22
devkulkarnibut I think it is okay as it provides a single place with all the required info..17:23
devkulkarniif we find it is becoming problematic, we can change that17:23
vijendar1if required we can get rid of that info in future17:23
devkulkarniyes, that is what I am thinking17:23
devkulkarnigood questions muralia17:23
devkulkarninow let me talk about the second patch17:23
devkulkarnihmm.. I am getting 503 Service unavailable17:24
-openstackstatus- NOTICE: Gerrit is restarting now, to alleviate current performance impact and WebUI errors.17:24
devkulkarnilet me just explain what the second patch is doing17:24
*** tej has quit IRC17:24
devkulkarniso in the second patch, I am populating the scale_config column17:25
devkulkarnithe main changes are in three places.. one, as part of the initial 'solum app deploy' call, we save the du location in the scale_config column.17:25
*** matrohon has quit IRC17:25
devkulkarnisecond, as part of the 'solum app scale' call, we update that column with the value of scale_target that is passed in17:26
devkulkarnithird, as part of the deployer, we inspect the scale_config column and then take appropriate action17:26
devkulkarnithe third part is not implemented yet17:26
devkulkarniI will implement it in a follow up patch17:27
devkulkarnithen there is the cli patch17:27
*** ashishjain1 has joined #openstack-meeting-317:27
devkulkarnithis patch makes the changes to support 'solum app scale' command17:28
muraliathanks dev17:28
devkulkarnithat is about it17:28
devkulkarnivijendar1: I have seen your comments on the patch17:28
devkulkarnivijendar1: I will address them today/tomorrow17:28
ashishjain1Devkulkarni, was looking at all your 3 patches17:28
devkulkarniashishjain, muralia, dimtruck: please review the patches17:29
devkulkarniashishjain1: thanks17:29
ashishjain1The deployment of multiple du's is yet to be implemented?17:29
devkulkarniashishjain1: yes, that is correct17:29
ashishjain1In heat.py def scale17:29
ashishjain1Is the one which will take the action as required?17:30
devkulkarniashishjain1: yes, the new scale api addition is to support scaling of a single container apps17:30
devkulkarniyes, that is correct17:30
*** mbound has quit IRC17:30
ashishjain1So will you modify the generated heat template for this17:30
devkulkarniashishjain1: yes, we will have to do that17:30
ashishjain1Heat has got tags for that?17:30
ashishjain1Okay cool thanks for this17:31
*** ashishjain has quit IRC17:31
devkulkarniashishjain1: will have to check what features, if any, are available in heat that we might be able to leverage for this17:31
devkulkarnivijendar1: do you think we might be able to use any heat features for single app scaling?17:31
*** e0ne has quit IRC17:32
devkulkarnivijendar1: feel free to jump in later..17:33
*** sdake has quit IRC17:33
devkulkarnilets move to the next one17:33
ashishjain1Devkulkarni: Heat has got a autoscaling group17:33
devkulkarniashishjain1: oh that's correct17:33
devkulkarniashishjain1: yes, then we should definitely explore how might we use it17:33
ashishjain1Which has got a field called min and max17:33
*** sdake has joined #openstack-meeting-317:33
*** egallen has joined #openstack-meeting-317:33
devkulkarniyep, thanks for refreshing my memory17:33
ashishjain1yeah we should see that17:34
devkulkarnithanks ashishjain117:34
devkulkarnilets move to the next one in the list17:34
devkulkarni3) Deploying pre-created DUs17:34
devkulkarniOk, let me give background on this one17:34
*** safchain has quit IRC17:34
*** tellesnobrega is now known as tellesnobrega_af17:34
devkulkarnithe basic idea is to be able to deploy a DU without building it first.. such a DU might be available, say, from a CI run that has happened outside of Solum17:35
devkulkarniashishjain1 has implemented a poc of doing just this17:35
devkulkarnihe has a setup where CI is done by Jenkins, completely out of Solum17:35
devkulkarniand then Solum is called only to deploy the DU17:36
devkulkarnithe patches below are first step in supporting this use case17:36
devkulkarni#link https://review.openstack.org/#/c/271111/17:36
devkulkarni#link https://review.openstack.org/#/c/271115/17:36
devkulkarnithe first link is api side changes17:36
devkulkarnithe second link is cli side changes17:37
devkulkarnicurrently on the api side, I have implemented support only for DUs that are stored in glance17:37
devkulkarnifrom the cli, you can pass in glance image id of the DU and that will be deployed, without going through the build and test steps17:38
devkulkarnivijendar1: I saw your comments on the patch, I will address them today/tomorrow17:38
devkulkarniothers, please review the patches17:38
vijendar1devkulkarni: thanks17:38
*** ajmiller has quit IRC17:39
devkulkarnialright, lets look at two other items next17:39
devkulkarni4) Converting bash scripts to Python17:39
devkulkarni#link https://review.openstack.org/#/c/196498/17:39
devkulkarnithis is currently in merge conflict17:40
devkulkarniI have pinged james_li to take a look at it17:40
devkulkarnihopefully this will be merged soon17:40
devkulkarnithanks muralia for approving the other bash-to-python patch from james_li17:40
devkulkarnivijendar1: if you have any comments on bash-to-python patch, please add them to the currently outstanding patch17:41
vijendar1devkulkarni: sure17:41
devkulkarnialright.. the last one is about cutting a release17:41
devkulkarni#link http://lists.openstack.org/pipermail/openstack-dev/2016-February/086152.html17:41
*** ajmiller has joined #openstack-meeting-317:42
devkulkarnithis morning ttx sent an email listing projects who need to do releases in next few weeks17:42
*** tej has joined #openstack-meeting-317:42
devkulkarnisince we are now using release-with-intermediate cycle, we need to release something before april 1st17:42
devkulkarnijust wanted to bring this to everyone's attention17:42
devkulkarniwhat I would like to do is17:42
devkulkarnimerge as many of the currently outstanding patches as possible in next two weeks17:43
devkulkarnithen, in the second week of march I will propose a change to the release repo with the commit17:43
devkulkarnifor release17:43
devkulkarniso everyone's help in reviewing and approving patches will be good17:44
*** mkovacik has quit IRC17:44
devkulkarnialright.. we have fifteen minutes for open discussion now17:44
devkulkarni#topic Open Discussion17:44
*** openstack changes topic to "Open Discussion (Meeting topic: Solum Team Meeting)"17:45
devkulkarnilets quickly go through the first topic and then we can discuss install docs17:45
devkulkarni1) Austin summit17:45
devkulkarniWe have submitted three talks -- one by ashishjain and devkulkarni, another by vijendar and devkulkarni, and another by mkam, dimtruck, and two openstack security contributors. Will post the links when I have them.17:45
devkulkarnidimtruck: have you seen the links for voting anywhere?17:45
devkulkarniI have not17:45
devkulkarniashishjain1: Travel support: February 9, 2016 (https://www.openstack.org/summit/austin-2016/austin-and-travel/#travel-support)17:46
devkulkarnideadline is today17:46
devkulkarnito apply to travel support17:46
ashishjain1Ya i have not submitted i am relying on my org :)17:46
devkulkarniashishjain1: :) sounds good17:46
ashishjain1Btw have not received atc code17:47
devkulkarniashishjain1: they should send out another batch in next couple of weeks17:47
*** davidsha has quit IRC17:47
devkulkarnialright.. lets talk about next topic17:47
*** safchain has joined #openstack-meeting-317:47
devkulkarni(thingee) Install docs17:48
thingeeso install docs, what's available today for solumn?17:48
devkulkarnifloor is yours thingee17:48
dimtrucki have not devkulkarni (sorry, my irc client froze)17:48
*** jtomasek has quit IRC17:48
devkulkarnithingee: we have an architecture diagram on how solum can be deployed in prod17:48
devkulkarnibeyond that, we have some chef receipes that we use internally at rax17:48
devkulkarnidimtruck: you might want to add17:49
devkulkarnithingee: let me get it17:49
dimtruckyeah, i'm looking for it too17:49
thingeeok, so people who aren't rackspace and don't use chef will have some trouble?17:49
dimtruckthingee: not necessarily17:49
dimtruckthe main chef codebase to deploy paas is in https://github.com/rackerlabs/cookbook-openstack-paas17:49
dimtruckall rackspace bits do is override a few attributes in that cookbook17:50
devkulkarnialso, I think ashishjain1 your team is working on kolla based deployment for solum, right?17:50
dimtruck#link https://github.com/rackerlabs/cookbook-openstack-paas17:50
thingeeYeah ok, I was a bit afraid of this. So just from an outsiders perspective, I attempted over the weekend to figure out solum. When you go to the wiki you're presented with a vagrant demo.17:50
thingeeI don't use chef17:50
thingeeI don't believe vagrant is install option17:50
ashishjain1Devkulkarni yeah17:50
thingeeand I don't know what each process is to figure out how to run things.17:51
thingeeThe project has existed since late 2013, so I'm curious why figuring this out is still difficult17:51
devkulkarnithingee: I see.. this is great feedback17:51
*** Swami has joined #openstack-meeting-317:51
*** tellesnobrega_af is now known as tellesnobrega17:52
devkulkarnithingee: agreed that there is scope for improvement for our devstack and vagrant docs17:52
thingeeI do understand generally how OpenStack projects work being former ptl for cinder and a contributor for a while now and I can't even figure it out, or how to run things in a liberty environment.17:52
dimtruckso you're right in that if you don't use chef, it'll be more challenging.  vagrant is being upgraded to use devstack plugins and should be ready shortly (i believe that are a few patches in progress)17:53
*** vgridnev has joined #openstack-meeting-317:53
thingeethe main reason I bring this up though is because I'm interested in presenting to app developers how to use openstack. I saw the early presentations by Adrian otto an it's impressive, but I'm curious what public clouds make use of it, or even how to deploy it for private cloud cases.17:53
dimtruckthingee: in that case, and we'll need to document that more explicitly, but it's just enable_service solum and enable_service python-solumclient17:53
devkulkarnithat is correct dimtruck.. we haven't completely converted our vagrant setup to use devstack plugin model17:53
thingeeI'm looking at murano and the new anisble 2.0 module which hides a lot of bad openstack api details behind shade. But I appreciate you all listening to me rant.17:54
dimtruckbut yes, that is good feedback, and we'll update documentation to alleviate your concerns17:54
devkulkarnithingee: this is great feedback actually17:54
dimtruckdevkulkarni: if there's a bug for docs out there, assign it to me17:54
dimtrucki'll take care of it17:54
dimtruckif not, i'll create one haha17:54
devkulkarnithingee: our most recent user/contributor from outside of rax has been ashishjain117:54
*** pavel_bondar_ has quit IRC17:54
devkulkarniashishjain1: would you mind sharing your experience with all of us?17:55
kzaitsev_mbsomeone said murano and I'm a bit out of the loop, but willing to help/clarify things, if that's possible )17:55
ashishjain1It has been great working with all you guys17:55
thingeeso is there anybody making use of solum today? I hear rackspace, but I haven't found an GUI similar to the one presented on solum's wiki on rackspace's portal17:55
ashishjain1I am still in the learning phase about solum and of course openstack17:56
dimtruckthingee: solum is in internal beta at rackspace right now17:56
devkulkarnithingee: internally we had a UI which is different than the horizon ui.. but is not yet integrated with rax's main ui portal17:56
thingeekzaitsev_mb: it was me. And I don't believe there is confusion. I'm trying to find things that are readily everybody today to talk about with app developers and other users.17:57
ashishjain1And have been getting good guidance from all and an awesome mentor like dev17:57
devkulkarnithingee: I believe there is some interest by ashishjain1's org as well17:57
thingeeok good information everyone. thanks again!17:57
dimtruckthank YOU17:57
devkulkarnithanks thingee for trying out solum17:58
devkulkarnisorry that the experience was not smooth17:58
devkulkarniwe will take your feedback and look to improving the first user/operator experience17:58
devkulkarnialright.. we are almost at the end of our meeting time17:59
devkulkarnithanks everyone for joining today.. we had great discussion17:59
thingeeYeah I just worry with projects that have existed a bit and adoption. If this isn't something available across public clouds, it's difficult to rely on from users looking a federated cloud cases.18:00
devkulkarniI am available on solum irc today (and everyday)18:00
*** jwang has joined #openstack-meeting-318:00
*** jwang_ has quit IRC18:00
*** vishwanathj has quit IRC18:00
devkulkarnipoint noted thingee .. good to have you today.. hopefully you will join more of our meetings18:00
dimtruckthingee: very valid concern.  and i'd say that before the last couple of weeks (integration with magnum, scaling, workflow fixes), it was very hard to utilize solum to full extent18:00
*** pavel_bondar_ has joined #openstack-meeting-318:00
devkulkarnigood point dimtruck18:01
*** neil_ has quit IRC18:01
devkulkarnihopefully, we are now able to showcase value of solum more18:01
devkulkarnithanks everyone for joining today18:01
devkulkarnisee you all next week18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:02
openstackMeeting ended Tue Feb  9 18:02:03 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/solum_team_meeting/2016/solum_team_meeting.2016-02-09-17.00.html18:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/solum_team_meeting/2016/solum_team_meeting.2016-02-09-17.00.txt18:02
openstackLog:            http://eavesdrop.openstack.org/meetings/solum_team_meeting/2016/solum_team_meeting.2016-02-09-17.00.log.html18:02
*** ashishjain1 has quit IRC18:02
*** rossella_s has quit IRC18:02
*** neil_ has joined #openstack-meeting-318:03
*** muralia has left #openstack-meeting-318:03
*** rossella_s has joined #openstack-meeting-318:03
*** woodster_ has quit IRC18:06
*** cbouch has joined #openstack-meeting-318:08
*** egallen has quit IRC18:12
*** egallen has joined #openstack-meeting-318:15
*** safchain has quit IRC18:16
*** e0ne has joined #openstack-meeting-318:17
*** Aish has quit IRC18:18
*** pavel_bondar_ has quit IRC18:18
*** piet has joined #openstack-meeting-318:23
*** piet has quit IRC18:23
*** neil_ has quit IRC18:24
*** Aish has joined #openstack-meeting-318:31
*** ajmiller has quit IRC18:33
*** irenab has joined #openstack-meeting-318:33
*** egallen has quit IRC18:36
*** ajmiller has joined #openstack-meeting-318:36
*** neelashah1 has quit IRC18:38
*** baoli_ has quit IRC18:40
*** vhoward has joined #openstack-meeting-318:42
*** matrohon has joined #openstack-meeting-318:46
*** vijendar1 has quit IRC18:47
*** iyamahat has quit IRC18:51
*** cbouch_ has joined #openstack-meeting-318:53
*** cbouch has quit IRC18:56
*** krtaylor has quit IRC18:57
*** matrohon has quit IRC18:57
*** ivar-lazzaro has joined #openstack-meeting-318:58
*** neelashah has joined #openstack-meeting-318:59
briancurtin#startmeeting python-openstacksdk19:00
openstackMeeting started Tue Feb  9 19:00:05 2016 UTC and is due to finish in 60 minutes.  The chair is briancurtin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: python-openstacksdk)"19:00
openstackThe meeting name has been set to 'python_openstacksdk'19:00
briancurtinrtheis you around? i don’t see terry online at all19:00
rtheisI have another meeting running at the same time so may be distracted for a bit19:01
briancurtinrtheis: all good, not much to discuss - i have a small update and then i know etoews has a thing19:02
briancurtini’m going to kick it off with an update on what i’ve been working on. it’s been in circles a few times, but i think i’m on the right path19:02
briancurtinafter going down a few rabbit holes that ended up being impossible with props being descriptors, i looked at maybe moving away from them being that, but it harms usability, so i think i can keep them intact but just change how we store things. since we’ve been putting headers together with body props in the _attrs dict, i’m looking at storing them19:04
briancurtincompletely separately and splitting how headers and body props work under the hood, while enabling URI-only props. i think through that it should help an issue everett saw with some services being strict about what they receive, so we’d be able to specify that certain things are read-only or for requests or something like that, so that we’re not sending19:04
briancurtinmore data than we need to (or more than the server can work with)19:04
*** vijendar has joined #openstack-meeting-319:05
*** neiljerram has joined #openstack-meeting-319:05
briancurtinthere hasn’t been a lot to show for it because there has been a lot of starting and stopping, heading another direction, running into the same road block, and then going back to the drawing board. i should be able to get a lot further with this, it just touches a lot of places and i need to figure out some good internal APIs for working with it19:05
*** fawadkhaliq has quit IRC19:06
*** vijendar1 has joined #openstack-meeting-319:06
etoewsthat sounds like a lot of work19:06
briancurtinsort of, but i don’t think it’s work we can avoid19:06
etoewsseems like it could be helpful down the road too though19:06
etoewsonce openstack gets stricter about the requests it accepts19:07
*** pballand has quit IRC19:07
*** pballand has joined #openstack-meeting-319:09
briancurtini’m going to try to minimize the change and just focus on getting the public stuff right so that we can release a 1.0, if it’s possible to split it up at all. i don’t really know how the full change is going to turn out  right now though19:09
*** krtaylor has joined #openstack-meeting-319:09
*** vijendar has quit IRC19:09
briancurtinanyway, that’s where that’s at. etoews do you want to talk about the metadata stuff?19:10
openstackLaunchpad bug 1487150 in OpenStack SDK "Object store set_object_metadata is a bit oddball" [Critical,In progress] - Assigned to Everett Toews (everett-toews)19:11
etoewsso starting on that has basically been pulling a loose thread on a sweater.19:11
etoewsfirst i ran into this https://bugs.launchpad.net/python-openstacksdk/+bug/1488269/19:12
openstackLaunchpad bug 1488269 in OpenStack SDK "Object get needs to be smarter about what headers it sends" [Undecided,New]19:12
etoewsi got sort of figured that one out (haven't sent a any new commits though)19:13
etoewsthen i learned of the horrific inconsistency in metadata handling between account/container and object in object store http://developer.openstack.org/api-ref-objectstorage-v1.html19:13
*** vhoward_ has joined #openstack-meeting-319:14
etoewsto smooth over that inconsistency it's got me considering redesigning the way compute handles metadata19:15
etoewshere's what i'm thinking19:15
*** alex_xu has quit IRC19:15
*** vhoward has quit IRC19:15
*** omer_etrog has joined #openstack-meeting-319:16
etoewsthe object store proxy would have a metadata interface like19:16
etoewsget_metadata(self, resource, key=None)19:16
etoewscreate_metadata(self, resource, **metadata)19:16
etoewsreplace_metadata(self, resource, **metadata)19:16
etoewsupdate_metadata(self, resource, **metadata)19:16
etoewsdelete_metadata(self, resource, key)19:16
etoews(very similar to compute)19:16
etoewsresource would have to be an instance of an account, container, or object, just so we can switch on the resource type to do the appropriate thing and `**metadata` would be able to update both custom metadata and regular metadata.19:17
*** dims_ has joined #openstack-meeting-319:17
*** jcook has quit IRC19:17
*** dims has quit IRC19:17
etoewsto keep things things consistent we'd want to change the metadata interface in compute to match19:17
etoewsalthough that would be part of a different patch set and not that difficult to do.19:18
*** alex_xu has joined #openstack-meeting-319:18
etoewswe'd also need to look at the image service metadata/properties/whatever-they-call-it to be sure that interface would work there too.19:19
briancurtinetoews and i already sort of talked about this, but yeah, i’m on board with it. consistency across the board, and allows us to fix some of the issues object_store has with its own inconsistencies19:20
*** jcook has joined #openstack-meeting-319:20
etoewsall in all it's a ridiculous amount of work just to set key/value pairs on resources :/19:20
briancurtinyep, but another one of those things we should spend the time to get right before shipping an inconsistent 1.0 that we can’t really change without a 2.019:21
etoewsya. better to get this stuff in now.19:21
etoewsrtheis: is https://review.openstack.org/#/c/270900/ updated on what we discussed last week ( https://bugs.launchpad.net/python-openstacksdk/+bug/1461200/comments/9 )?19:22
openstackLaunchpad bug 1461200 in OpenStack SDK "Create basic resource.props for id and ids attributes" [Critical,In progress] - Assigned to Richard Theis (rtheis)19:22
rtheisetoews: yes, I updated based last week's discussion19:23
rtheisIt is China holiday now so maybe Qiming is out19:23
etoewsthx. i'll give it another review.19:24
etoewsyear of the monkey!19:24
*** itxaka has quit IRC19:24
etoewsyear of the code monkey!19:25
briancurtinanything else going on?19:26
*** ivar-lazzaro has quit IRC19:26
*** dims_ has quit IRC19:27
*** Sukhdev has joined #openstack-meeting-319:27
*** dedery has quit IRC19:27
etoewsnot so much19:28
rtheisnothing else here19:28
*** dedery has joined #openstack-meeting-319:28
briancurtinalrighty then, back to the grind i guess19:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:29
openstackMeeting ended Tue Feb  9 19:29:36 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:29
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2016/python_openstacksdk.2016-02-09-19.00.html19:29
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2016/python_openstacksdk.2016-02-09-19.00.txt19:29
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2016/python_openstacksdk.2016-02-09-19.00.log.html19:29
*** dims has joined #openstack-meeting-319:30
*** kzaitsev_mb has quit IRC19:31
*** pballand has quit IRC19:31
*** ivar-lazzaro has joined #openstack-meeting-319:31
*** jtomasek_ has joined #openstack-meeting-319:31
*** ivar-lazzaro has quit IRC19:34
*** ivar-lazzaro has joined #openstack-meeting-319:34
*** dedery has quit IRC19:35
*** dedery has joined #openstack-meeting-319:36
*** mkovacik has joined #openstack-meeting-319:37
*** dedery has quit IRC19:38
*** kzaitsev_mb has joined #openstack-meeting-319:38
*** dedery has joined #openstack-meeting-319:39
*** dims has quit IRC19:41
*** thingee has left #openstack-meeting-319:41
*** vijendar1 has quit IRC19:41
*** dims has joined #openstack-meeting-319:42
*** dedery has quit IRC19:44
*** dedery has joined #openstack-meeting-319:46
*** dims_ has joined #openstack-meeting-319:46
*** omer_etrog has quit IRC19:47
*** vishwanathj has joined #openstack-meeting-319:47
*** dims has quit IRC19:49
*** e0ne has quit IRC19:49
*** omer_etr_ has joined #openstack-meeting-319:50
*** dedery has quit IRC19:51
*** dedery has joined #openstack-meeting-319:52
*** dedery has quit IRC19:56
*** dims_ has quit IRC19:57
*** dedery has joined #openstack-meeting-319:57
*** cbouch_ has quit IRC19:58
*** pt_15 has joined #openstack-meeting-320:00
*** rockyg has joined #openstack-meeting-320:01
*** dedery has quit IRC20:04
*** dedery has joined #openstack-meeting-320:05
*** cbouch has joined #openstack-meeting-320:05
*** neelashah has quit IRC20:05
*** vijendar has joined #openstack-meeting-320:08
*** neelashah has joined #openstack-meeting-320:08
*** piet has joined #openstack-meeting-320:09
*** kzaitsev_mb has quit IRC20:10
*** omer_etr_ has quit IRC20:12
*** omer_etrog has joined #openstack-meeting-320:12
*** piet has quit IRC20:13
*** piet has joined #openstack-meeting-320:13
*** tej has quit IRC20:14
*** tej has joined #openstack-meeting-320:15
*** tej has quit IRC20:16
*** dedery has quit IRC20:19
*** krtaylor has quit IRC20:19
*** dedery has joined #openstack-meeting-320:19
*** tej_ has joined #openstack-meeting-320:19
*** cbouch has quit IRC20:23
*** Sukhdev has quit IRC20:27
*** hdaniel has joined #openstack-meeting-320:29
*** Sukhdev has joined #openstack-meeting-320:30
*** krtaylor has joined #openstack-meeting-320:31
*** NobodyCa1 has joined #openstack-meeting-320:34
*** salv-orl_ has quit IRC20:36
*** SumitNaiksatam has joined #openstack-meeting-320:38
*** NobodyCa1 has quit IRC20:41
*** devkulkarni has quit IRC20:41
*** devkulkarni has joined #openstack-meeting-320:43
*** Sukhdev has quit IRC20:45
*** piet has quit IRC20:46
*** kzaitsev_mb has joined #openstack-meeting-320:47
*** NobodyCa1 has joined #openstack-meeting-320:48
*** deva_ has joined #openstack-meeting-320:49
*** salv-orlando has joined #openstack-meeting-320:53
*** krtaylor has quit IRC20:53
*** NobodyCa1 has quit IRC20:53
*** safchain has joined #openstack-meeting-320:54
*** deva_ has quit IRC20:54
*** pballand has joined #openstack-meeting-321:01
*** galstrom is now known as galstrom_zzz21:01
*** dedery has quit IRC21:02
*** dims has joined #openstack-meeting-321:03
*** krotscheck is now known as krotscheck_dcm21:03
*** e0ne has joined #openstack-meeting-321:03
*** ivar-laz_ has joined #openstack-meeting-321:04
*** krtaylor has joined #openstack-meeting-321:07
*** ivar-lazzaro has quit IRC21:07
*** jmckind has quit IRC21:13
*** galstrom_zzz is now known as galstrom21:14
*** neelashah has quit IRC21:16
*** tej_ has quit IRC21:21
*** tej has joined #openstack-meeting-321:22
*** tej has quit IRC21:27
*** matrohon has joined #openstack-meeting-321:28
*** tellesnobrega is now known as tellesnobrega_af21:30
*** omer_etrog has quit IRC21:32
*** lblanchard has quit IRC21:34
*** baoli has joined #openstack-meeting-321:38
*** vgridnev has quit IRC21:40
*** iyamahat has joined #openstack-meeting-321:40
*** jmckind has joined #openstack-meeting-321:41
*** nikhil has quit IRC21:44
*** sdake has quit IRC21:49
*** neelashah has joined #openstack-meeting-321:49
*** nkrinner has quit IRC21:50
*** FallenPegasus has joined #openstack-meeting-321:52
*** hdaniel has quit IRC21:54
*** jmckind_ has joined #openstack-meeting-321:56
*** jmckind has quit IRC21:59
*** rossella_s has quit IRC22:03
*** Sukhdev has joined #openstack-meeting-322:03
*** matrohon has quit IRC22:03
*** rossella_s has joined #openstack-meeting-322:03
*** FallenPegasus has quit IRC22:05
*** tej has joined #openstack-meeting-322:22
*** dedery has joined #openstack-meeting-322:22
*** egallen has joined #openstack-meeting-322:24
*** rockyg has quit IRC22:25
*** FallenPegasus has joined #openstack-meeting-322:26
*** safchain has quit IRC22:28
*** julim has quit IRC22:32
*** tej has quit IRC22:33
*** tej has joined #openstack-meeting-322:34
*** tej has quit IRC22:38
*** dims_ has joined #openstack-meeting-322:39
*** salv-orl_ has joined #openstack-meeting-322:40
*** dims has quit IRC22:40
*** salv-orlando has quit IRC22:43
*** rtheis has quit IRC22:46
*** Sukhdev has quit IRC22:47
*** FallenPegasus has quit IRC22:47
*** baoli has quit IRC22:50
*** baoli has joined #openstack-meeting-322:55
*** Sukhdev has joined #openstack-meeting-322:57
*** dimtruck is now known as zz_dimtruck22:57
*** Sukhdev has quit IRC22:58
*** Sukhdev has joined #openstack-meeting-322:59
*** jaypipes has quit IRC23:00
*** Sukhdev has quit IRC23:01
*** galstrom is now known as galstrom_zzz23:04
*** Sukhdev has joined #openstack-meeting-323:04
*** Sukhdev has quit IRC23:09
*** tej has joined #openstack-meeting-323:09
*** Sukhdev has joined #openstack-meeting-323:09
*** Sukhdev has quit IRC23:10
*** Sukhdev has joined #openstack-meeting-323:10
*** Sukhdev has quit IRC23:12
*** jtomasek_ has quit IRC23:12
*** kzaitsev_mb has quit IRC23:13
*** mkovacik has quit IRC23:13
*** tej has quit IRC23:14
*** Sukhdev has joined #openstack-meeting-323:14
*** tej has joined #openstack-meeting-323:15
*** mkovacik has joined #openstack-meeting-323:19
*** baoli has quit IRC23:20
*** yamamoto_ has joined #openstack-meeting-323:21
*** yamamoto_ has quit IRC23:23
*** haleyb has quit IRC23:25
*** zz_dimtruck is now known as dimtruck23:25
*** vijendar has quit IRC23:26
*** shwetaap has quit IRC23:28
*** Sukhdev has quit IRC23:30
*** Sukhdev has joined #openstack-meeting-323:31
*** Sukhdev has quit IRC23:32
*** jpomeroy has quit IRC23:32
*** tej has quit IRC23:38
*** neelashah has quit IRC23:44
*** Sukhdev has joined #openstack-meeting-323:47
*** dedery has quit IRC23:47
*** yamamoto_ has joined #openstack-meeting-323:50
*** sigmavirus24 is now known as sigmavirus24_awa23:51
*** Sukhdev has quit IRC23:54
*** pballand has quit IRC23:58
*** rbak has quit IRC23:59

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