Package repository locations are hardcoded in many Fuel components and build scripts

[Vladimir Kozhukalov]

We need to have a single data source from where all fuel components will get default repositories. Openstack.yaml can be such single data source.

Update: as discussed in the comments, openstack.yaml might not be suitable as single data source.

[Ihor Kalnytskyi (ikalnytskyi)]

Why 7.0? It's tech-debt, I think it should be done in 8.0.

[Vladimir Kozhukalov (kozhukalov)]

After thinking of this a little bit and discussing this with others I changed my mind. It does not look rational to use openstack.yaml both for deployment and for bootstrap image building repos. Bootstrap is to be totally independent from deployment, so it is better to have a separate config file for it.

[Dmitry Borodaenko (angdraug)]

Discarding openstack.yaml as the single data source does not invalidate the whole bug. Hardcoded package repo locations are a problem, and we need to find a way to address it.

[Vladimir Kozhukalov (kozhukalov)]

You are right about hardcoded repos, but the only place where they hardcoded is the build script for ubuntu bootstrap. We have a separate bug for this https://bugs.launchpad.net/fuel/+bug/1486551 Once it is fixed we will have two places where default repos are defined. Still it is better to have a single place for such things but the priority is not high, rather medium and milestone is 8.0 (it is rather a feature request)