Send et-mgmt-tools mailing list submissions to
et-mgmt-tools@xxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
or, via email, send a message with subject or body 'help' to
et-mgmt-tools-request@xxxxxxxxxx
You can reach the person managing the list at
et-mgmt-tools-owner@xxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of et-mgmt-tools digest..."
Today's Topics:
1. What's new in Cobbler development lately (Michael DeHaan)
2. Re: What's new in Cobbler development lately (Michael DeHaan)
3. Re: Virt-manager: 5.0, 5.1, 5.2 fail in Fedora 7
(Lawrence H Nitz)
4. Re: Re: Virt-manager: 5.0, 5.1, 5.2 fail in Fedora 7
(Hugh O. Brock)
5. Re: What's new in Cobbler development lately (Aaron Lippold)
----------------------------------------------------------------------
Message: 1
Date: Fri, 19 Oct 2007 17:03:19 -0400
From: Michael DeHaan <mdehaan@xxxxxxxxxx>
Subject: What's new in Cobbler development lately
To: "'et-mgmt-tools@xxxxxxxxxx'" <et-mgmt-tools@xxxxxxxxxx>
Message-ID: <47191B97.2010401@xxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
A few things of interest to a few people.... There are still a few
things upstream that I want to get done before pushing 0.6.3 out.
However, it's worth talking about what is already there, in case anyone
is interested in those features and would like to play with/test them
now.
First off -- performance upgrades. Cobbler does great now with an
average number of records, but performance with a very large number of
systems in the "database" could be better. By switching all serializers
(except settings) to serializer_shelve in /etc/cobbler/auth.conf,
cobbler gets a lot faster for very large configurations. This is
because changes to the cobbler "database" can be made without
reading/writing the whole file. I'm still undecided as to whether
this should
be the default for new Cobbler installs, but there will be a script to
migrate users between formats for those that have existing
configurations. With the new code, it's possible
to run a "cobbler list" command and see 5000 entries come back in 2
seconds -- before, YAML parsing/loading would have made storing a config
that large in YAML somewhat painful. Currently this is using BSD-DB
(which some of you said is scary, fair enough), though we could also use
gddb. I've tested both and performance is identical. sqlite is
possible, but maybe not needed. You can read more here:
https://hosted.fedoraproject.org/projects/cobbler/wiki/AlternativeSerializers
Second -- there was a request to extend the idea of Cobbler triggers (
https://hosted.fedoraproject.org/projects/cobbler/wiki/CobblerTriggers )
to support a "sync" trigger. We have that now. For instance, now we
have the service-restart code as a trigger. So by default it will
restart dhcpd/dnsmasq after a cobbler sync if you have DHCP management
turned on. If you don't, it does nothing. However, suppose you wanted
Cobbler to push out DHCP configurations to multiple servers? No
problem! Now you can modify the trigger yourself and make it do
whatever you want, all without modifying Cobbler code.
Both making things more modular (for arbitrary user extensibility) and
making things scale for extremely large configurations will definitely
be an ongoing focus for subsequent releases.
If you're interested in any of the above, check out the git version
control repo.
--Michael
------------------------------
Message: 2
Date: Fri, 19 Oct 2007 17:05:29 -0400
From: Michael DeHaan <mdehaan@xxxxxxxxxx>
Subject: Re: What's new in Cobbler development lately
To: Fedora/Linux Management Tools <et-mgmt-tools@xxxxxxxxxx>
Message-ID: <47191C19.9040402@xxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Michael DeHaan wrote:
By switching all serializers (except settings) to serializer_shelve in
/etc/cobbler/auth.conf, cobbler gets a lot faster for very large
configurations.
This should read /etc/cobbler/modules.conf.
------------------------------
Message: 3
Date: Fri, 19 Oct 2007 11:16:56 -1000
From: Lawrence H Nitz <lnitz@xxxxxxxxxx>
Subject: Re: Virt-manager: 5.0, 5.1, 5.2 fail in
Fedora 7
To: et-mgmt-tools@xxxxxxxxxx
Message-ID: <f5e7c4dc2fbe1.47189228@xxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii
Thanks for the kind responses.
I think there may be other problems, since I do not see any create buttons in any portion of my 0.5.2 virt-manager screen. I may have contaminated the installation in moving from one release to another. I suspect that the python archive called in the program may be ruined.
Is there a straightforward way to uninstall all of the virt-manager directories, so that I can do a truly clean install?
Thanks, Larry Nitz
------------------------------
Message: 4
Date: Fri, 19 Oct 2007 17:26:31 -0400
From: "Hugh O. Brock" <hbrock@xxxxxxxxxx>
Subject: Re: Re: Virt-manager: 5.0, 5.1, 5.2 fail in
Fedora 7
To: Fedora/Linux Management Tools <et-mgmt-tools@xxxxxxxxxx>
Message-ID: <20071019212631.GI15667@xxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii
On Fri, Oct 19, 2007 at 11:16:56AM -1000, Lawrence H Nitz wrote:
Thanks for the kind responses.
I think there may be other problems, since I do not see any create buttons in any portion of my 0.5.2 virt-manager screen. I may have contaminated the installation in moving from one release to another. I suspect that the python archive called in the program may be ruined.
Is there a straightforward way to uninstall all of the virt-manager directories, so that I can do a truly clean install?
Are you running virt-manager as root? The UI won't show a create
button unless the connection to your hypervisor is fully
privileged. Speaking of which, are you using the Xen hypervisor, or
KVM? And, do you see any guests you have previously defined (if you
defined any)?
--Hugh
------------------------------
Message: 5
Date: Fri, 19 Oct 2007 21:48:38 -0400
From: "Aaron Lippold" <lippold@xxxxxxxxx>
Subject: Re: What's new in Cobbler development lately
To: "Fedora/Linux Management Tools" <et-mgmt-tools@xxxxxxxxxx>
Message-ID:
<39d2723b0710191848j3ddc224eg29f17aef69f9b3a@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1
Hi Mike and gang,
These sound like some great enhancements. I was hoping the list and
yourself might help me work out some things.
I am going to be putting together a new infrastructure for the open
source group at my organization and I was thinking about setting up a
virt enviroment for my production services. Webserver,
development/project enviroment - i.e. svn, bugs, tickets, etc. most
likely trac or sourceforge - a gnumailman service, etc. I was thinking
that, if I did this, it might be smart to double up in a kind of virt
HA setup. Do you know anyone who has setup this type of thing and how
they are succeeding with it.
Also, for my testing and pre-deployment I was going to use another
virt env. This most likely wouldn't have to be HA.
I, of course, was going to use virt-manager to help manage this setup.
Thoughts? Suggestions?
Specifically what level of hardware would really be needed for a
medium load - 10-15 projects - 100 general users etc. I was thinking
about a 2 cpu dual or quad core setup with a SAN for the virt images
etc. This would be the first deployment of an infrastructure which was
virt rather than individual systems. Thoughts?
Thanks,
Aaron
On 10/19/07, Michael DeHaan <mdehaan@xxxxxxxxxx> wrote:
Michael DeHaan wrote:
By switching all serializers (except settings) to serializer_shelve in
/etc/cobbler/auth.conf, cobbler gets a lot faster for very large
configurations.
This should read /etc/cobbler/modules.conf.
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
------------------------------
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
End of et-mgmt-tools Digest, Vol 14, Issue 27
*********************************************
