Pages

Showing posts with label cloud computing. Show all posts
Showing posts with label cloud computing. Show all posts

Saturday, September 30, 2023

Database Admin - Kubernetes cheat sheet

 Kubernetes cheat sheet


Listing the below commands which will be useful for administering the kubernetes environment.

 

Version:

# Get kubernetes version: The Server Version line indicates the version of Kubernetes that is running on the Kubernetes cluster.

kubectl version


Pods:

# Get the details of all pods in one namespace

kubectl get pods -n <namespace>


#  Get the details of all pods in all namespaces

kubectl get pods --all-namespaces 


#  Get the details of all pods in the current namespace, with more details

kubectl get pods -o wide  




Deployments:

# Get all  the deployments 

kubectl get deployments


# Check the history of deployments including the revision

Kubectl rollout history deployment <deployment name>


# Rolling  restart of the deployment

Kubectl rollout restart deployment <deployment name>



Interacting with pods:

# Login to pod

Kubectl exec -it <podname> -- bash


#Run the commands in the pod

Kubectl exec <podname> -- ls /





configmap :


# Get all configmap in current namespace

Kubectl get cm


# Edit configmap 

Kubectl edit cm <configmap name>


Secrets:


# Display all the secrets 

Kubectl get secrets


# Display all the secrets 

Kubectl get secrets --all-namespaces 



Services:


# Display all the services 

Kubectl get svc


# List Services Sorted by Name

kubectl get services --sort-by=.metadata.name



Logs:

# Check the logs of the pod

kubectl logs <podname>


# Tail the logs of the pod

kubectl logs -f <podname>


Copy :

# copy  the data from local directory to  the pod

kubectl cp $HOME/data <pod>:/opt/app/data



Storage:


# List all PersistentVolumes

kubectl get pv


# List all PersistentVolumes sorted by capacity

kubectl get pv --sort-by=.spec.capacity.storage


# Describe specific persistent volume

kubectl describe pv <pv_name>


# List all persistent volumes claims

kubectl get pvc


# Describe specific persistent volume claim

kubectl describe pvc <pvc_name>



Create/Delete resources:



# Create specific resource

kubectl apply -f <deployment>.yaml


# Create specific resource using URL

kubectl apply -f https://gcs.io/pod


# Describe specific persistent volume claim

kubectl delete -f <deployment>.yaml



Formatting output:


# Append the following to command to get output in json format 


-o json  


# Append the following to command to get output in yaml format 


-o yaml


# Append the following to command to get output in plain text format with additional information for pods.


-o wide


# Print a table using a comma separated list of custom columns


-o=custom-columns=<spec> 


Cluster details:


# Display the cluster details


kubectl cluster-info


Below bash alias are more useful:


    alias k="kubectl"

    alias allpods="kubectl get pods --all-namespaces"

    alias kc="kubectl create -f"

    alias kg="kubectl get"

    alias pods="kubectl get pods"

    alias ktop="kubectl top nodes"

    alias rcs="kubectl get rc"

    alias sv="kubectl get services"

    alias dep="kubectl get deployment"

    alias kd="kubectl describe"

    alias kdp="kubectl describe pod "

    alias kds="kubectl describe service "

    alias nodes="kubectl get nodes"

    alias klogs="kubectl logs"

    alias ns="kubectl get ns"

    alias deploys="kubectl get deployment"

    alias events="kubectl get events"

    alias kexec="kubectl exec -it "

    alias sec="kubectl get secrets"

 


Friday, August 4, 2023

RCLONE - Data migration from on-premise to cloud using rclone tool

  Data migration from on-premise to cloud using rclone tool


Recently we had a requirement to migrate our on-premise data around 70TB from swift storage to aws s3 bucket.  We have initially explored various options to migrate, out of which we have chosen rclone for data migration, because it supports a wide range of cloud storage providers, including Google Drive, Dropbox, Amazon S3, and Microsoft OneDrive.


Why RCLONE ?


Rclone is mature, open-source software originally inspired by rsync and written in Go. It is multi threaded, very fast in transfer and allows to control the transfer speed.

Here is a summary of the Rclone equivalents to the Unix commands:


rsync: Rclone sync is a powerful tool for synchronizing files and directories between your local machine and the cloud. It can be used to create backups, mirror directories, or simply keep your local and cloud data in sync.

cp: Rclone copy is a simple tool for copying files and directories from your local machine to the cloud or vice versa.

mv: Rclone move is a simple tool for moving files and directories from one cloud storage provider to another.

mount: Rclone mount allows you to mount a cloud storage bucket as a directory on your local machine. This means that you can access your cloud files as if they were stored on your local hard drive.

ls: Rclone ls lists the contents of a cloud storage bucket.

ncdu: Rclone ncdu displays the disk usage of a cloud storage bucket.

tree: Rclone tree displays a tree view of the contents of a cloud storage bucket.

rm: Rclone rm removes files and directories from the cloud.

cat: Rclone cat displays the contents of a file in the cloud.



How to configure rclone and use?


Here am providing the configuration for amazon s3, we can follow the steps outlined below, also refer https://rclone.org/s3/


  1. Download the rclone software for your respective OS - https://rclone.org/downloads/

  2. Run “rclone config”, it will guide you through an interactive setup process.

Source configuration : https://rclone.org/swift/

Target configuration : https://rclone.org/s3/#configuration

  1. Validate the details in the configuration file (~/.config/rclone/rclone.conf) in your local machine and ensure you are able to connect to the source and target using rclone.



$ cat ~/.config/rclone/rclone.conf

[onprem_swift]

type = swift

env_auth = true

user = my_object_store

key =

auth = https://swift.company.com/auth/v1.0

domain =

tenant = my_object_store

tenant_domain =

region =

storage_url =

auth_version =

endpoint_type = public



[cloud-aws-s3]

type = s3

provider = AWS

access_key_id = <aws s3 access key id>

secret_access_key = < secret key>

region = us-east-2

location_constraint = us-east-2

acl = private

storage_class = STANDARD


Display the directories in swift/s3 buckets

[user@host01 ~]$ rclone lsd cloud-aws-s3:prod

           0 2023-10-28 02:33:56        -1 data

           0 2023-10-28 02:33:56        -1 images

[user@host01 ~]$ rclone lsd cloud-aws-s3:prod

           0 2023-10-28 02:33:56        -1 data

           0 2023-10-28 02:33:56        -1 images




  1. Now we are good to transfer the data, let do it


[user@host01 ~]$ rclone sync --progress --transfers=8 --bwlimit=10M onprem_swift:prod cloud-aws-s3:prod


[user@host01 ~] $ ps -ef|grep rclone

user+ 4018633       1  7 00:05 pts/0    00:00:26 rclone sync --progress onprem_swift:prod cloud-aws-s3:prod

user+ 4047166 2812493  0 00:11 pts/0    00:00:00 sh rclone_prod.sh

user+ 4047172 4047166 29 00:11 pts/0    00:00:11 rclone sync --progress onprem_swift:prod cloud-aws-s3:prod

user+ 4050901 2812493  0 00:11 pts/0    00:00:00 grep --color=auto rclone

[user@host01 ~]$



By using the rclone tool, we will have more control in transferring the data in parallel and very easy to use as all the commands are like unix commands. 


Best Practices:


  1. We have tried various options to speed up transfer between swift and aws s3, however we did not get the right speed to transfer. Later we analyzed the details thoroughly and decided to create aws s3 bucket in close to the region that we are in i.e us-east2 region and we have used around 5 machines to transfer in parallel, these significantly helped to speed up the migration process with average speed between 40mb/sec and 90mb/sec. 


  1. I recommend to use its latest version, it has a great support community  which we can make use of for posting our issues to get immediate assistance from the forum.

Wednesday, August 2, 2023

.


Tuesday, January 31, 2023

OCI Cloud - Top 10 things to consider when deploying applications.

Deploying applications on Oracle Cloud Infrastructure (OCI) involves several best practices to ensure efficiency, scalability, security, and reliability. Here are some key practices for OCI cloud deployments:

1. Well-Architected Framework:

Reliability, Performance, Security: Follow OCI's well-architected framework principles to design and implement your solutions for reliability, performance, and security.

2. Resource Planning and Optimization:

Right Sizing: Properly size compute, storage, and networking resources to meet application demands while avoiding unnecessary costs.

Utilize Autoscaling: Configure auto-scaling policies to dynamically adjust resources based on traffic patterns.

Cost Management: Leverage Oracle's tools for cost management and monitoring to optimize expenses.

3. Security Best Practices:

Identity and Access Management (IAM): Implement least privilege access control, utilize IAM policies, and regularly review permissions.

Network Security: Use Virtual Cloud Networks (VCNs), security lists, and security groups to control network traffic.

Data Encryption: Encrypt data at rest and in transit using encryption services provided by OCI.

4. High Availability and Fault Tolerance:

Multi-Availability Domains (ADs) and Regions: Deploy across multiple availability domains and regions to ensure high availability and disaster recovery.

Load Balancing: Use Load Balancers to distribute traffic across multiple instances for fault tolerance.

5. Automated Deployments:

Infrastructure as Code (IaC): Use tools like Terraform or Oracle's Resource Manager to define and provision infrastructure, ensuring consistency and repeatability.

CI/CD Pipelines: Implement continuous integration and deployment pipelines for automated testing and deployment.

6. Monitoring and Logging:

Monitoring Services: Use OCI Monitoring and Notifications to set up alerts and monitor resources, enabling proactive issue resolution.

Logging: Centralize logs using OCI Logging to facilitate troubleshooting and security auditing.

7. Backup and Disaster Recovery:

Backup Strategies: Implement regular backups of critical data and ensure their integrity.

Disaster Recovery Plans: Have well-defined plans for disaster recovery, including backup restoration and failover procedures.

8. Compliance and Governance:

Compliance Standards: Adhere to relevant compliance standards (e.g., GDPR, HIPAA) and regularly audit configurations.

Governance Policies: Establish governance policies for resource tagging, naming conventions, and access controls.

9. Performance Optimization:

Content Delivery Networks (CDN): Utilize OCI's CDN for caching and delivering content closer to end-users, enhancing performance.

Optimize Database Performance: Utilize OCI's database tuning and optimization features for improved performance.

10. Documentation and Training:

Documentation: Maintain detailed documentation of configurations, deployments, and best practices.

Training and Knowledge Sharing: Continuously educate and train teams on new features, best practices, and security measures within OCI.

Implementing these best practices will help in creating robust, secure, and efficient deployments on Oracle Cloud Infrastructure. Tailor these practices based on specific application requirements and stay updated with OCI's latest features and improvements for continual enhancement.