Integrate standalone into risedev

[kwannoel]

Unify it, so we can use risedev profile to configure and use it.

• Add it to risedev, as a profile.
• Generate its dashboard and prometheus configurations and commit them.

[github-actions]

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean.
Don't worry if you think the issue is still valuable to continue in the future.
It's searchable and can be reopened when it's time. 😄

[fuyufjh]

Shall we close this?

[BugenZhao]

Is this for testing purposes?

[kwannoel]

It's not really necessary, but I think it's a good improvement. Currently the way the cluster is started is rather manual for standalone mode. Still need to pass in the parameters. We should just use risedev to manage it instead.

[BugenZhao]

In my opinion, I think it'll be nice if we can simply add a flag to use standalone mode to start multiple services in the same process for existing profiles, achieving the goal of enhancing the coverage of the standalone mode without introduction of new services or profiles. However, this might require some refactoring in RiseDev, given that all services are independently started in its own tmux panel in current implementation.

[kwannoel]

In my opinion, I think it'll be nice if we can simply add a flag to use standalone mode to start multiple services in the same process for existing profiles, achieving the goal of enhancing the coverage of the standalone mode without introduction of new services or profiles. However, this might require some refactoring in RiseDev, given that all services are independently started in its own tmux panel in current implementation.

You can take a try using this approach @wcy-fdu

[BugenZhao]

May I know the updates on the motivation of this task?

[kwannoel]

May I know the updates on the motivation of this task?

Currently the way the standalone service is managed in ci is rather adhoc:

risingwave/ci/scripts/run-e2e-test.sh

Lines 34 to 42 in e99ad67

	if [[ $mode == "standalone" ]]; then
	mkdir -p "$PREFIX_LOG"
	risedev clean-data
	risedev pre-start-dev
	risedev dev standalone-minio-sqlite &
	PID=$!
	sleep 1
	start_standalone "$PREFIX_LOG"/standalone.log &
	wait $PID

It can lead to breakage in ci (see: #19067). If we support standalone in risedev, we can properly sequence the startup of its services.