[infinispan-issues] [JBoss JIRA] (ISPN-11010) Server should support config server

[Wolf-Dieter Fink (Jira)]

    [ https://issues.jboss.org/browse/ISPN-11010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819382#comment-13819382 ] 

Wolf-Dieter Fink commented on ISPN-11010:
-----------------------------------------

I would have to load a special tag/branch for a (git) repository.
also getting the basic configuration file (infinispan.xml) from the repository as well.

But it might make sense to override some of the attributes like bind-address to keep the configuration the same for different instances.
>From server.sh -h:
  -b, --bind-address=<address>  Binds the server to a specific address.
  -c, --server-config=<config>  Specifies a server configuration file. Defaults to `infinispan.xml`.
  -g, --cluster-name=<name>     Sets the name of the cluster. Defaults to `cluster`.
  -j, --cluster-stack=<name>    Specifies the JGroups stack for clustering. Defaults to `tcp`.
  -n, --node-name=<name>        Sets the name of this node. Must be unique across the cluster.
  -o, --port-offset=<offset>    Adds a numeric offset to all ports.
  -p, --bind-port=<port>        Binds the server to a specific port. Defaults to `11222`.
  -s, --server-root=<path>      Specifies the root path for the server. Defaults to `server`.
  -D<name>=<value>              Sets a system property to the specified value.

> Server should support config server
> -----------------------------------
>
>                 Key: ISPN-11010
>                 URL: https://issues.jboss.org/browse/ISPN-11010
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Server
>    Affects Versions: 10.1.0.Beta1
>            Reporter: Diego Lovison
>            Priority: Major
>
> As a developer, I would like to store the configurations outside the project.
> A few changes are required before that:
> 1) Server should support all in one config file (xml|yalm)
> The config file should support all configuration available at `server.sh -h`
> Example: *config.yaml*
> {code:yaml}
> bind-address: localhost
> server-config: infinispan.xml
> {code}
> In this case, I am going to start the server with: server.sh --file-config=config.yaml
> 2) In order to have all configuration in one place, as a developer I would like to have the following:
> {code:yaml}
> infinispan:
>   config:
>     server:
>       git:
>          uri: https://github.com/infinispan/config-repo
>          username: foo
>          password: foo123
> bind-address: localhost
> server-config: infinispan.xml
> {code}
> Different authentications should be supported like:
> {code:yaml}
> uri: git at gitserver.com:infinispan/repo1.git
> ignoreLocalSshSettings: true
> hostKey: myKey
> hostKeyAlgorithm: ssh-rsa
> privateKey: |
>      -----BEGIN RSA PRIVATE KEY-----
>      bLaH
>      -----END RSA PRIVATE KEY-----
> {code}
> It allows the team have a centralised configuration files with formal approval (aka PR).



--
This message was sent by Atlassian Jira
(v7.13.8#713008)