Please review this patch [1]. It is to remove the code from master branch. We still need test jobs for stable branches.
[1] https://review.openstack.org/#/c/335868/ Vladimir Kozhukalov On Mon, Jun 27, 2016 at 1:14 PM, Vladimir Kozhukalov < [email protected]> wrote: > Fuel-mirror python module itself will be removed from fuel-mirror > repository, but perestroika is to be there until Packetary is able to > substitute perestroika totally (work is now in progress). > > Just a reminder: According to our plan Packetary is to cover the whole > rpm/deb domain including building deb/rpm packages and repositories. > Sincing these repos over multiple locations as well as tracking repository > snapshots will be a matter of Trsync project (Fuel infra team project). > > Vladimir Kozhukalov > > On Mon, Jun 27, 2016 at 11:38 AM, Igor Kalnitsky <[email protected]> > wrote: > >> Vladimir, >> >> 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 [1]? >> It seems strange that fuel-mirror contains them. >> >> Thanks, >> Igor >> >> [1] https://github.com/openstack/fuel-mirror/tree/master/perestroika >> >> >> > On Jun 23, 2016, at 13:31, Vladimir Kozhukalov < >> [email protected]> 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 [0]. 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 [1] package and were introduced >> by this [2] patch. >> > >> > >> > [0] https://wiki.openstack.org/wiki/Packetary >> > [1] https://github.com/openstack/python-fuelclient >> > [2] https://review.openstack.org/#/c/326435/ >> > >> > >> > Vladimir Kozhukalov >> > >> __________________________________________________________________________ >> > OpenStack Development Mailing List (not for usage questions) >> > Unsubscribe: >> [email protected]?subject:unsubscribe >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
