[jira] [Comment Edited] (CASSANDRA-18508) Sensitive JMX SSL configuration options can be easily exposed
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724051#comment-17724051
]
Anthony Grasso edited comment on CASSANDRA-18508 at 5/18/23 11:12 PM:
--
The Kubernetes cluster example makes sense as to why we might want this to be
pluggable.
I will change the patch so that the settings can be optionally defined in the
_cassandra.yaml_ via a pluggable class. Lets limit the scope to providing one
implementation where the JMX encryption settings are specified in the class
parameters. Basically, the {{DefaultRetriever}} example that [~smiklosovic]
gave:
{code}
jmx_credentials_provider:
- class_name: org.apache.cassandra.auth.jmx.DefaultRetriever
keystore: "/path/to/keystore.jks"
keystore_password: "abc"
truststore: "/path/to/truststore.jks"
truststore_password: "def"
.
{code}
Tickets can be raised for other class implementations.
was (Author: anthony):
The Kubernetes cluster example makes sense as to why we might want this to be
pluggable.
I will change the patch so that the settings can be optionally defined in the
_cassandra.yaml_ via a pluggable class. Lets limit the scope to providing an
implementation where the JMX encryption settings are specified in the class
parameters. Basically, the {{DefaultRetriever}} example that [~smiklosovic]
gave:
{code}
jmx_credentials_provider:
- class_name: org.apache.cassandra.auth.jmx.DefaultRetriever
keystore: "/path/to/keystore.jks"
keystore_password: "abc"
truststore: "/path/to/truststore.jks"
truststore_password: "def"
.
{code}
> Sensitive JMX SSL configuration options can be easily exposed
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the ability to specify a configuration file that can contain these
> security sensitive settings using the {{com.sun.management.config.file}}
> argument. However, despite what the documentation
> ([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
> says, both the {{com.sun.management.jmxremote}} and
> {{com.sun.management.jmxremote.port}} arguments need to be defined in the
> _cassandra-env.sh_ for the JVM to read the contents of the file.
> The problem with defining the {{com.sun.management.jmxremote.port}} argument
> is it conflicts with the {{cassandra.jmx.remote.port}} argument. Even if the
> port numbers are different, attempting an encrypted JMX connection using
> {{nodetool}} fails and we see a {{ConnectException: 'Connection refused
> (Connection refused)'}} error.
> One possible way to fix this is to introduce a new option that would allow a
> file to be passed containing the JMX encryption options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18508) Sensitive JMX SSL configuration options can be easily exposed
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724051#comment-17724051
]
Anthony Grasso edited comment on CASSANDRA-18508 at 5/18/23 11:09 PM:
--
The Kubernetes cluster example makes sense as to why we might want this to be
pluggable.
I will change the patch so that the settings can be optionally defined in the
_cassandra.yaml_ via a pluggable class. Lets limit the scope to providing an
implementation where the JMX encryption settings are specified in the class
parameters. Basically, the {{DefaultRetriever}} example that [~smiklosovic]
gave:
{code}
jmx_credentials_provider:
- class_name: org.apache.cassandra.auth.jmx.DefaultRetriever
keystore: "/path/to/keystore.jks"
keystore_password: "abc"
truststore: "/path/to/truststore.jks"
truststore_password: "def"
.
{code}
was (Author: anthony):
The Kubernetes cluster example makes sense as to why we might want this to be
pluggable.
I will change the patch so that the settings can be optionally defined in the
_cassandra.yaml_ via a pluggable class. Lets limit the scope to providing an
implementation where the JMX encryption settings are specified in the class
parameters the _cassandra.yaml_ file. Basically, the {{DefaultRetriever}}
example that [~smiklosovic] gave:
{code}
jmx_credentials_provider:
- class_name: org.apache.cassandra.auth.jmx.DefaultRetriever
keystore: "/path/to/keystore.jks"
keystore_password: "abc"
truststore: "/path/to/truststore.jks"
truststore_password: "def"
.
{code}
> Sensitive JMX SSL configuration options can be easily exposed
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the ability to specify a configuration file that can contain these
> security sensitive settings using the {{com.sun.management.config.file}}
> argument. However, despite what the documentation
> ([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
> says, both the {{com.sun.management.jmxremote}} and
> {{com.sun.management.jmxremote.port}} arguments need to be defined in the
> _cassandra-env.sh_ for the JVM to read the contents of the file.
> The problem with defining the {{com.sun.management.jmxremote.port}} argument
> is it conflicts with the {{cassandra.jmx.remote.port}} argument. Even if the
> port numbers are different, attempting an encrypted JMX connection using
> {{nodetool}} fails and we see a {{ConnectException: 'Connection refused
> (Connection refused)'}} error.
> One possible way to fix this is to introduce a new option that would allow a
> file to be passed containing the JMX encryption options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18508) Sensitive JMX SSL configuration options can be easily exposed
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17724051#comment-17724051
]
Anthony Grasso commented on CASSANDRA-18508:
The Kubernetes cluster example makes sense as to why we might want this to be
pluggable.
I will change the patch so that the settings can be optionally defined in the
_cassandra.yaml_ via a pluggable class. Lets limit the scope to providing an
implementation where the JMX encryption settings are specified in the class
parameters the _cassandra.yaml_ file. Basically, the {{DefaultRetriever}}
example that [~smiklosovic] gave:
{code}
jmx_credentials_provider:
- class_name: org.apache.cassandra.auth.jmx.DefaultRetriever
keystore: "/path/to/keystore.jks"
keystore_password: "abc"
truststore: "/path/to/truststore.jks"
truststore_password: "def"
.
{code}
> Sensitive JMX SSL configuration options can be easily exposed
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the ability to specify a configuration file that can contain these
> security sensitive settings using the {{com.sun.management.config.file}}
> argument. However, despite what the documentation
> ([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
> says, both the {{com.sun.management.jmxremote}} and
> {{com.sun.management.jmxremote.port}} arguments need to be defined in the
> _cassandra-env.sh_ for the JVM to read the contents of the file.
> The problem with defining the {{com.sun.management.jmxremote.port}} argument
> is it conflicts with the {{cassandra.jmx.remote.port}} argument. Even if the
> port numbers are different, attempting an encrypted JMX connection using
> {{nodetool}} fails and we see a {{ConnectException: 'Connection refused
> (Connection refused)'}} error.
> One possible way to fix this is to introduce a new option that would allow a
> file to be passed containing the JMX encryption options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18508) Sensitive JMX SSL configuration options can be easily exposed
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723781#comment-17723781
]
Anthony Grasso edited comment on CASSANDRA-18508 at 5/18/23 4:10 AM:
-
I really like the idea of having the alternative location for the JMX
properties defined in the _cassandra.yaml_. While I think having pluggable is a
neat idea, I think we should just add the ability to optionally specify the JMX
encryption settings in only the _cassandra.yaml_ file.
Having a pluggable setting in this case adds more complexity to configure the
encryption settings which are already difficult enough to configure.
Introducing the pluggable file loader adds a layer of indirection and has the
same drawback as my original proposal.
I propose we have a new set of encryption settings in the _cassandra.yaml_ file
that either uses or extends the existing {{EncryptionOptions}} class.
{code:java}
jmx_encryption_options:
enabled:
keystore:
keystore_password:
keystore_type:
truststore:
truststore_password:
truststore_type:
require_client_auth:
protocols: []
cipher_suites: []
{code}
An other thing to consider is [~toblin] made a good suggestion in a [comment on
the pull
request|https://github.com/apache/cassandra/pull/2338#pullrequestreview-1427792356]
to have one single way to load system properties into the JVM from a file into
Cassandra in general. I feel this idea is mutually exclusive to the idea of
placing the JMX encryption options in to the _cassandra.yaml_.
I think we should pick one option to solve this issue and raise a ticket for
the other.
was (Author: anthony):
I really like the idea of having the alternative location for the JMX
properties defined in the _cassandra.yaml_. While I think having pluggable is a
neat idea, I think we should just add the ability to optionally specify the JMX
encryption settings in only the _cassandra.yaml_ file.
Having a pluggable setting in this case adds more complexity to configure the
encryption settings which are already difficult enough to configure.
Introducing the pluggable file loader adds a layer of indirection and has the
same drawback as my original proposal.
I propose we have a new set of encryption settings in the _cassandra.yaml_ file
that either uses or extends the existing {{EncryptionOptions}} class.
{code:java}
jmx_encryption_options:
enabled:
keystore:
keystore_password:
keystore_type:
truststore:
truststore_password:
truststore_type:
require_client_auth:
protocols: []
cipher_suites: []
{code}
An other thing to consider is [~toblin] made a good suggestion in a [comment on
the pull
request|https://github.com/apache/cassandra/pull/2338#pullrequestreview-1427792356]
to have one single way to load system properties into the JVM from a file into
Cassandra in general. I feel this idea is mutually exclusive to the idea of
placing the JMX encryption options in to the _cassandra.yaml_.
I think we should implement the functionality to optionally allow the JMX
encryption options to be placed in the _cassandra.yaml_ and create a ticket for
method to load the system properties into the JVM from a file (which I'd be
happy to implement as well). Whilst loading the JVM properties from a file
solves the issue, I feel it is broader in scope than what this ticket is trying
to solve.
> Sensitive JMX SSL configuration options can be easily exposed
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the ability to specify a configuration file that can contain these
> security sensitive settings using the {{com.sun.management.config.file}}
> argument. However, despite what the documentation
> ([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
> says, both the {{com.sun.management.jmxremote}} and
> {{com.sun.management.jmxremote.port}} arguments need to be defined in the
> _cassandra-env.sh_ for the JVM to read the contents of the file.
> The problem with
[jira] [Comment Edited] (CASSANDRA-18508) Sensitive JMX SSL configuration options can be easily exposed
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723781#comment-17723781
]
Anthony Grasso edited comment on CASSANDRA-18508 at 5/18/23 4:00 AM:
-
I really like the idea of having the alternative location for the JMX
properties defined in the _cassandra.yaml_. While I think having pluggable is a
neat idea, I think we should just add the ability to optionally specify the JMX
encryption settings in only the _cassandra.yaml_ file.
Having a pluggable setting in this case adds more complexity to configure the
encryption settings which are already difficult enough to configure.
Introducing the pluggable file loader adds a layer of indirection and has the
same drawback as my original proposal.
I propose we have a new set of encryption settings in the _cassandra.yaml_ file
that either uses or extends the existing {{EncryptionOptions}} class.
{code:java}
jmx_encryption_options:
enabled:
keystore:
keystore_password:
keystore_type:
truststore:
truststore_password:
truststore_type:
require_client_auth:
protocols: []
cipher_suites: []
{code}
An other thing to consider is [~toblin] made a good suggestion in a [comment on
the pull
request|https://github.com/apache/cassandra/pull/2338#pullrequestreview-1427792356]
to have one single way to load system properties into the JVM from a file into
Cassandra in general. I feel this idea is mutually exclusive to the idea of
placing the JMX encryption options in to the _cassandra.yaml_.
I think we should implement the functionality to optionally allow the JMX
encryption options to be placed in the _cassandra.yaml_ and create a ticket for
method to load the system properties into the JVM from a file (which I'd be
happy to implement as well). Whilst loading the JVM properties from a file
solves the issue, I feel it is broader in scope than what this ticket is trying
to solve.
was (Author: anthony):
I really like the idea of having the alternative location for the JMX
properties defined in the _cassandra.yaml_. I think we should just add the
ability to optionally specify the JMX encryption settings in only the
_cassandra.yaml_ file.
I think having a pluggable setting in this case adds more complexity to
configure the encryption settings which are already difficult enough to
configure. If we had a {{org.apache.cassandra.auth.jmx.DefaultFileRetriever}},
it would mean that a property in _canssandra-env.sh_ file would need to point
to the _cassandra.yaml file_. Then a setting in the _cassandra.yaml_ file would
need to point to a properties file. I feel it is too many layers of indirection
which may make debugging difficult.
I propose we have a new set of encryption settings in the _cassandra.yaml_ file
that either uses or extends the existing {{EncryptionOptions}} class.
{code:java}
jmx_encryption_options:
enabled:
keystore:
keystore_password:
keystore_type:
truststore:
truststore_password:
truststore_type:
require_client_auth:
protocols: []
cipher_suites: []
{code}
An other thing to consider is [~toblin] made a good suggestion in a [comment on
the pull
request|https://github.com/apache/cassandra/pull/2338#pullrequestreview-1427792356]
to have one single way to load system properties into the JVM from a file into
Cassandra in general. I feel this idea is mutually exclusive to the idea of
placing the JMX encryption options in to the _cassandra.yaml_.
I think we should implement the functionality to optionally allow the JMX
encryption options to be placed in the _cassandra.yaml_ and create a ticket for
method to load the system properties into the JVM from a file (which I'd be
happy to implement as well). Whilst loading the JVM properties from a file
solves the issue, I feel it is broader in scope than what this ticket is trying
to solve.
> Sensitive JMX SSL configuration options can be easily exposed
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the
[jira] [Commented] (CASSANDRA-18508) Sensitive JMX SSL configuration options can be easily exposed
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723781#comment-17723781
]
Anthony Grasso commented on CASSANDRA-18508:
I really like the idea of having the alternative location for the JMX
properties defined in the _cassandra.yaml_. I think we should just add the
ability to optionally specify the JMX encryption settings in only the
_cassandra.yaml_ file.
I think having a pluggable setting in this case adds more complexity to
configure the encryption settings which are already difficult enough to
configure. If we had a {{org.apache.cassandra.auth.jmx.DefaultFileRetriever}},
it would mean that a property in _canssandra-env.sh_ file would need to point
to the _cassandra.yaml file_. Then a setting in the _cassandra.yaml_ file would
need to point to a properties file. I feel it is too many layers of indirection
which may make debugging difficult.
I propose we have a new set of encryption settings in the _cassandra.yaml_ file
that either uses or extends the existing {{EncryptionOptions}} class.
{code:java}
jmx_encryption_options:
enabled:
keystore:
keystore_password:
keystore_type:
truststore:
truststore_password:
truststore_type:
require_client_auth:
protocols: []
cipher_suites: []
{code}
An other thing to consider is [~toblin] made a good suggestion in a [comment on
the pull
request|https://github.com/apache/cassandra/pull/2338#pullrequestreview-1427792356]
to have one single way to load system properties into the JVM from a file into
Cassandra in general. I feel this idea is mutually exclusive to the idea of
placing the JMX encryption options in to the _cassandra.yaml_.
I think we should implement the functionality to optionally allow the JMX
encryption options to be placed in the _cassandra.yaml_ and create a ticket for
method to load the system properties into the JVM from a file (which I'd be
happy to implement as well). Whilst loading the JVM properties from a file
solves the issue, I feel it is broader in scope than what this ticket is trying
to solve.
> Sensitive JMX SSL configuration options can be easily exposed
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the ability to specify a configuration file that can contain these
> security sensitive settings using the {{com.sun.management.config.file}}
> argument. However, despite what the documentation
> ([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
> says, both the {{com.sun.management.jmxremote}} and
> {{com.sun.management.jmxremote.port}} arguments need to be defined in the
> _cassandra-env.sh_ for the JVM to read the contents of the file.
> The problem with defining the {{com.sun.management.jmxremote.port}} argument
> is it conflicts with the {{cassandra.jmx.remote.port}} argument. Even if the
> port numbers are different, attempting an encrypted JMX connection using
> {{nodetool}} fails and we see a {{ConnectException: 'Connection refused
> (Connection refused)'}} error.
> One possible way to fix this is to introduce a new option that would allow a
> file to be passed containing the JMX encryption options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18508) Sensitive JMX SSL configuration options can be easily exposed
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17723089#comment-17723089
]
Anthony Grasso commented on CASSANDRA-18508:
That is an interesting idea. In short, no; there was no consideration for using
the {_}cassandra.yaml{_}.
Retrieving the properties from the _cassandra.yaml_ would be more work than the
original proposal. However, it definitely makes sense to do that from a
consistency perspective. I do have some ideas of how it could be implemented.
If we feel it is the right thing to do, then I am happy to change the patch. In
this case, would we still add this to Cassandra 4.0?
[~bereng] let me know what you think.
> Sensitive JMX SSL configuration options can be easily exposed
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the ability to specify a configuration file that can contain these
> security sensitive settings using the {{com.sun.management.config.file}}
> argument. However, despite what the documentation
> ([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
> says, both the {{com.sun.management.jmxremote}} and
> {{com.sun.management.jmxremote.port}} arguments need to be defined in the
> _cassandra-env.sh_ for the JVM to read the contents of the file.
> The problem with defining the {{com.sun.management.jmxremote.port}} argument
> is it conflicts with the {{cassandra.jmx.remote.port}} argument. Even if the
> port numbers are different, attempting an encrypted JMX connection using
> {{nodetool}} fails and we see a {{ConnectException: 'Connection refused
> (Connection refused)'}} error.
> One possible way to fix this is to introduce a new option that would allow a
> file to be passed containing the JMX encryption options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18508) Sensitive JMX SSL configuration options can be easily exposed
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Grasso updated CASSANDRA-18508:
---
Source Control Link: https://github.com/apache/cassandra/pull/2338
> Sensitive JMX SSL configuration options can be easily exposed
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the ability to specify a configuration file that can contain these
> security sensitive settings using the {{com.sun.management.config.file}}
> argument. However, despite what the documentation
> ([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
> says, both the {{com.sun.management.jmxremote}} and
> {{com.sun.management.jmxremote.port}} arguments need to be defined in the
> _cassandra-env.sh_ for the JVM to read the contents of the file.
> The problem with defining the {{com.sun.management.jmxremote.port}} argument
> is it conflicts with the {{cassandra.jmx.remote.port}} argument. Even if the
> port numbers are different, attempting an encrypted JMX connection using
> {{nodetool}} fails and we see a {{ConnectException: 'Connection refused
> (Connection refused)'}} error.
> One possible way to fix this is to introduce a new option that would allow a
> file to be passed containing the JMX encryption options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18508) Sensitive JMX SSL configuration options can be easily exposed
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Grasso updated CASSANDRA-18508:
---
Source Control Link: (was: https://github.com/apache/cassandra/pull/2338)
> Sensitive JMX SSL configuration options can be easily exposed
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the ability to specify a configuration file that can contain these
> security sensitive settings using the {{com.sun.management.config.file}}
> argument. However, despite what the documentation
> ([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
> says, both the {{com.sun.management.jmxremote}} and
> {{com.sun.management.jmxremote.port}} arguments need to be defined in the
> _cassandra-env.sh_ for the JVM to read the contents of the file.
> The problem with defining the {{com.sun.management.jmxremote.port}} argument
> is it conflicts with the {{cassandra.jmx.remote.port}} argument. Even if the
> port numbers are different, attempting an encrypted JMX connection using
> {{nodetool}} fails and we see a {{ConnectException: 'Connection refused
> (Connection refused)'}} error.
> One possible way to fix this is to introduce a new option that would allow a
> file to be passed containing the JMX encryption options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18508) Sensitive JMX SSL configuration options can be easily exposed
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Grasso updated CASSANDRA-18508:
---
Test and Documentation Plan:
Unit tests created for the patch.
End to end tests carried out and have verified that the fix hides sensitive SSL
information from the process output.
Status: Patch Available (was: In Progress)
Patch available in PR [#2338|https://github.com/apache/cassandra/pull/2338]
> Sensitive JMX SSL configuration options can be easily exposed
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the ability to specify a configuration file that can contain these
> security sensitive settings using the {{com.sun.management.config.file}}
> argument. However, despite what the documentation
> ([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
> says, both the {{com.sun.management.jmxremote}} and
> {{com.sun.management.jmxremote.port}} arguments need to be defined in the
> _cassandra-env.sh_ for the JVM to read the contents of the file.
> The problem with defining the {{com.sun.management.jmxremote.port}} argument
> is it conflicts with the {{cassandra.jmx.remote.port}} argument. Even if the
> port numbers are different, attempting an encrypted JMX connection using
> {{nodetool}} fails and we see a {{ConnectException: 'Connection refused
> (Connection refused)'}} error.
> One possible way to fix this is to introduce a new option that would allow a
> file to be passed containing the JMX encryption options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18508) Sensitive JMX SSL configuration options can be easily exposed
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17721769#comment-17721769
]
Anthony Grasso commented on CASSANDRA-18508:
The way I am thinking of fixing this issue is adding a new system property
called {{cassandra.jmx.remote.ssl.config.file}}. This property would specify a
path to a file containing only the {{javax.net.ssl.*}} properties.
> Sensitive JMX SSL configuration options can be easily exposed
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the ability to specify a configuration file that can contain these
> security sensitive settings using the {{com.sun.management.config.file}}
> argument. However, despite what the documentation
> ([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
> says, both the {{com.sun.management.jmxremote}} and
> {{com.sun.management.jmxremote.port}} arguments need to be defined in the
> _cassandra-env.sh_ for the JVM to read the contents of the file.
> The problem with defining the {{com.sun.management.jmxremote.port}} argument
> is it conflicts with the {{cassandra.jmx.remote.port}} argument. Even if the
> port numbers are different, attempting an encrypted JMX connection using
> {{nodetool}} fails and we see a {{ConnectException: 'Connection refused
> (Connection refused)'}} error.
> One possible way to fix this is to introduce a new option that would allow a
> file to be passed containing the JMX encryption options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18508) Sensitive JMX SSL configuration options can be easily exposed
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Grasso updated CASSANDRA-18508:
---
Complexity: Normal (was: Low Hanging Fruit)
> Sensitive JMX SSL configuration options can be easily exposed
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the ability to specify a configuration file that can contain these
> security sensitive settings using the {{com.sun.management.config.file}}
> argument. However, despite what the documentation
> ([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
> says, both the {{com.sun.management.jmxremote}} and
> {{com.sun.management.jmxremote.port}} arguments need to be defined in the
> _cassandra-env.sh_ for the JVM to read the contents of the file.
> The problem with defining the {{com.sun.management.jmxremote.port}} argument
> is it conflicts with the {{cassandra.jmx.remote.port}} argument. Even if the
> port numbers are different, attempting an encrypted JMX connection using
> {{nodetool}} fails and we see a {{ConnectException: 'Connection refused
> (Connection refused)'}} error.
> One possible way to fix this is to introduce a new option that would allow a
> file to be passed containing the JMX encryption options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18508) Sensitive JMX SSL configuration options can be easily exposed
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Grasso updated CASSANDRA-18508:
---
Summary: Sensitive JMX SSL configuration options can be easily exposed
(was: Allow JMX SSL configuration options to be passed via file)
> Sensitive JMX SSL configuration options can be easily exposed
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the ability to specify a configuration file that can contain these
> security sensitive settings using the {{com.sun.management.config.file}}
> argument. However, despite what the documentation
> ([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
> says, both the {{com.sun.management.jmxremote}} and
> {{com.sun.management.jmxremote.port}} arguments need to be defined in the
> _cassandra-env.sh_ for the JVM to read the contents of the file.
> The problem with defining the {{com.sun.management.jmxremote.port}} argument
> is it conflicts with the {{cassandra.jmx.remote.port}} argument. Even if the
> port numbers are different, attempting an encrypted JMX connection using
> {{nodetool}} fails and we see a {{ConnectException: 'Connection refused
> (Connection refused)'}} error.
> One possible way to fix this is to introduce a new option that would allow a
> file to be passed containing the JMX encryption options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18508) Allow JMX SSL configuration options to be passed via file
[
https://issues.apache.org/jira/browse/CASSANDRA-18508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Grasso updated CASSANDRA-18508:
---
Change Category: Operability
Complexity: Low Hanging Fruit
Fix Version/s: 4.0.x
4.1.x
5.0
Platform: (was: All)
Status: Open (was: Triage Needed)
> Allow JMX SSL configuration options to be passed via file
> -
>
> Key: CASSANDRA-18508
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Encryption
>Reporter: Anthony Grasso
>Assignee: Anthony Grasso
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0
>
>
> We need a way to specify sensitive JMX SSL configuration options to avoid
> them being easily exposed.
> When encrypting the JMX connection the passwords for the key and trust stores
> must be specified using the {{javax.net.ssl.keyStorePassword}} and
> {{javax.net.ssl.trustStorePassword}} options respectively in the
> _cassandra-env.sh_ file. After Cassandra is started it is possible to see the
> passwords by looking the running process ({{ps aux | grep "cassandra"}}).
> Java 8 has the ability to specify a configuration file that can contain these
> security sensitive settings using the {{com.sun.management.config.file}}
> argument. However, despite what the documentation
> ([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
> says, both the {{com.sun.management.jmxremote}} and
> {{com.sun.management.jmxremote.port}} arguments need to be defined in the
> _cassandra-env.sh_ for the JVM to read the contents of the file.
> The problem with defining the {{com.sun.management.jmxremote.port}} argument
> is it conflicts with the {{cassandra.jmx.remote.port}} argument. Even if the
> port numbers are different, attempting an encrypted JMX connection using
> {{nodetool}} fails and we see a {{ConnectException: 'Connection refused
> (Connection refused)'}} error.
> One possible way to fix this is to introduce a new option that would allow a
> file to be passed containing the JMX encryption options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18508) Allow JMX SSL configuration options to be passed via file
Anthony Grasso created CASSANDRA-18508:
--
Summary: Allow JMX SSL configuration options to be passed via file
Key: CASSANDRA-18508
URL: https://issues.apache.org/jira/browse/CASSANDRA-18508
Project: Cassandra
Issue Type: Improvement
Components: Feature/Encryption
Reporter: Anthony Grasso
Assignee: Anthony Grasso
We need a way to specify sensitive JMX SSL configuration options to avoid them
being easily exposed.
When encrypting the JMX connection the passwords for the key and trust stores
must be specified using the {{javax.net.ssl.keyStorePassword}} and
{{javax.net.ssl.trustStorePassword}} options respectively in the
_cassandra-env.sh_ file. After Cassandra is started it is possible to see the
passwords by looking the running process ({{ps aux | grep "cassandra"}}).
Java 8 has the ability to specify a configuration file that can contain these
security sensitive settings using the {{com.sun.management.config.file}}
argument. However, despite what the documentation
([https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html#gdevf])
says, both the {{com.sun.management.jmxremote}} and
{{com.sun.management.jmxremote.port}} arguments need to be defined in the
_cassandra-env.sh_ for the JVM to read the contents of the file.
The problem with defining the {{com.sun.management.jmxremote.port}} argument is
it conflicts with the {{cassandra.jmx.remote.port}} argument. Even if the port
numbers are different, attempting an encrypted JMX connection using
{{nodetool}} fails and we see a {{ConnectException: 'Connection refused
(Connection refused)'}} error.
One possible way to fix this is to introduce a new option that would allow a
file to be passed containing the JMX encryption options.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18027) Use G1GC as default
[ https://issues.apache.org/jira/browse/CASSANDRA-18027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17633692#comment-17633692 ] Anthony Grasso commented on CASSANDRA-18027: I am in favour of switching to G1 as well. Most production clusters I've seen are typically running with a heap size of 16 GB or higher which works well with G1. I agree with Elliott Sims's comment on the dev mailing list. Specifically, I think this change should go into 4.1 onwards. However, I feel the change is too significant to be back-ported to 4.0. > Use G1GC as default > --- > > Key: CASSANDRA-18027 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18027 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 4.x > > > G1GC is well battle tested now, and the recommended configuration for most > users. CMS can work well on smaller heaps but requires more tuning, initially > and over time. G1GC just works. CMS was deprecated in JDK 9. > Patch at > https://github.com/apache/cassandra/compare/trunk...thelastpickle:cassandra:mck/7486/trunk -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17569) DOC - tools/nodetool is untitled and might be affecting search results
[
https://issues.apache.org/jira/browse/CASSANDRA-17569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Grasso updated CASSANDRA-17569:
---
Mentor: Michael Semb Wever
Status: Ready to Commit (was: Review In Progress)
Changes reviewed. This is ready to commit.
[~erickramirezau] we need to make sure this is committed to the 3.0, 3.11, 4.0,
4.1, and trunk branches.
> DOC - tools/nodetool is untitled and might be affecting search results
> --
>
> Key: CASSANDRA-17569
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17569
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.0.x, 4.1.x
>
>
> Reported by [~mck] in [ASF Slack
> #cassandra-website|https://the-asf.slack.com/archives/C01RY1LUPD5/p1650446747714449]:
> {quote}I see that the nodetool doc pages have the title {{Untitled | …}} ( i
> think this impacting search results){quote}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17569) DOC - tools/nodetool is untitled and might be affecting search results
[
https://issues.apache.org/jira/browse/CASSANDRA-17569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Grasso updated CASSANDRA-17569:
---
Reviewers: Anthony Grasso
Status: Review In Progress (was: Patch Available)
Starting review.
> DOC - tools/nodetool is untitled and might be affecting search results
> --
>
> Key: CASSANDRA-17569
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17569
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Erick Ramirez
>Assignee: Erick Ramirez
>Priority: Normal
> Fix For: 4.0.x, 4.1.x
>
>
> Reported by [~mck] in [ASF Slack
> #cassandra-website|https://the-asf.slack.com/archives/C01RY1LUPD5/p1650446747714449]:
> {quote}I see that the nodetool doc pages have the title {{Untitled | …}} ( i
> think this impacting search results){quote}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16761) New Cassandra Website and Documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-16761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16761: --- Source Control Link: See tickets in epic for patch links. Resolution: Fixed Status: Resolved (was: Ready to Commit) > New Cassandra Website and Documentation > --- > > Key: CASSANDRA-16761 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16761 > Project: Cassandra > Issue Type: Epic > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: High > Fix For: 4.0.x > > > This epic captures the work associated with the development of the new > Cassandra website and documentation. > Work to create the new website and documentation will be broken up as follows: > * Proof of concept - CASSANDRA-16029 > * Website concept and design - CASSANDRA-16115 > * Develop tooling to render new website and documentation - CASSANDRA-16066 > * Create website content that will be rendered by new tooling - > CASSANDRA-16762 > * Create Cassandra documentation content that will be rendered by new > tooling - CASSANDRA-16763 > It is expected that the new website and documentation will be in asciidoc > format and rendered using Antora. > Antora is purpose built for rendering versioned documentation to HTML. In > addition it allows rendering customisations via Java Script which may be > useful when rending the website. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16761) New Cassandra Website and Documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-16761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16761: --- Mentor: Michael Semb Wever Status: Review In Progress (was: Patch Available) > New Cassandra Website and Documentation > --- > > Key: CASSANDRA-16761 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16761 > Project: Cassandra > Issue Type: Epic > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: High > Fix For: 4.0.x > > > This epic captures the work associated with the development of the new > Cassandra website and documentation. > Work to create the new website and documentation will be broken up as follows: > * Proof of concept - CASSANDRA-16029 > * Website concept and design - CASSANDRA-16115 > * Develop tooling to render new website and documentation - CASSANDRA-16066 > * Create website content that will be rendered by new tooling - > CASSANDRA-16762 > * Create Cassandra documentation content that will be rendered by new > tooling - CASSANDRA-16763 > It is expected that the new website and documentation will be in asciidoc > format and rendered using Antora. > Antora is purpose built for rendering versioned documentation to HTML. In > addition it allows rendering customisations via Java Script which may be > useful when rending the website. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16761) New Cassandra Website and Documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-16761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16761: --- Status: Ready to Commit (was: Review In Progress) > New Cassandra Website and Documentation > --- > > Key: CASSANDRA-16761 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16761 > Project: Cassandra > Issue Type: Epic > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: High > Fix For: 4.0.x > > > This epic captures the work associated with the development of the new > Cassandra website and documentation. > Work to create the new website and documentation will be broken up as follows: > * Proof of concept - CASSANDRA-16029 > * Website concept and design - CASSANDRA-16115 > * Develop tooling to render new website and documentation - CASSANDRA-16066 > * Create website content that will be rendered by new tooling - > CASSANDRA-16762 > * Create Cassandra documentation content that will be rendered by new > tooling - CASSANDRA-16763 > It is expected that the new website and documentation will be in asciidoc > format and rendered using Antora. > Antora is purpose built for rendering versioned documentation to HTML. In > addition it allows rendering customisations via Java Script which may be > useful when rending the website. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16761) New Cassandra Website and Documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-16761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16761: --- Test and Documentation Plan: N/A. Tickets in epic are already tested and resolved. Status: Patch Available (was: In Progress) > New Cassandra Website and Documentation > --- > > Key: CASSANDRA-16761 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16761 > Project: Cassandra > Issue Type: Epic > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: High > Fix For: 4.0.x > > > This epic captures the work associated with the development of the new > Cassandra website and documentation. > Work to create the new website and documentation will be broken up as follows: > * Proof of concept - CASSANDRA-16029 > * Website concept and design - CASSANDRA-16115 > * Develop tooling to render new website and documentation - CASSANDRA-16066 > * Create website content that will be rendered by new tooling - > CASSANDRA-16762 > * Create Cassandra documentation content that will be rendered by new > tooling - CASSANDRA-16763 > It is expected that the new website and documentation will be in asciidoc > format and rendered using Antora. > Antora is purpose built for rendering versioned documentation to HTML. In > addition it allows rendering customisations via Java Script which may be > useful when rending the website. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17521) WEBSITE - April 2022 blog "Apache Cassandra Changelog #14"
[ https://issues.apache.org/jira/browse/CASSANDRA-17521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17521: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - April 2022 blog "Apache Cassandra Changelog #14" > -- > > Key: CASSANDRA-17521 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17521 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17521-01-blog-index.png, c17521-02-blog-post.png > > > This ticket is to capture the work associated with publishing the April 2022 > blog "Apache Cassandra Changelog #14" > If this blog cannot be published by the *April 7, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17579) WEBSITE - April 2022 blog "Liquibase is Ready to Support Cassandra 4.0 Users" + Liquibase case study
[ https://issues.apache.org/jira/browse/CASSANDRA-17579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17579: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - April 2022 blog "Liquibase is Ready to Support Cassandra 4.0 Users" > + Liquibase case study > > > Key: CASSANDRA-17579 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17579 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.x > > Attachments: c17579-01-blog-index.png, c17579-02-blog-post.png, > c17579-03-case_studies-index.png, c17579-04-case_study.png > > > This ticket is to capture the work associated with publishing the April 2022 > blog "Liquibase is Ready to Support Cassandra 4.0 Users" and adding the > Liquidbase case study to the website. > If this blog + case study cannot be published by the *April 28, 2022 publish > date*, please contact me, suggest changes, or correct the date when possible > in the pull request for the appropriate time that the blog will go live (on > both the blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17511) WEBSITE - Kinetic Data case study and blog formatting edits
[ https://issues.apache.org/jira/browse/CASSANDRA-17511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17511: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Kinetic Data case study and blog formatting edits > --- > > Key: CASSANDRA-17511 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17511 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17511-01-blog-post.png, c17511-02-case_study.png > > > This ticket is to capture the work associated with addressing formatting > issues on the Kinetic Data case study and blog. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17555) WEBSITE - April 2022 blog "Inside Cassandra: An Interview with Project Contributor, Aleksandr Sorokoumov"
[ https://issues.apache.org/jira/browse/CASSANDRA-17555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17555: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - April 2022 blog "Inside Cassandra: An Interview with Project > Contributor, Aleksandr Sorokoumov" > - > > Key: CASSANDRA-17555 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17555 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17555-01-blog-index.png, c17555-02-blog-post.png > > > This ticket is to capture the work associated with publishing the April 2022 > blog "Inside Cassandra: An Interview with Project Contributor, Aleksandr > Sorokoumov" > If this blog cannot be published by the *April 14, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17497) WEBSITE - March 2022 blog "Kinetic Data chooses Apache Cassandra to deliver workflow automation solution"
[ https://issues.apache.org/jira/browse/CASSANDRA-17497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17497: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - March 2022 blog "Kinetic Data chooses Apache Cassandra to deliver > workflow automation solution" > - > > Key: CASSANDRA-17497 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17497 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17497-01-blog-index.png, c17497-02-blog-post.png > > > This ticket is to capture the work associated with publishing the March 2022 > blog "Kinetic Data chooses Apache Cassandra to deliver workflow automation > solution" > If this blog cannot be published by the *March 31, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17468) WEBSITE - Blog corrections and fixes, March 2022
[ https://issues.apache.org/jira/browse/CASSANDRA-17468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17468: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Blog corrections and fixes, March 2022 > > > Key: CASSANDRA-17468 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17468 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17468-01-blog-changelog_12.png, > c17468-02-blog-java_11_support.png, c17468-03-blog-behind_the_scenes.png, > c17468-04-blog-using_operators.png > > > This ticket is to capture the work associated with updating/fixing the Apache > Cassandra website with text/formatting/link edits. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17479) WEBSITE - Case Studies - Add Kinetic Data, fix Backblaze
[ https://issues.apache.org/jira/browse/CASSANDRA-17479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17479: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Case Studies - Add Kinetic Data, fix Backblaze > > > Key: CASSANDRA-17479 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17479 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17479-01-blog-index.png, c17479-02-blog-post.png > > > This ticket is to capture the work associated with adding a new case study to > the website and entry on the Case Studies page. > * Add Kinetic Data case study > * Add Kinetic Data card to Case Studies page > * Add Kinetic Data logo to images: kinetic_data.svg > * Fix Backblaze case study typo -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17483) WEBSITE - Homepage and Case Studies page edits
[ https://issues.apache.org/jira/browse/CASSANDRA-17483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17483: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Homepage and Case Studies page edits > -- > > Key: CASSANDRA-17483 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17483 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Priority: Normal > Fix For: NA > > > This ticket is to capture the work associated with updates to the Apache > Cassandra homepage, Case Studies page, and blog posts to address typos and > formatting issues. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17409) WEBSITE - March 2022 blog "Can Apache Cassandra take my PEM keys?"
[ https://issues.apache.org/jira/browse/CASSANDRA-17409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17409: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - March 2022 blog "Can Apache Cassandra take my PEM keys?" > -- > > Key: CASSANDRA-17409 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17409 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Maulin Vasavada >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17409-01-blog-index.png, c17409-02-blog-post.png, > c17409-03-blog-index-v2.png > > > This ticket is to capture the work associated with publishing the March 2022 > blog "Can Apache Cassandra take my PEM keys?" > If this blog cannot be published by the *March 10, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17446) DOC - Update 3.11 Backups page to use nodetool refresh instead of import
[ https://issues.apache.org/jira/browse/CASSANDRA-17446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17446: --- Epic Link: (was: CASSANDRA-16761) > DOC - Update 3.11 Backups page to use nodetool refresh instead of import > > > Key: CASSANDRA-17446 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17446 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Chien-Fu Chen >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.11.12 > > Time Spent: 10m > Remaining Estimate: 0h > > I've found a typo shown in official Cassandra website when I was looking for > Cassandra backup & restore solution. I believe there's no nodetool import > option available. It might be nodetool refresh? > [https://cassandra.apache.org/doc/3.11/cassandra/operating/backups.html] > h2. [Restoring from Incremental Backups and > Snapshots|https://cassandra.apache.org/doc/3.11/cassandra/operating/backups.html#restoring-from-incremental-backups-and-snapshots] > The two main tools/commands for restoring a table after it has been dropped > are: > * sstableloader > * nodetool import > Ref: > [https://cassandra.apache.org/doc/3.11/cassandra/tools/nodetool/refresh.html] -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17441) WEBSITE - March 2022 blog "Inside Cassandra: An Interview with Project Contributor, Lorina Poland"
[ https://issues.apache.org/jira/browse/CASSANDRA-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17441: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - March 2022 blog "Inside Cassandra: An Interview with Project > Contributor, Lorina Poland" > -- > > Key: CASSANDRA-17441 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17441 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17441-01-bad_render.png, c17441-02-blog-index.png, > c17441-03-blog-post.png > > > This ticket is to capture the work associated with publishing the March 2022 > blog "Inside Cassandra: An Interview with Project Contributor, Lorina Poland" > If this blog cannot be published by the *March 17, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17395) WEBSITE - Homepage quotes + spotlight updates, March 2022
[ https://issues.apache.org/jira/browse/CASSANDRA-17395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17395: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Homepage quotes + spotlight updates, March 2022 > - > > Key: CASSANDRA-17395 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17395 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17395-01-homepage-quote-witfoo.png, > c17395-02-homepage-quote-netflix.png, c17395-03-blog-C_is_here.png > > > This ticket is to capture the work associated with updating the Apache > Cassandra homepage and a few edits to blog posts to fix incorrect dates and > text. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17398) WEBSITE - February 2022 blog "Apache Cassandra and Java SE 11 support"
[ https://issues.apache.org/jira/browse/CASSANDRA-17398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17398: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - February 2022 blog "Apache Cassandra and Java SE 11 support" > -- > > Key: CASSANDRA-17398 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17398 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Chris Thornett >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.3 > > Attachments: c17398-01-blog-index.png, c17398-02-blog-post.png > > > This ticket is to capture the work associated with publishing the January > 2022 blog "Apache Cassandra and Java SE 11 support" > If this blog cannot be published by the *February 24, 2022 publish date*, > please contact me on ASF Slack or suggest/make changes when possible in the > pull request for the appropriate time that the blog will go live (on > blog.adoc and in the blog post .adoc). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17375) generate in-tree doc/antora.yml
[ https://issues.apache.org/jira/browse/CASSANDRA-17375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17375: --- Epic Link: (was: CASSANDRA-16761) > generate in-tree doc/antora.yml > --- > > Key: CASSANDRA-17375 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17375 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Michael Semb Wever >Assignee: Anthony Grasso >Priority: Normal > > This file contains only metadata that can be auto-generated. > Currently we can't build the website with > ``` > ANTORA_CONTENT_SOURCES_CASSANDRA_TAGS="cassandra-4.0.1 cassandra-3.11.12" > ``` > because the antora.yml files in those tags are clashing with their release > branches. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17406) WEBSITE - March 2022 blog "Apache Cassandra Changelog #13"
[ https://issues.apache.org/jira/browse/CASSANDRA-17406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17406: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - March 2022 blog "Apache Cassandra Changelog #13" > -- > > Key: CASSANDRA-17406 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17406 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Chris Thornett >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17406-01-blog-index.png, c17406-02-blog-post.png > > > This ticket is to capture the work associated with publishing the March 2022 > changelog blog #13 > If this blog cannot be published by the *March 3, 2022 publish date*, please > contact me, suggest changes, or correct the date when possible in the pull > request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17394) WEBSITE - February 2022 blog "Upgrade Advisory: 3.0, 3.11, 4.0 Possible for Remote Code Execution for Scripted UDFs"
[ https://issues.apache.org/jira/browse/CASSANDRA-17394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17394: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - February 2022 blog "Upgrade Advisory: 3.0, 3.11, 4.0 Possible for > Remote Code Execution for Scripted UDFs" > > > Key: CASSANDRA-17394 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17394 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Urgent > Labels: pull-request-available > Fix For: 3.0.0, 3.0.11, 4.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This ticket is to capture the work associated with publishing the February > 2022 blog "Upgrade Advisory: 3.0, 3.11, 4.0 Possible for Remote Code > Execution for Scripted UDFs" > If this blog cannot be published by the *February 18, 2022 publish date*, > please contact me/suggest changes when possible in the pull request for the > appropriate time that the blog will go live (on blog.adoc and in the blog > post .adoc). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17384) WEBSITE - February 2022 blog "Behind the scenes of an Apache Cassandra Release"
[ https://issues.apache.org/jira/browse/CASSANDRA-17384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17384: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - February 2022 blog "Behind the scenes of an Apache Cassandra > Release" > --- > > Key: CASSANDRA-17384 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17384 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Josh McKenzie >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17384-01-blog-index.png, c17384-02-blog-post.png > > > This ticket is to capture the work associated with publishing the January > 2022 blog "Behind the scenes of an Apache Cassandra Release" > If this blog cannot be published by the *February 17, 2022 publish date*, > please contact me/suggest changes when possible in the pull request for the > appropriate time that the blog will go live (on blog.adoc and in the blog > post .adoc). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17374) cassandra-website run.sh needs to move and prep files for content/ folder
[ https://issues.apache.org/jira/browse/CASSANDRA-17374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17374: --- Epic Link: (was: CASSANDRA-16761) > cassandra-website run.sh needs to move and prep files for content/ folder > - > > Key: CASSANDRA-17374 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17374 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Michael Semb Wever >Assignee: Anthony Grasso >Priority: Normal > Fix For: NA > > > See manual steps still required here: > https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1273-R1291 > -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17373) WEBSITE - February 2022 blog "Tightening Security for Apache Cassandra Part: 3"
[ https://issues.apache.org/jira/browse/CASSANDRA-17373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17373: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - February 2022 blog "Tightening Security for Apache Cassandra Part: > 3" > --- > > Key: CASSANDRA-17373 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17373 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez (deprecated) >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.2 > > Attachments: c17373-01-blog-index.png, c17373-02-blog-post.png > > > This ticket is to capture the work associated with publishing the January > 2022 blog "Tightening Security for Apache Cassandra Part: 3" > If this blog cannot be published by the *February 14, 2022 publish date*, > please contact me/suggest changes when possible in the pull request for the > appropriate time that the blog will go live (on blog.adoc and in the blog > post .adoc). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17343) WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 2"
[ https://issues.apache.org/jira/browse/CASSANDRA-17343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17343: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 2" > -- > > Key: CASSANDRA-17343 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17343 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17343-02-blog-post.png, c17343-examples-formatting.png > > > This ticket is to capture the work associated with publishing the January > 2022 blog "Tightening Security for Apache Cassandra Part: 2" > If this blog cannot be published by the *February 4, 2022 publish date*, > please contact me/suggest changes when possible in the pull request for the > appropriate time that the blog will go live (on blog.adoc and in the blog > post .adoc). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17317) WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 1"
[ https://issues.apache.org/jira/browse/CASSANDRA-17317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17317: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - January 2022 blog "Tightening Security for Apache Cassandra Part: 1" > -- > > Key: CASSANDRA-17317 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17317 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17317-01-blog_index.png, c17317-02-blog_post.png, > c17317-03-blog_index.png, c17317-04-blog_post.png > > > This ticket is to capture the work associated with publishing the January > 2022 blog "Tightening Security for Apache Cassandra Part: 1" > If this blog cannot be published by the *January 31, 2022 publish date*, > please contact me/suggest changes when possible in the pull request for the > appropriate time that the blog will go live (on blog.adoc and in the blog > post .adoc). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17356) WEBSITE - February 2022 changelog #12
[ https://issues.apache.org/jira/browse/CASSANDRA-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17356: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - February 2022 changelog #12 > - > > Key: CASSANDRA-17356 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17356 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez (deprecated) >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: c17356-01-blog-index.png, c17356-02-blog-post.png > > > This ticket is to capture the work associated with publishing the January > 2022 changelog blog #12 > If this blog cannot be published by the *February 10, 2022 publish date*, > please contact me, suggest changes, or correct the date when possible in the > pull request for the appropriate time that the blog will go live (on both the > blog.adoc and the blog post's file). -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16765) Update Cassandra build CI script for new website
[ https://issues.apache.org/jira/browse/CASSANDRA-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528078#comment-17528078 ] Anthony Grasso commented on CASSANDRA-16765: +1 > Update Cassandra build CI script for new website > > > Key: CASSANDRA-16765 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16765 > Project: Cassandra > Issue Type: Task > Components: Build, CI, Documentation/Website >Reporter: Anthony Grasso >Assignee: Michael Semb Wever >Priority: Normal > > Update the apache/cassandra-build repository has [.groovy job > script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy] > to use the new tooling to build the website. > The apache/cassandra-build repository has [.groovy job > script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy]. > It [builds and deploys the > website|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L1255-L1268] > to cassandra-website staging when the cassandra-website is updated. > We need to change the commands in the .groovy script to at least rebuild the > site when a change happens in the cassandra-website repository. > It would be also good to build the docs when a change happens to doc/source > directory in the cassandra repository. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17374) cassandra-website run.sh needs to move and prep files for content/ folder
[ https://issues.apache.org/jira/browse/CASSANDRA-17374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528077#comment-17528077 ] Anthony Grasso commented on CASSANDRA-17374: Thanks [~mck] . Patch added in commit [1de171b|https://github.com/apache/cassandra-website/commit/1de171b910983628e1b7e19dbeac0a3bb09dbab0] > cassandra-website run.sh needs to move and prep files for content/ folder > - > > Key: CASSANDRA-17374 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17374 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Michael Semb Wever >Assignee: Anthony Grasso >Priority: Normal > Fix For: NA > > > See manual steps still required here: > https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1273-R1291 > -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17374) cassandra-website run.sh needs to move and prep files for content/ folder
[ https://issues.apache.org/jira/browse/CASSANDRA-17374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17374: --- Fix Version/s: NA Since Version: NA Source Control Link: [1de171b|https://github.com/apache/cassandra-website/commit/1de171b910983628e1b7e19dbeac0a3bb09dbab0] Resolution: Fixed Status: Resolved (was: Ready to Commit) > cassandra-website run.sh needs to move and prep files for content/ folder > - > > Key: CASSANDRA-17374 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17374 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Michael Semb Wever >Assignee: Anthony Grasso >Priority: Normal > Fix For: NA > > > See manual steps still required here: > https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1273-R1291 > -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17550) SSTable Version documentation out of sync with code
[ https://issues.apache.org/jira/browse/CASSANDRA-17550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17550: --- Mentor: Anthony Grasso > SSTable Version documentation out of sync with code > --- > > Key: CASSANDRA-17550 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17550 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Phil Miesle >Assignee: Phil Miesle >Priority: Normal > > The website documentation around [SSTable > Versions|https://cassandra.apache.org/doc/latest/cassandra/architecture/storage_engine.html#sstable-versions] > is out of sync with the [source code > comments|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/format/big/BigFormat.java#L118], > on both the 3.11 and the current trunk branches. > As the source code appears to be kept current with the code, it would be > beneficial to keep the documentation automatically up-to-date with the source > code. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17550) SSTable Version documentation out of sync with code
[ https://issues.apache.org/jira/browse/CASSANDRA-17550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522002#comment-17522002 ] Anthony Grasso commented on CASSANDRA-17550: [~erickramirezau] the plan for this will be to automatically generate a section of the SSTable version documentation in the same way we automatically generate the nodetool help pages. The items that need to be done for this are: * Create a python script to parse the Java file and generate the ADOC * Update the SSTable version ADOC page to reference a partial ADOC file * Update website generation tooling to run the python script if it exists The script will need to live in the cassandra-3.11, cassandra-4.0, and trunk branches. > SSTable Version documentation out of sync with code > --- > > Key: CASSANDRA-17550 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17550 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Phil Miesle >Assignee: Phil Miesle >Priority: Normal > > The website documentation around [SSTable > Versions|https://cassandra.apache.org/doc/latest/cassandra/architecture/storage_engine.html#sstable-versions] > is out of sync with the [source code > comments|https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/io/sstable/format/big/BigFormat.java#L118], > on both the 3.11 and the current trunk branches. > As the source code appears to be kept current with the code, it would be > beneficial to keep the documentation automatically up-to-date with the source > code. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17517) In-tree documentation takes a long time to generate
[ https://issues.apache.org/jira/browse/CASSANDRA-17517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17517: --- Change Category: Performance Complexity: Challenging Priority: High (was: Normal) Status: Open (was: Triage Needed) > In-tree documentation takes a long time to generate > --- > > Key: CASSANDRA-17517 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17517 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: High > > To generate the in-tree documentation the website-content tooling will > execute the following steps for each branch. > # Copy or clone the Cassandra repository depending on the URL supplied > # Checkout the branch > # Select the version of Java based on the Cassandra version > # Compile Cassandra > # Generate ADOC files for Nodetool and the Cassandra YAML configuration > # Commit to repository > Once the generated ADOC files are committed to the repository, Antora is > executed to generate the HTML. > The majority of the time taken to execute the above steps is in Step 4 where > Cassandra is compiled. This time could be reduced by downloading the > precompiled binaries for branches and tags. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17517) In-tree documentation takes a long time to generate
[ https://issues.apache.org/jira/browse/CASSANDRA-17517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso reassigned CASSANDRA-17517: -- Assignee: Anthony Grasso > In-tree documentation takes a long time to generate > --- > > Key: CASSANDRA-17517 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17517 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: Normal > > To generate the in-tree documentation the website-content tooling will > execute the following steps for each branch. > # Copy or clone the Cassandra repository depending on the URL supplied > # Checkout the branch > # Select the version of Java based on the Cassandra version > # Compile Cassandra > # Generate ADOC files for Nodetool and the Cassandra YAML configuration > # Commit to repository > Once the generated ADOC files are committed to the repository, Antora is > executed to generate the HTML. > The majority of the time taken to execute the above steps is in Step 4 where > Cassandra is compiled. This time could be reduced by downloading the > precompiled binaries for branches and tags. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17517) In-tree documentation takes a long time to generate
Anthony Grasso created CASSANDRA-17517: -- Summary: In-tree documentation takes a long time to generate Key: CASSANDRA-17517 URL: https://issues.apache.org/jira/browse/CASSANDRA-17517 Project: Cassandra Issue Type: Improvement Components: Documentation/Website Reporter: Anthony Grasso To generate the in-tree documentation the website-content tooling will execute the following steps for each branch. # Copy or clone the Cassandra repository depending on the URL supplied # Checkout the branch # Select the version of Java based on the Cassandra version # Compile Cassandra # Generate ADOC files for Nodetool and the Cassandra YAML configuration # Commit to repository Once the generated ADOC files are committed to the repository, Antora is executed to generate the HTML. The majority of the time taken to execute the above steps is in Step 4 where Cassandra is compiled. This time could be reduced by downloading the precompiled binaries for branches and tags. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17374) cassandra-website run.sh needs to move and prep files for content/ folder
[
https://issues.apache.org/jira/browse/CASSANDRA-17374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Grasso updated CASSANDRA-17374:
---
Authors: Anthony Grasso (was: Anthony Grasso)
Impacts: Docs (was: None)
Mentor: Michael Semb Wever
Test and Documentation Plan:
1. Clone the cassandra-website repository.
{code:java}
$ git clone g...@github.com:apache/cassandra-website.git{code}
2. Run website generation command and include document generation.
{code:java}
$ cd cassandra-website
$ ./run.sh website build -g{code}
3. Inspect _content_ directory.
* Check if _content/doc_ directory is populated with documentation folders for
the most recent versions of Cassandra (3.11, 3.11.11, 3.11.12, 4.0, 4.0.1,
4.0.2, 4.0.3, 4.1, stable, latest, trunk)
4. Run the following commands to confirm hardcoded and missing domains have
been removed in URL links.
{code:java}
$ grep -rl 'https://cassandra.apache.org/' content/
$ grep -rl 'href="//' content/ {code}
Both commands should return an empty result.
Status: Patch Available (was: In Progress)
Opened pull request [#121|https://github.com/apache/cassandra-website/pull/121]
> cassandra-website run.sh needs to move and prep files for content/ folder
> -
>
> Key: CASSANDRA-17374
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17374
> Project: Cassandra
> Issue Type: Bug
> Components: Documentation/Website
>Reporter: Michael Semb Wever
>Assignee: Anthony Grasso
>Priority: Normal
>
> See manual steps still required here:
> https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1273-R1291
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16765) Update Cassandra build CI script for new website
[ https://issues.apache.org/jira/browse/CASSANDRA-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16765: --- Status: Ready to Commit (was: Review In Progress) Tested steps in groovy script. All commands look to be correct. This patch can be committed. > Update Cassandra build CI script for new website > > > Key: CASSANDRA-16765 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16765 > Project: Cassandra > Issue Type: Task > Components: Build, CI, Documentation/Website >Reporter: Anthony Grasso >Assignee: Michael Semb Wever >Priority: Normal > > Update the apache/cassandra-build repository has [.groovy job > script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy] > to use the new tooling to build the website. > The apache/cassandra-build repository has [.groovy job > script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy]. > It [builds and deploys the > website|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L1255-L1268] > to cassandra-website staging when the cassandra-website is updated. > We need to change the commands in the .groovy script to at least rebuild the > site when a change happens in the cassandra-website repository. > It would be also good to build the docs when a change happens to doc/source > directory in the cassandra repository. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16765) Update Cassandra build CI script for new website
[ https://issues.apache.org/jira/browse/CASSANDRA-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16765: --- Mentor: Michael Semb Wever Status: Review In Progress (was: Patch Available) > Update Cassandra build CI script for new website > > > Key: CASSANDRA-16765 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16765 > Project: Cassandra > Issue Type: Task > Components: Build, CI, Documentation/Website >Reporter: Anthony Grasso >Assignee: Michael Semb Wever >Priority: Normal > > Update the apache/cassandra-build repository has [.groovy job > script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy] > to use the new tooling to build the website. > The apache/cassandra-build repository has [.groovy job > script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy]. > It [builds and deploys the > website|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L1255-L1268] > to cassandra-website staging when the cassandra-website is updated. > We need to change the commands in the .groovy script to at least rebuild the > site when a change happens in the cassandra-website repository. > It would be also good to build the docs when a change happens to doc/source > directory in the cassandra repository. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17282) Add prompt to accept website/document sources before generating HTML
[ https://issues.apache.org/jira/browse/CASSANDRA-17282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17282: --- Change Category: Operability Complexity: Normal Fix Version/s: NA Mentor: Michael Semb Wever Reviewers: Michael Semb Wever Status: Open (was: Triage Needed) > Add prompt to accept website/document sources before generating HTML > > > Key: CASSANDRA-17282 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17282 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: Normal > Fix For: NA > > > Provide a summary of the repository and the branches/tags that will be used > as sources for Antora before any HTML generation is started. In addition, > prompt the user to accept the listed sources. > There are a number of defaults that are used which determine what is > generated by the documentation tooling. It is unclear what will be generated > exactly if the defaults are used when the script is executed. > We will need to have the ability to automatically accept changes; that is a > non-interactive option so CI can operate still. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17282) Add prompt to accept website/document sources before generating HTML
[ https://issues.apache.org/jira/browse/CASSANDRA-17282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso reassigned CASSANDRA-17282: -- Assignee: Anthony Grasso > Add prompt to accept website/document sources before generating HTML > > > Key: CASSANDRA-17282 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17282 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: Normal > > Provide a summary of the repository and the branches/tags that will be used > as sources for Antora before any HTML generation is started. In addition, > prompt the user to accept the listed sources. > There are a number of defaults that are used which determine what is > generated by the documentation tooling. It is unclear what will be generated > exactly if the defaults are used when the script is executed. > We will need to have the ability to automatically accept changes; that is a > non-interactive option so CI can operate still. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17282) Add prompt to accept website/document sources before generating HTML
Anthony Grasso created CASSANDRA-17282: -- Summary: Add prompt to accept website/document sources before generating HTML Key: CASSANDRA-17282 URL: https://issues.apache.org/jira/browse/CASSANDRA-17282 Project: Cassandra Issue Type: Task Components: Documentation/Website Reporter: Anthony Grasso Provide a summary of the repository and the branches/tags that will be used as sources for Antora before any HTML generation is started. In addition, prompt the user to accept the listed sources. There are a number of defaults that are used which determine what is generated by the documentation tooling. It is unclear what will be generated exactly if the defaults are used when the script is executed. We will need to have the ability to automatically accept changes; that is a non-interactive option so CI can operate still. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16867) DOC - Documentation page for Hints has a broken table
[ https://issues.apache.org/jira/browse/CASSANDRA-16867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16867: --- Epic Link: (was: CASSANDRA-16761) > DOC - Documentation page for Hints has a broken table > - > > Key: CASSANDRA-16867 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16867 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Andy Moore >Assignee: Erick Ramirez >Priority: Low > > The Cassandra Documentation page for Hints: > [https://cassandra.apache.org/doc/latest/cassandra/operating/hints.html] > has a problem with Table 1: Settings for Hints. > On the second row of the table, part of the Description column, the example, > has "wrapped" into the next Cell in the second row, in the Default Value > column. > > This has then resulted in all the following cells from the third row onwards > being bumped along one Cell. > > The Setting Column contains the value of the Default Value Column from the > previous row > The Description Column contains the value of the Setting Column > The Default Value Column contains the value of the Description Column -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16821) Documentation links broken, indexed by Google
[ https://issues.apache.org/jira/browse/CASSANDRA-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16821: --- Epic Link: (was: CASSANDRA-16761) > Documentation links broken, indexed by Google > - > > Key: CASSANDRA-16821 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16821 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Abe Ratnofsky >Assignee: Michael Semb Wever >Priority: Normal > Fix For: 4.0.1 > > > Internal documentation links like > [https://cassandra.apache.org/doc/latest/operating/compaction/index.html] are > now returning 404s. These links originate from within documentation > (referenced from [https://cassandra.apache.org/doc/latest/)] and are indexed > by Google (first result for "apache cassandra compaction", for example). > These links were working correctly as recently as late 2020: > https://web.archive.org/web/20201020194414/https://cassandra.apache.org/doc/latest/operating/compaction/index.html -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16829) WEBSITE - August 2021 updates
[ https://issues.apache.org/jira/browse/CASSANDRA-16829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16829: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - August 2021 updates > - > > Key: CASSANDRA-16829 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16829 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Assignee: Paul Au >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.1, 4.0 > > Attachments: Apache Cassandra Antora Site Updates.zip > > > Updates to be made to the website that include: > * add blog post: Apache-Cassandra-4.0-Overview.adoc to pages/blog > * added Apache Cassandra 4.0 Overview card to blog page > * If unable to post on August 6, 2021, the above will need an edit to publish > dates > * added case study for Stibo Systems to case studies page > * add 4.0-overview-1.png and 4.0-overview-2.png to images/blog > * add stibo-systems.png to images/companies > * instagram.*png* to replace instagram.*jpg* in images/companies > * corrected logo for Instagram and added Stibo Systems logo to home page index > * corrected logo for Instagram and added Stibo Systems logo to case studies > page -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16838) DOC - Broken link to contribution on community page
[
https://issues.apache.org/jira/browse/CASSANDRA-16838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Grasso updated CASSANDRA-16838:
---
Epic Link: (was: CASSANDRA-16761)
> DOC - Broken link to contribution on community page
> ---
>
> Key: CASSANDRA-16838
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16838
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Ruslan Fomkin
>Priority: Normal
> Fix For: 4.0.1
>
>
> Becoming a contributor in [How to
> Contribute|https://cassandra.apache.org/_/community.html#how-to-contribute]
> section contains link under {{contribute to Cassandra}}, which leads to
> cannot find the server and the link is
> [https://doc/latest/development/index.html]
>
> The issue is probably due to extra / in
>
[jira] [Updated] (CASSANDRA-16766) Development docs are not upto to date
[
https://issues.apache.org/jira/browse/CASSANDRA-16766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Grasso updated CASSANDRA-16766:
---
Epic Link: (was: CASSANDRA-16761)
> Development docs are not upto to date
> -
>
> Key: CASSANDRA-16766
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16766
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation/Website
>Reporter: Jogesh Anand
>Priority: Normal
> Labels: low-hanging-fruit
>
> The latest developers guide for unit testing isn't accurate
> [link|https://cassandra.apache.org/doc/latest/development/testing.html]
> For e.g
> {code:java}
> ant test -Dtest.name=
> {code}
> isn't valid. It's now
> {code:java}
> ant testsome -Dtest.name=
> {code}
> Similarly, we also have `ant long-testsome` & `ant burn-testsome` for e.g. I
> would be nice to have these documented as well for developers or users.
> AC:
> * The website accurately represents all testing scenarios present in
> build.xml or otherwise.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16889) WEBSITE - August 2021 updates #2
[ https://issues.apache.org/jira/browse/CASSANDRA-16889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16889: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - August 2021 updates #2 > > > Key: CASSANDRA-16889 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16889 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Assignee: Paul Au >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.2, 4.1 > > Attachments: Apache Cassandra Antora Site Updates.zip, > case-studies.adoc > > > Updates to be made to the website that include: > * Add blog post: Cassandra-on-Kubernetes-A-Beginners-Guide to pages/blog > * Added Cassandra-on-Kubernetes-A-Beginners-Guide card to blog index > * Changed Urban Airship to Airship on the case studies page > * Changed the contributor meetings learn more link on the community page > * Replace images/companies backblaze.png with the new logo attached with the > same name > * Removed Comcast logo from main page index > * Removed Comcast from case studies page > * Removed Yelp from Apache Cassandra 4.0 is Here blog -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16891) WEBSITE - Update supported versions, mark 2.2 as EOL
[
https://issues.apache.org/jira/browse/CASSANDRA-16891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Grasso updated CASSANDRA-16891:
---
Epic Link: (was: CASSANDRA-16761)
> WEBSITE - Update supported versions, mark 2.2 as EOL
>
>
> Key: CASSANDRA-16891
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16891
> Project: Cassandra
> Issue Type: Task
> Components: Legacy/Documentation and Website
>Reporter: Erick Ramirez
>Assignee: Paul Au
>Priority: Normal
> Fix For: 4.0.2, 4.1
>
> Attachments: CASSANDRA-16891-download-page.png
>
>
> The [Download|https://cassandra.apache.org/_/download.html] page incorrectly
> lists Cassandra 2.2 as:
> {quote}Apache Cassandra 2.2
> Released on 2020-11-04, and supported until 4.1 release (April 2022) with
> critical fixes only
> {quote}
> At this point, only Cassandra 3.0 is supported until the 4.1 release.
>
> !CASSANDRA-16891-download-page.png|width=300!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16890) WEBSITE - Remove section with company logos from homepage
[ https://issues.apache.org/jira/browse/CASSANDRA-16890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16890: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Remove section with company logos from homepage > - > > Key: CASSANDRA-16890 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16890 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Paul Au >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.2, 4.1 > > Attachments: Apache-Cassandra-Apache-Cassandra-Documentation.png > > > [~mck] advised that the company logos on the homepage are a breach of ASF > policy so will need to be removed. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16899) Change select wording to be more inclusive
[ https://issues.apache.org/jira/browse/CASSANDRA-16899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17480783#comment-17480783 ] Anthony Grasso commented on CASSANDRA-16899: [~jjirsa] CASSANDRA-16763 has now been merged. Let me know if you have time to re-do the patch. > Change select wording to be more inclusive > -- > > Key: CASSANDRA-16899 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16899 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Jeff Jirsa >Assignee: Jeff Jirsa >Priority: Normal > > The conscious language checker has flagged a few thousand places where we are > using words that may be insensitive or undesirable. > https://clc.diversity.apache.org/analysis.html?project=cassandra.git > This ticket will address the non-code comment text as a first pass. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16876) WEBSITE - Jumbled contents in doc/4.0/cassandra/configuration/cass_yaml_file.html
[ https://issues.apache.org/jira/browse/CASSANDRA-16876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16876: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Jumbled contents in > doc/4.0/cassandra/configuration/cass_yaml_file.html > - > > Key: CASSANDRA-16876 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16876 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Stefano Lottini >Assignee: Erick Ramirez >Priority: Normal > Fix For: 4.0.x > > Attachments: c4_doc.png > > > The page at > [https://cassandra.apache.org/doc/4.0/cassandra/configuration/cass_yaml_file.html#commitlog_directory] > seems to have published a portion of a Git merge annotation which renders > the formatting incorrect. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16870) Secure HTTPS link to the research paper in the website landing page
[ https://issues.apache.org/jira/browse/CASSANDRA-16870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16870: --- Epic Link: (was: CASSANDRA-16761) > Secure HTTPS link to the research paper in the website landing page > --- > > Key: CASSANDRA-16870 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16870 > Project: Cassandra > Issue Type: Bug >Reporter: Karuppiah Natarajan >Assignee: Karuppiah Natarajan >Priority: Normal > Attachments: extra-details-about-security-risk.png, > security-risk-warning.png > > > In [https://cassandra.apache.org/_/index.html] , under the Performant > section, there's a link to a research paper - > [http://vldb.org/pvldb/vol5/p1724_tilmannrabl_vldb2012.pdf] - "Solving Big > Data Challenges for Enterprise Application Performance Management". But this > link is a HTTP link. On clicking this, my browser shows me a security > warning. This is how it looks like on Firefox - > !security-risk-warning.png|width=450,height=75! > and some more details - > !extra-details-about-security-risk.png|width=351,height=259! > I noticed that the same research paper has an alternative HTTPS URL. I think > that could be used instead - > [https://vldb.org/pvldb/vol5/p1724_tilmannrabl_vldb2012.pdf] > I would love to make this small fix in the docs -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16899) Change select wording to be more inclusive
[ https://issues.apache.org/jira/browse/CASSANDRA-16899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16899: --- Epic Link: (was: CASSANDRA-16761) > Change select wording to be more inclusive > -- > > Key: CASSANDRA-16899 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16899 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Jeff Jirsa >Assignee: Jeff Jirsa >Priority: Normal > > The conscious language checker has flagged a few thousand places where we are > using words that may be insensitive or undesirable. > https://clc.diversity.apache.org/analysis.html?project=cassandra.git > This ticket will address the non-code comment text as a first pass. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16964) WEBSITE - September 2021 blog post on Reaper
[ https://issues.apache.org/jira/browse/CASSANDRA-16964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16964: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - September 2021 blog post on Reaper > > > Key: CASSANDRA-16964 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16964 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Anthony Grasso >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.2, 4.1 > > Attachments: CASSANDRA-16964-blog-index-v2.png, > CASSANDRA-16964-blog-index.png, CASSANDRA-16964-blogpost-page1.png, > CASSANDRA-16964-blogpost-page2.png, CASSANDRA-16964-blogpost-page3.png, > CASSANDRA-16964-blogpost-page4.png > > > This ticket is to capture the work associated with publishing the August 2021 > blog post. In the blog post we will cover the topic of Reaper and repairs. > We can close this once the blog post has gone live on the website. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16994) WEBSITE - September 2021 website edits
[ https://issues.apache.org/jira/browse/CASSANDRA-16994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16994: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - September 2021 website edits > -- > > Key: CASSANDRA-16994 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16994 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.x > > > Edits and fixes for formatting and typos across the website. > Can be closed upon merged changes. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16982) WEBSITE - Autogenerate blog index
[ https://issues.apache.org/jira/browse/CASSANDRA-16982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16982: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Autogenerate blog index > - > > Key: CASSANDRA-16982 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16982 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Anthony Grasso >Priority: Normal > > h1. Summary > Enhance the website generation so that the blog index page is automatically > populated based on the contents of the blog folder. > h1. Details > When an author needs to add a blog post, they need to update the blog index > page as well as add the new post. This can be tedious for new contributors > and in general is error prone. > We need to add the ability to autogenerate the blog index page when the > website is rendered. > This might be possible through the use of a JS function that is registered > with Antora and called when it runs. The JS function could generate the blog > index page from the contents of the blog directory and information in each of > the blogs. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16980) WEBSITE - September 2021 blog post on ApacheCon
[ https://issues.apache.org/jira/browse/CASSANDRA-16980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-16980: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - September 2021 blog post on ApacheCon > --- > > Key: CASSANDRA-16980 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16980 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Anthony Grasso >Priority: Urgent > Labels: pull-request-available > Fix For: NA > > Attachments: CASSANDRA-16980-blog-01-index_listing.png, > CASSANDRA-16980-blog-02-post.png > > > This ticket is to capture the work associated with publishing the September > 2021 blog post on ApacheCon 2021. > We can close this once the blog post has gone live on the website. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17060) WEBSITE - October 2021 blog post for What the Future Holds for Apache Cassandra and Apache Cassandra Changelog #10 formatting errors fix
[ https://issues.apache.org/jira/browse/CASSANDRA-17060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17060: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - October 2021 blog post for What the Future Holds for Apache > Cassandra and Apache Cassandra Changelog #10 formatting errors fix > > > Key: CASSANDRA-17060 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17060 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Urgent > Labels: pull-request-available > Fix For: 4.0.2, 4.1 > > Attachments: CASSANDRA-17060-blog-what_the_future_holds.png > > > This ticket is to capture the work associated with publishing the October > 2021 blog post for "What the Future Holds for Apache Cassandra." > If this blog cannot be published by the October 26 publish date, please be > sure to correct the date before going live. > Also added formatting errors fix for Apache Cassandra Changelog #10 > We can close this once the blog post and fixes have gone live on the website. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17061) DOC - Fix multiple headers, formatting on Monitoring page
[ https://issues.apache.org/jira/browse/CASSANDRA-17061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17061: --- Epic Link: (was: CASSANDRA-16761) > DOC - Fix multiple headers, formatting on Monitoring page > - > > Key: CASSANDRA-17061 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17061 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Erick Ramirez >Assignee: Erick Ramirez >Priority: Normal > Fix For: 4.x > > Attachments: website-monitoring-01-table_metrics.png, > website-monitoring-02-keyspace_metrics.png > > > [~azotcsit] reported on [ASF > Slack|https://the-asf.slack.com/archives/C01RY1LUPD5/p1635066428010900] that > several sections are formatted incorrectly on the > [Monitoring|https://cassandra.apache.org/doc/latest/cassandra/operating/metrics.html] > page. > For example, the *Table Metrics* section appears as: > !website-monitoring-01-table_metrics.png|width=300! > The following sections don't render correctly: > * Keyspace Metrics > * Threadpool Metrics > * Client Request Metrics > * Cache Metrics > For example: > !website-monitoring-02-keyspace_metrics.png|width=300! -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17018) WEBSITE - October 2021 blog post for Apache Cassandra Changelog #10
[ https://issues.apache.org/jira/browse/CASSANDRA-17018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17018: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - October 2021 blog post for Apache Cassandra Changelog #10 > --- > > Key: CASSANDRA-17018 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17018 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > This ticket is to capture the work associated with publishing the October > 2021 blog post for the Apache Cassandra Changelog #10. > We can close this once the blog post has gone live on the website. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17203) Broken API link on Cassandra Cloud Offering page
[ https://issues.apache.org/jira/browse/CASSANDRA-17203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17203: --- Epic Link: (was: CASSANDRA-16761) > Broken API link on Cassandra Cloud Offering page > > > Key: CASSANDRA-17203 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17203 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Blog >Reporter: Chris Thornett >Assignee: Diogenese Topper >Priority: Normal > > In the Cassandra document page: > [https://cassandra.apache.org/_/ecosystem.html,] the API link for Azure > Cosmos DB Cassandra API is broken because of incorrect asciidoc formatting, > see below: > https://docs.microsoft.com/en-us/azure/cosmos-db/cassandra-introduction[Azure > Cosmos DB Cassandra API,window=_blank]: Enables you to interact with data > stored in https://docs.microsoft.com/en-us/azure/cosmos-db/introduction[Azure > Cosmos DB,window=_blank] using the Cassandra Query Language (CQL) , > Cassandra-based tools (like cqlsh) and Cassandra client drivers that you're > already familiar with. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17066) Blog post: "Harry: A Fuzz Testing Tool for Apache Cassandra"
[ https://issues.apache.org/jira/browse/CASSANDRA-17066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17066: --- Epic Link: (was: CASSANDRA-16761) > Blog post: "Harry: A Fuzz Testing Tool for Apache Cassandra" > > > Key: CASSANDRA-17066 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17066 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Alex Petrov >Assignee: Alex Petrov >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.2, 4.1 > > Attachments: c17066-01-blog-index.png, c17066-02-blog-post.png, > c17066-03-blog-post-v2.png > > > This ticket is to capture the work associated with publishing the November > 2021 blog post titled "Harry, an Open Source Fuzz Testing and Verification > Tool for Apache Cassandra." > If this blog cannot be published by the November 9 publish date, please be > sure to *correct the date* before going live. > This ticket can be closed once the blog post has gone live on the website. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17219) WEBSITE - December 2021 blog post titled "Using Arithmetic Operators in Cassandra 4.0"
[ https://issues.apache.org/jira/browse/CASSANDRA-17219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17219: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - December 2021 blog post titled "Using Arithmetic Operators in > Cassandra 4.0" > -- > > Key: CASSANDRA-17219 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17219 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Urgent > Labels: pull-request-available, pull-requests-available, > pull_request_available > Fix For: 4.0.2, 4.1 > > Attachments: c17219-01-bad_table_title.png, > c17219-02-table_title_with_blank_line.png, c17219-03-blog_index.png, > c17219-04-blog_post.png, c17219-05-table_title_fixed.png > > > This ticket is to capture the work associated with publishing the December > 2021 blog post for "Using Arithmetic Operators in Cassandra 4.0" > If this blog cannot be published by the *December 21, 2021 publish date*, > please *correct the date before going live* (on blog.adoc and in the blog). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17157) WEBSITE - November 2021 blog post titled Inside Cassandra: an interview with Marcel Birkner at Instana
[ https://issues.apache.org/jira/browse/CASSANDRA-17157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17157: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - November 2021 blog post titled Inside Cassandra: an interview with > Marcel Birkner at Instana > -- > > Key: CASSANDRA-17157 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17157 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Urgent > Labels: pull-request-available, pull-requests-available > Fix For: 4.0.2, 4.1 > > Attachments: c17157-01-blog-index.png, c17157-02-blog-post.png > > > This ticket is to capture the work associated with publishing the November > 2021 blog post for "Inside Cassandra: an interview with Marcel Birkner at > Instana." > If this blog cannot be published by the *November 17 publish date*, please be > sure to *correct the date before going live*. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17260) Antora site.yml in-tree so in-tree html can be generated (again)
[ https://issues.apache.org/jira/browse/CASSANDRA-17260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17260: --- Epic Link: (was: CASSANDRA-16761) > Antora site.yml in-tree so in-tree html can be generated (again) > > > Key: CASSANDRA-17260 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17260 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Michael Semb Wever >Priority: Normal > > With the migration of the doc to asciidoc and antora we (intentionally) lost > the ability to generate in-tree html via `ant gen-doc`. > This was intentional as our first priority was publishing the docs to the > website. > But it is also beneficial to have plain html docs bundled into our packages > (tar, deb, rpm, docker, etc), so tackling this was expected and planned for a > later date. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17259) WEBSITE - January 2022 changelog #11
[ https://issues.apache.org/jira/browse/CASSANDRA-17259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17259: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - January 2022 changelog #11 > > > Key: CASSANDRA-17259 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17259 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Diogenese Topper >Priority: Normal > Labels: pull-request-available, pull_request_available > Fix For: NA > > Attachments: c17259-01-blog-index.png, c17259-02-blog-post.png, > c17259-03-blog-index.png, c17259-04-blog-post.png > > > This ticket is to capture the work associated with publishing the January > 2022 changelog blog #11 > If this blog cannot be published by the *January 18, 2022 publish date*, > please contact me, suggest changes, or correct the date yourself when > possible in the pull request for the appropriate time that the blog will go > live (on blog.adoc and in the blog). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17228) WEBSITE - December 2021 blog post titled "Configurable Storage Ports and Why We Need Them"
[ https://issues.apache.org/jira/browse/CASSANDRA-17228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17228: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - December 2021 blog post titled "Configurable Storage Ports and Why > We Need Them" > -- > > Key: CASSANDRA-17228 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17228 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.2, 4.1 > > Attachments: c17228-01-blog_post.png > > > This ticket is to capture the work associated with publishing the December > 2021 blog post for "Configurable Storage Ports and Why We Need Them" > If this blog cannot be published by the *December 28, 2021 publish date*, > please contact me, suggest changes, or correct the date yourself when > possible in the pull request for the appropriate time that the blog will go > live (on blog.adoc and in the blog). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17264) WEBSITE - Fix broken links
[ https://issues.apache.org/jira/browse/CASSANDRA-17264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17264: --- Epic Link: (was: CASSANDRA-16761) > WEBSITE - Fix broken links > -- > > Key: CASSANDRA-17264 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17264 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Paul Au >Assignee: Paul Au >Priority: Normal > Labels: pull-request-available > Fix For: 4.0 > > > Scans of the Apache Cassandra website revealed some broken links. See link: > [https://lists.apache.org/thread/3qtxndr4bxw5xo9gshrl4t2vyk4ym8o1] > > These links are found in both the template files as well as the adoc files. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17274) Broken link for contribute to cassandra on community page
[ https://issues.apache.org/jira/browse/CASSANDRA-17274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17274: --- Epic Link: (was: CASSANDRA-16761) > Broken link for contribute to cassandra on community page > - > > Key: CASSANDRA-17274 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17274 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Yash Ladha >Assignee: Yash Ladha >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: image-2022-01-21-10-45-44-885.png > > > When visiting the community page of cassandra and going to `How to > contribute` session the link is not rendered properly. > !image-2022-01-21-10-45-44-885.png! > > We can see that _contribute to Cassandra_ is a simple text instead of a blank > link tag. > > Cause for the issue was in content we were using the URL macro but instead > have to use link macro. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17275) FAQ page contains bullet list of div tags
[ https://issues.apache.org/jira/browse/CASSANDRA-17275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso reassigned CASSANDRA-17275: -- Assignee: Andrew Hogg (was: Anthony Grasso) > FAQ page contains bullet list of div tags > - > > Key: CASSANDRA-17275 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17275 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Andrew Hogg >Assignee: Andrew Hogg >Priority: Normal > Fix For: 3.11.x, 4.0.x > > Attachments: Screenshot 2022-01-21 at 10.28.16.png > > Time Spent: 10m > Remaining Estimate: 0h > > Within the versioned documentation, the FAQ page has a bullet list at the top > which relates to the div's within the layout that is used for navigation. > This bullet list is not a set of hyperlinks / clickable, they are just shown. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17275) FAQ page contains bullet list of div tags
[ https://issues.apache.org/jira/browse/CASSANDRA-17275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso reassigned CASSANDRA-17275: -- Assignee: Anthony Grasso (was: Andrew Hogg) > FAQ page contains bullet list of div tags > - > > Key: CASSANDRA-17275 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17275 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Andrew Hogg >Assignee: Anthony Grasso >Priority: Normal > Fix For: 3.11.x, 4.0.x > > Attachments: Screenshot 2022-01-21 at 10.28.16.png > > Time Spent: 10m > Remaining Estimate: 0h > > Within the versioned documentation, the FAQ page has a bullet list at the top > which relates to the div's within the layout that is used for navigation. > This bullet list is not a set of hyperlinks / clickable, they are just shown. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17275) FAQ page contains bullet list of div tags
[ https://issues.apache.org/jira/browse/CASSANDRA-17275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17275: --- Reviewers: Anthony Grasso, Anthony Grasso Anthony Grasso, Anthony Grasso (was: Anthony Grasso) Status: Review In Progress (was: Patch Available) > FAQ page contains bullet list of div tags > - > > Key: CASSANDRA-17275 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17275 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Andrew Hogg >Assignee: Anthony Grasso >Priority: Normal > Fix For: 3.11.x, 4.0.x > > Attachments: Screenshot 2022-01-21 at 10.28.16.png > > Time Spent: 10m > Remaining Estimate: 0h > > Within the versioned documentation, the FAQ page has a bullet list at the top > which relates to the div's within the layout that is used for navigation. > This bullet list is not a set of hyperlinks / clickable, they are just shown. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17275) FAQ page contains bullet list of div tags
[ https://issues.apache.org/jira/browse/CASSANDRA-17275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso updated CASSANDRA-17275: --- Bug Category: Parent values: Documentation(13562) Complexity: Low Hanging Fruit Discovered By: User Report Fix Version/s: 3.11.x 4.0.x Severity: Normal Status: Open (was: Triage Needed) > FAQ page contains bullet list of div tags > - > > Key: CASSANDRA-17275 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17275 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Andrew Hogg >Assignee: Andrew Hogg >Priority: Normal > Fix For: 3.11.x, 4.0.x > > Attachments: Screenshot 2022-01-21 at 10.28.16.png > > > Within the versioned documentation, the FAQ page has a bullet list at the top > which relates to the div's within the layout that is used for navigation. > This bullet list is not a set of hyperlinks / clickable, they are just shown. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17228) WEBSITE - December 2021 blog post titled "Configurable Storage Ports and Why We Need Them"
[ https://issues.apache.org/jira/browse/CASSANDRA-17228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17475131#comment-17475131 ] Anthony Grasso commented on CASSANDRA-17228: [~diotopper] great post! I added suggested changes to the pull request. There are few small typos we should probably fix before we push this out. > WEBSITE - December 2021 blog post titled "Configurable Storage Ports and Why > We Need Them" > -- > > Key: CASSANDRA-17228 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17228 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > Fix For: 4.0.2, 4.1 > > Attachments: c17228-01-blog_post.png > > > This ticket is to capture the work associated with publishing the December > 2021 blog post for "Configurable Storage Ports and Why We Need Them" > If this blog cannot be published by the *December 28, 2021 publish date*, > please contact me, suggest changes, or correct the date yourself when > possible in the pull request for the appropriate time that the blog will go > live (on blog.adoc and in the blog). -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16765) Update Cassandra build CI script for new website
[
https://issues.apache.org/jira/browse/CASSANDRA-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472437#comment-17472437
]
Anthony Grasso commented on CASSANDRA-16765:
> {color:#505f79}_It might be cumbersome to have to update the file after every
> release. Releases are a lot more frequent than release branches._{color}
{color:#505f79}_Is there a way that the run.sh could detect all releases
(>=3.11.2, >=4.0.2) ?_{color}
Yes, {{run.sh}} could detect releases. We do something similar in the [Anotra
YAML generation
script|https://github.com/apache/cassandra-website/blob/trunk/site-content/bin/site_yaml_generator.py#L35-L45].
However, I think I misunderstand the problem. My current understanding was we
generate documents for each branch (i.e. major version; 3.11, 4.0, etc).
I need help understanding the problem we want to solve. Do we want to build the
docs for each branch and tag (i.e. minor release version; 3.11.11, 4.0.1, etc)
or a subset of that?
> Update Cassandra build CI script for new website
>
>
> Key: CASSANDRA-16765
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16765
> Project: Cassandra
> Issue Type: Task
> Components: Build, CI, Documentation/Website
>Reporter: Anthony Grasso
>Assignee: Michael Semb Wever
>Priority: Normal
>
> Update the apache/cassandra-build repository has [.groovy job
> script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy]
> to use the new tooling to build the website.
> The apache/cassandra-build repository has [.groovy job
> script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy].
> It [builds and deploys the
> website|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L1255-L1268]
> to cassandra-website staging when the cassandra-website is updated.
> We need to change the commands in the .groovy script to at least rebuild the
> site when a change happens in the cassandra-website repository.
> It would be also good to build the docs when a change happens to doc/source
> directory in the cassandra repository.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16765) Update Cassandra build CI script for new website
[
https://issues.apache.org/jira/browse/CASSANDRA-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472433#comment-17472433
]
Anthony Grasso commented on CASSANDRA-16765:
> {color:#505f79}_Can we spin off separate tickets? The CI patch can go in, and
> get updates latter on._{color}
Works for me. I will complete the review of the CI changes. We can then work on
removing the CI hacks and fixing generation of the robots.txt, .htaccess, and
sitemap.xml files.
> Update Cassandra build CI script for new website
>
>
> Key: CASSANDRA-16765
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16765
> Project: Cassandra
> Issue Type: Task
> Components: Build, CI, Documentation/Website
>Reporter: Anthony Grasso
>Assignee: Michael Semb Wever
>Priority: Normal
>
> Update the apache/cassandra-build repository has [.groovy job
> script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy]
> to use the new tooling to build the website.
> The apache/cassandra-build repository has [.groovy job
> script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy].
> It [builds and deploys the
> website|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L1255-L1268]
> to cassandra-website staging when the cassandra-website is updated.
> We need to change the commands in the .groovy script to at least rebuild the
> site when a change happens in the cassandra-website repository.
> It would be also good to build the docs when a change happens to doc/source
> directory in the cassandra repository.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16765) Update Cassandra build CI script for new website
[
https://issues.apache.org/jira/browse/CASSANDRA-16765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17471808#comment-17471808
]
Anthony Grasso commented on CASSANDRA-16765:
[~mck] , good questions in the previous two comments. I will start work on
updates to the cassandra-website tooling with the aim of removing hacks and
hardcoded issues in the CI build.
See my comments below for answers to some of the questions raised.
{quote}the branches we can build in-tree docs becomes hardcoded in the jenkins
config, both in what to build] and in what changes to listen for to trigger off
a build,
{quote}
We can remove the hard coded versions from the [Jenkins
file|https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/16765#diff-1f760d89dfb81ea05a11d862007a4e4e586b38aac7ae87f62c5b2e86571809c0R1270].
The default documentation branches to generate are specified in the [content
container environment
variables|https://github.com/apache/cassandra-website/blob/trunk/site-content/Dockerfile#L93].
In addition, we can remove the hardcoded UI bundle ZIP file path from the
command as well. That line should be able to collapse down to something that
looks like this
{code:java}
./run.sh website container -a BUILD_USER_ARG:`whoami` -a UID_ARG:`id -u` -a
GID_ARG:`id -g` ;
./run.sh website build -g;
{code}
What changes to listen for will have to remain in Jenkins. The triggering of CI
is outside the scope of the {{run.sh}} script.
{quote}no released versions are listed, i.e. git tags. how will they be
introduced into this line
{quote}
If we want to build a new version of the docs, we would update the [content
container environment
variables|https://github.com/apache/cassandra-website/blob/trunk/site-content/Dockerfile#L93].
In this way, CI remains untouched and what to build remains in a single
repository.
{quote}the notions of stable and latest docs are hardcoded by jenkins here, is
this something that can be put into antora?
{quote}
This is a very good point. I believe this is something Antora can do. We should
be able to control this in the [Antora YAML template
file|https://github.com/apache/cassandra-website/blob/trunk/site-content/site.template.yaml#L41].
I will need to speak to [~polandll] about this.
{quote}we need to switch references from /doc/latest to /doc/stable
{quote}
This should be a quick fix.
{quote}robots.txt, .htaccess, and sitemap.xml were missing. manually added back
in with this commit, but this should be part of antora generation
{quote}
Agreed. I will discuss with [~polandll] first about how we could make these
changes. We may need to involve [~paul-travers-todd] as well.
{quote}all the hack steps need to solved and/or part of the run.sh
{quote}
Agreed. I will work out what Antora can do for us automatically, then offload
the remaining tasks to the {{run.sh}} script.
> Update Cassandra build CI script for new website
>
>
> Key: CASSANDRA-16765
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16765
> Project: Cassandra
> Issue Type: Task
> Components: Build, CI, Documentation/Website
>Reporter: Anthony Grasso
>Assignee: Michael Semb Wever
>Priority: Normal
>
> Update the apache/cassandra-build repository has [.groovy job
> script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy]
> to use the new tooling to build the website.
> The apache/cassandra-build repository has [.groovy job
> script|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy].
> It [builds and deploys the
> website|https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy#L1255-L1268]
> to cassandra-website staging when the cassandra-website is updated.
> We need to change the commands in the .groovy script to at least rebuild the
> site when a change happens in the cassandra-website repository.
> It would be also good to build the docs when a change happens to doc/source
> directory in the cassandra repository.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16763) Create Cassandra documentation content for new website
[
https://issues.apache.org/jira/browse/CASSANDRA-16763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462622#comment-17462622
]
Anthony Grasso edited comment on CASSANDRA-16763 at 12/20/21, 1:55 PM:
---
Updated cassandra trunk, cassandra-4.0, and cassandra-3.11 patches.
* Removed generated nodetool and Cassandra configuration pages
* Removed files that had been incorrectly added or modified outside of the
_doc_ directory
Updated cassandra-website tooling.
||Branch||Patch||
|trunk|[#85|https://github.com/apache/cassandra-website/pull/85]|
Changes for the above patch are:
* Removed the {{-i}} and {{-n}} options from the {{./run.sh}} script. Removing
the generated pages from the Cassandra repository makes these options redundant.
* README. md has been updated to reflect changes to {{./run.sh}}
* Changed site-content Docker file.
** Installed JDK 11 for compiling trunk and cassandra-4.0 branches.
** Made 'build' user a sudo user so it can switch the Java version depending
on which branch it is compiling.
* Changed the documentation generation function in the docker-entrypoint.sh.
** Always makes a copy of the repository if is supplied from the local host
calling the container.
** Select the version of JDK to use based on the version of Cassandra being
built.
was (Author: anthony grasso):
Updated cassandra trunk, cassandra-4.0, and cassandra-3.11 patches.
* Removed generated nodetool and Cassandra configuration pages
* Removed files that had been incorrectly added or modified outside of the
_doc_ directory
Updated cassandra-website tooling.
||Branch||Patch||
|trunk|[#85\|https://github.com/apache/cassandra-website/pull/85]|
Changes for the above patch are:
* Removed the {{-i}} and {{-n}} options from the {{./run.sh}} script. Removing
the generated pages from the Cassandra repository makes these options redundant.
* README. md has been updated to reflect changes to {{./run.sh}}
* Changed site-content Docker file.
** Installed JDK 11 for compiling trunk and cassandra-4.0 branches.
** Made 'build' user a sudo user so it can switch the Java version depending
on which branch it is compiling.
* Changed the documentation generation function in the docker-entrypoint.sh.
** Always makes a copy of the repository if is supplied from the local host
calling the container.
** Select the version of JDK to use based on the version of Cassandra being
built.
> Create Cassandra documentation content for new website
> --
>
> Key: CASSANDRA-16763
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16763
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Anthony Grasso
>Assignee: Michael Semb Wever
>Priority: High
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We need create the content (asciidoc) to render the Cassandra documentation
> using Antora. This work can commence once the following has happened:
> * Website and documentation proof of concept is done - CASSANDRA-16029
> * Website design and concept is done - CASSANDRA-16115
> * Website and document tooling is done - CASSANDRA-16066
> * Website UI components are done - CASSANDRA-16762
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16763) Create Cassandra documentation content for new website
[
https://issues.apache.org/jira/browse/CASSANDRA-16763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17462622#comment-17462622
]
Anthony Grasso commented on CASSANDRA-16763:
Updated cassandra trunk, cassandra-4.0, and cassandra-3.11 patches.
* Removed generated nodetool and Cassandra configuration pages
* Removed files that had been incorrectly added or modified outside of the
_doc_ directory
Updated cassandra-website tooling.
||Branch||Patch||
|trunk|[#85\|https://github.com/apache/cassandra-website/pull/85]|
Changes for the above patch are:
* Removed the {{-i}} and {{-n}} options from the {{./run.sh}} script. Removing
the generated pages from the Cassandra repository makes these options redundant.
* README. md has been updated to reflect changes to {{./run.sh}}
* Changed site-content Docker file.
** Installed JDK 11 for compiling trunk and cassandra-4.0 branches.
** Made 'build' user a sudo user so it can switch the Java version depending
on which branch it is compiling.
* Changed the documentation generation function in the docker-entrypoint.sh.
** Always makes a copy of the repository if is supplied from the local host
calling the container.
** Select the version of JDK to use based on the version of Cassandra being
built.
> Create Cassandra documentation content for new website
> --
>
> Key: CASSANDRA-16763
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16763
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Anthony Grasso
>Assignee: Michael Semb Wever
>Priority: High
> Labels: pull-request-available
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> We need create the content (asciidoc) to render the Cassandra documentation
> using Antora. This work can commence once the following has happened:
> * Website and documentation proof of concept is done - CASSANDRA-16029
> * Website design and concept is done - CASSANDRA-16115
> * Website and document tooling is done - CASSANDRA-16066
> * Website UI components are done - CASSANDRA-16762
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16913) Fix incorrect UI bundle URL in content Dockerfile
[ https://issues.apache.org/jira/browse/CASSANDRA-16913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso reassigned CASSANDRA-16913: -- Assignee: Michael Semb Wever (was: Anthony Grasso) > Fix incorrect UI bundle URL in content Dockerfile > - > > Key: CASSANDRA-16913 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16913 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Michael Semb Wever >Priority: High > Labels: pull-request-available > > We need to change the UI bundle URL in the content container Dockerfile to > point to a UI bundle that contains the correct site styling. > The URL to the bundle can be updated only after an initial version of the UI > bundle is tagged and released on the cassandra-website. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16913) Fix incorrect UI bundle URL in content Dockerfile
[ https://issues.apache.org/jira/browse/CASSANDRA-16913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456459#comment-17456459 ] Anthony Grasso commented on CASSANDRA-16913: Minor update associated with suggested change in pull request. > Fix incorrect UI bundle URL in content Dockerfile > - > > Key: CASSANDRA-16913 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16913 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Anthony Grasso >Priority: High > Labels: pull-request-available > > We need to change the UI bundle URL in the content container Dockerfile to > point to a UI bundle that contains the correct site styling. > The URL to the bundle can be updated only after an initial version of the UI > bundle is tagged and released on the cassandra-website. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16763) Create Cassandra documentation content for new website
[ https://issues.apache.org/jira/browse/CASSANDRA-16763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456456#comment-17456456 ] Anthony Grasso commented on CASSANDRA-16763: Updated trunk, and cassandra-4.0 patches as per feedback in pr#1128 comment Answered questions in pr#1128 comment Updated commit message in cassandra-3.11 patch to match trunk and cassandra-4.0 message. > Create Cassandra documentation content for new website > -- > > Key: CASSANDRA-16763 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16763 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Michael Semb Wever >Priority: High > Time Spent: 0.5h > Remaining Estimate: 0h > > We need create the content (asciidoc) to render the Cassandra documentation > using Antora. This work can commence once the following has happened: > * Website and documentation proof of concept is done - CASSANDRA-16029 > * Website design and concept is done - CASSANDRA-16115 > * Website and document tooling is done - CASSANDRA-16066 > * Website UI components are done - CASSANDRA-16762 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16763) Create Cassandra documentation content for new website
[ https://issues.apache.org/jira/browse/CASSANDRA-16763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Grasso reassigned CASSANDRA-16763: -- Assignee: Michael Semb Wever (was: Anthony Grasso) > Create Cassandra documentation content for new website > -- > > Key: CASSANDRA-16763 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16763 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Anthony Grasso >Assignee: Michael Semb Wever >Priority: High > > We need create the content (asciidoc) to render the Cassandra documentation > using Antora. This work can commence once the following has happened: > * Website and documentation proof of concept is done - CASSANDRA-16029 > * Website design and concept is done - CASSANDRA-16115 > * Website and document tooling is done - CASSANDRA-16066 > * Website UI components are done - CASSANDRA-16762 -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
