Update master for stable/2026.1
Add file to the reno documentation build to show release notes for stable/2026.1.
Use pbr instruction to increment the minor version number automatically so that master versions are higher than the versions on stable/2026.1.
Sem-Ver: feature Change-Id: Ia35611be458ee7f4c0a5b58023881e15d79d983b Signed-off-by: OpenStack Release Bot infra-root@openstack.org Generated-By: openstack/project-config:roles/copy-release-tools-scripts/files/release-tools/add_release_note_page.sh
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
Team and repository tags
magnum
Table of Contents
Overview
The magnum module is a part of OpenStack, an effort by the OpenStack infrastructure team to provide continuous integration testing and code review for OpenStack and OpenStack community projects not part of the core software. The module itself is used to flexibly configure and manage the container service for OpenStack.
Module Description
The magnum module is a thorough attempt to make Puppet capable of managing the entirety of magnum. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the magnum module to assist in manipulation of configuration files.
Setup
What the magnum module affects
Installing magnum
magnum is not currently in Puppet Forge, but is anticipated to be added soon. Once that happens, you’ll be able to install magnum with:
Beginning with magnum
To utilize the magnum module’s functionality you will need to declare multiple resources. This is not an exhaustive list of all the components needed, we recommend you consult and understand the core openstack documentation.
Implementation
magnum
magnum is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
Limitations
Development
Developer documentation for the entire puppet-openstack project.
Contributors
Release Notes
Repository