Sunday, 2018-04-08

*** odyssey4me has quit IRC00:42
*** odyssey4me has joined #zuul00:42
*** gouthamr has joined #zuul06:51
*** gouthamr has quit IRC07:07
*** yolanda_ is now known as yolanda08:31
*** snapiri- has joined #zuul08:50
*** logan- has quit IRC09:41
*** logan- has joined #zuul09:42
*** JasonCL has quit IRC10:19
*** odyssey4me has quit IRC11:59
*** odyssey4me has joined #zuul12:00
*** rcarrill1 has joined #zuul14:05
*** JasonCL has joined #zuul14:07
*** rcarrillocruz has quit IRC14:08
*** rcarrillocruz has joined #zuul14:13
*** CrayZee has joined #zuul14:14
*** rcarrill1 has quit IRC14:16
*** snapiri has quit IRC14:17
*** elyezer has quit IRC16:13
*** elyezer has joined #zuul16:16
*** elyezer has quit IRC17:18
*** elyezer has joined #zuul17:21
*** elyezer has quit IRC17:29
*** elyezer has joined #zuul17:30
*** elyezer has quit IRC17:40
*** elyezer has joined #zuul17:41
*** elyezer has quit IRC17:55
*** elyezer has joined #zuul18:05
*** elyezer has quit IRC18:12
*** elyezer has joined #zuul18:15
mrhillsmanwhere are docs bugs filed and where are patches submitted?18:16
mrhillsmanwhen you get a moment corvus ^18:17
clarkbmrhillsman: zuul docs are in the zuul repo and nodepool in nodepool and so on18:22
mrhillsmanyep18:22
clarkbbugs should be filed against those repos and patches pushed to then18:22
mrhillsmanbut - https://git.zuul-ci.org18:22
mrhillsmanso just use that vs o.o18:23
mrhillsmanor they are sync'd so does not matter18:23
mrhillsmanjust follow o.o workflow18:23
clarkbthose are hosted repos but not used for code review or bugs or docs18:24
mrhillsmanok thx18:24
clarkbsimilar to how git.openstack.org gives a reliable read only mirror of the content18:28
mrhillsmangotcha18:31
mrhillsmanwas not sure if anything additional had changed related to docs since things point to zuul-ci.org/docs18:31
mrhillsmanreading the docs i am reading that is - zuul-from-scratch18:32
openstackgerritMelvin Hillsman (mrhillsman) proposed openstack-infra/zuul master: Remove openstack-infra reference  https://review.openstack.org/55958618:36
*** elyezer has quit IRC19:12
*** elyezer has joined #zuul19:13
*** JasonCL has quit IRC19:16
*** elyezer has quit IRC19:41
*** elyezer has joined #zuul19:42
*** JasonCL has joined #zuul19:50
*** JasonCL has quit IRC19:55
mrhillsmanclarkb does nodepool-builder use a different port than 2181 or some other config options to know to use dib to build images?20:03
mrhillsmanfor some reason my nodepool-builder is simply not deciding to build image and create nodes from that20:04
mrhillsmanif i tell it to use cloud-images, no problem20:04
mrhillsmanconfig-validate checks out20:04
mrhillsmani am quite confident the config is proper20:04
mrhillsmani see it establish a connection with zookeeper20:04
mrhillsmanthere are no other builders/launchers running20:04
clarkbNo it talks to zookeeper on the default port unless you configure something different20:05
clarkbIt wont build images if no providers are configurws to use them I think20:05
mrhillsmani think, let me confirm that last statement20:05
mrhillsmanyeah, no other nodepool stuff running20:05
mrhillsmanonly one provider, only configured to use these images20:06
mrhillsmanmind looking - http://paste.openstack.org/show/718689/20:07
mrhillsmando i need disk-images at the same level as region-name?20:08
mrhillsmanlooking that is the only thing i can think of that i have not tried20:08
mrhillsmansince i see cloud-images there20:08
mrhillsmani bet that is it, maybe my eyes just did not hone in on this from the docs20:09
mrhillsmani have pool set but not provider -_-20:09
mrhillsmanugh, i see it in the docs now20:10
mrhillsmannvm20:10
clarkbyou need the cloud images stuff20:10
clarkbthats what maps an image built locally to the clojd20:11
clarkband it wont build images if they arent mapped to any vlouds20:11
clarkbto avoid unnecessary churn20:11
mrhillsmani thought that was for images i have in the cloud already? those not built by the builder20:12
mrhillsmanlooking over the docs again it is a bit confusing i think so will suggest some edits as well20:12
* clarkb double chwcks20:12
mrhillsmani'm reading https://zuul-ci.org/docs/nodepool/configuration.html20:12
clarkbsorry uts the diskimages section that does that20:13
mrhillsmanthese new docs i think are a bit different than the old ones20:13
mrhillsmannot sure everything got pulled over or re-org'd as clearly20:14
clarkbso you need a provider diskimages section for thag diskimage to map it onto a provider20:14
mrhillsmangot confused with diskimages20:14
mrhillsmangot it20:14
mrhillsmancloud-images in provider and cloud-image in pool is clear20:15
mrhillsmandiskimages and diskimages in provider and pool not so much :)20:15
mrhillsman"Each entry in a provider’s diskimages section must correspond to an entry in diskimages."20:16
mrhillsmanif you miss that there will be hell to pay lol20:16
mrhillsmanand i am not sure cloud-images/cloud-image was in the old docs, or i just missed that because was always using diskimages, and so i thought something changed and i was looking for diskimages and disk-image20:17
clarkbcloud images us new20:17
clarkbone improvement here could be to error on config validation if a pool label uses a diskimage not in provider diskimages20:18
mrhillsman++20:19
mrhillsmannodepool docs could use some hierarchy splitting like zuul which i think will help too, will suggest something hopefully before someone else beats me to it20:20
mrhillsmanit's all on one page which can throw you off, seems like providers could work well like how connections is split up in zuul docs20:20
*** patriciadomin has quit IRC20:54
*** patriciadomin has joined #zuul20:55
*** JasonCL has joined #zuul20:57
*** JasonCL has quit IRC21:20
*** JasonCL has joined #zuul21:30
*** JasonCL has quit IRC21:34
*** JasonCL has joined #zuul21:51
*** JasonCL has quit IRC21:52
*** JasonCL has joined #zuul21:52
*** elyezer has quit IRC23:38
*** elyezer has joined #zuul23:38

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