Skip to content
This repository was archived by the owner on May 6, 2020. It is now read-only.

Conversation

@jodh-intel
Copy link

No description provided.

@jodh-intel
Copy link
Author

Note that, strictly, this is blocked by clearcontainers/proxy#181.

@jodh-intel
Copy link
Author

Hi @grahamwhaley, @iphutch - please could you review?

@clearcontainersbot
Copy link

kubernetes qa-passed 👍

Copy link
Contributor

@grahamwhaley grahamwhaley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some nitpicks, but nothing that really needs to block this, so I'll also give my
lgtm

latter is useful as it is independent of the lifecycle of each container.

To view runtime log output,
To view runtime log output:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

silly nit - technically I think that is a colon :, not a semi-colon ; :-)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow, that's embarrassing! Fixing... ;)

README.md Outdated

The runtime, the shim (`cc-shim`), and the hypervisor all have separate debug
options in the [configuration file](#Configuration).
The runtime, the shim (`cc-shim`), the hypervisor and the proxy all have separate `enable_debug=` debug
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we are going to call out cc-shim, do we want to call out cc-proxy as well?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I'll re-order the elements and mention the proxy binary name...

README.md Outdated
$ sudo journalctl -t cc-runtime
```

### Enabling debug for various components
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think to changing this title to:
Enabling and viewing debug for other components
to cover the fact we now show enabling and viewing, and we cover the runtime separately in the above section ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I take your point but this section also enables debug for the runtime. I'll rework both sections to make this clearer...

@jodh-intel jodh-intel force-pushed the improve-doc-for-debug branch 2 times, most recently from a761e8c to 4a55e72 Compare December 6, 2017 10:55
@jodh-intel
Copy link
Author

Hi @grahamwhaley - branch updated.

@clearcontainersbot
Copy link

kubernetes qa-passed 👍

Copy link
Contributor

@grahamwhaley grahamwhaley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One suggestion - not a blocker.
lgtm


```bash
$ sudo sed -i -e 's/^#\(enable_debug\).*=.*$/\1 = true/g' /usr/share/defaults/clear-containers/configuration.toml
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking much better, thanks @jodh-intel
Sorry to be a mild pain, but one more suggestion - do you think we should also link from here to the more detailed/specific debug docs we now have as well?
https://github.com/clearcontainers/runtime/blob/master/docs/debug-agent.md
https://github.com/clearcontainers/runtime/blob/master/docs/debug-kernel.md

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. Note that those 2 docs had rotted a bit so I've had to update them. In fact, I'm wondering if we want to merge them (maybe into the README itself) since as you can see, they are now very similar.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @jodh-intel
lgtm

@clearcontainersbot
Copy link

kubernetes qa-passed 👍

@jodh-intel jodh-intel force-pushed the improve-doc-for-debug branch 3 times, most recently from d51328e to 001ed84 Compare December 6, 2017 12:11
@clearcontainersbot
Copy link

kubernetes qa-passed 👍

1 similar comment
@clearcontainersbot
Copy link

kubernetes qa-passed 👍

@jodh-intel
Copy link
Author

Hi @klynnrif, @rcaballeromx - please could you review?

@jodh-intel
Copy link
Author

Hi @klynnrif, @rcaballeromx - could you squeeze in a review for this one today possibly?

@klynnrif
Copy link

klynnrif commented Dec 8, 2017

@jodh-intel @rcaballeromx I should have time to take a look today.

Copy link

@klynnrif klynnrif left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Completed a scrub for grammar and style guide consistency. Thanks!

README.md Outdated
## Debugging
## Logging

The runtime provides `--log=` and `--log-format=` options. However, it can
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested rewrite to stay active: However, you can also configure it to log...

README.md Outdated

The runtime, the shim (`cc-shim`), and the hypervisor all have separate debug
options in the [configuration file](#Configuration).
Note that the proxy log entries also include output from the agent (`cc-agent`) and the
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am unsure how notes are dealt with here, but I would typically format any sentence(s) as a note if it begins with "Note that..." For example,

..note::
The proxy log entries also include output from the agent (cc-agent) and the hypervisor, which includes the guest kernel boot-time messages.

README.md Outdated

## Debugging

The runtime, the shim (`cc-shim`), the proxy (`cc-proxy`) and the hypervisor all have separate `enable_debug=` debug
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Including the final comma (based on the style guide): The runtime, the shim (cc-shim), the proxy (cc-proxy), and the hypervisor all have searate enable_debug= debug...

README.md Outdated

The runtime, the shim (`cc-shim`), the proxy (`cc-proxy`) and the hypervisor all have separate `enable_debug=` debug
options in the [configuration file](#Configuration). By default, all these
debug options are disabled. Look at the comments in the installed
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the comments in the...

README.md Outdated
debug options are disabled. Look at the comments in the installed
configuration file for further details.

If you wish to enable debug for all components, assuming a standard configuration file path, run:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you want to enable debug...

(standard program when running containers on bare metal).
The Clear Containers agent relies heavily on [`libcontainer`](https://github.com/opencontainers/runc/tree/master/libcontainer) used by [`runc`](https://github.com/opencontainers/runc/) (standard program when running containers on bare metal).

To provide a debug log of any agent activity on a guest, the Clear Containers
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lines 12-14 suggested rewrite (possible this changes the meaning): To provide a debug log of any agent activity on a guest, the Clear Containers agent sends a log through a QEMU serial console, which is collected by cc-proxy] (https://github.com/clearcontainers/proxy) and shown in the proxy's logs.

1. Filter the agent debug logs from the `cc-proxy` logs

The `cc-proxy` logs show the sources of its collated information. To only see
the agent debug logs, filter `cc-proxy` logs by the QEMU serial console (the
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... the agent debug logs, filter cc-proxy logs by the QEMU serial console that sent the agent logs.

1. Enable debug in `configuration.toml`
1. Enable kernel boot messages

Set the `enable_debug=` option in the `[proxy.cc]` section to `true` (assumes a standard configuration file path):
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Set the enable_debut= option in the [proxy.cc] section to true, which assumes a standard configuration file path:


1. Enable proxy debug

Set the `enable_debug=` option in the `[proxy.cc]` section to `true` (assumes a standard configuration file path):
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Set the enable_debug= option in the [proxy.cc] section to true, which assumes a standard configuration file path:


The Clear Containers Agent relies heavily on libcontainer used by runc
(standard program when running containers on bare metal).
The Clear Containers agent relies heavily on [`libcontainer`](https://github.com/opencontainers/runc/tree/master/libcontainer) used by [`runc`](https://github.com/opencontainers/runc/) (standard program when running containers on bare metal).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... used by [runc] (https://github.com/opencontainers/runc/), which is the standard program when running containers on bare metal.

@jodh-intel
Copy link
Author

Hi @klynnrif - thanks for reviewing. Branch updated.

(Note that as some of your suggested changes weren't strictly part of the changes I'd made on this PR, I've created a new commit specifically to address all the review changes).

@jodh-intel
Copy link
Author

Hi @klynnrif, @rcaballeromx - could one of you take a look at this please? I'd really like to get this landed this week if possible.

@klynnrif
Copy link

@jodh-intel @rcaballeromx I can take a look at this today. Thanks!

Copy link

@klynnrif klynnrif left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple minor changes suggested. Thanks!

README.md Outdated
Note:

The proxy log entries also include output from the agent (`cc-agent`) and the
hypervisor (which includes the guest kernel boot-time messages).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... hypervisor, which includes the guest kernel boot-time messages.

README.md Outdated

The runtime, the shim (`cc-shim`), the proxy (`cc-proxy`),
and the hypervisor all have separate `enable_debug=` debug
options in the [configuration file](#Configuration). By default, all these

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lines 116-117 suggested rewrite: All of these debug options are disables by default.

@clearcontainersbot
Copy link

kubernetes qa-passed 👍

James O. D. Hunt added 4 commits December 14, 2017 13:04
All commands should be introduced with a sentence that ends
with a colon.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Renamed "Debugging" section to "Logging" and explained how to view
log output for all system components.

Also created a top-level "Debugging" section which explains how to
enable full debug.

Fixes clearcontainers#845.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
The agent and kernel debug documents had deviated from reality.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Apply further changes to the debug and logging documents based on
review feedback.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
@jodh-intel jodh-intel force-pushed the improve-doc-for-debug branch from bdcb1fe to 56aa874 Compare December 14, 2017 13:05
@jodh-intel
Copy link
Author

Hi @klynnrif - thanks for re-reviewing. Branch updated.

@clearcontainersbot
Copy link

kubernetes qa-passed 👍

@jodh-intel
Copy link
Author

Hi @klynnrif - could you re-review this today if possible?

@klynnrif
Copy link

@jodh-intel Yes, I can. Thanks!

Copy link

@rcaballeromx rcaballeromx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jodh-intel
Copy link
Author

Hi @klynnrif - please can you check this today?

We have sufficient approvals (thanks Rodrigo) but I want to give you one last chance to review (as we still have the red cross against your name). If I haven't heard anything by COB today, I'll assume you are happy for me to force-merge this.

@jodh-intel
Copy link
Author

We have sufficient approvals, so merging as we really need this to land...

@jodh-intel jodh-intel merged commit 346b6d9 into clearcontainers:master Dec 19, 2017
mcastelino pushed a commit to mcastelino/runtime that referenced this pull request Dec 6, 2018
…oints

network: Marshal BridgedMacvlanEndpoint and MacvtapEndpoint
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants