Ubuntu QA:
BlogBrainstormPackage status
Log in
Ubuntu QA
The Ubuntu community has contributed 13963 ideas, 66846 comments, 1291785 votes

Idea #1357: Ubuntu Home Server for Home Users and Small Businesses Alike



up
192
down
Written by LFenton the 29 Feb 08 at 12:49. Category: Server.
Related to: Nothing/Others. Status: New
Description
What I would like to see from Canonical is an Ubuntu Home Server similar to that of Microsoft's Home Server solution with ease of setup and use as well as the ability to back up workstations on a small network like WHS (Windows Home Server) does. But without the 10 client limitation that WHS server currently has, as well as the ability to easily securely and remotely connect for multimedia content use while working from a remote location. It should be streamlined and easy to setup, maintain and implement both on the server and client(s) side of Ubuntu.
Thank you.


Developer comments
Creating such a product requires work on both the server and the desktop experience of Ubuntu. The final product integrates different components that are currently worked on, such as simple remote server administration, easy backup solution for desktops.

Most of the basic buildings blocks are already available (such as samba/nfs for file sharing and network authentication, avahi for service discovery). Once the others one are built, integration work can begin.

Defining which services or features should be provided and use cases would help.


Attachments
spec Blueprint domain-for-linux: [Information on this blueprint will be retrieved soon]


Duplicates


Comments
arch0njw wrote on the 29 Feb 08 at 12:53
Isn't this, in effect, Medibuntu? I could be missing some details that support "no" as an answer; I'd love to read them.

scorp123 wrote on the 1 Mar 08 at 00:47
@arch0njw: Medibuntu is for multimedia packages that may not be redistributed with the Ubuntu OS (and hence are not on the CD ... you have to use the Medibuntu repos to get those goodies).

I'd welcome if there was a Ubuntu Server edition that offered AD-like features out of the box, e.g. OpenLDAP + NFS + Samba ... right now you'd have to configure all this manually and it isn't really fun to do this.

NicolBolas wrote on the 1 Mar 08 at 13:39
I'm using SME Server 7.3 (CentOS based) for both home ans small business use. A similar solution providing a large service set (NT4 domain controler with samba, filsharing inclueding appleshare support, DNS, mail, web hosting, internet connexion sharing, transparent proxying with a windows update cache contrib, fetchmail,....), all configurable through a simple web inteface, inclueding some colaboration tools (gropware, shared agenda with mobile device synchronisation, like Funambol)... would be a killer solution for small business.

rawsausage wrote on the 1 Mar 08 at 20:13
FreeIPA+additions.

Kent88 wrote on the 3 Mar 08 at 21:09
I wouldn't mind a home server that came with a lightweight desktop like fluxbox (or, I guess, xfce or icewm) and VNC.

It would help me transition over to working with servers.

brettalton wrote on the 5 Mar 08 at 00:01
Ahem: http://www.ubuntuhomeserver.org

travis wrote on the 8 Mar 08 at 04:25
From http://brainstorm.ubuntu.com/idea/3479/

The Server version is a little too advanced, and I think that the Desktop edition would require a lot of configuration.

My ideal Server for home use, supports a software redundancy across drives (and restoration tools for when a drive dies) so that all hard drives don't have to be identical like RAID1 (to make upgrading easy), and also expensive RAID hardware wouldn't be needed. For me, this is the most important feature. I want to be able to add larger drives as they become more inexpensive and I want to be able to replace failed drives with larger versions.

It should also ideally:
* Have default public shares for Music, Video, Pictures, and Documents that are accessible not only from Ubuntu, but also OSX and Windows.
* Have a default website setup to share pictures or home movies if a user wants. (or maybe an app that integrates with Flickr and Vimeo, or other sites)
* Have a default share for backups from other machines on the network using Time Machine, RSync or XCopy.
* Easily integrate with an online backup service (like Mozy?)

The goal of this server version is that it is a central storage point that is reliable, compatible, and easily upgraded and administrated.

wladston wrote on the 14 Mar 08 at 04:25
I have a little computer here (called Kurobox, it doesn't even have a video card), it is running Ubuntu and it is currently my "Home Server". But, since there are no tools to manage it but the command line, it's hard to make stuff work on it! :)

JhansonJr wrote on the 26 Mar 08 at 08:13
I think something between xubuntu and ubuntu server edition would be great. something that would be easy to use RAID and Samba, and other great things that mostly take a degree or certification to figure out.

pierre.slamich@gmail.com wrote on the 6 May 08 at 21:22
http://www.ubuntuhomeserver.org seems more or less dead.

shovelhead wrote on the 13 Jun 08 at 08:28
I am happy to see, that a developer has started to look into it. Here's what I think should be in that home-server thingy:

1) as most users today seem to have an ADSL connection and a router that goes with it, it would be great to have a mode that makes use of it. Say, you just click on the "network via DSL router" button. Most routers will "call themselves" 192.168.0.1 out of the box - start from there and make the server 192.168.0.2 by default.

2) add a "who is in reach" function. Once the server is set up and connected to the router, it would be a dream if you only had to check a box and that links other workstations in reach to the server.

3) there is a /home/public folder (öffentlich in german, publique in french) on every system. That folder should be the place to start. Whatever you want to share, you just drop in /home/public and everybody in the net can read an copy it when connecting to the server and flip through "Adam public, Bobbie public, Charlie public etc... folders) This would also be a gift from heaven for schools and the use of edubuntu in classrooms.

4) provide a "prepare your workstation for networking" and "Prepare your router/switch for networking" manual (.txt will do, but people are suckers for .pdf and pictures...). Explain how to allocate a network adress, how to block a number for internal use and how to set the "free" numbers start value higher.

5) find a way to identify a computer by name - not number. My computers here in the house are named "sun" (the server) and then mercury, venus, earth, mars and jupiter. I work right now as "shovelhead@mercury". In the network, mercury is 192.168.0.3 - and I have to make the real name an "alias". It would be easyer/better to forget about the number and use mercury right from the start.

6) always keep in mind, that this "home-server" thingy is for people who want it foolproof rather than ultra slick. Performance can go a tad down, if the system is easy to maintain. A long time debian user will always set the server and network up in the classic way. I will do so, too. But the teacher in my girl's school, where I installed ubuntu + edubuntu add on on 12 machines, wants ist easy, with a very clear picture and no magic at all. Right now he calls me, when a new kid has to be added to the number of users. It would be great if there was a button "add new user" and then chose "limited to any special workstation" or "login on any worstation"

7) excuse my bad english - I sometimes miss a special term and have to use a lot of words to make my point.

8) rock n roll!


notyetroot wrote on the 10 Aug 08 at 17:58
1. Take Ubuntu Home.
2. Remove anything you don't want.
3. Install apache.
4. Profi- I mean, you're done!

NicolBolas wrote on the 14 Sep 08 at 00:10
Use case and features : See similar products, like :
- SME Server (www.contribs.org)
Workgroup server, CentOS based, Custom web administration panel and configuration file template mechanism (written in perl).
Providing many features to small workgroups or even home networks, including :
- IP Gateway with transparent proxy and VPN (pptp) server, DNS and DHCP server for LAN. Lacks IPv6 supports, DMZ, WiFi/unsafe zone, multihoming (multiple WAN interfaces for load balancing / redundancy)
- Mail server (qmail) with antispam/antivirus, supporting an optional fetchmail package
- Web/FTP : can hosts PHP or CGI applications easily
- Samba : windows domain controller, easy user management, shared home directories, use iBays for group directories
- Many contribs to add extra features

This feature set is enough for most workgroups. Some extra features will be requested by home users (media server, with the corresponding media player appliance), gameserver, domotic...

More or less : take SMEServer's feature set, add IPCop's features + IPv6 support to have a proper yet versatile network setup, pack this with a smooth Web UI providing a 3 level setup (basic feature sets, custom feature sets, advanced / manual config), try aiming to Leopard Server' ease of use, and choose components carefully (not exim, please, not exim...) and you should be on the good way.

ubuntuAdmin wrote on the 15 Oct 08 at 10:20
In my IDEA №13590 a have an answer:
"A developer has asked for use cases from the community, apparently without response (THAT is what is needed to make progress, not a feature list)"

Use cases for my & my company:
Preconditions:
1. installed Ubuntu (server or client), with installed "SOHO server" task.
2. All users are registred (in any way) on Ubuntu (here i mean that they have to be registred, but it does not mean thay have to linux users. They can be saved as LDAP records and do not have linux account).

*Use cases will be posted in next posts*

ubuntuAdmin wrote on the 15 Oct 08 at 10:25
Use case: I need mail for office.
1. I login to Ubuntu, then use *SOHO-tool* and connect to my server.
2. I set basic configuration: my server responsible for "mycompany.com" domain, all other mail are going to SMTP-relay. Setup SMTP-relay informaton.
3. I set basic server's field: [*] All registred users have mail boxes as their usernames plus domain.

This mean if we have domain "mycompany.com" and registred user "joe" server will get all mail going to "joe@mycompany.com". As soon as we register new use, for example "mary.family" - server will get mail to "mary.family@mycompany.com".

PS "SOHO server" task installs MTA (example: postfix) and IMAP(s) / POP3(s) server that responsible for mail-delivery process.

ubuntuAdmin wrote on the 15 Oct 08 at 10:29
Use case: I need DHCP & DDNS
1. I login to Ubuntu, then use *SOHO-tool* and connect to my server.
2. I configure DHCP: set primary & secondary DNS servers, gateway.

When computer start working it asks DHCP server for IP-address. When DHCP give IP-address DHCP updates DNS with info about that computer.

ubuntuAdmin wrote on the 15 Oct 08 at 10:37
Use case: I need DNS
1. I login to Ubuntu, then use *SOHO-tool* and connect to my server.
2. I configure DNS server and set provider DNS-server viа it can resolve name (SOHO DNS usually should work as DNS-proxy)

Of course DNS MUST know about all computers working in that network (DDNS & DHCP solve this problem).

ubuntuAdmin wrote on the 15 Oct 08 at 10:43
Use case: User authentication
All type of work on server can be done only by authenticated users.

1. I login to Ubuntu, then use *SOHO-tool* and connect to my server.
2. I select existing user (from existing OU) OR create new one.
3. For selected user i can set password.

After that all services that can authenticate user will use that password.

ubuntuAdmin wrote on the 15 Oct 08 at 10:46
Use case: File/print server

1. I login to Ubuntu, then use *SOHO-tool* and connect to my server.
2. I open SAMBA configuration.
3. In that config i set: shared resources, their names and users that can use them.

When user trying to use SAMBA resource he(she) have to authenticate with password setted on previous case: "Use case: User authentication".

ubuntuAdmin wrote on the 15 Oct 08 at 11:15
Use case: Company portal / Subversion repository authentication

Precondition:
1. apache & svn & dav_svn installed.
2. all necessary users are registered in *SOHO* server.

All users have to use *SOHO* credentials to get Subversion repository.

PS it is not difficult task because Subversion authenticates through apache, and apache authenticates users through *SOHO* LDAP server.

ubuntuAdmin wrote on the 15 Oct 08 at 11:15
Use case: Company proxy authentication

Precondition:
1. squid installed.
2. all necessary users are registered in *SOHO* server.

All users have to use *SOHO* credentials to use proxy.

ubuntuAdmin wrote on the 15 Oct 08 at 11:18
Use case: Company FTP-server authentication.

Precondition:
1. some FTP-server installed.
2. all necessary users are registered in *SOHO* server.

All users have to use *SOHO* credentials to use FTP.

ubuntuAdmin wrote on the 15 Oct 08 at 18:32
Use case: User login to computer

Precondition:
1. Admin register computers in *server*

Use case:
1. Users turn on their computers.
2. Users have to use *server* credentials to login.

PS SAMBA can be used for authentication in *SOHO* installations.


Post your comment