On Fri, Oct 4, 2019 at 9:41 AM Corey Bryant <corey.bryant@canonical.com> wrote:
Hi All,
I'd like to see if I can get some input on the current state of the Placement API split.
For some background, the nova placement API was removed from nova in train, and it's been split into its own project. It's mostly just a basic API charm. The tricky part is the migration of tables from the nova_api database to the placement database.
Code is located at: https://github.com/coreycb/charm-placement https://github.com/coreycb/charm-interface-placement
https://review.opendev.org/#/q/topic:charms-train-placement+(status:open+OR+...)
Test scenarios I've been testing with: 1) deploy nova-cc et al train, configure keystonev3, deploy instance 2) deploy nova-cc et al stein, configure keystonev3, deploy instance 1, deploy placement train, deploy instance 2, upgrade nova-cc to train, deploy instance 3
There is currently an issue with the second test scenario where instance 2 creation errors because nova-scheduler can't find a valid placement candidate (not sure of the exact error atm). However if I delete instance 1 before creating instance 2 it is created successfully. It feels like a DB related issue but I'm really not sure so I'll keep digging.
Thanks! Corey
In case anyone needs these for testing prior to the code getting merged I've pushed placement and nova-cloud-controller charms to the charm store under my namespace. I've released them to the edge channel. https://jaas.ai/u/corey.bryant/placement/bionic/0 https://jaas.ai/u/corey.bryant/nova-cloud-controller/bionic/0 Thanks, Corey