Knowledge

Ganymede (software)

Source 📝

202: 36: 27: 186:
Above all, Ganymede is designed around administration teams. Administrators are members of 'Owner Groups', which own objects. Any object that is changed by a user or an automated task can result in change report email being sent to administrators in the appropriate Owner Group, making it possible
174:
and to maintain consistency within and between objects. Adopters can also create custom tasks which can be executed at specified times by the internal Ganymede scheduler. Such custom tasks can make changes in the server's object database and/or can run external scripts to update external services.
166:
based) to create, modify, or delete objects in the database. Whenever a user commits a transaction, the Ganymede server schedules a number of background threads to write out updated network source files and run whatever system scripts are required to propagate the new data into the managed network
178:
Ganymede has an elaborate XML data format which can be used to import and export the server's object database schema and object data. Importing XML will typically result in the creation, modification, or deletion of database objects, and will trigger one or more network directory service rebuilds
187:
for admins to keep up to date with changes that others in their groups are making. Owner Groups can be granted authority over arbitrary subsets of the object database, making it easy to slice up the network directory space in any fashion that may be desired.
190:
As a programmable framework, Ganymede must be programmed for a specific set of directory management tasks. Fundamental Generic Networking in Germany has used it as the basis of their Doctor DNS project, which is being used to manage DNS for the
167:
directory services. If multiple users are working concurrently, the scheduler makes sure that the entire network environment is updated with transactionally consistent directory images as builds finish and new ones are issued.
162:. The Ganymede server maintains a transactional object graph database of network information such as user objects, group objects, system objects, network objects, etc. Users and administrators run Ganymede clients (GUI or 152: 411: 170:
The Ganymede server is meant to be programmed by the adopter, who can define arbitrary object data types along with custom logic to interact with the user through the
281: 123:
is an open source network directory management framework, designed to allow administrator teams to collaboratively manage subsets of an organization's
252: 406: 331: 416: 192: 391: 140: 401: 207: 227: 144: 285: 74: 159: 386: 128: 92: 67: 35: 26: 180: 171: 421: 396: 334:. Proceedings of 2007 IEEE Consumer Communications and Networking Conference. Archived from 335: 8: 79: 132: 124: 136: 87: 332:"Self-management in Heterogenous Networks Using A Service-Oriented Architecture" 231: 380: 310: 155:
conference, Ganymede has been under public development and use since then.
253:"Ganymede: An Extensible and Customizable Directory Management Framework" 367: 306: 46: 103: 358: 158:
Ganymede uses a central server which supports clients connecting via
362: 51:
Applied Research Laboratories at The University of Texas at Austin
371: 260: 148: 151:, among others. First announced and released at the 1998 163: 412:
Free software programmed in Java (programming language)
197: 378: 259:. Proceedings of the 1998 LISA Conference. 34: 25: 220: 193:Kaiserslautern University of Technology 379: 16:Network directory management software 208:Free and open-source software portal 257:Jonathan Abbey and Michael Mulvaney 13: 14: 433: 352: 407:Free network management software 200: 417:Software using the GPL license 324: 299: 274: 245: 82:/ Network directory management 1: 307:"FLOSS Weekly #143: Ganymede" 214: 392:Cross-platform free software 7: 402:Identity management systems 10: 438: 93:GNU General Public License 228:"Ganymede change history" 98: 86: 73: 63: 55: 45: 40:Ganymede Editing a System 33: 24: 80:Identity management 21: 387:Directory services 313:. 24 November 2010 179:just as using the 125:directory services 47:Original author(s) 19: 263:. 6 December 1998 183:client would do. 118: 117: 429: 347: 346: 344: 343: 328: 322: 321: 319: 318: 303: 297: 296: 294: 293: 284:. Archived from 278: 272: 271: 269: 268: 249: 243: 242: 240: 239: 230:. Archived from 224: 210: 205: 204: 203: 137:Active Directory 114: 111: 109: 107: 105: 38: 29: 22: 18: 437: 436: 432: 431: 430: 428: 427: 426: 377: 376: 355: 350: 341: 339: 330: 329: 325: 316: 314: 305: 304: 300: 291: 289: 280: 279: 275: 266: 264: 251: 250: 246: 237: 235: 226: 225: 221: 217: 206: 201: 199: 102: 56:Initial release 41: 17: 12: 11: 5: 435: 425: 424: 419: 414: 409: 404: 399: 394: 389: 375: 374: 365: 354: 353:External links 351: 349: 348: 323: 298: 273: 244: 218: 216: 213: 212: 211: 116: 115: 100: 96: 95: 90: 84: 83: 77: 71: 70: 65: 61: 60: 57: 53: 52: 49: 43: 42: 39: 31: 30: 15: 9: 6: 4: 3: 2: 434: 423: 422:1998 software 420: 418: 415: 413: 410: 408: 405: 403: 400: 398: 395: 393: 390: 388: 385: 384: 382: 373: 369: 366: 364: 360: 357: 356: 338:on 2010-05-02 337: 333: 327: 312: 308: 302: 288:on 2013-04-30 287: 283: 277: 262: 258: 254: 248: 234:on 2013-06-15 233: 229: 223: 219: 209: 198: 196: 194: 188: 184: 182: 176: 173: 168: 165: 161: 156: 154: 150: 146: 142: 138: 134: 130: 126: 122: 113: 101: 97: 94: 91: 89: 85: 81: 78: 76: 72: 69: 66: 62: 58: 54: 50: 48: 44: 37: 32: 28: 23: 397:DNS software 340:. Retrieved 336:the original 326: 315:. Retrieved 311:FLOSS Weekly 301: 290:. Retrieved 286:the original 276: 265:. Retrieved 256: 247: 236:. Retrieved 232:the original 222: 189: 185: 177: 169: 157: 120: 119: 282:"DoctorDNS" 153:USENIX LISA 381:Categories 342:2013-03-02 317:2013-03-01 292:2013-03-01 267:2013-08-15 238:2013-03-01 215:References 127:, such as 64:Written in 368:Ganymede 363:Open Hub 359:Ganymede 160:Java RMI 121:Ganymede 20:Ganymede 108:.utexas 99:Website 88:License 372:GitHub 261:USENIX 149:RADIUS 147:, and 112:/gash2 106:.arlut 104:tools 145:DHCP 141:LDAP 110:.edu 75:Type 68:Java 59:1998 370:on 361:at 181:GUI 172:GUI 164:XML 133:DNS 129:NIS 383:: 309:. 255:. 195:. 143:, 139:/ 135:, 131:, 345:. 320:. 295:. 270:. 241:.

Index



Original author(s)
Java
Type
Identity management
License
GNU General Public License
tools.arlut.utexas.edu/gash2
directory services
NIS
DNS
Active Directory
LDAP
DHCP
RADIUS
USENIX LISA
Java RMI
XML
GUI
GUI
Kaiserslautern University of Technology
Free and open-source software portal
"Ganymede change history"
the original
"Ganymede: An Extensible and Customizable Directory Management Framework"
USENIX
"DoctorDNS"
the original
"FLOSS Weekly #143: Ganymede"

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.