Move Perestroika code to stackforge/perestroika git repository
Bug #1489470 reported by
Vladimir Kozhukalov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Medium
|
Sergey Kulanov |
Bug Description
fuel-mirror repository was created with the intention behind to host all mirror related code there, including Perestroika. Dealing with mirrors and packages requires specific knowledge and placing this piece of expertise into a separate dedicated project looks reasonable. It is also important to keep it open how we build mirrors and packages.
description: | updated |
Changed in fuel: | |
status: | New → Triaged |
Changed in fuel: | |
assignee: | Fuel build team (fuel-build) → Dmitry Burmistrov (dburmistrov) |
summary: |
- Move Perestroika code to fuel-mirror git repository + Move Perestroika code to stackforge/perestroika git repository |
Changed in fuel: | |
assignee: | Dmitry Burmistrov (dburmistrov) → Sergey Kulanov (skulanov) |
tags: | added: area-build |
To post a comment you must log in.
Please apply Occam's razor and do not unnecessarily multiply entities. In its current state Perestroika is a set of shell scripts that is tightly coupled to Fuel, which fits the fuel-mirror repository just fine. As we convert Perestroika into a Python project covered with unit tests and compliant with OpenStack PTI (http:// governance. openstack. org/reference/ project- testing- interface. html), we should also expand its scope to cover the functionality of other package repository handling scripts that exist in fuel-mirror. At that point, we will be able to just rename fuel-mirror to fuel-perestroika (if it remains Fuel specific) or to just openstack/ perestroika (if it becomes useful on its own without Fuel).