4e35b0ee64
This configures tox to use upper-constraints for everything, except environments used for post jobs (as constraints aren't supported there yet). This also doesn't enable constraints for our image builds, as it isn't possible to pass an environment variable into the Dockerfile to allow folks to choose their own constraints file (and we don't want to force people to rely on git.o.o for building images). Change-Id: I285855c6386f59e9dd352473aa28463109818c90 |
||
---|---|---|
doc/source | ||
etc/ironic_python_agent | ||
imagebuild | ||
ironic_python_agent | ||
releasenotes | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
.travis.yml | ||
Dockerfile | ||
LICENSE | ||
plugin-requirements.txt | ||
proxy.sh | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
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.