I realize it makes re-enabling the feature more complicated but I'd like to throw my hat in with the --rescue-mode=true style of use instead of changing profiles.
On Thu, Dec 15, 2011 at 08:28, David Lee <[email protected]> wrote: > Thanks, Michael. I filed a ticket (#14) on 7 December. Joergen Mass is > also interested in this topic. > > My personal view, following a brief discussion with Joergen, remains that > we ought to view this primarily from the angle of "keep it simple and > well-documented for the average end-user". We shouldn't have to tell the > user to set up new profiles or any such techno-geekery. If such things > have to happen "under the covers", then the typical user should not need to > know about it. If it /really/ is necessary for the end-user to have to do > it, then first of all we need to write accurate, clear, unambiguous > documentation, then implement what the documentation says. > > Hope that helps. > > > -- David Lee > > Michael DeHaan wrote: > >> Filing a ticket in github (github.com/cobbler/cobbler) should be good >> enough. >> >> (I think reinstating the original behavior works best, at least at the >> code level.) >> >> -- Michael >> >> On Tuesday, December 6, 2011 at 9:24 AM, David Lee wrote: >> >> Thanks, Michael. >>> >>> This isn't urgent for us. But it is something which I think would be >>> very, very nice to have readily and easily available in the future. >>> >>> For any established system "client1", it would be good to be able to do >>> something as simple as a re-enabling of the original specification: >>> >>> cobbler system edit --name=client1 \ >>> --netboot-enabled=true --rescue-mode=true >>> >>> An alternative syntax might be: >>> cobbler system edit --name=client1 --netboot-enabled=rescue >>> >>> I merely offer those two as possible suggestions; I can see good and >>> not-so-good in both. >>> >>> The essential point is simplicity and (as Michael says) "it also >>> immediately exposes the capabilities to those who didn't know it was >>> there." >>> >>> Should I raise this on "cobbler-devel"? >>> >>> >>> -- >>> : David Lee >>> >>> >>> >>> >>> Michael DeHaan wrote: >>> >>>> Here's an older post that should be helpful: >>>> >>>> http://www.redhat.com/**archives/et-mgmt-tools/2008-** >>>> April/msg00059.html<http://www.redhat.com/archives/et-mgmt-tools/2008-April/msg00059.html> >>>> >>>> This was actually a feature for a long while: >>>> >>>> https://fedorahosted.org/**pipermail/cobbler/2008-** >>>> September/000773.html<https://fedorahosted.org/pipermail/cobbler/2008-September/000773.html> >>>> >>>> >>>> This functionality has apparently been commented out in recent "cobbler >>>> import" builds. >>>> >>>> I'm not sure why. It could be that in making imports modular it was >>>> just never finished, it or it could be because someone didn't like the >>>> extra profiles cluttering up the list. I think I'd like to see it >>>> return namely because you don't have to remember what to put in the >>>> rescue kickstart, and it is also immediately exposes the capabilities to >>>> those who didn't know it was there. >>>> >>>> https://github.com/cobbler/**cobbler/blob/master/cobbler/** >>>> modules/manage_import_redhat.**py<https://github.com/cobbler/cobbler/blob/master/cobbler/modules/manage_import_redhat.py> >>>> >>>> >>>> -- >>>> Michael DeHaan >>>> Sent with Sparrow >>>> <http://www.sparrowmailapp.**com/?sig<http://www.sparrowmailapp.com/?sig> >>>> > >>>> >>>> On Tuesday, December 6, 2011 at 5:48 AM, David Lee wrote: >>>> >>>> (Using cobbler 2.0.11 with RHEL 5.6.) >>>>> >>>>> I may have missed the documentation on this: if so, simply point me in >>>>> the right direction! >>>>> >>>>> During the last few months we have developed a cobbler installation for >>>>> installing new client systems, and are happy with it. Indeed, most of >>>>> our boxes don't have internal DVD drives, so cobbler has been >>>>> essential. >>>>> >>>>> But one thing we would like to be able to do occasionally is to boot a >>>>> client box into a "rescue mode". The most recent example was when we >>>>> had some suspect memory on a disk controller. >>>>> >>>>> Is there some sort of recipe somewhere for running a "rescue mode" boot >>>>> of a cobbler client system? >>>>> >>>>> >>>>> -- >>>>> : David Lee >>>>> : ECMWF (Data Handling System) >>>>> : Shinfield Park >>>>> : Reading RG2 9AX >>>>> : Berkshire >>>>> : >>>>> : tel: +44-118-9499 362 >>>>> : email: [email protected] <mailto:[email protected]> >>>>> ______________________________**_________________ >>>>> cobbler mailing list >>>>> [email protected] <mailto:cobbler@lists.** >>>>> fedorahosted.org <[email protected]>> >>>>> https://fedorahosted.org/**mailman/listinfo/cobbler<https://fedorahosted.org/mailman/listinfo/cobbler> >>>>> >>>> >>>> >>>> ------------------------------**------------------------------** >>>> ------------ >>>> >>>> ______________________________**_________________ >>>> cobbler mailing list >>>> [email protected] >>>> <mailto:cobbler@lists.**fedorahosted.org<[email protected]> >>>> > >>>> https://fedorahosted.org/**mailman/listinfo/cobbler<https://fedorahosted.org/mailman/listinfo/cobbler> >>>> >>> ______________________________**_________________ >>> cobbler mailing list >>> [email protected] >>> <mailto:cobbler@lists.**fedorahosted.org<[email protected]> >>> > >>> https://fedorahosted.org/**mailman/listinfo/cobbler<https://fedorahosted.org/mailman/listinfo/cobbler> >>> >> >> >> ------------------------------**------------------------------** >> ------------ >> >> ______________________________**_________________ >> cobbler mailing list >> [email protected] >> https://fedorahosted.org/**mailman/listinfo/cobbler<https://fedorahosted.org/mailman/listinfo/cobbler> >> > > ______________________________**_________________ > cobbler mailing list > [email protected] > https://fedorahosted.org/**mailman/listinfo/cobbler<https://fedorahosted.org/mailman/listinfo/cobbler> >
_______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
