Ongoing modification to PCA columns
ignore mac finder droppings
standardize -> standardized
build_cloud_with_hosts(create_json=True) or build_cloud(create_json=True) will create h2o-nodes.json which is python-test-world-visible h2o.nodes state (not all used after cloud building, but it's there. we can prune the state down over time). Can be ingested by a non-cloud--building python test*.py to create a h2o.nodes object so that test stuff will just run (as if that test*.py created the cloud, when it didn't. psutil behaviors, and paramiko channel behaviors will have to be disabled. (mostly just in terminate() and is_alive() methods. I was playing with 'fake_cloud=True' state to do that, so maybe the ingest can set h2o.nodes[*].fake_cloud or something. maybe call it external_cloud. will noodle some more.
limit the depth of the h2o.nodes object walk for create_json (build_cloud_with_hosts(create_json=True) works)
build_cloud_with_json() seems usable (assumes default 'h2o-nodes.json' file was created by build_cloud(create_json=True)
don't need 'fake_cloud'. get rid of it
updated some stuff on cloud cloning for test-only python. print some stuff about running h2o and java processes if you do that. have the guy who built the cloud detect be able to say it's a sandbox error if he sees a cloud shutdown (test shouldn't shutdown the cloud)
copied these two here
simple test config setup. see test_config_basic.py for use
forgot this
show that you can extract something out of a param dictionary in the json
do verify_cloud_size() as well as checking the sandbox (every 60 secs) to make sure h2o is still there
add param for timeoutSecs to verify_cloud_size()/get_cloud()
add a little rf to the example
add deleting keys in the teardown, and add the other subtests from test.py, into the example
print out the url to browse the cloud like michal (the port changes)
I didn't push these
Merge branch 'master' of https://github.com/0xdata/h2o
tom wanted configuration dependent key delete at end of release tests. do it with cloud build state: delete_keys_at_teardown, which is passed thru the json like any othe python node state, to the test with the cloned cloud.
then that's used in h2o_common.py to decide what to do in tearDownClass. assumes you're using h2o_common.py like in test_release_basic.py (although you could just copy/paste and use without the common)
tom will say it's bloated, but a little test