Directory HomeFAQEudora AccessTips and TricksComplex SearchesAbout the DirectoryVital Stats |
Introduction to X.500 for BeginnersSome RFCs to readThe Need for X.500UT System Mandate centralized directory services useful Advantages:
Experiences at other UT ComponentsIn early April of 1996 I gathered some technical information regarding the implementation and use of X.500 directory services from various components of the University of Texas System. The purpose of this was to familiarize myself with the X.500 system in general and more specifically to understand the hardware and systems administration requirements for running an X.500 server. I did not discuss policy issues except as they related to specific technical matters.Implementing X.500 at UT HoustonISODE ImplementationThe software itself consumes considerable disk space, on the order of 150MB - 200MB for the source and compiled binaries.Dataset SizeCurrently we have less than 10,000 staff and students total. According to William Green at UT Austin, it requires about 2K per person if the data is fully indexed. This number is on the high side but allows for plenty of cushion. Therefore the total dataset size would be about 20MB.In-Core Memory RequirementsGiven the wide array of machine sizes and configurations in use it is difficult to come up with a solid description for an appropriate machine, so it would be best to focus on finding a machine with sufficient capacity to include a cushion, plus very good upgradability. Since all of the machines currently in use seem to be older models, it is likely that the performance will be acceptable on any given modern host. With those requirements in mind a machine with 128MB of RAM and a dedicated 1.2GB hard drive to include both the DSA software and data. ReferencesWeb sites and other references |