Translations by Alexander Telenga

Now, back on the <emphasis>Front-End</emphasis>, add the nodes to the cluster:

Once the installation is complete, and it may take a while, in a browser go to <emphasis>https://front-end:8443</emphasis> and login to the administration interface using the default username and password of <emphasis>admin</emphasis>. You will then be prompted to change the password, configure an email address for the admin user, and set the storage URL.

For more <application>smbclient</application> options see the man page: <command>man smbclient</command>, also available <ulink url="http://manpages.ubuntu.com/manpages/jaunty/en/man1/smbclient.1.html">online</ulink>.

You can prevent these actions by adding a password to GRUB's configuration file of <filename>/boot/grub/menu.lst</filename>, which will be required to unlock GRUB's more advanced features prior to use.

First introduced as a shell script in Ubuntu 8.04LTS, <application>ubuntu-vm-builder</application> started with little emphasis as a hack to help developers test their new code in a virtual machine without having to restart from scratch each time. As a few Ubuntu administrators started to notice this script, a few of them went on improving it and adapting it for so many use case that Soren Hansen (the author of the script and Ubuntu virtualization specialist, not the golf player) decided to rewrite it from scratch for Intrepid as a python script with a few new design goals:

The mirror address specified here will also be used in the <filename>/etc/apt/source.list</filename> of the newly created guest, so it is usefull to specify here an address that can be resolved by the guest or to plan on reseting this address later on, such as in a <emphasis>--firstboot</emphasis> script.

sudo vmbuilder kvm ubuntu --suite intrepid --flavour virtual --arch i386 \ -o --libvirt qemu:///system --ip 192.168.0.100 --part vmbuilder.partition \ --user user --name user --pass default

There is a default HTTPS configuration file in <filename>/etc/apache2/sites-available/default-ssl</filename>. In order for <application>Apache</application> to provide HTTPS, a <emphasis>certificate</emphasis> and <emphasis>key</emphasis> file are also needed. The default HTTPS configuration will use a certificate and key generated by the <application>ssl-cert</application> package. They are good for testing, but the auto-generated certificate and key should be replaced by a certificate specific to the site or server. For information on generating a key and obtaining a certificate see <xref linkend="certificates-and-security"/>

To configure <application>Apache</application> for HTTPS, enter the following:

When joining an Ubuntu Desktop workstation to a domain, you may need to edit <filename>/etc/nsswitch.conf</filename> if your AD domain uses the <emphasis role="italic">.local</emphasis> syntax. In order to join the domain the <emphasis>"mdns4"</emphasis> entry from the <emphasis>hosts</emphasis> option. For example:

Once part of the domain, install the following packages:

Fortunately, your Ubuntu system may provide all such facilities to Windows clients and share network resources among them. One of the principal pieces of software your Ubuntu system includes for Windows networking is the Samba suite of SMB server applications and tools.

This section of the <phrase>Ubuntu</phrase> Server Guide will introduce some of the common Samba use cases, and how to install and configure the necessary packages. Additional detailed documentation and information on Samba can be found on the <ulink url="http://www.samba.org">Samba website</ulink>.

Samba File Server

One of the most common ways to network Ubuntu and Windows computers is to configure Samba as a File Server. This section covers setting up a <application>Samba</application> server to share files with Windows clients.

The server will be configured to share files with any client on the network without prompting for a password. If your environment requires stricter Access Controls see <xref linkend="samba-fileprint-security"/>

The first step is to install the <application>samba</application> package. From a terminal prompt enter:

That's all there is to it; you are now ready to configure Samba to share files.

The main Samba configuration file is located in <filename>/etc/samba/smb.conf</filename>. The default configuration file has a significant amount of comments in order to document various configuration directives.

Not all the available options are included in the default configuration file. See the <filename>smb.conf</filename><application>man</application> page or the <ulink url="http://samba.org/samba/docs/man/Samba-HOWTO-Collection/">Samba HOWTO Collection</ulink> for more details.

First, edit the following key/value pairs in the <emphasis>[global]</emphasis> section of <filename>/etc/samba/smb.conf</filename>:

workgroup = EXAMPLE ... security = user

The <emphasis>security</emphasis> parameter is farther down in the [global] section, and is commented by default. Also, change <emphasis>EXAMPLE</emphasis> to better match your environment.

Create a new section at the bottom of the file, or uncomment one of the examples, for the directory to be shared:

[share] comment = Ubuntu File Server Share path = /srv/samba/share browsable = yes guest ok = yes read only = no create mask = 0755

<emphasis>comment:</emphasis> a short description of the share. Adjust to fit your needs.

<emphasis>path:</emphasis> the path to the directory to share.

This example uses <filename>/srv/samba/sharename</filename> because, according to the <emphasis>Filesystem Hierarchy Standard (FHS)</emphasis>, <ulink url="http://www.pathname.com/fhs/pub/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM">/srv</ulink> is where site-specific data should be served. Technically Samba shares can be placed anywhere on the filesystem as long as the permissions are correct, but adhering to standards is recommended.

<emphasis>browsable:</emphasis> enables Windows clients to browse the shared directory using <application>Windows Explorer</application>.

<emphasis>guest ok:</emphasis> allows clients to connect to the share without supplying a password.

<emphasis>create mask:</emphasis> determines the permissions new files will have when created.

Now that <application>Samba</application> is configured, the directory needs to be created and the permissions changed. From a terminal enter:

sudo mkdir -p /srv/samba/share

sudo chown nobody.nogroup /srv/samba/share/

The <emphasis>-p</emphasis> switch tells mkdir to create the entire directory tree if it doesn't exist. Change the share name to fit your environment.

Finally, restart the <application>samba</application> services to enable the new configuration:

Once again, the above configuration gives all access to any client on the local network. For a more secure configuration see <xref linkend="samba-fileprint-security"/>.

From a Windows client you should now be able to browse to the Ubuntu file server and see the shared directory. To check that everything is working try creating a directory from Windows.

To create additional shares simply create new <emphasis>[dir]</emphasis> sections in <filename>/etc/samba/smb.conf</filename>, and restart <emphasis>Samba</emphasis>. Just make sure that the directory you want to share actually exists and the permissions are correct.

O'Reilly's <ulink url="http://www.oreilly.com/catalog/9780596007690/">Using Samba</ulink> is another good reference.

Samba Print Server

Another common use of Samba is to configure it to share printers installed, either locally or over the network, on an Ubuntu server. Similar to <xref linkend="samba-fileserver"/> this section will configure Samba to allow any client on the local network to use the installed printers without prompting for a username and password.

For a more secure configuration see <xref linkend="samba-fileprint-security"/>.

Before installing and configuring Samba it is best to already have a working <application>CUPS</application> installation. See <xref linkend="cups"/> for details.

To install the <application>samba</application> package, from a terminal enter:

After installing samba edit <filename>/etc/samba/smb.conf</filename>. Change the <emphasis>workgroup</emphasis> attribute to what is appropriate for your network, and change <emphasis>security</emphasis> to <emphasis role="italic">share</emphasis>:

In the <emphasis>[printers]</emphasis> section change the <emphasis>guest ok</emphasis> option to <emphasis role="italic">yes</emphasis>:

browsable = yes guest ok = yes

Securing a Samba File and Print Server

<emphasis>security = domain:</emphasis> this mode allows the Samba server to appear to Windows clients as a Primary Domain Controller (PDC), Backup Domain Controller (BDC), or a Domain Member Server (DMS). See <xref linkend="samba-dc"/> for further information.