##(see the SpecSpec for an explanation) * '''Launchpad Entry''': UbuntuSpec:server-karmic-directory-management * '''Created''': * '''Contributors''': * '''Packages affected''': == Summary == ## This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples. == Release Note == ## This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.) ## It is mandatory. == Rationale == ## This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. == User stories == * create/edit/update/delete a user/group/host/service via web and CLI. * search for user/group/host/service via web and CLI. * change user password. == Assumptions == == Design == ## You can have subsections that better describe specific parts of the issue. Several options: === Freeipa v2 === Pros: * Actively developed. * Solves our use cases. * Infrastructure already available: * install scripts * management interface in python, both CLI and web. Cons: * Upstream only interested in supporting Fedora Directory Server: https://www.redhat.com/archives/freeipa-users/2009-May/msg00020.html * v2 targeted for Q3 2009: https://www.redhat.com/archives/freeipa-users/2009-June/msg00008.html * Technical choice (minor): xmlrpc. === Freeipa v1 === Pros: * already released. * support base use case. * web + cli support. Cons: * v2 is a rewrite. * unknown support from upstream for v1. === smbldap-tools === Pros: * already packaged. * minor updates to support default DIT. Cons: * Only covers User/Group mgmt. * upstream not very active. * cmd line only. === ldapscripts === Pros: * already packaged. * minor updates to support default DIT. Cons: * Only covers User/Group mgmt. * Cmd line only === Gosa === * web interface written in php. * no CLI. * ACL stored as an attribute in the object rather than using the native openldap ACL system. === New mgmt interface === (pylons|turbogears)+lazr.restful+lazr.restclient. Something similar to the new Mailman 3 admin interface: http://wiki.list.org/display/DEV/PyCon+Sprint+2009 == Implementation == ## This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like: === FreeIPA v1 === 1. Update to support different DIT and package relevant part of freeipa v1 components: * ipa-server/xmlrpc-server * ipa-admintools * ipa-server/ipa-gui Note: ipa-kpasswd is not needed as it's supported in kadmind starting from 1.7. === UI Changes === ## Should cover changes required to the UI, or specific UI that is required to implement this === Code Changes === ## Code changes should include an overview of what needs to change, and in some cases even the specific details. === Migration === ## Include: ## * data migration, if any ## * redirects from old URLs to new ones, if any ## * how users will be pointed to the new way of doing things, if necessary. == Test/Demo Plan == ## It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage. ## This need not be added or completed until the specification is nearing beta. == Unresolved issues == ## This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved. == BoF agenda and discussion == ## Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected. ==== UDS Karmic discussion ==== {{{ = Managing the Directory = * Tool target Audience. * Tools for system admins, or users. * Allow customization by admins. * phpldapadmin * Need task specific tools. * Won't be provided by Ubuntu because they are too specific to the domain. * Should Ubuntu make the task easier? * Provide tools to manage the default DIT. * MDS tools. * Goza * Cluttered interface. * Not all features may be useful. * smbldaptools * Works well. * Needs some configuration. * Need to learn new commands. * Apache Directory Studio * Tool for System Admin. * adduser added functionality. * Will adduser only affect local user's, or the whole directory. * To manipulate the directory a special switch would be needed. * Still have an issue with password sync. * Focus on one task at a time. * Provide New tools for the Directory. * Web Admin component. * Web2LDAP -- customized * Need a write interface to the NSS attributes. * getent * putent * delent * Need to specify which backend to manipulate. * For Karmic * adduser * addgroup * modifygroup * addhost? * sudoers }}} ---- CategorySpec