Simple deployment and scheduling tool for bare metal
f98dfa61c1
cloud-init will use fall-back config when network metadata is *not* present. This works fine if the first NIC on the node is connected to a network with DHCP. But, when the first NIC is not used for provisioning, cloud-init will only write a fallback config for the first NIC. This causes the provisioned node to be unavailable. Extend instance configuration to include network metadata so that cloud-init can configure node networking. Story: 2009238 Task: 43378 Change-Id: I70f1a972a6d5a0398cd348f00308957386d66067 |
||
---|---|---|
doc | ||
metalsmith | ||
metalsmith_ansible | ||
playbooks/integration | ||
releasenotes | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
roles | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Deployment and Scheduling tool for Bare Metal
Overview
This is a simple tool to provision bare metal machines using OpenStack Bare Metal Service (ironic) and, optionally, OpenStack Image Service (glance) and OpenStack Networking Service (neutron).
- License: Apache License, Version 2.0
- Documentation: https://docs.openstack.org/metalsmith/
- Source: https://opendev.org/openstack/metalsmith
- Bugs: https://storyboard.openstack.org/#!/project/openstack/metalsmith
Installation
pip install --user metalsmith
Note
The current versions of metalsmith require Bare Metal API from the Stein release or newer. Use the 0.11 release series for older versions.
Contributing
- Pull requests: Gerrit (see developer's guide)
- Bugs and RFEs: StoryBoard (please do NOT report bugs to Github)