[PATCH] sessions directory should be moved from /usr/share/cobbler/web to /var (#499)
by Cristian Ciupitu
I have a fix for it at http://github.com/ciupicri/cobbler/commit/507b38453f7cafe42f2e37b406b0856...
In case there's a git problem my repo is git://github.com/ciupicri/cobbler.git (the release20 branch, although main has it too) and the patch is also available in the bug tracker.
I've tested the patch and it works fine, except for a tiny problem. /etc/httpd/conf.d/cobbler.conf contains this line:
AliasMatch ^/cobbler(.*)?$ "/var/www/cobbler$1"
which means that the cobbler_webui_sessions directory will be shared just like cobbler_webui_content. I propose to replace the regular expression with an explicit list of directories. As "The Zen of Python" says it, "Explicit is better than implicit". Another option could be to rename cobbler_ui_sessions to something else, e.g. sessions_cobbler. I'm waiting for your suggestions on this, so I can send another patch.
If you're for the first solution, are there any other directories starting with cobbler besides these?
- cobbler
- cobbler_webui_content
- cobbler_api
- cobbler_web
- cobbler_track.... (which is covered by another AliasMatch line)
Thank you,
Cristian
14 years, 6 months
[PATCH 1/2] Restore the ability to disable rsync management
by Joshua T Corbin
Functionality originally in 60fe75a5, but reverted by 4a7eee30 and
9113a190 amidst a raft of other changes.
---
cobbler/action_sync.py | 7 ++++---
installer_templates/defaults | 1 +
installer_templates/settings.template | 3 +++
3 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/cobbler/action_sync.py b/cobbler/action_sync.py
index 43f5e6d..4edcc28 100644
--- a/cobbler/action_sync.py
+++ b/cobbler/action_sync.py
@@ -136,9 +136,10 @@ class BootSync:
self.dns.regen_hosts()
self.dns.write_dns_files()
- if self.verbose:
- self.logger.info("rendering Rsync files")
- self.rsync_gen()
+ if self.settings.manage_rsync:
+ if self.verbose:
+ self.logger.info("rendering Rsync files")
+ self.rsync_gen()
if self.verbose:
self.logger.info("generating PXE menu structure")
diff --git a/installer_templates/defaults b/installer_templates/defaults
index 3da4476..efa7a6b 100644
--- a/installer_templates/defaults
+++ b/installer_templates/defaults
@@ -4,6 +4,7 @@ dns_module: 'manage_bind'
dhcp_module: 'manage_isc'
enable_dhcp: 0
enable_dns: 0
+enable_rsync: 1
next_server: '127.0.0.1'
pxe_once: 0
redhat_management_type: "off"
diff --git a/installer_templates/settings.template b/installer_templates/settings.template
index 2777b73..1ba1a0b 100644
--- a/installer_templates/settings.template
+++ b/installer_templates/settings.template
@@ -168,6 +168,9 @@ mgmt_classes: []
mgmt_parameters:
from_cobbler: 1
+# set to 1 to enable Cobbler's RSYNC management features.
+manage_rsync: $enable_rsync
+
# set to 1 to enable Cobbler's DHCP management features.
# the choice of DHCP management engine is in /etc/cobbler/modules.conf
manage_dhcp: $enable_dhcp
--
1.6.2.5
14 years, 7 months
_CIDR function missing in 2.0.1?
by Glenn Bailey
Just started playing with 2.0.1 and it seems the _CIDR function is missing from utils.py? Took a look in there, and the _IP function exists but not _CIDR .. Copy and pasting the function out of the 2.0.0 branch fixes it, but I'm gonna assume it's missing for a reason ;-)
Starting cobbler daemon: cannot import name _CIDR
Traceback (most recent call last):
File "/usr/bin/cobblerd", line 76, in main
api = cobbler_api.BootAPI(is_cobblerd=True)
File "/usr/lib/python2.4/site-packages/cobbler/api.py", line 121, in __init__
module_loader.load_modules()
File "/usr/lib/python2.4/site-packages/cobbler/module_loader.py", line 64, in load_modules
blip = __import__("modules.%s" % ( modname), globals(), locals(), [modname])
File "/usr/lib/python2.4/site-packages/cobbler/modules/cli_network.py", line 31, in ?
from utils import _, _IP, _CIDR
ImportError: cannot import name _CIDR
Glenn E. Bailey III, Operational Support Services gbailey(a)terremark.com
972-827-4292
terremark worldwide
222 W Las Colinas Blvd Ste 350E
Irving, TX 75039
14 years, 7 months
multiple DHCP servers on a single segment
by rob morrien
hello,
at this moment i have multiple DHCP servers on a single segment .
one dhcp server is runing on my router and one i need for cobbler on my
spacewalk server.
pls can somebody tell me how to configure this dhcp server for cobbler
regards rob
14 years, 7 months
Bugs closed so far for 2.0, what's left
by Michael DeHaan
In interest of radical transparency and all that, here's what I'm
planning on fixing for the 2.0.1 release. The goal is to get this out
Friday, worst case scenario -- Tuesday at absolute latest. Then we'll
crank out another testing RPM for folks to upgrade to.
From the changelog, we have already fixed this week:
- (BUGF) Fixes for image based CLI usage and object validation
- (BUGF) Fix koan check for images ... they don't need a kickstart
- (BUGF) Get NFS image mounting working again
- (BUGF) Show object name on cobbler-web edit pages
- (BUGF) Make memtest integration look in the right file locations
- (BUGF) Fix check for dhcpd installation
- (BUGF) Fix code to detect dhcpd config file installation
- (BUGF) Cleaned up generated comments in settings files
- (BUGF) Unhide per-system post-install kernel options
- (BUGF) Unhide owners fields
- (BUGF) Fix "cobbler profile/system dumpvars" command
- (BUGF) Remove acl_engine reference from authz_configfile
- (BUGF) Add "View Kickstart" link back on profile list page
----
Here are things we must fix, with notes on the fixes pending.
#491 cobbler reposync --only may not be working properly in 2.0.0
NOTES: most likely just a CLI/parameter not being routed
through cobblerd correctly. Easy enough.
#499 sessions directory should be moved from /usr/share/cobbler/web
to /var
#502 session related files needs to be stamped httpd_sys_content_t
if SELinux in enforcing mode
NOTES: we will let Cobbler check warn about the command
to run along with other SELinux rules
#503 cobbler import failing when SELInux in enforcing mode and
boolean rsync_disable_trans --> off
NOTES: we will let Cobbler check warn about the command
to run along with other SELinux rules
#504 utils.uniquify not found in Cobbler Web
NOTES: not sure yet
#507 paging navigation not showing up in profile view
NOTES: not sure yet
Need to Investigate/Reproduce Still:
#481 eth0 already present but can view it in cobbler_web
-----
Non Life-Threatening / Planning To Defer To Later Release / Send In A
Patch If You Are Interested In Seeing This Fixed:
#408 --virt-auto-boot needs to support qemu/KVM
#411 unicode data types should not appear in 'report' output 03/28/09
#431 'langsupport' command in
/var/lib/cobbler/kickstarts/pxerescue.ks breaks Fedora 10 PXE
#446 --onboot is invalid option for RHEL3 based builds
#452 make koan use blktap driver for Xen when possible
#459 --static-interface assumes the gateway is in the interface conf
#461 cobbler check prints /usr/sbin/semanage: No such file or directory
#477 don't allow non-printable chars (and spaces, where relev.) in
most fields
#479 ConfigParser doesn't parse correctly names of the form:
<user>@<REALM>
#496 "Add new" button in webapp location for 2.0 is not intuitive
#501 "accents"/diacritics characters not supported in Comment fields
(systems)
(also not listed: all RFEs currently in Trac)
----
Not Planned For 2.0.1, But *Must* Fix for 2.1:
#470 move from rhpl to python-eththool (and others)
---
Comments/etc welcome!
--Michael
14 years, 7 months
Feature-hold on 2.0.1+N, +further automated testing thoughts
by Michael DeHaan
Before we get too far along with making changes to 2.0.X (or think about
2.1) -- however small, we really need to spend some time to amp up our
testing. I alluded to this previously. Cobbler's development is
accelerating at a HUGE rate. This is awesome. Though as it
accelerates, the rate at which we QA things is not accelerating.
What I need is a surefire system so that when new patches go in, we can
know, for sure, what they break and don't break. Right now we have
solid tests for create, update, delete, modify kind of use cases. We
don't have good tests for koan and modules like DHCP/DNS manipulation.
As a result, some of these things -- which tend to be the
functional/ancillary features, not the core, require some manual
testing. This is not good because it takes a lot of time. There's an
overhead in patch acceptance that makes it a lot more than the 30
seconds it takes to merge something in.
I think there's a lot of work in this, but basically the inability for
me to automate /full/ testing after patch merging is starting to become
a bottleneck, and I want to get this fixed up for everyone. I think
some folks have mentioned that they want to help with this, so I'll
share more details as this gets further along.
I also have some other (non-Cobbler related) items I'm working on, so
the more I can make myself "not a bottleneck" the better.
To make it clear what this involves -- it means that we won't be
considering new features -- or bugfixes that might have other
implications -- until we can get this really improved.
It's easy for me to test things that happen when I modify core bits, but
when accepting patches, I don't really know what submitters have
tested. If we can make software do this, it means we can move forward
and accept patches/innovation at a faster rate.
Again, help with this is welcome. While what we have right now is
relatively unit-testy, what I want to do is get the framework to create
VMs, due to end to end enpoints, and everything, and be highly
configurable. This will also mean that when a new release goes out,
people will be able to help run tests and add to them -- on their own
hardware -- and be able to use this framework when adding features.
Hopefully this all makes sense. Short-term, it may seem like the patch
queue is not being mined. You might want to hold off a bit on new
feature development in the meantime as we start to figure out how to
scale this up.
--Michael
14 years, 7 months
