Michael, On Wed, Jan 22, 2014 at 9:38 PM, Michael <[email protected]>wrote:
> Viktor, I think that Adam post demonstrates my point very well. > sbt-native-packager > deploy > osgi-bundle > web-deployer > sbt multi jvm , > multi-node atmos > and the list is going on and on. They all trying to resolve the problem of > deployment. Obviously they see the problem from different angles. > > Deployment means a lot of things. And java community tries to standardize > it so you could deploy the same logical bundle to tomcat/felix/ or run it > as a server on windows / linux. After that you need to update your > application which is also not an easy task. > Live upgrades is a pipe dream IMO. > Multiply it by amount of nodes, multiple IP addresses / port allocation > based on environment , etc. ... I want to see how long does it take to > someone to deploy akka application with spray into equinox... > After you deployed dozens of nodes you need to gather metrics & monitor > and restart it if it failed. Sometimes you need to restart your application > due to disconnected akka nodes in the cluster (see mailing list topic on > this issue). Also add to the picture deployment as a service on different > Linuxes with different service startup mechanisms (ubuntu vs centos). MK > init script must be rewritten anyway. MK class loader is a topic of > discussion per se. > > So my point is - akka needs to be packaged more friendlier to environment > in which it runs (i.e. osgi) and instead of augmenting MK it should adopt > itself to the outside world. For instance run my war/wab file so i can > package once and run it everywhere. Without deploy folder / hardcoded > '*.jar' extension / plainly loading all embedded jars / not respecting > class path specifications of manifest etc... > I agree with all your assessments of creating friendlier packaging except OSGi—to me it's a failed experiment. > > If you want i can create a clean itemized list of issue but again, my > point is that it might not be required. > I guess I still don't understand the major issue with the MK, it does exactly what it sets out to do. It's a very lightweight packaging of an Akka application in a distributable archive. > > > > > > > > > > On Wed, Jan 22, 2014 at 2:33 PM, Adam <[email protected]> wrote: > >> You might want to look at >> sbt-native-packager<https://github.com/sbt/sbt-native-packager>. >> I use it for all of my projects that need to be run on servers and it works >> great! I also use yajsw <http://yajsw.sourceforge.net/> to run it as a >> service since at work I need to use Windows servers :( >> >> ~Adam~ >> >> >> On Wed, Jan 22, 2014 at 12:58 PM, Peter Wolf <[email protected]> wrote: >> >>> Thanks Victor, I had read that doc, but it left me puzzled. That's >>> why I asked here. >>> >>> Here is the important paragraph: >>> >>> "The purpose of the Akka Microkernel is to offer a bundling mechanism so >>> that you can distribute an Akka application as a single payload, without >>> the need to run in a Java Application Server or manually having to create a >>> launcher script." >>> >>> I would normally create a shell script that simply calls "java >>> <classpath> <class>". It is some work to get the classpath right and >>> include everything needed by Akka and my application. I would then zip >>> everything up and copy it manually to each machine, where I would install >>> it. I would finally set up the machine to boot my Actors when the system >>> comes up. >>> >>> Is this the work that Microkernel makes easier? Is this why I should >>> use it? >>> >>> Thanks >>> P >>> >>> -- >>> >>>>>>>>>> Read the docs: http://akka.io/docs/ >>> >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>> >>>>>>>>>> Search the archives: >>> https://groups.google.com/group/akka-user >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Akka User List" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/akka-user. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- >> >>>>>>>>>> Read the docs: http://akka.io/docs/ >> >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >> >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "Akka User List" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/akka-user/HJiZIex_6v8/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > > Michael Pavlovsky > > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: http://akka.io/faq/ > >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user > --- > You received this message because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/groups/opt_out. > -- Cheers, √ *———————**Viktor Klang* *Chief Architect - **Typesafe <http://www.typesafe.com/>* Twitter: @viktorklang -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/groups/opt_out.
