14:00:16 <swamireddy1> #startmeeting EC2-API
14:00:17 <openstack> Meeting started Tue Mar 31 14:00:16 2015 UTC and is due to finish in 60 minutes.  The chair is swamireddy1. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:18 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:20 <openstack> The meeting name has been set to 'ec2_api'
14:00:38 <swamireddy1> ping alevine
14:00:44 <alevine> pong
14:00:47 <swamireddy1> ping rushiagr
14:01:01 <swamireddy1> alevine: Welcome
14:01:29 <andrey-mp> #help
14:01:44 <swamireddy1> alevine:  As this is first meeting and need to check the currnet status
14:01:57 <swamireddy1> alevine: on the EC2 APIs
14:02:14 <swamireddy1> andrey-mp: Need help here?
14:02:20 <andrey-mp> no
14:02:29 <swamireddy1> andrey-mp: cool
14:03:16 <alevine> swamireddy1: Status of which EC2 API are you interested in? nova or stackforge?
14:03:19 <swamireddy1> alevine:  Currently EC2 API standalone project...how many EC2 APIs supported mean implemented and tested?
14:03:43 <alevine> swamireddy1: I don't understand the question.
14:03:57 <swamireddy1> alevine:  Is not NOVA any more as its (going) deprecated soon
14:04:28 <swamireddy1> alevine: so we will talk on stackforge only, eventually its called as standalone EC2 API
14:04:34 <alevine> swamireddy1: ok
14:05:20 <swamireddy1> alevine: OK. Q is: How may EC2 API supported the stackforge project?
14:05:46 <swamireddy1> alevine:  Are there any reviews pending?
14:05:52 <alevine> swamireddy1: What do you mean by "how many EC2 API"? There is only one EC2 API.
14:06:43 <alevine> swamireddy1: Review there appear and get closed all the time. There are some ongoing at the moment.
14:07:10 <swamireddy1> alevine: EC2 API is live APIs for ex: create_instanace, terminate_instance, stop_instance,etc all are EC2 APIs
14:07:42 <swamireddy1> alevine: Cool. Please let us know, if any review pending
14:07:50 <alevine> swamireddy1: Well, I can't agree with such definition. EC2 API - is a set of the commands you just listed.
14:08:02 <swamireddy1> alevine: so that we review the same asap
14:08:32 <alevine> swamireddy1: You mean the reviews for changes in nova?
14:08:51 <alevine> swamireddy1: Or reviews in the stackforge?
14:08:54 <swamireddy1> alevine: Iam ok with as set commands...
14:09:23 <alevine> swamireddy1: There is a list of limitations in the README and blueprint as I recall. The rest is supported.
14:10:00 <swamireddy1> alevine: I guess, we won´t go with Nova EC2 APIs review, as its going to deprecate and Nova team also may not agree for review and merge the code ATM
14:10:19 <swamireddy1> alevine: Great :(
14:10:54 <swamireddy1> alevine: so expect limitations mentioned in the README, rest should work...
14:11:09 <swamireddy1> alevine: :)
14:11:09 <alevine> swamireddy1: yes
14:11:32 <rushiagr> sorry, I'm late
14:11:44 <swamireddy1> rushiagr:  welcome
14:12:29 <swamireddy1> alevine:  We need to plan and work toward the standalone EC2 API support...
14:12:40 <swamireddy1> any inputs or suggestions are welcome
14:13:39 <alevine> swamireddy1: Well, for now we're totally ok. Since it's an independent project, we're not dependent anymore on nova, now that they approved our extensions.
14:14:11 <swamireddy1> alevine: Good
14:14:59 <swamireddy1> alevine:  We are the team to make the standalone EC2 API project sucessful...
14:15:06 <alevine> swamireddy1: Honestly speaking, I don't see much value in this meeting in the future, because there is not much to discuss at the moment. Whatever's needed we can ask in the mailing list. I understood it was suggested to have this meeting when there was need to discuss bugs in nova's EC2 API and necessary extensions. But for now nothing is required.
14:16:36 <swamireddy1> alevine:  I wont agree fully. But weekly meeting may not needed...But atleast we should meet bi-wekly and need see how we ate going...
14:17:48 <swamireddy1> rushiagr: Do you any thoughts?
14:17:59 <rushiagr> (or maybe if we don't have anything to discuss, we can close off the meeting in 10 mins)
14:18:54 <swamireddy1> rushiagr: I aggre and we need not use full 60 min. time slot...we are ok and no issues, we can close this meeting in 15-30 min...
14:19:06 <rushiagr> swamireddy1: right
14:19:09 <swamireddy1> alevine: what is your opinion
14:19:48 <alevine> alevine: Yes, I guess we can close the meeting and keep in touch in mail until we have something to discuss.
14:20:28 <swamireddy1> sure....
14:20:38 <swamireddy1> rushiagr: Do you have anything?
14:20:47 <rushiagr> nope
14:21:00 <swamireddy1> no items to discuss, we can end the meeting
14:21:12 <swamireddy1> ok. Thank for joining the meeting
14:21:15 <swamireddy1> #endmeeting