PCM Development/Palladio Concall/Minutes 20180709

Aus SDQ-Wiki

Participants

  • Uni Stuttgart
    • Floriment
    • Markus
    • Steffen
  • FZI
    • Christian
    • Jörg
    • Max
    • Sebastian
    • Stephan
  • Universiteit Utrecht
    • G. Maddodi

Follow up of Simulizar workshop

State of documentation (initial version was due to the concall)

  • Poweranalysis done (Christian), Action model and Extension almost done
  • Floriment:
    • Usage evolution, initial version created
  • Steffen:
    • cloud metrics done on high level
  • Markus:
    • Monitoring Repositories: students are working on it
    • Architectural templates:
      • Existing documentation (outdated) on Github, update as well? No. Just wiki.
      • initial version created
    • Refer to word-based tutorial from wiki
      • Future: Migrate to wiki
      • Christian: Convert to markdown with Pandoc;
        • What about screenshots and images?
      • Markus: Alternatively, out-of-service plugin for mediawiki
      • Next step: Markus sends document to Christian who checks the applicability of Pandoc
  • Sebastian: No progress
  • Dominik: No documentation as implementation not finished
  • Wiki pages go to Add-ons section and reference SimuLizar if they are specific to it; otherwise

Prototype of next gen Simulizar (Sebastian)

  • Process harder than expected
    • especially w/r/t Simucom Framework which has strong ties to process based simulation
  • New time estimate: Next concall

Possible student's theses (Max)

  • No progress - postpone to next concall

Status of removal of IModelAccess (Max)

  • Change impact analysis: No major issues
  • Next step: Check changes with Christian / Sebastian

Repair broken IResourceUriMeasuringPoints (Markus)

  • Checked out project
  • Could not reproduce the problem
    • Steffen assists, familiar with the problem

Impliciation of removing PCM measuring points without additional information (Dominik)

  • Clarification of question needed
  • Christian: Specific measuring points which do not add any specific information
  • Sufficient clarification

Assign tasks for cleanup of top 10 classes (wrt code)

  • Christian: no progress, realistically doable until next concall

Discussion about changes that shall be released

  • In view of less progress postpone to next concall

Status update

BWCloud (Max)

  • Jenkins slave running
  • Next step: Integrate with build server

OAuth2 for authorization (Dominik)

  • Works on local copy of jenkins
    • Usage of github login, permissions fine-grained controllable (Role-based fine-grained access control based on GitHub user, organization, team)
    • Alternative: Grant rights based on repository rights, but needs adaption to disallow build job manipulation for users with push rights (are currently granted, might be too permissive)
    • Christian: Best would be mixture of both, by default rights based on committers
      • Dominik: Probably not supported by plugins currently, but plugins could be adapted
    • Christian: Effect on builds which are not located on GitHub?
      • plugin does not grant any priviledges then. Need to find different solution. Mixture of current mechanism and github-based permissions is not possible.
  • Next step: Dominik sets up prototype, coordination with Stephan

Tycho builds (Stephan)

Build server

  • Exising-feature-complete (in comparison to Buckminster)
    • JavaDoc and Checkstyle work for tycho-based builds
  • Pipeline builds instead of template builds [1]
    • Workflow Enging build is based on pipelines
    • Build job definition much simpler (3 lines of code)
      • Needs to be done as groovy script on github
  • Student researcher works on migration of projects from svn+buckminster to Github+tycho
  • Who has created the TestPipeline? [2]
    • Steffen: I, it can be deleted.
  • Steffen: I am missing the Release button functionality
    • Stephan: Release plugin is incompatible with pipelines; Solution: parameterized build job with default values

QVT-R in workflow engine

  • Removal of QVT-R from WFE (Stephan)? Is anybody using it
    • Steffen: Last tool which used it is Chillies (Lucia)
    • Medini QVTr update site is down. Suggestion to remove it from future builds. Still contained in old versions.


Organizing Github repositories/organizations

  • JIRA/Github plugin for exchanging issues not available (at least for free)
    • Three options
      • Disable Github issues and only use JIRA
      • Shut down JIRA and only use Github
      • Name a person responsible for transferring issues into JIRA
      • Build plugin ourselves
    • Steffen: Shutdown github issue management and refer to Jira for issues
    • Stephan: Jira is more feature-rich

Jira speed issues

  • Large file transfers on every page load (10MB)
    • No time to research so far
  • Reduce amount of information to load on every page
    • Caching mechanisms work, but first page load takes long
  • Jira is running in parallel with build server, specs are suited for Jira only.
    • Steffen: Could we get a more powerful machine / another machine?
    • What about costs / administrative stuff
    • Steffen: BWCloud, currently progress with new hardware (10 times)
  • Students use interactive module of Jira for sprint planning

Next concall

  • 13.August 2018
Abgerufen von „https://sdq.kastel.kit.edu/mediawiki-sdq-extern/index.php?title=PCM_Development/Palladio_Concall/Minutes_20180709&oldid=28036“