SeaCloudsEU/SeaCloudsPlatform

Seamless adaptive multi-cloud management of service-based applications

perezp

@perezp

I had seen that line, but changing only this line will not make anything work.

Jose

@kiuby88

Sure

perezp

@perezp

ok :)

Sorry that I had not heard it :S

perezp

@perezp

I'm opening an issue with this, to point to this during the discussion.

Jose

@kiuby88

it is a Planner issue. @andreaturli and @rosogon were talking about another Discoverer issue (empty list returned)

Román SG

@rosogon

@andreaturli: There are some fields in the planner conf.yml unset:

influxdbURL: undefined
grafanaEndpoint: 127.0.0.1   # missing port
monitorGeneratorURL: undefined
monitorGeneratorPort: undefined

@PaoloCifariello : Planner README should also be updated with these

Andrea Turli

@andreaturli

monitorGenerator is not needed, @MicheleGuerriero said that planner doesn’t use it as a service

influxdb and grafana I don’t know, the doc is not clear

Román SG

@rosogon

You are right about monitorgenerator.

https://github.com/SeaCloudsEU/SeaCloudsPlatform/blob/master/monitor/monitoring-dam-generator-core/src/main/java/eu/seaclouds/monitor/monitoringdamgenerator/MonitoringDamGenerator.java#L91 throws a NPE because MonitorManagerUrl is not set. :S

Probably MonitorGeneratorURL var in the conf was reused to point to T4C manager.

I ask @PaoloCifariello and @kiuby88 to look at this.

Jose

@kiuby88

let me check it

Jose

@kiuby88

Yes, as Roman said monitorGeneratorURL and monitorGeneratorPort are T4C endpoint data. Currently MontorGenerator is required by MontoringDamGenerator interface, but probably it should be renamed probably something like monitorEndpointor t4cEndPoint. In any case, T4C endpoint information has to be added to the catalog. Because, rules and Datacollectors requires T4C endpoint. I can help on this. I can change the name of the Planner config and updating the DamGenerator configuration using the new configuration key names and I can test it

I will update #288 ASAP using artifacts from maven central

Andrea Turli

@andreaturli

@rosogon I’ve fixed the mongoimport thing

can you please try the new catalog.bom when you have time? thanks

Andrea Turli

@andreaturli

Screen Shot 2016-04-15 at 10.00.32 AM.png

@/all with the workaround for mongodb, step 3. passed, but step 4. doesn’t look good. I can see on the console.out of the planner the following

ERROR [2016-04-15 08:00:20,489] eu.seaclouds.platform.planner.core.application.ApplicationFacade: TargetType definition tosca.nodes.Computewas not foundso it will not added to DAM
INFO  [2016-04-15 08:00:20,492] eu.seaclouds.monitor.monitoringdamgenerator.MonitoringDamGenerator: Request received.
INFO  [2016-04-15 08:00:20,497] eu.seaclouds.monitor.monitoringdamgenerator.adpparsing.YAMLMonitorParser: Parsing the Abstract Deployment Model.
INFO  [2016-04-15 08:00:20,501] eu.seaclouds.monitor.monitoringdamgenerator.MonitoringDamGenerator: Generating monitoring information for host SoftLayer_Cloud_Servers_1core_2gb_AMS
INFO  [2016-04-15 08:00:20,501] eu.seaclouds.monitor.monitoringdamgenerator.rulesgenerators.InfrastructuralRulesGenerator: Generating infrastructural level monitoring rules for host: SoftLayer_Cloud_Servers_1core_2gb_AMS
ERROR [2016-04-15 08:00:20,512] io.dropwizard.jersey.errors.LoggingExceptionMapper: Error handling a request: dddf419b68b41ddd
! java.lang.NullPointerException: null
! at eu.seaclouds.monitor.monitoringdamgenerator.MonitoringDamGenerator.generateMonitoringInfo(MonitoringDamGenerator.java:91) ~[planner-service.jar:na]
! at eu.seaclouds.platform.planner.core.application.decorators.MonitoringInformationDecorator.generateMonitoringInfo(MonitoringInformationDecorator.java:53) ~[planner-service.jar:na]
! at eu.seaclouds.platform.planner.core.application.decorators.MonitoringInformationDecorator.apply(MonitoringInformationDecorator.java:46) ~[planner-service.jar:na]
! at eu.seaclouds.platform.planner.core.application.ApplicationFacadeDecoratorApplicator.applyDecorators(ApplicationFacadeDecoratorApplicator.java:14) ~[planner-service.jar:na]
! at eu.seaclouds.platform.planner.core.application.ApplicationFacade.applyDecorators(ApplicationFacade.java:140) ~[planner-service.jar:na]
! at eu.seaclouds.platform.planner.core.application.ApplicationFacade.generateDam(ApplicationFacade.java:111) ~[planner-service.jar:na]
! at eu.seaclouds.platform.planner.core.DamGenerator.generateDam(DamGenerator.java:71) ~[planner-service.jar:na]
! at eu.seaclouds.platform.planner.service.DamGenResource.damGenPost(DamGenResource.java:100) ~[planner-service.jar:na]
! at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_95]
! at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_95]
! at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_95]
! at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_95]
! at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81) ~[planner-service.jar:na]
! at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144) ~[planner-service.jar:na]
! at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161) ~[planner-service.jar:na]
! at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:205) ~[planner-service.jar:na]
! at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99) ~[planner-service.jar:na]
! at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389) ~[planner-service.jar:na]
! at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347) ~[planner-service.jar:na]
! at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102) ~[planner-service.jar:na]
! at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:309) ~[planner-service.jar:na]
! at org.glassfish.jersey.internal.Errors$1.call(Errors.jav

Román SG

@rosogon

@andreaturli :

https://github.com/SeaCloudsEU/SeaCloudsPlatform/blob/master/monitor/monitoring-dam-generator-core/src/main/java/eu/seaclouds/monitor/monitoringdamgenerator/MonitoringDamGenerator.java#L91 throws a NPE because MonitorManagerUrl is not set.

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 :)

Where communities thrive

People

Repo info

Activity