On Sat, Apr 25, 2015 at 08:18AM, Dmitriy Setrakyan wrote:
> On Fri, Apr 24, 2015 at 9:56 PM, Konstantin Boudnik <[email protected]> wrote:
> 
> > Sounds real good! A question though: when you say 'several docker files' do
> > you refer to Dockerfile(s) or actual images? As for AIM configuration: all
> > required in this case is essentially an Ignite configuration file, right?
> >
> 
> I thought that Docker files would be sufficient to deploy in any cloud
> environment. We can also generate configuration files in addition to the
> docker files as well.

Yeah, docker should work as a deployment media. But I am still unclear: are
you proposing to generate Dockerfiles or the container images? The later might
be time consuming and tricky in terms of management, etc. Perhaps just giving
the Dockerfiles would suffice, don't you think?

Cos

> > On Fri, Apr 24, 2015 at 05:52PM, Nikita Ivanov wrote:
> > > 100% great idea. Additionally to docker files, how about auto-configuring
> > > AIMs with these settings?
> > >
> > > --
> > > Nikita Ivanov
> > >
> > >
> > > On Fri, Apr 24, 2015 at 4:34 PM, Dmitriy Setrakyan <
> > [email protected]>
> > > wrote:
> > >
> > > > Hello everyone,
> > > >
> > > > I have an idea to simplify Ignite configuration via several web-based
> > > > wizards which will allow to configure Ignite with a few button clicks.
> > > >
> > > > For example, you should be able to specify all cache configuration
> > > > properties, all persistence properties, streaming, etc. through a very
> > > > intuitive UI interface. At the end of the process, we could provide
> > several
> > > > docker files which can be easily deployed in any environment.
> > > >
> > > > These wizards can reside as a separate web module under Ignite repo.
> > > >
> > > > Let this thread be the start of the discussion.
> > > >
> > > > Thoughts?
> > > >
> > > > D.
> > > >
> >

Attachment: signature.asc
Description: Digital signature

Reply via email to