Jun 2022 – Jul 2023 · 1 yr 1 mo · Bengaluru, Karnataka, India

Jul 2021 – Jun 2022 · 11 mos

• AppViewX on Cloud Provider Agnostic Managed Kubernetes
• This is an ambitious project in which we are attempting to deploy AppViewx Application in a cloud provider agnostic way i.e irrespective of whether it is GKE, EKS, AKS or Rancher. For this EKS specific technologies that we had used in our product like using S3 buckets or cluster autoscaler implementation or script based installation have to be replaced. The work is in progress.
• AppViewX on EKS
• AppViewX Installation, Upgrade and Patch facility was provided to work on Elastic Kubernetes Service provided by Amazon. In this project I along with my team had performed Istio Installation, Mongo replica orchestration, Need basis Mongo DB isolation for Performance, Implementation of HPA and Cluster Autoscaler using EKS managed Node groups, Logs synchronization using filebeat, Logs to NOC dashboard, Docker container security measures, Internal Vault implementation, Syncup with External hashicorp vault, Integration with external mongo atlas on need basis and scheduled mongo and vault backup.
• AppViewX on GCP, AWS, Azure and Hybrid Cloud and on Various OS Flavors - RHEL 8.4, CentOS and Ubuntu
• Originally AppViewX was designed to work on On-Prem and with CentOS. The idea of the project was to extend on-Prem support for these cloud providers. Most of the issues that I and my team had were on the side of Packaging, IP overlay for inter-node communication, IP bridging on the node, Fine tuning MTU from the Calico, OS specific package installation changes and OS specific terraform implementation.
• Additionally, I worked with 8 IIT KGP interns for over 3 months to clear our Tech Backlog.

Mar 2019 – Jul 2021 · 2 yrs 4 mos

• AppViewX on On-Prem and SAAS Kubernetes:
• I was part of a three member team that implemented Installation, Upgrade and Patch for AppViewX on Kubernetes. This included OS prerequisite checks, Modifying OS parameters, Installation of Docker and Kubeadm, Setting up Kube Cluster, Setting up AppViewX Infra that included Mongo, Consul and Vault and then deploying the AppViewX application. The Entire code was written in Shell, Terraform, Helm Charts and Python. The same code was later extended for Multi Node - 3 node, 4 node, 7 Node for Resiliency of Application and Kube functionality.
• Single touch, Zero Downtime UI based Plugin Upgrade.
• Implemented UI based upgrade with and without Internet using inbuilt Helm and rolling upgrade strategy. Canary deployment model was used. A similar approach was taken for Legacy where existing scripts were used for plugin upgrade.
• BugFix Porting Verification Tool
• Fixes for Bugs were needed to be ported across versions and sometimes they were missed. Inorder to solve this - We wrote a tool that collected data from Bug Portal, Release Portal and Git Code repositories to check if a bugfix is ported or not. Python Flask, AppViewX Visual Workflow for UI and GIT were the technologies involved.
• Single touch, UI based Application Upgrade for Legacy AppViewX
• Implemented UI based application upgrade with and without Internet connectivity on the node. When a setup has the internet, the package will be downloaded from AppViewX update center, which is a git repository. The artifacts in the Git repositories were used to upgrade the application. Optionally users could upload tar packages which they have downloaded from AppViewX release portal when their setup didn't have internet access.

Jan 2017 – Sep 2018 · 1 yr 8 mos · India

• eWLC client team is responsible for client specific features like security, management, policy enforcement etc for the clients on Elastic Wireless LAN controller. I worked on new Features and maintenance of existing Client features.
• Multi-Auth Feature
• The aim of the feature was to enable various L2 and L3 features in different combinations on eWLC.This included Dot1x+CWA (Central Web-Auth), Dot1x+LWA (Local Web-Auth), PSK+LWA, PSK+CWA and MAB+PSK+CWA. While the code for each of these L2 and L3 features was already present, our job was to ensure that the combination as a whole worked along with the other regular real life scenarios like Reassoc, Session timeout, Exclusion, various L2 and L3 roaming scenarios and interplay with other features like High availability and Fault tolerance.
• BYOD
• Bring Your Own Device feature. This had two parts, 1. Posture feature support from the client side and 2. BYOD single SSID and Dual SSID support. The work mainly included State machine changes.
• Apart from these, I worked on system issues like Crashes, Asserts, Memory leaks, Memory corruptions and CPU Hogs in the client code.

Apr 2013 – Sep 2015 · 2 yrs 5 mos

• Data externalization on WLC
• Worked with NGUI (Data Externalization) team to setup WLC configuration Filesystem in Userspace (FUSE). Wrote Lua scripts to automate JSON data generation from the Redis database. Wrote several Python scripts to study the XML database and configuration set, in our efforts to consolidate the amorphous configuration data of Cisco Wireless LAN controllers.
• Niagara Controllers
• I was part of a team which Worked in Niagara and ensured NIC card operability, Datapath portability and Infra portability to 8540 and 5520 Niagara Platforms for Cisco Wireless LAN controller. Our major contribution included ensuring clean manufacturing image with requisite Linux configurations and packages in place and Ensuring New model of NIC (Network Interface controller) worked with our new hardware.

Jul 2011 – Apr 2013 · 1 yr 9 mos

• High Availability for WLCs
• Worked in High Availability on Wireless Lan Controller - As part of it, we designed, developed and delivered features of optimization in boot up, infrastructure, serviceability and debuggability. We designed and implemented Configuration sync optimization between Active and Standby which reduced the need to boot the standby twice. We developed python scripts to automate code generation for configuration sync between Active and Standby controllers.
• Additionally, I owned XML configuration features for HA and mobility.

May 2010 – Jul 2010 · 2 mos · Bengaluru, Karnataka, India

• Raw fake AP(Access Point) tool was ported to work with Legacy WLC. This is to test WLC features to withstand a DoS attack from thousands of Fake APs.