v2023-09.21 #264
msherman64
announced in
Announcements
v2023-09.21
#264
Replies: 1 comment
-
Inspection also gives us an easy way to test if nodes are set up/connected correctly. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
It's been a while since our last "release", but we've added two main features of interest:
Large Instance Launches
Large instance launches with baremetal are much improved, leveraging the "batching" feature from upstream networking-generic-switch.
https://docs.openstack.org/networking-generic-switch/latest/configuration.html#batching
To enable:
enable_etcd: true
in defaults.yml, then rundeploy --tags etcd
enable_etcd
set, but you can also set it manually by specifying ngs_backend_urlngs_batch_requests: true
. After making the changes, rundeploy --tags neutron
Initial support for ironic node inspection
We're still working on generating the reference-repository data from it, but you can now use ironic inspection as a way to "healthcheck" your nodes. As of this release, you can enable the feature by editing your ansible hosts file to add
ironic
under the groupironic-inspector:children
as seen here, then runningdeploy --tags ironic
For nodes already enrolled, you'll need to update the ironic "inspect interface" by running
openstack baremetal node set --reset-inspect-interface
for each node.After this, you can inspect a node by the following sequence of commands:
openstack baremetal node manage <node>
openstack baremetal node inspect <node>
openstack baremetal node provide <node>
to make it available for use againThis procedure will exercise all features needed to boot a node, including setting the boot order on the node, baremetal switch networking, neutron dhcp config, routing from the provisioning network to the ironic pxe/ipxe service, and launching the ironic agent, only excluding the use of glance images.
Not yet included:
In a forthcoming release we will use the information gathered by inspection to verify the network port configuration on nodes, as well as auto-populate a searchable inventory and blazar reservation labels.
Note:
We've moved our image hosting to the github container registry. You'll note that docker images names have changes from
docker.chameleoncloud.org/kollla/...
toghcr.io/chameleoncloud/kolla/...
. This was done to improve the speed and reliability of container image hosting, and to better integrate with our CI/CD process for container image releases.Full Changelog: v2022-10.12...v2023-09.21
This discussion was created from the release v2023-09.21.
Beta Was this translation helpful? Give feedback.
All reactions