diff options
author | distix ticketing system <distix@pieni.net> | 2018-04-01 14:40:04 +0000 |
---|---|---|
committer | distix ticketing system <distix@pieni.net> | 2018-04-01 14:40:04 +0000 |
commit | da29002d8f6b162de89c13ab84f476366b2f22f7 (patch) | |
tree | 1ed0233950e1c9f9aed44871341984ddc50626be | |
parent | 4be734496160193733597c703862d124f4df83bd (diff) | |
download | ick-devel-distix-da29002d8f6b162de89c13ab84f476366b2f22f7.tar.gz |
imported mails
-rw-r--r-- | tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/new/1522593604.M320216P9506Q1.koom | 162 |
1 files changed, 162 insertions, 0 deletions
diff --git a/tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/new/1522593604.M320216P9506Q1.koom b/tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/new/1522593604.M320216P9506Q1.koom new file mode 100644 index 0000000..e82b766 --- /dev/null +++ b/tickets/4bbc9995f89d40c59451b743be4a4811/Maildir/new/1522593604.M320216P9506Q1.koom @@ -0,0 +1,162 @@ +Return-Path: <ick-discuss-bounces@ick.liw.fi> +X-Original-To: distix@pieni.net +Delivered-To: distix@pieni.net +Received: from yaffle.pepperfish.net (yaffle.pepperfish.net [88.99.213.221])
+ by pieni.net (Postfix) with ESMTPS id 055E5404C0
+ for <distix@pieni.net>; Sun, 1 Apr 2018 14:39:09 +0000 (UTC) +Received: from platypus.pepperfish.net (unknown [10.112.101.20])
+ by yaffle.pepperfish.net (Postfix) with ESMTP id E347D417A0
+ for <distix@pieni.net>; Sun, 1 Apr 2018 15:39:08 +0100 (BST) +Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net)
+ by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
+ id 1f2e8S-0006LY-SM; Sun, 01 Apr 2018 15:39:08 +0100 +Received: from koom.pieni.net ([88.99.190.206] helo=pieni.net)
+ by platypus.pepperfish.net with esmtpsa (Exim 4.80 #2 (Debian))
+ id 1f2e8R-0006LM-Vu
+ for <ick-discuss@ick.liw.fi>; Sun, 01 Apr 2018 15:39:08 +0100 +Received: from exolobe3 (62-78-212-250.bb.dnainternet.fi [62.78.212.250])
+ by pieni.net (Postfix) with ESMTPSA id 8CF69404C0
+ for <ick-discuss@ick.liw.fi>; Sun, 1 Apr 2018 14:39:07 +0000 (UTC) +Message-ID: <1522593545.2971.15.camel@liw.fi> +From: Lars Wirzenius <liw@liw.fi> +To: ick-discuss@ick.liw.fi +Date: Sun, 01 Apr 2018 17:39:05 +0300 +In-Reply-To: <1522581877.10476.1@ssh.steve.org.uk> +References: <1522571699.2971.5.camel@liw.fi>
+ <1522581877.10476.1@ssh.steve.org.uk> +X-Mailer: Evolution 3.22.6-1+deb9u1 +Mime-Version: 1.0 +X-Pepperfish-Transaction: 8bb5-6166-19f4-3374 +X-Pepperfish-Transaction-By: platypus +Subject: Re: What's needed before ick is ready for others to use? +X-BeenThere: ick-discuss@ick.liw.fi +X-Mailman-Version: 2.1.5 +Precedence: list +List-Id: discussions about the ick CI system <ick-discuss-ick.liw.fi> +List-Unsubscribe: <https://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/ick-discuss-ick.liw.fi>,
+ <mailto:ick-discuss-request@ick.liw.fi?subject=unsubscribe> +List-Archive: <http://listmaster.pepperfish.net/pipermail/ick-discuss-ick.liw.fi> +List-Post: <mailto:ick-discuss@ick.liw.fi> +List-Help: <mailto:ick-discuss-request@ick.liw.fi?subject=help> +List-Subscribe: <https://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/ick-discuss-ick.liw.fi>,
+ <mailto:ick-discuss-request@ick.liw.fi?subject=subscribe> +Content-Type: multipart/mixed; boundary="===============0111444398513094452==" +Mime-version: 1.0 +Sender: ick-discuss-bounces@ick.liw.fi +Errors-To: ick-discuss-bounces@ick.liw.fi + + +--===============0111444398513094452== +Content-Type: multipart/signed; micalg="pgp-sha512";
+ protocol="application/pgp-signature"; boundary="=-9hJtkkRaWgXAlYTWKXvA" + + +--=-9hJtkkRaWgXAlYTWKXvA +Content-Type: text/plain; charset="UTF-8" +Content-Transfer-Encoding: quoted-printable + +On Sun, 2018-04-01 at 11:24 +0000, Steve Kemp wrote:
+> > This morning I've been pondering on the following question: should I
+> > try to achieve "ready for others to use" as soon as possible, or
+> > should I concentrate on making sure all existing functionality is of
+> > high quality?
+>=20
+> I think there are pros and cons to either approach, but one thing
+> that I'm struggling with myself is the documentation.
+
+That's a very good point. Not much hope of other people using ick if
+they don't know how to do that.
+
+Of course, I will need help to provider or at least to review and test
+any installation and use documentation. I hope to update the
+architecture documentation on my own, but feedback on that will be
+most welcome as well.
+
+> I would love to see an overview of all the moving parts:
+>=20
+> * There is one ick-server / controller.
+> * This is what it needs
+> * This is how you configure it.is a=20
+>=20
+> * There is one artifact server.
+> * This is what it needs.
+> * This is how you configure it.
+>=20
+> * There are N-workers / worker-managers.
+> * This is what they need.
+> * This is how you configure them.
+>=20
+> Right now I've spent more time than I'd enjoy getting the
+> package(s) installed - in the end I resorted to your debian repository
+> but even that wasn't sufficient.
+>=20
+> Getting the artifact-server running, for example, required installation
+> of `python3-requests`. There was also some confusion about
+> `python-cliapp` being a dependency, but the code using `python3-cliapp`,
+> the latter of which couldn't be installed without forcing, as it
+> overwrote a file in the previous package.
+
+python-requests (for Python 2) is a build dependency, because the
+integration test suite still uses Python 2 and need python-requests.
+Ick itself, including the artifact store, uses python3-requests.
+
+The versions of cliapp (python-, python3-) on code.liw.fi work
+simultanously for me. There's an older version in stretch that
+conflicts with python3-cliapp from code.liw.fi, however. I think.
+Haven't tested recently.
+
+> The ansible role helps, but the random start-scripts in the top-level
+> are a distraction.
+
+Which scripts do you mean?
+
+> > I suspect there is a security problem with the artifact server, but
+> despite reading the architecture guide I'm missing the ability to
+> confirm it.
+
+Er, yes, I think you're right. The paths should be sanitised. Thanks
+for pointing that out, I will fix asap.
+
+I'm sorry you failed to get ick working, but I'm glad to hear you
+tried. If you're willing to try again and tell me more about what
+doesn't work, I would be most grateful. +--=-9hJtkkRaWgXAlYTWKXvA +Content-Type: application/pgp-signature; name="signature.asc" +Content-Description: This is a digitally signed message part +Content-Transfer-Encoding: 7bit + +-----BEGIN PGP SIGNATURE-----
+
+iQIzBAABCgAdFiEETNTnrewG6wEE1EJ3bC+mFux6IDEFAlrA7wkACgkQbC+mFux6
+IDFBpg/9HaDGXZhyu+1K/FIUWKLlUh+6nrm2bMSpQSrbgTndSBFgb64A/B9LB5UY
+Ha73A7UTqUoF0NVNIAjSzxMR4Ctvvkl7q8f6qzk16X9XM2UKBCL9wbMlJGFMlPHH
+77/L8W4w0vOi04MOIAoYNSiYgUHLlM7FVxCDGczSN6odBOcGqP3u9nvrOF/XmZAY
+CrR8s9s2DvqTyRarkYSpPhshcxV5VtKz4M5YP3Nayl8cbEgHld/Pl+JOoFFc42UE
+tVL2KQFYQwk0naDM2Emu0Da3BEQSyuIUxUS5u8QIV27pdrmpOzppPTKNsduf/xhR
+H9CJiYsAuXpWgisUdvkjKYBG3O4E6+bQvUizpTtQzv8oi3iT5qNacgkitz+cYqU7
+kyY70XzUsn+SsB72mbUWVQu0DI+R0uJwC775f9jKdXjGgqRPjEl7OiBteRvaQzXB
+7Da/7fsPFFNAQa66PczRONrORlP9XqgNwP1HHeWJDRI4z9W2doc0MC69X9z1Pxi7
+Dno8spIpmKz4V3MhIDmp9GlwgnVHewJNW4vAMckYaZMG89KvIOHo04Vf3sL6b0EZ
+XrGQ50jwGgbFGsqQ4iECCu7Y6MSFC+wwVex8jcz7sVJ9RyFZCk7FdkfE6vmh1k+1
+Ie4CMeRi/cjxmOqi24G8rWjCROUTCNS6rYTDBohVWw4Ch9Ngf1U=
+=/IPM
+-----END PGP SIGNATURE-----
+ +--=-9hJtkkRaWgXAlYTWKXvA-- +
+
+ +--===============0111444398513094452== +Content-Type: text/plain; charset="us-ascii" +MIME-Version: 1.0 +Content-Transfer-Encoding: 7bit +Content-Disposition: inline + +_______________________________________________
+ick-discuss mailing list
+ick-discuss@ick.liw.fi
+https://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/ick-discuss-ick.liw.fi
+ +--===============0111444398513094452==-- +
+
|