Would AD/LDAP integration be of help with this problem? If you are an organization that uses AD, and already have your machines grouped by OU it might be useful to be able to populate fog groups from OUs.
Something for the post .33 world?
Would AD/LDAP integration be of help with this problem? If you are an organization that uses AD, and already have your machines grouped by OU it might be useful to be able to populate fog groups from OUs.
Something for the post .33 world?
Getting back to work on PxePackage.
I did a little work on PxePackage over the holiday, and I’ve come up with 2 questions.
You did not like the design in part because it broke the one FOGControllerManager to one FOGcontroller relationship, and also due to concern that the calling code would need to know the subclass in order to get the call right. I think I can answer these objections, and would like to continue with the PxePackage and sub classes design because it simplifies the code to generate pxeconfig for fog tasks. It also creates a relatively clean route to extend/modify PxePackage to work with other pxe-bootable systems.
I propose 2 steps to address the problems of the multi class design.
First write a manager for each PxePackage controller subclass. The subclass managers can be one liners:
[PHP]class PxePackageFogManager extends PxePackageManager {}[/PHP]
Second create an interface that PxePackage and it’s subclasses must implement as a means of enforcing consistent method names and calling.
The idea is that calling code can always use PxePackageManager. The returned object could be either a PxePackage object or a PxePackageSubClass object,but the calling code won’t need to know or care about the difference.
Hello new forum. Note the new handle. With Christmas coming I’ll not be doing much php coding until after the first of the year.
rpoyner