| *** bengrue_ has joined #openstack-meeting | 00:16 | |
| *** nati_ has joined #openstack-meeting | 00:16 | |
| *** _0x44_ has joined #openstack-meeting | 00:19 | |
| *** RichiH_ has joined #openstack-meeting | 00:19 | |
| *** s1rp_ has joined #openstack-meeting | 00:20 | |
| *** bengrue has quit IRC | 00:22 | |
| *** _0x44 has quit IRC | 00:22 | |
| *** nati has quit IRC | 00:22 | |
| *** s1rp has quit IRC | 00:22 | |
| *** bengrue_ is now known as bengrue | 00:22 | |
| *** RichiH has quit IRC | 00:22 | |
| *** deshantm_laptop has joined #openstack-meeting | 00:27 | |
| *** deshantm_laptop has quit IRC | 00:30 | |
| *** _0x44_ is now known as _0x444 | 00:33 | |
| *** _0x444 is now known as _0x44 | 00:33 | |
| *** bengrue has quit IRC | 00:35 | |
| *** vladimir3p has quit IRC | 00:37 | |
| *** nati has joined #openstack-meeting | 00:50 | |
| *** zul has quit IRC | 00:51 | |
| *** nati_ has quit IRC | 00:51 | |
| *** hisaharu has quit IRC | 00:51 | |
| *** deshantm has joined #openstack-meeting | 00:57 | |
| *** dprince has joined #openstack-meeting | 01:06 | |
| *** zul has joined #openstack-meeting | 01:09 | |
| *** zul has joined #openstack-meeting | 01:09 | |
| *** dprince has quit IRC | 01:11 | |
| *** primeministerp1 has joined #openstack-meeting | 01:22 | |
| *** alekibango has quit IRC | 01:47 | |
| *** alekibango has joined #openstack-meeting | 01:47 | |
| *** alekibango has quit IRC | 01:49 | |
| *** alekibango has joined #openstack-meeting | 01:49 | |
| *** alekibango has quit IRC | 01:51 | |
| *** alekibango has joined #openstack-meeting | 01:52 | |
| *** nati_ has joined #openstack-meeting | 02:03 | |
| *** nati has quit IRC | 02:03 | |
| *** alekibango has quit IRC | 02:05 | |
| *** alekibango has joined #openstack-meeting | 02:05 | |
| *** msinhore has joined #openstack-meeting | 02:19 | |
| *** jakedahn has quit IRC | 02:34 | |
| *** dragondm has quit IRC | 02:35 | |
| *** nati has joined #openstack-meeting | 02:40 | |
| *** nati_ has quit IRC | 02:40 | |
| *** msinhore1 has joined #openstack-meeting | 02:57 | |
| *** msinhore has quit IRC | 02:57 | |
| *** jakedahn has joined #openstack-meeting | 03:17 | |
| *** nati has quit IRC | 03:39 | |
| *** adjohn has quit IRC | 03:55 | |
| *** jakedahn has quit IRC | 04:06 | |
| *** nati has joined #openstack-meeting | 04:09 | |
| *** adjohn has joined #openstack-meeting | 04:19 | |
| *** primeministerp2 has joined #openstack-meeting | 04:40 | |
| *** primeministerp1 has quit IRC | 04:40 | |
| *** msinhore1 has quit IRC | 04:59 | |
| *** martine has quit IRC | 05:19 | |
| *** adjohn has quit IRC | 05:51 | |
| *** adjohn has joined #openstack-meeting | 06:00 | |
| *** adjohn has quit IRC | 06:50 | |
| *** alekibango has quit IRC | 07:22 | |
| *** bengrue has joined #openstack-meeting | 07:32 | |
| *** bengrue has quit IRC | 08:19 | |
| *** nati has quit IRC | 08:56 | |
| *** nati has joined #openstack-meeting | 09:10 | |
| *** nati has quit IRC | 09:37 | |
| *** nati has joined #openstack-meeting | 09:42 | |
| *** nati has quit IRC | 09:57 | |
| *** RichiH_ is now known as RichiH | 10:52 | |
| *** msinhore has joined #openstack-meeting | 11:12 | |
| *** jaypipes has quit IRC | 11:14 | |
| *** markvoelker has joined #openstack-meeting | 11:18 | |
| *** jaypipes has joined #openstack-meeting | 11:31 | |
| *** msinhore has quit IRC | 11:56 | |
| *** joesavak has joined #openstack-meeting | 12:06 | |
| *** jsavak has joined #openstack-meeting | 12:14 | |
| *** joesavak has quit IRC | 12:16 | |
| *** zul has quit IRC | 12:21 | |
| *** zul has joined #openstack-meeting | 12:22 | |
| *** jsavak has quit IRC | 12:23 | |
| *** mattray has joined #openstack-meeting | 12:56 | |
| *** med_out is now known as medberry | 13:09 | |
| *** mattray has quit IRC | 13:23 | |
| *** martine has joined #openstack-meeting | 13:23 | |
| *** mattray has joined #openstack-meeting | 13:23 | |
| *** jjm has quit IRC | 13:41 | |
| *** mdomsch has joined #openstack-meeting | 13:46 | |
| *** creiht has joined #openstack-meeting | 13:49 | |
| *** joesavak has joined #openstack-meeting | 14:09 | |
| *** jsavak has joined #openstack-meeting | 14:11 | |
| *** joesavak has quit IRC | 14:14 | |
| *** vladimir3p has joined #openstack-meeting | 14:33 | |
| *** mattray1 has joined #openstack-meeting | 14:44 | |
| *** mattray has quit IRC | 14:44 | |
| *** rnirmal has joined #openstack-meeting | 14:45 | |
| *** mdomsch has quit IRC | 14:48 | |
| *** mattray1 has quit IRC | 14:50 | |
| *** dragondm has joined #openstack-meeting | 15:04 | |
| *** AlecTaylor has joined #openstack-meeting | 15:05 | |
| AlecTaylor | hi | 15:05 |
|---|---|---|
| AlecTaylor | Do you know of a locally-hostable project which allows for call-in radio-shows to be hosted (and interacted with) through a web-interface? | 15:05 |
| *** alekibango has joined #openstack-meeting | 15:19 | |
| *** jsavak has quit IRC | 15:30 | |
| *** joesavak has joined #openstack-meeting | 15:30 | |
| *** mattray has joined #openstack-meeting | 15:37 | |
| *** mattray has quit IRC | 15:46 | |
| *** troytoman-away is now known as troytoman | 15:47 | |
| *** jsavak has joined #openstack-meeting | 15:53 | |
| *** joesavak has quit IRC | 15:54 | |
| *** jsavak has quit IRC | 16:01 | |
| *** dendrobates is now known as dendro-afk | 16:02 | |
| *** adjohn has joined #openstack-meeting | 16:06 | |
| tr3buchet | . | 16:15 |
| *** mattray has joined #openstack-meeting | 16:18 | |
| *** dendro-afk is now known as dendrobates | 16:19 | |
| *** hisaharu has joined #openstack-meeting | 16:24 | |
| *** adjohn has quit IRC | 16:25 | |
| *** mdomsch has joined #openstack-meeting | 16:32 | |
| *** mdomsch_ has joined #openstack-meeting | 16:32 | |
| *** jaypipes has quit IRC | 16:42 | |
| *** jaypipes has joined #openstack-meeting | 16:43 | |
| *** mtaylor has quit IRC | 16:46 | |
| *** mtaylor has joined #openstack-meeting | 16:46 | |
| *** mtaylor has quit IRC | 16:46 | |
| *** mtaylor has joined #openstack-meeting | 16:46 | |
| *** jeblair has quit IRC | 16:51 | |
| *** termie_ has joined #openstack-meeting | 16:52 | |
| *** medberry is now known as med_out | 16:53 | |
| *** nati has joined #openstack-meeting | 16:55 | |
| *** termie has quit IRC | 16:56 | |
| *** jeblair has joined #openstack-meeting | 16:57 | |
| *** ecarlin has joined #openstack-meeting | 16:58 | |
| *** mdomsch_ has quit IRC | 17:01 | |
| *** mdomsch has quit IRC | 17:01 | |
| *** joesavak has joined #openstack-meeting | 17:02 | |
| *** ecarlin has quit IRC | 17:05 | |
| *** ecarlin has joined #openstack-meeting | 17:07 | |
| *** dabo has joined #openstack-meeting | 17:15 | |
| *** joearnold has joined #openstack-meeting | 17:17 | |
| *** Cyns has joined #openstack-meeting | 17:18 | |
| *** jaypipes has quit IRC | 17:27 | |
| *** msinhore has joined #openstack-meeting | 17:30 | |
| *** jaypipes has joined #openstack-meeting | 17:30 | |
| *** jaypipes has quit IRC | 17:31 | |
| *** jaypipes has joined #openstack-meeting | 17:34 | |
| *** adjohn has joined #openstack-meeting | 17:39 | |
| *** notmyname has quit IRC | 17:40 | |
| *** notmyname has joined #openstack-meeting | 17:40 | |
| *** jsavak has joined #openstack-meeting | 17:41 | |
| *** jsavak has quit IRC | 17:42 | |
| *** jsavak has joined #openstack-meeting | 17:42 | |
| *** jsavak has quit IRC | 17:44 | |
| *** joesavak has quit IRC | 17:46 | |
| *** Cyns has quit IRC | 17:48 | |
| *** alekibango has quit IRC | 17:48 | |
| *** bengrue has joined #openstack-meeting | 17:56 | |
| *** dendrobates is now known as dendro-afk | 17:57 | |
| *** dendro-afk is now known as dendrobates | 18:00 | |
| *** anotherjesse has joined #openstack-meeting | 18:04 | |
| *** joesavak has joined #openstack-meeting | 18:07 | |
| *** jsavak has joined #openstack-meeting | 18:08 | |
| *** jakedahn has joined #openstack-meeting | 18:09 | |
| *** jsavak has quit IRC | 18:11 | |
| *** troytoman is now known as troytoman-away | 18:23 | |
| *** jsavak has joined #openstack-meeting | 18:27 | |
| *** adjohn has quit IRC | 18:30 | |
| *** mattray1 has joined #openstack-meeting | 18:31 | |
| *** adjohn has joined #openstack-meeting | 18:32 | |
| *** mattray has quit IRC | 18:34 | |
| *** adjohn has joined #openstack-meeting | 18:48 | |
| *** _adjohn has joined #openstack-meeting | 18:52 | |
| *** adjohn has quit IRC | 18:52 | |
| *** _adjohn is now known as adjohn | 18:52 | |
| bengrue | ping | 19:01 |
| jaypipes | bengrue: heya | 19:01 |
| jeblair | hi | 19:01 |
| jaypipes | o/ | 19:01 |
| nati | o/ | 19:01 |
| jaypipes | bengrue: didn't see any reply from you or anotherjesse on my email :( | 19:01 |
| mtaylor | hey all - one sec... | 19:01 |
| anotherjesse | jaypipes: I am summonized | 19:01 |
| bengrue | I was WFH sick yesterday, just getting up to speed now. | 19:02 |
| jaypipes | anotherjesse: ? | 19:02 |
| *** ecarlin_ has joined #openstack-meeting | 19:02 | |
| anotherjesse | jaypipes: irc beeped me here | 19:04 |
| soren | brb | 19:04 |
| jaypipes | anotherjesse: any response on my email to you and grue? | 19:04 |
| mtaylor | ok. who wants to talk about CI? | 19:04 |
| anotherjesse | jaypipes: yes - I wanted grue to explain but as we heard he was sick yesterday | 19:04 |
| jaypipes | I do I do! | 19:04 |
| mtaylor | #startmeeting | 19:04 |
| openstack | Meeting started Tue Aug 23 19:04:59 2011 UTC. The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot. | 19:05 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 19:05 |
| jaypipes | bengrue, anotherjesse: no worries. | 19:05 |
| jaypipes | bengrue: feeling better today I hope? | 19:05 |
| bengrue | Yeah. In the office. | 19:05 |
| jaypipes | OK, so mtaylor, before you start... lemme get something in. | 19:05 |
| *** ecarlin has quit IRC | 19:06 | |
| *** ecarlin_ is now known as ecarlin | 19:06 | |
| * mtaylor punches jaypipes | 19:06 | |
| mtaylor | #topic jaypipes talking to people about things | 19:06 |
| *** openstack changes topic to "jaypipes talking to people about things" | 19:06 | |
| jaypipes | All: I'm putting together a project plan that has action items for folks on my team (mtaylor, soren, and jeblair) as well as some folks on other teams like anotherjesse's. | 19:06 |
| jaypipes | Hoped to get it done by this meeting time, but failed unfortunately. | 19:07 |
| *** jbryce has joined #openstack-meeting | 19:07 | |
| jaypipes | The basic gist of the plan is that mtaylor and jeblair will have Jenkins firing off an automated deployment of OpenStack onto 5 lab servers by Friday, and this deployment cluster will have a set of functional tests run against it. | 19:07 |
| jaypipes | The tests will be just the nova smoketests and possibly some stuff from smokestack or kong (for this Friday) | 19:08 |
| * soren is back | 19:08 | |
| jaypipes | mtaylor is at Burning Man all next week so jeblair will be working on documenting a bunch of stuff next week around the CI infrastructure and soren will be documenting and working on QA/QE stuff (the actual test cases and suites running on a deployed cluster) | 19:09 |
| soren | Burning man? Will he be alright? | 19:09 |
| mtaylor | soren: always am | 19:09 |
| jaypipes | termie_ and sleepsonthefloor got Djeep installed on one of the lab servers late yesterday and jeblair now has access to that (thank you termie_ and sleepsonthefloor!_ | 19:09 |
| mtaylor | soren: I will, however, be COMPLETELY unreachable | 19:09 |
| jaypipes | what anotherjesse wants most is to have all the code (puppet modules, glue code, etc) in a public repo that is tested and code reviewed like any othe ropenstack project. We are all in agreement on that! | 19:10 |
| anotherjesse | jaypipes: I'm cool with the CI team who is doing the draft not having to get approval at the begining ;) | 19:11 |
| mtaylor | anotherjesse: ++ | 19:11 |
| anotherjesse | but putting it in a repo we can watch and help would be muy bueno | 19:11 |
| jaypipes | anotherjesse: sure | 19:11 |
| anotherjesse | mtaylor: that doesn't mean 1 huge drop - if you don't commit at least daily, no burning man for you | 19:11 |
| mtaylor | anotherjesse: so far, depending on what it is, we put everything we do in either openstack/openstack-ci or openstack/openstack-ci-puppet | 19:11 |
| mtaylor | anotherjesse: hehe | 19:11 |
| anotherjesse | mtaylor: will that be added to ci.openstack.org - which repo is for what | 19:12 |
| mtaylor | anotherjesse: and we actually already do gerrit reviews and some testing on each other ... so we're set | 19:12 |
| jaypipes | I think that there are a number of GitHub repos already existing that contain puppet modules and chef recipes. These need to be identified and anotherjesse and others need to let mtaylor and jeblair know which puppet/chef modules we need to fire from Jenkins on each build to get continuos deployment testing better | 19:12 |
| mtaylor | anotherjesse: openstack-ci-puppet is for the puppet modules we use to manage the jenkins slaves and other servers | 19:12 |
| *** Shubhangi has joined #openstack-meeting | 19:12 | |
| mtaylor | anotherjesse: openstack-ci is for supporting scripts/glue code/docs/whatnot | 19:12 |
| anotherjesse | mtaylor: for the website - not for me ;) | 19:12 |
| jaypipes | one sec guys, can I just finish up? | 19:13 |
| mtaylor | anotherjesse: yup. | 19:13 |
| mtaylor | jaypipes: NO | 19:13 |
| mtaylor | jaypipes: yes | 19:13 |
| jaypipes | OK, so the Djeep installation on the deployment test cluster is temporary. Over the next week, jeblair is going to be looking into the puppet modules (site.pp IIRC) that Djeep generates/builds and converting the automation code to run cobbler instead of having the Djeep stuff on the deployment cluster. | 19:14 |
| jaypipes | This is going to be done with an eye to adaptability | 19:14 |
| jaypipes | so that in the future, things like Crowbar can also be used to deploy | 19:14 |
| jaypipes | anotherjesse: does above ^^ ok with you? | 19:14 |
| anotherjesse | jaypipes: cooleo - fyi djeep builds yaml files - and so puppet can run without it | 19:14 |
| jaypipes | anotherjesse: ok, well that is something that jeblair is going to document and analyze next week | 19:15 |
| jeblair | er, i'm at rookie-o next week | 19:15 |
| jaypipes | but the bottom line for all is that by Friday, we WILL have a deployment cluster that is at least: | 19:15 |
| jeblair | i'm not sure i'll have much time to work on this | 19:15 |
| jeblair | (next week) | 19:15 |
| anotherjesse | jeblair: take your laptop | 19:15 |
| jaypipes | jeblair: hold on, one sec :) | 19:15 |
| jaypipes | but the bottom line for all is that by Friday, we WILL have a deployment cluster that is at least: | 19:16 |
| jaypipes | a) testing *some* deployment packaging | 19:16 |
| jaypipes | b) firing *some* tests against the deployed cluster | 19:16 |
| jaypipes | OK.. .now | 19:16 |
| jaypipes | jeblair: documenting/analyzing stuff you can do while on the plane, etc.. Rookie-O isn't an all-consuming thing the entire week, and I'm trying to get us out of it a bit early so we can actually get some stuff done... | 19:17 |
| jaypipes | jeblair: if you don't get the analyze/document stuff done next week, it's ok... as long as we're moving forward and have a plan, I'm happy. | 19:18 |
| anotherjesse | jaypipes: fyi we took our laptops and sugarbear told us when we had to make sure to pay 100% attention (lawyers, hr, ...) | 19:18 |
| jaypipes | anotherjesse: yeah, but we're there the entire week... | 19:18 |
| jeblair | i just want to set expectations about how much time i'm really going to have to work on this stuff next week. | 19:18 |
| jaypipes | anyway, back on track... | 19:18 |
| jaypipes | jeblair: expectation is that you'll do the best you can, nothing more. | 19:18 |
| jaypipes | jeblair: same expectation for anyone else.. :) | 19:18 |
| jaypipes | the point is that we have a) a plan and b) we're moving forward and not spinning wheels | 19:19 |
| jaypipes | bengrue, anotherjesse, jeblair, mtaylor: agreed? ^^ | 19:19 |
| jeblair | lgtm | 19:19 |
| mtaylor | works for me | 19:19 |
| anotherjesse | jaypipes: agreed - mtaylor question about a | 19:19 |
| mtaylor | #agreed we have a) a plan and b) we're moving forward and not spinning wheels | 19:20 |
| mtaylor | anotherjesse: talk to me | 19:20 |
| bengrue | sounds clearer to me; where will the CI server be on friday? | 19:20 |
| anotherjesse | if we need to change the preseed or puppet rules - is that stuff that will be in the bzr repo? | 19:20 |
| jaypipes | as for soren's part in this, I will work with soren over the next few days to identify some low-hanging fruit re: funtional test suite and identifying/agreeing on OUTPUTs, etc | 19:20 |
| anotherjesse | (what it is pointing to) | 19:20 |
| jaypipes | anotherjesse: git repo, but yes | 19:20 |
| anotherjesse | jaypipes: cooleo - either way | 19:20 |
| mtaylor | anotherjesse: what jaypipes said | 19:20 |
| jaypipes | mtaylor: answer for bengrue ? | 19:20 |
| bengrue | (ie, what should I be paying attention to / eagerly awaiting with baited breath?) | 19:20 |
| anotherjesse | grue have seen your email from jay outlining a&b? | 19:21 |
| mtaylor | bengrue: I'm not sure I understand the question? | 19:21 |
| anotherjesse | (and cdefgh) | 19:21 |
| jaypipes | mtaylor: asking where he can see the deploy cluster | 19:21 |
| mtaylor | bengrue: as in - where will it physically be? | 19:21 |
| mtaylor | ah | 19:21 |
| mtaylor | well - jenkins.openstack.org will be the thing driving this puppy | 19:21 |
| bengrue | I have the email, scanned it so far, haven't responded yet. | 19:21 |
| jaypipes | mtaylor: and the code that is running/deploying the cluster, I assume | 19:21 |
| bengrue | Oh, the link is there. | 19:21 |
| bengrue | Well, the link to the documentation? http://ci.openstack.org | 19:22 |
| jaypipes | bengrue: that is mtaylor and jeblair are dumping docs on this stuff (and dumping more docs in the next days and weeks) | 19:22 |
| bengrue | are all of the ci jobs going to be prefixed with ci- ? | 19:23 |
| bengrue | Will there be more added in the next week? Or will everything be added into ci-puppet? | 19:23 |
| jaypipes | bengrue: more of what? sorry, docs or code? | 19:23 |
| mtaylor | sorry man - I'm still just not following the questions | 19:23 |
| jaypipes | yes, I'm not quite following you either, bengrue | 19:24 |
| anotherjesse | mtaylor: request for the ci.openstack.org site - can you put a "how to contribute" section? With links to repos and whatnot? | 19:24 |
| mtaylor | there will be a job, something like say "nova-baremetal" (it hasn't been named yet) that will launch the deploy/test stuff | 19:24 |
| mtaylor | anotherjesse: yes | 19:24 |
| jaypipes | anotherjesse: ++ | 19:24 |
| *** Atul has joined #openstack-meeting | 19:24 | |
| mtaylor | #action mtaylor Add how to contribute section to ci.openstack.org | 19:24 |
| jaypipes | mtaylor: openstack-deploy? :) nova is only one piece :) | 19:24 |
| anotherjesse | mtaylor: and perhaps a link to the ci site on the jenkins site? | 19:24 |
| bengrue | You're saying that by friday, there will be a deployment cluster that is testing deployment packaging and firing tests against it. You're saying that the ci server is jenkins.openstack.org. I assume that jenkins will be triggering the cluster deployment via new jobs, yes? | 19:25 |
| mtaylor | jaypipes: sure. like I said - I have not gotten there yet | 19:25 |
| jaypipes | bengrue: yep | 19:25 |
| mtaylor | bengrue: yes | 19:25 |
| bengrue | And then coordinating the testing against the cluster? | 19:25 |
| mtaylor | bengrue: yes | 19:25 |
| jaypipes | bengrue: well, firing a command that runs the tests, yes | 19:25 |
| bengrue | Will the new jenkins jobs be prefixed with ci- ? | 19:25 |
| mtaylor | no | 19:25 |
| jaypipes | no | 19:25 |
| jaypipes | All jenkins jobs are CI... | 19:25 |
| bengrue | where should I be looking on Jenkins for the new stuff? | 19:25 |
| mtaylor | I do not know what they will be prefixed with ... I'll send out a mailing list message | 19:26 |
| bengrue | Oh | 19:26 |
| bengrue | https://jenkins.openstack.org/job/ci/ | 19:26 |
| bengrue | Is this what I should be stalking? | 19:26 |
| mtaylor | no | 19:26 |
| jaypipes | co | 19:26 |
| jaypipes | no | 19:26 |
| bengrue | so tbd then, I'll wait for the msg. | 19:26 |
| mtaylor | that is merely a job that gerrit uses to check commits we make to openstack-ci - which are a collection of helper scripts | 19:26 |
| mtaylor | yeah - msg will make it clearer | 19:26 |
| mtaylor | also- I'd like to be clear on something ... | 19:27 |
| jaypipes | mtaylor: let's just determine the name now... can we call the master job openstack-deploy? | 19:27 |
| jaypipes | CI != QA :) | 19:27 |
| bengrue | I'm not sure I follow. | 19:27 |
| mtaylor | openstack-deploy is a bit encompasing - as I expect to have one of these jobs for msft/novel, one for citrix, etc. | 19:27 |
| mtaylor | so, how about openstack-deploy-rax | 19:27 |
| jaypipes | mtaylor: sure | 19:27 |
| mtaylor | since it's the one deploying to the rackspace hardware | 19:28 |
| anotherjesse | jaypipes: CI != QA - can you elaborate? | 19:28 |
| *** mdomsch has joined #openstack-meeting | 19:28 | |
| bengrue | In my experience, the whole point of CI/CD _is_ to play a large amount of the traditional QA role. | 19:28 |
| anotherjesse | jaypipes: this might be the disconnect? | 19:28 |
| anotherjesse | ;) | 19:28 |
| anotherjesse | since I agree with ben | 19:28 |
| mtaylor | CI is a tool/method used for QA | 19:28 |
| jaypipes | anotherjesse, bengrue: CI is the automation of continuous builds triggered by commits to trunk. QA is the tests and test suites that get executed against deployed clusteres | 19:28 |
| jaypipes | anotherjesse, bengrue: I explained this disconnect in terminology in my email to you both :) | 19:29 |
| jaypipes | anotherjesse, bengrue: sooo, in other words... | 19:29 |
| jaypipes | CI == Gerrit/Jenkins/Tarmac, CD == CI + deployment scripts and modules, QA == functional, unit, and integration test suites running on the clusters deployed by CD. | 19:30 |
| jaypipes | that make more sense? | 19:30 |
| jaypipes | mtaylor: would you agree with the above simplification? | 19:30 |
| anotherjesse | sure.. but the point of caring about CI is so you can do CD/QA | 19:31 |
| anotherjesse | not CI just for the sake of it | 19:31 |
| bengrue | I saw that, and I'm unsure that I agree with the premise. Technically the infrastructure to run tests are seperate from the tests, but both are necessary parts of the whole. | 19:31 |
| nati | jaypipes++ | 19:31 |
| bengrue | This is the CI/Testing team, right? | 19:31 |
| anotherjesse | so CI requirements are driven by CD/QA ? | 19:31 |
| jaypipes | anotherjesse: sure, but our team has expertise in CI and a bit in CD, and we need your team's expertise in D to get good CD and QA ;) | 19:31 |
| *** AlecTaylor has quit IRC | 19:31 | |
| bengrue | OMG acronym BBQ | 19:31 |
| anotherjesse | jaypipes: so - perhaps this is silly but imho most devs can't have a dev environment that even simulates a deployment | 19:32 |
| jaypipes | anotherjesse: the point being that mtaylor and jeblair own the glue code to fire off deployment modules that your team creates. | 19:32 |
| anotherjesse | since it is rather complicated to have a network toplogy | 19:32 |
| nati | NTT can also provide staff for QA in D ;) | 19:32 |
| anotherjesse | so - CI is needed to do development if you do TDD | 19:32 |
| jaypipes | anotherjesse: mtaylor and jeblair can't be responsible for creating working deployment/puppet modules... | 19:32 |
| bengrue | How can you have a stable testbed without working deployment scripts? | 19:33 |
| anotherjesse | not asking for that - asking for ability to not restrict the modules / scripts / … (which we have said we aren't!) | 19:33 |
| mtaylor | so... this is great ... I have the feeling we might not solve the acronym discussion right here | 19:33 |
| jaypipes | anotherjesse: but they *can* be responsible for making sure that the puppet modules your team and others create get automatically built on hardware linked in the CI environemt | 19:33 |
| anotherjesse | (they have said they aren't | 19:33 |
| anotherjesse | agree | 19:33 |
| jaypipes | anotherjesse: k. | 19:33 |
| jaypipes | anotherjesse: just trying to delineate who is owning what :) | 19:33 |
| anotherjesse | bengrue: I think he is saying that they will make the scripts that we collaborate on | 19:33 |
| anotherjesse | work | 19:33 |
| anotherjesse | but we (stackers) own the scripts | 19:33 |
| jaypipes | anotherjesse: yes! | 19:33 |
| jaypipes | :) | 19:33 |
| *** kris3968 has joined #openstack-meeting | 19:34 | |
| *** kris3968 has left #openstack-meeting | 19:34 | |
| bengrue | just the individual stacker teams? | 19:34 |
| jaypipes | anotherjesse: and we are relying on your team to create those puppet modules and make sure they actually work :) | 19:34 |
| anotherjesse | I've not thought otherwise - I've just not seen what are the assumptions about the environment our scripts need to run within ;) | 19:34 |
| bengrue | What about us sattelite companies? ; ) | 19:34 |
| anotherjesse | bengrue: you are a stacker | 19:34 |
| jaypipes | anotherjesse: and you are relying on us to make sure that jenkins continuously executes those puppet modules to test deployment and packaging. | 19:34 |
| bengrue | oh, openstack, derp. | 19:34 |
| bengrue | racker / stacker conflation | 19:35 |
| jaypipes | anotherjesse: we good on that distinction? | 19:35 |
| anotherjesse | bengrue: and so the CI environment needs to be chainable / …so you can kick off things (this is where monty/jim/jay can speak up since I don't even know the words) | 19:35 |
| anotherjesse | jaypipes: I've agreed with that and continue to agree with that | 19:35 |
| * soren needs to run for 3 minutes. | 19:35 | |
| mtaylor | anotherjesse: I think what you said may be part of a conversation we should have at some point re: "assumptions about the environment" | 19:35 |
| jaypipes | bengrue: outside partners and individuals such as yourself are welcome to contribute to any and all aspects of this, but IMHO, the most pressing needs are in the development of additional test cases. | 19:35 |
| mtaylor | anotherjesse: I think we may each be expecting to see those assumptions from each other :) | 19:35 |
| *** danwent has joined #openstack-meeting | 19:36 | |
| jaypipes | anotherjesse: re: chainable stuff, that's a task for mtaylor and jeblair to document: How to stand up a Jenkins builder in your own lab... | 19:36 |
| mtaylor | anotherjesse, bengrue: and yes. the intent is to allow all of the satelite companies to provide resources to ensure that specific hardware combinations/configurations that are important to them are tested | 19:37 |
| * soren returns | 19:37 | |
| jaypipes | mtaylor: ok, now that we've agreed to agree on the agreement about responsibilities, can we get an update on where we stand on the deployment cluster? | 19:37 |
| *** kris3968 has joined #openstack-meeting | 19:37 | |
| *** kris3968 has left #openstack-meeting | 19:37 | |
| mtaylor | jaypipes: jeblair is working with the djeep system that termie and sleepsonthefloor just handed off to him | 19:38 |
| jaypipes | mtaylor: by "working with", what do we mean? | 19:38 |
| *** Shubhangi has quit IRC | 19:38 | |
| jeblair | evaluating that it works as expected, and we have access. it does, and i do | 19:39 |
| jaypipes | jeblair: awesome. next steps? | 19:39 |
| bengrue | So, just for my general edification, when will the "assumptions about the environment" cease to be assumptions and start to be an agreed upon, explicit set of facts? Just looking for a general timeframe here, nothing binding. | 19:39 |
| mtaylor | hang on guys - one topic at a time please | 19:39 |
| bengrue | Is that a conversation for this coming week, etc? | 19:39 |
| *** msinhore has quit IRC | 19:40 | |
| jeblair | currently it's based on a puppetmaster server. we generally don't use that approach, and run puppet out of a local git repo. we may want to adjust the system to that approach | 19:40 |
| anotherjesse | bengrue: I think mtaylor as he deploys the first environment might have a heavily constrained first environment --- and then they are going to work on loosening it | 19:40 |
| jeblair | and get the puppet config in a git repo where we can all hack on it | 19:40 |
| mtaylor | anotherjesse: ++ | 19:40 |
| anotherjesse | bengrue: making it so there are multiple - and it evolves to multiple architectures | 19:40 |
| *** msinhore has joined #openstack-meeting | 19:40 | |
| bengrue | Okay, that makes sense. | 19:40 |
| anotherjesse | i'm hoping mtaylor will be guilted into lots of docs in ci.openstack.org ;) or beered into it | 19:41 |
| jeblair | we also need to start working on the jenkins job that fires off rebuilding the cluster | 19:41 |
| mtaylor | anotherjesse: definitely. | 19:41 |
| bengrue | I am a fan of spiking. | 19:41 |
| jaypipes | beer works best. | 19:41 |
| bengrue | make sure autocorrect is on. | 19:41 |
| bengrue | ; ) | 19:41 |
| jeblair | so i think that's the main thrust of work on the cluster, there are dependencies: | 19:42 |
| jaypipes | jeblair: the puppetmaster/git puppet thing can wait? or is that something you want to get done before Friday? | 19:42 |
| mtaylor | although just to set expectations ... priority #1 for the week is getting this working by friday. priority #2 is piles of docs. I want both, but I think 1 without 2 will be met with way more approval than 2 without 1 ... so if something has to slip to next week, it's going to be #2 | 19:42 |
| jaypipes | mtaylor: yes | 19:42 |
| anotherjesse | jeblair: the assumption is that we are working towards multiple architectures eventually (like VLAN mode vs LXC vs ...) | 19:42 |
| anotherjesse | right? | 19:42 |
| anotherjesse | so - tests will run against 1 or more architectures | 19:43 |
| mtaylor | yes | 19:43 |
| jaypipes | anotherjesse: yes, absolutely. | 19:43 |
| jaypipes | anotherjesse: there would be little point to this if that were not the case ;) | 19:44 |
| jeblair | yes -- the djeep setup presupposes one architecture, so that's probably a post-djeep step | 19:44 |
| jaypipes | jeblair, mtaylor: OK, so could you outline in steps exactly what you need to do before Friday to get this all going? Any blockers that anotherjesse can assist with? | 19:44 |
| anotherjesse | djeep pre-supposes nothing - but the preseeds/recipes it uses do … hence the roles / rolemapper - but for sake of arguement it doesn't change anything | 19:45 |
| jeblair | anotherjesse mentioned his team was continuing work on puppet recipies (and removing dependence on puppetmaster) -- any progress there we can use? | 19:45 |
| anotherjesse | jeblair: not yet - we've been focusing on d4 the last week | 19:46 |
| jaypipes | jeblair: is that a blocker for Friday or something post Rookie-O? | 19:47 |
| *** Shubhangi has joined #openstack-meeting | 19:47 | |
| anotherjesse | jeblair: imho if you have it kicking off with puppet solo but it blows up | 19:48 |
| anotherjesse | the community can fix it | 19:48 |
| anotherjesse | getting it so a button causes it to: spin up servers, kick off a script (that runs puppet or ?), then runs tests … if each of the steps is in CI, we can all pitch in if we can look at how it blows up | 19:49 |
| jeblair | we'll need the puppet config in git for that to work | 19:50 |
| jaypipes | anotherjesse: a Big Red Button? | 19:50 |
| anotherjesse | jeblair: isn't that what we are doing? | 19:50 |
| jeblair | so that's definitely the goal | 19:50 |
| *** johnpur has joined #openstack-meeting | 19:50 | |
| jaypipes | jeblair: where is the puppet config that is used to build the cluster now? | 19:50 |
| jeblair | it's on the cluster -- anotherjesse's team built it somewhat as a one-off | 19:51 |
| jeblair | so i'm not sure it's ready to go right into a git repo as-is | 19:51 |
| anotherjesse | jeblair: our puppet config is at github.com/cloudbuilders/openstack-puppet | 19:51 |
| anotherjesse | we don't even have a commit key on the server | 19:51 |
| anotherjesse | jeblair: so - the "missing" site.pp | 19:52 |
| anotherjesse | is because the whole point of djeep is 2 components | 19:52 |
| anotherjesse | 1) something that maps a server to a network / netboot config | 19:52 |
| anotherjesse | these configs get written to yaml/json files | 19:53 |
| anotherjesse | 2) puppet server that uses the node classification configuration | 19:53 |
| anotherjesse | that load those json/yaml | 19:53 |
| anotherjesse | so you can just use the puppet recipes with json & a classifier | 19:53 |
| anotherjesse | or you can use a site.pp | 19:53 |
| anotherjesse | or you can use everything if you are doing dev and switch between xen and kvm and different net models and blow away servers daily | 19:54 |
| *** Shubhangi has quit IRC | 19:54 | |
| anotherjesse | jeblair: make more sense? | 19:54 |
| anotherjesse | jeblair: I can show you how to manually run the node classifier on the djeep server | 19:54 |
| anotherjesse | djeep doesn't even have to be running after it writes the yaml files - it is pure puppet | 19:54 |
| jaypipes | anotherjesse: they are formulating their response :) | 19:55 |
| * jaypipes happy we are finally getting to the nitty gritty :) | 19:55 | |
| anotherjesse | jaypipes: sorry for the sploid | 19:55 |
| jaypipes | hey, no worries, this is exactly what I was hoping for. | 19:56 |
| jeblair | for the moment, i don't think we need to change the configuration, right? | 19:56 |
| jaypipes | these are precisely the conversations we need to have. | 19:56 |
| anotherjesse | in our master we set: | 19:56 |
| anotherjesse | [master] | 19:56 |
| anotherjesse | node_terminus = exec | 19:56 |
| anotherjesse | external_nodes = /root/djeep/etc/puppet/node_classes.py | 19:56 |
| jeblair | so we don't need to re-run the node classifier | 19:56 |
| anotherjesse | jeblair: node classifier is a way for puppet master to not have a sitepp | 19:56 |
| jeblair | i guess what i was trying to say is that we can leave the djeep configuration static for the time being | 19:58 |
| *** ecarlin has quit IRC | 19:59 | |
| *** Atul has quit IRC | 19:59 | |
| *** ecarlin has joined #openstack-meeting | 19:59 | |
| anotherjesse | jeblair: here is an example of output: | 19:59 |
| anotherjesse | http://paste.openstack.org/show/2259/ | 19:59 |
| anotherjesse | sanitized | 19:59 |
| jbryce | meeting time is almost up. = ) | 19:59 |
| anotherjesse | if site.pp wants to hardcode 356602-staging-cpu2 to have various global variables and classes you can | 20:00 |
| anotherjesse | it just is VERY verbose | 20:00 |
| anotherjesse | having a simple classifier is much easier | 20:00 |
| bengrue | Were there non-open-discussion topics that needed to be discussed? | 20:00 |
| mtaylor | out of time | 20:00 |
| mtaylor | :) | 20:00 |
| anotherjesse | we can continue in #dev | 20:00 |
| bengrue | Let's. | 20:00 |
| jaypipes | anotherjesse, jeblair: please do continue in #dev... | 20:00 |
| jeblair | i'll dig more into puppet and ask anotherjesse with questions | 20:00 |
| *** zns has joined #openstack-meeting | 20:01 | |
| mtaylor | thanks guys! easily the densest ci meeting we've had in a while! | 20:01 |
| mtaylor | #endmeeting | 20:01 |
| *** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/" | 20:01 | |
| openstack | Meeting ended Tue Aug 23 20:01:31 2011 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 20:01 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-08-23-19.04.html | 20:01 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-08-23-19.04.txt | 20:01 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-08-23-19.04.log.html | 20:01 |
| *** kris3968_ has joined #openstack-meeting | 20:01 | |
| *** Atul has joined #openstack-meeting | 20:02 | |
| *** kris3968_ has quit IRC | 20:03 | |
| *** kris3968 has joined #openstack-meeting | 20:03 | |
| jbryce | #startmeeting | 20:04 |
| openstack | Meeting started Tue Aug 23 20:04:09 2011 UTC. The chair is jbryce. Information about MeetBot at http://wiki.debian.org/MeetBot. | 20:04 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 20:04 |
| *** kris3968_ has joined #openstack-meeting | 20:04 | |
| jbryce | who's around? | 20:05 |
| notmyname | hi | 20:05 |
| johnpur | o/ | 20:05 |
| soren | o/ | 20:05 |
| jaypipes | o/ | 20:05 |
| danwent | hi jbryce, I'm here about quantum's incubation proposal | 20:05 |
| jsavak | hi | 20:05 |
| anotherjesse | not me | 20:05 |
| zns | ziad | 20:05 |
| jaypipes | danwent: denied. all done! ;P | 20:05 |
| danwent | :P | 20:05 |
| soren | aw. | 20:06 |
| ttx | o/ | 20:06 |
| vishy | o/ | 20:06 |
| jbryce | ok | 20:06 |
| jbryce | lots to cover today: http://wiki.openstack.org/Governance/PPB | 20:06 |
| *** joshuamckenty_ has joined #openstack-meeting | 20:06 | |
| *** kris3968_ has left #openstack-meeting | 20:07 | |
| jbryce | #topic keystone update | 20:07 |
| *** openstack changes topic to "keystone update" | 20:07 | |
| zns | 1. API spec published | 20:07 |
| jbryce | zns: can you give us an update on the progress of the api lockdown? | 20:07 |
| zns | Service (Public) API:Â https://github.com/openstack/keystone/blob/master/keystone/content/service/identitydevguide.pdf | 20:07 |
| zns | Admin (Private/Privileged) API:Â https://github.com/openstack/keystone/raw/master/keystone/content/admin/identityadminguide.pdf | 20:07 |
| zns | WADLs/XSD all available in the keystone/content folders in the source code | 20:07 |
| zns | 2. I'm working with core teams on integration. Just got of the phone with SandyWalsh. | 20:07 |
| jaypipes | anything in HTML? :) | 20:07 |
| zns | 3. Issues list import into Launchpad is waiting on Launchpad to do the import. | 20:07 |
| *** kris3968 has quit IRC | 20:07 | |
| zns | We're working on refactoring to meet that spec now. | 20:07 |
| *** ewanmellor has joined #openstack-meeting | 20:08 | |
| jbryce | joshuamckenty_, ewanmellor: we just got started; talking about keystone right now | 20:08 |
| zns | It compiles to HTML. But we don't have it published yet. We can work with Anne on that. | 20:08 |
| ewanmellor | Namaste | 20:08 |
| *** mattray1 has quit IRC | 20:08 | |
| jbryce | anotherjesse: does the published api make you feel better about the external stability of keystone? | 20:09 |
| zns | jaypipes: i.e. if you download the source from openstack-manuals, there is a webhelp folder with the HTML. | 20:09 |
| anotherjesse | jbryce: browsing it | 20:09 |
| jbryce | zns: thanks for the comprehensive update. you were ready! = ) | 20:10 |
| nati | o/ | 20:10 |
| zns | jbryce: You guys set a high bar :-) | 20:10 |
| anotherjesse | zns: what is tate of implementation of it? | 20:10 |
| anotherjesse | is the doc what is implemented? | 20:10 |
| dendrobates | sorry I'm late | 20:11 |
| zns | We're working on that now. Biggest change is the move from using username as identifier to supporting a UID. But the spec is now much smaller so implementation should be pretty quick. | 20:12 |
| nati | Wow these docs helps me a lot! | 20:12 |
| zns | And we need to move the management calls to RAX or OS extensions. | 20:12 |
| zns | anotherjesse: Not sure I answered your question. What metric would you like? | 20:13 |
| anotherjesse | zns: maybe a simple one - of when you think the core api will be finished implementation (and then maybe for extensions if reasonable to guestimate) | 20:14 |
| vishy | we need a locked version for d4 | 20:15 |
| zns | We should have it working by the end of the week. Code compiles and passes tests now and will continue to do so throughout. What we need to coordinate is changes to the middleware with the other core projects (since the middleware is now in their code). | 20:15 |
| jaypipes | zns: perhaps I'm missing something, but I'm not seeing API calls for POST /users/<ID>/roles? How does one add a user to a role through the admin API? | 20:15 |
| jbryce | vishy, anotherjesse: is that a component of a core promotion decision? again, the core promotion is really saying it would be a core project for essex, not for diablo. | 20:16 |
| anotherjesse | jbryce: but we can use these to put pressure on them to work faster ;) | 20:16 |
| zns | jaypipes: if you use our reference implementation, you would either use an extension or keystone-manage. If you're using something else, like Active Directory, then that's managed using the Active Directory tools. We're leaving the management out of the core API... | 20:16 |
| zns | jaypipes: the extension will be OS-KSADMIN. Separate WADL and XSDs. | 20:17 |
| *** kris3968 has joined #openstack-meeting | 20:17 | |
| jaypipes | zns: KSADMIN? | 20:17 |
| jaypipes | ah, Keystone... | 20:17 |
| anotherjesse | keith stone? | 20:17 |
| zns | Keystone Admin extensions. | 20:17 |
| *** kris3968 has left #openstack-meeting | 20:17 | |
| jaypipes | thought might be a typo for RSADMIN.... | 20:17 |
| jbryce | anotherjesse: +1, rename in order | 20:18 |
| zns | anotherjesse: don't start that meme again! | 20:18 |
| jsavak | lol | 20:18 |
| anotherjesse | zns: sorry - haven't slept much | 20:18 |
| jbryce | last week we decided to defer a vote and wait for an update on the feedback we'd given. we can either defer again to next week (last chance before 2011-09-05 deadline) or vote today | 20:18 |
| jaypipes | ok, so jbryce are we voting for promotion again today? | 20:18 |
| jaypipes | jinx. | 20:19 |
| zns | We'll have RAX extensions as well. | 20:19 |
| zns | … to support API key authentication | 20:19 |
| jbryce | i'd prefer to vote unless anyone feels strongly they have specific items to block until next week on | 20:20 |
| notmyname | indeed (and we have much else to discuss) | 20:20 |
| jbryce | #info VOTE: Should Keystone be accepted as a core project for Essex release cycle? | 20:21 |
| jaypipes | +1 | 20:21 |
| jbryce | +1 | 20:21 |
| jsavak | +1 | 20:21 |
| vishy | +1 | 20:21 |
| johnpur | +1 | 20:21 |
| ttx | +1 | 20:21 |
| dendrobates | +1 | 20:21 |
| soren | +1 | 20:21 |
| notmyname | +1 | 20:21 |
| anotherjesse | +1 | 20:21 |
| jaypipes | well that was easy... | 20:21 |
| jbryce | #agreed Keystone will be core for Essex (9 +, 2 abstain) | 20:21 |
| zns | Cool! | 20:21 |
| zns | Thanks, guys. | 20:22 |
| anotherjesse | zns: are you off to drink? | 20:22 |
| jbryce | congrats zns! | 20:22 |
| *** mdomsch has quit IRC | 20:22 | |
| jbryce | #topic Security Group Proposal take 2 | 20:22 |
| *** openstack changes topic to "Security Group Proposal take 2" | 20:22 | |
| jbryce | http://wiki.openstack.org/Governance/Proposed/OpenStack%20Security%20Group | 20:22 |
| ttx | zns: now the pain begins. | 20:22 |
| anotherjesse | zns: disneyland! | 20:22 |
| zns | More like off to work! | 20:22 |
| ttx | zns: I'll be your worst nightmare. | 20:22 |
| jbryce | ttx worked with jarret to update with our feedback | 20:22 |
| zns | ttx: I'll get to practice my French. | 20:23 |
| jbryce | the gist is that it is now split into a small vulnerability management team and a larger security testing etc team | 20:23 |
| ttx | basically it keeps the vulnerability treatment team small. Without preventing the set up of a large security interest group. | 20:23 |
| notmyname | jbryce: are we discussing it in toto or the 2 parts separately? | 20:23 |
| ttx | notmyname: we can do two parts, if there is a good reason to | 20:24 |
| jbryce | if we only want to approve one part that's fine | 20:24 |
| jbryce | i would like to discuss both though | 20:24 |
| notmyname | I like the first part (management team) and would prefer to defer ont he second | 20:24 |
| ttx | the first part is what's urgent | 20:24 |
| jbryce | ok. let's vote on the first part, because i think that's more time sensitive and agreed to already | 20:24 |
| ttx | (in order to have a team responsible for setting up the security info pages. quick) | 20:24 |
| jbryce | the first part being the "Vulnerability Management Team" heading on the page | 20:25 |
| jaypipes | I'm with notmyname | 20:25 |
| nati | +1 | 20:25 |
| nati | Oh too late | 20:25 |
| ttx | any issue with that first part ? | 20:25 |
| soren | No, sounds good. | 20:25 |
| jbryce | #info VOTE: Should we establish a vulnerability management team? | 20:25 |
| ewanmellor | +1 | 20:26 |
| jaypipes | +1 | 20:26 |
| joshuamckenty_ | +1 | 20:26 |
| jbryce | +1 | 20:26 |
| notmyname | as defined in that doc? | 20:26 |
| jbryce | notmyname: yes | 20:26 |
| ttx | note that core devs will have access to security bugs in LP. | 20:26 |
| notmyname | +1 | 20:26 |
| nati | +1 | 20:26 |
| johnpur | +1 | 20:26 |
| jaypipes | a SMALL vulnerability management team... | 20:26 |
| vishy | +1 | 20:26 |
| ttx | +1 | 20:26 |
| dendrobates | +1 | 20:26 |
| anotherjesse | -1 … we have no vulnerabilitys | 20:26 |
| jaypipes | lol :) | 20:26 |
| anotherjesse | joke - +1 | 20:26 |
| soren | +1 | 20:26 |
| johnpur | Jesse is in rare form! | 20:26 |
| vishy | can we add jesse as a vulnerability? | 20:26 |
| joshuamckenty_ | No | 20:26 |
| jbryce | #agreed Establish small vulnerability management team. (11 +) | 20:26 |
| jbryce | #action jbryce split out the vulnerability management paragraph into a separate document | 20:27 |
| jbryce | does anyone want to discuss the larger concept of the openstack security group now? | 20:27 |
| ttx | that can wait if we have more pressing matters | 20:27 |
| notmyname | I see no need | 20:27 |
| soren | Nor do I. | 20:27 |
| soren | People can form whatever groups they want. | 20:28 |
| notmyname | soren: +1 | 20:28 |
| soren | THere's no need for ppb blessing. | 20:28 |
| jbryce | are we fine if jarret moves forward along a path like he laid out there without official sanction | 20:28 |
| jbryce | soren: i agree | 20:28 |
| jaypipes | sure | 20:28 |
| jbryce | ok | 20:28 |
| notmyname | jbryce: as long as it's not presented as binding for openstack | 20:28 |
| anotherjesse | jbryce: I would like to put a requirement that the website gets updated | 20:28 |
| ttx | notmyname, soren: that's a fair point. | 20:28 |
| anotherjesse | to have a security link at the obttom of openstack pages | 20:28 |
| Daviey | I have been concerned that it seems nobody has been primarily tasked with just security auditing AIUI. | 20:28 |
| jbryce | #action jbryce to make sure security link makes it into openstack web property footers | 20:29 |
| jbryce | #info openstack security group can form informally with interested parties without official sanction | 20:29 |
| jaypipes | Daviey: nothing stopping a working group from being formed. | 20:29 |
| jbryce | Daviey: i think jarret is interested in forming that kind of group | 20:29 |
| ttx | we don't want to set a precedent that any discussion group needs to go through PPB | 20:29 |
| notmyname | ttx: +1000 | 20:30 |
| Daviey | jbryce: Good stuff. | 20:30 |
| jbryce | devcamcar: you around? | 20:30 |
| jbryce | danwent: still here? | 20:30 |
| ttx | if the group gets any privilege or special power, I see why it needs to be blessed by PPB. If not, then just form it[tm] | 20:30 |
| danwent | ready and waiting :) | 20:30 |
| johnpur | ttx: how about a legal working group? | 20:31 |
| jbryce | we'll circle back to dashboard if devcamcar is here | 20:31 |
| jbryce | #topic Quantum incubation | 20:31 |
| *** openstack changes topic to "Quantum incubation" | 20:31 | |
| ttx | johnpur: if its decisions are not binding the rest of the community, they can gather and discuss all they want. | 20:32 |
| jbryce | http://wiki.openstack.org/Projects/IncubatorApplication/Quantum | 20:32 |
| jbryce | quantum would like to become an incubated project | 20:32 |
| johnpur | ttx: i see it as an advisory group to ppb and governance issues | 20:32 |
| dendrobates | since I have been involved with quantum. should I recuse myself? | 20:32 |
| *** msinhore1 has joined #openstack-meeting | 20:33 | |
| *** jmckenty has joined #openstack-meeting | 20:33 | |
| devcamcar | o/ | 20:33 |
| soren | dendrobates: I don't think so. | 20:33 |
| anotherjesse | dendrobates: I was involved with keystone - and was a harsh critic of acceptance to core (sorry zns - just want it to be ready) | 20:34 |
| jbryce | dendrobates: i don't have a problem with your involvement | 20:34 |
| dendrobates | k | 20:34 |
| danwent | we're happy to answer any questions about quantum | 20:34 |
| anotherjesse | so - just put your opensource hat on and you will be a good person in the conversation | 20:34 |
| dendrobates | anotherjesse: It's the only hat I own | 20:35 |
| *** Tushar has joined #openstack-meeting | 20:35 | |
| Daviey | dendrobates: Can you see a time when quantum is likely to become a required part of openstack networking? | 20:35 |
| dendrobates | Daviey: I personally don't think it should ever be required | 20:35 |
| anotherjesse | dendrobates / danwent quantum works as well as existing model - but can you just use quantum and not existing models (eg is there the overlap?) | 20:36 |
| dendrobates | not for simple pilots or testing at least | 20:36 |
| danwent | +1 quantum is really about being able to take advantage of more advanced network functionality. | 20:36 |
| notmyname | danwent: so is it an abstraction of swift/router APIs? | 20:36 |
| anotherjesse | dendrobates / danwent if nova devs want to deprecate nova-network what do we lose? | 20:36 |
| notmyname | switch | 20:36 |
| *** jmckenty has left #openstack-meeting | 20:36 | |
| Daviey | dendrobates: What i am asking is, does it make sense for it to potentially superseed FlatManager and VlanManager ? | 20:36 |
| Daviey | (in production enviroments) | 20:37 |
| anotherjesse | dendrobates: what Daviey said | 20:37 |
| danwent | anotherjesse: if you're using quantum, we have a model that works well with the existing nova-manage commands (i.e., when you create a network with nova-manage, we create a quantum network on the backend). But yes, you would either use quantum, or the old bridge model. | 20:37 |
| dendrobates | anotherjesse: the ability to get test nova without installing quantum | 20:37 |
| *** msinhore has quit IRC | 20:37 | |
| danwent | notmyname: not related to swift at all. | 20:37 |
| *** jmckenty_ has joined #openstack-meeting | 20:37 | |
| notmyname | danwent: ya, mistype. muscle memory. I meant switch | 20:37 |
| dendrobates | Daviey: I think that is really a decision for Nova | 20:37 |
| dendrobates | I think it could | 20:37 |
| *** msinhore1 has quit IRC | 20:37 | |
| danwent | anotherjesse: nova-network still handles some things that are not done by quantum (e.g., deciding which vNICs a VM gets) | 20:38 |
| anotherjesse | dendrobates: for keystone integration we deprecated the existing user system and have a simple "noauth - eg trust whoever the user says they are" | 20:38 |
| anotherjesse | dendrobates: could / should we do something like that for quantum as it matures | 20:38 |
| *** msinhore has joined #openstack-meeting | 20:38 | |
| *** msinhore has quit IRC | 20:38 | |
| danwent | in general, I think it would make sense to simplify nova networking in the future, to just support a simple standalone model similar to flatmanager | 20:38 |
| dendrobates | anotherjesse: true, we did not want to assume that though | 20:38 |
| danwent | notmyname: yes | 20:39 |
| *** msinhore has joined #openstack-meeting | 20:39 | |
| anotherjesse | dendrobates: awesome | 20:39 |
| danwent | model is basically that you can define "networks" that correspond to an L2 domain, and "ports" on those L2 domains. | 20:39 |
| danwent | in the future we will explore L3, but right now the core API is only about L2 connectivity. | 20:39 |
| Daviey | dendrobates / danwent: I've struggled to work out how much i should care about Quantum, would it be possible to make better docs (or screencast), and help with the visability of those? | 20:39 |
| danwent | anotherjesse: yes, I think that's the right approach. | 20:39 |
| danwent | Daviey: I have been meaning to do a screencast for some time. | 20:40 |
| *** alandman has joined #openstack-meeting | 20:40 | |
| Daviey | rocking | 20:40 |
| anotherjesse | danwent: PLEASE DO THAT! (screencast) | 20:40 |
| jbryce | we're talking about incubation for quantum here, (not core) so the evaluation criteria are really around if we think this has a part as a potential core openstack project, is it at a point that it has code and developers and should start on the path for integration | 20:40 |
| anotherjesse | danwent: we started using / giving feedback on keystone since the beginning - should nova core as part of incubation get serious about using/knowing qauntum? | 20:40 |
| danwent | Daviey: the real pain point is for customers that need to be able use advanced network capabilities, whereas the existing nova networking is pretty tied to basic linux bridge + vlan capabilities | 20:40 |
| ttx | anotherjesse: if quantum gets in incubation before the design summit, we can set up sessions to discover the code base | 20:41 |
| dendrobates | Quantum has a very healthy and diverse dev community and a good leader in danwent | 20:41 |
| ttx | danwent++ | 20:41 |
| danwent | anotherjesse: so far we've been focused on building the core quantum service, just in the d4 timeline have we started focusing on nova integration in earnest. We've prototyped that with a QuantumManager class that replaces FlatManager, etc. | 20:41 |
| danwent | we're definitely happy for input from any nova team members. | 20:42 |
| anotherjesse | dendrobates: for dashboard we thought that having the openstack apis in place was important for incubation | 20:42 |
| anotherjesse | dendrobates: is there anything you think should be done before incubation with quantum? | 20:42 |
| anotherjesse | danwent: to kick the tires do I need anything more than a cluster? | 20:43 |
| notmyname | danwent: how autonomous is quantum? is it possible to deploy quantum without nova (or another openstack project)? | 20:43 |
| jaypipes | yes, I'm interested in the answer to that, too... notmyname's question... | 20:43 |
| danwent | anotherjesse: its pretty simple. for example, you can check out the tutorial demo I sent out to the the list (I will dig up the link) | 20:43 |
| *** joshuamckenty_ has quit IRC | 20:43 | |
| Daviey | This is screaming for a "how to test" blog post :) | 20:43 |
| dendrobates | anotherjesse: I think it is in pretty good shape for incubation | 20:43 |
| devcamcar | anotherjesse: quantum ui for dashboard is in code review right now | 20:43 |
| Daviey | danwent: Anyone driving dashboard integration? | 20:43 |
| devcamcar | will land probably in next few days | 20:43 |
| devcamcar | Daviey: ^^^ | 20:44 |
| Daviey | bah | 20:44 |
| markvoelker | Daviey: yes, asomya from my team is leading that | 20:44 |
| anotherjesse | devcamcar: saw that .. jake said it didn't use the extension model at first - is that important? (we can discuss in #dev) | 20:44 |
| jbryce | it actually seems like it is pretty mature for just entering incubation | 20:44 |
| devcamcar | anotherjesse: no | 20:44 |
| danwent | Daviey: yes, mark voelkers team from cisco is working on dashboard integration | 20:44 |
| dendrobates | jbryce: we held it out early on | 20:44 |
| dendrobates | jbryce: while the pbb wrestled with the policies | 20:44 |
| danwent | on being stand-alone, yes, quantum is a separate process that can run with nova. but nova is the only openstack service that we have integrated with so far. | 20:45 |
| anotherjesse | danwent: does the api follow a similar rest with openstack auth approach? | 20:45 |
| danwent | Daviey: I actually sent a link out for that to the list last week. will dig it up. | 20:45 |
| danwent | anotherjesse: yes, very much so | 20:45 |
| dendrobates | other iaas solutions have expressed interest in using quantum as well, so nothing to nova specific has been done | 20:45 |
| danwent | http://wiki.openstack.org/QuantumAPISpec | 20:46 |
| anotherjesse | looks squeeky clean to me - /me is excited to test it out once diablo is shipped | 20:46 |
| jbryce | i'm not hearing any huge blockers here and we're running low on time, so unless anyone objects, i'd like to vote | 20:46 |
| *** blamar_ has quit IRC | 20:46 | |
| anotherjesse | agree | 20:46 |
| anotherjesse | +1 | 20:46 |
| jaypipes | indeed. ++ for wiki API docs. | 20:46 |
| vishy | +1 | 20:46 |
| dendrobates | +1 | 20:46 |
| danwent | here's the link to a tutorial based on vish's script: http://wiki.openstack.org/QuantumOVSDemo | 20:46 |
| jbryce | #info VOTE: Should Quantum be accepted as an OpenStack Incubation project | 20:46 |
| jaypipes | +1 | 20:46 |
| johnpur | +1 | 20:46 |
| ewanmellor | +1 | 20:46 |
| jbryce | +1 | 20:46 |
| *** Shubhangi has joined #openstack-meeting | 20:46 | |
| notmyname | -1 | 20:46 |
| soren | +1 | 20:46 |
| ttx | +1 | 20:47 |
| anotherjesse | notmyname: reason? | 20:47 |
| jmckenty_ | +0 | 20:47 |
| notmyname | I've been burned by sitting on the fence before. I'd prefer not to +0 | 20:47 |
| *** joesavak has quit IRC | 20:47 | |
| anotherjesse | heh | 20:47 |
| jbryce | #agreed Quantum will be accepted for OpenStack incubation (9+, 1 abstain, 1-) | 20:47 |
| *** jsavak has quit IRC | 20:47 | |
| ewanmellor | #link Quantum dashboard integration: http://wiki.openstack.org/QuantumClientGUI | 20:47 |
| danwent | notmyname: definitely let me know if you have suggestions for improving the project | 20:47 |
| danwent | great, on behalf of the quantum team, thanks! | 20:48 |
| jbryce | thanks danwent, dendrobates | 20:48 |
| *** pballand has joined #openstack-meeting | 20:48 | |
| jbryce | #topic Dashboard core promotion | 20:48 |
| *** openstack changes topic to "Dashboard core promotion" | 20:48 | |
| ttx | in 12 min :) | 20:48 |
| devcamcar | i'll type fast :) | 20:48 |
| jmckenty_ | nice | 20:48 |
| jbryce | devin would like us to consider promoting Dashboard to a core project for the Essex release cycle | 20:48 |
| jbryce | if we can't get through it all today, we have one more week to vote on it before the deadline | 20:49 |
| *** novas0x2a|laptop has joined #openstack-meeting | 20:49 | |
| jbryce | but does anyone have any questions objections for devcamcar to start with? | 20:49 |
| devcamcar | i can give a quick overview of where it's at now as well if that would help | 20:49 |
| dendrobates | devcamcar: do you know of any other competing dashboard initiatives for openstack? | 20:49 |
| notmyname | what's the status of using standard tools/processes? | 20:49 |
| devcamcar | dendrobates: no | 20:49 |
| notmyname | devcamcar: what's the status of using standard tools/processes? | 20:49 |
| notmyname | LP, gerrit, etc | 20:50 |
| devcamcar | notmyname: we use launchpad for release management, bug tracking, blueprints, github for code, but we have not moved to gerrit but plan to do so soon | 20:50 |
| *** mencken has joined #openstack-meeting | 20:50 | |
| jmckenty_ | test coverage? | 20:50 |
| anotherjesse | devcamcar: you already do +1 for code reviews before merge though right? | 20:50 |
| devcamcar | notmyname: and follow milestones and release dates according to openstack proper | 20:50 |
| anotherjesse | err +2 | 20:50 |
| devcamcar | anotherjesse: yes | 20:51 |
| devcamcar | jmckenty: test coverage has been -greatly- improved in past few months | 20:51 |
| anotherjesse | devcamcar: I still think the name needs to be cooler for promotion to core | 20:51 |
| devcamcar | we have coverage reports as well | 20:51 |
| anotherjesse | nova, glance, swift, quantum keystone .. and dashboard? | 20:51 |
| *** somik has joined #openstack-meeting | 20:51 | |
| termie_ | dishrack | 20:51 |
| devcamcar | anotherjesse: i always have called it dash but that was taken on lp ;) | 20:51 |
| *** termie_ is now known as termie | 20:51 | |
| *** termie has joined #openstack-meeting | 20:51 | |
| ttx | "dash" is pretty overloaded. | 20:52 |
| johnpur | anotherjesse: +1 | 20:52 |
| vishy | hud! | 20:52 |
| zns | windows :-) | 20:52 |
| Daviey | Currently the dashboard is OSAPI centric, is anyone (and is it viable) to support ec2 elements? | 20:52 |
| *** edgarmagana has joined #openstack-meeting | 20:52 | |
| jaypipes | mrs. dash? | 20:52 |
| Daviey | Such as differeing crednetials? | 20:52 |
| anotherjesse | devcamcar: I'm going to owe you a whiskey if I get dashboard voted down due to naming ... | 20:52 |
| soren | instrumentbræt | 20:52 |
| soren | (dashboard in Danish) | 20:53 |
| devcamcar | Daviey: OS API vs EC2 API is more about what the guts of it use to communicate with the nova and glance pieces | 20:53 |
| vishy | trifle | 20:53 |
| jaypipes | pinch | 20:53 |
| jmckenty_ | braet is hard to type | 20:53 |
| vishy | smidge! | 20:53 |
| jmckenty_ | amudge? | 20:53 |
| soren | jmckenty_: You just hit the æ key. Easy. | 20:53 |
| devcamcar | Daviey: its more about feature support, and OS API has caught up to EC2 API in diablo | 20:53 |
| ewanmellor | soren: you don't even bother to spell your own name properly most of the time! | 20:53 |
| *** rohita has joined #openstack-meeting | 20:53 | |
| jbryce | does this mean we have no more substantive issue to discuss with it? = ) | 20:53 |
| anotherjesse | can we accept but with a new name to be determined later ? | 20:54 |
| soren | jmckenty_: Or compose+a+e. | 20:54 |
| Daviey | devcamcar: But the OSAPI doesn't expose EC2 credentials, (yet) :) | 20:54 |
| anotherjesse | if so - vote | 20:54 |
| jbryce | correct | 20:54 |
| soren | ewanmellor: Fair point :) | 20:54 |
| ttx | æ. | 20:54 |
| anotherjesse | Daviey: we are still adding those to nova & keystone | 20:54 |
| anotherjesse | Daviey: it will | 20:54 |
| Daviey | Ah, good stuff. | 20:54 |
| jbryce | #info VOTE: Should Dashboard be promoted to core for Essex release cycle? | 20:54 |
| vishy | Daviey: yes that should be a bug | 20:54 |
| anotherjesse | if there is a ec2 extension in keystone | 20:54 |
| jmckenty_ | devcamcar: is there a commitment | 20:54 |
| ewanmellor | +1 | 20:54 |
| soren | +1 | 20:54 |
| jmckenty_ | to keep dashboard up to partiy with the full OS API? | 20:54 |
| jbryce | +1 | 20:54 |
| vishy | +1 | 20:54 |
| anotherjesse | +1 | 20:55 |
| devcamcar | jmckenty_: that is absolutely the goal | 20:55 |
| jmckenty_ | +1 then | 20:55 |
| johnpur | +1 | 20:55 |
| ttx | +1 | 20:55 |
| anotherjesse | with a qualification that dash(board) isn't the name | 20:55 |
| * vishy hopes that these things becoming core will make them much easier to install | 20:55 | |
| jmckenty_ | +1 on a better name | 20:55 |
| jaypipes | -1 | 20:55 |
| anotherjesse | swift and dash are too close | 20:55 |
| devcamcar | anotherjesse: agreed! we will name it while drinking whiskey | 20:55 |
| * jmckenty_ promises to give vishy his installer | 20:55 | |
| *** rohita has quit IRC | 20:55 | |
| vishy | wait | 20:55 |
| vishy | can we call it whiskey? | 20:55 |
| jmckenty_ | devcamcar: add a session for boston for naming? | 20:55 |
| jmckenty_ | OOH | 20:55 |
| devcamcar | oo | 20:55 |
| jmckenty_ | bourbon | 20:55 |
| vishy | that is genius | 20:55 |
| devcamcar | haha | 20:56 |
| jmckenty_ | bourbon is the official drink of cloud, though | 20:56 |
| ttx | jaypipes: rationale ? | 20:56 |
| *** rohitagarwalla has joined #openstack-meeting | 20:56 | |
| devcamcar | jmckenty_: +1 | 20:56 |
| jbryce | #agreed Dashboard will be promoted to OpenStack core for Essex release cycle (8+, 2 abstain, 1-) | 20:56 |
| *** edconzel has joined #openstack-meeting | 20:56 | |
| jaypipes | ttx: same as my rationale for voting -1 for incubation to core :) | 20:56 |
| jaypipes | ttx: I don't think it's a core project ;) | 20:56 |
| ttx | jaypipes: you hate css ? | 20:56 |
| jaypipes | ttx: it's awesome, just don't consider it in the same vein. | 20:56 |
| jaypipes | ttx: just being consistent. | 20:56 |
| jbryce | congrats, devin | 20:56 |
| ttx | jaypipes: ack | 20:56 |
| bengrue | (whiskey would get confused with wsgi in conversation; bourbon is unambiguous.) | 20:56 |
| jbryce | #topic open discussion | 20:57 |
| *** openstack changes topic to "open discussion" | 20:57 | |
| *** jrouault has joined #openstack-meeting | 20:57 | |
| jaypipes | bengrue: hehe, good point. | 20:57 |
| ttx | devcamcar: welcome to hell too. | 20:57 |
| anotherjesse | summit registration! | 20:57 |
| devcamcar | hooray! | 20:57 |
| jbryce | anyone want to hit on anything in the last 2 minutes, 30 seconds? | 20:57 |
| notmyname | jaypipes: +1 | 20:57 |
| *** jrouault has quit IRC | 20:57 | |
| bengrue | summit registration! | 20:57 |
| ttx | anotherjesse: dude, don't steal my effects :) | 20:57 |
| anotherjesse | ttx: sorry - just excited about http://summit.openstack.org/ | 20:57 |
| jbryce | haha | 20:57 |
| *** jrouault has joined #openstack-meeting | 20:57 | |
| jbryce | anotherjesse: that's kind of wrong | 20:57 |
| jmckenty_ | jbryce: I've got a FITs framework doc coming together | 20:57 |
| soren | jaypipes: Would it be a fair summary to say that in your terminology "core" means (near) bottom of the stack? | 20:57 |
| *** pballand is now known as _nobody_ | 20:57 | |
| jmckenty_ | Will have a draft on the wiki for next week | 20:57 |
| * ttx must resist sudo apache2ctl stop | 20:57 | |
| jaypipes | soren: yes, I guess os. | 20:58 |
| jaypipes | so. | 20:58 |
| jbryce | jmckenty_: cool, sounds good | 20:58 |
| *** Tushar has quit IRC | 20:58 | |
| soren | ttx: There you have it ^ | 20:58 |
| vishy | can we put api discussion on the docket for next time | 20:58 |
| jmckenty_ | yes please | 20:58 |
| jmckenty_ | +1 for API discussion | 20:58 |
| anotherjesse | jmckenty_: with the FITs - is it online already? | 20:58 |
| jbryce | #action jbryce to add API discussion to next week's agenda | 20:58 |
| jmckenty_ | google doc, I'll share it when I'm sure it's not inflammatory | 20:58 |
| jmckenty_ | :) | 20:58 |
| *** _nobody_ is now known as pballand | 20:59 | |
| anotherjesse | jmckenty_: hmm - next month or ? | 20:59 |
| jbryce | he said next week | 20:59 |
| jbryce | thanks, everyone! | 20:59 |
| jmckenty_ | yup | 20:59 |
| *** pem has joined #openstack-meeting | 20:59 | |
| jbryce | #endmeeting | 20:59 |
| *** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/" | 20:59 | |
| openstack | Meeting ended Tue Aug 23 20:59:48 2011 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 20:59 |
| jmckenty_ | ktnxbye | 20:59 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-08-23-20.04.html | 20:59 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-08-23-20.04.txt | 20:59 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-08-23-20.04.log.html | 20:59 |
| ttx | jbryce: perfect timing | 21:00 |
| *** pem is now known as Guest75429 | 21:00 | |
| jbryce | ttx: can't believe we got through all that... | 21:00 |
| jaypipes | jbryce: I know :) | 21:00 |
| *** bcwaldon has joined #openstack-meeting | 21:00 | |
| jaypipes | jbryce: must be a record... | 21:00 |
| danwent | jbryce: much appreciated | 21:00 |
| ttx | jbryce: At this point in this day I'd agree to anything. | 21:00 |
| jbryce | haha | 21:00 |
| *** Vek has joined #openstack-meeting | 21:01 | |
| ttx | vishy, notmyname: still around ? | 21:01 |
| notmyname | hi | 21:01 |
| *** alandman has quit IRC | 21:01 | |
| vishy | y | 21:02 |
| ttx | let's get started | 21:02 |
| ttx | #startmeeting | 21:02 |
| openstack | Meeting started Tue Aug 23 21:02:11 2011 UTC. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 21:02 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 21:02 |
| *** cynb has joined #openstack-meeting | 21:02 | |
| ttx | Welcome to our weekly team meeting... Today's agenda is at: | 21:02 |
| ttx | #link http://wiki.openstack.org/Meetings/TeamMeeting | 21:02 |
| *** jamesurquhart has joined #openstack-meeting | 21:02 | |
| ttx | #topic Actions from previous meeting | 21:02 |
| *** openstack changes topic to "Actions from previous meeting" | 21:02 | |
| ttx | * notmyname to double check that everything is included in https://launchpad.net/swift/+milestone/1.4.3 | 21:02 |
| ttx | In progress ? | 21:02 |
| notmyname | done. if anything else comes up, it wll be added | 21:03 |
| ttx | cool. | 21:03 |
| ttx | * vishy to reprioritize admin-account-actions which is likely to miss diablo | 21:03 |
| ttx | We'll talk about that one in the Nova topic | 21:03 |
| ttx | * jk0 to push new dep email policy to ML | 21:03 |
| *** mdomsch has joined #openstack-meeting | 21:03 | |
| ttx | That was done, nobody complained... | 21:03 |
| glenc | yet | 21:04 |
| ttx | I think for history we should put such decisions on the wiki somewhere | 21:04 |
| ttx | so that we can blame newcomers that haven't read it. | 21:04 |
| notmyname | dep email policy? | 21:04 |
| Vek | change dependencies, send email | 21:04 |
| ttx | notmyname: warn about new deps by email | 21:04 |
| ttx | to the ML | 21:04 |
| *** comstud_ has joined #openstack-meeting | 21:05 | |
| ttx | so that downstreams can fix their packaging. | 21:05 |
| notmyname | ok :-) just wondering what "deps" was in this context :-) | 21:05 |
| ttx | #topic Swift status | 21:05 |
| *** openstack changes topic to "Swift status" | 21:05 | |
| ttx | notmyname: Anything on your mind ? | 21:05 |
| notmyname | nothing much to report with the code | 21:05 |
| notmyname | I'll be speaking in San Francisco on Sept 8 http://www.meetup.com/openstack/events/30605231/ | 21:05 |
| *** msinhore1 has joined #openstack-meeting | 21:06 | |
| ttx | notmyname: that's a crowded week :) | 21:06 |
| *** spectorclan_ has joined #openstack-meeting | 21:06 | |
| notmyname | I'm working with mtaylor and jeblair about moving to gerrit. I don't think we have a timeline yet. just "soon" | 21:07 |
| ttx | Raise your hand if you have questions on Swift... | 21:07 |
| *** Shubhangi has quit IRC | 21:07 | |
| *** kris3968 has joined #openstack-meeting | 21:07 | |
| ttx | #topic Glance status | 21:07 |
| *** openstack changes topic to "Glance status" | 21:07 | |
| ttx | jaypipes: o/ | 21:07 |
| ttx | jaypipes: I'd like to review the missed features and decide between deferring to Essex and granting a post-D4 exception | 21:07 |
| ttx | (The idea being to minimize the changes as we get nearer to release. The Essex gates will open on September 8, so it's not that far away for deferred features) | 21:08 |
| jaypipes | ttx: SSL support has a branch proposed but I'm stuck on getting a working functional test case for it... | 21:08 |
| ttx | what about Add filter for changes-since (changes-since-filter) ? | 21:08 |
| jaypipes | ttx: so I'd like that feature to go in. | 21:08 |
| jaypipes | ttx: can go to Essex. | 21:08 |
| ttx | ok, willdefer | 21:08 |
| ttx | jaypipes: You also have 13 D4-targeted bugs, which sounds like a lot to fix in two days. | 21:09 |
| ttx | ould you come up with a more reasonable "must-have-for-D4" list and target the others to RBP ? | 21:09 |
| *** tylesmit has joined #openstack-meeting | 21:09 | |
| ttx | Could* | 21:09 |
| *** msinhore has quit IRC | 21:09 | |
| ttx | I'd like to know what I should be waiting on, if possible | 21:09 |
| *** salv has joined #openstack-meeting | 21:09 | |
| jaypipes | ttx: the system-controlled/user-controlled properties will need to go into RBP | 21:10 |
| *** joesavak has joined #openstack-meeting | 21:10 | |
| *** jsavak has joined #openstack-meeting | 21:10 | |
| ttx | jaypipes: oh, missed that one | 21:10 |
| jaypipes | ttx: and yes on the bugs list. in process of writing a status update to the ML on glance bugs to focus on | 21:10 |
| *** masumotok has joined #openstack-meeting | 21:10 | |
| *** jakedahn has quit IRC | 21:10 | |
| ttx | jaypipes: any eta for system-controlled/user-controlled properties ? | 21:10 |
| *** jakedahn has joined #openstack-meeting | 21:11 | |
| jaypipes | ttx: depends on when Vek gets the functional test cases done for keystone. He's made good progress with _cerberus_ so far. Expect to see that bug closed soon (https://bugs.launchpad.net/bugs/825419) | 21:12 |
| *** zns has quit IRC | 21:12 | |
| uvirtbot | Launchpad bug 825419 in glance "Functional tests for private and shared images" [High,Confirmed] | 21:12 |
| jaypipes | ttx: that bug is the reason for that blueprint being in Blocked. | 21:12 |
| ttx | jaypipes: ok. You can add the tests in D4, btw, as a bugfix branch. | 21:12 |
| *** jsavak has quit IRC | 21:12 | |
| ttx | jaypipes: Other announcements/comments ? | 21:12 |
| jaypipes | ttx: thinking... | 21:13 |
| _cerberus_ | For the record, I *should* have those tests done shortly. Hitting a small roadblock in one of the tests | 21:13 |
| jaypipes | ttx: no, I think I'm good. | 21:13 |
| jaypipes | _cerberus_: rock. | 21:13 |
| ttx | Raise your hand if you have a question on Glance. | 21:13 |
| jaypipes | oooh... o/ | 21:14 |
| jaypipes | annegentle: about Glance API docs.... | 21:14 |
| jaypipes | annegentle: I'd like to put API doc into the RBP milestone: https://launchpad.net/glance/+milestone/diablo-rbp | 21:14 |
| jaypipes | annegentle: OK with you? | 21:14 |
| *** msinhore has joined #openstack-meeting | 21:15 | |
| *** msinhore1 has quit IRC | 21:15 | |
| jaypipes | OK, I'll follow up offline on that | 21:15 |
| *** troytoman-away is now known as troytoman | 21:15 | |
| ttx | ok then moving on to the meaty topic | 21:15 |
| vishy | pork? | 21:15 |
| *** Tushar has joined #openstack-meeting | 21:16 | |
| ttx | #topic Nova status | 21:16 |
| vishy | beef? | 21:16 |
| *** openstack changes topic to "Nova status" | 21:16 | |
| vishy | oh, right... | 21:16 |
| primeministerp2 | veal? | 21:16 |
| ttx | vishy: Let's review the numerous features that missed D4 for essex-deferring/rbp-excepting :) | 21:16 |
| ttx | * Implement Quantum Network Manager (implement-network-api) | 21:16 |
| danwent | hello | 21:16 |
| ttx | danwent: This one is proposed for merging, and reasonably self-contained ? | 21:16 |
| danwent | pretty much self-contained... a few changes to nova-manage and adding a field to the networks table. | 21:17 |
| danwent | otherwise pretty much everything is only run if you run the QuantumManager class | 21:17 |
| danwent | which is an alternative to FlatManager, etc. | 21:17 |
| ttx | danwent: but depends on Melange stuff, right ? | 21:17 |
| danwent | ttx: i recently change it so that it can work with the nova DB ip address management as well. | 21:17 |
| *** dendrobates is now known as dendro-afk | 21:17 | |
| danwent | its a flag | 21:17 |
| danwent | by default it uses nova IPAM, flag can change it to use melange. | 21:18 |
| danwent | this code needs more testing though... i merge propped it to try and flush out any major concerns early. | 21:18 |
| danwent | as wel talked about via email. | 21:18 |
| ttx | vishy: sounds like a good candidate for exception ? | 21:18 |
| vishy | agreed | 21:18 |
| danwent | much appreciated | 21:18 |
| ttx | * Adding Volume Types to Nova Volumes (volume-type) | 21:18 |
| vishy | i don't think the guys working on that are here atm | 21:19 |
| vishy | they have all the db code done and are adding api extensions | 21:19 |
| vladimir3p | re volume types : core will be ready today/tomorrow | 21:19 |
| vishy | ah there he is | 21:19 |
| ttx | vishy: how intrusive is it ? | 21:19 |
| annegentle | jaypipes: sorry for the late response, but yes, diablo-rpb seems doable | 21:19 |
| vishy | should only affect nova-volume | 21:19 |
| ttx | vishy: your call | 21:20 |
| vishy | i think it should go in if it can be approved by friday | 21:20 |
| ttx | +1 | 21:20 |
| vishy | if it doesn't make it by friday EOD we have to push to essex | 21:20 |
| ttx | * Various requirements for assigning IP addresses to XenServer guests (xs-guest-ip-addressing) | 21:20 |
| ttx | This one depends on Melange, and I don't think there is a pressing need to have it in Diablo, or is there ? | 21:21 |
| jaypipes | annegentle: k, gotcha | 21:21 |
| ttx | tr3buchet: ^ ? | 21:21 |
| jaypipes | ttx: the melange merge proposal has a number of things that need fixing IMHO. Might be very difficult to get that in for Diablo... | 21:22 |
| vishy | jaypipes: is it the stuff about using the nova version of utils/etc.? | 21:22 |
| jaypipes | vishy: well, I had a few more comments than just that on my review :) | 21:22 |
| ttx | vishy: I'm with Jay, sounds like a large drop just to be able to show it off | 21:22 |
| *** jakedahn_ has joined #openstack-meeting | 21:23 | |
| *** shwetaap has joined #openstack-meeting | 21:23 | |
| tr3buchet | ttx: you are correct | 21:23 |
| ttx | vishy: I don't expect the packaging to expose it anyway, so what's the point ? | 21:23 |
| ttx | * Melange - IP Address Management Service (melange-ipam) | 21:23 |
| tr3buchet | ttx: from my end we've got as much of it as we need at the moment | 21:23 |
| ttx | ok, jumping to Melange then | 21:23 |
| ttx | and deferring xs-guest-ip-addressing to Essex | 21:24 |
| vishy | ttx: so can they release an experimental package that is separate? | 21:24 |
| vishy | the merge to nova was just to get more eyes on it | 21:24 |
| *** jrouault has quit IRC | 21:24 | |
| ttx | vishy: I prefer that we don't do that post D4, but rather at the beginning on Essex | 21:25 |
| tr3buchet | yeah it's definitely a big work in progress at the moment | 21:25 |
| ttx | and get eyes on it in time for the design summit | 21:25 |
| *** jakedahn has quit IRC | 21:25 | |
| *** jakedahn_ is now known as jakedahn | 21:25 | |
| ttx | rather than ship half-baked code just for exposing it to the public | 21:25 |
| vishy | ttx: i'm ok with that | 21:25 |
| ttx | I wouldn't mind so much if it wasn't post D4 | 21:25 |
| ttx | ok, deferring to essex then | 21:26 |
| ttx | * Update Hyper-V to accommodate Diablo changes, add diff disk support (hyper-v-update) | 21:26 |
| ttx | sounds like bugfixes to me -- my only gripe is that I couldn't get status from JordanRinke | 21:26 |
| ttx | so I don't know where it's at | 21:26 |
| primeministerp2 | hey guys | 21:27 |
| primeministerp2 | i'm here | 21:27 |
| primeministerp2 | i haven't heard from jordan either | 21:27 |
| primeministerp2 | however | 21:27 |
| primeministerp2 | just some bits for to add | 21:27 |
| primeministerp2 | on the hyperv bit | 21:27 |
| primeministerp2 | we successfully deployed on core | 21:27 |
| primeministerp2 | er have | 21:28 |
| primeministerp2 | still have some minor issues to work out w/ networkikng | 21:28 |
| ttx | vishy: ok for an exception on this, but would be good to get Jordan's status ? | 21:28 |
| vishy | yes | 21:29 |
| ttx | * Volume Code cleanup (volume-cleanup) | 21:29 |
| *** spectorclan_ has quit IRC | 21:29 | |
| ttx | how much of it is cleanup, and how destructive is the cleanup ? | 21:30 |
| vishy | ttx: it is separating the concerns of volume and compute | 21:30 |
| vishy | so compute talks to volume through the api | 21:30 |
| ttx | From the description, it looks a bit risky. | 21:30 |
| vishy | and has a plugin | 21:30 |
| ttx | as in "prone to introducing some weird bugs" | 21:31 |
| vishy | I have gotten it working functionally, I have written some tests for the new code. It did introduce bugs into live migration, which the live migration team is working on. | 21:31 |
| ttx | vishy: why do we want it in Diablo ? | 21:31 |
| *** jk0 has joined #openstack-meeting | 21:32 | |
| *** bcwaldon has quit IRC | 21:32 | |
| vishy | ttx: let me think for a sec if there is anything requiring it | 21:32 |
| vishy | I think volume-cleanup-1 removing AoE support is important | 21:32 |
| vishy | so people don't start using it | 21:33 |
| ttx | vishy: is volume-types independent of volume-cleanup ? | 21:33 |
| vishy | in theory yes | 21:33 |
| vishy | aside from it having to touch the same parts of the code in some places | 21:33 |
| vishy | it should be separate | 21:33 |
| soren | I think jaypipes had a good point when he suggested that we don't actually know that noone is using it right now. | 21:34 |
| *** zns has joined #openstack-meeting | 21:34 | |
| vishy | soren: I guess we can't be sure. But I've never even heard of someone testing AoE | 21:34 |
| soren | ...and might be expecting an upgrade path, and failing that, at least some warning before we just break their stuff. | 21:34 |
| vishy | let alone deploying it | 21:34 |
| soren | Dunno. | 21:34 |
| soren | It's an interesting topic though: | 21:34 |
| soren | How do we deprecate stuff? | 21:34 |
| vishy | soren: how do we notify these people? | 21:34 |
| soren | Exactly. | 21:34 |
| soren | Even if we decided to keep AoE, but deprecate it, what does that actually mean? | 21:35 |
| soren | I mean.. | 21:35 |
| ttx | soren: sounds like a good topic for the summit. Can you rtm it somewhere ? | 21:35 |
| soren | Anyone who's talked to us knows not to use AoE :) | 21:35 |
| pvo | vishy: it it printing deprecated notices in the logs when you use it? then pulling next release? | 21:35 |
| vishy | pvo: that is what I'm trying to do with auth stuff | 21:35 |
| vishy | pvo: so maybe | 21:35 |
| soren | ..so it's not like it's a secret that it's de facto deprecated, but we've not really published the deprecation anywhere, and there are no warnings if you choose the AoE driver.. | 21:36 |
| ttx | vishy: I'm not exactly a fan of this spec. Sounds a good one at the beginning of a cycle, not so much at the end :) | 21:36 |
| vishy | ttx: ok. I'm concerned about leaving bad code in for another 6 months | 21:36 |
| vishy | ttx: but you're right it has potential to be destructive | 21:36 |
| ttx | vishy: we all know that Essex will start being better than Diablo about two weeks after Diablo is released | 21:37 |
| ttx | so if it gets in to Essex early, it's not really "6 months of bad code" | 21:37 |
| vishy | ttx: it is for people building external software | 21:37 |
| soren | vishy: We can put in the release notes that AoE is going away. | 21:37 |
| soren | Don't use it. | 21:38 |
| vishy | soren: seems reasonable | 21:38 |
| Daviey | ttx: It's supported for 18 months in Ubuntu.. oh golly. | 21:38 |
| ttx | vishy: how about adding deprecation messages in Diablo ? | 21:38 |
| primeministerp2 | people still use that | 21:38 |
| ttx | so that we have a good framework for removing it early Essex ? | 21:38 |
| soren | vishy: Don't get me wrong. I want it to *die* *die* *die*, too :) | 21:39 |
| vishy | ok, i can put the volume-cleanup code on ice until after the release. Hopefully merging isn't too painful | 21:39 |
| ttx | deal :) | 21:39 |
| vishy | I will need to back port a couple of minor fixes that i found while i was working on the code | 21:39 |
| ttx | * Virtual Storage Arrays for Nova (nova-virtual-storage-array) | 21:39 |
| ttx | this one sounds like a good candidate for deferring, unless I miss something | 21:40 |
| vishy | so the main issue with VSA is that it seemed to be a little too tightly coupled | 21:40 |
| ttx | as in, still under heavy discussion, and could use another round of design summit | 21:40 |
| *** jmckenty_ has quit IRC | 21:40 | |
| vishy | I've been working with them to try and separate it out, which was the main motivator for the volume type stuff | 21:40 |
| *** johnpur has quit IRC | 21:40 | |
| ttx | vishy: a bit late now, right ? | 21:41 |
| vishy | but they have put a lot of effort into this branch | 21:41 |
| ttx | how self-contained is it ? | 21:41 |
| vladimir3p | yep, we are trying to "generalize" it by moving from drive types to volume types | 21:41 |
| vladimir3p | and it is pretty self-contained | 21:41 |
| ttx | are you confident it can make it very soon ? | 21:41 |
| vishy | vladimir3p: did you remove the changes in nova-compute and use instance_types? | 21:41 |
| vladimir3p | we can adopt al volume_type changes within next couple of days | 21:42 |
| vladimir3p | yep, there are no more changes in nova-compute | 21:42 |
| vishy | so if they can switch to using volume-types | 21:42 |
| vladimir3p | changes in nova-volume will be minimal and will depend on volume types | 21:42 |
| vishy | it will be one additional db table | 21:42 |
| vishy | and an additional self-contained worker | 21:42 |
| *** ewanmellor has quit IRC | 21:43 | |
| vishy | it would be completely experimental | 21:43 |
| ttx | My main issue with this plan is that it needs volume-types to land first | 21:43 |
| ttx | so I fear VSA will land *late* | 21:43 |
| ttx | (and I hate new features post-D4, too) | 21:43 |
| vishy | we could give them the same friday time table? | 21:43 |
| vladimir3p | meanwhile we are on track to push it till Thu | 21:43 |
| vladimir3p | the VSA merge proposal is in from beg of July | 21:44 |
| vishy | vladimir3p: perhaps the best plan would be to just merge the db changes | 21:44 |
| ttx | vladimir3p: yes, true | 21:44 |
| ttx | ok for Friday | 21:44 |
| *** johan_-_ has joined #openstack-meeting | 21:44 | |
| ttx | * Administrative VMs / containers for provider services (administrative-vms) | 21:44 |
| vishy | then it is possible to ship the nova-vsa worker/driver/scheduler separately | 21:44 |
| ttx | this one is deferred though, right :) | 21:44 |
| vishy | yes defer that one | 21:44 |
| vladimir3p | the admin VM we can definitely defer :-) | 21:44 |
| vishy | it is still undetermined | 21:44 |
| ttx | \o/ | 21:45 |
| ttx | * Simple Usage (simple-usage) | 21:45 |
| ttx | looks very selfcontaine and ready | 21:45 |
| *** jsavak has joined #openstack-meeting | 21:45 | |
| ttx | I'd lean towards granting an exception | 21:45 |
| vishy | yes just an api extension really | 21:46 |
| ttx | * Validation of params in AWS API (aws-api-validation) | 21:46 |
| ttx | I'm a bit worried about the state of that one | 21:46 |
| ttx | by its own admission it's not really ready | 21:46 |
| ttx | though I'd like to see some validation :) | 21:46 |
| Daviey | Oo, i didn't know anyone was working on that. | 21:47 |
| ttx | It's been longing for you for too long :) | 21:47 |
| ttx | vishy: given that it doesn't look ready, I'd defer it ? | 21:48 |
| vishy | ttx: It doesn't really seem like a feature to me | 21:48 |
| vishy | ttx: it is testing/validation related, so seems like exactly what we should be doing now | 21:49 |
| vishy | ttx: or am I misunderstanding the purpose of the next 3-4 weeks | 21:49 |
| ttx | vishy: agreed. | 21:49 |
| ttx | I was wondering how featureful it was | 21:49 |
| * Daviey will sniff that branch to see if it does as he expects. | 21:49 | |
| ttx | but if its client validation, it can't hurt | 21:49 |
| ttx | last one: | 21:50 |
| vishy | ttx: I think it should be fine to go in without an FF exception. | 21:50 |
| ttx | * Admin API: server actions (admin-server-actions) | 21:50 |
| vishy | that is thoe one split into 3 parts? | 21:50 |
| ttx | vishy: yes | 21:50 |
| ttx | that third is the one that is supposedly implemenetd already | 21:50 |
| ttx | glenc: is that right ? | 21:50 |
| vishy | it didn't seem like they needed an exception for any specific functionality | 21:50 |
| glenc | that's correct | 21:50 |
| ttx | so is the code in already ? | 21:50 |
| glenc | the server (suspend/resume) is already in trunk | 21:50 |
| ttx | but not exposed in the API yet ? | 21:51 |
| glenc | there's a question as to whether or not it should be implemented as an extension | 21:51 |
| glenc | No, it's in the Admin API | 21:51 |
| glenc | the question is whether or not it should appear in /extensions since it's not part of the 1.1 spec | 21:51 |
| ttx | vishy: what do you think ? | 21:51 |
| ttx | if not, then it's completed by D4 | 21:52 |
| glenc | per jorge w, it should be part of the official admin API spec, but we don't really have that yet | 21:52 |
| pvo | it is implemented in the api, used by novaclient, but isn't an extension. | 21:53 |
| pvo | official admin api spec? :p | 21:53 |
| ttx | we'll take that one offline. | 21:53 |
| ttx | The other two parts are planned for end of September, so deferred to Essex. | 21:53 |
| vishy | sorry stepped away for a sec | 21:54 |
| ttx | vishy: You have two D4-targeted bugs on the list: | 21:54 |
| ttx | bug 803654 (availability zone ignored when creating volume) without an assignee | 21:54 |
| uvirtbot | Launchpad bug 803654 in nova "availability zone ignored when creating volume" [High,Confirmed] https://launchpad.net/bugs/803654 | 21:54 |
| ttx | bug 828907 (Distributed Scheduler docs need updating), assigned to dabo | 21:54 |
| uvirtbot | Launchpad bug 828907 in nova "Distributed Scheduler docs need updating" [Low,In progress] https://launchpad.net/bugs/828907 | 21:54 |
| ttx | Anything else that we *need* to fix before D4 release ? | 21:54 |
| dabo | ttx: that one's done | 21:54 |
| ttx | oh, cool | 21:55 |
| *** kris3968 has left #openstack-meeting | 21:55 | |
| vishy | the other can go into rbp | 21:55 |
| Daviey | bug 798876 .. i made a start on it, but i haven't been able to finish.. it would be realy nice if we can remove carrot for final release (considering kombu is already required for glance).. would anyone be able to assist? | 21:55 |
| uvirtbot | Launchpad bug 798876 in nova "Consider Switching from Carrot to Kombu for AMQP" [Low,Confirmed] https://launchpad.net/bugs/798876 | 21:55 |
| comstud_ | i'm 95% done | 21:55 |
| comstud_ | been testing code standalone | 21:55 |
| comstud_ | need to merge it into my branch and fix tests | 21:55 |
| comstud_ | was out sick all last week, otherwise would be done by now :( | 21:55 |
| *** comstud_ is now known as comstud | 21:55 | |
| ttx | vishy: what's your take on that ? | 21:56 |
| ttx | (bug 798876 for D4 or for RBP) | 21:56 |
| comstud | the problem is that it will introduce a new depdendency | 21:56 |
| comstud | for nova | 21:56 |
| jaypipes | comstud: picked a bad week to stop sniffing glue. | 21:56 |
| comstud | jaypipes: no kidding | 21:56 |
| comstud | i can optionally.... make kombu optional | 21:56 |
| comstud | and keep the carrot code alongside | 21:56 |
| vishy | comstud: it is already a dep | 21:56 |
| ttx | comstud: I like that. | 21:56 |
| *** jbryce has quit IRC | 21:56 | |
| comstud | vishy: for _nova_ ? | 21:57 |
| vishy | nova -> glance -> kombu | 21:57 |
| comstud | ah | 21:57 |
| comstud | i suppose that's true | 21:57 |
| Daviey | comstud: I had to use trunk kombu, do you? | 21:57 |
| vishy | believe me, it has caused a whole bunch of builds to fail everywhere :) | 21:57 |
| *** ryu_ishimoto has joined #openstack-meeting | 21:57 | |
| Daviey | (which meant amqplib > 1.0.) | 21:57 |
| comstud | Daviey: No, I'm working successfully with whatever's in pypi | 21:57 |
| comstud | vishy: I believe you :) | 21:57 |
| ttx | ok, let's also bring that one offline so that we can rush the end of the meeting | 21:57 |
| *** asomya has joined #openstack-meeting | 21:58 | |
| Daviey | comstud: Yes, sorry that is ~= trunk for what i mean't | 21:58 |
| Daviey | it's newer than Ubuntu & Debian. | 21:58 |
| vishy | yes online it. | 21:58 |
| comstud | ahh yeah | 21:58 |
| ttx | #topic Incubated projects news | 21:58 |
| *** openstack changes topic to "Incubated projects news" | 21:58 | |
| vishy | * offline | 21:58 |
| ttx | devcamcar, dolphm: you have one line. | 21:58 |
| nati | I have more point for bug | 21:58 |
| hisaharu | We need to fix bug 828399 | 21:58 |
| uvirtbot | Launchpad bug 828399 in nova "Can not delete a network which is associated with a project" [Wishlist,In progress] https://launchpad.net/bugs/828399 | 21:58 |
| danwent | quantum was approved for incubation today :) | 21:58 |
| hisaharu | it's almost done | 21:58 |
| somik | congratulations quantum team! | 21:59 |
| ttx | hisaharu: cool, will add to D4 list | 21:59 |
| nati | Thanks a lot | 21:59 |
| hisaharu | thanks | 21:59 |
| ttx | #topic Design Summit registration | 21:59 |
| *** openstack changes topic to "Design Summit registration" | 21:59 | |
| ttx | As you all should know, we'll have our Design Summit in Boston, from Oct 3 to Oct 5. | 21:59 |
| ttx | It is now separate from the OpenStack Conference, which will start on the evening of Oct 5 and end on Oct 7. | 21:59 |
| ttx | Registration is now officially open for the Design Summit at: http://summit.openstack.org | 22:00 |
| ttx | There is limited room, so register early ! | 22:00 |
| comstud | FYI, Oct 4 is my birthday.. so I expect gifts. | 22:00 |
| * comstud hides now. | 22:00 | |
| ttx | Note that developers attending the Design Summit can get a free pass to attend the OpenStack Conference, if you are interested. | 22:00 |
| ttx | Also, this is not for suits. Only for geeks. | 22:00 |
| primeministerp2 | ttx: question on that | 22:00 |
| *** SumitNaiksatam has joined #openstack-meeting | 22:01 | |
| ttx | primeministerp2: yes ? | 22:01 |
| primeministerp2 | ttx: I offered to speak re hyperv/openstack | 22:01 |
| ttx | primeministerp2: at the conference, right ? | 22:01 |
| primeministerp2 | yes | 22:01 |
| primeministerp2 | haven't heard anything else since that | 22:01 |
| primeministerp2 | I know spector knows | 22:01 |
| ttx | primeministerp2: ping spectorclan about it | 22:01 |
| primeministerp2 | thx | 22:01 |
| ttx | #topic Open discussion | 22:01 |
| *** openstack changes topic to "Open discussion" | 22:01 | |
| *** tylesmit has quit IRC | 22:02 | |
| ttx | a bit overtime already. anything else, anyone ? | 22:02 |
| annegentle | I'm working on a doc sprint day in Austin, date and location to be determined, but it will be in September. | 22:02 |
| annegentle | precise location. Secret bunker. That sort of thing. :) | 22:02 |
| * ttx watches the registration site crumble under load | 22:02 | |
| *** zns has quit IRC | 22:03 | |
| ttx | closing meetingin 10 seconds | 22:03 |
| annegentle | I know y'all are jealous of our tying the 86-year record for number of consecutive days with triple digits. | 22:03 |
| ttx | #endmeeting | 22:03 |
| *** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/" | 22:03 | |
| openstack | Meeting ended Tue Aug 23 22:03:38 2011 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 22:03 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-08-23-21.02.html | 22:03 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-08-23-21.02.txt | 22:03 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-08-23-21.02.log.html | 22:03 |
| *** jmeredit has joined #openstack-meeting | 22:03 | |
| Vek | heh. | 22:03 |
| ttx | danwent: a bit late :) | 22:03 |
| danwent | Ok netstackers..... let's get started :) | 22:03 |
| markvoelker | o/ | 22:04 |
| Vek | hey, as long as it's not 112+ like my parents have been dealing with :) | 22:04 |
| danwent | ttx: no worries... big deadline and a lot of stuff to cover | 22:04 |
| *** Vek has left #openstack-meeting | 22:04 | |
| rohitagarwalla | o/ | 22:04 |
| somik | o/ | 22:04 |
| danwent | #startmeeting | 22:04 |
| openstack | Meeting started Tue Aug 23 22:04:21 2011 UTC. The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot. | 22:04 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic. | 22:04 |
| danwent | agenda: http://wiki.openstack.org/Network/Meetings | 22:04 |
| *** creiht has left #openstack-meeting | 22:04 | |
| danwent | #topics nestack general topics | 22:05 |
| *** ying has joined #openstack-meeting | 22:05 | |
| danwent | #info congrats to the whole team.... quantum was accepted as an official OpenStack incubated project today | 22:05 |
| ttx | congrats ! | 22:05 |
| pvo | allright :) | 22:05 |
| SumitNaiksatam | hearty congrats! | 22:05 |
| * markvoelker cheers and looks around for champagne | 22:05 | |
| asomya | nice | 22:05 |
| rohitagarwalla | congrats | 22:05 |
| danwent | with the significant participation from folks from multiple different companies... I think it was an easy call for them. Great work folks... take a minute to relax, then get back to working on D-4 reviews :) | 22:06 |
| edgarmagana | Great News!! | 22:06 |
| *** dabo has left #openstack-meeting | 22:06 | |
| danwent | mark: we'll have to bring some to the essex summit to toast :) | 22:06 |
| markvoelker | danwent: I dunno...last time I tried to bring drinks on a plane the TSA got frisky. =p | 22:07 |
| danwent | in other news, we'll be moving to the new github/gerrit setup post diablo | 22:07 |
| danwent | if you're curious, read up on: http://wiki.openstack.org/GerritWorkflow | 22:07 |
| danwent | best to identify any concerns you have early and we can work with the openstack team to figure out solutions | 22:07 |
| SumitNaiksatam | post diablo - cheers to that as well! :-) | 22:07 |
| salv | danwent: do we have a leader for the migration effort? | 22:07 |
| salv | i.e.: somebody to bugger with question? | 22:07 |
| danwent | salv: are you volunteering ;) | 22:07 |
| danwent | ? | 22:07 |
| danwent | jaypipes said he would help out | 22:08 |
| salv | not really, I'd like to focus on blueprints for essex release :-) | 22:08 |
| pvo | mtaylor would be another guy to ping. | 22:08 |
| mtaylor | yes | 22:08 |
| mtaylor | what? | 22:08 |
| danwent | salv: no problem.... I was planning on driving this | 22:08 |
| pvo | you helping with gerrit and migration to git | 22:08 |
| danwent | sent an email to mtayler and heckj this morning. | 22:08 |
| *** jsavak has quit IRC | 22:08 | |
| *** joesavak has quit IRC | 22:08 | |
| mtaylor | yes. also jeblair will be involved | 22:08 |
| danwent | mtayler -> mtaylor | 22:08 |
| mtaylor | danwent: and - I haven't forgotten about your email about tarballs - I just had some world explosion earlier this morning I'm still cleaning up | 22:09 |
| bhall | danwent: I can help too if you want | 22:09 |
| danwent | #action danwent: send out email to folks helping with move to github | 22:09 |
| danwent | bhall: thx | 22:09 |
| danwent | mtaylor: no worries... tuesdays are always very busy days, I understand :) | 22:09 |
| _0x44 | jaypipes: ping | 22:09 |
| mtaylor | danwent: (sorry, I've got like, 5 todo list items for you guys) | 22:09 |
| danwent | mtaylor: we appreciate the help | 22:10 |
| *** edconzel_ has joined #openstack-meeting | 22:10 | |
| danwent | one other general netstack point: essex summit signup is now open | 22:10 |
| danwent | #info sign up for essex summit if you can: http://summit.openstack.org/ | 22:10 |
| danwent | we'll definitely be having discussions about blueprints for quantum, and it is generally a great chance to meet team members face to face. | 22:10 |
| danwent | so you can put a face to the reviewers name :) | 22:11 |
| salv | mine is particuarly ugly... | 22:11 |
| danwent | spots are limited and I think they ran out last time, so don't delay | 22:11 |
| danwent | salv: but your code is beautiful, so it makes up for it, right? :P | 22:11 |
| danwent | Ok, it troy around? | 22:12 |
| *** edconzel has quit IRC | 22:12 | |
| *** edconzel_ is now known as edconzel | 22:12 | |
| troytoman | yes | 22:12 |
| somik | About Essex Summit: Developers get a free pass to attend the conference I believe. | 22:12 |
| danwent | #topic melange | 22:12 |
| *** openstack changes topic to "melange" | 22:12 | |
| salv | danwent: you're too kind. Anyway seats are going away fast. 1 per minut. | 22:12 |
| salv | At this pace, the essex summit would be a sold out in 3 hours! | 22:12 |
| troytoman | we did the initial merge prop for Melange and have gotten a great deal of feedback. | 22:12 |
| troytoman | we're working on creating an OpenStack commons code area to address some of the concerns | 22:13 |
| troytoman | we're also cleaning up the cli etc. | 22:13 |
| *** edconzel has quit IRC | 22:13 | |
| danwent | cool. over the weekend I did a first cut at melange support for the quantum manager. | 22:13 |
| troytoman | it's too big of a change to get into Nova in Diablo but we should be setup for early Essex | 22:13 |
| *** edconzel has joined #openstack-meeting | 22:14 | |
| salv | danwent: we were just granted feature-freeze exception for quantum manager, is that correct? | 22:14 |
| troytoman | plan is to focus on the merge prop and the quantum/nova integration | 22:14 |
| danwent | Ok. and if we get the quantum manager code in nova, it should still be possible to run nova with melange, i believe, you will just need to download melange separately... is that correct? | 22:14 |
| danwent | salv: correct | 22:14 |
| troytoman | i believe so | 22:15 |
| danwent | I just created a new version of the qmanager branch that is not stacked on top of melange... still needs testing: | 22:15 |
| danwent | https://code.launchpad.net/~danwent/nova/qmanager-new | 22:15 |
| danwent | but you can look through the diff to get a sense of what it does | 22:15 |
| danwent | feedback appreciated. | 22:15 |
| danwent | ok troy, thanks for the update. I must say, the melange code has been rock solid in my testing against it. | 22:16 |
| danwent | any time there was a bug, it was in my code calling it :) | 22:16 |
| troytoman | i hope we can start getting some scale testing done on the integration soon | 22:16 |
| *** msinhore has quit IRC | 22:16 | |
| troytoman | we should be in good shape for that | 22:17 |
| danwent | agreed. | 22:17 |
| danwent | ok, anything else on melange? | 22:17 |
| danwent | #topic donabe | 22:17 |
| *** openstack changes topic to "donabe" | 22:17 | |
| danwent | is debo or someone else working on donabe here? | 22:18 |
| jamesurquhart | I'm here, but don't have an update. | 22:18 |
| jamesurquhart | I'll see if I can get Rick or Debo to send an update to the alias. | 22:18 |
| danwent | #action #debo send update on donabe to email list | 22:18 |
| danwent | james: thx | 22:18 |
| danwent | #topic quantum | 22:18 |
| *** openstack changes topic to "quantum" | 22:18 | |
| danwent | first off, congrats to everyone on incubation... | 22:19 |
| danwent | we've been making great progress on getting through the D-4 reviews | 22:19 |
| danwent | great work from many different folks on the team | 22:19 |
| danwent | https://code.launchpad.net/quantum/+activereviews | 22:19 |
| danwent | my understanding is that the cisco reviews are all stacked on each other, so they aren't quite as massive as they look. | 22:20 |
| danwent | is that correct? | 22:20 |
| SumitNaiksatam | yes | 22:20 |
| SumitNaiksatam | dont be too alarmed :-) | 22:20 |
| danwent | Sumit: great. As I mentioned in the email this morning, I'm confident that we can get these all into diablo, even if they aren't quite done by the D-4 deadline | 22:21 |
| danwent | https://code.launchpad.net/~salvatore-orlando/quantum/quantum-api-alignment/+merge/70788 | 22:21 |
| salv | I think the consolidation branch is stacked on top of the other three, which are independent | 22:21 |
| SumitNaiksatam | yes | 22:21 |
| SumitNaiksatam | there is one on the VIF-driver and Scheduler which is independent of the others | 22:21 |
| danwent | https://code.launchpad.net/~salvatore-orlando/quantum/quantum-api-alignment/+merge/70788 | 22:21 |
| salv | I had a good deal of feedback, especially from Simik | 22:21 |
| salv | Somik, sorry. | 22:21 |
| salv | Concerns have been addressed and updated code pushed to the branch. I.m pretty sure we can have it merged by thirsday. | 22:22 |
| danwent | Ok, anything we need to discuss here? | 22:22 |
| danwent | sounds like you're on top of it. | 22:22 |
| somik | salv: I think both of your branches are pretty close, i'll do the final review soon. | 22:22 |
| salv | somik: thanks. | 22:22 |
| somik | salv: Great work on both those branches! | 22:22 |
| danwent | any significant concerns with any of the reviews that we need to discuss here, or can we just keep plugging away? | 22:23 |
| danwent | sounds like we're in good shape. | 22:23 |
| salv | Not from the reviews I've done. Rohit updated the code after my review, and I think it should not be too much of an issue to merge that branch, | 22:23 |
| salv | I have not received a reply on the vif-scheduler review, though. | 22:23 |
| SumitNaiksatam | thanks Salv, yes I am in the process of fixing that | 22:24 |
| salv | good. | 22:24 |
| edgarmagana | salv: Rohit and I made some changes based on your reviews.. Thanks a lot! | 22:24 |
| SumitNaiksatam | vif-driver/scheduler that is | 22:24 |
| SumitNaiksatam | salv: that particular branch is independent of other cisco branches | 22:24 |
| danwent | ok, great work folks. | 22:24 |
| edgarmagana | We even increased our pylint score :-) | 22:24 |
| rohitagarwalla | thanks salv again for the review...and good to hear that the branch is in good shape for merge | 22:24 |
| SumitNaiksatam | so it can go in even later | 22:24 |
| danwent | Ok, onto talking about Nova Integration with Quantum | 22:25 |
| salv | SumitNaiksatam: very good | 22:25 |
| danwent | so Ryu's branch to add an extension to nova to expose vif uuids went in. | 22:25 |
| danwent | this should give us what we need for the GUI, is that correct arvind? | 22:25 |
| asomya | yup.. I integerated that into the dashboard waiting a merge on openstackx https://github.com/cloudbuilders/openstackx/pull/16 | 22:26 |
| danwent | cool! | 22:26 |
| salv | Does this extension also allow us to track to which instance a particular VIF belongs? | 22:26 |
| danwent | salv: I believe so | 22:26 |
| salv | danwent: something worth looking at for our issue with authorization | 22:27 |
| danwent | yeah... we discussed that. Could definitely be used for that, at least in the short-term. | 22:27 |
| salv | great | 22:28 |
| danwent | QuantumManager got an extension to try and get into diablo... so more coding for me :) | 22:28 |
| danwent | https://code.launchpad.net/~danwent/nova/qmanager-new | 22:28 |
| danwent | works with two modes for IPAM, melange, and the traditional nova DB IPAM. | 22:29 |
| salv | danwent: great choice | 22:29 |
| danwent | it also supports a tushar's extension to allow specifying networks when creating a VM. | 22:29 |
| danwent | that could be something that we leverage in the GUI as well in the future. | 22:29 |
| danwent | the os-create-server-ext extension | 22:30 |
| danwent | other than that, wanted to touch on packaging, is tyler here? | 22:30 |
| danwent | once we get all of the existing reviews in for diablo, we'll need to figure out how to switch the directory structure around. | 22:30 |
| markvoelker | danwent: nope...this meeting time doesnt' work with his schedule unfortunately | 22:31 |
| danwent | ok, i encourage people to check out the branch: https://code.launchpad.net/~tylesmit/quantum/quantum-packages | 22:31 |
| danwent | I have some questions that i'll be sending to the list soon. | 22:31 |
| *** johan_-_ has left #openstack-meeting | 22:32 | |
| danwent | Only other agenda item is to start thinking about documentation.... we've done an awesome job writing code, now we need to make sure people other than us can use it :) | 22:32 |
| danwent | Both docs for administrators (i.e., quantum users) as well as for developers. | 22:32 |
| salv | On this regard there was an interesting thread in the Openstack ML on documentation for openstack API | 22:32 |
| danwent | savl: indeed, thanks for bringing that up | 22:33 |
| salv | vishy was proposing to embed the documentation in source code, and I agree with this approach. | 22:33 |
| salv | Maintaning a separate wiki page for API spec has been quite cumbersome for me. | 22:33 |
| danwent | salv: +1 having an approval process to update an API spec seems very valuable | 22:33 |
| danwent | that way people are much more likely to see changes that are relevant to them. | 22:34 |
| salv | +1 on the approval process. Second troubling issue was getting formal feedback and approval on the contents of the wiki page :) | 22:34 |
| markvoelker | I'd encourage folks to participate in that thread if they have opinions... =) | 22:34 |
| salv | If I'm not wrong Keystone already has documentation in source tree, in rst format | 22:34 |
| danwent | salv: I think this is a great idea. Can you create a blueprint/bug for this? | 22:35 |
| salv | plan to have the same thing for Quantum API. Will be a blueprint with integration freeze as target a good idea? | 22:35 |
| salv | danwent: sorry did not see your last line | 22:35 |
| salv | Okay, please put an action for that | 22:35 |
| danwent | salv: if you can do it quickly, I think that would make sense. | 22:35 |
| *** msinhore has joined #openstack-meeting | 22:35 | |
| danwent | #action #salv will create a blueprint to put API spec into the source tree | 22:35 |
| salv | Sure, I think it can be achieved by next tuesday | 22:36 |
| danwent | salv: thanks for bringing that up | 22:36 |
| danwent | ok, and just on general docs, I think we have some work helping the rest of the nova team understand how quantum fits in... some of this material has already been created, we just need to present it in an organized form. | 22:36 |
| danwent | now that we have a mechanism for nova/quantum integration (actually... two mechanisms), we can create some tutorials which will help a lot. | 22:37 |
| danwent | ok, anything else on quantum? | 22:37 |
| asomya | quick update on the dashboard: it's complete with vif plugging .. just waiting on a couple of merges 1) Merge to the main dashboard trunk https://github.com/4P/openstack-dashboard/pull/92 and 2) The openstackx class to grab VIFS https://github.com/cloudbuilders/openstackx/pull/16 | 22:37 |
| danwent | that was quick :) nice work asomya | 22:38 |
| danwent | #topic open discussion | 22:38 |
| *** openstack changes topic to "open discussion" | 22:38 | |
| danwent | There's a openstack meetup in the bay area tonight | 22:38 |
| *** zns has joined #openstack-meeting | 22:38 | |
| salv | I'd love to attend, but my teleport is broken :) | 22:39 |
| danwent | http://www.meetup.com/SVForum-CloudSIG/events/18687151/?a=md1.2p_grp&rv=md1.2p | 22:39 |
| danwent | salv: you'll be in boston though, right? | 22:39 |
| markvoelker | You west coasters have all the fun...we east coasters just get earthquakes and hurricanes this week. =p | 22:39 |
| salv | danwent: yes, my passport has been renewed! | 22:39 |
| danwent | yeah, that earthquake was crazy | 22:39 |
| danwent | salv: good to hear :) | 22:40 |
| danwent | ok, anything else? | 22:40 |
| salv | Tyler and Arvind, which are not part of the core team, are giving a great contribution in terms of reviews (and code) | 22:40 |
| *** edconzel has quit IRC | 22:40 | |
| danwent | would they like to be part of the core team? | 22:40 |
| salv | shall we consider an extension of the core team? | 22:40 |
| danwent | (wink, wink?) | 22:40 |
| danwent | I'm definitely in favor. | 22:40 |
| somik | +1 | 22:40 |
| salv | if they agree, it's +1 from me | 22:40 |
| asomya | danwent: do we have to bribe someone for that :) | 22:40 |
| rohitagarwalla | +1 | 22:40 |
| SumitNaiksatam | +1 | 22:40 |
| bhall | +1 | 22:41 |
| edgarmagana | +1 | 22:41 |
| ying | +1 | 22:41 |
| danwent | Ok, seems like approval to me. | 22:41 |
| salv | if nobody complains in 10 seconds, it's approved | 22:41 |
| danwent | this is great point. please chime up if you are not a core but want to nominate yourself... or if you're shy, just talk to someone who will then nominate you | 22:41 |
| salv | approved! | 22:41 |
| danwent | sometimes people act like they are already in core, and we forget that they are not :) | 22:42 |
| danwent | ok, anything else? | 22:42 |
| salv | Another little thing on documentation: it would be great if we can provide use cases and reference architectures for quantum. | 22:42 |
| *** msinhore has quit IRC | 22:42 | |
| *** hisaharu has quit IRC | 22:42 | |
| salv | For instance, how to build the network topology for a three-tier app | 22:42 |
| somik | salv: once the quantum manager gets merged in, that would be the next step. | 22:43 |
| somik | but you are correct. | 22:43 |
| salv | somik: good, we had a blueprint for doing something similar | 22:43 |
| salv | https://blueprints.launchpad.net/quantum/+spec/use-case-milestones | 22:43 |
| danwent | salv: agreed. That demo link I sent out showed what is probably one of the most common use cases. | 22:43 |
| SumitNaiksatam | danwent: demo link? | 22:43 |
| salv | yeah, I must have missed it as well... | 22:44 |
| danwent | salv: I actually cleared that out once we started using launchpad milestones | 22:44 |
| danwent | it was buried in my update email to the openstack list... | 22:44 |
| SumitNaiksatam | oh ok will search | 22:44 |
| salv | found it: http://wiki.openstack.org/QuantumOVSDemo | 22:44 |
| danwent | have been meaning to do a screencast, but until then the text will have to do: http://wiki.openstack.org/QuantumOVSDemo | 22:44 |
| SumitNaiksatam | thanks guys! | 22:45 |
| danwent | Showing how we can use quantum to do cool things that aren't possible with existing nova will be key to helping people understand and get excited about quantum. | 22:45 |
| salv | danwent: that's very useful | 22:46 |
| danwent | for example, it would be really cool to do a demo that shows the cisco plugin, with extensions, doing something not exposed in nova | 22:46 |
| danwent | that code is a bit outdated now... i will update it to use real melange, but you should get the idea. | 22:47 |
| danwent | highlighting different use cases in this way will definitely help. | 22:47 |
| danwent | anything else? | 22:47 |
| salv | Just one little thing: who's doing the milestone release on thursday EOD? | 22:47 |
| danwent | I was planning on doing it | 22:48 |
| danwent | but its not a big deal | 22:48 |
| salv | danwent: great. I just wanted to make sure that it was EOD PST! That would be Friday Morning for me :) | 22:48 |
| danwent | the diable-rbp release is coming up pretty soon after it, so I'm not too worried about what does / does not make it into D-4 | 22:48 |
| danwent | salv: haha | 22:48 |
| danwent | if there's anything that is looking really tight, email me. we're small enough that we can fudge the times by a bit if there's a good reason | 22:49 |
| danwent | ok, keep up the great work on D-4 reviews folks, and congrats again on incubation :) | 22:49 |
| danwent | #endmeeting | 22:49 |
| *** openstack changes topic to "Openstack Meetings: http://wiki.openstack.org/Meetings | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/" | 22:49 | |
| openstack | Meeting ended Tue Aug 23 22:49:47 2011 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 22:49 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-08-23-22.04.html | 22:49 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-08-23-22.04.txt | 22:49 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-08-23-22.04.log.html | 22:49 |
| SumitNaiksatam | bye | 22:50 |
| danwent | have a good night/afternoon | 22:50 |
| *** SumitNaiksatam has quit IRC | 22:50 | |
| somik | have a good one OpenStack Quantum folks! | 22:50 |
| salv | bye, good night! | 22:50 |
| *** ryu_ishimoto has left #openstack-meeting | 22:50 | |
| *** jmeredit has left #openstack-meeting | 22:50 | |
| *** asomya has quit IRC | 22:50 | |
| *** Tushar has quit IRC | 22:50 | |
| *** hisaharu has joined #openstack-meeting | 22:52 | |
| *** novas0x2a|laptop has quit IRC | 22:54 | |
| *** novas0x2a|lapto1 has joined #openstack-meeting | 22:55 | |
| *** jk0 has left #openstack-meeting | 22:55 | |
| *** edgarmagana has quit IRC | 22:56 | |
| *** markvoelker has quit IRC | 22:57 | |
| *** ying has quit IRC | 22:59 | |
| *** rohitagarwalla has quit IRC | 22:59 | |
| *** carlp has joined #openstack-meeting | 23:01 | |
| *** zns has quit IRC | 23:04 | |
| *** danwent has left #openstack-meeting | 23:19 | |
| *** shwetaap has quit IRC | 23:19 | |
| *** jamesurquhart has quit IRC | 23:21 | |
| *** jbryce has joined #openstack-meeting | 23:23 | |
| *** jbryce has quit IRC | 23:23 | |
| *** pballand has left #openstack-meeting | 23:23 | |
| *** joearnold has quit IRC | 23:25 | |
| *** zns has joined #openstack-meeting | 23:25 | |
| *** joearnold has joined #openstack-meeting | 23:27 | |
| *** rnirmal has quit IRC | 23:29 | |
| *** novas0x2a|lapto1 has quit IRC | 23:32 | |
| *** novas0x2a|laptop has joined #openstack-meeting | 23:33 | |
| *** dendro-afk is now known as dendrobates | 23:39 | |
| *** novas0x2a|laptop has quit IRC | 23:40 | |
| *** novas0x2a|laptop has joined #openstack-meeting | 23:41 | |
| *** martine has quit IRC | 23:42 | |
| *** Cyns has joined #openstack-meeting | 23:45 | |
| *** novas0x2a|laptop has quit IRC | 23:51 | |
| *** novas0x2a|laptop has joined #openstack-meeting | 23:52 | |
| *** ecarlin has quit IRC | 23:54 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!