community 
VNF Shell Standard
I would like to see Quali Add a VNF Shells standard (template for shell development). While these are Virtual Appliances, they have more detailed networking needs when being added to a workflow, thus lend themselves to being defined as resources (instead of apps). The current networking hardware model is overly complex for a VNF. VNFs are much flatter in design than the current Unit/Chassis/Blade/Port hierarchy. And they have different discovery needs (so forking an existing hardware shell brings some baggage).
Some instances of VNF may mix and match different functional children (Routing + Firewall) with in the same deployment.
Having the flexibility to define the instancy by function, keeping relevant information to the function in the 'child' (which may include different IP address) will also lead to a more flexible design and deployment process.
And we can't ignore the VNF as App. I don't know what the answer here is; using the same template as a deployed app or developing its cousin as it's own template for deployed app. But a VNF Deployed App Template also seems logical.
