Configure compute node in OpenStack Installation Guide for Ubuntu 12.04/14.04 (LTS)  - icehouse

Bug #1371878 reported by omar-cloudscaling
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-manuals
Won't Fix
Undecided
Matt Kassawara

Bug Description

Under configure compute node - - ml2.conf is irrelevant for the agent. The agent is not aware that ML2 plugin is being used. The right configuration file here (for OVS agent) is ovs_neutron_plugin.ini.

-----------------------------------
Built: 2014-09-19T07:50:45 00:00
git SHA: 7241eb0fbd6dedac9007a28863fe7dcbf361e96f
URL: http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron-ml2-compute-node.html
source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-ml2-compute-node.xml
xml:id: neutron-ml2-compute-node

Revision history for this message
Tom Fifield (fifieldt) wrote :

Matt, can you check this for Juno?

Changed in openstack-manuals:
assignee: nobody → Matt Kassawara (ionosphere80)
milestone: none → juno
Revision history for this message
Matt Kassawara (ionosphere80) wrote :

The [ovs] section in ml2_conf.ini contains the OVS agent configuration.

Changed in openstack-manuals:
status: New → Invalid
Revision history for this message
omar-cloudscaling (f-omar) wrote : Re: [Bug 1371878] Re: Configure compute node in OpenStack Installation Guide for Ubuntu 12.04/14.04 (LTS) - icehouse

Yes. But the [OVS] section is copied and pasted from
ovs_neutron_plugin.ini. The rest of the original ML2 conf in in
ml2_conf.ini is not used by the agent.
So why don't the agent configuration just used ovs_neutron_plugin.ini ?
It is was straight forward.

On Tue, Sep 23, 2014 at 7:08 AM, Matt Kassawara <email address hidden>
wrote:

> The [ovs] section in ml2_conf.ini contains the OVS agent configuration.
>
> ** Changed in: openstack-manuals
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1371878
>
> Title:
> Configure compute node in OpenStack Installation Guide for Ubuntu
> 12.04/14.04 (LTS) - icehouse
>
> Status in OpenStack Manuals:
> Invalid
>
> Bug description:
> Under configure compute node - - ml2.conf is irrelevant for the
> agent. The agent is not aware that ML2 plugin is being used. The
> right configuration file here (for OVS agent) is
> ovs_neutron_plugin.ini.
>
>
> -----------------------------------
> Built: 2014-09-19T07:50:45 00:00
> git SHA: 7241eb0fbd6dedac9007a28863fe7dcbf361e96f
> URL:
> http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron-ml2-compute-node.html
> source File:
> file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-ml2-compute-node.xml
> xml:id: neutron-ml2-compute-node
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-manuals/+bug/1371878/+subscriptions
>

Revision history for this message
Matt Kassawara (ionosphere80) wrote :

The ovs_neutron_plugin.ini file is associated with the deprecated OVS plug-in and use by the ML2 plug-in is potentially specific to distribution packages.

Revision history for this message
omar-cloudscaling (f-omar) wrote :

Yes, I am aware that OVS and Linuxbridge "plugins" will be deprecated in
favor of ML2.

Both have their own config files. The config files contains section for
the plugin part and the agent part.

What I anticipated will happen when OVS plugin is eventually removed, its
that the ovs_neutron_plugin.ini will just be renamed (to something like
ovs_neutron_agent.ini), with the "ovs plugin" specific sections removed.
And the same would go for linux bridge.

And I would anticipate that all supported ML2 agents will have it's own
config files. (i.e. neutron_lb_agent --config-file=lb_neutron_agent.ini;
 and neutron_ovs_agent --config-file=ovs_neutron_agent.ini); rather than
being lumped inside ml2-conf.ini.

The ML2 mechanism (config by ml2-conf.ini) is specific to the plugin.
 ml2-conf.ini as is right now - without being manually migrating the
configs from ovs_neutron_plugin.ini, does absolutely nothing to the agent.

(Not to mention, the Ubuntu apt-get repo is still calling the service
 "neutron-plugin-openvswitch-agent" which make sense that it is configured
by ovs_neutron_plugin.ini)

On Tue, Sep 23, 2014 at 10:53 AM, Matt Kassawara <email address hidden>
wrote:

> The ovs_neutron_plugin.ini file is associated with the deprecated OVS
> plug-in and use by the ML2 plug-in is potentially specific to
> distribution packages.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1371878
>
> Title:
> Configure compute node in OpenStack Installation Guide for Ubuntu
> 12.04/14.04 (LTS) - icehouse
>
> Status in OpenStack Manuals:
> Invalid
>
> Bug description:
> Under configure compute node - - ml2.conf is irrelevant for the
> agent. The agent is not aware that ML2 plugin is being used. The
> right configuration file here (for OVS agent) is
> ovs_neutron_plugin.ini.
>
>
> -----------------------------------
> Built: 2014-09-19T07:50:45 00:00
> git SHA: 7241eb0fbd6dedac9007a28863fe7dcbf361e96f
> URL:
> http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron-ml2-compute-node.html
> source File:
> file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-ml2-compute-node.xml
> xml:id: neutron-ml2-compute-node
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-manuals/+bug/1371878/+subscriptions
>

Revision history for this message
Matt Kassawara (ionosphere80) wrote :

I don't see any deployments using a separate configuration file for the OVS or LB agents. Maybe a plan for Kilo?

Revision history for this message
omar-cloudscaling (f-omar) wrote :

It has been a convention for Neutron agent's to have it's own config files
(e.g.: l3 agent, dhcp agent..). If OVS and LB agent becomes an
independent agent by itself (that works with ML2 plugin), I would
anticipate the convention of agent specific config file is adhered.

On Tue, Sep 23, 2014 at 11:54 AM, Matt Kassawara <email address hidden>
wrote:

> I don't see any deployments using a separate configuration file for the
> OVS or LB agents. Maybe a plan for Kilo?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1371878
>
> Title:
> Configure compute node in OpenStack Installation Guide for Ubuntu
> 12.04/14.04 (LTS) - icehouse
>
> Status in OpenStack Manuals:
> Invalid
>
> Bug description:
> Under configure compute node - - ml2.conf is irrelevant for the
> agent. The agent is not aware that ML2 plugin is being used. The
> right configuration file here (for OVS agent) is
> ovs_neutron_plugin.ini.
>
>
> -----------------------------------
> Built: 2014-09-19T07:50:45 00:00
> git SHA: 7241eb0fbd6dedac9007a28863fe7dcbf361e96f
> URL:
> http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron-ml2-compute-node.html
> source File:
> file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-ml2-compute-node.xml
> xml:id: neutron-ml2-compute-node
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-manuals/+bug/1371878/+subscriptions
>

Revision history for this message
omar-cloudscaling (f-omar) wrote :

By the way, by using the ml2-conf.ini instead of the
ovs_neutron_plugin.ini and giving only the limited value that was paster
from the latter to the former; you are depriving the readers who are not
familiar with opevswitch agent of other configurations needed to fine tune
and customize the agent.

eg:
polling interval
vxlan_udp_port
integration_bridge name
tunnel_bridge name
....
..

Until OVS plugin in removed and the agent code (and ini file relocated),
 OVS agent should still be based on ovs_neutron_plugin.ini.

(Not to mention starting up OVS agent with ml2-conf.ini as is which has
absolutely no relevance to the agent's workings at all)

On Tue, Sep 23, 2014 at 12:06 PM, Omar Khalid <email address hidden> wrote:

> It has been a convention for Neutron agent's to have it's own config files
> (e.g.: l3 agent, dhcp agent..). If OVS and LB agent becomes an
> independent agent by itself (that works with ML2 plugin), I would
> anticipate the convention of agent specific config file is adhered.
>
> On Tue, Sep 23, 2014 at 11:54 AM, Matt Kassawara <email address hidden>
> wrote:
>
>> I don't see any deployments using a separate configuration file for the
>> OVS or LB agents. Maybe a plan for Kilo?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1371878
>>
>> Title:
>> Configure compute node in OpenStack Installation Guide for Ubuntu
>> 12.04/14.04 (LTS) - icehouse
>>
>> Status in OpenStack Manuals:
>> Invalid
>>
>> Bug description:
>> Under configure compute node - - ml2.conf is irrelevant for the
>> agent. The agent is not aware that ML2 plugin is being used. The
>> right configuration file here (for OVS agent) is
>> ovs_neutron_plugin.ini.
>>
>>
>> -----------------------------------
>> Built: 2014-09-19T07:50:45 00:00
>> git SHA: 7241eb0fbd6dedac9007a28863fe7dcbf361e96f
>> URL:
>> http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron-ml2-compute-node.html
>> source File:
>> file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-ml2-compute-node.xml
>> xml:id: neutron-ml2-compute-node
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/openstack-manuals/+bug/1371878/+subscriptions
>>
>
>

Tom Fifield (fifieldt)
Changed in openstack-manuals:
status: Invalid → New
status: New → Incomplete
Revision history for this message
Sean Winn (seanmwinn) wrote :

Those options for the agent are all documented in the official documentation at http://docs.openstack.org/icehouse/config-reference/content/networking-plugin-openvswitch_agent.html

The sample configurations are meant to be just that, samples of what's necessary to get started. None of the other projects includes every configuration option possible in the sample configs.

This does not appear to be a bug. I am able to get everything working in neutron by following the official documentation. All of the previous options are still supported, the config file location has just been simplified down to a single file for the ml2 plugin driver to prepare for the deprecation of the openvswitch plugin driver.

While supporting individual config files for the ovs agent would be consistent with how the other agents are configured, I think that would require an actual code change in the agent itself. As the code stands today, this is not an actual bug.

Changed in openstack-manuals:
status: Incomplete → Invalid
Revision history for this message
omar-cloudscaling (f-omar) wrote :

<< The sample configurations are meant to be just that, samples >>

They are not part of the source code structure. Programmers update the
corresponding config files as they developed

The documentation came from the source code.

This is a bazaar, not a cathedral.

<< All of the previous options are still supported >>

Of course they are "supported" since they are "pasted" to the ml2-conf.ini.

However the usage of ml2-conf.ini is inappropriate because :

(1) It wasn't meant for the agent

(2) The OVS agent has it's own config file.

And if perchance that an agent does needs to refer to ml2-conf.ini (afaik
neither LB nor OVS agents), then the process should start with
--config-file options for each config files needed.

<< I think that would require an actual code change in the agent itself >>

There is no code change in the openstack source code.

The code change you are referring to is the daemon service script created
and installed by Ubuntu packaging (that mistakenly uses ml2-conf.ini
for ovs agent).

Please refer to Neutron TOT source code.

Openvswitch (and Linux bridge) plugin has already been removed.

The configuration is as what I have been telling you !

They are keeping it as a separate OVS config file used for agent. No
merging with ml2-conf.ini whatsoever.

The document and ubuntu packaging to start the OVS agent with ml2-conf.ini
is wrong.

On Wed, Oct 15, 2014 at 2:28 PM, Matt Kassawara <email address hidden>
wrote:

> ** Changed in: openstack-manuals
> Status: Incomplete => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1371878
>
> Title:
> Configure compute node in OpenStack Installation Guide for Ubuntu
> 12.04/14.04 (LTS) - icehouse
>
> Status in OpenStack Manuals:
> Invalid
>
> Bug description:
> Under configure compute node - - ml2.conf is irrelevant for the
> agent. The agent is not aware that ML2 plugin is being used. The
> right configuration file here (for OVS agent) is
> ovs_neutron_plugin.ini.
>
>
> -----------------------------------
> Built: 2014-09-19T07:50:45 00:00
> git SHA: 7241eb0fbd6dedac9007a28863fe7dcbf361e96f
> URL:
> http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron-ml2-compute-node.html
> source File:
> file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-ml2-compute-node.xml
> xml:id: neutron-ml2-compute-node
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-manuals/+bug/1371878/+subscriptions
>

Revision history for this message
omar-cloudscaling (f-omar) wrote :

Correction.

-->"They are not part of the source code structure."

They are part of the source code tree structure.

On Wed, Oct 15, 2014 at 3:35 PM, Omar Khalid <email address hidden> wrote:

> << The sample configurations are meant to be just that, samples >>
>
>
> They are not part of the source code structure. Programmers update the
> corresponding config files as they developed
>
> The documentation came from the source code.
>
> This is a bazaar, not a cathedral.
>
>
>
> << All of the previous options are still supported >>
>
>
> Of course they are "supported" since they are "pasted" to the ml2-conf.ini.
>
> However the usage of ml2-conf.ini is inappropriate because :
>
>
> (1) It wasn't meant for the agent
>
> (2) The OVS agent has it's own config file.
>
>
> And if perchance that an agent does needs to refer to ml2-conf.ini (afaik
> neither LB nor OVS agents), then the process should start with
> --config-file options for each config files needed.
>
>
>
>
> << I think that would require an actual code change in the agent itself
> >>
>
>
> There is no code change in the openstack source code.
>
> The code change you are referring to is the daemon service script created
> and installed by Ubuntu packaging (that mistakenly uses ml2-conf.ini
> for ovs agent).
>
>
>
>
> Please refer to Neutron TOT source code.
>
> Openvswitch (and Linux bridge) plugin has already been removed.
>
> The configuration is as what I have been telling you !
>
> They are keeping it as a separate OVS config file used for agent. No
> merging with ml2-conf.ini whatsoever.
>
>
>
>
> The document and ubuntu packaging to start the OVS agent with ml2-conf.ini
> is wrong.
>
>
>
> On Wed, Oct 15, 2014 at 2:28 PM, Matt Kassawara <email address hidden>
> wrote:
>
>> ** Changed in: openstack-manuals
>> Status: Incomplete => Invalid
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1371878
>>
>> Title:
>> Configure compute node in OpenStack Installation Guide for Ubuntu
>> 12.04/14.04 (LTS) - icehouse
>>
>> Status in OpenStack Manuals:
>> Invalid
>>
>> Bug description:
>> Under configure compute node - - ml2.conf is irrelevant for the
>> agent. The agent is not aware that ML2 plugin is being used. The
>> right configuration file here (for OVS agent) is
>> ovs_neutron_plugin.ini.
>>
>>
>> -----------------------------------
>> Built: 2014-09-19T07:50:45 00:00
>> git SHA: 7241eb0fbd6dedac9007a28863fe7dcbf361e96f
>> URL:
>> http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron-ml2-compute-node.html
>> source File:
>> file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-ml2-compute-node.xml
>> xml:id: neutron-ml2-compute-node
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/openstack-manuals/+bug/1371878/+subscriptions
>>
>
>

Revision history for this message
omar-cloudscaling (f-omar) wrote :
Download full text (3.2 KiB)

Juno is out.
OVS plugin is removed.
No OVS config merged into ml2-conf.ini.
ovs_neutron_plugin.ini retained as the config for OVS agent.

On Wed, Oct 15, 2014 at 3:37 PM, Omar Khalid <email address hidden> wrote:

> Correction.
>
> -->"They are not part of the source code structure."
>
> They are part of the source code tree structure.
>
> On Wed, Oct 15, 2014 at 3:35 PM, Omar Khalid <email address hidden>
> wrote:
>
>> << The sample configurations are meant to be just that, samples >>
>>
>>
>> They are not part of the source code structure. Programmers update the
>> corresponding config files as they developed
>>
>> The documentation came from the source code.
>>
>> This is a bazaar, not a cathedral.
>>
>>
>>
>> << All of the previous options are still supported >>
>>
>>
>> Of course they are "supported" since they are "pasted" to the
>> ml2-conf.ini.
>>
>> However the usage of ml2-conf.ini is inappropriate because :
>>
>>
>> (1) It wasn't meant for the agent
>>
>> (2) The OVS agent has it's own config file.
>>
>>
>> And if perchance that an agent does needs to refer to ml2-conf.ini (afaik
>> neither LB nor OVS agents), then the process should start with
>> --config-file options for each config files needed.
>>
>>
>>
>>
>> << I think that would require an actual code change in the agent itself
>> >>
>>
>>
>> There is no code change in the openstack source code.
>>
>> The code change you are referring to is the daemon service script created
>> and installed by Ubuntu packaging (that mistakenly uses ml2-conf.ini
>> for ovs agent).
>>
>>
>>
>>
>> Please refer to Neutron TOT source code.
>>
>> Openvswitch (and Linux bridge) plugin has already been removed.
>>
>> The configuration is as what I have been telling you !
>>
>> They are keeping it as a separate OVS config file used for agent. No
>> merging with ml2-conf.ini whatsoever.
>>
>>
>>
>>
>> The document and ubuntu packaging to start the OVS agent with
>> ml2-conf.ini is wrong.
>>
>>
>>
>> On Wed, Oct 15, 2014 at 2:28 PM, Matt Kassawara <email address hidden>
>> wrote:
>>
>>> ** Changed in: openstack-manuals
>>> Status: Incomplete => Invalid
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1371878
>>>
>>> Title:
>>> Configure compute node in OpenStack Installation Guide for Ubuntu
>>> 12.04/14.04 (LTS) - icehouse
>>>
>>> Status in OpenStack Manuals:
>>> Invalid
>>>
>>> Bug description:
>>> Under configure compute node - - ml2.conf is irrelevant for the
>>> agent. The agent is not aware that ML2 plugin is being used. The
>>> right configuration file here (for OVS agent) is
>>> ovs_neutron_plugin.ini.
>>>
>>>
>>> -----------------------------------
>>> Built: 2014-09-19T07:50:45 00:00
>>> git SHA: 7241eb0fbd6dedac9007a28863fe7dcbf361e96f
>>> URL:
>>> http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron-ml2-compute-node.html
>>> source File:
>>> file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_neutron-ml2-compute-node.xml
>>> xml:id: neutron-ml2-compute-node
>>>
>>> To manage notifications about th...

Read more...

Tom Fifield (fifieldt)
Changed in openstack-manuals:
status: Invalid → Incomplete
Tom Fifield (fifieldt)
Changed in openstack-manuals:
milestone: juno → none
Changed in openstack-manuals:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.