master
stable/wallaby
stable/yoga
stable/zed
stable/2023.1
stable/xena
stable/train
stable/ussuri
stable/victoria
xena-em
12.0.0
12.0.0.0rc2
12.0.0.0rc1
9.1.0
wallaby-em
11.0.0
11.0.0.0rc1
victoria-em
10.0.0
10.0.0.0rc1
7.1.2
9.0.1
8.0.1
ussuri-em
6.2.2
9.0.0
9.0.0.0rc1
6.2.1
train-em
5.1.2
8.0.0
8.0.0.0rc2
8.0.0.0rc1
6.2.0
5.1.1
7.1.1
stein-eol
7.1.0
5.1.0
stein-em
4.1.4
6.1.0
5.0.3
7.0.0
7.0.0.0rc1
queens-eol
rocky-eol
4.1.3
5.0.2
6.0.1
4.1.2
pike-eol
ocata-eol
6.0.0
6.0.0.0rc1
rocky-em
3.2.2
5.0.1
4.1.1
3.2.1
queens-em
5.0.0
5.0.0.0rc2
4.1.0
3.2.0
2.1.2
5.0.0.0rc1
4.0.1
3.1.1
2.1.1
pike-em
1.0.5
3.1.0
2.1.0
ocata-em
4.0.0
4.0.0.0rc3
4.0.0.0rc2
4.0.0.0rc1
2.0.4
3.0.2
2.0.3
1.0.4
3.0.1
1.0.3
2.0.2
3.0.0
3.0.0.0rc3
3.0.0.0rc2
3.0.0.0rc1
3.0.0.0b3
3.0.0.0b2
3.0.0.0b1
2.0.1
1.0.2
2.0.0
2.0.0.0rc2
2.0.0.0rc1
2.0.0.0b3
2.0.0.0b2
2.0.0.0b1
newton-eol
0.9.2
1.0.1
1.0.0
1.0.0.0rc2
1.0.0.0rc1
1.0.0.0b3
mitaka-eol
1.0.0.0b2
1.0.0.0b1
liberty-eol
0.10.0
0.8.1
0.9.1
0.9.0
0.8.0
0.5.2
0.5.1
0.5.0
${ noResults }
3 Commits (d9e029960d34b451c492cea35a46e2e05fcc6f8b)
Author | SHA1 | Message | Date |
---|---|---|---|
![]() |
9c13499d21 |
Jobboard based controller
Introduce TaskFlowServiceController which uses taskflow jobboard feature and saves jobs info into persistence backend. Jobboard could be operated via RedisTaskFlowDriver or ZookeeperTaskFlowDriver, that could be set via the config. RedisTaskFlowDriver is intoduced as default backend for jobboard. Usage of jobboard allows to resume jobs in case of restart/stop of Octavia controller services. Persistence backend saves state of flow tasks that required in case of resuming job. SQLAlchemy backend is used here. Bump taskflow version to 3.7.1 and add dependency to SQLAlchemy-Utils (required for taskflow sqlalchemy backend support). Story: 2005072 Task: 30806 Task: 30816 Task: 30817 Change-Id: I92ee4e879e98e4718d2e9aba56486341223a9157 |
3 years ago |
![]() |
215c4c2284 |
Fix controller worker graceful shutdown
Fix an issue that prevents graceful shutdown of controller workers. cotyledon.Service.terminate function is by definition the graceful termination function and doesn't have any 'graceful' optional boolean argument (https://cotyledon.readthedocs.io/en/latest/api.html). Because of this error, message_listener.wait() was never called in the consumers' termination functions, so flows could be interrupted before completion and could leave resources such as load balancer in a PENDING_* provisioning state. By default cotyledon.Service terminates the server after a timeout if the worker could not shutdown itself gracefully. The default value for the timeout is 300 seconds (set in devstack plugin) and can be overriden using the graceful_shutdown_timeout setting in octavia.conf The default value will be updated to a lower value when work on persistant taskflow will be merged. Story: 2006603 Task: 36770 Change-Id: I3f776bd018246897c9a889699a2d0ecbbfbb7098 |
4 years ago |
![]() |
0ab16921ae |
Create Amphora V2 provider driver
This patch creates an Amphora v2 provider driver as well as a V2 controller worker. This is in preparation for having the amphora driver use the new provider driver data models and rely less on native Octavia database access. It is also a prepartion step for enabling TaskFlow JobBoard as this work will move to storing dictionaries in the flows instead of database models. Change-Id: Ia65539a8c39560e2276750d8e79a637be4c0f265 Story: 2005072 Task: 30806 |
4 years ago |