[kolla][iconic] baremetal network

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[kolla][iconic] baremetal network

Manuel Sopena Ballesteros

Dear Kolla-ansible team,

 

I am trying to deploy ironic through kolla-ansible. According to ironic documentation https://docs.openstack.org/ironic/rocky/install/configure-networking.html we need bare metal network with tenant_network_types = flat. However kolla-ansible configures:

 

[root@TEST-openstack-controller ~]# grep -R -i "baremetal" -R /etc/kolla/*

/etc/kolla/neutron-openvswitch-agent/ml2_conf.ini:mechanism_drivers = openvswitch,baremetal,l2population

/etc/kolla/neutron-server/ml2_conf.ini:mechanism_drivers = openvswitch,baremetal,l2population

 

 

[root@TEST-openstack-controller ~]# grep -R -i "tenant_network_types" -R /etc/kolla/*

/etc/kolla/neutron-openvswitch-agent/ml2_conf.ini:tenant_network_types = vxlan

/etc/kolla/neutron-server/ml2_conf.ini:tenant_network_types = vxlan

 

This is my filtered globals.yml:

 

[root@openstack-deployment ~]# grep -E -i "(^[^#]|ironic)" /etc/kolla/globals.yml

---

openstack_release: "rocky"

kolla_internal_vip_address: "192.168.1.51"

neutron_external_interface: "ens161"

enable_cinder: "yes"

enable_cinder_backend_nfs: "yes"

#enable_horizon_ironic: "{{ enable_ironic | bool }}"

enable_ironic: "yes"

#enable_ironic_ipxe: "no"

#enable_ironic_neutron_agent: "no"

#enable_ironic_pxe_uefi: "no"

glance_enable_rolling_upgrade: "no"

# Ironic options

# following value must be set when enable ironic, the value format

ironic_dnsmasq_dhcp_range: "192.168.1.100,192.168.1.150"

# PXE bootloader file for Ironic Inspector, relative to /tftpboot.

ironic_dnsmasq_boot_file: "pxelinux.0"

ironic_cleaning_network: "ens224"

#ironic_dnsmasq_default_gateway: 192.168.1.255

# Configure ironic upgrade option, due to currently kolla support

# two upgrade ways for ironic: legacy_upgrade and rolling_upgrade

# The variable "ironic_enable_rolling_upgrade: yes" is meaning legacy_upgrade

#ironic_enable_rolling_upgrade: "yes"

#ironic_inspector_kernel_cmdline_extras: []

tempest_image_id:

tempest_flavor_ref_id:

tempest_public_network_id:

tempest_floating_network_name:

 

ens224 is a my management network for admins to ssh and install and manage the physical nodes.

 

Any idea why tenant_network_types = vxlan and not flat as suggested by the ironic documentation?

 

Thank you

 

Manuel Sopena Ballesteros | Big data Engineer
Garvan Institute of Medical Research 
The Kinghorn Cancer Centre, 370 Victoria Street, Darlinghurst, NSW 2010
T: + 61 (0)2 9355 5760 | F: +61 (0)2 9295 8507 | E: 
[hidden email]

 

NOTICE
Please consider the environment before printing this email. This message and any attachments are intended for the addressee named and may contain legally privileged/confidential/copyright information. If you are not the intended recipient, you should not read, use, disclose, copy or distribute this communication. If you have received this message in error please notify us at once by return email and then delete both messages. We accept no liability for the distribution of viruses or similar in electronic communications. This notice should not be removed.

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [hidden email]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Reply | Threaded
Open this post in threaded view
|

Re: [kolla][iconic] baremetal network

Mark Goddard-2
Hi Manuel,

You can configure the neutron tenant network types in kolla-ansible via the 'neutron_tenant_network_types' variable in globals.yml. It's a comma-separated list. The default for that variable is vxlan, it's expected that you set it to match your requirements.

The 'ironic_cleaning_network' variable should be the name of a network in neutron to be used for cleaning, rather than an interface name. If you're using flat networking, this will just be 'the' network.

Regards,
Mark

On Mon, 12 Nov 2018 at 01:23, Manuel Sopena Ballesteros <[hidden email]> wrote:

Dear Kolla-ansible team,

 

I am trying to deploy ironic through kolla-ansible. According to ironic documentation https://docs.openstack.org/ironic/rocky/install/configure-networking.html we need bare metal network with tenant_network_types = flat. However kolla-ansible configures:

 

[root@TEST-openstack-controller ~]# grep -R -i "baremetal" -R /etc/kolla/*

/etc/kolla/neutron-openvswitch-agent/ml2_conf.ini:mechanism_drivers = openvswitch,baremetal,l2population

/etc/kolla/neutron-server/ml2_conf.ini:mechanism_drivers = openvswitch,baremetal,l2population

 

 

[root@TEST-openstack-controller ~]# grep -R -i "tenant_network_types" -R /etc/kolla/*

/etc/kolla/neutron-openvswitch-agent/ml2_conf.ini:tenant_network_types = vxlan

/etc/kolla/neutron-server/ml2_conf.ini:tenant_network_types = vxlan

 

This is my filtered globals.yml:

 

[root@openstack-deployment ~]# grep -E -i "(^[^#]|ironic)" /etc/kolla/globals.yml

---

openstack_release: "rocky"

kolla_internal_vip_address: "192.168.1.51"

neutron_external_interface: "ens161"

enable_cinder: "yes"

enable_cinder_backend_nfs: "yes"

#enable_horizon_ironic: "{{ enable_ironic | bool }}"

enable_ironic: "yes"

#enable_ironic_ipxe: "no"

#enable_ironic_neutron_agent: "no"

#enable_ironic_pxe_uefi: "no"

glance_enable_rolling_upgrade: "no"

# Ironic options

# following value must be set when enable ironic, the value format

ironic_dnsmasq_dhcp_range: "192.168.1.100,192.168.1.150"

# PXE bootloader file for Ironic Inspector, relative to /tftpboot.

ironic_dnsmasq_boot_file: "pxelinux.0"

ironic_cleaning_network: "ens224"

#ironic_dnsmasq_default_gateway: 192.168.1.255

# Configure ironic upgrade option, due to currently kolla support

# two upgrade ways for ironic: legacy_upgrade and rolling_upgrade

# The variable "ironic_enable_rolling_upgrade: yes" is meaning legacy_upgrade

#ironic_enable_rolling_upgrade: "yes"

#ironic_inspector_kernel_cmdline_extras: []

tempest_image_id:

tempest_flavor_ref_id:

tempest_public_network_id:

tempest_floating_network_name:

 

ens224 is a my management network for admins to ssh and install and manage the physical nodes.

 

Any idea why tenant_network_types = vxlan and not flat as suggested by the ironic documentation?

 

Thank you

 

Manuel Sopena Ballesteros | Big data Engineer
Garvan Institute of Medical Research 
The Kinghorn Cancer Centre, 370 Victoria Street, Darlinghurst, NSW 2010
T: + 61 (0)2 9355 5760 | F: +61 (0)2 9295 8507 | E: 
[hidden email]

 

NOTICE
Please consider the environment before printing this email. This message and any attachments are intended for the addressee named and may contain legally privileged/confidential/copyright information. If you are not the intended recipient, you should not read, use, disclose, copy or distribute this communication. If you have received this message in error please notify us at once by return email and then delete both messages. We accept no liability for the distribution of viruses or similar in electronic communications. This notice should not be removed.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@...?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [hidden email]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev