Wednesday, 2013-08-28

*** sacharya has joined #openstack-meeting00:02
*** anniec has quit IRC00:04
*** adalbas has quit IRC00:04
*** rdxc has quit IRC00:05
*** vipul-away is now known as vipul00:08
*** SumitNaiksatam has quit IRC00:08
*** otherwiseguy has quit IRC00:13
*** lexinator has quit IRC00:14
*** lexinator1 has joined #openstack-meeting00:14
*** lexinator has joined #openstack-meeting00:16
*** lexinator1 has quit IRC00:19
*** sacharya has quit IRC00:22
*** stevemar has quit IRC00:23
*** alexpilotti has joined #openstack-meeting00:26
*** markwash has quit IRC00:27
*** nati_ueno has joined #openstack-meeting00:28
*** lexinator has quit IRC00:31
*** lexinator has joined #openstack-meeting00:33
*** markvoelker2 has joined #openstack-meeting00:37
*** alexb_ has joined #openstack-meeting00:39
*** markvoelker1 has quit IRC00:41
*** welldannit has quit IRC00:42
*** rwsu is now known as rwsu-away00:42
*** SumitNaiksatam has joined #openstack-meeting00:43
*** mikal has joined #openstack-meeting00:45
*** spzala has joined #openstack-meeting00:46
*** colinmcnamara1 has joined #openstack-meeting00:51
*** bgorski has quit IRC00:51
*** colinmcnamara has quit IRC00:51
*** anniec has joined #openstack-meeting00:55
*** changbl has joined #openstack-meeting00:56
*** ujuc has joined #openstack-meeting00:56
*** jlucci has joined #openstack-meeting00:57
*** spzala has quit IRC00:57
*** sacharya has joined #openstack-meeting00:58
*** lexinator has left #openstack-meeting00:58
*** rongze_ has joined #openstack-meeting00:58
*** carlp has joined #openstack-meeting00:58
*** alexpilotti has quit IRC00:59
*** rongze has quit IRC00:59
*** carlp-away has quit IRC00:59
*** cyeoh__ has joined #openstack-meeting00:59
*** cyeoh_ has quit IRC01:01
*** colinmcnamara1 has quit IRC01:01
*** zaitcev has joined #openstack-meeting01:04
*** sjing has joined #openstack-meeting01:07
*** Mandell has quit IRC01:09
*** novas0x2a|laptop has quit IRC01:09
*** henrynash has quit IRC01:11
*** stevemar has joined #openstack-meeting01:11
*** jasondotstar has joined #openstack-meeting01:16
*** sarob_ has quit IRC01:19
*** gyee is now known as gyee_food01:22
*** sushils has quit IRC01:23
*** nati_ueno has quit IRC01:25
*** nati_ueno has joined #openstack-meeting01:26
*** dcramer_ has quit IRC01:27
*** markwash has joined #openstack-meeting01:28
*** malini is now known as malini_afk01:30
*** nati_ueno has quit IRC01:30
*** SumitNaiksatam has quit IRC01:32
*** sdake_ has quit IRC01:34
*** SumitNaiksatam has joined #openstack-meeting01:35
*** alexb_ has quit IRC01:43
*** stevemar has quit IRC01:50
*** jlucci has quit IRC01:51
*** cyeoh__ is now known as cyeoh01:51
*** dscannell has quit IRC02:01
*** Tross has quit IRC02:02
*** dscannell has joined #openstack-meeting02:04
*** edleafe- has quit IRC02:05
*** shang has joined #openstack-meeting02:05
*** edleafe has joined #openstack-meeting02:06
*** Tross has joined #openstack-meeting02:09
*** vkmc has quit IRC02:09
*** gongysh has joined #openstack-meeting02:10
*** sdake_ has joined #openstack-meeting02:11
*** fnaval_ has joined #openstack-meeting02:14
*** Tross has quit IRC02:17
*** Tross has joined #openstack-meeting02:20
*** anniec has quit IRC02:23
*** vipul has quit IRC02:35
*** vipul has joined #openstack-meeting02:35
*** shang has quit IRC02:44
*** jasondotstar has quit IRC02:50
*** gyee_food has quit IRC02:50
*** dscannell has joined #openstack-meeting02:56
*** shang has joined #openstack-meeting02:59
*** dscannell has quit IRC03:01
*** fifieldt has joined #openstack-meeting03:01
*** Tross has quit IRC03:06
*** leif has joined #openstack-meeting03:15
*** leif is now known as Guest8483803:15
*** shang has quit IRC03:18
*** neelashah has joined #openstack-meeting03:20
*** dscannell has joined #openstack-meeting03:34
*** sacharya has quit IRC03:35
*** Tross has joined #openstack-meeting03:40
*** gongysh has quit IRC03:41
*** markvoelker2 has quit IRC03:44
*** stevemar has joined #openstack-meeting03:44
*** zaitcev has left #openstack-meeting03:45
*** dcramer_ has joined #openstack-meeting03:49
*** gongysh has joined #openstack-meeting03:57
*** danwent has joined #openstack-meeting04:05
*** Tross has quit IRC04:06
*** jpeeler has quit IRC04:10
*** sjing has quit IRC04:10
*** jpeeler has joined #openstack-meeting04:10
*** neelashah has quit IRC04:20
*** tian has quit IRC04:30
*** yjiang5 is now known as yjiang5_away04:34
*** boris-42 has joined #openstack-meeting04:39
*** dcramer_ has quit IRC04:43
*** glikson has joined #openstack-meeting04:43
*** danwent has quit IRC04:45
*** danwent has joined #openstack-meeting04:49
*** branen has joined #openstack-meeting05:03
*** MIDENN_ has quit IRC05:03
*** KurtMartin has joined #openstack-meeting05:03
*** mdenny has joined #openstack-meeting05:03
*** kmartin has quit IRC05:04
*** branen_ has quit IRC05:04
*** dscannell has quit IRC05:13
*** Tross has joined #openstack-meeting05:15
*** SergeyLukjanov has joined #openstack-meeting05:16
*** michchap_ has joined #openstack-meeting05:19
*** Guest84838 has quit IRC05:19
*** michchap has quit IRC05:22
*** glikson has quit IRC05:30
*** Mandell has joined #openstack-meeting05:33
*** Tross has quit IRC05:34
*** Tross has joined #openstack-meeting05:37
*** glikson has joined #openstack-meeting05:38
*** danwent has quit IRC05:40
*** vuil has joined #openstack-meeting05:42
*** markpeek has quit IRC05:55
zynzelc05:55
zynzelwrong channel :)05:55
*** vuil has quit IRC06:00
*** mrunge has joined #openstack-meeting06:05
*** jhenner has joined #openstack-meeting06:11
*** stevemar has quit IRC06:14
*** alexb_ has joined #openstack-meeting06:14
*** jcoufal has joined #openstack-meeting06:15
*** glikson has quit IRC06:16
*** thomasbiege has joined #openstack-meeting06:18
*** thomasbiege has quit IRC06:22
*** alexb_ has quit IRC06:26
*** doron_afk has joined #openstack-meeting06:27
*** _ozstacker_ has quit IRC06:38
*** dkranz has quit IRC06:39
*** dkranz has joined #openstack-meeting06:41
*** glikson has joined #openstack-meeting06:45
*** flaper87|afk is now known as flaper8706:45
*** ozstacker has joined #openstack-meeting06:49
*** tkammer has joined #openstack-meeting06:53
*** sushils has joined #openstack-meeting06:57
*** Mandell has quit IRC06:58
*** afazekas has joined #openstack-meeting06:58
*** _ozstacker_ has joined #openstack-meeting07:05
*** _ozstacker_ has quit IRC07:06
*** ozstacker has quit IRC07:06
*** salv-orlando has joined #openstack-meeting07:10
*** egallen has joined #openstack-meeting07:11
*** sushils has quit IRC07:23
*** boris-42 has quit IRC07:24
*** jaimegil has joined #openstack-meeting07:25
*** shardy_afk is now known as shardy07:27
*** jtomasek has joined #openstack-meeting07:29
*** jtomasek_ has joined #openstack-meeting07:42
*** jtomasek has quit IRC07:43
*** yassine has joined #openstack-meeting07:53
*** yassine_ has joined #openstack-meeting07:54
*** yassine_ has quit IRC07:55
*** jhenner1 has joined #openstack-meeting08:03
*** ruhe has joined #openstack-meeting08:03
*** jhenner has quit IRC08:03
*** afazekas has quit IRC08:03
*** sushils has joined #openstack-meeting08:12
*** ndipanov_gone is now known as ndipanov08:14
*** thomasbiege has joined #openstack-meeting08:16
*** sushils has quit IRC08:17
*** sushils has joined #openstack-meeting08:18
*** jtomasek_ is now known as jtomasek08:20
*** ocozalp has joined #openstack-meeting08:21
*** derekh has joined #openstack-meeting08:21
*** thomasbiege has quit IRC08:23
*** ocozalp has left #openstack-meeting08:23
*** SergeyLukjanov has quit IRC08:24
*** henrynash has joined #openstack-meeting08:25
*** lsmola has quit IRC08:46
*** inkerra has quit IRC08:53
*** jhenner1 has quit IRC08:57
*** jhenner has joined #openstack-meeting08:58
*** lsmola has joined #openstack-meeting09:01
*** SergeyLukjanov has joined #openstack-meeting09:04
*** glikson_ has joined #openstack-meeting09:05
*** glikson has quit IRC09:06
*** glikson_ is now known as glikson09:06
*** afazekas has joined #openstack-meeting09:06
*** yaguang has joined #openstack-meeting09:15
*** rods1 has joined #openstack-meeting09:19
*** lsmola has quit IRC09:32
*** doron_afk is now known as doron09:37
*** boris-42 has joined #openstack-meeting09:37
*** doron is now known as doron_afk09:42
*** morganfainberg is now known as morganfainberg|a09:45
*** lsmola has joined #openstack-meeting09:46
*** bgorski has joined #openstack-meeting09:49
*** SergeyLukjanov has quit IRC09:54
*** SergeyLukjanov has joined #openstack-meeting09:59
*** pcm_ has joined #openstack-meeting10:05
*** yaguang has quit IRC10:05
*** pcm_ has quit IRC10:06
*** egallen has quit IRC10:06
*** pcm_ has joined #openstack-meeting10:06
*** bgorski has quit IRC10:20
*** bgorski has joined #openstack-meeting10:20
*** ruhe has quit IRC10:20
*** bgorski has quit IRC10:20
*** bgorski has joined #openstack-meeting10:21
*** bgorski_ has joined #openstack-meeting10:21
*** bgorski has quit IRC10:21
*** bgorski_ has quit IRC10:21
*** bgorski has joined #openstack-meeting10:21
*** bgorski has joined #openstack-meeting10:22
*** flaper87 is now known as flaper87|afk10:27
*** aguzikova has joined #openstack-meeting10:28
*** chuckieb has quit IRC10:41
*** mrunge has quit IRC10:42
*** mrunge has joined #openstack-meeting10:43
*** rdxc has joined #openstack-meeting10:43
*** flaper87|afk is now known as flaper8710:44
*** ujuc has quit IRC10:46
*** glikson_ has joined #openstack-meeting10:48
*** chuckieb has joined #openstack-meeting10:49
*** johnthetubaguy has joined #openstack-meeting10:49
*** glikson has quit IRC10:51
*** glikson_ is now known as glikson10:51
*** radsy has quit IRC10:55
*** gongysh has quit IRC10:57
*** ruhe has joined #openstack-meeting11:00
*** glikson_ has joined #openstack-meeting11:02
*** alexpilotti has joined #openstack-meeting11:04
*** glikson has quit IRC11:06
*** glikson_ is now known as glikson11:06
*** alexpilotti has quit IRC11:09
*** egallen has joined #openstack-meeting11:22
*** adalbas has joined #openstack-meeting11:28
*** glikson has quit IRC11:33
*** sacharya has joined #openstack-meeting11:41
*** glikson has joined #openstack-meeting11:45
*** markvoelker1 has joined #openstack-meeting11:47
*** sushils has quit IRC11:47
*** jhenner has quit IRC11:48
*** markvoelker1 has quit IRC11:48
*** flaper87 is now known as flaper87|afk11:52
*** zul has quit IRC11:55
*** ruhe has quit IRC11:59
*** afazekas has quit IRC12:02
*** ccorrigan has joined #openstack-meeting12:03
*** flaper87|afk is now known as flaper8712:07
*** gongysh has joined #openstack-meeting12:09
*** egallen has quit IRC12:10
*** egallen has joined #openstack-meeting12:10
*** noslzzp has joined #openstack-meeting12:13
*** jmh_ has joined #openstack-meeting12:14
*** afazekas has joined #openstack-meeting12:14
*** sacharya has quit IRC12:15
*** dvarga has joined #openstack-meeting12:18
*** eric-young has joined #openstack-meeting12:21
*** dprince has joined #openstack-meeting12:23
*** jaimegil has quit IRC12:27
*** pnavarro has joined #openstack-meeting12:36
*** anteaya has joined #openstack-meeting12:40
*** eharney has joined #openstack-meeting12:41
*** ruhe has joined #openstack-meeting12:44
*** dnavale has joined #openstack-meeting12:45
*** nmiller has joined #openstack-meeting12:45
*** afazekas has quit IRC12:46
*** woodspa has joined #openstack-meeting12:50
*** mrunge has quit IRC12:51
*** spzala has joined #openstack-meeting12:55
*** SergeyLukjanov has quit IRC12:56
*** jasondotstar has joined #openstack-meeting12:59
*** maurosr has quit IRC13:00
annegentleOk, who's here for the doc team meeting?13:00
EmilienMo/13:01
annegentleraise your hands, er slashes high!13:01
annegentle#startmeeting DocTeamMeeting13:01
openstackMeeting started Wed Aug 28 13:01:21 2013 UTC and is due to finish in 60 minutes.  The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: DocTeamMeeting)"13:01
openstackThe meeting name has been set to 'docteammeeting'13:01
annegentle#topic Action items from last week13:01
*** openstack changes topic to "Action items from last week (Meeting topic: DocTeamMeeting)"13:01
*** slong_ has joined #openstack-meeting13:01
annegentleroadnick to meet with Kersten to help through the WADL journey13:02
*** SergeyLukjanov has joined #openstack-meeting13:02
annegentleNick emailed his regrets that he couldn't attend so I don't know the status.13:02
*** radez_g0n3 is now known as radez13:02
annegentleannegentle codify our reviewing policies - done13:02
annegentleI do need to add that we don't require a bug for each patch submitted13:02
*** writerDiane has joined #openstack-meeting13:03
annegentle#action annegentle to clarify for reviewing policy whether we require a bug per patch13:03
annegentleNext action, sgordon propose more often meetings on -docs Mailing List - done.13:03
*** writerDiane is now known as dianefleming13:03
annegentleThough sgordon is still out this week13:03
*** brucer has joined #openstack-meeting13:03
annegentleBut, the ical feed is updated to every other Tuesday, we're just here this morning because a few of us missed it yesterday so I rescheduled.13:03
annegentle#topic Docs Boot Camp Sept 9-1013:03
*** openstack changes topic to "Docs Boot Camp Sept 9-10 (Meeting topic: DocTeamMeeting)"13:03
*** slong_ is now known as summerLong13:03
EmilienMannegentle: the meeting time stays wed 1pm UTC ?13:04
annegentleEmilienM: nope goes back to Tues13:04
annegentleEmilienM: this is a one-time move13:04
annegentlefor this week13:04
annegentle#link https://wiki.openstack.org/wiki/Docs_Bootcamp_201313:04
annegentleWe have nearly 25 people signed up. Great turnout.13:04
annegentleThe wiki page has instructions for what you should have set up on your laptop.13:05
annegentleThe schedule is shaping up to be half learn/labs, half unconference where we put up a board for future discussions.13:05
*** nmiller is now known as nerminamiller13:05
annegentleMirantis is taping the sessions and we'll post after camp.13:05
annegentleAny questions on Docs Boot Camp?13:06
*** radez is now known as radez_g0n313:06
nerminamillerannegentle: are all listed installs applicable to all attendees?13:06
annegentlewelcome nerminamiller and summerLong!13:06
summerLonghi!13:06
nerminamillerhi!13:06
annegentlenerminamiller: good question. I would consider the autodoc and publican to be optional13:06
annegentleoff the top of my head13:07
*** afazekas has joined #openstack-meeting13:07
nerminamillerthanks13:07
annegentleI'm getting excited to come to California13:07
annegentlefiguring out lunch, dinner, entertainment.13:08
annegentleOk on to13:08
annegentle#topic Admin guides13:08
*** openstack changes topic to "Admin guides (Meeting topic: DocTeamMeeting)"13:08
*** lblanchard has joined #openstack-meeting13:08
*** stevemar has joined #openstack-meeting13:08
annegentleI put this on there just to let people know the latest for the four we're parting out, and to see how a larger one looks.13:08
annegentleBlock Storage is already done, config moved to config, install to install.13:09
annegentleObject Storage is in progress.13:09
annegentleCompute Admin is pretty well parted out to user guide and config guide but more work needs to be done to delete outdated content.13:09
*** leif has joined #openstack-meeting13:10
*** fnaval_ has quit IRC13:10
annegentleNetwork Admin Guide hasn't been pieced out but I did talk to emagana about what goes where.13:10
*** leif is now known as Guest1465913:10
annegentlenerminamiller: how's the larger guide looking?13:10
*** stevemar has quit IRC13:10
annegentlenerminamiller: I haven't looked at the outline again since last week13:10
nerminamillerannegentle: the matchup with the blueprint is almost done.13:11
nerminamilleri took it offline to work on it.13:11
nerminamillerhope to replace it by cob today.13:11
annegentlenerminamiller: okie13:11
annegentlenerminamiller: are you thinking the Compute Admin guide "becomes" the OpenStack Admin guide?13:11
nerminamilleralso considering merge with ops guide. will propose in more detail in the blueprint.13:11
annegentlenerminamiller: or should I just wait for the blueprint :)13:12
nerminamillerre: compute = yes13:12
annegentlenerminamiller: ok good-o13:12
summerLongAnd don't touch compute until you're done...13:12
summerLongJust hit something with quotas...13:12
*** cppcabrera has joined #openstack-meeting13:12
annegentlesummerLong: oh it'll merge! :)13:12
annegentlesummerLong: I think13:12
annegentlesummerLong: so who shouldn't touch compute13:13
*** glikson has quit IRC13:13
nerminamillernot touching a thing :)13:13
summerLongBut the question is whether quota info will remain?13:13
annegentlesummerLong: oh yes it needs a home13:13
summerLongIs in admin user guide already.13:13
annegentlesummerLong: quotas and rate limiting I've seen in config ref too though, it's configuration.13:13
*** neelashah has joined #openstack-meeting13:13
summerLongAm doing xi includes from admin gd into project admin guides?13:14
*** zul has joined #openstack-meeting13:15
annegentlesummerLong: the idea is to make the project admin guides super small so that they could be xi:included into a larger admin guide (I think, correct me if that's wrong)13:15
*** doron_afk is now known as doron13:15
annegentlesummerLong: quota configuration is already out of the compute admin guide on the master branch13:15
*** shaunm has joined #openstack-meeting13:15
annegentlesummerLong: and into the config ref13:15
*** dguitarbite has joined #openstack-meeting13:15
*** radez_g0n3 is now known as radez13:16
annegentlesummerLong: is that crazy making?13:16
summerLongHmm, definitely13:17
annegentlesummerLong: oh dear13:17
summerLongIs now everywhere. It's in the admin user guide already. Had finished chapters on those (updated)13:17
summerLongNo problem with it not being in the project guides of course.13:18
annegentlesummerLong: if it's modular it's easy to move right13:18
summerLongYes.13:18
annegentlesummerLong: ohhhh right the admin user guide13:18
annegentlesummerLong: yes it makes sense for quota setting to be in there13:18
annegentlesummerLong: nerminamiller is outlining yet another admin guide13:18
*** sandywalsh has quit IRC13:18
annegentlesummerLong: so what you've done should stay, yes.13:18
annegentlethis kind of confusion is what I'm afraid of13:18
summerLongyes, the 'system' admin guide.13:19
annegentlebut -- I think there's good reason for an admin user guide13:19
summerLongBut would be good to have consistent info across guides.13:19
*** dkranz has quit IRC13:19
annegentlenerminamiller: be sure to read what is in the admin user guide13:19
annegentlesummerLong: yes13:19
nerminamillerwill do13:19
summerLongAnd I'll take a look at the config ref?13:19
annegentleso. Admin User Guide = Covers user tasks performed through the dashboard and CLIs for admin users.13:19
nerminamilleri'm looking at the ops as well13:19
annegentleAdministration Guide = Covers system administration tasks like maintaining, monitoring, and customizing an initially installed system. Could also be called "Cloud Administration Guide."13:20
annegentleI'm using shortened titles which is bad.13:20
annegentleSorry y'all.13:20
annegentlesummerLong: the config ref has quota info in it now, about how to configure, so do try to consolidate as needed.13:20
annegentlesummerLong: good catch13:20
summerLongOk, will do.13:20
annegentleWe could also call the Admin User Guide the User Guide for Administrators.13:21
annegentleOk any more questions13:21
annegentleon Admin Guides in all their glory?13:21
dianeflemingyes, i had a question about name for user guide for admins - the title13:21
*** doron is now known as doron_afk13:21
annegentledianefleming: sure13:21
dianeflemingwhat do people prefer 1) Admin User Guide 2) User Guide for Administrators13:22
dianeflemingI'm currently calling the regular User Guide -> End User Guide, but I could shorten to "User Guide"13:22
dianeflemingso we would have User Guide and User Guide for Administrators13:22
annegentleHm... thinking13:22
*** ruhe has quit IRC13:23
dianeflemingwe can discuss on docs list later - just throwing it out there13:23
summerLongSort of liked the earlier pairing of End User and Admin User guides.13:23
*** shang has joined #openstack-meeting13:23
annegentledianefleming: yeah it's a good question - I like Admin User Guide but I like shorter titles.13:23
brucerHm, I thnk having a guide name that is a subset of another guide name not such a good idea.13:23
dianeflemingI'm fine with End User Guide and Admin User Guide13:24
nerminamillerpoll users?13:24
annegentlebrucer: so no "User Guide for Administrators"13:24
*** timello_ is now known as timello13:24
dianefleming@brucer don't know what you mean13:24
bruceryeh, rather Admin UG and End UG13:24
nerminamilleragree with brucer13:25
dianeflemingthat's fine - I'll do that13:25
annegentledianefleming: ok good, you can definitely tell the ML and then if anyone hollers we'd reconsider but I think Admin UG and End UG13:25
annegentle#agreed Admin User Guide and End User Guide titles13:25
annegentleok, moving along13:25
annegentle#topic Install guides13:25
*** openstack changes topic to "Install guides (Meeting topic: DocTeamMeeting)"13:25
annegentleshaunm: I won't put you on the spot but I'll report what I know and you can chime in13:26
shaunmok13:26
*** vijendar has joined #openstack-meeting13:26
annegentleAfter several weeks trying to get some hardware from Cisco only to find out it is VMS they give out in their lab, shaunm is going to rig laptops for testing install instructions13:26
annegentlebasically, a laptop with a USB > Ethernet NIC added on works well for a 2 NIC "server"13:27
annegentleit's what the Rackspace training group uses for portability13:27
annegentleshaunm: you can add any other updates you have13:27
annegentleThere have been continual patches to the install guides13:29
shaunmthat's about it13:29
annegentleeven one came in yesterday that I'll backport to grizzly13:29
annegentleshaunm: are you going to submit a patch this week?13:29
annegentleshaunm: with a consolidated install guide?13:29
shaunmyes, though probably not complete13:30
annegentleshaunm: sure.13:31
annegentleThe install architectures are at https://etherpad.openstack.org/havanainstall13:31
annegentle#link https://etherpad.openstack.org/havanainstall13:31
annegentleany questions on install?13:31
*** sandywalsh has joined #openstack-meeting13:31
annegentleOk, going to translation13:32
annegentle#topic Translation builds13:32
*** openstack changes topic to "Translation builds (Meeting topic: DocTeamMeeting)"13:32
annegentlewe do have a reply from daisy on the mailing list13:32
annegentlesounds like they'd need a tools directory for each repository so that translated files can be sliced and built13:33
annegentleSounds like we still have work to do.13:33
*** sarob has joined #openstack-meeting13:33
annegentleI'm also working with Todd Morey, a designer at the Foundation, to ensure we do a good job with other-language landing pages for docs.13:33
annegentleAny questions on translation builds?13:34
summerLongHow many languages will be supported?13:34
summerLongOk, silly question.13:34
summerLongHow long is a piece of string.13:34
annegentlesummerLong: Long story, but basically we have the Ops Guide in Chinese and Japanese now13:35
annegentlesummerLong: heh13:35
annegentlesummerLong: well, yes, and also, the po files are available on Transifex for many many languages13:35
annegentlesummerLong: but we have 2 now13:35
nerminamillerplans for any other languages?13:35
*** fifieldt has quit IRC13:36
annegentlenerminamiller: you say "plans" :)13:36
nerminamiller:)13:36
annegentlenerminamiller: if you look at https://www.transifex.com/projects/p/openstack-manuals-i18n/resources/13:36
annegentlenerminamiller: you can see that there are five full translations of the API Quick Start13:36
annegentleChinese, Russian, Korean, Portuguese, Vietnamese13:37
annegentleThose are some of the most active language communities13:37
annegentleBut, that's also a very small guide.13:37
annegentleEvery Summit, we talk about their plans, I'm not saying it's not planned, just saying it's a huge coordination effort13:37
annegentleand we try to enable as much as we can13:37
annegentlewhile not slowing down English content dev.13:38
annegentleDoes that help?13:38
nerminamillerthanks13:38
*** malini_afk is now known as malini13:38
annegentleAny more questions on Translation? It's good for us all to know about the moving pieces and parts.13:38
annegentleOk, onward13:39
annegentle#topic Bugs and DocImpact13:39
*** openstack changes topic to "Bugs and DocImpact (Meeting topic: DocTeamMeeting)"13:39
annegentle#link https://launchpad.net/openstack-api-site/+milestone/havana13:39
annegentle#link https://launchpad.net/openstack-manuals/+milestone/havana13:39
annegentleI don't put this topic at the bottom of the agenda to de-emphasize its importance :)13:40
annegentleThere are 217 bugs targeted for admin/config/end users, and 72 targeted for API docs.13:40
annegentleThese are serious numbers.13:40
annegentleWe've done a great job getting the info and making it into data with DocImpact.13:40
*** zyuan_ has left #openstack-meeting13:41
annegentleSo keep looking at what you can do for doc bug fixes.13:41
annegentleAnd, recruit the dev who put DocImpact in the commit message to write docs.13:41
EmilienM+113:41
EmilienMit's a matter of education :)13:41
annegentleEmilienM: yep, and coaching to help them find the right place to put it now that we've done a lot of moving around.13:42
EmilienMsure13:42
annegentleThere are a lot of Fix Released on that list too13:42
*** doron_afk is now known as doron13:42
dianeflemingI'll try to knock out some of the api-site ones13:42
annegentledianefleming: ok thanks13:42
nerminamilleri'll commit to some this week as well13:42
annegentleThere are only 5 or 6 Triaged so even if all you can do is put a comment saying what to do to fix the bug, that's a help13:43
dianeflemingsure13:43
dianeflemingwill do13:43
annegentleTriaged means someone else can fix the bug with the info in the comments.13:43
*** fnaval_ has joined #openstack-meeting13:43
annegentleOk! Shall we go to Open Discussion?13:43
annegentle#topic Open discussion13:43
*** openstack changes topic to "Open discussion (Meeting topic: DocTeamMeeting)"13:43
EmilienMI would like to talk about openstack-ha guide13:43
EmilienM#link https://blueprints.launchpad.net/openstack-manuals/+spec/improve-high-availability-support13:43
EmilienM#link http://docs.openstack.org/trunk/openstack-ha/13:43
EmilienMI did not make a good progress this summer, but I'm on it right now.13:43
EmilienMI'm currently working on https://bugs.launchpad.net/openstack-manuals/+bug/119609913:43
EmilienMto bring neutron dhcp agent in HA, the doc is already here :13:43
annegentleEmilienM: go ahead13:43
*** joesavak has joined #openstack-meeting13:43
uvirtbotLaunchpad bug 1196099 in openstack-manuals "openstack-ha guide / Active-Active section: Miss Network section " [Wishlist,Confirmed]13:43
EmilienM#link http://docs.openstack.org/trunk/openstack-network/admin/content/demo_multiple_operation.html13:43
EmilienMmy question is: can I give basic explaining and redirect to the neutron doc ?13:43
EmilienM:)13:43
annegentleEmilienM: have you asked emagana if he's good with that? He's our doc liaison for Neutron13:44
annegentleEmilienM: does the Neutron doc have HA info?13:44
*** sacharya has joined #openstack-meeting13:44
EmilienMannegentle: I know him, I'm going to ping him13:44
annegentleEmilienM: ok, good.13:44
EmilienMannegentle: as I say, yes; for DHCP only.13:44
annegentleEmilienM: also is it known how to make neutron HA?13:44
annegentleEmilienM: oh ok.13:44
EmilienMmy second thing where I need help is that neutron does not provide yet active / active HA for some agents. You can run them by active / passive using Pacemaker / Corosync. So what I plan to do, is to write it in the active / passive sections, and document active / active in explaining that it's not supported yet, but they can have HA with active / passive (and refer to the AP section).13:45
EmilienMMake sense ?13:45
annegentleEmilienM: what is your sense of whether multi-host will make it into havana for neutron?13:45
*** michchap_ has quit IRC13:45
EmilienMannegentle: multihost is only for DHCP afik13:45
annegentleEmilienM: Yes, I think it's best to indicate where active/active is NOT available13:45
annegentleEmilienM: ok13:45
*** michchap has joined #openstack-meeting13:45
*** topol has joined #openstack-meeting13:45
EmilienMannegentle: L3, metadata, lbaas aren't scalable yet13:45
EmilienMok.13:46
annegentleEmilienM: ok, and L3 is nearly always what users are after it would seem13:46
EmilienMeverything is fine for me, let's go to work now :)13:46
annegentleEmilienM: sweet13:46
EmilienMthx annegentle13:46
annegentleI wanted to point out a Marketing portal is available13:46
annegentle#link http://www.openstack.org/marketing13:46
*** burt has joined #openstack-meeting13:46
annegentleAlso I'm attending once-monthly content meetings with Foundation staff, went to the first one last week.13:46
*** safchain has joined #openstack-meeting13:47
*** markpeek has joined #openstack-meeting13:47
annegentleDiscussing what content needs created, prioritizing it and finding resources.13:47
*** sushils has joined #openstack-meeting13:47
annegentleLast week was a chance to get to know each other, there were mostly company reps.13:47
annegentleWe should be getting first-run tshirts at docs boot camp, woo13:48
annegentleI think that's it! Anyone else?13:48
sarobNope13:48
annegentlesarob: lurk!13:48
annegentle:)13:48
sarob;)13:49
annegentleOk take back 11 minutes of your day!13:49
annegentle#endmeeting13:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:49
openstackMeeting ended Wed Aug 28 13:49:10 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-08-28-13.01.html13:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-08-28-13.01.txt13:49
openstackLog:            http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-08-28-13.01.log.html13:49
EmilienMgood day all !13:49
*** summerLong has left #openstack-meeting13:49
EmilienMannegentle: next meeting on next tuesday ?13:49
*** dnavale has left #openstack-meeting13:49
annegentleEmilienM: So, the next meeting time would be during boot camp.13:50
annegentlehttps://www.google.com/calendar/ical/bj05mroquq28jhud58esggqmh4@group.calendar.google.com/public/basic.ics13:50
EmilienMnice13:50
annegentleEmilienM: Sept. 8th.13:50
EmilienMenjoy the boot camp !13:50
*** spenceratx has joined #openstack-meeting13:50
annegentleEmilienM: I'll send a note out to the mailing list -- good reminder! Thanks.13:50
EmilienM:)13:50
*** dianefleming has left #openstack-meeting13:50
*** changbl has quit IRC13:50
*** ruhe has joined #openstack-meeting13:51
*** nerminamiller has left #openstack-meeting13:51
*** maurosr has joined #openstack-meeting13:52
*** brucer has quit IRC13:53
*** ivasev has joined #openstack-meeting13:54
*** doron is now known as doron_afk13:56
*** jlucci has joined #openstack-meeting13:56
*** rkukura has joined #openstack-meeting13:56
*** ruhe has quit IRC13:57
*** malini has left #openstack-meeting13:58
*** meganw has joined #openstack-meeting13:58
*** apech has joined #openstack-meeting13:59
*** dscannell has joined #openstack-meeting13:59
*** lblanchard has quit IRC13:59
*** sukhdev has joined #openstack-meeting13:59
rkukurahello14:00
*** matrohon has joined #openstack-meeting14:00
*** sarob has quit IRC14:01
sukhdevgood morning14:01
*** rcurran has joined #openstack-meeting14:01
*** ruhe has joined #openstack-meeting14:01
rkukuralets get started14:01
*** rods1 has quit IRC14:01
rkukura#startmeeting networking_ml214:01
openstackMeeting started Wed Aug 28 14:01:54 2013 UTC and is due to finish in 60 minutes.  The chair is rkukura. 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: networking_ml2)"14:01
openstackThe meeting name has been set to 'networking_ml2'14:01
rkukura#link https://wiki.openstack.org/wiki/Meetings/ML2 Agenda14:02
rkukuramestery is on vacation, so I'll do my best to run the meeting14:02
*** shaunm has left #openstack-meeting14:02
rkukurawho do we have?14:03
rcurranrcurran14:03
apechapech14:03
sukhdevsukhdev14:03
*** lblanchard has joined #openstack-meeting14:03
*** lblanchard has joined #openstack-meeting14:04
rkukura#topic Blueprints14:04
*** openstack changes topic to "Blueprints (Meeting topic: networking_ml2)"14:04
*** ruhe has quit IRC14:04
*** lblanchard has quit IRC14:04
*** lblanchard has joined #openstack-meeting14:04
rkukuraBP implementation proposal deadline was last Friday14:04
rkukuraBP implementation merge deadline is end-of-day next Tuesday, August 3rd14:05
rkukuraThere were a couple of recent ML2 merges:14:05
rkukurahttps://bugs.launchpad.net/neutron/+bug/119696314:05
uvirtbotLaunchpad bug 1196963 in neutron "Update the OVS agent code to program tunnels using ports instead of tunnel IDs" [Wishlist,Fix committed]14:05
rkukurahttps://review.openstack.org/#/c/43678/14:06
*** lblanchard has quit IRC14:06
rkukurathe above is: https://blueprints.launchpad.net/neutron/+spec/ml2-mechanism-driver-subnet-calls14:06
*** dscannell has quit IRC14:07
*** dcramer_ has joined #openstack-meeting14:07
rkukuraSo we now have the subnet-related calls on mechanism drivers, thanks to Zng MingJie14:07
*** amotoki_ has quit IRC14:07
apechgreat!14:08
sukhdevit seems it changes the context in the calls to mech drivers14:08
rkukuraThis merge also added @property to the context class property calls14:08
*** lblanchard has joined #openstack-meeting14:08
*** _TheDodd_ has joined #openstack-meeting14:09
rkukurasukhdev: Right. Hopefully this isn't too much of a problem for the drivers currently in review.14:09
rkukuraIt does require rebasing them, and removing the "()" from usage of the properties.14:09
*** otherwiseguy has joined #openstack-meeting14:09
*** rnirmal has joined #openstack-meeting14:09
sukhdevsounds good14:10
rkukuraAnything else related to recent merges?14:10
rkukuraSo we now have 5 BPs in review targeting H-3, and a few other things we should track14:11
*** nevrax has joined #openstack-meeting14:11
rkukurahttps://blueprints.launchpad.net/quantum/+spec/ml2-portbinding is in review at https://review.openstack.org/#/c/43129/14:12
rkukuraI've gotten some good feedback from reviews, and will post an updated patch very soon today rebasing and addressing the nits14:13
*** _TheDodd_ has quit IRC14:13
*** thomasbiege has joined #openstack-meeting14:13
rkukuraI'll need a bit more time to resolve a couple more significant items:14:14
rkukuraDB migration and duplication among the agent-based mech drivers were both identified in the reviews14:14
sukhdevI created a bug to integrate with this after the merge14:15
*** rods1 has joined #openstack-meeting14:15
rkukuraI also discovered at the last minute that the hyperv-agent does not yet implement the agents-db functionality, so it seems we should add that, or not claim to support hyperv14:15
*** annegentle has quit IRC14:15
rkukuraany thoughts on hyperv?14:16
rcurranno14:16
sukhdevno14:16
*** nevrax has left #openstack-meeting14:16
rkukuraI'm going to try to get one of its developers to test it with ml2.14:17
rkukuraOther main portbinding issue is how to get the host-id for ports of L3, DHCP, etc. agents?14:17
rkukuraSeems cleanest to have those agents set binding:host_id when they create/update their ports14:18
sukhdevyes, we need host-id for dhcp14:18
sukhdevpresently, there is no host-id when a dhcp call is invoked14:19
rkukurathe alternative is for the RPC code to take the agent-id and look it up in the agents-db to find the agent's host14:19
*** danwent has joined #openstack-meeting14:19
rkukuraany preferences between these approaches, or other ideas?14:19
sukhdevcleaner will be if it provided via port context to mech drivers14:19
*** thedodd has joined #openstack-meeting14:20
rkukurasukhdev: in either approach it would be in the port dictionary as binding:host_id14:20
rkukuraanything else on ml2-portbinding?14:21
sukhdevah OK - in that case I OK with either approach14:21
rkukuraOK14:22
*** doron_afk is now known as doron14:22
*** AlanClark has joined #openstack-meeting14:22
*** rwsu-away is now known as rwsu14:23
rkukuramestery posted implementation of https://blueprints.launchpad.net/neutron/+spec/ml2-multi-segment-api14:23
rkukurahttps://review.openstack.org/#/c/43569/14:23
*** jecarey has joined #openstack-meeting14:23
rkukurahas anyone had a chance to look at this in detail yet?14:23
apechnot yet14:24
rcurranno14:24
sukhdevno14:25
*** annegentle_ has joined #openstack-meeting14:25
rkukuraLets try to get him some feedback before he's back online, which I think will be sometime later this week14:25
sukhdevhe is back on 9/314:26
rkukuraAnything else on multi-segment-api?14:26
apechgeneral question - what's the cutoff date for all changes?14:26
rkukurasukhdev: I got the impression he may be available to update this before then, but I'm not sure14:26
apechwe have a few significant blueprints coming in that will change our mechanism drivers14:26
apechtrying to understand our timeline14:26
rkukuraI believe the BP implementations need to be merged by end-of-day 9/3 - next Tuesday.14:27
rcurranlot of  balls in the air between now and then14:28
rkukuraThere will still be opportunity for bug fixes, so if drivers needs additional updates to support multiple segments, that could be done after 9/314:28
rkukurarcurran: agreed14:28
apechok got it14:29
rkukurabut I don't think 5 merges is unreasonable with 3 of them being drivers that shouldn't effect other merges14:29
rcurranglad to read to state that :-)14:29
rkukuraSo lets discuss https://blueprints.launchpad.net/neutron/+spec/arista-ml2-mechanism-driver14:30
rkukuralhttps://review.openstack.org/#/c/41213/14:30
rkukuralink: https://review.openstack.org/#/c/41213/14:31
sukhdevI sent out an email yesterday in response to your comments14:31
rkukurasukhdev: and I tried to summarize that in the agenda14:31
sukhdevdoes that sound reasonable?14:31
rkukuraI think so14:31
*** yassine has quit IRC14:31
rkukuraWe need to document that single physical network limitation in the README and wiki14:32
*** yassine_ has joined #openstack-meeting14:32
*** glikson has joined #openstack-meeting14:32
*** IlyaE has joined #openstack-meeting14:32
sukhdevDid you look at the wiki, I mentioned this in the overview section14:32
*** Guest14659 has quit IRC14:32
sukhdevwill mention in the readme as well14:32
rkukuraI took a quick look - must have missed it - sorry14:33
rkukuragreat14:33
sukhdevSo, I will upload a new patch which will rebase based upon the latest merge and new readme file - but, no other changes - are you OK with that?14:34
rkukuraI think the redundant DB state is justified for now, given that there is no reasonable way to sync state without it, but we should look for a good general solution for this in icehouse14:34
sukhdevI agree14:34
rkukurasukhdev: I'm OK with that, as long as all review issues have been addressed14:34
sukhdevI have addressed all other issues14:35
sukhdevunless - a new one pops up :-)14:35
rkukurasukhdev: It woudn't hurt to include some of the email text in the review so others can see14:35
rkukuraSeems the Arista driver is on track to merge - anything else on this?14:36
rkukuraNext is the Cisco Nexus driver14:36
*** michchap has quit IRC14:36
rkukuralink: https://blueprints.launchpad.net/quantum/+spec/ml2-md-cisco-nexus14:36
rcurran2nd patch went up friday14:36
rkukuralink: https://review.openstack.org/#/c/43196/14:36
*** thedodd has quit IRC14:36
rcurranstill had an issue w/ one of the UTs14:36
rcurrani think this has been fixed (rkukura: has dane leblanc reached out to you?)14:37
*** tkammer has quit IRC14:37
rkukurarcurran: not that I recall14:37
*** thedodd has joined #openstack-meeting14:37
rcurranok, that may be coming ... he was having an issue that may require an update to core ml2 code14:38
rcurranregarding db duplication14:38
rkukurarcurran: is that related to the UT failure?14:38
rcurranyes14:38
rcurrandane is working on ml2 cisco nexus ut14:38
*** sarob has joined #openstack-meeting14:39
*** yaguang has joined #openstack-meeting14:39
*** BobBall has joined #openstack-meeting14:39
rkukuraOK, so hopefully we can work through this quickly and get an updated patch set14:39
rcurranyes14:39
rcurrandb duplication14:39
*** thedodd has quit IRC14:39
rcurranyou'll see this in the ml2 cisco nexus driver also. this is because the code is mostly a port from the current plugins/cisco14:40
*** thedodd has joined #openstack-meeting14:40
rcurrani think we decided a while ago that plugins/ml2 drivers shouldn't import modules from another plugin14:40
rkukurarcurran: OK, so this is code duplication with the cisco plugin?14:41
rcurranbut because cisco doesn't want to supprot duplicate code we'll thinking in the icehouse timeframe to have the cisco plugin import the ml2 code14:41
*** wolfdreamer has joined #openstack-meeting14:41
rcurraneventurally (if all goes as planned) the plugin/cisco code gets deprecated and we only have ml2 left14:41
rcurranwe can then clean up the duplicated db stuff14:42
rkukurasounds good to me - a README on the cisco driver would be helpful, especially setting expectations relative to the cisco plugin14:42
*** sacharya has quit IRC14:42
rkukuraREADME/wiki14:42
rcurranyeah, i saw that comment coming :-)14:42
rkukuraI'll definitely review the upcoming patch14:43
rkukuraanything else on this one?14:43
rkukuraSo Tail-f is next14:43
*** dkranz has joined #openstack-meeting14:44
rkukuralink: https://blueprints.launchpad.net/quantum/+spec/tailf-ncs14:44
rkukuralink: https://review.openstack.org/#/c/37647/14:44
*** salv-orlando has quit IRC14:44
rkukuraIs Luke here?14:46
*** hartsocks has joined #openstack-meeting14:46
rkukuraThis needs to be rebased and a couple nits fixed14:48
*** jjacob512 has joined #openstack-meeting14:48
*** sarob has quit IRC14:48
rkukuraI haven't looked this too closely, but will. It seems to be on track14:48
rkukuraanything else on tail-f?14:49
rkukurahas anyone been tracking the PXE work?14:50
rkukuralink: https://blueprints.launchpad.net/neutron/+spec/pxeboot-ports14:50
rkukuralink: https://review.openstack.org/#/c/30441/14:50
*** changbl has joined #openstack-meeting14:51
rkukuraThis adds an extension to openvswitch, and I had commented a while back that it should address ml2 as well14:51
*** Guest79474 has quit IRC14:51
rkukuradkehn: Are you online?14:51
dkehnyes14:51
rkukuraAre you planning to add ml2 support to the PXE boot patch?14:52
dkehnyes, agreed on the ml2, what markmcclain and others have agreed upon is after the patch lands we will add ml2 support in14:52
dkehnhttps://review.openstack.org/#/c/30441/, see lifeless comments14:53
rkukuraOK, I guess we can treat that as a bug fix and git it in H-314:53
rkukuraLooks like the plan is to do that in icehouse14:53
dkehncorrect14:54
rkukuraI guess that will do, but we've been trying to keep parity with openvswitch so it can be deprecated14:56
rkukuradkehn: I may followup with you offline14:56
dkehnrkukura, sounds good14:57
rkukuraLast BP items are devstack and documentation. Any updates on these?14:57
*** ruhe has joined #openstack-meeting14:58
apechI had volunteered to help, mestery was going to reach but I didn't hear anything14:59
apechreach out that is14:59
rkukuraLets focus on those, plus any bugs, next week then14:59
*** thomasbiege has quit IRC14:59
rkukurafeleouet doesn't seem to be online - anyone have any update on l2-population?15:00
safchainHi15:00
safchainon my side I'll submit a new patch for l2population, with an implementation as Mechanism Driver15:00
rkukurasafchain: I assume this will be targeting icehouse, right?15:01
rkukuraOut time is up. Thanks everyone!15:01
safchainprobably, but I'll do my best for H515:02
safchainH315:02
sukhdevthanks15:02
*** thomasbiege has joined #openstack-meeting15:02
rkukuraOK, lets get these reviews and merges done15:02
rkukura#endmeeting15:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:02
openstackMeeting ended Wed Aug 28 15:02:55 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-08-28-14.01.html15:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-08-28-14.01.txt15:02
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-08-28-14.01.log.html15:03
*** thomasbiege has quit IRC15:03
johnthetubaguy#startmeeting: XenAPI15:03
openstackMeeting started Wed Aug 28 15:03:15 2013 UTC and is due to finish in 60 minutes.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: : XenAPI)"15:03
openstackThe meeting name has been set to '__xenapi'15:03
*** matel has joined #openstack-meeting15:03
*** thomasbiege has joined #openstack-meeting15:03
*** dscannell has joined #openstack-meeting15:03
*** jsavak has joined #openstack-meeting15:03
BobBallMorning15:04
BobBallI'm here15:04
BobBallMatel too15:04
BobBallEuan is at his desk and can be pulled in15:04
*** tanisdl has quit IRC15:04
johnthetubaguysorry, I got the wrong name somehow15:04
BobBallRoll call over :)15:04
johnthetubaguy#endmeeting15:04
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:04
openstackMeeting ended Wed Aug 28 15:04:32 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/__xenapi/2013/__xenapi.2013-08-28-15.03.html15:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/__xenapi/2013/__xenapi.2013-08-28-15.03.txt15:04
openstackLog:            http://eavesdrop.openstack.org/meetings/__xenapi/2013/__xenapi.2013-08-28-15.03.log.html15:04
johnthetubaguy#startmeeting XenAPI15:04
openstackMeeting started Wed Aug 28 15:04:40 2013 UTC and is due to finish in 60 minutes.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.15:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:04
*** openstack changes topic to " (Meeting topic: XenAPI)"15:04
openstackThe meeting name has been set to 'xenapi'15:04
*** tanisdl has joined #openstack-meeting15:04
johnthetubaguyso, hello all15:04
BobBallWeird.15:04
*** apech has quit IRC15:04
johnthetubaguyusual agenda OK for everyone?15:05
*** richardwoo has joined #openstack-meeting15:05
johnthetubaguynothing big from me, other people got things to discuss?15:05
BobBallyup15:05
mateluh15:05
*** flaper87 is now known as flaper87|afk15:06
johnthetubaguy#topic actions from last meeting15:06
*** openstack changes topic to "actions from last meeting (Meeting topic: XenAPI)"15:06
matelI just updated my patches, and I am planning to look at other xenapi patches, maybe that helps for reviewers.15:06
*** jmontemayor has joined #openstack-meeting15:06
johnthetubaguyBobBall: did you look into that VDI.copy issue?15:06
BobBalldo you mean whether we need safe_copy_vdi15:06
*** galstrom_zzz is now known as galstrom15:06
johnthetubaguyyep15:07
*** joesavak has quit IRC15:07
*** leif has joined #openstack-meeting15:07
*** rcurran has quit IRC15:07
*** leif is now known as Guest2098715:07
BobBallno - but one sec15:07
BobBallcarry on with otehrs then I might have one!15:08
johnthetubaguyOK… will put down action for next time15:08
johnthetubaguy#action BobBall look into VDI.copy workaround and if it is still needed or not15:08
johnthetubaguyseems like its probably because of parallel VDI.copy or something like that15:08
johnthetubaguyanyways, moving on15:08
johnthetubaguy#topic Blueprints15:09
*** openstack changes topic to "Blueprints (Meeting topic: XenAPI)"15:09
johnthetubaguyany news here15:09
johnthetubaguymatel: you said about patches15:09
matelyes.15:09
*** whenry has quit IRC15:10
matelI updated all patches related to https://blueprints.launchpad.net/nova/+spec/xenapi-supported-image-import-export15:10
matelWhat's the question?15:11
*** thomasbiege has quit IRC15:11
johnthetubaguyah, thats all15:11
johnthetubaguycool15:11
johnthetubaguyno more for blueprints I guess15:12
johnthetubaguy#topic Docs15:12
*** openstack changes topic to "Docs (Meeting topic: XenAPI)"15:12
matelDon't think so15:12
johnthetubaguyany docs updates15:12
johnthetubaguy?15:12
matelI plan to finish the doc scanning this week.15:12
matelNeed to look at where we are with the re-structure.15:12
johnthetubaguycool15:13
johnthetubaguygood to get that looked over again15:13
*** meganw has quit IRC15:13
matelI think the main re-structure change has been merged, so that should not block.15:14
johnthetubaguycool15:14
johnthetubaguy#topic Bugs and QA15:14
*** openstack changes topic to "Bugs and QA (Meeting topic: XenAPI)"15:14
*** meganw has joined #openstack-meeting15:14
johnthetubaguyany bug questions or QA updates?15:14
matelI kill a bug whenever I find one.15:14
BobBallI guess we should have a QA update15:15
*** sacharya has joined #openstack-meeting15:15
*** branen_ has joined #openstack-meeting15:15
BobBallSmokestack has been struggling occasionally under the weight of reviews15:15
BobBallparticularly the 4 XS hosts15:15
johnthetubaguydon't forget the xenserver tag, an I will triage the bug ASAPI15:15
BobBallIn fact, for a short period, the XS jobs were disabled15:15
matelAre we adding more resources?15:15
BobBallI've prototyped a cloud-based XS installation15:15
BobBallwhich mostly works15:15
matelHow beefy is the VM?15:16
BobBallalthough yesterday Dan raised a concern with one of the tests and I'm not sure if itw as a code issue or an infrastructure issue15:16
BobBallbeefyish15:16
BobBallbut the problem is CPU15:16
BobBallsingle CPU speed15:16
johnthetubaguyhow much are you doing in a run? building the DomU?15:16
BobBallThat can't be increased unfortunately so it does run slower (about 10 mins slower) in a VM in RAX cloud rather than hardware15:17
BobBallthat's 30 minutes vs 2015:17
BobBallNo - this is just smokestack15:17
BobBallso not devstack at all15:17
johnthetubaguyah, I guess thats to be expected for nested virt?15:17
BobBallperhaps yes15:17
BobBallbut the real problem is that the virt is HVM and can't use PV drivers15:17
johnthetubaguyright, but that shouldn't hit CPU usage?15:18
BobBallbecause we can only use one xenstore (which must be for the nested VMs) therefore XS can't use PV disk/network15:18
BobBallso it's all emulated15:18
*** branen has quit IRC15:18
matel150% - I wasn't expecting this much overhead.15:18
BobBallhence using CPU :)15:18
*** jtomasek has quit IRC15:19
*** meganw has quit IRC15:19
johnthetubaguyah, OK, still a bit surprising high15:19
matelShould we try putting it to KVM?15:19
BobBallI've considered it, but I want to get it working right on Xen first15:19
BobBallsince that's what we know15:19
johnthetubaguylol, same issue on KVM I would guess?15:19
BobBallif we can push it to the HP cloud then that's based on KVM and we could use virtio to boost performance15:20
matelsure, I was just curious what would be the overhead there.15:20
johnthetubaguyah, I see15:20
BobBall(I think)15:20
BobBallalthough that's more work than I've got time to do ATM15:20
BobBalland I don't have an HP account ;)15:20
*** martine has joined #openstack-meeting15:20
*** martine is now known as Guest4062915:21
johnthetubaguyanyways, I guess running in Dom0 might be faster in that setup, because the inner VM is less hampered by performance?15:21
*** Guest40629 is now known as martine_15:21
BobBallish15:22
BobBallbut I think the real problem is Xen being HVM with no PV drivers15:22
antonymhow large is the instance?15:22
matelBob, 30 min is the test run, or it's the whole stuff with the setup?15:22
johnthetubaguyis it not because you are running rabbit and mysql inside a VM thats inside a VM?15:22
*** pentameter has joined #openstack-meeting15:23
matelwould be nice to do some profiling to see what slows us down.15:23
*** dguitarbite has quit IRC15:23
*** meganw has joined #openstack-meeting15:23
johnthetubaguymatel: +115:23
BobBallwhole stuff15:23
*** rnirmal has quit IRC15:23
*** vincent_hou has joined #openstack-meeting15:23
matelBob: how much is the setup part, and how much time does the test run take?15:24
*** rnirmal has joined #openstack-meeting15:24
BobBallI agree that'd be nice15:24
BobBalldunno :)15:24
BobBallonly have the initial results from running it once yesterday15:24
matelHow larg is the instance?15:24
BobBall8GB15:24
*** euanh has joined #openstack-meeting15:24
BobBallbut you can get any instance size you like15:24
antonymso you have 4 vcpus at least15:24
BobBallsure - but most of the work is single threaded15:25
antonymyeah15:25
*** bill has joined #openstack-meeting15:25
BobBallI think15:25
*** bill is now known as Guest8537415:25
BobBallit's a shame dprince isn't online atm15:25
BobBalloh hang on15:25
BobBallmaybe he is15:25
dprinceBobBall: I'm here... just on a call.15:25
BobBalloh15:25
BobBallok15:26
johnthetubaguyyeah, I suspect the work going on inside the DomU is really slowed down because its in a nested VM, which has super sucky performance15:26
BobBallbut it shouldn't be15:26
BobBalldon't forget it's running PV15:26
BobBallso it's only PV in one HVM container15:26
BobBallso CPU performance should be no worse than one HVM15:26
BobBallit doesn't need to trap the hypercalls etc (I think)15:27
antonymwould it run better on certain versions of xs?15:27
BobBallNot sure - I'd need to ask about the version of Xen and whether it'd affect the pefromance nested15:28
BobBallbut there may be things we can do - e.g. modifying smokestack to make less use of disk15:28
antonymif it does, we should be able to help resolve that15:28
BobBallyeah15:28
BobBallit's a bit rubbish if the real restriction is that we can't have Xen using PV drivers though...15:29
antonymat least it works :) should be able to optimize from there hopefully15:29
*** dkranz has quit IRC15:29
BobBalland it's in the cloud - so we can just scale out, right? ;)15:29
antonymof course!15:29
johnthetubaguyhttp://www.slideshare.net/xen_com_mgr/nested-virtualization-update-from-intel15:30
BobBallUnfortunately one problem is that the gate is now running jobs in parallel15:30
BobBallso should be a lot faster15:30
*** vijendar has quit IRC15:30
johnthetubaguyfrom those slides, looks like some recent work really helped15:31
johnthetubaguynot sure what version of Xen that maps to15:31
matelSlides are a year old.15:32
BobBallI'll look into that15:32
matelRead the comment :-)15:32
BobBallnice comment :)15:33
antonymheh15:33
BobBallNot sure if it'll help though - might be intel specific - we'll see.15:33
BobBallI'll investigate a bit15:33
BobBallgimme an action!15:33
BobBallbrb.15:33
johnthetubaguyyes, good points15:33
johnthetubaguyit could be nested virt on AMD performance issues15:33
johnthetubaguyanyways, lets move onwards15:33
matelsure15:34
johnthetubaguy#topic Open Discussion15:34
*** openstack changes topic to "Open Discussion (Meeting topic: XenAPI)"15:34
johnthetubaguyany more things people want to cover?15:34
johnthetubaguywill wait for BobBall to return an confirm, I think he had something else15:34
matelLet's review each other's changes, that's all.15:34
*** pycabrera has joined #openstack-meeting15:35
johnthetubaguyindeed, much reviewing to be done all around15:35
BobBallnothing else15:36
BobBalloh yes15:36
BobBallthat's it15:36
BobBallreviews15:36
BobBallwe need another core :)15:36
*** flaper87|afk is now known as flaper8715:36
BobBallchanges with +2 should just be able to go in I hope15:36
BobBallI've got a few of them15:36
BobBallshould I just add ppl to my review? or is there a better way to encourage them?15:36
*** stevemar has joined #openstack-meeting15:37
matelI guess everyone is busy these days.15:37
johnthetubaguycatch people on IRC I guess, but mostly I think people are working on the priority of the blueprints15:37
*** cppcabrera has quit IRC15:37
johnthetubaguyI have lots of changes pending myself (14)15:37
matelyes, I will look at them15:38
*** rkukura has left #openstack-meeting15:38
*** whenry has joined #openstack-meeting15:38
BobBallok15:39
BobBallare we done then15:39
matelCool, thanks.15:39
johnthetubaguythanks all15:39
johnthetubaguy#endmeeting15:39
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:39
openstackMeeting ended Wed Aug 28 15:39:44 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-08-28-15.04.html15:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-08-28-15.04.txt15:39
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-08-28-15.04.log.html15:39
*** jcoufal has quit IRC15:39
*** zul has quit IRC15:41
*** euanh has left #openstack-meeting15:41
*** jdurgin1 has joined #openstack-meeting15:42
*** BobBall has left #openstack-meeting15:42
*** dkranz has joined #openstack-meeting15:43
*** danwent has quit IRC15:44
*** sacharya has left #openstack-meeting15:45
*** joel-coffman has joined #openstack-meeting15:47
*** zhiyan has joined #openstack-meeting15:47
*** sacharya has joined #openstack-meeting15:49
*** sukhdev has quit IRC15:50
*** doron is now known as doron_afk15:50
*** ruhe has quit IRC15:52
*** edgarstp has joined #openstack-meeting15:52
*** jrodom has joined #openstack-meeting15:53
*** burt has quit IRC15:56
*** KurtMartin is now known as kmartin15:57
*** winston-d has joined #openstack-meeting15:57
*** reed has joined #openstack-meeting15:57
*** kartikaditya has joined #openstack-meeting15:57
*** gyee has joined #openstack-meeting15:58
*** changbl has quit IRC15:59
*** avishay has joined #openstack-meeting15:59
*** galstrom is now known as galstrom_zzz15:59
*** skolathu has joined #openstack-meeting15:59
*** caitlin-nexenta has joined #openstack-meeting15:59
*** jungleboyj has joined #openstack-meeting15:59
*** pycabrera is now known as cppcabrera16:01
*** bswartz has joined #openstack-meeting16:01
*** glikson has quit IRC16:02
jgriffithCinder??16:02
winston-dhi16:02
avishayCinder!!16:02
jjacob512Hello16:02
jgriffith#start meeting cinder16:03
winston-djjacob512: jacob from dell?16:03
jjacob512yes!16:03
jgriffith#startmeeting cinder16:03
openstackMeeting started Wed Aug 28 16:03:15 2013 UTC and is due to finish in 60 minutes.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:03
*** openstack changes topic to " (Meeting topic: cinder)"16:03
openstackThe meeting name has been set to 'cinder'16:03
bswartzjgriffith: every time16:03
*** bpb has joined #openstack-meeting16:03
kmartinhello16:03
jgriffithbswartz: makes ya wonder if I do it on purpose :)16:03
winston-djjacob512: good. thx for joining.16:03
bswartzI think you do16:03
* jgriffith makes a note to submit a code change to IRC16:03
zhiyanhi16:03
jjacob512thanks16:03
jgriffithOk, short agenda, but I'm sure we'll make up for it like we usually do: https://wiki.openstack.org/wiki/CinderMeetings16:04
avishaybswartz: wait till he tries to end the meeting... ;)16:04
jgriffithavishay: :)16:04
jgriffith#topic blueprints16:04
*** openstack changes topic to "blueprints (Meeting topic: cinder)"16:04
bswartzavishay: maybe we can modify the bot before the meeting ends16:04
avishaybswartz: :)16:04
jgriffithSo I just wanted to give a heads up that for I release, I'm thinking we should go back to being pretty strict with our BP's16:05
jgriffithThat means having *real* details of what the BP is16:05
jgriffithIncluding a specs page16:05
jgriffithand a user story etc16:05
*** jmh_ has quit IRC16:05
jgriffithguess jmh_ didn't like that16:05
*** changbl has joined #openstack-meeting16:05
avishayhaha16:06
DuncanT-ug, sorry I'm late16:06
jgriffithDuncanT-: you dind't miss much16:06
jgriffithThat's all I had on that16:06
avishaySounds good16:06
jgriffithIt'll sort of fall into place when folks submit BP's16:06
bswartzjgriffith: I can't see any counter argument, other than laziness, so +116:07
jgriffithavishay: you ready?16:07
jgriffithbswartz: HA!16:07
avishayjgriffith: for?16:07
DuncanT-I'm a supporter, even if I'll probably be bitten by it16:07
jgriffithbswartz: indeed, I think that is the only counter16:07
jgriffithavishay: DOH!16:07
jgriffithI meant winston-d16:07
winston-dyup16:07
jgriffithavishay: sorry16:07
jgriffith#topic Feature submission exception16:08
*** nati_ueno has joined #openstack-meeting16:08
*** openstack changes topic to "Feature submission exception (Meeting topic: cinder)"16:08
avishaywe're very similar in both name and appearance, i could understand the confusion16:08
jgriffithhaha!16:08
jgriffithand a is really close to q16:08
jgriffithw16:08
jgriffithgeeesh16:08
avishay:)16:08
avishayif you loop around, yes16:08
jgriffithI obviously can't type this morning16:08
jgriffithavishay: look at your keyboard :)16:08
avishay:)16:08
winston-dso jjacob512 recently submitted a patch/driver for Dell's back-end _after_ feature freeze.16:08
jjacob512yes16:08
jgriffithwinston-d: I've been talking with the Dell folks for a while on this16:09
winston-djgriffith: ok16:09
jgriffithwinston-d: I planned on granting the exception if there's no arguments from you or others16:09
winston-dim fine with that16:09
jgriffithcool16:09
*** zbitter has joined #openstack-meeting16:09
jgriffithDell and VmWare were the two that talked to me last month16:09
winston-dthe driver looks pretty simple for now.16:09
avishayit's OK16:09
*** colinmcnamara has joined #openstack-meeting16:10
avishaythe driver looks to be in decent shape, but exception handling was pretty non-existant if i remember correctly16:10
DuncanT-Does it make the minimum feature list for the release?16:10
winston-dif it was 5k+ LOC, i'll be hesitate16:10
*** galstrom_zzz is now known as galstrom16:10
kmartinsounds good, as long as it has unit test and meets the feature list for H16:10
jgriffithJust to be clear, this isn't a review session16:10
jgriffithThe question was just is it accepted for us to review16:10
jjacob512yes , it does, also was able to test it on devstack16:10
avishayif it was 5K+ lines of code i'd -3 it :)16:10
*** colinmcnamara has quit IRC16:10
* jgriffith wants a -3 button!16:11
*** colinmcnamara has joined #openstack-meeting16:11
avishayok, so we let it through, ok by me16:11
jgriffithavishay: to be explicit, we review it!16:11
jgriffithavishay: we don't let it through :)16:11
jungleboyj:-)16:11
kmartinavishay: : you must really be special to get a -3 , what color is that X?16:11
DuncanT-I'm happy to review it, with a 'but be early next time' note16:11
avishayjgriffith: you know what i meant16:11
jungleboyjkmartin: It would have flames around it.16:11
jgriffithavishay: :)  I did16:11
jgriffithflames!16:12
jgriffithnice!16:12
avishaykmartin: the patch gets deleted, and the user account destroyed and banned16:12
jungleboyj:-)16:12
kmartinavishay: nice16:12
*** caitlin-nexenta has quit IRC16:12
jgriffithwinston-d: anything else?16:12
* winston-d wants -3 button as well!16:12
jgriffithwinston-d: we're going to have to create one of those16:12
*** caitlin-nexenta has joined #openstack-meeting16:12
*** zaneb has quit IRC16:12
winston-djgriffith: nope, i guess that's the only exception?16:12
jgriffithDuncanT-: will get a -4 button16:13
avishayjgriffith: noooooo!!16:13
winston-dhah16:13
jgriffithwinston-d: the only other one will be the retype patch if I get to it today :)16:13
winston-d-4 will destory gerrit?16:13
DuncanT-What does -4 do? Geolocate your IP and nuke from orbit?16:13
kmartinsounds like a summit topic "a flaming -3 button"16:13
jungleboyj3d Burning X for -4?16:13
avishayOK, enough tomfoolery :)16:13
jgriffithwinston-d: but yes, I believe everything is in, and I've given up on the local scheduling patch for this release16:13
jgriffithWho's Tom?16:13
avishayAny other meeting topics?16:13
jgriffithavishay: yes!16:14
jgriffith#topic reviews and rechecks16:14
*** openstack changes topic to "reviews and rechecks (Meeting topic: cinder)"16:14
winston-djgriffith: retype, ok. let me knwo if you need help with scheduler16:14
* jungleboyj is laughing16:14
jgriffithOk....16:14
jgriffithso for those that don't read the ML16:14
jgriffithPlease please please take the time to look at the output/console on failed jenkins and gate jobs16:14
jgriffithwe're getting into a habbit of blindly typing "recheck no bug"16:15
jgriffithwhen there is clearly a failure16:15
*** egallen has quit IRC16:15
jgriffithand even worse I've noted a few cases this week where the failure was introduced by the patch16:15
* winston-d hides16:15
jgriffithit wasn't even an intermittent in tempest16:15
jgriffithalso... note16:15
jgriffithI pushed an add of a check conf file is up to date16:16
eharneyi'm very glad we have that now16:16
jgriffithIf you started your branch more than a week or so ago you may want to rebase16:16
jungleboyj+216:16
*** matel has quit IRC16:16
jgriffithand not only rebase, but actually run_tests.sh :)16:16
jgriffithif you need help with rebasing let me know, via IRC or email and I can help16:17
bswartztest before checking in? what are you, a QA guy?16:17
jgriffithbswartz: LOL16:17
*** hemnafk is now known as hemna16:17
jgriffithOk...16:17
jgriffithummmm16:17
jgriffithI think that's about it for me16:18
vincent_houadd test cases for newly added public methods.16:18
jgriffithjust give priority to the reviews that are up and have BP's targetted for H316:18
jgriffithwe have 17 in review last I checked16:18
jgriffithvincent_hou: ?16:18
*** shang has quit IRC16:18
kmartinsounds like a plan16:18
*** egallen has joined #openstack-meeting16:18
hemnaoh the sample conf is being generated and checked now like nova?16:18
jgriffithvincent_hou: that should be a given no?16:18
eharneyre: review priority16:18
jgriffitheharney: yes?16:19
eharneyis http://status.openstack.org/reviews/#cinder considered a somewhat useful list?  (other than it lying about -1s and -2s)16:19
avishayjgriffith: sample conf is being generated automatically or only checked?16:19
*** gongysh has quit IRC16:19
jgriffitheharney: hmm... personally I don't use that16:19
eharneyit tries to prioritize them16:19
eharneyyeah i just realized it was there recently16:19
jgriffitheharney: I just look at https://review.openstack.org/#/q/status:open+cinder,n,z16:19
avishayeharney: it also lies about priorities because not all blueprints are properly scheduled16:19
jgriffitheharney: I don't trust parsers :)16:19
eharneyavishay: ah. hrm.16:20
avishayi use what jgriffith uses16:20
vincent_houjgriffith: I meant the patches to be submitted.16:20
*** yassine_ has quit IRC16:20
jgriffithvincent_hou: yeah, they shouldn't land without unit tests16:20
jgriffithOh, I did have something else16:21
jgriffith2 things actually16:21
jgriffith#topic volume ACL's16:21
*** openstack changes topic to "volume ACL's (Meeting topic: cinder)"16:21
jgriffithI thought we resolved this16:21
jgriffithbut there was a discussion in my history this morning that would indicate otherwise16:21
*** boris-42 has quit IRC16:21
jgriffithso there are two patches for this:16:21
zhiyanjgriffith: i'm not sure why, but seems my readonly-attach change (#38322) not in that review list..16:21
jgriffithzhiyan, looking again16:22
*** nati_ueno has quit IRC16:22
*** nati_ueno has joined #openstack-meeting16:23
jgriffithzhiyan: we'll sort that, I think it's ready to land if we can get one more core to look at it anyway16:23
*** danwent has joined #openstack-meeting16:23
winston-d16:23
*** doron_afk has quit IRC16:23
winston-djgriffith: retype, ok. let me knwo if you need help with scheduler16:23
zhiyanjgriffith: thanks not push, I just confused.16:23
*** markmcclain has joined #openstack-meeting16:23
winston-dlsdf16:23
jgriffithwinston-d: yes, thanks maybe I'll double check something with you after the meeting16:24
*** winston-1 has joined #openstack-meeting16:24
jgriffithooops16:24
avishayjgriffith: i think thingee wanted to take a look at read-only, it's fine by me16:24
jgriffith#topic Read Only attach16:24
*** openstack changes topic to "Read Only attach (Meeting topic: cinder)"16:24
jungleboyjzhiyan: I will take a look as well.16:24
zhiyanjungleboyj: thx16:24
jgriffithavishay: since he's on vacation we'll need to move forward16:24
avishayjgriffith: aahhhh16:24
jgriffithhe's enjoying debachery in the desert16:24
zhiyanoh, ok16:24
jgriffithso this one...16:25
hemnammm debachery16:25
jgriffithtwo cnflicting patches16:25
jgriffithzhiyan: 's patch: https://review.openstack.org/#/c/3832216:25
jgriffithand Anastasia's patch: https://review.openstack.org/#/c/34723/16:25
zhiyanavishay: thanks for you support. and winston-d :)16:25
jgriffithI believe we agreed to go with the implementation zhiyan submitted no?16:26
zhiyanjgriffith: yes, actually i'm also not sure which way you prefer..16:26
jgriffithzhiyan: well my review should answer that for you16:26
avishaywe should just do a git merge of the two16:26
jgriffithavishay: ha!16:26
zhiyanjgriffith: but from former your comments, seems i'm on the right way :)16:26
jgriffithavishay: you get to resolve the conflicts16:26
jgriffithavishay: and I'll assign all bugs to you16:26
avishayjgriffith: :)16:26
vincent_houjgriffith: i am also waiting for ur answer. Anastasia asked me review hers.16:27
vincent_hou:-)16:27
jgriffithI'd like DuncanT- avishay and winston-d to look at those two patches and vote please16:27
jgriffithvincent_hou: my answer is zhiyan 's patch16:27
winston-djgriffith: ok16:27
*** nati_ueno has quit IRC16:27
DuncanT-I vote for zhiyan's patch16:27
jgriffithvincent_hou: it's simpler, less complicated IMO16:27
avishayjgriffith: can you quickly highlight the high-level differences?16:27
jgriffithand still does the job16:27
vincent_houyeah, zhiyan explained that to me.16:28
avishayjgriffith: i'm familiar with zhiyan's not anastasia's16:28
jgriffiththat's left as an exercise to the student :)16:28
winston-di'll take a look at ACL16:28
avishayi hate homeowkr :(16:28
avishayhomework16:28
jgriffithzhiyan: or Annastasia can do that if they want16:28
DuncanT-Anastasia's seems to be more ACL type stuff munged into R/O16:28
jgriffithbut not right now :)16:28
winston-di thought that was to solve a different problem?16:28
jgriffiththe ACL stuff worries me16:28
jgriffithI'm not very comfortable with it for some reason16:28
*** zul has joined #openstack-meeting16:28
jungleboyjjgriffith: +1 seems like that is something to get in earlier in a release cycle.16:29
jungleboyjIMHO16:29
jgriffithjungleboyj: I'd agree16:29
jgriffithjungleboyj: I'm also concerned about confusion for end users16:29
jgriffithand most of all quota management16:29
DuncanT-I still don't understand the ACL code right now, and that is a bad sign for something being merged this late in a cycle16:29
jgriffithOk, so I think the concensus is we defer it16:30
jgriffithavishay: opinion?16:30
jungleboyjSeems like a good idea, just bad timing.  Is there anyone begging for it right now?16:30
jgriffithwinston-d: ?16:30
avishayjgriffith: agree16:30
jgriffithjust mirantis folks16:30
jgriffithOk16:30
jungleboyjHe he, I am sure my folks won't be too far behind.  :-)16:30
winston-dagree16:30
vincent_houThis feature is demanded by Annastasia and her team.16:31
jgriffith'demanded'16:31
hemnaheh16:31
vincent_houShe used to ask me for the idea and design doc.16:31
winston-dvincent_hou: that was your BP?16:32
*** zbitter is now known as zaneb16:32
winston-dvincent_hou: no, it is not.16:32
vincent_houI proposed this topic in Portland.16:32
*** danwent has quit IRC16:33
*** ruhe has joined #openstack-meeting16:33
jgriffithvincent_hou: so what is that your'e suggesting?16:33
vincent_houSince there is no clear use cases for it, I decided to pause it.16:34
winston-dso i vote for zhiyan's patch for it's simplicity16:34
vincent_houjgriffith: i sent her the design, and she said that what they need and would like to implement it.16:35
jgriffithvincent_hou: fine, but everybody here feels uncomfortable with merging it at this stage16:35
winston-dany mirantis folks in here?16:35
jgriffithvincent_hou: do you have a proposal?16:35
vincent_houI decided not to merge it now.16:35
winston-di'm curious in their use cases for ACL.16:36
avishayok i think we're all in agreement16:36
jgriffithyep, let's move on16:36
jgriffithThe only other thing I have (really this time, I promise)16:36
jgriffithPlease take a look at: https://review.openstack.org/#/c/40660/16:36
jgriffithNot my comment16:36
jgriffiths/Not/Note/16:36
jgriffithand with that... I'm finally going to shut-up :)16:37
DuncanT-I don't understand it either - for tables with no uud (like flavor) yes, but we don't have any of those...16:37
jgriffith#topic open-floor16:37
*** openstack changes topic to "open-floor (Meeting topic: cinder)"16:37
hemnaI don't get that patch16:37
jgriffithDuncanT-: boris did point out a few tables like service etc16:37
hemnaI don't see the need for a unique constraint on a flag for deleted16:37
jgriffithDuncanT-: but I don't see the issue personally16:38
jgriffithDuncanT-: he gave a pretty convoluted example of how to have a race there16:38
DuncanT-jgriffith: on #openstack-cinder ?16:38
jgriffithguitarzan: fully agreed with him so maybe he could explain :)16:38
guitarzanmetadata key values16:38
jgriffithDuncanT-: yes16:38
guitarzanare a good example16:38
DuncanT-jgriffith: I'll read the scroll back16:38
kmartinany updates on the multi-attach patch? https://review.openstack.org/#/c/42886/16:38
* jgriffith votes we drop integer ID's everywhere anyway16:38
avishayi didn't understand the patch either...i was hoping thingee would come back and save the day :)16:38
*** kartikaditya has quit IRC16:39
jgriffithkmartin: sadly I think it's dead for this release16:39
zhiyanjgriffith: it is not ready16:39
*** kartikaditya has joined #openstack-meeting16:39
avishaylooks that way unfortunately16:39
kmartinjgriffith: ok, maybe first part of I16:39
zhiyankmartin: probably, sorry for that16:39
hemna:(16:39
*** otherwiseguy has quit IRC16:40
kmartinzhiyan: no problem16:40
*** SergeyLukjanov has quit IRC16:40
zhiyankmartin: yes we will do that out in early I. thanks16:40
zhiyanjgriffith: if you like it :)16:40
jgriffithzhiyan: I like it and we need it16:40
DuncanT-guitarzan: But a new metadata K/V pair will get a new ID, so what's the problem?16:40
jgriffithzhiyan: just not this late16:40
zhiyanjgriffith: nod16:41
guitarzanDuncanT-: the idea is that the key needs to be unique16:41
kmartinzhiyan: may want to move it to WIP16:41
guitarzanand it could be enforced by the db16:41
*** caitlin-nexenta has quit IRC16:41
jgriffithzhiyan: kmartin good point ^^16:41
zhiyankmartin: indeed16:41
*** caitlin-nexenta has joined #openstack-meeting16:41
jgriffithzhiyan: kmartin or even abandon and bring it back to life after H is out16:41
DuncanT-guitarzan: So this is just about increasing the DB enforced constraints, nothing else?16:41
guitarzanyes16:41
guitarzanat least I guess so16:41
zhiyanjgriffith: i prefer mark it WIP if you ok. and kmartin.16:42
DuncanT-guitarzan: Ok, that's the first I've heard of that. People kept talking about race conditions16:42
guitarzanchanging the deleted flag type is necessary due to the soft deletes16:42
*** ruhe has quit IRC16:42
guitarzanyeah, a db uniqueness constraint prevents the races too16:42
*** winston-1 has quit IRC16:42
*** ruhe has joined #openstack-meeting16:42
kmartinzhiyan: +1 from me as WIP16:42
guitarzanat least that's what I understand the "race condition" part of it to mean16:42
winston-dso i vote for zhiyan's patch for it's simplicity16:42
DuncanT-guitarzan: I'll read the scrollback16:43
*** winston-1 has joined #openstack-meeting16:43
zhiyanwinston-d: thank you16:43
guitarzanDuncanT-: it descended into the weeds, like most of our discussions16:43
avishayanother winston? :)16:43
kmartinzhiyan: just add a note with your plans as the note for the WIP16:43
jgriffithwinston-1: thanks16:43
winston-1i really need DuncanT-'s list of slow freenode server.16:43
DuncanT-guitarzan: It the patch hasn't got a clear cut reason for going in, I'm going to vote against it probably16:44
winston-dit's killing me16:44
*** cppcabrera is now known as cppcabrera_afk16:44
zhiyankmartin: sure, i will ask Charlie help mark it.16:44
DuncanT-winston: I've got no correlation between lag and servers... I'm now blaming our corporate proxy16:44
* jgriffith worries we're getting into a habbit of needless churn and complexity16:44
guitarzanDuncanT-: the commit message mentions unique constraints16:44
winston-dthe vote message was sent 5 mins ago. Grrr.16:44
guitarzanso it sounds like that is the goal16:45
DuncanT-guitarzan: But why is that a useful goal?16:45
guitarzanthat's not my question to answer16:45
jgriffithhaha16:45
guitarzanlots of people like data integrity at the db layer16:45
jgriffithguitarzan: drops chaos grenads and exits stage-left16:46
guitarzanand I can't really argue with them about it16:46
DuncanT-There's nothing in the blueprint, and DBAs be crazy16:46
guitarzanit *seems* useful to use unique constraints where appropriate16:46
jgriffithso there's an thread on ML about the long-term goal here16:46
jgriffithuuid, uuid, uuid, uuid, uuid16:46
hemnaunique constraints on uuids makes sense to me16:46
avishaythere definite value in making the DB proper, but i need to understand why/how/what..16:47
*** markmcclain has quit IRC16:47
*** thomasbiege has joined #openstack-meeting16:47
hemnabut not sure why it's needed elsewhere16:47
guitarzando unique constraints on metadata keys make sense?16:47
*** vkmc has joined #openstack-meeting16:47
*** vkmc has quit IRC16:47
*** vkmc has joined #openstack-meeting16:47
guitarzanor service names?16:47
hemnaI don't think so on metadata keys16:47
guitarzanno? why not?16:47
hemnawhy can't there be dupes?16:47
guitarzanhow do you get to the second copy?16:47
hemnawho cares, it's metadata16:47
guitarzankv get16:48
*** winston-1 has quit IRC16:48
*** briancline has quit IRC16:48
*** skolathu has quit IRC16:49
*** afazekas has quit IRC16:49
jgriffithguitarzan: winston-d avishay hemna kmartin ... everyone16:49
jgriffithhttp://lists.openstack.org/pipermail/openstack-dev/2013-August/013877.html16:49
winston-djgriffith: thx16:50
jgriffithno need to go in the weeds here, vote via review, or discuss in cinder channel16:50
jgriffithlet's move on16:50
joel-coffmanI have a quick question regarding https://bugs.launchpad.net/cinder/+bug/121596216:50
uvirtbotLaunchpad bug 1215962 in cinder "Cinder migration 017_add_encryption_information adds two new volume types without warning" [Undecided,Fix committed]16:50
jgriffithhaha16:50
jgriffithjoel-coffman: yes16:50
joel-coffmanis the migration policy to avoid adding anything to the database?16:50
joel-coffmancaught me by surprise this week...16:51
hemnaare we adding volume types by default ?16:51
avishayDB migrations should add columns and tables, not modify rows16:51
avishay*add/remove/modify columns and tables16:51
guitarzanwell, that's not necessarily true16:51
eharneyIMO if you need to add types like that by default, it needs to be done by code in Cinder, not DB migrations16:51
kmartinagree16:51
hemnaavishay, unless there is data migration needed due to a change no?16:52
guitarzanbut there's no reason to add a volume type just for fun16:52
hemnaguitarzan, +116:52
kmartinthese should be removed16:52
avishayhemna: sure there are exceptions, but overall, yes16:52
zhiyanhemna: yes +116:52
DuncanT-joel-coffman: We migrated a system and suddenly had a new type, that was a surprise....16:52
eharneyhemna: but you can do that in code, not in the migration schema, right?16:52
*** IlyaE has quit IRC16:52
joel-coffmanokay16:52
joel-coffmanwhat's the *correct* way to create new types that correspond to our front-end encryption schemes that are implemented in Nova?16:53
hemnaeharney, depends, if the data needs migration prior to code...that's what migration is for IMO.  but I don't think we should be adding volume types by default16:53
jgriffithjoel-coffman: the admin creates them as part of config16:53
avishayadmins should create whatever volume types they want in the deployment...i think cinder shouldn't create any at all16:53
jgriffithavishay: +116:53
bswartzavishay: +216:53
jgriffithjoel-coffman: for example, there's likely to be a number of people who choose not to enable/use encryption16:53
jungleboyjavishay: +116:54
joel-coffmanjgriffith: any way to automate this process for the types that we *know* should exist16:54
hemnajgriffith, +116:54
guitarzanthere are no types that should exist everywhere16:54
avishaythe cinder code should check extra_specs and do as necessary16:54
joel-coffmanconfiguration options could enable / disable it16:54
DuncanT-Why should encrypted types exist?16:54
jgriffithjoel-coffman: no, as types are all custom16:54
jgriffithjoel-coffman: not sure of the problem?16:54
winston-dguitarzan: +116:54
jgriffithjoel-coffman: cinder type-create luks16:54
jgriffithdone16:54
DuncanT-joel-coffman: We didn't want encrypted types. Not now, maybe never16:54
avishayjoel-coffman: for example, i may want a type that has encryption, a certain QoS setting, and no compression16:55
joel-coffmanokay, that makes sense16:55
avishayjoel-coffman: why should i be stuck with those 2 types?16:55
*** kirankv has joined #openstack-meeting16:55
avishayjoel-coffman: or i may not want compression at all, and then i need to go and remove the types16:55
joel-coffmanjust trying to understand the environment better16:55
jgriffithjoel-coffman: going through the code I didn't see where this would cause a problem16:55
jgriffithjoel-coffman: did I miss something perhaps (ie this being taking out the creation of the types)16:55
joel-coffmanno, not really a problem -- just a surprise16:56
jgriffithjoel-coffman: ahh, sorry about that16:56
jgriffithjoel-coffman: I was looking for you when DuncanT- and I discussed it the other day16:56
jgriffithjoel-coffman: you weren't around and sadly I forgot to follow up16:56
jgriffithjoel-coffman: You were also supposed to be added to the review16:57
joel-coffmanno worries, I'll know better next time (and try to hang out more on IRC)16:57
joel-coffman:)16:57
jgriffithjoel-coffman: sorry for the surprise16:57
joel-coffmanjgriffith: thanks, being part of that review would have been helpful16:57
avishaynext time we surprise you we'll make sure to bring confetti :)16:57
jgriffithjoel-coffman: yeah, that for sure would've been appropriate16:58
joel-coffmanavishay: ha!16:58
jgriffithOk.. so two topics on the agenda that took 10 minutes and we still filled our hour :)16:58
jgriffithdang we're good16:58
avishaynever fails16:58
avishaynow try to end the meeting :)16:58
*** markmcclain has joined #openstack-meeting16:58
bswartzwait for it....16:59
hemnalol16:59
kmartinwaiting...16:59
jgriffith#end meeting16:59
guitarzanhah16:59
jgriffithha!16:59
avishaylol16:59
winston-dasd///asdfas16:59
jgriffith#endmeeting cinder16:59
guitarzanavishay: wins16:59
hemnaawesome16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Wed Aug 28 16:59:21 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-08-28-16.03.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-08-28-16.03.txt16:59
eharneyhaha man you guys are harsh16:59
jgriffithI didn't want to dissappoint16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-08-28-16.03.log.html16:59
*** ruhe has quit IRC16:59
*** winston-1 has joined #openstack-meeting16:59
hartsockswoo!16:59
jgriffithuntil next virtbot16:59
*** avishay has left #openstack-meeting16:59
*** caitlin-nexenta has quit IRC16:59
*** bswartz has left #openstack-meeting16:59
jungleboyjLater.16:59
*** kartikaditya has quit IRC16:59
jgriffithcya all16:59
vincent_hougood day, folks!17:00
*** alexpilotti has joined #openstack-meeting17:00
*** zhiyan has left #openstack-meeting17:00
*** winston-d has left #openstack-meeting17:00
*** joesavak has joined #openstack-meeting17:00
*** vincent_hou has quit IRC17:00
*** danwent has joined #openstack-meeting17:00
hartsocks#startmeeting vmwareapi17:00
openstackMeeting started Wed Aug 28 17:00:48 2013 UTC and is due to finish in 60 minutes.  The chair is hartsocks. 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: vmwareapi)"17:00
openstackThe meeting name has been set to 'vmwareapi'17:00
*** jungleboyj has left #openstack-meeting17:00
hartsocksGreetings stackers!17:00
hartsocksWho's about?17:01
*** winston-1 has quit IRC17:02
hartsocksWell, most of the team are at VMworld so I had a feeling it might be *crickets* this week.17:02
*** RajeshMohan has quit IRC17:02
*** RajeshMohan has joined #openstack-meeting17:03
* hartsocks listens to the crickets… giving it 5 minutes17:03
*** markmcclain has quit IRC17:03
*** jsavak has quit IRC17:03
*** RajeshMohan has quit IRC17:03
*** RajeshMohan has joined #openstack-meeting17:03
*** SergeyLukjanov has joined #openstack-meeting17:05
*** burt has joined #openstack-meeting17:05
hartsocksOkay. Me and the crickets are signing off.17:05
hartsocks#endmeeting17:05
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:05
openstackMeeting ended Wed Aug 28 17:05:52 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-08-28-17.00.html17:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-08-28-17.00.txt17:05
openstackLog:            http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-08-28-17.00.log.html17:05
*** jjacob512 has left #openstack-meeting17:06
*** RajeshMohan has quit IRC17:06
*** hartsocks has left #openstack-meeting17:06
*** dims has joined #openstack-meeting17:06
*** derekh has quit IRC17:07
*** RajeshMohan has joined #openstack-meeting17:07
*** markwash has quit IRC17:07
*** ndipanov is now known as ndipanov_gone17:07
*** SumitNaiksatam has quit IRC17:08
*** joel-coffman has quit IRC17:08
*** markmcclain has joined #openstack-meeting17:09
*** ruhe has joined #openstack-meeting17:10
*** CaptTofu has joined #openstack-meeting17:10
* CaptTofu is here and skulks in17:10
*** comay has joined #openstack-meeting17:11
*** vijendar has joined #openstack-meeting17:11
*** thomasbiege has quit IRC17:13
*** joesavak has quit IRC17:13
*** Toshi has joined #openstack-meeting17:14
*** dcramer_ has quit IRC17:16
*** IlyaE has joined #openstack-meeting17:17
*** glikson has joined #openstack-meeting17:17
*** kirankv has quit IRC17:19
*** hartsocks has joined #openstack-meeting17:21
*** safchain has quit IRC17:22
*** hartsocks has left #openstack-meeting17:22
*** jdurgin1 has quit IRC17:23
*** danwent has quit IRC17:24
*** yaguang has quit IRC17:26
*** SumitNaiksatam has joined #openstack-meeting17:31
*** danwent has joined #openstack-meeting17:36
*** ruhe has quit IRC17:37
*** bpb has quit IRC17:40
*** markwash has joined #openstack-meeting17:42
*** boris-42 has joined #openstack-meeting17:42
*** morganfainberg|a is now known as morganfainberg17:42
*** thomasbiege has joined #openstack-meeting17:43
*** danwent has quit IRC17:44
*** jlucci has quit IRC17:45
*** danwent has joined #openstack-meeting17:47
*** yjiang5_away is now known as yjiang517:47
*** johnthetubaguy has quit IRC17:48
*** markmcclain has quit IRC17:49
*** sarob has joined #openstack-meeting17:51
*** glikson has quit IRC17:51
*** danwent has quit IRC17:52
*** thomasbiege has quit IRC17:52
*** colinmcnamara has quit IRC17:54
*** m4dcoder has joined #openstack-meeting17:55
*** Toshi has quit IRC17:56
*** otherwiseguy has joined #openstack-meeting17:58
*** cppcabrera_afk is now known as cppcabrera17:59
*** Toshi has joined #openstack-meeting17:59
*** colinmcnamara has joined #openstack-meeting17:59
*** mrunge has joined #openstack-meeting17:59
*** jjacob512 has joined #openstack-meeting17:59
*** colinmcnamara has quit IRC18:03
*** jjacob512 has quit IRC18:05
*** colinmcnamara has joined #openstack-meeting18:05
*** syerrapragada has quit IRC18:05
*** morganfainberg is now known as morganfainberg|a18:08
*** glikson has joined #openstack-meeting18:11
*** thedodd has quit IRC18:15
*** thedodd has joined #openstack-meeting18:16
*** colinmcnamara has quit IRC18:16
*** adalbas has quit IRC18:16
*** jmontemayor has quit IRC18:21
*** IlyaE has quit IRC18:22
*** Mandell has joined #openstack-meeting18:22
*** spenceratx_ has joined #openstack-meeting18:30
*** spenceratx has quit IRC18:31
*** spenceratx_ is now known as spenceratx18:31
*** hemanth_ has quit IRC18:31
*** hemanth has joined #openstack-meeting18:32
*** gyee has quit IRC18:32
*** mdenny has quit IRC18:33
*** mdenny has joined #openstack-meeting18:34
*** jmontemayor has joined #openstack-meeting18:34
*** acabrera has joined #openstack-meeting18:35
*** cppcabrera has quit IRC18:37
*** glikson has quit IRC18:37
*** novas0x2a|laptop has joined #openstack-meeting18:38
*** inkerra has joined #openstack-meeting18:38
*** nati_ueno has joined #openstack-meeting18:40
*** colinmcnamara has joined #openstack-meeting18:41
*** colinmcnamara has quit IRC18:43
*** openstack has joined #openstack-meeting18:46
*** ChanServ sets mode: +o openstack18:46
*** jlucci has joined #openstack-meeting18:48
*** topol has quit IRC18:49
*** m4dcoder has quit IRC18:52
*** ktbenton has quit IRC18:54
*** sarob has quit IRC18:57
*** dcramer_ has joined #openstack-meeting18:57
*** sarob has joined #openstack-meeting18:57
*** NobodyCam has quit IRC18:58
*** SergeyLukjanov has quit IRC18:58
*** NobodyCa1 has joined #openstack-meeting18:58
*** SergeyLukjanov has joined #openstack-meeting18:59
*** NobodyCa1 is now known as NobodyCam18:59
*** dianefleming has joined #openstack-meeting19:00
*** meganw has quit IRC19:01
*** meganw has joined #openstack-meeting19:01
*** lpabon has joined #openstack-meeting19:03
*** IlyaE has joined #openstack-meeting19:04
*** meganw has quit IRC19:06
*** dianefleming has quit IRC19:07
*** bgmccollum has left #openstack-meeting19:09
*** martines has joined #openstack-meeting19:10
*** safchain has joined #openstack-meeting19:10
*** bgmccollum has joined #openstack-meeting19:10
*** bgmccollum has left #openstack-meeting19:11
*** nati_ueno has quit IRC19:14
*** safchain has quit IRC19:14
*** nati_ueno has joined #openstack-meeting19:14
*** lpabon has quit IRC19:14
*** nati_ueno has quit IRC19:18
*** IlyaE has quit IRC19:20
*** gyee has joined #openstack-meeting19:20
*** rongze has joined #openstack-meeting19:24
*** alexpilotti has quit IRC19:24
*** SumitNaiksatam has quit IRC19:25
*** alexpilotti has joined #openstack-meeting19:25
*** lpabon has joined #openstack-meeting19:26
*** egallen has quit IRC19:26
*** colinmcnamara has joined #openstack-meeting19:27
*** adalbas has joined #openstack-meeting19:27
*** rongze_ has quit IRC19:27
*** glikson has joined #openstack-meeting19:30
*** jmontemayor has quit IRC19:35
*** davidhadas has joined #openstack-meeting19:36
*** kebray has joined #openstack-meeting19:37
*** sarob has quit IRC19:37
*** IlyaE has joined #openstack-meeting19:38
*** jmontemayor has joined #openstack-meeting19:39
*** dkranz has quit IRC19:41
*** dkranz has joined #openstack-meeting19:42
*** otherwiseguy has quit IRC19:43
*** kbs1 has quit IRC19:43
*** dprince has quit IRC19:44
*** eric-young has quit IRC19:47
*** topol has joined #openstack-meeting19:49
*** zul has quit IRC19:49
*** litong has joined #openstack-meeting19:53
*** danwent has joined #openstack-meeting19:54
*** TravT has joined #openstack-meeting19:55
*** nati_ueno has joined #openstack-meeting19:57
*** jasond has joined #openstack-meeting19:59
zaneb#startmeeting heat20:00
openstackMeeting started Wed Aug 28 20:00:19 2013 UTC and is due to finish in 60 minutes.  The chair is zaneb. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: heat)"20:00
openstackThe meeting name has been set to 'heat'20:00
sdake_o/20:00
zanebevening all20:00
asalkeldo/20:00
stevebakeryop20:00
spzalaHello!20:00
*** danwent has quit IRC20:00
bgorskio/20:00
*** andrew_plunk has joined #openstack-meeting20:01
jasondo/20:01
zanebshardy can't make it this evening, so y'all are stuck with me again ;)20:01
andrew_plunkhello everyone20:01
*** IlyaE has quit IRC20:01
*** timductive has joined #openstack-meeting20:01
*** m4dcoder has joined #openstack-meeting20:02
*** acabrera is now known as cppcabrera20:02
*** RajeshMohan has quit IRC20:02
jpeelerhey20:02
zanebok, I think that qualifies as a quorum20:02
SpamapSo/20:02
radixhello!20:02
asalkeld#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda20:02
zaneb#topic Review last week's actions20:02
*** openstack changes topic to "Review last week's actions (Meeting topic: heat)"20:02
m4dcodero/20:02
zaneb#link http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-08-21-20.01.html20:03
zanebonly one, shardy to post mission statement, again20:03
zanebthat actually happened!20:03
zanebwoohoo!20:03
radixfinally :)20:03
zaneblet's call that success, unless anybody wants to bikeshed some more ;)20:03
*** adrian_otto has joined #openstack-meeting20:03
SpamapSisn't that what meetings are for?20:04
zaneb#topic Reminder re FeatureProposalFreeze20:04
*** openstack changes topic to "Reminder re FeatureProposalFreeze (Meeting topic: heat)"20:04
zaneb#link https://wiki.openstack.org/wiki/FeatureProposalFreeze20:04
*** RajeshMohan has joined #openstack-meeting20:04
zanebhopefully y'all have proposed your features20:04
stevebakerthat seemed to go well20:04
SpamapScame and gone no?20:04
zanebSpamapS: yep20:04
*** SergeyLukjanov has quit IRC20:05
stevebakerwhen is feature freeze?20:05
* zaneb suspects copy-and-paste fail on the agenda here ;)20:05
zanebstevebaker: 4th September20:05
adrian_ottoam I in a time machine?20:05
zaneb#link https://wiki.openstack.org/wiki/Havana_Release_Schedule20:05
zanebso, good job everybody20:05
*** Toshi has quit IRC20:05
stevebakerso features still being reviewed after the 4th need explicit exceptions?20:06
zaneband it looks like we don't have a huge review backlog, so we should be in good shape for feature freeze20:06
*** sabeen has joined #openstack-meeting20:06
zanebstevebaker: well, havana-3 release is on the 6th20:06
zanebso there shouldn't really be any _features_ going in after that20:06
*** m4dcoder has quit IRC20:07
zanebreview queue looks about as long as always20:07
zaneb#link https://review.openstack.org/#/q/status:open+project:openstack/heat,n,z20:07
radixI'm trying to help :)20:07
SpamapSDo we have features which are racing to land?20:07
*** meganw has joined #openstack-meeting20:07
*** meganw has quit IRC20:07
*** cppcabrera has left #openstack-meeting20:07
zanebgood question20:08
radixyeah it'd be nice if I could filter gerrit by feature vs bugfix20:08
zaneb#topic h3 blueprint status20:08
*** openstack changes topic to "h3 blueprint status (Meeting topic: heat)"20:08
stevebakermy review queue alarm threshold is "does it scroll?"20:08
*** SumitNaiksatam has joined #openstack-meeting20:08
*** meganw has joined #openstack-meeting20:08
SpamapShttps://launchpad.net/heat/+milestone/havana-320:08
asalkeldzaneb, http://status.openstack.org/reviews/#heat20:08
zanebstevebaker: it's been scrolling for quite a while though ;)20:08
kebrayjasond is multi-engine stuff a feature or bug?20:08
*** m4dcoder has joined #openstack-meeting20:08
stevebakerkebray: yes!20:08
*** chamings has joined #openstack-meeting20:08
SpamapSlooks like all targetted BP's are in review20:08
zanebasalkeld: ooh, fancy :)20:09
jasondkebray: we decided it was a BP since the original commit was reverted20:09
radixah there we go20:09
stevebakerreviews on this are lacking https://review.openstack.org/#/c/43205/20:09
kebrayok.. so, zaneb, we're racing a bit on the multi-engine one.  I think jasond has it under control though.. it's down to more tests I believe.20:09
zanebok, thanks for the info20:10
*** thomasbiege has joined #openstack-meeting20:10
zaneb#link https://launchpad.net/heat/+milestone/havana-320:10
zanebtrusts and multi-engine are the two diciest, I think20:11
zanebbut I'm reasonably confident20:11
kebrayI want trusts... if help is needed, let me know and I can see what resources we can spare to help the effort.20:11
*** thomasbiege has quit IRC20:11
stevebakerkebray: reviews would be good20:12
kebrayk.20:12
*** chamings has left #openstack-meeting20:12
zanebkebray: we all want trusts ;) I think shardy has got it to the point where it's not going to be lack of resources causing a problem20:12
zanebit will be random stuff out of left field20:12
timductiveyes +1 on trusts :)20:12
kebrayzaneb: that's what I thought... and I figure throwing more people at the problem would actually slow it down.  so, also happy to stay out of the way :-)20:13
zanebafter studiously ignoring reviews for a few days to get the update stuff posted, my plan is to focus on reviews for the next few days20:13
kebraybut, stevebaker comment on reviews is appropriate.  we'll try to help with that.20:13
zanebthe gate will be crazy next week, so if everybody can try to get the review backlog down that would be very helpful20:13
asalkeldalso can we stick to looking for bugs in the reviews20:14
radixhm?20:14
asalkelduploading new patches is very time expensive20:14
zanebyeah, y'all would be surprised about how little anybody will care about typos in hte commit message a year from now ;)20:15
asalkeldradix, just saying very little value in fixing nits20:15
zanebs/hte/the/20:15
zaneb#topic Single Config file?20:15
zanebasalkeld: you have the floor20:15
*** openstack changes topic to "Single Config file? (Meeting topic: heat)"20:15
sdake_the commit message is the most important part of the change20:15
asalkeldhaah20:15
asalkeldso the change for the single config is in20:16
asalkeldso little to motivate for now20:16
asalkeldbut to let you know we are moving to a single heat.conf20:16
asalkeldI'll do the devstack change20:16
radixthe docs still need updated, right?20:17
stevebakeryay20:17
asalkeldthen kill the old heat-<>.conf's20:17
asalkeldradix, yes20:17
asalkeldgood point20:17
asalkeldthat's all from me20:17
stevebakerasalkeld: so the devstack change will start with heat.conf.sample and customize?20:17
asalkeldyip20:17
stevebakersweet20:17
sdake_is devstack broken atm with master/20:18
stevebakernot for me20:18
zanebsounds good, I guess the question was answered in the affirmative ;)20:18
asalkeldreally20:18
*** noslzzp has quit IRC20:18
asalkeldI have some environment and template patches for devstack20:18
stevebakeryou can always run heat standalone against some other cloud20:18
adrian_ottoyes it is broken20:18
asalkeldnot sure if they have made it in20:18
zaneb#info we will move to a single config file and remove the legacy configs20:18
asalkeldhttps://review.openstack.org/#/c/43631/20:19
asalkeldthat not being in might be causing issues20:19
stevebakeryes, we'll be needing that20:20
*** Toshi has joined #openstack-meeting20:20
spzalazaneb: asalked: is there a doc/link to learn more about single config?20:20
*** otherwiseguy has joined #openstack-meeting20:20
SpamapSwait when are the legacy configs being removed?20:21
SpamapS"icehouse" right?20:21
asalkeldno, what do you need?20:21
asalkeldSpamapS, we still support them20:21
SpamapSok, just examples.20:21
asalkeldjust removing the examples from master20:21
asalkeldya20:21
SpamapSroger, nothing to see here, move along20:21
asalkeldzaneb, SpamapS 's next topic...20:22
zaneb:)20:22
*** vipul has quit IRC20:22
*** noslzzp has joined #openstack-meeting20:22
zaneb#topic moving rackspace cloud server specific resources out of heat tree20:23
zanebso, can I just redefine something here?20:23
zanebin-repo = in openstack/heat git repo20:23
*** openstack changes topic to "moving rackspace cloud server specific resources out of heat tree (Meeting topic: heat)"20:23
zanebin-tree = under heat/engine/resources20:23
*** vipul has joined #openstack-meeting20:23
zanebso, SpamapS, what we're talking here is moving out of the repo?20:23
stevebakeror into a contrib dir20:23
SpamapSOk, I think they should be out of the repo, in the direct control of rackspace-cloud-interested people.20:23
asalkeldwell what really matters is what the rackers want20:24
zanebbecause I was under the impression we agreed to have it under /contrib, and then when it landed it was in-tree20:24
zaneband I don't know what happened there20:24
SpamapSI think the rackers are looking to us, heat-core, for guidance.20:24
zanebmiscommunication?20:24
asalkeldhello rackers, what do you want...20:24
SpamapScontrib still carries the problem that rackspace public cloud does not follow the openstack release cadence.20:24
radixping kebray20:25
zanebSpamapS: fair point20:25
kebrayFrom the Racker perspective, we want wants best for the project and all parties who want to contribute in a similar manner...20:25
SpamapSThis isn't like a driver in the kernel where it is there to support pieces of hardware that are "out there".20:25
kebraythere's an obvious advantage to us if our resources get tested as part of CI, as a change to a base resource could affect our resources... but, we also understand not everyone may be able to contribute a fix to our resources.20:25
zanebSpamapS: but then again, having them out of tree requires us to be more disciplined about the interface to plugins20:25
kebrays/what's/wants20:26
asalkeldI am not stressed it being there20:26
SpamapSThe rackspace public cloud is a special snowflake and will always be that way as long as it is not conformant with the rest of OpenStack.20:26
radixhmm, do the rackspace resource tests actually get run in CI? aren't they protected by a "if pyrax is available" clause?20:26
stevebakerfor now I would prefer to have no discipline about our plugin interface20:26
SpamapSzaneb: that much discipline will only help adoption of Heat and grow the ecosystem around Heat.20:26
*** danwent has joined #openstack-meeting20:26
*** dvarga has quit IRC20:26
asalkeldI think that is a strong point of somewhen in tree stevebaker20:26
zanebstevebaker: too long. "I would prefer to have no discipline." <- better20:27
andrew_plunkI just wonder about the priority that will be given to heat bugs that break plugins20:27
SpamapSradix: yeah, no pyrax, no testing20:27
SpamapSactually hm20:27
radixSpamapS: actually20:27
radixhehe :)20:28
radixI just saw the tests force the registration of the resource so it can be tested.20:28
SpamapSyeah and they just side-step the pyrax calls.20:28
kebraywhat about resources like Trove?   they should remain in-tree, no?20:28
SpamapSkebray: nobody is saying you can't be in stackforge of course. :)20:28
radix(that's probably what neutron tests should do too... therve has been writing the tests so they skip if neutronclient isn't available even if neutronclient isn't really used)20:28
SpamapSkebray: absolutely20:28
andrew_plunkSpamapS: we still run unit tests without pyrax20:28
andrew_plunkwe completely mock out pyrax20:28
SpamapSAny resource that is implementing an OpenStack API should be in-tree.20:29
zanebkebray: yes, as long as it uses regular keystone20:29
*** spzala has quit IRC20:29
kebraySpamapS.  Understood.. I feel I understand the arguments on both sides... so, I'm pretty neutral on this.20:29
*** spzala has joined #openstack-meeting20:29
andrew_plunkI feel like the contrib idea is a good middle road20:29
zanebfor my part I would still at least like to see it moved to /contrib20:29
stevebaker+1 for contrib20:29
zanebas a packager, I really don't feel it belongs where it is20:29
asalkeldsure20:29
jasond+1 for /contrib20:30
kebrayWe hope the RS Cloud Server resources goes away soon.. we're working internally to converge compatibility such that the generic nova server resource is sufficient.20:30
SpamapSI feel like we are holding the rax developers back, and they are putting code in front of us that has almost nothing to do with Heat's core mission (whether you like the one we all came up with, or Robert Collins succinct one)20:30
zanebwho wants an action to move it?20:30
asalkeldkebray, cool20:30
stevebakerkebray: i home when native nova server lands you can switch to subclassing that?20:30
andrew_plunkzaneb: you can give it to me20:30
kebrayLoad Balancer is another issue though.  I think HP and other vendors will have similar one off special implementations potentially.20:30
SpamapSkebray: even more reason to get them out of the repo and into a place that can just be shut down when the unicorns are finally harnessed. ;)20:31
zaneb#action andrew_plunk to move Rackspace resources to /contrib directory20:31
kebraySpamapS  I don't disagree.20:31
jasondSpamapS: i like getting feedback from the core devs20:31
*** pnavarro has quit IRC20:31
SpamapSkebray: HP's LBaaS is a published API (Atlas) IIRC.20:31
*** danwent has quit IRC20:31
*** jjacob512 has joined #openstack-meeting20:32
jasondwhen something is clearly up to us, the core devs can just approve based on votes from other rackers20:32
*** xBsd has joined #openstack-meeting20:32
zanebso, on the in-repo/out-of-repo question, I'm relaxed. If the current situation is not working for Rackspace folks, feel free to move it. And if it is, I'm not worried about leaving it in /contrib20:32
*** scottda has quit IRC20:32
SpamapSjasond: thats a fair counter-argument.. resources are still a bit mysterious and core devs can help make them better.20:32
*** scott_da has quit IRC20:32
radixif it's in /contrib, will it get CI?20:32
asalkeldradix, as long as you have tests20:33
*** scottda has joined #openstack-meeting20:33
*** scott_da has joined #openstack-meeting20:33
zanebradix: I'm sure there's a way to arrange it so it will20:33
SpamapSIt would be harder to test them from contrib20:33
SpamapSI'm kind of "meh" on contrib20:33
SpamapSheat/engine/resources/rackspace == contrib in my mind.20:33
zanebSpamapS: I don't know about Debian, but that's just a PITA to package in an RPM20:34
asalkeldlooks like we have come full circle20:34
adrian_ottoyou can have multiple repos in heat, and contrib could be its own repo, and it could still have CI.20:34
*** adalbas has quit IRC20:34
kebrayIs there a way to have contrib (or heat/engine/resources/rackspace be "optional" on test gates?  Maybe adrian_otto's suggestion accounts for that.20:35
jasondSpamapS: except contrib/rackspace could have its own heat tree (engine, api, etc..)20:35
SpamapSOk lets take a step back from the ideas on how. Am I in a minority in suggesting that these resources should be out of the repo/tree?20:35
*** colinmcnamara has quit IRC20:35
asalkeldI don't mind either way20:35
SpamapSzaneb: no its not hard with Debian, but it is far less automatic than just "let setup.py do its thing"20:35
andrew_plunkSpamapS I know that RandallBurt's vote is with you20:35
* zaneb is not taking a side20:35
kebrayI'm neutral.20:35
adrian_ottothen let's KISS20:36
SpamapSYeah, if its just me and Randall who care.. leave them be.20:36
adrian_ottoif having htem in tree is not causing objections, then let's revisit it once there is an objection to field.20:36
adrian_ottoI think we already worked around the test gate concern, right kebray?20:36
SpamapSMy objection mainly pertains to the fact that by having them in-tree we raise the barrier for other projects who want to write custom resources.. as it is not obvious _at all_ how to do that and not be in-tree.20:37
kebrayadrian_otto issue is if someone makes change to base resource and RS resource tests break, is that gating that change until someone fixes the RS resource?20:37
andrew_plunkSpamapS: that can be documented20:37
zanebSpamapS: true, but we weren't exactly fighting them off before either ;)20:37
*** egallen has joined #openstack-meeting20:38
*** gordc has joined #openstack-meeting20:38
*** gordc has quit IRC20:38
zanebandrew_plunk: that *is* documented https://wiki.openstack.org/wiki/Heat/Plugins20:38
stevebakerSpamapS: we'd need to decide that our resource interface was going to have proper change control before encouraging that though20:38
SpamapSzaneb: An ecosystem starts with one user though.. and we have done the one in a special way that we will likely never do again.20:38
kebraySpamapS: does moving them to contrib not address your main objection?20:38
*** gordc has joined #openstack-meeting20:38
adrian_ottocontrib is stuff that does not get tested, right?20:39
asalkeldthere is just a plugins_dir config option isn't there20:39
SpamapSkebray: moving them to contrib would make it more obvious, but would we accept a resource to control vagrant, or CloudStack, in contrib?20:39
adrian_ottoand it's use-at-your-own-risk20:39
zanebadrian_otto: I think we'd want to keep testing it20:39
adrian_ottothen it should probably be in your tree20:39
zanebSpamapS: I would20:40
adrian_ottoif you are supporting it, then treat it as such20:40
andrew_plunkKeeping these resources in the repo helps with collaboration outside of any specific company. Everyone gets visibility to Rackspace specific code and the converse20:40
adrian_ottoif it's unsupported, then it's contrib, right?20:40
kebraySpamapS I would be ok with it for now until we find a concrete objection.20:40
SpamapSMmk, if we would, and we'd be happy with the review load being centralized, then we should push to move resources out of tree en masse eventually.20:41
SpamapSBut for now, nothing is broken, and nobody is stifled, so I suggest we move on.20:41
zanebSpamapS: is this worth a mailing list post?20:41
adrian_ottobut to repeat kebray's comment, if it aids the project, we will not object to moving them elsewhere20:42
zanebseems like this is a long-form argument ;)20:42
kebrayI agree it some point it will happen.. if enough special contribs are there, centralized review from core team will become difficult in the long run.  But, it's still early.. we don't have many yet, so there's benefit to collaborating on the reviews.20:42
kebrayadrian_otto, correct.  I don't object to moving them out.  I defer to the core team's recommendation.20:42
zanebok20:43
zaneb#topic Open discussion20:43
*** openstack changes topic to "Open discussion (Meeting topic: heat)"20:43
zanebhave at it20:43
radixis there a way to schedule/plan individual meetings at the summit? like, things that aren't talks20:43
zanebradix: yes, the design summit20:43
kebrayis there a documented plan somewhere around native heat tools to replace heat-cfn, and overlap with what cloud-init provides?20:43
SpamapSradix: that is the entire point of the design summit. :) the talks were an after thought :)20:44
zanebradix: that hasn't been organised yet though20:44
*** jecarey has quit IRC20:44
SpamapSkebray: yes, .. blueprint native-in-instance-tools20:44
*** jecarey has joined #openstack-meeting20:44
stevebakerkebray: I'll propose a design summit session for that20:44
kebraySpamapS does that address the overlap in functionality with cloud-init?  I may just need to reread it.20:44
kebraystevebaker:  awesome!20:45
*** mrunge has quit IRC20:45
radixzaneb: wait, is the "design summit" something different from what is happening in HK?20:45
SpamapSkebray: there are 3 sub-blueprints20:45
SpamapSkebray: and there is no overlap.. cloud-init != a config management tool. :)20:45
zanebradix: it's a separate track20:45
kebraystevebaker: can you also propose the design summit happen in a place that isn't so expensive to travel to?  I'd love to send more people :-)20:45
zanebradix: but don't worry, it'll be in Hong Kong ;)20:45
radixhehe, ok20:45
SpamapSkebray: though for the bootstrap-config tool... it might work out :)20:45
stevebakerkebray: heh20:45
kebraySpamapS I know cloud-init isn't config management.  I guess my knowledge of cnf tools is lacking.  I'll read up on that :-)20:46
*** jjacob512 has quit IRC20:46
asalkeldansible as  a service?20:46
stevebakeransible as a metadata snippet?20:46
SpamapSaaas is a horrible, horrible name20:46
asalkeld:)20:46
* stevebaker drops the kids off at the school20:47
zanebradix: it's basically a bunch of rooms that are essentially developer-only design sessions. Official/incubated projects get allocated time. It'll be organised shortly.20:47
kebrayI'm going to ansiblefest.  I'm actually very interested in the convergence of the configuration tools with orchestration.. they are moving into orchestration, and some people think orchestration engine should solve config management (don't want to debate that now thought).20:47
radixzaneb: okay, cool20:47
*** radez is now known as radez_g0n320:47
radixzaneb: even though I'm not going to be there :( I want to propose some discussions20:47
SpamapSkebray: I may join you there.20:48
asalkeldkebray, it would be nice to support ansible/salt20:48
kebrayfwiw, I don't think many of us Rackspace devs will be at the summit :-(20:48
asalkeld:(20:48
zaneb:(20:48
zanebkebray: that's disappointing20:48
asalkeldheat summit in kebray's garage20:48
kebrayasalkeld feel free to take up a collection :-)20:48
SpamapSkebray: are you _asking_ us to kidnap your devs and take them to HK? ;)20:48
kebraySpamapS:  fine by me :-)20:49
andrew_plunkI don't know if you can kidnap the willing20:49
* asalkeld not rolling in cash20:49
adrian_ottoI will represent radix20:49
radixI know therve and adrian_otto are going to be there, not sure who else20:49
kebrayAnyway, we'll figure out how to contribute. We like working with you all :-)20:49
*** thomasm has joined #openstack-meeting20:49
zanebok, there no *law* that says we have to go the full hour ;)20:50
asalkeldw00t20:50
zanebso if we're done here I'll wrap it up20:50
asalkeldcoffee time20:51
SpamapSre ansible and salt.. we already integrate well with both of them, anything new would be syntactic sugar to make federating our instances into a salt/ansible grouping easier.20:51
kebraySpamapS asalkeld  I'd love to review more of ya'lls thoughts on config management, Salt/Ansible, orchestration, etc.20:51
*** eglynn has joined #openstack-meeting20:51
SpamapSkebray: we can chat about it in #heat after if you have time.20:51
kebrayOk.20:51
SpamapSzaneb: please yes lets wrap20:51
zanebok20:51
zaneb#endmeeting20:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:51
openstackMeeting ended Wed Aug 28 20:51:40 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-08-28-20.00.html20:51
radixSpamapS: I would really like to see more "syntactic sugar" :)20:51
*** andrew_plunk has left #openstack-meeting20:51
*** boris-42 has quit IRC20:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-08-28-20.00.txt20:51
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-08-28-20.00.log.html20:51
radixlater bros20:51
*** jasond has left #openstack-meeting20:52
*** spenceratx has left #openstack-meeting20:52
*** timductive has left #openstack-meeting20:52
spzalaradix: good day! later.20:52
*** m4dcoder has quit IRC20:52
*** glikson has quit IRC20:52
*** colinmcnamara has joined #openstack-meeting20:55
*** sandywalsh has quit IRC20:55
*** Tross has quit IRC20:56
*** herndon has joined #openstack-meeting20:56
*** llu-laptop has joined #openstack-meeting20:57
*** lblanchard has quit IRC20:57
*** thomasbiege has joined #openstack-meeting20:59
*** EricP_ has joined #openstack-meeting20:59
*** EricP_ has quit IRC20:59
*** sandywalsh has joined #openstack-meeting20:59
*** stevemar has quit IRC21:00
*** epende has joined #openstack-meeting21:00
jd__#startmeeting ceilometer21:00
openstackMeeting started Wed Aug 28 21:00:40 2013 UTC and is due to finish in 60 minutes.  The chair is jd__. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: ceilometer)"21:00
openstackThe meeting name has been set to 'ceilometer'21:00
thomasmo/21:00
dragondmo/21:00
dhellmanno/21:00
terriyuo/21:00
sandywalsho/21:00
herndono/21:00
llu-laptopo/21:00
eglynno/21:01
gordco/21:01
jd__#topic Review Havana-3 milestone21:02
*** openstack changes topic to "Review Havana-3 milestone (Meeting topic: ceilometer)"21:02
silehto/21:02
jd__#link https://launchpad.net/ceilometer/+milestone/havana-321:02
*** xBsd has quit IRC21:02
*** dkranz has quit IRC21:02
asalkeldo/21:02
eglynnI've made progress on the alarm history API21:02
eglynn(currently under review)21:03
jd__I'm sad to announce we're probably the worst project21:03
eglynnon the alarm service partitioner ...21:03
eglynnjd__: harsh!21:03
jd__so BOOO!21:03
jd__:-)21:03
*** Tross has joined #openstack-meeting21:03
* dhellmann hangs head in shame21:03
* terriyu feels bad21:03
eglynnI've been back to the drawing board a few times on the partitoner21:03
gordcworst as in we have the most open still?21:03
*** chuckieb has quit IRC21:03
jd__more seriously, we're getting better since eglynn's back we really need more review at this point21:03
dhellmannI've allocated time this sprint to do a lot of reviewing, though, and don't really expect to submit any code myself between now and h321:04
*** nwidell has joined #openstack-meeting21:04
eglynnbut I think I've workable and reasonably simply solution now for the paritioner21:04
*** nealph has joined #openstack-meeting21:04
jd__gordc: yes21:04
*** colinmcnamara has quit IRC21:04
eglynn(with the coordination between evaluators done over fanout AMQP)21:04
eglynn... cleaning it up currently21:04
jd__but Low priority are not really followed21:04
eglynnand adding test coverage21:04
*** colinmcnamara has joined #openstack-meeting21:04
jd__eglynn: fair enough21:04
eglynnhope to have a patch series proposed by end of week21:04
*** meganw has quit IRC21:04
gordcwe can close off count-api-requests bp right?21:04
sandywalshjd__, once I get this branch pushed up, I'll be doing a lot more review21:04
jd__considering the amount of time needed for reviewing, the end of the week is likely the ultimate deadline21:05
jd__sandywalsh: cool thanks21:05
gordci'll be doing pure reviews/bug fixes from now on.21:05
silehtjd__, I think db-tests-with-scenarios is finished21:05
dragondmI'm reviewing as well.21:05
jd__gordc: I need to update our oslo copy to bring the middleware before21:05
eglynnk21:05
*** meganw has joined #openstack-meeting21:05
jd__sileht: if you think so, can you change the status?21:05
gordcjd__: got it.21:05
terriyuI just submitted a new patch for my group by blueprint today21:05
jd__thanks dragondm21:05
silehtjd__, sure21:06
terriyucode review on this patch would be great https://review.openstack.org/#/c/44130/21:06
jd__I think some effort should be done on the pagination API, the patches are now in the queue for a long time21:06
jd__too long in my opinion21:06
gordcdid we settle the marker_pair stuff? i remember seeing a discussion on that.21:07
eglynndo we have a definition conclusion on the marker field for paging thru meters?21:07
eglynnsnap ...21:07
gordceglynn: :)21:07
jd__well I think dhellmann proposed a sane solution by using a combination of multiple fields21:07
eglynnah yes21:07
jd__the problem is that a lot of the discussion has been confused between samples/meters21:08
*** lpabon has quit IRC21:08
*** Tross has quit IRC21:08
dhellmannyes, all of that is confusing and also irrelevant21:08
dhellmannwe don't need numerical ids21:08
*** colinmcnamara has quit IRC21:08
*** jodom has joined #openstack-meeting21:08
*** shaneduan has joined #openstack-meeting21:08
dhellmannthe unique id for the value returned by the meters query is the name of the meter and the id of the resource on which that meter is collecting data21:08
*** boris-42 has joined #openstack-meeting21:08
*** meganw has quit IRC21:09
dhellmannso the marker should be the pair of those values, combined in some semi-opaque way so we can make it a single string21:09
*** meganw has joined #openstack-meeting21:09
*** topol has quit IRC21:09
jd__I hope it's clear to Fengqian21:09
eglynnbut we won't rely on the caller to do the attribute concatention or anything like that?21:09
silehtdhellmann, I agree the rest API user shouldn't be able to choose the marker21:10
*** TravT has quit IRC21:10
gordcdhellmann: i should track the comments from this patch? https://review.openstack.org/#/c/35454/21:10
dhellmanneglynn: no, we give the caller a marker value and they give it back to us, they shouldn't have to know what it is21:10
eglynndhellmann: cool21:10
*** jrodom has quit IRC21:10
dhellmannthat's what jay was saying about not having them give us "keys" as well as values -- they just give us one value21:10
dhellmanngordc: looking21:11
*** martine_ has quit IRC21:11
dhellmannok, sorting21:11
sandywalshright21:11
jaypipesoh, hi guys.21:11
dhellmannwe have to sort on the marker value before any user-provided sort keys21:11
sandywalshit's a magic cookie21:11
dragondmyup21:12
dhellmannand we always sort on that value, no matter what21:12
jd__sir yes sir! :)21:12
dhellmannthat way the marker always works, even if they don't specify a sort21:12
jaypipesdhellmann: right, and then in addition, sort on any user-provided sort keys.21:12
dhellmannright21:12
jd__if anything's not clear in the review about that we need to make it clear what we expect to Fengqian otherwise I don't think it'll progress21:13
dhellmannso we don't need to look in the database to make sure the marker is valid or anything like that any more21:13
dhellmannok21:13
eglynndumb question ... how is the marker attribute distinguished in the representation returned to the caller?21:13
dhellmannI'll add some comments to that review21:13
jd__and cigar number 3's coming fast21:13
* jaypipes thinks it would behoove the project to first start with a cleanup of the meter table to a) rename message_id to sample_id, and b) make it the primary key... then you only ever would need to provide a single marker value...21:14
dhellmanneglynn: it's a completely separate part of the return value, either in the "next" link or as a separate value21:14
dhellmannso you get a list of return values, a marker, a list of links, etc.21:14
eglynndhellmann: a-ha, got it21:14
jd__jaypipes: +inf21:14
jd__jaypipes: I think it's too late but I've pushed a lot of effort in the rest of the code base toward this, so doing it so in the storage backends would be much welcome21:14
* dhellmann thinks about what jaypipes said21:14
jaypipesdhellmann: would make the sorting/marker code easier, since only single field primary keys...21:15
*** ianw has joined #openstack-meeting21:15
dhellmannI think I see it. We're joining on the samples already, so if we return one of their ids as a marker then we don't need a composite marker? And that works because the sample id implies both a resource and a meter name21:15
jd__that could work indeed21:15
sandywalshwell, we should consider a proper sample table since the motivation of it is good21:16
dhellmann"proper sample table"?21:16
thomasmI am about to submit a bug fix that sorts on timestamp and ID as a tiebreaker.21:17
*** boris-42 has quit IRC21:17
thomasmin that function21:17
thomasmWell, get_resources21:17
gordci like this message_id to sample_id idea... do we have time to get both that and pagination stuff in by next week?21:17
gordci would think one would have to take priority.21:18
sandywalshdhellmann, an actual Sample table ... a smaller table that back links to Meter, with fewer fields that represent just the change in measurement21:18
jd__gordc: I don't think so21:18
jd__we need to wrap up21:18
* dhellmann wonders if we don't want to just say we'll need a ffe for pagination now, since it's likely21:18
dhellmannsandywalsh: ah, ok21:18
*** edgarstp has quit IRC21:18
gordcjd__: yeah, that's what i was thinking. wishful thinking for havana.21:18
jd__gordc: icehouse :)21:18
*** jasondotstar has quit IRC21:19
dhellmannso do we say "no pagination in havana" or "pagination will not make the h3 freeze"?21:19
dhellmannI wonder if we can get it done for havana at all, but I'm not writing it, so...21:19
dragondmyah, & if you redo the sample table in icehouse, mebbe we should redo the timestamps in atleast the sql backend to increase precision to < 1s ?21:19
jd__dhellmann: I think we're going to try until the end21:20
thomasmdragondm +121:20
jd__since the feature have been proposed long before the freeze we can have a freeze exception I guess21:20
thomasmIt depends also on if we have a floor version for some of the backends21:20
dhellmannjd__: cool21:20
sandywalshdragondm, +121:20
jd__#topic Ditch Alembic for Havana? (sandy)21:21
*** openstack changes topic to "Ditch Alembic for Havana? (sandy) (Meeting topic: ceilometer)"21:21
thomasmWell, not exactly if we want to go with the Decimal approach21:21
dhellmannif we're going for it, we should try to change the schema only as much as is needed for pagination, and not for unrelated things21:21
jd__that's kind of a good topic as a following I guess21:21
*** ayoung has quit IRC21:21
jaypipesdhellmann: exactly.21:21
sandywalshso, not rip out the alembic work, but the held up branches can use sqlalchemy-migration for H321:21
dragondmdhellmann: yes.21:21
*** timductive has joined #openstack-meeting21:21
*** rongze has quit IRC21:21
jd__I really think that it's too late for such a drastic change21:22
*** timductive has left #openstack-meeting21:22
jd__couldn't we just make things works?21:22
sandywalsh(since there are big issues with alembic under sqlite)21:22
dhellmannwe don't need to take it out21:22
dhellmannwe can just allow more sqlalchemy-migrate scripts21:22
sandywalshright, don't remove anything, just add a few new migrations to sqlalchemy-migrate21:22
gordcfor reference: https://bugs.launchpad.net/ceilometer/+bug/121715621:22
dhellmannthis is *exactly* why I didn't want the old scripts migrated and the old tool removed21:22
uvirtbotLaunchpad bug 1217156 in ceilometer "Alembic migrations not tested -- and they don't work for SQLite" [Undecided,New]21:22
jaypipesI think a good compromise would be doing the sample_id PK thing and then getting the migration upgrade removed from the base test case...21:22
*** rongze has joined #openstack-meeting21:23
jaypipesthat way tests would use the sqlalchemy.MetaData.create_all() call and would not re-run migrations on every test case of the storage test cases21:23
jaypipesand we could write specific tests for migrations in the style of Glance and Nova21:23
dhellmannI think those are 2 separate things though, right? I agree we want both at some point, but I'm not sure we need the second now.21:24
jaypipesheck, Alembic doesn't work with SQLite, anyway, so we can't test the alembic migrations in the unit tests..21:24
sandywalshright, that would be the goal, but unlikely given the time frame21:24
dhellmannjaypipes: alembic and sqlalchemy-migrate have the same limitations with sqlite, the difference is we're monkeypatching sqlalchemy-migrate all over the place21:24
jd__well, there's a MySQL usable in CI for unit testing I think, jaypipes21:25
jaypipesdhellmann: yes, indeed :) I've written many o monkey patched sqlite migration :)21:25
jd__I imagine you already know though :)21:25
jaypipesjd__: well, that's great for testing migrations, yes. SQLite is fine for unit tests though...21:25
dhellmannjaypipes: did you see the stuff boris's team put in oslo's db module to catch some changes and translate them automatically?21:25
jd__jaypipes: agreed :)21:25
jaypipesdhellmann: some of it... you talking about stuff like the unique constraint naming?21:26
*** nati_uen_ has joined #openstack-meeting21:26
dhellmannjaypipes: also column renaming I think21:26
jaypipesdhellmann: heh, but it doesn't work unfortunately :) or at least, it doesn't work when you try and run the very first alembic migration in Ceilometer against a SQLite db.21:26
*** henrynash has quit IRC21:27
gordcsorry i need to drop, talk to you guys later.  jd__: my meeting topic will be posted to mailinglist.21:27
dhellmann#link https://github.com/openstack/oslo-incubator/blob/master/openstack/common/db/sqlalchemy/migration.py#L16321:27
dhellmannlooks like it is just about unique constraints at this point21:27
dhellmannjaypipes: right, this was just for sqlalchemy-migrate :-(21:27
*** gordc has left #openstack-meeting21:27
*** gordc has quit IRC21:28
jaypipesdhellmann: right.21:28
*** dcramer_ has quit IRC21:28
dhellmannanyway, did we agree to just let folks continue to write sqlalchemy-migrate scripts instead of moving to alembic for havana?21:28
jd__hm, but don't we already have alembic stuff? isn't there an upgrade order issue likely?21:29
*** jlucci has quit IRC21:29
jaypipesso, here's another idea... at the start of the next release cycle, we're supposed to condense all existing migrations into a single one, named for the release. How about we just put off any of these changes until the start of Icehouse, and then immediately do a single "init" Alembic migration for havana, and then delete SA-migrate entirely.21:29
sandywalshjd__, don't think so ... i've converted mine from alembic back to migrate and it seems happy21:29
dhellmannjd__: did anyone successfully create an alembic script?21:29
jd__dhellmann: I thought so?21:30
*** nati_uen_ has quit IRC21:30
jaypipesdhellmann: I've successfully created one, sure... running it? not so much ;)21:30
herndonyes, there are a couple21:30
sandywalshdhellmann, only simple ones, the index/constraint related ones puke21:30
jd__there's things in ./storage/sqlalchemy/alembic/versions21:30
jaypipesherndon: I could not get either alembic migration to run.21:30
dhellmannjaypipes: how would that work for people doing continuous deployment? they would end up with a new migration that was apparently not run but that tries to put their database into a state that it's already in21:30
*** nati_uen_ has joined #openstack-meeting21:30
*** thomasbiege has quit IRC21:31
jaypipesdhellmann: we could add a single check to the migrate() routine that does an introspection of a single table that we know should have a particular schema... if the check returns True, then we simply instruct alembic that the schema is already up to date?21:31
*** egallen has quit IRC21:32
dhellmannjaypipes: I guess that would work.21:32
* dhellmann hates rolling up migrations21:32
jaypipesdhellmann: there is another alternative :) We could convert all of the sqlalchemy-migrate versions into alembic migrations.21:33
jaypipesand then remove sa-migrate entirely.21:33
dhellmannjaypipes: but if alembic doesn't work...21:33
sandywalshI'd rather that approach21:33
*** henrynash has joined #openstack-meeting21:33
jaypipesdhellmann: well if alembic doesn't work, then either way we're screwed :)21:33
sandywalshwell, if alembic doesn't work, we've got larger issues21:33
dhellmannand we have the same problem, because we have to *for each migration* figure out if it needs to be run or not21:33
sandywalshuh, what jay said :)21:33
jaypipesdhellmann: since alembic is already in ceilometer :)21:33
dhellmannbut if it's not actually doing anything21:33
dhellmannit doesn't matter, right?21:34
jaypipesdhellmann: that's partly why I wrote that email recommending to remove one  or the other..21:34
silehtdhellmann, we have 2 migrations scripts in alembic21:34
*** henrynash has quit IRC21:34
dhellmannah, well, ok21:34
jaypipessileht: they don't work.21:34
jaypipessileht: https://bugs.launchpad.net/ceilometer/+bug/121715621:34
uvirtbotLaunchpad bug 1217156 in ceilometer "Alembic migrations not tested -- and they don't work for SQLite" [Undecided,New]21:34
jaypipessileht: or at least, they don't work in the current ceilometer test setup...21:34
eglynnis the problem limited to sqlite?21:35
dhellmannwe had a long discussion about this on the mailing list, and several projects agreed to the same approach, so if we're going to change directions entirely we should bring it back there I guess21:35
dhellmanneglynn: yes, sqlite doesn't support some forms of ALTER TABLE21:35
eglynndhellmann: gotcha, thanks21:35
jaypipeseglynn: don't think so.. it's a Python error in that bug report.21:35
dhellmannhow is it that the tests are running the migrations and they are in master but are now failing?21:36
dhellmannwhat happened to them in the gate?21:36
jaypipeseglynn: "AttributeError: 'Column' object has no attribute 'create'" for the fix_meter_resource_m migration.21:36
jaypipesdhellmann: I mention in the bug report I just do not think these migrations are running in the tests...21:37
dhellmannah21:37
sandywalshit's the alter table that was giving me the grief. Complaining that the new column already existed. I suspect there was a create_all() going on under the hood.21:37
herndonjaypipes: what's different about them? tests from your event types patch are running and failing. does not compute...21:37
jaypipesherndon: I'm not sure :( Perhaps there is something about my submitted alembic migration that doesn't jive with SQLite...21:38
herndonsandywalsh: +1. jaypipes: your alembic migration is supposed to follow the existing migrations right? If there is a python error in those tests, I would never expect it to get to the point where it is trying to create event_types in alembic… am I missing something?21:40
jaypipesherndon: that is my understanding as well... but I can't get to a testable place :(21:40
*** sacharya has quit IRC21:41
sandywalshso, the way I see it is, there are other people actively working on the problem. We can allow new sqlalchemy-migrations without issue and, once they resolve the problem, either convert fully to alembic or run both as they are now. Whatever they recommend.21:41
jaypipesherndon: when I tried to "step through" the alembic migrations after running all the sa-migrate migrations successfully, i ran into that bug above :(21:41
*** thomasbiege has joined #openstack-meeting21:41
*** eharney has quit IRC21:41
sandywalshbut we shouldn't take on big make-work projects like this so close to H321:41
jaypipessandywalsh: my original patch had a working sa-migrate migration :)21:41
sandywalshjaypipes, me too21:41
sandywalshif anything, we should likely convert the existing alembic migrations to migrate just in case21:42
jaypipeslook, I don't mind going the alembic route at all... I tried to create a working alembic migration, and from what I can tell, it should have worked, but I can't get an environment running that enables me to test it in a step-by-step fashion :(21:42
sandywalsh+1 ... I'm a fan of alembic, looks quite nice. It's just a rough patch for us right now21:43
jaypipesagreed...21:43
herndon+121:43
sandywalsh(heh, the three people with alembic patch issues :)21:43
jaypipeslol21:44
jd__fair enough21:44
jaypipesok, so dhellmann and jd__, should we stick to sa-migrate patches for right now, then deal with alembic (translation of sa-migration stuff and removal) in first order of business in Icehouse?21:44
dragondmI think the problem is more that sqlite is a PITA, and we haven added the requisite hacks to alembic yet to deal w/ it.21:44
dhellmannjaypipes: I think that's probably the best approach21:45
sandywalshfair point21:45
jaypipesdragondm: and Mike Bayer has said he is not interested in hacking alembic to support failures in sqlite :)21:45
jd__jaypipes: yes that'll be good enough21:45
jaypipesjd__: ok. well I will volunteer to make the Icehouse sa-migrate stuff a top priority for me. I can do a lot of that work.21:46
herndonstill unresolved: do we need to move the existing alembic migrations to sa-migrate until alembic is more stable?21:46
jd__one point we may want to stop playing with sqlite and starts mysql at test time like we do with mongo for example, if that's something possible (thinking out loud)21:46
dragondmjaypipes: yah, and I can agree with that. (by add hacks read: workarounds so we don't need to do migrations on sqlite during tests )21:46
jaypipesyeah21:46
jd__jaypipes: sign here please -->21:46
jaypipesjd__: possibly, for the sqlalchemy storage tests at least, yes.21:46
* jaypipes signs paperwork.21:46
jd__great :)21:47
jaypipesback to what herndon was saying...21:47
jaypipesyou want me to submit a preliminary patch that moves the two alembic migrations to sa-migrate ones?21:47
jd__herndon: I don't think we *need* to21:47
*** jecarey has quit IRC21:47
jd__if there's enough time it might be even better to do though21:47
dragondmjd__: +1 sqlite is fine for unittests where  we can just dump a schema in a blank db. for testing data migrations, etc, starting mysql should be acceptable .21:47
jaypipesjd__: yeah.. I think it's worth it..21:47
dhellmannyeah, I would be worried about anyone doing CD who has already applied those changes21:47
*** pentameter has quit IRC21:47
jd__do you, sir jaypipes signatory of the sqlalchemy, could do that?21:47
jaypipesdragondm: ++21:48
jaypipesjd__: sure thing.21:48
jaypipesI can work on that tonight.21:48
jd__LADIES AND GENTLEMEN, HE CAN DO IT!21:48
sandywalshdragondm, +121:48
jaypipeslol21:48
jd__jaypipes: thanks :)21:48
sandywalsh:)21:48
jaypipesnp21:48
jd__that'll make us ship something I'll be less ashame of in this regard21:48
sandywalshjaypipes gets an "atta boy"21:49
jaypipesheh21:49
jd__#topic Release python-ceilometerclient?21:49
*** openstack changes topic to "Release python-ceilometerclient? (Meeting topic: ceilometer)"21:49
jd__I don't think we need it21:49
eglynnme neither21:49
jd__#topic Open discussion21:50
*** openstack changes topic to "Open discussion (Meeting topic: ceilometer)"21:50
jaypipeslol21:50
jaypipesquickest topic EVAR.21:50
*** meganw has quit IRC21:50
nealphquestion on "dispatchers" and "publishers": we seem to have overlapping functionality. IIRC, we decided to keep both  so folks can push data out directly from the agent (i.e. parallel to rpc publish) and/or at the end of the pipeline.21:50
nealpham I remembering correctly?21:51
*** meganw has joined #openstack-meeting21:51
*** nwidell has quit IRC21:52
litong@nealph, you can not use publisher to replace a dispatcher. they are not the same as far as I can tell.21:52
sandywalshnealph, dispatchers are on raw notifications and publishers are with samples, iirc21:52
dhellmannsandywalsh: right21:52
nealphhrmmm, okay, I'll look at it a little deeper.21:52
litongpublisher deals with meter (object), dispatcher takes the data as is.21:52
sandywalshand dragondm's trigger pipeline will be with events21:52
dragondmyup.21:53
*** sushils has quit IRC21:54
dragondm(and honestly I'd like to convert raw notification proccessing to use events instead)21:54
litong@dragondm, not really, raw data can contain more stuff then you can possibly predict.21:54
litong@dragondm, you do not really want to do that.21:55
dragondmyes, but you know what you need.21:55
sandywalshlitong, events are the stripped down version of the raw notification with the stuff you know you want21:55
*** meganw has quit IRC21:55
sandywalshlitong, but we will still store the full raw notification21:56
sandywalsh(just in case, as you say)21:56
litongthat is exactly the point, you want the dispatchers to deal with the data logic.21:56
sandywalshah, I see your point21:56
sandywalshyes, true21:56
*** bgorski has quit IRC21:56
dragondmYup. The reason, for one, is so we can process the data with the same tools whether it's just arrived, or has been persisted awaiting future needed data.21:56
dragondmdata logic?21:57
litongdata logic, the structure, whatever it maybe. how to interpret what is in raw data etc.21:57
*** vijendar has quit IRC21:57
sandywalsh(like the log dispatcher, it has no idea what the notification has, but it wants to log the whole thing)21:58
litongwho knows what might be in it. but a dispatcher can be very specific. all raw data goes through a dispatcher if it is enabled.21:58
dragondmlitong: ah. yes. Have you looked at https://review.openstack.org/#/c/42713/21:58
litong@sandywalsh, +121:58
*** fifieldt has joined #openstack-meeting21:58
*** Tross has joined #openstack-meeting21:59
litong@dragondm, no, I have not.21:59
jd__sorry, I have to end the meeting guys21:59
litonggood day folks.21:59
sandywalshgg21:59
jd__feel free to continue on #openstack-metering if needed :)21:59
jd__have a nice day and happy hacking21:59
nealphk. thanks!21:59
eglynn'night folks21:59
dhellmanngood night!21:59
jd__#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
dragondmG'NIGHT!22:00
openstackMeeting ended Wed Aug 28 22:00:01 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-08-28-21.00.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-08-28-21.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ceilometer/2013/ceilometer.2013-08-28-21.00.log.html22:00
*** litong has quit IRC22:00
*** dhellmann is now known as dhellmann_22:00
*** fifieldt_ has joined #openstack-meeting22:00
silehtnight22:00
*** ivasev has quit IRC22:01
thomasmTake it easy!22:01
*** thomasm has quit IRC22:02
*** thomasm has joined #openstack-meeting22:02
*** meganw has joined #openstack-meeting22:03
*** thomasm has quit IRC22:03
*** markmcclain has joined #openstack-meeting22:03
*** meganw_ has joined #openstack-meeting22:03
*** thomasbiege has quit IRC22:03
*** llu-laptop has quit IRC22:04
*** nati_uen_ has quit IRC22:04
*** meganw_ has quit IRC22:05
*** meganw_ has joined #openstack-meeting22:05
*** nati_uen_ has joined #openstack-meeting22:06
*** epende has quit IRC22:06
*** nati_uen_ has quit IRC22:06
*** meganw_ has quit IRC22:07
*** nati_uen_ has joined #openstack-meeting22:07
*** meganw_ has joined #openstack-meeting22:07
*** meganw has quit IRC22:07
*** Toshi has quit IRC22:11
*** meganw_ has quit IRC22:12
*** galstrom is now known as galstrom_zzz22:16
*** fifieldt has quit IRC22:18
*** IlyaE has joined #openstack-meeting22:18
*** flaper87 is now known as flaper87|afk22:20
*** spzala has quit IRC22:21
*** eharney has joined #openstack-meeting22:21
*** dscannell has quit IRC22:21
*** AlanClark has quit IRC22:22
*** henrynash has joined #openstack-meeting22:24
*** rods1 has quit IRC22:24
*** changbl has quit IRC22:26
*** markmcclain has quit IRC22:29
*** markmcclain has joined #openstack-meeting22:30
*** tanisdl_ has joined #openstack-meeting22:30
*** ilyashakhat_ has joined #openstack-meeting22:31
*** dkranz has joined #openstack-meeting22:31
*** woodspa has quit IRC22:31
*** ilyashakhat has quit IRC22:31
*** tanisdl has quit IRC22:33
*** tanisdl_ is now known as tanisdl22:33
*** radsy has joined #openstack-meeting22:36
*** dims has quit IRC22:38
*** kebray has quit IRC22:38
*** henrynash_ has joined #openstack-meeting22:41
*** henrynash has quit IRC22:43
*** henrynash_ is now known as henrynash22:43
*** thedodd has quit IRC22:44
*** Tross has quit IRC22:46
*** jmontemayor has quit IRC22:46
*** sushils has joined #openstack-meeting22:51
*** eglynn has quit IRC22:51
*** sacharya has joined #openstack-meeting22:53
*** dims has joined #openstack-meeting22:53
*** jodom has quit IRC22:54
*** sushils has quit IRC22:56
*** sushils has joined #openstack-meeting22:58
*** Toshi has joined #openstack-meeting22:59
*** herndon has quit IRC22:59
*** nati_ue__ has joined #openstack-meeting23:01
*** fifieldt has joined #openstack-meeting23:01
*** markmcclain1 has joined #openstack-meeting23:01
reedhello23:02
fifieldthi23:02
fifieldtsorry I'm late!23:02
reed1 minute is not late23:02
fifieldt_meeting time?23:02
fifieldt_:D23:02
*** fifieldt has quit IRC23:03
reed#meetingstart openstack-community23:03
*** fifieldt_ is now known as fifieldt23:03
reed#startmeeting openstack-community23:03
openstackMeeting started Wed Aug 28 23:03:18 2013 UTC and is due to finish in 60 minutes.  The chair is reed. Information about MeetBot at http://wiki.debian.org/MeetBot.23:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.23:03
*** openstack changes topic to " (Meeting topic: openstack-community)"23:03
openstackThe meeting name has been set to 'openstack_community'23:03
fifieldt#link https://wiki.openstack.org/wiki/Meetings/Community#Agenda_for_next_meeting23:03
reed#topic review action times from last meeting23:03
*** openstack changes topic to "review action times from last meeting (Meeting topic: openstack-community)"23:03
*** markmcclain has quit IRC23:03
reedI have contacted Hui Cheng, Bruce Lok and Yujie Du to recruite Ask moderators in ZH23:04
fifieldtgreat!23:04
reedno reply from Cheng, he must be busy with his startup23:04
reedthe others are interested and happy to help23:05
fifieldtgood news23:05
*** nati_uen_ has quit IRC23:05
reedI think it would be good to setup a training session with them and other volunteer moderators, not just rely on each of them reading the wiki page23:05
reedthoughts?23:05
fifieldtsounds good23:06
fifieldtwhat format are you thinking?23:06
*** morganfainberg|a is now known as morganfainberg23:06
fifieldtgetting them on the live system working on real questions?23:06
reedi am not sure what would be optimal23:06
reedthat sounds like a good idea actually23:07
reedI was thinking also to invite moderators in other Q&A sites, like askubuntu or ask fedora23:07
fifieldtI think there's enough on there that task one could be "find a question that needs help"23:07
fifieldtmmm, good thinking - if they like the pain of moderating, maybe they want more?23:07
fifieldt:)23:07
reedit's more to pick their brains,  they can give us ideas and thoughts too...23:08
fifieldtoh, right!23:08
fifieldtthat is a good idea23:08
fifieldtperhaps we could also start a post on the CLS forum or g+ thing?23:08
reednot sure who's on the G+ thing but yeah, spread the word as much as possible23:09
reeda blog post would be good too23:09
fifieldtindeed23:10
reedthe timeframe is  tight though23:10
fifieldtmake it a dual announce-chinese and ask for moderators?23:10
reedIMHO two announcements is better23:10
fifieldtok23:10
*** markpeek has quit IRC23:10
reedI was thinking moderators first because I'm afraid of getting too many questions at once and no moderators23:11
fifieldtright, ok23:11
reedfor English I feel can deal more easily with high volumes, in ZH not sure we can leave the site unattended at the beginning23:11
fifieldtI was thinking along the lines of motivation to join ... if there's no content, it's more difficult to get moderators23:12
fifieldtnot a strong feeling :)23:12
reeda good one-two combo may work better then: time the training moderators thing first and start shooting  announcements soon after23:13
fifieldtcool23:13
reedactually, this may work well because there is a Cloud Open something conference cloud in China (Shanghai IIRC) mid september and Lauren wants to issue a press release, we may mention Ask in ZH there23:14
fifieldtindeed23:14
* fifieldt will be at that one23:14
reedwhen is it exactly?23:14
fifieldt15-17 sept23:14
*** sarob has joined #openstack-meeting23:14
reedok, so the PR will be later next week or so23:14
*** neelashah has quit IRC23:14
reedwe need to have this session ASAP then23:15
fifieldtyup23:15
reedlike one week from now?23:15
fifieldtsure23:15
reedin Asian time zone, I think23:15
reedwhat time is it in China now?23:15
fifieldt071523:15
reedso one hour later? 0800... too early?23:16
reedi fear that if we do it later we may totally miss the US east coast23:16
fifieldtindeed23:16
reedeven so it's late for them23:17
reedoh well23:17
fifieldtI consider 0800 early, but it depends very much on the individual23:17
*** nati_ue__ has quit IRC23:17
fifieldtsometimes volunteers for these kind of activities can't meet during work hours23:17
reedis HK in the same timezone as China?23:17
fifieldtyup23:17
fifieldt"CST"23:17
reedk, so the plan is to:23:18
*** sabeen has quit IRC23:18
reed- date for the event is Sep 4th, 5pm PDT23:19
*** cyeoh is now known as cyeoh_23:19
reed- invite moderators wannabe and people from around various communities, groups to give us advice23:19
fifieldtwould you consider asking people what an appropriate time is?23:20
fifieldtusing doodle or similar?23:20
reed- format: brief introduction (from the wiki page) and real life intervention on questions23:20
fifieldtformat looks good23:21
*** Guest20987 has quit IRC23:21
*** jaypipes has quit IRC23:21
reedfifieldt, that may work too... it may require more time though23:21
reedyou need to give people time to see the survey and respond, and then announce the date23:21
fifieldtchoose a date, but ask for the time23:22
*** henrynash has quit IRC23:22
fifieldtmaybe it's like a 'registration' step23:22
*** marun has quit IRC23:22
fifieldtyou just give a couple of options23:22
*** dims has quit IRC23:22
reedlet's check with Lauren when she wants to have the PR ready to go out23:23
fifieldtok23:23
reedmaybe we have more time than that23:23
*** dims has joined #openstack-meeting23:24
reedor we just skip the announcement now and we do this training well23:24
fifieldtyeah, that might be a better option23:24
reedagreed23:24
reedset the bar to do this well and if we make it to the PR deadline, well, otherwise you'll mention it during your talk23:25
reedand we keep soft launching that way until big launch in HK23:25
fifieldtreed, example poll: http://doodle.com/b7agkwpgk59mdke523:26
*** shaneduan has left #openstack-meeting23:26
*** xBsd has joined #openstack-meeting23:26
reedfifieldt, looking good23:27
reednot23:27
reed5am PDT is out of question for me :)23:27
fifieldt:P23:27
*** haomaiwang has joined #openstack-meeting23:27
fifieldtadmin link is https://doodle.com/b7agkwpgk59mdke5699uem8w/admin?tmail=poll_admin_adminlink&tlink=adminbtn23:28
*** dscannell has joined #openstack-meeting23:28
*** dims has quit IRC23:28
*** haomaiwa_ has quit IRC23:28
reedok, will work on it later23:29
fifieldtwe should probably move to the next topic23:29
reedI think we have a plan23:29
fifieldtagreeed23:29
*** morganfainberg is now known as morganfainberg|a23:29
reed#info setting up a training session for moderators of Ask OpenStack, focusing on training new mods for Chinese language23:30
*** dims has joined #openstack-meeting23:30
reed#action reed to organize the event before Sep 1423:30
reednext topic is...23:31
fifieldtreed to draft a blog post to describe the training sprint, link to eventbrite, objectives and process ?23:31
*** dscannell has quit IRC23:31
reedfifieldt, haven't done that, fell off the list for this week23:31
fifieldtcoolo23:31
reedthe main reason why it fell off the list is that I need to understand it a bit more first23:31
reeddo you have a clear picture of that whole effort?23:32
fifieldtit is an ambitious project!23:32
fifieldtsarob ran me through things23:32
fifieldtone meeting where it was just us two23:32
fifieldtit should be logged23:32
reedi spoke with Jonathan about it yesterday, he gave me his view23:32
fifieldthttp://eavesdrop.openstack.org/meetings/openstack_community/2013/openstack_community.2013-08-14-22.59.log.html23:33
*** zul has joined #openstack-meeting23:33
fifieldthas the conversation which is the sum of my knowledge more or less23:33
reeddo you think you would be able to write the post easily?23:33
fifieldtmaybe not easily, but I could give it a start23:33
*** spzala has joined #openstack-meeting23:34
reedthat'd be good, it would speed things up23:34
fifieldtok, I'll get on that23:34
*** gongysh has joined #openstack-meeting23:34
reedI have commented on the out of date wiki pages :)23:34
fifieldtthank you :D23:35
fifieldt#info discussion on obsolete wiki pages continues on mailing list23:35
reed#action fifieldt to give a first stab at drafting the blog post for the training sprint23:35
reedso many threads :(23:35
reedok, we've exausted this topic I think23:36
fifieldt+123:36
reed#topic status update for running projects23:37
*** openstack changes topic to "status update for running projects (Meeting topic: openstack-community)"23:37
reed#info Activity Board Dash (the Bitergia charts) are getting integrated in stackforge, first step towards a tighter integration into the official Infrastructure23:38
*** changbl has joined #openstack-meeting23:38
*** adrian_otto has quit IRC23:38
clarkb#link https://review.openstack.org/#/c/44057/23:38
*** markmcclain1 has quit IRC23:39
fifieldt:D23:39
reedI'm working with them to create a roadmap for the Havana report23:39
reedthanks clarkb... my attempts to learn puppet go in that direction too, my patch is in draft :) too embarrassed to show it23:40
reedi'll share it with fifieldt23:40
reedhttps://review.openstack.org/#/c/42998/23:41
fifieldt:D23:41
clarkbdon't be embarrased :)23:42
reed#info the Groups portal is still waiting for the server to be created. Should be ready any time now23:42
reed#link https://review.openstack.org/#/c/42608/23:42
*** dscannell has joined #openstack-meeting23:42
*** morganfainberg|a is now known as morganfainberg23:42
fifieldtgood, good23:43
*** rdxc has quit IRC23:43
*** sacharya has quit IRC23:43
reed#info the Insights part of Activity Board is being updated to a new version. Some data (affiliation, especially) is not being updated... investigating23:43
*** spzala has quit IRC23:43
*** gongysh has quit IRC23:44
*** gongysh has joined #openstack-meeting23:44
fifieldtgoodo23:45
reed#info Ask project: waiting for an estimate (sprint plan) from the Askbot folks for adding new features (including import questions from Launchpad) and fixing some small issues23:45
fifieldtcool23:46
reedfifieldt, what's cooking on your side?23:46
*** michchap has joined #openstack-meeting23:46
fifieldtwell, the next post for the ambassador program went up23:46
fifieldt#link http://www.openstack.org/blog/2013/08/ambassador-program-specifics/23:46
*** fnaval_ has quit IRC23:46
fifieldtand we already have 3 applicants23:46
fifieldtbrave people!23:46
fifieldtI'm going to be writing a bunch of copy for an introductory pack23:47
fifieldtthat needs to be done before the end of sept23:47
fifieldtthere's some discussions going on in i18n and docs to get japanese operations guide online, and chinese translation effort for same is ramping up to get it from 80% to 100%23:48
fifieldtthe trystack survey is getting a lot more reponses now the link is on the login page23:48
fifieldtI started looking at the kind of analysis that could be done with this data23:48
*** michchap has quit IRC23:48
fifieldtheat made it to transifex23:49
*** michchap has joined #openstack-meeting23:49
fifieldtworking to update the user survey for a big push in september23:49
reedsounds good... when do you close the survey? or start looking into the results?23:49
fifieldtthat's probably the ongoing projects from me23:49
fifieldtit's looking like the first week of october so far23:49
fifieldtoh23:49
reedthe trystack survey I mean23:49
fifieldttrystack23:49
fifieldtany suggestions?23:49
fifieldtlet me see how many results we got23:50
fifieldtmoment23:50
fifieldtsitting at 61 results so far23:50
reedyeah, i don't think we need to rush it until we get the urgency to make any decision about trystack :)23:50
fifieldtyeah, even keeping it open for another month is fine I think23:50
fifieldtbut closing some time before the summit23:50
reedand propose a session for design summit in hk?23:50
fifieldtstraw man date: October 4th?23:50
fifieldtthere is already a couple of trystack sessions proposed23:51
fifieldtso maybe will just provide the data to those speakers23:51
reedgood, we'll show up with data :)23:51
reedfifieldt, ? when did the proposals for design summit open?23:51
fifieldtoh, design summit23:51
fifieldtsorry I meant conference23:51
*** dscannell has quit IRC23:51
fifieldtwe could do a design summit session, sure23:52
fifieldtthat's a good idea23:52
*** herndon has joined #openstack-meeting23:52
reed#info let's look at the data from trystack survey once the design summit opens for proposals23:53
fifieldtdone23:53
*** markpeek has joined #openstack-meeting23:53
reednow, since you mentioned i18n, I think we have an issue to solve together with the infra team23:53
fifieldtyes?23:54
reedwell... since transifex is not open source anymore we may want to look into alternatives23:54
reedand alternatives mean also provide these alternatives23:54
fifieldtright, indeed23:54
reedand the main alternative at the moment is self hosted poodle23:55
reedin order for the i18n team to evaluate it somebody needs to set that service up for testing23:55
reedi'll bring this up with jeblair and fungi23:55
fifieldtta23:56
*** alexpilotti has quit IRC23:56
fifieldtaction it for the log?23:56
jeblairo/23:56
reedthe other thing to bring up with infra is the request from the UX team for an askbot instance23:56
reedoh, hello jeblair23:56
fifieldtit's jeblair!23:56
* fifieldt bows down23:57
jeblairfrom what i've seen of poodle, it looks really promising and has improved from last time we looked at it23:57
reeda couple of lines above, the i18n things23:57
*** rnirmal has quit IRC23:57
fifieldts/poodle/pootle23:57
jeblairi'd be happy to spin one up; i don't want to be premature though, so any requirements gathering from i18n would be great23:57
reedright, jeblair, I have a doc from i18n ... wait23:57
jeblairfifieldt: oh, crap, i'm only prepared to spin up poodles!23:57
reedhttps://docs.google.com/spreadsheet/ccc?key=0Aqevw3Q-ErDUdFgzT3VNVXQxd095bFgzODRmajJDeVE#gid=023:58
* fifieldt has a vision of jeblair doing one of those spinning-plates-on-sticks routines, only with poodles instead of plates23:58
reedit has the comparison done at the time when Transifex was chosen23:58
* reed thinks this is the longest community meeting so far23:58
jeblairi think the translation memory stuff has improved, which was the week point23:58
jeblairweak point even23:59
jeblairwow23:59
fifieldtthat's what I heard too23:59

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