Open Stack

I've created https://github.com/puppet-community/puppet-git_resource/pull/12
to rectify the issue with git_resource. Note that the autorequires there
isn't really a critical bug, it will require the class if it exists, but do
nothing if the class does not exist.


On Thu, Sep 24, 2015 at 1:31 AM, Marton Kiss <marton.kiss at gmail.com> wrote:

> +1 to git_resource module. Anyway it needs some care to fix issues, and it
> is a bit more then documentation things. For example this direct dependency
> on a non-existent git class:
>
> https://github.com/puppet-community/puppet-git_resource/blob/master/lib/puppet/type/git.rb#L86
>
> The git class was included in nanilu's original repo, but was tied
> directly to RedHat, and the puppet run failed on a non-rh environment.
>
> M.
>
> On Wed, Sep 23, 2015 at 8:24 PM Spencer Krum <krum.spencer at gmail.com>
> wrote:
>
>> My preference is to use the puppet-community-git_resource module, it
>> provides an easy way to transition and can be opinionated about the git
>> functionality we want. I've heard from many people that the module only
>> supports redhat, which isn't true. But I think we should view that as a
>> documentation bug and fix it if we can.
>>
>> On Wed, Sep 23, 2015 at 8:31 AM, Marton Kiss <marton.kiss at gmail.com>
>> wrote:
>>
>>> I hope we can fix that refresh issue within a reasonable timeframe, and
>>> this change won't affect the new releases of production ask.o.o.
>>>
>>> M.
>>>
>>> On Wed, Sep 23, 2015 at 4:56 PM Jeremy Stanley <fungi at yuggoth.org>
>>> wrote:
>>>
>>>> On 2015-09-23 12:19:22 +0000 (+0000), Marton Kiss wrote:
>>>> > Yeah, this temporary fix solves the going offline thingy:
>>>> > https://review.openstack.org/#/c/222653/
>>>> >
>>>> > Sitting in the queue for a while, a +2 approval could help to stop
>>>> refresh
>>>> > triggers on ask.o.o
>>>>
>>>> As a very temporary measure I've approved it, but Clark expressed a
>>>> concern that this results in no longer updating automatically (so
>>>> any change to the ref for ask.openstack.org will need setting
>>>> askbot_ensure=>latest briefly and then =>present again once the
>>>> upgrade takes place). This also means ask-staging will stop
>>>> following the development branch unless we override
>>>> askbot_ensure=>latest for it.
>>>> --
>>>> Jeremy Stanley
>>>>
>>>> _______________________________________________
>>>> OpenStack-Infra mailing list
>>>> OpenStack-Infra at lists.openstack.org
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>>
>>>
>>> _______________________________________________
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>>
>>>
>>
>>
>> --
>> Spencer Krum
>> (619)-980-7820
>> _______________________________________________
>> OpenStack-Infra mailing list
>> OpenStack-Infra at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
>>
>


-- 
Spencer Krum
(619)-980-7820
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20150924/c3d7e69b/attachment.html>