Plone Instances

From ItsWiki
Jump to: navigation, search

This lists the live, staging and development instances of

running on cydonia/musa and corylus/mimosa.

These replace the early Plone installations on carpinus.ccs.bbk.ac.uk. (as listed at Zope/Plone instances on alnus, betula and buxus)

--Linda 12:03, 5 November 2014 (GMT)


For a current list of VMs and their server locations and usage please refer to OpenVZ_VM_List


Note that while optimsation work is carried out on the Linux webservers the location of the OpenVZ VMs may change from the documented layouts.

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


CHANGE Apr 19th 2011 - number of Zope instances in Plone cms2 live and staging instances has been doubled from 2 to 4, and the number of zserver threads in each cms2 Zope has been reduced from 4 to 2.

Update Jun 17th 2011 - new IP addresses have been allocated and new domain names created for future Plone instances - for full list see http://wiki.bbk.ac.uk/its/Plone_Domains

Contents

LIVE Instances

Live Plone 2.5.3 cms1


Zopes

cms1 Zopes

/var/lib/zope-2.9.11/bbk-zope1/log/event.log
/var/lib/zope-2.9.11/bbk-zope1/etc/zope.conf
webdav port bbk-zope1: 1973
/var/lib/zope-2.9.11/bbk-zope2/log/event.log
/var/lib/zope-2.9.11/bbk-zope2/etc/zope.conf
webdav port bbk-zope2: 1974

cms1 Zope start | stop

    vzctl enter cms1-zope1 (20225)

    /etc/init.d/zope stop
    /etc/init.d/zope start

 or as individual clients


    su - zope -c "/var/lib/zope-2.9.11/bbk-zope1/bin/zopectl stop"
    su - zope -c "/var/lib/zope-2.9.11/bbk-zope2/bin/zopectl stop"

    su - zope -c "/var/lib/zope-2.9.11/bbk-zope1/bin/zopectl start"
    su - zope -c "/var/lib/zope-2.9.11/bbk-zope2/bin/zopectl start"

   
 or from cydonia root:


    /usr/sbin/vzctl exec 20225 su - zope -c "/var/lib/zope-2.9.11/bbk-zope1/bin/zopectl stop"
    /usr/sbin/vzctl exec 20225 su - zope -c "/var/lib/zope-2.9.11/bbk-zope2/bin/zopectl stop"

    /usr/sbin/vzctl exec 20225 su - zope -c "/var/lib/zope-2.9.11/bbk-zope1/bin/zopectl start"
    /usr/sbin/vzctl exec 20225 su - zope -c "/var/lib/zope-2.9.11/bbk-zope2/bin/zopectl start"


cms1 Zopes

/var/lib/zope-2.9.11/bbk-zope3/log/event.log
/var/lib/zope-2.9.11/bbk-zope3/etc/zope.conf
webdav port bbk-zope3: 1973
/var/lib/zope-2.9.11/bbk-zope4/log/event.log
/var/lib/zope-2.9.11/bbk-zope4/etc/zope.conf
webdav port bbk-zope4: 1974

cms1 Zope start | stop

 vzctl enter cms1-zope2  (20226)

 /etc/init.d/zope stop
 /etc/init.d/zope start

 or as individual clients

    su - zope -c "/var/lib/zope-2.9.11/bbk-zope3/bin/zopectl stop"
    su - zope -c "/var/lib/zope-2.9.11/bbk-zope4/bin/zopectl stop"

    su - zope -c "/var/lib/zope-2.9.11/bbk-zope3/bin/zopectl start"
    su - zope -c "/var/lib/zope-2.9.11/bbk-zope4/bin/zopectl start"


   
 or from physical host root:

    /usr/sbin/vzctl exec 20226 su - zope -c "/var/lib/zope-2.9.11/bbk-zope3/bin/zopectl stop"
    /usr/sbin/vzctl exec 20226 su - zope -c "/var/lib/zope-2.9.11/bbk-zope4/bin/zopectl stop"

    /usr/sbin/vzctl exec 20226 su - zope -c "/var/lib/zope-2.9.11/bbk-zope3/bin/zopectl start"
    /usr/sbin/vzctl exec 20226 su - zope -c "/var/lib/zope-2.9.11/bbk-zope4/bin/zopectl start"

ZEO database for cms1 Zopes

/var/lib/zope-2.9.11/bbk-zeo/var/Data.fs
/var/lib/zope-2.9.11/bbk-zeo/log/zeo.log
/var/lib/zope-2.9.11/bbk-zeo/etc/zeo.conf

cms1 ZEO start | stop

    vzctl enter db1 (20231)

    su - zope -c "/var/lib/zope-2.9.11/bbk-zeo/bin/zeoctl stop"

    su - zope -c "/var/lib/zope-2.9.11/bbk-zeo/bin/zeoctl start"

or from physical server root:

    /usr/sbin/vzctl exec 20231 su - zope -c "/var/lib/zope-2.9.11/bbk-zeo/bin/zeoctl stop"

    /usr/sbin/vzctl exec 20231 su - zope -c "/var/lib/zope-2.9.11/bbk-zeo/bin/zeoctl start"

cms1 Apache Sites

updated 2015Nov17

 OLD SITES
  Apache URL                              Zope Folder
 ---------                               -----------
 (www.business.bbk.ac.uk  now redirected to www.bbk.ac.uk/business-services)
 /bill                                   /plone-sites/bill (site disabled (Apache status 410) 2014Jul28)
 /archsoc                                /plone-sites/archsoc (Redundant site redirected to https://www.facebook.com/BirkbeckArchaeologySociety/)
 www.ipa.bbk.ac.uk                       /plone-sites/ipa/ (No longer a Plone site. Now at 193.61.4.225 owned by Department of Psychological Sciences)

 CURRENT SITES
 Apache URL                              Zope Folder
 ---------                               -----------
 
 /jobs                                   /jobs
 /innovation                             /plone-sites/innovation
 /sculptureparks                         /plone-sites/sculptureparks
 /lod                                    /plone-sites/lod
 www.angles.bbk.ac.uk                    /plone-sites/angles
 www.ness.bbk.ac.uk                      /plone-sites/ness
 www.iscfsi.bbk.ac.uk                    /plone-sites/iscfsi
 www.lccge.bbk.ac.uk                     /plone-sites/lccge

Live Plone 3.2.1 cms2

CHANGE Apr 19th 2011 - number of Zope instances has been doubled from 2 to 4, and the number of zserver threads in each Zope has been reduced from 4 to 2.

Zopes

cms2 Zopes

/var/lib/zope-buildouts/cms2/var/client1/event.log
/var/lib/zope-buildouts/cms2/var/client1/Z2.log
/var/lib/zope-buildouts/cms2/parts/client1/etc/zope.conf
/var/lib/zope-buildouts/cms2/var/client2/event.log
/var/lib/zope-buildouts/cms2/var/client2/Z2.log
/var/lib/zope-buildouts/cms2/parts/client2/etc/zope.conf
/var/lib/zope-buildouts/cms2/var/client3/event.log
/var/lib/zope-buildouts/cms2/var/client3/Z2.log
/var/lib/zope-buildouts/cms2/parts/client3/etc/zope.conf
/var/lib/zope-buildouts/cms2/var/client4/event.log
/var/lib/zope-buildouts/cms2/var/client4/Z2.log
/var/lib/zope-buildouts/cms2/parts/client4/etc/zope.conf


cms2 Zope start | stop

 vzctl enter cms2-zope1 (20228)

 /etc/init.d/zope stop
 /etc/init.d/zope start

 or as individual clients

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 stop"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 stop"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 stop"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 stop"

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 start"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 start"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 start"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 start"

   
 or from physical server root:

    /usr/sbin/vzctl exec 20228 "/etc/init.d/zope stop"
    /usr/sbin/vzctl exec 20228 "/etc/init.d/zope start"

 or as individual clients

    /usr/sbin/vzctl exec 20228 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 stop"
    /usr/sbin/vzctl exec 20228 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 stop"
    /usr/sbin/vzctl exec 20228 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 stop"
    /usr/sbin/vzctl exec 20228 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 stop"

    /usr/sbin/vzctl exec 20228 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 start"
    /usr/sbin/vzctl exec 20228 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 start"
    /usr/sbin/vzctl exec 20228 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 start"
    /usr/sbin/vzctl exec 20228 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 start"
   


cms2 Zopes

/var/lib/zope-buildouts/cms2/var/client1/event.log
/var/lib/zope-buildouts/cms2/var/client1/Z2.log
/var/lib/zope-buildouts/cms2/parts/client1/etc/zope.conf
/var/lib/zope-buildouts/cms2/var/client2/event.log
/var/lib/zope-buildouts/cms2/var/client2/Z2.log
/var/lib/zope-buildouts/cms2/parts/client2/etc/zope.conf
/var/lib/zope-buildouts/cms2/var/client3/event.log
/var/lib/zope-buildouts/cms2/var/client3/Z2.log
/var/lib/zope-buildouts/cms2/parts/client3/etc/zope.conf
/var/lib/zope-buildouts/cms2/var/client4/event.log
/var/lib/zope-buildouts/cms2/var/client4/Z2.log
/var/lib/zope-buildouts/cms2/parts/client4/etc/zope.conf

cms2 Zope start | stop

 vzctl enter cms2-zope2 (20229)

 /etc/init.d/zope stop
 /etc/init.d/zope start

 or as individual clients

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 stop"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 stop"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 stop"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 stop"

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 start"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 start"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 start"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 start"
   

   
 or from physical server root:

    /usr/sbin/vzctl exec 20229 "/etc/init.d/zope stop"
    /usr/sbin/vzctl exec 20229 "/etc/init.d/zope start"

 or as individual clients

    /usr/sbin/vzctl exec 20229 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 stop"
    /usr/sbin/vzctl exec 20229 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 stop"
    /usr/sbin/vzctl exec 20229 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 stop"
    /usr/sbin/vzctl exec 20229 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 stop"

    /usr/sbin/vzctl exec 20229 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 start"
    /usr/sbin/vzctl exec 20229 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 start"
    /usr/sbin/vzctl exec 20229 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 start"
    /usr/sbin/vzctl exec 20229 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 start"
   

ZEO database for cms2 Zopes

/var/lib/zope-buildouts/cms2/var/filestorage/Data.fs
/var/lib/zope-buildouts/cms2/var/zeoserver/zeoserver.log
/var/lib/zope-buildouts/cms2/parts/zeoserver/etc/zeo.conf

cms2 ZEO start | stop

Note cannot use /etc/init.d/zope script unless you also want to shutdown cms1 ZEO which runs in same VM.

    vzctl enter db1 (20231)

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver stop"

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver start"

 
or from physical server root:

        /usr/sbin/vzctl exec 20231 su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver stop"

        /usr/sbin/vzctl exec 20231 su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver start"

cms2 Apache Sites

Updated 2016Sep12

 OLD SITES
 Apache URL                              Zope Folder
 ---------                               -----------
  /creative                               /plone-sites/creative
  /european                               /plone-sites/european
  /spanish                                /plone-sites/spanish
  /18                                     /plone-sites/18
  /pbs                                    /plone-sites/pbs   (replaces /po Planning Office)
  /prospective/international              /plone-sites/international (now in main /prospective site)
  /geology                                /plone-sites/geology      (Moved to Plone 3.3.5 on CMS3-zope1&2.  Replaces /es)
  /psychology                             /plone-sites/psychology   (Moved to Plone 3.3.5 on CMS3-zope1&2.  Replaces /psyc)
  /blu                                    /plone-sites/blu  (redirected to /languages 2016Sep12, don't remove plone site yet)
  /mybirkbeck                             /plone-sites/mybbk (redirected to Apex)
  /ref                                    /plone-sites/ref (obsolete, redirected to www.bbk.ac.uk/research)

 CURRENT SITES
 Apache URL                              Zope Folder
 ---------                               ----------- 
  /linkinglondon                          /plone-sites/linkinglondon (LinkingLondon Legacy Plone site)
  /orgpsych                               /plone-sites/orgpsych     (was /manop)


Live Plone 3.3.5 cms3

Listed on separate page because this one is getting too long, see Plone Instances cms3

STAGING Instances

Staging Plone 2.5.3 cms1


This is http://edit.bbk.ac.uk

Zopes

cms1 staging Zope

/var/lib/zope-2.9.11/bbk-zope1/log/event.log
/var/lib/zope-2.9.11/bbk-zope1/etc/zope.conf
/var/lib/zope-2.9.11/bbk-zope2/log/event.log
/var/lib/zope-2.9.11/bbk-zope2/etc/zope.conf


cms1 staging Zope start | stop

    vzctl enter cms1-zope-test (20217)

    /etc/init.d/zope stop
    /etc/init.d/zope start

 or as individual clients

    su - zope -c "/var/lib/zope-2.9.11/bbk-zope1/bin/zopectl stop"
    su - zope -c "/var/lib/zope-2.9.11/bbk-zope2/bin/zopectl stop"

    su - zope -c "/var/lib/zope-2.9.11/bbk-zope1/bin/zopectl start"
    su - zope -c "/var/lib/zope-2.9.11/bbk-zope2/bin/zopectl start"


   
 or from physical server root:

    /usr/sbin/vzctl exec 20217 su - zope -c "/var/lib/zope-2.9.11/bbk-zope1/bin/zopectl stop"
    /usr/sbin/vzctl exec 20217 su - zope -c "/var/lib/zope-2.9.11/bbk-zope2/bin/zopectl stop"

    /usr/sbin/vzctl exec 20217 su - zope -c "/var/lib/zope-2.9.11/bbk-zope1/bin/zopectl start"
    /usr/sbin/vzctl exec 20217 su - zope -c "/var/lib/zope-2.9.11/bbk-zope2/bin/zopectl start"


staging ZEO database for cms1 Zope

/var/lib/zope-2.9.11/bbk-zeo/var/Data.fs
/var/lib/zope-2.9.11/bbk-zeo/log/zeo.log
/var/lib/zope-2.9.11/bbk-zeo/etc/zeo.conf

staging cms1 ZEO musa start | stop

    vzctl enter db-test (20213)

    su - zope -c "/var/lib/zope-2.9.11/bbk-zeo/bin/zeoctl stop"

    su - zope -c "/var/lib/zope-2.9.11/bbk-zeo/bin/zeoctl start"


or from physical server root:

    /usr/sbin/vzctl exec 20213 su - zope -c "/var/lib/zope-2.9.11/bbk-zeo/bin/zeoctl stop"

    /usr/sbin/vzctl exec 20213 su - zope -c "/var/lib/zope-2.9.11/bbk-zeo/bin/zeoctl start"

staging cms1 Apache Sites

 Apache URL                              Zope Folder
 ---------                               -----------
 edit.bbk.ac.uk/                          /main    (bbk home page and top-level pages)


Staging Plone 3 cms2

CHANGE Apr 19th 2011 - number of Zope instances has been doubled from 2 to 4, and the number of zserver threads in each Zope has been reduced from 4 to 2.

This is http://edit.bbk.ac.uk/mybirkbeck

Zopes

cms2 staging Zope

/var/lib/zope-buildouts/cms2/var/client1/event.log
/var/lib/zope-buildouts/cms2/var/client1/Z2.log
/var/lib/zope-buildouts/cms2/parts/client1/etc/zope.conf
/var/lib/zope-buildouts/cms2/var/client2/event.log
/var/lib/zope-buildouts/cms2/var/client2/Z2.log
/var/lib/zope-buildouts/cms2/parts/client2/etc/zope.conf
/var/lib/zope-buildouts/cms2/var/client3/event.log
/var/lib/zope-buildouts/cms2/var/client3/Z2.log
/var/lib/zope-buildouts/cms2/parts/client3/etc/zope.conf
/var/lib/zope-buildouts/cms2/var/client4/event.log
/var/lib/zope-buildouts/cms2/var/client4/Z2.log
/var/lib/zope-buildouts/cms2/parts/client4/etc/zope.conf


cms2 staging Zope start | stop

 vzctl enter cms2-zope-test (20215)

 /etc/init.d/zope stop
 /etc/init.d/zope start

 or as individual clients

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 stop"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 stop"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 stop"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 stop"

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 start"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 start"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 start"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 start"
   

   
 or from physical server root:

    /usr/sbin/vzctl exec 20215 "/etc/init.d/zope stop"
    /usr/sbin/vzctl exec 20215 "/etc/init.d/zope start"

 or as individual clients

    /usr/sbin/vzctl exec 20215 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 stop"
    /usr/sbin/vzctl exec 20215 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 stop"
    /usr/sbin/vzctl exec 20215 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 stop"
    /usr/sbin/vzctl exec 20215 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 stop"

    /usr/sbin/vzctl exec 20215 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 start"
    /usr/sbin/vzctl exec 20215 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 start"
    /usr/sbin/vzctl exec 20215 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 start"
    /usr/sbin/vzctl exec 20215 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 start"
   

staging ZEO database for cms2 Zopes

/var/lib/zope-buildouts/cms2/var/filestorage/Data.fs
/var/lib/zope-buildouts/cms2/var/zeoserver/zeoserver.log
/var/lib/zope-buildouts/cms2/parts/zeoserver/etc/zeo.conf

staging cms2 ZEO start | stop

    vzctl enter db-test (20213)

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver stop"

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver start"

 
or from physical server root:

    /usr/sbin/vzctl exec 20213 su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver stop"

    /usr/sbin/vzctl exec 20213 su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver start"

staging cms2 Apache Sites

 Apache URL                              Zope Folder
 ---------                               -----------
 edit.bbk.ac.uk/mybirkbeck               /plone-sites/mybbk   

Staging Plone 3.3.5 cms3

Listed on separate page because this one is getting too long, see Plone Instances cms3

DEVELOPMENT Instances

beta2 Plone 3 cms2

This is a clone of cms2-zope-test and beta1 is a clone of db-test.

Zopes

beta2 cms2 Zope on ceiba - (goes with beta1 ZEO) This is a cms2-zope-test clone.

beta2 cms2 Zope start | stop

 vzctl enter beta2
 /etc/init.d/zope stop
 /etc/init.d/zope start

or as individual clients

    vzctl enter beta2 (20032)

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 stop"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 stop"

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 start"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 start"
   


or from physical server root:

  
    /usr/sbin/vzctl exec 20032 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 stop"
    /usr/sbin/vzctl exec 20032 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 stop"

    /usr/sbin/vzctl exec 20032 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 start"
    /usr/sbin/vzctl exec 20032 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 start"

Set up behind its own Apache config at /etc/apache2/sites-available/beta2.its.bbk.ac.uk

eggs-directory=/var/lib/zope-buildouts/cms2/buildout-cache/eggs
download-cache=/var/lib/zope-buildouts/cms2/buildout-cache/downloads

beta1 ZEO database for beta2 Zope and cms2-dev1 Zope

beta1 is now a clone of db1

beta1 cms2 ZEO start | stop

    vzctl enter beta1 (20031)

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver stop"

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver start"


or from physical server root:

    /usr/sbin/vzctl exec 20031 su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver stop"
 
    /usr/sbin/vzctl exec 20031 su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver start"

beta2 Apache Sites

 Apache URL                              Zope Folder
 ---------                               -----------
 beta2.its.bbk.ac.uk/mybirkbeck          /plone-sites/mybbk  


cms3-dev1 Plone 3.3.5 cms3

This is a clone of cms3-zope1 and beta5 is a clone of db2. Alan's cms3 scratch instance.


Zopes

cms3-dev1 cms3 Zope (goes with beta5 ZEO) This is a cms3-zope1 clone.

cms3-dev1 cms3 Zope start | stop

 vzctl enter cms3-dev1
 /etc/init.d/zope stop
 /etc/init.d/zope start

or as individual clients

    vzctl enter cms3-dev1 (20194)

    su - zope -c "/var/lib/zope-buildouts/cms3/bin/client1 stop"
    su - zope -c "/var/lib/zope-buildouts/cms3/bin/client2 stop"
    su - zope -c "/var/lib/zope-buildouts/cms3/bin/client3 stop"
    su - zope -c "/var/lib/zope-buildouts/cms3/bin/client4 stop"

    su - zope -c "/var/lib/zope-buildouts/cms3/bin/client1 start"
    su - zope -c "/var/lib/zope-buildouts/cms3/bin/client2 start"
    su - zope -c "/var/lib/zope-buildouts/cms3/bin/client3 start"
    su - zope -c "/var/lib/zope-buildouts/cms3/bin/client4 start"
  


or from physical server root:

 
    /usr/sbin/vzctl exec 20194 su - zope -c "/var/lib/zope-buildouts/cms3/bin/client1 stop"
    /usr/sbin/vzctl exec 20194 su - zope -c "/var/lib/zope-buildouts/cms3/bin/client2 stop"
    /usr/sbin/vzctl exec 20194 su - zope -c "/var/lib/zope-buildouts/cms3/bin/client3 stop"
    /usr/sbin/vzctl exec 20194 su - zope -c "/var/lib/zope-buildouts/cms3/bin/client4 stop"

    /usr/sbin/vzctl exec 20233 su - zope -c "/var/lib/zope-buildouts/cms3/bin/client1 start"
    /usr/sbin/vzctl exec 20233 su - zope -c "/var/lib/zope-buildouts/cms3/bin/client2 start"
    /usr/sbin/vzctl exec 20233 su - zope -c "/var/lib/zope-buildouts/cms3/bin/client3 start"
    /usr/sbin/vzctl exec 20233 su - zope -c "/var/lib/zope-buildouts/cms3/bin/client4 start"
eggs-directory=/var/lib/zope-buildouts/cms3/buildout-cache/eggs
download-cache=/var/lib/zope-buildouts/cms3/buildout-cache/downloads


beta5 ZEO for cms3-dev1 (Plone 3.3.5 cms3)

This is a clone of db2.

beta5 cms3 ZEO start | stop


    vzctl enter beta5 (20035)


      /etc/init.d/zope stop
      /etc/init.d/zope start

      (can use this script because only one ZEO instance is running in this VM)

 OR

    su - zope -c "/var/lib/zope-buildouts/cms3/bin/zeoserver stop"

    su - zope -c "/var/lib/zope-buildouts/cms3/bin/zeoserver start"


 or from physical server root:

    /usr/sbin/vzctl exec 20035 su - zope -c "/var/lib/zope-buildouts/cms3/bin/zeoserver stop"
 
    /usr/sbin/vzctl exec 20035 su - zope -c "/var/lib/zope-buildouts/cms3/bin/zeoserver start"

cms2-dev1 Plone 3.2.1 cms2

This is a clone of cms2-zope1 and beta1 is a clone of db1. Alan's cms2 scratch instance.

Zopes

cms2-dev1 cms2 Zope on ceiba - (goes with beta1 ZEO) This is a cms2-zope1 clone.

cms2-dev1 cms2 Zope ceiba start | stop

 vzctl enter cms2-dev1
 /etc/init.d/zope stop
 /etc/init.d/zope start

or as individual clients

    vzctl enter cms2-dev1 (20233)

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 stop"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 stop"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 stop"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 stop"

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 start"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 start"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 start"
    su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 start"
  


or from physical server root:

 
    /usr/sbin/vzctl exec 20233 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 stop"
    /usr/sbin/vzctl exec 20233 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 stop"
    /usr/sbin/vzctl exec 20233 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 stop"
    /usr/sbin/vzctl exec 20233 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 stop"

    /usr/sbin/vzctl exec 20233 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client1 start"
    /usr/sbin/vzctl exec 20233 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client2 start"
    /usr/sbin/vzctl exec 20233 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client3 start"
    /usr/sbin/vzctl exec 20233 su - zope -c "/var/lib/zope-buildouts/cms2/bin/client4 start"
eggs-directory=/var/lib/zope-buildouts/cms2/buildout-cache/eggs
download-cache=/var/lib/zope-buildouts/cms2/buildout-cache/downloads

beta1 ZEO database for cms2-dev1 Zope (Plone 3.2.1 cms2)


beta1 cms2 ZEO start | stop

    vzctl enter beta1 (20031)

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver stop"

    su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver start"


or from physical server root:

    /usr/sbin/vzctl exec 20031 su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver stop"
 
    /usr/sbin/vzctl exec 20031 su - zope -c "/var/lib/zope-buildouts/cms2/bin/zeoserver start"


Log Archives

@ /data/zope-logs
/data/zope-logs/cms1-zope1/bbk-zope1
/data/zope-logs/cms1-zope1/bbk-zope2
/data/zope-logs/cms2-zope1/client1
/data/zope-logs/cms2-zope1/client2
/data/zope-logs/cms2-zope1/client3
/data/zope-logs/cms2-zope1/client4
@ /data/zope-logs
/data/zope-logs/beta2/client1
/data/zope-logs/beta2/client2
/data/zope-logs/beta4/client1
/data/zope-logs/beta4/client2
/data/zope-logs/beta4/client3
/data/zope-logs/beta4/client4
/data/zope-logs/cms1-zope2/bbk-zope3
/data/zope-logs/cms1-zope2/bbk-zope4
/data/zope-logs/cms2-zope2/client1
/data/zope-logs/cms2-zope2/client2
/data/zope-logs/cms2-zope2/client3
/data/zope-logs/cms2-zope2/client4
/data/zope-logs/cms2-zope-test/client1
/data/zope-logs/cms2-zope-test/client2
/data/zope-logs/cms2-zope-test/client3
/data/zope-logs/cms2-zope-test/client4

OpenVZMA Monitor Application

These are Zope instances installed at physical root level, running on HTTP port 9080


cydonia OpenVZMA start | stop

From cydonia physical root

    /etc/init.d/zope stop
    /etc/init.d/zope start

 or as individual clients

    su - zope -c "/var/lib/zope/ovz-ma/bin/zopectl  stop"

    su - zope -c "/var/lib/zope/ovz-ma/bin/zopectl start"

To check if OpenVZMA is running, from physical root level do:

root@cydonia:/var/lib# ps -ef | grep 'ovz-ma'
root        1669       1  0 Sep26 ?        00:00:22 /usr/bin/python2.4 /usr/lib/zope-2.11.8/lib/python/zdaemon/zdrun.py -S /usr/lib/zope-2.11.8/lib/python/Zope2/Startup/zopeschema.xml -b 10 -s /var/lib/zope/ovz-ma/var/zopectlsock -x 0,2 -z /var/lib/zope/ovz-ma /var/lib/zope/ovz-ma/bin/runzope
zope        1671    1669  0 Sep26 ?        00:00:32 /usr/bin/python2.4 /usr/lib/zope-2.11.8/lib/python/Zope2/Startup/run.py -C /var/lib/zope/ovz-ma/etc/zope.conf

Backups

The latest backup of any Data.fs can be accessed at:

For musa VMs
root@cydonia:/data/vz/IN/<VM Number>/var/lib/<Path to Data.fs>
For cydonia VMs
root@musa:/data/vz/IN/<VM Number>/var/lib/<Path to Data.fs>


See http://wiki.its.bbk.ac.uk (admin: bbk?0709)

See http://wiki.its.bbk.ac.uk/RestoringFromBackups

 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 ccs-systems@bbk.ac.uk.


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