Confused by "mirror-locally"
by Chris O'Regan
According to the man page, "mirror-locally" does the following:
"When true, specifies that this yum repo is to be referenced directly
via kickstarts and not mirrored locally on the cobbler server. Only
http:// and ftp:// mirror urls are supported when using --mirror-locally=1."
I'm confused. This above seems to describe the exact opposite of what
mirror-locally does in practice. That is, --mirror-locally=1 fetches all
of the packages from the url provided and stores them on the cobbler
server. I have had to set "--mirror-locally=0" to prevent cobbler from
downloading everything in the mirrors I set up with mrepo.
Having said that, looking at the source, it seems that the opposite is
true if we are mirroring from RHN. In this case, mirror-locally must be
set to "0" in order to fetch the packages.
# rpm -q cobbler
cobbler-1.2.4-1.el5
Chris
15 years, 6 months
[PATCH] preliminary patch for template-files
by James Cammarata
Available via git hub: git://github.com/jimi1283/cobbler-template-files.git
I've done some testing on this, but I'm not sure if it's 100% so I'd like
for some others to play with it if they'd like. For those who don't follow
IRC, this patch allows for the templating of random config files via the
--template-files command. This command has the same syntax as the
ksmeta/kopts (space separated list) and honors the --in-place option.
Example:
cobbler profile edit --name test
--template-files="/path/to/template=/path/to/output"
Both the source and destination paths can have variables in them (ie.
$name, $arch, etc.), just don't forget to escape them if you're using
double quotes in the command. If the destination is not an absolute path,
the rendered file will be placed relative to /var/www/cobbler/rendered.
This is currently added on to distros/profiles/systems, though it should
probably be extended to images too.
Let me know if there are any questions/problems.
James C.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
15 years, 6 months
Looking for something to work on?
by Michael DeHaan
I've cleaned up Trac a good bit and there are a lot of ideas, some are
pretty easy to knock out:
https://fedorahosted.org/cobbler/report/1
If you'd like further details, ask me on #cobbler on freenode.
Currently I'm looking at the import and repo patches, followed up soon
by the config management idea we talked about earlier today -- so that's
where I'm spending my time right now. Pretty much everything else is
open and fair game, as are your own ideas if you have features that
aren't listed above.
I think some of the Web app features (i.e. search) are classified as
"very hard" as are the ideas around the new networking object ("cobbler
network add").
However finishing out the "network_config_post" snippet idea from last
month would be a pretty easy item, as would adding the bonding support.
--Michael
15 years, 6 months
FYI -- I'm going to be using our Trac more for bugs and RFEs
by Michael DeHaan
We're getting a bit busier on this list now (and as a project in
general) -- as a consequence I'm going to be keeping track [sic] of
items a bit more closely in Trac now. So if you mention a bug in IRC
or the mailing list, I'll file a ticket and share the URL. If there's
a new feature I need to investigate and merge, I'm also going to file a
ticket. (If you can go ahead and file those tickets, that's even
better!)
As a consequence of everything moving faster I'm also going to be
closing out some backlog RFE's that I realistically think we're not
going to do. If your favorite idea gets closed, you have a couple of
options (A) bring it up on the mailing list (good), and (B) add the code
for it! (better). I'll leave many items open so that folks new to the
project can know of ideas where they can hop in. (I need to mention
that on the Wiki also).
This can probably also help me balance debugging existing things easier
with new development. I'm also probably going to be relying on more
folks to help answer questions in IRC (#cobbler) if possible.
Here's Trac:
https://fedorahosted.org/cobbler/report
Here's where you get an account if you don't have one
https://admin.fedoraproject.org/accounts
Anyhow, just a heads up....
Thanks!
--Michael
15 years, 6 months
Help me edit the troubleshooting docs
by Michael DeHaan
Hi folks,
It seemed I got a lot of the same kind of questions asked a bit lately
on IRC, so I decided to clean up the troubleshooting pages a bit more.
I am guessing lots of folks can help me out better than I can as I'm
blinded by the "I know this app too well" problem.
Can you look over the following and suggest topics and/or edits to answers?
https://fedorahosted.org/cobbler/wiki/TroubleShooting (refactored, added
a topic on install trees vs repos)
https://fedorahosted.org/cobbler/wiki/VirtualizationTroubleshooting
(new page, moved some stuff over)
I also realized I rather uninterstingly just pointed folks to "man koan"
so a lot of people did not understand about how to do virtualized
installs, even though I had thought it was clear.
I added this which could probably also use some outside review to make
sure it explains things right:
https://fedorahosted.org/cobbler/wiki/KoanInstallVirtualGuests
We have all the options like --virt-bridge and stuff though in general
my philosophy with the manpage is to keep things simple and advertise
the Wiki heavily, which I hope is working out for everyone.
If that somehow means we're missing topics on the manpage that explain
the overall view of things though, let me know.
If you'd like to edit the Wiki you will of course need a very simple to
get Fedora account:
https://admin.fedoraproject.org/accounts
This does not require a GPG key, SSH key, or blood sample anymore, so I
would encourage folks to sign up and use it!
--Michael
15 years, 6 months
[PATCH] - importing debian based distros
by Javier Palacios
Hi,
I've started to work in order to allow debian provisioning with
cobbler. I send attached two patches.
The first on is actually not strictly related to debian, and it's a
reorganization of the archs management,
to simplify it and ease smooth addition of other distros: debian calls
amd64 to x86_64, and the idea is
to keep the RedHat names as canonical ones.
The second one does actually allow to import the content of a debian
CD/DVD and create the corresponding
distro. It also creates the profile breeded as debian, although it
might not be usable yet.
There are a couple of open questions that might affect other parts of
cobbler or where just ideas are required.
- the kickstarts for debian. They are called "preseed", and are by far
much more complex than a standard
kickstart. Although not strictly required, it might be better to
have new names for both ks files and directories,
but I think that they can be easyly added to PXE boot options. To
make things worst, ubuntu does allow both
the standard debian preseed and kickstart files.
- the package repositories. Debian follows a quite different approach,
and a single tree can hold many versions
and different architectures. Allowing a cobbler distro to have
multiple architectures might reduce the disk usage
and simplify the repository updating. Due to this fact, a single
debian media can install multiple archs, complexing
a little bit to import the media.
These are the only two points I see on the close horizon, but there
are probably more. It anyone has concerns
or ideas, they are welcome. And if anyone can actually test the
deployment (when it matures a little bit), much better.
Javier Palacios
15 years, 6 months
build on sles10
by Shuichi Ihara
Hi,
I'm attempting to build cobbler on sles10. I installed some packages
that are needed to build the cobbbler. The building is fine, but when I did
"cobbler sync" on sles10, I can see below errors. Do I still have any missing packages?
# cobbler sync
exceptions.ValueError
invalid literal for float(): no package provides redhat
File "/usr/lib64/python2.4/site-packages/cobbler/cobbler.py", line 65, in main
return BootCLI().run(sys.argv)
File "/usr/lib64/python2.4/site-packages/cobbler/cobbler.py", line 44, in run
return self.loader.run(args)
File "/usr/lib64/python2.4/site-packages/cobbler/commands.py", line 69, in run
return fn.run()
File "/usr/lib64/python2.4/site-packages/cobbler/modules/cli_misc.py", line 211, in run
return self.api.sync()
File "/usr/lib64/python2.4/site-packages/cobbler/api.py", line 326, in sync
sync = self.get_sync()
File "/usr/lib64/python2.4/site-packages/cobbler/api.py", line 340, in get_sync
return action_sync.BootSync(self._config,dhcp=self.dhcp,dns=self.dns)
File "/usr/lib64/python2.4/site-packages/cobbler/action_sync.py", line 61, in __init__
self.pxegen = pxegen.PXEGen(config)
File "/usr/lib64/python2.4/site-packages/cobbler/pxegen.py", line 55, in __init__
self.bootloc = utils.tftpboot_location()
File "/usr/lib64/python2.4/site-packages/cobbler/utils.py", line 609, in tftpboot_location
(make,version,rest) = os_release()
File "/usr/lib64/python2.4/site-packages/cobbler/utils.py", line 581, in os_release
return (make, float(version), rest)
Thanks
-Ihara
15 years, 6 months
RE: RH NFS TCP UDP installs
by Tim French
Thanks all.
Since the nfs kickstart line is created from the distro file I changed
it and the resulting ks file looked great. However, koan errs w/
koan: error: no such option: --opts
Here's the diff
i386
10c10
< tree:
'nfs://xxx:/vol/isos/IsoImages/rhel-5.2-server-i386-disc1'
---
> tree:
'nfs://xxx:/vol/isos/IsoImages/rhel-5.2-server-i386-disc1
--opts=tcp'
But it worked.
I'm guessing that editing the distro files is not the best way to do it.
* What does your kickstart template look like?
Also, NetApp's best practices for Linux is to use NFS 4 which is
strictly over TCP.
I used
cobbler import --name=someprefix --mirror=/mnt/nfs
--available-as=nfs://foosball.example.org/somepath
It was smooth.
Timothy French <tim.french(a)utah.edu>
Office of Information Technology, University of Utah
Key fingerprint = 838C F04D AAC8 6D9C 7ED7 2629 925E BF3E 1FD1 826C
This is a bit kludgy, so you might want to rethink why you want to do it.
>> How are folks NFS kickstarting with their Filers using NFS over TCP?
>>
>> The official RH line is to use a boot command line option for RH4.
>>
>>
>> Further research shows:
>>
>> It look like adding
>> --opts=tcp to the nfs line in the ks file would works.
>>
>> Since the ks file is generated on-the-fly how do I get something that
>> looks like this
>>
>> # INSTALLATION TYPE
>> nfs --server $nfs_server --dir $nfs_distro_root/$distro --opts=tcp
>>
>>
>> Timothy French <tim.french(a)utah.edu>
15 years, 6 months
RH NFS TCP UDP installs
by Tim French
I know it's not a cobbler question but maybe someone has run into this
prob.
It seems that RH (and thus cobbler) uses UDP for NFS kickstarts.
How are folks NFS kickstarting with their Filers using NFS over TCP?
The official RH line is to use a boot command line option for RH4.
Further research shows:
It look like adding
--opts=tcp to the nfs line in the ks file would works.
Since the ks file is generated on-the-fly how do I get something that
looks like this
# INSTALLATION TYPE
nfs --server $nfs_server --dir $nfs_distro_root/$distro --opts=tcp
Timothy French <tim.french(a)utah.edu>
Office of Information Technology, University of Utah
Key fingerprint = 838C F04D AAC8 6D9C 7ED7 2629 925E BF3E 1FD1 826C
This is a bit kludgy, so you might want to rethink why you want to do it.
15 years, 6 months
[PATCH 1/1] Fix config to disable restarting of dns-server
by mh
From: Marcel Haerry <haerry(a)puzzle.ch>
If you just "and" the string-variable it will always be true,
threfor we need to compare it as a string.
Signed-off-by: Marcel Haerry <haerry(a)puzzle.ch>
---
triggers/restart-services.trigger | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/triggers/restart-services.trigger b/triggers/restart-services.trigger
index 6eac017..38e94e7 100644
--- a/triggers/restart-services.trigger
+++ b/triggers/restart-services.trigger
@@ -33,7 +33,7 @@ if manage_dhcp != "0":
print "- error: unknown DHCP engine: %s" % bootapi.dhcp.what()
rc = 411
-if manage_dns != "0" and restart_dns:
+if manage_dns != "0" and restart_dns != "0":
if bootapi.dns.what() == "bind":
rc = os.system("/sbin/service named restart")
elif bootapi.dns.what() == "dnsmasq" and not has_restarted_dnsmasq:
--
1.5.5.1
15 years, 7 months
