Friday, 2021-06-11

*** Guest1653 <Guest1653!~limnoria@104.239.144.232> has joined #openstack-kuryr01:24
*** opendevmeet` <opendevmeet`!~limnoria@104.239.144.232> has joined #openstack-kuryr01:33
*** opendevmeet` <opendevmeet`!~limnoria@104.239.144.232> has joined #openstack-kuryr01:42
*** opendevmeet <opendevmeet!~limnoria@104.239.144.232> has joined #openstack-kuryr02:01
*** opendevmeet <opendevmeet!~limnoria@104.239.144.232> has joined #openstack-kuryr03:06
*** digitalsimboja <digitalsimboja!~digitalsi@105.112.46.219> has joined #openstack-kuryr05:40
*** ltomasbo <ltomasbo!~Luis@205.red-79-148-133.dynamicip.rima-tde.net> has joined #openstack-kuryr06:09
*** ltomasbo <ltomasbo!~Luis@205.red-79-148-133.dynamicip.rima-tde.net> has quit IRC (Remote host closed the connection)06:10
*** ltomasbo <ltomasbo!~Luis@205.red-79-148-133.dynamicip.rima-tde.net> has joined #openstack-kuryr06:10
*** digitalsimboja <digitalsimboja!~digitalsi@105.112.46.219> has quit IRC (Remote host closed the connection)06:53
*** digitalsimboja <digitalsimboja!~digitalsi@41.190.3.124> has joined #openstack-kuryr07:04
*** digitalsimboja <digitalsimboja!~digitalsi@41.190.3.124> has quit IRC (Ping timeout: 480 seconds)07:44
*** digitalsimboja <digitalsimboja!~digitalsi@41.190.3.157> has joined #openstack-kuryr08:23
*** Guest1685 <Guest1685!~limnoria@104.239.144.232> has joined #openstack-kuryr08:41
*** opendevmeet <opendevmeet!~limnoria@104.239.144.232> has joined #openstack-kuryr09:55
*** opendevmeet is now known as Guest168809:56
*** opendevmeet <opendevmeet!~limnoria@104.239.144.232> has joined #openstack-kuryr09:57
*** opendevmeet is now known as Guest168909:57
*** digitalsimboja <digitalsimboja!~digitalsi@197.149.87.38> has joined #openstack-kuryr09:58
*** Guest1690 <Guest1690!~limnoria@104.239.144.232> has joined #openstack-kuryr10:02
*** opendevmeet` <opendevmeet`!~limnoria@104.239.144.232> has joined #openstack-kuryr10:05
*** opendevmeet <opendevmeet!~limnoria@104.239.144.232> has joined #openstack-kuryr10:06
*** opendevmeet <opendevmeet!~limnoria@104.239.144.232> has joined #openstack-kuryr11:14
digitalsimbojaThanks all am fine11:16
*** digitalsimboja <digitalsimboja!~digitalsi@197.149.87.38> has quit IRC (Ping timeout: 480 seconds)11:57
*** jnamdar <jnamdar!~oftc-webi@static-176-139-14-39.ftth.abo.bbox.fr> has joined #openstack-kuryr13:17
*** raildo_ <raildo_!~raildo@89.38.227.174> has joined #openstack-kuryr13:20
*** raildo <raildo!~raildo@177.37.131.171> has quit IRC (Read error: Connection reset by peer)13:24
*** digitalsimboja <digitalsimboja!~digitalsi@105.112.77.90> has joined #openstack-kuryr14:03
*** digitalsimboja <digitalsimboja!~digitalsi@105.112.77.90> has quit IRC (Read error: Connection reset by peer)14:21
*** digitalsimboja <digitalsimboja!~digitalsi@105.112.26.17> has joined #openstack-kuryr14:29
digitalsimboja@ltomasbo: @ Maysams: Please assist the kill the process on the VM. mine Keyboard is hanging. Thanks14:38
ltomasbodigitalsimboja, not sure why, waht is haging is the edit/vim14:39
digitalsimbojayeah14:39
ltomasbodigitalsimboja, but you are using tmux there, so you can use tmux commands to create a new tab, and kill the process yourselfe14:40
ltomasboyourselve14:40
digitalsimbojaI tried but got a response14:40
ltomasbofor instance, you can do: Control B + %14:40
digitalsimbojanot permitted14:40
ltomasboand then check for the edit command to kill it14:40
ltomasbosee there? you have the kubectl edit klb....14:41
ltomasboso, you just need to kill that process14:41
digitalsimbojaPID14:41
ltomasbothe process belongs to the stuck user14:41
ltomasboso you cannot use the ubuntu one to kill it14:41
ltomasbounless you use "sudo"14:42
digitalsimbojaokay, noted because I tried with 'su stack' and it asks for password14:43
ltomasboyep, you need to first become root to be able to change to other users without passworkd14:44
ltomasbonot sure what you did... but the other window is stuck... just close it and keep working on the new tap14:45
ltomasboyou can move to that tab, and then close it with "contrl B + x"14:46
digitalsimboja#openstack loadbalancer delete digitalsimboja/demo --cascade?15:01
ltomasbonop15:03
digitalsimbojaPlease which handler is responsible for cleaning the openstack side?  15:03
ltomasboopenstack loadbalancer delete --cascade LOADBALANCER15:03
digitalsimbojaOhh!15:04
digitalsimbojaI think it worked?15:04
digitalsimbojaAs I can not see it again on the list15:04
ltomasbowhat do you mean? the same handlers are responsible for creating/deleting the associated OpenStack resources 15:04
digitalsimboja what do you mean? the same handlers are responsible for creating/deleting the associated OpenStack resources | Come back15:05
digitalsimbojaI dont get..15:06
digitalsimbojaYou mean lbaas is also responsible for deleting the loadbalancers?15:07
ltomasbohandlers are watching k8s resources15:07
ltomasboand that means both creation, modification and deletion of those objects15:07
ltomasboif the object is created/updated, then the on_present function gets called15:07
ltomasboif the object gets deleted then the on_delete or on_finalize functions on the handlers gets called15:07
ltomasboand it is the dutty of the handler to call the needed drivers to remove the OpenStack resources15:08
ltomasboand then remove the finalizer on the CRD/k8s object, allowing k8s to remove them15:08
digitalsimbojaLet me reclarify so I can be clear15:11
digitalsimbojaIf I want to delete the openstack resources such as deleting the loadbalancer on the openstack side:15:12
digitalsimbojaThis is handled by the on_finalize function? correct?15:12
opendevreviewSunday Mgbogu proposed openstack/kuryr-kubernetes master: Update the Handlers and the Resources  https://review.opendev.org/c/openstack/kuryr-kubernetes/+/79532215:34
maysamsdigitalsimboja: yes... once you trigger the deletion of the service the on_finilizer on the crd is called https://github.com/openstack/kuryr-kubernetes/blob/master/kuryr_kubernetes/controller/handlers/loadbalancer.py#L12715:53
digitalsimbojaI see!15:54
maysamsdigitalsimboja: I just suggested to include the deletion process on the docs as well https://review.opendev.org/c/openstack/kuryr-kubernetes/+/795363/15:57
*** ltomasbo <ltomasbo!~Luis@205.red-79-148-133.dynamicip.rima-tde.net> has quit IRC (Remote host closed the connection)16:01
digitalsimbojaGreat!16:01
digitalsimbojaI will include this also then16:02
digitalsimbojaOkay, I am clear with my observation at this stage16:03
digitalsimbojaI deleted the CRD on k8s and it disappeared on Openstack Side16:04
digitalsimbojaBut if I delete the openstack loadbalancer, it does not affect the k8s side16:04
digitalsimbojadeleting the openstack side is handled by loadbalancer on_finalize16:05
maysamsdeleting the openstack side has no impact in kuryr16:06
maysamskuryr won't notice it16:07
maysamswe only handle kubernetes events/actions16:07
maysamsnot openstack ones16:07
maysamsdigitalsimboja: ^16:07
digitalsimbojaokay got it!16:08
maysamsdigitalsimboja: any specific questions about the devref?16:09
digitalsimbojaFor now not yet, I am working on it so once I submit you could take a look to align my thoughts16:10
digitalsimbojaI needed the above clarifications16:10
maysamsok16:19
*** maysams is now known as maysams-afk16:36
*** digitalsimboja <digitalsimboja!~digitalsi@105.112.26.17> has quit IRC (Read error: Connection reset by peer)16:43
opendevreviewMerged openstack/kuryr-kubernetes master: Add golang dependency for devstack.  https://review.opendev.org/c/openstack/kuryr-kubernetes/+/79415917:40
*** raildo__ <raildo__!~raildo@177.37.131.171> has joined #openstack-kuryr17:56
*** raildo__ is now known as raildo17:57
*** raildo_ <raildo_!~raildo@89.38.227.174> has quit IRC (Ping timeout: 480 seconds)18:02
*** digitalsimboja <digitalsimboja!~digitalsi@105.112.73.231> has joined #openstack-kuryr18:26
*** digitalsimboja <digitalsimboja!~digitalsi@105.112.73.231> has quit IRC (Ping timeout: 480 seconds)19:14
*** digitalsimboja <digitalsimboja!~digitalsi@105.112.73.231> has joined #openstack-kuryr19:36
*** raildo <raildo!~raildo@177.37.131.171> has quit IRC (Quit: Leaving)19:45
*** digitalsimboja <digitalsimboja!~digitalsi@105.112.73.231> has quit IRC (Ping timeout: 480 seconds)20:14
*** maysams-afk <maysams-afk!~maysams@2a02:8308:b085:2800:b9b2:9f14:585c:eeec> has quit IRC (Ping timeout: 480 seconds)21:41

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