[
https://issues.apache.org/jira/browse/BIGTOP-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286634#comment-14286634
]
jay vyas edited comment on BIGTOP-1584 at 1/22/15 12:32 AM:
------------------------------------------------------------
[~warwithin] despite reservations of having two ways to do the same thing... I
reviewed this patch because i can tell you really did alot of awesome work on
it.
- This is anawesome body of work, and its really cool that you took the time to
demonstrate this.
- Personally, I learned alot about ansible from reading through it.
- Would you be interested in writing up how you ported puppet recipes to
ansible for a *bigtop blog post* ?
*I don't know wether we can maintain this inside of bigtop* : its 1000+ lines
of code and 60 new files. REally a tremendous amount of stuff to maintain and
duplicate functionality to what we have.
In any case, im more than willing to continue testing this with you. Its a
good way to learn more about *ansible* and a *good reference implementation of
bigtop provsiioning on ansible*, and in the end we can at least
- have a wiki page which talks about how to ansibilize bigtop, maybe even
- github repo that you maintain that we can add to our {{README}} as an
unsupported ansible port of the puppet recipes.
So, anyways, I tried it out, and got this error :
{noformat}
==> bigtop1: warning:
==> bigtop1: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID c105b9de:
NOKEY
...
==> bigtop1: Running Transaction
Updating : libselinux-2.0.94-5.8.el6.x86_64 1/5
==> bigtop1:
Updating : libselinux-utils-2.0.94-5.8.el6.x86_64 2/5
...
Verifying : libselinux-utils-2.0.94-5.3.el6_4.1.x86_64 5/5
==> bigtop1:
==> bigtop1:
==> bigtop1: Installed:
==> bigtop1: libselinux-python.x86_64 0:2.0.94-5.8.el6
==> bigtop1:
==> bigtop1: Dependency Updated:
==> bigtop1: libselinux.x86_64 0:2.0.94-5.8.el6 libselinux-utils.x86_64
0:2.0.94-5.8.el6
==> bigtop1: Complete!
==> bigtop1: Running provisioner: ansible...
ANSIBLE_FORCE_COLOR=true ANSIBLE_HOST_KEY_CHECKING=false PYTHONUNBUFFERED=1
ansible-playbook
--private-key=/Users/Jpeerindex/.vagrant.d/insecure_private_key --user=vagrant
--inventory-file=../../ansible/inventory.single.example
--extra-vars={"ansible_ssh_user":"vagrant","bigtop_yum_repo":"http://bigtop01.cloudera.org:8080/view/Releases/job/Bigtop-0.8.0/label=centos6/6/artifact/output/","num_instances":1}
-v --limit='all' ../../ansible/site.yml
The executable 'ansible-playbook' Vagrant is trying to run was not
found in the PATH variable. This is an error. Please verify
this software is installed and on the path.
07:05:00 {1584} $
{noformat}
I'm more than happy to continue reviewing this code with you, but in the end, I
dont think its wise to have 2 ways of doing the same thing in bigtop. So lets
keep this as a investigation unless one of the other commiters feels they want
to +1 it for commit. At this point, im not comfortable doing that (even though
Im more than happy to keep reviewing iterations of this patch if you want to
put them in).
was (Author: jayunit100):
[~warwithin] despite reservations of having two ways to do the same thing... I
reviewed this patch because i can tell you really did alot of awesome work on
it.
- This is anawesome body of work, and its really cool that you took the time to
demonstrate this.
- Personally, I learned alot about ansible from reading through it.
- Would you be interested in writing up how you ported puppet recipes to
ansible for a *bigtop blog post* ?
*I don't know wether we can maintain this inside of bigtop* : its 1000+ lines
of code and 60 new files. REally a tremendous amount of stuff to maintain and
duplicate functionality to what we have.
In any case, im more than willing to continue testing this with you. Its a
good way to learn more about *ansible* and a *good reference implementation of
bigtop provsiioning on ansible*, and in the end we can at least
- have a wiki page which talks about how to ansibilize bigtop, maybe even
- github repo that you maintain that we can add to our {{README}} as an
unsupported ansible port of the puppet recipes.
{noformat}
==> bigtop1: warning:
==> bigtop1: rpmts_HdrFromFdno: Header V3 RSA/SHA1 Signature, key ID c105b9de:
NOKEY
==> bigtop1: Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
==> bigtop1: Importing GPG key 0xC105B9DE:
==> bigtop1: Userid : CentOS-6 Key (CentOS 6 Official Signing Key)
<[email protected]>
==> bigtop1: Package: centos-release-6-5.el6.centos.11.1.x86_64
(@anaconda-CentOS-201311272149.x86_64/6.5)
==> bigtop1: From : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
==> bigtop1: Running rpm_check_debug
==> bigtop1: Running Transaction Test
==> bigtop1: Transaction Test Succeeded
==> bigtop1: Running Transaction
Updating : libselinux-2.0.94-5.8.el6.x86_64 1/5
==> bigtop1:
Updating : libselinux-utils-2.0.94-5.8.el6.x86_64 2/5
==> bigtop1:
Installing : libselinux-python-2.0.94-5.8.el6.x86_64 3/5
==> bigtop1:
Cleanup : libselinux-utils-2.0.94-5.3.el6_4.1.x86_64 4/5
==> bigtop1:
Cleanup : libselinux-2.0.94-5.3.el6_4.1.x86_64 5/5
==> bigtop1:
Verifying : libselinux-utils-2.0.94-5.8.el6.x86_64 1/5
==> bigtop1:
Verifying : libselinux-2.0.94-5.8.el6.x86_64 2/5
==> bigtop1:
Verifying : libselinux-python-2.0.94-5.8.el6.x86_64 3/5
==> bigtop1:
Verifying : libselinux-2.0.94-5.3.el6_4.1.x86_64 4/5
==> bigtop1:
Verifying : libselinux-utils-2.0.94-5.3.el6_4.1.x86_64 5/5
==> bigtop1:
==> bigtop1:
==> bigtop1: Installed:
==> bigtop1: libselinux-python.x86_64 0:2.0.94-5.8.el6
==> bigtop1:
==> bigtop1: Dependency Updated:
==> bigtop1: libselinux.x86_64 0:2.0.94-5.8.el6 libselinux-utils.x86_64
0:2.0.94-5.8.el6
==> bigtop1: Complete!
==> bigtop1: Running provisioner: ansible...
ANSIBLE_FORCE_COLOR=true ANSIBLE_HOST_KEY_CHECKING=false PYTHONUNBUFFERED=1
ansible-playbook
--private-key=/Users/Jpeerindex/.vagrant.d/insecure_private_key --user=vagrant
--inventory-file=../../ansible/inventory.single.example
--extra-vars={"ansible_ssh_user":"vagrant","bigtop_yum_repo":"http://bigtop01.cloudera.org:8080/view/Releases/job/Bigtop-0.8.0/label=centos6/6/artifact/output/","num_instances":1}
-v --limit='all' ../../ansible/site.yml
The executable 'ansible-playbook' Vagrant is trying to run was not
found in the PATH variable. This is an error. Please verify
this software is installed and on the path.
07:05:00 {1584} $
{noformat}
I'm more than happy to continue reviewing this code with you, but in the end, I
dont think its wise to have 2 ways of doing the same thing in bigtop. So lets
keep this as a investigation unless one of the other commiters feels they want
to +1 it for commit. At this point, im not comfortable doing that (even though
Im more than happy to keep reviewing iterations of this patch if you want to
put them in).
> Ansible roles and playbooks for Bigtop
> --------------------------------------
>
> Key: BIGTOP-1584
> URL: https://issues.apache.org/jira/browse/BIGTOP-1584
> Project: Bigtop
> Issue Type: New Feature
> Components: deployment, tests, vm
> Affects Versions: 0.8.0
> Reporter: YoungWoo Kim
> Priority: Minor
> Attachments: BIGTOP-1584.WIP.patch
>
>
> Ansible is a well-known provisioning tool. http://www.ansible.com/
> It would be useful if Bigtop include the Ansible roles and playbooks for the
> Bigtop release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
