Difference between revisions of "Network/Meetings"
(→On Demand Agenda) |
Ionosphere80 (talk | contribs) (→On Demand Agenda) |
||
Line 62: | Line 62: | ||
** We need to document and create a single interface configuration - https://review.openstack.org/#/c/153208/ | ** We need to document and create a single interface configuration - https://review.openstack.org/#/c/153208/ | ||
* Dims needs Project Ideas, Mentors for GSoC 2015 - https://wiki.openstack.org/wiki/GSoC2015 (dims or dims__) | * Dims needs Project Ideas, Mentors for GSoC 2015 - https://wiki.openstack.org/wiki/GSoC2015 (dims or dims__) | ||
+ | * OVS and LinuxBridge agent configuration files | ||
+ | ** Prior to ML2, OVS and LinuxBridge were plugins with their own configuration files, ovs_neutron_plugin.ini and linuxbridge_conf.ini, respectively. After ML2, these plugins became agents/mechanisms and the installation guide now configures them in the ml2_conf.ini file using [ovs], [agent], etc. [1]. However, some downstream packagers still use ovs_neutron_plugin.ini and linuxbridge_conf.ini, the former of which generates the most confusion because it contains the word "plugin" and doesn't relate to a plugin anymore. These differing opinions periodically generate documentation bugs [2][3] that lack clear resolution. Can we officially resolve this issue? If separate files make sense, I suggest renaming them to reduce confusion regarding where they fit into the big picture... such as ml2_conf_ovs.ini, ovs_agent_conf.ini, etc. | ||
+ | ** [1] http://docs.openstack.org/juno/install-guide/install/apt/content/neutron-network-node.html | ||
+ | ** [2] https://bugs.launchpad.net/openstack-manuals/+bug/1422038 | ||
+ | ** [3] https://bugs.launchpad.net/openstack-manuals/+bug/1375746 | ||
== Previous meeting logs == | == Previous meeting logs == |
Revision as of 21:11, 23 February 2015