From nobody Thu Sep 23 08:49:42 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 4E08117D18C8 for ; Thu, 23 Sep 2021 08:49:54 +0000 (UTC) (envelope-from pat@patmaddox.com) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HFTPY2zdXz3ll7 for ; Thu, 23 Sep 2021 08:49:50 +0000 (UTC) (envelope-from pat@patmaddox.com) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8C8F25C01BC; Thu, 23 Sep 2021 04:49:44 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 23 Sep 2021 04:49:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=patmaddox.com; h=from:to:subject:date:message-id:mime-version:content-type :content-transfer-encoding; s=fm1; bh=BJX6BIdnaszb9DMB62IAsoKwxZ EBABKnOdPPfzWNHyw=; b=FCJEJsWA1TKsJvLkS6capWSZVsQo+93PewgVxVWZ6g OE4TlAzjM7u+MHI02wC1aadU1xy0d8aIHOZezXOxPmuPBtFYR4TcFlJ8nrPWAocC VV1jQy6RJ8FVJbBzxY7Qrl4h95J1aWWj/vg129sTBC+wiGypJ/+3ngUXqdqY+kMv my3WmLV+GXWyQOkC1o2okI/d0u6oQCNbOwbMLLItFD0wiZzKOGjAYBBBxqKUQ4gc vFHubiVk8NizX1MKvebbnyGpuq33wphARTbHaiNKM8abwQm2pDq0ddcT7IpdbG3W vt46gLHaqN52nUZXmKz+27J2YL6E1sYs3idRbqy4/j7w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=BJX6BI dnaszb9DMB62IAsoKwxZEBABKnOdPPfzWNHyw=; b=mLLZPyd3ffrjrp4Y/HKOiP SKfCE+bIS334m+BweY3e4uTeGRaYZWLcCScvzTpvbvMW/sqBjxLXxBulVh48p/FH W5HmC4CQjE+tYwMPYpdo573B/rvNZXNP0G5F4uPVFpnxMu/j6gq3N5KuO5AYKjOB R8iwk9rbgeHvwH5hVx38F2ZmJSJdh6qRJMOGZ3+D/99ThKoCyocQqXBam68ucrX6 TVxpBLQUdY3Unp9Jke34tXz1umsl8GN4ONA97r/9bQhG4kujy7gjSZsIPjGs3vVM 6t20KIuSU+Jao9TBagObrOjwZHffCM+5FJmoPMlHNDbJ/b8vge8VP162DhgonTFA == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudeiledgtdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffokfggtgfgsegrkehmre ertdejnecuhfhrohhmpedfrfgrthcuofgrugguohigfdcuoehprghtsehprghtmhgruggu ohigrdgtohhmqeenucggtffrrghtthgvrhhnpeevtdevgedvheeuvdekudeggeelfffgud duveetgedtudelhfefgfffkeffheehffenucffohhmrghinhepfhhrvggvsghsugdrohhr ghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehprg htsehprghtmhgrugguohigrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Thu, 23 Sep 2021 04:49:44 -0400 (EDT) From: "Pat Maddox" To: freebsd-cloud@FreeBSD.org Subject: Current status of ZFS AMIs on EC2? Date: Thu, 23 Sep 2021 01:49:42 -0700 X-Mailer: MailMate (1.13.2r5673) Message-ID: <65D39FF2-C14D-430E-A83B-0C3606E0D7AF@patmaddox.com> 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 Content-Type: multipart/alternative; boundary="=_MailMate_2131FD5B-E26E-42AF-8ADC-75490D76EF96_=" Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4HFTPY2zdXz3ll7 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=patmaddox.com header.s=fm1 header.b=FCJEJsWA; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=mLLZPyd3; dmarc=none; spf=pass (mx1.freebsd.org: domain of pat@patmaddox.com designates 66.111.4.29 as permitted sender) smtp.mailfrom=pat@patmaddox.com X-Spamd-Result: default: False [-3.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[patmaddox.com:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.29:from]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:11403, ipnet:66.111.0.0/20, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[patmaddox.com:s=fm1,messagingengine.com:s=fm3]; FREEFALL_USER(0.00)[pat]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-cloud@freebsd.org]; DMARC_NA(0.00)[patmaddox.com]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; RCVD_TLS_LAST(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[66.111.4.29:from] X-ThisMailContainsUnwantedMimeParts: Y --=_MailMate_2131FD5B-E26E-42AF-8ADC-75490D76EF96_= Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown Content-Transfer-Encoding: 8bit Hi there, I came across Colin’s 2019 post announcing ZFS AMIs for EC2 [1]. I haven’t seen any more recent information regarding ZFS on EC2. I’ve launched one instance, and it appears to work fine from initial 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? 2. Why has ZFS not been incorporated into the official releases? Thanks, Pat [1] https://lists.freebsd.org/pipermail/freebsd-cloud/2019-February/000200.html --=_MailMate_2131FD5B-E26E-42AF-8ADC-75490D76EF96_=-- From nobody Thu Sep 23 09:42:46 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 3518C17D8038 for ; Thu, 23 Sep 2021 09:42:49 +0000 (UTC) (envelope-from pat@patmaddox.com) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HFVZc4cVvz3sMN for ; Thu, 23 Sep 2021 09:42:48 +0000 (UTC) (envelope-from pat@patmaddox.com) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 8A53B5C01E0; Thu, 23 Sep 2021 05:42:48 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 23 Sep 2021 05:42:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=patmaddox.com; h=from:to:subject:date:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=fm1; bh= pbWrvWvQzCKlYi4fJBHfVN3BgOo9cwNcAVAWQdRE8YA=; b=RM5TnWHMkyTpb9LA PdfEgvxLiX8CYrCfe7zgaVvFWp0Di4j+EnZStjygVxV++dP+iW/rB5sQ7FkMIgaY OjJzR2zMju2ALltHXdHlAIy68BjoZL2HnxQxk0+NrOukcGjvtQmB9P7P1Z2LKUxD sjHZPDKmRZK2vzJdqvCnG4STMuPHxKpJuzmWZZT4OnWzkpg1RYC4DmmX2Q3QpFIM sgRdZH2vjNfMq1d8/Zo1W51bCH/Ou1juBOwiq33A1Do12b2rcybwLxHIj1J8+rC3 3i8oRyJl4944bMatvMLAiHOrdn8ELFWrY/pTXzbYlkoUpSH/2z1TP2okS/4VwtNc qrz8tQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=pbWrvWvQzCKlYi4fJBHfVN3BgOo9cwNcAVAWQdRE8 YA=; b=SlFWMOkXeHNNSeaca7xMHBDS5amwzRIzAClCDMSFBs+uq2sWNSwHmXvnY cXNbw6xoJsq/E0sNWQb69tClSwcrkZcl6yBA80i2UatGTNMRxss7ijqCPYilkB8I PIHTWMk1OY6Fn7Zb2UmbnzsIAoGxdzqeuc5Hy5XKOLhdkmJCRZAvcRowi6axUANl 8Lpg5XEXe9IXrSkvL84z7sN9G1PpiOLy2olh2c0rCEQ+XSkPISS9wU0eidqeRekQ cBudXRDVgRyGSW3exTywY6oN0bVVWSveXPWCumVZ+QzlcRr5xeSx2Bz1j2NHaike +bIk+hkfXpPjU3Sc7VSuN4quzkbLQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudeiledgudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffokfgjfhggtgfgsegrke hmreertdejnecuhfhrohhmpedfrfgrthcuofgrugguohigfdcuoehprghtsehprghtmhgr ugguohigrdgtohhmqeenucggtffrrghtthgvrhhnpeeiveevgeejfeehgedvleeufeelff etfedthffhhfekveehleduiefgieekueeitdenucffohhmrghinhepfhhrvggvsghsugdr ohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hprghtsehprghtmhgrugguohigrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Thu, 23 Sep 2021 05:42:48 -0400 (EDT) From: "Pat Maddox" To: freebsd-cloud@FreeBSD.org Subject: Re: Current status of ZFS AMIs on EC2? Date: Thu, 23 Sep 2021 02:42:46 -0700 X-Mailer: MailMate (1.13.2r5673) Message-ID: <60E1F943-9C3C-4265-B7EC-F49680B9262B@patmaddox.com> In-Reply-To: <65D39FF2-C14D-430E-A83B-0C3606E0D7AF@patmaddox.com> References: <65D39FF2-C14D-430E-A83B-0C3606E0D7AF@patmaddox.com> 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 Content-Type: multipart/alternative; boundary="=_MailMate_E0509714-84B9-4F4E-BF2B-1048A8CCCC17_=" Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4HFVZc4cVvz3sMN X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=patmaddox.com header.s=fm1 header.b=RM5TnWHM; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=SlFWMOkX; dmarc=none; spf=pass (mx1.freebsd.org: domain of pat@patmaddox.com designates 66.111.4.29 as permitted sender) smtp.mailfrom=pat@patmaddox.com X-Spamd-Result: default: False [-3.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29:c]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[patmaddox.com:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:11403, ipnet:66.111.0.0/20, country:US]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.29:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[patmaddox.com:s=fm1,messagingengine.com:s=fm3]; FREEFALL_USER(0.00)[pat]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-cloud@freebsd.org]; DMARC_NA(0.00)[patmaddox.com]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; RWL_MAILSPIKE_POSSIBLE(0.00)[66.111.4.29:from] X-ThisMailContainsUnwantedMimeParts: Y --=_MailMate_E0509714-84B9-4F4E-BF2B-1048A8CCCC17_= Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown Content-Transfer-Encoding: 8bit Also, is there a 13.0-release ZFS AMI? On 23 Sep 2021, at 1:49, Pat Maddox wrote: > Hi there, I came across Colin’s 2019 post announcing ZFS AMIs for > EC2 [1]. I haven’t seen any more recent information regarding ZFS on > EC2. I’ve launched one instance, and it appears to work fine from > initial 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? > 2. Why has ZFS not been incorporated into the official releases? > > Thanks, > Pat > > [1] > https://lists.freebsd.org/pipermail/freebsd-cloud/2019-February/000200.html --=_MailMate_E0509714-84B9-4F4E-BF2B-1048A8CCCC17_=-- From nobody Thu Sep 23 20:22:22 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 80BF517D3D17 for ; Thu, 23 Sep 2021 20:22:29 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from mail.tarsnap.com (mail.tarsnap.com [54.86.246.204]) by mx1.freebsd.org (Postfix) with SMTP id 4HFmmj1lmmz4Wk0 for ; Thu, 23 Sep 2021 20:22:29 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: (qmail 41656 invoked from network); 23 Sep 2021 20:22:23 -0000 Received: from unknown (HELO dell7390.daemonology.net) (127.0.0.1) by mail.tarsnap.com with SMTP; 23 Sep 2021 20:22:23 -0000 Received: (qmail 36366 invoked from network); 23 Sep 2021 20:22:22 -0000 Received: from unknown (HELO dell7390.daemonology.net) (127.0.0.1) by localhost with SMTP; 23 Sep 2021 20:22:22 -0000 From: Colin Percival Subject: Re: Current status of ZFS AMIs on EC2? To: Pat Maddox , freebsd-cloud@FreeBSD.org References: <65D39FF2-C14D-430E-A83B-0C3606E0D7AF@patmaddox.com> Message-ID: <12428f52-ea5a-a2e5-7eb6-e170c97f0e17@freebsd.org> Date: Thu, 23 Sep 2021 13:22:22 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 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 In-Reply-To: <65D39FF2-C14D-430E-A83B-0C3606E0D7AF@patmaddox.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4HFmmj1lmmz4Wk0 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On 9/23/21 1:49 AM, Pat Maddox wrote: > Hi there, I came across Colin’s 2019 post announcing ZFS AMIs for EC2 [1]. I > haven’t seen any more recent information regarding ZFS on EC2. I’ve launched > one instance, and it appears to work fine from initial 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. (Not me, but I've heard from several people who are. I'll let them identify themselves if they choose to do so.) > 2. Why has ZFS not been incorporated into the official releases? ZFS, and other "flavoured" AMIs, were blocked waiting for this: https://www.daemonology.net/blog/2021-08-31-FreeBSD-AMI-SSM-Public-Parameters.html Now it's just a matter of finding time; my current top priority for EC2 is speeding up the FreeBSD boot process. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From nobody Thu Sep 23 21:00:52 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 C51D917D8ED8 for ; Thu, 23 Sep 2021 21:01:02 +0000 (UTC) (envelope-from pat@patmaddox.com) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HFndB3XLqz4dR2; Thu, 23 Sep 2021 21:01:02 +0000 (UTC) (envelope-from pat@patmaddox.com) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 6221732007E8; Thu, 23 Sep 2021 17:00:55 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 23 Sep 2021 17:00:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=patmaddox.com; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=fm1; bh= J/BS2F3zE2251hGoIBwExqW1W4OIcmnaTkNb7Yf5GSM=; b=Fkz8Ncbv2asF/TnD foBQNJxOwMlax9gfDkzusqBE70oLGS0yAK5t/jyI/Xe5kDPu6Zcs1sL4YLdl04uB WW8HXCXYgBuQTv2K+4IY93DJCVXcwLRH8HJQRuPLLYViiDAwCZS7qsoHoyapOTYJ aM6yQGSzCpMVU79/r20DbLPLG23djlbXIXAHLpaXC/ZhDzKDykm9mBI2JWeSDWTy uYQeW9bK2YWU1KHhL94hht7jD5IP7qB3Z9AUv/jsDUVv57RSQjMChTYg269jFJ9o I6yKDmflJVravaGTuso4jUjoxiN0zGsk+BqKShNBarFi269nfFUJC4Wp1MRtj4vi fOyJaA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=J/BS2F3zE2251hGoIBwExqW1W4OIcmnaTkNb7Yf5G SM=; b=PFG0D+rTIq9euE/Szupbh0XjhkHYse3msr0JTILpG7mtfyVxY6a3aVYeU VIDTyKUg1JucVKDU5RhtzkVs0l5LxO2oaYZFjHTyPqvxfP/C+FH2ynODXeljpDeN Mv8U16420HGnSeb1oWOmypWQnn/IgoJZuoEXWsizFZHO2OzlsNRVfr9wxctHO8/L ibGilqWYkyLWbjhbG1eogoIY+U/k2SgEdNQrx4FrOwIcJz6TjC4fp/Z+ok5aYJoH 1ylE5/1wHUJ7uu4fcRWeTVIF630OHSpt2WqQh2dkg5UnJDzwN+vBadxktim0TJc2 J4TmvndAC1vFJT16vk6G66bncmWvg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrudeiledgudehhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffokfgjfhggtgfgsehtqhhmtdertdejnecuhfhrohhmpedfrfgr thcuofgrugguohigfdcuoehprghtsehprghtmhgrugguohigrdgtohhmqeenucggtffrrg htthgvrhhnpeegveejjeevleetfedvleegvefftdelhfefudfhgfeiheektdelueelveeh ffehteenucffohhmrghinhepuggrvghmohhnohhlohhghidrnhgvthenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehprghtsehprghtmhgruggu ohigrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 23 Sep 2021 17:00:54 -0400 (EDT) From: "Pat Maddox" To: "Colin Percival" Cc: freebsd-cloud@FreeBSD.org Subject: Re: Current status of ZFS AMIs on EC2? Date: Thu, 23 Sep 2021 14:00:52 -0700 X-Mailer: MailMate (1.13.2r5673) Message-ID: In-Reply-To: <12428f52-ea5a-a2e5-7eb6-e170c97f0e17@freebsd.org> References: <65D39FF2-C14D-430E-A83B-0C3606E0D7AF@patmaddox.com> <12428f52-ea5a-a2e5-7eb6-e170c97f0e17@freebsd.org> 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 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4HFndB3XLqz4dR2 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On 23 Sep 2021, at 13:22, Colin Percival wrote: > On 9/23/21 1:49 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 initial 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. (Not me, but I've heard from several people who are. I'll let = > them > identify themselves if they choose to do so.) > >> 2. Why has ZFS not been incorporated into the official releases? > > ZFS, and other "flavoured" AMIs, were blocked waiting for this: > > https://www.daemonology.net/blog/2021-08-31-FreeBSD-AMI-SSM-Public-Para= meters.html > > Now it's just a matter of finding time; my current top priority for = > EC2 > is speeding up the FreeBSD boot process. Great, thanks for the info. I=E2=80=99ve done a 12.0 -> 12.2 -> 13.0 upgr= ade, = all seems to be good. Pat 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--