Comment 8 for bug 1516156
Revision history for this message
| Armando Migliaccio (armando-migliaccio) wrote Re: IPAM migration from non-pluggable to pluggable | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Hi Pavel, thanks for the initial investigation. Though I believe a few folks are generally positive about the initiative (see [1] for more details). I am unclear on a number of areas:
- Is the migration workflow to be performed on a live system and driven by API calls? Or the admin is intended to invoke a script that takes care of the data/schema migration only? In either case, is there a data plane migration that needs to occur first? Or existing workload remains unaffected?
- Are we suggesting that this migration is merely targeted to migrating the reference IPAM implementation, ie. from reference non-pluggable one to reference pluggable one?
- Idle curiosity, is it possible to switch from one pluggable IPAM solution to another (pluggable one)?
We should be clear about the objectives for this migration exercise, ie. that this migration effort is solely aimed at deprecating and removing the non-pluggable reference implementation.
[1] http://