Does anybody know if this blueprint is being actively work on?
https://blueprints.launchpad.net/heat/+spec/windows-instances If this is not
active, can I take ownership of this blueprint? My team wants to add support
for Windows in Heat for our internal deployment.
_
Regarding the last set of comments on the UpdatePolicy, I want to bring your
attention to a few items. I already submitted a new patch set and didn't want
to reply on the old patch set so that's why I emailed.
As you are aware, IG/ASG currently create instances by appending group name and
#.
I updated the implementation section of
https://wiki.openstack.org/wiki/Heat/Blueprints/as-update-policy on instance
naming to support UpdatePolicy where in the case of the LaunchConfiguration
change, all the instances need to be replaced and to support
MinInstancesInService, the handle_update
I updated the proposal at
https://wiki.openstack.org/wiki/Heat/Blueprints/as-update-policy. I will add
some more details to the actual rolling update mechanism when I'm coding the
handle_update method in InstanceGroup and AutoScalingGroup. Please review and
much thanks to Zane for his patienc
Zane,
I tested FnGetRefId() in LaunchConfiguration to return
unicode(self.physical_resource_name()). It doesn't work so well. When
InstanceGroup resolve runtime data and resolve resource refs, the physical
resource name (I.e.test_stack-JobServerConfig-jnzjnpomcxv5) replaced { 'Ref':
'JobServ
Proposal for the implementation is documented at
https://wiki.openstack.org/wiki/Heat/Blueprints/as-update-policy. Please
review and provide feedback.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/
Is the expectation here that the update policy for the auto-scaling group is
enforced only when either the launch configuration or subnet group membership
is changed in the auto-scaling group? The LaunchConfigurationName is not
currently listed as an update_allowed_properties in the AutoScaling
Metrics team,
Is there a best practice for counting commits made by a 3rd party
consultants/contractors (with multiple affiliations) on behalf of another
corporation? I recently had a conversation with Stefano and he suggested
adding a "Contributed for: " in the commit message. Stefano
recom
