179
179
$ make sampledata
181
Install the provisioning server::
183
$ sudo apt-get install maas-provision
185
181
By default, the snippet ``maas_proxy`` includes a definition for an http
186
182
proxy running on port 8000 on the same host as the MAAS server. This
187
183
means you can *either* install ``squid-deb-proxy``::
196
192
$ sudo tee -a /etc/tgt/targets.conf < contrib/tgt.conf
198
Now run ``maas-import-pxe-files`` to download current Ubuntu releases for
201
$ sudo http_proxy=$http_proxy PATH=$PATH:$PWD/bin:$PWD/scripts \
202
MAAS_PROVISIONING_SETTINGS=$PWD/etc/pserv.yaml \
203
./scripts/maas-import-pxe-files
205
This may download dozens or hundreds of megabytes, so depending on your
206
network connection it may take a while.
208
194
The http_proxy variable is only needed if you're downloading through a
209
195
proxy; "sudo" wouldn't pass it on to the script without the assignment.
210
196
Or if you don't have it set but do want to download through a proxy, pass
220
206
simple user using the test account (username: 'test', password: 'test') or the
221
207
admin account (username: 'admin', password: 'test').
209
At this point you may also want to `download PXE boot resources`_.
211
.. _`download PXE boot resources`: `Downloading PXE boot resources`_
223
213
To shut down the database cluster and clean up all other generated files in
219
Downloading PXE boot resources
220
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
222
To use PXE booting, each cluster controller needs to download several
223
files relating to PXE booting. This process is automated, but it does
224
not start by default.
226
First create a superuser and start all MAAS services::
228
$ bin/maas createsuperuser
231
Get the superuser's API key on the `account preferences`_ page in web
232
UI, and use it to log into MAAS at the command-line::
234
$ bin/maascli login dev http://localhost:5240
236
.. _`account preferences`: http://localhost:5240/account/prefs/
238
Start downloading PXE boot resources::
240
$ bin/maascli dev node-groups import-boot-images
242
This sends jobs to each cluster controller, asking each to download
243
the boot resources they require. This may download dozens or hundreds
244
of megabytes, so it may take a while. To save bandwidth, set an HTTP
247
$ bin/maascli dev maas set-config name=http_proxy value=http://...
229
250
Running the built-in TFTP server
230
251
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
414
435
``src/maasserver/migrations/<auto_number>_description_of_the_change.py``. Don't
415
436
forget to add that file to the project with::
418
src/maasserver/migrations/<auto_number>_description_of_the_change.py
438
$ bzr add src/maasserver/migrations/<auto_number>_description_of_the_change.py
420
440
To apply that migration, run::
439
459
methods where data should be actually migrated. Again, don't forget to
440
460
add that file to the project::
443
src/maasserver/migrations/<auto_number>_description_of_the_change.py
462
$ bzr add src/maasserver/migrations/<auto_number>_description_of_the_change.py
445
464
Once the methods have been written, apply that migration with::
added
removed
HACKING.txt
