Project

General

Profile

Feature #10101

Deploy addons and build bases within base images

Added by Evgeny Novikov about 1 year ago. Updated 7 months ago.

Status:
New
Priority:
High
Assignee:
-
Category:
Deployment
Target version:
-
Start date:
02/05/2020
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

At the moment addons and build bases are deployed just for particular instances. This is very inefficient.

Note, that there is a rather powerful update mechanism, so, new versions of addons and build bases will overwrite the old ones from images.


Related issues

Blocked by Klever - Feature #9356: Do not deploy the same build basesClosed10/29/2018

Actions

History

#1

Updated by Evgeny Novikov about 1 year ago

  • Blocked by Feature #9356: Do not deploy the same build bases added
#2

Updated by Ilya Shchepetkov 8 months ago

Recent changes in the improve-openstack-deployment branch make implementing this feature rather easy. However, potential deployment speed improvements are questionable: downloading addons and build bases is extremely fast right now due to the gigabit internet used in the cloud. Unarchiving these addons and build bases, on the other hand, is rather slow, and will remain slow even if these archives will be pre-deployed in the base image. We can't pre-deploy unarchived versions of these addons and build bases, since they will not be compatible with the default "klever.json" configuration file. Unfortunately, this is a restriction of local deployment.

#3

Updated by Evgeny Novikov 7 months ago

Indeed, deployment scripts will not need to download/decompress archives (and thus to save a lot of time) until addon versions within klever.json will change. For build bases we need to solve #9356 before thinking about this issue.

Also available in: Atom PDF