[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [atomic-devel] Moving osbs/atomic-reactor under projectatomic org on Github

On 07/03/2015 05:58 PM, Bohuslav Kabrda wrote:
Hi all,
on behalf of development team of OSBS (OpenShift Build Service), I'd like to propose moving three of our projects under projectatomic org on Github:


To describe the projects a bit:
- atomic-reactor is a Python library with command line interface for building docker images. For a complete set of features, see [1]
- osbs-client is a Python module and command line client for OpenShift Build Service.
- ansible-osbs is an ansible playbook to deploy OpenShift with atomic-reactor ready to build images.

To describe the whole system more: Builds are submitted through osbs-client by users/other tools. osbs-client communicates with OpenShift. OpenShift has an image with atomic-reactor installed inside, which is used to build requested images.

Hope this makes sense and thanks for considering. Questions are welcome!

I have couple of questions/concerns. But these should not stop moving the projects under projectatomic.

1. Why the name is "atomic-reactor"? I could not find the correlation atomic and atomic-reactor. IMO atomic-reactor should produce atomic images.

2. As of now we have overload of atomic name as prefix to many projects e.g. atomicapp , atomicapp-builder [1], atomic command and atomic host. So we are already having difficulty explaining the difference between those. So if we can avoid the atomic as the prefix unless it is really required, it would be good.

3.  What is the correlation between atomic-reactor and atomic-builder [1] ?

4. Does sti [2] uses atomic-reactor? is there any relation between these two?

[1] https://github.com/bkabrda/atomicapp-builder/
[2] https://github.com/openshift/source-to-image


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]