Add the ability to enable minimal ISO support for all platform types,
not just External. Adds a new flag to the 'agent create image' command.
Still WIP as dev-scripts testing needs to be done and integration tests
added.
- Renamed `ipxeBaseURL` to more generic `bootArtifactsBaseURL`
- Removed unwanted lint
- Added integration tests to create minimal ISO for external platform with and without bootArtifactsBaseURL in agent-config.yaml
- Fixed existing integration tests to include change of name from `ipxeBaseURL` to more generic `bootArtifactsBaseURL`
- Added BootArtifactsBaseUrl and bootArtifactsPath into parent asset AgentArtifacts
- AgentArtifacts also depends on AgentConfig asset
- Moved common code to generate rootfs.img file into extractRootFS() in AgentArtifacts asset
- If the bootArtifactsBaseURL is specified, construct the custom rootfs URL otherwise default to the URL from the RHCOS streams file
- For external platform when the bootArtifactsBaseUrl is specified, output the rootfs file alongside the minimal ISO
- For all other platforms, continue generating full ISO (no explicit rootfs.img is generated)
- Vendor changes after updating github.com/openshift/assisted-image-service dependency
- set IMAGE_TYPE_ISO to 'minimal-iso' in create-cluster-and-infraenv.service.template when using external platform
- Log an info message to upload CCM manifests
Signed-off-by: Pawan Pinjarkar <ppinjark@redhat.com>
AgentConfig accepts a new optional field pxeBaseUrl.
When provided, an iPXE script file is created
along with other PXE files in the pxe directory.
Signed-off-by: Pawan Pinjarkar <ppinjark@redhat.com>
In Agent based installation ZTP input, one can provide
AdditionalNTPSources in InfraEnv. The sources configured there are
merged by assisted-service with those that are provided by DHCP option
42 (According to RFC 2132) and provided to the openshift-install that
assisted-service runs as MachineConfigs for the different roles defined
for the cluster nodes.
This commit closes the gap we had when installing from install-config +
agent-config.
Signed-off-by: Antoni Segura Puimedon <antoni@redhat.com>
We expect to add more fields to the agent-config file in the future
(thus it is not time for v1 yet), but it will now appear in the 4.12
release and thus must be kept stable. Change the version to v1beta1.
Existing configs with version v1alpha1 will continue to work.
Set the initial version of AgentConfig to v1alpha1, since we are not yet
committing to not changing it.
This is itself a breaking change, as a version will now be required.
The InstallConfig schema does not have a Spec subresource, so
configuration items are added directly at the top level of the file. It
is desirable that the AgentConfig should behave the same. There is no
Status subresource for an AgentConfig either, and in fact not even any
plans to ever install AgentConfig into clusters as a CRD, so there is no
need for a Spec.
This is a breaking change that will require users to change their
existing agent-config.yaml files, so better that it happen now.
The type has been renamed to Config from AgentConfig to address
a golint stuttering issue. golint warns that the package name
and type name both started with agent: agent.AgentConfig.
