search

balanced-cookbooks / balanced-ci

Internal configuration for the Jekins CI environment
4 stars 1 forks source link

How do we configure the acceptance environment #3

Closed mjallday closed 10 years ago

mjallday commented 10 years ago

@coderanger @bninja what are your thoughts? I want to do this in two stages:

  1. up and running quickly

  2. optimise later once running

    Questions

    • What does this environment look like?

    IMO It should look like the test/prod environments ('cept maybe less instances of servers). Having at least 2 servers per service will give us the ability to do rolling deploys and test that migrations work as we'd expect them to under load. the current CI environment does not do this so let's do this in stage 2.

    • How do we configure this?

    The current acceptance environment is very simple, everything runs on a single machine. I'm OK with keeping this setup personally. But we configured it by hand. Is that acceptable for stage 1?

coderanger commented 10 years ago

I wouldn't think "the acceptance environment" would be a permanent thing, it would be something created by test-kitchen on the fly.

mjallday commented 10 years ago

noah mentioned creating a balanced-acceptance cookbook. it will provision a server and install the currently deployed versions of all applications.

need to figure out how to restore the db. maybe the db server is not ephemeral and separate from the acceptance server.

coderanger commented 10 years ago

+1 on separate DB. We can just make the cookbook use a well-known DNS name for the DB in all the various places.

coderanger commented 10 years ago

Update from talking with @mjallday and @mahmoudimus:

mahmoudimus commented 10 years ago

@mjallday @coderanger https://github.com/balanced-cookbooks/acceptance solves most of this right?

mahmoudimus commented 10 years ago

Closing this issue in favor of the acceptance repository.