During the describing images and missing their parents the `ccp build`
command sometime is not so informative, e.g. like that:
ERROR ccp 'base-tools'
Unit tests are included.
Change-Id: I14f6a4cc75e49f17c3d943d508bea9c0b819da9f
This allows to separate tempdir cleanup from build results reporting.
Also move build results reporting to happen only if we actually started
build process.
Change-Id: I13d7f3d05c86324b0154b3331470c6253a678090
Changing log level of dockerfile rendering message from info
to debug because we are now rendering all dockerfiles (including
not requested) at the beginning of the build.
Change-Id: I1dabf211bdb3abe926c580af0039ea426320b2c2
This requires changes in all component repos to replace FROM line to
FROM {{ image_spec('someimage') }}
Change-Id: I18281bdb41e91cd5c9160055f1617d7ee9d3b548
This will allow us to extract information about parent images from
rendered content instead of mathcing by regex.
Change-Id: Iedb8d1bb153297dfddce71d47b55b57fb6a0196d
This will allow to render Dockerfile separately from preparing work
directory and sources for building.
Change-Id: Ic12c42204f1c2e02c005939b498aa29da376c5a0
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
We still use oslo.config for CLI parsing and default values, so added
copying of all values from oslo.config to YAML dict. To keep easy
access, added AttrDict class that allows to access config dict via
attribute access. Created a new fixture for tests that loads default
values from oslo.config to reuse current definition.
Change-Id: I921830890463f295f9e6a2467d6bc15504742e1b
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
When "ccp build" command is searching for already built images,
only one tag for each image is being considered. This behavior
leads to rebuilding of already existing images.
Change-Id: I6c9d1ad523ddac7ed7fb4fa56ce2d5f0eeccc788
Closes-bug: #1619198
Adding ability to use git repositories or local folder
for components code
example:
sources:
openstack/keystone:
git_url: https://github.com/openstack/keystone.git
git_ref: master
OR
source_dir: /tmp/keystone
Defaults can be overriden in global config.
Validation will be added in separate patch.
Change-Id: I4d91aa8632fcd55735d791300fde475696b435b5
Currently we are rendering all existing dockerfiles
in repositories, but only requested for build should
be rendered.
Change-Id: Ib811ca24372fe42776e6458d2255bb82086dd70d
Closes-bug: #1615981
Without it(or debug logs) user will stare at blank screen without
knowing what is happening right now.
Change-Id: I9731efae35ff2ac68a4d3552b36cbfe0b7c944f9
Changes in Summary:
* all layres of image are already in registry under
the same tag => "already in registry" group
* at least one layer actually pushed or mounted from
other layer that exists in registry => "push succeeded"
group
Change-Id: I1a66157f13211047d41e3e0189472b6be20462db
Right now, it's possible to have a set of same images with different
tags, which is ok, but sometimes we could have an image without tag:
127.0.0.1:31500/ccp/heka latest
127.0.0.1:31500/ccp/heka <none>
This is related to how docker create layers, see also:
https://review.openstack.org/#/c/352360/
Change-Id: I6a610f49f2edd3d86cbbc2df01ee6d0d4f9fb87b
Message that image already exists in registry
will be printed if its layers already exist
in registry
Change-Id: Ib13588b17ef26dfc6b220f724f0bcae0ccfb557a
Custom tag was not taken into account during images
build and push.
Change-Id: Ic8ad1c3cf756b31114e75f2ecc5220dc8eb279cc
Closes-bug: #1610889
Closes-bug: #1610881
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