[NOT BUG or FEATURE] merge demo25 branch to main

[youngtaekiim]

Shutdown demo25 branch

As a preliminary step for shutting down the demo25 branch, we'll move the commits in main to the demo25 branch.

• Step 1: main -> demo25
• Step 2: Review the demo25 branch (with LGSI)
• Step 3: Merge PRs from demo25 to main and delete the demo25 branch.

Step 1 is completed by #397
Step 2 : TBD
Step 3 : TBD

Check list

• build 구조 변경에 따른 github workflow 파일 (test case 검증 빼고는 어느정도 정리 해놓음)
• etcd --> rocksdb 변경에 따른 관련 TC 코드 수정

[akshaylg0314]

Hey @youngtaekiim @daeyoung-jeong-lge
can you please guide me for rocks DB setup is there any prerequites for rocks db to use like ETCD, So tha i can change the Github workflow accordingly
thanks!!

[youngtaekiim]

@akshaylg0314
I hope it doesn't start yet. There are so many changes in demo25 branch. I've done the basic GH actions work.

And there will also be a big change as we are working on removing the bluechi dependency. The expected time of merge in the main branch is next Thursday or Friday (1/15 or 1/16).

If you are interested in the progress of the work, please refer to the demo25 branch and feature/remove-bluechi branch.

[youngtaekiim]

@akshaylg0314
One more thing.
There is no prerequites for rocksdb.
And we made rocksctl for replacing etcdctl.

[akshaylg0314]

un-rust-ci / rust_ci
System.IO.IOException: No space left on device : '/home/runner/actions-runner/cached/_diag/Worker_20260105-103814-utc.log'
at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan1 buffer, Int64 fileOffset) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id) at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message) at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args) System.IO.IOException: No space left on device : '/home/runner/actions-runner/cached/_diag/Worker_20260105-103814-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan1 buffer, Int64 fileOffset)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.Diagnostics.TextWriterTraceListener.Flush()
at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id)
at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message)
at GitHub.Runner.Common.Tracing.Error(Exception exception)
at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args)
Unhandled exception. System.IO.IOException: No space left on device : '/home/runner/actions-runner/cached/_diag/Worker_20260105-103814-utc.log'
at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.Diagnostics.TextWriterTraceListener.Flush()
at System.Diagnostics.TraceSource.Flush()
at GitHub.Runner.Common.Tracing.Dispose(Boolean disposing)
at GitHub.Runner.Common.Tracing.Dispose()
at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing)
at GitHub.Runner.Common.TraceManager.Dispose()
at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing)
at GitHub.Runner.Common.HostContext.Dispose()
at GitHub.Runner.Worker.Program.Main(String[] args)

[youngtaekiim]

@akshaylg0314
I heard from Daeyoung what you're planning to do.
However, even if you work on the demo25 branch now, you'll have to rework it anyway once remove-bluechi is applied.

The current branch configuration is as follows:
main --(fork)--> demo25 --(fork)--> feature/remove-bluechi

Therefore, as soon as the bluechi removal is complete, I'll merge it into the demo25 branch, where I'll work on GitHub Actions and test cases.
Then, it will be merged back into the main branch.

The following are the major changes for each branch.
In demo25

• Changed build structure (see containers/Dockerfile and Cargo.toml)
• Replaced etcd with rocksdb (see src/common/)

In feature/remove-bluechi

• Changed piccolo startup: Replaced systemd usage with a script to remove podman quadlet dependency (see Makefile and containers folder)
• Modified proto folder and other parts of src/common
• Substantial changes to src/agent/nodeagent

The following are tasks I'd like to request from your team after merging the branches. These are primarily related to the Eclipse badge process.

• Functional GitHub workflow: Currently, test case-related content is commented out in the demo25 branch. (See the .yml file in .github/workflows.)
• Achieved test coverage

There's no need to start immediately; I'll create a task once the bluechi removal task is complete.

---

나는 대영으로부터 너가 작업하려고 하는 내용을 들었다.
그러나 demo 브랜치에서 지금 작업해도 remove-bluechi 의 내용이 적용되면 어차피 재작업을 해야한다.

현재 branch 분기는 다음과 같다.
main --(fork)--> demo25 --(fork)--> feature/remove-bluechi

그래서 나는 bluechi 제거 작업이 되는대로 이를 demo25 branch에 머지하고 여기서 GitHub Actions 관련 작업과 Test case 관련 작업을 하려고 한다.
그 후 이는 main branch에 머지될 것이다.

다음은 각 branch 별 주요 변경사항이다.
demo25

• build structure 변경 ( containers/Dockerfile 과 Cargo.toml들을 참조해라)
• etcd 를 rocksdb 로 대체

feature/remove-bluechi

• piccolo 구동 방식 변경 : podman quadlet 의존성 제거를 위해 systemd 사용방식을 script로 대체 ( Makefile 및 containers 폴더를 참조해라. )
• src/common 의 proto 폴더 및 여러 부분 수정
• src/agent/nodeagent 상당히 변경

다음은 branch 병합 후 너의 팀에게 요청하고 싶은 작업이다. 주로 eclipse badge process 관련 작업이다.

• GitHub workflow 정상 동작 : 현재는 demo25 branch 에서 test case 관련 내용을 주석처리해놓았다. (.github/workflows 의 .yml 파일 참조해라.`)
• test coverage 달성

당장 시작할 필요는 없고 bluechi 제거 작업이 완료되면 task 를 생성하도록 하겠다.

[youngtaekiim]

un-rust-ci / rust_ci System.IO.IOException: No space left on device : '/home/runner/actions-runner/cached/_diag/Worker_20260105-103814-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan1 buffer, Int64 fileOffset) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id) at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message) at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args) System.IO.IOException: No space left on device : '/home/runner/actions-runner/cached/_diag/Worker_20260105-103814-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan1 buffer, Int64 fileOffset) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id) at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message) at GitHub.Runner.Common.Tracing.Error(Exception exception) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args) Unhandled exception. System.IO.IOException: No space left on device : '/home/runner/actions-runner/cached/_diag/Worker_20260105-103814-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at System.Diagnostics.TraceSource.Flush() at GitHub.Runner.Common.Tracing.Dispose(Boolean disposing) at GitHub.Runner.Common.Tracing.Dispose() at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing) at GitHub.Runner.Common.TraceManager.Dispose() at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing) at GitHub.Runner.Common.HostContext.Dispose() at GitHub.Runner.Worker.Program.Main(String[] args)

Unfortunately, I don't know much about this.

[daeyoung-jeong-lge]

@akshaylg0314 As far as I understand, it looks that there's a storage problem when github action runs. Is it possible to reduce the used storage for github actions with modifying github action? If not, should we get a paid runner for more storage? Please give a problem detail and solutions which we can consider. Thanks.

[akshaylg0314]

@akshaylg0314 I heard from Daeyoung what you're planning to do. However, even if you work on the demo25 branch now, you'll have to rework it anyway once remove-bluechi is applied.

The current branch configuration is as follows: main --(fork)--> demo25 --(fork)--> feature/remove-bluechi

Therefore, as soon as the bluechi removal is complete, I'll merge it into the demo25 branch, where I'll work on GitHub Actions and test cases. Then, it will be merged back into the main branch.

The following are the major changes for each branch. In demo25

• Changed build structure (see containers/Dockerfile and Cargo.toml)
• Replaced etcd with rocksdb (see src/common/)

In feature/remove-bluechi

• Changed piccolo startup: Replaced systemd usage with a script to remove podman quadlet dependency (see Makefile and containers folder)
• Modified proto folder and other parts of src/common
• Substantial changes to src/agent/nodeagent

The following are tasks I'd like to request from your team after merging the branches. These are primarily related to the Eclipse badge process.

• Functional GitHub workflow: Currently, test case-related content is commented out in the demo25 branch. (See the .yml file in .github/workflows.)
• Achieved test coverage

There's no need to start immediately; I'll create a task once the bluechi removal task is complete.

나는 대영으로부터 너가 작업하려고 하는 내용을 들었다. 그러나 demo 브랜치에서 지금 작업해도 remove-bluechi 의 내용이 적용되면 어차피 재작업을 해야한다.

현재 branch 분기는 다음과 같다. main --(fork)--> demo25 --(fork)--> feature/remove-bluechi

그래서 나는 bluechi 제거 작업이 되는대로 이를 demo25 branch에 머지하고 여기서 GitHub Actions 관련 작업과 Test case 관련 작업을 하려고 한다. 그 후 이는 main branch에 머지될 것이다.

다음은 각 branch 별 주요 변경사항이다. demo25

• build structure 변경 ( containers/Dockerfile 과 Cargo.toml들을 참조해라)
• etcd 를 rocksdb 로 대체

feature/remove-bluechi

• piccolo 구동 방식 변경 : podman quadlet 의존성 제거를 위해 systemd 사용방식을 script로 대체 ( Makefile 및 containers 폴더를 참조해라. )
• src/common 의 proto 폴더 및 여러 부분 수정
• src/agent/nodeagent 상당히 변경

다음은 branch 병합 후 너의 팀에게 요청하고 싶은 작업이다. 주로 eclipse badge process 관련 작업이다.

• GitHub workflow 정상 동작 : 현재는 demo25 branch 에서 test case 관련 내용을 주석처리해놓았다. (.github/workflows 의 .yml 파일 참조해라.`)
• test coverage 달성

당장 시작할 필요는 없고 bluechi 제거 작업이 완료되면 task 를 생성하도록 하겠다.

@akshaylg0314 I heard from Daeyoung what you're planning to do. However, even if you work on the demo25 branch now, you'll have to rework it anyway once remove-bluechi is applied.

The current branch configuration is as follows: main --(fork)--> demo25 --(fork)--> feature/remove-bluechi

Therefore, as soon as the bluechi removal is complete, I'll merge it into the demo25 branch, where I'll work on GitHub Actions and test cases. Then, it will be merged back into the main branch.

The following are the major changes for each branch. In demo25

• Changed build structure (see containers/Dockerfile and Cargo.toml)
• Replaced etcd with rocksdb (see src/common/)

In feature/remove-bluechi

• Changed piccolo startup: Replaced systemd usage with a script to remove podman quadlet dependency (see Makefile and containers folder)
• Modified proto folder and other parts of src/common
• Substantial changes to src/agent/nodeagent

The following are tasks I'd like to request from your team after merging the branches. These are primarily related to the Eclipse badge process.

• Functional GitHub workflow: Currently, test case-related content is commented out in the demo25 branch. (See the .yml file in .github/workflows.)
• Achieved test coverage

There's no need to start immediately; I'll create a task once the bluechi removal task is complete.

나는 대영으로부터 너가 작업하려고 하는 내용을 들었다. 그러나 demo 브랜치에서 지금 작업해도 remove-bluechi 의 내용이 적용되면 어차피 재작업을 해야한다.

현재 branch 분기는 다음과 같다. main --(fork)--> demo25 --(fork)--> feature/remove-bluechi

그래서 나는 bluechi 제거 작업이 되는대로 이를 demo25 branch에 머지하고 여기서 GitHub Actions 관련 작업과 Test case 관련 작업을 하려고 한다. 그 후 이는 main branch에 머지될 것이다.

다음은 각 branch 별 주요 변경사항이다. demo25

• build structure 변경 ( containers/Dockerfile 과 Cargo.toml들을 참조해라)
• etcd 를 rocksdb 로 대체

feature/remove-bluechi

• piccolo 구동 방식 변경 : podman quadlet 의존성 제거를 위해 systemd 사용방식을 script로 대체 ( Makefile 및 containers 폴더를 참조해라. )
• src/common 의 proto 폴더 및 여러 부분 수정
• src/agent/nodeagent 상당히 변경

다음은 branch 병합 후 너의 팀에게 요청하고 싶은 작업이다. 주로 eclipse badge process 관련 작업이다.

• GitHub workflow 정상 동작 : 현재는 demo25 branch 에서 test case 관련 내용을 주석처리해놓았다. (.github/workflows 의 .yml 파일 참조해라.`)
• test coverage 달성

당장 시작할 필요는 없고 bluechi 제거 작업이 완료되면 task 를 생성하도록 하겠다.

Oh ok @youngtaekiim
I made some changes in demo25 branch related to github workflow for rocksdb integration should i create PR for demo25 branch now or should i need to wait for remove-bluechi changes?
thanks!

[akshaylg0314]

@akshaylg0314 As far as I understand, it looks that there's a storage problem when github action runs. Is it possible to reduce the used storage for github actions with modifying github action? If not, should we get a paid runner for more storage? Please give a problem detail and solutions which we can consider. Thanks.

hey @daeyoung-jeong-lge
ichecked on google and i found there is issue for storage so to resolve that we need to clear extra spce from disk, now issue is resolved
thanks!!

[youngtaekiim]

Oh ok @youngtaekiim I made some changes in demo25 branch related to github workflow for rocksdb integration should i create PR for demo25 branch now or should i need to wait for remove-bluechi changes? thanks!

Please wait just until this week.

[youngtaekiim]

@akshaylg0314 Work has been completed on the demo25 branch. I'll provide additional comments tomorrow after discussion on how to proceed.

[akshaylg0314]

@akshaylg0314 Work has been completed on the demo25 branch. I'll provide additional comments tomorrow after discussion on how to proceed.

Ohk sure @youngtaekiim

[youngtaekiim]

@akshaylg0314 The meeting has been postponed due to the absence of a key participant. I will share a presentation summarizing the key work items for your review via email.