[Spacewalk-devel] Patch: disable syntax highlighting in editarea and remove duplicated code
Hi all Apologies for this. I've found that the perl and bash syntax checking is flawed so this patch turns the syntax checking off. It also cleans up the code a little. Thanks CC NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. 0005-Remove-duplicate-code-and-syntax-highlighting.patch Description: 0005-Remove-duplicate-code-and-syntax-highlighting.patch ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
RE: [Spacewalk-devel] RFC: Automatic kickstart profile changelogging
Question for the cobbler guys on the list. Before getting started on this, does cobbler provide anything like this? Should the problem be attacked from the spacewalk or cobbler side? Thanks CC > -Original Message- > From: spacewalk-devel-boun...@redhat.com > [mailto:spacewalk-devel-boun...@redhat.com] On Behalf Of > Brandon Perkins > Sent: Thursday, 8 January 2009 4:19 AM > To: spacewalk-devel@redhat.com > Subject: Re: [Spacewalk-devel] RFC: Automatic kickstart > profile changelogging > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Although the config management that comes with > Spacewalk/Satellite isn't > as feature-rich as some other alternatives, it is the only > real existing > built-in revision system into the Satellite. I'd strongly suggest > trying to find a way to tie the two together instead of coming up with > something completely new. > > Thanks. > Brandon > > > Coe, Colin C. (Unix Engineer) wrote: > > Hi > > > > Not really sure what you're saying here. My intent is to > do versioning of the kickstart profile by logging changes to > the KS profile (package adds/removes, partitioning changes, > script changes, etc) into the DB. > > > > Now that I think about it, it might make more sense to have > a seperate table with columns of ks_id, change_id, > description and date. That way you could get all the changes > for a KS profile if you wanted of all changes within a date range. > > > > I'd also meant to state that currently I store the > changelog manually at the top of the KS post script but this > is painful and requires all people modifying the KS profile > to do the same but experience has shown this not to be the case. > > > > CC > > > > From: spacewalk-devel-boun...@redhat.com > [spacewalk-devel-boun...@redhat.com] On Behalf Of > gerhardus.geldenh...@gta-travel.com > [gerhardus.geldenh...@gta-travel.com] > > Sent: Wednesday, 7 January 2009 6:54 PM > > To: spacewalk-devel@redhat.com > > Subject: RE: [Spacewalk-devel] RFC: Automatic kickstart > profile changelogging > > > > Hi, > > > > > >> I'd like to try and implement automatic changelogging of > kickstart profiles. I want to do this as I'm required by my > employer to show how >the 'build process' changes with > respect to our RHEL technical workstations and cluster nodes > (230+ nodes all up). > >> > >> I figure that I'd add two new columns to table 'rhnKSData' being: > >> - 'changeLog' (type blob); and > >> - 'changeVersion' (type number). > >> > >> When a new kickstart profile is created a note to that > effect is stored in changeLog with a date/time stamp. > Whenever the kickstart profile >is updated, a description of > the change is written to changeLog. > >> > >> The purpose of this email is to find out if anyone is > already working on something like this or if there are any objections. > > > > I don't have any objections but it does sound only a step > away from versioning the kickstarts or changes. For me > personally that would be first price. I would rather have > "change comments" as part of the change then stored > separately. Maybe long term we could have a versioning > plug-in that facilitates storing versioned information of > kickstarts/scripts(anything else relevant). You could still > keep the version in the database as "authoritave" and show > versions if available, that way if your underlying svn, git, > whatever breaks it does not break spacewalk. > > > > Regards > > > > > __ > > This email has been scanned by the MessageLabs Email > Security System. > > For more information please visit http://www.messagelabs.com/email > > > __ > > > > ___ > > Spacewalk-devel mailing list > > Spacewalk-devel@redhat.com > > https://www.redhat.com/mailman/listinfo/spacewalk-devel > > > > NOTICE: This email and any attachments are confidential. > > They may contain legally privileged information or > > copyright material. You must not read, copy, use or > > disclose them without authorisation. If you are not an > > intended recipient, please contact us at once by return > > email and then delete both messages and all attachments. > > > > > > ___ > > Spacewalk-devel mailing list > > Spacewalk-devel@redhat.com > > https://www.redhat.com/mailman/listinfo/spacewalk-devel > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.5 (GNU/Linux) > Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org > > iD8DBQFJZQ5ChwQhj8l1t/cRApSoAKCmOlwQpwnXTce7pwF/IQf5TIbZ7QCeLj6T > 8K4LcCLnUt5cqhHbNuwZ7gk= > =YybO > -END PGP SIGNATURE- > > ___ > Spacewalk-devel mailing list > Spacewalk-devel@redhat.com > https://www.redhat.com/mailman/listinfo/spac
RE: [Spacewalk-devel] RFC: Automatic kickstart profile changelogging
Yep, that makes sense and provides a revision history for ks scripts which is something else I want in satellite. CC From: spacewalk-devel-boun...@redhat.com [spacewalk-devel-boun...@redhat.com] On Behalf Of Brandon Perkins [bperk...@redhat.com] Sent: Thursday, 8 January 2009 5:19 AM To: spacewalk-devel@redhat.com Subject: Re: [Spacewalk-devel] RFC: Automatic kickstart profile changelogging -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Although the config management that comes with Spacewalk/Satellite isn't as feature-rich as some other alternatives, it is the only real existing built-in revision system into the Satellite. I'd strongly suggest trying to find a way to tie the two together instead of coming up with something completely new. Thanks. Brandon Coe, Colin C. (Unix Engineer) wrote: > Hi > > Not really sure what you're saying here. My intent is to do versioning of > the kickstart profile by logging changes to the KS profile (package > adds/removes, partitioning changes, script changes, etc) into the DB. > > Now that I think about it, it might make more sense to have a seperate table > with columns of ks_id, change_id, description and date. That way you could > get all the changes for a KS profile if you wanted of all changes within a > date range. > > I'd also meant to state that currently I store the changelog manually at the > top of the KS post script but this is painful and requires all people > modifying the KS profile to do the same but experience has shown this not to > be the case. > > CC > > From: spacewalk-devel-boun...@redhat.com [spacewalk-devel-boun...@redhat.com] > On Behalf Of gerhardus.geldenh...@gta-travel.com > [gerhardus.geldenh...@gta-travel.com] > Sent: Wednesday, 7 January 2009 6:54 PM > To: spacewalk-devel@redhat.com > Subject: RE: [Spacewalk-devel] RFC: Automatic kickstart profile changelogging > > Hi, > > >> I'd like to try and implement automatic changelogging of kickstart profiles. >> I want to do this as I'm required by my employer to show how >the 'build >> process' changes with respect to our RHEL technical workstations and cluster >> nodes (230+ nodes all up). >> >> I figure that I'd add two new columns to table 'rhnKSData' being: >> - 'changeLog' (type blob); and >> - 'changeVersion' (type number). >> >> When a new kickstart profile is created a note to that effect is stored in >> changeLog with a date/time stamp. Whenever the kickstart profile >is >> updated, a description of the change is written to changeLog. >> >> The purpose of this email is to find out if anyone is already working on >> something like this or if there are any objections. > > I don't have any objections but it does sound only a step away from > versioning the kickstarts or changes. For me personally that would be first > price. I would rather have "change comments" as part of the change then > stored separately. Maybe long term we could have a versioning plug-in that > facilitates storing versioned information of kickstarts/scripts(anything else > relevant). You could still keep the version in the database as "authoritave" > and show versions if available, that way if your underlying svn, git, > whatever breaks it does not break spacewalk. > > Regards > > __ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > __ > > ___ > Spacewalk-devel mailing list > Spacewalk-devel@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-devel > > NOTICE: This email and any attachments are confidential. > They may contain legally privileged information or > copyright material. You must not read, copy, use or > disclose them without authorisation. If you are not an > intended recipient, please contact us at once by return > email and then delete both messages and all attachments. > > > ___ > Spacewalk-devel mailing list > Spacewalk-devel@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-devel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFJZQ5ChwQhj8l1t/cRApSoAKCmOlwQpwnXTce7pwF/IQf5TIbZ7QCeLj6T 8K4LcCLnUt5cqhHbNuwZ7gk= =YybO -END PGP SIGNATURE- ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by retu
Re: [Spacewalk-devel] RFC: Automatic kickstart profile changelogging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Although the config management that comes with Spacewalk/Satellite isn't as feature-rich as some other alternatives, it is the only real existing built-in revision system into the Satellite. I'd strongly suggest trying to find a way to tie the two together instead of coming up with something completely new. Thanks. Brandon Coe, Colin C. (Unix Engineer) wrote: > Hi > > Not really sure what you're saying here. My intent is to do versioning of > the kickstart profile by logging changes to the KS profile (package > adds/removes, partitioning changes, script changes, etc) into the DB. > > Now that I think about it, it might make more sense to have a seperate table > with columns of ks_id, change_id, description and date. That way you could > get all the changes for a KS profile if you wanted of all changes within a > date range. > > I'd also meant to state that currently I store the changelog manually at the > top of the KS post script but this is painful and requires all people > modifying the KS profile to do the same but experience has shown this not to > be the case. > > CC > > From: spacewalk-devel-boun...@redhat.com [spacewalk-devel-boun...@redhat.com] > On Behalf Of gerhardus.geldenh...@gta-travel.com > [gerhardus.geldenh...@gta-travel.com] > Sent: Wednesday, 7 January 2009 6:54 PM > To: spacewalk-devel@redhat.com > Subject: RE: [Spacewalk-devel] RFC: Automatic kickstart profile changelogging > > Hi, > > >> I'd like to try and implement automatic changelogging of kickstart profiles. >> I want to do this as I'm required by my employer to show how >the 'build >> process' changes with respect to our RHEL technical workstations and cluster >> nodes (230+ nodes all up). >> >> I figure that I'd add two new columns to table 'rhnKSData' being: >> - 'changeLog' (type blob); and >> - 'changeVersion' (type number). >> >> When a new kickstart profile is created a note to that effect is stored in >> changeLog with a date/time stamp. Whenever the kickstart profile >is >> updated, a description of the change is written to changeLog. >> >> The purpose of this email is to find out if anyone is already working on >> something like this or if there are any objections. > > I don't have any objections but it does sound only a step away from > versioning the kickstarts or changes. For me personally that would be first > price. I would rather have "change comments" as part of the change then > stored separately. Maybe long term we could have a versioning plug-in that > facilitates storing versioned information of kickstarts/scripts(anything else > relevant). You could still keep the version in the database as "authoritave" > and show versions if available, that way if your underlying svn, git, > whatever breaks it does not break spacewalk. > > Regards > > __ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > __ > > ___ > Spacewalk-devel mailing list > Spacewalk-devel@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-devel > > NOTICE: This email and any attachments are confidential. > They may contain legally privileged information or > copyright material. You must not read, copy, use or > disclose them without authorisation. If you are not an > intended recipient, please contact us at once by return > email and then delete both messages and all attachments. > > > ___ > Spacewalk-devel mailing list > Spacewalk-devel@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-devel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org iD8DBQFJZQ5ChwQhj8l1t/cRApSoAKCmOlwQpwnXTce7pwF/IQf5TIbZ7QCeLj6T 8K4LcCLnUt5cqhHbNuwZ7gk= =YybO -END PGP SIGNATURE- ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
RE: [Spacewalk-devel] Follow-up: Shared script segments or cobbler script snippets
Cool, this is functionality I can't wait to use in Satellite... CC From: spacewalk-devel-boun...@redhat.com [spacewalk-devel-boun...@redhat.com] On Behalf Of Mike McCune [mmcc...@redhat.com] Sent: Thursday, 8 January 2009 4:38 AM To: spacewalk-devel@redhat.com Subject: Re: [Spacewalk-devel] Follow-up: Shared script segments or cobbler script snippets Coe, Colin C. (Unix Engineer) wrote: > Hi all > > Some time ago I emailed the list about having common scripts/scriptlets that > could be referenced in multiple kickstart profiles. At the time I was > advised that cobbler could do this and to wait for the cobbler integration. > https://www.redhat.com/archives/spacewalk-devel/2008-August/msg00066.html > > I guess this is just a follow-up and query as to how to use cobbler script > snippets in spacewalk 0.4. > We plan on writing a nice wiki howto with a lot of the new features available with the cobbler integration that will include info on this new area. Mike -- Mike McCune mmccune AT redhat.com Engineering | Portland, OR RHN Satellite | 650.567.9039x79248 ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
RE: [Spacewalk-devel] Email not showing in http://www.mail-archive.com/spacewalk-devel@redhat.com/
Cool, thanks CC From: spacewalk-devel-boun...@redhat.com [spacewalk-devel-boun...@redhat.com] On Behalf Of Devan Goodwin [dgood...@redhat.com] Sent: Wednesday, 7 January 2009 10:29 PM To: spacewalk-devel@redhat.com Subject: Re: [Spacewalk-devel] Email not showing in http://www.mail-archive.com/spacewalk-devel@redhat.com/ -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 7 Jan 2009 20:40:07 +0900 "Coe, Colin C. (Unix Engineer)" wrote: > Hi all > > Yesterday morning I sent an email containing two patches. I can see > the email in my sent items but its not showing up in the archive. > The subject was 'Patches'. > > Did anyone see this? Just trying to work out where the hold up is. > > Thanks > > CC > > NOTICE: This email and any attachments are confidential. > They may contain legally privileged information or > copyright material. You must not read, copy, use or > disclose them without authorisation. If you are not an > intended recipient, please contact us at once by return > email and then delete both messages and all attachments. > > > ___ > Spacewalk-devel mailing list > Spacewalk-devel@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-devel Yep they made it through, not sure if the archives have a delay or how long it is. Cheers, Devan - -- Devan Goodwin Software Engineer - Spacewalk / RHN Satellite Halifax, Canada650.567.9039x79267 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklkrjwACgkQAyHWaPV9my73bACeIwp/MwSs9GXWMPqz4p0tu+as JVMAn2KPB/geVJ7B2PqPmqSppivRcUw3 =mIll -END PGP SIGNATURE- ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Follow-up: Shared script segments or cobbler script snippets
Coe, Colin C. (Unix Engineer) wrote: Hi all Some time ago I emailed the list about having common scripts/scriptlets that could be referenced in multiple kickstart profiles. At the time I was advised that cobbler could do this and to wait for the cobbler integration. https://www.redhat.com/archives/spacewalk-devel/2008-August/msg00066.html I guess this is just a follow-up and query as to how to use cobbler script snippets in spacewalk 0.4. We plan on writing a nice wiki howto with a lot of the new features available with the cobbler integration that will include info on this new area. Mike -- Mike McCune mmccune AT redhat.com Engineering | Portland, OR RHN Satellite | 650.567.9039x79248 ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Patches: make kickstart use editarea not textarea
Coe, Colin C. (Unix Engineer) wrote: Hi all I figured I'd just get these in sooner rather than later. Attached are two patches: 1) replaces the HTML textarea tags with editarea. Very similar to the previous textarea -> editarea patch for the managed config files. And again, this depends on the editarea .zip being extacted to spacewalk/web/html/javascript/. I actually unzipped it (and spacewalk/web/html/javascript/editarea_0_7_2_3 was created) then created a symlink spacewalk/web/html/javascript/editarea. 2) fixes a whitespace error that wouldn't exist if I done the git commands in the right order. Apologies for this. Thanks to the guys on the spacewalk-devel channel for all the help with this. CC I'll review these and let you know if any revisions are needed. Thanks for the submission! -- Mike McCune mmccune AT redhat.com Engineering | Portland, OR RHN Satellite | 650.567.9039x79248 ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Email not showing in http://www.mail-archive.com/spacewalk-devel@redhat.com/
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 7 Jan 2009 20:40:07 +0900 "Coe, Colin C. (Unix Engineer)" wrote: > Hi all > > Yesterday morning I sent an email containing two patches. I can see > the email in my sent items but its not showing up in the archive. > The subject was 'Patches'. > > Did anyone see this? Just trying to work out where the hold up is. > > Thanks > > CC > > NOTICE: This email and any attachments are confidential. > They may contain legally privileged information or > copyright material. You must not read, copy, use or > disclose them without authorisation. If you are not an > intended recipient, please contact us at once by return > email and then delete both messages and all attachments. > > > ___ > Spacewalk-devel mailing list > Spacewalk-devel@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-devel Yep they made it through, not sure if the archives have a delay or how long it is. Cheers, Devan - -- Devan Goodwin Software Engineer - Spacewalk / RHN Satellite Halifax, Canada650.567.9039x79267 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklkrjwACgkQAyHWaPV9my73bACeIwp/MwSs9GXWMPqz4p0tu+as JVMAn2KPB/geVJ7B2PqPmqSppivRcUw3 =mIll -END PGP SIGNATURE- ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] spacewalk-cobber integration in main
On Wed, Jan 07, 2009 at 11:15:32AM +0100, Milan Zazrivec wrote: > > > > So every one use the official one the one under schema upgrade directory > > as its more robust.. Jan is there documentation on the usage :).. > > Manual page for spacewalk-schema-upgrade was added in > http://git.fedorahosted.org/git/?p=spacewalk.git;a=commitdiff;h=a22ab3ae00f18ea71278685f229320f9ac55adc4 > Thank you, man. -- Jan Pazdziora Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Follow-up: Shared script segments or cobbler script snippets
Hi all Some time ago I emailed the list about having common scripts/scriptlets that could be referenced in multiple kickstart profiles. At the time I was advised that cobbler could do this and to wait for the cobbler integration. https://www.redhat.com/archives/spacewalk-devel/2008-August/msg00066.html I guess this is just a follow-up and query as to how to use cobbler script snippets in spacewalk 0.4. Thanks CC NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
[Spacewalk-devel] Email not showing in http://www.mail-archive.com/spacewalk-devel@redhat.com/
Hi all Yesterday morning I sent an email containing two patches. I can see the email in my sent items but its not showing up in the archive. The subject was 'Patches'. Did anyone see this? Just trying to work out where the hold up is. Thanks CC NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
RE: [Spacewalk-devel] RFC: Automatic kickstart profile changelogging
Hi Not really sure what you're saying here. My intent is to do versioning of the kickstart profile by logging changes to the KS profile (package adds/removes, partitioning changes, script changes, etc) into the DB. Now that I think about it, it might make more sense to have a seperate table with columns of ks_id, change_id, description and date. That way you could get all the changes for a KS profile if you wanted of all changes within a date range. I'd also meant to state that currently I store the changelog manually at the top of the KS post script but this is painful and requires all people modifying the KS profile to do the same but experience has shown this not to be the case. CC From: spacewalk-devel-boun...@redhat.com [spacewalk-devel-boun...@redhat.com] On Behalf Of gerhardus.geldenh...@gta-travel.com [gerhardus.geldenh...@gta-travel.com] Sent: Wednesday, 7 January 2009 6:54 PM To: spacewalk-devel@redhat.com Subject: RE: [Spacewalk-devel] RFC: Automatic kickstart profile changelogging Hi, >I'd like to try and implement automatic changelogging of kickstart profiles. >I want to do this as I'm required by my employer to show how >the 'build >process' changes with respect to our RHEL technical workstations and cluster >nodes (230+ nodes all up). > >I figure that I'd add two new columns to table 'rhnKSData' being: >- 'changeLog' (type blob); and >- 'changeVersion' (type number). > >When a new kickstart profile is created a note to that effect is stored in >changeLog with a date/time stamp. Whenever the kickstart profile >is updated, >a description of the change is written to changeLog. > >The purpose of this email is to find out if anyone is already working on >something like this or if there are any objections. I don't have any objections but it does sound only a step away from versioning the kickstarts or changes. For me personally that would be first price. I would rather have "change comments" as part of the change then stored separately. Maybe long term we could have a versioning plug-in that facilitates storing versioned information of kickstarts/scripts(anything else relevant). You could still keep the version in the database as "authoritave" and show versions if available, that way if your underlying svn, git, whatever breaks it does not break spacewalk. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] spacewalk-cobber integration in main
On Friday 31 October 2008 05:14:35 Partha Aji wrote: > On schema updater I thought I did a rename Oh well lemme delete the > one in java/scripts ... > > Totally agree that spacewalk-schema-upgrade is the way to upgrade the > thing officially.. Well schema-updater is just for more fine grained > stuff.. Like Upgrade scripts starting from specific number and above.. > Its useful only during devel phases as devs keep adding one table at a > time... > > But sounds like the same can be achieved as Jan says by creating a > directory and symlinking exactly the files you want updated (me doesn't > think straighforwardly like that unfortunately :( ). > > So every one use the official one the one under schema upgrade directory > as its more robust.. Jan is there documentation on the usage :).. Manual page for spacewalk-schema-upgrade was added in http://git.fedorahosted.org/git/?p=spacewalk.git;a=commitdiff;h=a22ab3ae00f18ea71278685f229320f9ac55adc4 -MZ ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
RE: [Spacewalk-devel] RFC: Automatic kickstart profile changelogging
Hi, >I'd like to try and implement automatic changelogging of kickstart profiles. >I want to do this as I'm required by my employer to show how >the 'build >process' changes with respect to our RHEL technical workstations and cluster >nodes (230+ nodes all up). > >I figure that I'd add two new columns to table 'rhnKSData' being: >- 'changeLog' (type blob); and >- 'changeVersion' (type number). > >When a new kickstart profile is created a note to that effect is stored in >changeLog with a date/time stamp. Whenever the kickstart profile >is updated, >a description of the change is written to changeLog. > >The purpose of this email is to find out if anyone is already working on >something like this or if there are any objections. I don't have any objections but it does sound only a step away from versioning the kickstarts or changes. For me personally that would be first price. I would rather have "change comments" as part of the change then stored separately. Maybe long term we could have a versioning plug-in that facilitates storing versioned information of kickstarts/scripts(anything else relevant). You could still keep the version in the database as "authoritave" and show versions if available, that way if your underlying svn, git, whatever breaks it does not break spacewalk. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
