Re: Serving Remote Kickstart/Snippet Files
These changes have been pushed to cobbler master. Please let me know
if you experience any troubles with kickstart files or snippet
replacement. In theory, unless you enable the functionality, nothing
should change for the average user.
Cheers,
Devan
On Wed, Dec 30, 2009 at 10:00 AM, Devan Goodwin <dgoodwin(a)rm-rf.ca> wrote:
Just wanted to post about some work I'm doing to support
fetching
kickstarts and snippets over HTTP (and likely FTP/NFS as well). This
is to allow tighter integration for larger systems looking to
incorporate Cobbler. I wanted to post a little about what I've found
and plan to do in case it raises any alarms.
It appears you can already specify kickstarts as direct URLs, the only
caveat is that we don't do snippet replacement on them and just pass
the URL through directly to the client. I'm planning to modify this to
actually do the templating on the fly, and pass a cobbler hosted URL
for the kickstart to the client.
Snippets are expected to be stored on the local filesystem, as defined
by the /etc/cobbler/settings snippetsdir setting, I'm planning to
change this to support URLs as well. That might be a little sluggish
giving the multiple locations we check snippets for to support the
per-system and per-profile snippet functionality, but it should not
impact regular standalone cobbler users.
The kickstart behavior may need to be disabled by default in a config
setting so as not to impact existing users. The snippets should be
fine, just keep your snippetsdir pointing to the local filesystem and
nothing should change.
Let me know if you have any thoughts concerns or suggestions.
Thanks,
Devan
--
Devan Goodwin <dgoodwin(a)rm-rf.ca>
http://rm-rf.ca
--
Devan Goodwin <dgoodwin(a)rm-rf.ca>
http://rm-rf.ca