Merge lp://staging/~freyes/openstack-charm-testing/fix-port_security into lp://staging/openstack-charm-testing

Per our conversation in IRC, its probably better to have the cloud declare its capabilities and the code take that into account.

In my stsstack, this code failed with:

Traceback (most recent call last):
  File "./bin/post-deploy-config", line 160, in <module>
    del new_port['port_security_enabled']
KeyError: 'port_security_enabled'

(full pastebin https://pastebin.canonical.com/193011/)

I commented out two lines:

"port_security_enabled": False,
del new_port['port_security_enabled']

And the script went through successfully.

davecore - yeah that's a good point. The del line should be:

del new_port['port']['port_security_enabled']

However, I think with the changes that Felipe and I discussed it would add the port_security_enabled flag to the port properties if the under-cloud's profile states it supports it.

The code repo for this project is now at the following location:
https://github.com/openstack-charmers/openstack-charm-testing