[jira] [Assigned] (SLIDER-704) Explore Slider and Apache Ranger Integration scenarios
[ https://issues.apache.org/jira/browse/SLIDER-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Maron reassigned SLIDER-704: - Assignee: Jonathan Maron > Explore Slider and Apache Ranger Integration scenarios > -- > > Key: SLIDER-704 > URL: https://issues.apache.org/jira/browse/SLIDER-704 > Project: Slider > Issue Type: Task > Components: appmaster, client, security >Reporter: Jonathan Maron >Assignee: Jonathan Maron > > See what's involved, and what is possible, with respect to: > 1) Supporting deployment of applications leveraging Ranger > 2) Utilize Ranger for Slider AM authorization policy enforcement -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Application Management and Authorization
Hi, Is there an existing approach for exposing management functions to users other than the application creator? Most management operations validate the existence of a cluster definition in the cluster directory, which is by default under the creator’s home directory (e.g. /users/username/.slider/cluster/clusterName). That check will fail if a user other than the creator attempts a management operation (e.g. stop) even if an authorization policy is in place to allow the operation (assuming RPC ACLs or Ranger is leveraged). Do we: - Expect users to leverage the “slider.base.path” property to designate a location accessible to all management users (with appropriate permissions set for that directory)? - Move the default base path to one accessible to more users (the users designated as authorized to manage application instances), e.g. /apps/slider? — Jon -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
[jira] [Created] (SLIDER-729) move state int enum from ConfigurationDescription to standalone
Steve Loughran created SLIDER-729:
-
Summary: move state int enum from ConfigurationDescription to
standalone
Key: SLIDER-729
URL: https://issues.apache.org/jira/browse/SLIDER-729
Project: Slider
Issue Type: Improvement
Components: client
Affects Versions: Slider 0.60
Reporter: Steve Loughran
Assignee: Steve Loughran
Priority: Minor
Fix For: Slider 0.70
we use the {{ConfigurationDescription}} state constants in a lot of places; if
we isolate them into a {{StateValue}} class it cleans up how these references
come in
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SLIDER-729) move state int enum from ConfigurationDescription to standalone
[
https://issues.apache.org/jira/browse/SLIDER-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved SLIDER-729.
---
Resolution: Fixed
done, constants in {{ComponentDescription}} ref back to new values for
compatiblity
> move state int enum from ConfigurationDescription to standalone
>
>
> Key: SLIDER-729
> URL: https://issues.apache.org/jira/browse/SLIDER-729
> Project: Slider
> Issue Type: Improvement
> Components: client
>Affects Versions: Slider 0.60
>Reporter: Steve Loughran
>Assignee: Steve Loughran
>Priority: Minor
> Fix For: Slider 0.70
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> we use the {{ConfigurationDescription}} state constants in a lot of places;
> if we isolate them into a {{StateValue}} class it cleans up how these
> references come in
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Application Management and Authorization
some of these operations could skip the "is the cluster in the path" task; it's probably just there for fail-fast. the AM could be located via YARN rm lookup (today), or via the full YARN registry, then (IPC/REST) operations made to it straightforward: stop, status checks. the flex command currently writes the spec to HDFS if the cluster is down; it only talks to the AM when the AM is live. operations like create & destroy are very FS centric On 18 December 2014 at 14:54, Jon Maron wrote: > > Hi, > > Is there an existing approach for exposing management functions to users > other than the application creator? Most management operations validate > the existence of a cluster definition in the cluster directory, which is by > default under the creator’s home directory (e.g. > /users/username/.slider/cluster/clusterName). That check will fail if a > user other than the creator attempts a management operation (e.g. stop) > even if an authorization policy is in place to allow the operation > (assuming RPC ACLs or Ranger is leveraged). Do we: > > - Expect users to leverage the “slider.base.path” property to > designate a location accessible to all management users (with appropriate > permissions set for that directory)? > - Move the default base path to one accessible to more users (the > users designated as authorized to manage application instances), e.g. > /apps/slider? > > — Jon > > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Re: Application Management and Authorization
On Dec 18, 2014, at 1:53 PM, Steve Loughran wrote: > some of these operations could skip the "is the cluster in the path" task; > it's probably just there for fail-fast. > > the AM could be located via YARN rm lookup (today), or via the full YARN > registry, then (IPC/REST) operations made to it > > straightforward: stop, status checks. > the flex command currently writes the spec to HDFS if the cluster is down; > it only talks to the AM when the AM is live. OK - I had similar thoughts. I suppose a JIRA is required. > > operations like create & destroy are very FS centric > > On 18 December 2014 at 14:54, Jon Maron wrote: >> >> Hi, >> >> Is there an existing approach for exposing management functions to users >> other than the application creator? Most management operations validate >> the existence of a cluster definition in the cluster directory, which is by >> default under the creator’s home directory (e.g. >> /users/username/.slider/cluster/clusterName). That check will fail if a >> user other than the creator attempts a management operation (e.g. stop) >> even if an authorization policy is in place to allow the operation >> (assuming RPC ACLs or Ranger is leveraged). Do we: >> >>- Expect users to leverage the “slider.base.path” property to >> designate a location accessible to all management users (with appropriate >> permissions set for that directory)? >>- Move the default base path to one accessible to more users (the >> users designated as authorized to manage application instances), e.g. >> /apps/slider? >> >> — Jon >> >> >> >> -- >> CONFIDENTIALITY NOTICE >> NOTICE: This message is intended for the use of the individual or entity to >> which it is addressed and may contain information that is confidential, >> privileged and exempt from disclosure under applicable law. If the reader >> of this message is not the intended recipient, you are hereby notified that >> any printing, copying, dissemination, distribution, disclosure or >> forwarding of this communication is strictly prohibited. If you have >> received this communication in error, please contact the sender immediately >> and delete it from your system. Thank You. >> > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
[jira] [Commented] (SLIDER-147) Set up ganglia metrics for Accumulo
[ https://issues.apache.org/jira/browse/SLIDER-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252192#comment-14252192 ] Billie Rinaldi commented on SLIDER-147: --- Now that [~elserj] has gotten Accumulo set up for metrics2, I've been able to configure the Accumulo app package to use Ganglia metrics in a similar manner to the HBase and Storm packages. It uses Application3 and port 8669. One thing I want to make sure is that everything still works if Ganglia hasn't been set up properly. It looks like the other app packages have a site.global.ganglia_enabled property, but the HBase app package never uses this property. > Set up ganglia metrics for Accumulo > --- > > Key: SLIDER-147 > URL: https://issues.apache.org/jira/browse/SLIDER-147 > Project: Slider > Issue Type: Improvement >Reporter: Billie Rinaldi >Assignee: Billie Rinaldi > Fix For: Slider 2.0.0 > > > This may require changing how Accumulo does metrics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLIDER-711) Implement initial read-only view of REST resources
[ https://issues.apache.org/jira/browse/SLIDER-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252303#comment-14252303 ] ASF subversion and git services commented on SLIDER-711: Commit 9dffb40590a96bac96fd411564fe09f9ae77e134 in incubator-slider's branch refs/heads/feature/SLIDER-151_REST_API from [~ste...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=9dffb40 ] SLIDER-711 live/containers resource > Implement initial read-only view of REST resources > -- > > Key: SLIDER-711 > URL: https://issues.apache.org/jira/browse/SLIDER-711 > Project: Slider > Issue Type: Sub-task > Components: Web & REST >Affects Versions: Slider 0.70 >Reporter: Steve Loughran >Assignee: Steve Loughran > Fix For: Slider 0.70 > > Original Estimate: 24h > Time Spent: 3h > Remaining Estimate: 21h > > Implement the read only views of the API with the initial data structures. > this is simply building up and serving existing data, with tests to accompany > it. > This will be testable on secure clusters -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLIDER-724) don't serve web content until AM is fully configured
[ https://issues.apache.org/jira/browse/SLIDER-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252304#comment-14252304 ] ASF subversion and git services commented on SLIDER-724: Commit a3e229739b5a65088cbea9eb4645d01a2de5879f in incubator-slider's branch refs/heads/feature/SLIDER-151_REST_API from [~ste...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=a3e2297 ] SLIDER-724 TestPublishedSliderResources to spin for REST live > don't serve web content until AM is fully configured > > > Key: SLIDER-724 > URL: https://issues.apache.org/jira/browse/SLIDER-724 > Project: Slider > Issue Type: Sub-task > Components: Web & REST >Affects Versions: Slider 0.60 >Reporter: Steve Loughran >Assignee: Steve Loughran > Fix For: Slider 0.70 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Add a simple Web filter which can be turned offline/online, setting it > offline at startup. > This avoids any problems with the REST APIs being invoked before the AM is > completely initiated. We have seen this on GET operations; once other verbs > are supported this move from being a minor issue to a danger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLIDER-729) move state int enum from ConfigurationDescription to standalone
[
https://issues.apache.org/jira/browse/SLIDER-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252306#comment-14252306
]
ASF subversion and git services commented on SLIDER-729:
Commit c52183c6cdf657ea680ae1a14a475c5eead39bc6 in incubator-slider's branch
refs/heads/feature/SLIDER-151_REST_API from [~ste...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=c52183c ]
SLIDER-729 move state int enum from ConfigurationDescription to standalone
> move state int enum from ConfigurationDescription to standalone
>
>
> Key: SLIDER-729
> URL: https://issues.apache.org/jira/browse/SLIDER-729
> Project: Slider
> Issue Type: Improvement
> Components: client
>Affects Versions: Slider 0.60
>Reporter: Steve Loughran
>Assignee: Steve Loughran
>Priority: Minor
> Fix For: Slider 0.70
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> we use the {{ConfigurationDescription}} state constants in a lot of places;
> if we isolate them into a {{StateValue}} class it cleans up how these
> references come in
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLIDER-711) Implement initial read-only view of REST resources
[ https://issues.apache.org/jira/browse/SLIDER-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252307#comment-14252307 ] ASF subversion and git services commented on SLIDER-711: Commit 08b979c252a4067ddf79eeb21d3d76742cc10719 in incubator-slider's branch refs/heads/feature/SLIDER-151_REST_API from [~ste...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=08b979c ] SLIDER-711 container listing work > Implement initial read-only view of REST resources > -- > > Key: SLIDER-711 > URL: https://issues.apache.org/jira/browse/SLIDER-711 > Project: Slider > Issue Type: Sub-task > Components: Web & REST >Affects Versions: Slider 0.70 >Reporter: Steve Loughran >Assignee: Steve Loughran > Fix For: Slider 0.70 > > Original Estimate: 24h > Time Spent: 3h > Remaining Estimate: 21h > > Implement the read only views of the API with the initial data structures. > this is simply building up and serving existing data, with tests to accompany > it. > This will be testable on secure clusters -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLIDER-711) Implement initial read-only view of REST resources
[ https://issues.apache.org/jira/browse/SLIDER-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252308#comment-14252308 ] ASF subversion and git services commented on SLIDER-711: Commit 3c450b938c8b3144f527a7c14790fd2e1d491549 in incubator-slider's branch refs/heads/feature/SLIDER-151_REST_API from [~ste...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=3c450b9 ] SLIDER-711 components/ and components/$component > Implement initial read-only view of REST resources > -- > > Key: SLIDER-711 > URL: https://issues.apache.org/jira/browse/SLIDER-711 > Project: Slider > Issue Type: Sub-task > Components: Web & REST >Affects Versions: Slider 0.70 >Reporter: Steve Loughran >Assignee: Steve Loughran > Fix For: Slider 0.70 > > Original Estimate: 24h > Time Spent: 3h > Remaining Estimate: 21h > > Implement the read only views of the API with the initial data structures. > this is simply building up and serving existing data, with tests to accompany > it. > This will be testable on secure clusters -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLIDER-724) don't serve web content until AM is fully configured
[ https://issues.apache.org/jira/browse/SLIDER-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252309#comment-14252309 ] ASF subversion and git services commented on SLIDER-724: Commit a3e229739b5a65088cbea9eb4645d01a2de5879f in incubator-slider's branch refs/heads/develop from [~ste...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=a3e2297 ] SLIDER-724 TestPublishedSliderResources to spin for REST live > don't serve web content until AM is fully configured > > > Key: SLIDER-724 > URL: https://issues.apache.org/jira/browse/SLIDER-724 > Project: Slider > Issue Type: Sub-task > Components: Web & REST >Affects Versions: Slider 0.60 >Reporter: Steve Loughran >Assignee: Steve Loughran > Fix For: Slider 0.70 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Add a simple Web filter which can be turned offline/online, setting it > offline at startup. > This avoids any problems with the REST APIs being invoked before the AM is > completely initiated. We have seen this on GET operations; once other verbs > are supported this move from being a minor issue to a danger. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLIDER-151) Implement full slider API in REST and switch client to it
[ https://issues.apache.org/jira/browse/SLIDER-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252313#comment-14252313 ] ASF subversion and git services commented on SLIDER-151: Commit 57d0d2ed2c6ad94ede6d39bbe791c4391aaa115c in incubator-slider's branch refs/heads/develop from [~ste...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=57d0d2e ] Merge branch 'feature/SLIDER-151_REST_API' into develop > Implement full slider API in REST and switch client to it > - > > Key: SLIDER-151 > URL: https://issues.apache.org/jira/browse/SLIDER-151 > Project: Slider > Issue Type: New Feature > Components: client, Web & REST >Affects Versions: Slider 0.60 >Reporter: Steve Loughran >Assignee: Steve Loughran > Attachments: 2014-12-10-slider-REST.pptx, 2014-12-11-slider-REST.pdf, > SliderRESTAPIv3-001.pdf > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLIDER-709) Draft new REST API with use cases
[ https://issues.apache.org/jira/browse/SLIDER-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved SLIDER-709. --- Resolution: Fixed > Draft new REST API with use cases > - > > Key: SLIDER-709 > URL: https://issues.apache.org/jira/browse/SLIDER-709 > Project: Slider > Issue Type: Sub-task > Components: Web & REST >Affects Versions: Slider 0.60 >Reporter: Steve Loughran >Assignee: Steve Loughran > Fix For: Slider 0.70 > > Original Estimate: 8h > Time Spent: 2h > Remaining Estimate: 6h > > # Define use cases for the REST API, e.g: long-haul, thin-client, web UI, > management tools > # Propose initial REST API with outline URLs and data structures -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLIDER-711) Implement initial read-only view of REST resources
[ https://issues.apache.org/jira/browse/SLIDER-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved SLIDER-711. --- Resolution: Fixed > Implement initial read-only view of REST resources > -- > > Key: SLIDER-711 > URL: https://issues.apache.org/jira/browse/SLIDER-711 > Project: Slider > Issue Type: Sub-task > Components: Web & REST >Affects Versions: Slider 0.70 >Reporter: Steve Loughran >Assignee: Steve Loughran > Fix For: Slider 0.70 > > Original Estimate: 24h > Time Spent: 3h > Remaining Estimate: 21h > > Implement the read only views of the API with the initial data structures. > this is simply building up and serving existing data, with tests to accompany > it. > This will be testable on secure clusters -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLIDER-729) move state int enum from ConfigurationDescription to standalone
[
https://issues.apache.org/jira/browse/SLIDER-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252310#comment-14252310
]
ASF subversion and git services commented on SLIDER-729:
Commit c52183c6cdf657ea680ae1a14a475c5eead39bc6 in incubator-slider's branch
refs/heads/develop from [~ste...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=c52183c ]
SLIDER-729 move state int enum from ConfigurationDescription to standalone
> move state int enum from ConfigurationDescription to standalone
>
>
> Key: SLIDER-729
> URL: https://issues.apache.org/jira/browse/SLIDER-729
> Project: Slider
> Issue Type: Improvement
> Components: client
>Affects Versions: Slider 0.60
>Reporter: Steve Loughran
>Assignee: Steve Loughran
>Priority: Minor
> Fix For: Slider 0.70
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> we use the {{ConfigurationDescription}} state constants in a lot of places;
> if we isolate them into a {{StateValue}} class it cleans up how these
> references come in
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SLIDER-711) Implement initial read-only view of REST resources
[ https://issues.apache.org/jira/browse/SLIDER-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252312#comment-14252312 ] ASF subversion and git services commented on SLIDER-711: Commit 3c450b938c8b3144f527a7c14790fd2e1d491549 in incubator-slider's branch refs/heads/develop from [~ste...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=3c450b9 ] SLIDER-711 components/ and components/$component > Implement initial read-only view of REST resources > -- > > Key: SLIDER-711 > URL: https://issues.apache.org/jira/browse/SLIDER-711 > Project: Slider > Issue Type: Sub-task > Components: Web & REST >Affects Versions: Slider 0.70 >Reporter: Steve Loughran >Assignee: Steve Loughran > Fix For: Slider 0.70 > > Original Estimate: 24h > Time Spent: 3h > Remaining Estimate: 21h > > Implement the read only views of the API with the initial data structures. > this is simply building up and serving existing data, with tests to accompany > it. > This will be testable on secure clusters -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLIDER-711) Implement initial read-only view of REST resources
[ https://issues.apache.org/jira/browse/SLIDER-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252311#comment-14252311 ] ASF subversion and git services commented on SLIDER-711: Commit 08b979c252a4067ddf79eeb21d3d76742cc10719 in incubator-slider's branch refs/heads/develop from [~ste...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=08b979c ] SLIDER-711 container listing work > Implement initial read-only view of REST resources > -- > > Key: SLIDER-711 > URL: https://issues.apache.org/jira/browse/SLIDER-711 > Project: Slider > Issue Type: Sub-task > Components: Web & REST >Affects Versions: Slider 0.70 >Reporter: Steve Loughran >Assignee: Steve Loughran > Fix For: Slider 0.70 > > Original Estimate: 24h > Time Spent: 3h > Remaining Estimate: 21h > > Implement the read only views of the API with the initial data structures. > this is simply building up and serving existing data, with tests to accompany > it. > This will be testable on secure clusters -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLIDER-711) Implement initial read-only view of live REST resources
[ https://issues.apache.org/jira/browse/SLIDER-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated SLIDER-711: -- Summary: Implement initial read-only view of live REST resources (was: Implement initial read-only view of REST resources) > Implement initial read-only view of live REST resources > --- > > Key: SLIDER-711 > URL: https://issues.apache.org/jira/browse/SLIDER-711 > Project: Slider > Issue Type: Sub-task > Components: Web & REST >Affects Versions: Slider 0.70 >Reporter: Steve Loughran >Assignee: Steve Loughran > Fix For: Slider 0.70 > > Original Estimate: 24h > Time Spent: 75h > Remaining Estimate: 0h > > Implement the read only views of the API with the initial data structures. > this is simply building up and serving existing data, with tests to accompany > it. > This will be testable on secure clusters -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SLIDER-730) Lack of synchronization in RoleStatus#serialize()
Ted Yu created SLIDER-730: - Summary: Lack of synchronization in RoleStatus#serialize() Key: SLIDER-730 URL: https://issues.apache.org/jira/browse/SLIDER-730 Project: Slider Issue Type: Bug Reporter: Ted Yu Assignee: Ted Yu Priority: Minor Access to fields in RoleStatus#serialize() should be protected by synchronization on RoleStatus.this -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SLIDER-730) Lack of synchronization in RoleStatus#serialize()
[ https://issues.apache.org/jira/browse/SLIDER-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252416#comment-14252416 ] ASF subversion and git services commented on SLIDER-730: Commit 4e8e92e110369dcd0643ac76a0b24df9f2a45420 in incubator-slider's branch refs/heads/develop from [~tedyu] [ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=4e8e92e ] SLIDER-730 Lack of synchronization in RoleStatus#serialize() > Lack of synchronization in RoleStatus#serialize() > - > > Key: SLIDER-730 > URL: https://issues.apache.org/jira/browse/SLIDER-730 > Project: Slider > Issue Type: Bug >Reporter: Ted Yu >Assignee: Ted Yu >Priority: Minor > > Access to fields in RoleStatus#serialize() should be protected by > synchronization on RoleStatus.this -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SLIDER-730) Lack of synchronization in RoleStatus#serialize()
[ https://issues.apache.org/jira/browse/SLIDER-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu resolved SLIDER-730. --- Resolution: Fixed > Lack of synchronization in RoleStatus#serialize() > - > > Key: SLIDER-730 > URL: https://issues.apache.org/jira/browse/SLIDER-730 > Project: Slider > Issue Type: Bug >Reporter: Ted Yu >Assignee: Ted Yu >Priority: Minor > > Access to fields in RoleStatus#serialize() should be protected by > synchronization on RoleStatus.this -- This message was sent by Atlassian JIRA (v6.3.4#6332)
