Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B82ABD14A for ; Thu, 18 Oct 2012 05:18:10 +0000 (UTC) Received: (qmail 4703 invoked by uid 500); 18 Oct 2012 05:18:10 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 4503 invoked by uid 500); 18 Oct 2012 05:18:10 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 4230 invoked by uid 99); 18 Oct 2012 05:18:09 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Oct 2012 05:18:09 +0000 Date: Thu, 18 Oct 2012 05:18:09 +0000 (UTC) From: "Prasanna Santhanam (JIRA)" To: cloudstack-dev@incubator.apache.org Message-ID: <1826099243.62315.1350537489609.JavaMail.jiratomcat@arcas> In-Reply-To: <1809172244.62267.1350537242981.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (CLOUDSTACK-372) Auto provision of hosts(hypervisors) into cloud using auto discovery mechanism from the specified IP address range MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478680#comment-13478680 ] Prasanna Santhanam commented on CLOUDSTACK-372: ----------------------------------------------- I think this isn't something that IAAS orchestration software like CloudStack should do. There are many many tools out there that handle provisioning well - cobbler, crowbar, razor (more recently), Also bare-metal provisioning is partly done by CloudStack and likely will get more improvements there. We should address any fixes that we do to this as a part of that > Auto provision of hosts(hypervisors) into cloud using auto discovery mechanism from the specified IP address range > ------------------------------------------------------------------------------------------------------------------ > > Key: CLOUDSTACK-372 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-372 > Project: CloudStack > Issue Type: Improvement > Components: Management Server > Affects Versions: 4.0.0 > Reporter: Sailaja Mada > > Enhancement Details : > 1. Currently Hosts has to be added manually into the cloud to get provisioned. > 2. This is the request to support for Auto provision of hosts(hypervisors) into cloud using auto discovery mechanism from the specified IP address range > References for this enhancement : > 1. https://supportcontent.ca.com/cadocs/0/CA%20ARCserve%20Unified%20Data%20Protection%20Enterprise%20Support%2016%200-ENU/Bookshelf_Files/HTML/hbug/index.htm?toc.htm?ua_hb_auto_disc_hosts.htm > 2. http://www.youtube.com/watch?v=IdxcHtiwZNU > 3. http://support.hyperic.com/display/hyperforge/Hyperic+Custom+Auto-Discovery+Plug-ins -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira