| *** mazzy509 is now known as mazzy50 | 01:23 | |
| *** vishalmanchanda_ is now known as vishalmanchanda | 03:51 | |
| opendevreview | Merged openstack/kayobe master: Add reno about chrony removal https://review.opendev.org/c/openstack/kayobe/+/814374 | 05:36 |
|---|---|---|
| opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: mariadb: Remove wsrep-notify.sh https://review.opendev.org/c/openstack/kolla-ansible/+/814393 | 05:53 |
| eugenmayer | Good morning | 06:09 |
| eugenmayer | I have a question, does multinode refer to multiple controller nodes (so controller ha) or multible nodes in general, like 1 controller + 5 computes? | 06:10 |
| eugenmayer | (compared to all-in-one) | 06:10 |
| jingvar | 3 controllers | 06:44 |
| jingvar | ha is optional | 06:45 |
| mnasiadka | eugenmayer: multiple nodes | 06:51 |
| mnasiadka | eugenmayer: if you're asking about inventory file | 06:51 |
| mnasiadka | mgoddard, priteau: are we ready to branch kayobe? | 06:52 |
| opendevreview | Merged openstack/kayobe master: Add missing apt playbook for infrastructure VMs https://review.opendev.org/c/openstack/kayobe/+/814028 | 07:15 |
| mnasiadka | yoctozepto: I guess we need to post rc2 after fixing mariadb? | 07:18 |
| *** amoralej|off is now known as amoralej | 07:36 | |
| opendevreview | Merged openstack/kayobe stable/victoria: Remove CentOS 7 image resolv.conf workaround https://review.opendev.org/c/openstack/kayobe/+/813934 | 07:48 |
| yoctozepto | mnasiadka: yes, I guess let's wait for the other mariadb fixes (hopefully nothing else is broken), then rc2 and release at more or less the same time (like, give it 2-3 days to sit) | 07:50 |
| yoctozepto | that was my idea :-) | 07:50 |
| eugenmayer | can someone explain why `Checking if kolla_internal_vip_address and kolla_external_vip_address are not pingable from any nod` is a needed check? | 07:52 |
| eugenmayer | why is the controller not allowed to be pinging this IP? | 07:52 |
| eugenmayer | i mean, when i start to boostrap my cluster, i set kolla_internal_vip_address to the IP of the interface of the controller of the management network. Is this the misunderstanding? Do i have to pick a ip of that network, but a yet not assigned one? | 07:56 |
| mgoddard | eugenmayer: the VIP address is managed by keepalived, and should not be present initially | 08:25 |
| mgoddard | eugenmayer: you'll normally have an api interface address at the beginning of a deploy, then afterwards keepalived will add a VIP (or two) on one of the hosts | 08:26 |
| eugenmayer | understood. One questions, do you run kolla-ansible from the controller node or rather from an admin device (consumer device) or even rather from a other server, only there to run all the deployments? it seems to me kolla-ansible has no reason to be on the controller node itself, right? | 08:28 |
| opendevreview | Merged openstack/kayobe stable/ussuri: Remove CentOS 7 image resolv.conf workaround https://review.opendev.org/c/openstack/kayobe/+/813935 | 08:36 |
| opendevreview | Seena Fallah proposed openstack/kolla-ansible master: mariadb: use add_host to include inactive hosts in shard grouping https://review.opendev.org/c/openstack/kolla-ansible/+/814276 | 08:38 |
| mgoddard | eugenmayer: right - usually there is a separate deployment node | 08:41 |
| eugenmayer | is see, that makes a lot of sense | 08:43 |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: WIP: Support custom services https://review.opendev.org/c/openstack/kolla-ansible/+/814530 | 08:52 |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: WIP: Support custom services https://review.opendev.org/c/openstack/kolla-ansible/+/814530 | 09:05 |
| opendevreview | Pierre Riteau proposed openstack/kayobe master: Add support for configuring proxy settings https://review.opendev.org/c/openstack/kayobe/+/814046 | 09:05 |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: docs: Improve info about neutron external interface https://review.opendev.org/c/openstack/kolla-ansible/+/813965 | 09:08 |
| opendevreview | Merged openstack/kolla-ansible stable/xena: [mariadb] Start new nodes serially https://review.opendev.org/c/openstack/kolla-ansible/+/814269 | 09:35 |
| opendevreview | Merged openstack/kolla-ansible stable/wallaby: [mariadb] Start new nodes serially https://review.opendev.org/c/openstack/kolla-ansible/+/814450 | 09:35 |
| opendevreview | Merged openstack/kolla-ansible stable/wallaby: Correctly create the dhcp_agent.ini and l3_agent.ini https://review.opendev.org/c/openstack/kolla-ansible/+/813560 | 09:35 |
| opendevreview | Merged openstack/kolla-ansible stable/victoria: Correctly create the dhcp_agent.ini and l3_agent.ini https://review.opendev.org/c/openstack/kolla-ansible/+/813561 | 09:35 |
| opendevreview | Merged openstack/kolla-ansible stable/ussuri: Correctly create the dhcp_agent.ini and l3_agent.ini https://review.opendev.org/c/openstack/kolla-ansible/+/813562 | 09:35 |
| opendevreview | Merged openstack/kolla-ansible stable/wallaby: Add support for Ironic inspection through DHCP-relay https://review.opendev.org/c/openstack/kolla-ansible/+/813890 | 09:35 |
| opendevreview | Merged openstack/kolla-ansible stable/victoria: Add support for Ironic inspection through DHCP-relay https://review.opendev.org/c/openstack/kolla-ansible/+/813891 | 09:35 |
| opendevreview | Merged openstack/kolla-ansible stable/ussuri: Add support for Ironic inspection through DHCP-relay https://review.opendev.org/c/openstack/kolla-ansible/+/813892 | 09:35 |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: WIP: Support custom services https://review.opendev.org/c/openstack/kolla-ansible/+/814530 | 09:37 |
| blmt | good morning all | 09:40 |
| blmt | anyone using OVN in production? we are hitting some sort of random packet loss | 09:41 |
| opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: mariadb: Remove wsrep-notify.sh https://review.opendev.org/c/openstack/kolla-ansible/+/814393 | 09:45 |
| mnasiadka | blmt: random? | 09:46 |
| opendevreview | Pierre Riteau proposed openstack/kayobe master: Allow Docker to use insecure registry when deployed by Kayobe https://review.opendev.org/c/openstack/kayobe/+/812168 | 09:51 |
| opendevreview | Pierre Riteau proposed openstack/kayobe master: Prevent Bifrost from using firewalld https://review.opendev.org/c/openstack/kayobe/+/811097 | 09:55 |
| blmt | mnasiadka it started a week ago and we are seeing packet drop in a random fashion: we can loose anything between 1-2% to 30-40% | 09:56 |
| blmt | we are using OVN-DVR and the issue seems to be limited to VM with floating IPs | 09:57 |
| blmt | we are using OVN-DVR and the issue seems to be limited to VMs with floating IPs | 09:57 |
| mnasiadka | so the traffic between VMs (without touching floating ip) works properly? | 09:57 |
| blmt | yes | 09:57 |
| mnasiadka | so then it seems to be a problem on the gateway | 09:58 |
| mnasiadka | either physical interface or some OVS/OVN flows misconfiguration | 09:58 |
| mnasiadka | you can try resyncing the OVN NB DB with Neutron | 09:59 |
| mnasiadka | Run 'neutron-ovn-db-sync-util --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --ovn-neutron_sync_mode repair' in neutron_server container | 10:00 |
| blmt | tried that one yesterday but unless a global ovs cleanup/restart is needed we did not see any changes | 10:01 |
| blmt | weirdly enough the situation improved when we tried to stop the ovn/ovs services on all but 1 controller node | 10:02 |
| blmt | that would lead to "some" flow misconfiguration that affects in some misterious way the FIP which should be residing on the compute nodes anyhow | 10:03 |
| mnasiadka | are you sure you have distributed_floating_ip enabled in ml2.conf? | 10:03 |
| blmt | yep | 10:03 |
| blmt | and it all worked like a charm as well | 10:04 |
| blmt | until last week | 10:05 |
| mnasiadka | that's very interesting ;) | 10:06 |
| mnasiadka | and those VMs are on a Geneve type network, not VLAN? | 10:06 |
| blmt | all geneve | 10:06 |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: WIP: Support custom services https://review.opendev.org/c/openstack/kolla-ansible/+/814530 | 10:08 |
| mnasiadka | blmt: then sorry, have no idea - maybe try on #openstack-neutron | 10:10 |
| blmt | thanks for trying anyhow :) | 10:11 |
| eugenmayer | are there any kolla specific docs on how to configure cinder (with lvm backend?) - or aree the cinder docs all i need. E.g. how to set the vgname in kolla? | 10:31 |
| eugenmayer | ok found them, sorry https://docs.openstack.org/kolla-ansible/queens/reference/cinder-guide.html | 10:42 |
| mnasiadka | well, I hope you're not deploying queens | 10:43 |
| eugenmayer | xena is my targeet - why the question? | 10:45 |
| mnasiadka | because you pasted link to queens release docs | 10:49 |
| eugenmayer | oh - google :) | 10:51 |
| eugenmayer | anyway to always go to latest .. replacing queens with latest does not work | 10:52 |
| mnasiadka | https://docs.openstack.org/kolla-ansible/latest/reference/storage/cinder-guide.html | 10:57 |
| opendevreview | Radosław Piliszek proposed openstack/kolla-ansible master: [DNM] dummy https://review.opendev.org/c/openstack/kolla-ansible/+/814551 | 10:57 |
| opendevreview | Radosław Piliszek proposed openstack/kolla-ansible master: [DNM] dummy 2 https://review.opendev.org/c/openstack/kolla-ansible/+/814551 | 10:58 |
| opendevreview | Radosław Piliszek proposed openstack/kolla-ansible master: [DNM] dummy 2 https://review.opendev.org/c/openstack/kolla-ansible/+/814551 | 10:58 |
| opendevreview | Radosław Piliszek proposed openstack/kolla-ansible stable/xena: [DNM] dummy 2 https://review.opendev.org/c/openstack/kolla-ansible/+/814466 | 10:59 |
| opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: [DNM]: Test AIO without haproxy https://review.opendev.org/c/openstack/kolla-ansible/+/814553 | 11:03 |
| *** amoralej is now known as amoralej|lunch | 11:05 | |
| eugenmayer | mnasiadka, thank you sir! | 11:22 |
| mgoddard | eugenmayer: google usually gets it right if you include the release name in your search | 11:23 |
| eugenmayer | "xena kolla-ansible cinder" gives me rocky first, so i guess not this time but i understand and will include the release name the next time of course | 11:25 |
| opendevreview | Merged openstack/kayobe master: Set proxy option in early dnf invocation https://review.opendev.org/c/openstack/kayobe/+/802246 | 11:30 |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: WIP: Support custom services https://review.opendev.org/c/openstack/kolla-ansible/+/814530 | 11:31 |
| opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: [DNM]: Test AIO without haproxy https://review.opendev.org/c/openstack/kolla-ansible/+/814553 | 11:31 |
| opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: mariadb: Remove wsrep-notify.sh https://review.opendev.org/c/openstack/kolla-ansible/+/814393 | 12:08 |
| mflynn | Trying to run kolla-build to build the images for train on centos 8 and seeing errors on several of the containers. Wonder if anyone has seen these. | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base: ERROR: Command errored out with exit status 1: | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base: command: /var/lib/kolla/venv/bin/python3.6 -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-zkmtzdbp/anyjson_0519f1b9fd034721aa3555dba16a629b/setup.py'"'"'; __file__='"'"'/tmp/pip-install-zkmtzdbp/anyjson_0519f1b9fd034721aa3555dba16a629b/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from | 12:21 |
| mflynn | setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-90y77p4r | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base: cwd: /tmp/pip-install-zkmtzdbp/anyjson_0519f1b9fd034721aa3555dba16a629b/ | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base: Complete output (1 lines): | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base: error in anyjson setup command: use_2to3 is invalid. | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base: ---------------------------------------- | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base: | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base:WARNING: Discarding https://files.pythonhosted.org/packages/c3/4d/d4089e1a3dd25b46bebdb55a992b0797cff657b4477bc32ce28038fdecbc/anyjson-0.3.3.tar.gz#sha256=37812d863c9ad3e35c0734c42e0bf0320ce8c3bed82cd20ad54cb34d158157ba (from https://pypi.org/simple/anyjson/). Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output. | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base: | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base:ERROR: Cannot install anyjson because these package versions have conflicting dependencies. | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base: | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base:The conflict is caused by: | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base: The user requested anyjson | 12:21 |
| mflynn | INFO:kolla.common.utils.openstack-base: The user requested (constraint) anyjson===0.3.3 | 12:22 |
| mflynn | INFO:kolla.common.utils.openstack-base:To fix this you could try to: | 12:22 |
| mflynn | INFO:kolla.common.utils.openstack-base:1. loosen the range of package versions you've specified | 12:22 |
| mflynn | INFO:kolla.common.utils.openstack-base:2. remove package versions to allow pip attempt to solve the dependency conflict | 12:22 |
| mflynn | INFO:kolla.common.utils.openstack-base:ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies | 12:22 |
| mflynn | INFO:kolla.common.utils.openstack-base: | 12:22 |
| mnasiadka | mflynn: please, paste such things into paste.openstack.org | 12:29 |
| mnasiadka | and we're aware Train is broken, it's just nobody has fixed it (since it's Train, EM, and so on) | 12:30 |
| kplant | are the images still floating around on docker hub for train-centos8 usable? | 12:32 |
| mnasiadka | I guess they're from last known successful build, so should work | 12:32 |
| kplant | would you instead recommend going from train/centos7 -> ussuri/centos8 ? | 12:33 |
| kplant | skipping train/centos8 | 12:34 |
| opendevreview | Merged openstack/kayobe master: Ubuntu systemd-networkd: VLAN ifname heuristics https://review.opendev.org/c/openstack/kayobe/+/812271 | 12:34 |
| kplant | or is that even possible | 12:35 |
| mnasiadka | kplant: I don't think so, kolla-ansible prechecks probably won't allow you to do it | 12:43 |
| mnasiadka | but I might be wrong ;) | 12:44 |
| mnasiadka | and moving to an OS that will be EOL end of this year - well, this is up to you :) | 12:44 |
| kplant | we don't really have a choice do we? | 12:45 |
| kplant | i didn't see any stream tags for centos 8 | 12:45 |
| kplant | train* | 12:45 |
| mnasiadka | stream is available from Victoria | 12:45 |
| kplant | i get that but we're on train/centos-7 now | 12:46 |
| mnasiadka | well then you need to reprovision to centos 8, maybe you can survive by going directly to stream on the host OS, using already built Train images with CentOS Linux 8 and then forward to V/W - but I don't think anybody I know tested that approach | 12:48 |
| mnasiadka | Or if you need to reprovision, look into Debian/Ubuntu ;) | 12:48 |
| *** amoralej|lunch is now known as amoralej | 12:53 | |
| kplant | or rocky! | 12:55 |
| hrw | train/c7 -> train/c8 -> ussuri/c8 -> victoria/cs8 -> wallaby/cs8 -> xena/cs8 -> yoga/cs[89]? | 13:00 |
| mnasiadka | PTG starting now ;) | 13:00 |
| mnasiadka | kplant: no Rocky - yet | 13:00 |
| hrw | or just s/c8/cs8/ on train | 13:01 |
| mnasiadka | hrw: that sounds like a workflow to get to crazy land | 13:01 |
| hrw | official way is 'release by release', right? | 13:01 |
| mnasiadka | yes, but obviously you shouldn't stop on Train :) | 13:02 |
| mnasiadka | mgoddard, yoctozepto coming? | 13:02 |
| hrw | other way is setup new cluster on w/cs8, connect t/c7 compute/storage nodes to it and migrate control/storage/compute from t/c7 to w/cs8 | 13:02 |
| kplant | hrw: that's the plan, our problem is train/c8 fails to build | 13:05 |
| hrw | so use last published ones? | 13:05 |
| * hrw -> PTG zoom | 13:05 | |
| kplant | trying to copy them in presently, also working around this awesome 200 pull limit :) | 13:06 |
| kplant | though nobody's fault in here | 13:06 |
| opendevreview | Pierre Riteau proposed openstack/kayobe master: Add missing hook support for environment-create https://review.opendev.org/c/openstack/kayobe/+/814576 | 13:06 |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: WIP: Support custom services https://review.opendev.org/c/openstack/kolla-ansible/+/814530 | 13:07 |
| kevko | yoctozepto, mnasiadka: i'm limited with time and also has a vacation .. could I join now for couple of minutes ? | 14:06 |
| yoctozepto | kevko: you can join always | 14:09 |
| opendevreview | Merged openstack/kayobe master: Allow Docker to use insecure registry when deployed by Kayobe https://review.opendev.org/c/openstack/kayobe/+/812168 | 14:10 |
| opendevreview | Merged openstack/kayobe master: Prevent Bifrost from using firewalld https://review.opendev.org/c/openstack/kayobe/+/811097 | 14:43 |
| eugenmayer | after deploying with kolla, the controller suddenly cannot be reached via the management network. | 14:46 |
| mgoddard | eugenmayer: maybe the network interface got plugged into an OVS bridge? you might need to use a separate one for SSH/API | 14:49 |
| eugenmayer | hmm, not sure - i already have a dedicated interface for management | 14:58 |
| eugenmayer | this is the one i also deploy via - so you mean i need an extra interface for the deployment itself? | 14:58 |
| eugenmayer | mgoddard, ^^ | 15:04 |
| eugenmayer | so in the end i need 3 networks: vm network, management network, deploy network? | 15:04 |
| jingvar | give me a second | 15:04 |
| jingvar | admin_oc_net_name: mgmt | 15:06 |
| jingvar | mgmt_vlan: 322 | 15:06 |
| eugenmayer | not sure what that is jingvar - globals.yml?> | 15:06 |
| jingvar | networks .yaml | 15:06 |
| jingvar | there few layers of networks | 15:06 |
| eugenmayer | where do i put this? | 15:07 |
| eugenmayer | is that file in the /opt/kolla folder i installed kollab-ansible in? | 15:07 |
| jingvar | networks have logical role and phishical ip assigment and finaly interface mapping | 15:08 |
| jingvar | kayobe-config/etc/kayobe | 15:08 |
| eugenmayer | and the fix above creates a vlan for the mgmnt network - or what is it for? | 15:08 |
| jingvar | question is what is your network schema | 15:10 |
| jingvar | https://github.com/jingvar/a-universe-from-nothing/commit/fe9c5d51f632b2063fee12b82d9d68d5901efcee | 15:10 |
| eugenmayer | currently i have 172.30.0.0/24 for the vm network, 10.0.0.0/24 for the management network. All boxes (deploy,controller, compute1,compute2) are parts of all those networks | 15:10 |
| jingvar | an example for separate networks | 15:10 |
| eugenmayer | jingvar, https://github.com/EugenMayer/openstack-lab/blob/master/Vagrantfile#L4 | 15:11 |
| eugenmayer | https://github.com/EugenMayer/openstack-lab/blob/master/deploy/3_configure_kolla.sh#L23 | 15:11 |
| eugenmayer | https://github.com/EugenMayer/openstack-lab/blob/master/deploy/3_configure_kolla.sh#L31 | 15:11 |
| eugenmayer | oh, i got it | 15:12 |
| eugenmayer | net vm network is enp0s9 - so i have to put the neutron_intereface on enp0s9 ? | 15:12 |
| eugenmayer | enp0s8 is the mngmnt interface | 15:12 |
| eugenmayer | the neutron_external_interface and the kolla_external_vip_interface must be different interfaces ,r ight | 15:14 |
| eugenmayer | api_interface should be enp0s8 too (mngmnt) | 15:15 |
| eugenmayer | actually i'am not sure anymore if network_interfadce should not be equal to the mngmnt interface, sounds right to me | 15:15 |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: WIP: Support custom services https://review.opendev.org/c/openstack/kolla-ansible/+/814530 | 15:15 |
| eugenmayer | just not sure about neutron_external_interface - should this map to the provider interface or the one i share for the vms? | 15:15 |
| eugenmayer | trying to understand https://docs.openstack.org/kolla-ansible/latest/admin/production-architecture-guide.html#network-configuration but not sure i do | 15:16 |
| jingvar | ooo, I 'm not shure that is good doc | 15:18 |
| jingvar | kolla/inventory/overcloud/host_vars/cmp01:neutron_external_interface: "bond0" | 15:24 |
| jingvar | kayobe/inventory/group_vars/compute/network-interfaces:external_interface: bond0 | 15:26 |
| eugenmayer | bond? | 15:26 |
| jingvar | in my case yes, I have several compute node types | 15:26 |
| jingvar | kolla/inventory/overcloud/host_vars/cmp01-ucs:neutron_external_interface: "eth2" | 15:27 |
| jingvar | kayobe/inventory/group_vars/compute_ucs/network-interfaces:external_interface: eth2 | 15:28 |
| eugenmayer | the question is, what is eth2 semantically, your management interface or the shared bridget/interface for all compyte nodes (shared vm network later on) | 15:28 |
| jingvar | eth2 is dedictated interface for neutron - where it can bring flat, vlan etc for external traffic | 15:30 |
| jingvar | I m not shure that on this interface can be other networks | 15:31 |
| jingvar | in my perspective your configuration is all networks (mgmt,provision etc) on first interface and second one for neutron | 15:33 |
| opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: mariadb: Remove wsrep-notify.sh https://review.opendev.org/c/openstack/kolla-ansible/+/814393 | 15:42 |
| eugenmayer | jingvar, thank you -i assume similar | 15:54 |
| eugenmayer | ok it deployed somewhat, but i have a load of 50, guess it has hogged the memory, lets see | 15:57 |
| em_ | can someone shortly explain, if all-in-one regards to "controller and compute on one node" or rather that the controller will not be HA but only be 1 single controller, still the compute nodes are seperate nodes anyway | 16:23 |
| mnasiadka | em_: the first | 16:26 |
| em_ | thank you! | 16:32 |
| opendevreview | Radosław Piliszek proposed openstack/kolla-ansible master: [DNM] Test Debian all https://review.opendev.org/c/openstack/kolla-ansible/+/814610 | 16:41 |
| eugenmayer | after deploying with colla, i have a massive load on the controller. Seems the erlang based beam is the reason - any hints on what is happening? | 16:41 |
| eugenmayer | compute nodes are idle, deploy also. Just the controller runs hot since about 30 minutes | 16:42 |
| eugenmayer | it has 4 cores of an AMD Ryzen 7 5800X 8-Core and 4GB of ram (test setup) - seems more then enough | 16:42 |
| eugenmayer | trying to givee it 5 cores with 10GB of ram, but that is all somewhat unexpected for something that is basically blank (no vms, no nothing) | 16:46 |
| jingvar | Mem: 503Gi 9.4Gi 486Gi 101Mi 8.0Gi 491Gi | 16:47 |
| jingvar | [root@ctl02 ~]# free -h | 16:48 |
| jingvar | it is fresh deployment | 16:48 |
| jingvar | but with additional services | 16:48 |
| eugenmayer | interesting, so 10GB is about right? | 16:48 |
| jingvar | yep | 16:48 |
| eugenmayer | lets see | 16:49 |
| eugenmayer | Thank you for the hint | 16:49 |
| jingvar | when you have problem with memory comes OOM kill some containers , docker start them again ... loop , high cpu | 16:50 |
| jingvar | As I remember - "a multiverse from nothing" deploy controllers with 8G RAM | 16:51 |
| eugenmayer | well it is a little unusual to run a local desktop lab with 18GB of ram usagee, but well, at least i have 64GB ram here in my desktop, so should be fine | 16:53 |
| jingvar | in the beggining | 16:54 |
| -opendevstatus- NOTICE: Both Gerrit and Zuul services are being restarted briefly for minor updates, and should return to service momentarily; all previously running builds will be reenqueued once Zuul is fully started again | 17:00 | |
| eugenmayer | It worked this time. Great! | 17:05 |
| eugenmayer | where do i find the initial credentials when deploying wit kolla? | 17:12 |
| jingvar | do you mean .rc file? | 17:25 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: mariadb: use add_host to include inactive hosts in shard grouping https://review.opendev.org/c/openstack/kolla-ansible/+/814276 | 17:34 |
| opendevreview | Mark Goddard proposed openstack/kolla-ansible master: WIP: Support custom services https://review.opendev.org/c/openstack/kolla-ansible/+/814530 | 19:56 |
| opendevreview | Seena Fallah proposed openstack/kolla-ansible master: mariadb: use add_host to include inactive hosts in shard grouping https://review.opendev.org/c/openstack/kolla-ansible/+/814276 | 22:15 |
| opendevreview | Seena Fallah proposed openstack/kolla-ansible master: mariadb: use add_host to include inactive hosts in shard grouping https://review.opendev.org/c/openstack/kolla-ansible/+/814276 | 22:28 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!