<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Just to further muddy the waters</p>
<p>Has anybody looked at using AWS ECS?</p>
<p>If you're happy to tie yourself to AWS then it potentially looks
a more appropriate solution than k8s or docker-compose</p>
<p>Although Alfresco themselves seem to be going more and more down
the AWS route I don't think there's anything (yet) that is AWS
specific</p>
<p>(might be nice if the official S3 connector could be released to
the community...)<br>
</p>
<p>(unfortunately I'm traveling during the hackathon but will be at
the devcon if anybody wants to discuss)</p>
<p>Regards,</p>
<p>Ian<br>
</p>
<div class="moz-cite-prefix">On 08/01/2019 11:45, Axel Faust wrote:<br>
</div>
<blockquote type="cite"
cite="mid:0d0478ce-665a-2e7f-e7ab-de7a12f540d2@googlemail.com">
<p>Hi all,</p>
<p>as the mail by Ole has effectively stopped cold most ambitions
with regards to Docker-based SDK (until such a time that people
may get tired waiting on Alfresco deliver on the ideas Ole has
laid out), our focus should probably best be on the actual
(Community Edition) Docker images, and guides / templates
related to them. Angel was so kind and use my initial mail to
add a project to the list for the hack-a-thon at DevCon 2019
(<a class="moz-txt-link-freetext"
href="https://community.alfresco.com/docs/DOC-8064-projects-and-teams-hack-a-thon-at-devcon-2019"
moz-do-not-send="true">https://community.alfresco.com/docs/DOC-8064-projects-and-teams-hack-a-thon-at-devcon-2019</a>),
and of course anyone else who will join that event is invited to
join in on any specific efforts we decide to do on this day, if
interested.</p>
<p>Regards</p>
<p>Axel<br>
</p>
<div class="moz-cite-prefix">On 07/12/2018 14:27, Ole Hejlskov
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:15882FA8-2E4F-4BB8-987B-CA0AC3387C10@phpfreak.dk">
<div class="">Hi all</div>
<div class=""><br class="">
</div>
<div class="">Forgive me, this will be a wall-of-text long
email. TL;DR at the bottom for the lazy.</div>
<div class=""><br class="">
</div>
<div class="">First of all, I just wanted to recognise the
impact the lack of a compatible SDK release has for all of
you. </div>
<div class="">Initially when we released SDK 3.0, it came with a
bunch of promises of compatibility. However, this was all
before we went into the world of microservices and containers.
ACS6 has brought a lot of (good) changes, but unfortunately it
has resulted in unfortunate side effects for the SDK.</div>
<div class=""><br class="">
</div>
<div class="">I am happy to say that we (Alfresco) *are*
committed to bring a compatible SDK. We are working out the
details on exactly when this might happen, and we hope to
share more details soon. There.. I said it. "Soon". I flat out
know how this will rub people the wrong way, but that is
honestly the best I can do. </div>
<div class=""><br class="">
</div>
<div class="">OK with all of that out of the way, let's talk
details. </div>
<div class=""><br class="">
</div>
<div class="">We made good progress during the hackathon, and
lots of discussions later the approach we took was to spin up
the related services (database and search services) as Docker
containers. </div>
<div class=""><br class="">
</div>
<div class="">Now, why did we do this?</div>
<div class="">Several reasons:</div>
<div class="">1) Solr isn't a WAR file anymore, it's an
executable. We *can* have Maven spin up an external executable
(and stop it again) as part of the build lifecycle, but
getting this to work across multiple platforms will be a
nightmare, if not straight out impossible, unless we leverage
profiles (and thereby bring back the dreaded parent pom),
which will be hard to maintain. In SDK 3.0 we wrapped all the
craziness of dealing with Solr packaging into the Alfresco
Maven Plugin. By externalising this into a docker container we
removed A LOT of complexity in the plugin. </div>
<div class="">Solution? Spin it up externally manually, or
leverage Docker to automate it.</div>
<div class=""><br class="">
</div>
<div class="">2) No more H2.</div>
<div class="">Since ACS no longer leverages Hibernate, we can't
control the dialect which enabled us to use H2. There is no
way to cheat or work around it, can't be done as is today. ACS
will require a database to be running. </div>
<div class="">Solution? Spin it up externally manually, or
leverage Docker to automate it.</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">OK, so during the hackathon we relied on using the
Tomcat Maven Plugin to start the repository itself. This
worked at the time, but recent tests have discovered some
very, very annoying issues:</div>
<div class="">a) The Tomcat plugin has not been updated in
years. I believe around 5 years. </div>
<div class="">b) The Tomcat plugin is stuck on Tomcat7</div>
<div class="">c) The default version shipped with the Tomcat
plugin will not load JARs compiled with Java9 (throwing
exceptions about module-info.class and stuff). Latest versions
of ACS Enterprise relies on some artifacts that contains a
module-info.class, so exceptions are all over the place.
Without having tested it, I believe the latest Community
release will have the same issue</div>
<div class="">d) You can, in theory, force the Tomcat plugin to
use a different version, however you will be limited to
Tomcat7 since there are incompatibilities. For the last 5
years this issue has been open (<a
href="https://issues.apache.org/jira/browse/MTOMCAT-234"
class="" moz-do-not-send="true">https://issues.apache.org/jira/browse/MTOMCAT-234</a>)
which would bring support for Tomcat8, but no resolution or
progress made in years</div>
<div class=""><br class="">
</div>
<div class="">If anyone questions this, I'd be happy to dig up
my notes and search histories, there are A LOT of issues with
the plugin due it's been neglected for 5 years.</div>
<div class=""><br class="">
</div>
<div class="">OK, so a lot of issues with the Tomcat plugin. If
we bring out the big hammer and force the Tomcat plugin to the
latest Tomcat7 release, it will actually start without
exceptions... if you are on Java8. Anything higher and it
completely breaks apart.. you see where this is going. </div>
<div class=""><br class="">
</div>
<div class="">This is pretty much where things grinds to a
halt. </div>
<div class=""><br class="">
</div>
<div class="">I no longer believe using an embedded Tomcat like
this is viable. </div>
<div class=""><br class="">
</div>
<div class="">I would be willing to do experiments using the
Cargo plugin, but given the direction we will only start to
see more smaller services, Transformation service and event
gateway just to name a few. It's not impossible to configure
all of this without Docker, but it will be very complex and
extremely difficult to maintain. (Remember how bad upgrading
the between SDK 2.x releases?) </div>
<div class=""><br class="">
</div>
<div class="">The current design goals is to also leverage
Docker to spin up ACS to do integration tests. Ultimately the
SDK will consist of an archetype that can compile a JAR and
AMP, then leverage Docker to orchestrate the integration
tests. </div>
<div class=""><br class="">
</div>
<div class="">If you do not wish to leverage Docker, there is
nothing stopping you from removing the Docker orchestration
from the pom in your project and roll a custom setup. This has
always been the goal: The archetypes serves as an example that
gets you going quickly, but provide enough flexibility to make
changes and only use the bits you need for your project. </div>
<div class=""><br class="">
</div>
<div class="">I assume the next logical question will be how
this affects RAD and the overall development workflow.
Spinning up ACS as a Docker container sounds like it will be
painfully slow, and you have to wait for restarts on every
change. </div>
<div class=""><br class="">
</div>
<div class="">Well, there are different approaches to be taken.
We can mount the target directory into the container. We can
leverage some stuff from JRebel, or look at how DECVM/Spring
Loaded/HotSwap Agent are doing today. I have not personally
done experiments in this area yet, so I'd love to hear
feedback from people who have experimented with it. </div>
<div class=""><br class="">
</div>
<div class="">Again, please keep in mind that the archetypes can
be tweaked and changed based on your needs. Some people loathe
Docker. Some people hate using the embedded Tomcat. The
archetypes are meant to give you a good starting point and you
can totally tweak it to meet your needs.</div>
<div class=""><br class="">
</div>
<div class="">As always, we are very open to feedback. I will
find time to commit my latest experiments (leveraging Tomcat
plugin) to the sdk-4.0 branch ASAP.</div>
<div class=""><br class="">
</div>
<div class="">TL;DR:</div>
<div class="">There will be a compatible SDK with ACS 6.0 and
6.1. </div>
<div class="">The SDK will leverage Docker to spin up services
such as Postgres and Search Services, and ultimately the
repository itself. </div>
<div class=""><br class="">
</div>
<div class="">/Ole</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 7 Dec 2018, at 11.14, Douglas C. R. Paes
<<a href="mailto:douglascrp@gmail.com" class=""
moz-do-not-send="true">douglascrp@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="">Hello Jeff.</div>
<div class=""><br class="">
</div>
<div class="">The idea is not to force the Docker use,
but to use it to make things easier. This is why
Docker is used, to start PostgreSQL and Search
Services only.</div>
<div class="">For Alfresco and Share, there is nothing
different, as the war files are used as always.<br
class="">
</div>
<div class="">But those are optional, and one can have
then running locally using traditional methods.</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr" class="">
<div class="">
<div dir="ltr" class="">Douglas C. R. Paes<br
class="">
<div class=""><br class="">
<b class="">"D</b><b class="">one is
better than perfect</b><b class="">"</b><br
class="">
</div>
</div>
</div>
</div>
</div>
</div>
<br class="">
</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="">Em qui, 6 de dez de 2018 às
23:45, Jeff Potts <<a
href="mailto:jeffpotts01@gmail.com" class=""
moz-do-not-send="true">jeffpotts01@gmail.com</a>>
escreveu:<br class="">
</div>
<blockquote class="gmail_quote">
<div dir="ltr" class="">
<div class="">Why would I want the SDK to use a
Docker image?</div>
<div class=""><br class="">
</div>
<div class="">My opinion is that it should continue
to use the WAR as it has previously. Otherwise, as
you point out, the developer has to add technology
they may not have a need for.</div>
<div class=""><br class="">
</div>
<div class="">Jeff<br class="">
</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="">On Thu, Dec 6, 2018 at 11:36
AM Douglas C. R. Paes <<a
href="mailto:douglascrp@gmail.com"
target="_blank" class="" moz-do-not-send="true">douglascrp@gmail.com</a>>
wrote:<br class="">
</div>
<blockquote class="gmail_quote">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div class="">Hello everyone.</div>
<div class=""><br class="">
</div>
<div class="">Because of the lack of
support from Alfresco in the SDK
space, and because I want to start
using the Alfresco 6 version, I
decided to check on the current status
of the SDK project, and I took the
work started by Ole on the last
Hackathon, and tried to make it work.</div>
<div class=""><br class="">
</div>
<div class="">The result of my effort so
far is available at <a
href="https://github.com/douglascrp/alfresco-sdk/tree/sdk-4.0"
target="_blank" class=""
moz-do-not-send="true">https://github.com/douglascrp/alfresco-sdk/tree/sdk-4.0</a></div>
<div class=""><br class="">
</div>
<div class="">Important... I have been
working only with <b class="">alfresco-platform-jar-archetype</b>,
as I usually don't use the AIO
archetype for anything.<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">When you create the
project using the
alfresco-platform-jar-archetype, the
project will be configured to start
both PostgreSQL and Alfresco Search
Service as Docker containers, but the
project itself will be executed using
the tomcat plugin, just like it was
done in the SDK version 3.0.1.<br
class="">
</div>
<div class=""><br class="">
</div>
<div class="">As this relies on the
official Alfresco Docker image for
Alfresco Search Service, anyone
running it will have to perform the
configuration described by Angel at <a
href="https://github.com/keensoft/alfresco-docker-template/tree/master/templates/201806-GA#how-to-use-this-composition"
target="_blank" class=""
moz-do-not-send="true">https://github.com/keensoft/alfresco-docker-template/tree/master/templates/201806-GA#how-to-use-this-composition</a>,
which is to set the owner of the
.data/solr-data.</div>
<div class="">On Ubuntu: "sudo chown -R
1000:1000 data/solr-data"<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">There are still some
problems with activiti, and because of
that, I had to configure the engline
to be disabled by default.</div>
<div class=""><br class="">
</div>
<div class="">Feel free to test it and
tell me what you think.</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">
<div dir="ltr"
class="gmail-m_794878530123616912m_-5396404239063398204gmail_signature">
<div dir="ltr" class="">
<div class="">
<div dir="ltr" class="">Douglas
C. R. Paes<br class="">
<div class=""><br class="">
<b class="">"D</b><b
class="">one is better
than perfect</b><b
class="">"</b><br
class="">
</div>
</div>
</div>
</div>
</div>
</div>
<br class="">
</div>
</div>
</div>
</div>
</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="">Em seg, 26 de nov de
2018 às 10:16, Angel Borroy <<a
href="mailto:angel.borroy@keensoft.es"
target="_blank" class=""
moz-do-not-send="true">angel.borroy@keensoft.es</a>>
escreveu:<br class="">
</div>
<blockquote class="gmail_quote">
<div class="">
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_customfont"
class="">You are right, Axel.</div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_customfont"
class=""><br class="">
</div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_customfont"
class="">Sorry for trolling your initial
(and great) initiative.</div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_customfont"
class=""><br class="">
</div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_customfont"
class="">Hoping people will fallback to
main subject of this thread...</div>
<br class="">
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_sign_1543234550884515072"
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_sign"><span
class=""></span>
<p class=""><span class="">Angel Borroy</span><span
class=""><br class="">
</span><span class="" lang="EN-US">keen</span><b
class=""><span class="" lang="EN-US">soft </span></b><span
class="" lang="EN-US">a </span><b
class=""><span class="" lang="EN-US">UST </span></b><b
class=""><span class="" lang="EN-US">Global </span></b><span
class="" lang="EN-US">company</span></p>
<p class=""><span class="">CONFIDENCIALIDAD:</span></p>
<p class=""><span class="">La presente
comunicación y, en su caso, los
ficheros que lleve adjuntos,
pertenecen exclusivamente a las
personas a las que va dirigido y puede
contener información confidencial. Si
usted no es el destinatario de este
mensaje (o la persona responsable de
su entrega), considérese advertido de
que lo ha recibido por error y que
cualquier uso, difusión, reenvío o
copia están prohibidos legalmente. Si
ha recibido este mensaje por error,
por favor notifíquelo al remitente y
proceda a destruirlo inmediatamente.</span></p>
<p class=""><span class="" lang="EN-US">This
message and the attached documents may
contain privileged/confidential
information and intended solely for
the use of the individual to whom it
is addressed. If you are not the
intended recipient (or responsible for
delivery of the message to such a
person) be advised that you have
received this message in error and
that any use, dissemination,
forwarding, printing or copying of
this e-mail is strictly prohibited. If
you have received this message in
error please notify it to the sender
and destroy it immediately.</span></p>
</div>
<br class="">
<p
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672airmail_on">On
26 November 2018 at 13:14:33, Axel Faust (<a
href="mailto:axel.faust.g@googlemail.com" target="_blank" class=""
moz-do-not-send="true">axel.faust.g@googlemail.com</a>)
wrote:</p>
<blockquote type="cite"
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672clean_bq"><span
class="">
<div class="">
<div class="">
<p class="">This is only using a
test / RC (release candidate)
state of 6.1 EE - if you look in <a
href="http://artifacts.alfresco.com/" target="_blank" class=""
moz-do-not-send="true">artifacts.alfresco.com</a>
(I can via one of my customers)
you'll see there is no EE GA yet.</p>
<p class="">Haven't we all learned
by now not to trust Alfresco
marketing (e.g. what's written on
the homepage) when it comes to
100% correctly / transparently
representing facts? CE vs EE
comparison has been (naturally)
biased forever, and since Alfresco
was planning a marketing push for
November it is also understandable
that they might want to highlight
the next release, even if it may
not yet be fully ready...</p>
<p class="">Of course as always,
advance / roadmap communication by
Alfresco could be better to avoid
any such confusion.<br class="">
</p>
<div
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672moz-cite-prefix">On
26/11/2018 12:56, Angel Borroy
wrote:<br class="">
</div>
<blockquote type="cite" class="">
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_customfont"
class=""> At least, in my case,
comes from here:</div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_customfont"
class=""> <br class="">
</div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_customfont"
class=""> <span
id="cid:167848d0b48b73599f41"><part1.00570E7E.7B019451@googlemail></span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_customfont"
class=""> <br class="">
</div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_customfont"
class=""> This looks like a
public ACS EE 6.1 release...</div>
<br class="">
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_sign_1543233348719987968"
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672bloop_sign">
<p class=""> <span class="">Angel
Borroy</span><span class=""><br
class="">
</span> <span class=""
lang="EN-US">keen</span><b
class=""><span class=""
lang="EN-US">soft </span></b><span
class="" lang="EN-US">a </span><b
class=""><span class=""
lang="EN-US">UST </span></b><b
class=""><span class=""
lang="EN-US">Global </span></b><span
class="" lang="EN-US">company</span></p>
<p class=""> <span class="">email:
</span><a
href="mailto:angel.borroy@keensoft.es"
target="_blank" class=""
moz-do-not-send="true"><span
class="">angel.borroy@keensoft.es</span></a><span
class=""><br class="">
web: </span><a
href="http://www.keensoft.es/"
target="_blank" class=""
moz-do-not-send="true"><span
class="">http://www.keensoft.es</span></a><span
class=""><br class="">
móvil: <a
href="tel://+34%20655%2047%2047%2055"
target="_blank" class=""
moz-do-not-send="true">+34
655 47 47 55</a></span></p>
<p class=""> <span class="">CONFIDENCIALIDAD:</span></p>
<p class=""> <span class="">La
presente comunicación y, en
su caso, los ficheros que
lleve adjuntos, pertenecen
exclusivamente a las
personas a las que va
dirigido y puede contener
información confidencial. Si
usted no es el destinatario
de este mensaje (o la
persona responsable de su
entrega), considérese
advertido de que lo ha
recibido por error y que
cualquier uso, difusión,
reenvío o copia están
prohibidos legalmente. Si ha
recibido este mensaje por
error, por favor notifíquelo
al remitente y proceda a
destruirlo inmediatamente.</span></p>
<p class=""> <span class=""
lang="EN-US">This message
and the attached documents
may contain
privileged/confidential
information and intended
solely for the use of the
individual to whom it is
addressed. If you are not
the intended recipient (or
responsible for delivery of
the message to such a
person) be advised that you
have received this message
in error and that any use,
dissemination, forwarding,
printing or copying of this
e-mail is strictly
prohibited. If you have
received this message in
error please notify it to
the sender and destroy it
immediately.</span></p>
</div>
<br class="">
<p
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672airmail_on">On
26 November 2018 at 12:54:48,
Ole Hejlskov (<a
href="mailto:ole@phpfreak.dk"
target="_blank" class=""
moz-do-not-send="true">ole@phpfreak.dk</a>)
wrote:</p>
<blockquote type="cite"
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672clean_bq">
<div class="">
<div class=""><span class="">Hi
all</span>
<div class=""><span class=""><br
class="">
</span></div>
<div class=""><span class="">I’m
not sure where the
confusion started, but
I’ve just verified
internally that ACS 6.1
has entered the
regression testing
phase. Once this
completes there will be
a ACS 6.1 GA release for
Community, followed by
6.1 EE. The only thing
that isn’t clear to me
at this stage, is wether
6.1 EE comes before 6.1
CE (GA) or vice-versa. </span></div>
<div class=""><span class=""><br
class="">
</span></div>
<div class=""><span class="">Hope
this clears things up.</span></div>
<div class=""><span class=""><br
class="">
</span></div>
<div class=""><span class="">/Ole<br
class="">
</span>
<div class=""><span
class=""><br class="">
</span>
<blockquote type="cite"
class="">
<div class=""><span
class="">On 26 Nov
2018, at 11.33,
Francesco Corti
<<a
href="mailto:fcorti@gmail.com"
target="_blank"
class=""
moz-do-not-send="true">fcorti@gmail.com</a>>
wrote:</span></div>
<span class=""><br
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672Apple-interchange-newline">
</span>
<div class="">
<div dir="ltr"
class=""><span
class="">Good
morning guys,</span>
<div class=""><span
class=""><br
class="">
</span></div>
<div class=""><span
class="">I'm
afraid there
is something
to adjust.<br
class="">
ACS 6.1
Community
Edition won't
be a GA
release.</span></div>
<div class=""><span
class="">I
think John
mentioned the
EE release
(that will be
GA by
default).</span></div>
<div class=""><span
class="">Just
a heads up.</span></div>
<div class=""><span
class="">In
every case,
the initiative
continue to be
a good idea.</span></div>
<div class=""><span
class=""><br
class="">
</span></div>
<div class=""><span
class="">Cheers,</span></div>
<div class=""><span
class=""><br
class="">
</span></div>
<div class=""><span
class="">-F</span></div>
<div class=""><span
class=""><br
class="">
</span></div>
<div class=""><span
class=""><br
class="">
</span></div>
</div>
<span class=""><br
class="">
</span>
<div
class="gmail_quote">
<div dir="ltr"
class=""><span
class="">Il
giorno lun 26
nov 2018 alle
ore 10:29
Angel Borroy
<<a
href="mailto:angel.borroy@keensoft.es"
target="_blank" class="" moz-do-not-send="true">angel.borroy@keensoft.es</a>>
ha scritto:<br
class="">
</span></div>
<blockquote
class="gmail_quote">
<div class="">
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class="">Hi,</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class=""><br
class="">
</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class="">Sorry
for being so
vague. I have
no more
information
than you, as
UST Global is
not still an
Alfresco
partner. We
are applying
from June but
it looks like
Alfresco has
plenty of
skilled
partners in
Spain and
there is no
room for one
more. Two
weeks ago I
started an
Enterprise
project in
collaboration
with a local
partner, as
Alfresco
forbid UST
Global to work
with Community
(despite we
are not
partners
nowadays). I’m
starting to be
very concerned
about Alfresco
Sales
ecosystem, but
probably it’s
only my pov.</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class=""><br
class="">
</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class="">Anyway,
you are right,
John Knowles
said that they
will publish
an ACS
Community
release in GA
status. But,
afaik, this is
the first
Community
release
released after
the Enterprise
one. Error or
strategy? Who
knows…</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class=""><br
class="">
</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class="">Let’s
focus on this
initiative and
let’s keep
apart all my
bad feelings
about the life
in general.</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class=""><br
class="">
</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class="">Best,</span></div>
<span class=""><br
class="">
</span>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_sign_1543224161918328064"
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_sign">
<p class=""><span
class=""><span
class="">Angel
Borroy</span><span
class=""><br
class="">
</span> <span
class=""
lang="EN-US">keen</span><b
class=""><span
class=""
lang="EN-US">soft </span></b><span
class=""
lang="EN-US">a </span><b
class=""><span
class=""
lang="EN-US">UST </span></b><b
class=""><span
class=""
lang="EN-US">Global </span></b><span
class=""
lang="EN-US">company</span></span></p>
<p class=""><span
class="">email:
</span><a
href="mailto:angel.borroy@keensoft.es"
target="_blank" class="" moz-do-not-send="true"><span class="">angel.borroy@keensoft.es</span></a><span
class=""><br
class="">
web: </span><a
href="http://www.keensoft.es/" target="_blank" class=""
moz-do-not-send="true"><span
class="">http://www.keensoft.es</span></a><span
class=""><br
class="">
móvil: <a
class=""
moz-do-not-send="true">+34
655 47 47 55</a></span></p>
<p class=""><span
class="">CONFIDENCIALIDAD:</span></p>
<p class=""><span
class="">La
presente
comunicación
y, en su caso,
los ficheros
que lleve
adjuntos,
pertenecen
exclusivamente
a las personas
a las que va
dirigido y
puede contener
información
confidencial.
Si usted no es
el
destinatario
de este
mensaje (o la
persona
responsable de
su entrega),
considérese
advertido de
que lo ha
recibido por
error y que
cualquier uso,
difusión,
reenvío o
copia están
prohibidos
legalmente. Si
ha recibido
este mensaje
por error, por
favor
notifíquelo al
remitente y
proceda a
destruirlo
inmediatamente.</span></p>
<p class=""><span
class=""
lang="EN-US">This
message and
the attached
documents may
contain
privileged/confidential
information
and intended
solely for the
use of the
individual to
whom it is
addressed. If
you are not
the intended
recipient (or
responsible
for delivery
of the message
to such a
person) be
advised that
you have
received this
message in
error and that
any use,
dissemination,
forwarding,
printing or
copying of
this e-mail is
strictly
prohibited. If
you have
received this
message in
error please
notify it to
the sender and
destroy it
immediately.</span></p>
</div>
<br class="">
<p
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945airmail_on">On
26 November
2018 at
09:43:45, Axel
Faust (<a
href="mailto:axel.faust.g@googlemail.com"
target="_blank" class="" moz-do-not-send="true">axel.faust.g@googlemail.com</a>)
wrote:</p>
<blockquote
type="cite"
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945clean_bq">
<div class="">
<div class="">
<p class=""><span
class="">Hello
Angel,</span></p>
<p class=""><span
class="">since
you now are a
partner, you
may have some
information I
don't get to
see - but last
time John
Knowles was on
IRC (~2 weeks
ago) he
indicated that
the next ACS
Community
release would
be a GA, so
ACS 6.1 would
have a
Community
equivalent.</span></p>
<p class=""><span
class="">Regards,
Axel<br
class="">
</span></p>
<div
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945moz-cite-prefix"><span
class="">On
26/11/2018
09:36, Angel
Borroy wrote:<br
class="">
</span></div>
<blockquote
type="cite"
class="">
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class="">Nice
idea, Axel.</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class=""><br
class="">
</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class="">I’m
open to
collaborate,
despite my
basic skills
on Docker, k8s
and many other
relevant
software
involved in
the “new”
Alfresco.</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class=""><br
class="">
</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class="">Now
that Alfresco
is ignoring
deliberatively
the Community
(ACS 6.1 will
be published
without having
a Community
equivalent),
it’s time to
act. Probably
providing a
deployment and
developing
environment
for everyone
is the right
approach.</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class=""><br
class="">
</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class="">I’m
not able to
organise this
initiative,
but let me
know if I can
help in any
way.</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class=""><br
class="">
</span></div>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_customfont"
class=""><span
class="">Best,</span></div>
<span class=""><br
class="">
</span>
<div
id="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_sign_1543221187793185024"
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945bloop_sign">
<p class=""><span
class=""><span
class="">Angel
Borroy</span><span
class=""><br
class="">
</span> <span
class=""
lang="EN-US">keen</span><b
class=""><span
class=""
lang="EN-US">soft </span></b><span
class=""
lang="EN-US">a </span><b
class=""><span
class=""
lang="EN-US">UST </span></b><b
class=""><span
class=""
lang="EN-US">Global </span></b><span
class=""
lang="EN-US">company</span></span></p>
<p class=""><span
class="">email:
</span><a
href="mailto:angel.borroy@keensoft.es"
target="_blank" class="" moz-do-not-send="true"><span class="">angel.borroy@keensoft.es</span></a><span
class=""><br
class="">
web: </span><a
href="http://www.keensoft.es/" target="_blank" class=""
moz-do-not-send="true"><span
class="">http://www.keensoft.es</span></a><span
class=""><br
class="">
móvil: <a
href="tel://+34%20655%2047%2047%2055"
target="_blank" class="" moz-do-not-send="true">+34 655 47 47 55</a></span></p>
<p class=""><span
class="">CONFIDENCIALIDAD:</span></p>
<p class=""><span
class="">La
presente
comunicación
y, en su caso,
los ficheros
que lleve
adjuntos,
pertenecen
exclusivamente
a las personas
a las que va
dirigido y
puede contener
información
confidencial.
Si usted no es
el
destinatario
de este
mensaje (o la
persona
responsable de
su entrega),
considérese
advertido de
que lo ha
recibido por
error y que
cualquier uso,
difusión,
reenvío o
copia están
prohibidos
legalmente. Si
ha recibido
este mensaje
por error, por
favor
notifíquelo al
remitente y
proceda a
destruirlo
inmediatamente.</span></p>
<p class=""><span
class=""
lang="EN-US">This
message and
the attached
documents may
contain
privileged/confidential
information
and intended
solely for the
use of the
individual to
whom it is
addressed. If
you are not
the intended
recipient (or
responsible
for delivery
of the message
to such a
person) be
advised that
you have
received this
message in
error and that
any use,
dissemination,
forwarding,
printing or
copying of
this e-mail is
strictly
prohibited. If
you have
received this
message in
error please
notify it to
the sender and
destroy it
immediately.</span></p>
</div>
<br class="">
<p
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945airmail_on">On
25 November
2018 at
22:57:06, Axel
Faust (<a
href="mailto:axel.faust.g@googlemail.com"
target="_blank" class="" moz-do-not-send="true">axel.faust.g@googlemail.com</a>)
wrote:</p>
<blockquote
type="cite"
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945clean_bq">
<div class="">
<div class=""><span
class="">Hello
guys,<br
class="">
<br class="">
TL;DR: Instead
of revisiting
our previous
pre-bundled
Community
build<br
class="">
idea, maybe
more
short-term /
easier to
realize value
could be
gained by<br
class="">
collaborating
on guides /
documentation
/ examples
regarding
Docker<br
class="">
deployments to
help community
members make
the switch,
AND/OR create
a<br class="">
standard build
setup (in lieu
of an updated
Alfresco SDK
that may never<br
class="">
arrive)
incorporating
the new
deployment
approach and
achieving full<br
class="">
compatibility
with the most
recent
Alfresco
releases.<br
class="">
<br class="">
This mail is a
revisit of a
mail Daren
sent in the
middle of the
thread<br
class="">
for volunteers
for the DevCon
talk
submission
review ([1]).
I don't know<br
class="">
how many
actually read
the mail
considering
the misleading
subject line.<br
class="">
In it he asked
if there is
interest in
revisiting our
previous work<br
class="">
around a
pre-bundled
Alfresco
Community
build (at the
time using
puppet)<br
class="">
and maybe
adapted /
updating that
to be in line
with the
current Docker<br
class="">
/ Kubernetes
approach.<br
class="">
<br class="">
In the last
two months I
have had the
(dis-)pleasure
to familiarize<br
class="">
myself with
the current
state of the
Alfresco
Docker and
Helm charts /<br
class="">
Kubernetes
work in
preparation
for a training
at an Alfresco
partner.<br
class="">
Anyone
following me
on Twitter
might have
seen a rant or
two. It<br
class="">
certainly is
not the most
intuitive and
not helped by
the fact that<br
class="">
Alfresco tends
to break stuff
shortly after
providing an
initially<br
class="">
working state.<br
class="">
<br class="">
Given how
tricky it can
be for
community
members /
customers to
switch<br
class="">
over to the
new approach
without any
prior
experience, I
would say that<br
class="">
any guides /
documentation
that we as the
Order could
collaboratively<br class="">
put together
would be much
more
valuable/needed
at this point
than<br
class="">
simply
revisiting the
pre-bundled
build. As both
the Docker
Compose<br
class="">
scripts and
Helm charts
from Alfresco
should only be
considered as
a<br class="">
starting point
/ reference
rather than a
ready-to-use
setup, we
might<br
class="">
also want to
look into
providing
improved
variants for
these (Helm
may<br
class="">
be a lower
priority as
it/Kubernetes
likely is not
relevant for
most<br
class="">
community
users). I know
that Angel has
already done
work in the
area of<br
class="">
an improved
compose
reference
([2]) - maybe
that could be
a starting<br
class="">
point to flesh
out / improve
upon...<br
class="">
<br class="">
In my training
I have also
integrated the
new Docker
images as a
runtime<br
class="">
environment
for
("not-really-rapid")
application
development in
my Maven<br
class="">
setup, and
also used it
for the
integration
tests therein.
In another,<br
class="">
personal
project I have
started to use
Docker
containers
even for my<br
class="">
regular unit
tests.<br
class="">
Alfresco has
still not
released a SDK
natively
compatible
with Alfresco<br
class="">
6, and given
their
long-term goal
of moving
customers/users
off of<br
class="">
in-process
extensions may
likely not
provide an
updated
version
anytime<br
class="">
soon. I know
most people in
the Order have
sufficient
skill to adapt
the<br
class="">
current SDK to
work with 6,
but that is
likely not
true for most<br
class="">
community
users out
there. So
maybe we as
the Order
should look
into<br
class="">
providing a
reference
build setup of
our own, using
the new<br
class="">
incorporating
the new Docker
approach as
best as
possible. And
maybe<br
class="">
such work will
naturally lead
us to general
improvements /
definition of<br
class="">
a base image
e.g. with
regards to
image size,
code+test
round-trip
time<br
class="">
etc...<br
class="">
<br class="">
Regards<br
class="">
<br class="">
Axel<br
class="">
<br class="">
<br class="">
[1]<br
class="">
<a
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945moz-txt-link-freetext"
href="http://lists.xtreamlab.net/pipermail/ootb-hive/2018-September/001028.html"
target="_blank" moz-do-not-send="true">http://lists.xtreamlab.net/pipermail/ootb-hive/2018-September/001028.html</a><br
class="">
<br class="">
[2] <a
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945moz-txt-link-freetext"
href="https://github.com/keensoft/docker-alfresco" target="_blank"
moz-do-not-send="true">https://github.com/keensoft/docker-alfresco</a><br
class="">
<br class="">
_______________________________________________<br class="">
OOTB-hive
mailing list<br
class="">
<a
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945moz-txt-link-abbreviated"
href="mailto:OOTB-hive@lists.xtreamlab.net" target="_blank"
moz-do-not-send="true">OOTB-hive@lists.xtreamlab.net</a><br
class="">
<a
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672m_2548926153693929836m_5608294723039762945moz-txt-link-freetext"
href="https://lists.xtreamlab.net/mailman/listinfo/ootb-hive"
target="_blank"
moz-do-not-send="true">https://lists.xtreamlab.net/mailman/listinfo/ootb-hive</a><br
class="">
</span></div>
</div>
</blockquote>
</blockquote>
</div>
</div>
</blockquote>
</div>
_______________________________________________<br class="">
OOTB-hive
mailing list<br
class="">
<a
href="mailto:OOTB-hive@lists.xtreamlab.net"
target="_blank" class="" moz-do-not-send="true">OOTB-hive@lists.xtreamlab.net</a><br
class="">
<a
href="https://lists.xtreamlab.net/mailman/listinfo/ootb-hive"
rel="noreferrer" target="_blank" class="" moz-do-not-send="true">https://lists.xtreamlab.net/mailman/listinfo/ootb-hive</a><br
class="">
</blockquote>
</div>
_______________________________________________<br class="">
OOTB-hive mailing
list<br class="">
<a
href="mailto:OOTB-hive@lists.xtreamlab.net"
target="_blank"
class=""
moz-do-not-send="true">OOTB-hive@lists.xtreamlab.net</a><br
class="">
<a
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672moz-txt-link-freetext"
href="https://lists.xtreamlab.net/mailman/listinfo/ootb-hive"
target="_blank"
moz-do-not-send="true">https://lists.xtreamlab.net/mailman/listinfo/ootb-hive</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
_______________________________________________<br class="">
OOTB-hive mailing list<br
class="">
<a
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672moz-txt-link-abbreviated"
href="mailto:OOTB-hive@lists.xtreamlab.net" target="_blank"
moz-do-not-send="true">OOTB-hive@lists.xtreamlab.net</a><br
class="">
<a
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672moz-txt-link-freetext"
href="https://lists.xtreamlab.net/mailman/listinfo/ootb-hive"
target="_blank"
moz-do-not-send="true">https://lists.xtreamlab.net/mailman/listinfo/ootb-hive</a><br
class="">
</div>
</div>
</blockquote>
<br class="">
<fieldset
class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672mimeAttachmentHeader"></fieldset>
<pre class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672moz-quote-pre">_______________________________________________
OOTB-hive mailing list
<a class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672moz-txt-link-abbreviated" href="mailto:OOTB-hive@lists.xtreamlab.net" target="_blank" moz-do-not-send="true">OOTB-hive@lists.xtreamlab.net</a>
<a class="gmail-m_794878530123616912m_-5396404239063398204gmail-m_8322451100745873672moz-txt-link-freetext" href="https://lists.xtreamlab.net/mailman/listinfo/ootb-hive" target="_blank" moz-do-not-send="true">https://lists.xtreamlab.net/mailman/listinfo/ootb-hive</a>
</pre>
</blockquote>
_______________________________________________<br class="">
OOTB-hive mailing list<br class="">
<a
href="mailto:OOTB-hive@lists.xtreamlab.net"
target="_blank" class=""
moz-do-not-send="true">OOTB-hive@lists.xtreamlab.net</a><br
class="">
<a
href="https://lists.xtreamlab.net/mailman/listinfo/ootb-hive"
target="_blank" class=""
moz-do-not-send="true">https://lists.xtreamlab.net/mailman/listinfo/ootb-hive</a><br
class="">
</div>
</div>
</span></blockquote>
</div>
_______________________________________________<br class="">
OOTB-hive mailing list<br class="">
<a href="mailto:OOTB-hive@lists.xtreamlab.net"
target="_blank" class=""
moz-do-not-send="true">OOTB-hive@lists.xtreamlab.net</a><br
class="">
<a
href="https://lists.xtreamlab.net/mailman/listinfo/ootb-hive"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">https://lists.xtreamlab.net/mailman/listinfo/ootb-hive</a><br
class="">
</blockquote>
</div>
_______________________________________________<br
class="">
OOTB-hive mailing list<br class="">
<a href="mailto:OOTB-hive@lists.xtreamlab.net"
target="_blank" class="" moz-do-not-send="true">OOTB-hive@lists.xtreamlab.net</a><br
class="">
<a
href="https://lists.xtreamlab.net/mailman/listinfo/ootb-hive"
rel="noreferrer" target="_blank" class=""
moz-do-not-send="true">https://lists.xtreamlab.net/mailman/listinfo/ootb-hive</a><br
class="">
</blockquote>
</div>
</blockquote>
</div>
_______________________________________________<br
class="">
OOTB-hive mailing list<br class="">
<a href="mailto:OOTB-hive@lists.xtreamlab.net" class=""
moz-do-not-send="true">OOTB-hive@lists.xtreamlab.net</a><br
class="">
<a class="moz-txt-link-freetext"
href="https://lists.xtreamlab.net/mailman/listinfo/ootb-hive"
moz-do-not-send="true">https://lists.xtreamlab.net/mailman/listinfo/ootb-hive</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OOTB-hive mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OOTB-hive@lists.xtreamlab.net" moz-do-not-send="true">OOTB-hive@lists.xtreamlab.net</a>
<a class="moz-txt-link-freetext" href="https://lists.xtreamlab.net/mailman/listinfo/ootb-hive" moz-do-not-send="true">https://lists.xtreamlab.net/mailman/listinfo/ootb-hive</a>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
OOTB-hive mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OOTB-hive@lists.xtreamlab.net">OOTB-hive@lists.xtreamlab.net</a>
<a class="moz-txt-link-freetext" href="https://lists.xtreamlab.net/mailman/listinfo/ootb-hive">https://lists.xtreamlab.net/mailman/listinfo/ootb-hive</a>
</pre>
</blockquote>
</body>
</html>