Черновки

Построение на базе branch 4.0 + server4.0.1 + некоторые пакеты из сизифа
пакеты
apache2-mod_nss-1.0-alt1.20070710.i586.rpm apache2-mod_revocator-1.0-alt1.20070710.i586.rpm fedora-ds-adminserver_1.1.0-alt0.20070731_i586.rpm fedora-ds-adminutil_1.1.2-alt1.20070730_i586.rpm fedora-ds-admservconsole_1.1.0-alt0.20070731_noarch.rpm fedora-ds-console-framework_1.1.0-alt0.20070731_noarch.rpm fedora-ds-console_1.1.0-alt0.20070731_noarch.rpm fedora-ds-directoryconsole_1.1.0-alt0.20070731_noarch.rpm fedora-ds-setuputil_1.1.0-alt0.20070730_i586.rpm fedora-ds_1.1.0-alt0.20070730_i586.rpm gosa-apache2_2.5.12-alt1_noarch.rpm gosa-common_2.5.12-alt1_noarch.rpm gosa-php5_2.5.12-alt1_noarch.rpm gosa-schema_2.5.12-alt1_noarch.rpm gosa_2.5.12-alt1_noarch.rpm jss_4.2.4-alt0_i586.rpm ldapsdk-4.17-alt1_3jpp1.7.noarch.rpm perl-Mozilla-LDAP_1.5-alt3_i586.rpm

Создаем локальный репозитарий
mkdir -p localRepo/{RPMS.fds,base} ls -l localRepo итого 8 drwxr-xr-x 2 sysus sysus 4096 Авг 10 22:59 base drwxr-xr-x 2 sysus sysus 4096 Авг 10 22:59 RPMS.fds cp пакеты localRepo/RPMS.fds

Генерируем репозитарий
genbasedir --topdir=. localRepo fds Components: fds Processing pkglists... fds done Processing srclists... done Creating component releases... fds done Creating global release file... done Appending MD5Sum... fds done Creating legacy hashfile... fds done All your base are belong to us!!!

правим /etc/apt/sources.lists
cat /etc/apt/sources.list # Local package resource list for APT goes here. # To inspect package defined part, see /etc/apt/sources.list.d/*.list rpm file:/usr/repo/branch4.0 i586 classic rpm file:/usr/repo/branch4.0 noarch classic rpm file:/home/sysus/fds repo fds

Можно со спокойной душой создавать c помощью утилиты spt ovz-template для будущей системы.

В базовую систему ставим hasher, hasher-priv, spt, spt-profiles-ovz
cp /etc/spt/profiles/ovz/.defaul ~/ovz

Правим ~/ovz/profile/ovz/packages
apt etcnet glibc sysklogd vim-console apt-rsync fedora-ds fedora-ds-adminserver fedora-ds-adminutil fedora-ds-setuputil openssh-clients openssh-server su perl-libnet fedora-ds-admservconsole fedora-ds-directoryconsole

Правим ~/ovz/profile/ovz/config
OUT=altlinux-4.0 IDENT=ovz

Генерируем template
spt -v --image-type=tgz ~/ovz [skip] spt: Run hooks for: ovz spt: 02root done spt: 03services done spt: 04inittab done spt: 05mtab done spt: 06syslog done spt: Creating archive image for `ovz'. spt: Chroot image arhivation complete. spt: Creating image for `ovz'. [sysus@localhost ~]$ ls ovz/ altlinux-4.0.tar.gz profile [sysus@localhost ~]$

Переносим template в cache openvz
cp /home/sysus/ovz/altlinux-4.0.tar.gz /var/lib/vz/template/cache/

Создаем vz-контейнер
vzctl create 101 --ostemplate altlinux-4.0 --config ovz

Настраиваем параметры контейнера
vzctl set 101 --onboot yes --name s40 --hostname s40.mydomain.ru --ipadd 192.168.100.2 --save Name s40 assigned Saved parameters for VE 101

Статус vz сервиса
[root@localhost ~]# service vz status OpenVZ is running.

Запускаем контейнер
[root@localhost ~]# vzctl start 101 Starting VE ... VE is mounted Adding IP address(es): 192.168.100.2 Setting CPU units: 33500 Configure meminfo: 67623 Set hostname: s40.mydomain.ru VE start in progress...

Заходим в него
[root@localhost ~]# vzctl enter 101 entered into VE 101 -bash-3.1# id uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),19(proc) -bash-3.1# /sbin/ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) venet0:1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:192.168.100.2 P-t-P:192.168.100.2 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 -bash-3.1# hostname s40.mydomain.ru

Настройка fds (настройка fds-admin-server — это ldap-instance для хранения конфигов всех существующих instance'в) и запуск instance'а для обслуживания вашей организации (ну собственно основной ldap-сервер, где будет храниться вся информация)

Передустановкой стоит увеличить следующие параметры (я увеличиваю на порядок)
vzquota show 101 vzquota : (warning) Quota is running, so data reported from quota file may not reflect current values resource usage softlimit hardlimit grace 1k-blocks 203536 218593 240453 inodes 11605 213018 234320 [root@localhost ~]# vzquota setlimit 101 -b 2185930 -B 2404530 [root@localhost ~]# vzquota show 101 vzquota : (warning) Quota is running, so data reported from quota file may not reflect current values resource usage softlimit hardlimit grace 1k-blocks 203536 2185930 2404530 inodes 11605 213018 234320

[root@localhost ~]# сat /proc/user_beancounters [skip] privvmpages 755 7737 67623 74385 0 [skip] [root@localhost ~]# vzctl set 101 --privvmpages 676230:743850 --save UB limits were set successefully Configure meminfo: 676230 Saved parameters for VE 101

/usr/sbin/setup-ds-admin.pl ============================================================================== This program will setup the Fedora Directory and Administration Servers. [skip] Would you like to continue with setup? [yes]: ============================================================================== Choose a setup type: [skip] Choose a setup type [2]: ============================================================================== Enter the fully qualified domain name of the computer [skip] Computer name [s40.mydomain.ru.mydomain.ru]: s40.mydomain.ru ============================================================================== The servers must run as a specific user in a specific group. [skip] System User [nobody]: ldap System Group [nobody]: ldap ============================================================================== Server information is stored in the configuration directory server. [skip] Do you want to register this software with an existing configuration directory server? [no]: ============================================================================== Please enter the administrator ID for the configuration directory [skip] Configuration directory server administrator ID [admin]: Password: Password (confirm): ============================================================================== The information stored in the configuration directory server can be [skip] Administration Domain [mydomain.ru]: ============================================================================== The standard directory server network port number is 389. However, if [skip] Directory server network port [389]: ============================================================================== Each instance of a directory server requires a unique identifier. [skip] Directory server identifier [s40]: ============================================================================== The suffix is the root of your directory tree. The suffix must be a valid DN. [skip] Suffix [dc=mydomain, dc=ru]: ============================================================================== Certain directory server operations require an administrative user. [skip] Directory Manager DN [cn=Directory Manager]: Password: Password (confirm): ============================================================================== The Administration Server is separate from any of your web or application [skip] Administration port [9830]: ============================================================================== The interactive phase is complete. The script will now set up your [skip] Are you ready to set up your servers? [yes]: Creating directory server . . . Your new DS instance 's40' was successfully created. Creating the configuration directory server . . . Beginning Admin Server creation . . . Creating Admin Server files and directories . . . Updating adm.conf . . . Updating admpw . . . Registering admin server with the configuration directory server . . . Updating adm.conf with information from configuration directory server . . . Updating the configuration for the httpd engine . . . Starting admin server . . . The admin server was successfully started. Admin server was successfully created, configured, and started. Exiting . . . Log file is '/root/tmp/setuphNce2d.log'

Типа работает
netstat -an|egrep "(389|9830)" tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:9830 0.0.0.0:* LISTEN

Дальнейшая работа происходит с помощью консоли управления сервером /usr/bin/fedora-idm-console. При запуске вас спросят имя пользователя (admin), пароль (пароль admin'а), url (ip-адрес_сервера:9830).

На машине, с которой запущен fedora-ibm-console, и на сервере в /etc/hosts (или же в dns), должны быть соответствующие записи, сервер пускает только с машин *.mydomain.ru. Иначе, будет предлагать перезапустить instance.