OpenStack Dashboard Charm

Get this repository:
git clone https://git.launchpad.net/charm-openstack-dashboard

See all merge proposals.

Import details

Import Status: Reviewed

This repository is an import of the Git repository at https://opendev.org/openstack/charm-openstack-dashboard.git.

The next import is scheduled to run .

Last successful import was .

Import started on juju-98ee42-prod-launchpad-codeimport-4 and finished taking 30 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-1 and finished taking 20 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-0 and finished taking 20 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-5 and finished taking 1 minute — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-4 and finished taking 40 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-4 and finished taking 20 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-1 and finished taking 20 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-0 and finished taking 20 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-5 and finished taking 30 seconds — see the log
Import started on juju-98ee42-prod-launchpad-codeimport-4 and finished taking 25 seconds — see the log

Branches

Name Last Modified Last Commit
stable/ussuri 2024-04-17 13:34:03 UTC
Adjust haproxy timeout to intended values

Author: Rodrigo Barbieri
Author Date: 2024-03-06 17:59:11 UTC

Adjust haproxy timeout to intended values

Many years ago change Ida7949113594b9b859ab7b4ba8b2bb440bab6e7d
attempted to change the timeouts of haproxy but did not succeed,
as deployments were still using the values from the charm's
templates/haproxy.cfg file, being effectively set to 30 seconds
and causing timeouts (see bug). Additionally, the description
of the config options became inaccurate, stating the default to
be a value that they were really not.

This patch addresses the timeout value discrepancy, adjusting
to the original change's intended values.

Closes-bug: #2045168
Change-Id: I83405727b4a116ec6f47b61211bf8ef3d2d9fbd6
(cherry picked from commit 09c587116059319305b2a09cb393a084a52d1fc9)
(cherry picked from commit 2f430d15e64766fce4dc398ee23703a395693027)
(cherry picked from commit f013b18c7680174dcbc4217030081a451347c8ef)
(cherry picked from commit f6f60a37ba99fd56fd02ac1a4c518703e9d9efca)
(cherry picked from commit 62777b150b1753a5a33e16c6dbfce24bc828a9dd)
(cherry picked from commit fb63730e63fb09919d8b24c4ce34c77c85bb1317)
(cherry picked from commit 9885182a9316c3ff9e73578989fb790ce4677416)
(cherry picked from commit a7a427ad6a11fe5ac3952d072a79fa11b9cda083)
stable/victoria 2024-04-09 18:42:08 UTC
Adjust haproxy timeout to intended values

Author: Rodrigo Barbieri
Author Date: 2024-03-06 17:59:11 UTC

Adjust haproxy timeout to intended values

Many years ago change Ida7949113594b9b859ab7b4ba8b2bb440bab6e7d
attempted to change the timeouts of haproxy but did not succeed,
as deployments were still using the values from the charm's
templates/haproxy.cfg file, being effectively set to 30 seconds
and causing timeouts (see bug). Additionally, the description
of the config options became inaccurate, stating the default to
be a value that they were really not.

This patch addresses the timeout value discrepancy, adjusting
to the original change's intended values.

Closes-bug: #2045168
Change-Id: I83405727b4a116ec6f47b61211bf8ef3d2d9fbd6
(cherry picked from commit 09c587116059319305b2a09cb393a084a52d1fc9)
(cherry picked from commit 2f430d15e64766fce4dc398ee23703a395693027)
(cherry picked from commit f013b18c7680174dcbc4217030081a451347c8ef)
(cherry picked from commit f6f60a37ba99fd56fd02ac1a4c518703e9d9efca)
(cherry picked from commit 62777b150b1753a5a33e16c6dbfce24bc828a9dd)
(cherry picked from commit fb63730e63fb09919d8b24c4ce34c77c85bb1317)
(cherry picked from commit 9885182a9316c3ff9e73578989fb790ce4677416)
stable/wallaby 2024-04-05 20:31:40 UTC
Adjust haproxy timeout to intended values

Author: Rodrigo Barbieri
Author Date: 2024-03-06 17:59:11 UTC

Adjust haproxy timeout to intended values

Many years ago change Ida7949113594b9b859ab7b4ba8b2bb440bab6e7d
attempted to change the timeouts of haproxy but did not succeed,
as deployments were still using the values from the charm's
templates/haproxy.cfg file, being effectively set to 30 seconds
and causing timeouts (see bug). Additionally, the description
of the config options became inaccurate, stating the default to
be a value that they were really not.

This patch addresses the timeout value discrepancy, adjusting
to the original change's intended values.

Closes-bug: #2045168
Change-Id: I83405727b4a116ec6f47b61211bf8ef3d2d9fbd6
(cherry picked from commit 09c587116059319305b2a09cb393a084a52d1fc9)
(cherry picked from commit 2f430d15e64766fce4dc398ee23703a395693027)
(cherry picked from commit f013b18c7680174dcbc4217030081a451347c8ef)
(cherry picked from commit f6f60a37ba99fd56fd02ac1a4c518703e9d9efca)
(cherry picked from commit 62777b150b1753a5a33e16c6dbfce24bc828a9dd)
(cherry picked from commit fb63730e63fb09919d8b24c4ce34c77c85bb1317)
stable/xena 2024-04-04 11:14:07 UTC
Adjust haproxy timeout to intended values

Author: Rodrigo Barbieri
Author Date: 2024-03-06 17:59:11 UTC

Adjust haproxy timeout to intended values

Many years ago change Ida7949113594b9b859ab7b4ba8b2bb440bab6e7d
attempted to change the timeouts of haproxy but did not succeed,
as deployments were still using the values from the charm's
templates/haproxy.cfg file, being effectively set to 30 seconds
and causing timeouts (see bug). Additionally, the description
of the config options became inaccurate, stating the default to
be a value that they were really not.

This patch addresses the timeout value discrepancy, adjusting
to the original change's intended values.

Closes-bug: #2045168
Change-Id: I83405727b4a116ec6f47b61211bf8ef3d2d9fbd6
(cherry picked from commit 09c587116059319305b2a09cb393a084a52d1fc9)
(cherry picked from commit 2f430d15e64766fce4dc398ee23703a395693027)
(cherry picked from commit f013b18c7680174dcbc4217030081a451347c8ef)
(cherry picked from commit f6f60a37ba99fd56fd02ac1a4c518703e9d9efca)
(cherry picked from commit 62777b150b1753a5a33e16c6dbfce24bc828a9dd)
stable/yoga 2024-04-01 13:36:22 UTC
Adjust haproxy timeout to intended values

Author: Rodrigo Barbieri
Author Date: 2024-03-06 17:59:11 UTC

Adjust haproxy timeout to intended values

Many years ago change Ida7949113594b9b859ab7b4ba8b2bb440bab6e7d
attempted to change the timeouts of haproxy but did not succeed,
as deployments were still using the values from the charm's
templates/haproxy.cfg file, being effectively set to 30 seconds
and causing timeouts (see bug). Additionally, the description
of the config options became inaccurate, stating the default to
be a value that they were really not.

This patch addresses the timeout value discrepancy, adjusting
to the original change's intended values.

Closes-bug: #2045168
Change-Id: I83405727b4a116ec6f47b61211bf8ef3d2d9fbd6
(cherry picked from commit 09c587116059319305b2a09cb393a084a52d1fc9)
(cherry picked from commit 2f430d15e64766fce4dc398ee23703a395693027)
(cherry picked from commit f013b18c7680174dcbc4217030081a451347c8ef)
(cherry picked from commit f6f60a37ba99fd56fd02ac1a4c518703e9d9efca)
stable/zed 2024-03-28 15:06:36 UTC
Adjust haproxy timeout to intended values

Author: Rodrigo Barbieri
Author Date: 2024-03-06 17:59:11 UTC

Adjust haproxy timeout to intended values

Many years ago change Ida7949113594b9b859ab7b4ba8b2bb440bab6e7d
attempted to change the timeouts of haproxy but did not succeed,
as deployments were still using the values from the charm's
templates/haproxy.cfg file, being effectively set to 30 seconds
and causing timeouts (see bug). Additionally, the description
of the config options became inaccurate, stating the default to
be a value that they were really not.

This patch addresses the timeout value discrepancy, adjusting
to the original change's intended values.

Closes-bug: #2045168
Change-Id: I83405727b4a116ec6f47b61211bf8ef3d2d9fbd6
(cherry picked from commit 09c587116059319305b2a09cb393a084a52d1fc9)
(cherry picked from commit 2f430d15e64766fce4dc398ee23703a395693027)
(cherry picked from commit f013b18c7680174dcbc4217030081a451347c8ef)
master 2024-03-28 01:57:28 UTC
Added OPENSTACK_KEYSTONE_MFA_TOTP_ENABLED to config options

Author: Carlos Bravo
Author Date: 2024-03-22 14:52:25 UTC

Added OPENSTACK_KEYSTONE_MFA_TOTP_ENABLED to config options

Starting from Openstack Bobcat (2023.2) Multi Factor Authentication
was added for Horizon. This change introduced a new variable called
OPENSTACK_KEYSTONE_MFA_TOTP_ENABLED, which if set to True will display
a new form requesting for the user's TOTP code for MFA enabled users.

This change provides the missing OPENSTACK_KEYSTONE_MFA_TOTP_ENABLED
config option for the charm, allowing the user to enable from the
charm's configuration. If the value is set to True, the new bobcat
template will render the following values:
OPENSTACK_KEYSTONE_MFA_TOTP_ENABLED = True

AUTHENTICATION_PLUGINS = [
    'openstack_auth.plugin.totp.TotpPlugin',
    'openstack_auth.plugin.password.PasswordPlugin',
    'openstack_auth.plugin.token.TokenPlugin'
]

Closes-Bug: #2058689
Change-Id: Ifedf587356693b58612b1fc4d7404f0f446158ce
stable/2023.1 2024-03-27 19:24:31 UTC
Adjust haproxy timeout to intended values

Author: Rodrigo Barbieri
Author Date: 2024-03-06 17:59:11 UTC

Adjust haproxy timeout to intended values

Many years ago change Ida7949113594b9b859ab7b4ba8b2bb440bab6e7d
attempted to change the timeouts of haproxy but did not succeed,
as deployments were still using the values from the charm's
templates/haproxy.cfg file, being effectively set to 30 seconds
and causing timeouts (see bug). Additionally, the description
of the config options became inaccurate, stating the default to
be a value that they were really not.

This patch addresses the timeout value discrepancy, adjusting
to the original change's intended values.

Closes-bug: #2045168
Change-Id: I83405727b4a116ec6f47b61211bf8ef3d2d9fbd6
(cherry picked from commit 09c587116059319305b2a09cb393a084a52d1fc9)
(cherry picked from commit 2f430d15e64766fce4dc398ee23703a395693027)
stable/2023.2 2024-03-25 16:11:21 UTC
Adjust haproxy timeout to intended values

Author: Rodrigo Barbieri
Author Date: 2024-03-06 17:59:11 UTC

Adjust haproxy timeout to intended values

Many years ago change Ida7949113594b9b859ab7b4ba8b2bb440bab6e7d
attempted to change the timeouts of haproxy but did not succeed,
as deployments were still using the values from the charm's
templates/haproxy.cfg file, being effectively set to 30 seconds
and causing timeouts (see bug). Additionally, the description
of the config options became inaccurate, stating the default to
be a value that they were really not.

This patch addresses the timeout value discrepancy, adjusting
to the original change's intended values.

Closes-bug: #2045168
Change-Id: I83405727b4a116ec6f47b61211bf8ef3d2d9fbd6
(cherry picked from commit 09c587116059319305b2a09cb393a084a52d1fc9)
stable/train 2023-08-18 14:07:57 UTC
[train] Ensure get_requests_for_local_unit doesn't fail on incomplete relation

Author: Alex Kavanagh
Author Date: 2023-08-18 14:04:43 UTC

[train] Ensure get_requests_for_local_unit doesn't fail on incomplete relation

This is a rebuild/make sync for charms to pickup the fix in charmhelpers to fix
any inadvertant accesses of ['ca'] in the relation data before it is available
from vault in the certificates relation. Fix in charmhelpers is in [1].

[1] https://github.com/juju/charm-helpers/pull/832
Closes-Bug: #2028683

Change-Id: I07a812352107dbf7b861317799c88d8ff0aa8bd3
stable/queens 2021-10-21 14:03:58 UTC
21.10 - Release

Author: Alex Kavanagh
Author Date: 2021-10-21 13:49:41 UTC

21.10 - Release

Remove the "channel: candidate" from the func-test
bundles.

Change-Id: If5cdf2a0d7abacad345299f90e900691c1ae300d
stable/rocky 2021-10-21 14:03:58 UTC
21.10 - Release

Author: Alex Kavanagh
Author Date: 2021-10-21 13:49:41 UTC

21.10 - Release

Remove the "channel: candidate" from the func-test
bundles.

Change-Id: If5cdf2a0d7abacad345299f90e900691c1ae300d
stable/stein 2021-10-21 14:03:58 UTC
21.10 - Release

Author: Alex Kavanagh
Author Date: 2021-10-21 13:49:41 UTC

21.10 - Release

Remove the "channel: candidate" from the func-test
bundles.

Change-Id: If5cdf2a0d7abacad345299f90e900691c1ae300d
stable/21.10 2021-10-21 14:03:58 UTC
21.10 - Release

Author: Alex Kavanagh
Author Date: 2021-10-21 13:49:41 UTC

21.10 - Release

Remove the "channel: candidate" from the func-test
bundles.

Change-Id: If5cdf2a0d7abacad345299f90e900691c1ae300d
stable/21.04 2021-08-31 16:48:25 UTC
Sync release-tools

Author: Aurelien Lourot
Author Date: 2021-07-22 12:59:34 UTC

Sync release-tools

In order to fix ResolutionImpossible on tox invocation.

https://github.com/openstack-charmers/release-tools/issues/151
https://github.com/openstack-charmers/release-tools/pull/152

Change-Id: Idde242e447572696771a878653165c48fe331c3b
(cherry picked from commit d746d85433da96f2837982e049923327d92a4121)
stable/21.01 2021-02-10 19:17:34 UTC
Updates for stable branch creation 21.01

Author: Aurelien Lourot
Author Date: 2021-02-10 19:17:23 UTC

Updates for stable branch creation 21.01

Set default branch for git review/gerrit.
Switch tests to stable.
Switch to using stable charm-helpers branch.
Switch to using stable charm.openstack branch.
Switch to using stable zaza branch.
Switch to using stable zaza-openstack-tests branch.

Change-Id: Iee44b75dce4b70fd11b7bc318ef08a0ee25b5150
stable/20.10 2020-11-17 22:17:41 UTC
Revert "Update template to enable offline-compression"

Author: Eric Desrochers
Author Date: 2020-11-13 16:35:14 UTC

Revert "Update template to enable offline-compression"

This reverts commit 0fe556e389f4b7dcf68a5bbe1421c848cd78e6e1.

Closes-Bug: 1903911
Related-Bug: 1902890

Change-Id: I3e774e1ce98a9e77905bf49075c95ba478cb13c3
Signed-off-by: Eric Desrochers <eric.desrochers@canonical.com>
(cherry picked from commit 6ba0b72827115447de0f3060940d66b079f6d7da)
stable/20.08 2020-09-01 21:41:19 UTC
Ensure that certificates are correctly managed.

Author: Liam Young
Author Date: 2020-08-20 07:29:38 UTC

Ensure that certificates are correctly managed.

When the certificates relation is ready before the
HA relation is clustered, the VIP symlinks will not
be created pointing at the correct certificates. This
change updates the HA handlers to ensure that the
certificate relation is handled after clustering,
if there are any certificate relations.

There was no functional test coverage for HA and TLS
deployments so this change also add a test for
those and CMR too. Having said that, the test
initialises vault once the deployments are
complete so is unlikely to trigger #1886077 the tests
to check there is no regression of existing
functionality.

func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/389

Change-Id: I7c9c81318dbbcea618ac3781b8f19e8159e56bcb
Closes-Bug: #1886077
(cherry picked from commit b9905a9d3239fa59c18b4eaa25c44d02918c5c8c)
stable/20.05 2020-05-21 17:00:04 UTC
Updates for stable branch creation

Author: David Ames
Author Date: 2020-05-21 16:59:59 UTC

Updates for stable branch creation

Set default branch for git review/gerrit.

Switch tests to stable.

Switch to using stable charm-helpers branch.

Switch to using stable charm.openstack branch.

Change-Id: I3d22d9bc468047530295deba92b7f4cea05f37fa
stable/20.02 2020-04-01 14:32:49 UTC
Fix CONFIGS=None issue with action openstack-upgrade

Author: Alex Kavanagh
Author Date: 2020-03-31 14:29:14 UTC

Fix CONFIGS=None issue with action openstack-upgrade

When the CONFIGS was made lazy in the charm, unfortunately, some of the
work wasn't carried through correctly to the openstack-upgrade action
code. This patch corrects that. Tested manually as okay.

Change-Id: I095613ef2eca62da5fae5462e76fa83926d2e80a
Closes-Bug: #1869865
(cherry picked from commit 851821ff39a66fcdd75b414427b64c2979ba8bb7)
stable/19.10 2019-11-25 14:43:56 UTC
Remove Set-Cookie .... HttpOnly;secure to allow CSRF access

Author: Alex Kavanagh
Author Date: 2019-11-25 13:05:40 UTC

Remove Set-Cookie .... HttpOnly;secure to allow CSRF access

Angular (running in the page) can't access the CSRF token if the cookie
is set to secure. This is a temporary patch to resolve the issue whilst
a more permanent fix is found.

This reverts patch I1ded951d79ad9fa832d1e88f656a1e064b1ef007
(essentially).

Change-Id: Ied9d0f5486c260a17da9375ec6347d0952154225
Related-Bug: #1822751
Closes-Bug: #1853173
stable/19.07 2019-08-12 16:43:25 UTC
Updates for stable branch creation

Author: David Ames
Author Date: 2019-08-12 16:43:21 UTC

Updates for stable branch creation

Set default branch for git review/gerrit.

Switch amulet tests to stable.

Switch to using stable charm-helpers branch.

Change-Id: I3d6ee776a1b230dff839a411dfb71ab885f8b502
stable/19.04 2019-05-07 23:14:39 UTC
Merge "Fix incorrect policy rules" into stable/19.04

Author: Zuul
Author Date: 2019-05-07 23:14:39 UTC

Merge "Fix incorrect policy rules" into stable/19.04
stable/18.02 2019-04-19 19:34:48 UTC
OpenDev Migration Patch

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:34:48 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
stable/18.05 2019-04-19 19:34:48 UTC
OpenDev Migration Patch

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:34:48 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
stable/18.08 2019-04-19 19:34:48 UTC
OpenDev Migration Patch

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:34:48 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
stable/18.11 2019-04-19 19:34:48 UTC
OpenDev Migration Patch

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:34:48 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
stable/17.11 2019-04-19 19:34:47 UTC
OpenDev Migration Patch

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:34:47 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
stable/17.08 2019-04-19 19:34:47 UTC
OpenDev Migration Patch

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:34:47 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
stable/17.02 2019-04-19 19:34:47 UTC
OpenDev Migration Patch

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:34:47 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
stable/16.10 2019-04-19 19:34:47 UTC
OpenDev Migration Patch

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:34:47 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
stable/16.07 2019-04-19 19:34:47 UTC
OpenDev Migration Patch

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:34:47 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
stable/16.04 2019-04-19 19:34:47 UTC
OpenDev Migration Patch

Author: OpenDev Sysadmins
Author Date: 2019-04-19 19:34:47 UTC

OpenDev Migration Patch

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
1 → 33 of 33 results First • Previous • Next • Last

Other repositories

Name Last Modified
lp:charm-openstack-dashboard 22 hours ago
lp:~ec0/charm-openstack-dashboard 2017-05-18
1 → 2 of 2 results First • Previous • Next • Last
You can't create new repositories for OpenStack Dashboard Charm.