Tuesday I will be nuking the Hera server and rebuilding it as an OES-Linux server. The other two eDirectory servers will not be following it any time soon for two reasons:
And then we learn how to support these things. With patches coming out for them every other day (thank you, Open Source) the patch-cycle management will need tweaking from what we do with our other systems (specifically, NetWare and Windows). Also needing input is how to get the other admins in, and how hosting eDir on Linux changes how we kick problems.
Exciting stuff. There are a few things that needed doing to get it into our environment. Firstly, Hera is a Primary Timesync source, which will obviously have to change. Second to that, we have a pair of service monitoring services that need to be informed how to re-query their bits. This server doesn't do SLP, so we don't have to worry about that problem quite yet.
I hope to post experiences after I have things in place. But the server is physically hosted not in my building, so I'll be away-from-desk the whole day I'm doing the install.
Tags: netware, edir
- No direction yet from On High (which just changed people) regarding Novell-supplied operating systems.
- Two NetWare dependancies on those two servers
And then we learn how to support these things. With patches coming out for them every other day (thank you, Open Source) the patch-cycle management will need tweaking from what we do with our other systems (specifically, NetWare and Windows). Also needing input is how to get the other admins in, and how hosting eDir on Linux changes how we kick problems.
Exciting stuff. There are a few things that needed doing to get it into our environment. Firstly, Hera is a Primary Timesync source, which will obviously have to change. Second to that, we have a pair of service monitoring services that need to be informed how to re-query their bits. This server doesn't do SLP, so we don't have to worry about that problem quite yet.
I hope to post experiences after I have things in place. But the server is physically hosted not in my building, so I'll be away-from-desk the whole day I'm doing the install.
Tags: netware, edir
I'm looking forward to updates. I'm figuring my next brand new server install with a Novell OS will be OES Linux. I've played with it, but never in production. I'm looking at next summer being the year that I take the plunge.
I'm looking hard at OES2 for my further deployments. Like I said, I have a couple of NetWare dependancies that aren't resolvable on a Linux kernel right now and those need fixing before I can move those other two servers. The big thing will be when it comes time to replace nodes in the WUF cluster. That's the latest point where upper management can make the go/no-go decision regarding further comittment to Novell-supplied operating systems; though, that decision could come before that point.By next Summer, OES2 should be out. I'm crossing my fingers that I'll have hardware available to re-do the benchmark I did in January. That'll help. Plus, making NSS and NCP on Linux feature-complete when compared with NetWare will be the other BIG thing that needs doing in that release.
I'm with you on OES2. People are really chomping at the bit waiting for operating systems like Vista or OSX 1.5. I'm one of the few geeks sitting around waiting for any news on Cypress. I really think OES2 is going to be a huge factor with anyone running Netware. It will certainly determine the landscape of my server room for the next decade. Have you heard any feature rumors? There's nothing offical, from what I've been able to dig up.
As OES2 isn't in beta quite yet, Novell is being close-mouthed about what's going to be in it. I DO know that it'll be based on the SLES10 base, which will have significant improvements on the kernel end. How that'll affect the "netware services" hasn't been announced.
regarding patches on OES/Linux, you're right it is really tricky as Novell recommand you push all patches together rather than update one at a time.They provide a "rug pin oes:" but recommand to use a "rug ping --entire-channel".On our 20 OES/linux boxes it's rather difficult because if you test an "entire-chanel" on one server one day, and then wait 1 week and do the same on an other server : you won't have the same patches :-(