[
https://issues.apache.org/jira/browse/JCLOUDS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715559#comment-13715559
]
ASF subversion and git services commented on JCLOUDS-199:
---------------------------------------------------------
Commit 48b499c63661cb4c3febeaad0c25d98c3c3a5d84 in branch refs/heads/master
from [~abayer]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;h=48b499c ]
JCLOUDS-199. CloudStack live tests against ACS 4.2 simulator cleanup.
- ACS 4.x doesn't like taking SSH pub keys from the filesystem, so
generate them on the fly.
- vm.getDisplayName() can be null now.
- Add new possible resource limit types.
- Default to looking template=osFamily=CENTOS, since that's the only
template guaranteed to be there in the simulator.
- Use adminJobComplete instead of jobComplete in admin tests
- Accept capacity/usage/etc of 0.
- Premium configuration category not present in ACS.
- Sleep a bit between deleting a domain and verifying it's not there
any more. Also expect an IllegalStateException.
- Given that there are issues deleting zones at the moment (through
the UI, too), use a different zone for pod and zone tests.
Still failing tests:
- pretty much everything that creates a VM and expects to log into it,
but that's simulator-specific.
- Zone deletion, due to a bug in ACS, apparently.
- Registering and creating templates
- creating volumes from snapshots, and attaching volumes
> Live test failures for CloudStack against ACS 4.2 latest
> --------------------------------------------------------
>
> Key: JCLOUDS-199
> URL: https://issues.apache.org/jira/browse/JCLOUDS-199
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 1.6.1
> Reporter: Andrew Bayer
> Assignee: Andrew Bayer
> Fix For: 1.7.0, 1.6.2
>
>
> I've been able to start running tests against the ACS 4.2 simulator (see
> https://github.com/vogxn/docs/blob/master/Marvin.md for how to set it up -
> basically, run every mvn command on there, then go find the user it creates
> besides admin, create API keys for that user, and run the jclouds live tests
> with that user's creds) and am finding a number of failures we can actually
> do something about (as well as a bunch of failures that are, I think,
> simulator-specific - listed below):
> - Any test that tries to create an instance and SSH into it, since the
> simulator instances obviously aren't *real* instances
> - HypervisorApiLiveTest, which expects to find the same hypervisor list for
> all zones as in a specific zone, which isn't the case since the only zone
> only supports the simulator hypervisor.
> - ISOApiLiveTest can create ISOs, and mark them public, but they never hit
> "ready" and so listing them fails.
> - TemplateApiLiveTest seems to only want to create/register templates on
> basic networks, and at the moment, the simulator only works with advanced
> networks.
> - VolumeApiLiveTest seems to be failing due to the simulator hypervisor not
> actually supporting attaching volumes, but I could be wrong about this.
> More work to come - thanks to [~tsp] for getting me this far!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
