From commits-return-92056-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org  Wed Jul 24 12:18:10 2019
Return-Path: <commits-return-92056-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org>
X-Original-To: archive-asf-public@cust-asf.ponee.io
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [207.244.88.153])
	by mx-eu-01.ponee.io (Postfix) with SMTP id D536518025F
	for <archive-asf-public@cust-asf.ponee.io>; Wed, 24 Jul 2019 14:18:09 +0200 (CEST)
Received: (qmail 13504 invoked by uid 500); 24 Jul 2019 12:18:09 -0000
Mailing-List: contact commits-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@cloudstack.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@cloudstack.apache.org>
List-Post: <mailto:commits@cloudstack.apache.org>
List-Id: <commits.cloudstack.apache.org>
Reply-To: dev@cloudstack.apache.org
Delivered-To: mailing list commits@cloudstack.apache.org
Received: (qmail 13495 invoked by uid 99); 24 Jul 2019 12:18:09 -0000
Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jul 2019 12:18:09 +0000
From: GitBox <git@apache.org>
To: commits@cloudstack.apache.org
Subject: [GitHub] [cloudstack] wido opened a new pull request #3519:
 kvm/cloudstack-guest-info: Tool to query Qemu Guest Agent
Message-ID: <156397068919.9109.1650033820875911558.gitbox@gitbox.apache.org>
Date: Wed, 24 Jul 2019 12:18:09 -0000
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

wido opened a new pull request #3519: kvm/cloudstack-guest-info: Tool to query Qemu Guest Agent
URL: https://github.com/apache/cloudstack/pull/3519
 
 
   Using this tool on a hypervisor admins can query KVM Instances running
   on that hypervisor if they have the Qemu Guest Agent installed.
   
   All System VMs have this and they can be queried.
   
   For example:
   
   $ cloudstack-guest-tool i-2-25-VM
   
   This will print some information about network and filesystem status.
   
   root@hv-138-a05-23:~# ./cloudstack-guest-tool s-11-VM --command info|jq
   {
     "network": [
       {
         "ip-addresses": [
           {
             "prefix": 8,
             "ip-address": "127.0.0.1",
             "ip-address-type": "ipv4"
           }
         ],
         "name": "lo",
         "hardware-address": "00:00:00:00:00:00"
       },
       {
         "ip-addresses": [
           {
             "prefix": 16,
             "ip-address": "169.254.242.169",
             "ip-address-type": "ipv4"
           }
         ],
         "name": "eth0",
         "hardware-address": "0e:00:a9:fe:f2:a9"
       },
    ...
    ...
     "filesystem": [
       {
         "mountpoint": "/var",
         "disk": [
           {
             "bus": 0,
             "bus-type": "virtio",
             "target": 0,
             "unit": 0,
             "pci-controller": {
               "slot": 7,
               "bus": 0,
               "domain": 0,
               "function": 0
             }
           }
         ],
         "type": "ext4",
         "name": "vda6"
       },
   
   Signed-off-by: Wido den Hollander <wido@widodh.nl>
   
   ## Description
   <!--- Describe your changes in detail -->
   
   <!-- For new features, provide link to FS, dev ML discussion etc. -->
   <!-- In case of bug fix, the expected and actual behaviours, steps to reproduce. -->
   
   <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be closed when this PR gets merged -->
   <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
   <!-- Fixes: # -->
   
   ## Types of changes
   <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
   - [ ] Breaking change (fix or feature that would cause existing functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   
   ## Screenshots (if appropriate):
   
   ## How Has This Been Tested?
   <!-- Please describe in detail how you tested your changes. -->
   <!-- Include details of your testing environment, and the tests you ran to -->
   <!-- see how your change affects other areas of the code, etc. -->
   
   
   <!-- Please read the [CONTRIBUTING](https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md) document -->
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services