ccp status -s will show short status of provided components only
(instead of the whole cluster status)
Change-Id: Ib464c4a2eaaf2ab08c19b5e5add4cb79879794cf
User can define two type of restarts for actions "never" and "always".
For "never" will be created pod object without restarts.
For "always" will be created job objects to be restarted until success.
Change-Id: I74afbe2a4bff21df6d28b8f49cdb3080ca8f69b7
This patch adds support of actions on existing ccp deployment.
For example actions can run tempest, rotation fernet tokens and so on.
Documentation will be added in another patchset.
Change-Id: If45f1bfb823f2182b0e79ca269c6b0e95066d053
We'll reuse it to get current state for objects we're about to update to
make a decision whether we should do upgrade or not.
Change-Id: I327d1e94eaff179a3975d14d8ad108d70e568eda
DaemonSet objects will be replaced with Deployment objects,
but one-pod-per-node rule will be provided with pod
antiaffinity and replicas will be set to number of matched
nodes.
Change-Id: Ieb8ac38e8d4426dd66668dbee303592137ce7fa0
We need to run multiple memcached instances for scale and performance
and the best approach for doing it is to support PetSets.
Change-Id: I42c9f82508ed7f42df01b467f45531b67b52b054
* use merged version of old and new objects definitions to
prevent allocation of new NodePort after update.
* objects merge is supported by pykube
* ut updated
Change-Id: Iad88b7ad77a2ec0669d00c62e0439e77de4a6e83
* no new commands/flags implemented - if object already exists,
it will be updated
* only Deployment, ConfigMap, Service can be updated
* if deployment spec was not updated, but related configmaps were,
deployment will be updated
* deployments will be updated with RollingUpdate strategy
Change-Id: If8fe78d6bea95b11d87f243cadc79490736745e7
We're importing all modules from CLI anyway, so we always import all
config modules, spreading this across all modules provides no benefit.
This is another step towards YAML config.
Change-Id: I38e2e8ae7596829311388498df68a048ab1cd981
Also move config initialization to fuel_ccp.config.
This is the first step to replacing oslo.config with YAML-based config.
Change-Id: If1b1faf006b40df95a661ecd00cb744e9fd0aafa
--export-dir parameter was added to deploy command.
k8s objects will be created inside of this directory
with names <object_name>-<object_kind>.yaml.
Configmap objects will be created under subdirectory
"configmaps"
Objects can be created with kubectl in default namespace:
kubectl create -f <dir>/configmaps/ -f <dir>/
And removed:
kubectl delete -f <dir>/configmaps/ -f <dir>/
To create in another namespace:
kubectl create namespace <ns>
kubectl create -f <dir>/configmaps/ -f <dir>/ --namespace <ns>
kubectl delete -f <dir>/configmaps/ -f <dir>/ --namespace <ns>
Change-Id: I0d33e928526954c7a068118fe6af82a5a0ce4af6
This patch removes support of hardcoded node selectors.
This patch allows to specify dynamic node selection policy via
configs.
If service is not specified in topology config, service deployment skipped.
Selectors works via affinity feature in kubernetes.
Change-Id: I1f8defd90169cd08fd2ac191c3b186efae5da010
Andreas Jaeger