From owner-freebsd-cloud@freebsd.org Sat Nov 25 13:22:34 2017 Return-Path: Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C14DDE3939 for ; Sat, 25 Nov 2017 13:22:34 +0000 (UTC) (envelope-from raf@rafal.net) Received: from fbo-1.mxes.net (mxout-23.mxes.net [216.86.168.223]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48A3380CCD for ; Sat, 25 Nov 2017 13:22:33 +0000 (UTC) (envelope-from raf@rafal.net) Received: from smtp-out-2.mxes.net (smtp-out-2.mxes.net [67.222.241.249]) by fbi-1.mxes.net (Postfix) with ESMTP id 17CAB274F8 for ; Sat, 25 Nov 2017 08:15:39 -0500 (EST) Received: from [172.20.10.2] (s147-130.psd.vodafone.ie [213.233.147.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4DA0F274FB for ; Sat, 25 Nov 2017 08:15:14 -0500 (EST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Rafal Lukawiecki Mime-Version: 1.0 (1.0) Date: Sat, 25 Nov 2017 13:24:17 +0100 Subject: FreeBSD AWS AMI disk system Message-Id: <386518E3-1D01-4E1F-BB77-E9C530E05381@rafal.net> To: freebsd-cloud@freebsd.org X-Mailer: iPad Mail (15B202) X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Nov 2017 13:22:34 -0000 Pardon my ignorance, as a recent convert to running FreeBSD in AWS, but I wo= uld like to know a little more about the possibilities that regard the under= lying file system of the official RE and Marketplace FreeBSD 11 AMIs. Ideally, I would like to have the simplicity of using the official AMIs but h= ave the option of selecting a different initial volume size (both smaller, 4= -5GB, and larger), and to turn on the standard EBS encryption at the initial= instance launch time. I realise that I can create my own AMIs, as I have do= ne over the years using CentOS. Is there an easier way and one that would no= t require my own AMI rebuilding from my own snapshots each time FreeBSD is r= eleased? Then there is the question of the actual file system. Have you opinions abou= t any performance gains, especially startup/reboot time, for OpenZFS via EB= S? The usual ZFS advantages of versioning/ZFS snapshots and the ability to s= tream updates seem attractive to our way of running our (growing) server far= m. I was just reading the current issue of the FreeBSD Magazine and I have f= ound out that ScaleEngine use OpenZFS in their AWS set-up. As an aside, the EFS is pretty slow=E2=80=94I suppose I had higher expectati= ons, considering EBS performance. I do not think that has much to do with Fre= eBSD and more likely a limitation of AWS NFS, but I wonder if there is anyth= ing on the horizon that could improve it. On another note, will the >32 bit N= FS log spam disappear anytime soon, ie. when is FreeBSD likely to get 64-bit= handles? Many thanks for your thoughts and my regards from Ireland, Rafal Lukawiecki Data Scientist Project Botticelli Ltd