You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Rajkumar Rajaratnam (JIRA)" <ji...@apache.org> on 2015/11/13 09:07:11 UTC

[jira] [Created] (STRATOS-1614) Issues with cartridge-config.properties file

Rajkumar Rajaratnam created STRATOS-1614:
--------------------------------------------

             Summary: Issues with cartridge-config.properties file
                 Key: STRATOS-1614
                 URL: https://issues.apache.org/jira/browse/STRATOS-1614
             Project: Stratos
          Issue Type: Bug
    Affects Versions: 4.1.4
            Reporter: Rajkumar Rajaratnam
            Assignee: Rajkumar Rajaratnam
            Priority: Blocker
             Fix For: 4.1.5


This file content is as below.

autoscaler.service.url=https://localhost:9443/services/AutoscalerService/
cloud.controller.service.url=https://localhost:9443/services/CloudControllerService/
stratos.manager.service.url=https://localhost:9443/services/StratosManagerService/
das.metering.dashboard.url=https://localhost:9444/portal/dashboards/metering-dashboard
das.monitoring.dashboard.url=https://localhost:9444/portal/dashboards/monitoring-dashboard
puppet.ip=127.0.0.1
puppet.hostname=puppet.stratos.apache.org
puppet.dns.available=false
puppet.environment=stratos

CartridgeConfigFileReader class (part of SM component) reads this file and set these properties as system variables and these system variables are used by other components like AS (to communicate with CC).

This approach have several issues.

a) Since the component's start up order is CC > AS > SM, there is no guarantee that these properties will be set before other components (AS or CC) start.
b) In distributed deployment, these properties will not be set in AS JVM.
c) This file contains information which are used by other components, not only cartridges. So this file name is misleading.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)