NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Software > SoftwareDocs > DssDocs

Changes | Index | Contents | Search | Statistics | Go

Dynamic Scheduling System Documentation

• Project
• Design
• Development Environment
  • Getting Started
• Deployment
  • How to start the test server on Colossus?
  • How to stop the test server on Colossus?
  • Patching the Release
• Modification Requests
• Archived Documents
• HowTos

Project

Design

• Database:
  
• TurboGears Controllers
  

• The efficiency class design (python) is based off DSS Project Note 5.

• The scoring class design (python) uses the efficiency classes to generate scores for ranking sessions.

• The schedule class design (javascript) handles users' interactions with the bin, calendar, and scratchpad for both manual and automatic scheduling.

• The Antioch Weather design is as follows:

Development Environment

• We are leveraging a rapid web development framework, TurboGears, for the DSS.
• nell tree:
• config files
• UnitTestingWithNose

Getting Started

• get darcs in your path: export PATH="/home/gbt1/bin:"$PATH
• source the python installation: source /home/gbt7/galahad/McPython.bash
• grab the nell source module for nell from somebody: darcs get /home/sandboxes/mmccarty/nell
• cd nell
• chmod 755 create_test_db
• ./create_test_db
• cd ..
• grab the antioch source module and place it at the same level as nell: darcs get /home/sandboxes/mmccarty/antioch
• cd antioch
• read the INSTALL file, and follow instructions; you'll need to change the install dir to point to your new nell
• python setup.py install --install-purelib=/home/sandboxes/me/myNewNell/nell
• run the nell unit tests: cd ../nell/nell; nosetests -w tests
• create the server database: tg-admin sql create; tg-admin shell InitDBTables?.py
• start the server: tg-admin shell start-nell.py

Deployment

How to start the test server on Colossus?

• Log on to colossus as monctrl:

ssh -l monctrl colossus

• source /home/gbt7/galahad/McPython.bash
• cd to the top of test source tree, /home/dss, and into the test version that you wish to run. For example, 0.2/nell/nell.
• Make sure the source is updated with darcs to the version of the code that you want to run.
• If you are checking out a new pre-release
  • Edit the def.cfg to point to the "nell" devdata.sqlite database and set server.socket_port = 8087
• run nohup python start-nell.py &
• Test with a browser: point to http://colossus:8087.
• log out of colossus

How to stop the test server on Colossus?

• Log onto colossus as monctrl:

ssh -l monctrl colossus

• Get the pid for the python process running the test server.

ps axf | grep start-nell.py

• Kill the process. ps should have displayed three PIDs:

[monctrl@colossus ~]$ps axf | grep start-bos.py
14821 pts/1    S+     0:00              \_ grep start-nell.py
13752 ?        S      0:07 python start-nell.py
13756 ?        Sl     1:24  \_ /home/gbt7/galahad/bin/python start-nell.py

Ignore the grep PID. Kill (with default signal) the PID for the second python (the one with the full path specifier). The other will go as well. In this case:

kill 13756

Patching the Release

1. put out warning in two layout.html files of when patch is happening (hours in advance)
2. Make sure from the team that pulling all patches from integration is okay.
3. Make backup of the 'dss' database
4. stop the server: as yourself on host 'trent': sudo /etc/init.d/dss stop
5. as dss for this and all other installations steps, pull from integration into /home/dss/release/antioch
6. install there into antioch
7. make sure unit tests pass in antioch
8. install this antioch into /home/dss/release/nell
9. pull from integration into /home/dss/release/nell
10. recreate the test DB (may need to make nell/create_test_db an executable)
11. make sure that /home/dss/release/nell has symbolic link of test.cfg -> ../../test.cfg
12. run the nell unit tests, make sure they pass
13. make any desired changes to the production database
14. restart the server: sudo /etc/init.d/dss start
15. make sure all is well
16. oh yeah, remove those warnings from step 1.

Modification Requests

• ModificationRequest4C707
• ModificationRequest4C807

Archived Documents

HowTos

• Software/BuildingDssPython
• HowToSimulate

Attachment:	Action:	Size:	Date:	Who:	Comment:
weather.jpg	action	66130	05 Aug 2008 - 01:10	PaulMarganian