5707c35b41
When running unit tests in an environment without network access,
for example in a packaging env, test_run_with_sleep fails with a
timeout trying to list the network interfaces [1].
Mocking the _wait_for_interface call, as it is done currently on
master and stable/pike, fixes the issue. The original commit is
fdcb0922a5c4a4ecbb8cb1b307c6c750990699ff; this patch only grabs
the one mock from the original change.
[1] - See
|
||
---|---|---|
doc/source | ||
etc/ironic_python_agent | ||
imagebuild | ||
ironic_python_agent | ||
releasenotes | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
.travis.yml | ||
CONTRIBUTING.rst | ||
Dockerfile | ||
LICENSE | ||
README.rst | ||
plugin-requirements.txt | ||
proxy.sh | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
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.