在我的cloudformation堆栈中,我有一个启动配置,它在用户数据中运行ansible脚本。这里的问题是,即使ansible脚本没有完成exacution,我的堆栈状态也会显示CREATE_COMPLETE
。在我进入ec2实例后,我看到日志显示正在进行的ansible执行。我的示例cloudformation堆栈json是这样的:
"OpenShiftMasterASLaunchConfig": {
"Type": "AWS::AutoScaling::LaunchConfiguration",
"Metadata": {
"AWS::CloudFormation::Init": {
"configSets": {
"quickstart": ["GetPublicKey", "AddPublicKey", "rpms", "ConfigSSHD", "DockerGroup", "DockerSecurity", "InstallAWSCLI", "SetPrivateKey", "StartServices"]
},
"rpms": {
"packages": {
"yum": {
"epel-release": [],
"NetworkManager": [],
"ansible": [],
"docker": [],
"git": [],
"python-boto": [],
"python-cryptography": [],
"python-lxml": [],
"python-pip": [],
"origin-docker-excluder": [],
"centos-release-openshift-origin": [],
"atomic-openshift-utils": [],
"origin-clients": [],
"awslogs" : []
}
}
},
"Properties": {
"AssociatePublicIpAddress" : "true",
"KeyName": {
"Ref": "KeyPairName"
},
"ImageId": {
"Fn::FindInMap": [
"AWSAMIRegionMap",
{
"Ref": "AWS::Region"
},
"CENTOS7HVM"
]
},
"BlockDeviceMappings": [{
"DeviceName": "/dev/sda1",
"Ebs": {
"VolumeSize": "100"
}
}],
"InstanceMonitoring": "true",
"IamInstanceProfile": {
"Ref": "SetupRoleProfile"
},
"InstanceType": {
"Ref": "MasterInstanceType"
},
"SecurityGroups": [{
"Ref": "OpenShiftSecurityGroup"
}],
"UserData": {
"Fn::Base64": {
"Fn::Join": [
"", [
"bash /local/scripts/openshift-origin-bootstrap-master.sh\n",
"ansible-playbook -i /local/ansible/inventory/hosts.cluster /local/openshift-ansible/playbooks/prerequisites.yml >> /local/prereq.log\n",
"ansible-playbook -i /local/ansible/inventory/hosts.cluster /local/openshift-ansible/playbooks/deploy_cluster.yml -vvv > /local/cluster.log\n",
"bash /local/scripts/configure_openebs.sh\n"
]
]
}
}
}
这只是一个示例。此处的ansible-playbook
命令在堆栈显示为已完成时仍在执行中。有没有办法延迟堆栈上的创建条件,以确保首先执行所有用户数据。我尝试使用wait condition
,但它没有给出所需的结果。
答案 0 :(得分:1)
将CreationPolicy与您的资源相关联,以防止其状态达到“创建完成”,直到您的userdata脚本发出CloudFormation信号(在userdata末尾)。这是一个example。