# Metal3-io future plans - Incorporating more Ironic features (priority) -- root device hint operators https://github.com/metal3-io/baremetal-operator/issues/1159 -- attach network data to pre-provisioning image (we have Jire ticket for this) -- other features, probably Ironic folks can offer ideas what else could we enable - Network device management with snmp (topic is blocked) -- https://github.com/metal3-io/metal3-docs/pull/132 (closed atm) -- https://groups.google.com/g/metal3-dev/c/lSw8WhJyb4E/m/CCDOnwDYBAAJ -- https://github.com/metal3-io/baremetal-operator/issues/1227 - Non K8s node LCM management -- https://github.com/metal3-io/metal3-docs/pull/268 - Decomposition of BMO API for multy tenancy -- https://docs.google.com/document/d/1FL8oA0_WNcPdiC-0zrToinl8aol-NPQUjWe-OkcvTqA/edit?usp=sharing - create BMHs after cluster is provisioned and adding them to the cluster - being able to use BMHs from outside of the cluster's namespace - Support extra provisioners in BMO in addition to ironic -- BMO might be a good candidate to present a bare metal machine abstarcion on top of different providers (it might be something that CAPI would be interested) - Adopt and extend the simple go-redfish or other go-redfish client lib as an option beside Ironic for redfish-virtualmedia boots, certain environments might not need a all of the features that Ironic offers. -- https://github.com/Nordix/go-redfish or we could go with Dmitry's suggestion https://github.com/stmcginnis/gofish/. -- interactive user actions might be something that ops/DevOps folks would appreciate - Maybe in place upgrade features, although that is limited by CAPI - Separate e2e tests for BMO - Simplify interaction between CAPM3-BMO-Ironic (UX) -- documentation is key (why is ther Ironic pod, what are the parts of it, what is the flow of pre-provisioning and provisioning) -- we would need hands on examples of Ironic behaviour -- decouple from keepalived and dnsmasq in the examples - Maybe even extending Ironc and BMO functionality with pre-provisioning config drive support (Adam would drive this) - P2P vpn for communication between nodes (just an idea) - organic support for edge cluster/ single node cluster -- can't really delete a machine -- A/B upgrade ideas -- easier management of partition -- this might have CAPI ramification - visualization of Metal3-io clusters/processes -- THere is CAPI visualizer already (we could add advanced features for CPM3-IPAM-BMO) - advenaced monitoring or benchmarking the whole provisioning and inspection process -- timing of different preprovisioning and provisioning stages -- kernel boot time measurement -- systemd bootstrap timing - improve the tilt, CAPI has already improved it a lot (Grafana, Prometheus, Locky) - let's use the project board have a public roodmap -- could use milestones properly -- which PR goes to which milestone or release would not happen if it is dependent on a milestone - could involve the community more with new feature implementation - multi-conductor setup for Ironic, especially its limitations around dnsmasq - stabilizing APIs