[jira] [Commented] (IGNITE-13453) Docker: Change run.sh to call java directly
[
https://issues.apache.org/jira/browse/IGNITE-13453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198411#comment-17198411
]
Ilya Murchenko commented on IGNITE-13453:
-
[~alex_pl] Aleksey, now we are using direct java call to start Ignite node in
docker container. In the current implementation we are not using any "sh"
scripts like ingite.sh or parseargs.sh, if you need to pass any variables from
pasreargs.sh script (INTERACTIVE="1", NOJMX="1", etc.) you can pass it directly
to JVM_OPTS
> Docker: Change run.sh to call java directly
> ---
>
> Key: IGNITE-13453
> URL: https://issues.apache.org/jira/browse/IGNITE-13453
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.8.1
>Reporter: Alexandr Shapkin
>Assignee: Ilya Murchenko
>Priority: Critical
> Fix For: 2.10
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> ignite.sh is cumbersome in Docker as it creates the hassle with signals not
> being propagated but adds little value as most of what ignite.sh discovers
> about the system is known beforehand for our Docker images.
> Let's replace ignite.sh call with direct java invocation.
> {code:bash}
> #!/bin/bash
> #
> # Licensed to the Apache Software Foundation (ASF) under one or more
> # contributor license agreements. See the NOTICE file distributed with
> # this work for additional information regarding copyright ownership.
> # The ASF licenses this file to You under the Apache License, Version 2.0
> # (the "License"); you may not use this file except in compliance with
> # the License. You may obtain a copy of the License at
> #
> # http://www.apache.org/licenses/LICENSE-2.0
> #
> # Unless required by applicable law or agreed to in writing, software
> # distributed under the License is distributed on an "AS IS" BASIS,
> # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> # See the License for the specific language governing permissions and
> # limitations under the License.
> #
> source "${IGNITE_HOME}"/bin/include/functions.sh
> #
> # Discover path to Java executable and check it's version.
> #
> checkJava
> #
> # Set IGNITE_LIBS.
> #
> source "${IGNITE_HOME}"/bin/include/setenv.sh
> CP="${IGNITE_LIBS}"
> DEFAULT_CONFIG=config/default-config.xml
> #
> # Add optional libs to classpath
> #
> if [ -n "${OPTION_LIBS}" ]; then
> IFS=, LIBS_LIST=("$(tr -d '[:space:]' <<< ${OPTION_LIBS})")
> for lib in ${LIBS_LIST[@]}; do
> LIBS=$(JARS=("${IGNITE_HOME}/libs/optional/${lib}"/*); IFS=:; echo
> "${JARS[*]}")
> if [ -z "${USER_LIBS}" ]; then
> export USER_LIBS="${LIBS}"
> else
> export USER_LIBS="${USER_LIBS}:${LIBS}"
> fi
> done
> fi
> #
> # Add external libs to classpath
> #
> if [ -n "${EXTERNAL_LIBS}" ]; then
> IFS=, LIBS_LIST=("${EXTERNAL_LIBS}")
> for lib in "${LIBS_LIST[@]}"; do
> echo "${lib}" >> "${IGNITE_HOME}"/work/external_libs
> done
> wget --content-disposition -i "${IGNITE_HOME}"/work/external_libs -P
> "${IGNITE_HOME}"/libs/external
> rm "${IGNITE_HOME}"/work/external_libs
> fi
> #
> # Define classpath
> #
> if [ "${USER_LIBS:-}" != "" ]; then
> IGNITE_LIBS=${USER_LIBS:-}:${IGNITE_LIBS}
> fi
> CP="${IGNITE_LIBS}"
> unset IFS
> #
> # Define default Java options
> #
> if [ -z "${JVM_OPTS}" ] ; then
> JVM_OPTS="-Xms1g -Xmx1g -server -XX:MaxMetaspaceSize=256m"
> fi
> #
> # Add Java extra option
> #
> if [ "${version}" -eq 8 ] ; then
> JVM_OPTS="\
> -XX:+AggressiveOpts \
> ${JVM_OPTS}"
> elif [ "${version}" -gt 8 ] && [ "${version}" -lt 11 ]; then
> JVM_OPTS="\
> -XX:+AggressiveOpts \
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --illegal-access=permit \
> --add-modules=java.xml.bind \
> ${JVM_OPTS}"
> elif [ "${version}" -ge 11 ] ; then
> JVM_OPTS="\
> --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
> --add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
> --add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
> --add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
>
> --add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
> --add-opens=jdk.management/com.sun.management.internal=ALL-UNNAMED \
> --illegal-access=permit \
> ${JVM_OPTS}"
> fi
> DIGNITE_QUIET=$(printenv JVM_OPTS | grep -o 'IGNITE_QUIET=[^ ,]\+' | cut -d
> "=" -f 2)
> if [ "${IGNITE_QUIET}"
[jira] [Resolved] (IGNITE-13319) Docker: trim whitespaces in the OPTION_LIBS parameter
[ https://issues.apache.org/jira/browse/IGNITE-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko resolved IGNITE-13319. - Resolution: Duplicate Fixed in the linked issue. > Docker: trim whitespaces in the OPTION_LIBS parameter > - > > Key: IGNITE-13319 > URL: https://issues.apache.org/jira/browse/IGNITE-13319 > Project: Ignite > Issue Type: Bug >Reporter: Peter Ivanov >Assignee: Ilya Murchenko >Priority: Major > > When you list several libraries in the OPTION_LIB parameter, you have to > follow this format “ignite-aws,ignite-camel” with no whitespaces between the > names. > If anybody puts a space before the ignite-camel like this “ignite-aws, > ignite-camel” then the second library won’t be added to the classpath. > We need to trim all the whitespaces in the OPTION_LIB before passing the libs > to the launch script. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13319) Docker: trim whitespaces in the OPTION_LIBS parameter
[ https://issues.apache.org/jira/browse/IGNITE-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko reassigned IGNITE-13319: --- Assignee: Ilya Murchenko > Docker: trim whitespaces in the OPTION_LIBS parameter > - > > Key: IGNITE-13319 > URL: https://issues.apache.org/jira/browse/IGNITE-13319 > Project: Ignite > Issue Type: Bug >Reporter: Peter Ivanov >Assignee: Ilya Murchenko >Priority: Major > > When you list several libraries in the OPTION_LIB parameter, you have to > follow this format “ignite-aws,ignite-camel” with no whitespaces between the > names. > If anybody puts a space before the ignite-camel like this “ignite-aws, > ignite-camel” then the second library won’t be added to the classpath. > We need to trim all the whitespaces in the OPTION_LIB before passing the libs > to the launch script. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-9564) Ignite K8 service and sticky session with AWS K8 deployments
[ https://issues.apache.org/jira/browse/IGNITE-9564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16948473#comment-16948473 ] Ilya Murchenko edited comment on IGNITE-9564 at 10/10/19 11:36 AM: --- Hello [~mmuzaf] As I can see AWS Application Load Balancer and Network Load Balancer currently supports sessionAffinity. I think we should create an instruction how to run Ignite cluster on Kubernetes on AWS EC2, but it can be moved on the next release. was (Author: imurchenko): Hello [~mmuzaf] As I can see AWS Application Load Balancer and Network Load Balancer currently supports sessionAffinity. I think we should create an instruction how to run Ignite cluster on Kubernetes on AWS EC2, but it can be done on the next release. > Ignite K8 service and sticky session with AWS K8 deployments > > > Key: IGNITE-9564 > URL: https://issues.apache.org/jira/browse/IGNITE-9564 > Project: Ignite > Issue Type: Task >Reporter: Denis A. Magda >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.8 > > > _sessionAffinity_ parameter is not supported by AWS Kubernetes which causes > the failure of the standard Ignite service deployment: > http://apache-ignite-users.70518.x6.nabble.com/Error-installing-Ignite-on-K8s-td23999.html > See how Ignite service configuration have to be updated considering sticky > session capabilities of AWS: > https://aws.amazon.com/elasticloadbalancing/details/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9564) Ignite K8 service and sticky session with AWS K8 deployments
[ https://issues.apache.org/jira/browse/IGNITE-9564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16948473#comment-16948473 ] Ilya Murchenko commented on IGNITE-9564: Hello [~mmuzaf] As I can see AWS Application Load Balancer and Network Load Balancer currently supports sessionAffinity. I think we should create an instruction how to run Ignite cluster on Kubernetes on AWS EC2, but it can be done on the next release. > Ignite K8 service and sticky session with AWS K8 deployments > > > Key: IGNITE-9564 > URL: https://issues.apache.org/jira/browse/IGNITE-9564 > Project: Ignite > Issue Type: Task >Reporter: Denis A. Magda >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.8 > > > _sessionAffinity_ parameter is not supported by AWS Kubernetes which causes > the failure of the standard Ignite service deployment: > http://apache-ignite-users.70518.x6.nabble.com/Error-installing-Ignite-on-K8s-td23999.html > See how Ignite service configuration have to be updated considering sticky > session capabilities of AWS: > https://aws.amazon.com/elasticloadbalancing/details/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12007) Latest "apacheignite/web-console-backend" docker image is broken
[
https://issues.apache.org/jira/browse/IGNITE-12007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16892505#comment-16892505
]
Ilya Murchenko commented on IGNITE-12007:
-
[~dpavlov] as I can see - Dockerfile for Web Console Backend image is broken in
Apache/Ignite repository. I think we should fix at least Dockerfile.
> Latest "apacheignite/web-console-backend" docker image is broken
>
>
> Key: IGNITE-12007
> URL: https://issues.apache.org/jira/browse/IGNITE-12007
> Project: Ignite
> Issue Type: Bug
> Components: UI
>Affects Versions: 2.7
>Reporter: Igor Belyakov
>Priority: Critical
>
> It's not possible to run docker container by using the latest version of
> "apacheignite/web-console-backend" image.
> Next error happens on the start:
> {code:java}
> npm ERR! A complete log of this run can be found in:
> npm ERR! /root/.npm/_logs/2019-07-23T14_24_40_353Z-debug.log
> npm ERR! path /opt/web-console/package.json
> npm ERR! code ENOENT
> npm ERR! errno -2
> npm ERR! syscall open
> npm ERR! enoent ENOENT: no such file or directory, open
> '/opt/web-console/package.json'
> npm ERR! enoent This is related to npm not being able to find a file.
> npm ERR! enoent{code}
> How to reproduce:
> Run container by using docker-compose as described here:
> [https://hub.docker.com/r/apacheignite/web-console-backend]
>
> Seems like it was broken by the next commit:
> [https://github.com/apache/ignite/commit/4c295f8f468ddfce458948c17c13b1748b13e918#diff-ec0d595d738c4207e08ce210624e902aR22]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-11813) Remove deprecated parameters from Kuberenetes configuration templates.
Ilya Murchenko created IGNITE-11813: --- Summary: Remove deprecated parameters from Kuberenetes configuration templates. Key: IGNITE-11813 URL: https://issues.apache.org/jira/browse/IGNITE-11813 Project: Ignite Issue Type: Task Components: examples Reporter: Ilya Murchenko Assignee: Ilya Murchenko Need to remove "zones" parameter from Kuberenetes configuration templates for Storage Classes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10668) Web Console: Prepare sample NGINX config with two way ssl authentication support
[ https://issues.apache.org/jira/browse/IGNITE-10668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko reassigned IGNITE-10668: --- Assignee: Alexey Kuznetsov (was: Ilya Murchenko) > Web Console: Prepare sample NGINX config with two way ssl authentication > support > > > Key: IGNITE-10668 > URL: https://issues.apache.org/jira/browse/IGNITE-10668 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > Attachments: web-console-2-way-ssl.conf, web-console-ssl.conf > > > We need a sample config with SSL and ciphers + instruction how to pass to > "docker run". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10668) Web Console: Prepare sample NGINX config with two way ssl authentication support
[ https://issues.apache.org/jira/browse/IGNITE-10668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko updated IGNITE-10668: Attachment: web-console-ssl.conf web-console-2-way-ssl.conf > Web Console: Prepare sample NGINX config with two way ssl authentication > support > > > Key: IGNITE-10668 > URL: https://issues.apache.org/jira/browse/IGNITE-10668 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.8 > > Attachments: web-console-2-way-ssl.conf, web-console-ssl.conf > > > We need a sample config with SSL and ciphers + instruction how to pass to > "docker run". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10668) Web Console: Prepare sample NGINX config with two way ssl authentication support
[
https://issues.apache.org/jira/browse/IGNITE-10668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721469#comment-16721469
]
Ilya Murchenko commented on IGNITE-10668:
-
To enable SSL support for Web Console you should set "ssl_certificate" and
"ssl_certificate_key" options to NGINX web-console.conf configuration file
(server block):
{code:bash}
server {
listen 80;
listen 443 ssl;
server_name _;
set $ignite_console_dir /opt/static;
ssl_certificate /path/to/ssl/server.crt;
ssl_certificate_key /path/to/ssl/server.key;
root $ignite_console_dir;
{code}
To enable two-way SSL support for Web Console you should set
"ssl_client_certificate" and "ssl_verify_client" options in addition to SSL
configuration above to NGINX web-console.conf configuration file (server block):
{code:bash}
server {
listen 80;
listen 443 ssl;
server_name _;
set $ignite_console_dir /opt/static;
ssl_certificate /path/to/ssl/server.crt;
ssl_certificate_key /path/to/ssl/server.key;
ssl_client_certificate /path/to/ssl/ca.crt;
ssl_verify_client on;
root $ignite_console_dir;
{code}
To enable SSL/two-way SSL support for Web Console docker container you should
first prepare server certificates, server keys and web-console.conf
configuration file locally.
To run Web Console Docker image with these configuration files and certificates
please use the following command:
{code:bash}
docker run -v /path/to/ssl:/etc/nginx/ssl -v
/path/to/web-console.conf:/etc/nginx/web-console.conf -p 80:80 -p 443:443
apacheignite/web-console-frontend:latest
{code}
> Web Console: Prepare sample NGINX config with two way ssl authentication
> support
>
>
> Key: IGNITE-10668
> URL: https://issues.apache.org/jira/browse/IGNITE-10668
> Project: Ignite
> Issue Type: Improvement
> Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.8
>
>
> We need a sample config with SSL and ciphers + instruction how to pass to
> "docker run".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10668) Web Console: Prepare sample NGINX config with two way ssl authentication support
[ https://issues.apache.org/jira/browse/IGNITE-10668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko updated IGNITE-10668: Summary: Web Console: Prepare sample NGINX config with two way ssl authentication support (was: Web Console: Prepare sample NGINX config with SSL and ciphers support) > Web Console: Prepare sample NGINX config with two way ssl authentication > support > > > Key: IGNITE-10668 > URL: https://issues.apache.org/jira/browse/IGNITE-10668 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexey Kuznetsov >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.8 > > > We need a sample config with SSL and ciphers + instruction how to pass to > "docker run". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10121) Web console: Create documentation how to run Web agent as Docker image
[
https://issues.apache.org/jira/browse/IGNITE-10121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718952#comment-16718952
]
Ilya Murchenko commented on IGNITE-10121:
-
To run web agent as a Docker container you should specify the following
parameters for docker run command:
-v
local_path_to_folder_with_jdbc_drivers:/opt/ignite/ignite-web-agent/jdbc-drivers
-e "DRIVER_FOLDER=./jdbc-drivers" - Path to folder with JDBC drivers, default:
./jdbc-drivers
-e "NODE_URI=http://localhost:8080 " - Comma-separated list of URIs for
connect to Ignite REST server, default value: http://localhost:8080/
-e "SERVER_URI=http://localhost:3000"; - URI for connect to Ignite Web Console
via web-socket protocol, default value: http://localhost:3000/
-e "TOKENS=" - Comma-separated list of user's security tokens.
For example:
{code:bash}
docker run -d -v jdbc-drivers:/opt/ignite/ignite-web-agent/jdbc-drivers -e
"DRIVER_FOLDER=./jdbc-drivers" -e "NODE_URI=http://localhost:8080 " -e
"SERVER_URI=http://localhost:3000"; -e "TOKENS=tokens"
apacheignite/web-agent:latest
{code}
> Web console: Create documentation how to run Web agent as Docker image
> --
>
> Key: IGNITE-10121
> URL: https://issues.apache.org/jira/browse/IGNITE-10121
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Vasiliy Sisko
>Assignee: Ilya Murchenko
>Priority: Major
>
> Especially specify ho configure path to external folder with jdbc driver.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10121) Web console: Create documentation how to run Web agent as Docker image
[ https://issues.apache.org/jira/browse/IGNITE-10121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko reassigned IGNITE-10121: --- Assignee: Vasiliy Sisko (was: Ilya Murchenko) > Web console: Create documentation how to run Web agent as Docker image > -- > > Key: IGNITE-10121 > URL: https://issues.apache.org/jira/browse/IGNITE-10121 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > > Especially specify ho configure path to external folder with jdbc driver. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10373) Web console: we need to fix docker-compose.yml
[
https://issues.apache.org/jira/browse/IGNITE-10373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Murchenko reassigned IGNITE-10373:
---
Assignee: Pavel Konstantinov (was: Ilya Murchenko)
> Web console: we need to fix docker-compose.yml
> --
>
> Key: IGNITE-10373
> URL: https://issues.apache.org/jira/browse/IGNITE-10373
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.8
>
> Attachments: docker-compose.yml
>
>
> It located here 'modules/web-console/docker/compose' and it doesn't work
> {code}
> Version in "./docker-compose.yml" is invalid - it should be a string.
> {code}
> after I've fixed that I've got the next one
> {code}
> Version in "./docker-compose.yml" is invalid. You might be seeing this error
> because you're using the wrong Compose file version. Either specify a
> supported version (e.g "2.2" or "3.3") and place your service definitions
> under the `services` key, or omit the `version` key and place your service
> definitions at the root of the file to use version 1.
> {code}
> after I've fixed that I've got the next one
> {code}
> ERROR: Service 'frontend' depends on service 'testenv' which is undefined.
> {code}
> So, please make it workable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10373) Web console: we need to fix docker-compose.yml
[
https://issues.apache.org/jira/browse/IGNITE-10373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698553#comment-16698553
]
Ilya Murchenko commented on IGNITE-10373:
-
[~pkonstantinov]
Looks good to me, thank you!
> Web console: we need to fix docker-compose.yml
> --
>
> Key: IGNITE-10373
> URL: https://issues.apache.org/jira/browse/IGNITE-10373
> Project: Ignite
> Issue Type: Bug
> Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.8
>
> Attachments: docker-compose.yml
>
>
> It located here 'modules/web-console/docker/compose' and it doesn't work
> {code}
> Version in "./docker-compose.yml" is invalid - it should be a string.
> {code}
> after I've fixed that I've got the next one
> {code}
> Version in "./docker-compose.yml" is invalid. You might be seeing this error
> because you're using the wrong Compose file version. Either specify a
> supported version (e.g "2.2" or "3.3") and place your service definitions
> under the `services` key, or omit the `version` key and place your service
> definitions at the root of the file to use version 1.
> {code}
> after I've fixed that I've got the next one
> {code}
> ERROR: Service 'frontend' depends on service 'testenv' which is undefined.
> {code}
> So, please make it workable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10148) Add aws s3 and elb configs to benchmarks/config
[ https://issues.apache.org/jira/browse/IGNITE-10148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16680927#comment-16680927 ] Ilya Murchenko commented on IGNITE-10148: - [~ustas] looks good to me. Thank you! > Add aws s3 and elb configs to benchmarks/config > > > Key: IGNITE-10148 > URL: https://issues.apache.org/jira/browse/IGNITE-10148 > Project: Ignite > Issue Type: Bug >Reporter: Ilya Suntsov >Assignee: Ilya Suntsov >Priority: Major > > Add to yardstick: > * S3 discovery config > * ELB discovery config -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7926) Web console: demo faled to start under java >= 9
[ https://issues.apache.org/jira/browse/IGNITE-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669872#comment-16669872 ] Ilya Murchenko commented on IGNITE-7926: [~anovikov] looks good to me. > Web console: demo faled to start under java >= 9 > > > Key: IGNITE-7926 > URL: https://issues.apache.org/jira/browse/IGNITE-7926 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.4 >Reporter: Pavel Konstantinov >Assignee: Ilya Murchenko >Priority: Minor > Fix For: 2.7 > > > We need to add support for Java 9 to web console demo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9010) Move web-console build to dedicated root directory
[
https://issues.apache.org/jira/browse/IGNITE-9010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660859#comment-16660859
]
Ilya Murchenko commented on IGNITE-9010:
Hi [~vveider], I've checked your PR and I have a few comments:
# There is a typo in line 49 [1], the correct key for apt command is
"--no-install-recommends"
# "node:8-slim" image is using the old version of Debian jessie as a **base
image and doesn't have "apt clean" command [2]. It should be changed by
"apt-get clean" command.
[1]
[https://github.com/apache/ignite/pull/4528/commits/761e746e0c4e3d1c01ec6481311d20de14d87c02#diff-f006d67e8df98048b58850d4957a65afR49]
[2]
https://github.com/apache/ignite/pull/4528/commits/761e746e0c4e3d1c01ec6481311d20de14d87c02#diff-f006d67e8df98048b58850d4957a65afR53
> Move web-console build to dedicated root directory
> --
>
> Key: IGNITE-9010
> URL: https://issues.apache.org/jira/browse/IGNITE-9010
> Project: Ignite
> Issue Type: Task
>Reporter: Peter Ivanov
>Assignee: Ilya Murchenko
>Priority: Major
>
> # Move web-console docker image build (web-console, frontend and backend) to
> {{/docker}} directory.
> # Prepare README.md file in root of {{/docker}} directory with instructions
> on how to build corresponding image. Remove obsolete per-image README's from
> Dockerfile directories.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9089) Web Agent not starting in docker container.
[
https://issues.apache.org/jira/browse/IGNITE-9089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558278#comment-16558278
]
Ilya Murchenko commented on IGNITE-9089:
I've tested this image on docker/kubernetes cluster. Now Web Agent can start
and establish a session to Web Console.
> Web Agent not starting in docker container.
> ---
>
> Key: IGNITE-9089
> URL: https://issues.apache.org/jira/browse/IGNITE-9089
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Ilya Murchenko
>Assignee: Peter Ivanov
>Priority: Minor
> Fix For: 2.7
>
>
> After a successful build from the Dockerfile in the [Github
> repository|https://github.com/apache/ignite/blob/master/docker/web-agent/Dockerfile]
> Web Agent application not starting in docker container with the following
> error:
>
> {code:java}
> /bin/sh: ignite-web-agent.sh: not found
> {code}
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9089) Web Agent not starting in docker container.
Ilya Murchenko created IGNITE-9089:
--
Summary: Web Agent not starting in docker container.
Key: IGNITE-9089
URL: https://issues.apache.org/jira/browse/IGNITE-9089
Project: Ignite
Issue Type: Bug
Affects Versions: 2.6
Reporter: Ilya Murchenko
Assignee: Peter Ivanov
Fix For: 2.7
After a successful build from the Dockerfile in the [Github
repository|https://github.com/apache/ignite/blob/master/docker/web-agent/Dockerfile]
Web Agent application not starting in docker container with the following
error:
{code:java}
/bin/sh: ignite-web-agent.sh: not found
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8994) Configuring dedicated volumes for WAL and data with Kuberenetes
[ https://issues.apache.org/jira/browse/IGNITE-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko updated IGNITE-8994: --- Attachment: yaml.zip > Configuring dedicated volumes for WAL and data with Kuberenetes > --- > > Key: IGNITE-8994 > URL: https://issues.apache.org/jira/browse/IGNITE-8994 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.7 > > Attachments: yaml.zip > > > The current StatefulSet documentation request only one persistent volume for > both WAL and data/index files: > https://apacheignite.readme.io/docs/stateful-deployment#section-statefulset-deployment > However, according to Ignite performance guide the WAL has to be located on a > dedicated volume: > https://apacheignite.readme.io/docs/durable-memory-tuning#section-separate-disk-device-for-wal > Provide StatefulSet configuration that shows how to request separate volumes > for the WAL and data/index files. If needed, provide YAML configs for > StorageClass and volume claims. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8994) Configuring dedicated volumes for WAL and data with Kuberenetes
[ https://issues.apache.org/jira/browse/IGNITE-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko updated IGNITE-8994: --- Attachment: (was: yaml.zip) > Configuring dedicated volumes for WAL and data with Kuberenetes > --- > > Key: IGNITE-8994 > URL: https://issues.apache.org/jira/browse/IGNITE-8994 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.7 > > > The current StatefulSet documentation request only one persistent volume for > both WAL and data/index files: > https://apacheignite.readme.io/docs/stateful-deployment#section-statefulset-deployment > However, according to Ignite performance guide the WAL has to be located on a > dedicated volume: > https://apacheignite.readme.io/docs/durable-memory-tuning#section-separate-disk-device-for-wal > Provide StatefulSet configuration that shows how to request separate volumes > for the WAL and data/index files. If needed, provide YAML configs for > StorageClass and volume claims. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8923) Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
[
https://issues.apache.org/jira/browse/IGNITE-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543024#comment-16543024
]
Ilya Murchenko edited comment on IGNITE-8923 at 7/16/18 2:32 PM:
-
Added a step by step guide for Google Kubernetes Engine Deployment in Markdown
format.
Also please update
[example-kube.xml|https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube.xml]
from example-kube.xml file in attachments.
was (Author: imurchenko):
Added step by step guide for Google Kubernetes Engine Deployment in Markdown
format.
Also please update
[example-kube.xml|https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube.xml]
from example-kube.xml file in attachments.
> Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
>
>
> Key: IGNITE-8923
> URL: https://issues.apache.org/jira/browse/IGNITE-8923
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Reporter: Roman Guseinov
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.7
>
> Attachments: config.zip, example-kube.xml,
> google_cloud_engine_deployment.zip, yaml.zip
>
>
> We have such documentation for Microsoft Azure
> [https://apacheignite.readme.io/docs/microsoft-azure-deployment]
> It would be great to publish the same for GCE.
> Here are steps which I used to deploy cluster (stateless, stateful) and web
> console:
> {code:java}
> ## Start Ignite Cluster
> 1. Grant cluster-admin role to current google user (to allow create roles):
> $ kubectl create clusterrolebinding myname2-cluster-admin-binding \
> --clusterrole=cluster-admin \
> --user=
> 2. Create service account and grant permissions:
> $ kubectl create -f sa.yaml
> $ kubectl create -f role.yaml
> $ kubectl create -f rolebind.yaml
> 3. Create a grid service:
> $ kubectl create -f service.yaml
> 4. Deploy Ignite Cluster:
> $ kubectl create -f grid.yaml
> ## Enable Ignite Persistence
> 5. Deploy Ignite StatefulSet with enabled Persistence (instead of step 4).
> $ kubectl create -f grid-pds.yaml
> 6. Connect to the Ignite node and activate cluster:
> $ kubectl exec -it ignite-cluster-0 -- /bin/bash
> $ cd /opt/ignite/apache-ignite-*
> $ ./bin/control.sh --activate
> ## Deploy Web Console:
> 7. Create a volume to keep web console data:
> $ kubectl create -f console-volume.yaml
> 8. Create load balancer to expose HTTP port and make web console available by
> service DNS-name (web-console.default.svc.cluster.local) inside Kuberntes
> enviroment:
> $ kubectl create -f console-service.yaml
> 9. Deploy Web Console:
> $ kubectl create -f console.yaml
> 10. Check external IP:
> $ kubectl get service web-console
> 11. Open Web Console in a web browser and Sign Up.
> 12. Move to User Profile page (Settings > Profile) and copy security token.
> 13. Insert security token into web-agent.yaml (TOKENS environment variable).
> 14. Deploy Web Agent:
> $ kubectl create -f web-agent.yaml
> {code}
> YAML and configs are attached.
> Creating a public Docker-image for Web Agent in progress:
> https://issues.apache.org/jira/browse/IGNITE-8526
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-8993) Configuring sticky LoadBalancer for Ignite Service with Kubernetes
[
https://issues.apache.org/jira/browse/IGNITE-8993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545247#comment-16545247
]
Ilya Murchenko edited comment on IGNITE-8993 at 7/16/18 2:24 PM:
-
To enable session affinity we need to modify the Ignite Load Balancer Service:
{code:java}
#Add "sessionAffinity: ClientIP" property to "spec" section
spec:
type: LoadBalancer
...
sessionAffinity: ClientIP
{code}
{code:java}
1. Deploy Ignite Load Balancer Service
$ kubectl create -f ignite-statefulset.yaml
{code}
ignite-service.yaml configuration file is attached.
was (Author: imurchenko):
To enable session affinity we need to modify the Ignite load balancer service:
{code:java}
spec:
type: LoadBalancer
...
sessionAffinity: ClientIP
{code}
Configuration file (YAML) is attached.
> Configuring sticky LoadBalancer for Ignite Service with Kubernetes
> --
>
> Key: IGNITE-8993
> URL: https://issues.apache.org/jira/browse/IGNITE-8993
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Denis Magda
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.7
>
> Attachments: ignite-service.yaml
>
>
> Ignite service used for Ignite pods auto-discovery and access to the cluster
> from remote applications is deployed as LoadBalancer:
> https://apacheignite.readme.io/docs/ignite-service
> This might lead to problems when a stateful session is needed between an app
> and the cluster. For instance, Ignite JDBC driver preserves the state of an
> opened connection meaning that once LoadBalancer connects the driver to an
> Ignite pod, all the queries have to be redirected to that Ignite pod only
> (unless the pod is down).
> We need to show how to configure a sticky LoadBalancer that will assign a
> client connection to a specific pod and won't change it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8993) Configuring sticky LoadBalancer for Ignite Service with Kubernetes
[
https://issues.apache.org/jira/browse/IGNITE-8993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545247#comment-16545247
]
Ilya Murchenko commented on IGNITE-8993:
To enable session affinity we need to modify the Ignite load balancer service:
{code:java}
spec:
type: LoadBalancer
...
sessionAffinity: ClientIP
{code}
Configuration file (YAML) is attached.
> Configuring sticky LoadBalancer for Ignite Service with Kubernetes
> --
>
> Key: IGNITE-8993
> URL: https://issues.apache.org/jira/browse/IGNITE-8993
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Denis Magda
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.7
>
> Attachments: ignite-service.yaml
>
>
> Ignite service used for Ignite pods auto-discovery and access to the cluster
> from remote applications is deployed as LoadBalancer:
> https://apacheignite.readme.io/docs/ignite-service
> This might lead to problems when a stateful session is needed between an app
> and the cluster. For instance, Ignite JDBC driver preserves the state of an
> opened connection meaning that once LoadBalancer connects the driver to an
> Ignite pod, all the queries have to be redirected to that Ignite pod only
> (unless the pod is down).
> We need to show how to configure a sticky LoadBalancer that will assign a
> client connection to a specific pod and won't change it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8993) Configuring sticky LoadBalancer for Ignite Service with Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-8993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko updated IGNITE-8993: --- Attachment: ignite-service.yaml > Configuring sticky LoadBalancer for Ignite Service with Kubernetes > -- > > Key: IGNITE-8993 > URL: https://issues.apache.org/jira/browse/IGNITE-8993 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.7 > > Attachments: ignite-service.yaml > > > Ignite service used for Ignite pods auto-discovery and access to the cluster > from remote applications is deployed as LoadBalancer: > https://apacheignite.readme.io/docs/ignite-service > This might lead to problems when a stateful session is needed between an app > and the cluster. For instance, Ignite JDBC driver preserves the state of an > opened connection meaning that once LoadBalancer connects the driver to an > Ignite pod, all the queries have to be redirected to that Ignite pod only > (unless the pod is down). > We need to show how to configure a sticky LoadBalancer that will assign a > client connection to a specific pod and won't change it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8994) Configuring dedicated volumes for WAL and data with Kuberenetes
[
https://issues.apache.org/jira/browse/IGNITE-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545239#comment-16545239
]
Ilya Murchenko commented on IGNITE-8994:
Here are steps which I used to deploy Ignite StatefulSet with dedicated volumes
for WAL and Data:
{code:java}
##Create Ignite StatefulSet deployment with dedicated volumes for WAL and Data
1. Specify a Volume Type in storage-class-wal-.yaml and
storage-class-persistence-.yaml configuration templates.
2. Create a StorageClass for AWS or GKE
#AWS:
$ kubectl create -f storage-class-wal-aws.yaml
#GKE:
$ kubectl create -f storage-class-wal-gke.yaml
3. Create a PersistentVolumeClaim for AWS or GKE
#AWS:
$ kubectl create -f storage-class-persistence-aws.yaml
#GKE:
$ kubectl create -f storage-class-persistence-gke.yaml
4. Deploy Ignite StatefulSet with dedicated volumes for WAL and Data
$ kubectl create -f ignite-statefulset.yaml
{code}
Configuration templates (YAML) are attached.
> Configuring dedicated volumes for WAL and data with Kuberenetes
> ---
>
> Key: IGNITE-8994
> URL: https://issues.apache.org/jira/browse/IGNITE-8994
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Denis Magda
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.7
>
> Attachments: yaml.zip
>
>
> The current StatefulSet documentation request only one persistent volume for
> both WAL and data/index files:
> https://apacheignite.readme.io/docs/stateful-deployment#section-statefulset-deployment
> However, according to Ignite performance guide the WAL has to be located on a
> dedicated volume:
> https://apacheignite.readme.io/docs/durable-memory-tuning#section-separate-disk-device-for-wal
> Provide StatefulSet configuration that shows how to request separate volumes
> for the WAL and data/index files. If needed, provide YAML configs for
> StorageClass and volume claims.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8994) Configuring dedicated volumes for WAL and data with Kuberenetes
[ https://issues.apache.org/jira/browse/IGNITE-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko updated IGNITE-8994: --- Attachment: (was: yaml.zip) > Configuring dedicated volumes for WAL and data with Kuberenetes > --- > > Key: IGNITE-8994 > URL: https://issues.apache.org/jira/browse/IGNITE-8994 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.7 > > Attachments: yaml.zip > > > The current StatefulSet documentation request only one persistent volume for > both WAL and data/index files: > https://apacheignite.readme.io/docs/stateful-deployment#section-statefulset-deployment > However, according to Ignite performance guide the WAL has to be located on a > dedicated volume: > https://apacheignite.readme.io/docs/durable-memory-tuning#section-separate-disk-device-for-wal > Provide StatefulSet configuration that shows how to request separate volumes > for the WAL and data/index files. If needed, provide YAML configs for > StorageClass and volume claims. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8994) Configuring dedicated volumes for WAL and data with Kuberenetes
[ https://issues.apache.org/jira/browse/IGNITE-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko updated IGNITE-8994: --- Attachment: yaml.zip > Configuring dedicated volumes for WAL and data with Kuberenetes > --- > > Key: IGNITE-8994 > URL: https://issues.apache.org/jira/browse/IGNITE-8994 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.7 > > Attachments: yaml.zip > > > The current StatefulSet documentation request only one persistent volume for > both WAL and data/index files: > https://apacheignite.readme.io/docs/stateful-deployment#section-statefulset-deployment > However, according to Ignite performance guide the WAL has to be located on a > dedicated volume: > https://apacheignite.readme.io/docs/durable-memory-tuning#section-separate-disk-device-for-wal > Provide StatefulSet configuration that shows how to request separate volumes > for the WAL and data/index files. If needed, provide YAML configs for > StorageClass and volume claims. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8994) Configuring dedicated volumes for WAL and data with Kuberenetes
[ https://issues.apache.org/jira/browse/IGNITE-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko updated IGNITE-8994: --- Attachment: yaml.zip > Configuring dedicated volumes for WAL and data with Kuberenetes > --- > > Key: IGNITE-8994 > URL: https://issues.apache.org/jira/browse/IGNITE-8994 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.7 > > Attachments: yaml.zip > > > The current StatefulSet documentation request only one persistent volume for > both WAL and data/index files: > https://apacheignite.readme.io/docs/stateful-deployment#section-statefulset-deployment > However, according to Ignite performance guide the WAL has to be located on a > dedicated volume: > https://apacheignite.readme.io/docs/durable-memory-tuning#section-separate-disk-device-for-wal > Provide StatefulSet configuration that shows how to request separate volumes > for the WAL and data/index files. If needed, provide YAML configs for > StorageClass and volume claims. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8923) Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
[
https://issues.apache.org/jira/browse/IGNITE-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16543024#comment-16543024
]
Ilya Murchenko commented on IGNITE-8923:
Added step by step guide for Google Kubernetes Engine Deployment in Markdown
format.
Also please update
[example-kube.xml|https://raw.githubusercontent.com/apache/ignite/master/modules/kubernetes/config/example-kube.xml]
from example-kube.xml file in attachments.
> Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
>
>
> Key: IGNITE-8923
> URL: https://issues.apache.org/jira/browse/IGNITE-8923
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Reporter: Roman Guseinov
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.7
>
> Attachments: config.zip, example-kube.xml,
> google_cloud_engine_deployment.zip, yaml.zip
>
>
> We have such documentation for Microsoft Azure
> [https://apacheignite.readme.io/docs/microsoft-azure-deployment]
> It would be great to publish the same for GCE.
> Here are steps which I used to deploy cluster (stateless, stateful) and web
> console:
> {code:java}
> ## Start Ignite Cluster
> 1. Grant cluster-admin role to current google user (to allow create roles):
> $ kubectl create clusterrolebinding myname2-cluster-admin-binding \
> --clusterrole=cluster-admin \
> --user=
> 2. Create service account and grant permissions:
> $ kubectl create -f sa.yaml
> $ kubectl create -f role.yaml
> $ kubectl create -f rolebind.yaml
> 3. Create a grid service:
> $ kubectl create -f service.yaml
> 4. Deploy Ignite Cluster:
> $ kubectl create -f grid.yaml
> ## Enable Ignite Persistence
> 5. Deploy Ignite StatefulSet with enabled Persistence (instead of step 4).
> $ kubectl create -f grid-pds.yaml
> 6. Connect to the Ignite node and activate cluster:
> $ kubectl exec -it ignite-cluster-0 -- /bin/bash
> $ cd /opt/ignite/apache-ignite-*
> $ ./bin/control.sh --activate
> ## Deploy Web Console:
> 7. Create a volume to keep web console data:
> $ kubectl create -f console-volume.yaml
> 8. Create load balancer to expose HTTP port and make web console available by
> service DNS-name (web-console.default.svc.cluster.local) inside Kuberntes
> enviroment:
> $ kubectl create -f console-service.yaml
> 9. Deploy Web Console:
> $ kubectl create -f console.yaml
> 10. Check external IP:
> $ kubectl get service web-console
> 11. Open Web Console in a web browser and Sign Up.
> 12. Move to User Profile page (Settings > Profile) and copy security token.
> 13. Insert security token into web-agent.yaml (TOKENS environment variable).
> 14. Deploy Web Agent:
> $ kubectl create -f web-agent.yaml
> {code}
> YAML and configs are attached.
> Creating a public Docker-image for Web Agent in progress:
> https://issues.apache.org/jira/browse/IGNITE-8526
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8923) Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
[
https://issues.apache.org/jira/browse/IGNITE-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Murchenko updated IGNITE-8923:
---
Attachment: google_cloud_engine_deployment.zip
> Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
>
>
> Key: IGNITE-8923
> URL: https://issues.apache.org/jira/browse/IGNITE-8923
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Reporter: Roman Guseinov
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.7
>
> Attachments: config.zip, example-kube.xml,
> google_cloud_engine_deployment.zip, yaml.zip
>
>
> We have such documentation for Microsoft Azure
> [https://apacheignite.readme.io/docs/microsoft-azure-deployment]
> It would be great to publish the same for GCE.
> Here are steps which I used to deploy cluster (stateless, stateful) and web
> console:
> {code:java}
> ## Start Ignite Cluster
> 1. Grant cluster-admin role to current google user (to allow create roles):
> $ kubectl create clusterrolebinding myname2-cluster-admin-binding \
> --clusterrole=cluster-admin \
> --user=
> 2. Create service account and grant permissions:
> $ kubectl create -f sa.yaml
> $ kubectl create -f role.yaml
> $ kubectl create -f rolebind.yaml
> 3. Create a grid service:
> $ kubectl create -f service.yaml
> 4. Deploy Ignite Cluster:
> $ kubectl create -f grid.yaml
> ## Enable Ignite Persistence
> 5. Deploy Ignite StatefulSet with enabled Persistence (instead of step 4).
> $ kubectl create -f grid-pds.yaml
> 6. Connect to the Ignite node and activate cluster:
> $ kubectl exec -it ignite-cluster-0 -- /bin/bash
> $ cd /opt/ignite/apache-ignite-*
> $ ./bin/control.sh --activate
> ## Deploy Web Console:
> 7. Create a volume to keep web console data:
> $ kubectl create -f console-volume.yaml
> 8. Create load balancer to expose HTTP port and make web console available by
> service DNS-name (web-console.default.svc.cluster.local) inside Kuberntes
> enviroment:
> $ kubectl create -f console-service.yaml
> 9. Deploy Web Console:
> $ kubectl create -f console.yaml
> 10. Check external IP:
> $ kubectl get service web-console
> 11. Open Web Console in a web browser and Sign Up.
> 12. Move to User Profile page (Settings > Profile) and copy security token.
> 13. Insert security token into web-agent.yaml (TOKENS environment variable).
> 14. Deploy Web Agent:
> $ kubectl create -f web-agent.yaml
> {code}
> YAML and configs are attached.
> Creating a public Docker-image for Web Agent in progress:
> https://issues.apache.org/jira/browse/IGNITE-8526
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-8923) Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
[
https://issues.apache.org/jira/browse/IGNITE-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Murchenko updated IGNITE-8923:
---
Attachment: example-kube.xml
> Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
>
>
> Key: IGNITE-8923
> URL: https://issues.apache.org/jira/browse/IGNITE-8923
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Reporter: Roman Guseinov
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.7
>
> Attachments: config.zip, example-kube.xml,
> google_cloud_engine_deployment.zip, yaml.zip
>
>
> We have such documentation for Microsoft Azure
> [https://apacheignite.readme.io/docs/microsoft-azure-deployment]
> It would be great to publish the same for GCE.
> Here are steps which I used to deploy cluster (stateless, stateful) and web
> console:
> {code:java}
> ## Start Ignite Cluster
> 1. Grant cluster-admin role to current google user (to allow create roles):
> $ kubectl create clusterrolebinding myname2-cluster-admin-binding \
> --clusterrole=cluster-admin \
> --user=
> 2. Create service account and grant permissions:
> $ kubectl create -f sa.yaml
> $ kubectl create -f role.yaml
> $ kubectl create -f rolebind.yaml
> 3. Create a grid service:
> $ kubectl create -f service.yaml
> 4. Deploy Ignite Cluster:
> $ kubectl create -f grid.yaml
> ## Enable Ignite Persistence
> 5. Deploy Ignite StatefulSet with enabled Persistence (instead of step 4).
> $ kubectl create -f grid-pds.yaml
> 6. Connect to the Ignite node and activate cluster:
> $ kubectl exec -it ignite-cluster-0 -- /bin/bash
> $ cd /opt/ignite/apache-ignite-*
> $ ./bin/control.sh --activate
> ## Deploy Web Console:
> 7. Create a volume to keep web console data:
> $ kubectl create -f console-volume.yaml
> 8. Create load balancer to expose HTTP port and make web console available by
> service DNS-name (web-console.default.svc.cluster.local) inside Kuberntes
> enviroment:
> $ kubectl create -f console-service.yaml
> 9. Deploy Web Console:
> $ kubectl create -f console.yaml
> 10. Check external IP:
> $ kubectl get service web-console
> 11. Open Web Console in a web browser and Sign Up.
> 12. Move to User Profile page (Settings > Profile) and copy security token.
> 13. Insert security token into web-agent.yaml (TOKENS environment variable).
> 14. Deploy Web Agent:
> $ kubectl create -f web-agent.yaml
> {code}
> YAML and configs are attached.
> Creating a public Docker-image for Web Agent in progress:
> https://issues.apache.org/jira/browse/IGNITE-8526
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8994) Configuring dedicated volumes for WAL and data with Kuberenetes
[ https://issues.apache.org/jira/browse/IGNITE-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko reassigned IGNITE-8994: -- Assignee: Ilya Murchenko > Configuring dedicated volumes for WAL and data with Kuberenetes > --- > > Key: IGNITE-8994 > URL: https://issues.apache.org/jira/browse/IGNITE-8994 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.7 > > > The current StatefulSet documentation request only one persistent volume for > both WAL and data/index files: > https://apacheignite.readme.io/docs/stateful-deployment#section-statefulset-deployment > However, according to Ignite performance guide the WAL has to be located on a > dedicated volume: > https://apacheignite.readme.io/docs/durable-memory-tuning#section-separate-disk-device-for-wal > Provide StatefulSet configuration that shows how to request separate volumes > for the WAL and data/index files. If needed, provide YAML configs for > StorageClass and volume claims. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8993) Configuring sticky LoadBalancer for Ignite Service with Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-8993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Murchenko reassigned IGNITE-8993: -- Assignee: Ilya Murchenko > Configuring sticky LoadBalancer for Ignite Service with Kubernetes > -- > > Key: IGNITE-8993 > URL: https://issues.apache.org/jira/browse/IGNITE-8993 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.7 > > > Ignite service used for Ignite pods auto-discovery and access to the cluster > from remote applications is deployed as LoadBalancer: > https://apacheignite.readme.io/docs/ignite-service > This might lead to problems when a stateful session is needed between an app > and the cluster. For instance, Ignite JDBC driver preserves the state of an > opened connection meaning that once LoadBalancer connects the driver to an > Ignite pod, all the queries have to be redirected to that Ignite pod only > (unless the pod is down). > We need to show how to configure a sticky LoadBalancer that will assign a > client connection to a specific pod and won't change it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8923) Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
[
https://issues.apache.org/jira/browse/IGNITE-8923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Murchenko reassigned IGNITE-8923:
--
Assignee: Ilya Murchenko
> Add step-by-step guide - Google Cloud Engine Deployment (Kubernetes)
>
>
> Key: IGNITE-8923
> URL: https://issues.apache.org/jira/browse/IGNITE-8923
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
>Reporter: Roman Guseinov
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.7
>
> Attachments: config.zip, yaml.zip
>
>
> We have such documentation for Microsoft Azure
> [https://apacheignite.readme.io/docs/microsoft-azure-deployment]
> It would be great to publish the same for GCE.
> Here are steps which I used to deploy cluster (stateless, stateful) and web
> console:
> {code:java}
> ## Start Ignite Cluster
> 1. Grant cluster-admin role to current google user (to allow create roles):
> $ kubectl create clusterrolebinding myname2-cluster-admin-binding \
> --clusterrole=cluster-admin \
> --user=
> 2. Create service account and grant permissions:
> $ kubectl create -f sa.yaml
> $ kubectl create -f role.yaml
> $ kubectl create -f rolebind.yaml
> 3. Create a grid service:
> $ kubectl create -f service.yaml
> 4. Deploy Ignite Cluster:
> $ kubectl create -f grid.yaml
> ## Enable Ignite Persistence
> 5. Deploy Ignite StatefulSet with enabled Persistence (instead of step 4).
> $ kubectl create -f grid-pds.yaml
> 6. Connect to the Ignite node and activate cluster:
> $ kubectl exec -it ignite-cluster-0 -- /bin/bash
> $ cd /opt/ignite/apache-ignite-*
> $ ./bin/control.sh --activate
> ## Deploy Web Console:
> 7. Create a volume to keep web console data:
> $ kubectl create -f console-volume.yaml
> 8. Create load balancer to expose HTTP port and make web console available by
> service DNS-name (web-console.default.svc.cluster.local) inside Kuberntes
> enviroment:
> $ kubectl create -f console-service.yaml
> 9. Deploy Web Console:
> $ kubectl create -f console.yaml
> 10. Check external IP:
> $ kubectl get service web-console
> 11. Open Web Console in a web browser and Sign Up.
> 12. Move to User Profile page (Settings > Profile) and copy security token.
> 13. Insert security token into web-agent.yaml (TOKENS environment variable).
> 14. Deploy Web Agent:
> $ kubectl create -f web-agent.yaml
> {code}
> YAML and configs are attached.
> Creating a public Docker-image for Web Agent in progress:
> https://issues.apache.org/jira/browse/IGNITE-8526
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
