rofrano / devops-workshop Goto Github PK

As a: Service Provider
I need: the ability to deploy my service using Docker
So that: I can move with speed and agility

Assumptions:

• Need to create a Dockerfle for the service
• Need to update Travis CI to use Docker version

Acceptance Criteria:

Given I have my service in a Docker image
When I user docker run
Then I should have my service running in a contatiner

As a: Service Provider
I need: the ability to deploy my service on Kubernetes
So that: I can easily scale it out horizontally as needed

Assumptions:

• Need to create Kubernetes manifests
• Need a to deploy a Redis database in Kubernetes

Tasks:

• Create a deployment.yaml file for service
• Create a service.yaml file for the service
• Create a redis.yaml file to deploy Redis as a StatefulService

Acceptance Criteria:

Given I have my service in Kubernetes
When I ask Kubernetes to scale to 5 instance
Then I should have 5 instances of my service running

As a: Developer
I need: the ability to continuously test my code
So that: I can know if a Pull Request has broken the build

Assumptions:

• We will use Travis CI
• Need to tell Travis CI that we need a Redis database

Acceptance Criteria:

Given I have set up Travis CI
When I make a Pull Request
Then my automated tests should run automatically
And if they fail the build will be stopped

As a: User
I need: the ability to delete a counter
So that: I can remove unwanted counters

Assumptions:

• Deleting a counter will remove it from the database
• If the counter doesn't exist a 204_NO_CONTENT will be returned

Acceptance Criteria:

Given I have counter named foo
When I delete the counter named foo
Then I should receive a 204_NO_CONTENT
And I retrieve the counter named foo
Then I should receive 404_NOT_FOUND
And I delete the counter named foo again
Then I should receive a 204_NO_CONTENT

As a: User
I need: a way to register a hit on the counter
So that: it increments with every access

Assumptions:

• Calling the GET /counter URl will increment the counter
• No need for the counter to be persistent for now

Acceptance Criteria:

Given I have a counter
When I call the /counter URL
Then I should see the counter increment

As a: Service Provider
I need: a minimal Flask service
So that: my developers have a starting point to add code

Assumptions:

• Only the root / URl needs to be defined
• Call it app.py for now

Acceptance Criteria:

Given I have a skeleton Flask app
When I call the / URL
Then I should see "Hello from Flask" returned

As a: User
I need: the hit counter to persist the last known count
So that: I don't loose track of the count after the service is restarted

Assumptions:

• We will use Redis as the persistent store
• A Redis image from Docker should be used

Tasks:

• Need to update the Vagrantfile with Redis Docker image
• Need to create a Model that uses Redis

Acceptance Criteria:

Given I have a persistent counter
When I advance the hit counter to 2
And I restart the hit counter service
And I call the hit /counter URL
Then I should see 3 returned from the service

As a: User
I need: the ability to create multiple RESTful counters
So that: I can keep track of multiple hit targets

Assumptions:

• We will implement using REST API guidelines
• Add ability to create multiple named counters
• Add ability to update counters by name

Tasks:

• Need to update root / URL to return json message
• Need to rename /counter to /counters
• Need to change GET to only return the counter
• Need to implemtent POST to create new counters
• Need to implement PUT to update multiple counters

Acceptance Criteria:

Given I have a multi-counter ability
When I create a counter named foo
And I update the counter named foo to 1
And I call the hit /counters/foo URL
Then I should see 1 returned from the service