FGCP PHP+PostgreSQL Web Platform Template

Transcription

1 FGCP PHP+PostgreSQL Web Platform Template An introductory guide to deploying the FGCP PHP+PostgreSQL(TypeA) Web Platform Template The FGCP Platform as a Service library now includes several new Web Platform Templates. Each template consists of an Operating System, on top of which is installed a Web server, Application base (server) and Database elements. CentOS bit is used for the underlying Operating System, with the customer having the option of either PHP or Tomcat for the Application base (server) and PostgreSQL or MySQL as the Database server. A customer is therefore able to select the Web Template of choice to meet their individual needs, skill level and preference. Each template comes as a single VM, and contains all necessary software required for the web application and is available from within the FGCP portal and is deployable just like any other template image. View of Web Platform Templates within the portal: Type A Web Template - PHP+PostgreSQL This guide provides a brief introduction to deploying a Type A: PHP+PostgreSQL template, but does not include any specific configuration details. It is assumed that the deployer of these templates has sufficient skills and knowledge to configure a Web Application using the underlying Web Platform Applications. This template includes an Apache Web Server, PHP Application layer and PostgreSQL database. Depending on the requirements for your environment, a single Web Template can be deployed in the DMZ network to host both roles. Alternatively the roles can be shared out across two VMs and network segments as shown in the table below: Number Server Type CPU *1 Memory(GB) *1 Disk(GB) *1 of VMs 2 1. Web Server 1x IA 1.0GHz Database Server 1x IA 1.0GHz Web & Database Server 1x IA 1.0GHz *1 The resource values shown are for the economy VM type. Higher performance figures can be obtained by selecting a VM of a higher specification. Date: 24/04/2013 Page 1 of 5

2 An recommended example 2-tier architecture using 3VMs is shown in the below diagram: Here, the administrator accesses and configures each VM/Role using a SSH client such as Putty via the portal. When complete, an end user then accesses the Web Server which is located in the DMZ network using their Browser. Calls to and from the PHP application happen internally on the Web Server, with calls to the PostgreSQL Server via the FGCP firewall. Within a FGCP VSYS, this looks like: Date: 24/04/2013 Page 2 of 5

3 Firewall Ports The following table shows the ports used for communication between each server/vm. This may require the FGCP firewall to be configured to allow port access, depending on the number and location of each VM: Network Ports used Need to allow access on firewall Remarks TCP 80 Necessary(Internet, intranet, etc.) http TCP 5432 Necessary(From APP server to DB server) postgresql e.g. For the above 2-tier architecture Software Components The template is preinstalled with the following Software Components : Type component Package name version OSSlicense Web Apache httpd.x86_ el6.centos.1 ASL 2.0 HTTPServer Programming language PHP php.x86_64 php-devel.x86_64 php-pdo.x86_64 php-pgsql.x86_64 php-mbstring.x86_ el6_3 PHP DBMS PostgreSQL postgresql-libs.x86_64 postgresql.x86_64 postgresql-server.x86_64 postgresql-contrib.x86_64 postgresql-devel.x86_64 postgresql-plperl.x86_64 postgresql-plpython.x86_64 postgresql-pltcl.x86_ el6_3 PostgreSQL Notes: Files included in a package can be displayed by "rpm -ql<package name>" command. Date: 24/04/2013 Page 3 of 5

4 Host File Setup By default, each VM comes with a generic name. It is recommended to rename each VM based on its role, whilst also meeting any required naming standards. 1. To rename the VM, use a text editior of your choice and edit the file /etc/sysconfig/network e.g. vim /etc/sysconfig/network. 2. Next, the host file on each VM should be updated to reflect the IP address and HOST name of all other Web Platform VMs. To do this, edit the file /etc/hosts/ and add an uncommented line entry for each VM in your deployment. e.g x.x wb01-typec x.x x.x ap01-typec db01-typec 3. Finally enter the command reboot, to reboot the VM and pick up the new changes. Linux User IDs The following User IDs have been created and are included as part of the template Linux user Password Remarks root Initial password as displayed within the portal Used for root admin access to the virtual machine. apache NA Used to start and stop Apache HTTP Server (Service account) postgres NA Used to start and stop Postgres and for database operations (Service account) Predefined Partition Settings The template is configured with the following predefined partitions. Further partitions can be included if required. Mountpoint Purpose of use Size GB xvda1 /boot Boot directory 0.1 xvda2 / Boot directory 9.9 Commands to Start Web Platform Services Manual Service start-up commands and start-up script locations (as root / administrator): Service Manual Service Start-up Command Start-up script location/start-up command apache service httpd start /etc/rc.d/init.d/httpd start tomcat service tomcat6 start /etc/rc.d/init.d/tomcat6 start postgresql service postgresql start /etc/rc.d/init.d/postgresql start MySQL service mysqld start /etc/rc.d/init.d/mysqld start Services start-up with their associated Linux user id processes see Linux User IDs section. N.B. The start-up scripts can be linked-to as S<nn><scriptname> from within an /etc/rc.d/rc<n>.d directory to autorun the script on VM start-up on booting to run-level <N> [typically 3, 4 or 5, within /etc/rc.d/init.d/rc3.d, rc4.d, rc5.d respectively] and as K<nn><scriptname> on shutdown in /etc/rc.d/rc0.d. Where <nn> is a 2-digit execution sequence number within the start-up script directory. Date: 24/04/2013 Page 4 of 5

5 e.g. to have the Apache (httpd) service start automatically on boot through run-level 5, create a start-up script link to the httpd start-up script in the rc5.d start-up directory, e.g. as S98httpd : ln s /etc/rc.d/init.d/httpd /etc/rc.d/rc5.d/s98httpd Create the associated shutdown script in rc0.d as K15httpd. Note: this is already present in the Web platform template image: ln s /etc/rc.d/init.d/httpd /etc/rc.d/rc0.d/k15httpd Contact Fujitsu Global Cloud Team FUJITSU GlobalCloud@uk.fujitsu.com Website: uk.fujitsu.com All rights reserved, including intellectual property rights. Technical data subject to modifications and delivery subject to availability. Any liability that the data and illustrations are complete, actual or correct is excluded. Designations may be trademarks and/ or copyrights of the respective manufacturer, the use of which by third parties for their own purposes may infringe the rights of such owner. Copyright Fujitsu Services Limited 2013 Date: 24/04/2013 Page 5 of 5