Move Perestroika code to stackforge/perestroika git repository

Bug #1489470 reported by Vladimir Kozhukalov
6
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.

Tags: area-build
description: updated
Roman Vyalov (r0mikiam)
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
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

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).

Changed in fuel:
assignee: Dmitry Burmistrov (dburmistrov) → Sergey Kulanov (skulanov)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-mirror (master)

Fix proposed to branch: master
Review: https://review.openstack.org/235885

Changed in fuel:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-mirror (master)

Reviewed: https://review.openstack.org/235885
Committed: https://git.openstack.org/cgit/openstack/fuel-mirror/commit/?id=05d86902d57fb1dfb1b764b140148a03908ebe4b
Submitter: Jenkins
Branch: master

commit 05d86902d57fb1dfb1b764b140148a03908ebe4b
Author: Sergey Kulanov <email address hidden>
Date: Fri Oct 16 15:14:00 2015 +0300

    [perestroika] Inject perestroika into fuel-mirror

    While we have migration of perestroika to Python implementation
    we need to have friendly and open way to share and fix issues
    in current perestroika code

    Change-Id: I7fced52ddadc81d4d8a52659358936f6e68cc3e4
    Closes-bug: #1489470

Changed in fuel:
status: In Progress → Fix Committed
Dmitry Pyzhov (dpyzhov)
tags: added: area-build
Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Related fix proposed to fuel-infra/jenkins-jobs (master)

Related fix proposed to branch: master
Change author: Sergey Kulanov <email address hidden>
Review: https://review.fuel-infra.org/13176

Revision history for this message
Fuel Devops McRobotson (fuel-devops-robot) wrote : Related fix merged to fuel-infra/jenkins-jobs (master)

Reviewed: https://review.fuel-infra.org/13176
Submitter: Dmitry Kaigarodsev <email address hidden>
Branch: master

Commit: a9284c49ebe51f5d25a123efda24c2056d83a8dc
Author: Sergey Kulanov <email address hidden>
Date: Thu Nov 26 09:39:50 2015

Switch CI to use perestroika code from fuel-mirror repo

1) Use perestroika code from fuel-mirror:

  https://github.com/openstack/fuel-mirror/tree/master/perestroika

2) We have small workaround for now, since perestroika should
start from ${WORKSPACE} root, so in SCM we clone fuel-mirror to

   ${WORKSPACE}/fuel-mirror

and then copy perestroika code to ${WORKSPACE} root

  cp -rv ${WORKSPACE}/fuel-mirror/perestroika/* ${WORKSPACE}

Change-Id: I2b4752610365fd30bc9ca8e63109798f500c8afe
Related-bug: #1489470

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.