From owner-freebsd-current@FreeBSD.ORG Thu Nov 7 00:02:04 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 11883C2; Thu, 7 Nov 2013 00:02:04 +0000 (UTC) (envelope-from Devin.Teske@fisglobal.com) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C8FE32A08; Thu, 7 Nov 2013 00:02:03 +0000 (UTC) Received: from smtp.fisglobal.com ([10.132.206.16]) by ltcfislmsgpa05.fnfis.com (8.14.5/8.14.5) with ESMTP id rA701x0d006501 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 6 Nov 2013 18:01:59 -0600 Received: from LTCFISWMSGMB21.FNFIS.com ([169.254.1.152]) by LTCFISWMSGHT05.FNFIS.com ([10.132.206.16]) with mapi id 14.03.0158.001; Wed, 6 Nov 2013 18:01:57 -0600 From: "Teske, Devin" To: Glen Barber Subject: Re: [Review] bsdconfig pkgng integration Thread-Topic: [Review] bsdconfig pkgng integration Thread-Index: AQHO2x6RJrucrqXds0+MgGctNGb1BpoZR36A Date: Thu, 7 Nov 2013 00:01:57 +0000 Message-ID: <5B245AD6-DAEB-49E2-8E7F-323ED7A4B928@fisglobal.com> References: <527ACA8E.7010301@allanjude.com> <21C1BAD8-DC2F-4338-9AE5-28B28B64C933@fisglobal.com> <527ACE7B.6090002@allanjude.com> <20131106233218.GF1761@glenbarber.us> <39DE2EDF-69F3-43C5-AEDE-7A5399AC2859@fisglobal.com> <20131106234417.GG1761@glenbarber.us> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.132.253.120] Content-Type: multipart/signed; boundary="Apple-Mail=_02214403-73CD-450F-9EC2-79A7E20BE56B"; protocol="application/pgp-signature"; micalg=pgp-sha512 MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794, 1.0.431, 0.0.0000 definitions=2013-11-06_06:2013-11-06,2013-11-06,1970-01-01 signatures=0 Cc: Devin Teske , "Teske, Devin" , " Current" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Devin Teske List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2013 00:02:04 -0000 --Apple-Mail=_02214403-73CD-450F-9EC2-79A7E20BE56B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Nov 6, 2013, at 3:53 PM, Teske, Devin wrote: >=20 > On Nov 6, 2013, at 3:44 PM, Glen Barber wrote: >=20 >> On Wed, Nov 06, 2013 at 11:37:43PM +0000, Teske, Devin wrote: >>>> You do not need to show any servers except pkg.FreeBSD.org. >>>=20 >>> Bapt *just* got finished telling me in IRC that we should also list: >>>=20 >>> pkg.eu >>> pkg.us-* >>>=20 >>=20 >> Why? >>=20 >>> Which I assume to be the same make/model of pkg.f.o (does not >>> return an A or AAAA but only SVR). >>>=20 >>=20 >> And if we need to change something with the infrastructure, we now have >> to tell people that this was done. You are putting hard-coded >> limitations on us. Don't. >>=20 >=20 > I disagree. >=20 > You're making the argument for "what if a CDN goes away". >=20 > Well... people stop using that entry because it's broken and in the next = release > you remove it. >=20 > What sounds like a maintenance issue will actually save you support event= s. > And for whatever hours that this proposed maintenance actually cost you, = you'll > more than make up that in prevented support events. >=20 > I'm talking about saving time (because we're all volunteers, right?) >=20 > Let me be very explicit... >=20 >=20 >=20 >> With a single entry (pkg.FreeBSD.org), we do not have to worry about >> what is broken if (when) we need to change something. >>=20 >=20 > Let's say that the one entry doesn't do what you want (which requires tru= sting > the CDN maintenance on the back-end)... >=20 > You're telling me that it's more efficient to immediately defer every sin= gle user > to the support forums the moment there's a single hiccup in the ONE and O= NLY > CDN name that we're providing? >=20 > Ok... but let's look at one alternative... >=20 > If we listed more than one CDN, and one breaks... the wise and tenacious = user > simply ... tries another? >=20 > But if there are no other choices... then you'll be headed strait to the = forums or > mailing lists and generating what I call a "support event". >=20 > I'm sorry, but I don't agree that listing only one single entry is going = to be beneficial > to the end-user; only to the person that thinks having a single CDN to ma= intain is > going to actually save them work (which may only be true if they are not = the ones > that have to manage support events). I think there's a lot of misunderstanding going on because of the way that = clusteradm has set up our CDN. It is true that right now, pkg.f.o returns SRV records for all known mirror= s. It is also true that previously mentioned pkg.eu.f.o returns the one and on= ly SRV record for the one mirror in Europe. However, I am planning for a day when our CDN is administered in a more tra= ditional fashion. That is... I envisage pkg.f.o not returning all known mirrors (because there will be t= oo many as the CDN grows), but instead pkg.f.o would return only the 3 closest mirrors. Meanwhile, pkg.eu.f.o would grow to return records for the top-3 closest se= rvers in Europe. Just because the amount of machines that we have available for our CDN is s= mall, doesn't mean that it will be small forever. Eventually (as is the plan), the list of servers should far exceed the numb= er of SRV records you will want to return. And when we get to that point, I highly recommend = that we allow the user to choose the CDN specific to their country (at the very least). --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you. --Apple-Mail=_02214403-73CD-450F-9EC2-79A7E20BE56B Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJSeth1AAoJEKrMn5R9npq5YFEIAIRMa6nqerFn1wKu+dUjzEfG 2ZJv2M9+y+jWGHgEgvm7RpYhH9m2H9yF6ZK4spWsnmwzu7LUn8WMUrRl+okNfxli mMSj+y2oM+hIbIp2UMPIypVY7+m55YUBfn/Db8iFMFKwnOvMGEGoLT03MsYxfblY +OmLSmohMrtLJcoSMBYMSTcMWFtghXQA2F6fLhxFYwalJuZUNQrGEU0yr711LDX/ gbYCjq9aknDwoWIkVT57qnL6Ki+FEfGggJlkA4St+eHbBf+su+wzM1oWmG7XCcca ECWCbYUYumghvkhu496uSn8VUJ7uXCzerRAKSi7dYZKsluUfQygFRo9D16ld2sU= =BKYZ -----END PGP SIGNATURE----- --Apple-Mail=_02214403-73CD-450F-9EC2-79A7E20BE56B--