Skip to content

Release Notes

0.0.0

Prelude

Creating the foundation for the stable branch.

Initial release of a genestack installer for Rackspace OpenStack environments

New Features

  • Prometheus monitoring with the Prometheus Operator. This release uses Prometheus Operator to deploy and manage Prometheus, which is used for system monitoring and alerting.

    https://docs.rackspacecloud.com/prometheus/

  • MetalLB LoadBalancer is supported in this release. MetalLB can be deployed to provide LoadBalancer services to the Kubernetes cluster. This is used by default for VIP address functionality within platform service loadbalancers.

    https://docs.rackspacecloud.com/infrastructure-metallb/

  • NGINX Gateway API is supported in this release. NGINX Gateway API can be deployed to provide Gateway services to the Kubernetes cluster. This is used by default for all internal services and external ingress into the platform services.

    https://docs.rackspacecloud.com/infrastructure-gateway-api/

  • Grafana is supported in this release. Grafana can be deployed to provide metric visualization services for OpenStack and is used by default within the metering stack.

    https://docs.rackspacecloud.com/grafana/

  • Service metric collection is supported in this release and is interconnected with prometheus and grafana to provide metric visualization services throughout the cluster.

    Supported Exporters:
    • Kube-OVN
    • NGINX Gateway Fabris
    • RabbitMQ
    • Memcached
    • MariaDB
    • Postgres
    • OpenStack
    • Blackbox
    • Pushgateway

    Dashboards are all pre-configured for all supported exporters and visualized via Grafana.

  • Envoy Gateway with a full featured configuration in support of OpenStack. Envoy implements the Gateway API with traffic policies, loadbalancers, and listeners which are configured to support the OpenStack APIs.

Known Issues

  • The OVN loadbalancers options are by default available within Genestack but is currently \"tech preview\" and not recommended for production use.
  • Skyline UI currently limits the loadbalancer types to Amphora. This is a known issue and will be resolved in a future release.

Upgrade Notes

  • When upgrading from a pre-release to stable, the following changes will need to be made to the ansible inventory or group_vars to support stable cert-manager

    cert_manager_controller_extra_args:
  - "--enable-gateway-api"

    In previous builds the --enable-gateway-api was unset, but it is now a required option.

  • When upgrading from a pre-release to stable, the following changes will need to be made to the ansible inventory or group_vars to support stable metallb

    metallb_enabled: false

    In previous builds the metallb_enabled was set to true, but it is now managed by the MetalLB helm chart.

  • When upgrading from a pre-release to stable, the following changes will need to be made to the ansible inventory or group_vars to eliminate the CNI plugin from the Kubespray Management.

    kube_network_plugin: none

    In previous builds the kube_network_plugin was set to kube-ovn, but it is now managed by the Kube-OVN helm chart.

  • When upgrading from a pre-release to stable, the following changes will need to be made to the ansible inventory or group_vars to eliminate the previous assumption of the kubeadm patch files.

    kubeadm_patches: []

    In previous builds the kubeadm_patches was set to a dictionary of patches that would deploy files into the environment. This interface was changed upstream and now must be a list of string type patches. Review the upstream documentation[0] for more information.

    [0] https://github.com/kubernetes-sigs/kubespray/blob/v2.27.0/roles/kubernetes/kubeadm_common/defaults/main.yml

  • When upgrading from a pre-release to stable, the following file no longer has any effect on the environment and can be removed from the ansible group_vars.

    /etc/genestack/inventory/group_vars/k8s_cluster/k8s-net-kube-ovn.yml

    This file can be eliminated.

Deprecation Notes

  • The barbican chart will now use the online OSH helm repository. This change will allow the barbican chart to be updated more frequently and will allow the barbican chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall barbican
kubectl -n openstack delete -f /etc/genestack/kustomize/barbican/base/barbican-rabbitmq-queue.yaml
/opt/genestack/bin/install-barbican.sh

    This operation should have no operational impact on running VMs but should be performed during a maintenance window.

  • In early builds of Genestack Kube-OVN was deployed and managed by Kubespray; however, this is no longer the case. The Kube-OVN helm chart is now used to deploy and manage the Kube-OVN CNI plugin.
  • In early builds of Genestack MetalLB was deployed and managed by Kubespray; however, this is no longer the case. The MetalLB helm chart is now used to deploy and manage the MetalLB LoadBalancer.
  • In early builds of Genestack the cert-manager option ExperimentalGatewayAPISupport was set to true, within the ansible group_vars. This option should be removed as it no longer has any effect.

  • The ceilometer chart will now use the online OSH helm repository. This change will allow the ceilometer chart to be updated more frequently and will allow the ceilometer chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall ceilometer
kubectl -n openstack delete -f /etc/genestack/kustomize/ceilometer/base/ceilometer-rabbitmq-queue.yaml
/opt/genestack/bin/install-ceilometer.sh

    This operation should have no operational impact but should be performed during a maintenance window.

  • The cinder chart will now use the online OSH helm repository. This change will allow the cinder chart to be updated more frequently and will allow the cinder chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall cinder
kubectl -n openstack delete -f /etc/genestack/kustomize/cinder/base/cinder-rabbitmq-queue.yaml
/opt/genestack/bin/install-cinder.sh

    This operation should have no operational impact on running VMs but should be performed during a maintenance window.

  • The glance chart will now use the online OSH helm repository. This change will allow the glance chart to be updated more frequently and will allow the glance chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall glance
kubectl -n openstack delete -f /etc/genestack/kustomize/glance/base/glance-rabbitmq-queue.yaml
/opt/genestack/bin/install-glance.sh

    This operation should have no operational impact on running VMs but should be performed during a maintenance window.

  • The gnocchi chart will now use the online OSH helm repository. This change will allow the gnocchi chart to be updated more frequently and will allow the gnocchi chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall gnocchi
kubectl -n openstack delete -f /etc/genestack/kustomize/gnocchi/base/gnocchi-rabbitmq-queue.yaml
/opt/genestack/bin/install-gnocchi.sh

  • The heat chart will now use the online OSH helm repository. This change will allow the heat chart to be updated more frequently and will allow the heat chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall heat
kubectl -n openstack delete -f /etc/genestack/kustomize/heat/base/heat-rabbitmq-queue.yaml
/opt/genestack/bin/install-heat.sh

    This operation should have no operational impact on running VMs but should be performed during a maintenance window.

  • The horizon chart will now use the online OSH helm repository. This change will allow the horizon chart to be updated more frequently and will allow the horizon chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall horizon
/opt/genestack/bin/install-horizon.sh

    This operation should have no operational impact on running VMs but should be performed during a maintenance window.

  • The keystone chart will now use the online OSH helm repository. This change will allow the keystone chart to be updated more frequently and will allow the keystone chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall keystone
kubectl -n openstack delete -f /etc/genestack/kustomize/keystone/base/keystone-rabbitmq-queue.yaml
/opt/genestack/bin/install-keystone.sh

    This operation should have no operational impact on running VMs but should be performed during a maintenance window.

  • The libvirt chart will now use the online OSH helm repository. This change will allow the libvirt chart to be updated more frequently and will allow the libvirt chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall libvirt
/opt/genestack/bin/install-libvirt.sh

    This operation should have no operational impact on running VMs but should be performed during a maintenance window.

  • The magnum chart will now use the online OSH helm repository. This change will allow the magnum chart to be updated more frequently and will allow the magnum chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall magnum
kubectl -n openstack delete -f /etc/genestack/kustomize/magnum/base/magnum-rabbitmq-queue.yaml
/opt/genestack/bin/install-magnum.sh

    This operation should have no operational impact on running VMs but should be performed during a maintenance window.

  • The neutron chart will now use the online OSH helm repository. This change will allow the neutron chart to be updated more frequently and will allow the neutron chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall neutron
kubectl -n openstack delete -f /etc/genestack/kustomize/neutron/base/neutron-rabbitmq-queue.yaml
/opt/genestack/bin/install-neutron.sh

  • The nova chart will now use the online OSH helm repository. This change will allow the nova chart to be updated more frequently and will allow the nova chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall nova
kubectl -n openstack delete -f /etc/genestack/kustomize/nova/base/nova-rabbitmq-queue.yaml
/opt/genestack/bin/install-nova.sh

    This operation should have no operational impact on running VMs but should be performed during a maintenance window.

  • The octavia chart will now use the online OSH helm repository. This change will allow the octavia chart to be updated more frequently and will allow the octavia chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall octavia
kubectl -n openstack delete -f /etc/genestack/kustomize/octavia/base/octavia-rabbitmq-queue.yaml
/opt/genestack/bin/install-octavia.sh

    Depending on the state of the Octavia deployment, it may be nessessary to rerun the ansible-playbook for the octavia deployment. Note that this playbook will drop a marker file /tmp/octavia_hm_controller_ip_port_list which may need to be cleaned up before rerunning the playbook.

    https://docs.rackspacecloud.com/openstack-octavia/#run-the-playbook

    That said, if the deployment was healthy before, the cleanup steps should not be needed. This operation should have no operational impact on running VMs but should be performed during a maintenance window.

  • The placement chart will now use the online OSH helm repository. This change will allow the placement chart to be updated more frequently and will allow the placement chart to be used with the OpenStack-Helm project. Upgrading to this chart may require changes to the deployment configuration. Simple updates can be made by running the following command:

    helm -n openstack uninstall placement
/opt/genestack/bin/install-placement.sh

    This operation should have no operational impact on running VMs but should be performed during a maintenance window.