Adjust lvm and tftp profiles for SLE15 #111
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adjustments include following changes: * adjusted ntp client * registration section * adjusted software patterns and defined product We also have introduced some variables. REG_CODE variable should contain registration code for the product, and cannot be stored in git. REG_SERVER should contain url of the registration server, which has build number in the url, so has to be replaced dynamically. For example: http://all-400.4.proxy.scc.suse.de
rwx788
force-pushed
the
poo#28349_sle15
branch
from
d7f245c
to
9aa16b0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adjustments include following changes:
We also have introduced some variables. REG_CODE variable should contain
registration code for the product, and cannot be stored in git.
REG_SERVER should contain url of the registration server, which has
build number in the url, so has to be replaced dynamically.
For example: http://all-400.4.proxy.scc.suse.de
As per https://fate.suse.com/323373 it's not clear what will happen to xinetd and tftp profile may require additional changes.