Package: magnum / 8.0.0-3

Metadata

Package Version Patches format
magnum 8.0.0-3 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
install missing files.patch | (download)

MANIFEST.in | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 installing missing alembic migration files
 As always, PBR misses the Alembic stuff.
add wsgi script to magnum.patch | (download)

magnum/api/app.py | 7 7 + 0 - 0 !
setup.cfg | 3 3 + 0 - 0 !
2 files changed, 10 insertions(+)

 add wsgi script to magnum
revert magnum proxy patch.patch | (download)

magnum/drivers/common/templates/kubernetes/fragments/configure-etcd.sh | 14 2 + 12 - 0 !
magnum/drivers/heat/k8s_template_def.py | 3 1 + 2 - 0 !
magnum/drivers/heat/swarm_fedora_template_def.py | 3 1 + 2 - 0 !
magnum/drivers/heat/template_def.py | 26 2 + 24 - 0 !
magnum/tests/unit/conductor/handlers/test_k8s_cluster_conductor.py | 3 1 + 2 - 0 !
magnum/tests/unit/drivers/test_template_definition.py | 166 2 + 164 - 0 !
6 files changed, 9 insertions(+), 206 deletions(-)

 revert magnum proxy patch
 This reverts commit e8d0ee1b144f4db24367ad48bd2cb4306add6672.
 .
 This commit is reverted for two reasons:
 .
 * It is undesirable that the end user can inject proxy config into
   the magnum-conductor service via the cluster template.
 .
 * The proxy settings for the magnum-conductor service may not be
   the same as those which are required in the cluster template for
   the end user VM.
 .
 Systemd, docker and podman all include native mechanisms for setting
 environment variables for proecesses, and this should be used by the
 cloud operator / deployment tooling to configure the required proxy
 settings for the magnum-conductor service.
 .
 In particular this patch makes it impossible for the cloud operator
 to specify their own http_proxy via the environment, the user supplied
 cluster template setting will always be used.