No, because it's a sqlitedb per unit of charm. So a charm collocated on the same machine will still have its own state.
Can I ask what you're looking to achieve? Marco On Tue, Apr 18, 2017, 10:05 fengxia <[email protected]> wrote: > Replying my own question: > > charmhelpers.core.unitdata shows how states are stored -- > "reactive.state.xyz" is saved in a sqlite3 as a string. So if split > states in multiple charms, I think it will still work if deploying these > charms to the same unit because they will be registered in the same DB. > > Can someone verify this? > > On 04/18/2017 08:50 AM, fengxia wrote: > > I did a quick experiment: > > > > 1. Created two layers in one charm, each layer has a few states, > > set_state() can trigger @when defined in other layers. > > > > 2. Use the same set of states, now splitting them in two charms => > > @when don't trigger anymore. > > > > So does this mean states have a namespace by the charm it belongs? > > > > -- > Feng xia > Engineer > Lenovo USA > > Phone: 5088011794 > [email protected] > > Lenovo.com > Twitter | Facebook | Instagram | Blogs | Forums > > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
