Merge ~paul-meyer/cloud-init:lp1722959 into cloud-init:master
| Status: | Needs review | ||||
|---|---|---|---|---|---|
| Proposed branch: | ~paul-meyer/cloud-init:lp1722959 | ||||
| Merge into: | cloud-init:master | ||||
| Diff against target: |
226 lines (+192/-1) 2 files modified
cloudinit/reporting/handlers.py (+95/-1) tests/unittests/test_reporting_hyperv.py (+97/-0) |
||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Server Team CI bot | continuous-integration | Approve on 2017-12-11 | |
| Scott Moser | 2017-12-08 | Pending | |
|
Review via email:
|
|||
Commit Message
Add Hyper-V KVP reporter
Add a reporter that reports events to a Hyper-V host using Key-Value-Pair
exchange protocol and can be used to obtain high level diagnostic
information from the host.
To use this facility, the KVP user-space daemon (hv_kvp_daemon) has to be
running. It reads the kvpFile when the host requests the guest to
enumerate the KVP's.
This reporter collates all events for a module (origin|name) in a single
json string in the dictionary.
For more information, see
https:/
Description of the Change
Add a reporter that reports events to a Hyper-V host using Key-Value-Pair
exchange protocol and can be used to obtain high level diagnostic
information from the host.
To use this facility, the KVP user-space daemon (hv_kvp_daemon) has to be
running. It reads the kvpFile when the host requests the guest to
enumerate the KVP's.
This reporter collates all events for a module (origin|name) in a single
json string in the dictionary.
For more information, see
https:/
| Scott Moser (smoser) wrote : | # |
- e7cca41... by Paul Meyer on 2017-12-08
| Paul Meyer (paul-meyer) wrote : | # |
> So would i expect to find a subsequent merge proposal that would build in
> configuration of this reporter into Azure datasource?
Actually, I've been thinking that we may want to move most of that built-in config to files on disk in the images themselves, such that they can be properly overridden by custom images. Also, for this reporter it makes sense to have it on even while cloud-init searches for a data source, that way, we can detect if DSAzure is broken if the VM doesn't come online.
| Scott Moser (smoser) wrote : | # |
> > So would i expect to find a subsequent merge proposal that would build in
> > configuration of this reporter into Azure datasource?
>
> Actually, I've been thinking that we may want to move most of that built-in
> config to files on disk in the images themselves, such that they can be
> properly overridden by custom images. Also, for this reporter it makes sense
> to have it on even while cloud-init searches for a data source, that way, we
> can detect if DSAzure is broken if the VM doesn't come online.
Generally speaking we're after the goal that installing cloud-init in an image "does the right thing". That is as opposed to requiring Canonical or anyone building images to "know" that they should put some configuration files down in /etc/cloud/
I do appreciate that you'd like information to be posted when cloud-init is searching for easier debugging, but such changes wont work or cause issue on other platforms. We like to allow "one image" to work on different platforms.
| Paul Meyer (paul-meyer) wrote : | # |
> > > So would i expect to find a subsequent merge proposal that would build in
> > > configuration of this reporter into Azure datasource?
> >
> > Actually, I've been thinking that we may want to move most of that built-in
> > config to files on disk in the images themselves, such that they can be
> > properly overridden by custom images. Also, for this reporter it makes sense
> > to have it on even while cloud-init searches for a data source, that way, we
> > can detect if DSAzure is broken if the VM doesn't come online.
>
> Generally speaking we're after the goal that installing cloud-init in an image
> "does the right thing". That is as opposed to requiring Canonical or anyone
> building images to "know" that they should put some configuration files down
> in /etc/cloud/
>
> I do appreciate that you'd like information to be posted when cloud-init is
> searching for easier debugging, but such changes wont work or cause issue on
> other platforms. We like to allow "one image" to work on different platforms.
I understand the concern and I agree. We'll do both then. Add this as default configuration from the Azure DS and also make the defaults overridable from /etc/cloud for custom images (lp 1735008).
PASSED: Continuous integration, rev:e7cca41b254
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu LTS: Integration
SUCCESS: MAAS Compatability Testing
IN_PROGRESS: Declarative: Post Actions
Click here to trigger a rebuild:
https:/
Unmerged commits
- e7cca41... by Paul Meyer on 2017-12-08
- 1e4cc7d... by Paul Meyer on 2017-05-17


So would i expect to find a subsequent merge proposal that would build in configuration of this reporter into Azure datasource?