Thanks for your questions, I provided my answers inline.
On Wed, Feb 1, 2017 at 10:31 AM, Max Rydahl Andersen <manderse(a)redhat.com>
> Hey Andrew,
> Yes, this is a really important question, and it's something that I
> that the Forge architecture supports out-of-the-box. Every interaction
> the UI API (the Forge commands, per say) is stored in a request-scoped
> UIContext object that is initialized when a command is invoked and
> destroyed when the command finishes executing. That means that you can
> execute multiple concurrent commands in a single Forge instance and
> will not affect each other.
> When it comes to security, as a good practice, it is important to
> the commands that the exposed REST service can execute.
> That's why in the Obsidian backend we only expose a REST
> consuming the Forge API to execute a limited number of commands (more
> specifically, the ones exposed by the obsidian-addon)
> Last but not least, as the Forge Online app is just a PoC illustrating
> Forge can work in a web environment, it does not impose restrictions
> to the
> supported commands, therefore it shouldn't be a web app to be used in
Since we need something for production I would be curious to know what
you feel are missing ?
I was referring to the UI offered by Forge Online app (
). The core libraries
is already being used in the Obsidian Toaster and Fabric8 (not the same
binaries/packages, but the code is similar)
> PS: It would be nice to ping the Fabric8 team for this matter as they
> already using Forge as their project generator solution for a long
> time now.
In case you missed it - fabric8 team is now part of devtools and
devtools are fabric8 :)
We'll get James et.al. involved (they are in f2f meetings this week),
but as I understood
Fabric8 have a fork of the PoC adjusted to handle some more complex
workflows they were
exploring. Things they would like to get merged back as I understand it.
Good, yes, that's right
That said - to outline the items we were discussing about forge as a
Main reason we need it in first place is that Forge is *massive*, takes
up a lot of
resources - even more than Eclipse Che; thus we are very interested in
being able to run
Forge without having one instance per user.
I need some numbers here regarding the "a lot of resources - even more
Eclipse Che". Is that because it creates a Weld instance per addon
that depends on the furnace-cdi container?
Most of the core addons depend on the furnace-simple container, which does
not boot Weld.
Also, Weld is no longer heavy, you know :)
In that we had some questions and concerns in addition to the ones
A) can forge run without access to download updates etc. from maven and
i.e. can we lock updates down and ensure it and its execution cannot
just because someone updated a plugin.
(We discussed firewalling it completely to be sure :)
No updates are downloaded automatically in Forge. There are commands to
update addons, but if you don't expose those commands that will
Forge loads the addons on a specified directory. If nothing is deployed
there (by any external process), it won't change anything
In addition, you can specify a settings.xml with <offline> set to ensure
that the Maven API won't try to look for any remote data.
B) Is there a way to ensure that secrets like GitHub auth keys and
not exposed to users nor in logs ?
Yes, you can use the Configuration addon for that. There is an example
encrypting data here:
(maybe that's not a good example, but you get the idea)
Basically with this addon you'll have this information read from a
properties file (the contents may be encrypted or not - that's up to you).
If that's not enough, we can create a Forge addon or improve any of the
core ones that does what you need.
C) Any expectations/ideas on how we would integrate obsidian
Two options we considered:
1) call out to separate hosted obsidian-toaster and run the
exposing secrets on wire.
2) run obsidian-toaster or a copy of it inside fabric8 online so
we don't expose any secrets.
The obsidian-toaster backend consists of a Forge addon + a JAX-RS resource.
You could deploy this addon in the Fabric8 Forge service and invoke the UI
that Fabric8 renders dynamically based on the command's metadata (it
consumes the same JSON afaik)
Or you could do #2.
Pete and others might have more, but above are the ones I wrote down
while being on bluejeans to the conversations.
> I hope this helps. Looking forward to this list of requirements and
> to discuss about this anytime.
>  -
>  - https://github.com/obsidian-toaster/generator-backend
>  -
>  - https://github.com/obsidian-toaster/obsidian-addon
> Best Regards,
> *George Gastaldi*
> On Tue, Jan 31, 2017 at 9:27 PM, Andrew Lee Rubinger <alr(a)redhat.com>
>> Hi, all:
>> We have some requests coming down the pike from the Developer Group
>> regards to running Forge as a Service (which is great!).
>> Additionally, I'm suspecting this will soon be very important for us
>> well, as we continue to build out what's currently known as the
>> Generator", using Forge as a backend.
>> I'm hoping the Forge team will kindly advise as to our preparedness
>> running Forge in a multitenant environment. Concerns may include
>> consumption (not running an instance-per-user), security, etc. Have
>> we yet
>> broached this subject specifically in the prototypes I've seen thus
>> using Forge Online?
>> I've requested of the Developer Group a list of requirements they've
>> devised; will send those along here when I have them. In the
>> mind describing where we currently stand?
>> Red Hat Developer Group Architecture
>> forge-dev mailing list
> forge-dev mailing list
forge-dev mailing list