a035dc9be7
Remove AssignmentProviderConfig and use parameters from HostConfiguration instead ( #3181 )
...
This PR removes `AssignmentProviderConfig` and uses the corresponding
ondemand parameters from `HostConfiguration` instead. Additionally
`scheduling_lookahead` and all coretime/ondemand related parameters are
extracted in a separate struct - `SchedulerParams`.
The most relevant commit from the PR is [this
one](https://github.com/paritytech/polkadot-sdk/pull/3181/commits/830bc0f5e858944474171bbe33382ad96040b535 ).
Fixes https://github.com/paritytech/polkadot-sdk/issues/2268
---------
Co-authored-by: command-bot <>
2024-02-29 07:12:02 +00:00
8ba7a6aba8
chain-spec: getting ready for native-runtime-free world (#1256 )
...
This PR prepares chains specs for _native-runtime-free_ world.
This PR has following changes:
- `substrate`:
- adds support for:
- JSON based `GenesisConfig` to `ChainSpec` allowing interaction with
runtime `GenesisBuilder` API.
- interacting with arbitrary runtime wasm blob to[
`chain-spec-builder`](https://github.com/paritytech/substrate/blob/3ef576eaeb3f42610e85daecc464961cf1295570/bin/utils/chain-spec-builder/src/lib.rs#L46 )
command line util,
- removes
[`code`](https://github.com/paritytech/substrate/blob/3ef576eaeb3f42610e85daecc464961cf1295570/frame/system/src/lib.rs#L660 )
from `system_pallet`
- adds `code` to the `ChainSpec`
- deprecates
[`ChainSpec::from_genesis`](https://github.com/paritytech/substrate/blob/3ef576eaeb3f42610e85daecc464961cf1295570/client/chain-spec/src/chain_spec.rs#L263 ),
but also changes the signature of this method extending it with `code`
argument.
[`ChainSpec::builder()`](https://github.com/paritytech/substrate/blob/20bee680ed098be7239cf7a6b804cd4de267983e/client/chain-spec/src/chain_spec.rs#L507 )
should be used instead.
- `polkadot`:
- all references to `RuntimeGenesisConfig` in `node/service` are
removed,
- all
`(kusama|polkadot|versi|rococo|wococo)_(staging|dev)_genesis_config`
functions now return the JSON patch for default runtime `GenesisConfig`,
- `ChainSpecBuilder` is used, `ChainSpec::from_genesis` is removed,
- `cumulus`:
- `ChainSpecBuilder` is used, `ChainSpec::from_genesis` is removed,
- _JSON_ patch configuration used instead of `RuntimeGenesisConfig
struct` in all chain specs.
---------
Co-authored-by: command-bot <>
Co-authored-by: Javier Viola <javier@parity.io >
Co-authored-by: Davide Galassi <davxy@datawok.net >
Co-authored-by: Francisco Aguirre <franciscoaguirreperez@gmail.com >
Co-authored-by: Kevin Krone <kevin@parity.io >
Co-authored-by: Bastian Köcher <git@kchr.de >
2023-11-05 15:19:23 +01:00
ada1ac3dcd
[DNM] bump zombienet version ( #2083 )
...
This version includes:
- Move `spot` usage in CI to 50%
- Fix `PodMonitor`, metrics will be relayed to grafana
2023-10-31 13:33:01 -03:00
50242a61d7
rococo-runtime: RococoGenesisExt removed ( #1490 )
...
[`RococoGenesisExt`](https://github.com/paritytech/polkadot-sdk/blob/a414ea7515c9cdc81f1d12410e646afc148250e8/polkadot/node/service/src/chain_spec.rs#L152-L171 )
is removed. It was the hack to allow overwriting
`EpochDurationInBlocks`. Removal of `RococGenesisExt` prevents from
manipulating the state to change the runtime constants.
Changes:
- Environment variable which controls the `time::EpochDurationInBlocks`
value was added: `ROCOCO_EPOCH_DURATION` (epoch duration will be set to
the value of env),
- `10,100,600` versions of rococo-runtime are built in CI and put into `polkadot-debug` docker image.
`rococo-runtime` building examples:
- to build runtime for `versi_staging_testnet` which had
EpochDurationInBlocks set to 100:
```
ROCOCO_EPOCH_DURATION=100 cargo build --features=fast-runtime -p
rococo-runtime
```
- to build runtime for `wococo_development`
```
ROCOCO_EPOCH_DURATION=10 cargo build --features=fast-runtime -p
rococo-runtime
```
- to build `versi-staging` chain spec:
```
ROCOCO_EPOCH_DURATION=100 cargo run -p polkadot --features=fast-runtime
-- build-spec --chain versi-staging --raw
```
- to build `wococo-dev` chain spec:
```
ROCOCO_EPOCH_DURATION=10 cargo run -p polkadot --features=fast-runtime
-- build-spec --chain wococo-dev --raw
```
It is also possible to change the epoch duration by replacing the `code` field in the chain spec with the hex dump of pre-built runtime wasm blob (because the epoch duration is hard-coded into wasm blob).
---------
Co-authored-by: Bastian Köcher <git@kchr.de >
2023-09-28 18:29:12 +02:00
70852e9400
Make zombienet tests native friendly ( #6588 )
...
* Make zombienet tests native friendly
* Update zombienet_tests/README.md
Co-authored-by: Bastian Köcher <info@kchr.de >
* Get rid of `{{ZOMBIENET_NATIVE_BINARY_PREFIX}}`
* Remove pointless changes
* add set_env helper and doc in readme
* changes from feedback
---------
Co-authored-by: Bastian Köcher <info@kchr.de >
Co-authored-by: Javier Viola <javier@parity.io >
2023-01-28 12:00:45 +00:00
d54e20708d
Zombienet: paritydb test ( #5310 )
...
* Add test
Signed-off-by: Andrei Sandu <andrei-mihail@parity.io >
* gitlab integration
Signed-off-by: Andrei Sandu <andrei-mihail@parity.io >
* tune test
Signed-off-by: Andrei Sandu <andrei-mihail@parity.io >
* Try waiting for nodes to be up before checks
Signed-off-by: Andrei Sandu <andrei-mihail@parity.io >
* Use js check for paritydb folder
Signed-off-by: Andrei Sandu <andrei-mihail@parity.io >
* artifacts true
Signed-off-by: Andrei Sandu <andrei-mihail@parity.io >
* change error message
Signed-off-by: Andrei Sandu <andrei-mihail@parity.io >
* debug
Signed-off-by: Andrei Sandu <andrei-mihail@parity.io >
* try again
Signed-off-by: Andrei Sandu <andrei-mihail@parity.io >
* use log line contains for test
* bump zombienet verision for test
* Is approval checking lag 0 on rocksdb ?
Signed-off-by: Andrei Sandu <andrei-mihail@parity.io >
* Is approval checking lag 1 with paritydb ?
Signed-off-by: Andrei Sandu <andrei-mihail@parity.io >
* update zombienet test for parityDb
* Update zombienet_tests/misc/0001-check_paritydb.sh
Co-authored-by: Chevdor <chevdor@users.noreply.github.com >
Co-authored-by: Javier Viola <javier@parity.io >
Co-authored-by: Chevdor <chevdor@users.noreply.github.com >
2022-07-18 10:55:38 +00:00
Tsvetomir Dimitrov