-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathREADME
90 lines (60 loc) · 1.91 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
Slurm PHP extension
===================
Requirements (tested with)
* SLURM 2.2.0
* PHP 5.1.6
* APACHE (optional, but recommended)
This was made primarily for SLURMWEB to connect to slurm. Any extra
interactions are welcome.
to compile...
phpize
./configure
make
this should make modules/slurm_php.so
make install as root
should install this where your extensions are in your php install
in your php.ini file add the line
extension=slurm_php.so
and you should be able to use the functions here.
Example PHP site
================
The examples directory contains a sample site which tries to show case
as much of the php functionality as possible.
Documentation
=============
The documentation can be created using PHPDocumentor 1.4.3, should you ever feel
the need to regenerate the documentation, use the following command
~~~~
phpdoc -o HTML:frames:phpedit -d examples -po c,includes,objects -t docs \
-ti "php-slurm 1.0"
~~~~
Administrator Notes
===================
To build an installable RPM from the tarball
~~~~
rpmbuild -ta php-slurm-1.0.tar.gz
~~~~
The above assumes that the appropriate compiler and rpm-build packages
are installed on your system.
TEST CASES
==========
It is assumed that the user has both slurmctld and slurmd is
configured up with at least 1 partition and 1 node for these tests to
pass.
Developer Notes
===============
The 'develop' branch should be used for development work and the 'master'
branch should always be a stable branch to make life easier for people
who want to roll out the package.
To clean up the directory to a clean state do the following
~~~~
phpize --clean
~~~~
The coding style that should be adopted is
http://www.kernel.org/doc/Documentation/CodingStyle
Doing a release
===============
* Finalise changes
* Run bump-version script to make some version number changes to various files
* Tag repository
* then run release-stable.sh to generate a tarball for redistribution