Neutron Dynamic Routing Agent
- OpenStack Charmers
- Cloud
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/stable | 35 | 09 Dec 2021 | |
latest/stable | 25 | 09 Dec 2021 | |
latest/stable | 20 | 09 Dec 2021 | |
latest/stable | 15 | 11 Nov 2020 | |
latest/candidate | 34 | 21 Oct 2021 | |
latest/edge | 88 | 18 Nov 2024 | |
latest/edge | 87 | 18 Nov 2024 | |
latest/edge | 86 | 18 Nov 2024 | |
latest/edge | 85 | 18 Nov 2024 | |
latest/edge | 76 | 26 Mar 2024 | |
latest/edge | 75 | 26 Mar 2024 | |
latest/edge | 74 | 26 Mar 2024 | |
latest/edge | 73 | 26 Mar 2024 | |
latest/edge | 72 | 03 Oct 2023 | |
latest/edge | 71 | 03 Oct 2023 | |
latest/edge | 68 | 03 Oct 2023 | |
latest/edge | 67 | 03 Oct 2023 | |
latest/edge | 66 | 03 Oct 2023 | |
latest/edge | 64 | 03 Oct 2023 | |
latest/edge | 62 | 03 Oct 2023 | |
latest/edge | 61 | 03 Oct 2023 | |
latest/edge | 60 | 21 Jun 2023 | |
latest/edge | 59 | 21 Jun 2023 | |
latest/edge | 58 | 21 Jun 2023 | |
latest/edge | 57 | 21 Jun 2023 | |
xena/edge | 45 | 12 Apr 2022 | |
wallaby/edge | 46 | 25 Feb 2022 | |
wallaby/edge | 42 | 22 Feb 2022 | |
wallaby/edge | 38 | 22 Feb 2022 | |
victoria/edge | 46 | 25 Feb 2022 | |
victoria/edge | 42 | 22 Feb 2022 | |
victoria/edge | 39 | 22 Feb 2022 | |
ussuri/edge | 40 | 22 Feb 2022 | |
queens/edge | 48 | 25 Feb 2022 | |
queens/edge | 43 | 22 Feb 2022 | |
2024.1/candidate | 80 | 01 Jun 2024 | |
2024.1/candidate | 79 | 01 Jun 2024 | |
2024.1/candidate | 78 | 01 Jun 2024 | |
2024.1/candidate | 77 | 01 Jun 2024 | |
2024.1/candidate | 71 | 24 Jan 2024 | |
2024.1/candidate | 68 | 24 Jan 2024 | |
2024.1/candidate | 64 | 24 Jan 2024 | |
2024.1/candidate | 62 | 24 Jan 2024 |
juju deploy neutron-dynamic-routing
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
24.04
23.10
23.04
22.10
22.04
21.10
21.04
20.10
20.04
+5
-
openstack-upgrade
Perform openstack upgrades. Config option action-managed-upgrade must be set to True.
-
pause
Pause services. If the deployment is clustered using the hacluster charm, the corresponding hacluster unit on the node must first be paused as well. Not doing so may lead to an interruption of service.
-
restart-services
Restart services. Restart the services the charm manages.
-
resume
Resume services. If the deployment is clustered using the hacluster charm, the corresponding hacluster unit on the node must be resumed as well.