<p dir="ltr"><br>
On Jan 8, 2014 9:58 PM, "Georgy Okrokvertskhov" <<a href="mailto:gokrokvertskhov@mirantis.com">gokrokvertskhov@mirantis.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> I do understand why there is a push back for this patch. This patch is for infrastructure project which works for multiple projects. Infra maintainers should not know specifics of each project in details. If this patch is a temporary solution then who will be responsible to remove it? <br>
></p>
<p dir="ltr">I am not sure who is responsible for solum related configurations in infra project. I see that almost all the infra config for solum project is done by solum members. So I think any solum member can submit a patch to revert this once we have a permanent solution.</p>
<p dir="ltr">> If we need start this gate I propose to revert all patches which led to this inconsistent state and apply workaround in Solum repository which is under Solum team full control and review. We need to open a bug in Solum project to track this.<br>
></p>
<p dir="ltr">The problematic patch [1] solves a specific problem. Do we have other ways to solve it?</p>
<p dir="ltr">Regards,<br>
Noorul</p>
<p dir="ltr">[1] <a href="https://review.openstack.org/#/c/64226">https://review.openstack.org/#/c/64226</a></p>
<p dir="ltr">> Thanks<br>
> Georgy<br>
><br>
><br>
> On Wed, Jan 8, 2014 at 7:09 AM, Noorul Islam K M <<a href="mailto:noorul@noorul.com">noorul@noorul.com</a>> wrote:<br>
>><br>
>> Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a>> writes:<br>
>><br>
>> > On Wed, Jan 8, 2014 at 8:26 AM, Noorul Islam Kamal Malmiyoda <<br>
>> > <a href="mailto:noorul@noorul.com">noorul@noorul.com</a>> wrote:<br>
>> ><br>
>> >><br>
>> >> On Jan 8, 2014 6:11 PM, "Sean Dague" <<a href="mailto:sean@dague.net">sean@dague.net</a>> wrote:<br>
>> >> ><br>
>> >> > On 01/07/2014 11:27 PM, Noorul Islam Kamal Malmiyoda wrote:<br>
>> >> > > On Wed, Jan 8, 2014 at 9:43 AM, Georgy Okrokvertskhov<br>
>> >> > > <<a href="mailto:gokrokvertskhov@mirantis.com">gokrokvertskhov@mirantis.com</a>> wrote:<br>
>> >> > >> Should we rather revert patch to make gate working?<br>
>> >> > >><br>
>> >> > ><br>
>> >> > > I think it is always good to have test packages reside in<br>
>> >> > > test-requirements.txt. So -1 on reverting that patch.<br>
>> >> > ><br>
>> >> > > Here [1] is a temporary solution.<br>
>> >> > ><br>
>> >> > > Regards,<br>
>> >> > > Noorul<br>
>> >> > ><br>
>> >> > > [1] <a href="https://review.openstack.org/65414">https://review.openstack.org/65414</a><br>
>> >> ><br>
>> >> > If Solum is trying to be on the road to being an OpenStack project, why<br>
>> >> > would it go out of it's way to introduce an incompatibility in the way<br>
>> >> > all the actual OpenStack packages work in the gate?<br>
>> >> ><br>
>> >> > Seems very silly to me, because you'll have to add oslo.sphinx back into<br>
>> >> > test-requirements.txt the second you want to be considered for<br>
>> >> incubation.<br>
>> >> ><br>
>> >><br>
>> >> I am not sure why it seems silly to you. We are not anyhow removing<br>
>> >> oslo.sphinx from the repository. We are just removing it before installing<br>
>> >> the packages from test-requirements.txt<br>
>> >><br>
>> > in the devstack gate. How does that affects incubation? Am I missing<br>
>> >> something?<br>
>> >><br>
>> ><br>
>> > Docs are a requirement, and contributor docs are required for applying for<br>
>> > incubation. [1] Typically these are built through Sphinx and consistency is<br>
>> > gained through oslo.sphinx, also eventually we can offer consistent<br>
>> > extensions. So a perception that you're skipping docs would be a poor<br>
>> > reflection on your incubation application. I don't think that's what's<br>
>> > happening here, but I want to be sure you understand the consistency and<br>
>> > doc needs.<br>
>> ><br>
>> > See also<br>
>> > <a href="http://lists.openstack.org/pipermail/openstack-dev/2014-January/023582.htmlfor">http://lists.openstack.org/pipermail/openstack-dev/2014-January/023582.htmlfor</a><br>
>> > similar issues, we're trying to figure out the best solution. Stay<br>
>> > tuned.<br>
>> ><br>
>><br>
>> I have seen that, also posted solum issue [1] there yesterday. I started<br>
>> this thread to have consensus on making solum devstack gate non-voting<br>
>> until the issue gets fixed. Also proposed a temporary solution with<br>
>> which we can solve the issue for the time being. Since the gate is<br>
>> failing for all the patches, it is affecting every patch.<br>
>><br>
>> Regards,<br>
>> Noorul<br>
>><br>
>> [1] <a href="http://lists.openstack.org/pipermail/openstack-dev/2014-January/023618.html">http://lists.openstack.org/pipermail/openstack-dev/2014-January/023618.html</a><br>
>> [2] <a href="https://review.openstack.org/65414">https://review.openstack.org/65414</a><br>
>><br>
>> ><br>
>> ><br>
>> > 1.<br>
>> > <a href="https://github.com/openstack/governance/blob/master/reference/incubation-integration-requirements">https://github.com/openstack/governance/blob/master/reference/incubation-integration-requirements</a><br>
>> ><br>
>> >> Regards,<br>
>> >> Noorul<br>
>> >><br>
>> >> > -Sean<br>
>> >> ><br>
>> >> > --<br>
>> >> > Sean Dague<br>
>> >> > Samsung Research America<br>
>> >> > <a href="mailto:sean@dague.net">sean@dague.net</a> / <a href="mailto:sean.dague@samsung.com">sean.dague@samsung.com</a><br>
>> >> > <a href="http://dague.net">http://dague.net</a><br>
>> >> ><br>
>> >> ><br>
>> >> > _______________________________________________<br>
>> >> > OpenStack-dev mailing list<br>
>> >> > <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>> >> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>> >> ><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> OpenStack-dev mailing list<br>
>> >> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>> >><br>
>> >><br>
>> > _______________________________________________<br>
>> > OpenStack-dev mailing list<br>
>> > <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>> _______________________________________________<br>
>> OpenStack-dev mailing list<br>
>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
><br>
> -- <br>
> Georgy Okrokvertskhov<br>
> Technical Program Manager,<br>
> Cloud and Infrastructure Services,<br>
> Mirantis<br>
> <a href="http://www.mirantis.com">http://www.mirantis.com</a><br>
> Tel. +1 650 963 9828<br>
> Mob. +1 650 996 3284<br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
</p>