
So the prime driver behind pinning the MTU down on our interfaces is so traffic can cross mutlinode vxlan tunnels between nodes where the devstack plugin is executing to support more complex tests. But the reality is that doesn't always make sense, and when Neutron has a default mtu override based upon "upstream" traffic constraints, that is likey okay as well. Part of the CI configuration auto-pins the MTU down, which is fine for single node testing, however with multinode we need to pin the MTU further down to try and prevent packets from being dropped on the internal interfaces use to wire up test VMs. Change-Id: Idc145f4eea87a8db69202b8d7953975d7d5cba2c
Ironic
Team and repository tags
Overview
Ironic consists of an API and plug-ins for managing and provisioning physical machines in a security-aware and fault-tolerant manner. It can be used with nova as a hypervisor driver, or standalone service using bifrost. By default, it will use PXE and IPMI to interact with bare metal machines. Ironic also supports vendor-specific plug-ins which may implement additional functionality.
Ironic is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
Project resources
- Documentation: https://docs.openstack.org/ironic/latest
- Source: https://opendev.org/openstack/ironic
- Bugs: https://bugs.launchpad.net/ironic/+bugs
- Wiki: https://wiki.openstack.org/wiki/Ironic
- APIs: https://docs.openstack.org/api-ref/baremetal/index.html
- Release Notes: https://docs.openstack.org/releasenotes/ironic/
- Design Specifications: https://specs.openstack.org/openstack/ironic-specs/
Project status, bugs, and requests for feature enhancements (RFEs) are tracked in Launchpad: https://launchpad.net/ironic
For information on how to contribute to ironic, see https://docs.openstack.org/ironic/latest/contributor