It wasn't meant as a which-is-best. But having an app that can be
deployed on both, allows you to find the parts that are uniquely tied to
one or the other, so you can make your app.yml much more sane and
honest(with itself).
On 02/27/2014 12:31 PM, Michael DeHaan wrote:
This is not the plac
This is not the place for which-distro-is-best and is off topic, see the
subject of this thread and what we are discussing.
On Thu, Feb 27, 2014 at 1:18 PM, Adam Heath wrote:
> Sure, but it's easier in debian, as snapshot/backports are also mirrored.
>
> On 02/27/2014 12:17 PM, Michael DeHaan
Sure, but it's easier in debian, as snapshot/backports are also mirrored.
On 02/27/2014 12:17 PM, Michael DeHaan wrote:
Was talking about yum.
--
You received this message because you are subscribed to the Google Groups "Ansible
Project" group.
To unsubscribe from this group and stop receivin
Was talking about yum.
On Thu, Feb 27, 2014 at 1:17 PM, Adam Heath wrote:
> On 02/27/2014 12:10 PM, Michael DeHaan wrote:
>
>> Yep, that can be a valid approach.
>>
>> "This seems much lighter weight then cloning an entire OS distribution,"
>>
>> It's much smaller than the apt repo, however.
On 02/27/2014 12:10 PM, Michael DeHaan wrote:
Yep, that can be a valid approach.
"This seems much lighter weight then cloning an entire OS distribution,"
It's much smaller than the apt repo, however.
The other bonus is being able to control the package versions on all of
your hosts and update
Yep, that can be a valid approach.
"This seems much lighter weight then cloning an entire OS distribution,"
It's much smaller than the apt repo, however.
The other bonus is being able to control the package versions on all of
your hosts and update when you choose while still coding only state=la
For yum, I disable fastestmirror, set hard-coded repo sites, then
configure an http_proxy.
For apt, I set hard-coded repo sites, then configure an http_proxy.
This seems much lighter weight then cloning an entire OS distribution,
when most packages aren't going to be installed anyways.
ps: i
We've been through this discussion a bit before, and we believe the
repoquery needs to be there.
I'm a bit more curious about why you are spending so much time in the
operation and most people are not.
When using yum in any sort of important setup, I almost always create a yum
mirror with reposyn
Some feedback
I tried a few things still to make it perform better, including mirror
repositories, but the fact that repoquery is forced on the user is perhaps
limiting... any ways to make that optional instead of using it if it is
present?
On Thursday, February 20, 2014 2:39:48 PM UTC+9, Mar
@cove_s nice :) I didn't get to go down that much, but that reflects pretty
well what I am experiencing.
@Adam @Michael at least for updates, NOT using repoquery made things faster
for me. What I did is change the code for the yum module to undefine the
repoquery path.
On Thursday, February 20
I just happen to add some crude log traces to my yum module last night to see
if I could figure out what it's doing.
On RPMs that are already installed it will use up all the CPU/IO for a while,
on a small instance it can take a long time. The instance I was testing with
was an m1.small, so it
I'm manually adding yum-utils in my RedHat installs as I am performing a
minimal install. I figured that this was my fault for trying to install as
little as possible. It might make some sense to document that dependency
in the yum module page though.
Adam
On Wednesday, February 19, 2014 5:0
+1
Also, what (remote) OS is this?
We'd have this discussion before, where yum-utils we were pretty sure was
only excluded in @core installs. That might not b e true though -- need
to check.
I have no problem making the yum module self-add yum-utils if not already
there if it resolves problems
I am away from my Ansible machine and test, however in my playbook the
first thing i do is update yum, and yum-utils to the latest update as i
had similar issues with older releases.
On 19 February 2014 11:59, Marc Trudel wrote:
> Quick note. My playbooks break if I do not have repoquery... t
Quick note. My playbooks break if I do not have repoquery... the code seems
to suggest this is optional, but I just found a case, for instance, where
checking for an already installed package gave me a recursion error, while
another fresh install failed on "failed to parse: SUDO-SUCCESS-whatever
I think I found the issue - seems to be related to repoquery
Following tests were done as suggested with the test-module on the host
With repoquery:
real0m21.014s
user0m4.094s
sys0m1.337s
Without repoquery:
real0m8.130s
user0m1.914s
sys0m0.449s
I guess it is then no long
./hacking/test-module in the checkout is pretty useful for things like this.
Do a checkout on a machine with yum and even inserting some basic print
statements or logging could be a useful start to find out what functions or
commands are taking the most time.
On Tue, Feb 18, 2014 at 7:47 PM, Mar
I'll remove fastest-mirror, it indeed looks like it made things slower
(this is in fact what I was adding to my stack as an experiment to make YUM
faster - at first I thought it was purely YUM-related issue).
I will try to find some information as to how to benchmark, but would you
have any rec
I see from the above that you said 50 seconds above and I misread. In your
case this is definitely slower than the actual command by a very decent
margin. I'm still not seeing this.
If you can benchmark where it is spending it's time that would be
appreciated.
I noticed you were installing fast
It runs some extra ops to ensure it doesn't need to run change-inducing
commands up front.
However I would disagree that 20% is "much slower".
Do make sure you have "fastest mirror" disabled, BTW, the module usually
isn't faster.
Local mirroring is also always a fantastic idea! Check out "yum
I notice that --enablerepos should be --enablerepo - no worries, I tested
with the right flags.
Also, just to make sure its not ssh related, I also tried:
time ssh 123.1322.0.453 "sudo yum install yum-presto yum-fastestmirror
yum-fast-downloader --enablerepo=personalrepo,rpmforge"
Which gave m
21 matches
Mail list logo
