Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=stein-eol 2019-03-26T09:08:46+00:00 2019-03-26T09:08:46+00:00 Marcin Juszkiewicz marcin.juszkiewicz@linaro.org 2019-03-13T14:45:22+00:00 urn:sha1:a21ab86ca6e38a9b90a6c40f2aab87030e6f010f Before: (venv-for-kolla) 15:35 (s) hrw@puchatek:kolla$ ./tools/build.py --template-only INFO:kolla.common.utils:Found the docker image folder at /home/hrw/devel/linaro/kolla/docker Traceback (most recent call last): [.. here goes 100 lines of Jinja2 traceback ..] jinja2.exceptions.TemplateSyntaxError: unexpected '}', expected ']' After: (venv-for-kolla) 15:44 (s) hrw@puchatek:kolla$ ./tools/build.py --template-only INFO:kolla.common.utils:Found the docker image folder at /home/hrw/devel/linaro/kolla/docker ERROR:kolla.common.utils:Syntax error in template: ironic-inspector/Dockerfile.j2 ERROR:kolla.common.utils:unexpected '}', expected ']' INFO:kolla.common.utils:Dockerfiles are generated in /tmp/kolla-2019-03-13_15-44-28_0ovk4xu_/docker Change-Id: Iaa899f0b81f6698aa86b15977c39af3269d31e9a 2018-12-27T12:02:17+00:00 confi-surya singh.surya64mnnit@gmail.com 2018-12-24T07:14:57+00:00 urn:sha1:8acba6ff5640f16995bbdc35e14e0661eeb404c1 Use latest release 1.1.0 and compatible changes w.r.t pep8 Change-Id: Ia3d1166a2746a46591e4e5a04ea91e03ddc28d93 2017-03-29T17:48:58+00:00 Paul Bourke paul.bourke@oracle.com 2017-01-27T17:25:56+00:00 urn:sha1:e5410950c4cd3f89bef44f07f354cd71d8038105 Consider the case where you have a set of tagged / released images to production, and you want to apply a small hotfix, security patch, etc. to one of them, say keystone-ssh. Rebuilding keystone-ssh will cause a rebuild of base, openstack-base, and keystone-base, potentially pulling in updated packages / new dependencies, unless you have access to the exact machine they were previously built on. Ideally you want to use the exact parent images that are in production. This patch adds a new build argument '--skip-parents', which will result in only the image(s) specified by the regex and their children to be built. Parents are expected to exist either on machine or in a registry. Change-Id: I79d5f0b422f48d2dc36ae85dfa21668cf8177837 Implements: blueprint image-build-depth 2016-10-14T15:01:36+00:00 Martin André m.andre@redhat.com 2016-09-02T07:56:56+00:00 urn:sha1:9660b5786484172bd42c7fac332aa500fdc1790f Consistently set the search path to prefer PROJECT_ROOT as the source of packages to import if we are using local tools instead of pip installed kolla tools. TrivialFix Change-Id: Idd1d98bb82a8f1ddb32d1bdb23f346b461534b9f 2016-08-02T01:32:28+00:00 Lu lei lei.lu@easystack.cn 2016-08-01T05:27:50+00:00 urn:sha1:684b483fa814990e879d20de6a3c7046d068998d As we known, Exceptions are raised by the sys.exit() function. When they are not handled, no stack traceback is printed in the Python interpreter. In this patch we have known main() got return values(eg:0, 1), but it can't specifies exit status when terminate the main thread by unusing sys.exit(). So when using sys.exit(main()) instead of main() may be more readable and reasonable. TrivialFix. Change-Id: I184289d28b92a7e345907247c045535a0c42c974 2016-06-13T11:05:26+00:00 Ryan Hallisey rhallise@redhat.com 2016-06-13T11:01:48+00:00 urn:sha1:d360d4e5af09c5c194db783c4344aef10367b7f3 In order to use tools/build.py, we need to search locally for imports. Closes-bug: #1592030 Change-Id: Idfa651c1268f93366de9f4e3fa80c33be42c71c3 2016-06-07T16:40:16+00:00 Jeffrey Zhang jeffrey.zhang@99cloud.net 2016-06-06T03:37:45+00:00 urn:sha1:c31688be3688d2a4fe24b02aaad7e20ce0a0c516 First step to break it down is to make it importable lib rather than self-contained script. Change-Id: Ibbc924c2849cc79006046f62f31a1909ce959066 Partially-implements: bp build-refactor 2016-06-07T01:04:57+00:00 Jeffrey Zhang jeffrey.zhang@99cloud.net 2016-06-06T03:37:45+00:00 urn:sha1:9585c1be9f5bddb000b1aa6be68264df9f2aa445 TrivialFix Change-Id: I3ee10efc093ed394c3af483a229dcd9dc732ec9a 2016-06-02T18:21:24+00:00 Joshua Harlow jxharlow@godaddy.com 2016-05-26T20:38:21+00:00 urn:sha1:7c6990ccec16e55334376f696eb591891fc1fd7e Instead of using raw dicts and passing data around via dictionaries (which makes it really hard to figure out what is in those dictionaries at any point) prefer to use objects. That way people can actually understand what the object is supposed to be, vs guessing and/or having to decipher its usage. The same goes for raw string constants, prefer using named constants instead. Closes-Bug: #1586475 Change-Id: Ide179dc6593c50696d47a2d3d4cd000f343855d4 2016-06-02T18:21:09+00:00 Joshua Harlow jxharlow@godaddy.com 2016-05-26T01:53:11+00:00 urn:sha1:e78ae9bc618dff1ed38db1f5013d7f1735124790 Instead of having smart workers that need to know about the full logic of how they operate and what they will do which makes it hard to reuse parts of those workers switch the model so that workers are dumb and they just run tasks which themselves can request additional tasks to run when succesful. This makes it more consistent when tasks are to be retried and also makes it easier to know which task is running and when. Less specialized workers == good. Closes-Bug: #1586474 Change-Id: Ie7b7303b8bf2a80b3e26b6d4ffc27787f8c794d6