Guidelines to follow when writing new code or submitting patches.
- Need output of ~/.cloud-install/commands.log, use http://paste.ubuntu.com or some other form of pastebin.
- Which install type
- A
sosreport
from the host system if a single install, MAAS server if multi/landscape autopilot installation.
-
/var/log/landscape-server/job-handler.log
Obtain that by running the following from the MAAS system:
$ JUJU_HOME=~/.cloud-install/juju juju ssh landscape/0 $ sudo apt-get install pastebinit $ pastebinit /var/log/landscape-server/job-handler.log
-
lshw
outputObtain that by clicking on a node in the MAAS webui and following the link labeled
Show discovered details
-
Network response from Landscape's webui in the 'create-region' page.
See: https://github.com/Ubuntu-Solutions-Engineering/openstack-installer/issues/374#issuecomment-71521918
- Must sign the CLA http://www.ubuntu.com/legal/contributors/
- Rebase from master before a PR
- Coherent subject/commit message
- (optional) dco
- Passes unittests, pep8, pyflakes (use
make tox
if installed.)
- Follow PEP-8 style guide. http://www.python.org/dev/peps/pep-0008/
- Coding guidelines based off with a few differences
http://google-styleguide.googlecode.com/svn/trunk/pyguide.html
- Documenting code differences We use the default sphinx style for documenting classes, functions, methods.