Ok,

I understand now (that the flag is not really relevant in my case). I've
filled a bug report for the missing neutron-l3-agent package:
https://bugs.launchpad.net/charms/+source/neutron-gateway/+bug/1512458.

kind regards
Pshem


On Tue, 3 Nov 2015 at 08:15 David Ames <david.a...@canonical.com> wrote:

> On 11/01/2015 06:12 PM, Pshem Kowalczyk wrote:
> > Hi,
> >
> > I'm trying to get openstack installed using juju.
> > The configuration of the nova and neutron is fairly simple:
> >
> > nova-cloud-controller:
> >   openstack-origin: cloud:trusty-kilo
> >   network-manager: Neutron
> >   neutron-external-network: "ext-net"
> >   console-access-protocol: vnc
> >
> > neutron-api:
> >   openstack-origin: cloud:trusty-kilo
> >   neutron-external-network: "ext-net"
> >   neutron-security-groups: true
> >   enable-dvr: true
> >   manage-neutron-plugin-legacy-mode: true
> >
> > neutron-gateway:
> >   openstack-origin: cloud:trusty-kilo
> >   ext-port: eth3
> >
> > nova-compute:
> >   openstack-origin: cloud:trusty-kilo
> >
> > Reading the documentation I got the impression that the default value of
> > 'manage-neutron-plugin-legacy-mode' in the neutron-api charm should force
> > the installation of necessary plugins.
> >
> > Yet, after the setup is build (using 2 nodes, each with nova-compute and
> > neutron-gateway), I get the following:
> > ubuntu@juju-machine-0-lxc-6:~$ neutron agent-list
> >
> +--------------------------------------+--------------------+-------+-------+----------------+---------------------------+
> > | id                                   | agent_type         | host  |
> alive
> > | admin_state_up | binary                    |
> >
> +--------------------------------------+--------------------+-------+-------+----------------+---------------------------+
> > | 09989b3d-6aab-44a8-b595-84c7505833dd | Metering agent     | node2 | :-)
> > | True           | neutron-metering-agent    |
> > | 0e34444b-4218-43be-9fc3-726486cba6e4 | Open vSwitch agent | node1 | :-)
> > | True           | neutron-openvswitch-agent |
> > | 2051a1a5-2740-4d39-813a-34caa4ca23c9 | L3 agent           | node1 | xxx
> > | True           | neutron-l3-agent          |
> > | 3e57cfda-570c-42f9-a9f6-bf3a9374ad8b | Loadbalancer agent | node1 | :-)
> > | True           | neutron-lbaas-agent       |
> > | 58d849eb-a604-4273-bcaf-f65ff07fc2c0 | Metadata agent     | node2 | xxx
> > | True           | neutron-metadata-agent    |
> > | 81b4702c-8b6e-41ed-81bc-938b5ca974d8 | Metering agent     | node1 | :-)
> > | True           | neutron-metering-agent    |
> > | ae13892e-5e6b-48b3-9b7f-0f0a9e4e09c6 | Metadata agent     | node1 | xxx
> > | True           | neutron-metadata-agent    |
> > | bd98fdc6-d156-4934-84f9-fe0a3d6a38fc | Loadbalancer agent | node2 | :-)
> > | True           | neutron-lbaas-agent       |
> > | cda24198-1862-4694-8f57-0bac4ec67676 | DHCP agent         | node1 | xxx
> > | True           | neutron-dhcp-agent        |
> > | d2bc081c-5689-4a29-9c68-eac80a322885 | L3 agent           | node2 | xxx
> > | True           | neutron-l3-agent          |
> > | eb7b927d-9ca3-4229-a25d-0d8aebc1334b | Open vSwitch agent | node2 | :-)
> > | True           | neutron-openvswitch-agent |
> >
> +--------------------------------------+--------------------+-------+-------+----------------+---------------------------+
> >
> > (i.e L3 agent, DHCP agent and metadata agent are not running).
> >
> > a quick look at the packages installed on the nodes reveals that both
> > neutron-l3-agent and neutron-dhcp-agent are actually not installed.
> After
> > manual installation of those packages (they pull in
> neutron-metadata-agent
> > too) it all works as expected:
> >
> > ubuntu@juju-machine-0-lxc-6:~$ neutron agent-list
> >
> +--------------------------------------+--------------------+-------+-------+----------------+---------------------------+
> > | id                                   | agent_type         | host  |
> alive
> > | admin_state_up | binary                    |
> >
> +--------------------------------------+--------------------+-------+-------+----------------+---------------------------+
> > | 09989b3d-6aab-44a8-b595-84c7505833dd | Metering agent     | node2 | :-)
> > | True           | neutron-metering-agent    |
> > | 0e34444b-4218-43be-9fc3-726486cba6e4 | Open vSwitch agent | node1 | :-)
> > | True           | neutron-openvswitch-agent |
> > | 2051a1a5-2740-4d39-813a-34caa4ca23c9 | L3 agent           | node1 | :-)
> > | True           | neutron-l3-agent          |
> > | 3e57cfda-570c-42f9-a9f6-bf3a9374ad8b | Loadbalancer agent | node1 | :-)
> > | True           | neutron-lbaas-agent       |
> > | 58d849eb-a604-4273-bcaf-f65ff07fc2c0 | Metadata agent     | node2 | :-)
> > | True           | neutron-metadata-agent    |
> > | 81b4702c-8b6e-41ed-81bc-938b5ca974d8 | Metering agent     | node1 | :-)
> > | True           | neutron-metering-agent    |
> > | ae13892e-5e6b-48b3-9b7f-0f0a9e4e09c6 | Metadata agent     | node1 | :-)
> > | True           | neutron-metadata-agent    |
> > | bd98fdc6-d156-4934-84f9-fe0a3d6a38fc | Loadbalancer agent | node2 | :-)
> > | True           | neutron-lbaas-agent       |
> > | cda24198-1862-4694-8f57-0bac4ec67676 | DHCP agent         | node1 | :-)
> > | True           | neutron-dhcp-agent        |
> > | d2bc081c-5689-4a29-9c68-eac80a322885 | L3 agent           | node2 | :-)
> > | True           | neutron-l3-agent          |
> > | eb7b927d-9ca3-4229-a25d-0d8aebc1334b | Open vSwitch agent | node2 | :-)
> > | True           | neutron-openvswitch-agent |
> >
> +--------------------------------------+--------------------+-------+-------+----------------+---------------------------+
> >
> > I'm using juju 1.25 on ubuntu 14.04.3
> >
> > Should those 3 agents be installed automatically or not?
> >
> > kind regards
> > Pshem
> >
> >
> >
>
> Pshem,
>
> Sorry for the confusion. The short answer is when using neutron-api
> relate the subordinate charm, neutron-openvswitch [1], to nova-compute
> and neutron-api and it will install everything it needs to run openvswitch.
>
> The long answer is we have made your choice of SDN pluggable. By
> relating the correct SDN subordinate charm to nova-compute and
> neutron-api you can change the underlying SDN. In your case, you are
> using openvswitch as an SDN so the appropriate subordinate charm is
> neutron openvswitch.
>
> The really log answer: manage-neutron-plugin-legacy-mode is purely for
> historical reasons and will be deprecated soon. Prior to this
> pluggability, the nova-compute charm setup openvswitch directly. This
> topology is deprecated. The correct topology is what you have plus the
> correct SDN subordinate (neutron openvswitch).
>
> [1] https://jujucharms.com/neutron-openvswitch/trusty/12
>
> Let me know if this helped clear things up,
>
> David Ames
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Reply via email to