There where some questions regarding direction for this on the fuel meeting
today. Can you elaborate on the status?
On Thu, Feb 12, 2015 at 12:01 PM, Andrew Woodward xar...@gmail.com wrote:
On Thu, Feb 12, 2015 at 3:59 AM, Tomasz Napierala tnapier...@mirantis.com
wrote:
On 10 Feb 2015,
On Thu, Feb 12, 2015 at 3:59 AM, Tomasz Napierala tnapier...@mirantis.com
wrote:
On 10 Feb 2015, at 23:02, Andrew Woodward xar...@gmail.com wrote:
previously we used squid in 3.0 and before. The main problem is that the
deployment would proceeded even if not all the packages where cached
On 02/10/2015 03:24 PM, Tomasz Napierala wrote:
Hi,
We are currently redesigning our apporach to upstream distributions and
obviusly we will need some cache system for packages on master node. It
should work for deb and rpm packages, and be able to serve up to 200 nodes.
I know we had bad
On 10 Feb 2015, at 23:02, Andrew Woodward xar...@gmail.com wrote:
previously we used squid in 3.0 and before. The main problem is that the
deployment would proceeded even if not all the packages where cached or even
available on the remote. This often lead to broken deployments that where
Hello Tomasz,
In a previous life, I used squid to speed up packages downloads and it
worked just fine...
Simon
On Tue, Feb 10, 2015 at 3:24 PM, Tomasz Napierala tnapier...@mirantis.com
wrote:
Hi,
We are currently redesigning our apporach to upstream distributions and
obviusly we will need
Hi,
We are currently redesigning our apporach to upstream distributions and
obviusly we will need some cache system for packages on master node. It should
work for deb and rpm packages, and be able to serve up to 200 nodes.
I know we had bad experience in the past, can you guys share your
On Tue, 2015-02-10 at 15:24 +0100, Tomasz Napierala wrote:
Hi,
We are currently redesigning our apporach to upstream distributions and
obviusly we will need some cache system for packages on master node. It should
work for deb and rpm packages, and be able to serve up to 200 nodes.
I know we
previously we used squid in 3.0 and before. The main problem is that the
deployment would proceeded even if not all the packages where cached or
even available on the remote. This often lead to broken deployments that
where hard to debug and a waste of alot of time. This _MUST_ be resolved or
we
