Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jul 14 2016 13:06
    andreaturli unlabeled #311
  • Jul 14 2016 13:06

    rosogon on master

    Updating deployer and brooklyn-… Merge pull request #311 from ki… (compare)

  • Jul 14 2016 13:06
    rosogon closed #311
  • Jul 14 2016 13:06
    rosogon commented #311
  • Jul 14 2016 10:15
    kiuby88 commented #311
  • Jul 14 2016 08:50
    codecov-io commented #311
  • Jul 14 2016 08:42
    codecov-io commented #311
  • Jul 14 2016 08:42
    kiuby88 synchronize #311
  • Jul 13 2016 16:22

    rosogon on 1.1.0-beta

    (compare)

  • Jul 13 2016 11:24
    rosogon commented #311
  • Jul 13 2016 11:19
    kiuby88 synchronize #311
  • Jul 13 2016 10:15
    codecov-io commented #311
  • Jul 13 2016 10:08
    kiuby88 commented #311
  • Jul 13 2016 10:08
    andreaturli labeled #311
  • Jul 13 2016 10:08
    kiuby88 opened #311
  • Jul 11 2016 16:41
    IvanFebles commented #310
  • Jul 10 2016 18:09
    fradandria labeled #310
  • Jul 10 2016 18:09
    fradandria assigned #310
  • Jul 10 2016 18:09
    fradandria opened #310
  • Jun 29 2016 15:22
    andreaturli unlabeled #309
Andrea Turli
@andreaturli
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
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
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.
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
sorry, I wanted to say the urls
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/“"