Another idea, and I am sure this has been talked about before in other
threads. Has there been any thought around making cobbler a bit more
scalable in a master-slave type of setup. For example at my company we have
a single master that contains a golden copy of all of our systems, distros,
profiles, repos, etc etc. Whenever we make a single change to a system
record we have to go out to our slaves and enforce a replicate which pulls
everything down.
Now we know we can keep system records on each individual slave (or in this
case the master for that environment), but one thing that's convenient is
keeping all of our system records on the main master server (gold server)
for auditing and record keeping. So something that comes to mind is making
cobbler more aware of its slave servers and what configs are
owned/replicated to those slaves.
For example:
cobbler system add --name=test --slave-server=lon04
This would only replicate the system records to that slave server
(environment). This way my remote sites dont get DHCP entries, tftp links,
etc for hosts they dont support. From the master server it would be good to
be able to replicate directly to the slave when changes are made so I dont
have to go to the slave host and kick off a replicate.
Another thing this would buy us is by allowing the master to control the
slaves so we can get a status update on our environment.
For example:
cobbler slave status --all
This could print out a status of the cobbler environment, whether the slaves
are in sync with the latest changes. The last time they have been updated.
cobbler slave status --slave-server=lon04
I am assuming most of this can be done over XMRPC or func.
-Chris
On Mon, Feb 2, 2009 at 10:26 AM, Christopher Johnston <
cjohnstonwork(a)gmail.com> wrote:
Would it be possible to have an option in cobbler to see the last
(X)
number of changes made?
For example:
cobbler log --last 25
Could print out what changes were made for system records, distros,
profiles, etc etc. I know you could run something like history at the bash
prompt, but would be better if Cobbler had a stateful understanding of
things going on. Especially in a multi-user environment where we have lots
of admins making changes.
-Chris
On Mon, Feb 2, 2009 at 9:38 AM, James Laska <jlaska(a)redhat.com> wrote:
> On Fri, 2009-01-30 at 14:32 -0500, Michael DeHaan wrote:
> > The ongoing discussion of big things/themes missing is always a good
> > one
> > to have. We have also collected a lot of great RFE's, so I'm going
> > to
> > try to organize these further and make it a bit clearer as to what I
> > think interesting priorities for them are in case folks (including me)
> > want to knock them out.
>
> Improved integration with the anaconda monitoring (anamon) support.
> * integration with `cobbler status` ?
> * enable log viewing from cobbler web ?
> * other?
>
> Thanks,
> James
>
> --
> ==========================================
> James Laska -- jlaska(a)redhat.com
> Quality Engineering -- Red Hat, Inc.
> ==========================================
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/cobbler
>
>