On Monday, February 13, 2012 at 3:25 PM, Jim Nachlin wrote:
Pull request submitted.Maybe someone else will chime in as to the logic of trying differentreg systems. I am a bit of a novice at certificate-based RHN, soplease bear with me. It's my impression that not many people areusing it yet, anyway.Regards,JimOn Mon, Feb 13, 2012 at 3:15 PM, Michael DeHaan<michael.dehaan@gmail.com> wrote:On Monday, February 13, 2012 at 3:11 PM, Jim Nachlin wrote:On Mon, Feb 13, 2012 at 2:37 PM, Michael DeHaan<michael.dehaan@gmail.com> wrote:Thanks…Probably some existence check to see if subscription-manager is present andthen falling back to the old way rhn_register way if that's installedinstead sounds reasonable.Hi Michael,It makes a lot of sense to ensure that subscription-manager ispresent. I'm not sure about falling back to the other way, though.My thinking is that a shop will probably either want to use the newcert-based registration or the old one, and not have the old oneavailable as a fallback. That is, if you are going with cert-basedregistration and the registration fails, you probably just want tofail and not register (but not fail completely!).Yeah, so the script would just figure out which one to use, is what I wassuggesting.What you said was cert based seemed to still take a username/password fromwhat you pasted.I suppose if it took a cert the field could hold the cert value and it couldtry the cert value first.I'm not opposed to the system trying all three methods as long as it doesdecent error handlingand doesn't crash the installer.Cobbler should already be laying out the yum.repos.d files ok and shouldn'tneed to do the channel enablement -- many users are going to be mirroringchannels onto their cobbler server anyway, and using stock yum, so I don't*think* this needs a new parameter to work with the channel enablement.Maybe it should though.OK. I did not know that. In my case, it seemed to be necessary toenable the repos explicitly, because there's no longer anrhn.redhat,com where I can go and add the channels.Patches are pretty easy -- Basically it's just forking the project on githuband then sending github.com/cobbler/cobbler a pull request.Anyway, one thing at a time -- send me a patch or the subscription-registerpart and we can perhaps figure out if channel enablement should be there ornot separately?I don't have a patch. The way I did it was to create a complete file.If there's a way to create a patch for a new file, I can't figure itout!I will send you a pull request, though.git-format-patch has some special magic in it.Anyway, the github pull request is easier as it allows web based merge andsuch, plus maintains the queue of patcheswe need to review.Thanks,JimOn Monday, February 13, 2012 at 2:32 PM, Jim Nachlin wrote:Hi List,Red Hat is moving to a new, "certificate-based" registration system.They are doing away with rhn_register and moving tosubscription-manager.Here is a trivial but possibly useful snippet which we have saved as/var/lib/cobbler/snippets/install-puppet:# Subscribe (register) the systemsubscription-manager register --autosubscribe --username=XXXXXXX--password=XXXXXXXXXX# Add what used to be called channelsyum -y install yum-utilsyum-config-manager --enable rhel-6-server-optional-rpmsyum-config-manager --enable rhel-6-server-supplementaryI don't know the process for adding it to the cobbler github project,and I'd want to make the username and password into settings ratherthan having them hard coded, but I am open to doing that work andadding it if it is wanted.Regards,Jim_______________________________________________cobbler-devel mailing list_______________________________________________cobbler-devel mailing list_______________________________________________cobbler-devel mailing list_______________________________________________cobbler-devel mailing list_______________________________________________cobbler-devel mailing list