VNIC type is mainly used to determine how neutron should handle a port (e.g. which mechanism driver should handle the port). Reading the RFE bug description, it not clear on this point. The only need described is to make nova determine whetherr a corresponding port is managed by cybord. Could you clarify what kind of change is required from the point of view of processing a port in neutron?
Note that I am not necessarily against a new VNIC type but we need to clarify the impact on neutron. If the new VNIC type is a variant of existing VNIC types (like normal, direct and so on) we may need to explore another option.
In addition, regarding the naming, we don't use a project name like "cybord" in our API definition. The word used should be a name which represents a correspoding functionality rather than who implements the functionality.
VNIC type is mainly used to determine how neutron should handle a port (e.g. which mechanism driver should handle the port). Reading the RFE bug description, it not clear on this point. The only need described is to make nova determine whetherr a corresponding port is managed by cybord. Could you clarify what kind of change is required from the point of view of processing a port in neutron?
Note that I am not necessarily against a new VNIC type but we need to clarify the impact on neutron. If the new VNIC type is a variant of existing VNIC types (like normal, direct and so on) we may need to explore another option.
In addition, regarding the naming, we don't use a project name like "cybord" in our API definition. The word used should be a name which represents a correspoding functionality rather than who implements the functionality.