Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 59E9D101EE for ; Wed, 11 Mar 2015 08:53:28 +0000 (UTC) Received: (qmail 26072 invoked by uid 500); 11 Mar 2015 08:53:11 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 26023 invoked by uid 500); 11 Mar 2015 08:53:11 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 26006 invoked by uid 99); 11 Mar 2015 08:53:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Mar 2015 08:53:11 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: unknown -allinclude:_spf.google.com (nike.apache.org: encountered unrecognized mechanism during SPF processing of domain of phillip.kent@xmlsoup.com) Received: from [209.85.213.175] (HELO mail-ig0-f175.google.com) (209.85.213.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Mar 2015 08:52:46 +0000 Received: by igal13 with SMTP id l13so34961198iga.1 for ; Wed, 11 Mar 2015 01:52:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xmlsoup.com; s=google; h=mime-version:date:message-id:subject:from:to:content-type; bh=SZB7wSMFGRzsXKIaPq9Y3tkKLkn4k1ulakd3uI0nCxA=; b=QI4BdmgyJalmXNanAO9m1kZkqtSsSn8GfX+B2N3eNqTOBOWbP/YIZuKkicPGpfvOg5 G3wtokcoTg99FeQyjGXwW89U0PaZW015NRXcbDCR4IdindopTHqlx6Gd8mlhxI53zY4g epGWDoy+cdfudZFz9L0Q02LHKDj1Pz901wT3w= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=SZB7wSMFGRzsXKIaPq9Y3tkKLkn4k1ulakd3uI0nCxA=; b=AOEwqsvlbX5CcKBd/lT7hf5Eg0Ql70wNDyunOmu56zj7h5Nn5qoAySSmGvSvuoJ0Y0 dUgYaxUBv2lwfTtleUKo6p/vAZZ4U212z8UGpJq2yehTHOVjxuYOF9AINFJxm1VQlNlL JL4rdViO6ysOSCLrGOcjW09V3/ZkJ/Q1Pq3BW5Su4WwoDvYTk3/UpkZ2r7MGAQZnE3E6 aSLLyciwxa81wE5E0FIPPP0BIvI9/++/CORlLBATNZcP0AaLgO52E4ma4iQKPuaHT8Ik YEh/hsBjhdB/QLYr1ESN/fZC4+L6cGL3BeTDxKPgVs9HbOasinlFWkWcqCM/G8DwSJhl v1Hg== X-Gm-Message-State: ALoCoQk91jnNYlbEbQMeBktKsL2pQdsHuRx6RO8DuSJS1bR+951zcbey6AX9fKotmNuEgxjSG6fN MIME-Version: 1.0 X-Received: by 10.107.33.79 with SMTP id h76mr62002112ioh.36.1426063963602; Wed, 11 Mar 2015 01:52:43 -0700 (PDT) Received: by 10.107.166.148 with HTTP; Wed, 11 Mar 2015 01:52:43 -0700 (PDT) Date: Wed, 11 Mar 2015 08:52:43 +0000 Message-ID: Subject: Visualising networks using the CloudStack API From: Phillip Kent To: "" Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org Hi all, you may be interested in a simple Python tool which mashes up information from different API calls and also creates an output file that can be processed by the 'nwdiag' diagramming tool. I personally use tihs a lot to keep track of my networks and VMs. It's described in a blog post here: http://cloudstore.interoute.com/main/knowledge-centre/blog/visualising-networks-in-vdc It could be extended to cover VPCs etc, and the nwdiag program is more powerful than I have used it so far. You can keep in touch with Interoute blog posts by following https://twitter.com/Interoute or https://www.facebook.com/pages/Interoute/161759680529086 - Phillip