OK - thanks, Ahmad!
On Tue, Feb 12, 2013 at 1:48 PM, Ahmad Emneina <aemne...@gmail.com> wrote: > exactly, disk or a ridiculous cpu offering. You'll always get a job id > back... > > > On Tue, Feb 12, 2013 at 12:24 PM, Mike Tutkowski < > mike.tutkow...@solidfire.com> wrote: > >> You mean with a ton of disk space that can't be satisfied? >> >> I was thinking such things would fail before getting back a Job ID, but >> CS must just give you back a Job ID and then fail later. >> >> Sounds good - thanks! >> >> >> On Tue, Feb 12, 2013 at 1:11 PM, Ahmad Emneina <aemne...@gmail.com>wrote: >> >>> create a huge service offering might be the easiest, quickest, most >>> reliable failure :) >>> >>> I'm sure there are other creative ways. >>> >>> >>> On Tue, Feb 12, 2013 at 12:08 PM, Mike Tutkowski < >>> mike.tutkow...@solidfire.com> wrote: >>> >>> > Hi everyone, >>> > >>> > I'm just getting started using the CloudStack API. >>> > >>> > I want to call the deployVirtualMachine command. >>> > >>> > The thing is, I'd like to test its failure case. It is an asynchronous >>> > command, so I'd like to get a Job ID and I'd like the job to eventually >>> > (hopefully within a reasonable amount of time) fail. >>> > >>> > Any ideas on how I can do this? >>> > >>> > Thanks! >>> > >>> > -- >>> > *Mike Tutkowski* >>> > *Senior CloudStack Developer, SolidFire Inc.* >>> > e: mike.tutkow...@solidfire.com >>> > o: 303.746.7302 >>> > Advancing the way the world uses the >>> > cloud<http://solidfire.com/solution/overview/?video=play> >>> > *™* >>> > >>> >> >> >> >> -- >> *Mike Tutkowski* >> *Senior CloudStack Developer, SolidFire Inc.* >> e: mike.tutkow...@solidfire.com >> o: 303.746.7302 >> Advancing the way the world uses the >> cloud<http://solidfire.com/solution/overview/?video=play> >> *™* >> > > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *™*
