payload_generation_config.h revision 05feee0fc8f4f10b425f04e1f5cdd4831bbfb969
1//
2// Copyright (C) 2015 The Android Open Source Project
3//
4// Licensed under the Apache License, Version 2.0 (the "License");
5// you may not use this file except in compliance with the License.
6// You may obtain a copy of the License at
7//
8//      http://www.apache.org/licenses/LICENSE-2.0
9//
10// Unless required by applicable law or agreed to in writing, software
11// distributed under the License is distributed on an "AS IS" BASIS,
12// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13// See the License for the specific language governing permissions and
14// limitations under the License.
15//
16
17#ifndef UPDATE_ENGINE_PAYLOAD_GENERATOR_PAYLOAD_GENERATION_CONFIG_H_
18#define UPDATE_ENGINE_PAYLOAD_GENERATOR_PAYLOAD_GENERATION_CONFIG_H_
19
20#include <cstddef>
21
22#include <memory>
23#include <string>
24#include <vector>
25
26#include <brillo/key_value_store.h>
27
28#include "update_engine/payload_consumer/payload_constants.h"
29#include "update_engine/payload_generator/filesystem_interface.h"
30#include "update_engine/update_metadata.pb.h"
31
32namespace chromeos_update_engine {
33
34struct PostInstallConfig {
35  // Whether the postinstall config is empty.
36  bool IsEmpty() const;
37
38  // Whether this partition carries a filesystem with post-install program that
39  // must be run to finalize the update process.
40  bool run = false;
41
42  // The path to the post-install program relative to the root of this
43  // filesystem.
44  std::string path;
45
46  // The filesystem type used to mount the partition in order to run the
47  // post-install program.
48  std::string filesystem_type;
49};
50
51struct PartitionConfig {
52  explicit PartitionConfig(std::string name) : name(name) {}
53
54  // Returns whether the PartitionConfig is not an empty image and all the
55  // fields are set correctly to a valid image file.
56  bool ValidateExists() const;
57
58  // Open then filesystem stored in this partition and stores it in
59  // |fs_interface|. Returns whether opening the filesystem worked.
60  bool OpenFilesystem();
61
62  // The path to the partition file. This can be a regular file or a block
63  // device such as a loop device.
64  std::string path;
65
66  // The size of the data in |path|. If rootfs verification is used (verity)
67  // this value should match the size of the verity device for the rootfs, and
68  // the size of the whole kernel. This value could be smaller than the
69  // partition and is the size of the data update_engine assumes verified for
70  // the source image, and the size of that data it should generate for the
71  // target image.
72  uint64_t size = 0;
73
74  // The FilesystemInterface implementation used to access this partition's
75  // files.
76  std::unique_ptr<FilesystemInterface> fs_interface;
77
78  std::string name;
79
80  PostInstallConfig postinstall;
81};
82
83// The ImageConfig struct describes a pair of binaries kernel and rootfs and the
84// metadata associated with the image they are part of, like build number, size,
85// etc.
86struct ImageConfig {
87  // Returns whether the ImageConfig is an empty image.
88  bool ValidateIsEmpty() const;
89
90  // Load |rootfs_size| and |kernel.size| from the respective image files. For
91  // the kernel, the whole |kernel.path| file is assumed. For the rootfs, the
92  // size is detected from the filesystem.
93  // Returns whether the image size was properly detected.
94  bool LoadImageSize();
95
96  // Load postinstall config from a key value store.
97  bool LoadPostInstallConfig(const brillo::KeyValueStore& store);
98
99  // Returns whether the |image_info| field is empty.
100  bool ImageInfoIsEmpty() const;
101
102  // The ImageInfo message defined in the update_metadata.proto file describes
103  // the metadata of the image.
104  ImageInfo image_info;
105
106  // The updated partitions.
107  std::vector<PartitionConfig> partitions;
108};
109
110// The PayloadGenerationConfig struct encapsulates all the configuration to
111// build the requested payload. This includes information about the old and new
112// image as well as the restrictions applied to the payload (like minor-version
113// and full/delta payload).
114struct PayloadGenerationConfig {
115  // Returns whether the PayloadGenerationConfig is valid.
116  bool Validate() const;
117
118  // Image information about the new image that's the target of this payload.
119  ImageConfig target;
120
121  // Image information pertaining the old image, if any. This is only valid
122  // if is_full is false, so we are requested a delta payload.
123  ImageConfig source;
124
125  // Wheter the requested payload is a delta payload.
126  bool is_delta = false;
127
128  // The major_version of the requested payload.
129  uint64_t major_version;
130
131  // The minor_version of the requested payload.
132  uint32_t minor_version;
133
134  // The size of the rootfs partition, that not necessarily is the same as the
135  // filesystem in either source or target version, since there is some space
136  // after the partition used to store the verity hashes and or the bootcache.
137  uint64_t rootfs_partition_size = 0;
138
139  // The |hard_chunk_size| is the maximum size that a single operation should
140  // write in the destination. Operations bigger than chunk_size should be
141  // split. A value of -1 means no hard chunk size limit. A very low limit
142  // means more operations, and less of a chance to reuse the data.
143  ssize_t hard_chunk_size = -1;
144
145  // The |soft_chunk_size| is the preferred chunk size to use when there's no
146  // significant impact to the operations. For example, REPLACE, MOVE and
147  // SOURCE_COPY operations are not significantly impacted by the chunk size,
148  // except for a few bytes overhead in the manifest to describe extra
149  // operations. On the other hand, splitting BSDIFF operations impacts the
150  // payload size since it is not possible to use the redundancy *between*
151  // chunks.
152  size_t soft_chunk_size = 2 * 1024 * 1024;
153
154  // TODO(deymo): Remove the block_size member and maybe replace it with a
155  // minimum alignment size for blocks (if needed). Algorithms should be able to
156  // pick the block_size they want, but for now only 4 KiB is supported.
157
158  // The block size used for all the operations in the manifest.
159  size_t block_size = 4096;
160};
161
162}  // namespace chromeos_update_engine
163
164#endif  // UPDATE_ENGINE_PAYLOAD_GENERATOR_PAYLOAD_GENERATION_CONFIG_H_
165