Hello Kevin, At one of my clients we are running Apache Karaf in docker containers and we are happy with the result. We have a base docker image with Java and a custom distro of Apache Karaf. >From this base image we create specializations for different environments. Jenkins is used, but due to security and practical reasons, only to assemble the custom karaf distribution and the docker images. These images are pushed to a Nexus repository. For major releases we usually replace the docker images, but in some situations, like limited bandwidth or reduced/no downtime, we only update the bundles that changed. One aspect we are trying to improve is the size of the docker images. The images are a bit over 1GB, a size that is probably not a big issue when you are deploying to a datacenter or cloud environment, but in a situation with hundreds of remote locations and limited bandwidth, it starts to be a bit troublesome.
Regards, João Assunção Email: joao.assun...@exploitsys.com Mobile: +351 916968984 Phone: +351 211933149 Web: www.exploitsys.com On Fri, Jan 19, 2018 at 4:46 PM, Matthews, Kevin via osgi-dev < osgi-dev@mail.osgi.org> wrote: > Hi Raymond, you read my mind. I figured since no one answer better just do > whatever best fit. J Hopefully osgi grows so you can choose whatever you > like organic vs non-organic. > > > > *From:* Raymond Auge [mailto:raymond.a...@liferay.com] > *Sent:* Friday, January 19, 2018 11:14 AM > *To:* Matthews, Kevin > *Cc:* OSGi Developer Mail List > *Subject:* Re: OSGI application deployment targets > > > > Hey Kevin, > > I think the reason you are not getting an answer here is because the > question is a little bit like: > > What's better, Coke or Pepsi? > > There's no "best practice" for deployment in OSGi runtimes. The answer is > pretty much "Whatever works for you!" If Docker is something you know.. > then Docker it is! If it's ACE, then use ACE! If it's a home brewed thing > that has proven to work, then that's probably pretty ok as well. > > There's no right or wrong answer as long as you've considered and are > ready to deal with the implications of your choice. > > > > Sincerely, > > - Ray > > > > On Mon, Jan 8, 2018 at 11:32 AM, Matthews, Kevin < > kevin.matth...@firstdata.com> wrote: > > Hi OSGI Team, > > > > I would like to know what is the standard enterprise production way of > deploying OSGI bnd enroute application to a target. > > > > 1. Should we deploy our OSGI bnd enroute bundles as a single > executable JAR as stated in the tutorial http://enroute.osgi.org/ > tutorial_base/700-deploy.html > <https://urldefense.proofpoint.com/v2/url?u=http-3A__enroute.osgi.org_tutorial-5Fbase_700-2Ddeploy.html&d=DwMFaQ&c=ewHkv9vLloTwhsKn5d4bTdoqsmBfyfooQX5O7EQLv5TtBZ1CwcvjU063xndfqI8U&r=wKHHp1xupEN1UoR2CPDlg9US2Vs3om5ld5YqSsWMQX8&m=pTMH1ercBaKDApYfbgbhWDKR7ky456V1A_nvwKjjmj4&s=tsKpvHcQsOYjT1AvTX7vaLlTc0LWRl8a3NpcbxBQFog&e=> > to a single server that has OS and JVM? > > 2. Should we deploy using Jenkins and apache ACE to a standalone > server or (Cloud)? > > 3. Should we deploy using Jenkins/bamboo and ACE to a docker > container.? > > 4. If we deploy as an excucatble Jar, will we be able to > stop/start/activate individual bundles? > > > > > > Thanks, > > Kevin > > The information in this message may be proprietary and/or confidential, > and protected from disclosure. If the reader of this message is not the > intended recipient, or an employee or agent responsible for delivering this > message to the intended recipient, you are hereby notified that any > dissemination, distribution or copying of this communication is strictly > prohibited. If you have received this communication in error, please notify > First Data immediately by replying to this message and deleting it from > your computer. > > > > > -- > > *Raymond Augé* > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.liferay.com_web_raymond.auge_profile&d=DwMFaQ&c=ewHkv9vLloTwhsKn5d4bTdoqsmBfyfooQX5O7EQLv5TtBZ1CwcvjU063xndfqI8U&r=wKHHp1xupEN1UoR2CPDlg9US2Vs3om5ld5YqSsWMQX8&m=pTMH1ercBaKDApYfbgbhWDKR7ky456V1A_nvwKjjmj4&s=G5v1u-70SLhW1kO8yyF9iZsxLeJlrWtQm_AyDYdrvfY&e=> > (@rotty3000) > > Senior Software Architect *Liferay, Inc.* > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.liferay.com&d=DwMFaQ&c=ewHkv9vLloTwhsKn5d4bTdoqsmBfyfooQX5O7EQLv5TtBZ1CwcvjU063xndfqI8U&r=wKHHp1xupEN1UoR2CPDlg9US2Vs3om5ld5YqSsWMQX8&m=pTMH1ercBaKDApYfbgbhWDKR7ky456V1A_nvwKjjmj4&s=rsXqV73F4wECsGN4_th9yL9iEEIrzWlkQDTSTT453kc&e=> > (@Liferay) > > Board Member & EEG Co-Chair, OSGi Alliance > <https://urldefense.proofpoint.com/v2/url?u=http-3A__osgi.org&d=DwMFaQ&c=ewHkv9vLloTwhsKn5d4bTdoqsmBfyfooQX5O7EQLv5TtBZ1CwcvjU063xndfqI8U&r=wKHHp1xupEN1UoR2CPDlg9US2Vs3om5ld5YqSsWMQX8&m=pTMH1ercBaKDApYfbgbhWDKR7ky456V1A_nvwKjjmj4&s=cB324QOLmCw3_ICW_dnrasfQHbbSZkC7LTapb3lyyLE&e=> > (@OSGiAlliance) > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev >
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
