New Features
Private Cloud Core v4.0.0
- Private Cloud Core v4.0.0 has been released. For full details, see our announcement post: https://openmetal.io/resources/blog/private-cloud-core-v4/
- PCC v4 clouds now use the Horizon UI by default. Users can opt in to Skyline from the Cloud → Settings page.
Versioned Datadog Monitors
- We added support for versioned Datadog monitors and released the v1.1 monitor set. New Datadog deployments will receive the v1.1 monitors, and existing deployments will keep the v1.0 monitors, which are still supported.
- v1.1 adds many more monitors, refines the existing ones, and covers more failure cases, including Ceph health and capacity issues, OOM kills, floating IP exhaustion, Octavia problems, stuck VMs, bond speed issues, and Neutron L3 transition failures.
Firewall Configuration Management API
- PCC v4 deployments now have a firewall configuration management API, which lets users set node-level whitelist entries for ports and IP sets.
Other New Features
- Reprovision Nodes from the Available State — Nodes in the “available” state can now be reprovisioned without manual intervention.
Bug Fixes
- False Alerts During Node Removal — Hosts are now muted before cleanup when a node is removed, which cuts down on false monitoring alerts.
- Datadog Coverage Lost After Node Changes — Nodes in clouds with Datadog enabled now keep their Datadog coverage through node addition, reprovisioning, and node replacement.
- Add Hardware Flow Failing to Load — We corrected an issue that could stop the Add Hardware flow from loading when it was opened from a cloud’s Assets page.
- Incorrect Datacenter Location at Checkout — When hardware is added to an existing cloud, the checkout confirmation now shows the target cloud’s actual location instead of the fallback value of Ashburn.
- New Clusters Not Appearing Immediately — New clusters now show up in the dashboard right after ordering, without a page reload.
- Phone Number Country Codes Not Editable — Phone number country codes can now be edited in Central’s user and organization profile settings.
- Redirect After Re-Authentication — After a session expires, users who sign in again are now taken to the page they were trying to reach.
- IP-Whitelisted API Keys Rejected — We fixed a customer-reported issue where API keys with an IP whitelist were rejected by most endpoints. Whitelisted keys now work as expected, IPv6 entries match correctly, and rejected requests now give the reason, including the IP address that was seen, instead of a generic “token invalid” message.
What’s Next
We’re working on an improved way for users to browse both our Private Cloud and Bare Metal products. More details coming very soon.
If you have questions or feedback, reach out to our support team – we’d love to hear from you.