Tuesday, 2013-04-09

*** danwent has joined #openstack-meeting00:03
*** maksimov has quit IRC00:04
*** egallen has quit IRC00:05
*** markvoelker1 has joined #openstack-meeting00:05
*** maksimov has joined #openstack-meeting00:06
*** netapp has quit IRC00:06
*** netapp has joined #openstack-meeting00:08
*** markvoelker1 has quit IRC00:09
*** gyee has quit IRC00:11
*** armax has quit IRC00:13
*** sacharya has joined #openstack-meeting00:21
*** zhuadl has joined #openstack-meeting00:22
*** ijw has quit IRC00:23
*** dhellmann_ has joined #openstack-meeting00:24
*** dhellmann_ has quit IRC00:25
*** dhellmann has quit IRC00:27
*** lloydde has quit IRC00:27
*** sdake_ has quit IRC00:29
*** cp16net|away is now known as cp16net00:32
*** bdpayne has quit IRC00:32
*** jog0 has quit IRC00:37
*** rmohan has quit IRC00:39
*** rmohan has joined #openstack-meeting00:40
*** colinmcnamara has left #openstack-meeting00:43
*** markmcclain has quit IRC00:47
*** salv-orlando has joined #openstack-meeting00:51
*** stevemar has quit IRC00:52
*** sankarsh` is now known as sankarshan00:56
*** Mandell_ has joined #openstack-meeting00:58
*** Mandell has quit IRC00:58
*** sankarshan has quit IRC00:58
*** sankarshan has joined #openstack-meeting00:58
*** danleyden has quit IRC01:01
*** rmohan has quit IRC01:02
*** rmohan has joined #openstack-meeting01:03
*** danleyden has joined #openstack-meeting01:03
*** zul has quit IRC01:03
*** zul has joined #openstack-meeting01:03
*** rmohan has quit IRC01:05
*** rmohan has joined #openstack-meeting01:05
*** markvoelker1 has joined #openstack-meeting01:05
*** vipul is now known as vipul|away01:07
*** beagles_back_l8r is now known as beagles01:07
*** markvoelker1 has quit IRC01:10
*** ryanpetrello has joined #openstack-meeting01:15
*** emagana has quit IRC01:18
*** zhuadl has quit IRC01:20
*** roampune has quit IRC01:23
*** vipul|away is now known as vipul01:31
*** terry7 has quit IRC01:33
*** sdake_ has joined #openstack-meeting01:36
*** esker has joined #openstack-meeting01:42
*** oubiwann has quit IRC01:43
*** ryanpetrello has quit IRC01:46
*** cp16net is now known as cp16net|away01:48
*** ryanpetrello has joined #openstack-meeting01:59
*** markvoelker1 has joined #openstack-meeting02:06
*** fnaval has joined #openstack-meeting02:06
*** fnaval has quit IRC02:06
*** fnaval has joined #openstack-meeting02:07
*** ladquin is now known as ladquin_away02:09
*** markvoelker1 has quit IRC02:10
*** martine has joined #openstack-meeting02:16
*** dwcramer has quit IRC02:16
*** martine_ has quit IRC02:17
*** vkmc has quit IRC02:30
*** dwcramer has joined #openstack-meeting02:33
*** ryanpetrello has quit IRC02:49
*** danwent has quit IRC03:02
*** lillie- is now known as lillie03:03
*** markwash has joined #openstack-meeting03:04
*** lillie has quit IRC03:05
*** markvoelker1 has joined #openstack-meeting03:06
*** lillie- has joined #openstack-meeting03:06
*** gary has joined #openstack-meeting03:07
*** gary is now known as Guest4619603:07
*** diogogmt has quit IRC03:08
*** dwcramer has quit IRC03:08
*** Guest46196 has quit IRC03:09
*** diogogmt has joined #openstack-meeting03:10
*** markvoelker1 has quit IRC03:10
*** sdake_ has quit IRC03:12
*** fifieldt has joined #openstack-meeting03:24
*** dwcramer has joined #openstack-meeting03:27
*** ijw has joined #openstack-meeting03:30
*** adjohn has quit IRC03:36
*** dguitarbite has joined #openstack-meeting03:52
*** danwent has joined #openstack-meeting03:58
*** sirushti has quit IRC03:59
*** boris-42 has joined #openstack-meeting04:03
*** sandywalsh has quit IRC04:04
*** markvoelker1 has joined #openstack-meeting04:06
*** markvoelker1 has quit IRC04:11
*** arata has joined #openstack-meeting04:23
*** diogogmt has quit IRC04:24
*** carlp is now known as carlp-away04:27
*** lbragstad has joined #openstack-meeting04:34
*** adjohn has joined #openstack-meeting04:37
*** sandywalsh has joined #openstack-meeting04:37
*** resker has joined #openstack-meeting04:38
*** esker has quit IRC04:40
*** adjohn has quit IRC04:41
*** Mandell_ has quit IRC04:42
*** markwash has quit IRC04:42
*** zhuadl has joined #openstack-meeting04:42
*** markwash has joined #openstack-meeting04:50
*** sacharya has quit IRC04:50
*** garyk has quit IRC04:51
*** novas0x2a|laptop has quit IRC04:59
*** markvoelker1 has joined #openstack-meeting05:07
*** markvoelker1 has quit IRC05:11
*** dguitarbite has quit IRC05:18
*** dwcramer has quit IRC05:26
*** lloydde has joined #openstack-meeting05:29
*** SergeyLukjanov has joined #openstack-meeting05:30
*** markwash has quit IRC05:32
*** salv-orlando has quit IRC05:35
*** garyk has joined #openstack-meeting05:43
*** garyk has left #openstack-meeting05:43
*** gary has joined #openstack-meeting05:52
*** gary is now known as Guest4591905:53
*** salv-orlando has joined #openstack-meeting05:54
*** martine has quit IRC05:54
*** reed has quit IRC05:55
*** sdake_ has joined #openstack-meeting05:55
*** salv-orlando has quit IRC05:59
*** topol has quit IRC06:01
*** SergeyLukjanov has quit IRC06:07
*** markvoelker1 has joined #openstack-meeting06:07
*** Guest45919 has quit IRC06:10
*** markvoelker1 has quit IRC06:12
*** mrunge has joined #openstack-meeting06:12
*** adjohn has joined #openstack-meeting06:14
*** adjohn has quit IRC06:14
*** davidhadas has quit IRC06:27
*** ijw has quit IRC06:28
*** ijw has joined #openstack-meeting06:28
*** SergeyLukjanov has joined #openstack-meeting06:28
*** SergeyLukjanov has quit IRC06:32
*** flaper87 has joined #openstack-meeting06:33
*** flaper87 has joined #openstack-meeting06:33
*** ijw has quit IRC06:34
*** ijw has joined #openstack-meeting06:37
*** ijw has quit IRC06:43
*** boris-42 has quit IRC06:50
*** garyk has joined #openstack-meeting06:52
*** Mandell has joined #openstack-meeting06:54
*** psedlak has joined #openstack-meeting06:58
*** egallen has joined #openstack-meeting07:00
*** markvoelker1 has joined #openstack-meeting07:08
*** matiu has quit IRC07:09
*** markvoelker1 has quit IRC07:12
*** afazekas has joined #openstack-meeting07:36
*** lillie- is now known as lillie07:37
*** afazekas has quit IRC07:41
*** danwent has quit IRC07:42
*** Kharec has joined #openstack-meeting07:48
*** SergeyLukjanov has joined #openstack-meeting07:49
*** egallen has quit IRC07:51
*** reed has joined #openstack-meeting08:03
*** afazekas has joined #openstack-meeting08:05
*** Khaja has joined #openstack-meeting08:07
*** markvoelker1 has joined #openstack-meeting08:08
*** Mandell has quit IRC08:10
*** markvoelker1 has quit IRC08:12
*** kirminas has joined #openstack-meeting08:15
*** rahmu has joined #openstack-meeting08:24
*** boris-42 has joined #openstack-meeting08:24
*** jhenner has joined #openstack-meeting08:28
*** pnavarro has joined #openstack-meeting08:28
*** mkollaro has joined #openstack-meeting08:49
*** darraghb has joined #openstack-meeting08:52
*** markwash has joined #openstack-meeting08:54
*** markwash has quit IRC09:00
*** egallen has joined #openstack-meeting09:03
*** egallen has quit IRC09:04
*** egallen has joined #openstack-meeting09:05
*** zykes has quit IRC09:07
*** sankarshan is now known as sankarshan_away09:08
*** markvoelker1 has joined #openstack-meeting09:08
*** markvoelker1 has quit IRC09:13
*** mkollaro has quit IRC09:15
*** Khaja has quit IRC09:15
*** mkollaro has joined #openstack-meeting09:16
*** egallen has quit IRC09:46
*** markwash has joined #openstack-meeting09:55
*** oleg__ has joined #openstack-meeting09:56
*** markwash has quit IRC09:59
*** markvoelker1 has joined #openstack-meeting10:09
*** ccorrigan has quit IRC10:10
*** hanney has joined #openstack-meeting10:10
*** markvoelker1 has quit IRC10:14
*** arata has quit IRC10:28
*** arata has joined #openstack-meeting10:28
*** ttrifonov is now known as ttrifonov_zZzz10:35
*** pcm_ has joined #openstack-meeting10:35
*** ttrifonov_zZzz is now known as ttrifonov10:36
*** gongysh has quit IRC10:42
*** gongysh has joined #openstack-meeting10:42
*** anteaya has joined #openstack-meeting10:43
*** rahmu has quit IRC10:58
*** rkukura has quit IRC11:00
*** Yada has joined #openstack-meeting11:00
*** adalbas has joined #openstack-meeting11:07
*** rahmu has joined #openstack-meeting11:09
*** markvoelker1 has joined #openstack-meeting11:09
*** egallen has joined #openstack-meeting11:11
*** markvoelker1 has quit IRC11:14
*** zhuadl has quit IRC11:17
*** adalbas has quit IRC11:21
*** pnavarro has quit IRC11:30
*** sandywalsh has quit IRC11:30
*** adalbas has joined #openstack-meeting11:34
*** sandywalsh has joined #openstack-meeting11:44
*** dhellmann has joined #openstack-meeting11:46
*** SergeyLukjanov has quit IRC11:50
*** vkmc has joined #openstack-meeting11:53
*** vkmc has joined #openstack-meeting11:53
*** sankarshan_away is now known as sankarshan11:53
*** egallen has quit IRC11:55
*** egallen has joined #openstack-meeting11:55
*** markvoelker1 has joined #openstack-meeting12:00
*** markvoelker1 has quit IRC12:01
*** fifieldt_ has joined #openstack-meeting12:04
*** rnirmal has joined #openstack-meeting12:09
*** ttrifonov is now known as ttrifonov_zZzz12:12
*** martine has joined #openstack-meeting12:21
*** dhellmann has quit IRC12:21
*** ttrifonov_zZzz is now known as ttrifonov12:23
*** tongli has joined #openstack-meeting12:26
*** dhellmann has joined #openstack-meeting12:33
*** dhellmann has quit IRC12:33
*** resker has quit IRC12:36
*** egallen has quit IRC12:40
*** koolhead11 has joined #openstack-meeting12:44
*** egallen has joined #openstack-meeting12:45
*** pnavarro has joined #openstack-meeting12:48
*** boris-42 has quit IRC12:49
*** Daisy has joined #openstack-meeting12:49
*** ladquin_away is now known as ladquin12:50
*** zhuadl has joined #openstack-meeting12:51
*** writerDiane has joined #openstack-meeting12:55
*** mrodden has joined #openstack-meeting12:55
* annegentle waves12:56
fifieldt_hi WriterDi_, ladquin, annegentle, EmilienM!12:57
*** dprince has joined #openstack-meeting12:57
*** mrodden1 has joined #openstack-meeting12:57
ladquinhi, fifieldt!12:57
annegentlehey! fifieldt_!12:57
*** SergeyLukjanov has joined #openstack-meeting12:58
fifieldt_hihi, long time no chat :)12:58
* annegentle reviews action items and doesn't think she did one :)12:58
koolhead11hi all12:58
fifieldt_yo !12:59
*** koolhead11 is now known as koolhead1712:59
Daisyhello12:59
Daisyall of us are on time today12:59
annegentleok hopefully meeting bot is working today12:59
writerDianegood morning12:59
annegentleheh for me it's because it's an hour later and my kids are out of the house :)12:59
fifieldt_I think the error last time was the wrong meeting name or something13:00
annegentlenah the bot was borked13:00
fifieldt_try: #startmeeting docwebteam13:00
*** mrodden has quit IRC13:00
*** lbragstad has quit IRC13:00
annegentle#startmeeting docwebteam13:00
openstackMeeting started Tue Apr  9 13:00:44 2013 UTC.  The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
fifieldt_rather than #startmeeting Doc Team13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
fifieldt_oh, ok13:00
*** openstack changes topic to " (Meeting topic: docwebteam)"13:00
openstackThe meeting name has been set to 'docwebteam'13:00
fifieldt_my bad13:00
annegentleno worries :)13:00
annegentleI guess I do what I'm told!13:01
koolhead17annegentle: :P13:01
annegentle#topic Action items from the last meeting13:01
*** openstack changes topic to "Action items from the last meeting (Meeting topic: docwebteam)"13:01
annegentleaction: fifieldt_ send a note to discuss grizzly priorities on the OpenStack mailing list13:01
annegentleThat's done13:01
fifieldt_done13:01
*** egallen has quit IRC13:01
annegentleaction: annegentle to ask Doc Tool team about Crown Quarto PDF output13:01
fifieldt_unfortunately, not a reply, and little response in the bug assignment department13:01
annegentleYeah I noticed that...13:02
annegentleAlso done, and we can output Crown Quarto to our PDF13:02
fifieldt_yay13:02
annegentlebut they're already using DocImpact for Havana. sigh. :)13:02
annegentleaction: annegentle to send a call to action to help with grizzly doc bugs13:02
annegentleSo, I think I did that? But maybe to the -doc list?13:02
annegentleor?13:02
*** zhuadl has quit IRC13:02
annegentleI have Grizzly doc bugs as an entire topic of its own so we can talk more then13:03
fifieldt_you did mention it in your -doc newsletter13:03
annegentleone more action13:03
fifieldt_cool13:03
annegentleaction annegentle to add info about pom.xml change for 1.7.1 to wiki13:03
*** egallen has joined #openstack-meeting13:03
annegentleSo this is halfway done, definitely need more info.13:03
annegentleI'm going to reassign it to me :)13:03
fifieldt_got a  link?13:03
*** arata has quit IRC13:03
annegentle#action annegentle to add more info about 1.7.2 to the HowTo wiki page13:04
annegentlefifieldt_: what I did so far was to update the Conventions page about image markup13:04
annegentle#link https://wiki.openstack.org/wiki/Documentation/Conventions#Embedding_images13:04
fifieldt_ta13:04
annegentlebut there's more to it than that13:04
annegentlethere's pom.xml stuff too13:04
*** zhuadl has joined #openstack-meeting13:04
annegentleit's not a huge task though, I'll get to it13:05
annegentleok, I think that's it13:05
annegentlefor actions13:05
annegentlenow! Onward! To Grizzly!13:05
annegentle#topic Grizzly release13:05
*** openstack changes topic to "Grizzly release (Meeting topic: docwebteam)"13:05
fifieldt_#link https://launchpad.net/openstack-manuals/+milestone/grizzly13:05
fifieldt_#link https://launchpad.net/openstack-api-site/+milestone/grizzly13:05
*** ryanpetrello has joined #openstack-meeting13:05
annegentleI have to say I'm having a tough time knowing when to call done done.13:05
fifieldt_understandable13:06
annegentleMy sense is that the majority are quantum and swift deficits. Tom, what's your sense of it? (fifieldt_)13:06
annegentleAnd, I don't know if the install docs are releasable when the packages aren't completed? Thoughts?13:07
fifieldt_I'm a big believer in testing13:07
fifieldt_so right now those bugs are mostly derived from DocImpact13:07
annegentleThe broken script links are certainly getting comments in the docs :)13:07
fifieldt_I think once someone has run through the install docs and verified they work13:07
annegentlefifieldt_: yeah I agree with testing the install docs.13:07
fifieldt_then that's release goodness13:07
koolhead17annegentle: that install using nova-network is not there anymore :(13:07
annegentlekoolhead17: where's there?13:08
koolhead17i was thinking to re-test and modify it13:08
koolhead17appendixB13:08
koolhead17one13:08
fifieldt_for the 'reference' guide, that's something that can go once there are no obvious errors/pitfalls left  - i.e. there';s only new features left to add13:08
koolhead17ubuntu installation with openstack & we had a APPENDIXB13:08
koolhead17which covered single machine deployment with nova-network13:09
fifieldt_#link https://bugs.launchpad.net/openstack-manuals/+bug/113369913:09
uvirtbotLaunchpad bug 1133699 in openstack-manuals "grizzly: Update Appendix B OpenStack Deployment Guide" [Medium,In progress]13:09
annegentlekoolhead17: yeah we got rid of Appendix B it was causing too much maintenance headache and mismatch13:09
koolhead17annegentle: ok.13:10
annegentleI want to talk alot about install doc in the "refactor" session next week13:10
koolhead17annegentle: so do i :)13:10
annegentleyeah13:10
annegentleI figure we all do :)13:10
koolhead17ahaha13:10
koolhead17i would say it will be too much of clean up13:10
annegentleit's a big job13:11
annegentlebut I have ideas :)13:11
fifieldt_me too :)13:11
annegentleso I sense others in the community are going to create the one-pagers13:11
annegentlefor install13:11
annegentleit's more important that ours is a tested path for "production-like" enviros13:11
annegentleSo, are we okay with "once install is tested and packages are out, release?"13:11
annegentleor is there another set of criteria we need to be above?13:12
fifieldt_for install guide, that sounds reasonable13:12
fifieldt_for the 'reference' guide, I think that can go once there are no obvious errors/pitfalls left  - i.e. there';s only new features left to add13:12
*** boris-42 has joined #openstack-meeting13:12
writerDianeWhat's the 'reference' guide?13:12
writerDianeis that the API reference page?13:12
fifieldt_'compute admin'13:12
fifieldt_not the API one13:13
writerDianeoh!13:13
fifieldt_sorry for confusion13:13
writerDianeno problem!13:13
fifieldt_speaking of which - api ref for grizzly - all good?13:13
annegentlefifieldt_: I think so -- ladquin or writerDiane do you have input?13:13
writerDianeI'm still working through the bugs13:13
annegentleladquin wrote a lovely end-of-internship report13:14
annegentleladquin: thank you SO much for all your hard work!13:14
ladquinI'm finishing the Quantum section, which samples took me a lot more that expected13:14
ladquinannegentle, :)13:14
fifieldt_there are some reviews waiting at13:14
ladquinmy pleasure13:14
fifieldt_#link https://review.openstack.org/#/q/status:open+project:openstack/api-site,n,z13:14
annegentleladquin and writerDiane Ok, keep on trucking then.13:14
fifieldt_+1 API is hardd13:14
annegentlefifieldt_: so how much do you think it would take for the reference guide with all the conf options to be "done"13:15
koolhead17hi ladquin writerDiane13:15
writerDianehi!13:15
fifieldt_ok, so config options that were reported with doc impact are more or less done13:15
annegentlefifieldt_: and is that a new guide (standalone) or are you saying it's in other guides?13:15
fifieldt_they were the easy bugs to solve13:16
koolhead17annegentle: are they the one working as interns 4 the doc stuff under gnome internship?13:16
* koolhead17 is confused13:16
annegentlefifieldt_: impressive13:16
fifieldt_but we're still missing many -13:16
fifieldt_for that I think the autogenerate is the solution13:16
annegentlekoolhead17: ladquin is just now finished with her GNOME OPW internship, writerDiane works with me at Rackspace13:16
fifieldt_doing it manually is going to be a pain13:16
koolhead17ooh okey13:16
ladquinhi, koolhead17!13:16
fifieldt_we're growing koolhead17 :D13:16
*** zhuadl has quit IRC13:16
koolhead17fifieldt_: yay!!13:16
*** zhuadl has joined #openstack-meeting13:16
annegentlewriterDiane: koolhead17 is Atul, has been working on OpenStack docs since wayyyy back when! Cactus, right?13:16
koolhead17yes :)13:17
writerDianeoh! hi koolhead1713:17
annegentlefifieldt_: I completely agree on the autogenerate.13:17
koolhead17writerDiane: salute13:17
annegentlefifieldt_: ok, so what I hear is, release Grizzly with the config we've got13:17
annegentlefifieldt_: after install is tested13:17
fifieldt_roger13:17
koolhead17annegentle: fifieldt_  my 1 line suggestion would be we are interested in doing things from scratch :)13:17
koolhead17make it plug and play/moduler13:17
fifieldt_'course ;)13:18
annegentleIs that possible in about two weeks even with the Summit? Or a month from now?13:18
koolhead17that way we exactly know in all our docs what needs to be modified everytime new release comes13:18
annegentle5/9? or end of April? Hm13:18
fifieldt_I think when the cybera guys get through it is a good timeframe13:18
koolhead17annegentle: also we need to get guys guys from RH/Ubuntu/Suse community to help us a bit13:19
fifieldt_indeed13:19
koolhead17if we are pushing the doc with the distro13:19
koolhead17it would be great if they do testing for us13:19
koolhead17:)13:19
koolhead17just a suggestion13:19
annegentlekoolhead17: yeah I constantly reach out13:19
koolhead17annegentle: probably we should have a doc session title "vedors & openstack docs"13:20
annegentlekoolhead17: will do more in person next week13:20
koolhead17where we can address some of these issues13:20
annegentlekoolhead17: heh and if no one came? :)13:20
fifieldt_I think a more individual approach is better13:20
fifieldt_rather than a session13:20
koolhead17annegentle: okey13:20
koolhead17i am saying this because tomorrow13:20
fifieldt_we/"the foundation" should be contacting people and roping them in?13:20
koolhead17cinder driver folks would like to have stuff added13:20
annegentleyeah this is an ongoing bit of relationship building13:20
koolhead17so kind of we need to know whom to approach13:21
koolhead174 helping hand13:21
koolhead17so am wondering if we should have session addressing this need13:21
koolhead17just a suggestion13:21
koolhead17:P13:21
annegentlekoolhead17: yeah I get it, just saying this is what we already do :)13:21
koolhead17cool13:21
koolhead17:)13:21
annegentlekoolhead17: so it feels a little like you're telling me I'm not doing my job13:21
koolhead17let me know whom to trouble 4 redhat installation help13:22
koolhead17annegentle: oops not at all13:22
annegentlekoolhead17: it's okay, just telling you how I'm perceiving it :)13:22
koolhead17annegentle: apology for that :(13:22
annegentlekoolhead17: but definitely we need more relationship building and "I" don't scale13:22
annegentlekoolhead17: so we have to continue to reachout, get names, get to know people.13:23
koolhead17annegentle: what i simply meant we need to have folks identified whom we can reach out 4 help13:23
*** lbragstad has joined #openstack-meeting13:23
koolhead17annegentle: that is what i meant :)13:23
annegentleah yes! For RHEL install, I have a Racker Phil Hopkins who wants to take the Basic install guide and make it RHEL ready.13:23
*** dkehn has quit IRC13:23
fifieldt_cool13:23
koolhead17awesome13:23
annegentlekoolhead17: Yeah, it would be great to designate "maintainers" for docs13:23
*** ek6 has joined #openstack-meeting13:23
annegentlekoolhead17: so far I don't sense that much responsibility for individual docs, well maybe in some cases. Hm, it's a good question.13:24
writerDianeI think it's hard to "own" a doc13:24
annegentle#agreed Release Grizzly docs after install is tested and packages are available. Approximately in 3-4 weeks.13:24
koolhead17annegentle: if you can see current questions in maling list about basic redhat install13:24
writerDianein the community sphere -13:24
annegentlewriterDiane: yeah I don't see it, yet.13:25
annegentlekoolhead17: yeah I think Phil's work will help with that13:25
fifieldt_maybe this is a good discussion to have via ML or an etherpad - thresh out a strategy ?13:25
*** stevemar has joined #openstack-meeting13:25
writerDianeit might be interesting to get feedback from people at the summit about why they don't contribute to doc - there might be reasons we don't know about13:25
fifieldt_"strategy for increasing contribution"13:25
writerDianefifieldt_: yes exactly13:25
annegentlefifieldt_: for install doc, it has been interesting to see install docs pop up individually but the "official" ones lightly touched13:26
koolhead17writerDiane: yes13:26
ladquinagree13:26
koolhead17yes13:26
annegentlewriterDiane: yes, I think I know the reasons (toolchain is hard, I don't know enough to speak authoritatively, I don't have an enviro)13:26
annegentlewriterDiane: not that those are all! There are many is what I mean :)13:26
fifieldt_#link https://etherpad.openstack.org/IncreasingDocContributions13:27
annegentlenice, fifieldt_13:27
writerDianeyes, toolchain is hard but also the environment is a little unsettling - people patching patches, etc - not clear ownership (which is by design) - but that can be unsettling13:27
*** dkehn has joined #openstack-meeting13:27
annegentleso that leads naturally into our next topic13:27
annegentle#topic Refactor docs discussion - review blueprint before Summit13:27
*** openstack changes topic to "Refactor docs discussion - review blueprint before Summit (Meeting topic: docwebteam)"13:27
koolhead17cool13:27
annegentle#link https://blueprints.launchpad.net/openstack-manuals/+spec/restructure-documentation13:28
annegentleIt'll be easiest to talk about it in person next week but wanted to be sure you all have the ideas ahead of time13:29
annegentle#link https://wiki.openstack.org/wiki/Blueprint-restructure-documentation13:29
fifieldt_LGTM :P13:29
*** egallen has quit IRC13:29
annegentlefifieldt_: hee13:29
annegentlefifieldt_: devil's in the details13:30
koolhead17:P13:30
annegentleOkay13:30
annegentlemoving on in the interest of time13:30
annegentle#topic Docs-draft work for easier reviews13:30
*** openstack changes topic to "Docs-draft work for easier reviews (Meeting topic: docwebteam)"13:30
annegentlefor one of ladquin's major contributions, she has a huge patch to the openstack-infra/config project to add "gate" builds13:30
ladquinI couldn't get that approved yet :(13:30
annegentleladquin: yeah I saw that13:31
*** egallen has joined #openstack-meeting13:31
annegentleladquin: I like jeblair's thinking for patterns, how difficult is it to do though?13:31
*** woodspa has joined #openstack-meeting13:31
fifieldt_#link https://review.openstack.org/#/c/22768/13:31
annegentlefifieldt_: thanks, you were quicker :)13:31
*** egallen has quit IRC13:31
ladquinjeblair wanted a little modification and mordred put it in progress, form some reason, so I hopefully be taking care of that today13:31
annegentleladquin: and, how much time do you really have? Should one of us pick it up?13:31
annegentleladquin: wow cool!13:32
ladquinannegentle, oh, it's simple13:32
annegentleladquin: sweet13:32
ladquinannegentle, but still would like to further discuss it with him13:32
annegentleladquin: ok, great. Let us know if you need one of us to help.13:33
mordredladquin: hey13:33
annegentlemordred: heya13:33
mordredladquin: I basically started putting things as WIP that it seemed the next step was for someone to upload a new patch13:33
koolhead17And yes mordred: never sleeps!!  :)13:33
ladquinannegentle, it should really be something quick to finish today, need to make sure it fully complies with our infra team needs ;)13:33
annegentleheh sleep when you're dead right koolhead17? :)13:34
annegentleladquin: excellent. And thanks mordred for the help13:34
*** egallen has joined #openstack-meeting13:34
*** stevemar has quit IRC13:34
ladquinmordred, hey, thanks, yes, I need to amend that13:34
annegentleok ready to talk translation?13:34
*** egallen has quit IRC13:34
*** rkukura has joined #openstack-meeting13:34
annegentle#topic Translation uploading/downloading scripts13:34
*** openstack changes topic to "Translation uploading/downloading scripts (Meeting topic: docwebteam)"13:34
Daisyhi, I'm here13:34
annegentleDaisy: you have any news to report?13:34
annegentle#link https://review.openstack.org/#/c/25810/13:35
Daisythe patch is submitted to git review.13:35
annegentleI did see that ^^13:35
Daisyjust need to discuss with you about how to store the translation po files.13:35
DaisyI guess, there will be a big amout of po files.13:35
annegentleDaisy: ok, sure. I saw .tx directories somewhere?13:35
* annegentle looks13:35
*** egallen has joined #openstack-meeting13:35
annegentle#link https://github.com/openstack/openstack-manuals/tree/master/doc/src/docbkx/openstack-install/locale13:36
DaisyDo you think, if the authors/readers will be bothered if we put these files under master ?13:36
annegentleAlso locale directories13:36
annegentleDaisy: honestly it's not bothering me lately but I have super mega fast Internts.13:36
annegentlewhat do others think?13:37
* annegentle wonders if translation also is a factor for the refactor13:37
*** SergeyLukjanov has quit IRC13:37
fifieldt_I have a slight personal preference for keeping the repo small in size, due to frequent travel = unreliable/slow internets13:37
DaisyNova/Keystone and others have the po and pot file in master, but I think, their size are small, not like documents.13:37
fifieldt_but I wouldn't allow my personal preferences stand in the way :)13:37
fifieldt_ah - if there's an established precedent, maybe we should follow it13:37
annegentlefifieldt_: yeah compltely understand that13:37
Daisyso we agree to put them in master?13:38
fifieldt_sure13:38
annegentleDaisy: mordred: what are some of our other options? Just to be sure.13:38
Daisyok.13:38
koolhead17slow internet reminds me of my broadband13:38
Daisyuse a different branch?13:38
Daisywe put the po files in a different branch, like, translation. If the developers don't want to download translations, they can pull from master.13:39
DaisyActually, I have not clear ideas.13:39
DaisyI'm not a git master.13:39
annegentleDaisy: oh yeah that would make sense, actually, why not store with stable/folsom and also stable/grizzly in a month?13:39
fifieldt_storing with stable makes sense to me13:39
fifieldt_it changes less13:39
*** esker has joined #openstack-meeting13:40
fifieldt_= less frustration for translators ?13:40
annegentlewhen I asked on the list, jaypipes said something about submodules?13:40
Daisythe translation po files will be changed because the downloading job runs daily. Can we put them in stable?13:40
annegentlewhich sounded AWFUL I have to admit :)13:40
annegentleyeah I really like starting with stable13:40
fifieldt_stable :D13:40
Daisythe translation po files will be changed daily, so they are not stable.13:41
*** dhellmann has joined #openstack-meeting13:41
Daisywhat's the disadvantages if we create a new branch?13:41
*** mtreinish has joined #openstack-meeting13:42
annegentleDaisy: hm. I don't know... really we just want to keep translators happy while not preventing new doc contributions from being a pain13:42
* koolhead17 is going to spend few days to understand Git magic13:42
Daisyexactly.13:42
annegentleDaisy: how much do translators know about the git branch label though? Do they see that much?13:43
annegentleDaisy: or is it just the Jenkins robots that need to use the branch?13:43
annegentleDaisy: because the Jenkins robots won't care if it's called "stable/relname"13:43
annegentleDaisy: people might think that's odd but it might not matter?13:43
Daisytranslators doesn't need to know about branch lable.  Branch lable is not required by Jenkins robots too.13:44
annegentleDaisy: ok then I think it's okay to go with stable13:44
Daisyok then.13:44
Daisygo with stable.13:45
* annegentle hopes my future self doesn't hate me for that :)13:45
fifieldt_hmmm!13:45
ladquinhaha13:45
*** beagles is now known as beagles_brb13:45
annegentleI think it'll work the way we want it to13:45
fifieldt_I'm sure by next meeting we will know whether it was correct13:45
fifieldt_and if it wasn't we can change it13:45
fifieldt_right?13:45
*** bdpayne has joined #openstack-meeting13:45
DaisyI have a question...13:46
annegentleyeah13:46
annegentlesure go ahead13:46
Daisywhen will stable/grizzly be created? or it has been created?13:46
annegentleDaisy: so that was our discussion today. We need packages released (depends on Ubuntu) and install docs tested (in progress).13:46
* fifieldt_ is watching crazy tram track maintenance vehicles randomly block an intersection in very interesting ways13:46
annegentleDaisy: my guess is either end of April or first 2 weeks of May13:46
annegentleDaisy: will that be too much delay?13:47
fifieldt_ok, so that might be a problem - we probably want grizzly translation to start sooner, yes?13:47
annegentlefifieldt_: well, why translate what isn't done?13:47
Daisyso I have to use stable/folsom to store the translation of grizzly?13:47
annegentlefifieldt_: is my thinking?13:47
annegentleDaisy: oh. No. :)13:47
annegentleDaisy: Hm.13:47
annegentleSo, here's the release process for docs:13:47
annegentle#link https://wiki.openstack.org/wiki/Documentation/Release13:47
annegentlethat takes at least a day13:48
annegentleI could do it this week?13:48
annegentleI could do it the week after Summit13:48
annegentleOr could wait for Install docs to be done.13:48
annegentleOr.13:48
writerDianeI'd say after summit and when install docs are done?13:48
annegentlewriterDiane: that's my preference but hadn't considered translations13:49
*** metral has joined #openstack-meeting13:49
annegentleDaisy: my top priortiy would be the Operations Guide anyway, which is in stable/folsom13:49
annegentleand is very folsom13:49
Daisythere is a operation guide in master , isn't it?13:49
writerDianecan't translation be staged? I.e. make a prioritized list and work through it? install guide would be last?13:49
fifieldt_indeed13:49
annegentleDaisy: yep it matches folsom13:50
annegentlewriterDiane: yeah that makes sense13:50
annegentleDaisy: do you have a sense of whether translators work thorugh a list?13:50
*** pnavarro has quit IRC13:50
Daisywhen we have coordinators, we can ask the help from coordinators.13:50
annegentleDaisy: yeah13:50
annegentleDaisy: so I'd like a decision on stable/folsom and stable/grizzly -- is it okay if stable/grizzly is in a few weeks? Like after the Summit?13:51
Daisyso you mean that the translators start translation of stable/folsom?13:51
*** sacharya has joined #openstack-meeting13:51
annegentleDaisy: the translators wait until after the Summit and work on stable/grizzly13:52
DaisyI need to think it more.13:52
annegentleDaisy: except for the Ops Guide, start on that in stable/folsom13:52
Daisycurrently, translators are doing the translation of master, that means, the latest version, the version are being developed.13:52
*** mrodden1 has quit IRC13:53
annegentleDaisy: ok let's think about this from a release perspective. Translators won't wait for a release, they work on master.13:53
annegentleDaisy: so how do we "release" master docs?13:53
Daisytranslations will be later than the release of master.13:53
* ladquin wonders if Transifex works with translation memories13:53
DaisyBut if we keep translators to translate the old version of documents, will they be happy?13:53
annegentleladquin: yep, it does! One of the reasons we picked it13:54
DaisyTransifex can work with translation memories.13:54
annegentleDaisy: for the Ops Guide, for sure it's best.13:54
annegentleDaisy: for other guides, master would be ok, as long as we know what happens at release time13:54
Daisyok. I need to think more about it. Maybe we won't make decision tonight.13:54
*** primeministerp has joined #openstack-meeting13:54
annegentleDaisy: I think that we might end up making smaller docs repos after the refactor? Possibly? We already split out ops/admin guides from API13:54
DaisyI'm not able to handle the documents differently.13:55
annegentleWould putting docs in individual repositories matter?13:55
fifieldt_The review Daisy posted is the script that links to Transifex and back13:56
*** markwash has joined #openstack-meeting13:56
annegentleThat's the only way to take care of the tradeoff of size, is to put items into smaller "buckets"13:56
*** markmcclain has joined #openstack-meeting13:56
fifieldt_My guess is that it can be modified for any scenario13:56
annegentlefifieldt_: yep probably so13:56
Daisycurrently, the docs are in a single repository. So I look at them as single repository. When a single document is updated, the update event will triger the uploading jobs, the updated POT file will be upload to Transifex.13:57
annegentlefifieldt_: what do you think of smaller repositories?13:57
fifieldt_I prefer the big repo13:57
annegentlefifieldt_: okay13:57
fifieldt_I do a lot of grepping to find stuff across different docs13:57
annegentlefifieldt_: yep13:57
annegentleDaisy: I think it's okay to use master13:58
annegentleDaisy: I don't think the pot files will be all that big13:58
Daisythere are only two Jenkins jobs for me: uploading and downloading, a single repository. Not several jobs for individual documents.13:58
annegentleDaisy: yeah13:58
Daisyso we use master firstly.13:58
annegentleDaisy: yep. I still want to understand what happens when we cut stable/grizzly in a few weeks?13:58
DaisyAnd then we discuss more in the summit.13:59
*** egallen has quit IRC13:59
*** gongysh has quit IRC13:59
annegentleDaisy: yep13:59
Daisyversioning will be a problem for translation too.13:59
annegentleDaisy: are you able to come?13:59
DaisyI should list this as a topic.13:59
annegentleDaisy: yes it will :)13:59
DaisyYes, I'm able to come.13:59
fifieldt_yayy!13:59
annegentleDaisy: wonderful!14:00
annegentleOkay, great!14:00
Daisy:)14:00
annegentleWow where did the time go?14:00
Daisywe are run out of time.14:00
annegentle#topic Open discussion14:00
*** openstack changes topic to "Open discussion (Meeting topic: docwebteam)"14:00
annegentleor I can end the meeting if no one has anything :)14:00
*** markwash has quit IRC14:00
* fifieldt_ needs tex mex14:00
annegentlehee14:00
annegentleGood tortilla chips and salsa just don't travel well14:01
mordredannegentle: what did I do?14:01
annegentlemordred: all of the things!14:01
mordredawesome!14:01
koolhead17:P14:01
*** SergeyLukjanov has joined #openstack-meeting14:01
ladquinhahah14:01
*** markvan has joined #openstack-meeting14:01
annegentlemordred: if your team can attend the Docs Translation session at the Summit next week on Monday it would be super-uper helpful14:01
mordredannegentle: yes. that one is definitely on my list14:01
*** egallen has joined #openstack-meeting14:01
mordredI'll make olaph be there for sure, but I believe more of us will be there as well14:02
annegentle#info Monday 2013-04-15 13:50  - Translation management enhancement14:02
koolhead17annegentle: am working on that install doc with nova-network14:02
mordredttx: it would be GREAT if I could get an ical feed from sched.org14:02
fifieldt_all hail nova-network14:02
koolhead17i will not add/push it in offical repo unless i test it atleast 10 times14:02
koolhead17:)14:02
annegentlekoolhead17: ok, how can you incorporate?14:02
koolhead17fifieldt_: i don`t want nova-network die so soon14:02
koolhead17:D14:02
annegentlekoolhead17: oh well propose apatch and we'll see how you incorporate :)14:02
*** markvan_ has joined #openstack-meeting14:02
annegentlekoolhead17: yeah it's definitely not dead since quantum is so hard14:03
ttxmordred: if only sched was open source ;)14:03
annegentleheh14:03
annegentleok, I'll end our meeting -- thanks all for attending!14:03
annegentle#endmeeting14:03
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"14:03
openstackMeeting ended Tue Apr  9 14:03:27 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docwebteam/2013/docwebteam.2013-04-09-13.00.html14:03
koolhead17annegentle: yes let me get it 100% first & will write it in docbook & request 4 merge14:03
mordredttx: wow, if only there was an open source option for doing that task...14:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docwebteam/2013/docwebteam.2013-04-09-13.00.txt14:03
ttxmordred: oh.14:03
openstackLog:            http://eavesdrop.openstack.org/meetings/docwebteam/2013/docwebteam.2013-04-09-13.00.log.html14:03
fifieldt_cheers all14:03
ttxmordred: how about http://openstacksummitapril2013.sched.org/all.ics14:03
fifieldt_zzz time14:03
* ladquin runs to class (after disturbing the peace in -infra)14:03
sdaguemordred: or http://openstacksummitapril2013.sched.org/sdague.ics (with your username)14:04
ttxor even better: http://openstacksummitapril2013.sched.org/YOURNAMEHERE.ics14:04
mordredoh - neat14:04
ttxmordred: details @ http://openstacksummitapril2013.sched.org/mobile-site14:04
fifieldt_night annegentle, koolhead17, writerDiane, ladquin, Daisy14:04
writerDianegood night!14:04
koolhead17night fifieldt_14:04
annegentlenight! :)14:04
ladquinnight, fifieldt_14:04
*** ek6 has quit IRC14:04
ttxmordred: looks like they did their homework14:05
*** fifieldt_ has quit IRC14:05
*** writerDiane has left #openstack-meeting14:05
*** armax has joined #openstack-meeting14:05
sdaguethat worked at least in the last summit14:05
sdagueI used it last time14:05
*** armax has left #openstack-meeting14:05
*** armax has joined #openstack-meeting14:06
*** Gordonz has joined #openstack-meeting14:06
*** markvan has quit IRC14:06
*** markvan_ is now known as markvan14:06
*** Gordonz has quit IRC14:06
*** maoy has joined #openstack-meeting14:07
mordredworks!  yay!14:07
*** Gordonz has joined #openstack-meeting14:07
*** Daisy has quit IRC14:07
*** mrodden has joined #openstack-meeting14:08
*** boris-42 has quit IRC14:09
jaypipesannegentle: what did I do now? :)14:10
annegentlejaypipes: hee. You suggested submodules for storing translations for docs. Way to go dude. :)14:10
annegentlejaypipes: at least I think it was you14:10
jaypipeshehe14:10
*** metral_ has joined #openstack-meeting14:16
*** dolphm has joined #openstack-meeting14:18
*** dolphm has quit IRC14:18
*** oubiwann has joined #openstack-meeting14:19
*** dolphm has joined #openstack-meeting14:19
*** metral has quit IRC14:19
*** metral_ is now known as metral14:19
*** beagles_brb is now known as beagles14:22
*** danwent has joined #openstack-meeting14:23
*** eharney has joined #openstack-meeting14:24
*** dwcramer has joined #openstack-meeting14:25
*** davidha has joined #openstack-meeting14:26
*** oubiwann has quit IRC14:28
*** cp16net|away is now known as cp16net14:28
*** cp16net is now known as cp16net|away14:28
*** cp16net|away is now known as cp16net14:28
*** mrodden1 has joined #openstack-meeting14:29
*** colinmcnamara has joined #openstack-meeting14:31
*** sirushti has joined #openstack-meeting14:33
*** mrodden has quit IRC14:33
*** maoy_ has joined #openstack-meeting14:35
*** egallen has quit IRC14:35
*** maoy has quit IRC14:35
*** maoy_ is now known as maoy14:35
*** garyTh has joined #openstack-meeting14:36
*** fnaval has quit IRC14:37
*** john5223 has joined #openstack-meeting14:37
*** stevemar has joined #openstack-meeting14:38
*** dolphm has quit IRC14:40
*** egallen has joined #openstack-meeting14:45
*** sacharya has quit IRC14:45
*** lloydde has quit IRC14:45
*** zhuadl has quit IRC14:45
*** cp16net is now known as cp16net|away14:46
*** ociuhandu has joined #openstack-meeting14:48
*** dolphm has joined #openstack-meeting14:48
*** primeministerp has quit IRC14:49
*** sankarshan is now known as sankarshan_away14:49
*** kirminas has quit IRC14:51
*** cp16net|away is now known as cp16net14:53
*** ivasev has joined #openstack-meeting14:53
*** fnaval has joined #openstack-meeting14:54
*** colinmcnamara has quit IRC14:55
*** topol has joined #openstack-meeting14:57
*** metral has quit IRC14:57
*** primeministerp has joined #openstack-meeting14:57
primeministerp#startmeeting #hyper-v14:57
openstackMeeting started Tue Apr  9 14:57:37 2013 UTC.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.14:57
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:57
*** openstack changes topic to " (Meeting topic: #hyper-v)"14:57
openstackThe meeting name has been set to '_hyper_v'14:57
primeministerpthere we go14:57
primeministerphi everyone14:57
primeministerpdon't think we have everyone yet14:58
primeministerpwe'll wait five14:58
*** dolphm has quit IRC14:58
*** pnavarro has joined #openstack-meeting14:59
primeministerppnavarro: pedro!14:59
pnavarrohi primeministerp !14:59
primeministerppnavarro: getting ready for the summit?14:59
pnavarroyeahhh ready for the partys !14:59
primeministerphahaha15:00
primeministerpgetting the internal clock ready15:00
primeministerphey btw15:00
primeministerpactually i'll wait a sec15:00
primeministerpwant to see if the cern folks show up15:00
pnavarrook !15:00
primeministerpwell15:01
*** n0ano has joined #openstack-meeting15:01
primeministerpI started putting some puppet manifests on github15:01
primeministerppnavarro: ^15:01
pnavarrogreat15:01
primeministerppnavarro: one for pxe provisioning linux/windows, one for building a winpe image, and the nova-compute node beginings15:02
primeministerphopefully we can work w/ luis and add to it15:03
*** danwent has quit IRC15:03
primeministerpanyway what's the state of the cinder bits15:03
primeministerpI saw you report a bug to alessandro15:03
primeministerpthat was found in the installer15:03
pnavarrothe installer works ok15:03
ociuhanduhi all15:03
primeministerphi tavi15:04
pnavarrobut, I have problems when launching the service15:04
primeministerppnavarro: something in the conf file?15:04
pnavarrono, it's still something related to eventlet15:05
primeministerpo15:05
*** mrodden has joined #openstack-meeting15:05
primeministerpmrodden1: howdy15:05
primeministerpmrodden: howdy15:05
pnavarroif i start cinder-all (cinder-volume, cinder-all, cinder-volume) it works15:05
*** Mandell has joined #openstack-meeting15:05
primeministerpociuhandu: are you going to be ready to pick back up on the puppet bits post summit?15:05
ociuhanduprimeministerp: yep15:06
primeministerpociuhandu: good15:06
*** mrodden has left #openstack-meeting15:06
primeministerpociuhandu:anything else to add from the cloudbase side of things?15:07
primeministerpi was hoping luis and iben would show up to discuss the puppet bits15:07
primeministerpbut if they are not then I can save it for the summit15:08
pnavarroso primeministerp, I'll send an e-mail later about that15:08
ociuhanduwe released the grizzly installer so the beta one can "move on"15:08
*** mrodden1 has quit IRC15:08
primeministerppnavarro: about what?15:08
pnavarroabout cinder problems15:08
primeministerpo15:08
primeministerpthx15:08
primeministerpappreciate it15:08
primeministerpanything either of you want to add then?15:09
primeministerpif not looking forward to seeing you both at the summit.15:09
*** gyee has joined #openstack-meeting15:09
primeministerpi'll be in #openstack-hyper-v if there's questions15:09
primeministerp#endmeeting15:09
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"15:09
openstackMeeting ended Tue Apr  9 15:09:55 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:09
openstackMinutes:        http://eavesdrop.openstack.org/meetings/_hyper_v/2013/_hyper_v.2013-04-09-14.57.html15:09
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/_hyper_v/2013/_hyper_v.2013-04-09-14.57.txt15:09
openstackLog:            http://eavesdrop.openstack.org/meetings/_hyper_v/2013/_hyper_v.2013-04-09-14.57.log.html15:10
*** egallen has quit IRC15:15
*** dricco has joined #openstack-meeting15:15
*** psedlak has quit IRC15:18
*** egallen has joined #openstack-meeting15:18
*** markwash has joined #openstack-meeting15:18
*** sacharya has joined #openstack-meeting15:23
*** hanrahat has joined #openstack-meeting15:24
*** gyee has quit IRC15:27
*** gyee has joined #openstack-meeting15:29
*** danwent has joined #openstack-meeting15:29
*** ijw has joined #openstack-meeting15:34
*** hanrahat has quit IRC15:38
*** afazekas has quit IRC15:39
*** otherwiseguy has joined #openstack-meeting15:41
*** beagles is now known as beagles_appointm15:42
*** rkukura has left #openstack-meeting15:43
*** topol has quit IRC15:44
*** liang_ has joined #openstack-meeting15:48
*** koolhead17 has quit IRC15:49
*** salv-orlando has joined #openstack-meeting15:53
*** dolphm has joined #openstack-meeting15:54
*** writerD__ has joined #openstack-meeting15:55
*** ayoung-afk is now known as ayoung15:55
*** davidkranz has quit IRC15:55
*** davidkranz_ has joined #openstack-meeting15:55
*** topol has joined #openstack-meeting15:59
*** matelakat has joined #openstack-meeting16:00
matelakatHi16:00
BobBall#startmeeting XenAPI16:00
openstackMeeting started Tue Apr  9 16:00:44 2013 UTC.  The chair is BobBall. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: XenAPI)"16:00
openstackThe meeting name has been set to 'xenapi'16:00
*** colinmcnamara has joined #openstack-meeting16:00
BobBallMorning!16:00
BobBall#topic Actions16:01
*** openstack changes topic to "Actions (Meeting topic: XenAPI)"16:01
BobBallMate - documenting ISO boot?16:01
matelakatThat's sitting in the backlog at the moment together with the Wiki -> doc16:01
matelakat/boot/guest has been added to the docs.16:02
BobBallOk got it16:02
*** hemna has joined #openstack-meeting16:02
BobBallthat was action #316:02
BobBallAction #4 was  add https://wiki.openstack.org/wiki/XenServer/BootFromISO to the install docs16:02
matelakatdevstack change also merged to trunk.16:02
BobBallis that the same as  "look at documenting ISO boot"?16:02
matelakatI think these two items are the same16:03
BobBall#action matelakat to document ISO boot16:03
BobBallThere you go - the action can carry over to next week :)16:03
matelakatIt's not prioritized.16:03
BobBallAh - it's worth mentioning what the agenda is this week16:03
BobBallGood point.  But it's in the backlog.16:03
BobBallWe can close that action then16:03
matelakatOkay.16:04
*** liang_ has quit IRC16:04
BobBallSorry for pushing it over to next week16:04
BobBallI don't think I can #unaction :)16:04
matelakatYou can always try16:04
BobBall*trying to log in to the wiki to get the Agenda*16:04
matelakat#topic Actions from last meeting16:05
BobBall#link This week's agenda is https://wiki.openstack.org/w/index.php?title=Meetings/XenAPI&oldid=1998316:05
BobBallI'd already done actions16:05
BobBalllet's move on to the next agenda item16:05
BobBall#topic blueprints16:05
*** openstack changes topic to "blueprints (Meeting topic: XenAPI)"16:05
matelakatNo update from my side.16:06
BobBallI know it's empty and there's nothing to discuss - but we'll be talking about the blueprints at the summit :)16:06
BobBall#topic docs16:06
*** openstack changes topic to "docs (Meeting topic: XenAPI)"16:06
BobBallSo the agenda links to a couple of the changes that have been made:16:06
BobBall#link https://review.openstack.org/#/c/26079/ documents /boot/guest16:06
BobBall#link https://review.openstack.org/#/c/26086/ documents dom0 modifications in the install manual16:06
matelakatAll merged.16:06
BobBallGood news16:07
BobBallanything else on the docs front pending?16:07
matelakatNot really, apart from the ISO stuff.16:07
matelakatI am looking at Quantum at the moment.16:07
BobBallSounds good to me - apparently we're in good shape to move into Havana then!16:08
BobBall#topic Bugs / QA16:08
*** openstack changes topic to "Bugs / QA (Meeting topic: XenAPI)"16:08
matelakatSome docs are saying, that quantum is using the internal xapi interface - so we might need to revisit the architecture diagram.16:08
BobBallsorry, yes16:09
BobBallbut that's something we can do once the quantum patch hits trunk16:09
matelakatsure.16:09
BobBallwhich has been ressurected again I see16:09
BobBallWe need to try and keep it alive this time - hopefully post-summit we can join the push for getting it merged16:10
BobBallok16:10
BobBallso are there any other bugs to talk about?16:10
matelakatpass16:11
BobBallThe iSCSI XSM block migration bug (can't XSM migrate when an iSCSI volume is attached) has a candidate fix up at https://review.openstack.org/#/c/25419/16:11
BobBallFeel free to review it Mate :)16:11
matelakatOkay.16:11
BobBallDon't think we've got other bugs16:12
BobBallUnfortunately with John not with us (just this week and next) he's not able to raise any more bugs with us!16:12
matelakat:-)16:12
BobBall#Topic Open discussion16:12
*** openstack changes topic to "Open discussion (Meeting topic: XenAPI)"16:12
BobBalloh - we skipped a bit from the agenda16:13
matelakatI guess we'll skip the meeting next week.16:13
BobBallsorry - the result of running the full tempest test is up16:13
BobBallhttp://paste.openstack.org/show/35276/16:13
*** ryanpetrello has quit IRC16:13
BobBallA few things to work on before XenAPI has full coverage of the tempest tests16:13
matelakaty16:13
BobBallbut only 3 failures is positive since we don't gate on Tempest on XenAPI yet16:13
*** ryanpetrello has joined #openstack-meeting16:14
BobBallof course the 3 errors may be something to look into too, but all in all better than it could have been16:14
BobBallSo yes, next week's meeting will be cancelled since we'll all be at the summit16:14
BobBalland for a pre-summit meeting we can probably finish in record time!16:15
BobBall#endmeeting16:15
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"16:15
openstackMeeting ended Tue Apr  9 16:15:16 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:15
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-04-09-16.00.html16:15
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-04-09-16.00.txt16:15
BobBallSee you on Monday!16:15
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-04-09-16.00.log.html16:15
matelakatSee U16:15
*** matelakat has quit IRC16:15
*** primeministerp has quit IRC16:17
*** pnavarro has quit IRC16:18
*** lloydde has joined #openstack-meeting16:23
*** lillie has quit IRC16:23
*** garyk has quit IRC16:24
*** lillie- has joined #openstack-meeting16:24
*** gyee has quit IRC16:28
*** davidha has quit IRC16:33
*** markmcclain has quit IRC16:34
*** markmcclain has joined #openstack-meeting16:35
*** koolhead17 has joined #openstack-meeting16:35
*** johnthetubaguy has joined #openstack-meeting16:38
*** johnthetubaguy has left #openstack-meeting16:39
*** garyk has joined #openstack-meeting16:40
*** SergeyLukjanov has quit IRC16:40
*** egallen has quit IRC16:41
*** egallen has joined #openstack-meeting16:41
*** rahmu has quit IRC16:44
*** dolphm has quit IRC16:45
*** dolphm has joined #openstack-meeting16:48
*** mrunge_ has joined #openstack-meeting16:50
*** diogogmt has joined #openstack-meeting16:51
*** mrunge has quit IRC16:52
*** jog0 has joined #openstack-meeting16:52
*** terry7 has joined #openstack-meeting16:53
*** ijw has quit IRC16:53
*** otherwiseguy has quit IRC17:01
*** otherwiseguy has joined #openstack-meeting17:04
*** ijw has joined #openstack-meeting17:04
*** boris-42 has joined #openstack-meeting17:09
*** davidha has joined #openstack-meeting17:11
*** marun has quit IRC17:13
*** oubiwann has joined #openstack-meeting17:18
*** vipul is now known as vipul|away17:18
*** marun has joined #openstack-meeting17:20
*** salv-orlando has quit IRC17:22
*** vipul|away is now known as vipul17:23
*** egallen has quit IRC17:23
*** marun has quit IRC17:24
*** marun has joined #openstack-meeting17:25
*** mrunge_ has quit IRC17:25
*** marun has joined #openstack-meeting17:25
*** egallen has joined #openstack-meeting17:25
*** jpich has joined #openstack-meeting17:26
*** SergeyLukjanov has joined #openstack-meeting17:29
*** dhellmann has quit IRC17:32
*** dhellmann has joined #openstack-meeting17:33
*** lloydde has quit IRC17:36
*** lloydde has joined #openstack-meeting17:38
*** Kharec has quit IRC17:38
*** dwaite has joined #openstack-meeting17:39
*** eharney has quit IRC17:42
*** eharney has joined #openstack-meeting17:43
*** eharney has quit IRC17:43
*** marun has quit IRC17:43
*** marun has joined #openstack-meeting17:43
*** eharney has joined #openstack-meeting17:43
*** eharney has quit IRC17:43
*** eharney has joined #openstack-meeting17:43
*** eharney has quit IRC17:44
*** eharney has joined #openstack-meeting17:44
*** eharney has quit IRC17:44
*** eharney has joined #openstack-meeting17:45
*** eharney has quit IRC17:46
*** eharney has joined #openstack-meeting17:46
*** eharney has quit IRC17:46
*** eharney has joined #openstack-meeting17:46
*** haleyb has left #openstack-meeting17:49
*** Yada has quit IRC17:54
*** spzala has joined #openstack-meeting17:54
*** gyee has joined #openstack-meeting17:59
stevemaro/17:59
dolphmo/18:00
dolphm#startmeeting keystone18:00
openstackMeeting started Tue Apr  9 18:00:19 2013 UTC.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
openstackThe meeting name has been set to 'keystone'18:00
topolHello, anyone have plans for next week?18:00
dolphmi was thinking about staying home and watching tv18:00
stevemaryeah, i was thinking the same18:00
dolphm#topic OpenStack summit!18:00
*** openstack changes topic to "OpenStack summit! (Meeting topic: keystone)"18:00
stevemarheard something about a summit18:01
*** joesavak has joined #openstack-meeting18:01
spzalaHi all!18:01
joesavako/ hi18:01
dolphmsomething something yelling at each other in tiny conference rooms on the west coast something something18:01
dolphm#link https://wiki.openstack.org/wiki/Summit/Havana/Etherpads#Keystone18:01
gyeeand bad beer breath18:01
dolphmI created etherpads for all of our summit sessions18:01
topoldolphm, cool18:02
dolphmIn a couple cases there were existing etherpads so I ensured those were used - if there's an existing etherpad that I didn't link, please crosslink them and move the aggregate the content into one place as appropriate18:02
topolI need to fill mine out18:02
dolphmi just stubbed all the new ones18:02
dolphmat minimum, each etherpad needs to have a list of topics that need to be discussed, and a question to be answered / goal to be reached / etc18:02
topolwill do18:03
dolphm#topic Bad beer breath arguments18:03
*** openstack changes topic to "Bad beer breath arguments (Meeting topic: keystone)"18:03
*** darraghb has quit IRC18:03
dolphmso, for officially unofficial unconferencing purposes, i guess twitter?18:03
*** nachi has joined #openstack-meeting18:03
stevemarsounds easy enough18:04
gyee+118:04
dolphmI'll be arriving in Portland around 3p on Sunday, and i'll start tweetering wherever i wander thereafter if anyone wants to follow/join/stalk do some pub-based arguing18:04
dolphm#link https://twitter.com/dolphm18:04
dolphm(this is where everyone posts links to their twitter account or runs off to twitter to sign up)18:04
joesavak#link twitter.com/joesavak18:05
stevemar#link https://twitter.com/stevebot18:05
dolphmjoesavak: fully formed uri's please18:05
dwaite#link https://twitter.com/dwaite18:05
*** colinmcnamara has quit IRC18:06
joesavak#link https://twitter.com/joesavak18:06
topol#link https://twitter.com/bradtopol18:06
*** egallen has quit IRC18:06
dolphmayoung: ?18:06
dolphmgyee: ?18:07
gyeeI need to sign up first :)18:07
dolphm#link https://twitter.com/heckj18:07
dwaiteoh interesting, what is this twitter thing that I've never heard about?18:07
joesavaklol18:08
dolphmit's where you regurgitate unoriginal truncated quotes from more creative sources than yourself18:08
joesavakgarbage data replicator18:08
dolphm#topic Grizzly docs18:08
*** openstack changes topic to "Grizzly docs (Meeting topic: keystone)"18:08
dolphm#link http://docs.openstack.org/18:08
dolphmdocs need some updating now that grizzly has shipped18:08
dolphmi believe we have a short window before the docs open up for havana-related things18:09
dwaitedolphm: https://twitter.com/dwaite/status/32168624962471936018:09
dolphmso please get to reviewing, testing, revising & amending as appropriate :)18:09
topoldolphm, do you have a list of known doc issues you want to hand out to folks?18:10
dolphmdwaite: i hope it's not awkward if i retweet your unattributed quote18:10
dolphmtopol: i haven't taken a pass through the doc bug list myself, yet18:10
dolphm#link https://bugs.launchpad.net/openstack-manuals18:10
topolor do we just read an look for glaring errors18:10
dolphmthere's lots of stuff in there for us to tackle though18:11
topolOK. figured you would say that18:11
dolphmthere's several major new things in grizzly that are undocumented afaik18:11
ayoungI'm here.18:11
dolphmsource-18:11
dolphm#link https://github.com/openstack/openstack-manuals/tree/master/doc/src/docbkx18:11
dolphmthings that come to mind: pki_setup, policy.json enforcement/customization18:11
dolphmmaking DEFAULT_DOMAIN_ID go on non-sql based identity drivers *cough*ldap*cough*18:11
dolphmldap schema changes18:12
ayoungUgh...twitter.  DO I need to set up an account?  Someone already squatted on admiyo18:12
*** metral has joined #openstack-meeting18:12
dolphmayoung: https://twitter.com/ayoungerest18:12
dwaitedolphm: I prefer thinking twitter is so that the next generations can still know what it feels like to compose a classified ad18:13
dolphmlol18:13
dolphmhmm18:14
dolphm#topic High priority bugs or immediate issues?18:14
topol4 sale Buick Skylark 76K Mint18:14
*** openstack changes topic to "High priority bugs or immediate issues? (Meeting topic: keystone)"18:14
*** metral has quit IRC18:14
*** metral has joined #openstack-meeting18:14
dolphm(i'm not really aware of anything)18:15
dolphmthere's a few unanswered queries on the mailing list regarding PKI and LDAP if anyone wants to take a stab at forming a coherent semi-useful response :)18:16
topolK, I remember seeing an LDAP one18:16
dolphm#link http://www.mail-archive.com/openstack@lists.launchpad.net/msg21954.html18:17
topolI can take that18:17
dolphm#link http://www.mail-archive.com/openstack@lists.launchpad.net/msg21806.html18:17
dolphmPKI ^18:17
dolphmi think i'm qualified to answer the PKI one, but i don't want to get security details wrong18:17
dolphmso, ayoung?18:17
gyeedolphm, I took care of that already18:18
*** rnirmal has quit IRC18:18
gyeeMark is good to go18:18
ayoung#link https://twitter.com/admiyoung18:18
*** rmohan has quit IRC18:18
dolphmgyee: hmm, alright -- was it off-list then?18:18
*** rmohan has joined #openstack-meeting18:18
gyeedolphm, yeah, I forgot to reply to the whole list18:18
ayoungdolphm, -dev or just openstack?  I18:18
dolphmgyee: it'd be nice if you resent it to the list :)18:18
ayoung'm about 3500 messages behind on the main list18:18
gyeedolphm, sure18:19
ayoungand 4600 behind on -dev18:19
dolphmayoung: the two i linked above are the only ones i'm aware of18:19
topolayoung, better do like the postman and start burying them in your basement18:19
gyeeayoung, try to use your round folder more often18:19
*** henrynash has joined #openstack-meeting18:20
dolphmi'm also working on v3 auth in keystoneclient when i have time, but it's been a really slow process and there's way more changes required than expected18:20
henrynashjoined, sorry to be late18:20
dolphmi'd like to do a v0.3.0 release of keystoneclient by the end of the week with v3 auth and any relevant bug fixes we can squeeze in18:20
ayoungMark asked me off list and I told him to ask here.  But I did answer him directly.18:20
*** rmohan has quit IRC18:20
*** rmohan has joined #openstack-meeting18:21
dolphm#topic Open discussion18:21
*** openstack changes topic to "Open discussion (Meeting topic: keystone)"18:21
gyee#link https://twitter.com/gyeeeeee18:21
ayoungLDAP one ... guessing that the pre-existing values don't have default domain set18:21
henrynashdolphm: feel free to pull me in to work on the client of you need help18:21
*** rnirmal has joined #openstack-meeting18:21
dwaitere: session next week, I thought about it and will probably drop SCIM from slides in favor of OpenID (Connect). Not sure if I have a recourse to update schedules.18:22
dolphmhenrynash: thanks18:22
dwaitewas hoping to have draft slides to share, but still need to pull out more content for time :)18:22
henrynashdwaite: I think OpenID connect would be a great thing to cover18:22
dolphmhenrynash: p.s. we exchanged links to twitter accounts earlier if you have one to add18:22
topol+1 on OpenID connect18:22
ayoung-2 on OpenID and any web only SSO18:23
dolphmdwaite: if you email me a new description, i can revise sched.org18:23
dwaiteok!18:23
ayoungthe more I read about them, the more scared I get18:23
henrynashdolphm: @henrynash18:23
dolphmweb-only is a definite non-starter18:23
henrynash(shockingly)18:23
dolphm#link https://twitter.com/henrynash18:23
ayoungRedirect based SSO is a non starter in my book18:25
*** nijaba has quit IRC18:26
ayoungdwaite, you are not going to talk about Kerberos or Client Side X509, are you?18:27
dwaitevery briefly18:27
topoldwaite, I believe you are not supposed to put a slide deck together, just FYI18:27
*** nijaba has joined #openstack-meeting18:27
*** nijaba has quit IRC18:27
*** nijaba has joined #openstack-meeting18:27
ayoungI'm going to cover Kerberos in depth.  I think that my talk is just going to eat into the first Keystone session.18:28
topolso the OS design summit gurus tell me18:28
dwaitehmm, will there be a projector for shadow puppetry?18:28
*** hanney has quit IRC18:28
ayoung it got scheduled as a main conference talk, but they decided to schedule it on the only day that it conflicted with things I needed to do.18:28
dolphmslides should be incredibly short so we can get to the discussion stuff18:29
dolphm3 slides in a design summit session is a lot18:29
dolphmand if you have an intro slide something is wrong18:29
ayounghttp://openstacksummitapril2013.sched.org/event/02841e3d64620e15b861db63628735bd#.UWReAaquI94  is the same time as the first Keystone slot.  dolphm what is going in there?18:29
dolphmi didn't schedule that18:29
ayoungSAML, OAuth 2, and SCIM - Overview and Application:18:29
ayoungdolphm, I know...that was the confusion last week.  Now I am committed, though18:30
topoljust curiously why do the other projects get like 4 days of design summit and we get 1?18:30
dolphmask if you can have that session moved to wednesday morning?18:30
ayoungSo I am going to miss dwaite 's session18:30
ayoungI'll try18:30
dolphmtopol: nova is the only one that gets a *lot* of time18:30
topolOK18:31
dolphmoslo, glance, swift and keystone are all about the same18:31
ayoungdolphm, any idea who to ask?  This whole thing is kindog a mystery to me18:31
dwaitehmm. thats no good. I get the feeling that we will be pushing strongly opposing technologies18:31
topolprimadonnas :-)18:31
dolphmayoung: ttx would know18:31
dwaiteif we conflict - where will the fight be, where will the entertainment be?18:31
ayoungdwaite, nah, we need to support a range of options18:31
dwaite:D18:31
ayoungand not dictate18:31
*** adjohn has joined #openstack-meeting18:31
dolphmdwaite: that's the discussion we want to have at the summit :)18:32
dolphmdesign summit = coming to an agreement & making a decision18:32
ayounghttp://www.swordsofmight.com/larp-weapons-latex-swords.aspx  in the middle of the lunch room, I think18:32
*** bknudson has joined #openstack-meeting18:32
dolphmdwaite: i scheduled your talk first on thurs because i imagine the outcome will affect the discussions for the rest of the day18:32
dwaiteooh, no pressure18:32
dwaitewow those swords are great18:32
topoldwaite, I just wanted to let you know, we are all counting on you18:33
dwaiteneed one on the class divider of my cubicle, over my head18:33
dwaitehmm, I'm going to try to crush things down. any other points will be in my notes to bring up in discussion :D18:34
*** markwash has quit IRC18:34
*** colinmcnamara has joined #openstack-meeting18:35
topolthose larp throwing knives are surprisingly affordable18:35
ayoungshould we plan on having a face-to-face meeting on Monday morning and plan out the rest of the week then?18:36
topolayoung +118:36
stevemar+1, that would help out18:36
henrynashayoung: +1 count me in18:37
*** adjohn_ has joined #openstack-meeting18:37
dolphmimmediately after design summit kickoff?18:37
gyeesounds good18:37
ayoungyes18:38
ayoungI need to make sure I get to this one at 11 http://openstacksummitapril2013.sched.org/event/66519fa2fd27cfc6b1428b62aac3fba2#.UWRf5aquI9418:38
ayoungand I suggest we have a decent number of Keystone folks there.  That is Trust/Oauth stuff.18:38
dolphmooh, anyone aware of any other non-keystone track sessions that we should be crashing?18:38
ayoungBut I don't think we have anything pressing at the 9 AM session18:38
dolphm9am is the intro18:39
gyeedolphm, is Key Manager part of Keystone?18:39
dolphmyes18:39
gyeecool18:39
ayoungSorry, 9:50.  First session.18:39
dolphmthere's definitely some debate about that18:39
dolphmbut it's on our track, regardless of whether the feature ends up in keystone18:39
gyeelooking forward to that one as well18:40
*** adjohn has quit IRC18:40
dolphmi was wondering if the /v3/credentials api could somehow back an external key manager service?18:40
chmouelit would be nice if somebody from keystone can come over to this one http://openstacksummitapril2013.sched.org/event/79780b828202669f572483884dcbf3b1 to talk about v3+ swift18:40
ayoungOh, hey, look, another Federation project18:40
dolphmchmouel: thanks18:40
ayoungI really should look at the other tracks more closely18:41
gyeedolphm, yeah, I was thinking the same thing18:41
*** danwent has quit IRC18:41
dolphmgyee: awesome, i didn't know if i was crazy or not18:41
topolI could use a talking points cheat sheet: if interested in keystone stuff make sure you attendy x, y, z18:41
ayoungdolphm, we've already established that you are crazy.  The rest is details18:41
dolphmayoung: +118:41
ayoungI mean, you took the PTL position.18:41
chmouelheh18:41
dolphm+218:42
topolq.e.d. :-)18:42
ayoungCloud Keep is at the same time http://openstacksummitapril2013.sched.org/event/886118ad75e16dae1da91d9ca9866ca7#.UWRhKKquI9418:42
ayoungKey management as a service18:43
gyeeyou trust you key to the cloud?!18:43
ayoungwe should have someone (or several someones)  here http://openstacksummitapril2013.sched.org/event/40c9f9db30ba96480d094aca32d94f5e#.UWRhUqquI9418:43
ayoung0 downtime upgrades18:43
henrynashayoung: count me in for that18:44
ayoungI think there are a few sessions on Upgrade.  We got burnt on that this release, and we should be the smartest team about it from here on out18:45
ayoungPeople should be able to do Keystone upgrades and have the rest of the cloud keep running, and lets make sure we know what that really means.18:45
dolphmayoung: +118:45
*** danwent has joined #openstack-meeting18:46
nachiIs there a live webcast for keystone sessions. Where will be the slides uploaded for keystone sessions18:46
topolayoung, a failover keystone?18:46
chmouelfrom experience I think the evernotes are the most reliable sources18:46
dolphmnachi: my understanding is that there won't be a webcast18:46
chmoueletherpad18:46
ayoungtopol, that is a different issue18:46
nachiok. thanks18:46
dolphmnachi: and there generally aren't slides for design summit sessions, but notes will be taken here https://wiki.openstack.org/wiki/Summit/Grizzly/Etherpads18:46
*** markmcclain has quit IRC18:47
ayoungtopol, for now, lets absorb from the other projects, but keep in mind the peculiarities of keystone18:47
gyeehow about a self-healing keystone? :)18:47
gyeefixes its own bug18:47
ayounggyee, you know what happens when you remove the keystone?18:47
dolphmnachi: sorry, that was the old link, for havana: https://wiki.openstack.org/wiki/Summit/Havana/Etherpads18:47
nachidophm: ok thanks. i will look at the etherpad for notes18:47
*** SwaminathanVasud has joined #openstack-meeting18:48
dolphmayoung: everything collapses!18:48
ayoungI don't think that metaphor is accidental, either18:48
gyeeayoung, a hole in the wall?18:48
topoldolphm, yes, thats why I said the need for a failover keystone.  all roads typically go thru us18:49
ayoung gyee more likely that there is no wall anymore18:49
*** SwaminathanVasud has quit IRC18:49
dolphmtopol: definitely, but we're not doing anything to block that18:49
topolI was just probing on whether there was a lighter weight option. I can think of one18:50
topols/can/cant18:50
ayoungtopol, so the issue is with Database upgrades.  From here on out, we should think "what would happen if I ran this upgrade with the existing Keystone code?"  COuld I have Grizzz GA and Havana 1 running against the same back end?18:51
topolthat'd be nice.  I'd buy one of those18:52
ayoungIt might not be achievable18:52
ayoungbut we should try18:52
*** markmcclain has joined #openstack-meeting18:52
dolphmwe definitely don't code that way18:52
ayoungit means that we have to deal with holes in the data, either by defaulting values put in by the old code, or by assuming that there can be blanks18:52
ayoungdolphm, not yet we don't.18:52
ayoungThat is why we need to think about it long and hard before we start accepting patches18:53
bknudsonand missing columns?18:53
topolayoung +118:53
*** markmcclain has quit IRC18:53
gyeewe did v2 v3 token data intermix, that was fun :)18:53
dolphmayoung: i imagine it's really, really difficult to take that approach in an open source project18:53
bknudsonhow about a data service?18:54
bknudsona REST API on top of sql.18:54
topolbknudson, how would you use that to mitigate the issue?18:54
bknudsonkeystone is talking to this data service instead of making sqlalchemy calls directly18:55
bknudsonso it can handle the translation18:55
topola proxy layer18:55
*** martine has quit IRC18:56
bknudsonor, it's more like how keystone-client works with older versions of keystone.18:56
*** novas0x2a|laptop has joined #openstack-meeting18:56
bknudsonkeystone would be a client of this data service18:56
ayoungbknudson, how about an AMQP api on top of SQL instead18:56
bknudsonit doesn't have to be rest.18:57
ayoungthat way we can do asyn IO18:57
topolayoung, you still need a piece to be the proxy layer, correct18:57
ayoungasync18:57
dolphmalright, i'm going to endmeeting a few minutes early and leave ya'll to keep dreaming ;)18:57
dolphm#endmeeting18:57
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"18:57
openstackMeeting ended Tue Apr  9 18:57:41 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:57
bknudsoncould be a direct api, but needs to be a layer18:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-04-09-18.00.html18:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-04-09-18.00.txt18:57
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-04-09-18.00.log.html18:57
*** bknudson has left #openstack-meeting18:57
*** olaph has joined #openstack-meeting18:57
topolwe scared dolphm18:58
*** gyee has quit IRC18:58
*** woodspa has quit IRC18:58
ayoungtopol, proxy layer?  You mean as insulation against the schema changing?18:59
*** UtahDave has joined #openstack-meeting19:00
*** markmc has joined #openstack-meeting19:00
*** metral has quit IRC19:00
topolsomething that allows you to be in the middle and handle the differences as necessary19:00
jeblairare ci/infra people around19:01
clarkbo/19:01
pleia2o/19:01
fungiyep19:01
* clarkb needs to grab something to drink be back in a minute19:01
anteayao/19:02
zaroo/19:02
*** dolphm has quit IRC19:02
jeblair#startmeeting infra19:02
mordredo/19:02
openstackMeeting started Tue Apr  9 19:02:38 2013 UTC.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
olapho/19:02
*** jgriffit1 has joined #openstack-meeting19:02
jeblairmordred: do you have anything before you get on a plane?19:03
mordredjeblair: I need to unbreak 2.6 for pbr projects19:03
jeblair#topic mordred plane flight19:03
*** openstack changes topic to "mordred plane flight (Meeting topic: infra)"19:03
*** jgriffit1 is now known as jgriff19:03
jeblairwe had wanted to just wait for rhel to fix that for us19:03
jeblairfungi: but i'm guessing that's not going to happen today19:04
*** jsavak has joined #openstack-meeting19:04
mordredyeah - but rhel seems unhappy too I thought?19:04
*** maoy has quit IRC19:04
mordredor is it legit just 2.6 ubuntu that's giving us the problem?19:04
jeblairmordred: and pbr is broken now19:04
fungii believe dprince was still working on backports from master19:04
*** metral has joined #openstack-meeting19:04
fungiwhich is to say we could switch to rhel6 today for master/havana afaik19:04
jeblairmordred: so what if we switch the pbr projects to rhel for 26?19:05
*** nachi has quit IRC19:05
mordredjeblair: let's try that as step one19:05
mordredjeblair: and see how it goes before trying a plan b19:05
jeblairmordred: i'm worried that otherwise it involves puppet hacking19:05
mordredit _should_ solve the underlying problem19:05
fungimordred: have an example of a job you'd like me to fire on a rhel6 slave as a test?19:05
*** gyee has joined #openstack-meeting19:05
jeblairmordred: which would be very useful, i mean, clarkb thinks we are going to run into this again with python319:06
*** joesavak has quit IRC19:06
fungior is it already testing successfully on rhel6 non-voting?19:06
clarkbjeblair: I actually spoke to someone about that and assuming pip -E works properly we should be able to patch the puppet provider19:06
*** afazekas has joined #openstack-meeting19:06
clarkbor we run puppet twice with two different python envs set19:06
mordredfungi: gate-os-config-applier-python26 and gate-gear-python2619:06
*** turul_ has joined #openstack-meeting19:06
mordredjeblair: yah. I believe we ultimately need to solve this more resiliently19:06
jeblairmordred, clarkb: you want to fight over which of you hacks that? :)19:06
*** colinmcnamara has quit IRC19:06
mordredbut I think that doing that with some time to think about it properly would be nice19:06
clarkbjeblair: I did install zmq for the log pusher script through apt and not pip to avoid this problem :)19:06
fungimordred: those are also failing on rhel6...19:07
jeblairclarkb: also, that's preferred anyway.  :)19:07
fungi#link https://jenkins.openstack.org/job/gate-os-config-applier-python26-rhel6/19:07
*** jgriff has quit IRC19:07
*** sandywalsh has quit IRC19:07
mordredfungi: GREAT19:07
fungino idea if they're failing the same way, but they're failing19:07
clarkbjeblair: I can bring it back up with finch over at puppetlabs, and see if we can hack something useful for all of puppet users19:07
jeblairmordred: fascinating -- and that's with a 2.6 egg19:07
*** joesavak has joined #openstack-meeting19:07
mordredok. that blows my previous theory19:08
clarkbbasically requires me to do more pip testing and feed him the info so that we can get a patch into the provider19:08
mordredhow about I spin up a rhel env and debug and get back to everyone. in the mean time, os-config-applier and gear could disable python2.6 tests for the time being if they're blocked19:08
jeblairmordred: +119:08
clarkbsounds good19:09
jeblairclarkb: +1 as well19:09
mordred(not ideal, but, you know, neither project will die without 2.6 for a day)19:09
mordredclarkb: ++19:09
* mordred will add better 2.6 testing to pbr as well19:09
* mordred cries19:09
jeblairmordred: and did you see the zuul bug i filed?19:09
* dprince is willing to help out if needed too19:09
jeblair#link https://bugs.launchpad.net/zuul/+bug/116693719:09
uvirtbotLaunchpad bug 1166937 in zuul "Option to group multiple jobs together in job trees" [Wishlist,Triaged]19:09
mordredjeblair: I did not. I'll look19:09
mordredawesome19:09
*** jsavak has quit IRC19:10
mordreddprince - if you happen to get bored and figure out why https://jenkins.openstack.org/job/gate-os-config-applier-python26-rhel6/ is breaking in the next hour before I get back online, I will buy you a puppy19:10
jeblairi encapsulated what we talked about, including after you dropped off19:10
*** woodspa has joined #openstack-meeting19:10
mordredjeblair: thanks!19:10
*** vipul is now known as vipul|away19:10
*** vipul|away is now known as vipul19:10
jeblairmordred: i think that implementation is mostly in zuul/model.py19:10
anteayadprince: make sure it is a house trained puppy19:10
mordredexcellent19:10
jeblairmordred: and a little bit in the config parser in scheduler.py19:11
dprincemordred: I already have one (a humpy one)19:11
mordrednice19:11
mordredok - me run to plane19:11
mordredback online in a bit19:11
jeblairmordred: godspeed19:11
jeblairthere were no actions from last meeting19:11
jeblair#topi gerrit/lp groups19:11
jeblair#topic gerrit/lp groups19:11
*** openstack changes topic to "gerrit/lp groups (Meeting topic: infra)"19:12
fungimmm, did we still have any to-dos on that?19:12
fungii think it's wrapped up aside from any other cleanup ttx might have wanted to do in lp19:12
*** colinmcnamara has joined #openstack-meeting19:12
jeblairfungi: did the ptl change land?19:12
fungii was just checking...19:13
fungi#link https://review.openstack.org/2580619:13
fungimerged yesterday19:13
jeblairwoo19:13
fungioh, i probably should add a note in that groups cleanup bug of ttx's19:13
jeblair#topic grenade19:14
*** openstack changes topic to "grenade (Meeting topic: infra)"19:14
*** jhenner has quit IRC19:14
jeblairdtroyer pointed me at some changes he wants to merge first, and then...19:14
jeblairwe can cut stable/grizzly branches of grenade and devstack19:14
jeblairand then i think we'll be set to run non-voting grenade jobs widely on both master and stable/grizzly19:14
clarkb\o/19:15
clarkbis it working now?19:15
jeblairclarkb: it has occasionally succeeded19:15
*** almaisan-away is now known as al-maisan19:16
clarkbnice19:16
jeblairclarkb: i haven't really analyzed the failures to know more about when it succeeds/fails19:16
*** matiu has joined #openstack-meeting19:16
*** matiu has joined #openstack-meeting19:16
jeblair#topic gearman19:17
*** openstack changes topic to "gearman (Meeting topic: infra)"19:17
jeblairso on my side, i wrote a new python gearman client that is much more suited to how we want to use it it zuul19:17
zarothis is depressing me19:17
zaroi've been debugging.19:17
jeblair#link https://github.com/openstack-infra/gear19:18
zarofinally figured out exactly why getting double builds.19:18
*** lbragstad has quit IRC19:18
*** colinmcnamara has quit IRC19:18
zaroit is because error occurs when attempting to reregister functions while current build is running.19:18
jeblairzaro: i can't see a need to register functions while a build is running19:19
*** sandywalsh has joined #openstack-meeting19:19
*** UtahDave has quit IRC19:19
zarowhen error occurs on worker it will close the connection with gearman then reopen but build is still on gearman queue so it runs again.19:19
zarojeblair: code i've got re-registers on events from jenkins.19:20
jeblairzaro: right, but it doesn't need to do that while a build is running19:20
zarojeblair: you might want to register at anytime.19:20
zarojeblair: you mean block until build finishes?19:21
jeblairzaro: functions are registered per-worker; a worker doesn't need to change its functions while a build is running19:21
jeblairzaro: i would postpone changing functions until after the build is complete (which i included in my sketch of a worker routine i sent the other day)19:22
zarojeblair: i see what you mean.  i was looking for a way to get more granular in registering, but didn't see a way.  i can look again.19:22
zarook.  will try this approach again.  can't remember why i gave up last time.19:24
jeblairzaro: i'm of the opinion that the gearman-java GearmanWorkerImpl makes too many assumptions about how it's being used; I think we probably will need to write our own GearmanWorker.  I'm still reading, but I'd like you to consider that as you continue to dig into it.19:24
zarowill do.19:25
*** vipul is now known as vipul|away19:25
jeblair#topic pypi mirror/requirements19:25
*** openstack changes topic to "pypi mirror/requirements (Meeting topic: infra)"19:25
clarkbwe are gating openstack/requirements on the ability to isntall all requirements together19:26
jeblairand when https://review.openstack.org/#/c/26490/ merges, we will actually be running the requirements gate jobs for projects19:26
*** dwaite has quit IRC19:26
*** martine has joined #openstack-meeting19:27
jeblairwe probably need to make the jobs and repo branch aware pretty soon...19:27
jeblairi think that depends on how openstack/requirements wants to handle branches.  maybe a summit question.19:28
clarkbI do have a question about reviewing openstack/requirements. currently we have +2 and approve perms, but it seems like we should defer to the PTLs for most of those reviews?19:28
jeblairclarkb: i think so.  i only really intend on weighing in when it seems to affect build/test oriented things...19:29
fungii've been refraining from approving them in most cases if it's only ci core votes on them, unless there's some urgency19:29
fungiusually only when it's breaking the gate or holding back a ci project19:30
jeblairi don't feel i have a lot of input on random library versions, so yeah, i'd say we should be conservative and mostly the openstack-common and ptls should be weighing in most of the time19:30
jeblairfungi: +119:30
*** lbragstad has joined #openstack-meeting19:30
clarkbcool. I figured we had the perms to sort out problems, but wasnt sure if we had been asked to actuall manage the repo19:31
fungier, poor wording. not a ci project but rather ci work on an openstack project which uses the requirements repo19:31
*** Kharec has joined #openstack-meeting19:31
jeblairmarkmc did explicitly want us to be involved, so afaik, we're not stepping on anyone's toes.19:31
*** ijw has quit IRC19:31
jeblairwe didn't accidentally get perms to the repo, we really are supposed to have them.  :)19:32
jeblair#topic releasing git-review19:32
*** openstack changes topic to "releasing git-review (Meeting topic: infra)"19:32
fungiit happened19:33
jeblairwoo!19:33
fungi1.21 is on pypi, manually this time19:33
fungi1.22 may be automated, if the gods are willing19:33
fungii've been running back through and closing out bug reports if they're fixed in 1.2119:33
*** hanney has joined #openstack-meeting19:33
jeblairfungi: do we need to schedule a chat (perhaps when mordred is around) about pbr/etc for git-review?19:34
fungiyes, some time in one of those rare moments when he's not on a plane19:34
jeblairfungi: i'll put it on the agenda so we don't forget19:34
fungithanks19:34
jeblair#topic baremetal testing19:35
*** openstack changes topic to "baremetal testing (Meeting topic: infra)"19:35
pleia2so the tripleo folks have been changing up diskimage-builder and how it creates the bootstrap node a bit19:35
pleia2so I've been testing changes as it comes along so we're ready once they're ready to start doing formal testing19:36
pleia2also been working on getting this going https://github.com/openstack-infra/devstack-gate/blob/master/README.md#developer-setup but keep bumping into issues with the instructions (they're a bit slim, need some local additions and modifications)19:37
* ttx lurks19:37
jeblairpleia2: they may have bitrotted too, let me know if you have questions19:37
jeblairpleia2: i haven't actually had to follow those in months19:37
pleia2did have a wip-devstack-precise-1365534386.template.openstack.org started on hpcloud this morning though, even if it failed once it tried to grab hiera data from puppet19:37
pleia2jeblair: great, thanks19:38
pleia2just trying to work with it to get a feel for how this works19:38
pleia2(aside from just reading scripts)19:38
pleia2that's about it though for baremetal19:38
fungithat's awesome progress19:38
*** otherwiseguy has quit IRC19:38
anteayao/19:39
jeblairpleia2: you may need to combine the 'install_jenkins_slave.sh' trick of running puppet apply with the devstack-gate developer setup to avoid it trying to talk to our puppetmaster19:39
pleia2jeblair: makes sense, thanks19:39
fungipleia2: did you get past the sqlite db content requirements, i guess?19:39
pleia2fungi: yeah, devananda got me sorted :) (I'll be updating the docs)19:39
jeblairpleia2: thanks much.  :)19:39
fungiexcellent19:39
jeblairi think the config portion of the sqlite db should become a yaml file (though the status portion should probably remain a sqlite db)19:40
jeblairthat is not high on my todo list.  :(19:40
*** markvoelker has quit IRC19:41
jeblair#topic open discussion19:41
*** openstack changes topic to "open discussion (Meeting topic: infra)"19:41
clarkblogstash19:41
anteayao/ I added openstackwatch as an agenda item to the wrong wikipage19:41
jeblairanteaya: which page?19:41
anteayahttps://wiki.openstack.org/wiki/Meetings/CITeamMeeting19:42
fungianteaya: yeah should have been https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:42
* clarkb blazes ahead with logstash because it should be short19:42
anteayayeah19:42
anteayad'oh19:42
jeblairclarkb: go19:42
clarkblogstash is running on logstash.openstack.org. you can get the web gui and query it at http://logstash.openstack.org19:42
jeblairanteaya: (didn't know that existed; will delete)19:42
anteayak19:42
clarkbcurrently all jenkins job console logs should be getting indexed there.19:42
clarkbI may delete data for cleanup purposes19:43
clarkband some of the current data is ugly, but it is getting better as I add filters to logstash to properly parse things19:44
jeblairclarkb: i'd say feel free to delete/reset at will as we work this out up until (if/when) we decide logstash is the primary repository instead of logs.o.o19:44
clarkbover the course of 24 hours we have added over 21 million log lines19:44
fungiany feel for how much retention we can reasonably shoot for there?19:44
clarkbthe index for today (UTC time) is up to almost 12GB compressed19:44
clarkband this is just console logs19:44
clarkbat the end of today UTC time I will run the optimize operation on that index to see if that results in a smaller index19:45
jeblairclarkb: that is a lot.19:45
clarkbyeah, we may need to aggressively filter and/or run a proper elasticsearch cluster if we want to use this for long term storage19:46
jeblairclarkb: as in, almost certainly too much, especially since it's a fraction of what we're storing.19:46
pleia2yeah, I think we're averaging about 2G/day compressed in static form19:46
*** ijw1 has joined #openstack-meeting19:46
*** adjohn_ has quit IRC19:46
clarkbfwiw I think logstash is viable as a short term storage location for easy querying19:46
clarkbthen have an archive like logs.openstack.org for long term storage.19:47
clarkbthen if we need to run the log-pusher script over particular logs to reshove them into logstash if we need something from the past19:47
*** adalbas has quit IRC19:47
*** SergeyLukjanov has quit IRC19:47
clarkbthats about all I have19:48
jeblairclarkb: if we have to compromise on what we use it for, we should actually set out some goals and requirements and make sure we achieve them.19:48
jeblairclarkb: good summit conversation fodder19:48
pleia2reminds me, someone might want to check that my find command to rotate logs is behaving as expected19:48
clarkbjeblair: yup19:48
*** jhenner has joined #openstack-meeting19:48
pleia2pretty sure it should have deleted some by now19:48
*** al-maisan is now known as almaisan-away19:49
fungipleia2: maybe not... as i said before i didn't restore any logs from prior to september 26 when i rebuilt the server19:49
clarkbanteaya: I think you are up19:49
anteayaopenstackwatch is alive: http://rss.cdn.openstack.org/cinder.xml19:49
anteayabut serves no content19:49
pleia2fungi: oh right, I had an off by one month in my head month-wise19:49
anteayathis is what it should be serving: http://rss.chmouel.com/cinder.xml19:49
anteayaso somewhere part of the script is not getting what it expected19:50
anteayaso the question came up, do we stay with making swift work or do we go with serving xml files19:50
jeblairanteaya: i thought the hypothesis was that review-dev was overwriting it?19:50
anteayathat was a potential hypothesis yes19:50
anteayaclarkb might be able to expand on that more19:50
*** vipul|away is now known as vipul19:51
fungijeblair: i chimed in later when i got back from dinner and pointed out that the config on review-dev lacks swift credentials, so could not19:51
jeblairah19:51
anteayaI too had missed that, thank you fungi19:51
anteayaso in terms of a way forward19:51
anteayastay with swift, or go with xml was my understanding of the question19:51
fungiand also suggested that the stdout capability openstackwatch has as a fallback would be a useful way to troubleshoot it19:52
jeblairyes, it seems the lack of content is a separate question from the output format.  that just needs debugging.19:52
anteayaso at this point, do we have a way to debug what is running?19:52
anteayaat least to understand why no content is being served?19:53
jeblairi think it would be useful for this group to decide what we actually want to do with this19:53
fungianteaya: you can run it yourself but don't put swift credentials in the config and it should spew on stdout what it would otherwise upload to swift19:53
jeblairwhat service are we trying to provide?  and how should we host that service?19:53
fungiat least from what i could tell reading through the script19:53
anteayayes, well chmouel's feed bears witness to that19:53
anteayabut I am at a loss as to why our configuration of the script serves no content19:54
fungiwell, the short description is "rss feeds of new changes uploaded for review on individual projects"19:54
clarkbjeblair: I think the service here is providing reviewers/interested parties an alternative to the gerrit project watches and email19:54
chmouelmaybe it would be best to generate xml static file than uploading to swift?19:54
jeblairclarkb: that sounds like a useful service; so in that case, i think we should have it automatically generate a feed for every project on review.o.o19:55
anteayachmouel any idea why our config would serve no content yet yours does?19:55
*** metral has quit IRC19:55
chmouelhumm i'm not sure19:55
chmouellet me check the scollback19:55
fungichmouel: that's one suggestion which came up. basically modify it so that we serve those rss xml files directly from the apache instance our gerrit server19:55
anteayachmouel: the script is the same: https://github.com/openstack-infra/jeepyb/blob/master/jeepyb/cmd/openstackwatch.py19:56
jeblairif we want to make this a more seamless integration with gerrit, then i think we sholud host it at review.o.o.  perhaps at a url like 'review.openstack.org/rss/org/project.xml'19:56
fungiand then link that in the gerrit theme?19:56
chmoueljeblair: the proper solution would be that gerrit itself provide rss feeds :)19:56
jeblairwe could have it either read project.yaml or 'gerrit ls-projects' to get the list19:56
jeblairchmouel: true.  :)  people so rarely volunteer for java hacking projects around here.19:57
chmouelheh fair  java+xml is not much  fun19:57
jeblairfungi: the theme linking will take some thought i think, especially a way to handle the per-project feeds19:58
*** fontana has joined #openstack-meeting19:58
anteayajeblair: should we continue to mull on it and discuss it again next week?19:58
*** ryanpetr_ has joined #openstack-meeting19:58
anteayaI'm not feeling a decision is nigh19:58
fungiright, i'm not immediately coming up with any great ideas as to how to make that visible in the gerrit interface19:58
fungithe projects list is not something people hit often, for example19:59
chmouelnext week is probably going to be beer^H^Hsummit time :)19:59
*** markmcclain has joined #openstack-meeting19:59
clarkbplenty of time for discussion :)19:59
* anteaya notes to use the correct wiki page next time19:59
jeblairyeah, let's think about that.  there's always just documenting it in the wiki; but it would be nice to get some kind of link going on.19:59
jeblairthanks everyone!19:59
jeblairsee you next week, in person, i hope19:59
ttxsee you all soon!19:59
chmouelsee you soon!19:59
jeblair#endmeeting19:59
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:59
openstackMeeting ended Tue Apr  9 19:59:57 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-04-09-19.02.html20:00
*** gabrielhurley has joined #openstack-meeting20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-04-09-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-04-09-19.02.log.html20:00
ttxOK, our turn20:00
ttxWho is around for the TC meeting ?20:00
markmcclaino/20:00
jgriffitho/20:00
markmchey20:00
jd__o/20:00
notmynameo/20:00
ttxsdake, dolphm, annegentle, mikal, mordred, markwash, vishy, gabrielhurley: around ?20:00
*** topol_ has joined #openstack-meeting20:01
gabrielhurley\o20:01
*** lillie- is now known as lillie20:01
*** adalbas has joined #openstack-meeting20:01
*** ryanpetrello has quit IRC20:02
*** markvan has quit IRC20:02
ttxWe need one more to have quorum20:02
*** dolphm has joined #openstack-meeting20:02
ttxand here comes dolphm20:02
dolphmo/20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Apr  9 20:02:42 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: tc)"20:02
openstackThe meeting name has been set to 'tc'20:02
ttxBefore we dive into licensing subtleties... Last minute chance to opt out of the TC members dinner on Wednesday, April 17, 6:30pm at Olympic Provisions NW20:03
ttxI know sdake can't join us... that would make 14 of us.20:03
*** dwcramer has quit IRC20:03
markmcthat's a good crowd :)20:03
ttxAnyone up to call them for booking for 14 ? Will be better if they have a US phone number on the registration :)20:03
ttx#link http://www.olympicprovisions.com/northwest/reservations/20:04
jgriffithttx: I can call them20:04
annegentleor I an20:04
ttxjgriffith: thanks!20:04
annegentlecan even20:04
*** dwcramer has joined #openstack-meeting20:04
ttxannegentle, jgriffith: just make sure one of you does it :)20:04
jgriffithttx: what time Pacific did we settle on?20:04
ttxWednesday, April 17, 6:30pm20:04
jgriffithK.. doing it now20:05
ttx#topic Discussion: Policy on use of GPL libraries20:05
*** openstack changes topic to "Discussion: Policy on use of GPL libraries (Meeting topic: tc)"20:05
*** topol has quit IRC20:05
annegentlethanks jgriffith20:05
ttxjgriffith: let us know if it fails :)20:05
ttxmarkmc: care to introduce this one ?20:05
markmcI guess I'll recap the background to start20:05
markmcso, sdague noticed that cinder was using an AGPL library - rtslib20:05
markmcit's not anymore, so that's a non-issue now20:05
*** markwash has joined #openstack-meeting20:06
markmcbut it did raise the question of what process we use for looking at the licensing of new dependencies20:06
markmcespecially given our bylaws statement about that the project must be distributable under the apache license20:06
ttxwill the central dependency process give us a sufficient barrier to entry so that we can add some validation process ?20:07
markmcso, it's a question of process20:07
fontanamarkmc: the bylaws don't say that exactly :-)20:07
markmcfontana, ok :)20:07
*** topol_ has quit IRC20:07
ttxmarkmc: see what you get when you invite lawyers :P20:07
markmchehe20:07
fontanasorry20:07
* fontana will try to restrain himself20:07
mikalMorning20:07
gabrielhurleyit's also something that core reviewers/PTLs just need to be aware of20:07
markmcttx, the dependency process only enforces the checks we ask reviewers to enforce20:07
*** adalbas has quit IRC20:08
markmcIMHO, it comes down to most permissive license are fine20:08
ttxmarkmc: right, but at least we can insert more process than compared to, say, a mailing-list post20:08
*** ijw1 has quit IRC20:08
markmcttx, absolutely20:08
gabrielhurleyyeah, it's really only an issue for GPL/AGPL/LGPL licenses (or esoteric ones)20:08
ttxwhich was done about 20% of the time anyway20:08
markmcbut in the specific case of GPL/AGPL and maybe other copyleft licenses, we need to have a rule or a process20:08
*** reed has quit IRC20:08
markmcand the more fontana explains the nuances20:09
fontanaI have noticed that OpenStack projects use quite a lot of LGPL dependencies20:09
*** dolphm_ has joined #openstack-meeting20:09
*** dolphm has quit IRC20:09
markmcI think we actually need a process to look at each case20:09
jgriffithdependecies are fine but inclusion is sticky IMO20:09
gabrielhurleythat sounds like exactly the sort of the a Technical Committee would be responsible for... ;-)20:09
gabrielhurley*thing20:09
markmcgabrielhurley, right, exactly20:09
markmcbut do any of us want to make licensing calls on our own?20:10
ttxgabrielhurley: sounds boring. Did we sign up to do boring ? :)20:10
markmcor do we want the support of e.g. the Legal Affairs Committee20:10
dhellmannnew dependencies now need to go through the requirements list project, could a license check be part of that review process20:10
gabrielhurleyI'll make those decisions. unilaterally. because I can. ;-)20:10
markmcdhellmann, absolutely20:10
fontanaI think it is important to understand something about the Legal Affairs Committee20:10
dhellmannso at least there's a point where the review can happen, and every ptl (or core team) doesn't have to worry about it20:10
dolphm_dwcramer: +120:10
dolphm_dhellmann: *20:11
mikalfontana: explain away20:11
markmcyeah20:11
* markmc is more or less done20:11
gabrielhurleydhellmann: point for inserting review: +1, PTLs/core reviewers *not* worrying about: -120:11
markmcand knows fontana has lots of interesting viewpoints on all of this20:11
fontanaWhich is that the Legal Affairs Committee doesn't necessarily have more competence to make decisions on this than any of you do20:11
*** otherwiseguy has joined #openstack-meeting20:11
fontanaTrust me on that.20:11
fontanaIf you want to pretend that it does, okay. I can tell you what the likely result will be.20:12
ttxfontana: could the Legal Affairs Committee give guidelines on what should be acceptable, that reviewers could use in reviewing new dependencies proposed ?20:12
markmcfontana, would you say a committee with that title should have that competence?20:12
jgriffithttx: I'll update on the reservation before we break20:12
gabrielhurleyttx: I've seen that go very badly before. see NASA.20:12
fontanamarkmc: I am not sure.20:12
mikalI do think having some rules of thumb we share with the community is a good idea20:13
mikalOtherwise we'll be starting the conversation from scratch for each dependancy20:13
markmcindeed20:13
*** tong|2 has joined #openstack-meeting20:13
*** tong|2 has left #openstack-meeting20:13
markmcand I think we know roughly what the rule of thumb is20:13
gabrielhurleyI propose that the TC + Legal Affairs draft a general set of "what we know is acceptable, and what we know is *not* acceptable" and then deal with individual grey area cases as they arise. That'd cover the 90% case, right?20:13
fontanaI think the TC should be as involved in this as the Legal Affairs Committee20:14
markmcfontana, agree on that20:14
gabrielhurley+120:14
markmcclain+120:14
mikal+120:14
fontanaUnderstand, the Legal Affairs Committee knows nothing about OpenStack, Python, etc20:14
fontanaOpen source licensing.20:14
mikalI think once we have a rhythmn of what to look for it shouldn't take too much time20:15
markmcgabrielhurley, one idea fontana had is to compile the list of acceptable license by looking at our current set of dependencies20:15
markmcgabrielhurley, any license in there is almost by definition acceptable20:15
gabrielhurleymarkmc: that'd be a good place to start20:15
markmcI have to say, though, I'm not sure at this point what I'd add to the *not* acceptable list20:15
markmcwell, AGPL say20:16
gabrielhurleyyeah, GPL variants. Anything the has a requirement that the code including it also be it's license type.20:16
fontanaI have expressed concern about discrimination against AGPL. There are lots of bad licenses out there.20:16
*** vipul is now known as vipul|away20:16
mordredo/20:16
jgriffithSo we should probably seperate concerns regarding inclusion and dependencies20:16
*** dwaite has joined #openstack-meeting20:17
gabrielhurleyfontana: what do you mean by "concern about discrimination against AGPL"?20:17
markmcgabrielhurley, well, we're talking about libraries here - so, not 'including it' but (for python) 'importing it'20:17
fontanajgriffiths: 'inclusion' = actually using code under some non-Apache license in an OpenStack project source tree?20:17
jgriffithfontana: yes20:17
jgriffithThat's actually what started this in Cinder20:18
fontanagabrielhurley: Like, all other conceivable licenses are okay other than AGPL. A license that says 'no commercial use allowed' is okay. Or an obscure license with an AGPL-like condition (there are several OSI-approved ones).20:18
markmcjgriffith, cinder didn't include AGPL code, it used it as library20:18
gabrielhurleyfontana: that's what I thought you meant, just wanted to be sure. agreed.20:18
gabrielhurleyany copyleft license is a problem.20:18
jgriffithmarkmc: yes, but that's not how this started20:18
fontanagabrielhurley: Including LGPL?20:18
mordredlgpl isn't copyleft20:19
dolphm_gabrielhurley: is copyleft the source of the issue?20:19
fontanaLGPL is copyleft.20:19
markmchehe20:19
mordredin the same way20:19
markmcin the "viral" sense I guess mordred means20:19
fontanaOkay20:19
gabrielhurleylgpl is "modified copyleft", not true copyleft20:19
markmcthat what all this comes down to, no?20:19
*** lloydde has quit IRC20:19
mordredit does not require transferrance of copyright terms20:19
mordredI believe 'viral' is the issue20:19
fontanaYou are reasonably assuming that using an LGPL library has no frightening consequences for OpenStack20:19
gabrielhurleythat ^^^20:19
mordredyes. I am20:20
fontanaThe Apache Software Foundation would disagree with you. I don't disagree, at least in most cases.20:20
gabrielhurleyheh20:20
mordredthe LGPL is essentially the BSD20:20
mordredand I don't agree with many things the apache foundation says20:20
fontanamordred: that is probably a good thing20:20
*** adalbas has joined #openstack-meeting20:20
* gabrielhurley is with mordred on this one20:20
gabrielhurleythere may be intricacies that could be nasty, but again in the 90% case I believe it would be safe20:21
mordredI think the problem is that we have chosen the apache license for our project and do not want to unwittingly wind up shipping a project which causes ours to be licensed differently, yeah?20:21
fontanaanyway the knowledge that many LGPL libraries are being used was what made me think of approaching this by seeing what is actually being done and working out a policy from that20:21
mordredfontana: ++20:21
mikalI certainly think an audit of the current state is required20:21
mikalSo that's not wasted effort20:21
markmcfontana, I'd always assumed LGPL would be on the list of acceptable licenses for library dependencies20:21
mordredpypi.openstack.org/openstack has the entirety of the dependencies that we use on a python basis20:22
mordredincluding non-declared transtive20:22
fontanaOh, that is useful20:22
markmcquestion is whether (the TC thinks that) OpenStack can (ever?) use a GPL library and the result be that OpenStack must now be distributed under the GPL ?20:22
mordredit does not include c librarises such as libxml or libvirt20:22
jeblair(strictly speaking a superset because old ones are not purged)20:22
markmcfontana, and I think you were (on the mailing list) making a reasonable case that we should consider each such case separately20:22
jeblair(and so requires double checking of current state, but is otherwise a great start for what mordred suggested)20:22
mordredmarkmc: I believe that gets down to what the author of that gpl library believes derivative work is20:23
*** ociuhandu has quit IRC20:23
fontanamarkmc: I object to any legal conclusion that using a GPL library requires OpenStack to be distributed under the GPL. This is contradicted by the practices of numerous open source projects.20:23
mordredmarkmc: since they are the ones licensing their work to us for our use under a set of terms20:23
dolphm_i don't see an issue with LGPL's copyleft ... unless we're forking something distributed under LGPL and branding it as an openstack component20:23
mordredfontana: MySQL/Oracle would argue the opposite, of course :)20:23
mordredthus the specific licensing of libmysqlclient20:24
markmcfontana, do you think the TC would be wise to add GPL to the list of "always acceptable" licenses?20:24
fontanamordred: true20:24
mordredI believe it's a grey area20:24
markmcthat using a GPL licensed library never has scary consequences for OpenStack?20:24
fontanamarkmc: No20:24
markmcright, cool20:24
markmcgrey area :)20:24
mordredyay. because we need more grey areas here :)20:24
fontanamarkmc: I just want to say that I think some of this is coming out of superstition20:24
mordredfontana: ++20:24
markmcfontana, I'm persuaded on that :)20:25
fontanaI recognize you have to deal with that superstition. You don't want licensing FUD to hurt OpenStack20:25
gabrielhurleyanything which is GPL (not LGPL) will absolutely need closer review, if not be denied.20:25
*** boris-42 has quit IRC20:25
gabrielhurleythe GPL's terms are quite strict but also full of holes20:25
markmcok, so if we're all happy with this idea of a review process for grey areas like GPL libraries20:25
markmcwhat should the review process be?20:25
dolphm_gabrielhurley: +120:26
markmcif e.g. the TC wants to make that call itself?20:26
fontanamarkmc: What I'd think is that in vast majority of cases GPL library would not be okay20:26
markmcfontana, ok, interesting20:26
mikalI think until we understand the parameters better covering additions in TC meetings is a good idea20:26
gabrielhurleyfontana: I second that20:26
mordredmikal: ++20:26
mikalOnce we have it down to something routine, we can hand it off if we want to20:26
mordredI believe we can safely say that new things licensed Apache2 or BSD or MIT are pretty safe, yeah?20:26
markmcso, we come up with guidelines over time by looking at each case individually?20:27
mordredand things licensed GPL need to come to the TC for further discussion?20:27
mikalmarkmc: yeah20:27
markmcsounds good20:27
fontanaClearly anything Apache2 is safe  :-)20:27
mikalWell, obviously correct things can be a one sentence email to the TC list20:27
mikalThat way there's a paper trail (for example if a dependancy changes its license later)20:27
*** dprince has quit IRC20:27
markmcdo we want help for the grey area reviews from esteemed persons like fontana?20:27
markmcor good doing it on our own?20:27
fontanaAnother issue though is I do not know how accurate license designations for PyPI are20:27
dolphm_who's core on openstack/requirements?20:28
ttxalso current analysis will go a long way to set expectations correctly20:28
mikalttx: agreed20:28
jeblairfontana: often inaccurate, sometimes the metadata even contradicts itself20:28
mikalmarkmc: I think we should escalate to experts whenever we feel the need to20:28
gabrielhurleyfontana: they're about 75% accurate in my experience20:28
fontanajeblair: that was what I was afraid of20:28
gabrielhurleyI have definitely contacted authors in the past to clarify their licenses20:28
fontana75% is better than I thought20:29
mikalWe can use dnspython as a practise run!20:29
*** alexpilotti has joined #openstack-meeting20:29
markmcmikal, seems pretty clear cut permissive :)20:30
ttxso, I think we first need to do a complete analysis of current deps20:30
ttxand have a process in place when a new dep is added, so that licensing is at least considered20:30
mikalI am a bit worried cores will forget to do this when something gets added to the pip files20:31
jeblairi believe VanL was interested in a current-dep analysis as well20:31
ttxwhich means, making openstack/requirement a necessary step for adding deps20:31
markmcit already is, no?20:31
fontanajeblair: yes, re VanL20:31
mordredmarkmc: yes, it is20:31
mordredwe have a gating job for that now20:31
ttxmarkmc: for all projects ? ok20:31
mordredit runs when you change requires files20:32
*** beagles_appointm is now known as beagles_brb20:32
mikalI can't see a wiki page for openstack/requirement. Do we need one?20:33
ttxwho is working on current dependencies analysis ? Should we use some etherpad to share the load ?20:33
gabrielhurleyis it possible to add another field to gerrit for "license approved"? on the dependencies project?20:33
jeblairmikal: i started a stub here: https://wiki.openstack.org/wiki/Requirements20:33
jeblairmikal: if the requirements job fails, it links to that page20:33
*** jsavak has joined #openstack-meeting20:34
mordredgabrielhurley: we'd have to add that field for all projects :(20:34
gabrielhurleydarn. too bad20:34
mikaljeblair: ahhh, cool20:34
*** lloydde has joined #openstack-meeting20:35
ttxfontana: did you start an analysis on the legal affairs committee side ?20:36
fontanattx: not sure, VanL talked about it in an email which you may have been on - I missed last couple of calls20:36
fontanattx: oh, if by analysis you mean the policy analysis... not really20:37
ttxno, meant current dependency licensing lists20:37
fontanattx: I don't think so. VanL is in charge of seeing that that is done I guess20:37
ttxok, so it looks like we could add comments to the *-requires files about dep licensing when known20:37
*** jsavak has quit IRC20:38
*** joesavak has quit IRC20:38
ttxmarkmc: anything you'd see as the next step ?20:38
*** spzala has quit IRC20:38
markmcttx, just the review of current deps licenses20:39
markmcI guess we need to let openstack/requirements folks know they should check licenses too20:39
ttxmarkmc: would you rather etherpad it or submit comments to openstack/requirements ?20:39
ttxthe latter is a bit more painful but also lasts longer20:40
mikalComments sounds better to me20:40
dolphm_could include the license of each dep as in the openstack/requirements repo, which will make it easy for reviewers to see that a particular license has already been reviewed as acceptable20:40
dolphm_then you just have to double check that the author specified the correct license20:40
ttx#action start licensing analysis by adding comments to *-requires files in openstack/requirements20:40
ttxfurther discussion at the dependency management session at the Design Summit20:41
mordreddon't forget when doing analysis - transitive depends20:41
ttxhttp://openstacksummitapril2013.sched.org/event/662c7d06e08b846e64c07efb41101c3420:41
ttxSo, now the bad news.20:41
mordreduhoh20:42
ttxThe restaurant is full on Wednesday night20:42
ttxuntil 920:42
mordredWHATT?20:42
gabrielhurleyha20:42
mordreddo they know who we are?20:42
mordred:)20:42
ttxand let's say that the neighborhood for the RAX party isn't full of other options20:42
ttxso...20:42
ttxwe can move to another day (probably a bad idea)20:42
ttxwe can have dinner at 9 (probably a bad idea)20:43
ttxwe can go to another restaurant and get to the RAX party by our own means20:43
annegentleyeah find another restaurant. Boo hoo20:44
ttxthen hit on 6 cabs to run from there to the party, since public transport is not really an option20:44
gabrielhurleythere's plenty of good food in Portland... we can just grab a couple cabs.20:44
markwashwe can just eat donuts together in a parking lot20:45
mikalLOL20:45
gabrielhurleyI prefer pie20:45
ttxanyone has a suggestion for a restaurant ? Otherwise I'll do proper research tomorrow :)20:45
*** rafaduran has joined #openstack-meeting20:46
annegentlesorry I don't, and your research is good research :)20:46
*** rafaduran has left #openstack-meeting20:46
gabrielhurleyPortland City Grill is lovely, just to throw an option out there20:46
dolphm_i've been told to go to http://www.yelp.com/biz/andina-portland20:46
ttxdolphm_: been there, pretty good20:46
markwashfaint praise? or endorsement?20:47
*** vipul|away is now known as vipul20:47
*** eharney has quit IRC20:47
markwashnevermind20:47
ttxI'll have a proposal up tomorrow :)20:47
* markwash <3s peruvian20:47
markwashmordred: should we talk about image-building in openstack?20:48
markwashand where something like that should live, projectwise?20:49
mordredmarkwash: we can - or we can just do it over beer next week20:49
markwashas you wish20:49
ttxOK, anything more before we close ?20:49
*** lloydde has quit IRC20:49
*** david-lyle has joined #openstack-meeting20:50
ttxI guess not20:50
ttx#endmeeting20:51
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:51
openstackMeeting ended Tue Apr  9 20:51:12 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-04-09-20.02.html20:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-04-09-20.02.txt20:51
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-04-09-20.02.log.html20:51
*** Vek has joined #openstack-meeting20:52
*** tongli has quit IRC20:52
*** tong|2 has joined #openstack-meeting20:52
*** jbresnah has joined #openstack-meeting20:52
*** apevec has joined #openstack-meeting20:54
*** hanney has quit IRC20:54
*** danwent has quit IRC20:55
*** marun has quit IRC20:55
*** lbragstad has quit IRC20:57
*** lloydde has joined #openstack-meeting20:58
*** rmohan has quit IRC20:58
*** eharney has joined #openstack-meeting20:58
*** adjohn has joined #openstack-meeting20:59
*** rmohan has joined #openstack-meeting20:59
*** stevemar has quit IRC20:59
ttxLooks like Andina would be good, we can even take a bus to go there from the Convention Center21:00
dolphm_awesome, i was really hoping to make it there21:01
ttxmarkmc, dolphm, notmyname, markwash, jgriffith, russellb, gabrielhurley, markmcclain, sdake, jd__: around ?21:01
markwasho/21:01
jd__o/21:01
notmynameo/21:01
markmcyep21:01
markmcclaino/21:01
ttxdolphm_: will send message to make sure nobody has some issue with peru21:01
jgriffith./21:01
*** ijw has joined #openstack-meeting21:01
*** vipul is now known as vipul|away21:02
ttx#startmeeting project21:02
openstackMeeting started Tue Apr  9 21:02:22 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: project)"21:02
openstackThe meeting name has been set to 'project'21:02
gabrielhurley\o21:02
ttxWe won't be doing per-project status today, as the agenda is a bit different21:02
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttxshould be quick21:02
ttx#topic Grizzly release post-mortem21:02
*** openstack changes topic to "Grizzly release post-mortem (Meeting topic: project)"21:02
ttxSo... The Grizzly common release was published last week21:03
*** markvan has joined #openstack-meeting21:03
ttxWhile it's hot, anything you would like to raise that we need to better address next time ?21:03
*** lbragstad has joined #openstack-meeting21:03
ttxNova had its share of bugs that flew below release radar until just after release21:03
ttxIn particular https://bugs.launchpad.net/nova/+bug/1158958 and https://bugs.launchpad.net/nova/+bug/116240921:04
uvirtbotLaunchpad bug 1158958 in oslo "Nova API Memcached Encoding Error" [Medium,Confirmed]21:04
gabrielhurleythe translation string freeze/translation re-integration could probably be a little more coordinated. Otherwise I liked the pacing of this release.21:04
*** danwent has joined #openstack-meeting21:04
ttxmarkmc: vishy wanted to consider an early point release to fix the most obvious stuff21:04
ttxgabrielhurley: yes, i'm not sure we picked up the latest translations once RC1 was cut21:05
gabrielhurleyI think it was *inconsistent*21:06
markmcttx, sounds good - Daviey and apevec were talking about that too on the stable-maint list21:06
apevecttx, vishy, how early?21:06
vishywell currently we are identifiying the performance problem21:07
vishythere are a couple critical fixes which we should address asap21:07
vishybut we haven't fully fixed one of them yet :(21:07
ttxgabrielhurley: we globally still need to have a more polished story when it comes to translations. What we translate, how we integrate them, how we use them.21:07
*** vipul|away is now known as vipul21:07
gabrielhurleyindeed. I think there are folks working on that at the summit21:08
*** colinmcnamara has joined #openstack-meeting21:08
ttxvishy: the main thing is to get the fix in stable/grizzly. point release is the cherry on top of the cake21:08
ttxannegentle: how is Grizzly documentation release going ?21:08
*** jhenner has quit IRC21:08
markmcgabrielhurley, kinda randomly, you might be interested in http://openstacksummitapril2013.sched.org/event/17d2bd1f676d9843756b4e0cbda7af9321:08
gabrielhurleymarkmc: thanks for the link. I knew it was happening but hadn't looked for when.21:09
annegentlegabrielhurley: we have a docs translation session Mon. at 1:5021:09
annegentlehttp://openstacksummitapril2013.sched.org/event/b85bf7ac93e121e96dd9a6af16ffa8be#.UWRFvdNAT2k21:09
gabrielhurleyI'll try and attend anything i18n related just on principle. people in the community are stepping up on it more though, which is great.21:10
ttx<ttx> annegentle: how is Grizzly documentation release going ?21:11
annegentlettx: getting there but we don't have to take up Horizon meeting time :)21:11
annegentlettx: oh sorry I'm confused on my meetings :)21:12
annegentle#info in our doc team meeting today we decided to release after the summit21:12
ttxannegentle: indeed. You have plenty of time :)21:12
annegentlewe need more testing21:12
annegentleesp. for install docs of course21:12
*** spzala has joined #openstack-meeting21:12
annegentleI have 2 testers, one for RHEL, one for Ubuntu21:13
annegentleMy best guess is either by 4/26 or by 5/10.21:13
annegentleYou can tell I'm reallll accurate21:13
annegentle:)21:13
*** salv-orlando has joined #openstack-meeting21:14
*** fontana has quit IRC21:14
annegentlefifieldt said in our meeting this morning that "most" of the DocImpact bugs are addressed, but if you logged a DocImpact, it's really on you to follow up21:15
ttxanything anyone wanted to add on the Grizzly postmortem topic ?21:15
annegentlebut I think DocImpact had a good impact this release21:15
annegentle#info if you logged a DocImpact in the Grizzly release, please look into the docs for the impact21:15
gabrielhurleyon a related topic21:16
gabrielhurleythere's probably a wiki page about the tags we use, but it'd be helpful to have something that put them more forward in peoples' minds21:16
gabrielhurleyI myself forget to tag things frequently, or can't remembe what the right tag to use is21:16
ttxgabrielhurley: you can edit the list of official tags in LP21:16
* gabrielhurley didn't know there was one21:17
ttxhttps://bugs.launchpad.net/horizon/+manage-official-tags21:17
ttxgabrielhurley: affects autocomplete21:17
gabrielhurleyinteresting21:17
ttx#topic 2012.2.4 stable release21:17
*** openstack changes topic to "2012.2.4 stable release (Meeting topic: project)"21:17
ttxmarkmc, apevec: floor is yours21:17
markmcwe're almost ready to go, I think21:18
ttxgabrielhurley: (and https://wiki.openstack.org/wiki/Bug_Tags)21:18
markmca couple of reviews in cinder for the nec driver21:18
ttxI checked that there were no missing files in the tarballs, fwiw21:18
markmcbut apart from that, it's been quiet since the freeze21:18
markmcttx, thanks, was there a worry there?21:18
apevecand in quantum for pfc driver21:18
ttxmarkmc: no. Just doublechecking :)21:19
apevecttx, thanks21:19
markmcso, seems good to go to me, unless anyone has any concerns21:19
ttxsounds good21:20
ttx#topic Summit schedule adjustment fair21:20
*** openstack changes topic to "Summit schedule adjustment fair (Meeting topic: project)"21:20
ttxDesign Summit schedule is up at http://openstacksummitapril2013.sched.org/overview/type/design+summit21:21
ttxWe are still missing Glance and Horizon schedules21:21
gabrielhurleyI just pushed mine21:21
*** marun has joined #openstack-meeting21:21
ttxgabrielhurley: hmm, recently then :)21:21
gabrielhurley5 minutes ago21:21
ttxhah21:21
ttxgot me again21:21
* gabrielhurley is multi-tasking21:21
*** russellb has joined #openstack-meeting21:21
ttxmarkwash: any ETA for yours ?21:22
markwashttx: I'd prefer tomorrow night if that is okay21:22
ttxmarkwash: will do21:22
markwashsome things are getting squashed together, and I want a chance for a little more glance team feedback (tomorrow at the glance meeting)21:23
ttxmarkwash: if you have partial content you can still push it though21:23
ttxI know people start looking into their session selection, so the sooner the better21:23
markwashttx: ah, okay, I'll push what I have so far today21:23
markwashgood point!21:23
ttxmarkwash: no problem pushing multiple times21:23
ttxmarkwash: the only thing the sync doesn't do is removing sessions if you suppress some21:24
*** diogogmt has quit IRC21:24
ttxOK, so if you want to ask for small adjustments so that you can avoid being double-booked, now is a good time to ask21:24
dolphm_we just discovered this morning that the 'security' track got scheduled on the same day as the keystone track, which presents some conflicts... any chance we can move anything around?21:24
ttxdolphm_: it's quite tricky at this point21:25
markwashI don't know of any reason why Glance is married to Wednesday21:25
markwashbut it wouldn't be the first important thing I just don't know about21:25
jd__yeah I already sent a mail to move a nova and quantum session, but I'm under the impression that russellb and markmcclain aren't around?21:26
markmcclainI'm here21:26
russellbi'm here21:26
russellbbeen on a plane all day, so haven't seen the mail21:26
jd__wrong impression :)21:26
jd__http://openstacksummitapril2013.sched.org/event/c44c71996bf04d28d8eb926031312974#.UWPcc5BzTf0 and http://openstacksummitapril2013.sched.org/event/dd227871952ae6a572658d16d8272f7c#.UWPcdJBzTf021:27
jd__and both are about Ceilometer21:27
jd__which is great, but if one could be moved so us Ceilometer folks can participates in both that'd be awesome21:27
russellbseems reasonable21:27
ttxdolphm_: to minimize changes we would have to swap two topics, and Thursday is the only one with 9 slots21:27
jd__ttx: btw do you happen to know who handles the scheduling of talks etc?21:28
*** hyakuhei_ has joined #openstack-meeting21:28
dolphm_ttx: understandable21:28
*** tong|2 has quit IRC21:28
*** toanster_ has joined #openstack-meeting21:28
ttxand Swift and Heat need to happen "not on Thursday"'21:28
ttxjd__: each conference track has its own group of people21:29
dolphm_there's at least 4 'security' sessions where it would make sense to have a strong keystone-core presence in attendance21:29
*** llu_linux has joined #openstack-meeting21:29
ttxhyakuhei_ is the lead for the security track21:30
russellbmarkmcclain: i'll move the nova+ceilometer one21:30
ttxi don't think he has the option to move any of it on another day now21:30
*** markmcclain has quit IRC21:30
*** rnirmal has quit IRC21:31
*** notmyname_ has joined #openstack-meeting21:32
ttxdolphm_: no, I don't really see a good solution for the issue at this point. one or two weeks ago we could probably have tried something, but now that everything was scheduled and published...21:32
*** _cerberu` has joined #openstack-meeting21:32
dolphm_it's not critical, we'll try to work around it... sorry we didn't notice sooner :(21:32
jd__thanks russellb21:32
*** markmcclain has joined #openstack-meeting21:33
ttxdolphm_: you can still watch the presentations videos...21:33
russellbjd__: markmcclain shold be all set now21:33
*** llu has quit IRC21:33
*** shang has quit IRC21:33
*** hyakuhei has quit IRC21:33
*** toanster has quit IRC21:33
*** notmyname has quit IRC21:33
*** _cerberus_ has quit IRC21:33
*** notmyname_ is now known as notmyname21:33
ttxanything else ?21:34
jd__russellb: thanks!21:34
russellbnp21:35
markmcclainrussellb: cool21:35
*** dolphm_ has quit IRC21:35
ttxOK, so if you need further adjustments you can just contact the topic lead so that he moves things around21:36
ttxuse with caution, as the move is likely to piss off someone else21:36
ttxand remember that there is no way to please everyone21:37
ttxanyone has anything else to add ?21:37
ttxquestions about the summit ?21:37
*** john5223 has quit IRC21:38
*** _cerberu` is now known as _cerberus_21:38
* russellb is excited to see you all21:38
*** markmcclain_ has joined #openstack-meeting21:38
*** shang has joined #openstack-meeting21:39
*** dolphm has joined #openstack-meeting21:39
ttxI guess no questions21:40
ttxwell, you know where to ask if you have some21:40
ttx#endmeeting21:40
*** adalbas has quit IRC21:40
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"21:40
openstackMeeting ended Tue Apr  9 21:40:28 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-04-09-21.02.html21:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-04-09-21.02.txt21:40
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-04-09-21.02.log.html21:40
*** Vek has left #openstack-meeting21:40
*** colinmcnamara has quit IRC21:41
*** mkollaro has quit IRC21:41
*** davidkranz_ is now known as davidkranz21:42
*** asalkeld has quit IRC21:42
*** turul_ has quit IRC21:42
*** markmcclain_ has quit IRC21:42
*** asalkeld has joined #openstack-meeting21:43
*** pcm_ has quit IRC21:44
*** markvan_ has joined #openstack-meeting21:45
*** sacharya has quit IRC21:45
*** reed has joined #openstack-meeting21:45
*** rmohan has quit IRC21:46
*** markwash has quit IRC21:46
*** rmohan has joined #openstack-meeting21:46
*** markvan has quit IRC21:48
*** markvan_ is now known as markvan21:48
*** rmohan has quit IRC21:48
*** rmohan has joined #openstack-meeting21:48
*** dwaite has quit IRC21:50
*** nati_ueno has joined #openstack-meeting21:51
*** dolphm has quit IRC21:51
*** lbragstad has quit IRC21:53
*** kspear has joined #openstack-meeting21:54
*** sirushti has quit IRC21:54
*** beagles_brb is now known as beagles21:56
*** colinmcnamara has joined #openstack-meeting21:57
*** salv-orlando has quit IRC21:58
*** danwent has quit IRC22:00
*** Mandell has quit IRC22:01
gabrielhurley#startmeeting horizon22:01
openstackMeeting started Tue Apr  9 22:01:27 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** openstack changes topic to " (Meeting topic: horizon)"22:01
openstackThe meeting name has been set to 'horizon'22:01
gabrielhurleyhello horizon peoples!22:01
jpichHello!22:01
david-lylehello22:01
gabrielhurley#topic general announcements22:02
*** openstack changes topic to "general announcements (Meeting topic: horizon)"22:02
gabrielhurleyGrizzly was released! Congratulations everyone!22:02
kspearhowdy22:02
kspearwoo!22:02
*** russellb has quit IRC22:02
gabrielhurleyIn other news the Horizon track for the summit is scheduled all throughout Tuesday next week. I look forward to seeing many of you there. :-)22:03
gabrielhurley#info no horizon project meeting on IRC next week. come to Portland. ;-)22:03
*** carlp-away is now known as carlp22:03
gabrielhurleyI'm very excited to talk about things like the Keystone v3 API/domains, and integrating Heat and Ceilometer. Should be great stuff.22:04
jpichVery sad I'll be missing the keystone v3 one, take good notes people :-)22:04
gabrielhurleyare you double-booked during that slot?22:04
*** ryanpetr_ has quit IRC22:04
jpichgabrielhurley: I'm co-giving the talk about internships at the same time22:05
gabrielhurleyah, gotcha22:05
gabrielhurleyI was trying to avoid obvious conflicts between quantum session + other quantum talks, etc.22:05
gabrielhurleydidn't know about that one22:06
jpichI thought I sent you an email about it last week22:06
jpichThat's why etherpad are there anyway :)22:06
jpichvkmc is presenting too22:06
gabrielhurleyah, yes, you did send me that, but the short version is that switching sessions around is really painful22:07
gabrielhurleyif you followed the Project Status meeting that happens the hour before this one, you'll know what I mean22:07
jpichFair enough22:08
jpichI'll catch up the logs for the project meeting22:08
gabrielhurleyI may look at whether it makes sense to try and flip something, but I can't promise anything22:08
gabrielhurley*flip something within the Horizon slots22:08
*** apevec has left #openstack-meeting22:08
gabrielhurleyanyhow, summit next week. good times!22:08
jpichYeah it's so close to the summit now, I understand22:08
gabrielhurleyI honestly don't think I have anything else on my agenda for this meeting.22:09
*** salv-orlando has joined #openstack-meeting22:09
gabrielhurley#topic open discussion22:09
*** openstack changes topic to "open discussion (Meeting topic: horizon)"22:09
*** vipul is now known as vipul|away22:09
gabrielhurleyanybody else want the floor?22:09
gabrielhurleywell exellent22:11
gabrielhurleyI will never compain about short meetings22:11
gabrielhurleysee y'all next week!22:12
gabrielhurley#endmeeting22:12
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:12
openstackMeeting ended Tue Apr  9 22:12:22 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:12
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-04-09-22.01.html22:12
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-04-09-22.01.txt22:12
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-04-09-22.01.log.html22:12
*** markmc has left #openstack-meeting22:12
*** markvan has quit IRC22:12
kspearbye, see you next week!22:12
jpichyep, bye everyone22:13
*** gabrielhurley has quit IRC22:15
*** jpich has quit IRC22:17
*** david-lyle has left #openstack-meeting22:18
*** colinmcnamara has quit IRC22:21
*** kspear has quit IRC22:22
*** mtreinish has quit IRC22:23
*** ijw has quit IRC22:26
*** Gordonz has quit IRC22:28
*** colinmcnamara has joined #openstack-meeting22:29
*** woodspa has quit IRC22:30
*** ivasev has quit IRC22:33
*** flaper87 has quit IRC22:35
*** ijw has joined #openstack-meeting22:38
*** beagles has quit IRC22:40
*** ewindisch has quit IRC22:41
*** rmohan has quit IRC22:47
*** rmohan has joined #openstack-meeting22:48
*** lillie has quit IRC22:48
*** lillie has joined #openstack-meeting22:49
*** lillie has joined #openstack-meeting22:49
*** markwash has joined #openstack-meeting22:50
*** lillie has joined #openstack-meeting22:50
*** lillie- has joined #openstack-meeting22:51
*** esker has quit IRC22:51
*** fnaval has quit IRC22:55
*** afazekas has quit IRC22:58
*** reed has quit IRC23:00
*** lloydde has quit IRC23:00
*** dwcramer has quit IRC23:00
*** dolphm has joined #openstack-meeting23:02
*** lloydde has joined #openstack-meeting23:04
*** colinmcnamara has quit IRC23:04
*** asalkeld has quit IRC23:06
*** dolphm has quit IRC23:06
*** koolhead17 has quit IRC23:07
*** asalkeld has joined #openstack-meeting23:07
*** colinmcnamara has joined #openstack-meeting23:09
*** salv-orlando has quit IRC23:11
*** sacharya has joined #openstack-meeting23:11
*** ewindisch has joined #openstack-meeting23:11
*** sacharya has quit IRC23:11
*** otherwiseguy has quit IRC23:11
*** ewindisch has quit IRC23:15
*** salv-orlando has joined #openstack-meeting23:16
*** eharney has quit IRC23:16
*** spzala has quit IRC23:16
*** colinmcnamara has quit IRC23:24
*** colinmcnamara has joined #openstack-meeting23:28
*** ijw has quit IRC23:32
*** danwent has joined #openstack-meeting23:33
*** gongysh has joined #openstack-meeting23:40
*** markmcclain has quit IRC23:44
*** vipul|away is now known as vipul23:47
*** armax has left #openstack-meeting23:55
*** garyTh has quit IRC23:56
*** lloydde has quit IRC23:56

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