[OpenStack-Infra] Migrate Fuel repo to StackForge

Matthew Mosesohn mmosesohn at mirantis.com
Mon Dec 9 14:47:44 UTC 2013


Mordred,

Yes, of course. If anyone finds a big interest in this tool and wants
to give it a more generic, useful name, we could revisit this topic.
For now, fuel-devops is absolutely acceptable.

On Mon, Dec 9, 2013 at 6:39 PM,  <mordred at inaugust.com> wrote:
> Hey Matthew!
>
> Awesome. Could we call devops fuel-devops? Devops seems a bit generic (I don't feel strongly, just seems like an odd match)
>
> On Dec 9, 2013 3:34 PM, Matthew Mosesohn <mmosesohn at mirantis.com> wrote:
>>
>> Hi Infra team!
>>
>> We're interested in migrating all of the Fuel project to StackForge
>> because we really find the gerrit workflow to be beneficial for
>> development. Earlier there were some reservations about importing the
>> main Fuel Git repository to Stackforge, and instead submit several
>> separate puppet modules as independent repos (similar to
>> PuppetLabs/Puppet Forge) style. We're under heavy development and our
>> deployment relies on all puppet modules being locked in sync together
>> in a single repo. One concern is that the majority of our code
>> consists of forks of other open source Puppet modules. We're slowly
>> working through and contributing our enhancements upstream and expect
>> that in a few months we will be 100% in sync with upstream, and
>> probably using a system like puppet-librarian to compile Fuel. In
>> speaking with Jeremy Stanley, he seemed to agree that this was a fair
>> solution.
>>
>> In addition, we have two more project I would like to put in
>> StackForge. The first we call "devops"
>> (https://github.com/Mirantis/devops )which is a simple Django
>> application that uses python-libvirt and paramiko to create, destroy,
>> and snapshot groups of virtual machines, networks, and allocate local
>> storage. It currently has no application outside of Fuel because it is
>> designed to launch our deployment testing scripts, but it could be
>> adapted if others are interested.
>>
>> The second is fuel-docs (https://github.com/Mirantis/fuel-docs ). It
>> contains our end-user documentation (devel docs are in fuel-web
>> already in StackForge). While I realize that most projects do
>> documentation in the same repo as the main project repo, Fuel is
>> broken up into many parts, and we decided to build docs separately.
>>
>> In summary, I am requesting these 3 Git repositories to be migrated to
>> StackForge:
>> https://github.com/Mirantis/fuel
>> https://github.com/Mirantis/devops
>> https://github.com/Mirantis/fuel-docs
>> These groups should be managed by group fuel-core (already exists).
>>
>> If there are objections or concerns about the content of these repos,
>> feel free to raise them and I promise to do my best to address them.
>> Thank you for your continued help, Infra team.
>>
>> Best Regards,
>> Matthew Mosesohn
>>
>> _______________________________________________
>> OpenStack-Infra mailing list
>> OpenStack-Infra at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>



More information about the OpenStack-Infra mailing list