Skip to content

Fix/nfv controlplane novnc and metricstorage#770

Open
aharivel wants to merge 2 commits into
openstack-k8s-operators:mainfrom
aharivel:fix/nfv-controlplane-novnc-metricstorage
Open

Fix/nfv controlplane novnc and metricstorage#770
aharivel wants to merge 2 commits into
openstack-k8s-operators:mainfrom
aharivel:fix/nfv-controlplane-novnc-metricstorage

Conversation

@aharivel

Copy link
Copy Markdown

Fixes two gaps in the NFV OVS-DPDK-SRIOV controlplane configuration identified by comparing rendered manifests against authoritative RHOSO component specs:

  • Add noVNCProxyServiceTemplate to nova cell1 (lib/control-plane/base): The base OpenStackControlPlane defines cell1 without a noVNCProxyServiceTemplate, meaning VNC console access to VMs on cell1 compute nodes is unavailable out of the box. The authoritative RHOSO docs specify enabled: true with a ctlplane network attachment. This affects all validated architectures inheriting from lib/control-plane/base.

  • Add metricStorage kustomize replacement (va/nfv/ovs-dpdk-sriov): The NFV VA already exposes telemetry.enabled and ceilometer.enabled via service-values replacements, but metricStorage.enabled has no replacement — it stays false regardless of deployer intent. This adds the missing replacement so NFV deployments can toggle Prometheus metric collection through service-values.yaml.

The base OpenStackControlPlane defines cell1 without a
noVNCProxyServiceTemplate, which means VNC console access to VMs
scheduled on cell1 compute nodes is not available.

The authoritative RHOSO documentation specifies that cell1 should
include noVNCProxyServiceTemplate with enabled: true and a ctlplane
network attachment. Without this, operators must manually patch every
deployment to enable console access — a common source of post-deploy
debugging.

This affects all validated architectures that inherit from
lib/control-plane/base.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Anthony Harivel <aharivel@redhat.com>
@openshift-ci openshift-ci Bot requested review from cjeanner and karelyatin June 18, 2026 13:25
@openshift-ci

openshift-ci Bot commented Jun 18, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: aharivel
Once this PR has been reviewed and has the lgtm label, please assign leifmadsen for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

…values

The NFV OVS-DPDK-SRIOV validated architecture enables telemetry and
ceilometer via service-values replacements, but metricStorage (Prometheus
monitoring stack) has no replacement — it stays at the base default of
enabled: false regardless of what the deployer sets in service-values.

This adds a kustomize replacement for
telemetry.template.metricStorage.enabled so NFV deployments can toggle
Prometheus metric collection through service-values.yaml, consistent
with how telemetry.enabled and ceilometer.enabled are already handled.

Also adds the metricStorage.enabled field to example service-values for
both ovs-dpdk-sriov and ovs-dpdk-sriov-ipv6 to satisfy the kustomize
replacement source requirement and provide a working default.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@aharivel aharivel force-pushed the fix/nfv-controlplane-novnc-metricstorage branch from 02dcdba to ed23b12 Compare June 18, 2026 13:28
@mnietoji

Copy link
Copy Markdown
Contributor

It looks ok to me

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.

2 participants