Skip to content
This repository was archived by the owner on Apr 17, 2019. It is now read-only.

snapshot table.md

lang edited this page Mar 5, 2015 · 1 revision

Task List And Schedule of App "snapshot-table"

Stages

Here are definitions of all current planned stages of this app.

  1. All basic components of IRIS system, including the front-end SPA files, and the two level web services are ready to be packaged and deployed.

    • SPA - snapshot-table

      • can show the SR/package/submitter list for each snapshot
      • can support simple folding or pagination for the big table
    • Webgw - common part It should work with LDAP user authentication and can forward the http requests to internal services properly.

    • Service - snapinfo As the flask(py) based pure json-formated RESTful web api service, it will provide the interfaces for querying all the detailed information of each snapshot and the images. At first, snapinfo will query all information about BOSS processes by python-bossinfo to access the BOSS redis server directly.

  2. Enhancement of the features in Stage1

    • SPA - snapshot-table

      • can provide more user friendly interface to show the details of SR, pkg and submitters.
      • can support filters to limit the items in table
    • Service - snapinfo

      • can accept the daily/weekly pickup operations from release-engineers based on valid rbac checking.
      • can integrate the real testing results from CATS
      • provide a separated bossinfo service, and let snapinfo integrate the data by using http apis.

Schedule

  1. Stage1 due to 2012-11-14
  2. Stage2 due to 2012-11-28

Task List

  1. Stage1:

    • SPA - snapshot-table

      • based on current demo code, rewrite it using AMD module style, and start to use 'yeoman' to manage all the development/debugging/deployment tasks.
    • Webgw - common part

      • code ready
      • source code tree is in good shape for development and packaging
      • prepare the rpm packages in otctools
    • Service - snapinfo

      • code ready
      • source code tree is in good shape for development and packaging
      • prepare the rpm packages in otctools
    • Staging system setup

    • Deployment

    • Documentation

Clone this wiki locally