Re: [xcat-user] best practices for packages

2018-06-22 Thread Russell Auld
You're exactly right - the "otherpkgs" repo is for packages that are not part of the official OS distribution. Note that if you use "osimage" then you can specify a comma-separated list of package directories for both pkgdir and otherpkgsdir. You will need to run "createrepo" in each of the pac

Re: [xcat-user] [External] Re: xCAT node name invalid characters or hard codelimitations ?

2018-06-22 Thread Jarrod Johnson
Except in the domain portion, ‘_’ is a common prefix for SRV records, for example. The host name portion is still technically restricted per IETF standards. Of course, a lot of dns implementations have started accepting _ ‘just because’, but I don’t think an RFC ever came out to technically bl

Re: [xcat-user] [External] Re: xCAT node name invalid characters or hard code limitations ?

2018-06-22 Thread Jarrod Johnson
To add to this, at least at the time there were a number of situations where applications would fail if there were an underscore in a name. So we added filtering out _. This is all rooted in https://tools.ietf.org/html/rfc952 which did not include _ in the host name. I have not revisited the

[xcat-user] best practices for packages

2018-06-22 Thread Jeff Berry
Good morning all, when building images with extra packages, what is considered best practice? Or to rephrase, what are the pros and cons of: * adding lots of packages to the pglist file, as opposed to * creating a repo and using otherpkglist and otherpkgdir I can see where ot

Re: [xcat-user] xCAT node name invalid characters or hard codelimitations ?

2018-06-22 Thread Kevin Keane (USD)
It’s more fundamental than xCAT. The _ (underscore) is not allowed in DNS at all; xCAT simply follows that rule. Sent from Mail for Windows 10 From: peter CZ1 Peng Sent: Thursday, June 21, 2018 10:31 PM To: xCAT Users Mailing list Subject: [xcat-user] xCAT node name invalid characters or hard co