[openstack-dev] [Fuel] Deprecation of fuel-mirror tool
ikalnitsky at mirantis.com
Mon Jun 27 08:38:34 UTC 2016
Thanks for driving this! What about fuel-mirror itself? Does it mean it's deprecated? If so, what will happen to perestroika scripts inside it ? It seems strange that fuel-mirror contains them.
> On Jun 23, 2016, at 13:31, Vladimir Kozhukalov <vkozhukalov at mirantis.com> wrote:
> Dear colleagues.
> I'd like to announce that fuel-mirror tool is not going to be a part of Fuel any more. Its functionality is to build/clone rpm/deb repos and modify Fuel releases repository lists (metadata).
> Since Fuel 10.0 it is recommended to use other available tools for managing local deb/rpm repositories.
> Packetary is a good example . Packetary is ideal if one needs to create a partial mirror of a deb/rpm repository, i.e. mirror that contains not all available packages but only a subset of packages. To create full mirror it is better to use debmirror or rsync or any other tools that are available.
> To modify releases repository lists one can use commands which are to available by default on the Fuel admin node since Newton.
> # list of available releases
> fuel2 release list
> # list of repositories for a release
> fuel2 release repos list <release_id>
> # save list of repositories for a release in yaml format
> fuel2 release repos list <release_id> -f yaml | tee repos.yaml
> # modify list of repositories
> vim repos.yaml
> # update list of repositories for a release from yaml file
> fuel2 release repos update <release_id> -f repos.yaml
> They are provided by python-fuelclient  package and were introduced by this  patch.
>  https://wiki.openstack.org/wiki/Packetary
>  https://github.com/openstack/python-fuelclient
>  https://review.openstack.org/#/c/326435/
> Vladimir Kozhukalov
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev