need support for configuring syslog
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Unassigned | ||
| cloud-init |
Fix Released
|
Medium
|
Scott Moser | ||
Bug Description
in order to instruct a host to easily log syslog information to another system, we need to add a cloud-config format for this.
The format to use looks like this:
## syslog module allows you to configure the systems syslog.
## configuration of syslog is under the top level cloud-config
## entry 'syslog'.
##
## "remotes"
## remotes is a dictionary. items are of 'name: remote_info'
## name is simply a name (example 'maas'). It has no importance other than
## for cloud-init merging configs
##
## remote_info is of the format
## * optional filter for log messages
## default if not present: *.*
## * optional leading '@' or '@@' (indicates udp or tcp).
## default if not present (udp): @
## This is rsyslog format for that. if not present, is '@' which is udp
## * ipv4 or ipv6 or hostname
## ipv6 addresses must be encoded in [::1] format. example: @[fd00::1]:514
## * optional port
## port defaults to 514
##
## Example:
#cloud-config
rsyslog:
remotes:
# udp to host 'maas.mydomain' port 514
maashost: maas.mydomain
# udp to ipv4 host on port 514
maas: "@[10.5.1.56]:514"
# tcp to host ipv6 host on port 555
maasipv6: "*.* @@[FE80:
Related branches
- Andres Rodriguez (community): Approve
- Mike Pontillo (community): Approve
-
Diff: 102 lines (+26/-1)5 files modifiedcontrib/preseeds_v2/enlist_userdata (+4/-0)
src/maasserver/compose_preseed.py (+16/-0)
src/maasserver/preseed.py (+2/-0)
src/maasserver/tests/test_compose_preseed.py (+3/-0)
src/maasserver/tests/test_preseed.py (+1/-1)
| description: | updated |
| Changed in maas: | |
| milestone: | none → 1.9.0 |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
| no longer affects: | maas |
| Scott Moser (smoser) wrote | #1 |
| Scott Moser (smoser) wrote | #2 |
| Changed in cloud-init: | |
| assignee: | nobody → Scott Moser (smoser) |
| status: | New → Fix Committed |
| importance: | Undecided → Medium |
| Changed in maas: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in maas: | |
| milestone: | none → 1.9.0 |
| Changed in maas: | |
| status: | Confirmed → Triaged |
| Changed in maas: | |
| milestone: | 1.9.0 → 2.0.0 |
| importance: | Medium → High |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Scott Moser (smoser) wrote | #4 |
| Changed in cloud-init: | |
| status: | Fix Committed → Fix Released |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
| James Falcon (falcojr) wrote | #5 |
added a branch at lp:~smoser/cloud-init/syslog-rework
that implements much of the above.
then realized cc_rsyslog.conf is present in cloud-init since before 2012.
its config looks like:
#cloud-config
rsyslog:
- "*.* @@192.158.1.1"
- content: "*.* @@192.0.2.1:10514"
- filename: 01-examplecom.conf
content: |
*.* @@syslogd.
I'll spend some time monday getting the improved test and systemd restart that i have in my new branch into the older one. Also will support calling the dictionary as 'syslog' rather than rsyslog to be more generic.