DB Migration Tool
Tacker supports multi-version API: v1 API based on SOL 003 v2.6.1 [1] and v2 API based on v3.3.1 [2]. Since v2 API doesn't have backward compatibility for v1 API, the v1 API users who want to shift from v1 API to v2 API have to terminate their VNF once and re-instantiate them with v2 API. However, this will incur a service outage and thus not realistic. Moreover, some VNFs run for more than 5 years, which consequently means that Tacker cannot deprecate an old API version for more than 5 years. This can be a barrier to the future update roadmap of Tacker when it plans to implement a new ETSI SOL release, e.g., Rel. 4. This is simply because, without the deprecation of an old API, the maintenance cost increases as the supported versions increase.
This BP proposes to provide the migration tool for API version update from the Tacker community e.g., a DB migration tool for updating from v1 API to v2 API.
[1] https:/
[2] https:/
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Hiromu Asahina
- Direction:
- Needs approval
- Assignee:
- Masaki Oyama
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Fix db-migration-tool issues
