weizhouapache commented on issue #10703: URL: https://github.com/apache/cloudstack/issues/10703#issuecomment-2802894284
> Yes, they are configured via NetworkManager, but they have other names (I read that cloudbr0 and cloudbr1 are not mandatory names, so I decided to go with names I can work with) > ``` > [root@myhost root]# nmcli c > NAME UUID TYPE DEVICE > br_net0 fbb70492-5f6e-49a6-ab08-7ec0e44075a3 bridge br_net0 > br_npf0 1efc9f99-264b-4093-8c97-7a1c3d6ff2ec bridge br_npf0 > br_clients 8dee85da-513a-4c03-aca8-2b89097f28ea bridge br_clients > bond0 caf4d02a-e999-4559-af05-7f270531056c bond bond0 > br_bgp0 2b6aa2d5-59bc-46f1-a2a0-9df786fbd8be bridge br_bgp0 > [...] > ``` > > Btw, running `cloudstack-setup-agent` manually works (but the host doesn't appear on the management server): > ``` > cloudstack-setup-agent -a -m cloudstack01i.npf.local -z NPF_CORE -p NPF_CORE_POD -c NPF_CORE_CLS -t kvm --pubNic=br_net0 --prvNic=br_npf0 --guestNic=br_clients -g $(uuidgen) > Starting to configure your system: > Configure Host ... [OK] > Configure SElinux ... [OK] > Configure Network ... [OK] > Configure Libvirt ... [OK] > Configure Firewall ... [OK] > Configure Nfs ... [OK] > Configure cloudAgent ... [OK] > CloudStack Agent setup is done! > ``` > > [EDIT]cloudstack-agent shows that server certificate isn't good, which isn't surprising since I used an internal dns name[/EDIT] > Go to zone->physical networks, update the kvm network traffic label of the physical networks to br_xxx0 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
