Open Stack

Guys, we are next to moving fuel_agent directory into a separate
repository. Action flow is going to be as follows:

1) Create verify jobs on our CI https://review.fuel-infra.org/#/c/9186
(DONE)
2) Freeze fuel_agent directory in https://github.com/stackforge/fuel-web
(will announce in a separate mail thread). That means we stop merging
patches into master which change fuel_agent directory. Unfortunately, all
review requests need to be re-sent, but it is not going to be very
difficult.
3) Create temporary upstream repository with fuel_agent/* as a content. I'm
not planning to move 5.x and 6.x branches. Only master. So, all fixes for
5.x and 6.x will be living in fuel-web.
4) This upstream repository is going to be sucked in by openstack-infra.
Patch is here https://review.openstack.org/#/c/199178/ (review is welcome)
I don't know how long it is going to take. Will try to poke infra people to
do this today.
5) Then we need to accept two patches into new fuel-agent repository:
 - rpm spec (extraction from fuel-web/specs/nailgun.spec) (ready, but there
is no review request)
 - run_tests.sh (to run tests) (ready, but there is no review request)

!!! By this moment there won't be any impact on ISO build process !!!

6) Then we need to change two things at the same time (review is welcome)
  - fuel-web/specs/nailgun.spec in order to prevent fuel-agent package
building  https://review.openstack.org/#/c/200595
  - fuel-main so as to introduce new fuel-agent repository into the build
process https://review.openstack.org/#/c/200025

And good luck to me -)


Vladimir Kozhukalov

On Wed, Jul 8, 2015 at 12:53 PM, Vladimir Kozhukalov <
vkozhukalov at mirantis.com> wrote:

> There were some questions from Alexandra Fedorova about independent
> release cycle.
>
> >according to the configuration [1] Infra team won't be able to do
> >branching or any kind of release management for new repository.
>
> >Could you please clarify, do we plan to version new repository the
> >same way as we do for main fuel repositories or there going to be
> >separate releases as in python-fuelclient [2]? Who should drive the
> >release process for this repo and how this change will affect Fuel ISO
> >release?
>
> >[1]
> https://review.openstack.org/#/c/199178/1/gerrit/acls/stackforge/fuel-agent.config,cm
> >[2]
> http://lists.openstack.org/pipermail/openstack-dev/2015-July/068837.html
>
> IMO all Fuel components should be as much independent as possible with
> highly defined APIs used for their interaction, with their own teams, with
> their own independent release cycles. But we cannot switch to this model
> immediately. For the start, we can just move those components into separate
> repositories, leaving the same access rights and core team as we have for
> fuel-web.
>
> When Fuel Agent is a separate repository we discuss team. It looks like a
> team leader is the best person to manage releases for a particular
> component. This thread is totally about separation stuff and how to do this
> not breaking anything.
>
>
>
> Vladimir Kozhukalov
>
> On Wed, Jul 8, 2015 at 12:24 PM, Vladimir Kozhukalov <
> vkozhukalov at mirantis.com> wrote:
>
>> Dear colleagues,
>>
>> I am going to move Fuel Agent into a separate git repository. The thing
>> is that we have quite a few review requests to fuel-web with changes for
>> Fuel Agent. The new repository is going to look like this
>> https://github.com/kozhukalov/fuel-agent i.e. there is no additional
>> sub-directory fuel_agent. In fact, I don't think it is a big deal to update
>> all fuel agent related review requests.
>>
>> Work items:
>> 0) request to openstack-infra https://review.openstack.org/#/c/199178/1
>> 0.1) upstream for this request with commit history
>> https://github.com/kozhukalov/fuel-agent
>> 1) fuel-agent/specs/fuel-agent.spec is an extraction from
>> fuel-web/specs/nailgun.spec (separate commit, in progress)
>> 2) modify fuel-main to build fuel-agent package (in progress)
>> 3) create jenkins-jobs/servers/fuel-ci/verify-fuel-agent.yaml (in
>> progress)
>>
>> For the start Fuel Agent core team will be the same as in fuel-web.
>>
>> If there is anything I forgot, please remind me about that.
>>
>> Vladimir Kozhukalov
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150710/81913bf5/attachment.html>