[JBoss JIRA] (WFCORE-4682) Upgrade Jandex to 2.1.1.Final
by Jeff Mesnil (Jira)
Jeff Mesnil created WFCORE-4682:
-----------------------------------
Summary: Upgrade Jandex to 2.1.1.Final
Key: WFCORE-4682
URL: https://issues.jboss.org/browse/WFCORE-4682
Project: WildFly Core
Issue Type: Component Upgrade
Components: Management
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
- 1
- 0
[JBoss JIRA] (DROOLS-4565) MVELDialectRuntimeData is not thread safe
by Timo Gutjahr (Jira)
[ https://issues.jboss.org/browse/DROOLS-4565?page=com.atlassian.jira.plugi... ]
Timo Gutjahr updated DROOLS-4565:
---------------------------------
Description:
MVELDialectRuntimeData#mvelReaders is accessed concurrently but is not thread safe due to the usage of a HashSet. This may cause lost updates. (See [^ForkJoinPool-1-worker-1.txt] and [^main.txt] )
If this happens and the kie base is serialized and deserialized it results in a NullPointerException at runtime. (See [^NPE.txt] )
We observed that the entries in this Set (mvelReaders) are serialized and important for the deserialization step because they contain information about transient objects that have to be re-initialized after deserialization.
While losing this information due to concurrent access does not cause problems during compilation, serialization and deserialization of a kie base, they may cause NullPointerExceptions at runtime when transient fields remain uninitialized.
was:
MVELDialectRuntimeData#mvelReaders is accessed concurrently but is not thread safe due to the usage of a HashSet. This may cause lost updates. (See [^ForkJoinPool-1-worker-1.txt] )
If this happens and the kie base is serialized and deserialized it results in a NullPointerException at runtime. (See [^NPE.txt] )
We observed that the entries in this Set (mvelReaders) are serialized and important for the deserialization step because they contain information about transient objects that have to be re-initialized after deserialization.
While losing this information due to concurrent access does not cause problems during compilation, serialization and deserialization of a kie base, they may cause NullPointerExceptions at runtime when transient fields remain uninitialized.
> MVELDialectRuntimeData is not thread safe
> -----------------------------------------
>
> Key: DROOLS-4565
> URL: https://issues.jboss.org/browse/DROOLS-4565
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.16.0.Final
> Environment: Java 11.0.2
> Different OS
> Reporter: Timo Gutjahr
> Assignee: Mario Fusco
> Priority: Major
> Attachments: ForkJoinPool-1-worker-1.txt, NPE.txt, main.txt
>
>
> MVELDialectRuntimeData#mvelReaders is accessed concurrently but is not thread safe due to the usage of a HashSet. This may cause lost updates. (See [^ForkJoinPool-1-worker-1.txt] and [^main.txt] )
> If this happens and the kie base is serialized and deserialized it results in a NullPointerException at runtime. (See [^NPE.txt] )
> We observed that the entries in this Set (mvelReaders) are serialized and important for the deserialization step because they contain information about transient objects that have to be re-initialized after deserialization.
> While losing this information due to concurrent access does not cause problems during compilation, serialization and deserialization of a kie base, they may cause NullPointerExceptions at runtime when transient fields remain uninitialized.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
- 1
- 0
[JBoss JIRA] (DROOLS-4565) MVELDialectRuntimeData is not thread safe
by Timo Gutjahr (Jira)
[ https://issues.jboss.org/browse/DROOLS-4565?page=com.atlassian.jira.plugi... ]
Timo Gutjahr updated DROOLS-4565:
---------------------------------
Attachment: main.txt
> MVELDialectRuntimeData is not thread safe
> -----------------------------------------
>
> Key: DROOLS-4565
> URL: https://issues.jboss.org/browse/DROOLS-4565
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.16.0.Final
> Environment: Java 11.0.2
> Different OS
> Reporter: Timo Gutjahr
> Assignee: Mario Fusco
> Priority: Major
> Attachments: ForkJoinPool-1-worker-1.txt, NPE.txt, main.txt
>
>
> MVELDialectRuntimeData#mvelReaders is accessed concurrently but is not thread safe due to the usage of a HashSet. This may cause lost updates. (See [^ForkJoinPool-1-worker-1.txt] )
> If this happens and the kie base is serialized and deserialized it results in a NullPointerException at runtime. (See [^NPE.txt] )
> We observed that the entries in this Set (mvelReaders) are serialized and important for the deserialization step because they contain information about transient objects that have to be re-initialized after deserialization.
> While losing this information due to concurrent access does not cause problems during compilation, serialization and deserialization of a kie base, they may cause NullPointerExceptions at runtime when transient fields remain uninitialized.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
- 1
- 0
[JBoss JIRA] (WFWIP-192) Sync eap CRD with wildfly CRD
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-192?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFWIP-192:
-----------------------------------
[~mchoma] that's a very good idea, I'll modify the map-operator-packaging so that it copies the CRD from wildfly-operator git commit and uses it for the EAP CRD.
> Sync eap CRD with wildfly CRD
> -----------------------------
>
> Key: WFWIP-192
> URL: https://issues.jboss.org/browse/WFWIP-192
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Major
>
> Comparing wildfly and eap CRD revealed differences
> {code}
> wget https://raw.githubusercontent.com/wildfly/wildfly-operator/master/deploy/... -O wildfly_operator_crd
> wget https://raw.githubusercontent.com/jbossas/eap-operator-packaging/prototyp... -O eap_operator_crd
> diff wildfly_operator_crd eap_operator_crd
> {code}
> {code}
> 36,37d35
> < disableHTTPRoute:
> < type: boolean
> 50,53d47
> < sessionAffinity:
> < description: SessionAffinity defines if connections from the same client
> < ip are passed to the same WildFlyServer instance/pod each time
> < type: boolean
> 79,82d72
> < hosts:
> < items:
> < type: string
> < type: array
> 94a85,86
> > required:
> > - pods
> {code}
> Please sync so we can test against.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
- 1
- 0
[JBoss JIRA] (WFWIP-192) Sync eap CRD with wildfly CRD
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-192?page=com.atlassian.jira.plugin.... ]
Martin Choma commented on WFWIP-192:
------------------------------------
Yeah I mean. We release wildfly-operator, e.g {{1.0}} and say we want to productize to eap-operator {{1.0}}. In that case CRD of wildfly-operator and eap-operator will be same, right? This is guaranteed?
So I understand sync is now manual step. That mean error prone. So someone should check. Will that be checked during productization? Or should we check? Sometimes our testsuite can reveal error in CRD, but this is not 100%
For sure best would be to have sync fully automated (if possible) so eap-operator gets always same CRD as wildfly-operator which he is based on. What do you think?
> Sync eap CRD with wildfly CRD
> -----------------------------
>
> Key: WFWIP-192
> URL: https://issues.jboss.org/browse/WFWIP-192
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Major
>
> Comparing wildfly and eap CRD revealed differences
> {code}
> wget https://raw.githubusercontent.com/wildfly/wildfly-operator/master/deploy/... -O wildfly_operator_crd
> wget https://raw.githubusercontent.com/jbossas/eap-operator-packaging/prototyp... -O eap_operator_crd
> diff wildfly_operator_crd eap_operator_crd
> {code}
> {code}
> 36,37d35
> < disableHTTPRoute:
> < type: boolean
> 50,53d47
> < sessionAffinity:
> < description: SessionAffinity defines if connections from the same client
> < ip are passed to the same WildFlyServer instance/pod each time
> < type: boolean
> 79,82d72
> < hosts:
> < items:
> < type: string
> < type: array
> 94a85,86
> > required:
> > - pods
> {code}
> Please sync so we can test against.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
- 1
- 0
[JBoss JIRA] (DROOLS-4571) It's possible to set an empty title header
by Yeser Amer (Jira)
[ https://issues.jboss.org/browse/DROOLS-4571?page=com.atlassian.jira.plugi... ]
Yeser Amer updated DROOLS-4571:
-------------------------------
Summary: It's possible to set an empty title header (was: It's possible to set an emprty title label)
> It's possible to set an empty title header
> ------------------------------------------
>
> Key: DROOLS-4571
> URL: https://issues.jboss.org/browse/DROOLS-4571
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Fix For: 7.28.0.Final
>
>
> In Scenario Test, it is currently possibile to set an empty label as Instance name or property name. This should be forbidden.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
- 1
- 0
[JBoss JIRA] (WFWIP-192) Sync eap CRD with wildfly CRD
by Jeff Mesnil (Jira)
[ https://issues.jboss.org/browse/WFWIP-192?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil commented on WFWIP-192:
-----------------------------------
[~mchoma] there is no guarantee that the WildFly Operator and EAP Operator will always be in sync as they move at different pace
Right now, we are working from the wildfly-operator master HEAD but after the first release, the EAP Operator will be based on releases from the wildfly-operator.
The CRD of the EAP Operator will then be synchronised only when we change the release of the WildFly Operator we want to productize.
I'll sync the EAP CRD once I fixed the WildFly Operator CRD by change the Size field to Replicas
> Sync eap CRD with wildfly CRD
> -----------------------------
>
> Key: WFWIP-192
> URL: https://issues.jboss.org/browse/WFWIP-192
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Major
>
> Comparing wildfly and eap CRD revealed differences
> {code}
> wget https://raw.githubusercontent.com/wildfly/wildfly-operator/master/deploy/... -O wildfly_operator_crd
> wget https://raw.githubusercontent.com/jbossas/eap-operator-packaging/prototyp... -O eap_operator_crd
> diff wildfly_operator_crd eap_operator_crd
> {code}
> {code}
> 36,37d35
> < disableHTTPRoute:
> < type: boolean
> 50,53d47
> < sessionAffinity:
> < description: SessionAffinity defines if connections from the same client
> < ip are passed to the same WildFlyServer instance/pod each time
> < type: boolean
> 79,82d72
> < hosts:
> < items:
> < type: string
> < type: array
> 94a85,86
> > required:
> > - pods
> {code}
> Please sync so we can test against.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
- 1
- 0
[JBoss JIRA] (DROOLS-4571) It's possible to set an emprty title label
by Yeser Amer (Jira)
Yeser Amer created DROOLS-4571:
----------------------------------
Summary: It's possible to set an emprty title label
Key: DROOLS-4571
URL: https://issues.jboss.org/browse/DROOLS-4571
Project: Drools
Issue Type: Bug
Components: Scenario Simulation and Testing
Reporter: Yeser Amer
Assignee: Yeser Amer
Fix For: 7.28.0.Final
In Scenario Test, it is currently possibile to set an empty label as Instance name or property name. This should be forbidden.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
- 1
- 0
[JBoss JIRA] (DROOLS-4571) It's possible to set an emprty title label
by Yeser Amer (Jira)
[ https://issues.jboss.org/browse/DROOLS-4571?page=com.atlassian.jira.plugi... ]
Yeser Amer updated DROOLS-4571:
-------------------------------
Original Estimate: (was: 1 minute)
Remaining Estimate: (was: 1 minute)
Story Points: 1
> It's possible to set an emprty title label
> ------------------------------------------
>
> Key: DROOLS-4571
> URL: https://issues.jboss.org/browse/DROOLS-4571
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Fix For: 7.28.0.Final
>
>
> In Scenario Test, it is currently possibile to set an empty label as Instance name or property name. This should be forbidden.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
- 1
- 0
[JBoss JIRA] (WFWIP-192) Sync eap CRD with wildfly CRD
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-192?page=com.atlassian.jira.plugin.... ]
Martin Choma edited comment on WFWIP-192 at 9/27/19 1:41 AM:
-------------------------------------------------------------
Again crds of wildfly and eap operator are out of sync. I would like to discuss how to handle this situation in future not to happen. Is this manual process? Could it be automatic so we ensure upstream and prod are in sync? So they both behave same so we can avoid difference in behaviour like observed on WFWIP-209
{code:sh}
wget https://raw.githubusercontent.com/wildfly/wildfly-operator/master/deploy/... -O wildfly_operator_crd
wget https://raw.githubusercontent.com/jbossas/eap-operator-packaging/master/r... -O eap_operator_crd
diff wildfly_operator_crd eap_operator_crd
{code}
{code}
[mchoma@10 tmp]$ diff wildfly_operator_crd eap_operator_crd
1,467d0
< apiVersion: apiextensions.k8s.io/v1beta1
< kind: CustomResourceDefinition
< metadata:
< name: wildflyservers.wildfly.org
< spec:
< group: wildfly.org
< names:
< kind: WildFlyServer
< listKind: WildFlyServerList
< plural: wildflyservers
< singular: wildflyserver
< shortNames:
< - wfly
< scope: ""
< version: v1alpha1
< versions:
< - name: v1alpha1
< schema:
< openAPIV3Schema:
< description: WildFlyServer is the Schema for the wildflyservers API
< properties:
< apiVersion:
< description: 'APIVersion defines the versioned schema of this representation
< of an object. Servers should convert recognized schemas to the latest
< internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources'
< type: string
< kind:
< description: 'Kind is a string value representing the REST resource this
< object represents. Servers may infer this from the endpoint the client
< submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-...'
< type: string
< metadata:
< type: object
< spec:
< description: WildFlyServerSpec defines the desired state of WildFlyServer
< properties:
< applicationImage:
< description: ApplicationImage is the name of the application image
< to be deployed
< type: string
< disableHTTPRoute:
< description: DisableHTTPRoute disables the creation a route to the
< HTTP port of the application service (false if omitted)
< type: boolean
< env:
< description: Env contains environment variables for the containers
< running the WildFlyServer application
< items:
< description: EnvVar represents an environment variable present in
< a Container.
< properties:
< name:
< description: Name of the environment variable. Must be a C_IDENTIFIER.
< type: string
< value:
< description: 'Variable references $(VAR_NAME) are expanded using
< the previous defined environment variables in the container
< and any service environment variables. If a variable cannot
< be resolved, the reference in the input string will be unchanged.
< The $(VAR_NAME) syntax can be escaped with a double $$, ie:
< $$(VAR_NAME). Escaped references will never be expanded, regardless
< of whether the variable exists or not. Defaults to "".'
< type: string
< valueFrom:
< description: Source for the environment variable's value. Cannot
< be used if value is not empty.
< properties:
< configMapKeyRef:
< description: Selects a key of a ConfigMap.
< properties:
< key:
< description: The key to select.
< type: string
< name:
< description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#...
< TODO: Add other useful fields. apiVersion, kind, uid?'
< type: string
< optional:
< description: Specify whether the ConfigMap or it's key
< must be defined
< type: boolean
< required:
< - key
< type: object
< fieldRef:
< description: 'Selects a field of the pod: supports metadata.name,
< metadata.namespace, metadata.labels, metadata.annotations,
< spec.nodeName, spec.serviceAccountName, status.hostIP,
< status.podIP.'
< properties:
< apiVersion:
< description: Version of the schema the FieldPath is
< written in terms of, defaults to "v1".
< type: string
< fieldPath:
< description: Path of the field to select in the specified
< API version.
< type: string
< required:
< - fieldPath
< type: object
< resourceFieldRef:
< description: 'Selects a resource of the container: only
< resources limits and requests (limits.cpu, limits.memory,
< limits.ephemeral-storage, requests.cpu, requests.memory
< and requests.ephemeral-storage) are currently supported.'
< properties:
< containerName:
< description: 'Container name: required for volumes,
< optional for env vars'
< type: string
< divisor:
< description: Specifies the output format of the exposed
< resources, defaults to "1"
< type: string
< resource:
< description: 'Required: resource to select'
< type: string
< required:
< - resource
< type: object
< secretKeyRef:
< description: Selects a key of a secret in the pod's namespace
< properties:
< key:
< description: The key of the secret to select from. Must
< be a valid secret key.
< type: string
< name:
< description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#...
< TODO: Add other useful fields. apiVersion, kind, uid?'
< type: string
< optional:
< description: Specify whether the Secret or it's key
< must be defined
< type: boolean
< required:
< - key
< type: object
< type: object
< required:
< - name
< type: object
< type: array
< envFrom:
< items:
< description: EnvFromSource represents the source of a set of ConfigMaps
< properties:
< configMapRef:
< description: The ConfigMap to select from
< properties:
< name:
< description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#...
< TODO: Add other useful fields. apiVersion, kind, uid?'
< type: string
< optional:
< description: Specify whether the ConfigMap must be defined
< type: boolean
< type: object
< prefix:
< description: An optional identifier to prepend to each key in
< the ConfigMap. Must be a C_IDENTIFIER.
< type: string
< secretRef:
< description: The Secret to select from
< properties:
< name:
< description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#...
< TODO: Add other useful fields. apiVersion, kind, uid?'
< type: string
< optional:
< description: Specify whether the Secret must be defined
< type: boolean
< type: object
< type: object
< type: array
< serviceAccountName:
< type: string
< sessionAffinity:
< description: SessionAffinity defines if connections from the same
< client ip are passed to the same WildFlyServer instance/pod each
< time (false if omitted)
< type: boolean
< size:
< format: int32
< type: integer
< standaloneConfigMap:
< description: StandaloneConfigMapSpec defines the desired configMap
< configuration to obtain the standalone configuration for WildFlyServer
< properties:
< key:
< description: Key of the config map whose value is the standalone
< XML configuration file ("standalone.xml" if omitted)
< type: string
< name:
< type: string
< required:
< - name
< type: object
< storage:
< description: StorageSpec defines specific storage required for the
< server own data directory. If omitted, an EmptyDir is used (that
< will not persist data across pod restart).
< properties:
< emptyDir:
< description: Represents an empty directory for a pod. Empty directory
< volumes support ownership management and SELinux relabeling.
< properties:
< medium:
< description: 'What type of storage medium should back this
< directory. The default is "" which means to use the node''s
< default medium. Must be an empty string (default) or Memory.
< More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir'
< type: string
< sizeLimit:
< description: 'Total amount of local storage required for this
< EmptyDir volume. The size limit is also applicable for memory
< medium. The maximum usage on memory medium EmptyDir would
< be the minimum value between the SizeLimit specified here
< and the sum of memory limits of all containers in a pod.
< The default is nil which means that the limit is undefined.
< More info: http://kubernetes.io/docs/user-guide/volumes#emptydir'
< type: string
< type: object
< volumeClaimTemplate:
< description: PersistentVolumeClaim is a user's request for and
< claim to a persistent volume
< properties:
< apiVersion:
< description: 'APIVersion defines the versioned schema of this
< representation of an object. Servers should convert recognized
< schemas to the latest internal value, and may reject unrecognized
< values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources'
< type: string
< kind:
< description: 'Kind is a string value representing the REST
< resource this object represents. Servers may infer this
< from the endpoint the client submits requests to. Cannot
< be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-...'
< type: string
< metadata:
< description: 'Standard object''s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata'
< type: object
< spec:
< description: 'Spec defines the desired characteristics of
< a volume requested by a pod author. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistent...'
< properties:
< accessModes:
< description: 'AccessModes contains the desired access
< modes the volume should have. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-mod...'
< items:
< type: string
< type: array
< dataSource:
< description: This field requires the VolumeSnapshotDataSource
< alpha feature gate to be enabled and currently VolumeSnapshot
< is the only supported data source. If the provisioner
< can support VolumeSnapshot data source, it will create
< a new volume and data will be restored to the volume
< at the same time. If the provisioner does not support
< VolumeSnapshot data source, volume will not be created
< and the failure will be reported as an event. In the
< future, we plan to support more data source types and
< the behavior of the provisioner may change.
< properties:
< apiGroup:
< description: APIGroup is the group for the resource
< being referenced. If APIGroup is not specified,
< the specified Kind must be in the core API group.
< For any other third-party types, APIGroup is required.
< type: string
< kind:
< description: Kind is the type of resource being referenced
< type: string
< name:
< description: Name is the name of resource being referenced
< type: string
< required:
< - kind
< - name
< type: object
< resources:
< description: 'Resources represents the minimum resources
< the volume should have. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources'
< properties:
< limits:
< additionalProperties:
< type: string
< description: 'Limits describes the maximum amount
< of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resource...'
< type: object
< requests:
< additionalProperties:
< type: string
< description: 'Requests describes the minimum amount
< of compute resources required. If Requests is omitted
< for a container, it defaults to Limits if that is
< explicitly specified, otherwise to an implementation-defined
< value. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resource...'
< type: object
< type: object
< selector:
< description: A label query over volumes to consider for
< binding.
< properties:
< matchExpressions:
< description: matchExpressions is a list of label selector
< requirements. The requirements are ANDed.
< items:
< description: A label selector requirement is a selector
< that contains values, a key, and an operator that
< relates the key and values.
< properties:
< key:
< description: key is the label key that the selector
< applies to.
< type: string
< operator:
< description: operator represents a key's relationship
< to a set of values. Valid operators are In,
< NotIn, Exists and DoesNotExist.
< type: string
< values:
< description: values is an array of string values.
< If the operator is In or NotIn, the values
< array must be non-empty. If the operator is
< Exists or DoesNotExist, the values array must
< be empty. This array is replaced during a
< strategic merge patch.
< items:
< type: string
< type: array
< required:
< - key
< - operator
< type: object
< type: array
< matchLabels:
< additionalProperties:
< type: string
< description: matchLabels is a map of {key,value} pairs.
< A single {key,value} in the matchLabels map is equivalent
< to an element of matchExpressions, whose key field
< is "key", the operator is "In", and the values array
< contains only "value". The requirements are ANDed.
< type: object
< type: object
< storageClassName:
< description: 'Name of the StorageClass required by the
< claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#class-1'
< type: string
< volumeMode:
< description: volumeMode defines what type of volume is
< required by the claim. Value of Filesystem is implied
< when not included in claim spec. This is a beta feature.
< type: string
< volumeName:
< description: VolumeName is the binding reference to the
< PersistentVolume backing this claim.
< type: string
< type: object
< status:
< description: 'Status represents the current information/status
< of a persistent volume claim. Read-only. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistent...'
< properties:
< accessModes:
< description: 'AccessModes contains the actual access modes
< the volume backing the PVC has. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-mod...'
< items:
< type: string
< type: array
< capacity:
< additionalProperties:
< type: string
< description: Represents the actual resources of the underlying
< volume.
< type: object
< conditions:
< description: Current Condition of persistent volume claim.
< If underlying persistent volume is being resized then
< the Condition will be set to 'ResizeStarted'.
< items:
< description: PersistentVolumeClaimCondition contails
< details about state of pvc
< properties:
< lastProbeTime:
< description: Last time we probed the condition.
< format: date-time
< type: string
< lastTransitionTime:
< description: Last time the condition transitioned
< from one status to another.
< format: date-time
< type: string
< message:
< description: Human-readable message indicating details
< about last transition.
< type: string
< reason:
< description: Unique, this should be a short, machine
< understandable string that gives the reason for
< condition's last transition. If it reports "ResizeStarted"
< that means the underlying persistent volume is
< being resized.
< type: string
< status:
< type: string
< type:
< description: PersistentVolumeClaimConditionType
< is a valid value of PersistentVolumeClaimCondition.Type
< type: string
< required:
< - status
< - type
< type: object
< type: array
< phase:
< description: Phase represents the current phase of PersistentVolumeClaim.
< type: string
< type: object
< type: object
< type: object
< required:
< - applicationImage
< - size
< type: object
< status:
< description: WildFlyServerStatus defines the observed state of WildFlyServer
< properties:
< hosts:
< items:
< type: string
< type: array
< pods:
< items:
< description: PodStatus defines the observed state of pods running
< the WildFlyServer application
< properties:
< name:
< type: string
< podIP:
< type: string
< state:
< description: "Represent the state of the Pod, it's used especially
< during scale down the expected values are represented by the
< PodState* constants \n Read-only."
< type: string
< required:
< - name
< - podIP
< - state
< type: object
< type: array
< scalingdownPods:
< description: "Represents the number of pods which are in scaledown
< process what particular pod is scaling down can be verified by PodStatus
< \n Read-only."
< format: int32
< type: integer
< required:
< - scalingdownPods
< type: object
< type: object
< served: true
< storage: true
< subresources:
< status: {}
{code}
was (Author: mchoma):
Again crds of wildfly and eap operator are out of sync. I would like to discuss how to handle this situation in future not to happen. Is this manual process? Could it be automatic so we ensure upstream and prod are in sync? So they both behave same.
{code:sh}
wget https://raw.githubusercontent.com/wildfly/wildfly-operator/master/deploy/... -O wildfly_operator_crd
wget https://raw.githubusercontent.com/jbossas/eap-operator-packaging/master/r... -O eap_operator_crd
diff wildfly_operator_crd eap_operator_crd
{code}
{code}
[mchoma@10 tmp]$ diff wildfly_operator_crd eap_operator_crd
1,467d0
< apiVersion: apiextensions.k8s.io/v1beta1
< kind: CustomResourceDefinition
< metadata:
< name: wildflyservers.wildfly.org
< spec:
< group: wildfly.org
< names:
< kind: WildFlyServer
< listKind: WildFlyServerList
< plural: wildflyservers
< singular: wildflyserver
< shortNames:
< - wfly
< scope: ""
< version: v1alpha1
< versions:
< - name: v1alpha1
< schema:
< openAPIV3Schema:
< description: WildFlyServer is the Schema for the wildflyservers API
< properties:
< apiVersion:
< description: 'APIVersion defines the versioned schema of this representation
< of an object. Servers should convert recognized schemas to the latest
< internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources'
< type: string
< kind:
< description: 'Kind is a string value representing the REST resource this
< object represents. Servers may infer this from the endpoint the client
< submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-...'
< type: string
< metadata:
< type: object
< spec:
< description: WildFlyServerSpec defines the desired state of WildFlyServer
< properties:
< applicationImage:
< description: ApplicationImage is the name of the application image
< to be deployed
< type: string
< disableHTTPRoute:
< description: DisableHTTPRoute disables the creation a route to the
< HTTP port of the application service (false if omitted)
< type: boolean
< env:
< description: Env contains environment variables for the containers
< running the WildFlyServer application
< items:
< description: EnvVar represents an environment variable present in
< a Container.
< properties:
< name:
< description: Name of the environment variable. Must be a C_IDENTIFIER.
< type: string
< value:
< description: 'Variable references $(VAR_NAME) are expanded using
< the previous defined environment variables in the container
< and any service environment variables. If a variable cannot
< be resolved, the reference in the input string will be unchanged.
< The $(VAR_NAME) syntax can be escaped with a double $$, ie:
< $$(VAR_NAME). Escaped references will never be expanded, regardless
< of whether the variable exists or not. Defaults to "".'
< type: string
< valueFrom:
< description: Source for the environment variable's value. Cannot
< be used if value is not empty.
< properties:
< configMapKeyRef:
< description: Selects a key of a ConfigMap.
< properties:
< key:
< description: The key to select.
< type: string
< name:
< description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#...
< TODO: Add other useful fields. apiVersion, kind, uid?'
< type: string
< optional:
< description: Specify whether the ConfigMap or it's key
< must be defined
< type: boolean
< required:
< - key
< type: object
< fieldRef:
< description: 'Selects a field of the pod: supports metadata.name,
< metadata.namespace, metadata.labels, metadata.annotations,
< spec.nodeName, spec.serviceAccountName, status.hostIP,
< status.podIP.'
< properties:
< apiVersion:
< description: Version of the schema the FieldPath is
< written in terms of, defaults to "v1".
< type: string
< fieldPath:
< description: Path of the field to select in the specified
< API version.
< type: string
< required:
< - fieldPath
< type: object
< resourceFieldRef:
< description: 'Selects a resource of the container: only
< resources limits and requests (limits.cpu, limits.memory,
< limits.ephemeral-storage, requests.cpu, requests.memory
< and requests.ephemeral-storage) are currently supported.'
< properties:
< containerName:
< description: 'Container name: required for volumes,
< optional for env vars'
< type: string
< divisor:
< description: Specifies the output format of the exposed
< resources, defaults to "1"
< type: string
< resource:
< description: 'Required: resource to select'
< type: string
< required:
< - resource
< type: object
< secretKeyRef:
< description: Selects a key of a secret in the pod's namespace
< properties:
< key:
< description: The key of the secret to select from. Must
< be a valid secret key.
< type: string
< name:
< description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#...
< TODO: Add other useful fields. apiVersion, kind, uid?'
< type: string
< optional:
< description: Specify whether the Secret or it's key
< must be defined
< type: boolean
< required:
< - key
< type: object
< type: object
< required:
< - name
< type: object
< type: array
< envFrom:
< items:
< description: EnvFromSource represents the source of a set of ConfigMaps
< properties:
< configMapRef:
< description: The ConfigMap to select from
< properties:
< name:
< description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#...
< TODO: Add other useful fields. apiVersion, kind, uid?'
< type: string
< optional:
< description: Specify whether the ConfigMap must be defined
< type: boolean
< type: object
< prefix:
< description: An optional identifier to prepend to each key in
< the ConfigMap. Must be a C_IDENTIFIER.
< type: string
< secretRef:
< description: The Secret to select from
< properties:
< name:
< description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#...
< TODO: Add other useful fields. apiVersion, kind, uid?'
< type: string
< optional:
< description: Specify whether the Secret must be defined
< type: boolean
< type: object
< type: object
< type: array
< serviceAccountName:
< type: string
< sessionAffinity:
< description: SessionAffinity defines if connections from the same
< client ip are passed to the same WildFlyServer instance/pod each
< time (false if omitted)
< type: boolean
< size:
< format: int32
< type: integer
< standaloneConfigMap:
< description: StandaloneConfigMapSpec defines the desired configMap
< configuration to obtain the standalone configuration for WildFlyServer
< properties:
< key:
< description: Key of the config map whose value is the standalone
< XML configuration file ("standalone.xml" if omitted)
< type: string
< name:
< type: string
< required:
< - name
< type: object
< storage:
< description: StorageSpec defines specific storage required for the
< server own data directory. If omitted, an EmptyDir is used (that
< will not persist data across pod restart).
< properties:
< emptyDir:
< description: Represents an empty directory for a pod. Empty directory
< volumes support ownership management and SELinux relabeling.
< properties:
< medium:
< description: 'What type of storage medium should back this
< directory. The default is "" which means to use the node''s
< default medium. Must be an empty string (default) or Memory.
< More info: https://kubernetes.io/docs/concepts/storage/volumes#emptydir'
< type: string
< sizeLimit:
< description: 'Total amount of local storage required for this
< EmptyDir volume. The size limit is also applicable for memory
< medium. The maximum usage on memory medium EmptyDir would
< be the minimum value between the SizeLimit specified here
< and the sum of memory limits of all containers in a pod.
< The default is nil which means that the limit is undefined.
< More info: http://kubernetes.io/docs/user-guide/volumes#emptydir'
< type: string
< type: object
< volumeClaimTemplate:
< description: PersistentVolumeClaim is a user's request for and
< claim to a persistent volume
< properties:
< apiVersion:
< description: 'APIVersion defines the versioned schema of this
< representation of an object. Servers should convert recognized
< schemas to the latest internal value, and may reject unrecognized
< values. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#resources'
< type: string
< kind:
< description: 'Kind is a string value representing the REST
< resource this object represents. Servers may infer this
< from the endpoint the client submits requests to. Cannot
< be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#types-...'
< type: string
< metadata:
< description: 'Standard object''s metadata. More info: https://git.k8s.io/community/contributors/devel/api-conventions.md#metadata'
< type: object
< spec:
< description: 'Spec defines the desired characteristics of
< a volume requested by a pod author. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistent...'
< properties:
< accessModes:
< description: 'AccessModes contains the desired access
< modes the volume should have. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-mod...'
< items:
< type: string
< type: array
< dataSource:
< description: This field requires the VolumeSnapshotDataSource
< alpha feature gate to be enabled and currently VolumeSnapshot
< is the only supported data source. If the provisioner
< can support VolumeSnapshot data source, it will create
< a new volume and data will be restored to the volume
< at the same time. If the provisioner does not support
< VolumeSnapshot data source, volume will not be created
< and the failure will be reported as an event. In the
< future, we plan to support more data source types and
< the behavior of the provisioner may change.
< properties:
< apiGroup:
< description: APIGroup is the group for the resource
< being referenced. If APIGroup is not specified,
< the specified Kind must be in the core API group.
< For any other third-party types, APIGroup is required.
< type: string
< kind:
< description: Kind is the type of resource being referenced
< type: string
< name:
< description: Name is the name of resource being referenced
< type: string
< required:
< - kind
< - name
< type: object
< resources:
< description: 'Resources represents the minimum resources
< the volume should have. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#resources'
< properties:
< limits:
< additionalProperties:
< type: string
< description: 'Limits describes the maximum amount
< of compute resources allowed. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resource...'
< type: object
< requests:
< additionalProperties:
< type: string
< description: 'Requests describes the minimum amount
< of compute resources required. If Requests is omitted
< for a container, it defaults to Limits if that is
< explicitly specified, otherwise to an implementation-defined
< value. More info: https://kubernetes.io/docs/concepts/configuration/manage-compute-resource...'
< type: object
< type: object
< selector:
< description: A label query over volumes to consider for
< binding.
< properties:
< matchExpressions:
< description: matchExpressions is a list of label selector
< requirements. The requirements are ANDed.
< items:
< description: A label selector requirement is a selector
< that contains values, a key, and an operator that
< relates the key and values.
< properties:
< key:
< description: key is the label key that the selector
< applies to.
< type: string
< operator:
< description: operator represents a key's relationship
< to a set of values. Valid operators are In,
< NotIn, Exists and DoesNotExist.
< type: string
< values:
< description: values is an array of string values.
< If the operator is In or NotIn, the values
< array must be non-empty. If the operator is
< Exists or DoesNotExist, the values array must
< be empty. This array is replaced during a
< strategic merge patch.
< items:
< type: string
< type: array
< required:
< - key
< - operator
< type: object
< type: array
< matchLabels:
< additionalProperties:
< type: string
< description: matchLabels is a map of {key,value} pairs.
< A single {key,value} in the matchLabels map is equivalent
< to an element of matchExpressions, whose key field
< is "key", the operator is "In", and the values array
< contains only "value". The requirements are ANDed.
< type: object
< type: object
< storageClassName:
< description: 'Name of the StorageClass required by the
< claim. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#class-1'
< type: string
< volumeMode:
< description: volumeMode defines what type of volume is
< required by the claim. Value of Filesystem is implied
< when not included in claim spec. This is a beta feature.
< type: string
< volumeName:
< description: VolumeName is the binding reference to the
< PersistentVolume backing this claim.
< type: string
< type: object
< status:
< description: 'Status represents the current information/status
< of a persistent volume claim. Read-only. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistent...'
< properties:
< accessModes:
< description: 'AccessModes contains the actual access modes
< the volume backing the PVC has. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#access-mod...'
< items:
< type: string
< type: array
< capacity:
< additionalProperties:
< type: string
< description: Represents the actual resources of the underlying
< volume.
< type: object
< conditions:
< description: Current Condition of persistent volume claim.
< If underlying persistent volume is being resized then
< the Condition will be set to 'ResizeStarted'.
< items:
< description: PersistentVolumeClaimCondition contails
< details about state of pvc
< properties:
< lastProbeTime:
< description: Last time we probed the condition.
< format: date-time
< type: string
< lastTransitionTime:
< description: Last time the condition transitioned
< from one status to another.
< format: date-time
< type: string
< message:
< description: Human-readable message indicating details
< about last transition.
< type: string
< reason:
< description: Unique, this should be a short, machine
< understandable string that gives the reason for
< condition's last transition. If it reports "ResizeStarted"
< that means the underlying persistent volume is
< being resized.
< type: string
< status:
< type: string
< type:
< description: PersistentVolumeClaimConditionType
< is a valid value of PersistentVolumeClaimCondition.Type
< type: string
< required:
< - status
< - type
< type: object
< type: array
< phase:
< description: Phase represents the current phase of PersistentVolumeClaim.
< type: string
< type: object
< type: object
< type: object
< required:
< - applicationImage
< - size
< type: object
< status:
< description: WildFlyServerStatus defines the observed state of WildFlyServer
< properties:
< hosts:
< items:
< type: string
< type: array
< pods:
< items:
< description: PodStatus defines the observed state of pods running
< the WildFlyServer application
< properties:
< name:
< type: string
< podIP:
< type: string
< state:
< description: "Represent the state of the Pod, it's used especially
< during scale down the expected values are represented by the
< PodState* constants \n Read-only."
< type: string
< required:
< - name
< - podIP
< - state
< type: object
< type: array
< scalingdownPods:
< description: "Represents the number of pods which are in scaledown
< process what particular pod is scaling down can be verified by PodStatus
< \n Read-only."
< format: int32
< type: integer
< required:
< - scalingdownPods
< type: object
< type: object
< served: true
< storage: true
< subresources:
< status: {}
{code}
> Sync eap CRD with wildfly CRD
> -----------------------------
>
> Key: WFWIP-192
> URL: https://issues.jboss.org/browse/WFWIP-192
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Jeff Mesnil
> Priority: Major
>
> Comparing wildfly and eap CRD revealed differences
> {code}
> wget https://raw.githubusercontent.com/wildfly/wildfly-operator/master/deploy/... -O wildfly_operator_crd
> wget https://raw.githubusercontent.com/jbossas/eap-operator-packaging/prototyp... -O eap_operator_crd
> diff wildfly_operator_crd eap_operator_crd
> {code}
> {code}
> 36,37d35
> < disableHTTPRoute:
> < type: boolean
> 50,53d47
> < sessionAffinity:
> < description: SessionAffinity defines if connections from the same client
> < ip are passed to the same WildFlyServer instance/pod each time
> < type: boolean
> 79,82d72
> < hosts:
> < items:
> < type: string
> < type: array
> 94a85,86
> > required:
> > - pods
> {code}
> Please sync so we can test against.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
- 1
- 0