RFE - Add functionality to deploy OpenDaylight with Composable roles

Open
#343 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
ansible

Research direction

Start by reading composable_roles/roles/roles_data.yaml alongside plugins/openstack/defaults/topology/nodes/odl.yml, roles/networker/controller.yml, and roles/networker/networker.yml. Compare how the existing OpenDaylight and Networker services are represented, then verify that an updated composable profile deploys OpenDaylight successfully in the overcloud.

Written by the indexing model from the issue text.

Description

Currently in infrared, there is no composable functionality for OpenDyalight. Although following steps didn't help to deploy Networker composable profile for OpenDaylight.
Can someone share appropriate steps to deploy OpenDaylight service in Networker composable profile? It would be appreciated infrared we can create an additional composable profile for ODL.

  1. Modify the interface and groups for odl node in topology section.
cat /root/.venv_infrared/infrared/plugins/openstack/defaults/topology/nodes/odl.yml
name: odl
flavor_id: m1.small
interfaces:
    nic1:
        network: "management"
    nic2:
        network: "data"
    nic3:
        network: "external"
external_network: management

security_groups:
    - general_access

groups:
    - odl_controller
    - openstack_nodes
    - overcloud_nodes
    - network
  1. Commented the required OSP service and updated ODL services in networker composable yml.
/root/.venv_infrared/infrared/plugins/tripleo-overcloud/files/roles/networker/controller.yml
	#- OS::TripleO::Services::OpenDaylightApi
        - "{% if install.version|default(undercloud_version) |openstack_release > 12 %}OS::TripleO::Services::OpenDaylightOvs{% endif %}"

/root/.venv_infrared/infrared/plugins/tripleo-overcloud/files/roles/networker/networker.yml
	#- OS::TripleO::Services::NeutronDhcpAgent
	#- "{% if install.version|default(undercloud_version) |openstack_release > 11 %}OS::TripleO::Services::NeutronL2gwAgent{% endif %}"
	#- OS::TripleO::Services::NeutronL3Agent
	#- "{% if install.version|default(undercloud_version) |openstack_release > 11 %}OS::TripleO::Services::NeutronLbaasv2Agent{% endif %}"
	#- "{% if install.version|default(undercloud_version) |openstack_release > 11 %}OS::TripleO::Services::NeutronLinuxbridgeAgent{% endif %}"
	#- OS::TripleO::Services::NeutronMetadataAgent
	#- OS::TripleO::Services::NeutronOvsAgent
	#- "{% if install.version|default(undercloud_version) |openstack_release > 11 %}OS::TripleO::Services::NeutronVppAgent{% endif %}"
	 - OS::TripleO::Services::Ntp
	#- OS::TripleO::Services::OpenDaylightOvs
	- "{% if install.version|default(undercloud_version) |openstack_release > 12 %}OS::TripleO::Services::OpenDaylightApi{% endif %}"

It seems the above steps didn't help to include the updated service in following roles (composable_roles/roles/roles_data.yaml) for overcloud deployment.

Dominant language
Jinja
Stars
105
Forks
100
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from redhat-openstack/infrared

All issues in redhat-openstack/infrared

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.