15:26:52 #startmeeting 15:26:53 Meeting started Tue Nov 15 15:26:52 2011 UTC. The chair is zul. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:26:54 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:27:09 sorry for being late, welcome to the nova ec2 api team meeting 15:27:24 The agenda for this meeting is the following: 15:27:27 1. Introduction 15:27:32 2. Bug Workflow 15:27:34 3. Testing 15:28:00 so lets get started 15:28:02 #topic 15:28:09 #topic Introduction 15:28:37 so the purpose of the nova ec2 api team is to take care of the EC2 API on nvoa 15:29:01 in diablo, alot of work was done for the Openstack API but the EC2 API was left a bit to lag 15:29:55 so the nova ec2 api team is a group of interested developers parties that want to use the EC2 API on nova 15:30:13 any questions so far? 15:31:03 so we have a lp team called the nova-ec2-api team which is free for anyone to join 15:31:18 so lets get to the second topic 15:31:27 #topic Bug Workflow 15:32:24 so there is a number of bugs on launchpad that deals with especially with the EC2 API, this week i am going to start going through the bugs on nova, glance, and swift and start tagging them specifically as ec2 15:32:57 after that happens then we can start to follow the regular bug worklfow, getting them reviewed in git and getting them fixed for essex 15:33:08 any comments so far? 15:34:26 is there any bugs that people want to bring up if not I can go into testing as well 15:34:53 ... 15:35:18 I may have one 15:35:18 ok then 15:35:20 one sec 15:35:21 sure 15:35:40 https://bugs.launchpad.net/nova/+bug/813685 15:35:41 Launchpad bug 813685 in nova "EC2 API input validation is poor" [Wishlist,In progress] 15:35:58 there's not much to say other than this died during the switch to git/gerrit 15:36:06 right 15:36:12 but wanted to call it out so people know I'll be porting it 15:36:20 sweet! 15:36:29 kewl 15:36:31 how far along are you? 15:36:37 and I'd welcome a review from ec2-api team 15:36:47 ill be happy to do it 15:37:07 and im sure other people from canonical would be happy to review it as well 15:37:21 I just need to merge HEAD (and resolve a fair bit of hairiness) 15:37:33 ill look forward to it 15:37:54 which leads me to the last topic which is testing 15:37:57 #topic testing 15:38:55 so there are a couple of testing frameworks that i am aware of that we can use. I think it would be important to have those tests in jenkins so we can run a regular automated test on the EC2 API 15:39:10 this would require help from the openstack-ci team 15:39:14 ttx: what do you think? 15:39:54 I think I would need to talk to mtaylor about getting that started somehow 15:40:09 arro? 15:40:11 reading 15:40:46 yes 15:40:52 we should definitely test things 15:40:59 ok ill poke you after the meeting then 15:41:14 should we incorporate those into openstack-integration-tests? 15:41:29 or are you talking about third-party ec2 api test things? 15:41:30 cloudscaling i believe has a pretty comprenhensive testsuite that takes care of it as well 15:41:47 and are you talking unittest-level testing? or are we talking about testing against an installed openstack? 15:41:50 third-party testing...ill poke you about it after the meeting 15:41:52 I'm representing cloud scaling and will plug our tests in a bit 15:41:55 ok. great. 15:41:59 awesome 15:42:02 sorry, autocorrect "Cloudscaling" 15:42:09 mwhooker_: awesome 15:42:36 the quick response here is a) awesome on integrating - b) I also plan on getting some jobs going running the test suits from various connectors, like libcloud and jclouds 15:42:41 mwhooker_: if you want to plug your tools now would be a good time 15:42:53 so - hopefully between all of that things will be happy making 15:43:22 aws-compat, our testing tools is available here: https://github.com/cloudscaling/aws-compat 15:43:50 zul: sorry for joining late... are you focusing primarily on in-tree ec2 stuff? 15:44:07 mtaylor: yes we are 15:44:13 it's a functional test: it runs through some use-cases and tries to tell you which of the cases aren't working 15:44:38 mwhooker_: cool...how does the nova ec2 api looking so far? 15:44:49 it has two failing tests 15:44:53 mwhooker_: lovely. looks like something that could at least physically be merged in with openstack-integration-tests ... whether or not that's the right choice I'll leave as a different conversation 15:45:10 mtaylor: could be. 15:45:30 one test is a known bug, the other I'd like someone to verify before I add it as a bug 15:45:59 sounds like a todo item 15:46:25 the other thing I'd like to do is get someone else to run it ;) 15:46:45 mwhooker_: its actually on my todo list for this week as well 15:46:53 excellent 15:47:15 I'll be available if you have any troubles 15:47:22 cool.. 15:48:16 so the last thing i want to bring up is this is a good time for everyone, this is the first meeting and we are going to get some more traction in the long run, I do want this to become a weekly meeting as well 15:48:23 what do others think? 15:48:23 zul, sorry for being late. i was thinking this was a bit later in the day. 15:48:42 does anyone know if ec2 api is now functional out of the box on devstack ? 15:49:05 jeblair: ^^ 15:49:18 it was not a couple weeks ago when i tested, and having that functional is a major helping hand 15:49:39 weekly meeting sounds great, though I wonder if we could move it back a bit 15:50:09 mwhooker_: i was thinking 18 UTC 15:50:19 * mtaylor does not know that ... although we're working on getting devstack hooked in to gating, so a) it should be easy enough to add support once we do and b) I guess we'll need that before we can start running ec2 api tests in jenkins 15:50:23 zul: another meeting at that time 15:50:29 (Keystone) 15:50:38 son of a.. 15:50:48 sounds good 15:50:50 is there a list of when meetings happen? 15:50:53 maybe another day 15:50:59 http://wiki.openstack.org/Meetings 15:51:00 there is even a gcal. 15:51:07 yeah ill send out an email 15:52:03 smoser: its on my todo list as well :( 15:52:26 ok. thank you. 15:52:34 #topic Open Floor 15:52:48 is there anything else someone wants to bring up 15:53:02 is there *any* documentation on how you set up a functional ec2 api end point given keystone ? 15:53:36 not that i know of 15:53:36 it didn't "just work" and i didn't know where to go from there when i was playing with devstack. 15:54:20 smoser: maybe hunt down the keystone developers 15:54:42 alright. maybe i play with this today. 15:55:09 smoser: I believe koolhead is looking at doing it at the moment. 15:55:51 i think the keysone ppa needs some love as well at least 15:56:01 link: http://keystone.openstack.org/configuration.html 15:56:13 see "Creating Keystone Credentials" 15:56:29 er.. "Creating EC2 Credentials" 15:56:53 My other area of concern is the EC2-compatible way of registering images (objectstore/S3 wrapping) 15:57:11 joesavak, does that also work for the public and private key path ? 15:57:18 If that's to be kept in nova, it needs some love 15:57:31 ttx: right 15:57:32 which is what is required for registering images 15:57:44 smoser: not sure 15:59:19 zul: I wonder how it can even work, with bugs like https://bugs.launchpad.net/nova/+bug/890486 15:59:21 Launchpad bug 890486 in nova "Cannot create image with kernel_id and ramdisk_id in S3ImageService" [Low,In progress] 16:00:00 ttx: we need to start tagging ec2 stuff more 16:00:07 will do 16:00:19 It seems apparet that testing and certification is currently weak. 16:00:39 and with that we have run out of time thanks for coming can we continue this conversation on #openstack-dev 16:00:42 #endmeeting