You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Andrei Savu (Created) (JIRA)" <ji...@apache.org> on 2012/02/14 11:33:59 UTC

[jira] [Created] (WHIRR-513) Add integration test for BYON provider

Add integration test for BYON provider
--------------------------------------

                 Key: WHIRR-513
                 URL: https://issues.apache.org/jira/browse/WHIRR-513
             Project: Whirr
          Issue Type: Test
          Components: core
            Reporter: Andrei Savu
            Assignee: Andrei Savu
             Fix For: 0.8.0


We need some sort of automated integration tests for BYON. My suggestion is to use Whirr to start a bunch of noop nodes (on ec2 or cloudservers as configured), generate the .yaml file, and deploy a cluster using the byon provider. This way we can be sure that BYON works without doing a lot of manual testing with virtualbox / vmware. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (WHIRR-513) Add integration test for BYON provider

Posted by "Tom White (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WHIRR-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White updated WHIRR-513:
----------------------------

    Fix Version/s:     (was: 0.8.0)
                   0.8.1
    
> Add integration test for BYON provider
> --------------------------------------
>
>                 Key: WHIRR-513
>                 URL: https://issues.apache.org/jira/browse/WHIRR-513
>             Project: Whirr
>          Issue Type: Test
>          Components: core
>            Reporter: Andrei Savu
>            Assignee: Andrei Savu
>             Fix For: 0.8.1
>
>
> We need some sort of automated integration tests for BYON. My suggestion is to use Whirr to start a bunch of noop nodes (on ec2 or cloudservers as configured), generate the .yaml file, and deploy a cluster using the byon provider. This way we can be sure that BYON works without doing a lot of manual testing with virtualbox / vmware. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (WHIRR-513) Add integration test for BYON provider

Posted by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WHIRR-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209449#comment-13209449 ] 

Andrei Savu commented on WHIRR-513:
-----------------------------------

I agree. Can you share the Vagrantfile & the .yaml file you are using? Any other scripts? 
                
> Add integration test for BYON provider
> --------------------------------------
>
>                 Key: WHIRR-513
>                 URL: https://issues.apache.org/jira/browse/WHIRR-513
>             Project: Whirr
>          Issue Type: Test
>          Components: core
>            Reporter: Andrei Savu
>            Assignee: Andrei Savu
>             Fix For: 0.8.0
>
>
> We need some sort of automated integration tests for BYON. My suggestion is to use Whirr to start a bunch of noop nodes (on ec2 or cloudservers as configured), generate the .yaml file, and deploy a cluster using the byon provider. This way we can be sure that BYON works without doing a lot of manual testing with virtualbox / vmware. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (WHIRR-513) Add integration test for BYON provider

Posted by "Karel Vervaeke (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WHIRR-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234494#comment-13234494 ] 

Karel Vervaeke commented on WHIRR-513:
--------------------------------------

Note to future self:
Getting exceptions from FastDNSResolver (because there are no DNS entries for the virtualbox instances)?
Stack tracke here: https://gist.github.com/2149470
Workaround: Add entries to /etc/hosts, run dnsmasq, and use WHIRR_CLI_OPTS="-Ddns.search=localhost"
                
> Add integration test for BYON provider
> --------------------------------------
>
>                 Key: WHIRR-513
>                 URL: https://issues.apache.org/jira/browse/WHIRR-513
>             Project: Whirr
>          Issue Type: Test
>          Components: core
>            Reporter: Andrei Savu
>            Assignee: Andrei Savu
>             Fix For: 0.8.0
>
>
> We need some sort of automated integration tests for BYON. My suggestion is to use Whirr to start a bunch of noop nodes (on ec2 or cloudservers as configured), generate the .yaml file, and deploy a cluster using the byon provider. This way we can be sure that BYON works without doing a lot of manual testing with virtualbox / vmware. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (WHIRR-513) Add integration test for BYON provider

Posted by "Karel Vervaeke (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WHIRR-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230042#comment-13230042 ] 

Karel Vervaeke commented on WHIRR-513:
--------------------------------------

Currently I'm not calling vagrant from within unit tests.
The tests assume you have prepared the vm instances.
The CI server does a vagrant up before running the tests and vagrant destroy (only if the tests are successful so you can inspect the vm's when things go wrong).
You can use a vagrant plugin for working with snapshots - this speeds things up a bit (at the cost of having to pay more attention to clock synchronisation).
                
> Add integration test for BYON provider
> --------------------------------------
>
>                 Key: WHIRR-513
>                 URL: https://issues.apache.org/jira/browse/WHIRR-513
>             Project: Whirr
>          Issue Type: Test
>          Components: core
>            Reporter: Andrei Savu
>            Assignee: Andrei Savu
>             Fix For: 0.8.0
>
>
> We need some sort of automated integration tests for BYON. My suggestion is to use Whirr to start a bunch of noop nodes (on ec2 or cloudservers as configured), generate the .yaml file, and deploy a cluster using the byon provider. This way we can be sure that BYON works without doing a lot of manual testing with virtualbox / vmware. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (WHIRR-513) Add integration test for BYON provider

Posted by "Frank Scholten (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WHIRR-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228475#comment-13228475 ] 

Frank Scholten commented on WHIRR-513:
--------------------------------------

Awesome! Curious how this is implemented. Would you call vagrant from a JUnit test as a system process or via JRuby?
                
> Add integration test for BYON provider
> --------------------------------------
>
>                 Key: WHIRR-513
>                 URL: https://issues.apache.org/jira/browse/WHIRR-513
>             Project: Whirr
>          Issue Type: Test
>          Components: core
>            Reporter: Andrei Savu
>            Assignee: Andrei Savu
>             Fix For: 0.8.0
>
>
> We need some sort of automated integration tests for BYON. My suggestion is to use Whirr to start a bunch of noop nodes (on ec2 or cloudservers as configured), generate the .yaml file, and deploy a cluster using the byon provider. This way we can be sure that BYON works without doing a lot of manual testing with virtualbox / vmware. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (WHIRR-513) Add integration test for BYON provider

Posted by "Karel Vervaeke (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WHIRR-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209445#comment-13209445 ] 

Karel Vervaeke commented on WHIRR-513:
--------------------------------------

It's relatively easy to automate BYON tests virtualbox if you use vagrant. Basically you do 'vagrant up' before tests and 'vagrant destroy' after tests (or to speed things up, you can use a snapshot which you rollback to before every test - there are some vagrant plugins for that as well).

It does introduce a dependency on gems/ruby(jruby)/... (but could prove to be nice in a development setup)
                
> Add integration test for BYON provider
> --------------------------------------
>
>                 Key: WHIRR-513
>                 URL: https://issues.apache.org/jira/browse/WHIRR-513
>             Project: Whirr
>          Issue Type: Test
>          Components: core
>            Reporter: Andrei Savu
>            Assignee: Andrei Savu
>             Fix For: 0.8.0
>
>
> We need some sort of automated integration tests for BYON. My suggestion is to use Whirr to start a bunch of noop nodes (on ec2 or cloudservers as configured), generate the .yaml file, and deploy a cluster using the byon provider. This way we can be sure that BYON works without doing a lot of manual testing with virtualbox / vmware. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (WHIRR-513) Add integration test for BYON provider

Posted by "Karel Vervaeke (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WHIRR-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209471#comment-13209471 ] 

Karel Vervaeke commented on WHIRR-513:
--------------------------------------

Sure, I'll see if I can refactor an existing integration test to make it a meaningful contribution.
There's a Vagrant file, a yaml file and a puppet manifest to prepare the hosts file on each node.
                
> Add integration test for BYON provider
> --------------------------------------
>
>                 Key: WHIRR-513
>                 URL: https://issues.apache.org/jira/browse/WHIRR-513
>             Project: Whirr
>          Issue Type: Test
>          Components: core
>            Reporter: Andrei Savu
>            Assignee: Andrei Savu
>             Fix For: 0.8.0
>
>
> We need some sort of automated integration tests for BYON. My suggestion is to use Whirr to start a bunch of noop nodes (on ec2 or cloudservers as configured), generate the .yaml file, and deploy a cluster using the byon provider. This way we can be sure that BYON works without doing a lot of manual testing with virtualbox / vmware. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira