You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Evans Ye (JIRA)" <ji...@apache.org> on 2015/03/08 06:17:38 UTC

[jira] [Created] (BIGTOP-1735) Use puppet installed boxes/images directly to get rid off puppet installation

Evans Ye created BIGTOP-1735:
--------------------------------

             Summary: Use puppet installed boxes/images directly to get rid off puppet installation
                 Key: BIGTOP-1735
                 URL: https://issues.apache.org/jira/browse/BIGTOP-1735
             Project: Bigtop
          Issue Type: Improvement
          Components: deployment, vm
    Affects Versions: 0.8.0
            Reporter: Evans Ye
            Assignee: Evans Ye
            Priority: Minor


The BigTop VM/Docker provisioner takes at least 30 mins to complete, which is time consuming for CI tests. In addition, sometimes I got puppet installation failed like this:
{code}
==> bigtop1: http://yum.puppetlabs.com/el/6/products/x86_64/puppet-3.7.4-1.el6.noarch.rpm: [Errno 12] Timeout on http://yum.puppetlabs.com/el/6/products/x86_64/puppet-3.7.4-1.el6.noarch.rpm: (28, 'Operation too slow. Less than 1 bytes/sec transfered the last 30 seconds')
{code}

I think we can switch our deployment bases to those puppet pre-installed vagrant boxes and docker images: 
* vagrant-puppet-vm: puppetlabs/{centos,debian,ubuntu}-6.6-64-puppet
* vagrant-puppet-docker: bigtop/puppet:{centos,ubuntu}

Those boxes are pretty mature and even have more downloads than nocm boxes. 
At docker side, we can leverage bigtop_toolchain to do puppet installation in dockerfiles.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)