New config section introduced:
services:
keystone-db:
service_def: mariadb
keystone:
service_def: keystone
mapping:
database: keystone-db
Defined services can be used in topology definition.
In this example keystone-db service will be created from mariadb
definition and keystone will use it instead of mariadb.
Change-Id: I274826648390b844d240b7ae545c40264f662452
* scheme can be added with with_scheme=True flag
* ingress port will be added to the end of the address
Change-Id: I94efeea5a8a0acb67781d3e5a50b0c99601f7b4e
* ingress support added
port:
cont: 123
ingress: test
* two config params added:
configs:
ingress:
enable: False
domain: external
Ingress will be disabled by default
Change-Id: Ic621af6930f078eea17fd83fce26b42cd32ecf01
Replace them with storing data from components centrally in global CONF
and using it all over the place.
This allows to centrally control how configs are handled, i.e. if we
decide to not use defaults anymore, we can just remove
load_component_defaults from cli module.
Change-Id: Id58bb43a7a9cbb367719ba59484bf3121ec68379
* "address" function was added to jinja env.
This function takes service name as a parameter and
returns address of the service (<service_name>.<namespace>
currently)
* k8s namespace added to "globals" configmap
Change-Id: I163857fa0c671e21725d7276540f5fbba09619d2
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
Consists of two parts:
1) OS cleanup:
Instances, subnets and networks from all OS
projects will be removed.
2) K8s objects cleanup
Usage:
ccp cleanup --auth-url <auth_url> --skip-os-cleanup
--auth-url parameter is optional, by default
it takes internal keystone url, whick is not
appropriate in some cases.
--skip-os-cleanup is optional
Note: do not use default namespace for deployment
because it could not be cleaned up by cleanup command
Change-Id: I53f59d9ca8de09ac33e37c90dacf821dda72afec
Andreas Jaeger