multi-appliance name issues with banners
-
Deleted User- Assigned user set to Deleted User
- Milestone set to 1.0.0.Beta2
-
bob (at oddthesis)
- 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
Agreed. What should we inject there:
- IP address.
Something more?
We should add also a static info with appliance name there.
-
bob (at oddthesis)
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
- 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
- Tag changed from feature request, appliance, puppet to appliance, bug, puppet
- State changed from resolved to open
Reopening, not really fixed :)
-
Deleted User
- 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.