From 05e4a733f2141995181a551854d5df929f084adf Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Wed, 9 Aug 2023 21:55:35 +0200 Subject: New upstream version 1.44.0 --- docs/api/html/nm-cloud-setup.html | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-) (limited to 'docs/api/html/nm-cloud-setup.html') diff --git a/docs/api/html/nm-cloud-setup.html b/docs/api/html/nm-cloud-setup.html index 360519fa..794c1375 100644 --- a/docs/api/html/nm-cloud-setup.html +++ b/docs/api/html/nm-cloud-setup.html @@ -137,7 +137,9 @@

  • NM_CLOUD_SETUP_LOG: control the logging verbosity. Set it to one of TRACE, DEBUG, INFO, WARN, ERR or OFF. The program - will print message on stdout and the default level is WARN.

    • + will print message on stdout and the default level is WARN. When + run as systemd service, the log will be collected by journald can can be seen with + journalctl.

  • NM_CLOUD_SETUP_AZURE: boolean, whether Microsoft Azure support is enabled. Defaults to no.

  • NM_CLOUD_SETUP_EC2: boolean, whether Amazon EC2 (AWS) support is enabled. Defaults @@ -149,6 +151,15 @@

    +

    Debugging

    +

    Enable debug logging by setting NM_CLOUD_SETUP_LOG environment variable to TRACE.

    +

    In the common case where nm-cloud-setup is running as systemd service, this can be done via systemctl edit nm-cloud-setup.service + and add Environment=NM_CLOUD_SETUP_LOG=TRACE to the [Service] section. Afterwards, the log can + be found in syslog via journalctl. You may also want to enable debug logging in NetworkManager as descibed + in the DEBUGGING section in NetworkManager(5) + manual. When sharing logs, it's best to share complete logs and not preemptively filter for NetworkManager or nm-cloud-setup logs.

    +
    +

    Example Setup for Configuring and Predeploying nm-cloud-setup

    As detailed before, nm-cloud-setup needs to be explicitly enabled. As it runs as a systemd service and timer, that basically means to enable and configure @@ -182,7 +193,7 @@ ln -s /etc/systemd/system/timers.target.wants/nm-cloud-setup.timer /usr/lib/syst

    Supported Cloud Providers

    -

    Amazon EC2 (AWS)

    +

    Amazon EC2 (AWS)

    For AWS, the tools tries to fetch configuration from http://169.254.169.254/. Currently, it only configures IPv4 and does nothing about IPv6. It will do the following.

      @@ -239,7 +250,7 @@ ln -s /etc/systemd/system/timers.target.wants/nm-cloud-setup.timer /usr/lib/syst
    -

    Google Cloud Platform (GCP)

    +

    Google Cloud Platform (GCP)

    For GCP, the meta data is fetched from URIs starting with http://metadata.google.internal/computeMetadata/v1/ with a HTTP header "Metadata-Flavor: Google". @@ -267,7 +278,7 @@ ln -s /etc/systemd/system/timers.target.wants/nm-cloud-setup.timer /usr/lib/syst

    -

    Microsoft Azure

    +

    Microsoft Azure

    For Azure, the meta data is fetched from URIs starting with http://169.254.169.254/metadata/instance with a URL parameter "?format=text&api-version=2017-04-02" and a HTTP header "Metadata:true". @@ -299,7 +310,7 @@ ln -s /etc/systemd/system/timers.target.wants/nm-cloud-setup.timer /usr/lib/syst

    -

    Alibaba Cloud (Aliyun)

    +

    Alibaba Cloud (Aliyun)

    For Aliyun, the tools tries to fetch configuration from http://100.100.100.200/. Currently, it only configures IPv4 and does nothing about IPv6. It will do the following.

      @@ -327,7 +338,7 @@ ln -s /etc/systemd/system/timers.target.wants/nm-cloud-setup.timer /usr/lib/syst
    -

    See Also

    +

    See Also

    NetworkManager(8) nmcli(1) -- cgit 1.3.0-6-gf8a5