opendevreview | Liron Kuchlani proposed openstack/manila-tempest-plugin master: Move access rule creation to the test level method https://review.opendev.org/c/openstack/manila-tempest-plugin/+/839506 | 09:59 |
---|---|---|
opendevreview | Liron Kuchlani proposed openstack/manila-tempest-plugin master: Move access rule creation to the test level method https://review.opendev.org/c/openstack/manila-tempest-plugin/+/839506 | 10:56 |
opendevreview | Merged openstack/manila-ui master: Fix share replica creation https://review.opendev.org/c/openstack/manila-ui/+/837763 | 11:02 |
*** dviroel|rover|out is now known as dviroel|rover | 11:16 | |
fzzf[m] | gouthamr: carloss and in dashboard. show have use these two instance and 8 vcpu, 16g memory... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/YWwtxjMUYZaUcxPKrEJATOkU) | 15:01 |
*** dviroel|rover is now known as dviroel|rover|lunch | 15:29 | |
ecsantos[m] | fzzf: Sorry, I was a bit inactive here lately. You need to create a provider network with a pool of public IP addresses. There's need to be a route between the Zuul executor host and the test nodes provided by your OpenStack cloud, i.e., their IP addresses need to be in the same subnet. About security groups, check the security group rules for the project on which Nova instances are being spawned, you'll need to create an ingress | 16:12 |
ecsantos[m] | rule for protocol TCP in port 22 (OpenSSH) and port 19885. [1] | 16:12 |
ecsantos[m] | [1] https://zuul-ci.org/docs/zuul/latest/howtos/nodepool_static.html#node-requirements | 16:12 |
ecsantos[m] | This requirement for port 19885 is not really well-documented, the above page isn't even in the How-To Guides page index anymore, but it's required | 16:14 |
*** dviroel|rover|lunch is now known as dviroel|rover | 16:18 | |
ecsantos[m] | I see you're passing providers.pools.networks = public to nodepool.yaml. I haven't tested using a public network directly without using floating IPs, it could work, the all the Neutron documentation I've read suggests using a private Geneve or VXLAN network and attaching public floating IPs (flat or VLAN) to instances | 16:18 |
ecsantos[m] | Nodepool will handle attaching and dettaching floating IPs to instances by itself | 16:18 |
ecsantos[m] | We use DevStack instances as cloud providers (this is arguably not ideal), by default it creates one private Geneve network and one public flat network | 16:20 |
ecsantos[m] | You can set your pool of public floating IPs using the Q_FLOATING_ALLOCATION_POOL [2] local.conf option (I personally find the documentation on these options a bit lacking) | 16:22 |
ecsantos[m] | [2] https://docs.openstack.org/devstack/latest/networking.html#shared-guest-interface | 16:22 |
opendevreview | Goutham Pacha Ravi proposed openstack/manila-ui stable/yoga: Fix share replica creation https://review.opendev.org/c/openstack/manila-ui/+/839547 | 18:46 |
*** dviroel|rover is now known as dviroel|rover|biab | 21:12 | |
*** dviroel|rover|biab is now known as dviroel|rover | 22:31 | |
*** dviroel|rover is now known as dviroel|rover|out | 22:54 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!