Skip to content

Add HVM cluster 2.0 network config fields to the cluster server create schema - #372

Open
RDavisHPE wants to merge 2 commits into
tf-devfrom
morph-17748-cluster-hvm-2
Open

RDavisHPE wants to merge 2 commits into
tf-devfrom
morph-17748-cluster-hvm-2

Conversation

@RDavisHPE

Copy link
Copy Markdown
Contributor

What this adds

Adds the HVM Cluster 2.0 network configuration fields to
clusterServerCreateConfigHVM (the HVM variant of the cluster server create
config):

  • virtSwitchName
  • dns1, dns2, dns3
  • searchDomain
  • ntp1, ntp2
  • proxy, noProxy

All are optional strings. On the Morpheus API these are written into the
cluster server config when the selected cluster layout supports cluster
version 2.0 or greater.

Read side

The cluster read config is intentionally left as a generic object: cluster
config is polymorphic across provision types and the API echoes back more
properties than were set, so consumers read the values they set back out of
the generic map. These fields round-trip that way, consistent with the other
HVM config fields.

Ryan Davis added 2 commits September 24, 2026 20:42
Add virtSwitchName, dns1-3, searchDomain, ntp1, ntp2, proxy and noProxy
to the HVM cluster server create config, add a matching HVM read variant
so these fields round-trip on cluster read.
Drop the typed HVM read variant; the HVM 2.0 fields round-trip through the
generic echoed config, consistent with how the existing HVM config fields
are read.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant