Revision history for HServer


Revision [1098]

Last edited on 2009-11-30 17:13:36 by LinusEricsson
Additions:
===Useful documentation===
[[https://help.ubuntu.com/community/SSH/OpenSSH/Advanced?action=show&redirect=AdvancedOpenSSH Ubuntu documentation - AdvancedOpenSSH]]
[[https://help.ubuntu.com/community/SingleSignOn Ubuntu documentation - SingleSignOn]]
[[https://help.ubuntu.com/community/OpenLDAPServer Ubuntu documentation - OpenLDAPServer]]

Revision [1097]

Edited on 2009-11-30 16:42:18 by LinusEricsson
Additions:
~- Some sort of PKI, example: [[https://www.openca.org/projects/openca/ OpenCA]] or [[http://wiki.openxpki.org OpenXPKI]]
Deletions:
~- Some sort of PKI, example: [[https://www.openca.org/projects/openca/ OpenCA]] or [[http://wiki.openxpki.org OpenXPKI]

Revision [1096]

Edited on 2009-11-30 16:42:04 by LinusEricsson
Additions:
~- Some sort of PKI, example: [[https://www.openca.org/projects/openca/ OpenCA]] or [[http://wiki.openxpki.org OpenXPKI]
~- http://www.cynops.de/oss/CertNanny/
Deletions:
~- Some sort of PKI, example: [[https://www.openca.org/projects/openca/ OpenCA]]

Revision [879]

Edited on 2009-03-19 20:34:16 by LinusEricsson
Additions:
~- http://eol.ovh.org/winexe/

Revision [777]

Edited on 2008-11-28 23:30:34 by LinusEricsson
Additions:
~- [[http://www.isc.org/index.pl?/sw/bind/index.php BIND]] as nameserver. (Alternatives are djbdns or PowerDNS) Use together with ldap2dns for automatic generation of zone files from ldap. (OR: http://bind-dlz.sourceforge.net)
Deletions:
~- [[http://www.isc.org/index.pl?/sw/bind/index.php BIND]] as nameserver. (Alternatives are djbdns) Use together with ldap2dns for automatic generation of zone files from ldap. (OR: http://bind-dlz.sourceforge.net)

Revision [776]

Edited on 2008-11-28 20:39:20 by LinusEricsson
Additions:
There will be an agent running on all GNU/Linux clients, the agent will be responsible for checking the LDAP directory for changes and apply them.
The agent authenticate against the directory using kerberos and the computers machine account. (Principal host/fqdn@DOMAIN.TLD)
Responsibles:
Deletions:
Some sort of software is needed. There must be a daemon responsible for configure the computer acording to the configuration data in the directory.

Revision [752]

Edited on 2008-10-25 20:52:58 by LinusEricsson
Additions:
===Useful tools===
[[http://directory.apache.org/studio/ Apache DS studio]]

Revision [707]

Edited on 2008-08-12 14:04:07 by LinusEricsson
Additions:
=== My idea ===
Deletions:
=== My dream ===

Revision [619]

Edited on 2008-05-30 21:59:17 by LinusEricsson
Additions:
---
CategoryProjects

Revision [500]

Edited on 2008-05-14 22:40:29 by LinusEricsson
Additions:
~- http://mds.mandriva.org/

Revision [389]

Edited on 2008-03-06 11:36:31 by LinusEricsson
Additions:
~- IM-server (jabberd2)
Deletions:
~- IM-server (Jabberd2)

Revision [388]

Edited on 2008-03-06 11:36:13 by LinusEricsson
Additions:
~- IM-server (Jabberd2)

Revision [317]

Edited on 2008-01-29 09:26:07 by LinusEricsson
Additions:
~- [[http://www.ubuntu.com Ubuntu]] as base, use software packages for ubuntu as much as possible.
~- [[http://www.openldap.org OpenLDAP]] as directory service, for storage of account information, computer configuration and network configuration (All configuration in other words...)
Deletions:
~- Ubuntu as base, use software packages for ubuntu as much as possible.
~- OpenLDAP as directory service, for storage of account information, computer configuration and network configuration (All configuration in other words...)

Revision [316]

Edited on 2008-01-29 09:25:25 by LinusEricsson
Additions:
~- [[http://www.isc.org/index.pl?/sw/bind/index.php BIND]] as nameserver. (Alternatives are djbdns) Use together with ldap2dns for automatic generation of zone files from ldap. (OR: http://bind-dlz.sourceforge.net)
Deletions:
~- BIND as nameserver. (Alternatives are djbdns) Use together with ldap2dns for automatic generation of zone files from ldap. (OR: http://bind-dlz.sourceforge.net)

Revision [315]

Edited on 2008-01-29 09:23:03 by LinusEricsson
Additions:
~- [[http://www.postfix.org Postfix]] as MTA
~- [[http://www.openafs.org openAFS]] for file serving...
~- [[http://httpd.apache.org/ Apache]] as http server.
~- [[http://www.courier-mta.org/imap/ Courier IMAP]] for IMAP and POP-service
~- Some sort of PKI, example: [[https://www.openca.org/projects/openca/ OpenCA]]
Deletions:
~- Postfix as MTA
~- openAFS for file serving...
~- Apache as http server.
~- Courier IMAP for IMAP and POP-service
~- Some sort of PKI, example: https://www.openca.org/projects/openca/

Revision [314]

Edited on 2008-01-28 23:10:32 by LinusEricsson
Additions:
~- http://unattended.sourceforge.net/

Revision [313]

Edited on 2008-01-28 23:10:03 by LinusEricsson
Additions:
Other interesting software:
~- http://unattended-gui.sourceforge.net/

Revision [300]

Edited on 2007-12-14 10:29:26 by LinusEricsson
Additions:
~- Windows clients will be installed by first installing using a traditional installation CD, and then installing an application suite to configure it and to connect it to the domain (Please note: Not an Active directory domain, a Halier domain! ) (Windows client may be installed unattended too: http://unattended.sourceforge.net/)
~- Some sort of PKI, example: https://www.openca.org/projects/openca/
Deletions:
~- Windows clients will be installed by first installing using a traditional installation CD, and then installing an application suite to configure it and to connect it to the domain (Please note: Not an Active directory domain, a Halier domain! )

Revision [296]

Edited on 2007-12-09 19:14:58 by LinusEricsson
Additions:
WindowsHserverClient
Deletions:
WindowsHserver

Revision [295]

Edited on 2007-12-09 19:14:45 by LinusEricsson
Additions:
WindowsHserver

Revision [275]

Edited on 2007-11-02 08:50:34 by LinusEricsson
Additions:
~- BIND as nameserver. (Alternatives are djbdns) Use together with ldap2dns for automatic generation of zone files from ldap. (OR: http://bind-dlz.sourceforge.net)
Deletions:
~- BIND as nameserver. (Alternatives are djbdns) Use together with ldap2dns for automatic generation of zone files from ldap.

Revision [265]

Edited on 2007-09-28 11:52:45 by LinusEricsson
Additions:
~- Ubuntu as base, use software packages for ubuntu as much as possible.
~- BIND as nameserver. (Alternatives are djbdns) Use together with ldap2dns for automatic generation of zone files from ldap.
Deletions:
~- BIND as nameserver.

Revision [264]

Edited on 2007-09-19 23:47:15 by LinusEricsson
Additions:
~- Domain-server (includes: DNS-server, DHCP-server, Directory server, TFTP-server)
~- Desktop server (For thin clients)
~- Diskless client server (for diskless but not thin clients)
Deletions:
~- Domain-server (includes: DNS-server, DHCP-server, Directory server)

Revision [263]

Edited on 2007-09-19 23:43:02 by LinusEricsson
Additions:
Feel free to make comments to this document.

Revision [262]

Edited on 2007-09-19 23:41:33 by LinusEricsson
Additions:
This is my dream. I may however probably never make this come true by myself, perhaps if i get some help!
Interested? Send a mail to {{image alt="Linus" title="Linus" url="http://www.halier.net/le.png" }}
Deletions:
There shall be tools availible to make integration of custom software easy

Revision [261]

Edited on 2007-09-19 23:35:56 by LinusEricsson
Additions:
~- Domain-server (includes: DNS-server, DHCP-server, Directory server)
~- Web-server (May include: Webmail, WIKI, Intranet software like eGroupware etc..)
~- Mail-server (Includes: MTA, POP-server, IMAP-server)
~- File-server (includes: AFS-server, Samba server )
Sub-functions like IMAP-server may be installed without installing the entire Mail function.
Deletions:
~- Domain-server
~- Web-server
~- Mail-server
~- File-server

Revision [260]

Edited on 2007-09-19 23:30:58 by LinusEricsson
Additions:
~- When user A loggs in to a computer for the first time, all the company wide software are configured to work with the domain. Like E-mail agents, network file systems mounted etc...
~- Windows clients will have som basic set of software installed to make it work together with the linux servers (Example: AFS client)
Deletions:
~- Windows clients will have som basic set of software installed to make it work together with the linux servers

Revision [259]

Edited on 2007-09-19 23:28:10 by LinusEricsson
Additions:
~- Configure software acording to data in the directory
~- It is possible to achive the same function as you may with Microsofts group policy by writing some simple software.
~- Windows clients will have som basic set of software installed to make it work together with the linux servers

Revision [258]

Edited on 2007-09-19 23:23:28 by LinusEricsson
Additions:
Some sort of software is needed. There must be a daemon responsible for configure the computer acording to the configuration data in the directory.
~- Installing/removing software

Revision [257]

Edited on 2007-09-19 23:21:23 by LinusEricsson
Additions:
== Clients ==
==GNU/Linux clients==
==Windows clients==
~- Software installation may be administred by [[http://www.wpkg.org WPKG]]
Deletions:
== Clients =
=GNU/Linux clients=
=Windows clients=
~- Software installation may be administred by WPKG

Revision [256]

Edited on 2007-09-19 23:15:07 by LinusEricsson
Additions:
~- Domain-server
~- Web-server
~- Mail-server
~- File-server
~- Print-server
~- Backup-server (For performing domain wide backups)
All servers and clients shall have a minimum set of software installed, like ssh-server
== Clients =
=GNU/Linux clients=
=Windows clients=
~- Software installation may be administred by WPKG
=== finaly ===
There shall be tools availible to make integration of custom software easy
Deletions:
~- Domain
~- Web
~- Mail
~-

Revision [255]

Edited on 2007-09-19 23:03:14 by LinusEricsson
Additions:
~- Traditional tools for software administration in GNU/Linux systems. Like apt or yum.
== Example of functions a server might have ==
~- Domain
~- Web
~- Mail
~-

Revision [254]

Edited on 2007-09-19 22:59:03 by LinusEricsson
Additions:
~- Courier IMAP for IMAP and POP-service
All server functions are configured with data from the directory service. If a computer is added to the domain, then BIND and the DHCP-server are updated accordingly.
If an additional DNS server is added to the domain, then all clients will automaticly use this one as well since the DHCP server(s) inform the clients about the new nameserver.
If the same function is provided by more than one server, they will be configured to work together by using load balancing, failover or what is suitable for the function in question.

Revision [253]

Edited on 2007-09-19 22:49:28 by LinusEricsson
Additions:
=== How will it work ===
Deletions:
==== How will it work ===

Revision [252]

Edited on 2007-09-19 22:49:11 by LinusEricsson
Additions:
=== My dream ===
Deletions:
==== My dream ====

Revision [251]

Edited on 2007-09-19 22:48:46 by LinusEricsson
Additions:
~- Using the domain administration software, you will add or remove functions from all servers in your domain, all functions you add or remove are configured to work perfectly together with your domain without any further configuration (utopia?)
~- Using the domain administration software, you will confiigure all clients, including installing and removing software.
==== How will it work ===
The plan is to use existing software as far as possible (don't reinvent the weel).
~- OpenLDAP as directory service, for storage of account information, computer configuration and network configuration (All configuration in other words...)
~- MIT Kerberos 5 for authentification
~- BIND as nameserver.
~- ISC:s DHCP as dhcp server.
~- Postfix as MTA
~- openAFS for file serving...
~- samba for file serving for windows computers. (I would like to only use AFS, but I dont think this is realistic )
~- Apache as http server.
~- Some sort of TFTP-server

Revision [250]

Edited on 2007-09-19 22:31:22 by LinusEricsson
Additions:
~- Windows clients will be installed by first installing using a traditional installation CD, and then installing an application suite to configure it and to connect it to the domain (Please note: Not an Active directory domain, a Halier domain! )
~- Once a domain is created, with at least one domain server, all administration will be performed with the domain administration software

Revision [249]

Edited on 2007-09-19 22:26:49 by LinusEricsson
Additions:
My solution are based on the assumtion that there will be only GNU/Linux servers and no Windows servers, but both GNU/Linux clients and windows clients.
~- When an administrator installs a server he should only be faced some simple questions. Like: New or existing domain
~- When a client computer is installed, there should only be one question: Witch domain do you want to connect to? The client computer will then be under complete control of the domain server
~- If there is a domain server on the local network, it will be possible to install a client computer or a new server directly from the domain server by booting from the network (PXE, TFTP etc.. )
Deletions:
~- When an administrator installs a server he should only be faced some simple questions.
dfdsds

Revision [248]

Edited on 2007-09-19 22:18:05 by LinusEricsson
Additions:
dfdsds

Revision [247]

Edited on 2007-09-19 22:17:21 by LinusEricsson
Additions:
~- When an administrator installs a server he should only be faced some simple questions.

Revision [246]

Edited on 2007-09-19 22:13:16 by LinusEricsson
Additions:
=== Preface ===
GNU/Linux systems on the other hand is very flexible, too flexible. An GNU/Linux administrator will have many descisions to make before he can start installing his server. He will have to choose a distribution, he will have to choose how to store his user data, how to authenticate his users, choose webserver, choose mail transfer agent, choose POP or IMAP-server. There are an huge amount of ways to do things. This is the strength of GNU/Linux (and the whole open source movement ).
I would like a GNU/Linux solution were I don't have to make all descisions. I don't say i would like GNU/Linux to become more like Windows, but I would like a better way to administer several GNU/Linux servers and clients.
==== My dream ====
This is how I would like a computer system to work.
Some of the things here are inspired by the way Active Directory works on windows servers.
Deletions:
GNU/Linux systems on the other hand is very flexible, too flexible. An GNU/Linux administrator will have many descisions to make before he can start installing his server. He will have to choose a distribution, he will have to choose how to store his user data, how to authenticate his users, choose webserver, choose mail transfer agent, choose POP or IMAP-server

Revision [245]

Edited on 2007-09-19 22:01:01 by LinusEricsson
Additions:
If an administrator chooses Windows as his server operating system, he usually don't have to make any more choises. He just adds or removes server roles from his server using Microsofts tool for this. Every role he/she installs works together with his server by default. BUT if he/she wants to do something other than the Microsoft way, he will be on his own...
GNU/Linux systems on the other hand is very flexible, too flexible. An GNU/Linux administrator will have many descisions to make before he can start installing his server. He will have to choose a distribution, he will have to choose how to store his user data, how to authenticate his users, choose webserver, choose mail transfer agent, choose POP or IMAP-server

Revision [244]

Edited on 2007-09-19 21:51:33 by LinusEricsson
Additions:
Most computer users use Windows as their operating system on their computers, but some users choose som variant of GNU/Linux. Users usually don't care about the operating system on the server. Administrators choose operating system on the servers, some administrators prefer Windows, some prefer GNU/Linux
Deletions:
Most computer users use Windows as their operating system on their computers, but some users choose som variant of GNU/Linux. Users usually don't care about the operating system on the server.

Revision [243]

Edited on 2007-09-19 21:22:54 by LinusEricsson
Additions:
Most computer users use Windows as their operating system on their computers, but some users choose som variant of GNU/Linux. Users usually don't care about the operating system on the server.

Revision [242]

The oldest known version of this page was created on 2007-09-19 21:10:58 by LinusEricsson
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki