[JIRA] (JENKINS-36406) Ability to utilize HEAT orchestration templates

[ogon...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I presume this is a use-case already implemented by https://wiki.jenkins-ci.org/display/JENKINS/Openstack+Heat+Plugin  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36406  
 
 
  Ability to utilize HEAT orchestration templates   
 

  
 
 
 
 

 
Change By: 
 Oliver Gondža  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] (JENKINS-36406) Ability to utilize HEAT orchestration templates

[grimb...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Grimberg created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36406  
 
 
  Ability to utilize HEAT orchestration templates   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Oliver Gondža  
 
 
Components: 
 openstack-cloud-plugin  
 
 
Created: 
 2016/Jul/04 2:52 AM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Andrew Grimberg  
 

  
 
 
 
 

 
 Our environment makes extensive use of additional instance creation in jobs (aka multi-node labs). However, we have to share the resources between our build instances and these multi-node labs. Given that we can easily starve one or the other for resources if we don't balance things carefully, we can regularly have a job start on a lead multi-node instance and then fail because it can't allocate the needed additional instances. It would be really handy if we could instead of encoding all the instance setup logic in our jobs, instead utilize HEAT orchestration templates that have a lead node identified with a label attached to it. These could then be spun up and wait for Jenkins to attach to the lead node until the entire HEAT stack is online. I've added the HEAT orchestration developer docs link  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment