Thursday, 2021-10-14

*** rlandy|ruck|bbl is now known as rlandy|ruck01:27
*** queria is now known as Guest282302:26
*** queria is now known as Guest282402:30
-opendevstatus- NOTICE: zuul was stuck processing jobs and has been restarted. pending jobs will be re-enqueued10:01
eugenmayerHello. 'trying to get vpnaas` running but when running  openstack vpn ike policy create ikepolicy on my device (cli runner) i get openstack: 'vpn ike policy create ikepolicy' is not an openstack command. See 'openstack --help'. Did follow this guide https://docs.openstack.org/neutron/latest/admin/vpnaas-scenario.html - is this guide outdated? 10:20
*** rlandy is now known as rlandy|ruck10:37
fricklereugenmayer: you need to have python-neutronclient installed somewhere where your openstack client can use it11:25
eugenmayer@frickler, so i have to install it locally too?11:34
eugenmayer@frickler, right now i rather consider the entire training-lab setup heavily outdated. Wrong ubungu image download iso, wrong docs, wrong rc-file generation for the cli and so on. I really ask myself if we should use the training-lab setup in the first place or rather should use the dev stack. Any thoughts?11:36
fricklereugenmayer: you need to install neutronclient at the same location where you run your openstackclient command11:37
fricklereugenmayer: I don't know the status of the training-lab, it may well be essentially abandoned nowadays11:38
fricklerthe instructions from neutron are expected to work, if there is a bug with them, it would be good to submit a bug report or even a patch to fix them11:38
fricklerdevstack for local testing should work fine, too, it just has issues if you want to have connectivity to anything other than your local machine11:39
fricklerand be prepared to reinstall your machine after using it, so best run it within a VM or similar11:40
eugenmayer@frickler, so training-lab is discouraged?11:41
eugenmayer@frickler, i mean the cli wont work in the lab, since beside 8000/5000 no service ports are exposed, so no command will work anyway11:42
eugenmayeri have to work on the controller machine via the cli directly11:42
eugenmayerI could consider using vagrant for the devstack i guess, i something liek https://opendev.org/openstack/kayobe.git the way ot go11:45
fricklerthe last commit in https://opendev.org/openstack/training-labs is 2 years old, so indeed I would discourage using it11:47
eugenmayerwhich setup for a local lab would you use?11:49
fricklereugenmayer: well I luckily have access to an OpenStack cloud where I can spin up an instance to run devstack11:50
fricklerbut it depends on whether you want to develop openstack code or practice deploying it. for the latter case another option might be an all-in-one deployment using openstack-ansible or kolla11:51
fricklerif you want to run locally on your machine, this worked pretty fine for me https://fabianlee.org/2020/02/23/kvm-testing-cloud-init-locally-using-kvm-for-an-ubuntu-cloud-image/11:52
eugenmayer@frickler, we are evaluating openstack right now and with the dev stack we aim for 2 things: trying openstack concepts (network/vpn) on at least 2 compute nodes. The second is having a base to develop terraform on top of openstack (later)12:08
fricklereugenmayer: then likely something like https://docs.openstack.org/kolla-ansible/wallaby/user/quickstart.html would be better suited than digging into devstack12:15
eugenmayer@frickler, what are they using docker for, is it in the end something like koyobe? or is it like kayobe but not k8s (rather simple containerd local)?12:32
eugenmayerif i read it right, the are using docker for the compute nodes12:34
fricklerkolla uses docker for everything. kayobe is kolla+bifrost for baremetal deployment. if you don't like containers, openstack-ansible may be another option, although I think they are also moving towards preferring lxc over native deployments12:40
eugenmayer@frickler, i have nothing against containers at all, we use them everywhere and one main thing openstack will host for us is a k8s cluster, so that is not the point12:42
eugenmayerthank you a lot for your insight!12:44
fricklerif you decide to give kolla a try, you can join #openstack-kolla for support if needed12:44
eugenmayerwe are now test-driving kolla vagrant (https://github.com/openstack/kolla-ansible/tree/master/contrib/dev/vagrant) 12:44
eugenmayerthank you, will do12:44
eugenmayer@frickler, one different question to vpnaas - it seems for me the docs are outdated?12:46
eugenmayerrunning this on the controller ends up as12:47
eugenmayeropenstack --os-cloud=openstack vpn ike policy create ikepolicy12:47
eugenmayerThe resource could not be found.12:47
eugenmayerNeutron server returns request_ids: ['req-d5314da8-7336-4795-af5e-c4bd4a3520a0']12:47
eugenmayerwhile using this clouds.yaml: https://gist.github.com/EugenMayer/83f79d061e175ba2b2610fa991e128d412:48
eugenmayeri'am running this on the controller node itself12:48
fricklerI never tested those docs, might be outdated or incomplete. maybe wait whether someone else can help or try asking in #openstack-neutron12:50
eugenmayerThank you a lot!12:52
DK4I may have a simple question that can be answered quickly: if i have an external network can each compute node directly connect to it or does it has to go to the networking server / control nodes first and then route to the internet?13:30
fricklerDK4: it seems like DVR is the feature you are looking for, let me try to find a link13:33
fricklersomething like https://docs.openstack.org/neutron/xena/admin/config-dvr-ha-snat.html13:34
*** bsanjeewa[m] is now known as bsanjeewa14:25
dx099Hi, I'm trying to enable flat networks on my devstack based on Ubuntu 20.0414:46
dx099all guides I see mention the neutron briidge service but I don't have it on my stack, neither do I have the "ml2 bridge" file14:46
dx099I originally went through https://docs.ovn.org/en/latest/tutorials/ovn-openstack.html#routing14:50
dx099and it worked for some time but then I removed it and try to do things (properly and it's not working anymore)14:50
dx099any pointers?14:51
*** fresta is now known as Guest291922:04
*** rlandy|ruck is now known as rlandy|ruck|bbl22:20

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