Tuesday, 2011-11-29

*** zul has joined #openstack-meeting00:02
*** mattray has quit IRC00:13
*** sleepsonthefloo has quit IRC00:25
*** reed_ has quit IRC00:42
*** zns has joined #openstack-meeting00:50
*** reed has joined #openstack-meeting00:55
*** AlanClark has quit IRC00:57
*** anotherjesse has quit IRC01:12
*** dendro-afk is now known as dendrobates01:17
*** dendrobates has joined #openstack-meeting01:17
*** anotherjesse has joined #openstack-meeting01:18
*** donaldngo_hp has quit IRC01:24
*** anotherjesse has quit IRC01:25
*** vladimir3p has quit IRC01:47
*** jdurgin has quit IRC01:55
*** novas0x2a|laptop has quit IRC02:07
*** lloydde has quit IRC02:11
*** bengrue has quit IRC02:13
*** adjohn has quit IRC02:25
*** reed has quit IRC02:26
*** vladimir3p has joined #openstack-meeting03:16
*** jog0 has quit IRC03:19
*** adjohn has joined #openstack-meeting03:36
*** adjohn has quit IRC03:40
*** rnirmal has joined #openstack-meeting03:49
*** donaldngo_hp has joined #openstack-meeting04:27
*** adjohn has joined #openstack-meeting04:27
*** sleepsonthefloo has joined #openstack-meeting05:13
*** vladimir3p has quit IRC05:24
*** reed has joined #openstack-meeting05:25
*** reed has quit IRC05:26
*** rnirmal has quit IRC05:55
*** adjohn has quit IRC06:07
*** adjohn has joined #openstack-meeting06:07
*** beekhof has quit IRC06:19
*** jakedahn has quit IRC06:24
*** jakedahn has joined #openstack-meeting06:29
*** adjohn has quit IRC06:48
*** jog0 has joined #openstack-meeting06:50
*** anotherjesse has joined #openstack-meeting06:59
*** jakedahn has quit IRC07:01
*** jakedahn has joined #openstack-meeting07:04
*** anotherjesse has quit IRC07:07
*** zns has quit IRC07:17
*** vladimir3p has joined #openstack-meeting07:21
*** vladimir3p has quit IRC07:26
*** jog0 has quit IRC07:30
*** jakedahn has quit IRC09:45
*** darraghb has joined #openstack-meeting09:47
*** donaldngo_hp has quit IRC13:04
*** markvoelker has joined #openstack-meeting13:34
*** lloydde has joined #openstack-meeting14:24
*** pringles_ has quit IRC14:30
*** pringles_ has joined #openstack-meeting14:36
*** zns has joined #openstack-meeting14:40
*** jamespage has joined #openstack-meeting14:58
Davieyzul: ?15:00
zulsorry here15:00
openstackMeeting started Tue Nov 29 15:01:01 2011 UTC.  The chair is zul. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.15:01
zulwelcome to the the nova ec2 api team meeting15:01
zul1) Discuss ec2 api issues15:01
zul2) Open Bugs15:01
zul3) Openfloor15:01
zul#topic Discuss ec2 api issues15:02
*** openstack changes topic to "Discuss ec2 api issues"15:02
zulso i have been running the aws-cloud testsuite and trying to figure out how to report issues.15:02
zulIt seems to me that tests are not intuiative enough so I was thinking of writing a patch to make the tests a bit more informatiive15:03
zulSo that is on my todo list.15:03
zulLast week I didnt really make any progress on the ec2 bug list because i got distracted with work related stuff15:04
Davieysounds good15:04
zulAlso there has been several gerrit review for ec2 related problems15:04
zulmwhooker has submitted a gerrit review branch for aws compatiabblity tests15:05
zulits at: https://review.openstack.org/186015:05
zulhey medberry15:05
zulPlease help review it15:05
zulanyone else have any comments15:06
Davieyzul: add an action?15:06
zuloh i forgot one thing smoser pointed me to a branch that might help with speeding up the ec2 metadata server15:06
zulDaviey: so the action points would be:15:07
zul#action review https://review.openstack.org/186015:07
zul#action review aws-cloud testsuite to make it better15:07
Davieyzul: How complete is the testsuite?15:08
DavieyAre we testing S3?15:08
zulDaviey: the aws-cloud one or the one in the gerrit review15:08
zulthe aws-cloud tests both ec2  and s315:08
zulalthough i havent used it to test s315:09
zuli would like to see it act like the nova testsuite but it just prints a summary at the end so I think I might be missing something15:10
zulso any other comments?15:10
zulok then15:11
zul#topic Open Bugs15:11
*** openstack changes topic to "Open Bugs"15:11
zulso we still have a lot of open bugs that are ec2 specific:15:11
zulan example of a new one is:15:12
uvirtbotLaunchpad bug 897164 in nova "neither EC2 api nor openstack API expose the hostname" [Undecided,New]15:12
zulso right now they are just sitting there until someone actually does something with them, I think as a group we should start attacking them and get essex to support ec2 better15:13
zulheh ok15:14
medberryzul, are you just grepping for EC2 in the bug name or are they being tagged somehow?15:14
zulmedberry: they are tagged ec215:14
* medberry sees the tag...15:15
*** coli has joined #openstack-meeting15:15
zuli try to go through the bug list once a week usually before the meeitng and tag any bugs that I might be missing15:15
zuland hopefully its a frenzy to fix the ec2 bugs ;)15:15
zulwhich right now it is not15:15
zulso developers who need to use ec2 need to get excited about fixing them15:16
zulhint hint15:16
* zul sees tumbleweeds run on by15:17
zulso with that15:18
* ttx wonders who actually does15:18
zul#topic Open Floor15:18
*** openstack changes topic to "Open Floor"15:18
medberryttx, I see a lot of tumbleweeds roll by....15:18
ttxzul: you might need to actively engage people that work with EC2 api and encourage them to join this meeting :)15:18
zulttx: agreed15:19
DavieyI suspect a vast minoirty of those that care about ec2 actually know, or can attend this meeting15:19
zulmwhudson was at the first meeting at least15:19
zulmaybe change the meeting time?15:19
DavieyI suspect awarness15:19
medberryI think soliciting and advertising15:19
ttxzul: first, collect the names of people interested15:19
medberry(time slot isn't especially bad)15:20
ttx(or good)15:20
medberryzul, I'll mention it to justinlw15:20
* Daviey glares at medberry for soliciting!15:20
zuli suspect alot of the people who are interested in the ec2 api are on the west coast and this wouldnt be a good time for them15:20
* medberry puts on polarized glasses and hires a solicitor.15:21
Davieyzul: No, i think it requires a blog post and more visability on the mailing list.15:21
zulgood idea15:22
zul#action zul to write a blog post about the team meeting15:22
zulany other comments?15:23
medberrya "where's chuck" meme in the #openstack-meeting picture with #startmeeting EC2 API on Google + couldn't hurt....15:23
zulthankfully that is dead i think ;)15:23
zulif no one has anything else then i think thats it15:24
zulat least i have nothing else15:24
Davieyworks for me15:25
zulthanks for coming15:25
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"15:25
openstackMeeting ended Tue Nov 29 15:25:33 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-15.01.html15:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-15.01.txt15:25
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-15.01.log.html15:25
*** rnirmal has joined #openstack-meeting15:50
*** hggdh has quit IRC16:00
*** adjohn has joined #openstack-meeting16:01
*** zns has quit IRC16:03
*** zns has joined #openstack-meeting16:03
*** zns has quit IRC16:13
*** vladimir3p has joined #openstack-meeting16:18
*** zns has joined #openstack-meeting16:20
*** vladimir3p has quit IRC16:23
*** hggdh has joined #openstack-meeting16:30
*** vladimir3p has joined #openstack-meeting16:34
*** vladimir3p has quit IRC16:38
*** reed has joined #openstack-meeting16:41
*** adiantum has joined #openstack-meeting16:51
*** zns has quit IRC16:58
*** zns has joined #openstack-meeting17:02
*** vladimir3p has joined #openstack-meeting17:05
*** zns1 has joined #openstack-meeting17:08
*** zns has quit IRC17:09
*** zns1 has quit IRC17:10
*** zns has joined #openstack-meeting17:12
*** vishy has left #openstack-meeting17:13
*** vishy has joined #openstack-meeting17:14
*** jakedahn has joined #openstack-meeting17:15
*** jakedahn has quit IRC17:15
*** jakedahn has joined #openstack-meeting17:15
*** jakedahn has quit IRC17:23
*** jakedahn has joined #openstack-meeting17:23
*** jdurgin has joined #openstack-meeting17:42
*** oubiwann has joined #openstack-meeting17:45
*** gyee has joined #openstack-meeting17:47
*** anotherjesse has joined #openstack-meeting17:51
zns#startmeeting Keystone Team Meeting18:00
openstackMeeting started Tue Nov 29 18:00:59 2011 UTC.  The chair is zns. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.18:01
*** openstack changes topic to " (Meeting topic: Keystone Team Meeting)"18:01
znsHi There! Anyone here for the Keystone meeting?18:02
gyeeI am. My first keystone meeting. :)18:03
*** zns has quit IRC18:03
*** zns has joined #openstack-meeting18:03
znsGot disconnected. ANyone here?18:04
*** zns_ has joined #openstack-meeting18:05
znsgyee: hi - are you working with/on Keystone?18:06
znsgreat. Looks like we're the only ones here now. I'm going to report some progress for the record, but let me know if you have specific questions?18:07
zns#topic Status and Progress18:08
*** openstack changes topic to "Status and Progress (Meeting topic: Keystone Team Meeting)"18:08
*** dprince has joined #openstack-meeting18:08
znsDocumentation updates have been uploaded to http://keystone.openstack.org/ and http://docs.openstack.org/trunk/openstack-identity/admin/content/18:09
znsI'd like to call out a some docs that have been asked for:18:09
znshttp://keystone.openstack.org/endpoints.html on Endpoints and Endpoint Templates18:10
znshttp://docs.openstack.org/trunk/openstack-identity/admin/content/example-flows.html example sequence diagrams explaining client and service interaction with Keystone.18:10
znshttp://keystone.openstack.org/middleware_architecture.html and http://keystone.openstack.org/configuringservices.html on middleware and service configuration and design.18:11
znsWe've also had 8 code merges and a number of reviews go in to address bugs and updates.18:13
znsWe continue to focus on stabilizing and documenting Keystone in this release cycle.18:14
zns#topic Open Discussion18:14
*** openstack changes topic to "Open Discussion (Meeting topic: Keystone Team Meeting)"18:15
znsANy questions?18:15
gyeezns: I'll be working on 890411. Any specific procedures I need to be aware of?18:15
gyeeIt may affect documentation as well.18:16
znsDo you have a blueprint or comment in the bug for your solution?18:17
gyeeNot yet. I'll be proposing a solution shortly, most likely today.18:17
znsYou can submit documentation updates with your code review (the RST docs are in the same repo).18:18
gyeeWill do. Thanks!18:18
znsGreat. That's all you need seeing as this will probably require an extension or API contract change18:18
znsThe other thing is if you will be including any database schema changes let us know - we're using sqlalchemy_migrate and know that schema changes have been a challenge for the community who have production deploymewnts of pre-released code.18:19
gyeeSure. I am not anticipating any schema changes for this one.18:20
znsgyee: ping me on IRC when you have your proposal and I'll take a look at it today.18:21
gyeeWill do.18:21
znsOK. Closing the meeting unless anyone has anything else?18:21
znsgyee: thanks!18:21
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"18:21
openstackMeeting ended Tue Nov 29 18:21:55 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:21
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-18.00.html18:21
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-18.00.txt18:21
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-18.00.log.html18:22
*** zns_ has quit IRC18:22
*** adjohn has quit IRC18:25
*** vladimir3p has quit IRC18:25
*** deshantm_laptop has joined #openstack-meeting18:34
*** jog0 has joined #openstack-meeting18:35
*** darraghb has quit IRC18:35
*** oubiwann1 has joined #openstack-meeting18:36
*** oubiwann has quit IRC18:39
*** GheRivero has quit IRC18:51
*** dolphm has joined #openstack-meeting19:00
*** dprince has quit IRC19:05
*** ArseneRei has joined #openstack-meeting19:08
*** vladimir3p has joined #openstack-meeting19:09
*** bengrue has joined #openstack-meeting19:10
*** jk0 has joined #openstack-meeting19:27
*** novas0x2a|laptop has joined #openstack-meeting19:34
*** danwent has joined #openstack-meeting19:47
*** bcwaldon has joined #openstack-meeting19:48
*** yogirackspace has joined #openstack-meeting19:53
*** bencherian has joined #openstack-meeting19:56
*** novas0x2a|laptop has quit IRC19:57
*** joesavak has joined #openstack-meeting19:59
dolphmkeystone time?20:00
* joesavak does the keystone dance20:00
dolphmassuming i'm reading UTC correctly this week20:00
joesavaki'll double check20:00
*** GheRivero has joined #openstack-meeting20:00
anotherjesseI see pbb20:00
KiallIts 20:00 UTC at the mo20:00
anotherjesseon my calendar - but not sure if it came from the ical feed or not - http://wiki.openstack.org/Meetings20:00
anotherjessethink I'm going to delete all my meetings and re-click that link20:01
ttxnope, that's PPB time20:01
znsI did Keystone at noon…. this is PPB time?20:01
znsnoon CST20:01
dolphmdammit lol20:01
ttx20:00 UTC20:01
dolphmoh well :P20:01
mtaylorwow. it's AMAZING how bad we all are at this post-daylight savings time change stuff20:01
ttxdolphm: I suggest you use the Google Calendar. Or http://www.timeanddate.com/worldclock/fixedtime.html?iso=20111202T2120:02
ttxmtaylor: not "all".20:02
*** johnpur has joined #openstack-meeting20:02
notmynameis there a ppb meeting?20:02
reedgoogle calendar is the best, don't copy the event, just import the feed... it worked for me on Evolution20:02
mtaylorttx: collectively, I think we're all bad - individually, some of you are better than others of us20:02
dolphmdone -- thanks20:03
mtaylorreed: yup. problem is when I remember meeting times in my head so I don't actually look at my calendar for them. fail20:03
reedit's all about the tools... they all suck, people are good20:03
ttxmtaylor: let's say being out of US timezones forces you to think about time in a very relative way20:03
* mtaylor punches self in the face20:03
vishydon't know if there is anything on the agenda for the peeb20:03
* vishy waits for jbryce20:03
ttxwe don't have anything on the agenda, let's wait for jbryce who will call it off20:03
ttxor on20:03
reedttx, mtaylor doesn't live in one timezone20:04
ttxreed: so he has no excuse20:04
reedhe transcends time20:04
reedand has no excuse :)20:04
* mtaylor memorized meeting times in all of the timezones he's in, and knows how to switch the time in his head20:04
mtaylorbut then meeting times changed, and apparently my brain is write-once20:04
* ttx cheats and uses google calendar.20:05
sorenttx: Knowing your weaknesses is a good thing.20:05
ttxalso, translating UTC to CET is not very difficult.20:05
sorenttx: if you have any, of course :)20:06
*** adiantum has quit IRC20:06
reedsince we're all hanging here, all PTL please check this thread and make sure that all requirements for the Q&A site are there... I'll move on with software selection based on them https://lists.launchpad.net/openstack/msg05715.html20:06
anotherjessereed: would this deprecate the forum?20:08
mtaylorthere's a forum?20:08
znsreed: How can we start an investigation into something like http://feedback.rackspacecloud.com/ for OpenStack to rank features?20:08
notmynamemtaylor: ya, remember that huge argument we all had about it (and then never used...)20:08
anotherjessemtaylor: http://forums.openstack.org/20:08
reedanotherjesse, we'll see... why would you want to deprecate?20:08
jk0spreading resources too thin20:09
reedzns, I hear you ... one thing at the time :)20:09
anotherjessereed: they provide very similar usecases20:09
znsreed: :-)20:09
mtaylornotmyname: I must have blocked that from my memory... I abhor web forums20:10
reedanotherjesse, indeed, but I don't want anybody to feel offended... we may decide that forum is the best way to proceed. At this point I'm not excluding anything20:10
notmynamemtaylor: so when is your vcsversion tool going to be ready?20:10
*** dprince has joined #openstack-meeting20:10
mtaylornotmyname: hopefully this week20:10
anotherjessereed: I think those enthusiastic about the forums preferred to have a q&a site20:11
notmynamevishy: anotherjesse: I'll be in SF next week. I'm planning on being at the RAX office for some amount of time20:11
mtaylornotmyname: I need to get translations imports done first, as well as a bunch of blueprint writeups20:11
ttxnotmyname: we had an argument about it because we didn't want to use it :)20:12
mtaylornotmyname: but then I want to get vcsversion finished20:12
jk0or have to support it20:12
ttxjk0: I think we proved we were right20:12
jk0ttx: that's why I was surprised to see the Q/A discussion brought up again so soon20:12
ttxsomeone called jbryce ?20:12
pvojk0: ttx: i'm with you both. I didn't think it was really needed20:13
ttxjk0: reed hates forums, he is with us20:13
reedI don't hate anything :)20:13
ttxpvo: they were supposed to be so successful they would prove all devs wrong.20:13
ttxreed: yes you do20:13
ttxreed: you hate them even more than I do !20:14
reedttx, your words, not mine :)20:14
pvottx: I'm waiting with baited breath20:14
ttxok, I think we can postpone this PPB meeting, in absence of chair, agenda and quorum.20:15
* mtaylor tried to work on a project a few months ago that _only_ had web forums - no mailing list, no irc channel. just a web forum20:15
mtaylorit was CRAZY20:15
* mtaylor gave up20:15
pvoits 15 minutes…we doing college rules?20:16
ttxGeneral team meeting in 45min20:16
*** masumotok has joined #openstack-meeting20:16
notmynamepvo: does that make jbryce a full professor?20:16
pvoguest lecturer ?20:17
anotherjessemtaylor: are you referring to cloudfoundry?20:17
Davieynotmyname: If it does, that makes you in detention.20:17
pvottx: see you in a bit20:17
mtayloranotherjesse: no, it's a thing called openFrameworks - a c++ framework for doing multimedia programming20:17
*** jakedahn has quit IRC20:18
*** dragondm has joined #openstack-meeting20:20
*** Kiall has quit IRC20:28
*** Kiall has joined #openstack-meeting20:31
*** jsavak has joined #openstack-meeting20:31
*** markmc has joined #openstack-meeting20:34
*** joesavak has quit IRC20:34
*** johnpur has quit IRC20:43
*** coli has quit IRC20:44
*** Ravikumar_hp has joined #openstack-meeting20:47
*** Ravikumar_hp has quit IRC20:47
*** Ravikumar_hp has joined #openstack-meeting20:47
*** wwkeyboard has joined #openstack-meeting20:50
*** Vek has joined #openstack-meeting20:59
bcwaldonpvo, come on21:00
ttxzns, notmyname, jaypipes, devcamcar: around ?21:00
pvoi'm angled today21:00
*** mjfork has joined #openstack-meeting21:00
bcwaldonits a salute21:00
dolphmstanding in for zns21:01
jaypipesttx: o/21:01
ttxdolphm: ack21:01
dolphmttx: ?21:01
ttxdolphm: that was an acknowledgement21:01
ttxnotmyname, devcamcar ?21:02
dolphmdoesn't syn come first?21:02
* Vek debates whether to initiate backoff...21:02
ttxVek: I won't reply to syn broadcast.21:02
Vekhehe :)21:03
ttxok, let's start21:03
openstackMeeting started Tue Nov 29 21:03:23 2011 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.21:03
ttxOur agenda for today: http://wiki.openstack.org/Meetings/TeamMeeting21:03
ttxNote that we'll discuss the new core repositories for client projects after the project updates, so stay around after your project topic is done...21:03
ttx#topic Actions from previous meeting(s)21:04
*** openstack changes topic to "Actions from previous meeting(s)"21:04
ttx* mtaylor devcamcar to discuss and converge to a common view on the need to split repos for horizon (or not)21:04
ttxmtaylor: Did you discuss that yet ?21:04
*** somik has joined #openstack-meeting21:04
ttx* Keystone devs to help with bug 89144221:04
uvirtbotLaunchpad bug 891442 in horizon "renaming of api_key causes several unhandled exceptions" [Critical,Confirmed] https://launchpad.net/bugs/89144221:04
ttxdolphm: not sure if your help is still needed there ?21:05
*** edgarmagana has joined #openstack-meeting21:05
dolphmttx: don't believe so21:06
ttxHmm, let's talk back about it during the horizon topic, hopefully we'll have devcamcar in by then21:06
ttx#topic Keystone status21:06
*** openstack changes topic to "Keystone status"21:06
mtaylorhi ttx21:06
ttxmtaylor: ah21:06
*** adiantum has joined #openstack-meeting21:06
ttxmtaylor: let's discuss that at the split repo topic21:07
mtaylorttx: great21:07
ttx#link https://launchpad.net/keystone/+milestone/essex-221:07
ttxdolphm: is the status on there current ?21:07
dolphmkeystone updates -- we're focusing mostly on open bugs (yay!), doc improvements (yay!) and finally paying more attention to integration efforts21:07
notmynamettx: here21:08
dolphmttx: yes, those statii (-es? lol) look accurate?21:08
ttxSo service-endpoint-location endpoint-identifiers are not started yet ?21:08
*** KyleM1 has joined #openstack-meeting21:08
*** ArseneRei has left #openstack-meeting21:09
dolphmI'm not aware of any code published for locations, and we're still discussing endpoint identifiers21:09
ttx(Remember the E2 changes need to be proposed and merged by December 13.)21:09
ttxLooking at the general essex roadmap, there is a blueprint without a milestone target:21:09
ttxdolphm: Should that be targeted to essex-3 ?21:09
ttx(since that's you last feature milestone, iirc)21:10
*** dprince has quit IRC21:10
dolphmttx: endpoint-identifiers probably should be... in exchange, we may be addressing https://blueprints.launchpad.net/keystone/+spec/portable-identifiers sooner rather than later21:10
dolphm(as the endpoint-identifiers mentions)21:10
*** liemmn has joined #openstack-meeting21:11
ttxdolphm: should keystone-domains be targeted to E3 ?21:11
ttxor you don't know when is HP committed to it ?21:12
jsavakttx: (hi) - that's a HP question21:12
*** mcohen has joined #openstack-meeting21:12
dolphmyeah, i don't have any visibility on keystone-domains myself21:12
ttxok, will try to break the bug IRC wall and get more status updates21:12
ttxdolphm: Anything else ?21:12
jsavakalso I'm wondering if  https://blueprints.launchpad.net/keystone/+spec/endpoint-identifiers and https://blueprints.launchpad.net/keystone/+spec/portable-identifiers can be merged21:13
ttxjsavak: noted21:13
ttxIn other news, we cut a 2011.3.1 "Diablo+" tarball last week:21:13
*** edgarmagana has quit IRC21:13
ttxQuestions for Keystone ?21:13
dolphmyes, i have an open question for keystone consumers / CI peeps -- we'd like to directly support a CI effort in the long run... is openstack-integration-tests the best place to do that?21:14
*** somik has quit IRC21:14
jaypipesdolphm: yep21:14
jaypipesdolphm: it's handled the same as all core projects... gerrit-ified and all.21:15
dolphmis it the *only* such effort we should support?21:15
reed#info <dolphm> keystone updates -- we're focusing mostly on open bugs (yay!), doc improvements (yay!) and finally paying more attention to integration efforts21:15
jaypipesdolphm: yes.21:15
*** troytoman-away is now known as troytoman21:15
dolphmcool -- will do21:15
jaypipesdolphm: or rather, the only one that the QA team is focusing on.21:15
*** jmckenty has joined #openstack-meeting21:15
dolphmfair enough21:15
ttxOther questions for Keystone ?21:15
jaypipesdolphm: awesome, thx21:16
dolphmi'll be joining those meetings then21:16
ttx#topic Swift status21:16
*** openstack changes topic to "Swift status"21:16
ttxnotmyname: o/21:16
notmynameswift 1.4.4 was released last thursday21:16
reed#info  swift 1.4.4 was released last thursday21:17
notmynamewe recommend you upgrade21:17
ttxnotmyname: do you agree that the next version will be called 1.4.5 ?21:17
notmynamettx: I have no reason to think otherwise right now21:17
ttxNo ETA yet, I suspect ?21:17
notmynamettx: of course, that can quickly get in to other topics :-)21:17
ttx#action ttx to create swift/1.4.5 milestone, no ETA yet21:17
notmynameno ETA for the next version of swift yet21:17
ttxnotmyname: Anything else ?21:18
notmynameI'm currently working on getting better visibility into progress and tasks and such21:18
notmynameI'l be in the bay area next week. come to the meetup to talk swift21:18
ttxQuestions on Swift ?21:18
reednotmyname, visibility into progress? can you elaborate?21:18
notmynamereed: better coordination with internal project management tools and expternal, openstack ones.21:19
reedcool. thanks21:19
notmynamereed: and better visibility on what's being worked on and planned21:19
notmynamereed: so it's easier to coordinate between companies21:20
ttx#topic Glance status21:20
*** openstack changes topic to "Glance status"21:20
reed#info <notmyname> I'm currently working on getting better visibility into progress and tasks and such [to the community]21:20
ttxjaypipes: yo21:20
jaypipesttx: oy21:20
ttx#link https://launchpad.net/glance/+milestone/essex-221:20
ttxProgress on features looks good...21:20
jaypipesttx: meh. got a bunch of reviews currently in progress.21:21
ttxLooking at the general essex plan at: https://blueprints.launchpad.net/glance/essex21:21
ttxYou still have glance-xml and gzip-compression in plan, with no milestone...21:21
jaypipesttx: ran into a bunch of issues with our Keystone functional tests that required fixes to Keystone.21:21
ttxjaypipes: Should I unset the series goal for them ? Or do you have someone committed to do them ?21:21
jaypipesttx: you can unset those. sorry for not doing that earlier.21:21
*** adiantum has quit IRC21:22
ttx#action ttx to unset glance-xml and gzip-compression21:22
*** dprince has joined #openstack-meeting21:22
ttxjaypipes: "required", so it's ok now ?21:22
dolphmjaypipes: thanks for those :)21:22
* ttx likes the dependency tree at https://blueprints.launchpad.net/glance/+spec/api-221:22
*** novas0x2a|laptop has joined #openstack-meeting21:23
ttxjaypipes: feeling confident that this tree can all be completed in E3 ?21:23
jaypipesdolphm: yeah, no worries. mostly just version skew.21:23
ttx(Lots of small blueprints, I suspect)21:23
jaypipesttx: no, it's going to be tough. I've been trying to get the third version of the 2.0 API proposal done. 90% there.21:23
jaypipesttx: everything depends on signoff on the 2.0 proposal.21:24
glencmy bad21:24
ttxjaypipes: so it may overflow on E4 ?21:24
jaypipesttx: perhaps, yes.21:25
jaypipesglenc: not your fault.21:25
ttxjaypipes: Anything else ?21:25
jaypipesttx: no, not right now. thx.21:25
glencjaypipes: but I do have some stuff I need to run by you - I'll contact you tomorrow21:25
jaypipesglenc: cool.21:25
ttxQuestions on Glance ?21:26
ttx#topic Nova status21:26
*** openstack changes topic to "Nova status"21:26
ttxvishy: yo21:26
ttx#link https://launchpad.net/nova/+milestone/essex-221:27
ttxProgress looks good in general21:27
vishyyes we need some reviews21:27
ttxRight, two essential blueprints look blocked in review:21:27
ttxnova-vm-state-management -> https://review.openstack.org/#change,169521:27
ttxnova-volume-snapshot-backup-api -> https://review.openstack.org/#change,120221:27
vishythe first is the big one21:27
vishythe second we are waiting on updates from the author21:27
* vishy wishes we had a WIP flag21:28
ttxmtaylor: ^ :)21:28
vishythe other stuff seems to be implemented/on track21:28
mtaylorvishy: yes! it's on the CI roadmap with high priority21:28
ttxvishy: on the general Essex plan, are you making progress with the subteams ?21:28
ttxOr do you need help in getting feedback from them ?21:29
mtaylorvishy: I will have the blueprint about it done today21:29
vishytitan team.  Anyone know how much more uuid related changes are needed?21:29
vishy* many21:29
vishyttx: I haven't received any feedback21:29
bcwaldoncoming to a close, very close to being done21:29
westmaasbcwaldon: next round don't need as many changes?21:30
ttxvishy: would going to thei21:30
vishyand not much is targeted to e-3 yet21:30
ttxr team meeting help ?21:30
bcwaldonwe're up around 40 branches at this point already in, with a few more left to do21:30
bcwaldonwestmaas: correct21:30
ttxvishy: or they don't have any ?21:30
vishyso maybe i should start threatening violence21:30
ttxif violence means "less features" i'm all for it21:30
vishyI've been attending meetings as I can21:31
vishyI just want the features actually targetted21:31
ttxI'm concerned about disk-configuration-parity (feature parity team / sleepsonthefloor)21:31
vishyand assigned21:31
*** somik has joined #openstack-meeting21:31
westmaasvishy: is the uuid story a problem?21:31
ttxand separate-nova-volumeapi (Nova API team, bcwaldon)21:31
vishywestmaas: no21:31
sorenI'm not sure it's going to scale to have the PTL to attend other's team meetings..21:31
vishysoren: cloning?21:32
sorenvishy: Clones still need to grow up. PEople always forget that.21:32
*** jrouault has joined #openstack-meeting21:32
vishysoren: well I would appreciate general updates occasionally21:32
vishysoren: but mostly if the subteam leads just stay on top of their blueprints21:32
vishythat would probably be enough21:32
sorenIt should be.21:33
sorenThat's my point :)21:33
vishyttx: what is your concern about those two?21:33
ttxvishy: they are marked essential, so I suppose they are extra-important for you21:33
ttxand they won't happen if nobody is committed to work on them21:33
vishythey are21:34
tr3buchetdidn't they figure out how to accelerate the growth rate of clones21:34
vishywhich means I will probably have to do them myself!21:34
ttxvishy: if teams don't produce anything and don't report up, they should be disbanded. Having them becomes a distraction21:34
vishyttx: true21:35
Vekor new leaders appointed.21:35
vishyttx: know there are things going on21:35
ttxVek: depends if the problem is leadership or membership21:35
vishyttx: they just haven't congealed into specific tasks21:35
ttxvishy: ok, will talk to you about that this week21:35
vishyttx: cool.  Open to suggestions21:35
vishymaybe we need a mandatory team-lead meeting?21:36
ttx#action ttx and vishy to discuss how to solve Nova's team structure21:36
ttxIn other news, https://blueprints.launchpad.net/nova/+spec/consolidate-testing-infrastructure is in the plan, without a milestone set21:36
tr3buchetvishy: that seems like a good idea21:36
ttxsoren, oubiwann: do you have a target milestone for that ?21:36
*** Tushar has joined #openstack-meeting21:36
sorenttx: When's the next milestone again?21:36
ttxDec 1521:36
vishysoren: ah yes I pinged you about that yesterday.21:36
sorenvishy: Yeah. I suck. I know :)21:36
vishysoren: i wanted to make sure you thought it was correct before I approved it21:36
vishyalthough apparently i already accepted for essex :)21:37
ttxvishy: could you approve/set prio ?21:37
sorenYes, I saw that too :)21:37
sorenI think E2 is doable.21:37
vishysoren: no qualms with approving it?21:37
ttxvishy: soren is in drivers so it's auto-approved to Essex21:37
* soren smells a trick questino21:37
sorenquestion, even.21:37
sorenttx: I didn't touch it!21:37
ttxvishy: he is supposed to know what he is doing21:38
vishysoren: no, just wanted to make sure it fits in with your testing refactor21:38
ttxyou didn't set the series goal to essex ?21:38
sorenI think it must have been vishy. It was approved when I first went and looked.21:38
vishyi might have done it21:38
ttxvishy: Anything else ?21:38
vishyyes I want to talk about ppas21:38
sorenYes, I think it definitely falls within the testing refactor.21:38
vishybut I don't know if i should save that until the end.21:38
ttx#action vishy to set E2/prio/approval on consolidate-testing-infrastructure21:39
*** lhrc has joined #openstack-meeting21:39
*** thingee1 has joined #openstack-meeting21:39
ttxvishy: save it, if it's general21:39
ttxQuestions on Nova ?21:39
mtaylorvishy: ping me when you start talking about that21:39
ttxdevcamcar: around now ?21:40
ttxskipping Horizon, we'll be back if devcamcar or someone else shows up to represent Horizon21:40
ttx#topic Status on new core repositories21:40
*** openstack changes topic to "Status on new core repositories"21:40
*** dprince has quit IRC21:41
ttxSo, for E2 we are introducing new repositories for several core projects21:41
ttxFor Nova for example we are adding novaclient as an additional release deliverable21:41
ttxI'd like to go over the list and get status, see if we are on track for that for E221:41
ttxmtaylor: For Nova, we have novaclient being added -- how is that going so far ?21:41
mtaylorttx: novaclient is in and good to go21:42
*** jmckenty has quit IRC21:42
ttxDo we have tarball CI jobs up yet ?21:42
ttxor just the repo ?21:42
mtaylorttx: it's gerrit-ified and cutting tarballs21:42
ttxWe'll probably need milestone-proposed jobs21:42
ttxI'll check that21:42
ttxFor Horizon, there was a proposal to split the django lib and the reference implementation, where are we with that ?21:43
mtaylorwe are not doing that at the moment21:43
mtaylorthere are workflow issues that need to be solved21:43
ttx#action ttx to check the need for MP jenkins jobs on novaclient21:43
*** lhrc is now known as mikeyp21:43
mtaylorI have a todo list item to present devcamcar with some options of how it could work21:43
ttxmtaylor: so we keep a single tarball for e2 ?21:43
mtaylorttx: yes.21:44
ttxmtaylor: ok, but it would be good to have the final form by E321:44
mtaylorttx: ok. noted21:44
ttxwhatever that is21:44
ttxmtaylor: Do we need client splits for other projects (Keystone, Swift, Glance) ?21:44
mtaylorwe need to pull python-keystoneclient in to the fold, split out quantum client and glance client, and I think we'll be in good shape21:44
ttxthose are still TODOs, right ?21:45
znsYes. Would like to do that for Keystone.21:45
troytomanmtaylor: we should get Melange set up right from the start21:45
ttxmtaylor: but on track for E2 ?21:45
mtaylorzns: is the 4P repo the one we should work on bringing in?21:45
mtaylortroytoman: ++21:45
mtaylorttx: glance is not21:45
mtaylorttx: I think we can get quantum, keystone and melange on track by E221:46
znsmtaylor: that's a good start. I've added Keystone code to novaclient, but we can start with 4P.21:46
ttxglance is... done ? or not on track ?21:46
mtaylorzns: cool. I'll try to arrange21:46
mtaylorttx: glance client is a little bit more integrated into glance, I need to chat with jaypipes about splitting strategy21:47
Vekglance client is still tightly attached to glance, afaik21:47
ttxmtaylor: ok, let's keep horizon and glance for E3 then21:47
ttxmtaylor: anything needed on swift side ?21:47
mtaylorttx: I think similar to glance- notmyname said it's doable, but not on the immediate todo list21:47
notmynamestep one, make a client library21:48
ttxany other remark on that topic ?21:48
*** dprince has joined #openstack-meeting21:48
ttx#topic Incubated projects and other Team reports21:48
*** openstack changes topic to "Incubated projects and other Team reports"21:48
ttxdanwent, troytoman: o/21:49
danwenti'll let troy go first :P21:49
ttxAnything interesting in Melange and Quantum land ?21:49
troytomanwe plan to have Melange moved into gerrit tomorrow afternoon21:49
troytomanotherwise, cleaning up docs and other items to make it more accessible21:49
anotherjesserelated to the cli extraction I've been talking to various folks about how to make the CLI tools work the same way - http://wiki.openstack.org/CLIAuth21:49
reed#info <troytoman> we plan to have Melange moved into gerrit tomorrow afternoon21:50
reed#info <anotherjesse> related to the cli extraction I've been talking to various folks about how to make the CLI tools work the same way - http://wiki.openstack.org/CLIAuth21:50
* Vek wonders whatever happened to his blueprint about auth21:50
*** salv-orlando has joined #openstack-meeting21:50
troytomannot much else to report at this point21:51
Vek(because getting auth to work the same way across all the tools was part of my goal when I wrote that up...)21:51
danwentfor quantum, we are trimming essex-2 a bit: https://launchpad.net/quantum/+milestone/essex-221:51
danwentmain code changes for quantum that need to get into nova are already under review.21:51
ttxdanwent: looks more reasonable :)21:51
danwentmtaylor: let's chat about quantum client lib offline21:51
danwentor you can come to netstack meeting next21:51
ttxAny other team lead with a status report ?21:51
anotherjesseVek: link?21:51
znsVek: been heavily focused on Keystone itself and middleware testing. Not much on the client yet.21:51
danwentand a heads up to the horizon folks, we'll probably be pinging you about some quantum related changes this week.  can target either e2 or e321:52
mtaylordanwent: yes! I've been meaning to find you to chat about that - yours is actually probably one of the easiest to deal with :)21:52
annegentleDocs team working on a blueprint for API reference pages… see http://heckj.github.com/api-site-mock/# for a mockup.21:52
Vekanotherjesse: looking up now.21:52
reed#info <annegentle> Docs team working on a blueprint for API reference pages… see http://heckj.github.com/api-site-mock/# for a mockup.21:52
ttxannegentle: looks nice21:52
Vekanotherjesse: http://wiki.openstack.org/ClientAuthenticationPlugin21:52
tr3buchettroytoman: danwent: can you guys put some current status info for quantum and melange on http://etherpad.openstack.org/nova-network-team21:52
annegentleI want one more level of navigation added, but as a wireframe it's going to be useful.21:53
ttxdevcamcar: still not around ?21:53
dolphmannegentle: very cool!21:53
danwenttr3buchet: I assume this is limited to quantum changes affecting nova, not quantum changes in general?21:53
*** somik has quit IRC21:53
annegentleWe experimenting with WADL as source for this output.21:53
dolphmannegentle: how is this being built?21:54
dolphmthanks ^^21:54
annegentledolphm: this is a wireframe made with copy/paste for review :) the actual building will be based on the reqs gathered.21:54
tr3buchetdanwent: yes correct21:54
ttxOK, switching to open discussion, as we have a few things to discuss there21:54
ttx#topic Open discussion21:54
*** openstack changes topic to "Open discussion"21:54
tr3buchetdanwent: i assume you have plenty of etherpads floating around for the rest21:54
ttxvishy: you wanted to mention PPAs ?21:54
danwenttre3buchet:  indeed.  sounds like a plan21:54
ttxdolphm: <<"Status" is a male noun of the Fourth Declension in Latin, and as such the plural is "status", spelled identically>>21:55
anotherjesseVek: that seems like it would make doing the what the CLI Auth page is talking about easier.  the cli auth page is talking about what the interface for users is, whereas the CAP page is about how you would then implement it21:55
ttxvishy: go for it21:55
dolphmpsh, i studied latin, i'll stick with statii21:55
vishyin my mind we have a big problem with our ppa21:55
*** somik has joined #openstack-meeting21:55
vishyand we need to fix it21:55
ttxwhich ppa ?21:55
vishywe are still providing a release ppa21:55
vishyand it is broken21:56
salv-orlandottx: second declension21:56
vishyi would like to replace all of our ppas21:56
vishywith a stable ppa21:56
vishymtaylor: ping21:56
*** debo-os has joined #openstack-meeting21:56
* mtaylor agrees with vishy21:56
* annegentle cheers21:56
vishyi don't want to have people installing a bunch of stuff that doesn't work21:56
mtaylorhaving a ppa up there with broken packages isn't doing anybody any favors21:56
ttxvishy: I agree we should remove the release PPA. But..21:57
vishyand currently there is no option for people running on lucid21:57
ttxI don't want to have people installing a bunch of stuff nobody actually maintains21:57
vishyttx: well we already have that :)21:57
mtaylorI think that we have people maintaining stable/diablo now21:57
dolphmreed: that shows statii (stat-longI), right?21:57
mtaylorand that is at least more maintained than the current diablo packages in openstack-release21:57
vishywe might as well give them something that is a best effort at working rather than something that is totally broken21:57
zulwe are going to be releasing a stable/diablo we just have to get through some bureacracy21:58
markmcvishy, how about doing releases from stable/diablo and pushing ppas of those?21:58
mtaylorzul: for lucid?21:58
markmcright, what zul said21:58
zulmtaylor: oneiric21:58
ttxmtaylor: my point is that they maintain a branch for backports... not necessarily something that is supposed to be run in production21:58
glencTu es adhuc bene litteratus, sed fallitur.21:58
markmcvishy, rather than e.g. nightly builds of stable/diablo21:58
reeddolphm, not for the noun21:58
*** edgarmagana has joined #openstack-meeting21:58
vishymarkmc: I'm ok with that21:58
dolphmreed: just noticed that :P21:58
zuland we might have a ppa that has a weekly snapshot of stable/diablo soon as well21:58
vishymarkmc: mainly i just want to give people an option who aren't running on oneiric21:58
mtayloryeah. that's the important bit.21:59
zulso we will be testing stable/diablo for oneiric21:59
markmcttx, any release from stable/diablo should be as production ready as 2011.321:59
* dolphm happily ignored latin conjugation in highschool21:59
vishyzul: is it possible to have a stable/diablo for lucid?21:59
markmcttx, or put it this way, we wouldn't release from stable/diablo until we were confident of it being production ready21:59
vishymarkmc, ttx: any release would be better than 2011.3 :)21:59
vladimir3pand natty?22:00
* Vek 's high school did not have latin, or in fact most other foreign languages...22:00
zulvishy: i dont know..22:00
ttxmarkmc: I still think it's "less good" than something the distros would provide.22:00
vishywe already have all of the infrastructure (backports etc.) in place for a lucid ppa22:00
mtaylorttx: distros don't provide for pre-oneiric22:00
ttxcompare stable/diablo and the current SRUs on Oneiric22:00
markmcttx, oh, I agree with that22:00
vishyit just needs the nova code to be updated.22:00
markmcttx, it's less bad than 2011.3 from upstream, too though22:00
ttxmarkmc: so if it ends up being "better but not good enough for production", I'd rather just scrap them22:01
vishyif that means a 2011.3.1 release that is fine?22:01
markmcttx, well - 2011.3.x releases would be useful IMHO22:01
*** SumitNaiksatam has joined #openstack-meeting22:01
ttxuntil someone maintains a true distribution of openstack for old stable versions of distros22:01
markmcttx, if release PPAs are useful at all, then a release PPA of 2011.3.x would be useful too22:01
* dolphm tried unsuccessfully to sign up for Canadian22:02
mtaylorI think we should cut packages from 2011.3.1 and upload them to the release ppa. whatever we do for essex, the diablo release exists and people are trying to sue it22:02
mtayloruse it22:02
ttxthis all needs a discussion. I'll explain why I think this is a bad idea22:02
*** masumotok has quit IRC22:02
ttxbut that would probably delay the net guys by a few hours22:02
markmcttx, perhaps separate out doing 2011.3.x releases from the usefulness of release PPAs22:02
dolphma bad idea for keystone, or for every project?22:03
ttxA bad idea for openstack itself as an upstreal22:03
markmcwhich one is a bad idea? 2011.3.x releases or release PPAs?22:03
vishyif I can't get by in on updating the ppa22:03
vishyi think we need to delete it22:03
vishyand someone else can make one22:03
ttxso far we had a model where we put out releases and downstreams make them production-ready and updateable22:03
vishybut there is a lot of backporting effort that will be hard to redo22:04
markmcvishy, e.g. Kiall :)22:04
Kiallvishy: that already happened ;)22:04
mtaylorttx: I do not believe that model has worked22:04
ttx#action ttx or vishy to start a discussion on release PPA22:04
*** jsavak has quit IRC22:04
vishyKiall: you have a lucid ready version of stable/diablo?22:04
ttxmtaylor: I think we'll just end up spreading our resourecs and lower end quality as a result22:04
ttxbut let's close this meeting and let the netstack guys in22:05
Kiallvishy: nope.. I havent done any bar oneiric22:05
markmcttx, which one is a bad idea? 2011.3.x releases or release PPAs? or both?22:05
mtaylorttx: I think that it's clear people want this ppa. at the moment, Kiall is maintaining one. and I'd really love to avoid the sentence:22:05
mtaylor"the openstack release ppa is broken, please see this person's ppa for working packages"22:05
ttxIf there is a need, a company should make a distro around it22:05
*** ying has joined #openstack-meeting22:05
reedmtaylor, indeed22:06
mtaylorI disagree ttx22:06
reedbetter none than a broken one22:06
mtaylorthis is theoretically a community project22:06
jog0why is the https://launchpad.net/~nova-core/+archive/trunk nova 2 weeks old also?22:06
Kiallmtaylor: even I agree there... People use my PPA doesnt look good for ubuntu or openstack...22:06
mtaylorthere is community making pacakges22:06
mtaylorhow about we actually embrace that22:06
*** Uri_ has joined #openstack-meeting22:06
ttxmtaylor: we should have that discussion on the ML22:06
mtaylorinstead of deferring to theoretical companies who do not exist22:07
ttxand close this meeting.22:07
reedyes, this is ml material22:07
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:07
openstackMeeting ended Tue Nov 29 22:07:09 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:07
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-21.03.html22:07
mtaylorI do not think that this disucssion on the mailing list will be useful at all22:07
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-21.03.txt22:07
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-21.03.log.html22:07
mtaylorbut whatever22:07
*** dprince has quit IRC22:07
ttxmtaylor: or on #openstack-dev, at an hour where I can actually sustain it22:07
ttxdanwent: sorry for being late22:07
mtaylorttx: fair.22:07
danwenthello netstackers22:07
danwentttx: np22:07
reedI like the minutes with lots of #info tags...22:07
*** markmc has left #openstack-meeting22:07
danwentwelcome back salv-orlando22:08
somikhello folks!22:08
GheRiverohi people22:08
openstackMeeting started Tue Nov 29 22:08:12 2011 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.22:08
openstackUseful Commands: #action #agreed #help #info #idea #link #topic.22:08
reedeverybody: remember to use #info more often22:08
*** Vek has left #openstack-meeting22:08
salv-orlandonice to talk to you again22:08
danwent#link agenda: http://wiki.openstack.org/Network/Meetings22:08
reedit makes minutes more readable22:08
danwentmtaylor: you around?22:08
cdubreed: that should be #info'd ;)22:09
danwentbefore diving into melange + quantum specifically, I wanted to have mtaylor talk about his thoughts on splitting clients out of the main repo, and how that woould work for quantum + melange22:09
danwentmarkvoelker: welcome back :)22:09
*** valgarie has joined #openstack-meeting22:09
danwentmtaylor: ping?22:10
cdubdanwent: as in nova/network/quantum/client.py ?22:10
mtaylordanwent: pong22:10
danwentcdub:  the goal is that once we have clients packaged, we can remove the nasty copy of client.py in different repos22:11
cdub*nod* just making sure that was client we were talking about22:11
mtaylordanwent: I would like to make the client subdir its own repo. and the common subdir its own repo22:11
danwentcdub: yup22:11
danwentmtaylor: i'm worried about the complexity here…22:12
mtaylordanwent: and I would like to put both of those repos in to gerrit as projects that are managed by quantum core22:12
mtaylordanwent: yes. however, it's a complex problem, so sometimes complexity is going to happen :)22:12
*** Tushar has quit IRC22:12
bhallmtaylor: what about server, plugins, etc?22:12
mtaylordanwent: the problem is that we've got projects that need to depend on this stuff (horizon being a good example)22:12
mtaylorso we need to be able to reference the actual thing that's needed, wihtout pulling in the entire server22:13
*** dprince has joined #openstack-meeting22:13
danwentmtaylor: definitely understand that.. we want to be able to package things separately, definitely22:13
cdubsounds more like packagin then repo mgmt22:13
danwentI think the question is why packaging needs to be tied to repo so tightly.22:13
cdube.g. simple to build multpile packages from a single repo22:13
danwenti definitely understand that you have a lot of experience here… :)22:13
danwentcdub: yes, in fact that is what we do already.22:14
mtaylorit's for a few reasons22:14
mtaylorpip requires git lines can't reference sub directories22:14
mtaylorso you wind up with venv installs that require actual releases to pypi to be consumable22:15
mtayloradditionally, once you start having submodules in tree, standard tooling winds up being difficult to apply - knowing to interact with a setup.py in trunk is straight forward22:15
mtaylorknowing that there are 4 setup.py files spread throughout the tree is less obviouos22:15
bhallas of yesterday all setup.py's are in the root :)22:16
danwentok, so the trade-off here is if we want the pip files of other projects to automatically pull "trunk", we need separate repos?22:16
mtayloralso, it's the  model we're using for the other projects, so in keeping with a consistent project-wide approach, I'd kind of want to hear a really good reason that it can't work22:17
bhallhow many repos are we talking about? client, common, server, plugins?22:17
danwentI'm also worried about trying to keep quantum simple enough that its easy for new people to join and hack on the project22:18
mtaylorI don't think, as of yet, that we need separate ones for plugins22:18
mtaylorthe most important one in my brain in client - as we have a python-*client project either in existence or coming in to existence for every openstack project22:18
bhallcould we go with two repos? client, common/server/plugins22:19
mtaylorthe common one is just because that's how you've organized your code - and i believe client depends on it, yeah/22:19
mtaylordoes client depend on common?22:19
danwentI believe that was the original goal22:19
danwentbut perhaps we should revisit that… I'm not sure how much is currently shared.22:19
bhallI think it does currently22:19
bhallyeah, I don't think there is a lot of code that it depends on22:20
danwentmtaylor: so the main goal here is pip install, which are mainly targetted at developers right?22:20
danwent(I assume non-developers will get everything via packages, which should have dependencies described in terms of packages)22:21
mtaylordanwent: yes22:21
danwentok, thanks for the explanations… I think I understand this better now, but still need to noodle on whether there are ways we can both be happy :)22:22
mtaylordanwent: there is no thought that people will be doing production releases from pip :)22:22
mtaylordanwent: awesome22:22
danwentmtaylor: given your goal of doing this for e2, we'll follow-up with you soon.  and we'll make sure netstack list is cc'd22:22
mtaylordanwent: sounds great!22:23
danwentappreciate your time22:23
danwentOk, troy, still around?22:23
danwent#status Melange Update22:23
danwent#topic Melange Update22:23
*** openstack changes topic to "Melange Update"22:23
danwenttired fingers :)22:23
troytoman#info the melange repo will move to the openstack github/gerrit system tomorrow at 3PM CST22:24
troytomanmostly been working with mtaylor and jeblair on that.22:24
troytomanwe are almost done with adding notifications as well.22:24
troytomanonce we have that done we will look to implement notifications for quantum22:25
troytomanprobably an e-3 type item22:25
troytomanotherwise, trying to flesh out documentation, etc.22:25
danwentanswered the question before I could ask :)22:25
troytomanthat's about it22:25
salv-orlandotroytoman: do you think explicit plugin support would be required/adivsable for notifications?22:25
troytomanmy fingers aren't as tired22:25
troytomansalv-orlando: you mean support for plugins within notifications?22:26
troytomanor plugins for notifications?22:26
salv-orlandoactually, I meant to ask whether plugins should be explicitly aware of the presence of the notification mechanism22:27
*** thingee1 has left #openstack-meeting22:27
salv-orlandoor if that something you can entirely handle in the API layer22:27
troytomanthat's probably a good topic to consider. since we have focused initially on Melange we haven't thought about plugins22:27
danwentyeah, probably depends on the scope of notifications.  if they just map to API actions, I would assume plugins don't need to know about them.22:28
troytomanbut it would be a good thing to think through - initially we are focusing on basic notifications like create/delete network, ports, etc.22:28
salv-orlandook, cool. We'll see as soon as the spec is more defined.22:28
troytomani think plugins could add notifications that take advantage of the basic structure that is there22:28
troytomanlook over the blueprint and let's discuss further22:28
danwentok, anything else on melange?22:29
danwent#topic Quantum Status22:29
*** openstack changes topic to "Quantum Status"22:29
*** troytoman is now known as troytoman-away22:29
danwent#info we're doing pretty well on reviews: https://review.openstack.org/#q,status:open+project:openstack/quantum,n,z22:29
danwent#info largest existing review is salvatore's patch left from e-1, but that just requires minor tweaks.22:30
danwentBrad, can you also send a pointer to the nova-parity-nat review, as that is in nova?22:30
bhallsure, lemme find it22:31
salv-orlandotweaks should be in tomorrow. Apologies if I've been lazy on Quantum lately :)22:31
danwentsalv: next two topics for e-2 are you… so we'll see :)22:31
danwentessex-2 milestone: https://launchpad.net/quantum/+milestone/essex-222:31
bhall#info nova-parity-nat review: https://review.openstack.org/#change,194022:31
danwentthings are still a bit loaded for e-2, so I wanted to review the major items.22:31
danwentsalv-orlando: operational status22:32
danwentI think this needs to be available soon if plugins are going to be able to implement the interface in time for e-222:32
salv-orlandoThis will be available for e2, definitely. The issue is what we should assume about plugins.22:32
salv-orlandoIf a plugin does not support the operational status, how are we going to behave?22:33
danwent#link operationa status still targeted for e2: https://blueprints.launchpad.net/quantum/+spec/api-operational-status22:33
salv-orlandoReturn an "UNKNOWN" status, return an exception?22:33
salv-orlandoI'm for the UNKNOWN status22:33
danwentsalv: that is what I was going to suggest as well.22:33
salv-orlandocool. Anybody against the UNKNOWN state?22:33
danwentyou're going to send out a detailed spec proposal though?22:34
salv-orlandoStill need to update the one on the wiki. My apologies for that...22:34
salv-orlando#action Salvatore to provide updated spec22:34
danwentOk, please ping netstack.  yup, great22:34
danwentanyone from cisco around that can comment on whether there should be a bug for doing operational status for the cisco plugin in e-2?22:35
danwentnext API topic: filters (https://blueprints.launchpad.net/quantum/+spec/api-filters)22:36
danwentsalv, this is you as well.  delivery status is "unknown"22:36
SumitNaiksatamdanwent: yeah, need to look at the spec22:36
danwentsumit: great, thanks22:37
danwentsumit: perhaps create a bug/bp for this and target to essex-2, just so we can track it.22:37
SumitNaiksatamdan: ok22:38
danwentsalv-orlando: comments on status of filter?  still planning on e-2?22:38
salv-orlandoI reckon we put this spec to unknown because we did not want to create too much pressure on plugin for essex-222:38
danwentso sounds like e-3?22:38
*** bcwaldon has quit IRC22:38
salv-orlandoThe code is fairly straightforward, but as any thing requires some thought. And there will possibly be plugin support required.22:38
*** jk0 has left #openstack-meeting22:39
salv-orlandoI therefore suggest to move this feature to e-322:39
danwentsalv-orlando: yes, I suspect plugin support would be required22:39
danwentsounds good.22:39
salv-orlandoI think that in this case it is advisable, but not strictly required (plugin can return all data, and API does filter)22:39
danwentsalv: for the filtering, would be good for us to do a quick analysis of any inefficient queries that quantummanager has to do… those are probably primary targets22:39
salv-orlandoanyway, we would still need a mechanism to understand whether the plugin is providing the filter :)22:39
salv-orlandoyeah, let's target the analysis in a week.22:40
danwentok, thanks22:40
danwentcarlp: you here?22:40
salv-orlando#Action salvatore to publish on wiki and discuss on NetStack mailing list points where API filters might be required.22:40
danwent#action #danwent contact #carlp about jenkins environment: https://blueprints.launchpad.net/quantum/+spec/quantum-functional-test-environment22:41
danwent#info: plan is to have at least one simple integration test for nova + quantum in by essex-2, just so we start flushing out practical issues.  If anyone wants to contribute more, please do22:42
danwentbhall: nova-nat parity?22:42
bhallone review so far22:42
bhallone more to go22:42
danwentok, sounds good.22:43
danwentdebo-os: any comments on the cloudpipe work?22:43
debo-osI figured out the main changes ... writing hte BP22:43
*** somik_ has joined #openstack-meeting22:43
debo-osalso we discussed pushing this to E3 due to nova changes22:44
debo-osBP should have the flow and be done in 1-2 days22:44
danwentdebo-os: yes, makes sense.  don't want to push anything to nova team last minute22:44
*** salv has joined #openstack-meeting22:44
danwentok, sounds great.  ideally we get this done early e-3, which makes for a more relaxed nova reivew process :)22:44
danwentlooks like arvind isn't around, but I know he is planning on spinning up again on the quantum + horizon work.  if you're interested in collaborating, send mail to the list.  I expect to see more BPs soon.22:44
danwentthree bugs to talk about:22:45
danwentbug #80308622:45
uvirtbotLaunchpad bug 803086 in quantum "plugins.ini should be collapsed into quantum.conf to prevent configuraitn"sprawl"" [Medium,In progress] https://launchpad.net/bugs/80308622:45
*** SumitNaiksatam_ has joined #openstack-meeting22:45
*** liemmn has quit IRC22:45
danwentI'm still in favor of getting this in.  we delayed it from e-1 because it was too close to the deadline.  any concerns?22:45
danwentbasically, just means that you configure the plugin in quantum.conf to avoid having too many config files.22:46
danwentbug #89781722:46
uvirtbotLaunchpad bug 897817 in quantum "The cisco plugin extensions need to move to the cisco plugin directory" [Medium,New] https://launchpad.net/bugs/89781722:46
danwentthis is point raised on ML.  wanted to get comment from cisco team.22:46
*** ying has quit IRC22:46
*** edgarmagana has quit IRC22:46
*** somik has quit IRC22:46
*** edgarmagana has joined #openstack-meeting22:46
cdubdanwent: what about this comment "Considering that we are relying on plugins.ini in several places outside of quantum, ..." (re first bug)22:47
*** jrouault has quit IRC22:47
danwentactually, that was a concern I raised.  we have some automation scripts that do this as part of automated configuration.22:47
*** Uri_ has quit IRC22:47
*** SumitNaiksatam has quit IRC22:47
*** salv-orlando has quit IRC22:47
*** sapachat has joined #openstack-meeting22:47
danwentto me this is one of those things where the long we wait, the more things we'll break, so we might as well change it soon.22:48
salvcdub: good point. However, keeping two conf files does not look good.22:48
cdubas long as "places outside of quantum" is well-known, then makes sense to collapse and update the few external dependencies22:48
edgarmaganaI got kicked out from the IRC meeting!22:48
salvWe can deprecate plugins.ini but still support it in e-2 and e-322:48
*** dprince has quit IRC22:49
danwentcdub: yeah, trying to get it changed while that is still the case :)22:49
salvand then remove it completely for the final release22:49
cdub+1 to that22:49
danwentsalv: yeah, a "soft" removal is probably best22:49
salvcool. So, is that agreed?22:49
danwent#agreed:  implement "soft" removal of plugins.ini, which final removal targeted in essex main release22:50
danwentsalv: patch will have to change a bit then, correct?22:50
salvyes, but not a lot.22:50
danwentk, great22:51
danwentfinal bug of note: Bug #89783722:51
uvirtbotLaunchpad bug 897837 in quantum "The new packaging breaks find_config_file" [Critical,New] https://launchpad.net/bugs/89783722:51
bhallthat one is in already22:51
danwenttyler just filed this today, but seems important so I upped it to critical and targeted for e-222:51
bhallbug maybe not updated22:51
cdubdanwent: i think that's in the repo22:51
danwentdamn, that was quick, nice work :)22:51
danwentI will update the bug22:52
cdubcan someone explain this to me?22:52
cdubDate:   Tue Mar 29 23:15:10 2011 -040022:52
cdubTyler's commits are all from the past, but then i saw one from Brad as well22:52
*** dolphm has quit IRC22:52
danwentas a note: people should always include bug ids in the first line of the git commit, that way jenkins automatically updates the bug to committed.22:52
bhallone of my dev vms isn't using ntp I think22:53
cdubcommit done on workstation w/ wrong date?22:53
bhalland is way off as far as date is concerned22:53
cdubok, wasn't sure if there was some other weird magic going on ;)22:53
danwentok, i'll ping tyler about that too.  probably just dates being off, but yeah, its confusing.22:53
danwentOk, anything else for e-2?22:54
danwentremember, branch will be early on Dec 13th, for final release on Dec 15th22:54
danwentwe should now have correct repo permissions to do the branch, unlike with essex-122:54
danwent#topic Open Discussion22:54
*** openstack changes topic to "Open Discussion"22:54
edgarmaganaDan: I just created a BP for network services insertion22:55
danwentedgarmagana: link?22:55
edgarmaganada: #link https://blueprints.launchpad.net/quantum/+spec/services-insertion-wrapper22:55
edgarmaganaI am updating the full description but basically is what we decided during the summit22:56
danwentOk, from the write-up its not clear what changes will be made to quantum, so it seems a bit risky to me to target for essex-222:57
edgarmaganaIt will consist of a wrapper to insert a service "in-path" into the network22:57
danwentwhat portions of the codebase are affected?22:57
danwent"wrapper"… is this a new api extension?22:57
edgarmagananot impact to any other code, it will be an isolated piece of code calling other methods22:58
danwentok, so a quantum client?22:58
edgarmaganayes, very similar to client22:58
danwentok, if so, that seems pretty low risk for e-222:58
danwentI look forward to reading the BP.22:59
danwentanything else?22:59
danwentok, have a good one folks.  one minute to spare :)22:59
*** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/"22:59
openstackMeeting ended Tue Nov 29 22:59:42 2011 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-22.08.html22:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-22.08.txt22:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-11-29-22.08.log.html22:59
*** KyleM1 has left #openstack-meeting22:59
*** edgarmagana has quit IRC23:00
danwentbye all23:00
*** markvoelker has left #openstack-meeting23:00
*** sapachat has quit IRC23:02
*** debo-os has quit IRC23:06
*** dprince has joined #openstack-meeting23:07
*** valgarie has quit IRC23:10
*** dprince has quit IRC23:14
*** lloydde has quit IRC23:19
*** bencherian has quit IRC23:20
*** jog0 has left #openstack-meeting23:20
*** bencherian has joined #openstack-meeting23:21
*** rnirmal has quit IRC23:24
*** lloydde has joined #openstack-meeting23:28
*** bencherian has quit IRC23:40
*** bencherian has joined #openstack-meeting23:42
*** GheRivero has quit IRC23:49
*** adjohn has joined #openstack-meeting23:53
*** mcohen has left #openstack-meeting23:56

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