"dev" <dev-boun...@openvswitch.org> wrote on 07/03/2016 01:16:05 PM:
> From: Ben Pfaff <b...@ovn.org> > To: Nimay Desai <nimaydes...@gmail.com> > Cc: dev@openvswitch.org > Date: 07/03/2016 01:16 PM > Subject: Re: [ovs-dev] [PATCH v3] ovn-northd, tests: Adding IPAM to > ovn-northd. > Sent by: "dev" <dev-boun...@openvswitch.org> [snip for BW] > Usually we do not design OVSDB schemas so that daemons with different > purposes modify the same column, because it can be a recipe for > confusion. For example, we use separate columns in the Open_vSwitch > schema to report the MAC address for a port and to request that a port > be assigned a specific MAC address, because with a single column it's > difficult to distinguish whether its value is meant for one purpose or > the other. I am not sure that this is exactly the same case, but if we > were going to follow this principle here, too, I would add a new column > to Logical_Switch_Port for northd-assigned addresses. It could be > called "dynamic_addresses", for example. I certainly could get behind this idea... > I am not sure that I am comfortable with the idea of assigning a dynamic > address automatically when there is nothing in the addresses column. It > seems somewhat surprising. I would consider adding a new "addresses" > syntax to request a dynamic MAC/IP; for example, having it requested by > specifying "dynamic" in addresses. I can say I am rather uncomfortable, because I might want to create ports without an IP address and this precludes me from doing that. I like the idea of using the keyword idea to keep the nothing case meaning "I don't need an address yet" Ryan _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev