Return-Path: X-Original-To: apmail-whirr-dev-archive@www.apache.org Delivered-To: apmail-whirr-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DDED4EAAE for ; Fri, 1 Mar 2013 06:22:09 +0000 (UTC) Received: (qmail 73791 invoked by uid 500); 1 Mar 2013 06:22:09 -0000 Delivered-To: apmail-whirr-dev-archive@whirr.apache.org Received: (qmail 73610 invoked by uid 500); 1 Mar 2013 06:22:05 -0000 Mailing-List: contact dev-help@whirr.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@whirr.apache.org Delivered-To: mailing list dev@whirr.apache.org Received: (qmail 73571 invoked by uid 99); 1 Mar 2013 06:22:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Mar 2013 06:22:03 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of savu.andrei@gmail.com designates 209.85.212.170 as permitted sender) Received: from [209.85.212.170] (HELO mail-wi0-f170.google.com) (209.85.212.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Mar 2013 06:21:58 +0000 Received: by mail-wi0-f170.google.com with SMTP id hm11so9998920wib.1 for ; Thu, 28 Feb 2013 22:21:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=19KVd68H5DVaEZw/ZeYdcSv8OCSr1bGZqD4k0ccdB/g=; b=XH4FAEuOpEHAnef3gxBnLqyvgAoGgXluVtWVQ01xHvd8/fN0UgRusJt1fCCRz5iQOC 3CMfz9/NlVNNEdGbAshN30Q0QrlNIAuPbepsWyO67ZWwZD01bYYb3PEjIhyf98vhdq3Z eMFD5tfU+JjV3yz3vzfib7/Jw/wIDjUxyJPGLgM8EcrIaas2cTBkc9n4yrTd9MwyJk3u BogA0cCaUUHiet0CxWQRVe0hlO9M+jjAZrbeHSSq1I1ve2pxLVM3HNPCgAdzKpCpSZvs or/S+YPf3V4h66+nDAHbQE3zalka0l2l28KmZXJpImpPIYAAbYeVBCng6TbX09YYBPb7 4F8w== X-Received: by 10.194.103.72 with SMTP id fu8mr15305177wjb.42.1362118897709; Thu, 28 Feb 2013 22:21:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.239.13 with HTTP; Thu, 28 Feb 2013 22:21:16 -0800 (PST) In-Reply-To: References: <5115B81E.802@gmail.com> <51295DC3.5020801@gmail.com> From: Andrei Savu Date: Thu, 28 Feb 2013 22:21:16 -0800 Message-ID: Subject: Re: Provisioning as a Dedicated Service To: "dev@whirr.apache.org" Content-Type: multipart/alternative; boundary=089e010d86100a39f304d6d70551 X-Virus-Checked: Checked by ClamAV on apache.org --089e010d86100a39f304d6d70551 Content-Type: text/plain; charset=ISO-8859-1 Thanks Ashish! How would you use or extend Provisionr? -- Andrei Savu On Thu, Feb 28, 2013 at 5:14 PM, Ashish wrote: > Andrei, > > Can you add me as contributor, if it works for you :) > > > On Fri, Mar 1, 2013 at 12:32 AM, Andrei Savu > wrote: > > > Hi guys - > > > > I have submitted a proposal to bring Axemblr Provisionr to the Apache > > Incubator (see general@incubator.apache.org): > > > > http://wiki.apache.org/incubator/ProvisionrProposal > > > > And this is a slide deck that explains medium term plans & challenges: > > > > > > > http://www.slideshare.net/savu.andrei/creating-pools-of-virtual-machines-apachecon-na-2013 > > > > If you want to join as a mentor / initial contributor you are welcome! > > > > Thanks, > > > > -- Andrei Savu > > > > On Sat, Feb 23, 2013 at 4:24 PM, Paul Baclace > >wrote: > > > > > On 20130209 4:37 , Andrei Savu wrote: > > > > > >> On Sat, Feb 9, 2013 at 4:44 AM, Paul Baclace > > >> wrote: > > >> > > >> Do you have any rough idea of state transition latency and throughput > > you > > >>> get when using Activiti and how this compares to using Whirr/jclouds > > in a > > >>> single process? > > >>> > > >>> Is this important? During pool creation most of the time is spent in > > >> loops > > >> waiting for external services. We try to keep each activity as short > as > > >> possible to avoid long running transactions. > > >> > > >> The reason I ask is that although Activiti has good support for > > designing > > >>> processes and programmatic control of the engine, it is necessarily > DB > > >>> transaction limited. An obvious alternative design is to use > something > > >>> that > > >>> is actor based which can run entirely in RAM. I admit that an actor > > >>> control > > >>> system would make it harder to trace what happened, compared to > > business > > >>> process control which is very much oriented toward human-in-the-loop. > > >>> > > >>> I think it's going to take while for us to hit that limitation. I > see > > >> good > > >> performance even if we are using an embedded H2 database - it should > > work > > >> a > > >> lot better with a PostgresSQL server. It's true that Activiti is > > oriented > > >> towards human-in-the-loop processes but it works well also for > > >> unsupervised > > >> ones. > > >> > > >> > > >> As long as the orchestration is at the appropriate granularity (not > > > micro-managing), then using Activiti should be fine. Another thing it > can > > > do that is more challenging for a single machine actor system is > preserve > > > state across controller restarts. > > > > > > Paul > > > > > > > > > > > > -- > thanks > ashish > > Blog: http://www.ashishpaliwal.com/blog > My Photo Galleries: http://www.pbase.com/ashishpaliwal > --089e010d86100a39f304d6d70551--