The structure currently described is very old and does not match
the current one after refactoring.
Change-Id: I2b39a6f14175f0478c7fc14698f4e477ce05351b
... to use docs.openstack.org . Also the deployment guide is no longer
maintained so remove the link to it.
Change-Id: I51378ae474e1edc515858ae629aa88a8b4d2c6a4
* Use context manager to open files
* Response codes are already checked within swiftclient methods
* etag is now returned by put_object method
Change-Id: I446118a314929c7d646c66bc2d8a0f1fa41e4fed
Because we run container side applications using the swift user, we
need a mechanism to limit number of processes launched inside storlet
containers so that user workloads do not consume all allowed pids in
host.
This introduces a new option to set pids limit in each container.
Change-Id: Idc07807ab7dba12c795d19d6405fc998e7b09893
This replaces the python script to update swift config files by set
of raw commands or functions in bash.
This also removes the hard-coded storlet-proxy-server.conf and
replaces it by the common internal-client.conf .
Change-Id: I45e92e9323d144230d5850274692c5cbf6aa0014
This renames a few options of docker gateway to generalize name of
these options in case we support any different runtimes such as podman.
- docker_repo to container_image_namespace
- default_docker_image to default_container_image
Change-Id: Id256e85f79912b5f5130e259475e9c9db28d7912
Docker supports binding a container to specific cpu cores memory nodes.
This introduces a few options to allow operators to limit resources
used by storlet containers.
Change-Id: Ifa734850f4284724a5ee06a172b81e04e5fb7015
We can omit try-except in case we just re-raise all exceptions.
Also, we should fail in case fd is requested but the log file is not
open.
Change-Id: I2d8588cc8356e32f5bb199416243b52edad30ef6
Now swift and storlet daemon inside containers run with consistent uid
so we don't need group/other permissions.
Also chown should be executed before actual file content is written,
so that the content is not read by a different user.
Closes-Bug: #2047723
Change-Id: I7790e51556875be1fc6438d1e2c599b693ca3b5b
... because the behavior is different in recent versions. The same note
was already removed from requirements.txt.
Change-Id: Icd256666bf50d8c43535079399576d6626f51b0c
... instead of implementing our own logics. Also, the fstab entry is
already managed by the core devstack.
Change-Id: I6a8fbcfebf1e501f41ac82117688572533ae624d
