Yup. We need something in 0.1.0 (to be replaced by provisioning when it arrives)
+1 grz Bram On Mon, Jan 24, 2011 at 3:06 PM, Mark Machielsen <Mark.Machielsen at gxsoftware.com> wrote: > +1 for restoring fileinstall. > > Regards, > Mark. > > From: amdatu-developers-bounces at amdatu.org > [mailto:amdatu-developers-bounces at amdatu.org] On Behalf Of Ivo Ladage-van > Doorn > Sent: Friday, January 21, 2011 9:19 AM > To: amdatu-developers at amdatu.org > Subject: Re: [Amdatu-developers] Edit configuration entries > > Agreed, if we remove something (like fileinstall) we should make sure there > is an alternative before removing it. What we did support in 0.0.4, before > config was refactored and fileinstall was removed was this valid use case; > > - Download Amdatu distribution > - Unzip, append custom bundles, zip > - Send zip to the admin, he will > o Unzip > o Change configuration (like hostname and port of the http service) prior to > first boot > o Start Amdatu > > So in 0.0.4 there was an easy way to set up your own Amdatu server and run it > with you own configuration. > In 0.1.0 the use case above is not supported any more, a typical case of > 'throwing away old shoes' > > So until there is an alternative for the above use case (for example by > provisioning in 0.2.0, 0.3.0 of whenever it comes available), we should keep > fileinstall. > > Regards, Ivo > > > From: amdatu-developers-bounces at amdatu.org > [mailto:amdatu-developers-bounces at amdatu.org] On Behalf Of Mark Machielsen > Sent: woensdag 19 januari 2011 14:17 > To: amdatu-developers at amdatu.org > Subject: Re: [Amdatu-developers] Edit configuration entries > > I would state: since we don't have provisioning yet, we don't remove > functionality (that is used) what will be replaced by provisioning in the > future: don't throw away your old shoes, when you don't have new ones yet. > > Regards, > Mark. > > From: amdatu-developers-bounces at amdatu.org > [mailto:amdatu-developers-bounces at amdatu.org] On Behalf Of Marcel Offermans > Sent: Tuesday, January 18, 2011 4:12 PM > To: amdatu-developers at amdatu.org > Subject: Re: [Amdatu-developers] Edit configuration entries > > Fair enough. > > On 18 Jan 2011, at 13:44 , Dion Meijer wrote: > > If that is the mechanism, we can't use it for the BlueConic releases. We have > to build one final BlueConic release , which is used by everyone, including > external partners. > > From:?amdatu-developers-bounces at > amdatu.org?[mailto:amdatu-developers-bounces at amdatu.org]?On Behalf > Of?Marcel Offermans > Sent:?dinsdag 18 januari 2011 13:18 > To:?amdatu-developers at amdatu.org > Subject:?Re: [Amdatu-developers] Edit configuration entries > > For now, yes, that's the mechanism. Once the management agent is up and > running, you can create a configuration according to the Auto Configuration > specification and provision that to the right target. > > On 18 Jan 2011, at 12:35 , Ivo Ladage-van Doorn wrote: > > How do you 'provision configuration alongside bundles'? Do you mean checking > out Amdatu, update the settings.xml, compile the filebased config bundle and > replace the one in the distribution with this one? > > From:?amdatu-developers-bounces at > amdatu.org?[mailto:amdatu-developers-bounces at amdatu.org]?On Behalf > Of?Marcel Offermans > Sent:?dinsdag 18 januari 2011 12:19 > To:?amdatu-developers at amdatu.org > Subject:?Re: [Amdatu-developers] Edit configuration entries > > Configurations can be provisioned alongside bundles, so before you start a > node you make sure the configuration is correct. > > WebConsole is a developer tool, just like FileInstall, and both should not be > shipped with Amdatu as a means to hand-edit configurations. > > Greetings, Marcel > > > On 18 Jan 2011, at 12:00 , Ivo Ladage-van Doorn wrote: > > > Hi All, > > Last week we discussed the fact that configuration entries stored in > Configuration Admin are currently read-only. We agreed that we should add > metatype information to the configuration entries so that will be editable > using the Felix webconsole. However, while describing the steps to setup a > 2-node Cassandra cluster I figured that this still doesn't provide a real > solution for common use cases, for several reasons: > > .?????????To setup a Cassandra cluster, some 'autobootstrap' must be set to > false on node 1 and to true on one 2, prior to starting the nodes. The nodes > must never be started for the first time with the incorrect autobootstrap > setting. So changing the configuration in the Felix webconsole won't do; > that's just too late. > .?????????You cannot always access the Felix webconsole without the proper > hostname and portnr defined prior to starting Amdatu, as the default port may > already be occupied by another service. When the http service cannot be > started, of course I cannot enter the Felix web console to change the > configuration entries to the proper values. In my case I run the nodes on a > Linux server and cannot access the httpservice as long as it tries to listen > to the default hostname 'localhost' and port '8080'; it will fail with an > 'address already in use' since 8080 is usually already taken by another > service. > > The only possible solution I see right now is replacing the filebased config > bundle with fileinstall (yes, there it is again). In this case config files > are stored on disk and can be changed to the proper values prior to starting > Amdatu for the first time. I know that there is a lot of resistance against > the use of fileinstall, but are there any better alternatives? > > Regards, Ivo > > GX?|?Ivo Ladage-van Doorn?|?Product Architect?|?Wijchenseweg 111?|?6538 SW > Nijmegen?|?The Netherlands?|?T +31(0)24 - 388 82 61?|?F +31(0)24 - 388 86 > 21?|?ivo.ladage-vandoorn at > gxsoftware.com?|?www.gxsoftware.com?|?twitter.com/GXSoftware > > _______________________________________________ > Amdatu-developers mailing list > Amdatu-developers at amdatu.org > http://lists.amdatu.org/mailman/listinfo/amdatu-developers > > _______________________________________________ > Amdatu-developers mailing list > Amdatu-developers at amdatu.org > http://lists.amdatu.org/mailman/listinfo/amdatu-developers > > _______________________________________________ > Amdatu-developers mailing list > Amdatu-developers at amdatu.org > http://lists.amdatu.org/mailman/listinfo/amdatu-developers > > > _______________________________________________ > Amdatu-developers mailing list > Amdatu-developers at amdatu.org > http://lists.amdatu.org/mailman/listinfo/amdatu-developers >
