<p>When using Packer to create a custom image, you need to create a template file in JSON format. In this template file, you need to specify the PACloud Image Builder and Provisioners that create a custom image. Packer has a variety of configurators that can be used to configure custom image content generation methods.</p> <p>You need to customize the following parameter values.</p> <table border="1" cellpadding="0" cellspacing="0" style="width:100%"> <tbody> <tr> <td style="background-color:#ededed; vertical-align:top"> <p><strong>Parameter</strong></p> </td> <td style="background-color:#ededed; vertical-align:top"> <p><strong>Description</strong></p> </td> </tr> <tr> <td style="vertical-align:top"> <p>url</p> </td> <td style="vertical-align:top"> <p>API Address.</p> <p><strong>Note:</strong> When the program detects that the value is empty, it will automatically fill in a default value, so usually no configuration is required. However, if you need to use packer under a private cloud belonging to Ping An, which is not a yun.pingan.com domain name such as Ping An Finance Cloud, you need to fill in the API gateway address of the private cloud.</p> <p>The address of Ping An Finance Cloud is as follows:</p> <p>https:// fincloud.pinganyun.com/api/v1</p> </td> </tr> <tr> <td style="vertical-align:top"> <p>access_key_id</p> </td> <td style="vertical-align:top"> <p>Your Access Key ID.</p> <p>Note: For how to query your Access Key ID, see the appendix for the Access Key ID and Access Key Secret.</p> </td> </tr> <tr> <td style="vertical-align:top"> <p>access_key_secret</p> </td> <td style="vertical-align:top"> <p>Your Access Key Secret.</p> <p><strong>Note:</strong> For how to query your Access Key ID, see the appendix for the <strong>Access Key ID and</strong> <strong>Access Key Secret</strong>.</p> </td> </tr> <tr> <td style="vertical-align:top"> <p>zone_name</p> </td> <td style="vertical-align:top"> <p>The region number used when creating a custom image.</p> <p><strong>Note:</strong> For how to query the region number, see the query region number in the description of the appendix of this document.</p> </td> </tr> <tr> <td style="vertical-align:top"> <p>image_name</p> </td> <td style="vertical-align:top"> <p>The name of a custom image.</p> </td> </tr> <tr> <td style="vertical-align:top"> <p>source_image_id</p> </td> <td style="vertical-align:top"> <p>ID of the Ping An Cloud basic image.</p> <p><strong>Note:</strong> For how to obtain the ID corresponding to the Ping An Cloud image,see the obtaining the ID of the Ping An Cloud base image in the appendix description.</p> </td> </tr> <tr> <td style="vertical-align:top"> <p>provisioners</p> </td> <td style="vertical-align:top"> <p>The type of Packer configurator used when creating a custom image.</p> </td> </tr> <tr> <td style="vertical-align:top"> <p>cpu_amount</p> </td> <td style="vertical-align:top"> <p>The number of CPU cores of the custom image.</p> <p><strong>Note:</strong> If cpu_amount and memory_size_mb are not defined, the cheapest calculation scheme will be selected to generate a custom image.</p> </td> </tr> <tr> <td style="vertical-align:top"> <p>memory_size_mb</p> </td> <td style="vertical-align:top"> <p>Custom image memory size (MB).</p> <p><strong>Note:</strong> If cpu_amount and memory_size_mb are not defined, the cheapest calculation scheme will be selected to generate a custom image.</p> </td> </tr> </tbody> </table> <p>&nbsp;</p>