On Wed, 2012-11-21 at 11:52 +0200, [email protected] wrote: > > - part5_test.rb will fail on checking status after /stop /start. I think > > this a real issue as executing /stop /start resturns a 200 but the state > > never changes > > - part3_test.rb just leaves a comment that Deltacloud CIMI does not > > support MachineTemplates right now > > - cep_test.rb doubles as part1 > > - part4_test.rb is incomplete - please see > > https://issues.apache.org/jira/browse/DTACLOUD-375 > > fixed this - ready for testing please (patches at > http://tracker.deltacloud.org/set/145) - I set jira to resolved if it > works close it otherwise reassign to me > > > - Tests are written to be run with the mock provider, as they stand, in as > > much as we would need to include polling after a action is executed on a > > real provider. I am open to adding this polling now so that the tests are > > compatible with all providers we test > > right. well, we do the polling for the deltacloud equivalent tests (e.g. > for cleaning up created resources machines etc) so I don't think this is > a problem. I'm not sure what will be tested at the plugfest - perhaps > only mock (David's input required here).
Yes, I think we need to add the polling now, at a minimum, to enable FGCP as Dies said. > Besides setting up the polling, another thing to do is make sure the > right creds are parsed from the config file (right now there is only one > set under 'cimi') - you could reuse the creds from the deltacloud > section of the config file. However you'd still need driver specific > sections under cimi for the 'preferred' bits. We don't need to change anything about hte config files - people can just have multiple config files and pass them in with 'rake CONFIG=fgcp-config.yaml test:cimi' or similar David
