-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create VM from template in the Stack Create command #18
Comments
Hi Dave! I'm not able reproduce the issue your are seeing. Can you make sure you can list the template like this: cloudstack-cli command listTemplates name=<template-name> templatefilter=executable You have to make sure the calling user is the owner of the template (or the templates are shared or featured). It won't work if you execute the command as root-admin and are not the owner. Thanks, |
Hi Nik! C:\Users\606457840>cs command listTemplates name="IT_W2K8R2_EE_v1.0_ESXi" templatefilter=executable
C:\Users\606457840>cs command listTemplates name="Win_2012r2_Gold_Hardened" templatefilter=executable
C:\Users\606457840> thanks! |
Just to make sure:
Thanks, |
Ok. I used 'Template' rather than 'template' in the YAML definition file for the stack create. Using 'template' allows it to begin to process. I was using v. 1.5.4, not 1.5.5. However, I receive the following error: C:\Users\606457840\cloudstack\Seqirus>cs stack destroy temp-test-4Aug.yml |
Hi Dave, Thats ugly... :-( Thanks, |
Hello Nik!
I wanted to use your software in a new environment I am turning up. In this environment, as opposed to the previous work I did when using .ISO files for starting VMs, this time I wanted to use a personal template in my cloud account (So, create a VM, then configure/install/modify it, create a snapshot then create a template from the snapshot).
When I try and specify that template within the YML file, I can not access it. It looks like the templates are filtered on Featured and Public, and not listing templates which are Mine.
Thanks!
-dave
British Telecom; Advise/Compute team -- USA.
The text was updated successfully, but these errors were encountered: