SME Server wishlist
From SME Server
Jump to navigationJump to searchNice to have
- Webmail (Ian)
- Decide if webmail is Core or Contrib
- Investigate the webmail solutions available, and features such as activesync
- Decide which webmail should be in core, if any
- IPV6 (Ian)
- support IPv6. See Bug 6393
- Samba 4 (David Harper)
- Decide whether Samba 4 is going to be production ready for the SME 9 dev cycle
- Investigate the implications for the SME ecosystem of moving to Samba 4 (e.g. currently UNIX accounts are used for authentication but for Samba 4 all auth would have to be done through Active Directory - e.g. IMAP, webmail, VPN etc.)
- Would likely require BIND 9 instead of dnsmasq
- NFS server (David Harper)
- Investigate ways of promulgating network-wide UNIX UID & GID - LDAP or AD based
- Would allow for "roaming profile" like setups for clients like Ubuntu and CentOS Desktop
- High Availability (HF)
- Initial HA based on 2-node fail-over, active/standby cluster involving 2 SME Servers
- Only supervised services are monitored and HA aware
- Includes real-time replication of data between the 2 nodes (LAN/WAN Raid1 based on DRBD)
- Proof of concept available
- Cloud awareness (HF)
- Market development and usage of services and software are changing quickly. One of them being 'Cloud' and all xaaS related services
- Being able to deploy SME Server as a Virtual Machine (VPS) in ServerGateway mode with an ISP that only offers 1 Network interface
- Patch available, Proof of concept applied on production servers
Bug 7200
- Delegation - into core (larieu)
- Server roles - support by default for "split" servers
- one approach is PDC + mail only + ftp only...
- in this scenario if you declare server 2 mail only and you set on the primary mx.domain.tld remote x.x.x.x both must work in tandem as one
- the main one should not keep any mail all related tasks to mail should be delegate to the second one, the second one should receive and maintain local backup user data from main one
- another approach is PDC Main branch + backup PDC + branch server 1 + branch server 2 ....
- in this scenario you have the main with HA backup + subdomain1.domain.tld should contain everything for your subdomain inclusive local authentication + mails of users (+ VPN s2s between master and subdomains - star scenario) but users data should be set only on main one, the server-manager on subdomain should have only local users
- one approach is PDC + mail only + ftp only...
- user role delegation - now you can achieve this by separate contrib
- to be able to delegate user administration for group / domain /...
- to be able to delegate ibay administration
- to be able to delegate access to some panels
- Server roles - support by default for "split" servers
- OpenVPN Bridge (Credit: Daniel)
- OpenVPN_Bridge is a much wanted feature, and could be considered as a Core feature
- Remote workers, home office, road-worriers is a very common way of working today
- Git (Marco Hess)
- Move the development of SME Server and SME Contribs to a more modern version controls system like Git instead of CVS.
- Some work/investigation has already be done https://github.com/smeserver a few years ago.
- Minimise Required Reboots (Marco Hess)
- It would be nice if a contrib package on install (or upgrade) could flag that the full blown signal-event post-upgrade and signal-event reboot is not required.
- chpst (wellsi)
- Make a decision on chpst vs softlimit (runit rather than daemontools). See Bug 509
- Re-ordered server configuration pages (HF)
- Start with server role, then continue with existing order (POC available)
- Add new server role 'Hosted virtual server'. If only 1 NIC present, a second dummy will be used, otherwise usual server/gateway mode (POC available)
- Add SNMP monitoring in default installation (Simon van Sleuwen)
- 2 WAN + 2 LAN
- 2 WAN - nowadays you have one terrestrial internet connection and for shure good plans from GSM company (Wireless one - but with ETH connection for the whole house) - why to not have