I have spent some time during the weekend thinking about the options here. Looking at the requirements from all parties, I see the following: a) From the packaging side, we want to split Glance into several packages (glance,-common,-api and -registry). b) From the deployment side, we want the glance package to behave as it did before, i.e. pull -api and -registry. c) From the puppet-glance side, if we have separate -api and -registry packages, we want to reflect that change in the Puppet modules and be able to configure -api and -registry independently. Also, this package split is already happening in Debian/Ubuntu, so removing distro-specific code is always welcome. With that in mind, I think the following options as the easiest ones to implement: 1- Split packages, with the following deps: * -api and -registry depend on -common * glance depends on -api and -registry This would require moving the existing content in glance (/usr/bin/glance-manage and /usr/bin/glance-control) into -common, so glance becomes a meta-package. With this, we would get b) and c), and most of a). The only drawback is that glance-manage and glance-control may not be a good fit for the -common package (Haikel, can you comment on this?). FWIW, this is how it is being packaged today in Debian. 2- Keep the old situation (no Glance package split) This obviously negates a), and keeps distro-specific code in c), but still works and does not break any existing code. Any thoughts? Regards, Javier