[almighty] Adhoc stack instance for PR code builds

[Karanbir Singh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Trying to think through how we achieve
https://github.com/almighty/almighty-jobs/issues/11

My current thinking is is that we deploy this PR against latest-master
of everything else. eg. a PR for 'core' would deploy against last
deployed api and db. Similarly the PR for core would deploy with the
last good UI and db etc ; but each time, the entire stack is brought
up as an app, and exposed under its own set of hostnames.[1]

Since the PR can come from different services, we would need to map
that via the hostname for clarity eg: core-pr25.<qdn> or ui-pr40.<qdn> e
tc

Two primary concerns at this point are :
1) it will almost always be a blank db.
2) it will be had to have a api change be visible in sync with a
proposed UI PR.

for (1) the easy route is to do a db dump from demo.db and load that
into the db brought up for the instance. However, given that this
brings with it the risk of exposing otherwise-private or privileged
info, we should never really do that. The middle ground between
no-data and all-the-data is to have a test dataset. Is this something
we can do ? if so, we can workout the mechanics of storing it and
loading/validating it.

Given the present dataset live at demo.a.i, generating this test data
might just be a case of dumping the present dataset into sql and
checking it into the git repos.

for (2) the solution will likely be in finding a way to parse and
establish the cross services PR relationship via the github comments.
However, given the complexity in that, and given that the actual CD
pipeline for the service as a while will need to be atomic - I propose
that the PR test stages also be atomic. If a UI function needs core
functionality, it should be built, tested and deployed via core first
then exercised via the UI.

regards

[1]: this would be done using a new-project in openshift, each service
will still come up as a service, and each piece of that will come up
as its own pod - so exactly how we run the demo.* services.

- -- 
Karanbir Singh, Project Lead, The CentOS Project, London, UK
Red Hat Ext. 8274455 | DID: 0044 207 009 4455
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJX0nb2AAoJEI3Oi2Mx7xbtMSwIAJYUjYk6ptQ8pLn28KvNffW4
ULTLU+YihVB/hpKEQmBE3U0MQmk/g2CR8v3VWJnafyKqFYlLsVjNTNT7XoGKj5JC
WX3afTkmCzAS8XB1p8dyI6TFh/L0dpz4GloTtgqrMwscwyT7l0LeVsAqDjKVHLQU
T1IyUaf4kdyDPf7ST9HyXOByW3aBJ8EIFPbsq6pwX9mh/qgtb7WVH3dGoxSxLmX6
rTxhp+kMUnWUF9y1LjzlxzZa3h/oExrJ1KMA1jwc6LHy6qh5hYczH0/vPxR6IJKL
xf38OmUXtjodKa00CYcqTVR+c8I13am1Gsgy4J+EN0lz8Q5cjHenaSbCjlKGTW0=
=rsNF
-----END PGP SIGNATURE-----