forked from camsas/firmament
-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Shivram Srivastava
authored and
Shivram Srivastava
committed
Oct 22, 2018
1 parent
6ad8fd7
commit 63087f7
Showing
1 changed file
with
49 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
## Release notes for firmament v0.5 | ||
|
||
# Significant changes | ||
|
||
* Adding Support for ephemeral storage. | ||
* Support for events feature in Firmament. | ||
* Static Persistant Volume support, [more info.](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) | ||
* Bug fixes and minor performance improvements. | ||
|
||
# Required Actions | ||
|
||
To enable the new CPU-MEM cost model ```--flow_scheduling_cost_model``` | ||
flag should be set to '10' | ||
like shown below | ||
|
||
```--flow_scheduling_cost_model=10``` | ||
|
||
To enable the Pod Affinity/Anti-Affinity symmetry ```--pod_affinity_antiaffinity_symmetry``` | ||
flag should be set to 'true' in the firmament config file | ||
like show below | ||
|
||
```firmament_scheduler_cpu_mem.cfg=true``` | ||
|
||
This fix is based above the CPU-MEM cost model. | ||
This feature currently are not supported in other cost model. | ||
|
||
# Highlighted changes | ||
|
||
Ephemeral Storage and Events support. | ||
Static Persistant Volume support is also avaliable from the V0.5 'Poseidon' release. | ||
|
||
# Static Persistant Volume support | ||
|
||
This works with V0.5 Poseidon release. | ||
There is no change for this feature in firmament. | ||
|
||
Pre-Bound PVC to a PV will be picked by 'Poseidon' if a Pod has that PVC requirement. | ||
|
||
It will be used as a node selector term in the NodeAffinity 'Hard-constraint' section of the Pod. | ||
|
||
When 'Frimament' try to schedule this Task it will try to satify the NodeAffinity Hard Constraints, | ||
which will result in the Pod getting scheduled on the Node which satisfy the PV's NodeSelector term. | ||
|
||
# Full change list | ||
|
||
* [Adding Support for ephemeral storage ](https://github.com/Huawei-PaaS/firmament/pull/12) | ||
* [Adding events feature in Firmament ](https://github.com/Huawei-PaaS/firmament/pull/13) | ||
* [Adding max pods feature](https://github.com/Huawei-PaaS/firmament/pull/14) | ||
* [Removed max pods changes](https://github.com/Huawei-PaaS/firmament/pull/15) |