Skip to content
This repository has been archived by the owner on Mar 1, 2018. It is now read-only.

Future Directions

Jump to bottom
rickychilcott edited this page May 6, 2012 · 4 revisions

What is next for munki server? Well, here is a high-level overview of the features we hope to add to munki server. This won't cover any details of implementation, but will be more of an end-user wish list. As a disclaimer, this really is a wish list -- some items may never be implemented. In no particular order...

Client Integration/Features

  • Full support for all munki features - This includes blocking applications, optional installs, and anything else that is missing. This will also likely also include non-plist interfaces for features like the installs key.
  • Registration Page - An anonymous page which would allow non-IT users to tell admins about their computers, what unit it should be, etc.
  • Custom Scripts - MunkiServer Scripting Framework for preflight/postflight scripts. We should also allow scripts to live on MunkiServer and dynamically get pulled down at each run
  • Computer Integrity Tests - The ability to assign any number of tests, in the form of scripts, to be run on a munki client to test the integrity of that computer. Is it bound to Active Directory? Are support administrator accounts present? Are the logs in good order?
  • Client Preferences - Fully configurable client preferences with inheritance based on computer, computer group, and unit.

Security

  • Server authentication - This is currently possible, but needs documentation.
  • Security - HTTP Basic username/password on a per-computer basis
  • Client authentication - Client authentication based on an SSL certificate. Intended to tighten security on manifests

LDAP Integration

  • User Integration - The ability to tie MunkiServer to LDAP of (probably) any kind. This includes Active Directory and CAS.
  • Group to Unit Membership Integration - The ability to specify a list of LDAP groups whose members will become members of a specific unit. This moves any user management work to a system that people are used to operating.
  • Computer Integration - Auto-discover computers based on being bound to an LDAP service

Usability

  • Step-by-Step Server Installation Script - In-a-nutshell, setup a server in 10 minutes (plus compile time), without having to know much about Rails or Apache.
  • Linux Server Support - Well, it already supports this, but requires the upload of a pkginfo file along with a package. Perhaps this extra requirement could be removed.
  • Search - A handy search that allows you to find the record you are looking for based on almost any attribute of that record.
  • Slave Package Servers - Easily configurable synchronization of package content to another server for bandwidth limitations or load balancing.
Clone this wiki locally