multi-appliance name issues with banners
Reported by Deleted User | January 15th, 2009 @ 11:22 PM | in 1.0.0.Beta3
If we log in to a node via ssh we can't recognize in a simple way which node it is. Maybe put something more in /etc/motd?
Comments and changes to this ticket
-
Deleted User February 3rd, 2009 @ 02:54 AM
- Assigned user set to “Deleted User”
- Milestone set to “1.0.0.Beta2”
-
bob (at oddthesis) February 3rd, 2009 @ 07:16 AM
- Tag changed from “feature request, appliance” to “feature request, appliance, puppet”
ACE should be injecting into /etc/motd and /etc/issue.net if the puppet rules run to completion.
-
Deleted User February 3rd, 2009 @ 10:43 PM
Agreed. What should we inject there:
- IP address.
Something more?
We should add also a static info with appliance name there.
-
bob (at oddthesis) February 4th, 2009 @ 05:46 AM
Ah, it already should do that, if the boot sequence is successful.
It includes the IP address and the appliance name. But when doing a multi-appliance, only the last appliance-name wins. We need a better strategy for multi-appliance appliances.
In the appliance puppet recipes is an ACE banners module, which handles the motd/issue(.net) files.
-
Deleted User February 14th, 2009 @ 05:31 AM
- Milestone changed from “1.0.0.Beta2” to “1.0.0.Beta3”
- Title changed from “Provide a simple way to recognize current node” to “multi-appliance name issues with banners”
Yes, it works, I don't know, maybe I was looking at a appliance in which ACE wasn't started without glitches, dunno.
Changing title and moving to Beta3.
Haven't tested multi-appliance so far.
-
Deleted User February 20th, 2009 @ 02:27 AM
- State changed from “new” to “resolved”
Fixed appliance name pb.
-
Deleted User February 20th, 2009 @ 06:23 AM
- Tag changed from “feature request, appliance, puppet” to “appliance, bug, puppet”
- State changed from “resolved” to “open”
Reopening, not really fixed :)
-
Deleted User February 26th, 2009 @ 07:51 AM
- State changed from “open” 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 »
**We moved**
Read more here: http://community.jboss.org/docs/DOC-14372
People watching this ticket
- Nobody is watching this ticket.