unknown 1-87e4ea39 1 src/site/apt/architecture.apt.vm 49-50 30 unknown unknown@0pdd.com The specification is still rather vague for now. I haven't written any assumptions here just yet. Let's write them down here as they come up. DES 261 1-422bba33 1 src/site/apt/architecture.apt.vm 56-59 30 unknown unknown@0pdd.com We should have a class diagram here. Ideally, we should have a tool that autogenerates the diagrams at deploy time from text data. However, we haven't decided yet on what this tool should be. Once that's been agreed upon, include the class diagrams right here. DES unknown 261-83965aa4 261 src/jekyll/_posts/2014/apr/2014-04-01-architecture.md 39-42 30 unknown unknown@0pdd.com Our data model class diagrams are now generated by Requs and included in the SRS. But, we also need to show the classes and interfaces that involve the other parts of the system, e.g. API infrastructure, UI classes, data persistence classes, etc. DES unknown 1-0c2dd6e7 1 src/site/apt/architecture.apt.vm 60-62 30 unknown unknown@0pdd.com Let's define the packaging structure of Thindeck. Describe the purposes of each package, the classes and resources that they contain, etc. Include a diagram showing how they are all related. DES unknown 1-8220001d 1 src/site/apt/architecture.apt.vm 68-71 30 unknown unknown@0pdd.com So far we don't know what components we're going to use. Let's find out, and document those decisions here. Think about what we're going to need here - APIs for services that we're going to use, code libraries, web framework, etc. DES unknown 1-21a7e6b2 1 src/site/apt/architecture.apt.vm 77-79 30 unknown unknown@0pdd.com We don't know what the system looks like when it's been deployed. Let's document that here. Stuff that we might need to think about: 1) Web hosting, 2) Code repository (Github, most likely), 3) Data hosting DES unknown 1-4e36e10e 1 src/site/apt/architecture.apt.vm 85-86 30 unknown unknown@0pdd.com Requs should automatically generate the use case sequence diagrams. It doesn't support it yet, but when it does, let's include that here. DES unknown 1-0f336fa3 1 src/site/apt/architecture.apt.vm 92-93 30 unknown unknown@0pdd.com We need to identify the risks associated with this project. Let's document those risks in this section. DES unknown 1-2ac4b43a 1 src/site/apt/architecture.apt.vm 99-100 30 unknown unknown@0pdd.com Let's document the architectural and design decisions in this section. DES unknown 1-9b3a63bd 1 target/site/architecture.html 106-108 30 unknown unknown@0pdd.com Let's define the packaging structure of Thindeck. Describe the purposes of each package, the classes and resources that they contain, etc. Include a diagram showing how they are all related. DES unknown 239-59e78fdb 239 src/jekyll/_posts/2014/jun/2014-06-24-component-view.md 162-165 30 unknown unknown@0pdd.com How should we decide which hostname needs more containers? I'm not sure how to do it. Should be a combination of factors, including data from Meter. It's important to have at least three running containers for any repository. IMP unknown 239-fde3f532 239 src/jekyll/_posts/2014/jun/2014-06-24-component-view.md 172-174 30 unknown unknown@0pdd.com How we decide when to start/stop Tanks? I'm not sure how to make such a decision. Should be a combination of factors. IMP unknown 136-94e0aa31 136 thindeck-cockpit/src/main/webapp/xsl/stats.xsl 41-41 30 unknown unknown@0pdd.com Create page 'Runtime stats'. IMP unknown 136-59781d81 136 thindeck-cockpit/src/main/webapp/xsl/welcome.xsl 41-41 30 unknown unknown@0pdd.com Fill the text of 'how it work' part. IMP unknown 136-1ffa9f73 136 thindeck-cockpit/src/main/webapp/xsl/welcome.xsl 47-47 30 unknown unknown@0pdd.com Fill the text of 'Pricing' part. IMP unknown 136-360ecdbc 136 thindeck-cockpit/src/main/webapp/xsl/welcome.xsl 55-56 30 unknown unknown@0pdd.com Fill the text of 'Terms of service' part. It might need to create separate page for that IMP unknown 136-c30c85e1 136 thindeck-cockpit/src/main/webapp/xsl/welcome.xsl 63-64 30 unknown unknown@0pdd.com Fill the text of 'Terms of service' part. It should be here. IMP unknown 256-65bbc8b6 256 src/jekyll/_posts/2014/apr/2014-04-01-architecture.md 125-126 30 unknown unknown@0pdd.com Let's document next set of decisions made, by removing ellipsis, from the above list. IMP unknown 256-25d36e08 256 src/jekyll/_posts/2014/aug/2014-08-03-packaging.md 20-20 30 unknown unknown@0pdd.com Add a diagram showing how packages are related. IMP 312 293-c68bbdc4 293 src/main/java/com/thindeck/steps/LoadBalancer.java 40-44 30 unknown unknown@0pdd.com Let's implement a class Nginx that implements this interface. It should be able to connect via SSH to a server that has Nginx installed. At the minimum, we should be update the Nginx configuration of the server it's connected to. This class will be used primarily for the UpdateLB step. See https://github.com/yegor256/thindeck/issues/303 for more details. IMP 345 312-b2cbc220 312 src/main/java/com/thindeck/steps/Nginx.java 67-68 30 unknown unknown@0pdd.com Handle case when given host is not yet configured, need to create basic main.conf and hosts.conf files, and add them to ngnix.conf. IMP unknown 345-7e2a1db1 345 src/main/java/com/thindeck/steps/Nginx.java 69-72 30 unknown unknown@0pdd.com When a *hosts.conf file is created for a new host, it should be included in nginx.conf so that it can be loaded by the Nginx server. See the explanation in in https://github.com/yegor256/thindeck/issues/347 for more details. IMP unknown 345-8793b688 345 src/main/java/com/thindeck/steps/Nginx.java 73-79 30 unknown unknown@0pdd.com Let's handle the file *main.conf, which should contain the server configuration for a given host. The file name is prefixed by the host name, e.g. the host "www.example.com" will have the file name "www.example.com.hosts.conf". If the file doesn't exist yet, we should create it and include it in nginx.conf. If it already exists, we should update it. See the Javadoc above or the explanation in https://github.com/yegor256/thindeck/issues/347 for more details. IMP unknown 345-06272fcc 345 src/main/java/com/thindeck/steps/Nginx.java 71-78 30 unknown unknown@0pdd.com Let's handle the file *main.conf, which should contain the server configuration for a given host. The file name is prefixed by the host name, e.g. the host "www.example.com" will have the file name "www.example.com.hosts.conf". If the file doesn't exist yet, we should create it and include it in nginx.conf. If it already exists, we should update it. See the Javadoc above or the explanation in https://github.com/yegor256/thindeck/issues/347 for more details. @checkstyle MultipleStringLiterals (300 lines) IMP unknown 345-f56694d0 345 src/main/java/com/thindeck/steps/Nginx.java 66-72 30 unknown unknown@0pdd.com Let's handle the file *main.conf, which should contain the server configuration for a given host. The file name is prefixed by the host name, e.g. the host "www.example.com" will have the file name "www.example.com.main.conf". If the file doesn't exist yet, we should create it and include it in nginx.conf. If it already exists, we should update it. See the Javadoc above or the explanation in https://github.com/yegor256/thindeck/issues/347 for more details. IMP unknown 312-375f6020 312 src/main/java/com/thindeck/steps/Nginx.java 69-70 30 unknown unknown@0pdd.com Handle case when given hosts is already in the load balancing group. IMP unknown 312-6fb7b082 312 src/main/java/com/thindeck/steps/Nginx.java 71-71 30 unknown unknown@0pdd.com Add a test for this class. IMP unknown 312-8be93123 312 src/test/java/com/thindeck/steps/NginxTest.java 51-52 30 unknown unknown@0pdd.com Create a test to check that ngnix process receives HUP signal, after configuration update. IMP 311 293-6e4765a2 293 src/test/java/com/thindeck/steps/UpdateLBTest.java 52-58 30 unknown unknown@0pdd.com The test is currently ignored for two reasons: 1. The schema memo.xsd does not yet define the domain element. The test will fail because the XML validation will throw an exception. 2. UpdateLB is not yet implemented, which means the verify statements will fail even if the Memo XML is valid. Let's address these issues and enable this test. See Github issue https://github.com/yegor256/thindeck/issues/308 for further details. IMP unknown 311-b0b102b2 311 src/test/java/com/thindeck/steps/UpdateLBTest.java 52-54 30 unknown unknown@0pdd.com The test is currently ignored because UpdateLB is not yet implemented. Let's implement it and enable the test. See Github issue https://github.com/yegor256/thindeck/issues/308 for further details. IMP 310 291-536f8d9b 291 src/test/java/com/thindeck/steps/ReadConfigTest.java 57-60 30 unknown unknown@0pdd.com This test is currently ignored because ReadConfig is not yet implemented. Let's implement it, and have it read the info from the .thindeck.yml file of the repository root and update the Memo XML. See https://github.com/yegor256/thindeck/issues/291 for further details. IMP 369 310-82db8b8c 310 src/main/java/com/thindeck/steps/ReadConfig.java 53-55 30 unknown unknown@0pdd.com Add check if domains and ports are already in memo. Current implementation duplicates them if step is called several times on the same context. IMP unknown 369-8972f543 369 src/test/java/com/thindeck/steps/ReadConfigTest.java 59-61 30 unknown unknown@0pdd.com This unit test additionally checks if step called on the same context does not duplicate domains and ports. It should be put into another unit test, instead. IMP 319 289-341cbc3a 289 pom.xml 480-481 30 unknown unknown@0pdd.com Increase test code coverage >= 80% for all packages and uncomment lines below. IMP unknown 319-be3482ea 319 src/test/java/com/thindeck/life/LifecycleTest.java 57-57 30 unknown unknown@0pdd.com When jcabi-aspects#95 is fixed enable this test. IMP 351 319-17808bfb 319 src/test/java/com/thindeck/life/LifecycleTest.java 81-81 30 unknown unknown@0pdd.com Migrate to com.thindeck.api.mock classes instead of mockito. IMP unknown 351-ebb2c3b5 351 src/test/java/com/thindeck/life/LifecycleTest.java 81-83 30 unknown unknown@0pdd.com Implement MkScenario and MkStep. Rewrite the test after that using mocks from com.thindeck.api.mock package instead of mockito. IMP 554 319 0 IMP 319-6d18aceb 710-712 Increase code coverage > 30%, by uncommenting the lines below and writting test classes. pom.xml Yegor Bugayenko yegor256@gmail.com 580 319 0 DEV 319-9b930429 602-604 Increase code coverage > 30%, by uncommenting the lines below and writing test classes. pom.xml @yegor256 yegor256@gmail.com unknown 290-3defbeba 290 src/main/java/com/thindeck/cockpit/ReposRs.java 93-93 30 unknown unknown@0pdd.com Add a CasperJS test for adding repositories by user. IMP 322 290-ed461ae0 290 src/main/java/com/thindeck/dynamo/DyBase.java 47-47 30 unknown unknown@0pdd.com Implement user, repos and txn methods to retrieve data from IMP 372 322-31a411b0 322 src/main/java/com/thindeck/dynamo/DyBase.java 47-47 30 unknown unknown@0pdd.com Implement txn method to retrieve data from appropriate table. IMP 462 372-437563d3 372 src/main/java/com/thindeck/dynamo/DyTxn.java 60-60 30 unknown unknown@0pdd.com increment should use actions fetched from item. IMP unknown 462-c5de49b4 462 src/main/java/com/thindeck/dynamo/DyContext.java 45-46 30 DyContext.memo() should be implemented. This method should return the Memo object that will use in this context. IMP oruam85 oruam85@gmail.com unknown 462-ec070d26 462 src/main/java/com/thindeck/dynamo/DyContext.java 52-53 30 DyContext.log() should be implemented. This method should add a new line in the log. IMP oruam85 oruam85@gmail.com 464 372-6dfa5421 372 src/test/java/com/thindeck/dynamo/DyBaseTest.java 66-66 30 unknown unknown@0pdd.com should retrieve DyTxn. IMP unknown 464-b7102912 464 src/test/java/com/thindeck/dynamo/DyBaseTest.java 68-68 30 unknown unknown@0pdd.com Remove the @Ignore this when DyTxn is fully implemented. IMP 373 322-5e7e33aa 322 src/main/java/com/thindeck/dynamo/DyRepo.java 43-43 30 unknown unknown@0pdd.com Implement tasks and memo methods. IMP 405 373-67a7ac85 373 src/main/java/com/thindeck/dynamo/DyRepo.java 44-44 30 unknown unknown@0pdd.com Implement memo method. IMP unknown 405-d6ee4a6b 405 src/main/java/com/thindeck/dynamo/DyMemo.java 47-47 30 unknown unknown@0pdd.com implement update. IMP 406 373-e9bbc535 373 src/main/java/com/thindeck/dynamo/DyTasks.java 46-46 30 unknown unknown@0pdd.com Implement get and open methods. IMP unknown 406-e0d78f7e 406 src/main/java/com/thindeck/dynamo/DyTask.java 46-46 30 unknown unknown@0pdd.com Implement command method. IMP 420 406-14dae9d0 406 src/main/java/com/thindeck/dynamo/DyTask.java 47-47 30 unknown unknown@0pdd.com Implement scenario method. IMP unknown 420-427af42c 420 src/main/java/com/thindeck/dynamo/DyScenario.java 42-42 30 unknown unknown@0pdd.com Implement steps method - example in OnDeploy. Task command will determine steps. IMP unknown 406-b5fe8676 406 src/main/java/com/thindeck/dynamo/DyTasks.java 50-50 30 unknown unknown@0pdd.com Implement open method. IMP unknown 373-400c0a90 373 src/main/java/com/thindeck/dynamo/DyTasks.java 47-47 30 unknown unknown@0pdd.com Implement all and add methods. IMP unknown 322-1ad9bb23 322 src/main/java/com/thindeck/dynamo/DyRepos.java 43-43 30 unknown unknown@0pdd.com Implement iterate method. IMP 370 322-123c6c41 322 src/main/java/com/thindeck/dynamo/DyRepos.java 44-44 30 unknown unknown@0pdd.com Create test for this class when jcabi/jcabi-dynamo#13 is done. IMP unknown 370-bb822dca 370 src/main/java/com/thindeck/dynamo/DyRepos.java 48-48 30 unknown unknown@0pdd.com Create test for #add new repo IMP 374 322-75940d12 322 src/main/java/com/thindeck/dynamo/DyUser.java 43-43 30 unknown unknown@0pdd.com Implement repos and usage methods. IMP 409 374-bb504035 374 src/main/java/com/thindeck/dynamo/DyUser.java 44-50 30 unknown unknown@0pdd.com At the moment, the repos() method returns all Repos associated with the Dynamo region, and this is definitely incorrect. I think we need to refactor DyRepos in order to include a user criteria (probably URN) in its constructor, and have DyUser pass it so that it will only return the associated criteria. I'm not completely sure about this design, feel free to implement something else if you think it's wrong. The intuition behind it is that we should only get the repos associated with the current user. IMP unknown 409-272f0225 409 src/main/java/com/thindeck/api/Repo.java 46-48 30 Let's add a new method User user(). It should return the User whom the Repo is associated to. Let's also add implementations in the classes that implement this interface. IMP Carlos Miranda carlosmiranda@users.noreply.github.com 408 374-a01072dc 374 src/main/java/com/thindeck/dynamo/DyUser.java 51-53 30 unknown unknown@0pdd.com Implement usage method. To do this we need to implement a class DyUsage that implements the Usage interface. This will obtain the usage associated to this user from Dynamo DB. IMP unknown 408-195c40b4 408 src/main/java/com/thindeck/dynamo/DyUsage.java 69-71 30 Let's implement the add() method. This method should add the supplied Value to the usage info of the current user. Make sure to include unit tests for this method in DyUsageTest. IMP Carlos Miranda carlosmiranda@users.noreply.github.com unknown 408-b5d67474 408 src/main/java/com/thindeck/dynamo/DyUsage.java 77-79 30 Let's implement the select() method. This method should return the values that fit the given criteria (user and date range). Make sure to include unit tests for this method in DyUsageTest. IMP Carlos Miranda carlosmiranda@users.noreply.github.com unknown 408-75ca2bde 408 src/main/java/com/thindeck/dynamo/DyUsage.java 85-87 30 Let's implement the sum() method. This method should return the aggregate sum of values that fit the given criteria. Make sure to include unit tests for this method in DyUsageTest. IMP Carlos Miranda carlosmiranda@users.noreply.github.com 410 374-c45270af 374 src/test/java/com/thindeck/dynamo/DyUserTest.java 52-54 30 unknown unknown@0pdd.com We should create an integration test for DyUser. Let's call it DyUserITCase. It should test whether DyUser can perform its operations on a real (local) Dynamo server. When done, ensure that this puzzle is removed. IMP unknown 410-108e5987 410 src/test/java/com/thindeck/dynamo/DyUserTestITCase.java 45-45 30 Implement an integration test for DyUser.repos() IMP Adam Siemion adam.siemion+github@gmail.com unknown 322-7e6f773d 322 src/test/java/com/thindeck/dynamo/DyBaseTest.java 55-55 30 unknown unknown@0pdd.com Enable this test when jcabi/jcabi-dynamo#13 is done. IMP 321 290-5f41f67f 290 src/main/java/com/thindeck/dynamo/DyBase.java 49-50 30 unknown unknown@0pdd.com Add dynamo maven plugin and create IT tests for dynamo based classes. IMP 341 321-7e1601a9 321 src/test/java/dynamo/DyBaseITCase.java 51-54 30 unknown unknown@0pdd.com DyBase should be implemented to make this test pass. You should make sure the DynamoDB Local has all the required tables, and all methods of all API-classes are implemented in com.thinkdeck.dynamo package IMP unknown 341-7e1601a9 341 src/test/java/dynamo/DyBaseITCase.java 52-55 30 unknown unknown@0pdd.com DyBase should be implemented to make this test pass. You should make sure the DynamoDB Local has all the required tables, and all methods of all API-classes are implemented in com.thinkdeck.dynamo package IMP unknown 341-c00e1503 341 src/test/java/dynamo/DyBaseITCase.java 53-54 30 unknown unknown@0pdd.com Add definition of tasks table to dynamoDb local and remove Ignore annotation. IMP unknown 491-fa4a100f 491 src/test/java/com/thindeck/dynamo/DyTasksTest.java 81-82 15 Unignore following test when #492 is finished and check the test passes IMP Artem Nakonechny wentwog@gmail.com 555 460 0 IMP 460-15412ba6 722-722 add EqualsAndHashCode verifier, e.g. http://www.jqno.nl/equalsverifier/ pom.xml Yegor Bugayenko yegor256@gmail.com