search

Praqma / praqma-rnd

Praqma research and development work issue tracker
MIT License
0 stars 1 forks source link

Docker - Base Training Image with Teams In Space Concept #16

Open TheDukeDK opened 7 years ago

TheDukeDK commented 7 years ago

This issue is a discussion issue. The intent is to get some feedback...

Teams in Space(TIS) is a Git repository provided by Atlassian. It contains some good data which can be used for training. I have gotten access to the Bitbucket repository. It is not public due to licenses. Atlassian experts can request access to the repository. So we need to keep it somewhere private. Our own docker registry?

Right now it Includes the following:

It does not have the Portfolio plugin :-(

I have forked the bitbucket repository, so we can pull updates from Atlassian and provide access to other Praqma personnel for training sessions.

The questions:

  1. Should we do docker here? Is this overkill?
  2. Should we do a docker file to build the base image? My first thoughts are yes. We want it reproducible.
  3. If we make a Dockerfile for building the image then we need to provide a key for the clone command. What is the best approach for this?
    • one option is to embed the key in a based image. But this is not very secure.
    • Another option is to pass it in as an ENV variable at build time?
    • A final, and maybe better, option is to use something like Vault in another image, along with docker compose, to retrieve the key. Is this possible?
  4. What should the image layers look like? My first Idea is something like this:
    • A base image with TIS cloned and installed.
    • Other training specific images with data added on top by adjusting the base image and committing the changes. For example a Portfolio training image, A Jira admin training image, a Service Desk training image, etc..
TheDukeDK commented 7 years ago

@buep @hoeghh @drBosse : Looking for some feedback here. What do you guys think?

buep commented 7 years ago

When you have a fork of the repo, we should share it internally in Praqma either by a praqma internal git repo clone and/or docker image. I would like both.

Is it possible to configure automation from your fork TIS to a Praqma github private repo? E.g. by a API key with access to your fork, plus our Jenkins server? So when TIS is updated our private repo is also?

Then we add our own docker file, build an image and push to a private registry on our docker hub. Then we have reproducible images. If we have a license key in the image, and push to our private docker hub repo, then that should be fine enough. We just need to make sure we don't share it outside Praqma scope.

TheDukeDK commented 7 years ago

@buep I know we can import from BitBucket to GitHub. Not sure about a "mirror", for lack of a better word, but this would be the right solution in my opinion. Just not sure it is possible. I will use some time to consider the options. But first thoughts are along the same lines as yours. We will probably need to use Jenkins to keep them in sync.

TheDukeDK commented 7 years ago

@buep : I have given you access to fork on BitBucket. https://bitbucket.org/tim-praqma/teams-in-space-demo