@scottalanmiller said:
@johnhooks said:
I was assuming he meant it was a single point of failure, which is why I said that.
No, it's about mixing workloads. There is a lot of value to "do one thing, do it well." UTMs don't do this. Everything is mashed onto one box. Rather like people throwing every little workload onto a NAS. It isn't designed for that.
Oh OK. Makes sense. Sorry @JaredBusch I wasn't trying to be a jerk, I promise.
@scottalanmiller said:
@johnhooks said:
Multiple vms on one physical device, unless you have HA.
Physical device is not the same as mixing code or functions in a single container. Hypervisor also does not imply running multiple VMs, only hardware abstraction. HA doesn't change anything that I can tell, not sure what you were meaning by that.
I was assuming he meant it was a single point of failure, which is why I said that.
@scottalanmiller said:
@JaredBusch said:
DO is new, and most behind ML (generally @ntg ) have had longstanding use of RackSpace
That pretty much sums it up. Been on RS for a very long time and for the most part they work really well.
I had seen some posts of you using them, I was just curious.
@scottalanmiller said:
Hey, NodeBB 0.7.3 just dropped. We will have to see if we can get that set up tonight. I have to travel tomorrow night and am hanging in PC all weekend so would like to not be working on that this weekend.
Out of curiosity, what was the reason for choosing rackspace and not something like digital ocean?
@scottalanmiller said:
@johnhooks said:
Like a hypervisor?
not sure what you mean. How does a hypervisor put lots of things on one device?
Multiple vms on one physical device, unless you have HA.
@JaredBusch said:
@johnhooks said:
For ~$50 more you could buy a small Sophos UTM.
Never, ever, buy a UTM, from any vendor. I hate the entire concept of putting everything in a single device.
Like a hypervisor?
@Minion-Queen said:
I worked in Helpdesk for 11 years. Now I don't
oh wait yeah I do when someone around here is sick or doesn't "show" up I get to still.
I guess that's probably true of all of us to an extent Esp at home ha
@scottalanmiller said:
What I have found to be more common is that people who go to college to start their careers often then leave college and start in helpdesk, but those that skip college often start in other career areas. College is the most common path into IT from the inside, helpdesk is the most common entry point from the inside. So those two seem to line up as the "following the commonly accepted path" course of action. And it seems that people who feel that college is the only way to get a job and those that feel that all IT starts with helpdesk are very often the same people, so there might be a connection. Or I might just imagine that.
It's kind of crazy. You get a degree in whatever field it is (CS, CIS, etc) and then start in an entry level position where someone who never went to college could start and do fine.
@scottalanmiller said:
@johnhooks said:
This kind of destroys the thread I saw on SW where everyone said you had to start in a Help Desk position to be able to learn anything.
LOL. Yup, I've been fighting that misconception my whole career. @AndyW didn't start in helpdesk either and he's a well known consulting IT guy with a long career too (one of the NTG founders.)
I know very few people who hit six figures and started on helpdesk. Most of the people I work with that are in the higher income brackets in IT tended to start off in junior administration, engineering or development roles. You can obviously get there from helpdesk too, but it feels like a very uncommon path to me. Unless you are starting really young.
I've never worked in a Help Desk (thankfully) but from what I have seen/heard, it seems like it's almost impossible to get out. And it looks like it rarely challenges people enough to make them want to be there.
This kind of destroys the thread I saw on SW where everyone said you had to start in a Help Desk position to be able to learn anything.
@coliver said:
I've always seen Kerberos+LDAP+NFS to do the "Active Directory" stuff with Linux. Even had a grad class that had us setup that environment.
I had heard of Kerberos and Samba 4 as an AD replacement but I didn't know you could use it in that regard.
This is along the same lines as a Blackhawk or that d-link spaceship router with a million antennas.
For ~$50 more you could buy a small Sophos UTM. Or save money like Scott said and get all ubiquiti.
@scottalanmiller said:
There are other tools too, like NIS and NIS+ but they are not very good and pretty much no one uses them anymore.
Are there "group policy" type tools that are used or is it just DAC & MAC?
I saw something called Pesselus but I don't know if some of these things solve problems that arent there and are evenenterprise accepted.
@scottalanmiller said:
@johnhooks said:
I never looked into it but I never thought of using kerberos without samba. I just assumed it was mostly for Windows.
Nope, it's all from UNIX originally. That's where it started while at MIT. The use of both LDAP and Kerberos on Windows is completely copied from the UNIX world.
Thanks again!
@scottalanmiller said:
In a large environment of UNIX you would expect to see LDAP and Kerberos most of the time. There are other ways to tackle this like local users and tools to push those out that but that is generally too complex to do on scale.
I never looked into it but I never thought of using kerberos without samba. I just assumed it was mostly for Windows.
@scottalanmiller said:
Linux home directories in a large environment are typically handled via NFS automounters which is amazing. This works so much better than anything on Windows. NFS v3 with AutoFS is fast, transparent and totally slick. And the ease of user between machines is fantastic.
Thanks @scottalanmiller!
@scottalanmiller said:
Well the first question would be.... what kind of large Linux environment are you picturing? Does this mean Linux on the desktop? Only Linux on the server?
I had pictured both. Linux servers and end users on Linux desktops.
I'd like to ask those who are much wiser in Linux than I, what do you use for server/client setups? Samba4? NFS home folders & LDAP? 389 Directory Server? I haven't been a part of a large enterprise Linux environment (yet) and I'm just curious how they tackle these types of things. Thanks!
Pardon my ignorance, what's the advantage to a Mac server?
