PCM Development/Palladio Concall/Developer Meeting 08.11.2017

Aus SDQ-Wiki
  • Participants
    • Dominik Werle (KIT)
    • Sandro Koch (KIT)
    • Kateryna Yurchenko (KIT)
    • Christian Stier (FZI)
    • Stephan Seifermann, host (FZI)
    • Markus Frank (Uni Stuttgart)
    • Angelika Kaplan (KIT)
    • Manar Matzkatli (KIT)
    • Felix Willnecker (Fortiss)
    • Jörg Henß (FZI)
    • Max Scheerer (FZI)
    • Sebastian Krach (FZI)
    • Maximilian Walter (KIT)
    • Misha Strittmatter, log (KIT)
    • Emre Taspolatoglu (FZI)
  • Felix-Extension
    • Description
      • Introduction of new resource: Memory
      • Garbage collection behavior via probabilities
      • Memory is partitioned into multiple generations
      • Abstracts from System Implementation
      • Generic (not much knowledge of GC required)
    • Current implementation
      • For Palladio 3.4.1 stable
      • Metamodel: 2 two new elements for ResourceContainer
      • Uses Sensorframework
      • Implemented for GMF Editors
      • Supported by SimuCom, EventSim
      • Currently inherits from AbstractSchedulingResource
      • Listener is hardcoded to calculate memory utilization
    • Should be integrated as optional extension
      • Possible to implement as totally different model?
        • Using extension of Micha Hauck?
        • Problematic, as memory simulation requires state
    • Felix Prepares Patch (for 4.1)
      • But cannot restructure the solution (to make it as optional extension)
      • Touched Palladio Modules: PCM, PCM Editor, SimuCom, SensoFramework, EventSim, Scheduler, GMF, Sirius
      • The Palladio devs will integrate it (as a optional feature?)
  • SimuCom deprecation
    • According to Steffen SimuCom is deprecated
    • But is still shipped (with the drop and marketplace)
    • Still two blockers to ship SimuLizar as default
      • Usability (e.g. provide default measuring points)
      • Reliability simulation
  • New maintainers for Palladio projects
    • ProtoCom: Stephan, Maintenance on Error
    • SimuLizar: Sebastian
    • Descartes: ausblenden/löschen
    • BySuite: Stephan
    • DecisionRequirements: löschen
    • EventSim: Sandor
    • ExperimentAutomation: Sebastian
    • IntBIIS: Sando, neu aufnehmen
    • MDSD Profiles: Emre
    • MetricSpec: QUAL mergen, Stephan
    • SLO: Doc (Markus) Hilbrich
    • ExactScheduler: Markus F.
    • SoMoX: Manar
    • SSJ: Sanro
    • View-druf: can be removed, as according to Heiko the issue tracking of github is used
  • Migrate built infrastructure to Maven/Tycho
    • Buckminster is deprecated (Eclipse 4.4 required)
    • Remainder: see slides from Stephan
    • Action item: migration during coding evening at the start of 2018 (Stephan)
  • Interface Inheritance
    • See last concall
    • Affected modules: Metamodel (constraints), Simulators, Editors
    • Wo is interested in simulation support? (Stephan, Roman)
    • Warning: metamodel change may cascade into simulation engine
    • At first: hidden feature
    • Two(?) possibilities to deal with signature conflicts when inheriting
      • Disallow
      • Signature compatibility: co-variance, contra-variance
    • Action items:
      • Stephan looks at issues, tries to estimate effort
  • Distributed deployment of subsystems
    • Introduction of new notation element that shows which allocationContexts belong to the distributed subsystem
      • Already implemented and available in the nightly build
    • Change color of blob (black) EDITORS-210
    • Allow deletion of blob (to reassemble allocations) EDITORS-207
    • Hiding of blobs EDITORS-208
      • Show only if an allocation is selected (possible?)
      • Layer
    • new editor issue: disallow nesting of subsystems into theirself (subsystemception) EDITORS-209
  • If a subsystem is deployed multiple times, the model doesn't support to create allocations for the inner assemblies
    • The allocation diagram shows the inner allocations only once, and each of the allocations of the subsystems are seperated
      • This behavior is accepatable, in the best case the simulator can deal with unified deployment of inner assemblies of multiply assembled subsystems
    • Is a really rare special case
  • Documentation of stakes of stakeholders regarding simulators
    • Which simulators should be maintained?
    • Which should be the go-to simulator for new PhD students / new research projects?
    • If SimuCom is discontinued/deprecated, soon ProtoCom could be forced to follow the same path, as knowledge is lost
      • ProtoCom is useful for coupled simulation
        • However, coupled simulation is not tied to SimuCom
    • Should EventSim be ported to QUAL?
      • Throw a practical course student at it TODO: Sandro
    • A R exporter would be cool for QUAL
Abgerufen von „https://sdq.kastel.kit.edu/mediawiki-sdq-extern/index.php?title=PCM_Development/Palladio_Concall/Developer_Meeting_08.11.2017&oldid=27141“