Ok I did not have 3.2 and 3.3 installed, I did install them now and run tox and I see the errors.
I was only running the 2.7 tests manually.
I will make sure to run tox next time, sorry about that.
About the docs that's my bad, I wanted to fix the security group weird string passing and did not properly re-read everythign for compliance. I would have fixed it in a next commit.
thanks for the review. I will look more closely into it. This is merely a first step to get deploy_node to work. Right now It only works by passing a ssh_key parameter and expecting a ex_keyname in the kwargs of create_node. I did not implement tested the auth object. base.py is actually a bit confusing there because ssh_key in the features is used to say that you need a auth as NodeauthSSHKey, yet you can pass ssh_key and it will go forward with the deploy. If deploy only works with ssh_key can we set features to an empty dict ?
Indeed we also have ex_import_keypair calls in the driver, I will add the import_by_key_material, but I don't think it's very intuitive. A User that has already import or generated a keypair will know it by name and can specify by name instead of passing the actual pubkey, but that's just my opinion