Page History

...

All tests are written keeping regions in mind. Null value  have been passed for region. To get the endpoint it was making call to describeRegions, which is not supported by Cloudstack so code changes have been made for that.

A  new project cloudsatck-query-ec2  have been created in jclouds. These The changes are in ec2 project. These  changes are on repo in cloudstack-ec2-queryapi branch and  in cloudstack-query-ec2 project .

In summary 13  34  API calls in tests scenarios are passing. Some failing/skipped ones are dependent on failed tests which are expected to pass once the failed test is ok. The APIs which are passing are as follows

1. describeImages
2. describeInstances
3. describeAddresses
4. createVolume
5. describeVolumes
6. describeSnapshots
7. describeAvailabilityZones
8. createKeyPair
9. describeKeyPairs
10. deleteKeyPair
11. createSecurityGroup
12. deleteSecurityGroup
13. describeSecurityGroups

These tests are failing or skipped(dependent on failed tests)

1. authorizeSecurityGroupIngress
2. revokeSecurityGroupIngress
3. createSnapshot
4. createVolumeFromSnapshot
5. deleteVolumeattachVolume
6. detachVolume
7. runInstances
8. terminateInstances
9. deleteSnapshot

...

The API calls which are working fine with jclouds parser after my changes

1. attachVolume
2. detachVolume
3. StopInstances
4. StartInstances
5. RebootInstances
6. DescribeInstanceAttribute
7. CreateImage
8. DeregisterImage
9. DescribeImageAttributeModifyImageAttribute
10. ResetImageAttribute
11. RegisterImage
12. ImportKeyPair
13. AllocateAddress 
14. AssociateAddress
15. DisassociateAddress
16. ReleaseAddress

These tests are failing or skipped(dependent on failed tests) on jclouds as some API call is broken in jclouds

1. authorizeSecurityGroupIngress
2. revokeSecurityGroupIngress

These tests are not implemented in jclouds

1. ModifyImageAttribute
2. GetPassword
3. createTags
4. describeTags
5. deleteTags
6. ImportKeyPair

Below things are in following format

...

1. test scenario
   1. EC2 API Calls made in this scenario (parameters passed)

Below information describe the API calls covered with what parameters. For Example

...

1. 1. )

1. testDescribeImages test scenario tests following API call
   1. describeImagesInRegion API call is made and returns the correct response i.e. parsed successfully by jclouds
   2. describeImagesInRegion API call is made with parameter imageid and returns the correct response i.e. parsed successfully by jclouds.

Example 2. CloudStackQueryEC2KeyPairClientLiveTest

1. testDescribeImages test scenario tests following API call
   1. createKeyPairInRegion API call is made with parameter keyName and returns the correct response i.e. parsed successfully by jclouds
   2. describeKeyPairsInRegion API call is made with parameter keyName and returns the correct response i.e. parsed successfully by jclouds
   3. deleteKeyPairInRegion API call is made with parameter keyName and returns the correct response i.e. parsed successfully by jclouds

Tests which are passing

CloudStackQueryEC2AMIClientLiveTest

...

API Calls which are not called in any tests

...

1. DeregisterImage
2. DescribeImageAttribute
3. ModifyImageAttribute
4. ResetImageAttribute
5. RegisterImage
6. ImportKeyPair
7. AllocateAddress 
8. AssociateAddress
9. DisassociateAddress
10. ReleaseAddress
11. GetPassword
    

...