From owner-freebsd-cloud@freebsd.org Tue Nov 7 23:36:04 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 B0D00E67929 for ; Tue, 7 Nov 2017 23:36:04 +0000 (UTC) (envelope-from raf@rafal.net) Received: from smtp-out-1.mxes.net (smtp-out-1.mxes.net [67.222.241.250]) (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 8E89077A4B for ; Tue, 7 Nov 2017 23:36:03 +0000 (UTC) (envelope-from raf@rafal.net) Received: from [192.168.40.37] (86-40-118-125-dynamic.agg2.bri.bbh-prp.eircom.net [86.40.118.125]) (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 E4D1B27508 for ; Tue, 7 Nov 2017 18:35:55 -0500 (EST) From: Rafal Lukawiecki Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: AWS c5.class unsupported? Message-Id: Date: Tue, 7 Nov 2017 23:35:53 +0000 To: freebsd-cloud@freebsd.org X-Mailer: Apple Mail (2.3445.4.7) X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 07 Nov 2017 23:36:04 -0000 I have just noticed that the official (=E2=80=9CColin=E2=80=9D) = Marketplace AMI for FreeBSD 11.1 is showing the c5.large instance type = (and the rest of c5) as unsupported and not available. May I ask what is = the reason? Many thanks, Rafal -- Rafal Lukawiecki Data Scientist=20 Project Botticelli Ltd From owner-freebsd-cloud@freebsd.org Wed Nov 8 00:33:12 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 E8461E68BC4 for ; Wed, 8 Nov 2017 00:33:12 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 D21BA7B97A for ; Wed, 8 Nov 2017 00:33:12 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [IPv6:2607:fb90:5d1:88bb:6ade:2d8f:4093:cdbd] (2607:fb90:5d1:88bb:6ade:2d8f:4093:cdbd [IPv6:2607:fb90:5d1:88bb:6ade:2d8f:4093:cdbd]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 5bcf1741 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 7 Nov 2017 16:33:07 -0800 (PST) Date: Tue, 07 Nov 2017 16:33:09 -0800 Subject: Re: AWS c5.class unsupported? Message-ID: <22772d45-812b-4592-87b7-7e9bafcc86f7@email.android.com> X-Android-Message-ID: <22772d45-812b-4592-87b7-7e9bafcc86f7@email.android.com> From: Pete Wright To: Rafal Lukawiecki Cc: freebsd-cloud@freebsd.org Importance: Normal X-Priority: 3 X-MSMail-Priority: Normal MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.23 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, 08 Nov 2017 00:33:13 -0000 From owner-freebsd-cloud@freebsd.org Wed Nov 8 00:38:09 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 0B58AE68DED for ; Wed, 8 Nov 2017 00:38:09 +0000 (UTC) (envelope-from raf@rafal.net) Received: from smtp-out-1.mxes.net (smtp-out-1.mxes.net [67.222.241.250]) (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 DB8D87BD0F for ; Wed, 8 Nov 2017 00:38:08 +0000 (UTC) (envelope-from raf@rafal.net) Received: from [192.168.40.37] (86-40-118-125-dynamic.agg2.bri.bbh-prp.eircom.net [86.40.118.125]) (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 84735274F9; Tue, 7 Nov 2017 19:38:06 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Re: AWS c5.class unsupported? From: Rafal Lukawiecki X-Priority: 3 In-Reply-To: <22772d45-812b-4592-87b7-7e9bafcc86f7@email.android.com> Date: Wed, 8 Nov 2017 00:38:04 +0000 Cc: freebsd-cloud@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <53A5CAA0-B37C-4BAE-A42A-338C04D9612E@rafal.net> References: <22772d45-812b-4592-87b7-7e9bafcc86f7@email.android.com> To: Pete Wright X-Mailer: Apple Mail (2.3445.4.7) X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.23 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, 08 Nov 2017 00:38:09 -0000 Ah, that explains the reason I have been seeing failed instance = launches. Metadata (user-data) scripts have been occasionally *not* = running when the cloudconfig run. Overall, I am finding c5.large is a little slower to start than = t2.medium, too. I suppose I will retest when they are officially = supported by FreeBSD. Many thanks for letting me know, I will add Colin to my Tweet = notifications. Rafal > On 8 Nov 2017, at 00:33, Pete Wright wrote: > Colin actually had a tweet about this earlier today: > https://twitter.com/cperciva/status/927768546129485824 > =20 > Sounds like he's working on it tho! >=20 > -pete From owner-freebsd-cloud@freebsd.org Wed Nov 8 00:47:31 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 59B63E692AB for ; Wed, 8 Nov 2017 00:47:31 +0000 (UTC) (envelope-from 0100015f991887de-8d9baeb9-0182-435d-876c-3c3863b05ac5-000000@amazonses.com) Received: from a8-237.smtp-out.amazonses.com (a8-237.smtp-out.amazonses.com [54.240.8.237]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 20B377C5EF for ; Wed, 8 Nov 2017 00:47:30 +0000 (UTC) (envelope-from 0100015f991887de-8d9baeb9-0182-435d-876c-3c3863b05ac5-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ae7m2yrxjw65l2cqdpjxuucyrvy564tn; d=tarsnap.com; t=1510102043; h=Subject:To:References:Cc:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; bh=r+42T5mwdWpKbXGwzQhozxJ3FHIZhhF9QqvIANEzuD8=; b=ILyhF5rfDtkyQblCPSYsubgydiTwUJ9k0Kmd47cxkVTnKsEeBrDEa4qROAIEEg5n 3ayj9qcaHV4j0vUS54/asR/IhhNh0R6hooQP9E6W01a80A82DCI90JYnYCazQ09gSju 0ouGrDNnWL6hauE+LkUp74lT05YVLQ/EHcVbbtTI= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1510102043; h=Subject:To:References:Cc:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=r+42T5mwdWpKbXGwzQhozxJ3FHIZhhF9QqvIANEzuD8=; b=gcdQnLQ2dUhqT1g4UBviN6jXj8JSCkih/RH55DdYrAcRWT4eb9e6lQaXYVbN2hq/ lLmbbrDs0PZtApfTtuIZFUBjw7CvgvWJo3xbvJ0TYsWFDnKeH/rWPcqEI4PlBjqMfCB yFuF6G0oH5u9d/JUChnu8AsHx0N7nS7Sg8f8Q6k0= Subject: Re: AWS c5.class unsupported? To: Rafal Lukawiecki , Pete Wright References: <22772d45-812b-4592-87b7-7e9bafcc86f7@email.android.com> <53A5CAA0-B37C-4BAE-A42A-338C04D9612E@rafal.net> Cc: freebsd-cloud@freebsd.org From: Colin Percival Message-ID: <0100015f991887de-8d9baeb9-0182-435d-876c-3c3863b05ac5-000000@email.amazonses.com> Date: Wed, 8 Nov 2017 00:47:23 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <53A5CAA0-B37C-4BAE-A42A-338C04D9612E@rafal.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-SES-Outgoing: 2017.11.08-54.240.8.237 Feedback-ID: 1.us-east-1.Lv9FVjaNvvR5llaqfLoOVbo2VxOELl7cjN0AOyXnPlk=:AmazonSES X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.23 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, 08 Nov 2017 00:47:31 -0000 On 11/07/17 16:38, Rafal Lukawiecki wrote: > Ah, that explains the reason I have been seeing failed instance launches. Metadata (user-data) scripts have been occasionally *not* running when the cloudconfig run. Actually no -- the problem I'm aware of has nothing to do with user-data scripts and should not affect instance launching. I wouldn't be surprised if some instance launches are failing due to capacity issues though -- EC2 often has such problems when they launch a new instance family. The problem I'm tracking with C5 relates to disk hotplug: If you add an EBS volume, FreeBSD will not notice it until you run 'devctl rescan pci0', and if you remove an EBS volume FreeBSD will panic. Warner is working on fixing the "hotunplug" path in the nvme driver in order to correct the panic; we were hoping to have it fixed in HEAD before C5 was launched, but I thought we had a few weeks left. If you have a good test case for user-data script problems, please let me know (off-list). Given how much new hardware and software there is in the C5 instances I wouldn't be surprised if there are a few bugs lurking, and I'm sure my contacts at EC2 will be happy to receive reports. (FWIW, C5 not being available in the Marketplace images is probably just a case of the Marketplace taking a while to get up to speed; I marked those images as "make these available on all new instances". But I'll probably go in and disable C5 for now due to the disk attach/detach issues.) -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-cloud@freebsd.org Wed Nov 8 00:59:27 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 AC824E695B9 for ; Wed, 8 Nov 2017 00:59:27 +0000 (UTC) (envelope-from raf@rafal.net) Received: from smtp-out-1.mxes.net (smtp-out-1.mxes.net [67.222.241.250]) (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 86E607CD48 for ; Wed, 8 Nov 2017 00:59:26 +0000 (UTC) (envelope-from raf@rafal.net) Received: from [192.168.40.37] (86-40-118-125-dynamic.agg2.bri.bbh-prp.eircom.net [86.40.118.125]) (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 2207B2753C; Tue, 7 Nov 2017 19:59:24 -0500 (EST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Re: AWS c5.class unsupported? From: Rafal Lukawiecki In-Reply-To: <0100015f99189134-61e4c63e-1f35-4854-ad9c-b4b62bb084a0-000000@email.amazonses.com> Date: Wed, 8 Nov 2017 00:59:23 +0000 Cc: Pete Wright , freebsd-cloud@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <22772d45-812b-4592-87b7-7e9bafcc86f7@email.android.com> <53A5CAA0-B37C-4BAE-A42A-338C04D9612E@rafal.net> <0100015f99189134-61e4c63e-1f35-4854-ad9c-b4b62bb084a0-000000@email.amazonses.com> To: Colin Percival X-Mailer: Apple Mail (2.3445.4.7) X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.23 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, 08 Nov 2017 00:59:27 -0000 > On 8 Nov 2017, at 00:47, Colin Percival wrote: >=20 > Actually no -- the problem I'm aware of has nothing to do with = user-data > scripts and should not affect instance launching. I wouldn't be = surprised > if some instance launches are failing due to capacity issues though -- = EC2 > often has such problems when they launch a new instance family. >=20 > The problem I'm tracking with C5 relates to disk hotplug: If you add = an EBS > volume, FreeBSD will not notice it until you run 'devctl rescan pci0', = and > if you remove an EBS volume FreeBSD will panic. Warner is working on = fixing > the "hotunplug" path in the nvme driver in order to correct the panic; = we > were hoping to have it fixed in HEAD before C5 was launched, but I = thought > we had a few weeks left. >=20 > If you have a good test case for user-data script problems, please let = me > know (off-list). Given how much new hardware and software there is in = the C5 > instances I wouldn't be surprised if there are a few bugs lurking, and = I'm > sure my contacts at EC2 will be happy to receive reports. >=20 > (FWIW, C5 not being available in the Marketplace images is probably = just a > case of the Marketplace taking a while to get up to speed; I marked = those > images as "make these available on all new instances". But I'll = probably go > in and disable C5 for now due to the disk attach/detach issues.) >=20 > --=20 > Colin Percival > Security Officer Emeritus, FreeBSD | The power to serve > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly = paranoid It was odd. Your cloudconfig seemed not to run *some* of the scripts (or = *none* of the scripts) that it got from the tar instance user-data. It = could have been related to a fluke co-incidence. During the project = development, I have, so far, launched 150+ t2.medium and c4.large and I = have never had this issue. Today I thought of testing c5.large but I = have only launched 12 of them. I had this problem in 1 case out of the = 12. On a side note, the performance our optimised web heads running FreeBSD = 11.1 + PHP 7 + Drupal 7 got from c5.large was on-par or a little worse = than from t2.medium in a short but intensive load test. I was surprised, = so perhaps there are some other issues lurking beneath. I was also = hoping the slowish EFS access would be faster, but it is no different at = the low-end of EFS storage it seems. Of course, t2 is limited to bursts, = so this is not a fair comparison to c5, but I was still hoping to see = better results even in a 5 min load. More testing needed, results inconclusive, I suppose. I am on a deadline = to complete the project this week, so I won=E2=80=99t go back to c5 = testing but happy to do that in about 5 weeks from now. Rafal=