Plone Instances responsive

From ItsWiki
Jump to: navigation, search

Back to Plone Instances (on cydonia/musa/corylus/mimosa)

Note that while optimsation work is carried out on the Linux webservers the location of the OpenVZ VMs may change. To see what VMs are currently mounted on a server run the following command from the server physical root (cydonia, corylus, musa or mimosa):

vzlist -a

LIVE Instances - Plone 4.3.6 responsive corporate


The Birkbeck homepage and top-level corporate site, responsive template with Diazo, created by Netsight.


Pre go-live Apache URL:

live cms5 Apache Sites

Apache configuration for live Plone 4.3.6 sites is in file on web1 VM. For testing with URLs can use in the web-test VM

 Apache URL                  Zope Folder
 ---------                   -----------
 /  (       /main
 /bisr                    /plone-sites/bisr
 /cilavs                  /cilavs 
 /lib                     /plone-sites/lib
 /prospective             /plone-sites/prospective

STAGING Instances - Plone 4.3.6 responsive corporate



   Debian 7.0 Wheezy, Standalone Zope and local Apaches in c1-zope1-test and c1-zope2-test.
   Separate Zeo in c1-db-test.
   Debian 8.0 Jessie with Varnish 4.1 and Haproxy 5.8, hatop installed.

DEVELOPMENT/MIGRATION Instances - Plone 4.3.6 responsive corporate

beta4 forms part of a migration environment for importing sites from Plone 3.3.5 into Plone 4.3.6. Products and buildout config on beta4 should be kept in step with cms5-zope-test and cms5-zope1.


Debian 7.0 Wheezy     Migration environment for Plone 4.3.6 (Netsight Corporate/Prospective Responsive theme)
- cloned from cms5-zope-test (local Zeo, shared-blob ON, 2 zope clients, Plone 4.3.6)

Regarding shared-blob setting...see

    The location of the blob zeocache, defaults to var/blobcache. If shared-blob is on it defaults to ${buildout:directory}/var/blobstorage.
    Defaults to off. Set this to on if the ZEO server and the instance have access to the same directory. Either by being on the same physical
machine or by virtue of a network file system like NFS. Make sure this instances blob-storage is set to the same 
directory used for the ZEO servers blob-storage. In this case the instance will not stream the blob file through the
 ZEO connection, but just send the information of the file location to the ZEO server, resulting in faster 
execution and less memory overhead.


Currently on mimosa and in use by Marija for bbk.sharedcorporate version 3.x collective.cover tiles development Barbara 18:13, 3 February 2017 (GMT) (2 x Zope clients) (Zeo)

Debian 7.0 Wheezy Development and testing environment for Plone 4.3.6 

USER TESTING Instances - Plone 4.3.6 responsive corporate

Used by Naomi for user testing the new Corporate site.

cd2    Zope    Zeo

Debian 7.0 Wheezy     (Corporate Responsive theme)
- 2 zope clients, Plone 4.3.6, local Apache in cd2, Standalone Zope in cd2, Zeo in cd3)


See (admin: bbk?0709)


 Onsite Backup Diagram

Corylus <* * *> Mimosa
   ^              ^
   *              *
      *        *
         *  *
         *  *
      *        *
   *              *
   v              v
Cydonia  <* * *> Musa

Onsite Backup Configuration

As per config files in /etc/backup.d on each machine, four days of backups are kept. The purpose is mostly for restoring latest backup (up to 24 hours old), to replace a failed VM or a whole failed PH quickly. Each PH is backed up twice and each holds backups of two other PHs, details in the diagram above. the backup runs are staggered at 0:20, 1:20, 2:20 and 3:20, respectively, and upon completion of backups (successful or otherwise), an email is sent to

To locate VM backups go to /data/vz/IN/ at physical server root.

Example for cydonia VMs

To retrieve the Data.fs backup for db4 (20114) VM, go to root@musa:/data/vz/IN/20114/var/lib/zope-buildouts/cms4/var/filestorage

Also see