> Sent: Monday, February 19, 2018 3:07:41 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Potential backward incompatibility problem in building
> SystemVM
>
> Daan, Rohit
>
> With the new packer build (4.11+) one cannot give "blah" to be the final
> name of th
he.org
Subject: Re: Potential backward incompatibility problem in building SystemVM
Daan, Rohit
With the new packer build (4.11+) one cannot give "blah" to be the final
name of the template.
The script will look for a folder called "blah" in appliance folder which
does not e
Daan, Rohit
With the new packer build (4.11+) one cannot give "blah" to be the final
name of the template.
The script will look for a folder called "blah" in appliance folder which
does not exist. But in before
packer (prior to 4.11) one can give "blah" to be the final name, because
the script wou
Khosrow,
The name 'systemvmtemplate' refers to the name of the folder, the build.sh
script now accepts a folder that has the packer definitions such as the
built-in one or any other future packer based templates. The systemvm
template's file name is never used for compatibilities sake, one can
Khosrow,
If I read your description correct you want the script to (effectively)
build the systemvm64template if I pass appliance name "bla" on the
commandline. I don't think we want that. What am I missing?
On Fri, Feb 16, 2018 at 5:58 PM, Khosrow Moossavi
wrote:
> Hi
>
> I just noticed that t
