Open Stack

On Fri, May 20, 2016 at 2:31 PM, Simon Pasquier <spasquier at mirantis.com>
wrote:

> Hello,
> You can find the rationale in the review [1] importing m.o.f. into o.t.m.
> Basically it was asked by the operators community to avoid the sprawl of
> repositories.
> BR,
> Simon
> [1] https://review.openstack.org/#/c/248352/
>

Thanks Simon,

  so from "This import will probably lead to the end of
monitoring-for-openstack project" it seems that project deletion just was
not performed at the end. Is anybody against submitting patch to
openstack-infra to delete the project?

Regards,
Martin


>
>
> On Fri, May 20, 2016 at 11:08 AM, Martin Magr <mmagr at redhat.com> wrote:
>
>> Greetings guys,
>>
>>   there is a duplication of code within openstack/osops-tools-monitoring
>> and openstack/monitoring-for-openstack projects.
>>
>> It seems that m-o-f became part of o-t-m, but the former project wasn't
>> deleted. I was just wandering if there is a reason for the duplication (or
>> fork, considering the projects have different core group maintaining each)?
>>
>> I'm assuming that m-f-o is just a leftover, so can you guys tell me what
>> was the reason to create one project to rule them all (eg.
>> openstack/osops-tools-monitoring) instead keeping the small projects
>> instead?
>>
>> Thanks in advance for answer,
>> Martin
>>
>> --
>> Martin Mágr
>> Senior Software Engineer
>> Red Hat Czech
>>
>
>


-- 
Martin Mágr
Senior Software Engineer
Red Hat Czech
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160520/73fdc210/attachment.html>