Re: [TOOLS-DEVELOPMENT] Backing up Github WG repositories

Robert Sparks <rjsparks@nostrum.com> Wed, 26 February 2020 16:43 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71FC53A0B9E for <tools-development@ietfa.amsl.com>; Wed, 26 Feb 2020 08:43:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.403
X-Spam-Level:
X-Spam-Status: No, score=-1.403 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.276, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMFUBLFjDyvt for <tools-development@ietfa.amsl.com>; Wed, 26 Feb 2020 08:43:10 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEBE03A0B92 for <tools-development@ietf.org>; Wed, 26 Feb 2020 08:43:10 -0800 (PST)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 01QGh4Bi037593 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 26 Feb 2020 10:43:05 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1582735386; bh=IMcvSQwg7uhuI6qhpVZcRYp9w15R9LgovlPCTwCu4vw=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=KPo0iMkfulKFndwm2NRZOBerVPdi5Yde4n65VAdRi2d4qytXeCyhaS6mK71dw4oa3 ipeI9wSTw5XXiIUPmta9+zUdV05rUiCNtsx1kc245axzngP2FLedYOacpK2Uyg3kui OZi91AHDgJPhhPQPfzrhhNU2z2z4Chww2Hio1SRo=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
To: "John R. Levine" <johnl@iecc.com>, Russ Housley <housley@vigilsec.com>
Cc: IETF Tools Development <tools-development@ietf.org>, Martin Thomson <mt@lowentropy.net>
References: <9de49701-4477-291a-9a98-a39feb819a44@nostrum.com> <0AEE469F-F140-45E4-B553-1B03A7B4DC45@vigilsec.com> <alpine.OSX.2.22.407.2002251542010.4947@ary.qy>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <b28452e4-42c5-54e0-fd37-cc1d2c32eed7@nostrum.com>
Date: Wed, 26 Feb 2020 10:43:04 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.22.407.2002251542010.4947@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/X9J3v-FXJWlNrS_h3x45qRqyExI>
Subject: Re: [TOOLS-DEVELOPMENT] Backing up Github WG repositories
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Feb 2020 16:43:16 -0000

On 2/25/20 2:42 PM, John R. Levine wrote:
>> This looks fine to me.  I am not sure, but should item number 3 also 
>> allow restore to a local git repository?
>
> I'd think it'd be a good idea to provide some idea of how many repos, 
> how large they're likely to be, and how often they're backed up.  A 
> lot of thongs that work fine on 100MB die painfully on multiple 
> gigabytes.

The frequency will start out as hourly, as specified in 
draft-ietf-git-github-wg-configuration.

At the moment, we can only thumbnail the expected initial number of 
repositories. We can put a theoretical upper bound on it using the total 
number of active WG/RG drafts.

Getting the size of what the backup of a repository will be is going to 
be something the project will have to discover. We could get some 
anecdotal points with help from one of the larger WG users perhaps. The 
difficulty will be in exercising the API (or things built on it) that 
gets the entire project (issues, pull-requests, etc), not just the git 
repository itself. Martin - have you tried that with any of the 
repositories you have they keys for?

RjS

>
>
> Regards,
> John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for 
> Dummies",
> Please consider the environment before reading this e-mail. https://jl.ly