March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4135) Support for read only server configuration directory

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFCORE-4135?page=com.atlassian.jira.plug... ] Yeray Borges Santana commented on WFCORE-4135: ---------------------------------------------- I changed the issue title and description since analysis reveals that we could fulfill issue requirements by using --read-only-server-config=<config> setting if we allow it to work with read-only configuration directories. > Support for read only server configuration directory > ---------------------------------------------------- > > Key: WFCORE-4135 > URL: https://issues.redhat.com/browse/WFCORE-4135 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Rafael Ruiz > Assignee: Yeray Borges Santana > Priority: Major > > -We need something like- > ---disable-configuration-history- > -to use when running in containers to avoid write to any directory ('standalone_xml_history').- > History backups are senseless running on a container, and certain cloud use cases could require a non-writable storage mounted as a configuration directory. Also, when we are running on a non-containerized environment we could have very strict security rules that could force us the use of a read-only configuration directory. > We need a solution to make the server able to work with read-only configuration directories. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4135) Support for read only server configuration directory

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFCORE-4135?page=com.atlassian.jira.plug... ] Yeray Borges Santana edited comment on WFCORE-4135 at 3/16/20 8:29 AM: ----------------------------------------------------------------------- I changed the issue title and description since analysis reveals that we could fulfill issue requirements by using {{--read-only-server-config=<config>}} setting if we allow it to work with read-only configuration directories. was (Author: yersan): I changed the issue title and description since analysis reveals that we could fulfill issue requirements by using --read-only-server-config=<config> setting if we allow it to work with read-only configuration directories. > Support for read only server configuration directory > ---------------------------------------------------- > > Key: WFCORE-4135 > URL: https://issues.redhat.com/browse/WFCORE-4135 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Rafael Ruiz > Assignee: Yeray Borges Santana > Priority: Major > > -We need something like- > ---disable-configuration-history- > -to use when running in containers to avoid write to any directory ('standalone_xml_history').- > History backups are senseless running on a container, and certain cloud use cases could require a non-writable storage mounted as a configuration directory. Also, when we are running on a non-containerized environment we could have very strict security rules that could force us the use of a read-only configuration directory. > We need a solution to make the server able to work with read-only configuration directories. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4135) Support for read only server configuration directory

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFCORE-4135?page=com.atlassian.jira.plug... ] Yeray Borges Santana updated WFCORE-4135: ----------------------------------------- Description: -We need something like- ---disable-configuration-history- -to use when running in containers to avoid write to any directory ('standalone_xml_history').- History backups are senseless running on a container, and certain cloud use cases could require a non-writable storage mounted as a configuration directory. Also, when we are running on a non-containerized environment we could have very strict security rules that could force us the use of a read-only configuration directory. We need a solution to make the server able to work with read-only configuration directories. was: We need something like --disable-configuration-history to use when running in containers to avoid write to any directory ('standalone_xml_history'). > Support for read only server configuration directory > ---------------------------------------------------- > > Key: WFCORE-4135 > URL: https://issues.redhat.com/browse/WFCORE-4135 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Rafael Ruiz > Assignee: Yeray Borges Santana > Priority: Major > > -We need something like- > ---disable-configuration-history- > -to use when running in containers to avoid write to any directory ('standalone_xml_history').- > History backups are senseless running on a container, and certain cloud use cases could require a non-writable storage mounted as a configuration directory. Also, when we are running on a non-containerized environment we could have very strict security rules that could force us the use of a read-only configuration directory. > We need a solution to make the server able to work with read-only configuration directories. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4135) Support for read only server configuration directory

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFCORE-4135?page=com.atlassian.jira.plug... ] Yeray Borges Santana updated WFCORE-4135: ----------------------------------------- Summary: Support for read only server configuration directory (was: Add a new property to disable backups of configuration XML files. Also avoid writing to standalone_xml_history when --read-only-server-config=<config> is set. ) > Support for read only server configuration directory > ---------------------------------------------------- > > Key: WFCORE-4135 > URL: https://issues.redhat.com/browse/WFCORE-4135 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Rafael Ruiz > Assignee: Yeray Borges Santana > Priority: Major > > We need something like > --disable-configuration-history > to use when running in containers to avoid write to any directory ('standalone_xml_history'). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1090) Automate Sidecar validations

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1090?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1090. ----------------------------------- Resolution: Done > Automate Sidecar validations > ---------------------------- > > Key: SWSQE-1090 > URL: https://issues.redhat.com/browse/SWSQE-1090 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://github.com/kiali/kiali-ui/pull/1687 > https://github.com/kiali/kiali/pull/2500 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1081) Automate Sidecar error: https://github.com/kiali/kiali/pull/2468

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1081?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1081. ----------------------------------- Resolution: Done > Automate Sidecar error: https://github.com/kiali/kiali/pull/2468 > ---------------------------------------------------------------- > > Key: SWSQE-1081 > URL: https://issues.redhat.com/browse/SWSQE-1081 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5164) Automate with ansible HACep deploy

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5164?page=com.atlassian.jira.plug... ] Massimiliano Dessi updated DROOLS-5164: --------------------------------------- Sprint: 2020 Week 10-12 (from Mar 2) > Automate with ansible HACep deploy > ---------------------------------- > > Key: DROOLS-5164 > URL: https://issues.redhat.com/browse/DROOLS-5164 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > > Automate with Ansible the setup from scratch and for every new End user test on CRC -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5165) Align docs to the new Maven related scripts without new user

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5165?page=com.atlassian.jira.plug... ] Massimiliano Dessi updated DROOLS-5165: --------------------------------------- Sprint: 2020 Week 10-12 (from Mar 2) > Align docs to the new Maven related scripts without new user > ------------------------------------------------------------ > > Key: DROOLS-5165 > URL: https://issues.redhat.com/browse/DROOLS-5165 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5165) Align docs to the new Maven related scripts without new user

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5165?page=com.atlassian.jira.plug... ] Massimiliano Dessi resolved DROOLS-5165. ---------------------------------------- Resolution: Done > Align docs to the new Maven related scripts without new user > ------------------------------------------------------------ > > Key: DROOLS-5165 > URL: https://issues.redhat.com/browse/DROOLS-5165 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4031) Drools HACEP Operator/Ansible/Helm

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4031?page=com.atlassian.jira.plug... ] Massimiliano Dessi closed DROOLS-4031. -------------------------------------- Resolution: Duplicate Issue > Drools HACEP Operator/Ansible/Helm > ---------------------------------- > > Key: DROOLS-4031 > URL: https://issues.redhat.com/browse/DROOLS-4031 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > Labels: HADrools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2020