19:59:05 #startmeeting heat 19:59:06 Meeting started Wed Dec 5 19:59:05 2012 UTC. The chair is asalkeld. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:59:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:59:09 The meeting name has been set to 'heat' 19:59:25 roll call ... 19:59:53 jpeeler here 20:00:32 #chair jpeeler asalkeld zaneb 20:00:33 Current chairs: asalkeld jpeeler zaneb 20:00:38 hey zaneb 20:00:44 heya 20:00:59 #chair jpeeler asalkeld zaneb radez 20:01:00 Current chairs: asalkeld jpeeler radez zaneb 20:01:15 radez, you are here right 20:01:16 here, 20:01:21 cool 20:01:26 yea, sry on a diff screen 20:01:50 well small meeting today, shardy tomas away 20:02:12 so topics 20:02:50 #agenda Review last week's actions, web ui update, g2 20:02:59 any others? 20:03:33 #topic Review last week's actions 20:03:50 put heatclient in pypi 20:03:57 is that done? 20:04:11 stevebake, ^ 20:04:35 well i enabled tag pushing 20:04:47 so some of it is possible 20:05:02 "make a bug to update the ubuntu tdls to install a recent version of boto" 20:05:40 I think that is still at todo 20:05:45 here, mobile internet is working 20:05:54 hey stevebake 20:06:01 put heatclient in pypi 20:06:08 stevebake, did that happen? 20:06:14 0.1.0 has been released to pypi 20:06:21 well done 20:06:26 sudo pip-install python-heatclient! 20:06:49 stevebake, so how did you do that (so someone else can do it) 20:06:59 just push the tag? 20:07:38 Its a secret! Actually we should submit a ci change to automatically release to pypi when a tag is pushed 20:07:59 #action stevebake should submit a ci change to automatically release to pypi when a tag is pushed 20:08:03 :) 20:08:16 asalkeld: shouldwe also kill the heat-api/python-heatclient repo? 20:08:17 python setup.py sdist upload <-- otherwise 20:08:39 #action asalkeld kill the heat-api/python-heatclient repo 20:09:08 Can we talk GettingStarted.rst? 20:09:25 sure 20:09:35 #topic GettingStarted.rst? 20:10:05 I started porting it to python-heatclient, but it parses results so it will take a bit of effort. 20:10:36 is see 20:10:40 I see 20:10:47 When I first started on Heat it the structure of the doc confused me because it mixed image building, server and client hosts 20:11:16 well, it's the getting started guide 20:11:23 not the deploy openstack guide 20:11:35 well we could explain it a bit better 20:11:38 i wonder if that structure is dictated by its dual role as an integration test 20:11:52 yes, we could definitely explain better 20:12:09 stevebake: maybe 20:12:26 the idea of that was that we can try what we're actually telling people to do 20:12:33 see if it actually works 20:12:44 #action stevebake look at make the gettingStart easier to understand 20:13:01 and still make it runnable for now? 20:13:05 I'm fine with splitting it up into separate files 20:13:38 text should not effect the script part 20:13:44 Is this still most people's entry point to heat? 20:13:53 if so, then we should keep it runnable 20:14:01 good question, on fedora it probably is 20:14:04 not sure, maybe devstack 20:14:34 after grizzly maybe not 20:14:36 I'll have a play 20:14:52 one option is to focus on devstack for devs and RPM for everyone else 20:15:05 in that case, maybe a lot of that guide could go away 20:15:08 yip 20:15:10 so what will be the first easy way of installing on Ubuntu? PPA? pip? 20:15:16 git? 20:15:19 rpm/deb 20:15:20 but it will require a bunch of work on RPMs 20:15:26 and even more on .debs 20:16:06 would help if we had a keen user that helped with packaging 20:16:15 on deb 20:16:22 so lets move on to webui 20:16:31 #topic webui status 20:16:32 Hopfully you all got a chance to look at my email to the list. 20:16:35 Happy to take feedback. 20:16:37 i'll need to go in 4 minutes 20:16:47 My plan of action is as partially mentioned in the email: 20:16:49 - setup Launchpad & create blueprints (been working on that this afternoon) 20:16:51 - unit tests 20:16:53 - deployment on devstack 20:16:55 - update docs 20:16:57 thoughts? 20:17:29 does it need the lauchpad presence? 20:17:35 radez: do you want to switch to the released python-heatclient? it probably has enough now 20:17:53 I've been using master stevebake 20:17:53 haven't looked yet unfortunately. still need to find a computer that will actually play those 20:18:01 when we get to core/whatever it will be merged into horizon? 20:18:18 is there a big difference between master and released? 20:18:36 asalkeld: maybe not, should I scratch the LP setup? 20:18:50 well I am just asking 20:18:57 radez: currently not, but using a released version will help new users get started 20:19:03 I don't know for certain if it will be merged in 20:19:18 why not ask the horizon guys 20:19:23 seems like now Heat is in incubation, we should at least ask about merging it 20:19:31 kk, I'll get intouch with them 20:19:32 what their opinion is 20:19:46 just less work for you 20:19:59 admin stuff is a pita 20:20:33 so radez you happy with the progress 20:20:57 radez: do you want help with devstack? 20:21:07 I think so, I'd like some feed back on what you guys would like to see it in 20:21:21 ok 20:21:32 I haven't yet - still morning 20:21:45 I'm starting to get pulled into another project so we need to have a plan if I'm to continue developing it 20:21:46 I'll look at the screencast when I have bandwidth 20:21:50 I'll get there and give you some feedback 20:22:00 cool thx 20:22:14 #action checkout the demo 20:22:31 #topic g2 20:22:50 so we need to release on jan 10 20:23:04 with the holidays in the middle 20:23:31 so we have maybe 2 weeks now and 1 week after 20:23:37 (the holiday) 20:23:41 i will be around mostly 20:23:54 I'll be on holiday until the 14th 20:23:55 so we should start looking at bugs a bit more 20:24:02 apart from stats 20:24:03 ok 20:24:21 and pay attension to the target release 20:24:27 and docs 20:24:29 (of the bugs) 20:24:37 yea, that's right 20:24:52 so are all the bp done? 20:25:07 they don't say so 20:25:21 Add an OpenStack ReST API 20:25:27 zaneb, you done right? 20:25:29 zaneb: could you update that? 20:25:33 sure 20:25:38 it says unknown 20:25:54 not to say there's nothing more to do, but the feature exists 20:26:04 stevebake, quantum is still in progress 20:26:29 they keep adding features! 20:26:33 zaneb, done if the feature work done - we can raise bugs after that 20:26:45 yep 20:26:56 stevebake, well you have to define what you are going to do 20:27:06 can't have a moving target 20:27:12 yep, i'll break up the bp 20:27:22 done 20:27:42 cool 20:28:22 seems like a bunch of ubuntu related bugs 20:28:55 ok - well I think you get the idea, lets make our first openstack release good 20:29:12 whew, walking and typing is hard 20:29:27 #topic open discussion 20:29:42 fyi, openstack common has been updated to depend on something not packaged in fedora (extras) 20:29:51 * stevebake is sitting in a room with 300 kids 20:30:01 stevebake, sssh 20:30:13 ;) 20:30:18 back to school 20:30:22 jpeeler: our setup.py should handle that now 20:30:34 I hate dependencies like that 20:30:37 oh really? ok then 20:30:49 so the other projects will drag it in too 20:31:01 stevebake: actually, via a pip install? going to create a packaging mess 20:31:03 (if it is in oslo) 20:31:04 will have to wait for packaging. lifeless_ wrote extras 20:31:27 lovely name 20:31:28 jpeeler: for devstack it will do a pip-install 20:32:02 we may as well use it for our conditional imports 20:32:18 I am done, anything else ... 20:32:32 nope 20:32:35 #endmeeting