Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 20453200C15 for ; Wed, 8 Feb 2017 10:25:01 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1ECEB160B5A; Wed, 8 Feb 2017 09:25:01 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6758B160B4E for ; Wed, 8 Feb 2017 10:25:00 +0100 (CET) Received: (qmail 77689 invoked by uid 500); 8 Feb 2017 09:24:09 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 77622 invoked by uid 500); 8 Feb 2017 09:24:09 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 77613 invoked by uid 99); 8 Feb 2017 09:24:09 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Feb 2017 09:24:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id F405DC76FD for ; Wed, 8 Feb 2017 09:24:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Q1-debrLn-qQ for ; Wed, 8 Feb 2017 09:24:08 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id DF0B65F613 for ; Wed, 8 Feb 2017 09:24:07 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B80DCE0BDF for ; Wed, 8 Feb 2017 09:24:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 462BB25286 for ; Wed, 8 Feb 2017 09:23:59 +0000 (UTC) Date: Wed, 8 Feb 2017 09:23:59 +0000 (UTC) From: "Daan Hoogland (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (CLOUDSTACK-4320) [UI] Provide a search filter to list routers from specific zone/Network Name/ID/Account name MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 08 Feb 2017 09:25:01 -0000 [ https://issues.apache.org/jira/browse/CLOUDSTACK-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland closed CLOUDSTACK-4320. ------------------------------------- Resolution: Won't Fix > [UI] Provide a search filter to list routers from specific zone/Network Name/ID/Account name > -------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-4320 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4320 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the default.) > Components: UI > Affects Versions: 4.2.0 > Reporter: Sailaja Mada > Attachments: listroters.png > > > Observation: > Currently we create router for every guest network. In a cloud era, it is expected to have multiple accounts and guest networks for each account. There could be multiple zones as well. > So for the cloud admin , there is no search filter option in the UI to list out the specific routers if admin happens to perform some operations. > It is so painful to get the exact Router among many listed routers. > This is the request to enhance the search filter to list routers from specific zone/Network Name/ID -- This message was sent by Atlassian JIRA (v6.3.15#6346)