Comment 13 for bug 1421230

Hi Kevin, no worries! That's a bit my fault for not resetting the bug status, so there's plenty of blame to go around. ;)

So the key purpose of calico-origin is to ensure that if you are, say, deploying OpenStack Kilo we use the Kilo PPA (ppa:project-calico/kilo) rather than the Icehouse PPA. This unfortunate situation is because we have some patches to Nova/Neutron that we need to deploy, and for obvious reasons it's better to do that using the PPA system than to do some terrible install-time patch logic. In the *long* term this need should go away (we've landed our Nova patches into Liberty, but our Neutron patches are not yet integrated upstream), but for now we do need to know what OpenStack release we're going into.

If there's a good central location we can find that information on (e.g. over the relation with neutron-api) I'd be happy to change the charm to use that relation. Otherwise, I think the neutron-calico charm needs *some* information.

Either way, I think for the short term the answer is to, on config-changed, do an apt-add-repository and then apt-upgrade. That should ensure that we pick up any change the user performs to do *upgrade*, at the very least.