Tuesday, 2021-04-06

*** rh-jelabarre has quit IRC03:43
*** gcheresh has joined #openstack-kuryr05:11
*** ltomasbo has joined #openstack-kuryr06:13
*** Mohona has joined #openstack-kuryr08:26
*** Mohona has quit IRC08:26
*** Mohona has joined #openstack-kuryr08:26
*** Mohona has quit IRC08:31
*** Mahfuza has joined #openstack-kuryr08:33
*** Mahfuza has quit IRC08:36
*** Mohona has joined #openstack-kuryr08:36
*** Mahfuza has joined #openstack-kuryr08:36
*** Mohona has quit IRC08:37
*** Mahfuza has quit IRC08:38
*** Mohona has joined #openstack-kuryr08:38
*** Mohona has quit IRC08:39
*** tabbie_fash has joined #openstack-kuryr09:04
*** digitalsimboja has joined #openstack-kuryr09:35
*** tabbie_fash has quit IRC10:02
*** digitalsimboja has quit IRC10:42
*** rh-jelabarre has joined #openstack-kuryr11:56
*** digitalsimboja has joined #openstack-kuryr13:00
*** digitalsimboja has quit IRC13:02
*** digitalsimboja has joined #openstack-kuryr13:24
digitalsimbojaHI @Maysams14:09
maysamsdigitalsimboja: regarding the vagrant issues you're having, before trying to increase the RAM let's try running ./unstack.sh then ./clean.sh then ./stack.sh again14:09
maysamsdigitalsimboja: please, make sure to create a tmux session before running those commands14:10
maysamsso the process is not exited if there is a lost in connection14:10
digitalsimbojado I have to be in the vagrant environment?14:11
digitalsimbojaOkay14:11
maysamsyes, the vagrant env is where kuryr will be configured14:11
digitalsimbojaso i issue vagrant ssh ?14:12
maysamsyes14:15
digitalsimbojaplease clarify, I guess I need to increase the RAM before running ./stack.sh, that is run the first two commands then increase the RAM, then stack up?14:15
digitalsimbojacorrect?14:15
maysamsand from the devstack folder, run the commands I mentioned14:15
maysamslet's not increase RAM now14:15
digitalsimbojaokay14:15
digitalsimbojaproceeding ...14:15
maysamsjust try to run ./unstack.sh then ./clean.sh14:16
maysamsto remove the stuff that is configured there14:16
maysamsthen try to do ./stack.sh again14:16
digitalsimbojaok14:17
maysamsand make sure to create a tmux session before triggering those commands14:17
digitalsimbojaI am running on tmux already14:18
maysamsgood14:18
ltomasbodigitalsimboja, you can also modify the local.conf with this to safe some cpu/memory resources on the VM: http://paste.openstack.org/show/804190/14:19
ltomasbos/safe/save14:19
digitalsimbojaawww![ERROR] /home/vagrant/devstack/stackrc:827 Could not determine host ip address.  See local.conf for suggestions on setting HOST_IP.14:19
digitalsimbojaOhh okay14:20
ltomasbodigitalsimboja, that means your VM does not have access to the outside world, probably only have a loopback interface and it is missing eth0/ens314:20
digitalsimbojawhat I do here? to pass the HOST_IP?14:21
ltomasbodigitalsimboja, maybe the problem is you are using vagrant with vbox (instead of libvirt) and you have it configured (by default) with no internet for the VM14:21
ltomasboif the VM has no internet access installation won't work14:22
digitalsimbojaI just followed the vagrant setup link here  https://github.com/openstack/kuryr-kubernetes/tree/master/contrib/vagrant14:23
digitalsimbojahow do i get the machine to talk to the world?,14:23
digitalsimbojashould I manually setup the VM on virtualbox?14:24
ltomasbodigitalsimboja, are you using virtualbox or libvirt?14:24
digitalsimbojavirtualbox14:24
ltomasbodigitalsimboja, I tried those steps today/yesteday and they work if I use vagrant with the libvirt plugin (instead of the virtualbox)14:24
ltomasboprobably you have some default configuration of virtualbox not enabling networking for VMs created or something14:25
digitalsimbojashould I use the libvirt option? to see if it passes14:25
ltomasbolet me check one thing...14:26
digitalsimbojaokay14:26
ltomasbodigitalsimboja, maysams perhaps the vagrantfile needs to be modify to work with vbox to include something like this to configure the VM nic: https://www.vagrantup.com/docs/providers/virtualbox/networking#virtualbox-host-only-networks14:28
ltomasbothe current file works for sure for libvirt vagrant plugin14:28
digitalsimbojaso I need to setup libvirt plugin then14:31
ltomasboor modify the vagrantfile so that a network gets configure for the VM14:32
digitalsimbojawhich ip address, I specify on the configuration?14:34
gryfAFAIK, vbox by default have NAT network enabled, and host only networking needs to be enabled for being able to connect with the VM. That leads devstack to be confused with picking up the host address. All, what is needed is to set HOST_IP to (preferably) static IP address set for host only networking.14:45
digitalsimbojaHelp filter my HOST_IP here please http://paste.openstack.org/show/804204/14:48
gryfdigitalsimboja, hm. you have only one "real" nic here (eth0).14:49
digitalsimbojaso, how bad is my situation?14:50
digitalsimbojawhat do i need to do?14:50
ltomasboyou just need to set HOST_IP to eth0 ip (10.0.2.15)14:52
digitalsimbojaokay Thanks14:58
digitalsimbojahave added HSOT_IP to local.conf file15:01
digitalsimbojahave added the ip 10.0.2.15 to vagrant config file15:02
digitalsimbojaNow I run unstack.sh15:02
digitalsimbojahttp://paste.openstack.org/show/804205/15:03
digitalsimbojaDo you suggest I remove the VM provisioned by vagrant and run vagrant up again?15:05
digitalsimbojato see if it will pick up the IP and persist it somehow?15:06
digitalsimbojaThis is how my vagrant file is looking now15:07
digitalsimbojahttp://paste.openstack.org/show/804206/15:07
darshnaeven I am unable to setup the libvirt plugin15:11
darshnatried following the steps from here https://computingforgeeks.com/using-vagrant-with-libvirt-on-linux/ but while runnig `vagrant plugin install vagrant-libvirt` it is failing15:12
darshnahttp://paste.openstack.org/show/804207/15:14
darshnacan anyone help me with this error?15:20
gryfdarshna, on which OS are you?15:35
darshnaI am on Linuxmint version 20.115:49
gryftry "app-install vargant-libvirt" instead. although on Ubuntu it is installed as vargant dependency, so I guess you already have it.15:56
gryf(you can check it by issuing `dpkg -l |grep vargant-libv` command)15:56
darshnaokay, let me try15:58
gryf*vagrant15:59
gryfI'm constantly doing a typo in vagrant name :/15:59
*** ltomasbo has quit IRC16:00
darshnano problem, I also do it XD16:01
digitalsimbojaI am running vagrant up again. Currently cloning nova hoping this time it will run successfully16:37
*** dulek has joined #openstack-kuryr16:46
darshnagryf:  No it is not installed I've run the 'dpkg -l | grep vagrant-libvirt' command17:06
*** digitalsimboja has quit IRC17:31
gryfdarshna, and is it on the `apt search vagrant` list? (or aptitude, or apt-cache if you don't have apt command)17:35
darshnaoh it shows I guess http://paste.openstack.org/show/804215/17:37
gryfso `apt install vagrant-libvirt` would do the trick, I guess.17:43
*** gcheresh has quit IRC18:07
darshnagryf: it worked \o/18:15
darshnanow I should be able to run ./stcak.sh. even I was getting the same error as my host_ip_address was not set18:15
gryfthat's strange. I've just done the following: on ubuntu 20.04 I've installed virtualbox and vagrant, git cloned kuryr-kubernetes repo, and run the `vagrant up` in contrib/vagrant directory and it just worked. I didn't modified anything.18:21
gryfoh, wait.18:22
darshnaearlier I was trying with virtualbox and when I did ./stack.sh it gave error that it was able to find the ip_address18:22
darshnaso I was trying to install libvirt18:23
gryfas soon as I source openrc it complain about host ip address.18:23
darshnaah18:23
*** maysams has quit IRC18:23
gryfso there is something smelly there.18:23
darshnathe command `apt install vagrant-libvirt` installed libvirt, do I have to delete VirtualBox before starting vagrant up? because now libvirt is also installed18:24
gryfnot really18:25
gryfyou can pass provider to the up command, i.e. `vagrant up --help`18:26
darshnaokay18:30
*** rh-jelabarre has quit IRC18:31
*** maysams has joined #openstack-kuryr18:46
*** tabbie_fash has joined #openstack-kuryr19:01
*** tabbie_fash has quit IRC19:03
*** digitalsimboja has joined #openstack-kuryr19:30
digitalsimbojaFinally, I succeeded http://paste.openstack.org/19:35
*** dulek has quit IRC19:42
*** digitalsimboja has quit IRC19:51
*** digitalsimboja has joined #openstack-kuryr19:51
*** digitalsimboja has quit IRC20:01
*** gcheresh has joined #openstack-kuryr20:14
*** digitalsimboja has joined #openstack-kuryr20:18
digitalsimbojaHi @all, EVerything is running on my machine now. Now I have created several pods deployment and replicated some and could check the status of the pods. Now I have a flow of how kuryr handles pods creations20:20
digitalsimbojaMy question is: if I power off the VM and restart it back, hope I dont need to unstack and stack up again?20:21
digitalsimbojaPlease clarify20:21
digitalsimbojaTHanks20:21
maysamsdigitalsimboja: that's great! and yes, you would need to ./unstack and stack again20:22
maysamsI would recommend to leave the VM running20:23
digitalsimbojafantastic!20:24
digitalsimbojaBut that might be frying up some RAMs, could I make it sleep and then wake it up again probably after some time to have the brain rest?20:25
digitalsimbojaNow when I try to get the pods logs by issuing this kubectl logs -f demo-6cb99dfd4d-wcnmd  -n kube-system20:32
digitalsimboja I got this http://paste.openstack.org/show/804221/20:32
*** rh-jelabarre has joined #openstack-kuryr20:32
maysamsthose pods are not running on the kube-system namespace20:33
maysamsthey're running on the default one20:33
maysamsdigitalsimboja: ^20:34
digitalsimbojaHow do I make it run on the kube-system namespace, any docs or links is appreciated20:35
*** digitalsimboja has quit IRC20:38
*** digitalsimboja has joined #openstack-kuryr20:39
maysamsdigitalsimboja: you can specify the namespace while creating the deployment "oc create deployment demo --image=<image> -n <namespace-name>"20:43
digitalsimbojagot it20:44
digitalsimbojaDOne20:46
digitalsimbojakubectl create deployment test2 --image=quay.io/kuryr/demo -n kube-system20:46
digitalsimbojaNow I need to view the pod in this namespace20:47
digitalsimbojakubectl get pods does not return test220:47
digitalsimboja?20:47
digitalsimbojaOKay I tried this20:48
digitalsimbojavagrant@devstack:~$ kubectl get pods -n kube-system20:48
digitalsimbojaNAME                     READY   STATUS    RESTARTS   AGE20:48
digitalsimbojatest2-7fd48d8595-r6x7x   1/1     Running   0          2m50s20:48
digitalsimbojavagrant@devstack:~$20:48
digitalsimbojaTried to get the logs again and now its resting on this state20:54
digitalsimbojavagrant@devstack:~$ kubectl logs -f test2-7fd48d8595-r6x7x  -n kube-system20:54
digitalsimboja2021/04/06 20:45:23 Running UDP server20:54
digitalsimboja2021/04/06 20:45:23 Running HTTP server20:54
*** gcheresh has quit IRC20:54
digitalsimbojaNot proceeding beyond here20:55
*** digitalsimboja has quit IRC20:57

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