OES 11 SP2 Shema Extensions

Question

I am planning on adding my first OES 11 SP2 server into our Tree. What is the best way to Extend the schema to prepare for this? According to the Docs it says
"The simplest way to extend the schema for OES 11 SP2 servers is to have a tree admin install the first OES 11 SP2 server and the first instance of each OES 11 SP2 service that you plan to run on your network."
I am a tree admin, so if I install the latest SLES/OES on a server, does this mean that the schema will automatically be extended and I will not have to do anything else with the Schema? Or is there a better way to do this by extending it prior to installing the server into the tree?
Thanks,
Andrew

Answer 1

On 04/08/2014 10:56 AM, acshearer wrote:
>
> Here is the link from the documentation.
>
> https://www.novell.com/documentation...t.html#bhora0c
Good to know.
Well, there are technically correct things about that page, though I wish
it would elaborate a bit more.
First, the reason you use a tree admin is because you need to be a tree
admin to make schema changes at the [root] of the tree. Simple enough.
Second, while pointing to a Read/Write of [root] should work, the fact of
the matter is that one of the few roles that a Master has alone is control
of schema, so why does the doc state to point to a R/W? No idea. Point
to the Master of [root] unless you really, really cannot (and I would be
surprised if this was ever really a legitimate problem/limitation). Doing
so ensures that, if schema is taken by the Master, it will be pushed out
(to other server holding replicas of the [root] partition) and down (to
child partition Masters and R/Ws). Schema always flows out and down.
That a R/W may be clever enough to take changes and send them to the
Master is moot, in my mind.
Finally, I've never used that Yast-based schema tool, and that may work
really well. The biggest concern I would have with that is that it
implies adding your new server to the tree in a way that cannot extend
tree schema, and then doing the schema extension later. That's not
terrible, and eDirectory will be fine eventually, but in the meantime your
new OES server may have fits about things requiring new schema, such as
the LDAP services in eDir 8.8 SP8. As a result, LDAP may not load until
you do this schema extension, then some followup steps ('ndsconfig
upgrade' on the new server may do all of it for you) to get things
configured once the new schema is available throughout the tree. My hope,
though, is that the Yast-based tool can be pointed not just to the Master
(not R/W... a broken record I am, I know) or [root], but that it can be
pointed from this tree (the test one I mentioned before) to that tree over
there (the production one) and do the same thing. If so, this may be the
easiest and safest way (since not using ndsrepair) to extend schema in a
tree from another server. If so, I like this tool.
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...