fa4bb8f690
Renamed jobs to more appropriate names, and extended base timouts, as well as the build timeouts for coreos as the image we work with today is a little larger than it was previously. Change-Id: I2884ba795bae689b40826b8c7e2714e3eb5811fb Depends-On: I139679db835b7a87c55f69a4d807ff8ec9099e3a |
||
---|---|---|
doc/source | ||
etc/ironic_python_agent | ||
imagebuild | ||
ironic_python_agent | ||
playbooks/legacy | ||
releasenotes | ||
tools | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.travis.yml | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
Dockerfile | ||
LICENSE | ||
lower-constraints.txt | ||
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, features, and bugs are tracked on StoryBoard:
Developer documentation can be found here:
- Release notes for the project are available at:
-
https://docs.openstack.org/releasenotes/ironic-python-agent/
Additional resources are linked from the project wiki page:
- IRC channel:
-
#openstack-ironic
To contribute, start here: Openstack: How to contribute.