[openstack-dev] [Fuel] Separate repo for Fuel Agent

Vladimir Kozhukalov vkozhukalov at mirantis.com
Wed Jul 8 09:53:26 UTC 2015

There were some questions from Alexandra Fedorova about independent release

>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


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

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/20150708/3fcc326d/attachment.html>

More information about the OpenStack-dev mailing list