Open Stack

Hi, Vladimir,

I like the initiative, just to add some steps:

10) patch to fuel-qa/ and jenkins jobs to change the workflow of upgrades tests,
11) clarification on how upgrade should be tested (against which
repositories and ISO images), how update of upgrade rpm should be
tested
12) documentation fixes on how upgrade should be performed,
13) patch to HCF and release checklists to change publishing process.

I see the 11) as the most unclear here, so please include it in your
considerations with high priority. Let's involve QA team from the very
beginning.



On Thu, Jul 16, 2015 at 11:46 AM, Vladimir Kozhukalov
<vkozhukalov at mirantis.com> wrote:
> By the way, first step for this to happen is to move
> stackforge/fuel-web/fuel_upgrade_system into a separate repository.
> Fortunately, this directory is not the place where the code is continuously
> changing (changes are rather seldom) and moving this project is going to
> barely affect the whole development flow. So, action flow is as follows
>
> 0) patch to openstack-infra for creating new repository (workflow -1)
> 1) patch to Fuel CI to create verify jobs
> 2) freeze stackforge/fuel-web/fuel_upgrade_system directory
> 3) create upstream repository which is to be sucked in by openstack infra
> 4) patch to openstack-infra for creating new repository (workflow +1)
> 5) patch with rpm spec for fuel-upgrade package and other infrastructure
> files like run_tests.sh
> 6) patch to perestroika to build fuel-upgrade package from new repo
> 7) patch to fuel-main to remove upgrade tarball
> 8) patch to Fuel CI to remove upgrade tarball
> 9) patch to fuel-web to remove fuel_upgrade_system directory
>
>
>
> Vladimir Kozhukalov
>
> On Thu, Jul 16, 2015 at 11:13 AM, Vladimir Kozhukalov
> <vkozhukalov at mirantis.com> wrote:
>>
>> Dear colleagues,
>>
>> I'd like to suggest to get rid of Fuel upgrade tarball and convert this
>> thing into fuel-upgrade rpm package. Since we've switched to online rpm/deb
>> based upgrades, it seems we can stop packaging rpm/deb repositories and
>> docker containers into tarball and instead package upgrade python script
>> into rpm. It's gonna decrease the complexity of build process as well as
>> make it a little bit faster.
>>
>> What do you think of this?
>>
>>
>> Vladimir Kozhukalov
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Aleksandra Fedorova
Fuel CI Engineer
bookwar