Tuesday, 2020-05-26

*** born2bake has quit IRC00:21
*** wuchunyang has joined #openstack-kolla01:02
*** cah_link1 has joined #openstack-kolla01:07
*** cah_link has quit IRC01:08
*** cah_link1 is now known as cah_link01:08
*** wuchunyang has quit IRC01:11
*** wuchunyang has joined #openstack-kolla01:12
*** wuchunyang has quit IRC01:16
*** Torel has joined #openstack-kolla01:35
*** Torel has quit IRC01:42
*** Torel has joined #openstack-kolla02:46
*** Wuchunyang1 has joined #openstack-kolla02:51
*** Torel has quit IRC02:51
*** Wuchunyang1 has quit IRC02:52
*** wuchunyang has joined #openstack-kolla02:53
*** wuchunyang has quit IRC02:59
*** hongbin has joined #openstack-kolla03:08
*** hongbin has quit IRC03:28
*** vishalmanchanda has joined #openstack-kolla03:35
*** ykarel|away is now known as ykarel03:35
*** ykarel is now known as ykarel|afk03:54
*** evrardjp has quit IRC04:33
*** evrardjp has joined #openstack-kolla04:33
*** threestrands has joined #openstack-kolla04:40
*** Torel has joined #openstack-kolla04:58
*** skramaja has joined #openstack-kolla05:05
*** cah_link has quit IRC05:18
*** ykarel|afk is now known as ykarel05:25
*** cah_link has joined #openstack-kolla05:46
*** hjensas__ has quit IRC06:14
sorin-mihai_trying to deploy monasca i see https://pastebin.com/raw/rc7dkDFX and i noticed that the monasca-log-api keeps failing when i run kolla-build. is this some sort of bug or it just on my system?06:31
yoctozeptor3ap3r: yes, you could limit this to nova-compute as well06:50
yoctozeptosorin-mihai_: ussuri? it's gone; patch is in progress06:50
*** ricolin_ has joined #openstack-kolla06:52
*** ricolin_ has quit IRC06:54
sorin-mihai_i guess if i force building the images from master tarballs it's some sort of victoria? but anyway, thanks06:54
yoctozeptosorin-mihai_: ah, yeah, it is victoria already, just nothing has happened in victoria obviously ;p06:55
yoctozeptoor "not so much"06:55
mnasiadkamorning07:01
bjolo_morning07:02
*** hjensas has joined #openstack-kolla07:12
*** dougsz has joined #openstack-kolla07:16
*** e0ne has joined #openstack-kolla07:21
*** amoralej|off is now known as amoralej07:27
openstackgerritChristian Berendt proposed openstack/kolla-cli master: README: add deprecation note  https://review.opendev.org/73045207:36
*** openstackstatus has quit IRC07:39
*** openstackstatus has joined #openstack-kolla07:40
*** ChanServ sets mode: +v openstackstatus07:40
*** srin has joined #openstack-kolla07:41
*** zijlboot_ has joined #openstack-kolla07:43
*** vishalmanchanda has quit IRC07:44
*** zijlboot has quit IRC07:46
openstackgerritRadosław Piliszek proposed openstack/kolla-cli master: README: add deprecation note  https://review.opendev.org/73045207:46
*** rpittau|afk is now known as rpittau07:46
*** shyamb has joined #openstack-kolla07:49
*** dougsz has quit IRC07:55
*** JangwonLee has joined #openstack-kolla08:04
*** born2bake has joined #openstack-kolla08:05
*** shyamb has quit IRC08:12
*** jbadiapa has joined #openstack-kolla08:17
*** Tony31 has joined #openstack-kolla08:29
Tony31Hello Openstack-Kolla, how is everyone? Hope you are all keeping safe and well ?08:30
*** sorin-mihai_ has quit IRC08:32
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: Initial jinja2 templates syntax checks  https://review.opendev.org/72889408:37
*** ykarel is now known as ykarel|lunch08:44
Tony31May I clarify with you with regards to flat external networks / VLAN nets? After deployment I have physnet1 and physnet2. Physnet2 is the external data network from the network nodes. How would I go about configuring a physnet3? The use case is deploying an openstack VM and giving it direct network access through the compute node.08:52
Tony31Is there a guide on this topic?08:53
*** priteau has joined #openstack-kolla08:54
*** k_mouza has joined #openstack-kolla09:02
openstackgerritMerged openstack/kolla master: Revert "Update OPENSTACK_RELEASE to ussuri"  https://review.opendev.org/73052209:04
*** shyamb has joined #openstack-kolla09:07
openstackgerritMerged openstack/kolla master: Revert "Switch to Ussuri release tarballs for vmware-nsx*"  https://review.opendev.org/73052109:16
openstackgerritMerged openstack/kolla master: Revert "Switch to Ussuri release of ovn-octavia-provider source tarball"  https://review.opendev.org/73052009:16
openstackgerritMerged openstack/kolla master: Revert "Switch to tarballs.opendev.org for source images"  https://review.opendev.org/73052509:16
openstackgerritMerged openstack/kolla master: Revert "Switch to versioned tarballs part 2"  https://review.opendev.org/73052609:16
openstackgerritMerged openstack/kolla master: Revert "Switch to Ussuri release tarballs"  https://review.opendev.org/73052309:16
*** shyam89 has joined #openstack-kolla09:23
*** shyamb has quit IRC09:26
*** gfidente|afk is now known as gfidente09:30
*** ykarel|lunch is now known as ykarel09:51
*** Tony31 has quit IRC09:59
*** shyam89 has quit IRC09:59
*** Torel has quit IRC09:59
*** Torel has joined #openstack-kolla10:00
*** shyamb has joined #openstack-kolla10:02
*** threestrands has quit IRC10:05
*** e0ne has quit IRC10:16
*** e0ne has joined #openstack-kolla10:17
*** e0ne has quit IRC10:18
*** rpittau is now known as rpittau|bbl10:20
*** e0ne has joined #openstack-kolla10:21
*** e0ne has quit IRC10:22
*** vishalmanchanda has joined #openstack-kolla10:23
*** e0ne has joined #openstack-kolla10:24
*** priteau has quit IRC10:35
*** Torel has quit IRC10:37
*** simplyolaf has joined #openstack-kolla10:43
simplyolafGood morning! I have tried to do a fresh install of Kolla, all-in-one, with the openstack-train release. I am not able to get it to work. I came across a few errors:1. Errors importing queue , when running the openstack client. queue is named with lower case in python 3.  Fix was to change affected imports to import Queue. Problem solved2. After10:44
*** Fl1nt has joined #openstack-kolla10:44
simplyolafsetting everything up including the demo network, router shows interfaces for private network and for public network as downI can see errors in /var/log/kolla/neutron/neutron-l3-agent.log:2020-05-23 00:22:12.862 17 ERROR neutron.agent.l3.agent [-] Failed to process compatible router: 19b4e5ca-73f7-4c72-84be-5f4c6bc3060f: NetlinkError: (101,10:44
Fl1ntHi everyone!10:45
simplyolafNetwork is unreachable')2020-05-23 00:22:12.862 17 ERROR neutron.agent.l3.agent Traceback (most recent call last):3. On the startup of neutron-server container I saw the following error: ++ /usr/bin/update-alternatives --query iptables/usr/local/bin/kolla_extend_start: line 11: /usr/bin/update-alternatives: No such file or directory++ .10:45
simplyolafsimplyolaf/usr/local/bin/kolla_neutron_extend_startFor reference I setup my globals.yml in the following way:network_interface: "aggi"keepalived_virtual_router_id: “101”kolla_internal_vip_address: "10.143.3.148"kolla_external_vip_address: "10.143.3.149”neutron_external_interface: "agge"aggi is my private network interface and agge is my10:45
simplyolafexternal10:45
simplyolafplease see this link for my specific problem which I am trying to solve10:46
simplyolafhttps://ask.openstack.org/en/question/127787/ansible-kolla-unable-to-access-external-networks-gateway/10:46
*** shyamb has quit IRC10:50
Fl1nt@simplyolaf, hey, did you installed your platform using OVS or LinuxBridge?10:56
*** also_stingrayza has joined #openstack-kolla10:56
*** stingrayza has quit IRC10:59
simplyolafI left the defaults so I think it was using OVS11:02
simplyolafI changed the following settings in globals.yml:11:02
simplyolafnetwork_interface: "aggi"11:02
simplyolafkeepalived_virtual_router_id: “101”11:02
simplyolafkolla_internal_vip_address: "10.143.3.148"11:02
simplyolafkolla_external_vip_address: "10.143.3.149”11:03
simplyolafneutron_external_interface: "agge"11:03
simplyolafkolla_install_type: "source"11:03
Fl1ntyour nic interface is named agge???11:03
*** simplyolaf has quit IRC11:04
Fl1ntand aggi ? which kind of nic are they? vlan? Team? bond? vnic?11:04
*** shyamb has joined #openstack-kolla11:04
*** simplyolaf has joined #openstack-kolla11:07
simplyolafagge is the name of the external interface11:07
simplyolafwith public internet access11:08
simplyolafit is called that because it is an aggregated interface with bonding11:08
Fl1ntis this interface handled by OVS ? Is this interface having an IP?11:08
Fl1ntIf it have an IP, it shouldn't.11:09
Fl1ntwhen handled by OVS11:09
Fl1nthas the agent will actually deal it.11:09
Fl1ntand last thing is, how did you created the external network? using flat type or something else?11:09
simplyolafafter the install it doesn't have an ip. BUt I assigned an ip to br-ex so I have internet access11:10
simplyolafusing flat type11:10
mnasiadkaand that Neutron log snippet isn't helping in anything11:10
simplyolafthat's all I can find in the logs11:10
mnasiadkasimplyolaf: can you post some next lines of the Neutron log with error on paste.openstack.org?11:10
simplyolaflok11:11
simplyolafok11:11
Fl1ntyou don't have to assign IP to the br-ex neither11:11
mnasiadkait's Ubuntu, right?11:11
simplyolafCentos11:12
simplyolaf2020-05-23 00:21:45.816 17 INFO neutron.agent.l3.agent [-] Starting router update for 19b4e5ca-73f7-4c72-84be-5f4c6bc3060f, action 3, priority 2, update_id b45496ac-0224-4b14-be8f-444e36def40f. Wait time elapsed: 7.2072020-05-23 00:21:46.929 17 INFO neutron.agent.linux.interface [-] Device qg-c9268f44-17 already exists2020-05-23 00:21:48.173 1711:12
simplyolafERROR neutron.agent.l3.router_info [-] (101, 'Network is unreachable'): NetlinkError: (101, 'Network is unreachable')2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info Traceback (most recent call last):2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info   File11:12
simplyolaf"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/common/utils.py", line 166, in call2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info     return func(*args, **kwargs)2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info   File "/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/l3/router_info.py", line 1218,11:12
simplyolafin process2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info     self.process_external()2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info   File "/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/l3/router_info.py", line 983, in process_external2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info11:12
simplyolafself._process_external_gateway(ex_gw_port)2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info   File "/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/l3/router_info.py", line 865, in _process_external_gateway2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info     self.external_gateway_added(ex_gw_port,11:12
simplyolafinterface_name)2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info   File "/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/l3/router_info.py", line 816, in external_gateway_added2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info     ex_gw_port, interface_name, self.ns_name, preserve_ips)2020-05-23 00:21:48.173 1711:12
simplyolafERROR neutron.agent.l3.router_info   File "/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/l3/router_info.py", line 793, in _external_gateway_added2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info     device.route.add_gateway(ip)2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info   File11:12
simplyolaf"/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/ip_lib.py", line 594, in add_gateway2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info     scope=scope)2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info   File "/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/ip_lib.py", line 632, in11:12
simplyolafadd_route2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info     table=table, metric=metric, scope=scope, **kwargs)2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info   File "/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/ip_lib.py", line 1473, in add_ip_route2020-05-23 00:21:48.173 17 ERROR11:12
simplyolafneutron.agent.l3.router_info     metric=metric, scope=scope, **kwargs)2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info   File "/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/privileged/agent/linux/ip_lib.py", line 53, in sync_inner2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info     return input_func(*args,11:12
simplyolaf**kwargs)2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info   File "/var/lib/kolla/venv/lib/python2.7/site-packages/oslo_privsep/priv_context.py", line 245, in _wrap2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info     return self.channel.remote_call(name, args, kwargs)2020-05-23 00:21:48.173 17 ERROR11:12
simplyolafneutron.agent.l3.router_info   File "/var/lib/kolla/venv/lib/python2.7/site-packages/oslo_privsep/daemon.py", line 204, in remote_call2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info     raise exc_type(*result[2])2020-05-23 00:21:48.173 17 ERROR neutron.agent.l3.router_info NetlinkError: (101, 'Network is unreachable')2020-05-2311:12
simplyolaf00:21:48.173 17 ERROR neutron.agent.l3.router_info11:12
mnasiadkasimplyolaf: paste.openstack.org - not here!11:12
simplyolafright11:12
simplyolafsorry11:12
mnasiadkadon't flood the channel with your logs or configs... please.11:13
simplyolafOk still new11:14
simplyolafhttp://paste.openstack.org/show/793983/11:14
Fl1ntso you're using a linux bridge.11:15
mnasiadkawell, something is surely wrong with your network setup, if it can't add route...11:15
mnasiadkaFl1nt: and from where do you reckon that?11:16
Fl1nt@mnasiadka, "/var/lib/kolla/venv/lib/python2.7/site-packages/neutron/agent/linux/ip_lib.py" <- from there, this is not the ovs_agent that is called.11:16
simplyolafbut surely whatever it is trying to use, it would be limited to the options I pick in globals.yml?11:18
Fl1ntdepends on how you setup your globals.yml but yeah, if you didn't requested to use neutron_ovs_agent and openvswitch usage you're using linux bridge.11:19
Fl1ntbut as I always work/use OVS I can't really help in here sorry .11:19
mnasiadkaFl1nt: I'm sorry, but you're wrong.11:19
simplyolafI want to use OVS as well11:21
simplyolafwhich options do I pick then in globals.yml11:21
simplyolafso I am sure it is using OVS11:21
mnasiadkasimplyolaf: if you haven't enabled linuxbridge - it's openvswitch11:22
mnasiadkasimplyolaf: just run docker ps | grep openvswitch11:22
simplyolafI see three jobs running11:22
simplyolafthree containers11:23
simplyolafneutron_openvswitch_agent11:23
simplyolafopenvswitch_vswitchd11:23
simplyolafopenvswitch_db11:23
Fl1nt@mnasiadka, yep, you're right sorry, mixed up things.11:23
simplyolafIn a similar machine I was able to do a setup of packstack RDO11:24
simplyolafit worked11:24
Fl1nt@simplyolaf, just to be sure, what's the value of the neutron_plugin_agent variable within your globals.yml?11:25
simplyolaf# Valid options are [ openvswitch, linuxbridge, vmware_nsxv, vmware_nsxv3, vmware_dvs, opendaylight ]# if vmware_nsxv3 is selected, enable_openvswitch MUST be set to "no" (default is yes)#neutron_plugin_agent: "openvswitch"11:27
Fl1ntok, fine11:27
Fl1ntand so you get a neutron network mapping configuration with agge:physnet1 right?11:28
simplyolafyes11:30
simplyolafhttp://paste.openstack.org/show/793985/11:30
simplyolafthe link above shows the configuration of the public network I created11:31
simplyolafusing physnet111:31
simplyolafas you can see in globals.yml agge is the network I provided for neutron11:32
Fl1nthum, you didn't provided this network a range yep?11:32
Fl1nthow did you provided an IP to you br-ex ?11:32
Fl1nt-yep+yet11:32
simplyolafI created a network-script11:33
simplyolaflet me paste it11:33
simplyolafone sec11:33
simplyolafhttp://paste.openstack.org/show/793986/11:35
Fl1ntdon't get why you assign an IP to the br-ex bridge.11:36
Fl1ntyou don't need to do that. Or I missed something.11:37
*** wuchunyang has joined #openstack-kolla11:40
*** wuchunya_ has joined #openstack-kolla11:40
Fl1ntyou'll be able to specify all of that at the network/subnet creation doing that is prohibiting you to attach any new external/provider networks to your bridge.11:41
Fl1ntno need to specify that your bond is OVS managed neither, are you mixing system-wide OVS installation with the OVS containers from kolla?11:42
simplyolafI need to keep internet access11:49
simplyolafas the agge interface is the only one with internet access11:49
simplyolafso I assigned an ip address to it. I had done the same thing when I did the packstack install11:49
simplyolafIf that is not the right place to put the scripts, where can I put them?>11:49
Fl1ntbasically, no need for scripts11:50
Fl1ntkolla/ovs is taking care of that.11:50
Fl1ntwhat I'm having a hard time to get is your internet requirement.11:50
simplyolafthe server itself loses connectivity to the internet11:51
simplyolafafter running the install11:51
simplyolafi have two network interfaces but only one has internet access11:51
Fl1nthold on, your node is directly connected to your internet router?11:51
simplyolafI am testing an all in one install in a server with direct internet access via a gateway11:52
simplyolafit is not my local computer11:52
*** shyamb has quit IRC11:52
Fl1ntin that case you'll need a bond between both nic, then create upper vnic and assign those upper vnic to external bridge.11:52
*** e0ne has quit IRC11:57
*** e0ne_ has joined #openstack-kolla11:57
Fl1nt@simplyolaf, did you created a subnet for this network?11:57
simplyolafyes11:58
simplyolafhttps://pasteboard.co/Ja9zcTk.png11:58
simplyolafabove is a screenshot of the network interface attached to the router for the external gateway11:58
simplyolafThis is from the ansible kolla setup11:58
simplyolafI am going to also show the same thing but from the Packstack RDO which worked11:58
Fl1ntno I mean, the external network, does it have a subnet?11:58
simplyolafit does11:58
simplyolafhttps://pasteboard.co/Ja9zZlO.png11:59
Fl1ntok, that's a subnet of only 1 fixed IP. what's the gateway IP that you assigned to this subnet?11:59
*** wuchunya_ has quit IRC12:01
simplyolafit has 3 ips12:01
simplyolafpublic1-subnet 142.91.120.240/2812:01
simplyolafthe gw ip is set to 142.91.120.18712:02
simplyolafwhich is the same as for the server12:02
Fl1ntyou can't do that12:02
Fl1ntyour gateway have to be the br-ex addr if you assign an addr to the bridge12:03
Fl1ntand you can't use that IP addr and gateway IP from within the available subnet CIDR.12:03
Fl1ntor you gonna mess your routing.12:03
Fl1ntso your subnet gateway addr should be 140.91.120.10012:04
simplyolafthe public network should be setup with the real external gateway right?12:06
simplyolafand only the router will have a gateway setup with a diffferent ip, differnt from the real gateway12:07
simplyolaf?12:07
Fl1ntnope, you can't, your neutron router won't be able to contact it.12:07
Fl1ntFirst thing first, do you want to create a network that will be directly used by your VMs or through a neutron router?12:10
simplyolafI don't want to give direct access to the external network12:10
simplyolafI want the vms to go through the router12:10
Fl1ntok, and your VMs will have an IP assigned within this public range right?12:11
simplyolafno just private ips.12:12
simplyolafI might give them floating ip addresses12:12
simplyolafbut the vms will not even know it12:13
Fl1ntok12:13
Fl1ntso12:13
Fl1ntyour router connecting from your private network to the public network should have an IP addr and a gateway which is your network bridge address.12:15
Fl1ntsomething like 140.91.120.247 gw 140.91.120.10012:15
Fl1ntbecause, if you don't do that, how is your router supposed to know where to send your packet?12:17
simplyolafnetwork bridge address?12:18
*** k_mouza_ has joined #openstack-kolla12:19
simplyolafyou mean the ip address assgined to br-ex12:20
Fl1ntyes12:20
Fl1ntyou should have a look at neutron's router namespaces created on your host, you'll get a clearer understanding at why a router can't directly talk to your gateway.12:21
*** rpittau|bbl is now known as rpittau12:22
Fl1ntalso, be aware that by default routers are doing SNAT12:22
*** k_mouza has quit IRC12:22
*** ykarel is now known as ykarel|afk12:23
simplyolafI tried the exact same setup with packstack RDO, I assigned the real gateway to the public network and I was able to get it to work12:24
Fl1ntI don't know how is packstack doing stuff, so can't really compare sorry.12:24
simplyolafI see in https://pasteboard.co/Ja9zcTk.png ovs_hybrid_plug set to true12:25
simplyolafany idea what that means?12:25
simplyolafwhen comparing it to the version of openstack that works(not kolla)12:26
simplyolafhttps://pasteboard.co/Ja9L0Li.png12:26
simplyolafdifferences that I notice between the two. connectivity and that attribute12:27
*** amoralej is now known as amoralej|lunch12:28
Fl1ntthat it to let API services to know that OVS agent will have to create firewall bridge (linuxbridge <-> ovs) thing, hence why I asked if you installed OVS using the system packages on this machine and thought you where using a linux bridge, there is something wrong on your setup, if you're fully using kolla containerized OVS you should have such thing.12:31
Fl1ntshouldn't have such thing.12:32
Fl1ntsorry12:32
*** wuchunyang has quit IRC12:32
Fl1ntcan you compare both network type on packstack and your kolla installationt too ?12:33
*** wuchunyang has joined #openstack-kolla12:33
Fl1ntyour kolla is a provider network, how is your packstack network?12:33
simplyolafhttp://paste.openstack.org/show/793991/12:36
simplyolafI think this will give you an answer of my setup for packstack12:36
*** wuchunyang has quit IRC12:37
simplyolafIn Kolla, I set enable_neutron_provider_networks: "yes"12:38
Fl1ntnope, that doesn't answer my question as I don't know if your network is set as a provider network within your packstack installation.12:38
simplyolafSorry I think my knowledge is a bit limited12:39
Fl1ntDon't worry12:39
simplyolafI can see in my kolla globals.yml #neutron_plugin_agent: "openvswitch"12:39
simplyolafso it should still be using that as the default12:39
Fl1nthold on, one thing after the other.12:40
simplyolafok12:40
Fl1ntfirst, goes within your packstack network named external_network and retrieve the informations to know which type of network it is.12:41
*** cah_link has quit IRC12:41
simplyolafhttps://pasteboard.co/Ja9Rc3v.png12:41
Fl1ntok, that's what I thought, your packstack is declaring your network as an external network but not a provider network.12:44
simplyolafok12:44
Fl1ntwhere your kolla is declaring it as a provider network12:44
simplyolaflet me double check12:44
Fl1ntsure12:44
*** dave-mccowan has joined #openstack-kolla12:45
simplyolafhttps://pasteboard.co/Ja9SJTF.png12:45
simplyolafthat's for kolla12:45
Fl1nthum, could you get the info from the cli?12:46
simplyolafwhat's the command12:46
*** rgogunskiy has joined #openstack-kolla12:48
simplyolafhttp://paste.openstack.org/show/793992/12:50
simplyolafI got I think12:50
*** ricolin has quit IRC12:51
Fl1ntok,and now do the same with packstack12:52
simplyolafpackstack: http://paste.openstack.org/show/793994/12:52
Fl1nthum... I'm out of ideas12:53
Fl1ntis packstack using the same br-ex with an assigned IP ?12:54
simplyolafI setup the same thing I did for kolla12:54
simplyolafI assigned an ip address12:54
simplyolafI am using train release of kolla12:54
simplyolafand packstack is using stein release12:54
*** ricolin has joined #openstack-kolla12:55
*** ricolin_ has joined #openstack-kolla12:55
simplyolafI can alwasy try another release and hope I am lucky?12:55
*** ricolin_ has quit IRC12:55
Fl1ntI don't think it's coming from the release12:55
Fl1ntI'm using rocky and train, both are using external without any issue.12:56
openstackgerritPiotr Kopec proposed openstack/kolla stable/train: nova-compute: add ndctl to expose NVDIMMs to guests  https://review.opendev.org/73078712:56
Fl1ntthe main difference is my bridge don't get an IP assigned12:56
simplyolaf I see12:56
simplyolafI did a previous setup without messing around with the bridge12:57
simplyolafand it was the same result12:57
Fl1nton a side note, my bridges are also fully managed by kolla, and don't get anything prepared in advance.12:58
simplyolafa major difference for packstack. It is using the same interface for all12:59
Fl1ntwhat do you mean?12:59
simplyolafit is not using the internal interface aggi12:59
simplyolafmaybe i can just give it agge for network_interface and neutron_network_interface?12:59
Fl1ntthat should make difference as you get br-tun connecting everything in between.13:00
simplyolafYou mean make no difference?13:00
Fl1ntif you set network_interface = agge no need to specify neutron_* as it will fallback to network_interface if not set.13:00
*** ykarel|afk is now known as ykarel13:01
simplyolafok13:01
simplyolafI will try the setup that way13:01
Fl1ntI mean if you use aggi for br-tun and agge for br-ex you should have a br-int bridge that get a patch interface on each of them connecting them.13:01
simplyolafand see what I get13:01
Fl1ntalso13:02
Fl1ntdisable neutron_enable_provider_network if you're not doing DVR13:02
simplyolafDVR?13:02
Fl1ntDistributed routing13:03
Fl1ntbut as you're using an all-in-one installation, don't mind about that now13:04
simplyolafok13:04
Fl1ntit's a way to get vm-to-vm traffic to be direct and not going back and forth using the network node.13:04
*** wuchunyang has joined #openstack-kolla13:06
simplyolafok13:15
openstackgerritWill Szumski proposed openstack/kayobe master: Add ability to run playbooks before and after a kayobe command  https://review.opendev.org/72481813:16
*** amoralej|lunch is now known as amoralej13:18
*** ykarel is now known as ykarel|afk13:24
*** JamesBenson has joined #openstack-kolla13:42
openstackgerritPierre Riteau proposed openstack/kolla stable/train: Fix release note formatting by removing extra backtick  https://review.opendev.org/73082113:45
*** jcmdln has quit IRC13:47
*** yoctozepto8 has joined #openstack-kolla14:00
*** yoctozepto has quit IRC14:01
*** yoctozepto8 is now known as yoctozepto14:01
*** TrevorV has joined #openstack-kolla14:08
*** rpittau is now known as rpittau|brb14:10
*** srin has quit IRC14:17
openstackgerritMerged openstack/kolla stable/train: Fix release note formatting by removing extra backtick  https://review.opendev.org/73082114:17
*** amoralej is now known as amoralej|brb14:17
*** ykarel|afk is now known as ykarel14:21
*** jcmdln has joined #openstack-kolla14:30
*** rpittau|brb is now known as rpittau14:39
*** amoralej|brb is now known as amoralej14:50
r3ap3ryoctozepto: thanks for the reply, sorry, it has been a crazy morning. That nova.conf didn't appear to be there? All I could find yesterday was the nova.conf.j2 file which seemed to be similar however it didn't have the `cpu_mode` option from what I can remember? I'll try taking another peek this afternoon, thanks.14:51
*** stingrayza has joined #openstack-kolla14:52
*** also_stingrayza has quit IRC14:55
*** cah_link has joined #openstack-kolla14:56
*** jcmdln has quit IRC14:59
openstackgerritSebastian Luna-Valero proposed openstack/kayobe master: Fix encoding of subprocess output  https://review.opendev.org/73084215:00
*** seco has joined #openstack-kolla15:01
*** jcmdln has joined #openstack-kolla15:04
*** seco has quit IRC15:11
*** ysirndjuro has quit IRC15:17
*** e0ne_ has quit IRC15:17
*** ysirndjuro has joined #openstack-kolla15:18
*** e0ne has joined #openstack-kolla15:21
openstackgerritMichal Nasiadka proposed openstack/kayobe master: WIP: Test vault functionality in kayobe on CI runs  https://review.opendev.org/73085515:29
*** priteau has joined #openstack-kolla15:34
*** skramaja has quit IRC15:35
openstackgerritMerged openstack/kolla-cli master: README: add deprecation note  https://review.opendev.org/73045215:39
openstackgerritRadosław Piliszek proposed openstack/kolla-cli stable/ussuri: README: add deprecation note  https://review.opendev.org/73085815:40
priteauI see in Train release notes: urls should be constructed using the {{ internal_protocol }} and {{ external_protocol }} configuration parameters15:40
priteauYet, there is only two occurrences of external_protocol: this release note and a comment15:41
yoctozeptopriteau: sounds like an oopsie :D15:41
priteauShould we s/external_protocol/public_protocol15:42
yoctozeptopriteau: yes15:42
priteauping headphoneJames15:42
yoctozeptowell, this sounds like a note to contributors15:43
priteauNot necessarily. A deployer can customise endpoint URLs via globals.yml (I do)15:45
yoctozeptopriteau: ah, but you are an advanced user :-)15:48
yoctozeptolet's say powerusers :D15:48
*** rpittau is now known as rpittau|afk15:51
*** ykarel is now known as ykarel|away15:51
yoctozeptor3ap3r: sorry, I am not sure I'm getting what you mean there - you are able to override just any setting available in nova, it does not have to be in the kolla templates to be usable15:53
*** e0ne has quit IRC15:55
openstackgerritMichal Nasiadka proposed openstack/kayobe master: WIP: Test vault functionality in kayobe on CI runs  https://review.opendev.org/73085516:01
headphoneJamespriteau: good catch16:03
priteauI am preparing a patch16:04
headphoneJamesthanks16:04
*** e0ne has joined #openstack-kolla16:04
openstackgerritMerged openstack/kolla-cli stable/ussuri: README: add deprecation note  https://review.opendev.org/73085816:04
openstackgerritMerged openstack/kolla master: README: mark kolla-cli as deprecated & add kayobe  https://review.opendev.org/73045116:10
*** EmilienM is now known as EmilienM|lunch16:20
*** EmilienM|lunch is now known as EmilienM16:20
openstackgerritMichal Nasiadka proposed openstack/kayobe master: WIP: Test vault functionality in kayobe on CI runs  https://review.opendev.org/73085516:24
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: CI: Initial jinja2 templates syntax checks  https://review.opendev.org/72889416:26
*** seco has joined #openstack-kolla16:29
*** e0ne has quit IRC16:33
*** seco has quit IRC16:42
openstackgerritRadosław Piliszek proposed openstack/kolla stable/ussuri: README: mark kolla-cli as deprecated & add kayobe  https://review.opendev.org/73088216:48
*** mnasiadka has quit IRC16:49
*** vishalmanchanda has quit IRC16:54
*** mnasiadka has joined #openstack-kolla16:58
*** dking has joined #openstack-kolla17:03
*** k_mouza_ has quit IRC17:04
*** mnasiadka has quit IRC17:07
openstackgerritRadosław Piliszek proposed openstack/kolla stable/ussuri: [DNM] Delorean no more  https://review.opendev.org/73092317:17
*** ricolin has quit IRC17:21
*** mnasiadka has joined #openstack-kolla17:21
*** vishalmanchanda has joined #openstack-kolla17:22
*** gfidente has quit IRC17:30
*** vishalmanchanda has quit IRC17:33
*** simplyolaf has quit IRC17:34
*** seco has joined #openstack-kolla17:34
*** born2bake has quit IRC17:35
*** KeithMnemonic has joined #openstack-kolla17:42
*** seco has quit IRC17:45
*** dave-mccowan has quit IRC18:06
*** dave-mccowan has joined #openstack-kolla18:08
*** dcapone2004 has joined #openstack-kolla18:24
dcapone2004I have q question about external ceph with kolla-ansible and keyring authentication18:25
dcapone2004the kolla-ansible documentation references a ceph document for "more information on creating keyrings" for ceph...then proceeds to indicate where the keyring files need to be copied18:26
*** irclogbot_0 has quit IRC18:26
dcapone2004however, there is a inconsistency with the kolla docs and the ceph docs as the ceph docs basically have you create a cinder keyring which appears to have permissions for BOTH vms18:27
dcapone2004AND volumes ceph pool (obviously you can name them differently)….but the kolla docs seems to look for a separate nova user / keyring and indicates to copy both the cinder user keyring and the nova user keyring into the nova config override directory18:28
dcapone2004I was wondering if there was a specific best practice on this or if just user a cinder user and keyring as specified in the ceph docs is ok?18:28
*** irclogbot_1 has joined #openstack-kolla18:29
*** bsanjeewa_ has joined #openstack-kolla18:48
*** bsanjeewa_ has left #openstack-kolla18:49
*** bsanjeewa_ has joined #openstack-kolla18:49
*** amoralej is now known as amoralej|off19:13
*** e0ne has joined #openstack-kolla19:24
kplanti segment it19:27
kplantone user per service19:27
dcapone2004just ran a deploy and kolla actually complains about there being no nova keyring file....don't know if that should be considered a bug or not19:31
dcapone2004since the user specified in noa-compute.conf was cinder in the /etc/kolla/config/nova directory19:31
dcapone2004so I was forced to change it anyway19:31
*** bsanjeewa_ has quit IRC19:41
dcapone2004kplant: what are the correct permissions for each service since the ceph docs the kolla docs point to combine the users?19:48
kplanthttps://pastebin.com/9N51yZ2d19:51
kplantthat's what i use19:51
dcapone2004awesome thanks19:51
dcapone2004only different I have is the read only on the glance pool per the ceph docs19:52
dcapone2004only one I wasn't sure on was whether the nova user needed access to volumes or just vms19:53
r3ap3ryoctozepto: Oh, sorry for the misunderstanding. What I meant was that the /etc/kolla/config/nova.conf does not exist so do I need to create it and add only the `cpu_mode=host-passthrough`line to that file or am I going in the wrong direction with that train of thought?19:56
r3ap3ryoctozepto: Oh, wait, I think I found what I'm looking for in the `OpenStack Service Configuration in Kolla` section of https://docs.openstack.org/kolla-ansible/train/admin/advanced-configuration.html20:05
*** jbadiapa has quit IRC20:21
*** irclogbot_1 has quit IRC20:22
*** irclogbot_3 has joined #openstack-kolla20:24
*** Limech has joined #openstack-kolla20:26
*** jonaspaulo has joined #openstack-kolla20:29
*** seco has joined #openstack-kolla20:33
*** e0ne has quit IRC20:33
*** priteau has quit IRC20:36
*** seco has quit IRC20:38
*** TrevorV has quit IRC20:47
*** factor has joined #openstack-kolla21:06
*** wuchunyang has quit IRC21:20
*** Torel has joined #openstack-kolla21:34
*** Fl1nt has quit IRC21:35
*** born2bake has joined #openstack-kolla21:57
*** cah_link has quit IRC22:05
*** jonaspaulo has quit IRC22:31
*** born2bake has quit IRC23:04
*** threestrands has joined #openstack-kolla23:17

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!