WIP: Align config files and scripts with upstream (v30.0.0) #202
Reference in New Issue
Block a user
Delete Branch "mchiappero/Factory:alignment-v30.0.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Copy the configuration files and scripts from upstream to align with v30.0.0. Leave any SUSE specific customization to separate commits that could be re-applied in the future.
This PR depends on #201.
Align config files and scripts with upstreamto WIP: Align config files and scripts with upstream4a9e341f07to51804fea1d51804fea1dto4bc7e416a84bc7e416a8to318765a043As mentioned in #200 - we can't remove this as it's required to allow Ironic to accept the nmstate network-data format instead of enforcing the openstack schema
We should perhaps push a change to the upstream ironic-image so this can be enabled/disabled via a variable as our use-case isn't unique and the idea of disabling the schema was previously discussed upstream so I expect such a change may be acceptable
@@ -0,0 +3,4 @@# Ramdisk logs pathLOG_DIR="/shared/log/ironic/deploy"mkdir -p "${LOG_DIR}"This may reintroduce the spurious restart I fixed in https://build.opensuse.org/package/rdiff/isv:SUSE:Edge:Metal3:Ironic:2024.2/ironic-image?linkrev=base&rev=10 - at the time I couldn't reproduce the same issue with the upstream environment but it would probably be reasonable to push the change upstream anyway?
@@ -0,0 +12,4 @@<Directory ~ "/shared/html">Order deny,allowdeny from allThis reverts the fix I made for https://gitlab.com/sylva-projects/sylva-core/-/issues/2147 but I think it's probably OK since the uefi bootloader is now access via
file://instead of the vmedia webservera9551f2fcbto0efa970293WIP: Align config files and scripts with upstreamto WIP: Align config files and scripts with upstream (v30.0.0)I'm going to drop this PR since in the meantime upstream has move forward with newer releases.
Pull request closed