New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"apt install ansible" OR pre-compiled pip OR .deb needed (7X faster install) #249
Comments
Might get some inspiration from #164 but if you are looking to just deploy a tar file, think a virtual environment might be required to be able to scoop the files from one directory. This one looked useful and just over a year old so it's more current than whatever is in play now https://gist.github.com/dpalomar/96b826dac5c2e8b62cbf4c86dbd1c9df |
Update for @tim-moody : to lower RPi contributors' very high barriers to entry (constant refrain at Open Source Summit in LA last week: "involve new developers within 1 HOUR MAXIMUM") @jvonau & @georgejhunt have bravely tried to help me find a fast-installing Ansible 2.2.0 for IIAB 6.4 (via apt, pip, .deb, whatever @ #164) but no luck just yet :/ @jvonau surmises that Admin Console jobs are "SCHEDULED" but never actually moving forward due to:
|
|
FYI a clean install starting with apt's Ansible 2.2.1 on Raspbian Stretch Lite was attempted using http://download.iiab.io/6.4/rpi/load-min-ansibletest-vpn.txt which at least ran to completion, even though Admin Console did not work. Assisted by @jvonau. Recap:
FYI near the very end of ./runansible, munin failed with the following error:
So: vars/local_vars.yml was changed to "munin_install: False" and "munin_enabled: False" in order to allow the full bash script (load-min-ansibletest-vpn.txt) to complete... |
Missing from the initial load list but installing in scripts/ansible and
was not installed, debs: python-keyczar pips: pyrax pysphere boto
dnspython
…On Sat, Sep 16, 2017 at 10:20 PM, A Holt ***@***.***> wrote:
FYI a clean install starting with apt's Ansible 2.2.1 on Raspbian Stretch
Lite was attempted using http://download.iiab.io/6.4/
rpi/load-min-ansibletest-vpn.txt which at least ran to completion, even
though Admin Console did not work. Assisted by @jvonau
<https://github.com/jvonau>. Recap:
# apt -y install ansible python-kerberos python-selinux python-winrm (>= 0.1.1) python-xmltodict cowsay sshpass git bzip2 file findutils gzip hg svn sudo tar which unzip xz zip libselinux-python
# ABOVE LINE FAILED DUE TO THESE 6: (>= 0.1.1) hg svn which xz libselinux-python
# SO THE FOLLOWING WAS RUN INSTEAD
apt -y install python-kerberos python-selinux python-winrm python-xmltodict cowsay sshpass git bzip2 file findutils gzip sudo tar unzip zip
apt install ansible
***@***.***:~# ansible --version
ansible 2.2.1.0
config file = /etc/ansible/ansible.cfg
configured module search path = Default w/o overrides
FYI near the very end of ./runansible, munin failed with the following
error:
TASK [munin : Create admin user] >
fatal: [127.0.0.1]: FAILED! => {"changed": false, "failed": true, "msg": "invalid version number '1.7.0.post20170423015547'"}
to retry, use: --limit @/opt/iiab/iiab/iiab.retry
< PLAY RECAP >
127.0.0.1 : ok=297 changed=212 unreachable=0 failed=1
So: vars/local_vars.yml was changed to "munin_install: False" and
"munin_enabled: False" in order to allow the full bash script
(load-min-ansibletest-vpn.txt) to complete...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#249 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFUjvu-40QLi600Nfs7ISgc_JTZMVAuMks5sjJAGgaJpZM4PZs_v>
.
|
Notes from first pass of apt ansible install debs.txt |
console needs to adjust path to ansible in cmdsrv.conf |
apt correctly now installs Ansible 2.2.1 and has been tested with IIAB's Admin Console, thanks to @jvonau's heroic overnight work. This is now part of IIAB 6.4 Beta -- full explanation here: |
|
Currently we install Ansible 2.2.0 as follows which takes ~7 minutes on RPi3:
Let's accelerate our RPi install routine (by 5 min or more, very important for new contributors) using a ready-to-go Ansible like one of these possibly:
The text was updated successfully, but these errors were encountered: