SeaCloudsEU/SeaCloudsPlatform

Seamless adaptive multi-cloud management of service-based applications

Jose

@kiuby88

A DamGenerator issue

I agree with @rosogon

Andrea Turli

@andreaturli

where should it be set?

Jose

@kiuby88

from the catalog, I think

Andrea Turli

@andreaturli

ok sure, which component requires that URL?

the planner?

Jose

@kiuby88

MonitorManagerUrl is called from the planner.conf as monitorGeneratorURL

yes

the planner

Andrea Turli

@andreaturli

ok what’s the URL then?

Jose

@kiuby88

give me one minute

Román SG

@rosogon

It's the url of tower4clouds manager

Andrea Turli

@andreaturli

ok thanks @rosogon I’ll update the bom

Jose

@kiuby88

https://github.com/SeaCloudsEU/SeaCloudsPlatform/blob/master/planner/service/plannerconf.yml#L9-L10

Andrea Turli

@andreaturli

give me 1 minute

Jose

@kiuby88

monitorGeneratorURL: t4c host
monitorGeneratorPort: t4c port

Andrea Turli

@andreaturli

the host should be the IP or http://IP ?

Jose

@kiuby88

I think so

give me 2 minutes

please

Andrea Turli

@andreaturli

anything else missing for the planner?

currently I have

      - type: seaclouds-planner
        name: seaclouds-planner
        brooklyn.config:
          planner.discoverer.url: $brooklyn:formatString("http://%s:%s/", $brooklyn:component("discoverer").attributeWhenReady("host.address"), $brooklyn:component("discoverer").config("http.port"))
          planner.sla_generator.url: $brooklyn:component("sla-core").attributeWhenReady("main.uri")
          planner.grafana.url: $brooklyn:component("grafana").attributeWhenReady("host.address")
          planner.monitor_manager.url: $brooklyn:component("monitor-manager").attributeWhenReady("host.address")
          planner.monitor_manager.port: $brooklyn:component("monitor-manager").config("monitor.manager.port")
        launch.latch: $brooklyn:component("deployer").attributeWhenReady("service.isUp”)

Jose

@kiuby88

currently the URL is composed using a IP and a port from the DamGeneratorConfigBag.

here

Andrea Turli

@andreaturli

ok return new URL("http://" + monitorUrl + ":" + monitorPort + "”); monitorUrl is not an URL

Jose

@kiuby88

but if you can not obtain the standalone IP from the catalog.bom I can open a PR

Andrea Turli

@andreaturli

redeploying now, if ok I will commit

Jose

@kiuby88

let us know :)

Andrea Turli

@andreaturli

@kiuby88 what are the jars for the deployer?

ok @rosogon monitorGenerator solves the bug, now a new one

INFO  [2016-04-15 08:18:16,634] eu.seaclouds.platform.planner.core.utils.HttpHelper: Getting request for http://127.0.0.1:8080//seaclouds/commands/fromtemplate
ERROR [2016-04-15 08:18:16,660] io.dropwizard.jersey.errors.LoggingExceptionMapper: Error handling a request: 4e97174a8dec2bf2
! java.util.NoSuchElementException: null
! at java.util.Scanner.throwFor(Scanner.java:907) ~[na:1.7.0_95]
! at java.util.Scanner.next(Scanner.java:1416) ~[na:1.7.0_95]
! at eu.seaclouds.platform.planner.core.utils.HttpHelper.getRequest(HttpHelper.java:73) ~[planner-service.jar:na]
! at eu.seaclouds.platform.planner.core.application.agreements.AgreementGenerator.getAgreement(AgreementGenerator.java:67) ~[planner-service.jar:na]

Jose

@kiuby88

Andrea, give me 1 minute and I will send the jars

about the new issue

the problem is that planner requires SLA endpoint too

Andrea Turli

@andreaturli

no tell me the URLs, don’t send me anything

Jose

@kiuby88

here

sorry, I wanted to say the urls

Andrea Turli

@andreaturli

interesting there is no mention on the README https://github.com/SeaCloudsEU/SeaCloudsPlatform/blob/8edb7235a12921550cc82435ba6e9537633a3a80/planner/README.md#L10-L10

Jose

@kiuby88

I am not stupid hahahahaha

Román SG

@rosogon

I think the sla generator url is passed to the planner.

Andrea Turli

@andreaturli

sla endpoint is the sla-core url?

Román SG

@rosogon

I saw it filled in the conf yesterday.

Yes

Andrea Turli

@andreaturli

      - type: seaclouds-planner
        name: seaclouds-planner
        brooklyn.config:
          planner.discoverer.url: $brooklyn:formatString("http://%s:%s/", $brooklyn:component("discoverer").attributeWhenReady("host.address"), $brooklyn:component("discoverer").config("http.port"))
          planner.sla_generator.url: $brooklyn:component("sla-core").attributeWhenReady("main.uri")
          planner.grafana.url: $brooklyn:component("grafana").attributeWhenReady("host.address")
          planner.monitor_manager.url: $brooklyn:component("monitor-manager").attributeWhenReady("host.address")
          planner.monitor_manager.port: $brooklyn:component("monitor-manager").config("monitor.manager.port")
        launch.latch: $brooklyn:component("deployer").attributeWhenReady("service.isUp”)

sla_generator is there

Jose

@kiuby88

I see

Andrea Turli

@andreaturli

and brooklyn resolves it as "SLA_GENERATOR_URL="http://127.0.0.1:8080/“"

I think the problem is the trailing slash in the end

as the log says

eu.seaclouds.platform.planner.core.utils.HttpHelper: Getting request for http://127.0.0.1:8080//seaclouds/commands/fromtemplate

Jose

@kiuby88

Probably, it is not the correct URL

could you paste here the planner/conf.yml?

Where communities thrive

People

Repo info

Activity