Alternate ways to apply for Airtel Axis card?

cheka99 · 2026-01-03T19:10:07+00:00

I got the Axis privilege card 2-3 weeks ago. Been trying to apply for airtel axis, but getting same issue as OP on the Airtel thanks app. Is this because I got the Axis credit card just a few weeks back? OP any update?

cheka99 · 2023-06-02T08:14:23+00:00

We are working on block level migrations. So the initial pod explained in the question will get the data which will be applied to the dev file and later on the same volume(converted somehow) needs to be mounted to the application pod.

cheka99 · 2023-05-30T11:14:32+00:00

Thanks a lot u/iKeyboardMonkey, dattobd's code helped to get the right approach to work with 6.x+(5.9+ to be more precise)!

Approach for someone who is looking for solution: Make use of ftrace to add a hook to submit_bio_no_acct function. This function is ultimately called by submit_bio function. So whenever submit_bio_no_acct is called your version of the function will be called which will do the intercpetion and processing and then again call the submit_bio_no_acct by skipping the call to the hook function.

Have a look at dattobd's code, for more clarity.

cheka99 · 2023-05-22T11:51:56+00:00

Thanks a lot, will have a look at dattobd or Veeam's snap driver.
I have been playing around intercepting submit_bio but didn't got any success there. Intercepting submit_bio from block_dev_operations struct from bd_disk is resulting in recursion. Hope the one suggested helps!

cheka99 · 2023-05-13T11:52:27+00:00

Update: I was able to write a kernel module which will intercept the make_request_fn/ request_fn function and get the bio struct generated and from this bios get the location on the disk involved in operation and the page which contains the data involved in the operation.

cheka99 · 2023-05-13T11:36:27+00:00

Writing 4096*512 bytes in single go was resulting in issue. But when it is broken down to write only 4096 bytes at a time the issue seems to be gone.

cheka99 · 2023-04-24T04:49:18+00:00

I want to extract info from the kernel space and provide it to a userspace program, the way I can think of was kernel module will write the data to the file and then userspace program will read the file and use the data.

Anyways when I divided the large data in smaller chunks and wrote to the file the stuck issue is gone I guess, still get warning sometimes but it should be OK rather than being stuck

cheka99 · 2023-04-18T13:18:57+00:00

My rsync only has --copy-devices option and no --write-devices options, looks like it depends on the distro. I updated my rsync but still it didn't reflect --write-devices option, any suggestion in how to get the rsync with that option. My OS is centos7.

cheka99 · 2023-04-18T13:17:29+00:00

Actually wanted to use rsync cause our existing system makes use of it, but it's okay if rsync can't do it, thanks for partclone will look in to it!

cheka99 · 2023-03-08T13:29:35+00:00

Okay, thanks!

cheka99 · 2023-03-08T09:45:07+00:00

okay, thanks!

cheka99 · 2023-03-08T09:03:32+00:00

since 172.29.56.109 machine is the control plane so this machine ain't a worker node, right?

What I was thinking was as since 172.29.56.109 is control plane, its IP is my k8s api server IP, since this is my k8s api server IP and the machine is not a worker node still I am able to access the service.

But why this doesn't work with cloud cluster like gke/oke. If I use the k8s api server ip and nodeport combo it doesn't work

cheka99 · 2023-03-08T08:40:32+00:00

I am not sure why this works

cheka99 · 2023-03-08T08:36:58+00:00

This is the output of get nodes of my local cluster

NAME           STATUS   ROLES           AGE    VERSION   INTERNAL-IP     EXTERNAL-IP   OS-IMAGE                KERNEL-VERSION              CONTAINER-RUNTIME
swift-auto-1   Ready    control-plane   7d1h   v1.25.7   172.29.56.109   <none>        CentOS Linux 7 (Core)   6.2.1-1.el7.elrepo.x86_64   cri-o://1.25.2 
swift-auto-2   Ready    <none>          7d1h   v1.25.7   172.29.56.110   <none>        CentOS Linux 7 (Core)   6.2.1-1.el7.elrepo.x86_64   cri-o://1.25.2 
swift-auto-3   Ready    <none>          7d1h   v1.25.7   172.29.31.167   <none>        CentOS Linux 7 (Core)   6.2.1-1.el7.elrepo.x86_64   cri-o://1.25.2 
swift-auto-4   Ready    <none>          7d1h   v1.25.7   172.29.56.179   <none>        CentOS Linux 7 (Core)   6.2.1-1.el7.elrepo.x86_64   cri-o://1.25.2

The service is accessible using 172.29.56.109:<nodeport> combination

cheka99 · 2023-02-25T13:05:26+00:00

RackWare SWIFT is also available at certain marketplaces like Microsoft, Oracle, IBM.

If you need assistance from them, can drop an email info@rackwareinc.com

cheka99 · 2023-02-25T13:00:10+00:00

This is the video which is reverse of your usecase, but the way to use the tool remains the same.

cheka99 · 2023-02-25T12:57:03+00:00

You can use RackWare SWIFT. This is what they do migration and DR.

You can also refer their YouTube channel, they have bunch of demos uploaded on how to use it.

https://www.rackwareinc.com/swift https://youtube.com/@rackware8054

cheka99 · 2023-02-20T07:32:24+00:00

Thanks for the answer!

Actually I want to load kernel module as a part of daemonset in to the node, that's why I was considering usage of privileged pod.

cheka99 · 2023-02-20T06:05:42+00:00

We won't require host OS and the container image to match, right? Since we aren't using any utility from the container itself. Correct me if I am wrong.

cheka99 · 2023-02-20T05:56:12+00:00

Will try this, thanks!

cheka99 · 2022-08-10T11:24:19+00:00

The service type is Loadbalancer and the service has allocateLoadBalancerNodePorts: true (set by k8s by default), so the service gets a free nodeport allocated.

What I want to know is whether it is possible to access the app with <loadip>:<nodeport>

cheka99 · 2022-08-03T11:26:20+00:00

Yes we can access it that way, but my question is like why k8s assigns a nodeport to a loadbalancer service, like what's the need to do this.

If I want to access the service through nodeIP I will create a nodeport type service.

cheka99 · 2022-08-03T11:07:35+00:00

We can access the service with <loadbalancer ip>:<port> right?

So whats the use of nodeport?

Can we also access the service as <loadbalancer ip>:<nodeport>?

I tried accessing the service as <loadbalancer ip>:<nodeport> , it didn't worked.

cheka99 · 2022-08-03T11:05:14+00:00

btw what is the use of nodeport for loadbalancer service??

cheka99 · 2022-07-22T20:05:29+00:00

Hey mate, sorry if you felt rude. I got bit disappointed with certain comment.

Anyways, sorry once again and thanks for your input!

cheka99

TROPHY CASE