Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v1.3.x] Allow usage of OpenStackConfigGenerator without a full deployed env #1053

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1048

/assign stuggi

This change allows to just generate ansible playbooks using the
OpenStackConfigGenerate without deploying controller VMs or
compute baremetal nodes. This is useful e.g. for debugging
purposes to just get the content from ConfigMaps/Secrets and
analyse rendering issues on a different system.

a) As a pre-requ create the required ConfigMaps and Secrets
ConfigMaps:
- heat-env-config-deploy
- tripleo-deploy-config-default
- tripleo-tarball-config-deploy

Secrets:
- git-secret (make sure to prepare the git repo, or run the
  OpenStackConfigGenerator with `interactive: true` and run the
  create_playbooks.sh manually. This allows to check the generated
  playbooks whithin the pod)
- tripleo-passwords ()

b) Create the OpenStackConfigGenerator with name `default` and an `debug` section like e.g.:
~~~
apiVersion: osp-director.openstack.org/v1beta1
kind: OpenStackConfigGenerator
metadata:
  name: default
  namespace: openstack
spec:
  enableFencing: false
  ephemeralHeatSettings:
    heatEngineReplicas: 3
  gitSecret: git-secret
  heatEnvConfigMap: heat-env-config-deploy
  heatEnvs:
  - ssl/tls-endpoints-public-dns.yaml
  - ssl/enable-tls.yaml
  - services/octavia.yaml
  imageURL: registry.redhat.io/.../.../openstack-tripleoclient:17.1
  interactive: false
  tarballConfigMap: tripleo-tarball-config-deploy
  debug:
    skipWaiting: true
    tripleoDeployConfigOverride: tripleo-deploy-config-default
    openStackRelease: "17.1"
~~~
Copy link
Contributor

@abays abays left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Jun 5, 2024
Copy link
Contributor

openshift-ci bot commented Jun 5, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abays, openshift-cherrypick-robot

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

The pull request process is described here

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

@openshift-ci openshift-ci bot added the approved label Jun 5, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 176b2d2 into openstack-k8s-operators:v1.3.x Jun 5, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants