Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Distinguish the server node

#152

The rundeck server should have a visual distinction that sets it apart from the other nodes in the model. This can be a text affect (type face) or graphical (special icon).

The rundeck server can be determined by matching against the framework.node.name value in the configuration.

Reported by Alex-SF · December 29th, 2010 @ 10:45 AM

State: resolved
Milestone: Rundeck 1.1
Assigned to: Greg Schueler Greg Schueler

Activity

  1. Greg Schueler
    Greg Schueler
    • Assigned user set to Greg Schueler

    December 29th, 2010 @ 10:45 AM

  2. Deleted User
    Deleted User

    Matching the node in framework.properties has caused confusion when you start to create your own resource model and forget to include the node. Is there a way to make it never break on the user even if they create an incorrect resource model?

    December 29th, 2010 @ 12:34 PM

  3. Greg Schueler
    Greg Schueler

    the node name defined in framework.properties will always be included in the potential node list, as the server node definition is auto-generated if it does not exist in the resources.xml.

    December 29th, 2010 @ 12:48 PM

  4. Deleted User
    Deleted User
    • State changed from new to resolved

    (from [ecc839d6600bd0935086fc4c0a6f1fc70a02c186]) Indicate server node in node listing.

    Set islocal for local nodes in nodes action result dataset. Update css
    and nodes listing for server nodes

    [#152 state:resolved] https://github.com/dtolabs/rundeck/commit/ecc839d6600bd0935086fc4c0...

    December 29th, 2010 @ 05:00 PM

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.