Request from customer c311 using CFY 4.6:
Using OS plugin v2.14.15, in the case where a user provides their public SSH key, a VM cannot be created allowing access for the key without first importing the public key into OpenStack (also meaning it can't be removed on uninstall) and providing a path (in /etc/cloudify) to the private key (can be empty file).
In v3.x plugin, the public key can be specified in the keypair node and that's all that's required. This is the desired functionality for v2.x.
Do you mean that “import public key” is not supported in 2.X?
You can’t create a vm using v2 of the OS plugin with access allowed for a public key when all you have is the public key.
There are workarounds, but v2 doesn’t work as it should (like v3 plugin - it works), such as:
Regarding customer impact (from the customer):
“There are many workarounds for this issue; for example right now we are just cleaning platform in openstack after running "uninstall" workflow.
The problem is that we can't expose cloudify interface to the tenants - they must have access to openstack or to cloudify manager filesystem to make things working. Nor can we fully automate the end-to-end process using just cloudify.“
This sounds reasonable. of course if there are technical hurdles making it a risky/lengthy change please let me know. adding as a tentative fix for the Sprint 5 period.
I understand that the issue is import public key is not supported in v2. It is not a big change.