You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* wip
Signed-off-by: Cassandra Coyle <[email protected]>
* rm scheduleJob logic. keep only init/uninstall logic
Signed-off-by: Cassandra Coyle <[email protected]>
* Fixes install and uninstall of scheduler in standalone mode.
Signed-off-by: Artur Souza <[email protected]>
* Fixing path for Go tools in Darwin.
Signed-off-by: Artur Souza <[email protected]>
* Fix Go bin location for MacOS.
Signed-off-by: Artur Souza <[email protected]>
* Fix min scheduler version to be 1.14.x
Signed-off-by: Artur Souza <[email protected]>
* Use env var to pass scheduler host.
Signed-off-by: Artur Souza <[email protected]>
* Fix CLI build to work with latest MacOS runners from GH
Signed-off-by: Artur Souza <[email protected]>
---------
Signed-off-by: Cassandra Coyle <[email protected]>
Signed-off-by: Artur Souza <[email protected]>
Co-authored-by: Artur Souza <[email protected]>
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Before you file an issue, make sure you've checked the following:
40
40
- 👎 down-vote
41
41
1. For bugs
42
42
- Check it's not an environment issue. For example, if running on Kubernetes, make sure prerequisites are in place. (state stores, bindings, etc.)
43
-
- You have as much data as possible. This usually comes in the form of logs and/or stacktrace. If running on Kubernetes or other environment, look at the logs of the Dapr services (runtime, operator, placement service). More details on how to get logs can be found [here](https://docs.dapr.io/operations/troubleshooting/logs-troubleshooting/).
43
+
- You have as much data as possible. This usually comes in the form of logs and/or stacktrace. If running on Kubernetes or other environment, look at the logs of the Dapr services (runtime, operator, placement, scheduler service). More details on how to get logs can be found [here](https://docs.dapr.io/operations/troubleshooting/logs-troubleshooting/).
44
44
1. For proposals
45
45
- Many changes to the Dapr runtime may require changes to the API. In that case, the best place to discuss the potential feature is the main [Dapr repo](https://github.com/dapr/dapr).
46
46
- Other examples could include bindings, state stores or entirely new components.
Copy file name to clipboardExpand all lines: README.md
+12-7Lines changed: 12 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ Install windows Dapr CLI using MSI package.
68
68
69
69
### Install Dapr on your local machine (self-hosted)
70
70
71
-
In self-hosted mode, dapr can be initialized using the CLI with the placement, redis and zipkin containers enabled by default(recommended) or without them which also does not require docker to be available in the environment.
71
+
In self-hosted mode, dapr can be initialized using the CLI with the placement, scheduler, redis, and zipkin containers enabled by default(recommended) or without them which also does not require docker to be available in the environment.
72
72
73
73
#### Initialize Dapr
74
74
@@ -89,6 +89,7 @@ Output should look like so:
89
89
✅ Downloaded binaries and completed components set up.
90
90
ℹ️ daprd binary has been installed to $HOME/.dapr/bin.
91
91
ℹ️ dapr_placement container is running.
92
+
ℹ️ dapr_scheduler container is running.
92
93
ℹ️ dapr_redis container is running.
93
94
ℹ️ dapr_zipkin container is running.
94
95
ℹ️ Use `docker ps` to check running containers.
@@ -118,10 +119,11 @@ Output should look like so:
118
119
✅ Downloaded binaries and completed components set up.
119
120
ℹ️ daprd binary has been installed to $HOME/.dapr/bin.
120
121
ℹ️ placement binary has been installed.
122
+
ℹ️ scheduler binary has been installed.
121
123
✅ Success! Dapr is up and running. To get started, go here: https://aka.ms/dapr-getting-started
122
124
```
123
125
124
-
>Note: When initializing Dapr with the `--slim` flag only the Dapr runtime binary and the placement service binary are installed. An empty default components folder is created with no default configuration files. During `dapr run` user should use `--resources-path` (`--components-path` is deprecated and will be removed in future releases) to point to a components directory with custom configurations files or alternatively place these files in the default directory. For Linux/MacOS, the default components directory path is `$HOME/.dapr/components` and for Windows it is `%USERPROFILE%\.dapr\components`.
126
+
>Note: When initializing Dapr with the `--slim` flag only the Dapr runtime, placement, and scheduler service binaries are installed. An empty default components folder is created with no default configuration files. During `dapr run` user should use `--resources-path` (`--components-path` is deprecated and will be removed in future releases) to point to a components directory with custom configurations files or alternatively place these files in the default directory. For Linux/MacOS, the default components directory path is `$HOME/.dapr/components` and for Windows it is `%USERPROFILE%\.dapr\components`.
125
127
126
128
#### Install a specific runtime version
127
129
@@ -171,7 +173,7 @@ Move to the bundle directory and run the following command:
171
173
172
174
> If you are not running the above command from the bundle directory, provide the full path to bundle directory as input. For example, assuming the bundle directory path is $HOME/daprbundle, run `$HOME/daprbundle/dapr init --from-dir $HOME/daprbundle` to have the same behavior.
173
175
174
-
> Note: Dapr Installer bundle just contains the placement container apart from the binaries and so `zipkin` and `redis` are not enabled by default. You can pull the images locally either from network or private registry and run as follows:
176
+
> Note: Dapr Installer bundle just contains the placement and scheduler containers apart from the binaries and so `zipkin` and `redis` are not enabled by default. You can pull the images locally either from network or private registry and run as follows:
175
177
176
178
```bash
177
179
docker run --name "dapr_zipkin" --restart always -d -p 9411:9411 openzipkin/zipkin
> Note: When installed to a specific Docker network, you will need to add the `--placement-host-address` arguments to `dapr run` commands run in any containers within that network.
200
202
> The format of `--placement-host-address` argument is either `<hostname>` or `<hostname>:<port>`. If the port is omitted, the default port `6050` for Windows and `50005` for Linux/MacOS applies.
201
203
204
+
> Note: When installed to a specific Docker network, you will need to add the `--scheduler-host-address` arguments to `dapr run` commands run in any containers within that network.
205
+
> The format of `--scheduler-host-address` argument is either `<hostname>` or `<hostname>:<port>`. If the port is omitted, the default port `6060` for Windows and `50006` for Linux/MacOS applies.
206
+
202
207
#### Install with a specific container runtime
203
208
204
209
You can install the Dapr runtime using a specific container runtime
@@ -228,7 +233,7 @@ For more details, see the docs for dev containers with [Visual Studio Code](http
228
233
229
234
### Uninstall Dapr in a standalone mode
230
235
231
-
Uninstalling will remove daprd binary and the placement container (if installed with Docker or the placement binary if not).
236
+
Uninstalling will remove daprd binary along with the placement and scheduler containers (if installed with Docker or the placement and scheduler binaries if not).
232
237
233
238
234
239
```bash
@@ -237,15 +242,15 @@ dapr uninstall
237
242
238
243
> For Linux users, if you run your docker cmds with sudo, you need to use "**sudo dapr uninstall**" to remove the containers.
239
244
240
-
The command above won't remove the redis or zipkin containers by default in case you were using it for other purposes. It will also not remove the default dapr folder that was created on `dapr init`. To remove all the containers (placement, redis, zipkin) and also the default dapr folder created on init run:
245
+
The command above won't remove the redis or zipkin containers by default in case you were using it for other purposes. It will also not remove the default dapr folder that was created on `dapr init`. To remove all the containers (placement, scheduler, redis, zipkin) and also the default dapr folder created on init run:
241
246
242
247
```bash
243
248
dapr uninstall --all
244
249
```
245
250
246
251
The above command can also be run when Dapr has been installed in a non-docker environment, it will only remove the installed binaries and the default dapr folder in that case.
247
252
248
-
> NB: The `dapr uninstall` command will always try to remove the placement binary/service and will throw an error is not able to.
253
+
> NB: The `dapr uninstall` command will always try to remove the placement and scheduler binaries/services and will throw an error is not able to.
249
254
250
255
**You should always run a `dapr uninstall` before running another `dapr init`.**
dapr run --app-id nodeapp --placement-host-address dapr_placement node app.js
408
413
```
409
414
410
-
> Note: When in a specific Docker network, the Redis, Zipkin and placement service containers are given specific network aliases, `dapr_redis`, `dapr_zipkin`and `dapr_placement`, respectively. The default configuration files reflect the network alias rather than `localhost` when a docker network is specified.
415
+
> Note: When in a specific Docker network, the Redis, Zipkin and placement and scheduler service containers are given specific network aliases, `dapr_redis`, `dapr_zipkin`, `dapr_placement`, and `dapr_scheduler`, respectively. The default configuration files reflect the network alias rather than `localhost` when a docker network is specified.
Copy file name to clipboardExpand all lines: cmd/init.go
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -210,7 +210,7 @@ func init() {
210
210
InitCmd.Flags().BoolVarP(&devMode, "dev", "", false, "Use Dev mode. Deploy Redis, Zipkin also in the Kubernetes cluster")
211
211
InitCmd.Flags().BoolVarP(&wait, "wait", "", false, "Wait for Kubernetes initialization to complete")
212
212
InitCmd.Flags().UintVarP(&timeout, "timeout", "", 300, "The wait timeout for the Kubernetes installation")
213
-
InitCmd.Flags().BoolVarP(&slimMode, "slim", "s", false, "Exclude placement service, Redis and Zipkin containers from self-hosted installation")
213
+
InitCmd.Flags().BoolVarP(&slimMode, "slim", "s", false, "Exclude placement service, scheduler service, Redis and Zipkin containers from self-hosted installation")
214
214
InitCmd.Flags().StringVarP(&runtimeVersion, "runtime-version", "", defaultRuntimeVersion, "The version of the Dapr runtime to install, for example: 1.0.0")
215
215
InitCmd.Flags().StringVarP(&dashboardVersion, "dashboard-version", "", defaultDashboardVersion, "The version of the Dapr dashboard to install, for example: 0.13.0")
216
216
InitCmd.Flags().StringVarP(&initNamespace, "namespace", "n", "dapr-system", "The Kubernetes namespace to install Dapr in")
// By marking this as deprecated, the flag will be hidden from the help menu, but will continue to work. It will show a warning message when used.
455
457
RunCmd.Flags().MarkDeprecated("components-path", "This flag is deprecated and will be removed in the future releases. Use \"resources-path\" flag instead")
456
458
RunCmd.Flags().String("placement-host-address", "localhost", "The address of the placement service. Format is either <hostname> for default port or <hostname>:<port> for custom port")
459
+
RunCmd.Flags().String("scheduler-host-address", "localhost", "The address of the scheduler service. Format is either <hostname> for default port or <hostname>:<port> for custom port")
457
460
// TODO: Remove below flag once the flag is removed in runtime in future release.
458
461
RunCmd.Flags().BoolVar(&appSSL, "app-ssl", false, "Enable https when Dapr invokes the application")
459
462
RunCmd.Flags().MarkDeprecated("app-ssl", "This flag is deprecated and will be removed in the future releases. Use \"app-protocol\" flag with https or grpcs values instead")
Copy file name to clipboardExpand all lines: cmd/uninstall.go
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ var UninstallCmd = &cobra.Command{
43
43
# Uninstall from self-hosted mode
44
44
dapr uninstall
45
45
46
-
# Uninstall from self-hosted mode and remove .dapr directory, Redis, Placement and Zipkin containers
46
+
# Uninstall from self-hosted mode and remove .dapr directory, Redis, Placement, Scheduler, and Zipkin containers
47
47
dapr uninstall --all
48
48
49
49
# Uninstall from Kubernetes
@@ -99,7 +99,7 @@ func init() {
99
99
UninstallCmd.Flags().BoolVarP(&uninstallKubernetes, "kubernetes", "k", false, "Uninstall Dapr from a Kubernetes cluster")
100
100
UninstallCmd.Flags().BoolVarP(&uninstallDev, "dev", "", false, "Uninstall Dapr Redis and Zipking installations from Kubernetes cluster")
101
101
UninstallCmd.Flags().UintVarP(&timeout, "timeout", "", 300, "The timeout for the Kubernetes uninstall")
102
-
UninstallCmd.Flags().BoolVar(&uninstallAll, "all", false, "Remove .dapr directory, Redis, Placement and Zipkin containers on local machine, and CRDs on a Kubernetes cluster")
102
+
UninstallCmd.Flags().BoolVar(&uninstallAll, "all", false, "Remove .dapr directory, Redis, Placement, Scheduler, and Zipkin containers on local machine, and CRDs on a Kubernetes cluster")
103
103
UninstallCmd.Flags().String("network", "", "The Docker network from which to remove the Dapr runtime")
104
104
UninstallCmd.Flags().StringVarP(&uninstallNamespace, "namespace", "n", "dapr-system", "The Kubernetes namespace to uninstall Dapr from")
105
105
UninstallCmd.Flags().BoolP("help", "h", false, "Print this help message")
0 commit comments