Cloudfoundry V2 offline installation (pseudo offline installation)

Installing Cloudfoundry has been using online installation for a long time, cloudfoundry a bunch of code to download, and to consider using cloudfoundry files that have already been installed, saving a single deployment time.

Get Cloudfoundry installation files

Server 10.106.1.51 (Ubuntu 10.04 LTS) has been installed online cloudfoundry to obtain two directory files cfvcap.tar.gz and home.tar.gz

tar-zcvf/home/backup/cfvcap.tar.gz/var/vcap/

tar-zcvf/home/backup/home.tar.gz/home/ubuntu/

Installing with installation files

Use the server 10.106.1.42 (Ubuntu 10.04 LTS-bits) as the target server. Copy cfvcap.tar.gz and home.tar.gz to the server, unzip to the corresponding directory/var/vcap and/home/ubuntu

(If no Ubuntu users need to first create Ubuntu users and add Ubuntu to/etc/sudoers)

1. Change Ubuntu to 163 source

2, installation software:

Apt-get Install build-essential libssl-dev lsof strace bind9-host dnsutils Curl wget libcurl3 libcurl3-dev libxml2 libxml2 -dev zip unzip Nfs-common Flex Psmisc apparmor-utils iptables sysstat rsync openssh-server traceroute Libncurses5-dev A tcpdump iputils-arping bison libreadline6-dev libxslt1.1 libxslt1-dev linux-image-virtual-lts-backport-oneiric Linux-headers-virtual-lts-backport-oneiric git-daemon-run libcap2-bin libxslt1-dev libmysqlclient16-dev git-core gdb GetText Libcroco3

3, download monit-5.2.4 put to/tmp directory

Download Address: http://mmonit.com/monit/dist/monit-5.2.4.tar.gz

Modify the Nise-bosh file/home/ubuntu/cf_nise_installer/nise_bosh/bin/init comment out the 65th line of the file. The reason for using this procedure is that the download monit-5.2.4 is very slow, so it takes offline downloading.

4, use the Ubuntu user login system, into the directory/home/ubuntu/cf_nise_installer/execution sudo./local/install.sh

More Wonderful content: http://www.bianceng.cnhttp://www.bianceng.cn/Servers/cloud-computing/

Wait for an estimated 10 minutes, install successfully, reboot the system.

5, Configuration Modification 1

1)/var/vcap/data/jobs/cloud_controller_ng/19/config/cloud_controller.yml

2)/var/vcap/data/jobs/cloud_controller_ng/19/config/syslog_forwarder.conf

3)/var/vcap/data/jobs/dea_next/21/config/dea.yml

4)/var/vcap/data/jobs/dea_next/21/config/syslog_forwarder.conf

5)/var/vcap/data/jobs/gorouter/8/config/gorouter.yml

6)/var/vcap/data/jobs/gorouter/8/config/syslog_forwarder.conf

7)/var/vcap/data/jobs/health_manager_next/13/config/health_manager.yml

8)/var/vcap/data/jobs/health_manager_next/13/config/syslog_forwarder.conf

9)/var/vcap/data/jobs/nats/13/config/nats.yml

/var/vcap/data/jobs/nats/13/config/syslog_forwarder.conf)

One)/var/vcap/data/jobs/uaa/33/config/uaa.yml

)/var/vcap/data/jobs/uaa/33/config/syslog_forwarder.conf

/VAR/VCAP/DATA/JOBS/UAA/33/CONFIG/BATCH.YML)

)/var/vcap/data/jobs/uaa/33/config/cf-registrar/config.yml

IP and domain name substitution for the above files

6, Configuration Modification 2

To modify the time zone configuration for container in warden:

Modify file/var/vcap/data/packages/rootfs_lucid64/2/etc/timezone to stay in line with host/etc/timezone

7, Upgrade Gorouter:

The Cloudfoundry version currently in use is cf145, and Gorouter has been found to be problematic and needs to be upgraded for the Gorouter version. Gorouter final execution file is binary file, upgrade is simpler

Replace older versions of the Gorouter directory/var/vcap/data/jobs/gorouter/8 and/var/vcap/data/packages/gorouter/16 with files in the new version of the directory

(Gorouter version changes, the name of the second-level file changed, you need to modify the/var/vcap/data/jobs/gorouter/8/bin/gorouter_ctl and/var/vcap/data/packages/ Gorouter/16/bin/gorouter file)

After modifying the gorouter, it may cause monit to be unable to monitor the Gorouter state, this time need to modify the/VAR/VCAP/MONIT/JOB/0001_MICRO_NG.GOROUTER.MONITRC need to re-establish the soft connection

Problems

1, warden, the DEA can not start, view Log Discovery/var/vcap/data/packages/warden/33/warden/root/linux/setup.sh script in the shutdown/etc/init.d/apparmor Teardown error, this server apparmor does not support teardown command, so speak teardown modify to stop command, run OK

2, Postgres s database has been unable to start, using the Vcap user to execute the start database command:

/var/vcap/data/packages/postgres/5/bin/postgres-d/var/vcap/store/postgres-h 0.0.0.0-p 5524

The discovery is cloudfoundry the system uses the English environment by default, therefore speaks the Ubuntu system to switch into the English environment to be OK.

3, the middle also appears gorouter, UAA cannot start the reason, discovers the system 80 ports and 8080 ports are occupied causes, will occupy the port the program to kill, everything is normal.