1 = Setup PVE Development Environment =
3 1. Install Debian 'jessie'
4 2. Configure pvetest repository in apt sources.list
6 deb http://download.proxmox.com/debian jessie pvetest
8 3. Add our repository key with apt-key:
10 wget -O- "http://download.proxmox.com/debian/key.asc" | apt-key add -
12 4. make sure you have a read IP address for your hostname in /etc/hosts
13 (using 127.0.1.1 will not work)
15 5. run: apt-get update
16 6. run: apt-get dist-upgrade
17 7. run: apt-get install proxmox-ve-3.10.0
19 You should now have a working Proxmox VE installation.
21 = Install build prerequisites for development environment =
23 apt-get -y install build-essential git-core debhelper autotools-dev \
24 autogen dh-autoreconf dkms doxygen check pkg-config groff quilt dpatch \
25 automake autoconf libtool lintian libdevel-cycle-perl libjson-perl \
26 libcommon-sense-perl liblinux-inotify2-perl libio-stringy-perl \
27 libstring-shellquote-perl dh-systemd rpm2cpio libsqlite3-dev sqlite3 \
28 libglib2.0-dev librrd-dev librrds-perl rrdcached libdigest-hmac-perl \
29 libxml-parser-perl gdb libcrypt-openssl-random-perl \
30 libcrypt-openssl-rsa-perl libnet-ldap-perl libauthen-pam-perl \
31 libjson-xs-perl libterm-readline-gnu-perl oathtool libmime-base32-perl \
32 liboath0 libpci-dev texi2html libsdl1.2-dev libgnutls28-dev \
33 libspice-protocol-dev xfslibs-dev libnuma-dev libaio-dev \
34 pve-libspice-server-dev libusbredirparser-dev glusterfs-common \
35 libusb-1.0-0-dev librbd-dev libpopt-dev iproute bridge-utils numactl \
36 glusterfs-common ceph-common python-ceph libgoogle-perftools4 \
37 libfile-chdir-perl lvm2 glusterfs-client liblockfile-simple-perl \
38 libsystemd-daemon-dev libreadline-gplv2-dev libio-multiplex-perl \
39 libnetfilter-log-dev libipset3 ipset socat libsasl2-dev libogg-dev \
40 python-pyparsing libfilesys-df-perl libcrypt-ssleay-perl \
41 libfile-readbackwards-perl libanyevent-perl libanyevent-http-perl \
42 unzip liblocale-po-perl vlan ifenslave-2.6 libfile-sync-perl cstream \
43 lzop dtach apt-transport-https hdparm gdisk parted ttf-dejavu-core \
44 liblzma-dev dosfstools mtools libxen-dev libfuse-dev libcorosync-pve-dev \
45 libqb-dev libapparmor-dev docbook2x libcap-dev dh-apparmor libcgmanager-dev \
46 graphviz libseccomp-dev libglib-perl libgtk3-perl libnss3-dev libdlm-dev \
49 = Compile PVE packages from Source =
51 Download and install the following git modules in order from top to bottom:
53 # git clone git://git.proxmox.com/git/<PACKAGE.git>
55 You currently need the following packages:
62 pve-access-control.git
71 #resource-agents-pve.git
73 #pve-kernel-3.10.0.git
76 ksm-control-daemon.git
81 Most packages can be installed with 'make dinstall' command.
84 5. Learn to use the quilt patch scripts.
87 There is an experimental package containing the API documentation
92 You can view the source code at:
94 https://git.proxmox.com
99 We decided to change our SOAP API (1.X) and use a REST like API. The
100 concept is described in [1] (Resource Oriented Architecture
101 (ROA)). The main advantage is that we are able to remove a lot of code
102 (the whole SOAP stack) to reduce software complexity.
104 We also moved away from server side content generation. Instead we use
105 the ExtJS Rich Internet Application Framework
106 (http://www.sencha.com).
108 That framework, like any other AJAX toolkit, can talk directly to the
109 REST API using JSON. So we were able to remove the server side
110 template toolkit completely.
112 = JSON and JSON Schema =
114 We use JSON as data format, because it is simple and parse-able by any
117 Additionally, we use JSON Schema [2] to formally describe our API. So
118 we can automatically generate the whole API Documentation, and we can
119 verify all parameters and return values.
121 A great side effect was that we are able to use JSON Schema to
122 produce command line argument parsers automatically. In fact, the REST
123 API and the command line tools use the same code.
125 Object linkage is done using the JSON Hyper Schema (links property).
127 A small utility called 'pvesh' exposes the whole REST API on the command
130 So here is a summary of the advantage:
132 - easy, human readable data format (native web browser format)
133 - automatic parameter verification (we can also verify return values)
134 - automatic generation of API documentation
135 - easy way to create command line tools (using same API).
137 = API Implementation (PVE::RESTHandler) =
139 All classes exposing methods on the API use PVE::RESTHandler as base class.
141 use base qw(PVE::RESTHandler);
143 To expose methods, one needs to call register_method():
145 __PACKAGE__->register_method ($schema);
147 Where $schema is a PVE method schema as described in
148 PVE::JSONSchema. It includes a description of parameters and return
149 values, and a reference to the actual code
151 __PACKAGE__->register_method ({
155 description => "simple return value of parameter 'text'",
157 additionalProperties => 0,
168 my ($conn, $resp, $param) = @_;
170 return $param->{text};
174 The 'name' property is only used if you want to call the method
175 directly from Perl. You can do that using:
177 print __PACKAGE__->echo({ text => "a test" });
179 We use Perl's AUTOLOAD feature to implement this. Note: You need to
180 pass parameters a HASH reference.
182 There is a special helper method called cli_handler(). This is used by
183 the CLIHandler Class for command line tools, where you want to pass
184 arguments as array of strings. This uses Getopt::Long to parse parameters.
186 There is a second way to map names to methods - using the 'path'
187 property. And you can register subclasses. That way you can set up a
188 filesystem like hierarchy to access methods.
191 ----------------------------
194 __PACKAGE__->register_method ({
200 __PACKAGE__->register_method ({
209 __PACKAGE__->register_method ({
215 -------------------------------
217 The utily method find_handler (in PVE::RESTHandler) can be use to do
218 'path' related method lookups.
220 C1->find_handler('GET', "/index") => C1::list1
221 C1->find_handler('GET', "/sub2/index") => C2::list2
223 The HTTP server use the URL (a path) to find the corresponding method.
228 [1] RESTful Web Services
229 Web services for the real world
232 Leonard Richardson, Sam Ruby
238 [2] JSON Schema links: http://json-schema.org/