From nobody Thu Sep 23 22:13:21 2021 X-Original-To: freebsd-cloud@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 8DE7B17DEE42 for ; Thu, 23 Sep 2021 22:14:53 +0000 (UTC) (envelope-from erobison@gmail.com) Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HFqGP3B1Dz4jsg for ; Thu, 23 Sep 2021 22:14:53 +0000 (UTC) (envelope-from erobison@gmail.com) Received: by mail-wr1-x42b.google.com with SMTP id u18so21448235wrg.5 for ; Thu, 23 Sep 2021 15:14:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HysEjHIL0Si8GQBUnw78vzhljn4cAikabaWpmnazAp8=; b=SrxWT97b5FQ27O4at/ZRRVU7UGDXPrJiVfMB5Gf7JKA+BYwtbRMD5X2GD+96u+zgK3 2qEfJAHo/Q2XsLkQNlhHwxWLpU0WecORqeqJ6kmOQkgBZXyYG9XSX1YWgj6IOrC3K22W A7c+snUrgdT6sScrjMufbrwCBbDG5UEoFzp/igj/EiBu2SdZRQriJXmNC4SdhjBbWQtW McgAELNhKEt/zM5yUcfzMVcZ2vLOf594QsUNpdJ8zeJDXrsVIxJmlPqE8XkO8CojrFEj dZ/qnPK8I9zjk9GlWJfphK+Wrwps25IVWq/yciEnluddqa9bFLiqL0DucVsUICHeudx2 O8LQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HysEjHIL0Si8GQBUnw78vzhljn4cAikabaWpmnazAp8=; b=YesVvcAm09L9j4PibvOdUuXlMb3zy+cM9tWhnN+glt3NxkbVZeLcM6C/BFsRPL72jt iyar/xlg4ioRYPCCpJFrxvmXkjtd8gYmkT/Em3PiwoT/oZ/KFBacuXpMYCzfSZCY2WFQ 5yzwGBTdnVxJEeLDgXmSF0eXI8Y+kuRsKj+CbPREz/Qm30354WeQ+kysn6GDM4mOnPg0 Bx5FVzLcynXcbPqffWsgB/I6axEv8SNCyz7/L6FzsH6G3NLFz/0aPSnOH6EreyCxKdXV snAEOnnl/FlYmfHuT8fvxNWU+MH/WmVaM8MXjVEdL9bF2lZkcxZBP48mOxa4V3C1FvDS NfHw== X-Gm-Message-State: AOAM532dp6VehufzA9bS6HuWTrhiy7450uVGJsvlyxIutT5Vp7fmnEZu si1HosET5sXwBRReSgxIsThZIJPrOFIto3Pimas= X-Google-Smtp-Source: ABdhPJyTNxTLm/DuJbo8G65LliSBghuXJO0myjUV3C9fOAPZq+/Ut/ZUQYS2vWwc1f2FfFhEX3rt/CLwEwa/PNtZSKc= X-Received: by 2002:a5d:6dce:: with SMTP id d14mr8059591wrz.363.1632435292301; Thu, 23 Sep 2021 15:14:52 -0700 (PDT) List-Id: FreeBSD on cloud platforms (EC2, GCE, Azure, etc.) List-Archive: https://lists.freebsd.org/archives/freebsd-cloud List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-cloud@freebsd.org MIME-Version: 1.0 References: <65D39FF2-C14D-430E-A83B-0C3606E0D7AF@patmaddox.com> In-Reply-To: <65D39FF2-C14D-430E-A83B-0C3606E0D7AF@patmaddox.com> From: ericr Date: Thu, 23 Sep 2021 16:13:21 -0600 Message-ID: Subject: Re: Current status of ZFS AMIs on EC2? To: Pat Maddox Cc: freebsd-cloud@freebsd.org Content-Type: multipart/alternative; boundary="000000000000b76f2505ccb0f532" X-Rspamd-Queue-Id: 4HFqGP3B1Dz4jsg X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --000000000000b76f2505ccb0f532 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Sep 23, 2021 at 2:50 AM Pat Maddox wrote: > Hi there, I came across Colin=E2=80=99s 2019 post announcing ZFS AMIs for= EC2 > [1]. I haven=E2=80=99t seen any more recent information regarding ZFS on = EC2. > I=E2=80=99ve launched one instance, and it appears to work fine from init= ial > tests (including recovering a known working boot env using beadm). > > I have also installed the official 12 and 13 releases, and see that they > are UFS. > > I have two questions: > > 1. Is anyone using the ZFS AMIs for production? > Yes. ~30 in five regions, mostly 12.2-RELEASE. > 2. Why has ZFS not been incorporated into the official releases? > $COLIN =3D 1 Hopefully some day soon ZFS will be the default filesystem for all installs and images. For now, we use the 12.0-RELEASE AMI Colin built (Thanks Colin!) and upgrade to 12.2, then make an AMI of it. If we want 13.0, we'll upgrade a copy and create another AMI. It's not painful, and it doesn't take long. There are other ways to do it, but being lazy I find that freebsd-update -r takes the least effort. Once you make a 'base' AMI, you don't have to deal with it again. [1] > https://lists.freebsd.org/pipermail/freebsd-cloud/2019-February/000200.ht= ml --000000000000b76f2505ccb0f532--