Image catalog structure
Use this information as a reference for creating a valid image catalog.
The image catalog JSON file includes the following two high-level sections:
images: Contains information about the created images. The burned images are stored in the
versions: Contains the
cloudbreakentry, which includes mapping between Data Hub versions and the image identifiers of burned images available for these Data Hub versions.
The images section
The burned images are stored in the
base-images sub-section of
base-images section stores one or more
image “records”. Every image “record” must contain the date, description, images, os,
os_type, and uuid fields.
|date||Date for your image catalog entry.|
|description||Description for your image catalog entry.|
|images||The image sets by cloud provider. For AWS, an image set must store the virtual machine image IDs by the related region of the provider. The virtual machine image IDs come from the result of the image burning process and must be an existing identifier of a virtual machine image on the related provider side.|
|os||The operating system used in the image.|
|os_type||The type of operating system which will be used to determine the default
Cloudera Manager and CDP Distro repositories to use. Set
|package-versions||The package versions used for Salt (
The versions section
versions section includes a single “cloudbreak” entry, which maps
the uuids to a specific Data Hub version:
|versions||The Data Hub version(s) for which you would like to use the images.|