cloudify

生命周期事件——Lifecycle Events

由 非 Y 不嫁゛ 提交于 2021-02-20 08:03:37
Lifecycle Events Overview Cloudify支持以下类型的生命周期事件: Application events — 内置events，在Cloudify shell提示符输入命令来调用。 Service events —在service recipe中定义的事件，由ESM调用。 Service instance events — 在service recipe中定义的最后要的生命周期事件，由ESM调用。 当一个生命周期事件被触发，事件需要的动作发生对应的事件处理脚本会运行。例如一个安装事件被ESM调用，对应的安装事件处理（定义在服务描述文件中）会执行。 已知的限制： 当 start 事件反回,Cloudify将认为service 实例已经停止并且会试图重试。为了避免该行为，确保start脚本永久睡眠。 Application Events Application events 是Cloudify内置的，当前不能在应用recipe中自定义。它们是由Cloudify shell提示符输入命令来调用的。通常用于执行各各任务，如，将recipes拷贝到管理machines中，然后触发相应的内置应用事件。 存在两种application events: Application install –用于安装应用，在 Cloudify shell prompt中输入:

How to get ip public AWS in Cloudify

由 我的未来我决定 提交于 2019-12-13 07:11:34
问题 Using in my script file .sh: ctx logger info $(ctx instance host_ip) I get the private IP of my instance on AWS. How do I get the public IP? 回答1: Short answer is that as of right now you cannot, but the feature is planned. More complete answer - ctx.instance.host_ip maps to a compute node instance's runtime property ctx.instance.runtime_properties[ip]. By convention this is a private ip address. This property is set if the current node is of, or is derived from, the type cloudify.nodes

Deploying nodecellar in Cloudify,nodecellar can't start

由 一个人想着一个人 提交于 2019-12-13 04:12:48
问题 2015-07-14T02:33:19 LOG <nodecellar> [nodecellar_e32b8.start] INFO: [GET] http://localhost:8080 404 2015-07-14T02:33:20 LOG [nodecellar_e32b8.start] INFO: Nodecellar has not started. waiting... 2015-07-14T02:33:21 LOG [nodecellar_e32b8.start] INFO: [GET] http://localhost:8080 404 2015-07-14T02:33:21 LOG [nodecellar_e32b8.start] INFO: Nodecellar has not started. waiting... 2015-07-14T02:33:22 LOG [nodecellar_e32b8.start] INFO: [GET] http://localhost:8080 404 2015-07-14T02:33:22 LOG [nodecellar

cloudify service dependsOn other service

由 痴心易碎 提交于 2019-12-12 02:15:51
问题 When I use cloudify(2.7) to deploy an application,it includs two services(e.g. service A dependsOn service B),here is the app-application.groovy application { name "app" service { name = "B" } service { name = "A" dependsOn = [ "B" ] } } when the service B has 2 instances,one of the instances of service B is available,the service A begin to invoke the start event,but the service A dependsOn all instance of service B, Does it have some configuration to solve it ? 回答1: Copying my answer from

byon with phycal machine, SLA is global, how to ensure that the applications are not be installed on the same machine

由 ≡放荡痞女 提交于 2019-12-12 02:05:39
问题 I hava scenario like this: I have applications A,B,C,D..., and I hava physical machines M,N,O,P,Q... I use byon to manage physical machine, because the physial machine is "strong", so I want to deploy several application on it, so I set the SLA is global, at this time I have a question: when application A is deployed on machine M, I deploy other application B,C,D...,whether application A,B,C,D...will install on M machine only, rather than install on machine N,O,P,Q...(in this case, the host A

Retrieve IP of the Cloudify Manager from inside Cloudify Application VM

由 前提是你 提交于 2019-12-12 01:28:56
问题 I am using Cloudify 2.7 with OpenStack Iceouse. How could I do to retrieve IP of the Cloudify Manager from inside Cloudify Application VM? 回答1: Good question. Unfortunately, there is no simple API to get this. As Cloudify 2 has reached End-of-Life, there are no plans for adding such an API. Having said that, there is an environment variable that contains this information. The environment variable name is: LOOKUPLOCATORS The value of this variable is of the format: <HOST1>:<PORT1>;<HOST2>:

cloudify 2.7 locator NO_PROCESS_LOCATORS

由 ⅰ亾dé卋堺 提交于 2019-12-02 20:15:50
问题 I am using the cloudify(version 2.7),when I try to develop a recipe,just a simple command( java -jar some.jar ),the events grid display "Service Instance non-responsive",and the lifcycle restart again and again,but when I add the lifecycle locator locator { NO_PROCESS_LOCATORS } it is ok! I want to know how it works, I read the example recipe on the github, and they don't have the locator lifecycle ,what are they speciled? 回答1: By default, Cloudify assumes that a recipe will launch a process

cloudify 2.7 locator NO_PROCESS_LOCATORS

由 蓝咒 提交于 2019-12-02 07:34:09
I am using the cloudify(version 2.7),when I try to develop a recipe,just a simple command( java -jar some.jar ),the events grid display "Service Instance non-responsive",and the lifcycle restart again and again,but when I add the lifecycle locator locator { NO_PROCESS_LOCATORS } it is ok! I want to know how it works, I read the example recipe on the github, and they don't have the locator lifecycle ,what are they speciled? By default, Cloudify assumes that a recipe will launch a process and that process should stay alive. If the process shuts down, this is assumed to be a crash and the process
订阅 cloudify