Return-Path: X-Original-To: apmail-ace-users-archive@minotaur.apache.org Delivered-To: apmail-ace-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B84CF1020A for ; Tue, 9 Apr 2013 12:24:08 +0000 (UTC) Received: (qmail 15337 invoked by uid 500); 9 Apr 2013 12:24:08 -0000 Delivered-To: apmail-ace-users-archive@ace.apache.org Received: (qmail 15227 invoked by uid 500); 9 Apr 2013 12:24:05 -0000 Mailing-List: contact users-help@ace.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@ace.apache.org Delivered-To: mailing list users@ace.apache.org Received: (qmail 15195 invoked by uid 99); 9 Apr 2013 12:24:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 12:24:04 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [194.109.24.25] (HELO smtp-vbr5.xs4all.nl) (194.109.24.25) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 12:23:57 +0000 Received: from macpro.fritz.box (planetmarrs.xs4all.nl [82.95.193.148]) (authenticated bits=0) by smtp-vbr5.xs4all.nl (8.13.8/8.13.8) with ESMTP id r39CNYJN065927 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Tue, 9 Apr 2013 14:23:35 +0200 (CEST) (envelope-from marcel.offermans@luminis.nl) From: Marcel Offermans Content-Type: multipart/alternative; boundary="Apple-Mail=_B237E14C-E097-40DD-9953-4DCCB37EA20E" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Using the management interface to deploy distros to targets Date: Tue, 9 Apr 2013 14:23:34 +0200 References: To: In-Reply-To: X-Mailer: Apple Mail (2.1503) X-Virus-Scanned: by XS4ALL Virus Scanner X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_B237E14C-E097-40DD-9953-4DCCB37EA20E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hello Dan, On Apr 9, 2013, at 13:50 , Dan Gravell = wrote: > Hi all. I just built and ran up the latest version of the server from = SVN > trunk. I've got some questions... mainly about the UI. >=20 > What do "retrieve", "store" and "revert" do? Is there some notion of = local, > uncommitted data? Yes. The idea is similar to a version control system: 1. First you retrieve the latest state from the server into your = "workspace". 2. Then you edit that data until you are happy with the changes. 3. Finally you store your changes to make them take effect (or revert if = not). > How do I uninstall a distro from an agent? "-" buttons do nothing. "x" > removes a target but then it re-appears, disassociated. Even though it > appears disassociated to the distro the bundles are still installed on = the > target. You make associations by drag and drop. Removing them is a bit less intuitive. You select one hand of the = association, then move your mouse to the other hand (which should be = highlighted at this point) and press the "-" to just remove the = association. The "x" is to remove something. For targets that still won't work 100% = because of [1] and [2]. > Similarly, I want to remove a distro and add a new distro, to simulate = a > new release of my product. I expect this is related to how to = uninstall... > but how do I do this? See above, remove one association, create a new one. > The "identification" of an agent - how is this normally populated? I = assume > people don't leave it as "target-1". Any ideas on how to make this = work for > thousands of targets? You have to somehow generate a unique ID. The management agent uses an = "Identification" service for that. The current one simply reads a system = property, but you could provide an implementation that, for example, = uses the MAC address of your network card or some other unique property. > I have a set of beta users. I want to be able to offer the latest beta > distro to the beta users, and the latest GA release to everyone else. > What's the best way of doing this... different servers or a way of > parameterising? You could create two distributions ("beta" and "GA") and associate = targets (users) with either. In your case, if you have many users, I = would programmatically create one association between "GA" and all = targets that don't have a beta flag, and one association between "beta" = and all targets that do have a beta flag. I think I briefly mentioned how to do that with the REST API, but feel = free to follow up... > After a while I can't use the UI anymore, I get "Session Expired". = Even > when I log back in I get the same message and this redirects me back = to > login page. I can log in via incognito mode instead. Hmm, I did recently fix a bug which now expires sessions a bit more = aggressively. However, you should still be able to log out and back in = if this happens. I would have to investigate. It could be that something is left in the = Vaadin session. As a work-around you could try appending this to the = URL: ?restartApplication=3Dtrue That should restart the Vaadin application. Let me know if that helps, = as that would be a hint that something in Vaadin is not correctly reset = when the session times out now. Greetings, Marcel [1] https://issues.apache.org/jira/browse/ACE-221 [2] https://issues.apache.org/jira/browse/ACE-230= --Apple-Mail=_B237E14C-E097-40DD-9953-4DCCB37EA20E--