iammi Absent Member.
Absent Member.
347 views

Basic question moving objects with childs within eDirectory


Hello

I have an Organizational Unit objects under a given container on
eDirectory

The structure of my Organizational Units is hierarchical of 9 levels

The business rules stipulates that if a non leaf OU (called "myOU" for
instance) has to be deleted, all his children has to be moved a level
up, so "myOU" is deleted and all the subtree (under myOU) will be
atached to "myOU" parent

Before I start doing this, I would like to know if there is any out of
the box operation in NIM allowing this, or every thing has to be
implemented from scratch?

Thanks in advance


--
iammi
------------------------------------------------------------------------
iammi's Profile: http://forums.novell.com/member.php?userid=71308
View this thread: http://forums.novell.com/showthread.php?t=449563

Labels (1)
0 Likes
9 Replies
Knowledge Partner
Knowledge Partner

Re: Basic question moving objects with childs within eDirectory

On 12/14/2011 7:56 AM, iammi wrote:
>
> Hello
>
> I have an Organizational Unit objects under a given container on
> eDirectory
>
> The structure of my Organizational Units is hierarchical of 9 levels
>
> The business rules stipulates that if a non leaf OU (called "myOU" for
> instance) has to be deleted, all his children has to be moved a level
> up, so "myOU" is deleted and all the subtree (under myOU) will be
> atached to "myOU" parent
>
> Before I start doing this, I would like to know if there is any out of
> the box operation in NIM allowing this, or every thing has to be
> implemented from scratch?


Out of the box the driver supports flat (everyone goes in one container)
and mirror, where the current model is mirrored to the other tree.

The shuffling OU's and moving objects would be custom on your part.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Basic question moving objects with childs within eDirectory

Geoffrey Carman wrote:

> The shuffling OU's and moving objects would be custom on your part.


and non-trivial stuff with a high risk of runnig into replication problems,
too. IIRC non-empty containers can only be moved if they are partition
boundaries or you'd have to play towers of saigon with the OUs to keep. You'd
have to move all of them in leaf-to-root order to the new parent ou first and
then rebuild the tree structure in root-to leaf order my moving every OU
another time.

This would make for a good dirxmlscript contest challenge, btw. Geoff....?
0 Likes
Knowledge Partner
Knowledge Partner

Re: Basic question moving objects with childs within eDirectory

On 12/14/2011 9:13 AM, Lothar Haeger wrote:
> Geoffrey Carman wrote:
>
>> The shuffling OU's and moving objects would be custom on your part.

>
> and non-trivial stuff with a high risk of runnig into replication problems,
> too. IIRC non-empty containers can only be moved if they are partition
> boundaries or you'd have to play towers of saigon with the OUs to keep. You'd
> have to move all of them in leaf-to-root order to the new parent ou first and
> then rebuild the tree structure in root-to leaf order my moving every OU
> another time.
>
> This would make for a good dirxmlscript contest challenge, btw. Geoff....?


I agree, it seems ill advised.

I am up for another contest. Lets come up with something slightly more
constrained than just most interesting script examples.

Got any thoughts?

Maybe interesting Packaging tricks this time? What do you guys think?

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Basic question moving objects with childs within eDirectory

Geoffrey Carman wrote:

> Maybe interesting Packaging tricks this time?


How to change the driver shim with an add-on package and revert to the base
package shim on uninstall?

Really like to know the answer for the uninstall part...
0 Likes
Knowledge Partner
Knowledge Partner

Re: Basic question moving objects with childs within eDirectory

On 12/14/2011 9:29 AM, Lothar Haeger wrote:
> Geoffrey Carman wrote:
>
>> Maybe interesting Packaging tricks this time?

>
> How to change the driver shim with an add-on package and revert to the base
> package shim on uninstall?
>
> Really like to know the answer for the uninstall part...


So this is almost an approach, of lets pose some challenges, in terms of
how could I do this?

Interesting, I could see that as a workable approach.

I think this is in the Package Prompts, but not exactly sure how to do
it. I am pretty sure the upgrade would be easy. I am not sure what
will happen on the uninstall.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Basic question moving objects with childs within eDirectory

On 14.12.2011 15:29, Lothar Haeger wrote:
> Geoffrey Carman wrote:
>
>> Maybe interesting Packaging tricks this time?

>
> How to change the driver shim with an add-on package and revert to the base
> package shim on uninstall?


This sounds very much like it's against the design intent of packages.
The driver shim IS the base package.

Or do you simply mean adding for example an extra parameter in
driver-options within an add-on package? And then having this removed on
uninstall. I've been meaning to dig into this type of example myself.
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Basic question moving objects with childs within eDirectory

On 12/14/2011 10:02 AM, Alex McHugh wrote:
> On 14.12.2011 15:29, Lothar Haeger wrote:
>> Geoffrey Carman wrote:
>>
>>> Maybe interesting Packaging tricks this time?

>>
>> How to change the driver shim with an add-on package and revert to the
>> base
>> package shim on uninstall?

>
> This sounds very much like it's against the design intent of packages.
> The driver shim IS the base package.
>
> Or do you simply mean adding for example an extra parameter in
> driver-options within an add-on package? And then having this removed on
> uninstall. I've been meaning to dig into this type of example myself.


I agree with Alex that it is probably against the point, but the more I
think about that, its in an attribute right, not part of the Config XML.

In which case, maybe a Resource of a Ds-object. But that will just
remove it on package uninstall, not likely easy to put it back to the
original... Hmm... Interesting issue.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Basic question moving objects with childs within eDirectory

Alex McHugh wrote:

> This sounds very much like it's against the design intent of packages. The
> driver shim IS the base package.


I have to admit that this is probably a very rare use case, but it is a real
world example and an issue still to solve in the package version of the
PWNotify driver.

The base driver can run on both the null and loopback shim but since it relies
on publisher heartbeat and there were (are?) some bugs with heartbeat in the
loopback shim, the null shim is the safest way to go for most deployments.

Only when you install the jobs and trigger add-on you would need the loopback
shim so the subscriber trigger events that replace the built in scheduler can
loop over to the publisher channel.

Currently the add-on changes the shim on install, which is trivial (just add
the proper attribute to the initial settings of the package), but I still have
to find a way to revert back ti the null shim on removal.

--

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Basic question moving objects with childs within eDirectory

Alex McHugh wrote:

> This sounds very much like it's against the design intent of packages.


btw. this seems more of a general shortcoming of the current package system.
There are transforms that run on install time (Initial Settings) and on
Upgrade/Downgrade (Upgrade Settings) but no way to specifically do anything on
uninstall only.
Maybe the package developers should have a chat with the zenworks folk, this is
very similar to software distribution and nobody who ever worked in that field
would forget to implement the uninstall scripts feature. This is even stranger
considering much more advanced features like requirements and chaining already
have been implemented. Well, something to hope for in 2012, I guess 🙂

--

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.