From owner-freebsd-cloud@freebsd.org Wed Dec 27 17:31:49 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 262F3EA2FE9 for ; Wed, 27 Dec 2017 17:31:49 +0000 (UTC) (envelope-from michiel@vanbaak.eu) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B47E16E657 for ; Wed, 27 Dec 2017 17:31:47 +0000 (UTC) (envelope-from michiel@vanbaak.eu) Received: by mail-wm0-x22d.google.com with SMTP id f140so40286371wmd.2 for ; Wed, 27 Dec 2017 09:31:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vanbaak-eu.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=vp4f2PQzvm5JwnmjrdZqgDT4exIyXT5+eC80OqlJp9k=; b=Wmr3mwHYLQfBHd/UoF6/4a6M08ugz0BhyE9TQ3GjuuiSD2f0A/VtI3cDS0LMIraKJv THFB4rXjdrKCIBCF7cTrHSgVlIOGE2/APFdaUhMwl7jRVV0sipthxk+2tnXCDtPofc3n dphtrDB4hHZ4GX4Bi7t+8e3KW1B30uTAHPybiHsJ5R8+UaEt2OD14iYLYB0CPjHESV7Y sYp0mFwRW64rUhH1I7lPN8QMh+WDgCVBZF2BnZS7SK5wCjeXaliuhNG9RrSBU9RypEjv 0SnRhhcl8p+S2QgTnxWG9mWCu+6QOePGY8d9JU2La6TbdAlanClbYz0RRukMBwy0HEpp ydRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=vp4f2PQzvm5JwnmjrdZqgDT4exIyXT5+eC80OqlJp9k=; b=a9x0TOG0pv7qDgUQVikEaa3qEVe5zSEDgLnfdkbb2oaYn8l7WhSHlkA8Cjj72gSM7o SL0FHS/+YZ+c1boQkbG5AK3wy7mSzmJqH8ziR6HDgupQ8MvOuxE8/q5ABWMbp4nCVjSr jEB4MjhJ2Nmcb4cccDGwJ1aTabNzKtOHtttSZSN9ey2oFWv26miGrMaJ2m8rq+HDFg0b O3QTcSioTExEIYQBJdj3yuS8q2Ynpd7D6DPQ/XuRg++wxd3wIG4T4qDbiSPbkayPY+2u lZL9khcIwl3VSdAalkbxMO1hLfXhuZdv186vUHmzi6L1oAufOin6BMeVTY/Wojp8P3z3 1HMQ== X-Gm-Message-State: AKGB3mLWgYhKTbGS7eDwuiugM7Kh99x1IeWty0eDS+XgfH1L5yU3Is/9 ZPD+nuxxKlQrOt494wuJwdRNNMCvKyU= X-Google-Smtp-Source: ACJfBouUmpvSuazgB8+rCh5T0ikNYuAlf2Gg/vp+ObzbvFSMIe0LCfToGLHT44Hlo4fXKuC9RD88IQ== X-Received: by 10.80.153.210 with SMTP id n18mr37255040edb.281.1514395905861; Wed, 27 Dec 2017 09:31:45 -0800 (PST) Received: from localhost ([2a02:a443:381e:1::13]) by smtp.gmail.com with ESMTPSA id q10sm27837891edc.32.2017.12.27.09.31.45 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Dec 2017 09:31:45 -0800 (PST) Date: Wed, 27 Dec 2017 18:31:44 +0100 From: Michiel van Baak To: freebsd-cloud@freebsd.org Subject: Re: AMI building AMI Message-ID: <20171227173144.vsdlovd3gz2w7w5g@freebsd02> References: <085D225B-2E99-4540-B693-223087B14A27@rafal.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2z62ewwcjxeipjdb" Content-Disposition: inline In-Reply-To: <085D225B-2E99-4540-B693-223087B14A27@rafal.net> User-Agent: NeoMutt/20171013 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: Wed, 27 Dec 2017 17:31:49 -0000 --2z62ewwcjxeipjdb Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 27, 2017 at 03:53:03PM +0000, Rafal Lukawiecki wrote: > Is there a list of AWS AMI ids (and regions) containing Colin=E2=80=99s A= MI builder AMI? The 2015 article http://www.daemonology.net/blog/2015-11-21= -FreeBSD-AMI-builder-AMI.html mentions one in us-east-1 ami-28682f42. Are th= ere more? Or a documented procedure on using RE tools to achieve the same? >=20 > I am particularly interested in recompiling 11.1 release kernel, adding a= good few packages (to speed up instance launch time) and creating an AMI o= ut of that. Of course, I can take the lazy route of building a normal AWS A= MI, which will not be as =E2=80=9Cclean and unused=E2=80=9D as the one sugg= ested in Colin=E2=80=99s article. But if there is a current way to do the c= leaner thing, I would like to know, please. Your best bet is to use the official FreeBSD AMI, do your changes, and build an AMI out of that. We do this with the help of ansible: - boot official ami - install ansible - download ansible playbooks from S3 to /tmp - run ansible - clean /tmp - build AMI - ... - PROFIT --=20 Michiel van Baak michiel@vanbaak.eu GPG key: http://pgp.mit.edu/pks/lookup?op=3Dget&search=3D0x6FFC75A2679ED069 NB: I have a new GPG key. Old one revoked and revoked key updated on keyser= vers. --2z62ewwcjxeipjdb Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEO9oGFWGYJa7y6GXGb/x1omee0GkFAlpD2QAACgkQb/x1omee 0GluBAgAp/bIq2pYyFkGzO/LdUMnSmbNMcAHcp1pO+PpJJ9wKLLod+H4U2ph+JGC T+Cngo4ACEnqd6bOZB7yYfiejeH3q1F4B7TzQag9LtSy9FrgZd+DlM5MKgJnksm6 5yCi5A74Ilp5jMN486h9bT8hQ7HGPaRgshzTj5aPLIDnNuPd1NT6tCrfLVTRZbop Wn1habdFTUApZL3W925MyVazwY7qJZJQtT/xGAq/dUPJDHci30pLN9L5hMpgU//Z 2yktOZf9MAXzrqJOwcNr3YJmGvCuVpfBBxGBHvxkC7kl5FfNtT6kGXMVdx8gyFGR fVxGy5+CeHWzi6VCcc+Lq409UTVMsQ== =CLgC -----END PGP SIGNATURE----- --2z62ewwcjxeipjdb--