Add node state attribute to resource model definition
Reported by Alex-SF | October 11th, 2010 @ 02:21 PM | in Rundeck 1.3 (closed)
Define an attribute for the Node type that represents if the Node is "active" and therefore commands can be executed on it. Optionally, an attribute can be defined to represent other states a system can hold (active, parked, allocated, free, decommissioned, etc.)
Comments and changes to this ticket
-
Alex-SF November 2nd, 2010 @ 03:20 PM
- Milestone changed from “Rundeck 1.0” to “Rundeck 1.1”
- Milestone order changed from “6” to “0”
-
Alex-SF December 17th, 2010 @ 08:22 AM
- Milestone cleared.
- Milestone order changed from “1” to “0”
-
Alex-SF January 14th, 2011 @ 07:27 AM
- Milestone set to “Rundeck 1.2”
- Milestone order changed from “12” to “0”
-
Alex-SF February 1st, 2011 @ 11:46 AM
- Milestone changed from “Rundeck 1.2” to “Rundeck 1.3”
- Milestone order changed from “1” to “0”
-
Greg Schueler April 20th, 2011 @ 10:00 AM
- Milestone order changed from “5” to “0”
What name should this attribute have? "active"? or should we combine it with "state"?
The new plugin system/service architecture will make this easy to implement. The question is what should happen when...
e.g.:
if node attribute "active" has value "false" then: skip over the node completely and echo a message that the node has been skipped.
Is this the desired behavior?
-
Deleted User April 20th, 2011 @ 10:08 AM
Why not punt on having rundeck do anything with the information? Just make sure it's passed to the dispatcher plugin and let it decide.
-
Greg Schueler April 20th, 2011 @ 10:24 AM
Well, I think this would be implemented at a higher level than the Node Executor (at the Command interpreter level). This would intercept any workflow command (script, exec, etc).
It also might be inconsistent/not applied depending on the particular node executor/file copier you are using. I think if we want to add this feature it should work consistently.
Better to bake this in at the higher level so it is reliable, (at least for the active/inactive behavior.)
Either way the same question then arises for our built in SSH/SCP implementations: what should the attribute be and what should the behavior be?
-
Deleted User April 20th, 2011 @ 02:59 PM
I don't think this ticket is about acting on the data...open another ticket for that feature. Just allow the ability to put it in the resource.xml and pass it along so it can be acted upon.
-
Greg Schueler April 20th, 2011 @ 03:09 PM
in that case it's already done due to resources allowing arbitrary attributes.
vote to mark resolved?
-
-
Greg Schueler April 20th, 2011 @ 09:37 PM
- State changed from “new” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues
Alex-SF
Greg Schueler