> -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: Monday, July 08, 2013 1:56 PM > To: dev@cloudstack.apache.org > Subject: Re: Using the ACS simulator for jclouds "live" tests - some > questions. > =) > > On Thu, Jul 04, 2013 at 08:49:52PM +0530, Prasanna Santhanam wrote: > > On Mon, Jun 24, 2013 at 11:08:20AM -0700, Andrew Bayer wrote: > > > - At least one available simulator template (best-case would be > > > Ubuntu > > > 10.04 or 12.04) that can be "booted up" out of the box - for > > > whatever reason (I honestly can't tell, from the brief dive I did > > > through the code), all the builtin templates come up with > > > isready=false in the listTemplates output, which makes jclouds think > > > there are no templates, etc, etc... I thought this is because > > > they're all in Allocated state, not Ready, but even changing them to > Ready in the DB didn't do the trick. > > > > The guest OS is something that doesn't matter to the simulator. > > Whatever you ask for will be deployed. One limitation of the simulator > > is that it keeps CloudStack 'happy' by telling it it's got whatever is > > requested. So any negative scenarios will be harder to test without a > > change in the simulator. > > > > The templates issue still exists but with cloudmonkey you can register > > your template and it will come to ready state: > > > > cloudmonkey>> register template format=RAW hypervisor=Simulator > > cloudmonkey>> isfeatured=true ispublic=true name=tiny displaytext=tiny > > cloudmonkey>> url=http://test.url.com/test.raw > > cloudmonkey>> ostypeid=bb62589e-e3cd-11e2-ad39-ea6434daa8ba > > cloudmonkey>> zoneid=55318568-8d4b-412c-8c10-82f47651eb51 > > I've been using [1], and I keep hitting an issue with finding the template > prior > to creating a VM. > > What's the simulator trick to convincing the server that the templates are > "Ready"?
Seems there are bugs related to simulator after object store branch is merged, I am fixing the simulator to work with latest storage code. > > Snipped results: > > > [INFO] --- exec-maven-plugin:1.2.1:exec (integration-test) @ cloud-marvin -- > - ERROR Test Deploy Virtual Machine ... ERROR ERROR ERROR Test to create > disk offering ... ok Test to update existing disk offering ... ok Test to > delete > disk offering ... ok test update configuration setting at zone level scope > ... ok > Test guest vlan range dedication ... ok Test to update a physical network and > extend its vlan ... ERROR ERROR Test to acquire a provisioned public ip > range ... ok Test to create a portable public ip range ... ok Test public IP > range > dedication ... ok Test for create region ... ok ERROR > > ========================================================== > ============ > ERROR: test suite for <class > 'integration.smoke.test_affinity_groups.TestDeployVmWithAffinityGroup'> > ---------------------------------------------------------------------- > Traceback (most recent call last): > File "/usr/local/lib/python2.7/dist-packages/nose/suite.py", line 208, in > run > self.setUp() > File "/usr/local/lib/python2.7/dist-packages/nose/suite.py", line 291, in > setUp > self.setupContext(ancestor) > File "/usr/local/lib/python2.7/dist-packages/nose/suite.py", line 314, in > setupContext > try_run(context, names) > File "/usr/local/lib/python2.7/dist-packages/nose/util.py", line 469, in > try_run > return func() > File "/home/sg- > user/cloudstack/test/integration/smoke/test_affinity_groups.py", line 81, in > setUpClass > cls.services["ostype"] > File "/usr/local/lib/python2.7/dist- > packages/marvin/integration/lib/common.py", line 141, in get_template > ostypeid) > Exception: Exception: Failed to find template with OSTypeID: f7691800-e7e9- > 11e2-8591-02004f97000b
