Skip to content
This repository has been archived by the owner on Nov 23, 2023. It is now read-only.

Enable nix development environment #996

Closed
33 tasks
billgeo opened this issue Sep 22, 2021 · 2 comments · Fixed by #922
Closed
33 tasks

Enable nix development environment #996

billgeo opened this issue Sep 22, 2021 · 2 comments · Fixed by #922
Assignees
Labels
enabler story Enable to team to improve

Comments

@billgeo
Copy link
Contributor

billgeo commented Sep 22, 2021

Enabler

So that we can easily manage packages and simplify the development, we want to use nix tools to create and manage development environments

Acceptance Criteria

  • ...
  • ...

Additional context

Tasks

  • ...
  • ...

Definition of Ready

  • This story is ready to work on
    • Negotiable (team can decide how to design and implement)
    • Valuable (from a user perspective)
    • Estimate value applied (agreed by team)
    • Small (so as to fit within an iteration)
    • Testable (in principle, even if there isn't a test for it yet)
    • Environments are ready to meet definition of done
    • Resources required to implement will be ready
    • Everyone understands and agrees with the tasks to complete the story
    • Release value (e.g. Iteration 3) applied
    • Sprint value (e.g. Aug 1 - Aug 15) applied

Definition of Done

  • This story is done:
    • Acceptance criteria completed
    • Automated tests are passing
    • Code is peer reviewed and pushed to master
    • Deployed successfully to test environment
    • Checked against CODING guidelines
    • Relevant new tasks are added to backlog and communicated to the team
    • Important decisions recorded in the issue ticket
    • Readme/Changelog/Diagrams are updated
    • Product Owner has approved acceptance criteria as complete
    • Meets non-functional requirements:
      • Scalability (data): Can scale to 300TB of data and 100,000,000 files and ability to
        increase 10% every year
      • Scability (users): Can scale to 100 concurrent users
      • Cost: Data can be stored at < 0.5 NZD per GB per year
      • Performance: A large dataset (500 GB and 50,000 files - e.g. Akl aerial imagery) can be
        validated, imported and stored within 24 hours
      • Accessibility: Can be used from LINZ networks and the public internet
      • Availability: System available 24 hours a day and 7 days a week, this does not include
        maintenance windows < 4 hours and does not include operational support
      • Recoverability: RPO of fully imported datasets < 4 hours, RTO of a single 3 TB dataset <
        12 hours
@billgeo billgeo added the enabler story Enable to team to improve label Sep 22, 2021
@l0b0 l0b0 mentioned this issue Sep 22, 2021
12 tasks
@l0b0 l0b0 self-assigned this Sep 22, 2021
@billgeo
Copy link
Contributor Author

billgeo commented Sep 30, 2021

Remaining to do: split node.js changes to another issue.

@billgeo billgeo closed this as completed Sep 30, 2021
@billgeo billgeo reopened this Sep 30, 2021
@billgeo
Copy link
Contributor Author

billgeo commented Sep 30, 2021

And approve PR etc

@l0b0 l0b0 closed this as completed in #922 Sep 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enabler story Enable to team to improve
Development

Successfully merging a pull request may close this issue.

2 participants