Forem: Choonho Son

Mindmap Tool: A Free Mindmap SaaS service

Choonho Son — Sat, 15 Nov 2025 08:47:53 +0000

advancd.ai started as a scratch pad for visual thinkers and turned into a polished, free SaaS built by a tiny team obsessed with flow. If you spend more time prepping your canvas than capturing ideas, this one’s for you.

advancd.ai

Why it feels different

Instantly ready workspace Open the editor and a centered root node, zoom-fit canvas, and shortcut hints are already in place. No toolbars to rearrange or zoom to rescale.

Keyboard-native UX Enter toggles inline edit, Tab adds a child, A adds a standalone node, M opens the context menu near your focus, and the arrow keys walk connected nodes or edges. You can map an entire sprint with barely a mouse click.

Rich nodes and edges Images, PDFs, embeds, and draggable edge inspectors all live directly on the canvas. PDF nodes include a built-in viewer modal so you can present without popping out of the map.

Smart sharing Each map is versioned in its own Git branch (GitHub or local Git). Flip a share badge when you’re ready, or stay private in guest mode—the data lives in your repo.

Version history you can trust

Every save is a Git commit. If you ever need to revisit past thinking, the version view lets you jump back to any earlier state to inspect it before deciding what to restore.

Get started

Sign in (or stay in guest mode).
Create a map; the root node is created and auto-saved so you never lose the blank slate.
Use Tab, Enter, and M to run. Paste images or drag PDFs as needed.
When you want to share, hit save—Git commits the branch, and share badges appear in both the dashboard and editor.

Mindmap Ziin is free to use, easy to self-host, and built openly with the community. If you like mind maps that feel more like thinking and less like wrangling tooling, give it a spin and let us know what you build.

advancd.ai

The Identity of OpenStack, Keystone

Choonho Son — Fri, 27 Sep 2024 09:54:14 +0000

Keystone, the heart of OpenStack's Identity

Authentication, Authorization is the starting point of API call. IAM in AWS, GCP, or Azure is core component for Authentication and Authorization. In the OpenStack, keystone works as IAM.

I want to understand how keystone works?

The basic concept of Authentication, Authorization in the micro service architecture is 1) there is a central identity which publishs token, 2) all other micro services validate token(authentication) and check permission (authorization)

Keystone v2 and v3

Keystone v3 supports Domain and Project

Token Types

Type	Description	Support From
UUID	32-bit UUID, Just random number
FERNET	256Bytes, symmetric encryption and signing	Kilo (default since Queens)
JWS	JSON Web Token, asymmetric cryptography	Stein

Fernet and JWS has no databased backed

UUID

[token]
provider = keystone.token.providers.uuid.Provider

FERNET (Cryptographic Authentication Method)

[token]
provider = keystone.token.providers.fernet.Provider
[fernet_tokens]
key_repository = /etc/keystone/fernet-keys/
max_active_keys = <number of keys> # defaults is 3

JWS (JSON Web Signature)

a type of JWT (JSON Web Token)

[token]
provider = jws
[jwt_tokens]
jws_public_key_repository = /etc/keystone/jws-keys/public
jws_private_key_repository = /etc/keystone/jws-keys/private

Token Scope

Type	Description
Un-scoped	-
System	interacting with resources at the system level, usually admin only
Domain	Users and Groups
Project	users to work on items that fit withinn a project scope

Reference

Integrating Keystone with large-scale centralized authentication

How OpenStack's Keystone handles authentication and authorization

https://www.redhat.com/sysadmin/keystone-identity-openstack

Deep Dive into Keystone Tokens and Lessons Learned

https://www.slideshare.net/slideshow/deep-dive-into-keystone-tokens-and-lessons-learned/54414862

Keystone JWS Tokens Past, Present, and Future

A Complete Guide to OpenID Connect in OpenStack

Nitro Card, Why AWS is best!

Choonho Son — Fri, 28 Jun 2024 07:47:03 +0000

One of my interesting area is a virtualization. It is very complicated area in computer science and hardware. Why AWS is so special compared with Google Cloud and Microsoft Azure. Some people said that "First Mover Advantage"

Generally speaking, Yes. But from the point of computer scientist, I think AWS Nitro is the key technology. There is no similar technology in Google Cloud and Microsoft Azure. But the detailed information is not well documented. I want to summarize the Nitro Card. This is my understanding from the AWS re-invent.

Secret Sauce, Annapurna Labs

In Early 2010, the performance of AWS EC2 instance was not different other Companies, since commodity hardware and open-source Xen hypervisor would have been used. To overcome the performance bottleneck of virtualization, IO virtualization was the key technical area. At that time, everyone said about SR-IOV for network interface.

In 2015, the partnership opportunity between AWS and Annapurna Labs launched AWS EC2 C4 instance family, the network virtualization to custom hardware and ASIC optimized for storage services.

In 2016, Amazon announced that it is acquiring the Israeli startup, Annapurna Labs.

With Annapurna Labs, AWS introduced Storage Virtualization.

EC2 C4 instance type

EC2 C4 has traditional Xen hypervisor and Intel SR-IOV.
In C4 instance type, block storage looks like scsi disk not NVMe.



  
  
  Hypervisor Info


[    0.000000] DMI: Xen HVM domU, BIOS 4.11.amazon 08/24/2006

[    0.000000] Hypervisor detected: Xen HVM

[    0.000000] Xen version 4.11.

  
  
  Block Device


[    0.858936] blkfront: xvda: barrier or flush: disabled; persistent grants: disabled; indirect descriptors: enabled; bounce buffer: disabled;

[    0.859416] scsi host1: ata_piix

[    0.863963] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14 lpm-pol 0

[    0.866375] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc008 irq 15 lpm-pol 0

[    0.867267]  xvda: xvda1 xvda14 xvda15 xvda16

  
  
  SR-IOV intel NIC


[    4.511853] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver

[    4.511857] ixgbevf: Copyright (c) 2009 - 2018 Intel Corporation.

[    4.535946] ixgbevf 0000:00:03.0: 02:64:96:26:40:13

[    4.535949] ixgbevf 0000:00:03.0: MAC: 1

[    4.535951] ixgbevf 0000:00:03.0: Intel(R) 82599 Virtual Function

PCI Devices



root@ip-172-31-30-241:~# lspci

00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC Natoma

00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]

00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]

00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 01)

00:02.0 VGA compatible controller: Cirrus Logic GD 5446

00:03.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01)

00:1f.0 Unassigned class [ff80]: XenSource, Inc. Xen Platform Device (rev 01)

In EC2 C4 instance type, there is no Nitro System.

Intel 82599 10GbE

Key	Description
Name	Intel 82599 10G gigabit Ethernet Controller
Launch Date	Q2'09
Lithography	65 nm
System Interface Type	PCIe v2.0 (5.0 GT/s)

EC2 C5 Instance

AWS Nitro System was adopted from EC2 C5 instance.
With the Nitro System, AWS changed the hypervisor from Xen to KVM.



  
  
  KVM Hypervisor


[    0.000000] efi: EFI v2.7 by EDK II

[    0.000000] efi: SMBIOS=0xbbe6a000 ACPI=0xbbf5d000 ACPI 2.0=0xbbf5d014 MEMATTR=0xba3f0518 MOKvar=0xbbe58000 INITRD=0xb9ecdf18

[    0.000000] secureboot: Secure boot disabled

[    0.000000] SMBIOS 2.7 present.

[    0.000000] DMI: Amazon EC2 c5.large/, BIOS 1.0 10/16/2017

[    0.000000] Hypervisor detected: KVM

[    0.014734] Booting paravirtualized kernel on KVM

[    0.202690] smpboot: CPU0: Intel(R) Xeon(R) Platinum 8275CL CPU @ 3.00GHz (family: 0x6, model: 0x55, stepping: 0x7)

  
  
  NVMe


[    0.455535] nvme nvme0: pci function 0000:00:04.0

[    0.465281] nvme nvme0: 2/0/0 default/read/poll queues

[    0.469270]  nvme0n1: p1 p14 p15 p16

[    0.992904] EXT4-fs (nvme0n1p1): mounted filesystem 6387caa1-122f-48bc-b447-9f1386d06e06 ro with ordered data mode. Quota mode: none.

[    2.899354] EXT4-fs (nvme0n1p1): re-mounted 6387caa1-122f-48bc-b447-9f1386d06e06 r/w. Quota mode: none.

[    3.729719] EXT4-fs (nvme0n1p16): mounted filesystem 9d39f3ff-b465-4c20-9ec1-06182226356c r/w with ordered data mode. Quota mode: none.

  
  
  Elastic Network Adaptor


[    3.409564] ena 0000:00:05.0: ENA controller version: 0.0.1 implementation version 1

[    3.430162] ena 0000:00:05.0: Elastic Network Adapter (ENA) found at mem c0510000, mac addr 06:4e:11:f5:80:6b

[    3.466230] ena 0000:00:05.0 ens5: renamed from eth0

PCI Devices



root@ip-172-31-44-203:~# lspci

00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma]

00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]

00:01.3 Non-VGA unclassified device: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)

00:03.0 VGA compatible controller: Amazon.com, Inc. Device 1111

00:04.0 Non-Volatile memory controller: Amazon.com, Inc. NVMe EBS Controller

00:05.0 Ethernet controller: Amazon.com, Inc. Elastic Network Adapter (ENA)

NVMe



00:04.0 Non-Volatile memory controller: Amazon.com, Inc. NVMe EBS Controller (prog-if 02 [NVM Express])

Subsystem: Amazon.com, Inc. NVMe EBS Controller

Physical Slot: 4

Latency: 0

...

Interrupt: pin A routed to IRQ 11

Region 0: Memory at c0514000 (32-bit, non-prefetchable) [size=16K]

Capabilities: [70] Express (v2) Endpoint, MSI 00

PBA: BAR=0 offset=00003000

Kernel driver in use: nvme

AWS ENA Network Interface Card

ENA does not provide Link Speed. From the Linux Kernel, single ENA driver can provides 10GbE, 25GbE, or 40GbE.



00:05.0 Ethernet controller: Amazon.com, Inc. Elastic Network Adapter (ENA)

Physical Slot: 5

...

Capabilities: [b0] MSI-X: Enable+ Count=9 Masked-

Vector table: BAR=0 offset=00002000

PBA: BAR=0 offset=00003000

Kernel driver in use: ena

Kernel modules: ena

AWS Nitro Server

2023 AWS re-invent, AWS describe the Nitro Server in "A Deep dive on AWS infrastructure powering the generative AI boom", https://d1.awsstatic.com/events/Summits/reinvent2023/CMP201_A-deep-dive-on-AWS-infrastructure-powering-the-generative-AI-boom.pdf

There are two Nitro Cards, 1x primary and 1x networking.

From the image and form factor, this nitro card is nitro v3. But these two nitro cards have a little different from size and color.

Front panel cabling: most of commodity server has back panel cabling. But AWS has front panel cabling.
No Power Unit: in the back side there is no power unit. This means AWS Nitro server uses DC power instead of AC.
No SSD: From the image, I can't find any SSD like NVMe. This means the root volume of EC2 instance is not located at local SSD. Nitro Card provides Instance Store remotely.

After watching two different Nitro Cards, my question was what is the functionality of each Nitro Cards?

The hint can be founded in AWS Outpost.

Nitro Cards cabling

AWS Outpost uses same hardware in AWS Data Center.

IPMI UTP cable: Left green UTP cable is IPMI port
Orange UTP in left Nitro Card: Nitro Controller APIs. EC2 control plane network.

From the above feature, there is a EC2 VM with single ENA, EBS, Local Storage. The Local Storage and EBS may be processed by right Nitro Card. The ENA may be processed by left Nitro Card.

No 802.11ad Bonding interface

One of hardware challenges are no redundancy for Nitro Card failure. Commodity server usually make bonding interface coupling two physical interfaces to single logical interface. But AWS Nitro Server does not make bonding interface.
But this is an understandable architecture, since network interface and storage device are PCIe devices with SR-IOV.

Hidden Technology, PCIe with single root complex

Remote NVMe via Nitro Card is one of the key technologies in AWS.

In the commodity hardware and standard, we need PCIe switch and separate PCI express networking equipments with MR-IOV (multi root complex) support. But Nitro Card do all these features in the Ethernet networking.

Who is the next Annapurna Labs

We call this kind of Nitro Card as SmartNIC or DPU(Data Processing Unit),a new class of programmable processor.

Nvidia BlueField-3

Nvidia acquired Mellanox in 2020

AMD Pendando DSC

AMD acquired Pensando for its DPU Future in 2022

Apple Silicon, State-of-the-art ARM CPU

Choonho Son — Fri, 21 Jun 2024 02:12:03 +0000

My Macbook air has M2 CPU. I want to deploy my Cloudforet application in my Macbook. But we have only X86 docker image, because github does not support ARM linux runner for github action. There is a way for building X86 and ARM docker image in one command, but it takes too much time. Because it is a cross compilation for ARM image build in X86 machine.

Suddenly, I just want to know about ARM CPU.

Apple Silicon

CPU Version	ARM Instruction Set	Manufacturer	Release Date
Apple M1	ARMv8.5-A (3.2 GHz)	5nm TSMC	Nov. 2020
Apple M2	ARMv8.6-A (3.49 GHz)	5nm TSMC	Jun. 2022
Apple M3	ARMv8.6-A (4.05 GHz)	3nm TSMC	Oct. 2023
Apple M4	ARMv9.2-A	3nm TSMC	May 2024

AWS

AWS provides Graviton instance

CPU Version	ARM Instruction Set	Manufacturer	Release Date
Graviton	ARMv8-A (2.3 GHz)	16nm TSMC	Nov. 2018
Graviton2	ARMv8.2-A (2.5 GHz, Neoverse N1)	7nm TSMC	Dec. 2019
Graviton3	ARMv8.4-A (2.6 GHz, Neoverse v1)	5nm TSMC	May 2022
Graviton4	ARMv9.0-A (2.7 GHz, Neoverse v2)	4nm TSMC

In EC2 instances, 7 generation is Graviton3, 8 generation is Graviton4.
For example c7g.large is 2 vcores, 4GB memory Graviton3 CPU instance.

Google Cloud

Google Cloud also provides ARM VM.

CPU Version	ARM Instruction Set	Manufacturer	Release Date
Ampere Altra	ARMv8.2-A (3.0 GHz, Neoverse N1)	7nm TSMC	July 2022
Axion	ARMv9.0-A (Neoverse V2)	TSMC	Apr. 2024

Apple, State-of-the-art

From the ARM Instruction Set and Manufacturing technology, Apple adopts the latest technology in the world. The clock speed of Apple Silicon is unbelievable.

Is it real?

In MacOS, "sudo powermetrics" can see the System Information. From the log, CPU speed is adaptive on workload. In Apple Silicon, there are two type of CPUs. E-Cluster and P-Cluster. E means "efficiency" and P means "Performance".



**** Processor usage ****

E-Cluster HW active frequency: 999 MHz
CPU 0 frequency: 1113 MHz
CPU 1 frequency: 1079 MHz
CPU 2 frequency: 1082 MHz
CPU 3 frequency: 1132 MHz

P-Cluster HW active frequency: 711 MHz
CPU 4 frequency: 2249 MHz
CPU 5 frequency: 2137 MHz
CPU 6 frequency: 3058 MHz
CPU 7 frequency: 2624 MHz

What is Neoverse?

Neoverse is an ARM CPU architecture for server-class for datacenter, edge-computing, and high-performance computing.

Neoverse V2 CPU

Who design custom ARM CPU?

AWS and Google has their own ARM CPU, Graviton, Ampere and Axion.

Annapururna Labs

Amazon acquires Annapururna Labs, an Israeli microelectronics company in January 2015. Annapururna Labs launched AWS Nitro hardware, Graviton, Trainium, and Inferentia.

Ampere Computing

Google Cloud and Azure uses Ampere Altra ARM CPU, which is designed by Ampere Computing LLC.

Ampere Computing is an American fabless semiconductor company founded in 2017. Renne James is CEO, ex-President of Intel.

Google Silicon

Google also has their own Silicon design team, they launched Tensor Processing Units in 2015. Google's first ARM-based CPU is Axion

Intel's alien moved to ARM

Intel has been an indispensable company in CPU design, there were rumors that Intel CPUs were designed by aliens. Now that alien moved to ARM!

Intel Corp Stock Market

ARM Stock Market

Develop in Macbook Apple Silicon, Launch ARM Kubernetes.

Cloudforet 101: Provider & Service Accounts

Choonho Son — Wed, 19 Jun 2024 08:19:59 +0000

In the Cloudforet a series of LinuxFoundation Open Source Project, the key concept for resources is "Provider" and "Service Account"

Overview

A provider is the overarching entity that offers resources, within which multiple service accounts exist. These service accounts are used to securely and efficiently access the resources provided by the provider.Concept of Provider and Service Accounts

User Experience: Console

In the Cloudforet console web page, Provider and Service Accounts can be seen at "Home > Asset Inventory > Service Account"

Provider

In the context of Cloudforet, a provider is a top-level entity that groups a range of resources. Providers can include cloud providers like Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure, as well as any entity that groups together like software_licence.

Service Account

A service account functions as an identifier for a group of resources within a provider. This means that the service account is used as primary key for distinguishing a specific set of resources.

References

https://cloudforet.io/docs/concepts/identity/provider/
cloudforet: https://cloudforet.io

Discord Webhook

Choonho Son — Tue, 11 Jun 2024 06:31:10 +0000

Discord webhooks are a powerful way to send messages and updates from external sources into your Discord channels. Whether you're integrating with a CI/CD pipeline, receiving alerts from a monitoring system, or simply automating messages, webhooks are an efficient solution. In this blog post, we'll walk you through the process of creating a webhook in Discord and how to send messages to it.

Step 1. Create Webhook

1.1 Open Your Discord Server
First, navigate to the Discord server where you want to create the webhook. You must have the appropriate permissions to manage webhooks in the channel.

1.2 Access Channel Settings
Go to the specific channel where you want the webhook to send messages. Click on the gear icon (⚙️) next to the channel name to open the channel settings.

1.3 Navigate to Integrations
In the channel settings, select the "Integrations" tab from the sidebar. Here, you’ll see an option to create a new webhook.

1.4 Create a Webhook
Click the "Create Webhook" button. You’ll be prompted to set up your webhook:

Name: Choose a name for your webhook. This will be displayed as the sender of the messages.
Channel: Select the channel where the messages will be sent. By default, it’s the channel you accessed the settings from.
Avatar: Optionally, you can set an avatar for your webhook.

1.5 Copy Webhook URL
After setting up your webhook, click the "Copy Webhook URL" button. This URL is crucial as it will be used to send messages to this webhook.

Step 2: Sending Messages to the Webhook

Now that you have your webhook URL, you can send messages to it using a simple HTTP POST request. Here's a basic example using Python and the requests library.

import requests

webhook_url = 'YOUR_WEBHOOK_URL'

embed = {
    "title": "Sample Embed",
    "description": "This is an example of an embedded message.",
    "color": 16711680,  # Red color in RGB
    "fields": [
        {"name": "Field 1", "value": "This is field 1", "inline": True},
        {"name": "Field 2", "value": "This is field 2", "inline": True},
    ]
}

data = {
    "content": "This message contains an embed.",
    "embeds": [embed]
}

response = requests.post(webhook_url, json=data)

if response.status_code == 204:
    print("Message sent successfully!")
else:
    print(f"Failed to send message: {response.status_code}")

Output looks like

References

https://discord.com/developers/docs/resources/channel#embed-object

Best Practice: Micro Service Architecture

Choonho Son — Thu, 06 Jun 2024 02:04:43 +0000

Cloudforet, a series of LinuxFounation Open Source projects is one of the best practice for Micro Service Architecture and Cloud Native.

Micro Service Architecture

Cloudforet adopts a microservice architecture to provide a scalable and flexible platform. The microservice architecture is a design pattern that structures an application as a collection of loosely coupled services. Each service is self-contained and implements a single business capability. The services communicate with each other through well-defined APIs. This architecture allows each service to be developed, deployed, and scaled independently.

The frontend is a service provided for web users, featuring components such as console and console-api that communicate directly with the web browser. The core logic is structured as independent microservices and operates based on gRPC to ensure high-performance and reliable communication.

Each core logic can be extended by plugin services. Every plugins are developed and deployed independently, and they can be added, removed or upgraded without affecting the core logic.

API-Driven design

API-Driven design in microservice architecture is a pattern where APIs (Application Programming Interfaces) are the primary way that services interact and communicate with each other. This approach emphasizes the design of robust, well-defined, and consistent APIs that serve as the contracts between microservices. Here’s a detailed explanation of the API-Driven design pattern:

gRPC as the Communication Protocol

gRPC is a high-performance, open-source, universal RPC (Remote Procedure Call) framework that is widely used in microservice architectures. It uses HTTP/2 as the transport protocol and Protocol Buffers (protobuf) as the interface definition language. gRPC provides features such as bidirectional streaming, flow control, and authentication, making it an ideal choice for building efficient and reliable microservices.

Loose Coupling

API-Driven design promotes loose coupling between microservices by defining clear and well-documented APIs. Each microservice exposes a set of APIs that define how other services can interact with it. This allows services to evolve independently without affecting each other, making it easier to develop, deploy, and maintain microservices.

Version control

Cloudforet APIs support two types of versioning, core and plugin version. Core version is for communication between micro services for frontend. plugin version of internal communication in a single micro services for implementing API.

API Documentation https://cloudforet.io/api-doc/

Protobuf API Specification https://github.com/cloudforet-io/api

Service-Resource-Verb Pattern

API-Driven design can be effectively explained using the concepts of service, resource, and verb. Here’s how these concepts apply to microservices:

Service

A service in microservice architecture represents a specific business functionality. Each service is a standalone unit that encapsulates a distinct functionality, making it independently deployable, scalable, and maintainable. Services communicate with each other over a network, using lightweight protocols gRPC.

Example: in the Cloudforet, individual services are identity, repository, or inventory.
- identity service: manages user authentication and authorization.
- repository service: manages the metadata for plugins and their versions.
- inventory service: manages the resources and their states.

Resource

A resource represents the entities or objects that the services manage. Resources are typically data entities that are created, read, updated, or deleted (CRUD operations) by the services.

Example: in the identity Service, resources include Domain, User, and Workspace.
- Domain: represents a seperated organization or customer.
- User: represents a user account.
- Workspace: represents a logically isolated group contains resources.

Verb

A verb represents the actions or operations that can be performed on resources. These are typically the gRPC methods (get, create, delete, update, list, etc.) in a service. Verbs define what kind of interaction is taking place with a resource.

Example: in the User resource, verbs include create, get, update, delete, and list.
- create: creates a new user.
- get: retrieves the user information.
- update: updates the user information.
- delete: deletes the user.
- list: lists all users.

Reference

Cloudforet https://cloudforet.io
Cloudforet github https://github.com/cloudforet-io

[Cloudforet] Enable Azure Billing Plugin

Choonho Son — Mon, 20 May 2024 08:08:19 +0000

Azure Billing Plugin(Ver 1.1.12) is compatible for Cloudforet Ver 1.12

1. Register Azure Billing DataSource Plugin

Create azure_data_source.yaml

---
name: Azure Cost Management Data Source
data_source_type: EXTERNAL
provider: azure
secret_type: MANUAL
plugin_info:
  plugin_id: plugin-azure-cost-mgmt-cost-datasource
  secret_data:
    client_id: 4e56b0f1-XXXXXXXXXXX
    client_secret: V.18Q~YYYYYYYYYYYYYY
    tenant_id: 8f97eaee-TTTTTTTTTTTTTTT
    billing_account_id: 9fd31315BBBBBBBBBBBBBBBBBB
  options:
    collect_resource_id: true
    currency: USD
  version: 1.1.12
  upgrade_mode: MANUAL

To register DataSource

spacectl exec register cost_analysis.DataSource -f azure_data_source.yaml

2. Sync DataSource

spacectl exec sync cost_analysis.DataSource -p data_source_id=<Data Source ID>

References

client_id, client_secret: https://github.com/cloudforet-io/plugin-azure-inven-collector/tree/master/docs/en
billing_account_id: https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/view-all-accounts#scopes-for-billing-accounts

Cloudforet for Production

Choonho Son — Mon, 13 May 2024 01:55:26 +0000

This guide is for Installation of Cloudforet for Production.

On-premise Kubernetes
MongoDB Atlas SaaS

Architecture

Pre-requisite

Kubernetes

Install your own Kubernetes Clusters

Nginx Ingress

https://kubernetes.github.io/ingress-nginx/deploy/

helm upgrade --install ingress-nginx ingress-nginx \
  --repo https://kubernetes.github.io/ingress-nginx \
  --namespace ingress-nginx --create-namespace

MongoDB Cluster

Case 1) MongoDB Atlas

Case 2) MongoDB self-hosted (Helm Chart)

Domain Name

Prepare your domain name (In this guide, example.com)

Certificates

https://dev.to/choonho/install-cert-manager-lets-encrypt-443b

SMTP Server

For sending email notification

https://www.gmass.co/blog/gmail-smtp/

Survey on the Feasibility of AI Ops Agents Replacing Human Tasks?

Choonho Son — Thu, 02 May 2024 00:39:00 +0000

This question aims to investigate the feasibility of Artificial Intelligence Operations (AI Ops) agents replacing human tasks. Your valuable participation will help increase understanding in this field and provide insights into future job transformations.

Q-1. To what extent do you believe AI Ops agents can replace human tasks?
a) Completely replaceable
b) Replaceable to some extent, but not entirely
c) Hardly replaceable
d) Not replaceable at all

Q-2. Which types of tasks do you think are most suitable for AI Ops agents? (Multiple choices possible)
a) Data analysis and prediction
b) Incident management and troubleshooting
c) Automated operational tasks
d) Security and compliance
e) Customer support and service desk
Other (please specify)

https://forms.gle/QQYhS6HQXiLoUiA67

What is Next Item after Terraform?

Choonho Son — Thu, 25 Apr 2024 06:20:20 +0000

The transition to the cloud-native era is reshaping today's IT landscape. Consequently, enterprises are adopting hybrid and multi-cloud strategies, utilizing multiple cloud platforms and on-premises infrastructure rather than relying solely on a single cloud platform. To manage and optimize this complexity, integrated tools and platforms are necessary.

Infrastructure as Code (IaC) tools like Terraform are incredibly useful for provisioning and managing cloud infrastructure. However, in cloud-native environments, management extends beyond infrastructure operations to include areas such as application deployment, monitoring, security, and regulatory compliance. For this reason, enterprises are looking beyond simply provisioning infrastructure and are adopting Multi-Cloud Management Platforms (MCMPs) and similar tools to comprehensively manage and optimize both cloud infrastructure and applications.

IBM's acquisition of Terraform reflects these market trends. It is expected that IBM will leverage Terraform's capabilities to develop and integrate multi-cloud management platforms. While Terraform will continue to play a significant role in creating and managing infrastructure, integration with tools like MCMPs will be necessary in cloud-native environments.

Therefore, in the future of cloud management, tools like Terraform and MCMPs are expected to be used together to effectively manage both cloud infrastructure and applications.

One of the best combination with Terraform will be Cloudforet, An open-source LinuxFoundation Project.

https://cloudforet.io

How to Get and Apply AWS Credits: A Step-by-Step Guide

Choonho Son — Mon, 25 Mar 2024 01:30:40 +0000

1. What are AWS Credits?

AWS credits are a monetary value that can be used to pay for AWS services. AWS offers credits to new and existing customers through various promotional programs.

2. How to Get AWS Credits

AWS Promotions: AWS offers various promotional programs that provide AWS credits. You can check the current promotions on the AWS website.
AWS Partners: You can also get AWS credits through AWS partners.
AWS Training: You can earn AWS credits by completing AWS training courses.

3. How to Apply AWS Credits

Log in to the AWS Management Console. (by ROOT account)
Select Billing and Cost Management Service.
Find the Credits section.
Click Redeem credit.
Enter your Credit Code.

Use within Expiration Date

Each credit has its own expiration date.