Sunday, 2020-04-19

*** swest has quit IRC01:14
*** swest has joined #zuul01:29
*** Goneri has quit IRC01:51
*** bhavikdbavishi has joined #zuul02:50
*** bhavikdbavishi has quit IRC02:54
*** bhavikdbavishi has joined #zuul04:01
*** bhavikdbavishi has quit IRC04:30
*** evrardjp has quit IRC04:37
*** evrardjp has joined #zuul04:37
*** bhavikdbavishi has joined #zuul05:00
*** bhavikdbavishi1 has joined #zuul05:37
*** bhavikdbavishi has quit IRC05:39
*** bhavikdbavishi1 is now known as bhavikdbavishi05:39
*** evgenyl has quit IRC06:13
*** stevthedev has quit IRC06:13
*** mugsie has quit IRC06:13
*** Open10K8S has quit IRC06:13
*** evgenyl has joined #zuul06:15
*** stevthedev has joined #zuul06:15
*** mugsie has joined #zuul06:15
*** Open10K8S has joined #zuul06:15
*** bhavikdbavishi has quit IRC06:16
*** bhavikdbavishi has joined #zuul06:36
*** bhavikdbavishi has quit IRC07:25
*** sgw has quit IRC08:13
*** bhavikdbavishi has joined #zuul08:29
*** evrardjp has quit IRC09:01
*** evrardjp has joined #zuul09:07
*** bhavikdbavishi has quit IRC10:44
*** bhavikdbavishi has joined #zuul11:50
*** bhavikdbavishi has quit IRC13:31
mordredfungi: I believe he means the construct in jenkins where you can list a single static node via multiple labels so that it is matched for work when a job requests any of those labels.13:45
*** bhavikdbavishi has joined #zuul15:50
*** evrardjp has quit IRC16:18
*** evrardjp has joined #zuul16:24
*** evrardjp has quit IRC16:35
*** evrardjp has joined #zuul16:35
*** bhavikdbavishi has quit IRC16:39
*** sgw has joined #zuul17:11
*** bhavikdbavishi has joined #zuul17:52
*** bhavikdbavishi has quit IRC19:05
*** bhavikdbavishi has joined #zuul19:32
*** Goneri has joined #zuul19:45
fungiwell, i mean, we labelled non-static nodes too (not that jenkins knows the difference between static and ephemeral nodes)19:49
fungithe idea was that you label nodes based on their capabilities and then write the job to require a specific capability19:50
fungisetting aside the fact that nodepool generally just builds resources on demand, it's not all that different from the association between node labels and images right?19:52
clarkbfungi: one difference is jenkins would do the set union of requirements19:53
clarkbnodepool wont combine a x86 and ubuntu and 8vcpu for you19:54
clarkbbut you can make a label for that if you need it19:54
clarkbitsessentially what we've done for highmem, numa, and gpu nodes19:54
fungii did not realize you could have a jenkins job require multiple labels, but that's definitely something nodepool lacks (we essentially have to explode the possible combinations we care about)19:57
*** bhavikdbavishi has quit IRC20:15
jktcan I tell nodepool from what network to allocate floating ipv4 addresses?21:57
jkt(using the openstack driver)21:57
jktit's unfortunately consistently picking public floating ipv4 addresses from a wrong network, even though there's just one neutron router connected to the network the VMs are in22:05
jktdigging through the sources, this looks like an openstacksdk issue :(22:27
*** Goneri has quit IRC22:31
*** armstrongs has joined #zuul22:39
*** armstrongs has quit IRC22:48
clarkbjkt: you can set it via clouds.yaml23:05
clarkbI forget the  exact settings thoufh23:05
* jkt keeps grepping, but this is not exactly a nice keyword to be searching for23:22
jktclarkb: I tried setting routes_externally, routes_ipv4_externally and default_interface for the network that I would like to use, but that doesn't appear to help23:26
fungii see there's a floating_ip_source option but the documentation doesn't have any info on what all it can do23:35
fungiwe only ever use it by setting it to None signifying not to try to use floating ips on specific providers23:36
fungibut i wonder if you can specify a pool or something there23:36
* jkt checks, thanks23:38
jktfungi: that appears to be just for determining whether to use nova-network or neutron23:39
fungiahh, nevermind then23:39
fungimordred's our openstacksdk whisperer, maybe he can think of something23:40
jktmordred: I'm trying to get nodepool working, but our neutron has many public networks, and openstacksdk is picking the wrong one. I've traced this to wait_for_server(auto_ip=True) -> get_active_server -> add_ips_to_server -> _add_auto_ip -> available_floating_ip -> _neutron_available_floating_ips -> _neutron_create_floating_ip23:47
jktmordred: it seems that _neutron_create_floating_ip() is the culprit; no `network` arg is passed, so it just calls to _get_floating_network_id() which returns the first one, which is a wrong choice for me23:49
jktmordred: I have a neutron router between my network to which my VMs are connected; I am hoping for openstacksdk to look at my routers (just one), see that it is connected to both my network and the correct public one, and choose to use the public network for floating ip requests23:50
jktI wonder why our company-internal deities decided to publish a network that I'm not supposed to use, but meh23:51
jktaaargh, and that's exactly what _get_floating_network_id() would do if only get_external_ipv4_floating_networks() did not return a list of valid networks23:55

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!