[rdo-users] Error creating network isolation file
wodel youchi
wodel.youchi at gmail.com
Mon Aug 16 09:18:06 UTC 2021
Hi,
anyone???
Regards.
Le jeu. 12 août 2021 à 11:11, wodel youchi <wodel.youchi at gmail.com> a
écrit :
> Hi, and thank you for your help.
>
> As I said, after re-reading the documentation, I found the new
> documentation, and I tried to follow it, but it's not clear.
> First of all, I did not find the
> "/usr/share/openstack-tripleo-heat-templates/network-data-samples"
> directory in my system, so I used the one from the GIT.
> 1 - I modified the network_data.yaml file as needed.
> 2 - Then I copied the vip_data.yaml file as is without modification.
> 3 - I created then the network-environment-overrides.yaml using this link (
> https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/network_isolation.html#creating-custom-interface-templates),
> I wanted to use bond-with-vlans configuration.
> 4 - I used this file (
> https://opendev.org/openstack/tripleo-ansible/src/branch/master/tripleo_ansible/roles/tripleo_network_config/templates/bonds_vlans/bonds_vlans.j2)
> and I modified it to create my bonds and vlans and to map them to the
> different networks.
> 5 - I created the networks-deployed-environment.yaml as mentioned like
> this :
> openstack overcloud network provision --output
> networks-deployed-environment.yaml network_data.yaml
> 6 - Then I created the vip-deployed-environment.yaml using :
> openstack overcloud network vip provision --output
> ~/templates/vip-deployed-environment.yaml ~/templates/vip_data.yaml
>
> Am I correct till now? my conf files are attached
>
> Then the documentation says, if you want to deploy use :
>
> a - this command
> openstack overcloud deploy --templates \
> -n network_data.yaml \
> -e networks-deployed-environment.yaml \
> -e vip-deployed-environment.yaml \
> -e network-environment-overrides.yaml
>
>
> b - Or this command
> openstack overcloud deploy --templates \
> --networks-file network_data.yaml \
> --vip-file vip_data.yaml \
> --baremetal-deployment baremetal_deployment.yaml \
> --network-config \
> -e network-environment-overrides.yaml
>
> What I don't understand is the difference between the two of them,
> Does the first command mean : deploy the configuration on the already
> deployed nodes (or already deployed overcloud)?
> And does the second command mean : deploy the OS on the overcloud nodes
> before deploying the overcloud itself?
>
> PS : for the network part :
> Each overcloud node has 6 nics :
> - 2 nics will be bonded and used for the provisioning network. -> I didn't
> know how to modify the bonds_vlans.j2 to create a bond on the ctplane
> network.
> - 2 nics will be bonded and used for the external, api and tenant networks.
> - 2 nics will be bonded and used on the storage and the storage management
> networks.
>
> Regards.
>
> Le jeu. 12 août 2021 à 03:04, Wan, Sam <Sam.Wan at dell.com> a écrit :
>
>> Hi Wodel Youchi,
>>
>>
>>
>> You’re using the template for Victoria and prior releases according to
>> https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/custom_networks.html#custom-networks
>> .
>>
>>
>>
>> For wallaby, the hierarchy is like this:
>>
>> *name*
>>
>> Name of the network (mandatory)
>>
>> *vip*
>>
>> Enable creation of a virtual IP on this network
>>
>> *subnets*
>>
>> Dictionary’s, one or more subnet definition items keyed by the subnet
>> name.
>>
>> *subnet_name*
>>
>> Name of the subnet
>>
>> *ip_subnet*
>>
>> IP/CIDR, e.g. *'10.0.0.0/24 <http://10.0.0.0/24>'*
>>
>> *allocation_pools*
>>
>> IP range list, e.g. *[{'start':'10.0.0.4',* *'end':'10.0.0.250'}]*
>>
>> *gateway_ip*
>>
>> Gateway for the network
>>
>> *vlan*
>>
>> Vlan ID for this network. (supported in Queens and later)
>>
>>
>>
>> And there’s an example in the doc
>>
>> - *name*: CustomNetwork
>>
>> *vip*: false
>>
>> *name_lower*: custom_network
>>
>> *subnets*:
>>
>> *custom_network_subnet*:
>>
>> *ip_subnet*: 172.16.6.0/24
>>
>> *allocation_pools*:
>>
>> - *start*: 172.16.6.4
>>
>> - *end*: 172.16.6.250
>>
>> *gateway_ip*: 172.16.6.1
>>
>>
>>
>>
>>
>> Another example in the doc:
>>
>> *subnets*:
>>
>> *subnet_name_a*:
>>
>> *ip_subnet*: 192.0.2.0/24
>>
>> *allocation_pools*:
>>
>> - *start*: 192.0.2.50
>>
>> *end*: 192.0.2.99
>>
>> *gateway_ip*: 192.0.2.1
>>
>> *vlan*: 102
>>
>> *subnet_name_b*:
>>
>> *ip_subnet*: 198.51.100.0/24
>>
>> *allocation_pools*:
>>
>> - *start*: 198.51.100.50
>>
>> *end*: 198.51.100.99
>>
>> *gateway_ip*: 198.51.100.1
>>
>> *vlan*: 101
>>
>>
>>
>>
>>
>> So your network_data.yaml should be like this:
>>
>> - name: Storage
>>
>> vip: true
>>
>> mtu: 1500
>>
>> name_lower: storage
>>
>> subnets:
>>
>> storage_subnet:
>>
>> ip_subnet: 10.100.7.0/24
>>
>> allocation_pools: [{'start': '10.100.7.150', 'end': '10.100.7.250'}
>>
>> vlan: 1107
>>
>> - name: StorageMgmt
>>
>> vip: true
>>
>> mtu: 1500
>>
>> name_lower: storage_mgmt
>>
>> subnets:
>>
>> storagemgmt_subnet:
>>
>> ip_subnet: 10.100.8.0/24
>>
>> allocation_pools: [{'start': '10.100.8.150', 'end': '10.100.8.250'}
>>
>> vlan: 1108
>>
>> - name: InternalApi
>>
>> vip: true
>>
>> mtu: 1500
>>
>> name_lower: internal_api
>>
>> subnets:
>>
>> internalapi_subnet:
>>
>> ip_subnet: 10.100.5.0/24
>>
>> allocation_pools: [{'start': '10.100.5.150', 'end': '10.100.5.250'}]
>>
>> vlan: 1105
>>
>> - name: Tenant
>>
>> vip: false
>>
>> mtu: 1500
>>
>> name_lower: tenant
>>
>> subnets:
>>
>> tenant_subnet:
>>
>> ip_subnet: 10.100.6.0/24
>>
>> allocation_pools: [{'start': '10.100.6.150', 'end': '10.100.6.250'}]
>>
>> vlan: 1106
>>
>> - name: External
>>
>> vip: true
>>
>> mtu: 1500
>>
>> name_lower: external
>>
>> subnets:
>>
>> external_subnet:
>>
>> ip_subnet: 10.0.1.0/24
>>
>> allocation_pools: [{'start': '10.0.1.4', 'end': '10.0.1.250'}]
>>
>> gateway_ip: '10.0.1.1'
>>
>> vlan: 2100
>>
>>
>>
>>
>>
>> Thanks and regards
>>
>>
>>
>> ===============================
>>
>> *sam.wan at dell.com <sam.wan at dell.com>*
>>
>> *E-LAB*
>>
>> *Dell **EMC** | Technical Operations IEO*
>>
>> *Phone: **+86 (28) 82966713*
>>
>>
>>
>> *From:* wodel youchi <wodel.youchi at gmail.com>
>> *Sent:* 2021年8月11日 20:42
>> *To:* Wan, Sam
>> *Cc:* users at lists.rdoproject.org
>> *Subject:* Re: [rdo-users] Error creating network isolation file
>>
>>
>>
>> [EXTERNAL EMAIL]
>>
>> Hi,
>>
>>
>>
>> After re-reading the documentation, I found another document that
>> explains that there were new modifications in Wallaby (https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deployment/network_v2.html
>> [docs.openstack.org]
>> <https://urldefense.com/v3/__https:/docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deployment/network_v2.html__;!!LpKI!3Rb8aWc2vu_BHTZXCwLgrAFqMD43mcZSUu077veZB9gtUVflc1SP2BAwYl5w$>
>> ).
>>
>> The document points to other links like this one (https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/custom_networks.html#custom-networks
>> [docs.openstack.org]
>> <https://urldefense.com/v3/__https:/docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/custom_networks.html*custom-networks__;Iw!!LpKI!3Rb8aWc2vu_BHTZXCwLgrAFqMD43mcZSUu077veZB9gtUVflc1SP2FcvPH9w$>),
>> it's really hard to follow and understand the documentation.
>>
>>
>>
>>
>>
>> Regards.
>>
>>
>>
>> [avast.com]
>> <https://urldefense.com/v3/__https:/www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail__;!!LpKI!3Rb8aWc2vu_BHTZXCwLgrAFqMD43mcZSUu077veZB9gtUVflc1SP2LgjcIIK$>
>>
>> Virus-free. www.avast.com [avast.com]
>> <https://urldefense.com/v3/__https:/www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail__;!!LpKI!3Rb8aWc2vu_BHTZXCwLgrAFqMD43mcZSUu077veZB9gtUVflc1SP2LgjcIIK$>
>>
>>
>>
>> Le mer. 11 août 2021 à 05:25, Wan, Sam <Sam.Wan at dell.com> a écrit :
>>
>> Sorry I see you’ve paste the content of your network_data.yaml.
>>
>> Please make changes to your network_data.yaml following the sample.
>>
>>
>>
>> Thanks and regards
>>
>>
>>
>> ===============================
>>
>> *sam.wan at dell.com <sam.wan at dell.com>*
>>
>> *E-LAB*
>>
>> *Dell **EMC** | Technical Operations IEO*
>>
>> *Phone: **+86 (28) 82966713*
>>
>>
>>
>> *From:* Wan, Sam
>> *Sent:* 2021年8月11日 12:23
>> *To:* 'wodel youchi'; users at lists.rdoproject.org
>> *Subject:* RE: [rdo-users] Error creating network isolation file
>>
>>
>>
>> Hi Wodel Youchi,
>>
>>
>>
>> The error is obvious.
>>
>> *Additional properties are not allowed ('ip_subnet', 'enabled',
>> 'allocation_pools', 'gateway_ip', 'vlan', 'ipv6_subnet',
>> 'ipv6_allocation_pools', 'gateway_ipv6' were unexpected) \n\nFailed schema
>> validation at :\n 'subnets' is a required property"*
>>
>>
>>
>> Seems you’ve specified an unexpected ‘gateway_ipv6’ in ‘Management'
>> network
>>
>> Could you please share your ‘network_data.yaml' File?
>>
>>
>>
>> There’s a link to network-data samples in the documentation you gave
>> however it’s broken.
>>
>> Create and Edit network data YAML definition file¶ [docs.openstack.org]
>> <https://urldefense.com/v3/__https:/docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/network_isolation.html*create-and-edit-network-data-yaml-definition-file__;Iw!!LpKI!3Rb8aWc2vu_BHTZXCwLgrAFqMD43mcZSUu077veZB9gtUVflc1SP2Gv8B-oo$>
>>
>> Use the network-data-samples [opendev.org]
>> <https://urldefense.com/v3/__https:/opendev.org/openstack/tripleo-heat-templates/network-data-samples__;!!LpKI!3Rb8aWc2vu_BHTZXCwLgrAFqMD43mcZSUu077veZB9gtUVflc1SP2GGKaQsL$>
>> (broken) in tripleo-heat-templates [opendev.org]
>> <https://urldefense.com/v3/__https:/opendev.org/openstack/tripleo-heat-templates__;!!LpKI!3Rb8aWc2vu_BHTZXCwLgrAFqMD43mcZSUu077veZB9gtUVflc1SP2F4GQ9z5$> as
>> a reference and customize the networks, IP addressing, VLANs, etc., as per
>> the cluster requirements.
>>
>>
>>
>>
>>
>> But you can still find a sample in the source: https://opendev.org/openstack/tripleo-heat-templates/src/branch/stable/wallaby/network-data-samples/legacy-routed-networks-ipv6.yaml
>> [opendev.org]
>> <https://urldefense.com/v3/__https:/opendev.org/openstack/tripleo-heat-templates/src/branch/stable/wallaby/network-data-samples/legacy-routed-networks-ipv6.yaml__;!!LpKI!3Rb8aWc2vu_BHTZXCwLgrAFqMD43mcZSUu077veZB9gtUVflc1SP2BTTVW5L$>
>>
>> And there’s an example with gateway_ipv6, it should be in the subnets
>> property.
>>
>>
>>
>> You might need to change your network-data.yaml following this sample.
>>
>>
>>
>> Thanks and regards
>>
>>
>>
>> ===============================
>>
>> *sam.wan at dell.com <sam.wan at dell.com>*
>>
>> *E-LAB*
>>
>> *Dell **EMC** | Technical Operations IEO*
>>
>> *Phone: **+86 (28) 82966713*
>>
>>
>>
>> *From:* users <users-bounces at lists.rdoproject.org> *On Behalf Of *wodel
>> youchi
>> *Sent:* 2021年8月5日 0:22
>> *To:* users at lists.rdoproject.org
>> *Subject:* [rdo-users] Error creating network isolation file
>>
>>
>>
>> [EXTERNAL EMAIL]
>>
>> Hi,
>>
>> A newbie in Openstack, I am deploying an overcloud using the Wallaby
>> version.
>>
>> I am using "container-tools 3.0 [e]"
>>
>>
>>
>> I am trying to create the networks-deployed-environment.yaml file using :
>>
>> *openstack overcloud network provision -o
>> /home/stack/templates/networks-deployed-environment.yaml
>> /home/stack/templates/network_data.yaml *
>>
>> I am following this documentation : https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/network_isolation.html
>> [docs.openstack.org]
>> <https://urldefense.com/v3/__https:/docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/network_isolation.html__;!!LpKI!xc4qNPJ0garbZ7l0yI6qpDEAABzfeM0X6sDwSZT0QNTcENQ9AcDo-ssQW6s$>
>>
>>
>>
>> But I am getting these errors on all networks defined in
>> network_data.yaml:
>>
>>
>> *2021-08-04 17:13:54.071521 | 52540075-9baf-e063-4b37-00000000000e |
>> FATAL | Create/Update composable networks | localhost | item={'name':
>> 'Management', 'enabled': True, 'vip': False, 'name_lower': 'management',
>> 'vlan': 60, 'ip_subnet': '10.0.1.0/24 [10.0.1.0]
>> <https://urldefense.com/v3/__http:/10.0.1.0/24__;!!LpKI!xc4qNPJ0garbZ7l0yI6qpDEAABzfeM0X6sDwSZT0QNTcENQ9AcDoLdX87P4$>',
>> 'allocation_pools': [{'start': '10.0.1.4', 'end': '10.0.1.250'}],
>> 'gateway_ip': '10.0.1.1', 'gateway_ipv6': 'fd00:fd00:fd00:6000::1',
>> 'ipv6_subnet': 'fd00:fd00:fd00:6000::/64', 'ipv6_allocation_pools':
>> [{'start': 'fd00:fd00:fd00:6000::10', 'end':
>> 'fd00:fd00:fd00:6000:ffff:ffff:ffff:fffe'}], 'mtu': 1500} |
>> error={"ansible_index_var": "idx", "ansible_loop_var": "item", "changed":
>> false, "idx": 5, "item": {"allocation_pools": [{"end": "10.0.1.250",
>> "start": "10.0.1.4"}], "enabled": true, "gateway_ip": "10.0.1.1",
>> "gateway_ipv6": "fd00:fd00:fd00:6000::1", "ip_subnet": "10.0.1.0/24
>> [10.0.1.0]
>> <https://urldefense.com/v3/__http:/10.0.1.0/24__;!!LpKI!xc4qNPJ0garbZ7l0yI6qpDEAABzfeM0X6sDwSZT0QNTcENQ9AcDoLdX87P4$>",
>> "ipv6_allocation_pools": [{"end":
>> "fd00:fd00:fd00:6000:ffff:ffff:ffff:fffe", "start":
>> "fd00:fd00:fd00:6000::10"}], "ipv6_subnet": "fd00:fd00:fd00:6000::/64",
>> "mtu": 1500, "name": "Management", "name_lower": "management", "vip":
>> false, "vlan": 60}, "msg": "Failed schema validation at :\n Additional
>> properties are not allowed ('ip_subnet', 'enabled', 'allocation_pools',
>> 'gateway_ip', 'vlan', 'ipv6_subnet', 'ipv6_allocation_pools',
>> 'gateway_ipv6' were unexpected)\n\nFailed schema validation at :\n
>> 'subnets' is a required property"} ......*
>>
>>
>>
>>
>>
>>
>>
>> Here is my network_data.yaml :
>>
>> - name: Storage
>> vip: true
>> vlan: 1107
>> name_lower: storage
>> ip_subnet: '10.100.7.0/24 [10.100.7.0]
>> <https://urldefense.com/v3/__http:/10.100.7.0/24__;!!LpKI!xc4qNPJ0garbZ7l0yI6qpDEAABzfeM0X6sDwSZT0QNTcENQ9AcDo19NKNJI$>
>> '
>> allocation_pools: [{'start': '10.100.7.150', 'end': '10.100.7.250'}]
>> mtu: 1500
>> - name: StorageMgmt
>> name_lower: storage_mgmt
>> vip: true
>> vlan: 1108
>> ip_subnet: '10.100.8.0/24 [10.100.8.0]
>> <https://urldefense.com/v3/__http:/10.100.8.0/24__;!!LpKI!xc4qNPJ0garbZ7l0yI6qpDEAABzfeM0X6sDwSZT0QNTcENQ9AcDokDoJOtI$>
>> '
>> allocation_pools: [{'start': '10.100.8.150', 'end': '10.100.8.250'}]
>> mtu: 1500
>> - name: InternalApi
>> name_lower: internal_api
>> vip: true
>> vlan: 1105
>> ip_subnet: '10.100.5.0/24 [10.100.5.0]
>> <https://urldefense.com/v3/__http:/10.100.5.0/24__;!!LpKI!xc4qNPJ0garbZ7l0yI6qpDEAABzfeM0X6sDwSZT0QNTcENQ9AcDoIFOPzzM$>
>> '
>> allocation_pools: [{'start': '10.100.5.150', 'end': '10.100.5.250'}]
>> mtu: 1500
>> - name: Tenant
>> vip: false # Tenant network does not use VIPs
>> name_lower: tenant
>> vlan: 1106
>> ip_subnet: '10.100.6.0/24 [10.100.6.0]
>> <https://urldefense.com/v3/__http:/10.100.6.0/24__;!!LpKI!xc4qNPJ0garbZ7l0yI6qpDEAABzfeM0X6sDwSZT0QNTcENQ9AcDoCzXKWlQ$>
>> '
>> allocation_pools: [{'start': '10.100.6.150', 'end': '10.100.6.250'}]
>> mtu: 1500
>> - name: External
>> vip: true
>> name_lower: external
>> vlan: 2100
>> ip_subnet: '10.0.1.0/24 [10.0.1.0]
>> <https://urldefense.com/v3/__http:/10.0.1.0/24__;!!LpKI!xc4qNPJ0garbZ7l0yI6qpDEAABzfeM0X6sDwSZT0QNTcENQ9AcDoLdX87P4$>
>> '
>> allocation_pools: [{'start': '10.0.1.4', 'end': '10.0.1.250'}]
>> gateway_ip: '10.0.1.1'
>> mtu: 1500
>>
>>
>>
>> What I am missing.
>>
>> Regards.
>>
>>
>>
>> [avast.com]
>> <https://urldefense.com/v3/__https:/www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail__;!!LpKI!3Rb8aWc2vu_BHTZXCwLgrAFqMD43mcZSUu077veZB9gtUVflc1SP2LgjcIIK$>
>>
>> Virus-free. www.avast.com [avast.com]
>> <https://urldefense.com/v3/__https:/www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail__;!!LpKI!3Rb8aWc2vu_BHTZXCwLgrAFqMD43mcZSUu077veZB9gtUVflc1SP2LgjcIIK$>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/users/attachments/20210816/bb466576/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 18391 bytes
Desc: not available
URL: <http://lists.rdoproject.org/pipermail/users/attachments/20210816/bb466576/attachment-0001.png>
More information about the users
mailing list