Kevin, you're right. My use case is that the plugin enriches the vif
binding information. The value is generated along the ml2 agents
configuration files (the name of the interface to plug the port to).
There's no input coming from the user via API.
Irina, thanks for clarification. binding:vif_det
Hi Andreas,
On Fri, Jun 26, 2015 at 4:04 PM, Andreas Scheuring <
scheu...@linux.vnet.ibm.com> wrote:
> Hi together,
> for a new ml2 plugin I would like to pass over some data from neutron to
> nova on port creation and update (exploiting port binding extension
> [1]). For my prototype I thought o
On Fri, Jun 26, 2015 at 8:14 AM, Neil Jerram
wrote:
> Hi Andreas,
>
> On 26/06/15 14:04, Andreas Scheuring wrote:
>
>> Hi together,
>> for a new ml2 plugin I would like to pass over some data from neutron to
>> nova on port creation and update (exploiting port binding extension
>> [1]). For my pr
That bug is about adding things that the user can pass to the port. I think
Andreas is just talking about passing data to Nova that his ML2 plugin
generates. The key difference would be that adding key/value pairs to the
port API that the user populates would be exposing implementation details
to u
Hi Andreas,
On 26/06/15 14:04, Andreas Scheuring wrote:
Hi together,
for a new ml2 plugin I would like to pass over some data from neutron to
nova on port creation and update (exploiting port binding extension
[1]). For my prototype I thought of using one of the following response
dictionaries t
Hi together,
for a new ml2 plugin I would like to pass over some data from neutron to
nova on port creation and update (exploiting port binding extension
[1]). For my prototype I thought of using one of the following response
dictionaries to add my information:
- binding:vif_details
- binding:pro
