You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/03/09 15:11:00 UTC

[jira] [Commented] (METRON-1485) Upgrade vagrant for dev environments

    [ https://issues.apache.org/jira/browse/METRON-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392963#comment-16392963 ] 

ASF GitHub Bot commented on METRON-1485:
----------------------------------------

GitHub user JonZeolla opened a pull request:

    https://github.com/apache/metron/pull/959

    METRON-1485 Upgrade vagrant for dev environments

    ## Contributor Comments
    It looks like we are going to be forced into upgrading vagrant based on some HashiCorp deprecation activities.  See:
    
    https://www.hashicorp.com/blog/terraform-enterprise-saas-has-a-new-address
    
    I'm still digging around for the vagrant commit that fixes this in newer versions - I just upgraded to the latest and that fixed it.
    
    Currently, if you don't have centos6 or ubuntu14 locally, you get see something like the following:
    
    $ vagrant up
    Bringing machine 'node1' up with 'virtualbox' provider...
    ==> node1: Box 'centos/6' could not be found. Attempting to find and install...
    node1: Box Provider: virtualbox
    node1: Box Version: >= 0
    The box 'centos/6' could not be found or
    could not be accessed in the remote catalog. If this is a private
    box on HashiCorp's Atlas, please verify you're logged in via
    `vagrant login`. Also, please double-check the name. The expanded
    URL and error message are shown below:
    
    URL: ["https://atlas.hashicorp.com/centos/6"]
    Error: The requested URL returned error: 404 Not Found
    
    ## Testing
    Testing is underway, just need to upgrade vagrant and spin up the dev environment to test.  Review for errors and such.
    
    ## Pull Request Checklist
    
    Thank you for submitting a contribution to Apache Metron.  
    Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions.  
    Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) for complete smoke testing guides.  
    
    
    In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
    
    ### For all changes:
    - [ ] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
    - [ ] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    
    ### For code changes:
    - [ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed?
    - [ ] Have you included steps or a guide to how the change may be verified and tested manually?
    - [ ] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
      ```
      mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh 
      ```
    
    - [ ] Have you written or updated unit tests and or integration tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)?
    - [ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?
    
    ### For documentation related changes:
    - [ ] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via `site-book/target/site/index.html`:
    
      ```
      cd site-book
      mvn site
      ```
    
    #### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
    It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/JonZeolla/metron METRON-1485

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/metron/pull/959.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #959
    
----
commit 4ca17d5780729a61615e7ee6bc86e6ddf86c339e
Author: Nick Allen <ni...@...>
Date:   2017-11-27T20:29:38Z

    METRON-1320 Cannot perform a bare-metal installation

commit b64606997307e233a4ef9741c2ad16e622eac952
Author: Nick Allen <ni...@...>
Date:   2017-11-27T20:55:12Z

    Cleaning up after the C++ file(s) that we create

commit 551e3084c60346a6459101994043afa84869ab61
Author: Jon Zeolla <ze...@...>
Date:   2017-11-29T02:03:54Z

    Merge branch 'METRON-1320' of https://github.com/nickwallen/metron into METRON-1320

commit 1040681a59907fdedf8784bf19fc025cc9125b1c
Author: Jon Zeolla <ze...@...>
Date:   2017-12-05T12:56:40Z

    Merge branch 'master' of https://github.com/apache/metron

commit e916d3dcbeb744a426559d7e7e47695ebd37748b
Author: Jon Zeolla <ze...@...>
Date:   2017-12-06T14:00:51Z

    Merge branch 'master' of https://github.com/apache/metron

commit a7b5bdfd5652035beb38aed52fd4e1e12e680439
Author: Jon Zeolla <ze...@...>
Date:   2017-12-07T20:14:46Z

    Merge branch 'master' of https://github.com/apache/metron

commit f9af29979385877b90f7940561382c722404eff8
Author: Jon Zeolla <ze...@...>
Date:   2017-12-08T14:22:24Z

    Merge branch 'master' of https://github.com/apache/metron

commit 5c6dc76d9fbdb58274171446bc75800a42466ba2
Author: Jon Zeolla <ze...@...>
Date:   2017-12-27T12:34:43Z

    Merge branch 'master' of https://github.com/apache/metron

commit 4d52410120830ea0586b54fb2c85fdefc0a8444d
Author: Jon Zeolla <ze...@...>
Date:   2018-03-05T17:57:47Z

    Merge branch 'master' of https://github.com/jonzeolla/metron

commit fce1b423b1f890c612eec6d6c6e3a16acd6ee716
Author: Jon Zeolla <ze...@...>
Date:   2018-03-09T14:02:02Z

    Merge branch 'master' of https://github.com/apache/metron

commit 7dc33efad311e5ca2b82f615d73834c149edca27
Author: Jon Zeolla <ze...@...>
Date:   2018-03-09T14:08:58Z

    Merge branch 'master' of https://github.com/apache/metron

commit ae1bbbff25c6d2931c4795286bb681829ea8b145
Author: Jon Zeolla <ze...@...>
Date:   2018-03-09T15:05:37Z

    Suggest newer versions of vagrant

commit 06b583272101ebed351ac30ff2212364ed3b22af
Author: Jon Zeolla <ze...@...>
Date:   2018-03-09T15:08:38Z

    Fix platform info

----


> Upgrade vagrant for dev environments
> ------------------------------------
>
>                 Key: METRON-1485
>                 URL: https://issues.apache.org/jira/browse/METRON-1485
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Jon Zeolla
>            Assignee: Jon Zeolla
>            Priority: Major
>
> It looks like we are going to be forced into upgrading vagrant based on some HashiCorp deprecation activities.  See:
> [https://www.hashicorp.com/blog/terraform-enterprise-saas-has-a-new-address
> ]
> I'm still digging around for the vagrant commit that fixes this in newer versions - I just upgraded to the latest and that fixed it.
> Currently, if you don't have centos6 or ubuntu14 locally, you get see something like the following:
> $ vagrant up
> Bringing machine 'node1' up with 'virtualbox' provider...
> ==> node1: Box 'centos/6' could not be found. Attempting to find and install...
> node1: Box Provider: virtualbox
> node1: Box Version: >= 0
> The box 'centos/6' could not be found or
> could not be accessed in the remote catalog. If this is a private
> box on HashiCorp's Atlas, please verify you're logged in via
> `vagrant login`. Also, please double-check the name. The expanded
> URL and error message are shown below:
> URL: ["https://atlas.hashicorp.com/centos/6"]
> Error: The requested URL returned error: 404 Not Found



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)