Re: [hackathon] Interop testing within hackathon network

Ted Lemon <mellon@fugue.com> Fri, 12 March 2021 20:04 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: hackathon@ietfa.amsl.com
Delivered-To: hackathon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A6A33A0E59 for <hackathon@ietfa.amsl.com>; Fri, 12 Mar 2021 12:04:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DC_PNG_UNO_LARGO=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 lezhPfThSvyV for <hackathon@ietfa.amsl.com>; Fri, 12 Mar 2021 12:04:56 -0800 (PST)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (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 639603A0E52 for <hackathon@ietf.org>; Fri, 12 Mar 2021 12:04:54 -0800 (PST)
Received: by mail-qt1-x836.google.com with SMTP id l13so4797474qtu.9 for <hackathon@ietf.org>; Fri, 12 Mar 2021 12:04:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=/+o6zAJk3ji6ve6CGcJsRCfDWxxZfS17psnkrPVT8Zg=; b=a8NkW0tcon694J4ijn9Z7Y+4ao3ujpH+2ScAPU7s2owqjIZnrHL3xce2h/znXf7Jg6 j0AdcOc/GSsW5py79jI/Bdj7QXUP5CkpL1cSdRziBUuo29g7VTVTgNfALwPGYrBkm1Mm ke/uTGtaLhmVmj9G70VYnBlEBsFhTvVtg0gTMcy49wI4VL+mXiM+GFdwfp15H+rWvxch ytCq3neB2FJNbQgw1Pr4sMvrTJBQMhMtsPSDdNwxeyk3ljbfsskrSvoTB7BOWEA/8+ax GgqEBcEON9ePErM7P+Yubm9nsrQPD4aA5EZYj7wYSWcck1VCH7ePjbSILde8eV6RIOAR KxGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=/+o6zAJk3ji6ve6CGcJsRCfDWxxZfS17psnkrPVT8Zg=; b=B44x0sMNPcysah4CEdUhZEPo6+wTuk+8wBCKjGS/HSAPOSyxxyU0MigvklT/SADLKG 8CQmTkJqHl0Ibor5Au10wOvHThkJnFI5KJxj/D9vETjZcJNkqiifYJzPJMC+6FpovXXL o8ReRhkIDtPA875Dq50JgkIWuYCUyRt6s6zi2rD85jisF1HMRGwiL4qG4/5BRCdilAEk ACF/rcmVd7OzWVQklA3i3o8HhAsxfcPgE/KkpYAWO2GnVWbHvOaLErxGEb0dl35tukry DQEWGBq5DvZ90ukvaijTt+GrAb/b0kjP08WMcHcNhifmxpTc7J0iPuFeRdDZYB+DF/a7 Wxkw==
X-Gm-Message-State: AOAM531QR3taoNz5zYOu//QLqIK+vxALqjz8Jp13AAliOceSYW/Xsg8+ Ro9piU3PjDJo+I1cfrXPbiZz/Q==
X-Google-Smtp-Source: ABdhPJx3qsqe6QxAopwrhKsKooEAEGrZBdVWgc5sddOMvH+th5O6hizeo3Z8G0vUqg9s0zMrUSxRpA==
X-Received: by 2002:ac8:1494:: with SMTP id l20mr13615443qtj.151.1615579491184; Fri, 12 Mar 2021 12:04:51 -0800 (PST)
Received: from [192.168.4.70] (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id f8sm4480106qth.6.2021.03.12.12.04.49 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Mar 2021 12:04:49 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <31546C18-2B25-4265-BB1F-355399B676BC@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BCA53B42-C68B-45E8-BEE2-1446D233ADCE"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.2\))
Date: Fri, 12 Mar 2021 15:04:47 -0500
In-Reply-To: <fd6b2bb1-2381-d467-f520-ea616cadff7d@gmail.com>
Cc: Chris Morrow <morrowc=40google.com@dmarc.ietf.org>, Badma Butaev <badma@juniperlab.ru>, Juhamatti Kuusisaari <juhamatk@gmail.com>, "Charles Eckel (eckelcu)" <eckelcu=40cisco.com@dmarc.ietf.org>, Pierre Francois <pierre.francois@insa-lyon.fr>, hackathon@ietf.org
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <DD39C726-5A0E-4414-AF43-F08C8643F439@cisco.com> <6C32DBAB-D3B2-48A8-9949-580EA0E2A3ED@juniperlab.ru> <CAMeF8nC1UR396=Hrm7zJf1v1arO0Tz9VV5mXT8otN8n417xW9g@mail.gmail.com> <fd6b2bb1-2381-d467-f520-ea616cadff7d@gmail.com>
X-Mailer: Apple Mail (2.3654.60.0.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hackathon/6giD6EJhulDcJdX2gvdXRi4k8pY>
Subject: Re: [hackathon] Interop testing within hackathon network
X-BeenThere: hackathon@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion regarding past, present, and future IETF hackathons." <hackathon.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hackathon>, <mailto:hackathon-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hackathon/>
List-Post: <mailto:hackathon@ietf.org>
List-Help: <mailto:hackathon-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hackathon>, <mailto:hackathon-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2021 20:04:59 -0000

On Mar 12, 2021, at 2:55 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> In fairness, Chris, the unsubscribe link in the headers is significantly hard to find since typical user agents will not normally display it. For example, on Thunderbird you need to select View/Headers/All and scroll down about three pages. On the gmail webmail interface you have to find the "Show Original" option and scroll through the whole SMTP header junk.

Depends on the MUA. If you are running MacOS, it looks like this:



It’s weird that GMail doesn’t do better. They definitely know how to read the header, because they do it for spam. Somebody ought to add this to Thunderbird. It’s sad how many mail UAs are stuck in the 20th century (not to say that Apple Mail is a paragon in every way, but it does get this right).

> 
> However, the convention of sending an Unsubscribe message to <listname>-request@<domain> should be known to everybody.
> 
> Regards
>   Brian
> 
> On 13-Mar-21 08:29, Chris Morrow wrote:
>> People need to learn how mailing lists work, please read the headers
>> and click the included link to unsubscribe.
>> 
>> On Thu, Mar 11, 2021 at 6:16 PM Badma Butaev <badma@juniperlab.ru> wrote:
>>> 
>>> Hello!
>>> 
>>> Please remove me from the mailing list.
>>> 
>>>> 12 марта 2021 г., в 00:22, Charles Eckel (eckelcu) <eckelcu=40cisco.com@dmarc.ietf.org> написал(а):
>>>> 
>>>> Pierre,
>>>> 
>>>> Thanks, and yes, ultimately it is up to the project champions and the rest of the team to determine how they want to work and what tools they want to use. A goal of the hackathon is to provide an environment and tools that can be helpful.
>>>> 
>>>> Cheers,
>>>> Charles
>>>> 
>>>> On 3/11/21, 12:52 PM, "Pierre Francois" <pierre.francois@insa-lyon.fr> wrote:
>>>> 
>>>>   Charles,
>>>> 
>>>>   these are great initiatives, but shouldn't we simply rely on the champions to provide the env for interop testing?
>>>> 
>>>>   Cheers,
>>>> 
>>>>   Pierre.
>>>> 
>>>>   ----- Mail original -----
>>>>> De: "Charles Eckel (eckelcu)" <eckelcu=40cisco.com@dmarc.ietf.org>
>>>>> À: "Juhamatti Kuusisaari" <juhamatk@gmail.com>, hackathon@ietf.org
>>>>> Envoyé: Jeudi 11 Mars 2021 21:47:50
>>>>> Objet: Re: [hackathon] Interop testing within hackathon network
>>>> 
>>>>> Hi Juhamatti,
>>>>> 
>>>>> Shared compute resources were made available at some previous in person
>>>>> hackathons, but that practice stoped due to low utilization.
>>>>> For recent online only hackathons, we have provided remote networking options,
>>>>> as described here,
>>>>> https://datatracker.ietf.org/doc/html/draft-eckel-shmoo-ietf-hackathon-03#section-6.8
>>>>> 
>>>>> We ran into some complications that resulted in these services not being
>>>>> available for IETF 110, but we intend to offer something comparable for future
>>>>> hackathons. If so, would this work for the interop testing you have in mind?
>>>>> 
>>>>> Cheers,
>>>>> Charles
>>>>> 
>>>>> On 3/11/21, 8:06 AM, "hackathon on behalf of Juhamatti Kuusisaari"
>>>>> <hackathon-bounces@ietf.org on behalf of juhamatk@gmail.com> wrote:
>>>>> 
>>>>>  Hello,
>>>>> 
>>>>>  Just wondering how people have been doing interop testing in remote
>>>>>  hackathons so far, what would be the best practices? For my use case
>>>>>  the simplest thing would be to have a common server where a KVM image
>>>>>  would be instantiated and other KVM instances or even host processes
>>>>>  could connect to it over kernel switch. Anything like this available?
>>>>> 
>>>>>  Thanks,
>>>>>  --
>>>>>   Juhamatti
>>>>> 
>>>>>  _______________________________________________
>>>>>  hackathon mailing list
>>>>>  hackathon@ietf.org
>>>>>  https://www.ietf.org/mailman/listinfo/hackathon
>>>>> 
>>>>> _______________________________________________
>>>>> hackathon mailing list
>>>>> hackathon@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/hackathon
>>>> 
>>>> _______________________________________________
>>>> hackathon mailing list
>>>> hackathon@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/hackathon
>>> 
>>> _______________________________________________
>>> hackathon mailing list
>>> hackathon@ietf.org
>>> https://www.ietf.org/mailman/listinfo/hackathon
>> 
>> _______________________________________________
>> hackathon mailing list
>> hackathon@ietf.org
>> https://www.ietf.org/mailman/listinfo/hackathon
>> 
> 
> _______________________________________________
> hackathon mailing list
> hackathon@ietf.org
> https://www.ietf.org/mailman/listinfo/hackathon