<commit_before>ceph-container
==============

![Ceph Daemon Stars](https://img.shields.io/docker/stars/ceph/daemon.svg)
![Ceph Daemon Pulls](https://img.shields.io/docker/pulls/ceph/daemon.svg)

Build Ceph into container images with upstream support for the latest few Ceph releases on
Ubuntu-based containers. ceph-container also supports builds for multiple distributions but does not
support the containers non-Ubuntu released images.


Find available container image tags
-----------------------------------

All tags can be found on the Docker Hub.
For the daemon-base tags [visit](https://hub.docker.com/r/ceph/daemon-base/tags/).
For the daemon tags [visit](https://hub.docker.com/r/ceph/daemon/tags/).

Alternatively, you can run the following command (install jq first):

```
$ curl -s https://registry.hub.docker.com/v2/repositories/ceph/daemon/tags/ | jq '."results"[] .name'
```

Be careful, by default the Docker API returns the first page with its 10 elements.
To improve your `curl` you can pass the `https://registry.hub.docker.com/v2/repositories/ceph/daemon/tags/?page=2`


Core Components
---------------

- [`ceph/daemon-base`](src/daemon-base/): Base container image containing Ceph core components.
- [`ceph/daemon`](daemon/): All-in-one container containing all Ceph daemons.

See README files in subdirectories for instructions on using containers.


Building ceph-container
-----------------------
`make` is used for ceph-container builds. See `make help` for all make options.

### Specifying flavors for make
The `make` tooling allows the environment variable `FLAVORS` to be optionally set by the user to
define which flavors to operate on. Flavor specifications follow a strict format that declares what
ceph-container source to use, what architecture to build for, and what container image to use as the
base for the build. See `make help` for a full description.

### Building a single flavor
Once the flavor is selected, specify its name in the `FLAVORS` environment variable and call the
`build` target:
```
make FLAVORS=luminous,x86_64,centos,7,_,centos,7 build
```

### Building multiple flavors
Multiple flavors are specified by separating each flavor by a space and surrounding the entire
specification in quotes and built the same as a single flavor:
```
make FLAVORS="luminous,x86_64,centos,7,_,centos,7 kraken,x86_64,centos,7,_,centos,7"  build
```

Flavors can be built in parallel easily with the `build.parallel` target:
```
make FLAVORS="<flavor> <other flavor> <...>" build.parallel
```<commit_msg>Presentations: Adding reworking ceph-container<commit_after>ceph-container
==============

![Ceph Daemon Stars](https://img.shields.io/docker/stars/ceph/daemon.svg)
![Ceph Daemon Pulls](https://img.shields.io/docker/pulls/ceph/daemon.svg)

Build Ceph into container images with upstream support for the latest few Ceph releases on
Ubuntu-based containers. ceph-container also supports builds for multiple distributions but does not
support the containers non-Ubuntu released images.


Find available container image tags
-----------------------------------

All tags can be found on the Docker Hub.
For the daemon-base tags [visit](https://hub.docker.com/r/ceph/daemon-base/tags/).
For the daemon tags [visit](https://hub.docker.com/r/ceph/daemon/tags/).

Alternatively, you can run the following command (install jq first):

```
$ curl -s https://registry.hub.docker.com/v2/repositories/ceph/daemon/tags/ | jq '."results"[] .name'
```

Be careful, by default the Docker API returns the first page with its 10 elements.
To improve your `curl` you can pass the `https://registry.hub.docker.com/v2/repositories/ceph/daemon/tags/?page=2`


Core Components
---------------

- [`ceph/daemon-base`](src/daemon-base/): Base container image containing Ceph core components.
- [`ceph/daemon`](daemon/): All-in-one container containing all Ceph daemons.

See README files in subdirectories for instructions on using containers.


Building ceph-container
-----------------------
`make` is used for ceph-container builds. See `make help` for all make options.

### Specifying flavors for make
The `make` tooling allows the environment variable `FLAVORS` to be optionally set by the user to
define which flavors to operate on. Flavor specifications follow a strict format that declares what
ceph-container source to use, what architecture to build for, and what container image to use as the
base for the build. See `make help` for a full description.

### Building a single flavor
Once the flavor is selected, specify its name in the `FLAVORS` environment variable and call the
`build` target:
```
make FLAVORS=luminous,x86_64,centos,7,_,centos,7 build
```

### Building multiple flavors
Multiple flavors are specified by separating each flavor by a space and surrounding the entire
specification in quotes and built the same as a single flavor:
```
make FLAVORS="luminous,x86_64,centos,7,_,centos,7 kraken,x86_64,centos,7,_,centos,7"  build
```

Flavors can be built in parallel easily with the `build.parallel` target:
```
make FLAVORS="<flavor> <other flavor> <...>" build.parallel
```

## Presentations

<p><a href="https://docs.google.com/presentation/d/e/2PACX-1vQsN2ywxSibTSH-p-0PpNWpKTSfSSLx3gApetKzmuLiMwKm0Sk9mg-Swnae-m5tKkHwCGULDfFOJsvJ/pub?start=false&loop=false&delayms=3000"> Restructuring ceph-container </a></p>
{'fraction_non_alphanumeric': 0.13157894736842105, 'fraction_numerical': 0.010824934677118328, 'mean_word_length': 4.259077526987243, 'pattern_counts': {'":': 0, '<': 13, '<?xml version=': 0, '>': 13, 'https://': 13, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5464254', 'n_tokens_mistral': 1691, 'n_tokens_neox': 1576, 'n_words': 575}