Monday, 2020-02-10

*** goldyfruit has quit IRC00:42
*** goldyfruit has joined #openstack-kolla00:44
*** zhanglong has joined #openstack-kolla00:45
*** xinliang has joined #openstack-kolla00:54
openstackgerritNoboru Iwamatsu proposed openstack/kolla-ansible master: Adapt to Octavia Certificate Configuration Guide.  https://review.opendev.org/70620301:02
*** cloudnull has quit IRC01:04
*** cloudnull has joined #openstack-kolla01:05
*** openstackstatus has joined #openstack-kolla01:16
*** ChanServ sets mode: +v openstackstatus01:16
*** dking_desktop has quit IRC01:35
*** zhanglong has quit IRC01:42
*** zhanglong has joined #openstack-kolla01:45
*** zhanglong has quit IRC02:22
*** pbing19 has joined #openstack-kolla04:18
*** ricolin has joined #openstack-kolla04:34
*** Tony31 has joined #openstack-kolla04:36
*** skramaja has joined #openstack-kolla04:46
*** pbing19 has quit IRC04:57
osmanlicilegimorning05:29
Tony31good morning05:32
*** evrardjp has quit IRC05:34
*** evrardjp has joined #openstack-kolla05:34
Tony31how could I debug the nova_compute container keep restarting? This was during deployment and deployment failed due to waiting for the compute service to register05:40
Tony312nd problem which I am facing is the compute node is not getting the storage network provisioned onto it05:40
Tony31`FAILED - RETRYING: Waiting for nova-compute services to register themselves (1 retries left).05:41
Tony31"--os-project-domain-name", "default", "--os-tenant-name", "admin", "--os-username", "admin", "--os-password", "removed", "--os-user-domain-name", "default", "--os-region-name", "RegionOne", "compute", "service", "list", "--format", "json", "--column", "Host", "--service", "nova-compute"], "delta": "0:00:03.594549", "end": "2020-02-1005:41
Tony3112:47:13.118327", "rc": 0, "start": "2020-02-10 12:47:09.523778", "stderr": "", "stderr_lines": [], "stdout": "[]", "stdout_lines": ["[]"]}`05:41
osmanlicilegiTony31: is it train?05:58
osmanlicilegiTony31: are you using k-a provided ceph or something else?06:00
Tony31hi, it's Train and is kayobe06:02
Tony31p.s. - could be user error on my part - this is my first time going through the deployment06:02
Tony31I wonder if the compute node is trying to contact the DNS `fqdn:35357`06:05
Tony31dns was not resolving06:08
*** shyamb has joined #openstack-kolla06:16
*** pbing19 has joined #openstack-kolla06:17
osmanlicilegiTony31: ah kayobe... unfortunately I'm not a kayobe guy yet :|06:31
Tony31:)06:32
Tony31no worries - thanks for your help. I think adding the /etc/hosts has fixed that problem, the deploy is still running now06:32
Tony31I'm really excited over this kayobe/openstack deployment. I hope to contribute as much as I can.06:34
osmanlicilegiTony31: glad to hear that :]06:35
Tony31deployment completed - adminrc.sh files are created now... i'll continue on to post deployment06:35
Tony31:)06:35
osmanlicilegikayobe will rule my deployments too at future06:36
openstackgerritMerged openstack/kolla master: aarch64: enable influxdb and telegraf for Debian/Ubuntu  https://review.opendev.org/70497006:37
Tony31While going through this, it's so much easier than the tripleo. I had a thought - I think it would be easy to create a web configuration front-end. Like some web page that you can use, to fill out the boxes or drag/drop config to create the openstack design06:37
Tony31Hooray I now have a horizon login page :)06:38
osmanlicilegigreat! now it's time to enjoy your cloud :]06:40
Tony31almost - I need to figure out: 1) why the controller does not have a storage network added (I understand it's required for building instances) 2) why the compute node doesnt have a storage network (required for cinder isci for instances) 3) how to configure cinder 4) how to configure LDAP/Active Directory06:46
Tony31Then I can look at minor things :)06:46
*** shyamb has quit IRC06:56
xinliangHello all, anyone knows is it possible to upgrade kolla oenstack from rocky directly to train? Or the right upgrade way is  rocky->stein->train ?06:58
Tony31Hi Xinliang, I believe that all openstack need to upgrade to each release. So you need Stein > Train. You cannot miss any release. The only time you can miss a release, is if there are specific instruction for how to achieve it.07:02
*** numans_ has joined #openstack-kolla07:02
Tony31https://docs.openstack.org/kayobe/train/upgrading.html#upgrading-the-overcloud07:02
xinliangTony31: thanks, I do tried upgrade from rocky directly to train. The upgrade process repoorts no error, but some service, such as cinder, horizon does not work properly.07:12
xinliangIf there is this limiation, really hope we can document it here:https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html#limitations-and-recommendations07:13
Tony31Are you able to wait for the experts to come online, so that you can speak with them?07:14
Tony31I am sorry that I am not an expert with this.07:14
*** shyamb has joined #openstack-kolla07:14
xinliangSure, thanks Tony3107:14
*** sri_ has joined #openstack-kolla07:26
sri_Hi Tony31, quick question kayobe work with vmbc ?07:29
Tony31Hi sri_ - virtual bmc? You mean like for pxe boot VMs ?07:30
sri_Tony31, Yes07:30
sri_tto test baremetal provisioning07:31
Tony31Actually, I had this same chat with the devs here last week - They said to me that there's no point pretending that VMs are real bare metal. And they told me to just install the VM myself manually, set up the SSH access key and then add the VM(s) to the inventory. So I done just that. And it saved me the trouble of messing around with any vbmc07:31
*** cah_link has joined #openstack-kolla07:31
sri_hmm, ok07:32
Tony31If you just want to test real bare metal with vbmc then I dont know... but I guess you would need to fake the ipmi (or other interface). I was leaning to go down this path but it's not required for a deployment onto VMs.07:32
Tony31vbmc should work - all you would be doing is faking the ipmi or other management interface.07:33
sri_I was thinking to use tripleo for baremetal provisioning and just kolla-ansible07:33
sri_to deploy openstack07:33
sri_I've not give try with kayobe yet07:34
Tony31I have tripleO already deployed, I have the controller as a VM. At that time (3 years ago) I used the fake driver for ipmi and then powered on the VM manually during the deployment. Was a pain. :)07:34
Tony31With kayobe - I did not need any of that pain.07:34
sri_ack07:35
Tony31when you say bare metal provisioning, are you talking about deploying openstack onto bare metal? Or are you talking about using openstack to deploy instances onto entire bare metal ?07:35
sri_deploying openstack to baremetal07:36
Tony31ok07:37
*** dciabrin has joined #openstack-kolla07:37
sri_Tony31, Thanks for the info, Last week I saw you mentioned about the DR with ovirt and openstack, that's really interesting07:43
*** Tengu has quit IRC07:44
Tony31Yes - so basically where I am at the moment is trying to create an openstack that will allow me to implement a DR plan for my org. with it. The tripleO deployment which I have has problems, like 1) can't upgrade it 2) running Pike version 3) can't access the tools I need for DR 4) can't maintain it 5) lack of documentation or rather, lots of07:45
Tony31documentation errors or confusing documentations07:45
Tony31so I've gone back to the beginning and working on re-deploying and migratiom07:45
*** Tengu has joined #openstack-kolla07:46
Tony31oVirt has a DR plan which I have set up and tested as working. I havent decided how I'll achieve it with Openstack as yet. But I have 2 x baremetal compute in the DR site only. I'd prefer to keep 2 x compute tied in with oVirt so that oVirt has resilience. And then run a virtual compute node on top of that, which would be used in DR scenario only.07:47
Tony31But I have yet to dive into it, or plan / test.07:47
Tony31...virtual compute node for openstack, I mean07:48
sri_I am also working on same thing DR for openstack , we were using Tripleo as you told it's very hard to customize07:48
Tony31I would accept lower performance in the DR situation. Although, the DR site is new and the CPUs and memory are also new and much faster than my production site. So I am expecting not much difference in performance.07:48
Tony31The way I set up tripleO was to deploy it as best I could. Then do manual post-deployment of cinder, horizon, ldap and add projects, routers and networks. I was unable to achieve that during the deployment for various reasons.07:50
Tony31I would have tried to stick with tripleo if the documentation supported me. But I'm on Pike and the documentation which is there doesnt align.07:51
sri_true, i think it's apply for all big opensource source projects07:53
sri_it's really interesting approach the way you are planning to DR. I will also try to do some POC07:55
Tony31yes - test, test and test again :)07:55
sri_Tony31, i really appreciate your input :)07:56
Tony31my idea is to layer the design. With oVirt managing the lower bare-metal and the failover of the VMs.07:57
Tony31Actually, it's Red Hat Virtualisation, where I have support. It's just red hat branded, supported oVirt.07:57
sri_Is it same as Red Hat Virtualization ?07:58
Tony31yes, redhat = support07:59
Tony31and different logo ;)07:59
sri_Got it :)07:59
yoctozeptoxinliang: openstack requires upgrade from release to release, skipping releases is not supported08:00
Tony31experts incoming ^ :)08:00
*** shyamb has quit IRC08:01
yoctozeptoTony31: thanks08:01
yoctozepto06:40:21 <Tony31> how could I debug the nova_compute container keep restarting? This was during deployment and deployment failed due to waiting for the compute service to register08:01
yoctozepto06:41:19 <Tony31> `FAILED - RETRYING: Waiting for nova-compute services to register themselves (1 retries left).08:01
yoctozeptothese are the very same problem08:01
yoctozeptolook into /var/log/kolla/nova/nova-compute.log08:01
Tony31thanks - that issue was due to dns. the compute node could not contact the controller due to missing dns resolution. Fixed with /etc/hosts entry08:02
*** cah_link has quit IRC08:02
Tony31i successfully deployed08:02
yoctozepto(I'm writing these paths from the top of my head)08:02
yoctozeptoah, understood08:02
Tony31:)08:02
yoctozeptowell, now you also know how to debug08:02
Tony31thanks :)08:02
yoctozepto07:46:17 <Tony31> almost - I need to figure out: 1) why the controller does not have a storage network added (I understand it's required for building instances) 2) why the compute node doesnt have a storage network (required for cinder isci for instances) 3) how to configure cinder 4) how to configure LDAP/Active Directory08:02
Tony31my controller and compute node does not have storage network - do I need to enable cinder and iscsi in kolla.yml ?08:02
*** mleone87 has joined #openstack-kolla08:02
yoctozeptoad 1) no idea, depends on storage configuration - it might not be necessary there08:02
yoctozeptoah, yeah, storage is for cinder08:03
Tony31ok - no problem. This is what I like. Deploy - see a problem - fix problem, move on to the next. Always learning08:03
yoctozeptobut I don't know kayobe flow so not sure if it should be there already or not08:03
*** bengates has joined #openstack-kolla08:04
Tony31is it right that kayobe is just layered over the top of kolla?08:04
yoctozeptoad 3) enable_cinder is a good start, then decide on the backend08:04
yoctozeptoTony31: yeah, kayobe (provision of baremetal with bifrost) -> kolla-ansible (deployment of openstack) -> kolla (container images)08:04
Tony31thank you08:05
yoctozeptonp08:05
Tony31for LDAP with keystone, to enable the `domain` - along with the modification of the horizon to enable the `domain` field on the login page - is this a manual task with kolla-ansible? I mean, do I need to log in to the containers and make the config change then restart the container?08:06
xinliangyoctozepto: I see, thanks.08:07
*** cah_link has joined #openstack-kolla08:09
sri_Tony31, I don't think you don't have to login to the containers, All the configuration is out of container, exp: /etc/kolla/keystone/  you make changes to config and restart the container08:09
sri_yoctozepto, correct me if i am wrong^08:10
Tony31wow thanks sri_ - I only checked `ls -l /etc/key` and it wasnt there. So I then logged into the container08:10
yoctozeptoTony31: sri_ is right, then you just need to reconfigure08:10
yoctozeptoor whatever kayobe calls that :-)08:11
Tony31but indeed, on the controller, the config file is there `/etc/kolla/keystone`08:11
yoctozeptoon the deployment host you add such overrides08:11
mnasiadkamorning08:11
yoctozeptoand kolla-ansible merges them08:11
Tony31what I am worried about is making the config change on the controller directly, then running the `kayobe overcloud service reconfigure` will wipe out the config08:11
yoctozeptomnasiadka welcome, our timezone-friendly local kayobe expert08:11
Tony31morning08:11
yoctozeptoTony31: yeah, you should not do that08:12
yoctozeptothe overrides are on the deployment host08:12
*** sorin-mihai has quit IRC08:12
Tony31my deployment host is the ansible control host08:12
mnasiadkayoctozepto: I wouldn't put the kayobe expert close to my name, I just use it :)08:12
yoctozeptomnasiadka: shh08:12
yoctozepto;D08:12
Tony31but I cant see where to add such config - do I need to make up ansible files for it?08:12
mnasiadkait's hard to read from history what are you trying to achieve - can you write it once again?08:15
*** tonythomas has joined #openstack-kolla08:16
*** gfidente has joined #openstack-kolla08:20
kevinzhrw: ^08:27
yoctozeptomnasiadka: override keystone config for kayobe08:29
kevinzhrw: there?  xinliang met a problem about upgrade from Rocky-> Train. It looks that we can't do skip version upgrade from R->T, just can do R->S->T08:29
*** carli has joined #openstack-kolla08:31
mnasiadkayoctozepto, Tony31: I think this describes how to override globals and per service config in kayobe - https://docs.openstack.org/kayobe/latest/configuration/kolla-ansible.html08:31
mnasiadkaespecially this: https://docs.openstack.org/kayobe/latest/configuration/kolla-ansible.html#service-configuration08:32
yoctozeptokevinz: yeah, no matter the deployment method08:32
Tony31thank you - reading08:33
yoctozeptokevinz: it's also necessary to adjust any config as mentioned in the upgrade notes08:33
kevinzhi yoctozepto, sure thanks, upgrading action is dangerous08:34
mnasiadkakevinz: we do not support fast-forward upgrades, also known as skip-level upgrades08:34
mnasiadkathere was some work around it - but nobody picked it up08:34
*** ivve has joined #openstack-kolla08:36
kevinz<mnasiadka> : yes I see. If we must to do so, I guess much configurations need to be sort out08:37
mnasiadkakevinz: nobody said OpenStack is easy :)08:38
kevinzmnasiadka: absolutely :D08:38
yoctozeptomnasiadka: does any deployment project support it anyway?08:39
mnasiadkayoctozepto: tripleo - they have to08:40
yoctozeptomnasiadka: mhm, interesting08:40
mnasiadkayoctozepto: since RHOS supports LTS releases - and it's every third release I think08:40
*** shyamb has joined #openstack-kolla08:40
Tony31so I do not have storage network configured on compute or controller. I have just enabled Cinder service in `kolla.yml` and I can see the cinder containers now - but still no storage network. I think I need to run `kayobe overcloud host configure` -> can anyone confirm?08:40
yoctozeptoah, because they ensure specific paths08:40
mnasiadkaso in most customer envs  - every upgrade is a FFU...08:40
yoctozeptoso it's not like they allow just any update to happen anyway08:40
*** rpittau|afk is now known as rpittau08:41
yoctozeptoor, well, "allow" is not the best08:41
mnasiadkayoctozepto: I survived doing N->Q in TripleO for my previous employer08:41
yoctozeptothey don't offer "unb0rkability promise"08:42
Tony31tripleo is similar (if not same) to RHOS. I used RHOS docs to fill in the tripleO documentation gaps.08:42
yoctozeptoTony31: RHOS is commercial offering of tripleo exactly08:42
Tony31got it, thanks08:42
mnasiadkayoctozepto: need your review on https://review.opendev.org/#/c/704309 :-)08:42
patchbotpatch 704309 - kolla-ansible - Remove kolla-ceph - 9 patch sets08:42
yoctozepto"mnasiadka: I need to learn to apologise for the apologising :-)"08:43
yoctozeptodid you?08:43
mnasiadkanot yet08:43
yoctozeptothen no +208:43
mnasiadkaonly working with the Brits since August 2019 :D08:43
yoctozepto;D08:44
yoctozeptooh my, the change is brutal08:44
yoctozepto+90, -315508:44
*** Luzi has joined #openstack-kolla08:45
*** pbing19 has quit IRC08:49
*** pbing19 has joined #openstack-kolla08:49
*** mleone87 has quit IRC08:52
Tony31""mnasiadka: I need to learn to apologise for the apologising :-)" 🤣🤣 you know us well :)08:53
mnasiadkayoctozepto: I guess it's not easy to rip apart years of code :)08:53
Tony31I ran again `kayobe overcloud host configure` and i am still not getting storage network on compute or controller08:56
Tony31confused about it08:56
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: OVN Support  https://review.opendev.org/69684108:56
mnasiadkaTony31: https://docs.openstack.org/kayobe/latest/configuration/network.html#network-to-host-mapping08:57
Tony31in `networks.yml` i have, all of these assigned to the storage network: `storage_net_name:` / `ceph_storage_net_name` / `swift_storage_net_name:` / `swift_storage_replication_net_name`08:58
Tony31mnasiadka - I was expecting the storage aspect to be covered in the networks.yml - is it not the case?08:59
*** dougsz has joined #openstack-kolla08:59
Tony31have to rush off - i'll come back in a few hours. If you reply to my Q I'll check the logged messages :)  Thanks all - tachau09:01
*** Tony31 has quit IRC09:06
yoctozeptomnasiadka: reviewed, uff09:07
mnasiadkathanks :)09:08
*** sri_ has quit IRC09:17
*** k_mouza has joined #openstack-kolla09:17
*** bjolo has joined #openstack-kolla09:19
*** k_mouza has quit IRC09:22
*** rgogunskiy has joined #openstack-kolla09:43
bjolomorning09:45
mgoddardmorning09:47
bjolohi marc, how are you>?09:47
*** k_mouza has joined #openstack-kolla09:50
hrwmorning09:53
mgoddardhi bjolo. Long time no see. I'm good thanks. And you?09:55
*** dking_desktop has joined #openstack-kolla09:57
bjologood good09:58
bjoloyah i know. been a while since i was around :)09:58
bjolobeen busy with other stuff than OS10:00
bjolomostly non tech10:03
bjolobut now im back to handson and pending upgrades in the near future10:03
bjolokolla still seems alive and thriving :)10:04
*** shyamb has quit IRC10:04
yoctozeptobjolo: yeah, it is10:04
yoctozeptoever-blooming10:04
bjolonice :)10:04
bjolowe run 2 clouds on kolla rocky, going to stein in a 1-2 months10:05
bjoloi have a silly question... perhaps google fu is bad this monday morning but.. where do i report a bug on openstackclient?10:06
bjoloand also for kolla. is that still launchpad?10:07
hrwkolla yes10:07
mnasiadkakolla uses launchpad10:07
yoctozeptomgoddard, mnasiadka: as far as upgrades are concerned, I upgraded production from stein to train; obviously dropped horizon vncproxy sessions due to haproxy restart but otherwise no user impact, woop woop10:07
mnasiadkaopenstackclient probably uses storyboard10:07
mnasiadkayoctozepto: probably you were just lucky, it can't be so straightforward :)10:08
yoctozeptomnasiadka: thought so, my bad!10:08
*** dking_desktop has quit IRC10:12
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: OVN Support  https://review.opendev.org/69684110:16
*** Tengu has quit IRC10:17
*** Tengu has joined #openstack-kolla10:18
*** cah_link has quit IRC10:18
*** shyamb has joined #openstack-kolla10:19
bjologee storyboard is slow10:21
yoctozeptobjolo: complaints go to #storyboard10:22
*** cah_link has joined #openstack-kolla10:23
*** Tengu has quit IRC10:31
hrwstorage-sig managed to rebuild / crosstag all ceph nautilus deps into10:33
hrwstorage8-ceph-nautilus-candidate [1] target thanks to the new el8 buildroot10:33
hrwcentos-release-ceph-nautilus will arrive soon10:33
*** Tengu has joined #openstack-kolla10:40
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: OVN Support  https://review.opendev.org/69684110:42
mnasiadkahrw: that's interesting, given the previous statement by Sage that Nautilus will not be supported on centos8 :)10:44
mnasiadkaand these are only deps, still I can't find any ceph package built on el8 using cbs10:46
hrwmnasiadka: ach, right. need more coffe10:49
hrw-ENOCOFFEE10:49
*** shyamb has quit IRC10:58
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: Remove kolla-ceph  https://review.opendev.org/70430911:10
openstackgerritMark Goddard proposed openstack/kayobe master: [ussuri][goal] Drop python 2.7 support and testing  https://review.opendev.org/69561711:17
*** Tony31 has joined #openstack-kolla11:18
Tony31Hi guys11:19
Tony31:)11:19
mgoddardhi Tony3111:20
Tony31maybe I can word it this way - what are the storage networks for, in networks.yml ? Why are they there and why do we have to configure them a part of the first steps?11:20
Tony31Are any of those used for cinder / iscsi?11:20
Tony31Are any of them used for glance image download during instance build process ?11:20
Tony31Hi Mark :)11:21
mgoddardFirst, I saw you were asking about SSH users. Try the *_bootstrap_user variables (e.g. controller_bootstrap_user). These are used when first accessing the hosts to setup the stack user that is used from that point onwards11:24
mgoddardstorage networks are used by ceph and swift11:24
Tony31Sorry, i should probably provide an update :)11:25
Tony31I managed to successfully deploy today :)11:25
mgoddardoh, great work!11:25
Tony31the issue which I am facing now at this point (which means I am misunderstanding / not done something, but i dont know what, yet) is that the controller and compute does not have the storage subnet configured onto them11:25
Tony31i am planning to use cinder/iscsi. no storage nodes. I have external storage that I would like to use11:26
Tony31the storage network via compute will be used to mount the instance volumes11:26
Tony31and from past experience, the storage subnet is required on the controller node, because during the instance build process, the controller mounts the storage, downloads the image from glance and then moves the storage over to a compute node to run the instance11:27
*** jopdorp has joined #openstack-kolla11:27
Tony31i've enabled cinder in kolla.yml and re-deployed using the kayobe configure11:27
mgoddardTony31: ok. compute nodes should be on the storage network by default11:27
*** shyamb has joined #openstack-kolla11:28
mgoddardhave you set storage_net_name and defined a subnet, vlan etc?11:28
Tony31ok, I thought this... Also I had a inventory issue which meant the compute node was not built at first. Once I fixed the inventory issue I went back and re-ran kayobe overcloud host configure and provision11:29
*** tony3170 has joined #openstack-kolla11:32
tony3170sorry my vpn kicked me off11:32
tony3170yes I have that11:32
*** Tony31 has quit IRC11:33
*** sri_ has joined #openstack-kolla11:34
tony3170I also have `compute_network_interfaces:  - inside  - osiapi  - osipip  - ossana`11:34
tony3170last one is OS-SAN-A `ossana`11:34
mgoddardtony3170: you could try looking at `kayobe configuration dump`. You can run it for one host, and even dump a single variable. The network_interfaces variable is the list of neteworks the host is mapped to11:35
tony3170and in hos_vars/group_vars I have which network name corresponds to which ethX interfacw11:35
tony3170ok great I'll try that :)  thanks11:35
tony3170when I make host changes, do I need to run kayobe host configure11:36
hrwTASK [common : Pulling common images] ********************************************************************************************************************11:40
hrwAn exception occurred during task execution. To see the full traceback, use -vvv. The error was: ImportError: No module named ssl_match_hostname11:40
hrwmeh...11:40
tony3170i dont see the config there in the config dump11:43
tony3170it shows the allocation pool but not a host IP for any node11:43
*** zhanglong has joined #openstack-kolla11:44
tony3170wait - let me check these variables have the correct spelling11:44
tony3170i think it would have worked if i didnt have a typo in the host config 🙈11:46
tony3170re-running conigure now11:46
tony3170thanks Mark11:46
tony3170looking good so far - storage node has a storage IP11:48
*** rgogunskiy has quit IRC11:48
tony3170fixed - thank you11:53
hrwwhy ansible produces so unreadable error messages?11:57
hrwhttps://pastebin.com/HW8F2Kcc11:57
mnasiadkathat's jinja11:59
mnasiadkatemplate error while templating string: no filter named 'kolla_address'11:59
mnasiadkapip install kolla_ansible :)11:59
hrwmnasiadka: 'pip install .' was done..11:59
hrwHEAD of master12:00
mnasiadkayeah well, so then ansible can't find it12:00
hrw(venv3) 13:01 (1s) hrw@puchatek:kolla-ansible$ grep -r "def kolla_address" ../venv3/12:01
hrw../venv3/lib/python3.7/site-packages/kolla_ansible/kolla_address.py:def kolla_address(context, network_name, hostname=None):12:01
mnasiadkaare you sure ansible uses python3, not python2? :)12:02
hrwmnasiadka: first checkd for py3 then py2 so should py312:03
hrwchecked. py312:04
mnasiadkaso that's purely interesting12:05
*** rgogunskiy has joined #openstack-kolla12:05
hrwmeh. will then move to target machine and do all-in-one on localhost12:06
*** rpittau is now known as rpittau|bbl12:08
hrwso fresh os, fresh venv12:11
*** kplant has joined #openstack-kolla12:13
mgoddardtony3170: great!12:13
hrwmeh. another set of stein fixes needed ;(12:13
tony3170now to figure out applying .conf config. I have some things to read through tomorrow12:14
admin0"Kayobe is a subproject of Kolla that uses Kolla Ansible and Bifrost to deploy an OpenStack control plane to bare metal." - this means no docker containers ?12:21
*** shyamb has quit IRC12:21
kplantno it still uses docker12:21
*** tony3170 has quit IRC12:22
admin0i am trying for days to get a all-in-one up .. failing .. who can help ? https://asciinema.org/a/ig2c0AOq8xenGdOgzZxf99wNM12:22
hrwadmin0: kayobe uses kolla-ansible to deploy containers built with kolla.12:22
kplantkolla-ansible takes systems that have already been provisioned with OS and networking and goes from there12:22
kplantkayobe starts from almost nil and loads the OS... then kicks off k-a12:22
admin0so kayobe will build the docker images locally and then deploy .. while kolla-ansible will use pre-built images ?12:22
kplantno, that's not the difference12:23
hrwadmin0: kayobe does not call kolla to build containers.12:23
kplantkayobe will use bifrost to deploy the OS on the nodes in your inventory12:23
admin0ok .. as an operator, who just wants openstack installed, how do I decide which route i need to take ?12:24
kplantdo you want to install the operating system yourself?12:24
kplantor do you want something else to do it for you12:24
admin0oh oh .. now i get it12:24
admin0overcloud  / undercloud type12:24
kplantyou could say it's similar to tripleo - yes12:24
admin0thanks for the clarification12:25
admin0please review my terminal recording .. i am not sure why i am getting issues .. i *think* I followed the documentation as mentioned12:26
mgoddardadmin0: where did you get the all-in-one inentory from?12:30
admin0i copied it12:30
admin0its in the instructions12:30
mgoddardfrom where?12:30
mgoddardok12:30
admin0our kolla readme12:31
admin0let me12:31
mgoddardI see12:31
admin0https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html   Copy all-in-one and multinode inventory files to the current directory. ..12:31
kplantalso, what version of ansible are you running?12:31
mgoddardit says that localhost has not hostvars12:31
mgoddardwhat version of ansible are you using?12:32
mgoddard:)12:32
admin0i am supposed to follow the docs and get it working :)12:32
admin0let me check the versions12:32
kplanti've copied and pasted the quickstart guide several times with success12:32
admin0which is why I recorded it this time to present here12:33
admin0all steps done in a brand new 18.04 install12:33
mgoddard"Currently, Kolla Ansible requires Ansible 2.6+."12:33
mgoddardin the quickstart :)12:33
mgoddardoften the version provided by the distro is old. You might be better using pip12:33
hrwand 18.04 has 2.5.broken12:34
admin0ansible 2.5.112:34
mgoddardvery old12:34
admin0so where in our docs give the steps to upgrade this ?12:34
mgoddardpip install 'ansible>2.6'12:34
kplantalso: 'Install Ansible. Kolla Ansible requires at least Ansible 2.8 and supports up to 2.9.'12:34
admin0its now downloading 2.9.412:35
kplanthttps://docs.openstack.org/kolla-ansible/latest/user/quickstart.html12:35
hrwfsck. stein and it's 2.7 python...12:35
kplantfsck failed: please repair manually and reboot12:36
admin0this step is not in   "Install dependencies not using virtual environment" where the docs say  apt-get install ansible instead of this12:36
kplant`Install Ansible. Kolla Ansible requires at least Ansible 2.8 and supports up to 2.9.`12:36
hrwadmin0: send patch to the docs?12:36
kplantthat's right in "Install dependencies not using a virtual environment¶"12:36
admin0yeah .. planning to do that12:36
admin0yes ..  3. Install Ansible. Kolla Ansible requires at least Ansible 2.8 and supports up to 2.9.  and then in the steps to copy paste for ubuntu run:  apt-get install ansible12:37
admin0i will try to send a patch note and put more comments to the docs12:37
* hrw votes for marking ubuntu as not supported distribution12:37
kplant^12:37
kplantcanonical is the absolute devil12:37
kplantcan i say that in here without getting shot?12:38
hrwkplant: I do not care ;D12:38
admin0failed at the exact same error12:38
admin0The conditional check 'inventory_hostname not in groups['bifrost'] or 'ansible_' + hostvars[inventory_hostname]['api_interface']12:38
hrwmgoddard: why we did not had debian-source CI in stein? :(12:39
*** zhanglong has quit IRC12:40
admin0its a single system .. i ran all-in-one .. why its complaining about bifrost12:41
kplantthat's probably the first group, alphabetically12:42
kplantit has nothing to do with bifrost, just the first group that got hit and failed12:42
*** zhanglong has joined #openstack-kolla12:42
hrw2020-02-10 13:43:28.676 6 ERROR nova.compute.manager [instance: 7d62960f-ecc4-458a-a6f5-a418dee52ec2] libvirt.libvirtError: invalid argument: could not find capabilities for domaintype=kvm12:44
hrwnasty...12:44
admin0i am going to remove the apt installed ansible, do a apt clean, remove all dependencies and retry again12:45
admin0it moved forward \o/12:48
admin0does kolla also manage the external_vip address and add it automatically ?12:52
admin0or is the external address supposed to be NAT to the internal vip address12:52
* admin0 starts to read global file :)12:54
hrw~curse py212:54
mgoddardadmin0: kolla manages the VIP12:55
admin0yeah.. i see it now in the configs12:56
admin0kolla-ansible  -i ./all-in-one deploy -- this finished .. but i do not see any service docker containers .. i only see rabbit, memcached, db, keepalived, haproxy, chrony, cron, kolla_toolbox and fluentd12:57
admin0shouldn't i be seeing neutron, glance etc also ?12:57
mnasiadkayoctozepto: have any useful conclusions with keepalived?12:58
hrwfolks: can rocky debian/source be migrated to stein debian/binary to train debian/source?12:59
*** shyamb has joined #openstack-kolla12:59
admin0rabbit failed .. redoing13:00
admin0RUNNING HANDLER [rabbitmq : Waiting for rabbitmq to start on first node] -- always fails .. known issue or a workaround here to proceed ?13:02
mnasiadkahrw: as long as you don't use services that rely on unbuildable images - I guess you should be fine13:02
mgoddardhrw: need to set nova_compute_virt_type: qemu?13:02
hrwmgoddard: probably.13:02
hrwmnasiadka: yep.13:02
openstackgerritMark Goddard proposed openstack/kolla-ansible master: Ironic: fix documentation  https://review.opendev.org/70682213:05
mgoddardadmin0: probably need to remove an entry from /etc/hosts. Although I thought we had a fix for this13:06
mgoddardadmin0: see https://bugs.launchpad.net/kolla-ansible/+bug/185593513:07
openstackLaunchpad bug 1855935 in kolla-ansible "Kolla-ansible deploy fails at rabbitmq" [Undecided,Incomplete]13:07
devfazmgoddard: I also run into this issue. I fixed it in our branch but not jet upstream!13:07
*** shyamb has quit IRC13:07
devfazadmin0: fyi13:07
devfazadmin0: https://github.com/noris-network/kolla-ansible/commit/3058f601c9b593b7455cc5a383c86270afe2cd2613:08
admin0devfaz, thanks .. so if hostname points to the api interface IP, that is good to go ?13:09
devfazadmin0: correct13:09
admin0done ..rerunning13:10
admin0assuming this is up, what is the process to add more stuff ? just edit in globals file and rerun the bootstrap,precheck and deploy ?13:11
*** sorin-mihai has joined #openstack-kolla13:11
admin0\o/ now i see keystone being configured ..13:11
kplantstuff: more nodes, yes bootstrap them13:11
kplantstuff: mode services, no bootstrap13:11
kplantmore*13:11
admin0but if no new nodes, the same ones, still bootstrap is required ?13:11
kplantno13:11
admin0ok13:12
admin0got it13:12
*** rpittau|bbl is now known as rpittau13:12
kplantmake config changes, deploy13:12
kplantthat should be it13:12
admin0my notes: 1. -  follow the docs, but not apt-get install ansible. Instead pip install 'ansible>2.6' 2. - make sure hostname does not point to loopback, but point to internal ip.13:14
mgoddarddevfaz: would appreciate that commit upstream!13:14
mgoddardand a bug report if possibel13:14
*** vesper11 has quit IRC13:15
*** vesper has joined #openstack-kolla13:15
devfazmogddard: your wish is my command :)13:16
r3ap3radmin0: that is why the docs reccomend doing the the install in a Python Virtual Environment. That way you can "isolate" your Python requirements for Kolla from the requirements of the Host system. ;-)13:18
admin0r3ap3r, with that, i struggled for a whole day . before selecting this non virtualhost one13:19
mgoddardthanks devfaz :)13:19
admin0non virtualenv*13:19
sorin-mihaithat wasn't really clear for me, venv vs system packages, but now i get it. though, are there things that i should install in the host(s) before trying to use kolla-ansible? if yes, where can i see the whole list? when i tried the non-venv method it worked, the venv method had some hick-ups13:20
admin0r3ap3r, https://gist.github.com/a1git/9fc701e4d2aaec41f46499cefe2ede78  --- documentation related to the virtualenv one13:20
*** skramaja has quit IRC13:22
sorin-mihaiadmin0, i assume you're using ubuntu. i'm using centos here, but had same problem. ended up installing docker-ce manually, and then had some other (minor) problems, sort of sorted them afterwards13:24
*** gary_perkins has joined #openstack-kolla13:26
admin0sorin-mihai, i tend to stick to the docs and when the docs not work, complain .. because we know and we can do stuff manually .. but for a first time operator who heard kolla is awesome and wants to us it, he may not be able to get even the basic setup up which is a big putoff13:26
admin0sorin-mihai, did you submitted the fixes ?13:26
sorin-mihaiyeah, same here. doing a clean install now, trying to get everything sorted with venv, as normal user with sudo, will post the findings once done13:28
admin0the deploy failed in nova-cell .. i will run deploy again .. is there a way to tell the script not to re-run keystone etc but start at nova ?13:30
admin0fails on: TASK [service-rabbitmq : nova-cell | Ensure RabbitMQ users exist]  -- * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server13:38
*** dougsz has quit IRC13:38
r3ap3radmin0: I use CentOS 7 for my deployment, haven't tried deploying on Ubuntu yet but plan to try giving it a go now that I have the process down for my CentOS environment. IDK when I will have the time though?13:39
admin0fails on: TASK [service-rabbitmq : nova-cell | Ensure RabbitMQ users exist]  -- * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server13:40
openstackgerritMark Goddard proposed openstack/kayobe master: [ussuri][goal] Drop python 2.7 support and testing  https://review.opendev.org/69561713:42
r3ap3radmin0: you may also want to try "pip install -U kolla-ansible" after doing a normal install. In my experience the normal install only grabs the base Kolla-Ansible version and not any minor version updates. Mayber the Kolla team pushed out a fix for your issues and you just haven't grabbed them yet?13:43
r3ap3radmin0: I mean running that directly after "pip install kolla-ansible". Not after the deployment. ;-)13:44
admin0 i added to the notes13:45
admin0right now , trying to redo the deploy so that it might fix rabbit and allow me to proceed with the installation from where its stuck .. nova-cell13:45
openstackgerritMerged openstack/kayobe stable/rocky: Allow Kayobe to wipe virtualized disks  https://review.opendev.org/70461313:48
*** tony31 has joined #openstack-kolla13:49
*** kplant has quit IRC13:49
*** priteau has joined #openstack-kolla13:50
hrwmnasiadka: if someone has <ussuri with kolla-ceph and does upgrade to ussuri then how to use ceph? the existing one will work as external or does it need to be migrated to some external ceph?13:50
*** kplant has joined #openstack-kolla13:52
*** tony31 has quit IRC13:53
admin0i think its official .. kolla aio train is broken :D13:54
admin0on ubuntu13:54
hrwif you say so...13:54
r3ap3radmin0: why don't you give CentOS a go? After all, Linux is nothing more than a tool, the end goal is to teach in your case. ;-)13:56
admin0https://gist.github.com/a1git/29ad3a1919fbf7b2dae1310ca61eb708 - stuck here again and again13:56
admin0r3ap3r, i have had my fair share of rpm cyclic dependency hell :)13:56
r3ap3rlol13:58
hrwI did aio on debian 10 but with master13:58
openstackgerritMerged openstack/kayobe stable/rocky: Stop running kolla-target-venv in seed hypervisor host upgrade  https://review.opendev.org/70461513:59
admin0for me to give it a try in office and have one kolla-ansible on top of every other openstack-ansible, i have to document it working on a latest release ( train) and then develop some sort of roadmap to test upgrades, updates etc14:00
admin0i can start with rocky/stein if they work out of the box14:00
openstackgerritRadosÅ‚aw Piliszek proposed openstack/kolla-ansible master: CI: Fix deploy guide jobs  https://review.opendev.org/70683414:01
*** dougsz has joined #openstack-kolla14:02
*** rgogunskiy has quit IRC14:06
openstackgerritRadosÅ‚aw Piliszek proposed openstack/kolla-ansible master: CI: Ignore zuul.d  https://review.opendev.org/70683614:07
openstackgerritRadosÅ‚aw Piliszek proposed openstack/kolla-ansible master: CI: Fix deploy guide jobs  https://review.opendev.org/70683414:07
hrwadmin0: so, you got fresh 18.04 system, cloned kolla-ansible stable/train and then deployed all-in-one and it did not worked for you?14:08
hrwadmin0: which distro/install_type images?14:08
admin0distro is ubuntu 18.0414:09
admin0source based installed14:09
hrwok14:10
admin0hrw, my server prep is recorded here: https://asciinema.org/a/ig2c0AOq8xenGdOgzZxf99wNM14:10
yoctozeptoadmin0: looks like rmq is really down or under different address14:10
yoctozeptoadmin0: did you get past that "localhost" being undefined?14:11
yoctozeptoit is really weird14:11
hrwffs... py2/py3 is mess14:12
admin0yes .. hostname should not be mapped to loopback, and i had to remove apt ansible but do pip install ansible>2.6 instead to get past that14:12
openstackgerritMerged openstack/kayobe stable/rocky: Fix use of IPA images in Bifrost without a checksum  https://review.opendev.org/70461914:13
hrwI am waiting for moment when we get c8 working and drop c714:13
hrwthen I plan to hunt for every py2 use and kill it14:13
yoctozeptoadmin0: ah, ansible from apt will not work with venv14:14
admin0its not inside venv14:14
admin0venv gave this issue: https://gist.github.com/a1git/29ad3a1919fbf7b2dae1310ca61eb708 which could not solve14:15
admin0wrong one .. this one : https://gist.github.com/a1git/9fc701e4d2aaec41f46499cefe2ede7814:16
yoctozeptoadmin0: ah, it's a very old ansible :D 2.514:16
yoctozeptoyeah, ansible from apt is just too old14:16
yoctozeptoand the venv problem I could not reproduce14:16
yoctozeptowhatever I did it did the right thing, very weird14:16
yoctozeptoobviously I am doing that one thing differently14:17
yoctozeptojust no idea which14:17
r3ap3rhrw: kill with extreme prejudice right? lol14:18
yoctozeptor3ap3r: berserk mode 8-)14:18
r3ap3rOh yeah!!14:18
hrwr3ap3r: I have to deal with rocky/stain/train/ussuri - each has own 'py2 or py3' issues.14:19
hrwr3ap3r: once ussuri will be c7 free there will be no place for py2 in it.14:19
r3ap3rHeat seekers and all! Grab my BFG from Doom and we should be good! ;-D14:19
hrwr3ap3r: IDKFA/IDDQD and we can work on py2 removal14:19
yoctozeptoyou, you... cheater!14:20
yoctozepto;D14:20
mnasiadkahrw: so, oficially you need to convert to external ceph - which will be a nice challenge14:20
hrwyoctozepto: better cheat was to edit save file to have 65535/65535 ammo so idkfa was more useful14:21
mnasiadkaUnofficially - you can extract keys from kolla-ceph and use them in external ceph mode ;)14:21
r3ap3rhrw: lol14:22
hrwmnasiadka: I will point kevinz to you for docs then ;d14:22
*** vmixor has joined #openstack-kolla14:22
admin0https://asciinema.org/a/bRJ3SMAoqgEMimqF5WA90SmOs    prechecks 2:25 deploy: 3:2014:24
mnasiadkahrw: he'll be delighted - you have a production kolla-ceph deployment?14:27
hrwmnasiadka: more than one14:28
hrwmnasiadka: openstack infra uses two of them14:29
mnasiadkagood one14:29
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: OVN Support  https://review.opendev.org/69684114:31
hrwadmin0: out of luck I am then...14:35
*** sri_ has quit IRC14:35
hrwadmin0: fresh 18.04 VM, kolla-ansible from git stable/train, ansible from pip, ubuntu-source:train images and deployment finished. now initrunonce and ready for vm14:35
openstackgerritIsaac Prior proposed openstack/kayobe master: WIP: Apply sane defaults to Monasca configuration  https://review.opendev.org/70685314:36
admin0if anyone can make me a  setup.sh file that i can just run  and get it up, that would be great14:36
*** zhanglong has quit IRC14:38
hrwadmin0: https://pastebin.com/Z7Qrm8fB can be?14:38
admin0works for me14:38
hrw(vevn3) hrw@ubuntu:~/kolla-ansible$ openstack server list14:39
hrw+--------------------------------------+-------+--------+--------------------+--------+---------+14:39
hrw| ID                                   | Name  | Status | Networks           | Image  | Flavor  |14:39
hrw+--------------------------------------+-------+--------+--------------------+--------+---------+14:39
hrw| e4bed5c1-e1b1-4627-b4d9-d1974a0bdf89 | demo1 | ACTIVE | demo-net=10.0.0.60 | cirros | m1.tiny |14:39
hrw+--------------------------------------+-------+--------+--------------------+--------+---------+14:39
hrwhttps://pastebin.com/cGnVXsLg shows running containers14:41
hrwhttp://paste.ubuntu.com/p/XcfjXgWQHd/ is globals.yml I used (set ubuntu/source/train, defined proper names instead of eth0/eth1, disabled haproxy)14:42
admin0 --configdir $PWD/hrw  -- hrw is globals ?14:42
*** peeejayz has joined #openstack-kolla14:42
hrwadmin0: (vevn3) hrw@ubuntu:~/kolla-ansible$ ls hrw14:43
hrwadmin-openrc.sh  all-in-one  globals.yml  passwords.yml14:43
admin0ok14:43
hrwadmin0: system is VM with two network cards14:44
admin0same as mine14:44
hrwadmin0: I prefer to use directory for all thsoe files instead of keeping them in /etc/kolla/14:45
openstackgerritMerged openstack/kayobe stable/rocky: Fix kayobe overcloud provision without seed in limit  https://review.opendev.org/70461714:46
peeejayzAnyone running Kolla-Ansible in production here?14:46
hrwpeeejayz: who would be so insane??? production can only be run with devstack!14:47
kplantdevstack?? you cowboy14:47
kplantpackstack only14:47
peeejayzoh dear...14:47
kplantpeeejayz: yes, what's up14:47
hrwkplant: venv tarballs!14:48
hrwpacked into rpms!14:48
kplantinside apks so you can run them on android14:48
peeejayzI'm just evaluating it and was wondering how many are running it and how it is after day 014:48
kplantpeeejayz: pretty great14:48
kplantprobably the most flexible thing i've found14:48
peeejayzAny major pitfalls that you'd highlight to stay clear of?14:48
kplantpython sucks14:49
kplantso try to run everything in venvs :-)14:49
kplantthat includes both the ansible host and target machines14:49
peeejayzI've deployed a few clusters, but we are about to go down a new cluster and I'm evaluating what is the current best deployment method14:49
peeejayzoh thats very interesting about the venvs14:49
kplanti also advise grabbing kolla & kolla-ansible from git14:50
kplantnot from pypi14:50
kplanti currently run stable/stein and stable/train in my environment14:50
hrw+1 for 'from git'14:50
kplantjust need to schedule an upgrade of the last site14:50
peeejayzhow large are the clusters your running in it?14:50
hrwwe do releases for pypi but git nearly always has some fixes which are not yet on pypi14:51
kplantpretty mediocre: 1 build, 3 ctl, 2 net, 3 monitoring, N compute14:51
kplanti only need 1 nova-cell (for now) per site14:51
kplantand then i have separate ceph clusters14:51
*** ivve has quit IRC14:51
hrwpeeejayz: no idea, I am just using deployed cloud. And build images to get them deployed.14:51
*** dking_desktop has joined #openstack-kolla14:56
admin0i removed localhost, put it my hostname, mapped it to an interface ip and now redploying15:00
admin0i see how this will never be an issue in multinode setups .15:01
*** sorin-mihai has quit IRC15:02
*** Luzi has quit IRC15:03
*** dougsz has quit IRC15:04
*** TrevorV has joined #openstack-kolla15:04
*** KeithMnemonic has joined #openstack-kolla15:06
openstackgerritMerged openstack/kayobe stable/rocky: Use internal API endpoints in overcloud API interaction  https://review.opendev.org/70462115:12
mnasiadkayoctozepto: https://review.opendev.org/#/c/704309/ - happier now?15:16
patchbotpatch 704309 - kolla-ansible - Remove kolla-ceph - 10 patch sets15:16
*** primeministerp has joined #openstack-kolla15:17
vmixorHi, I have a question about variable naming convention in Kolla-Ansible15:17
vmixorshould I use: audit_notifications_topic_cinder or cinder_audit_notifications_topic15:18
vmixorand15:18
vmixorenable_audit_notifications_cinder or enable_cinder_audit_notifications or cinder_enable_audit_notifications15:19
admin0it has not stuck now .. still running..15:19
mnasiadkavmixor: cinder_audit_notifications_topic and enable_cinder_audit_notifications gets +1 from me, mgoddard yoctozepto hrw osmanlicilegi?15:20
hrwvmixor: COMPONENT_something and enable_COMPONENT_something15:24
osmanlicilegi+1 for mnasiadka15:25
vmixorhrw, mnasiadka, osmanlicilegi: thanks15:25
*** numans_ has quit IRC15:28
admin0still running .. looks like its finally through15:36
admin0so question that went unanswered .. in case deploy fails for any reason, is there a way to pick it up from the role it failed15:38
admin0like --start-at-role --start-at-step etc15:38
admin0say keystone, glance, nova, neutron were OK and it failed at cinder .. how to tell it to restart at cinder and below15:38
admin0so that time is not wasted redoing keystone .. neutron15:39
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: WIP: CI: Add CentOS 8 ceph-ansible job  https://review.opendev.org/70688615:41
*** sorin-mihai has joined #openstack-kolla15:41
hrwadmin0: as you may seen in my script I just restart everything. but that makes sense with all-in-one setups only iirc15:43
admin0so this feature is not there yet ?15:44
admin0is there a way to make a feature requst ? is it via git issues ?15:44
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: OVN Support  https://review.opendev.org/69684115:44
mnasiadkaadmin0: launchpad.net/kolla-ansible15:44
*** dougsz has joined #openstack-kolla15:45
admin0https://bugs.launchpad.net/kolla-ansible/+bug/1862649  -- hopefully the details is enough15:51
openstackLaunchpad bug 1862649 in kolla-ansible "kolla-ansible start at a particular task " [Undecided,New]15:51
*** carli has quit IRC15:56
openstackgerritMark Goddard proposed openstack/kayobe master: [ussuri][goal] Drop python 2.7 support and testing  https://review.opendev.org/69561715:57
*** Trevor_V has joined #openstack-kolla16:02
*** TrevorV has quit IRC16:06
admin0i thought it was working .. but during openvswitch , the network went down ( i was doing it via ssh) .. so have to login to the system using console and check again :D16:06
admin0i forgot to tmux this time16:06
admin0but i think the setup/packages issues are gone16:06
*** pbing19 has quit IRC16:09
*** bengates has quit IRC16:29
*** bengates has joined #openstack-kolla16:30
*** bengates has quit IRC16:35
mgoddardadmin0: sounds like openvswitch swallowed your IP16:49
mgoddardadmin0: neutron_external_interface can't have an IP16:49
mgoddardbecause it gets plugged into an OVS bridge16:49
*** priteau has quit IRC16:56
*** rpittau is now known as rpittau|afk17:07
*** peeejayz has quit IRC17:17
openstackgerritMerged openstack/kolla-ansible master: Docs: fix cells upgrade guide  https://review.opendev.org/70666917:25
*** pbing19 has joined #openstack-kolla17:25
jopdorphi!17:26
jopdorpanyone know about ceilometer deployment failures related to gnocchiclient.exceptions.NotFound17:26
jopdorp?17:26
admin0;)17:32
admin0i have to redo-restart17:32
admin0which is OK17:32
openstackgerritMark Goddard proposed openstack/kolla-ansible stable/train: Docs: fix cells upgrade guide  https://review.opendev.org/70691717:32
admin0so quick question .. if everything kolla can setup is enabled , in an aio, how big of a resource would it need ?17:33
*** evrardjp has quit IRC17:34
*** evrardjp has joined #openstack-kolla17:34
jopdorphttps://pastebin.com/f5zVjAY017:38
jopdorpthat is my /var/log/kolla/ceilometer/ceilometer-upgrade.log17:38
*** k_mouza has quit IRC17:39
jopdorpany idea about that deployment failure?17:40
openstackgerritMark Goddard proposed openstack/kayobe master: WIP: Allow OVS bridges to connect directly to interface  https://review.opendev.org/70503717:41
jopdorpit fails at step "ceilometer : Running Ceilometer bootstrap container"17:43
*** jopdorp has quit IRC17:53
*** gfidente is now known as gfidente|afk17:55
*** openstackstatus has quit IRC17:57
*** openstack has joined #openstack-kolla18:00
*** ChanServ sets mode: +o openstack18:00
openstackgerritJames Kirsch proposed openstack/kolla-ansible master: Construct service configuration urls using kolla_internal_fqdn  https://review.opendev.org/70662718:24
openstackgerritMerged openstack/kayobe stable/rocky: Don't list tasks for config dump  https://review.opendev.org/70461118:28
openstackgerritViktor Michalek proposed openstack/kolla-ansible master: Adds support of CADF notifying for other APIs next to keystone.  https://review.opendev.org/67457918:36
*** dcapone2004 has joined #openstack-kolla18:40
dking_desktopLooking at ironic-dnsmasq.conf.j2, I noticed that the tftp options use api_interface_address. Is that generally useful? Isn't that typically going to be on a different network/VLAN than the baremetal servers are accessing during boot?18:44
*** vedup19 has joined #openstack-kolla18:46
*** pbing19 has quit IRC18:48
*** jopdorp has joined #openstack-kolla18:49
yoctozeptodking_desktop: I had similar suspicions when doing ipv6, but I think there is one more place this would need to change - the tftp server itself18:49
dking_desktopThe tftp server seems to listen on 0.0.0.0, so if it had the right IP to reach it, then it seems to me that it should be fine.18:50
yoctozeptodking_desktop: and it would have to be routable anyway18:51
dking_desktopYes, it would. ironic-pxe.json.j2 has "/usr/sbin/in.tftpd --verbose --foreground --user root --address 0.0.0.0:69 ...". I was able to reach it by putting in the IP of my controller. So, I can reach it that way, but just not over the separate internal api vlan.18:54
dking_desktopI was wondering what is commonly done, and if it might be better to allow that IP to be set separately.18:55
openstackgerritMerged openstack/kolla-ansible master: Add --clean to kolla-mergepwd  https://review.opendev.org/70666819:00
yoctozeptomgoddard could help ^19:03
*** vedup19 has quit IRC19:12
*** reph has joined #openstack-kolla19:21
dking_desktopI've heard that most people in here are in Europe, and it's late there.19:34
*** igordc has joined #openstack-kolla19:35
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: WIP: CI: Add CentOS 8 ceph-ansible job  https://review.opendev.org/70688619:37
openstackgerritDincer Celik proposed openstack/kolla stable/rocky: Fixes fluentd for rocky  https://review.opendev.org/70671319:42
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: OVN Support  https://review.opendev.org/69684119:44
openstackgerritDincer Celik proposed openstack/kolla stable/rocky: Fixes fluentd for rocky  https://review.opendev.org/70671319:45
*** numans has joined #openstack-kolla19:48
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: Remove kolla-ceph  https://review.opendev.org/70430919:48
*** igordc has quit IRC19:53
*** reph has quit IRC19:54
*** umbSublime has joined #openstack-kolla19:55
*** jopdorp has quit IRC19:55
openstackgerritMerged openstack/kolla-ansible stable/train: Docs: fix cells upgrade guide  https://review.opendev.org/70691720:01
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: WIP: CI: Add CentOS 8 ceph-ansible job  https://review.opendev.org/70688620:04
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: Tidy up tools/ subdirectory  https://review.opendev.org/70649620:10
yoctozeptodking_desktop: yeah, I am one of those "people in Europe" ;-)20:14
kplantpeople live there?20:15
kplantgross20:15
*** cah_link has quit IRC20:24
*** cah_link has joined #openstack-kolla20:24
yoctozeptokplant: yeah, happens20:30
kplanthow do you function without an orange emperor?20:34
*** kplant has quit IRC20:45
admin0here in NL we have the church of flying spaghetti monster  to guide us21:19
hrwlooks like first all-in-one using infra images will be deployed ;D21:26
openstackgerritMarcin Juszkiewicz proposed openstack/kolla master: WIP: Create 'infra' type of images  https://review.opendev.org/69875321:46
openstackgerritMarcin Juszkiewicz proposed openstack/kolla-ansible master: WIP: Use 'infra' type of images  https://review.opendev.org/70698221:46
hrwmaybe their dependencies should be done in reverse21:46
hrwor k-a part gets build of images enabled21:46
hrwhttps://pastebin.com/CM76qD7N - created VM in infra type deployment21:47
* hrw off21:52
dking_desktopyoctozepto, mgoddard: There's also 'ironic_inspector_internal_fqdn: "{{ kolla_internal_fqdn }}"' in group_vars/all.yml22:07
*** vmixor has quit IRC22:09
*** k_mouza has joined #openstack-kolla22:16
*** k_mouza has quit IRC22:20
*** cah_link has quit IRC22:33
*** openstackgerrit has quit IRC22:46
*** Trevor_V has quit IRC22:56
*** jaicaa has quit IRC23:47
*** jaicaa has joined #openstack-kolla23:48
*** iniazi_ has joined #openstack-kolla23:53
*** iniazi has quit IRC23:55
*** openstackgerrit has joined #openstack-kolla23:59
openstackgerritJames Kirsch proposed openstack/kolla-ansible master: Add support for encrypting backend HAProxy traffic  https://review.opendev.org/66451623:59

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