Open Stack

On Jan 8, 2014 9:58 PM, "Georgy Okrokvertskhov" <
gokrokvertskhov at mirantis.com> wrote:
>
> Hi,
>
> 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?
>

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.

> 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.
>

The problematic patch [1] solves a specific problem. Do we have other ways
to solve it?

Regards,
Noorul

[1] https://review.openstack.org/#/c/64226

> Thanks
> Georgy
>
>
> On Wed, Jan 8, 2014 at 7:09 AM, Noorul Islam K M <noorul at noorul.com>
wrote:
>>
>> Anne Gentle <anne at openstack.org> writes:
>>
>> > On Wed, Jan 8, 2014 at 8:26 AM, Noorul Islam Kamal Malmiyoda <
>> > noorul at noorul.com> wrote:
>> >
>> >>
>> >> On Jan 8, 2014 6:11 PM, "Sean Dague" <sean at dague.net> wrote:
>> >> >
>> >> > On 01/07/2014 11:27 PM, Noorul Islam Kamal Malmiyoda wrote:
>> >> > > On Wed, Jan 8, 2014 at 9:43 AM, Georgy Okrokvertskhov
>> >> > > <gokrokvertskhov at mirantis.com> wrote:
>> >> > >> Should we rather revert patch to make gate working?
>> >> > >>
>> >> > >
>> >> > > I think it is always good to have test packages reside in
>> >> > > test-requirements.txt. So -1 on reverting that patch.
>> >> > >
>> >> > > Here [1] is a temporary solution.
>> >> > >
>> >> > > Regards,
>> >> > > Noorul
>> >> > >
>> >> > > [1] https://review.openstack.org/65414
>> >> >
>> >> > If Solum is trying to be on the road to being an OpenStack project,
why
>> >> > would it go out of it's way to introduce an incompatibility in the
way
>> >> > all the actual OpenStack packages work in the gate?
>> >> >
>> >> > Seems very silly to me, because you'll have to add oslo.sphinx back
into
>> >> > test-requirements.txt the second you want to be considered for
>> >> incubation.
>> >> >
>> >>
>> >> I am not sure why it seems silly to you. We are not anyhow removing
>> >> oslo.sphinx from the repository. We are just removing it before
installing
>> >> the packages from test-requirements.txt
>> >>
>> > in the devstack gate. How does that affects incubation? Am I missing
>> >> something?
>> >>
>> >
>> > Docs are a requirement, and contributor docs are required for applying
for
>> > incubation. [1] Typically these are built through Sphinx and
consistency is
>> > gained through oslo.sphinx, also eventually we can offer consistent
>> > extensions. So a perception that you're skipping docs would be a poor
>> > reflection on your incubation application. I don't think that's what's
>> > happening here, but I want to be sure you understand the consistency
and
>> > doc needs.
>> >
>> > See also
>> >
http://lists.openstack.org/pipermail/openstack-dev/2014-January/023582.htmlfor
>> > similar issues, we're trying to figure out the best solution. Stay
>> > tuned.
>> >
>>
>> I have seen that, also posted solum issue [1] there yesterday. I started
>> this thread to have consensus on making solum devstack gate non-voting
>> until the issue gets fixed. Also proposed a temporary solution with
>> which we can solve the issue for the time being. Since the gate is
>> failing for all the patches, it is affecting every patch.
>>
>> Regards,
>> Noorul
>>
>> [1]
http://lists.openstack.org/pipermail/openstack-dev/2014-January/023618.html
>> [2] https://review.openstack.org/65414
>>
>> >
>> >
>> > 1.
>> >
https://github.com/openstack/governance/blob/master/reference/incubation-integration-requirements
>> >
>> >> Regards,
>> >> Noorul
>> >>
>> >> >         -Sean
>> >> >
>> >> > --
>> >> > Sean Dague
>> >> > Samsung Research America
>> >> > sean at dague.net / sean.dague at samsung.com
>> >> > http://dague.net
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > OpenStack-dev mailing list
>> >> > OpenStack-dev at lists.openstack.org
>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >> >
>> >>
>> >>
>> >> _______________________________________________
>> >> OpenStack-dev mailing list
>> >> OpenStack-dev at lists.openstack.org
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>
>> >>
>> > _______________________________________________
>> > OpenStack-dev mailing list
>> > OpenStack-dev at lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> --
> Georgy Okrokvertskhov
> Technical Program Manager,
> Cloud and Infrastructure Services,
> Mirantis
> http://www.mirantis.com
> Tel. +1 650 963 9828
> Mob. +1 650 996 3284
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140108/85acbe14/attachment.html>