Skip to content

Milestones

List view

  • We plan to move into mongodb from MySQL for managing cloud metrics. * We may redesign databases. * We may need to change queries. Tasks * Install mongodb in local * Migrate current databases into mongodb * Create mongodb functions to perform like mysql functions * Test mongodb with cloud metrics Additional task for web service with Flask (Abstract) * Create statistic table for displaying cloud usage on the web * Test with mongodb * * This task should be re examined later.

    No due date
    0/1 issues closed
  • Our developments should be documented on the portal webpages or local files. There are two aspects; a user-oriented guide/tutorial and a system administrative note/instruction. On the source codes, there also should be docstring to explain functions, objects, classes, etc. This has to be done when any changes are made.

    Overdue by 13 year(s)
    Due by March 16, 2013
    1/7 issues closed
  • No due date
    4/7 issues closed
  • We are aiming to achieve high quality of software development in terms of open source perspective. Well defined functions and reasonably separated logic would be helpful to understand, also not too much customized or abstracted code lines do not hurt software development. Further reading * Diomidis Spinellis. Code Quality: The Open Source Perspective. Addison Wesley, Boston, MA, 2006. * Robert C. Martin. Clean Code: A Handbook of Agile Software Craftsmanship, 2008

    No due date
    0/3 issues closed
  • The metrics tool keeps looking for meaningful factors that can be extracted from log files, command tools, etc. It should cover eucalyptus 2.0 and 3.0+ as well. Since there are new entries in logs of eucalyptus 3.0+, we will investigate metrics in two tracks. First, we try to find out some metrics via an existing log entries (2.0). Second, we also try new one (3.0+).

    No due date
    4/18 issues closed
  • We need to finish or abandon incomplete tasks as soon as possible. Through this milestone Hyungro Lee will identify every tasks and list here what tasks need to be done and what tasks need to be diminished.

    No due date
    1/3 issues closed
  • This Milestone is to facilitate the deployment of our tools into the production portal and the production environment. a) we need an estimate how much data is generated and to be stored each day not only in the log files, but also the database b) we need to deploy the "final" scripts in the production environment c) we need to identify a pathway to include the pages generated into the html directory into the portal d) we need to place the db into production server based on data provided in a) This task will most likely be managed in jira once coding is completed. Notes Production-level code may has following attributes: * error handling * edge case condition handling * portable to multiple platforms * well thought out naming of variables, functions, methods, classes, parameters etc * testability * documentation * optimizations for code space or speed * user interface considerations

    No due date
    0/1 issues closed