Future of Satellite
by Konrad Scherer
Hello all,
I have seen this mentioned in several other places (puppet users) but not here.
As cobbler is integrated with Satellite I think this is of interest to the
people subscribed to this list. At the 2011 RedHat summit there was a
presentation at about the future of Satellite[1].
There is a pdf of the slides of the presentation[2]. Of interest to cobbler
users is the new provisioning engine: The Foreman (pg 39). Interestingly v5 of
the pdf described The Foreman as "cobbler on steroids" and that item has been
removed from v7.
Some obvious questions:
1) Will the next major version of Satellite support both cobbler and foreman?
2) Will there be any tools to help users of cobbler migrate to foreman?
As a happy and grateful user of cobbler I have noticed that the cobbler project
is not as active as it used to be. Is it time for me to move on?
Konrad
[1]
http://www.redhat.com/webinars/?zPage=2011-07-07-Future-of-Red-Hat-Networ...
[2]
http://www.redhat.com/summit/2011/presentations/summit/whats_next/thursda...
12 years, 5 months
Snapshotting repos
by Gerhardus Geldenhuis
Hi
I am working on a simple internal file based (symlinks) method to snapshot
repos on a monthly basis making use of cobbler. For various reasons we are
not using spacewalk to manage that... I am thinking with a Red Hat / CentOS
hat on so probably not considering other OS'es. My question is simple, do
you think that adding a repo snapshot ability to cobbler is worthwhile or is
that task better suited to be implemented in spacewalk or other management
software? If our interim solution becomes more permanent, I thought it would
be useful to build this into cobbler rather than tagging it on afterwards.
However things get more complicated if you take into consideration that
these snapshots potentially need to be replicated across multiple cobbler
servers and all of the other things I have probably not considered. So
before I go off on a tangent I thought I would get some opinions.
Regards
--
Gerhardus Geldenhuis
12 years, 5 months
cobbler and multiple "disks"
by Greg Swift
So, i'm prepping our rhevm infrastructure and made a base set of bits that i
will hopefully eventually be able to get into koan so I can push builds
(yay). During this though I found that I was limited in cobbler only
handling 1 virtual disk. I was thinking about maybe implementing the basic
structure that the network interfaces use for the disks. any thoughts?
(i'm also not promising this quickly, but its on my list to finish this
project).
-greg
12 years, 6 months
Seeking feedback from build ISO users
by Jörgen Maas
Hi all,
I'm currently working on some patches regarding the cobbler buildiso feature.
Now i'm wondering who is using the netboot iso and the profiles as
provided in the boot menu, instead of the system records in the menu?
Could you also describe your use case, e.g. why are you using this
feature?
Any feedback would be greatly appreciated!
Thanks
--
Grtz,
Jörgen Maas
12 years, 6 months
[PATCH] power_virsh.template can fail
by Bill Peck
Attached is a patch for power_virsh.template which adds a domstatus
check to see what the current status of the dom is. This is needed
because issuing a power off on an already off dom will produce an error.
This has been tested.
12 years, 6 months
[PATCH] - do not fail if hostname is resolvable
by Miroslav Suchý
>From git comment:
in commit 588756aa7aefc122310847d007becf3112647944 cobbler start using
IP address in kickstart path due s390x, but in BZ 253274 we have example
where hostname is not resolvable from the location where cobbler run.
But it is resolvable from location where client runs.
So if cobbler is unable to resolve hostname, do not fail and revert to
behaviour prior 588756aa7aefc122310847d007becf3112647944.
This passed our test.
--
Miroslav Suchy
Red Hat Satellite Engineering
12 years, 6 months
A few bugs and fixes
by Javier Palacios
Hello,
I have found (and fixed) some minor bugs:
Missing Import*Manager.path_tail() method
https://github.com/javiplx/cobbler-2.x/commit/a7c65366b93691825a01a656b4c...
There are also some inconsistencies in handling of keep_updated and
mirror_locally for repos.
When they are set to different values, different errors happen:
keep False , mirror True - check warns about unsynced repo, but
reposync updates nothing
keep True , mirror False - a local repo is created, but with anything
but the config.repo file
https://github.com/javiplx/cobbler-2.x/commit/31ed180b3257a823e9213b27f3e...
There is a method on import managers that is never called
(get_tree_location, actually a duplicate of configure_tree_location)
https://github.com/javiplx/cobbler-2.x/commit/f37ffb3c6018d3f73912dfd8f1f...
I have also modified debian/ubuntu importer to remove a method defined
twice, and to create the associated repos when importing a debian
netinstall media [Enabling apt on VALID_REPO_BREEDS not included on
patch]
https://github.com/javiplx/cobbler-2.x/commit/b2b3acde4f3d0d34d21cbe41886...
And finally, I have patched cobbler to extend the use of
utils.rsync_files, to reduce direct calls to rsync command.
https://github.com/javiplx/cobbler-2.x/commit/87f64562f08f0f1c29027a6c68f...
Javier Palacios
12 years, 7 months