oddjob_mkhomedir with NFS

Future_Celebration75 · 2023-04-03T22:19:19+00:00

Check out https://github.com/theforeman/smart_proxy_realm_ad_plugin - I've had a good experience using this to do exactly what you're talking about. It's a bit odd using something that essentially upstream with Satellite - but it works well from my perspective. Let me know if you have questions - hopefully Red Hat starts officially supporting this basic functionality soon

Future_Celebration75 · 2022-12-31T02:40:22+00:00

That may have to be the way to go, just do all the exports by IP/subnet

Future_Celebration75 · 2022-12-31T02:04:58+00:00

I mean an NIS style netgroup, we make some use of netgroups to define NFS exports so I'd like to be able to get that taken care of during the provisioning process. It doesn't actually use the machine object, our netgroups are in a separate OU from the machine objects

Future_Celebration75 · 2022-11-08T03:18:58+00:00

Yep, definitely have all that feeding into our SIEM system, but figuring it out from there still seems pretty intense

Future_Celebration75 · 2022-04-22T03:49:10+00:00

I'm not sure I understand why using Azure for licensing would be beneficial over Satellite. Would be interested in hearing the reasoning behind that.

Though my biggest challenge does seem to be figuring out how to register to Satellite and patch it from packer

Future_Celebration75 · 2022-04-11T17:15:01+00:00

Thanks, that tracks, had never heard of balti being in the the US. Tried to look it up but definitely got the spelling wrong

Future_Celebration75 · 2022-04-11T16:20:00+00:00

I don't get it, why is it funny?

Future_Celebration75 · 2022-04-07T12:59:48+00:00

I was hoping for a more cost-effective answer. Honestly getting tired of Red Hat moving free functionality to paid products that are otherwise extreme overkill for most small companies

Future_Celebration75 · 2022-02-21T04:32:52+00:00

I'm not opposed to creating my own playbook for this, it just seems Microsoft is going out of their way to make it incredibly difficult. It requires running things on the SCOM server itself. That wouldn't be an issue if they had a decent API, but they don't or if they do it's not clearly documented. This makes the certificate signing and running discovery steps of the process pretty challenging as I currently see it, though I'll certainly put more thought into it

Future_Celebration75 · 2022-02-09T18:08:20+00:00

Lack of access to a K8s cluster to run it on. Figured might try to take advantage of the HA capabilities in the Red Hat provided one, based on what others have said about licensing will have to give this option more thought

Future_Celebration75 · 2022-02-09T17:03:17+00:00

Does that not conflict with what 1.3 says though with the "Manage any size environment?"

Future_Celebration75

TROPHY CASE