e082559046
The Zuul v3 job is looking for the log files from the release notes in: .tox/releasenotes/log/ but we had then in .tox/venv/log/ Fix it to where the Zuul v3 job expects it to be. Also updated the 'docs' job, even though job isn't failing. If the job did fail, with current setup, no log files would be copied which would make debugging more difficult. This change will make it so the log files are copied. Change-Id: I5c036db1a9e94ca28e26fd7b45475d52223f5f0e |
||
---|---|---|
doc/source | ||
etc/ironic_python_agent | ||
imagebuild | ||
ironic_python_agent | ||
releasenotes | ||
tools | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.travis.yml | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
Dockerfile | ||
LICENSE | ||
plugin-requirements.txt | ||
proxy.sh | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Team and repository tags
ironic-python-agent
An agent for controlling and deploying Ironic controlled baremetal nodes.
The ironic-python-agent works with the agent driver in Ironic to provision the node. Starting with ironic-python-agent running on a ramdisk on the unprovisioned node, Ironic makes API calls to ironic-python-agent to provision the machine. This allows for greater control and flexibility of the entire deployment process.
The ironic-python-agent may also be used with the original Ironic pxe drivers as of the Kilo OpenStack release.
Building the IPA deployment ramdisk
For more information see the Image Builder section of the Ironic Python Agent developer guide.
Using IPA with devstack
This is covered in the Deploying Ironic with DevStack section of the Ironic dev-quickstart guide.
Project Resources
Project status, bugs, and blueprints are tracked on Launchpad:
Developer documentation can be found here:
Additional resources are linked from the project wiki page:
- IRC channel:
-
#openstack-ironic
To contribute, start here: Openstack: How to contribute.