[jira] [Created] (AMBARI-23285) ${hdp.version} parameter in downloaded Service Client Configs
Juanjo Marron created AMBARI-23285:
--
Summary: ${hdp.version} parameter in downloaded Service Client
Configs
Key: AMBARI-23285
URL: https://issues.apache.org/jira/browse/AMBARI-23285
Project: Ambari
Issue Type: Improvement
Components: ambari-client
Affects Versions: 2.6.2, 2.7.0
Reporter: Juanjo Marron
When using Download Service Client Configs feature in Ambari APIs, some of the
configuration files the ${hdp.version} parameter is not resolved.
This token needs to be replaced by the right hdp version value in order to
properly use some of the properties.
A good example is: mapred-site.xml configuration file form MapReduce2 service
where multiple property values downloaded maintain the parameter ${hdp.version}
These are two of them:
mapreduce.application.classpath
$PWD/mr-framework/hadoop/share/hadoop/mapreduce/*:$PWD/mr-framework/hadoop/share/hadoop/mapreduce/lib/*:$PWD/mr-framework/hadoop/share/hadoop/common/*:$PWD/mr-framework/hadoop/share/hadoop/common/lib/*:$PWD/mr-framework/hadoop/share/hadoop/yarn/*:$PWD/mr-framework/hadoop/share/hadoop/yarn/lib/*:$PWD/mr-framework/hadoop/share/hadoop/hdfs/*:$PWD/mr-framework/hadoop/share/hadoop/hdfs/lib/*:$PWD/mr-framework/hadoop/share/hadoop/tools/lib/*:/usr/hdp/${hdp.version}/hadoop/lib/hadoop-lzo-0.6.0.${*hdp.version}.*jar:/etc/hadoop/conf/secure:/usr/hdp/current/ext/hadoop/*
mapreduce.application.framework.path
/hdp/apps/*${hdp.version}*/mapreduce/mapreduce.tar.gz#mr-framework
Also I have seen tokens that get replaced in the UI but not in the
configuration file downloaded, for example:
The property yarn.nodemanager.aux-services.spark2_shuffle.classpath in advanced
yarn-site.xml (YARN service) shows this value in the UI:
{\{stack_root}}/${hdp.version}/spark2/aux/*
While in the client configurations obtained after downloaded
yarn.nodemanager.aux-services.spark2_shuffle.classpath
/usr/hdp/${hdp.version}/spark2/aux/*
{\{stack_root}} gets properly replaced but ${hdp.version} remains as a string
not resolved
According to the answers in the Ambari user mail list is expected for now.
The problem is that client configs are run and rendered on the Ambari server
itself, which might not even be a part of the cluster. Some properties, such as
the ones showed above , are rendered on a per-host basis, and can be different
depending on the versions of the components which are installed.
We believe that the download client configs logic needs to be rewritten to
allow you to specify the host on which you want to download them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-10186) Support consistent uid/gid for service owners
[ https://issues.apache.org/jira/browse/AMBARI-10186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16354368#comment-16354368 ] Juanjo Marron commented on AMBARI-10186: I think it might me duplicated by AMBARI-21483 which is marked as resolver and delivered to 2.5.2 > Support consistent uid/gid for service owners > - > > Key: AMBARI-10186 > URL: https://issues.apache.org/jira/browse/AMBARI-10186 > Project: Ambari > Issue Type: Bug > Components: ambari-server, blueprints, security >Affects Versions: 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0 >Reporter: Eric Yang >Priority: Major > > Service owners maybe created by Ambari, such as hdfs user created in recipies > in Linux flat file database. However, it does not manage the uid and gid > numbers consistently between nodes. Although HDFS is immune to uid/gid > inconsistency between nodes, other services may be impacted by inconsistent > service owners. > It would be nice to have a way to manage service owners customization like > uid/gid, and ensure the users are consistent across nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-21145) Allow wildcard for log directory folder in the path component of Logfeeder input
[
https://issues.apache.org/jira/browse/AMBARI-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16251852#comment-16251852
]
Juanjo Marron commented on AMBARI-21145:
Thanks for the update!
> Allow wildcard for log directory folder in the path component of Logfeeder
> input
>
>
> Key: AMBARI-21145
> URL: https://issues.apache.org/jira/browse/AMBARI-21145
> Project: Ambari
> Issue Type: Improvement
> Components: logsearch
>Affects Versions: 2.5.0
>Reporter: Keta Patel
>Assignee: Olivér Szabó
>Priority: Minor
> Fix For: 2.6.1
>
>
> The wildcard processing in Logfeeder is carried out only for the last file
> component in the log path. For a few services, where there are multiple log
> folders and log files from each of the folders is desired to be parsed in
> Logsearch UI, the lack of a wildcard processing for the previous portions
> becomes an issue. Hence, introducing wildcard processing for the log
> directory part of the "path" in the Logfeeder's input for the service will
> help resolve this issue.
> The idea is if we have a folder pattern, we will craete a thread group, and
> there will be different threads for every matching input (now only for tail
> file)
> Features (new input block settings):
> - {{path_update_interval_min}}: the period in minutes for checking new files
> (default: 5, based on detach values, its possible that a new input wont be
> monitored)
> - {{detach_interval_min}}: the period in minutes for checking which files are
> too old (default: 300)
> - {{detach_time_min: the period}} in minutes when we flag a file is too old
> (default: 2000)
> - if a path contains a {{*}} before the last {{/}}, then logfeeder will know
> that the inputs should handled in a thread group, not in a standalone thread
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21145) Allow wildcard for log directory folder in the path component of Logfeeder input
[ https://issues.apache.org/jira/browse/AMBARI-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16243130#comment-16243130 ] Juanjo Marron commented on AMBARI-21145: Thanks [~oleewere] for the branch-2.6 integration. It means it should be available on Ambari 2.6.1, right? > Allow wildcard for log directory folder in the path component of Logfeeder > input > > > Key: AMBARI-21145 > URL: https://issues.apache.org/jira/browse/AMBARI-21145 > Project: Ambari > Issue Type: Improvement > Components: logsearch >Affects Versions: 2.5.0 >Reporter: Keta Patel >Assignee: Olivér Szabó >Priority: Minor > > The wildcard processing in Logfeeder is carried out only for the last file > component in the log path. For a few services, where there are multiple log > folders and log files from each of the folders is desired to be parsed in > Logsearch UI, the lack of a wildcard processing for the previous portions > becomes an issue. Hence, introducing wildcard processing for the log > directory part of the "path" in the Logfeeder's input for the service will > help resolve this issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22259) Include property key type under consideration for smartsense anonymization
[
https://issues.apache.org/jira/browse/AMBARI-22259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Juanjo Marron resolved AMBARI-22259.
Resolution: Feedback Received
After conversation with SmartSense Dev team it will be considered in next
releases.
For now there are anonymization rules available based on specific property
name, so this case is cover.
> Include property key type under consideration for smartsense anonymization
> --
>
> Key: AMBARI-22259
> URL: https://issues.apache.org/jira/browse/AMBARI-22259
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Akshay Kotecha Jain
>Priority: Major
>
> Currently, smart-sense anonymization uses a service's property name to detect
> any passwords or sensitive data to replace it with a random hashed value.
> However, this does not work if the type of the property is set to
> *_PASSWORD_* but the name of the property does not match the expression found
> in the following anonymization rule snippet:
> {color:red} {
> "name": "PASSWORDS",
> "rule_id": "Property",
> "properties": [".*password.*", ".*awsAccessKeyId.*",
> ".*awsSecretAccessKey.*", ".*awsAccessKeyId.*", "fs.azure.account.key.*",
> "ranger.service.https.attrib.keystore.pass"],
> "include_files": ["*.xml", "*.properties", "*.yaml", "*.ini"],
> "exclude_files" : ["capacity-scheduler.xml"],
> "shared": false
> }{color}
> Smart-sense should consider both the name and the type of the property to
> apply anonymization.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22149) SmartSense architecture pluggable for third party services
[ https://issues.apache.org/jira/browse/AMBARI-22149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron resolved AMBARI-22149. Resolution: Feedback Received > SmartSense architecture pluggable for third party services > --- > > Key: AMBARI-22149 > URL: https://issues.apache.org/jira/browse/AMBARI-22149 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Juanjo Marron >Priority: Major > > In the current SmartSense design, a third party service targeting to be > integrated into the collection scripts framework needs to deploy its own > specification file under the SmartSense expected path. The SmartSense > scripts_dir by default is: > /var/lib/smartsense/hst-agent/resources/collection-scripts but it accepts > customization in the configuration file /etc/hst/conf/hst-agent.ini, so it > could be different. > Similar to other frameworks and features in Ambari (service advisor, > kerberos, quicklinks, extensions, role_command_order, metrics, widgets, > alerts or Ambari Log Search...) services should be self-described and easily > pluggable on the SmartSense framework just by adding their own definition in > the service directories itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22150) Allow SmartSense reporting to multiple servers
[ https://issues.apache.org/jira/browse/AMBARI-22150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron resolved AMBARI-22150. Resolution: Feedback Received > Allow SmartSense reporting to multiple servers > -- > > Key: AMBARI-22150 > URL: https://issues.apache.org/jira/browse/AMBARI-22150 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Juanjo Marron >Priority: Major > > Third party services should have the option to capture and send bundles to a > SmartSense Server different that the embedded by default at HDP stack. > In the case of service dependencies, host reports and other cluster metrics > this information should be sent to more than one server too -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22151) SmartSense should accept recommendations from more than one server
[ https://issues.apache.org/jira/browse/AMBARI-22151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron resolved AMBARI-22151. Resolution: Feedback Received > SmartSense should accept recommendations from more than one server > -- > > Key: AMBARI-22151 > URL: https://issues.apache.org/jira/browse/AMBARI-22151 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Juanjo Marron >Priority: Major > > If a third party service reports to a SmartSense server different than the > default one in HDP stack, the SmartSense recommendations capability should > accept recommendations originated from different servers. One server could > send recommendations specific to HDP services while other analyzes and > creates suggestions for a third party service. In case of conflict in the > recommendations customers could decide what to apply based on the > priorities/intentions for the cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22149) SmartSense architecture pluggable for third party services
[ https://issues.apache.org/jira/browse/AMBARI-22149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16231388#comment-16231388 ] Juanjo Marron commented on AMBARI-22149: [~sheetal_dolas] Per our conversation today, could you please add a related JIRA capturing this effort for future Ambari released before closing this one? Thanks > SmartSense architecture pluggable for third party services > --- > > Key: AMBARI-22149 > URL: https://issues.apache.org/jira/browse/AMBARI-22149 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Juanjo Marron >Priority: Major > > In the current SmartSense design, a third party service targeting to be > integrated into the collection scripts framework needs to deploy its own > specification file under the SmartSense expected path. The SmartSense > scripts_dir by default is: > /var/lib/smartsense/hst-agent/resources/collection-scripts but it accepts > customization in the configuration file /etc/hst/conf/hst-agent.ini, so it > could be different. > Similar to other frameworks and features in Ambari (service advisor, > kerberos, quicklinks, extensions, role_command_order, metrics, widgets, > alerts or Ambari Log Search...) services should be self-described and easily > pluggable on the SmartSense framework just by adding their own definition in > the service directories itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22149) SmartSense architecture pluggable for third party services
[ https://issues.apache.org/jira/browse/AMBARI-22149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-22149: --- Summary: SmartSense architecture pluggable for third party services (was: SmartSense pluggable architecture for third party services) > SmartSense architecture pluggable for third party services > --- > > Key: AMBARI-22149 > URL: https://issues.apache.org/jira/browse/AMBARI-22149 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Juanjo Marron > > In the current SmartSense design, a third party service targeting to be > integrated into the collection scripts framework needs to deploy its own > specification file under the SmartSense expected path. The SmartSense > scripts_dir by default is: > /var/lib/smartsense/hst-agent/resources/collection-scripts but it accepts > customization in the configuration file /etc/hst/conf/hst-agent.ini, so it > could be different. > Similar to other frameworks and features in Ambari (service advisor, > kerberos, quicklinks, extensions, role_command_order, metrics, widgets, > alerts or Ambari Log Search...) services should be self-described and easily > pluggable on the SmartSense framework just by adding their own definition in > the service directories itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22151) SmartSense should accept recommendations from more than one server
Juanjo Marron created AMBARI-22151: -- Summary: SmartSense should accept recommendations from more than one server Key: AMBARI-22151 URL: https://issues.apache.org/jira/browse/AMBARI-22151 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.5.2 Reporter: Juanjo Marron If a third party service reports to a SmartSense server different than the default one in HDP stack, the SmartSense recommendations capability should accept recommendations originated from different servers. One server could send recommendations specific to HDP services while other analyzes and creates suggestions for a third party service. In case of conflict in the recommendations customers could decide what to apply based on the priorities/intentions for the cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22150) Allow SmartSense reporting to multiple servers
Juanjo Marron created AMBARI-22150: -- Summary: Allow SmartSense reporting to multiple servers Key: AMBARI-22150 URL: https://issues.apache.org/jira/browse/AMBARI-22150 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.5.2 Reporter: Juanjo Marron Third party services should have the option to capture and send bundles to a SmartSense Server different that the embedded by default at HDP stack. In the case of service dependencies, host reports and other cluster metrics this information should be sent to more than one server too -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22149) SmartSense pluggable architecture for third party services
[ https://issues.apache.org/jira/browse/AMBARI-22149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-22149: --- Description: In the current SmartSense design, a third party service targeting to be integrated into the collection scripts framework needs to deploy its own specification file under the SmartSense expected path. The SmartSense scripts_dir by default is: /var/lib/smartsense/hst-agent/resources/collection-scripts but it accepts customization in the configuration file /etc/hst/conf/hst-agent.ini, so it could be different. Similar to other frameworks and features in Ambari (service advisor, kerberos, quicklinks, extensions, role_command_order, metrics, widgets, alerts or Ambari Log Search...) services should be self-described and easily pluggable on the SmartSense framework just by adding their own definition in the service directories itself. was: In the current SmartSense design, a third party service targeting to be integrated into the SmartSense collection scripts framework needs to deploy its own specification file under the SmartSense expected path. The scripts_dir by default is: /var/lib/smartsense/hst-agent/resources/collection-scripts but it accepts customization in the configuration file /etc/hst/conf/hst-agent.ini, so it could be different. Similar to other frameworks and features in Ambari (service advisor, kerberos, quicklinks, extensions, role_command_order, metrics, widgets, alerts or Ambari Log Search...) services should be self-described and easily pluggable on the SmartSense framework just by adding their own definition in the service directories itself. > SmartSense pluggable architecture for third party services > -- > > Key: AMBARI-22149 > URL: https://issues.apache.org/jira/browse/AMBARI-22149 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Juanjo Marron > > In the current SmartSense design, a third party service targeting to be > integrated into the collection scripts framework needs to deploy its own > specification file under the SmartSense expected path. The SmartSense > scripts_dir by default is: > /var/lib/smartsense/hst-agent/resources/collection-scripts but it accepts > customization in the configuration file /etc/hst/conf/hst-agent.ini, so it > could be different. > Similar to other frameworks and features in Ambari (service advisor, > kerberos, quicklinks, extensions, role_command_order, metrics, widgets, > alerts or Ambari Log Search...) services should be self-described and easily > pluggable on the SmartSense framework just by adding their own definition in > the service directories itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22149) SmartSense pluggable architecture for third party services
Juanjo Marron created AMBARI-22149: -- Summary: SmartSense pluggable architecture for third party services Key: AMBARI-22149 URL: https://issues.apache.org/jira/browse/AMBARI-22149 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.5.2 Reporter: Juanjo Marron In the current SmartSense design, a third party service targeting to be integrated into the SmartSense collection scripts framework needs to deploy its own specification file under the SmartSense expected path. The scripts_dir by default is: /var/lib/smartsense/hst-agent/resources/collection-scripts but it accepts customization in the configuration file /etc/hst/conf/hst-agent.ini, so it could be different. Similar to other frameworks and features in Ambari (service advisor, kerberos, quicklinks, extensions, role_command_order, metrics, widgets, alerts or Ambari Log Search...) services should be self-described and easily pluggable on the SmartSense framework just by adding their own definition in the service directories itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21145) allow wildcard for log directory folder in the path component of Logfeeder input
[ https://issues.apache.org/jira/browse/AMBARI-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177309#comment-16177309 ] Juanjo Marron commented on AMBARI-21145: Thanks [~mgergely] for your answer. I would keep this JIRA as unresolved since, in the services we are installing on top of HDP, we are hitting the issue described by [~patel...@us.ibm.com] when trying to integrate into LogSearch. One of the logs for our service has different paths for diff nodes in the cluster (minor numeric change in one of the folders) and ideally they should be captured under an unique log id > allow wildcard for log directory folder in the path component of Logfeeder > input > > > Key: AMBARI-21145 > URL: https://issues.apache.org/jira/browse/AMBARI-21145 > Project: Ambari > Issue Type: Improvement > Components: logsearch >Affects Versions: 2.5.0 >Reporter: Keta Patel >Assignee: Keta Patel >Priority: Minor > > The wildcard processing in Logfeeder is carried out only for the last file > component in the log path. For a few services, where there are multiple log > folders and log files from each of the folders is desired to be parsed in > Logsearch UI, the lack of a wildcard processing for the previous portions > becomes an issue. Hence, introducing wildcard processing for the log > directory part of the "path" in the Logfeeder's input for the service will > help resolve this issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21145) allow wildcard for log directory folder in the path component of Logfeeder input
[ https://issues.apache.org/jira/browse/AMBARI-21145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172403#comment-16172403 ] Juanjo Marron commented on AMBARI-21145: Can we confirm this JIRA has been resolved by AMBARI-21387? In that case it could be marked as resolved > allow wildcard for log directory folder in the path component of Logfeeder > input > > > Key: AMBARI-21145 > URL: https://issues.apache.org/jira/browse/AMBARI-21145 > Project: Ambari > Issue Type: Improvement > Components: logsearch >Affects Versions: 2.5.0 >Reporter: Keta Patel >Assignee: Keta Patel >Priority: Minor > > The wildcard processing in Logfeeder is carried out only for the last file > component in the log path. For a few services, where there are multiple log > folders and log files from each of the folders is desired to be parsed in > Logsearch UI, the lack of a wildcard processing for the previous portions > becomes an issue. Hence, introducing wildcard processing for the log > directory part of the "path" in the Logfeeder's input for the service will > help resolve this issue. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21325) Ability to switch Quick Links to use Service URL through Knox or given proxy
[ https://issues.apache.org/jira/browse/AMBARI-21325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-21325: --- Affects Version/s: 2.5.3 2.5.2 > Ability to switch Quick Links to use Service URL through Knox or given proxy > > > Key: AMBARI-21325 > URL: https://issues.apache.org/jira/browse/AMBARI-21325 > Project: Ambari > Issue Type: Improvement >Affects Versions: trunk, 2.5.2, 2.5.3 >Reporter: Jeffrey E Rodriguez >Assignee: Chandana Mirashi > Attachments: AMBARI-21325.patch > > Original Estimate: 336h > Remaining Estimate: 336h > > Knox has the ability to proxy Hadoop user interfaces URL. Having the ability > to setup Quicklinks through Knox so instead of for example going to "Hbase > Master UI" directly we can proxy through Knox for example: > http://hdpjeff1.fyre.ibm.com:16010/master-status > can be instead go through: > https://hdpjeff1.fyre.ibm.com:8443/gateway/default/hbase/hbaseui/master-status > Here https://hdpjeff1.fyre.ibm.com:8443/gateway is the Knox gateway URL. > This will bring authentication to the UI access and would secure the UI > access. > Ideally this behavior can be set as secure going through proxy by default or > it can be turn off to go directly by Ambari Admin. > Changes added: > 1. Add new json properties knox_url, knox_path, supports_knox >a. knox_url: template to be used for urls that are proxied through Knox >b. knox_path: Knox gateway path that will be added to the proxy url. >c. supports_knox: whether link will be redirected through Knox > 2. Add above json properties to quicklinks.json > 3. Add HDFSUI & DATANODE,YARNUI & NODEUI, JOBHISTORYUI, HBASEUI, OOZIEUI, > SPARKUI services to Knox topology template. > 4. Automate protocol and port added to Knox topology file. Based on whether > SSL is enabled for the services listed above, the port and protocol in > params_linux.py will be updated. > 5. Update quick_view_link_view.js so that when Knox is installed and > support_knox is true, quicklink url follows knox url template specified in > the quicklinks.json for the service/component. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-14149) Python 2.7.9 or later fails to establish connection between agent and server.
[ https://issues.apache.org/jira/browse/AMBARI-14149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16063843#comment-16063843 ] Juanjo Marron commented on AMBARI-14149: Hit this same issue in a RHEL 7.4 power cluster where the python version is 2.7.5. Since that the context=ssl._create_unverified_context() argument would be required also in python versions leaser than 2.7.9 > Python 2.7.9 or later fails to establish connection between agent and server. > - > > Key: AMBARI-14149 > URL: https://issues.apache.org/jira/browse/AMBARI-14149 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.2.0 > > > Ambari-agent would not talk to ambari-server. > > > INFO 2015-11-14 15:26:48,572 main.py:289 - Connecting to Ambari server at > https://sandbox.hortonworks.com:8440 (10.0.2.15) > INFO 2015-11-14 15:26:48,572 NetUtil.py:59 - Connecting to > https://sandbox.hortonworks.com:8440/ca > ERROR 2015-11-14 15:26:48,693 NetUtil.py:77 - [SSL: > CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) > ERROR 2015-11-14 15:26:48,693 NetUtil.py:78 - SSLError: Failed to > connect. Please check openssl library versions. > Refer to: https://bugzilla.redhat.com/show_bug.cgi?id=1022468 for more > details. > WARNING 2015-11-14 15:26:48,695 NetUtil.py:105 - Server at > https://sandbox.hortonworks.com:8440 is not reachable, sleeping for 10 > seconds... > > STR might include enabling two-way ssl. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21098) Integrate Titan into Ambari
[ https://issues.apache.org/jira/browse/AMBARI-21098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-21098: --- Labels: titan (was: ) > Integrate Titan into Ambari > --- > > Key: AMBARI-21098 > URL: https://issues.apache.org/jira/browse/AMBARI-21098 > Project: Ambari > Issue Type: Story >Affects Versions: trunk, 2.5.1 >Reporter: Hui Cao >Assignee: Hui Cao > Labels: titan > Fix For: trunk > > Original Estimate: 504h > Remaining Estimate: 504h > > Titan is designed to support the processing of graphs so large that they > require storage and computational capacities beyond what a single machine can > provide. Scaling graph data processing for real time traversals and > analytical queries is Titan’s foundational benefit. > This story is aimed to integrate Titan into Ambari so that it can be > installed and managed by Ambari from web UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21098) Integrate Titan into Ambari
[ https://issues.apache.org/jira/browse/AMBARI-21098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-21098: --- Affects Version/s: 2.5.1 trunk > Integrate Titan into Ambari > --- > > Key: AMBARI-21098 > URL: https://issues.apache.org/jira/browse/AMBARI-21098 > Project: Ambari > Issue Type: Story >Affects Versions: trunk, 2.5.1 >Reporter: Hui Cao >Assignee: Hui Cao > Fix For: trunk > > Original Estimate: 504h > Remaining Estimate: 504h > > Titan is designed to support the processing of graphs so large that they > require storage and computational capacities beyond what a single machine can > provide. Scaling graph data processing for real time traversals and > analytical queries is Titan’s foundational benefit. > This story is aimed to integrate Titan into Ambari so that it can be > installed and managed by Ambari from web UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-21098) Integrate Titan into Ambari
[ https://issues.apache.org/jira/browse/AMBARI-21098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-21098: --- Fix Version/s: trunk > Integrate Titan into Ambari > --- > > Key: AMBARI-21098 > URL: https://issues.apache.org/jira/browse/AMBARI-21098 > Project: Ambari > Issue Type: Story >Affects Versions: trunk, 2.5.1 >Reporter: Hui Cao >Assignee: Hui Cao > Fix For: trunk > > Original Estimate: 504h > Remaining Estimate: 504h > > Titan is designed to support the processing of graphs so large that they > require storage and computational capacities beyond what a single machine can > provide. Scaling graph data processing for real time traversals and > analytical queries is Titan’s foundational benefit. > This story is aimed to integrate Titan into Ambari so that it can be > installed and managed by Ambari from web UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20825) check_ambari_permissions.py does not run for all the files and directories listed
[ https://issues.apache.org/jira/browse/AMBARI-20825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-20825: --- Resolution: Fixed Fix Version/s: trunk Status: Resolved (was: Patch Available) > check_ambari_permissions.py does not run for all the files and directories > listed > - > > Key: AMBARI-20825 > URL: https://issues.apache.org/jira/browse/AMBARI-20825 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.0, 2.4.2 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: trunk, 2.5.0 > > Attachments: AMBARI-20825.patch > > > ambari-server/src/main/resources/scripts/check_ambari_permissions.py script > introduced in branch 2.5.0 and published here > (https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.0) > to solve Public Vulnerability: > https://nvd.nist.gov/vuln/detail/CVE-2017-5642 > only works partially. > There is a bug and it will only handle the last directory/file when there > are multiple directories/files listed. > So the vulnerability is not totally resolved. > For example files under /etc/ambari-server/conf/ -such as ambari.properties- > are not revised -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-20454) Some Ambari configuration should be managed similar to other configuration
[ https://issues.apache.org/jira/browse/AMBARI-20454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron reassigned AMBARI-20454: -- Assignee: Juanjo Marron > Some Ambari configuration should be managed similar to other configuration > --- > > Key: AMBARI-20454 > URL: https://issues.apache.org/jira/browse/AMBARI-20454 > Project: Ambari > Issue Type: New Feature > Components: ambari-server, ambari-web >Reporter: Tuong Truong >Assignee: Juanjo Marron > > Currently, Ambari has a number of configuration in ambari.properties and > quite a few other such as service check time out, directory permission that > are hard coded. This make it hard to manage Ambari customization to > better work with the cluster.Many of these properties should be managed > in Ambari similar to service configuration for better version control, and > upgrading from release to release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (AMBARI-20825) check_ambari_permissions.py does not run for all the files and directories listed
[ https://issues.apache.org/jira/browse/AMBARI-20825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15981969#comment-15981969 ] Juanjo Marron commented on AMBARI-20825: Submitted to branch-2.5: https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=56c0e736d1a26e6a8d1552db26073df6535b935d And trunk branch: https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=acde08995f46b67f0acd656f6a52889385317217 > check_ambari_permissions.py does not run for all the files and directories > listed > - > > Key: AMBARI-20825 > URL: https://issues.apache.org/jira/browse/AMBARI-20825 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.0, 2.4.2 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 2.5.0 > > Attachments: AMBARI-20825.patch > > > ambari-server/src/main/resources/scripts/check_ambari_permissions.py script > introduced in branch 2.5.0 and published here > (https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.0) > to solve Public Vulnerability: > https://nvd.nist.gov/vuln/detail/CVE-2017-5642 > only works partially. > There is a bug and it will only handle the last directory/file when there > are multiple directories/files listed. > So the vulnerability is not totally resolved. > For example files under /etc/ambari-server/conf/ -such as ambari.properties- > are not revised -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20825) check_ambari_permissions.py does not run for all the files and directories listed
[ https://issues.apache.org/jira/browse/AMBARI-20825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-20825: --- Affects Version/s: trunk > check_ambari_permissions.py does not run for all the files and directories > listed > - > > Key: AMBARI-20825 > URL: https://issues.apache.org/jira/browse/AMBARI-20825 > Project: Ambari > Issue Type: Bug >Affects Versions: trunk, 2.5.0, 2.4.2 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 2.5.0 > > Attachments: AMBARI-20825.patch > > > ambari-server/src/main/resources/scripts/check_ambari_permissions.py script > introduced in branch 2.5.0 and published here > (https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.0) > to solve Public Vulnerability: > https://nvd.nist.gov/vuln/detail/CVE-2017-5642 > only works partially. > There is a bug and it will only handle the last directory/file when there > are multiple directories/files listed. > So the vulnerability is not totally resolved. > For example files under /etc/ambari-server/conf/ -such as ambari.properties- > are not revised -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20825) check_ambari_permissions.py does not run for all the files and directories listed
[ https://issues.apache.org/jira/browse/AMBARI-20825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-20825: --- Status: Patch Available (was: Open) > check_ambari_permissions.py does not run for all the files and directories > listed > - > > Key: AMBARI-20825 > URL: https://issues.apache.org/jira/browse/AMBARI-20825 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.4.2 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 2.5.0 > > Attachments: AMBARI-20825.patch > > > ambari-server/src/main/resources/scripts/check_ambari_permissions.py script > introduced in branch 2.5.0 and published here > (https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.0) > to solve Public Vulnerability: > https://nvd.nist.gov/vuln/detail/CVE-2017-5642 > only works partially. > There is a bug and it will only handle the last directory/file when there > are multiple directories/files listed. > So the vulnerability is not totally resolved. > For example files under /etc/ambari-server/conf/ -such as ambari.properties- > are not revised -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20825) check_ambari_permissions.py does not run for all the files and directories listed
[ https://issues.apache.org/jira/browse/AMBARI-20825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-20825: --- Attachment: AMBARI-20825.patch > check_ambari_permissions.py does not run for all the files and directories > listed > - > > Key: AMBARI-20825 > URL: https://issues.apache.org/jira/browse/AMBARI-20825 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.4.2 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 2.5.0 > > Attachments: AMBARI-20825.patch > > > ambari-server/src/main/resources/scripts/check_ambari_permissions.py script > introduced in branch 2.5.0 and published here > (https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.0) > to solve Public Vulnerability: > https://nvd.nist.gov/vuln/detail/CVE-2017-5642 > only works partially. > There is a bug and it will only handle the last directory/file when there > are multiple directories/files listed. > So the vulnerability is not totally resolved. > For example files under /etc/ambari-server/conf/ -such as ambari.properties- > are not revised -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20825) check_ambari_permissions.py does not run for all the files and directories listed
[ https://issues.apache.org/jira/browse/AMBARI-20825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-20825: --- Summary: check_ambari_permissions.py does not run for all the files and directories listed (was: check_ambari_permissions.py does not run in all the files and directories listed) > check_ambari_permissions.py does not run for all the files and directories > listed > - > > Key: AMBARI-20825 > URL: https://issues.apache.org/jira/browse/AMBARI-20825 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.4.2 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 2.5.0 > > > ambari-server/src/main/resources/scripts/check_ambari_permissions.py script > introduced in branch 2.5.0 and published here > (https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.0) > to solve Public Vulnerability: > https://nvd.nist.gov/vuln/detail/CVE-2017-5642 > only works partially. > There is a bug and it will only handle the last directory/file when there > are multiple directories/files listed. > So the vulnerability is not totally resolved. > For example files under /etc/ambari-server/conf/ -such as ambari.properties- > are not revised -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (AMBARI-20825) check_ambari_permissions.py does not run in all the files and directories listed
[ https://issues.apache.org/jira/browse/AMBARI-20825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-20825: --- Description: ambari-server/src/main/resources/scripts/check_ambari_permissions.py script introduced in branch 2.5.0 and published here (https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.0) to solve Public Vulnerability: https://nvd.nist.gov/vuln/detail/CVE-2017-5642 only works partially. There is a bug and it will only handle the last directory/file when there are multiple directories/files listed. So the vulnerability is not totally resolved. For example files under /etc/ambari-server/conf/ -such as ambari.properties- are not revised was: ambari-server/src/main/resources/scripts/check_ambari_permissions.py script introduced in branch 2.5.0 and published here (https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.0) to solve Public Vulnerability: https://nvd.nist.gov/vuln/detail/CVE-2017-5642 only works partially. There is a bug and it will only handle the last directory/file when there are multiple directories/files listed. So vulnerability is still present. For example files under /etc/ambari-server/conf/ Such as ambari.properties are not revised > check_ambari_permissions.py does not run in all the files and directories > listed > > > Key: AMBARI-20825 > URL: https://issues.apache.org/jira/browse/AMBARI-20825 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.4.2 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 2.5.0 > > > ambari-server/src/main/resources/scripts/check_ambari_permissions.py script > introduced in branch 2.5.0 and published here > (https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.0) > to solve Public Vulnerability: > https://nvd.nist.gov/vuln/detail/CVE-2017-5642 > only works partially. > There is a bug and it will only handle the last directory/file when there > are multiple directories/files listed. > So the vulnerability is not totally resolved. > For example files under /etc/ambari-server/conf/ -such as ambari.properties- > are not revised -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (AMBARI-20825) check_ambari_permissions.py does not run in all the files and directories listed
Juanjo Marron created AMBARI-20825: -- Summary: check_ambari_permissions.py does not run in all the files and directories listed Key: AMBARI-20825 URL: https://issues.apache.org/jira/browse/AMBARI-20825 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0, 2.4.2 Reporter: Juanjo Marron Assignee: Juanjo Marron Fix For: 2.5.0 ambari-server/src/main/resources/scripts/check_ambari_permissions.py script introduced in branch 2.5.0 and published here (https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Vulnerabilities#AmbariVulnerabilities-FixedinAmbari2.5.0) to solve Public Vulnerability: https://nvd.nist.gov/vuln/detail/CVE-2017-5642 only works partially. There is a bug and it will only handle the last directory/file when there are multiple directories/files listed. So vulnerability is still present. For example files under /etc/ambari-server/conf/ Such as ambari.properties are not revised -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-19906) Ambari Log Search – Single Click Log Collection and Download.
[ https://issues.apache.org/jira/browse/AMBARI-19906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron reassigned AMBARI-19906: -- Assignee: Juanjo Marron > Ambari Log Search – Single Click Log Collection and Download. > - > > Key: AMBARI-19906 > URL: https://issues.apache.org/jira/browse/AMBARI-19906 > Project: Ambari > Issue Type: Story > Components: ambari-logsearch, logsearch >Affects Versions: 2.4.0, 2.4.2 >Reporter: George Mathew >Assignee: Juanjo Marron > Fix For: trunk > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (AMBARI-10642) Mechanism to automatically update Ambari versions in component upgrades
[ https://issues.apache.org/jira/browse/AMBARI-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron reassigned AMBARI-10642: -- Assignee: Juanjo Marron > Mechanism to automatically update Ambari versions in component upgrades > --- > > Key: AMBARI-10642 > URL: https://issues.apache.org/jira/browse/AMBARI-10642 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, ambari-web >Affects Versions: 2.0.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron >Priority: Minor > Fix For: 2.4.0 > > > Currently, Ambari reflects the version of the component in the UI in: > - The installation wizard when adding services. > - Once services are installed under Ambari -> Admin -> Repositories. > These versions are read from the metainfo.xml files included in each service > in the Ambari code. > When a service is updated hosting a new rpm in the yum repo, if it changes > also the component version number, the version property in the metainfo file > should be edited as well to show this version change > This minor change forces to rebuild the Ambari server rpm and reinstall it > to modified the version value. > Update Ambari versions automatically could be provided as part of Ambari > offering a mechanism that reads the version of the component from the > installed rpm package and write it on the metainfo file of the service -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-10642) Mechanism to automatically update Ambari versions in component upgrades
[ https://issues.apache.org/jira/browse/AMBARI-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526702#comment-15526702 ] Juanjo Marron edited comment on AMBARI-10642 at 9/27/16 4:47 PM: - Solve by AMBARI-15636: Use a new concept called a Version Definition File (VDF) to support installation was (Author: jmarron): Solve in AMBARI-15636: Use a new concept called a Version Definition File (VDF) to support installation > Mechanism to automatically update Ambari versions in component upgrades > --- > > Key: AMBARI-10642 > URL: https://issues.apache.org/jira/browse/AMBARI-10642 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, ambari-web >Affects Versions: 2.0.0 >Reporter: Juanjo Marron >Priority: Minor > Fix For: 2.4.0 > > > Currently, Ambari reflects the version of the component in the UI in: > - The installation wizard when adding services. > - Once services are installed under Ambari -> Admin -> Repositories. > These versions are read from the metainfo.xml files included in each service > in the Ambari code. > When a service is updated hosting a new rpm in the yum repo, if it changes > also the component version number, the version property in the metainfo file > should be edited as well to show this version change > This minor change forces to rebuild the Ambari server rpm and reinstall it > to modified the version value. > Update Ambari versions automatically could be provided as part of Ambari > offering a mechanism that reads the version of the component from the > installed rpm package and write it on the metainfo file of the service -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-10642) Mechanism to automatically update Ambari versions in component upgrades
[ https://issues.apache.org/jira/browse/AMBARI-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron resolved AMBARI-10642. Resolution: Duplicate Fix Version/s: 2.4.0 > Mechanism to automatically update Ambari versions in component upgrades > --- > > Key: AMBARI-10642 > URL: https://issues.apache.org/jira/browse/AMBARI-10642 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, ambari-web >Affects Versions: 2.0.0 >Reporter: Juanjo Marron >Priority: Minor > Fix For: 2.4.0 > > > Currently, Ambari reflects the version of the component in the UI in: > - The installation wizard when adding services. > - Once services are installed under Ambari -> Admin -> Repositories. > These versions are read from the metainfo.xml files included in each service > in the Ambari code. > When a service is updated hosting a new rpm in the yum repo, if it changes > also the component version number, the version property in the metainfo file > should be edited as well to show this version change > This minor change forces to rebuild the Ambari server rpm and reinstall it > to modified the version value. > Update Ambari versions automatically could be provided as part of Ambari > offering a mechanism that reads the version of the component from the > installed rpm package and write it on the metainfo file of the service -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-10642) Mechanism to automatically update Ambari versions in component upgrades
[ https://issues.apache.org/jira/browse/AMBARI-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15526702#comment-15526702 ] Juanjo Marron commented on AMBARI-10642: Solve in AMBARI-15636: Use a new concept called a Version Definition File (VDF) to support installation > Mechanism to automatically update Ambari versions in component upgrades > --- > > Key: AMBARI-10642 > URL: https://issues.apache.org/jira/browse/AMBARI-10642 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, ambari-web >Affects Versions: 2.0.0 >Reporter: Juanjo Marron >Priority: Minor > > Currently, Ambari reflects the version of the component in the UI in: > - The installation wizard when adding services. > - Once services are installed under Ambari -> Admin -> Repositories. > These versions are read from the metainfo.xml files included in each service > in the Ambari code. > When a service is updated hosting a new rpm in the yum repo, if it changes > also the component version number, the version property in the metainfo file > should be edited as well to show this version change > This minor change forces to rebuild the Ambari server rpm and reinstall it > to modified the version value. > Update Ambari versions automatically could be provided as part of Ambari > offering a mechanism that reads the version of the component from the > installed rpm package and write it on the metainfo file of the service -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13238) MySQL service status needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13238: --- Assignee: Vishal Ghugare (was: Juanjo Marron) > MySQL service status needs to be more robust > > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Thomas Friedrich >Assignee: Vishal Ghugare >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-13238.patch > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-13238) MySQL service status needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron reassigned AMBARI-13238: -- Assignee: Juanjo Marron (was: Vishal Ghugare) > MySQL service status needs to be more robust > > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Thomas Friedrich >Assignee: Juanjo Marron >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-13238.patch > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13363) Stack featurization: Enhance Ambari framework to facilitate alternative stack definition
[ https://issues.apache.org/jira/browse/AMBARI-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13363: --- Summary: Stack featurization: Enhance Ambari framework to facilitate alternative stack definition (was: Stack featurization: Enhance Ambari framework to support alternative stack definition) > Stack featurization: Enhance Ambari framework to facilitate alternative > stack definition > - > > Key: AMBARI-13363 > URL: https://issues.apache.org/jira/browse/AMBARI-13363 > Project: Ambari > Issue Type: Epic > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0 >Reporter: Tuong Truong >Assignee: Juanjo Marron > Labels: common-services, parametize > Fix For: 2.4.0 > > Attachments: AMBARI-13363 Enhance Ambari framework to support > alternative stack definition.pdf > > > Currently, Ambari common services > (git/ambari/ambari-server/src/main/resources/common-services/*) codes contain > specific logic about HDP stack including stack name (HDP), version (2.0, 2.1, > 2.2...), and install location (/usr/hdp). > The refactor of services from the stack into a common area is a first > important steps. However, we need refactor stack specific information out > these services so that they can be reused by other distribution and stack > definition as part of the ODP initiative. > We hope to use this feature JIRA and its subtask to deliver a setup of > changes that will make the common services codes fully parameterized and can > be reused easily by any other distribution of Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13363) Stack featurization: Enhance Ambari framework to facilitate alternative stack definitions
[ https://issues.apache.org/jira/browse/AMBARI-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13363: --- Summary: Stack featurization: Enhance Ambari framework to facilitate alternative stack definitions (was: Stack featurization: Enhance Ambari framework to facilitate alternative stack definition) > Stack featurization: Enhance Ambari framework to facilitate alternative > stack definitions > -- > > Key: AMBARI-13363 > URL: https://issues.apache.org/jira/browse/AMBARI-13363 > Project: Ambari > Issue Type: Epic > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0 >Reporter: Tuong Truong >Assignee: Juanjo Marron > Labels: common-services, parametize > Fix For: 2.4.0 > > Attachments: AMBARI-13363 Enhance Ambari framework to support > alternative stack definition.pdf > > > Currently, Ambari common services > (git/ambari/ambari-server/src/main/resources/common-services/*) codes contain > specific logic about HDP stack including stack name (HDP), version (2.0, 2.1, > 2.2...), and install location (/usr/hdp). > The refactor of services from the stack into a common area is a first > important steps. However, we need refactor stack specific information out > these services so that they can be reused by other distribution and stack > definition as part of the ODP initiative. > We hope to use this feature JIRA and its subtask to deliver a setup of > changes that will make the common services codes fully parameterized and can > be reused easily by any other distribution of Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13364) Parameterize stack information used by common services
[ https://issues.apache.org/jira/browse/AMBARI-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13364: --- Summary: Parameterize stack information used by common services (was: Stack featurization: Parameterize stack information used by common services) > Parameterize stack information used by common services > -- > > Key: AMBARI-13364 > URL: https://issues.apache.org/jira/browse/AMBARI-13364 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.1.0, 2.2.0 >Reporter: Tuong Truong >Assignee: Juanjo Marron > Fix For: 2.4.0 > > Attachments: AMBARI-13364.patch, stack_featurizer.patch > > > This feature will add a basic framework to remove hardcoded stack information > out of the common services and use parameter to get access to stack > information. Currently, common services hardcodes much information specific > to Hortonworks' HDP stack including name (HDP), specific versions (2.0, 2.1, > 2.2), and install location. This feature will propose a way of > configuration these information and parameterize them into the services for > reference as require. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13364) Stack featurization: Parameterize stack information used by common services
[ https://issues.apache.org/jira/browse/AMBARI-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13364: --- Summary: Stack featurization: Parameterize stack information used by common services (was: Parameterize stack information used by common services) > Stack featurization: Parameterize stack information used by common services > > > Key: AMBARI-13364 > URL: https://issues.apache.org/jira/browse/AMBARI-13364 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.1.0, 2.2.0 >Reporter: Tuong Truong >Assignee: Juanjo Marron > Fix For: 2.4.0 > > Attachments: AMBARI-13364.patch, stack_featurizer.patch > > > This feature will add a basic framework to remove hardcoded stack information > out of the common services and use parameter to get access to stack > information. Currently, common services hardcodes much information specific > to Hortonworks' HDP stack including name (HDP), specific versions (2.0, 2.1, > 2.2), and install location. This feature will propose a way of > configuration these information and parameterize them into the services for > reference as require. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13238) MySQL service status needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13238: --- Attachment: AMBARI-13238.patch > MySQL service status needs to be more robust > > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Thomas Friedrich >Assignee: Juanjo Marron >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-13238.patch > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13238) MySQL service status needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13238: --- Attachment: (was: AMBARI-13238.patch) > MySQL service status needs to be more robust > > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Thomas Friedrich >Assignee: Juanjo Marron >Priority: Minor > Fix For: 3.0.0 > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13238) MySQL service status needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13238: --- Summary: MySQL service status needs to be more robust (was: MySQL service check needs to be more robust) > MySQL service status needs to be more robust > > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Thomas Friedrich >Assignee: Juanjo Marron >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-13238.patch > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13238) MySQL service check needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13238: --- Status: Patch Available (was: Open) > MySQL service check needs to be more robust > --- > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Thomas Friedrich >Assignee: Juanjo Marron >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-13238.patch > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-13238) MySQL service check needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15330155#comment-15330155 ] Juanjo Marron commented on AMBARI-13238: A new patch is proposed based on the reviews added to the previous one: https://reviews.apache.org/r/39146/ The patch relies now on the pid (similar to other status check). pid_file is not known a priori for mySQL (it is not a service property similar to other ambari components) and it depends on the OS. The pid file location is obatined with "mysqladmin variables" command (which seems recognized by all the Ambari supported OS). The Hive MySQL server instance is started without passing in any parameters so It uses the default configuration. Any other MySQL instance that could be running on the machine would need to be started with explicit config. Hence just running mysqladmin will return the values for the Hive MySQL instance. The pid file name is parsed by a new method which has been created to obtain it from the mysqladmin variables return. Status action relies now on check_process_status() which is already an ambari function. Unit Test have been modified accordingly to avoid the pgrep verification that could create conflicts with others mysql instances working on the same node. > MySQL service check needs to be more robust > --- > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Thomas Friedrich >Assignee: Juanjo Marron >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-13238.patch > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13238) MySQL service check needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13238: --- Attachment: AMBARI-13238.patch > MySQL service check needs to be more robust > --- > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Thomas Friedrich >Assignee: Juanjo Marron >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-13238.patch > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13238) MySQL service check needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13238: --- Attachment: AMBARI-13238.patch > MySQL service check needs to be more robust > --- > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Thomas Friedrich >Assignee: Juanjo Marron >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-13238.patch > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13238) MySQL service check needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13238: --- Affects Version/s: 2.2.0 Fix Version/s: 3.0.0 > MySQL service check needs to be more robust > --- > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Thomas Friedrich >Assignee: Juanjo Marron >Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-13238.patch > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-13238) MySQL service check needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-13238: --- Status: Open (was: Patch Available) > MySQL service check needs to be more robust > --- > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0 >Reporter: Thomas Friedrich >Assignee: Juanjo Marron >Priority: Minor > Attachments: AMBARI-13238.patch > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-13238) MySQL service check needs to be more robust
[ https://issues.apache.org/jira/browse/AMBARI-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron reassigned AMBARI-13238: -- Assignee: Juanjo Marron (was: Thomas Friedrich) > MySQL service check needs to be more robust > --- > > Key: AMBARI-13238 > URL: https://issues.apache.org/jira/browse/AMBARI-13238 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0 >Reporter: Thomas Friedrich >Assignee: Juanjo Marron >Priority: Minor > Attachments: AMBARI-13238.patch > > > The mysql service check in mysql_service.py simply checks for the existence > of a mysqld process. If an unrelated mysqld service is running on the same > node and Hive is configured to run with a MySQL db, the Hive start action > won't start the MySQL server instance and the metastore connection fails. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-16101) clean up import * at common-services level
[ https://issues.apache.org/jira/browse/AMBARI-16101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron resolved AMBARI-16101. Resolution: Fixed > clean up import * at common-services level > -- > > Key: AMBARI-16101 > URL: https://issues.apache.org/jira/browse/AMBARI-16101 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.2.1 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This JIRA and subtasks will clean up import * from resource_management and > replace it for specific imports -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AMBARI-13363) Enhance Ambari framework to support alternative stack definition
[ https://issues.apache.org/jira/browse/AMBARI-13363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron reassigned AMBARI-13363: -- Assignee: Juanjo Marron > Enhance Ambari framework to support alternative stack definition > > > Key: AMBARI-13363 > URL: https://issues.apache.org/jira/browse/AMBARI-13363 > Project: Ambari > Issue Type: Epic > Components: ambari-server >Affects Versions: 2.0.0, 2.1.0 >Reporter: Tuong Truong >Assignee: Juanjo Marron > Labels: common-services, parametize > Fix For: 2.4.0 > > Attachments: AMBARI-13363 Enhance Ambari framework to support > alternative stack definition.pdf > > > Currently, Ambari common services > (git/ambari/ambari-server/src/main/resources/common-services/*) codes contain > specific logic about HDP stack including stack name (HDP), version (2.0, 2.1, > 2.2...), and install location (/usr/hdp). > The refactor of services from the stack into a common area is a first > important steps. However, we need refactor stack specific information out > these services so that they can be reused by other distribution and stack > definition as part of the ODP initiative. > We hope to use this feature JIRA and its subtask to deliver a setup of > changes that will make the common services codes fully parameterized and can > be reused easily by any other distribution of Ambari. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-16101) clean up import * at common-services level
[ https://issues.apache.org/jira/browse/AMBARI-16101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron reopened AMBARI-16101: > clean up import * at common-services level > -- > > Key: AMBARI-16101 > URL: https://issues.apache.org/jira/browse/AMBARI-16101 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.2.1 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This JIRA and subtasks will clean up import * from resource_management and > replace it for specific imports -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16175) clean up import * : Accumulo, AMS Atlas, Falcon, Flume and Ganglia
[ https://issues.apache.org/jira/browse/AMBARI-16175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16175: --- Summary: clean up import * : Accumulo, AMS Atlas, Falcon, Flume and Ganglia (was: clean up import * : Accumulo, Atlas, Falcon, Flume and Ganglia) > clean up import * : Accumulo, AMS Atlas, Falcon, Flume and Ganglia > -- > > Key: AMBARI-16175 > URL: https://issues.apache.org/jira/browse/AMBARI-16175 > Project: Ambari > Issue Type: Sub-task > Components: ambari-agent, ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-16175.patch > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for: > Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16175) clean up import * : Accumulo, Atlas, Falcon, Flume and Ganglia
[ https://issues.apache.org/jira/browse/AMBARI-16175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16175: --- Summary: clean up import * : Accumulo, Atlas, Falcon, Flume and Ganglia (was: clean up import * : Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia) > clean up import * : Accumulo, Atlas, Falcon, Flume and Ganglia > -- > > Key: AMBARI-16175 > URL: https://issues.apache.org/jira/browse/AMBARI-16175 > Project: Ambari > Issue Type: Sub-task > Components: ambari-agent, ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-16175.patch > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for: > Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16916) clean up import * for SPARK2 service
[ https://issues.apache.org/jira/browse/AMBARI-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16916: --- Status: Patch Available (was: Open) > clean up import * for SPARK2 service > - > > Key: AMBARI-16916 > URL: https://issues.apache.org/jira/browse/AMBARI-16916 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16916.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16916) clean up import * for SPARK2 service
[ https://issues.apache.org/jira/browse/AMBARI-16916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16916: --- Attachment: AMBARI-16916.patch > clean up import * for SPARK2 service > - > > Key: AMBARI-16916 > URL: https://issues.apache.org/jira/browse/AMBARI-16916 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16916.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16797) clean up import * for SPARK service
[ https://issues.apache.org/jira/browse/AMBARI-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16797: --- Resolution: Resolved Status: Resolved (was: Patch Available) > clean up import * for SPARK service > --- > > Key: AMBARI-16797 > URL: https://issues.apache.org/jira/browse/AMBARI-16797 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16797.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-16101) clean up import * at common-services level
[ https://issues.apache.org/jira/browse/AMBARI-16101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron resolved AMBARI-16101. Resolution: Resolved > clean up import * at common-services level > -- > > Key: AMBARI-16101 > URL: https://issues.apache.org/jira/browse/AMBARI-16101 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.2.1 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This JIRA and subtasks will clean up import * from resource_management and > replace it for specific imports -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16672) clean up import * for OOZIE service
[ https://issues.apache.org/jira/browse/AMBARI-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16672: --- Resolution: Resolved Status: Resolved (was: Patch Available) > clean up import * for OOZIE service > --- > > Key: AMBARI-16672 > URL: https://issues.apache.org/jira/browse/AMBARI-16672 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16672.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-16797) clean up import * for SPARK service
[ https://issues.apache.org/jira/browse/AMBARI-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312676#comment-15312676 ] Juanjo Marron commented on AMBARI-16797: Thanks Jayush > clean up import * for SPARK service > --- > > Key: AMBARI-16797 > URL: https://issues.apache.org/jira/browse/AMBARI-16797 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16797.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16797) clean up import * for SPARK service
[ https://issues.apache.org/jira/browse/AMBARI-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16797: --- Attachment: (was: AMBARI-16797.patch) > clean up import * for SPARK service > --- > > Key: AMBARI-16797 > URL: https://issues.apache.org/jira/browse/AMBARI-16797 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16797.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16797) clean up import * for SPARK service
[ https://issues.apache.org/jira/browse/AMBARI-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16797: --- Attachment: AMBARI-16797.patch > clean up import * for SPARK service > --- > > Key: AMBARI-16797 > URL: https://issues.apache.org/jira/browse/AMBARI-16797 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16797.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16797) clean up import * for SPARK service
[ https://issues.apache.org/jira/browse/AMBARI-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16797: --- Status: Patch Available (was: Open) > clean up import * for SPARK service > --- > > Key: AMBARI-16797 > URL: https://issues.apache.org/jira/browse/AMBARI-16797 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16797.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16797) clean up import * for SPARK service
[ https://issues.apache.org/jira/browse/AMBARI-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16797: --- Status: Open (was: Patch Available) > clean up import * for SPARK service > --- > > Key: AMBARI-16797 > URL: https://issues.apache.org/jira/browse/AMBARI-16797 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16797.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16672) clean up import * for OOZIE service
[ https://issues.apache.org/jira/browse/AMBARI-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16672: --- Attachment: (was: AMBARI-16672.patch) > clean up import * for OOZIE service > --- > > Key: AMBARI-16672 > URL: https://issues.apache.org/jira/browse/AMBARI-16672 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16672.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16672) clean up import * for OOZIE service
[ https://issues.apache.org/jira/browse/AMBARI-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16672: --- Attachment: AMBARI-16672.patch > clean up import * for OOZIE service > --- > > Key: AMBARI-16672 > URL: https://issues.apache.org/jira/browse/AMBARI-16672 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16672.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16672) clean up import * for OOZIE service
[ https://issues.apache.org/jira/browse/AMBARI-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16672: --- Status: Patch Available (was: Open) > clean up import * for OOZIE service > --- > > Key: AMBARI-16672 > URL: https://issues.apache.org/jira/browse/AMBARI-16672 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16672.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16672) clean up import * for OOZIE service
[ https://issues.apache.org/jira/browse/AMBARI-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16672: --- Status: Open (was: Patch Available) > clean up import * for OOZIE service > --- > > Key: AMBARI-16672 > URL: https://issues.apache.org/jira/browse/AMBARI-16672 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16672.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16916) clean up import * for SPARK2 service
Juanjo Marron created AMBARI-16916: -- Summary: clean up import * for SPARK2 service Key: AMBARI-16916 URL: https://issues.apache.org/jira/browse/AMBARI-16916 Project: Ambari Issue Type: Technical task Components: ambari-agent, ambari-server Affects Versions: 2.1.0, 2.2.0, 2.4.0 Reporter: Juanjo Marron Assignee: Juanjo Marron Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16743) clean up import * for RANGER service
[ https://issues.apache.org/jira/browse/AMBARI-16743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16743: --- Attachment: AMBARI-16743.patch > clean up import * for RANGER service > > > Key: AMBARI-16743 > URL: https://issues.apache.org/jira/browse/AMBARI-16743 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16743.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16743) clean up import * for RANGER service
[ https://issues.apache.org/jira/browse/AMBARI-16743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16743: --- Status: Patch Available (was: Open) > clean up import * for RANGER service > > > Key: AMBARI-16743 > URL: https://issues.apache.org/jira/browse/AMBARI-16743 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16743.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16849) clean up import * for YARN service
[ https://issues.apache.org/jira/browse/AMBARI-16849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16849: --- Attachment: AMBARI-16849.patch > clean up import * for YARN service > -- > > Key: AMBARI-16849 > URL: https://issues.apache.org/jira/browse/AMBARI-16849 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.4.0, 2.2.2 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16849.patch > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for YARN service -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16850) clean up import * for ZOOKEEPER service
[ https://issues.apache.org/jira/browse/AMBARI-16850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16850: --- Attachment: AMBARI-16850.patch > clean up import * for ZOOKEEPER service > --- > > Key: AMBARI-16850 > URL: https://issues.apache.org/jira/browse/AMBARI-16850 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16850.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16850) clean up import * for ZOOKEEPER service
[ https://issues.apache.org/jira/browse/AMBARI-16850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16850: --- Status: Patch Available (was: Open) > clean up import * for ZOOKEEPER service > --- > > Key: AMBARI-16850 > URL: https://issues.apache.org/jira/browse/AMBARI-16850 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16850.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16848) clean up import * for STORM, TEZ and ZEPPELIN services
[ https://issues.apache.org/jira/browse/AMBARI-16848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16848: --- Attachment: AMBARI-16848.patch > clean up import * for STORM, TEZ and ZEPPELIN services > -- > > Key: AMBARI-16848 > URL: https://issues.apache.org/jira/browse/AMBARI-16848 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16848.patch > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for: > Storm, Tez and Zeppelin services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16848) clean up import * for STORM, TEZ and ZEPPELIN services
[ https://issues.apache.org/jira/browse/AMBARI-16848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16848: --- Summary: clean up import * for STORM, TEZ and ZEPPELIN services (was: clean up import * for SQOOP, STORM, TEZ and ZEPPELIN services) > clean up import * for STORM, TEZ and ZEPPELIN services > -- > > Key: AMBARI-16848 > URL: https://issues.apache.org/jira/browse/AMBARI-16848 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for: > Sqoop, Storm, Tez and Zeppelin services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16848) clean up import * for STORM, TEZ and ZEPPELIN services
[ https://issues.apache.org/jira/browse/AMBARI-16848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16848: --- Description: Python code at at common-services level used generic imports form resource_management (from resource_management import *) Ideally, for easier code tracking and performance, these import should be more specific, such as: from resource_management.libraries.script.script import Script from resource_management.core.resources.system import Directory This subtask cleans up import * from resource_management and replace it for specific imports for: Storm, Tez and Zeppelin services was: Python code at at common-services level used generic imports form resource_management (from resource_management import *) Ideally, for easier code tracking and performance, these import should be more specific, such as: from resource_management.libraries.script.script import Script from resource_management.core.resources.system import Directory This subtask cleans up import * from resource_management and replace it for specific imports for: Sqoop, Storm, Tez and Zeppelin services > clean up import * for STORM, TEZ and ZEPPELIN services > -- > > Key: AMBARI-16848 > URL: https://issues.apache.org/jira/browse/AMBARI-16848 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for: > Storm, Tez and Zeppelin services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16850) clean up import * for ZOOKEEPER service
Juanjo Marron created AMBARI-16850: -- Summary: clean up import * for ZOOKEEPER service Key: AMBARI-16850 URL: https://issues.apache.org/jira/browse/AMBARI-16850 Project: Ambari Issue Type: Technical task Components: ambari-agent, ambari-server Affects Versions: 2.1.0, 2.2.0, 2.4.0 Reporter: Juanjo Marron Assignee: Juanjo Marron Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16849) clean up import * for YARN service
[ https://issues.apache.org/jira/browse/AMBARI-16849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16849: --- Description: Python code at at common-services level used generic imports form resource_management (from resource_management import *) Ideally, for easier code tracking and performance, these import should be more specific, such as: from resource_management.libraries.script.script import Script from resource_management.core.resources.system import Directory This subtask cleans up import * from resource_management and replace it for specific imports for YARN service > clean up import * for YARN service > -- > > Key: AMBARI-16849 > URL: https://issues.apache.org/jira/browse/AMBARI-16849 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.4.0, 2.2.2 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for YARN service -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16848) clean up import * for SQOOP, STORM, TEZ and ZEPPELIN services
[ https://issues.apache.org/jira/browse/AMBARI-16848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16848: --- Description: Python code at at common-services level used generic imports form resource_management (from resource_management import *) Ideally, for easier code tracking and performance, these import should be more specific, such as: from resource_management.libraries.script.script import Script from resource_management.core.resources.system import Directory This subtask cleans up import * from resource_management and replace it for specific imports for: Sqoop, Storm, Tez and Zeppelin services > clean up import * for SQOOP, STORM, TEZ and ZEPPELIN services > - > > Key: AMBARI-16848 > URL: https://issues.apache.org/jira/browse/AMBARI-16848 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for: > Sqoop, Storm, Tez and Zeppelin services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16848) clean up import * for SQOOP, STORM, TEZ and ZEPPELIN services
[ https://issues.apache.org/jira/browse/AMBARI-16848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16848: --- Summary: clean up import * for SQOOP, STORM, TEZ and ZEPPELIN services (was: clean up import * for SQOOP, STORM and TEZ service) > clean up import * for SQOOP, STORM, TEZ and ZEPPELIN services > - > > Key: AMBARI-16848 > URL: https://issues.apache.org/jira/browse/AMBARI-16848 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16848) clean up import * for SQOOP, STORM and TEZ service
[ https://issues.apache.org/jira/browse/AMBARI-16848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16848: --- Summary: clean up import * for SQOOP, STORM and TEZ service (was: clean up import * for STORM and TEZ service) > clean up import * for SQOOP, STORM and TEZ service > -- > > Key: AMBARI-16848 > URL: https://issues.apache.org/jira/browse/AMBARI-16848 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16849) clean up import * for YARN service
Juanjo Marron created AMBARI-16849: -- Summary: clean up import * for YARN service Key: AMBARI-16849 URL: https://issues.apache.org/jira/browse/AMBARI-16849 Project: Ambari Issue Type: Technical task Components: ambari-agent, ambari-server Affects Versions: 2.1.0, 2.4.0, 2.2.2 Reporter: Juanjo Marron Assignee: Juanjo Marron Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-16848) clean up import * for STORM and TEZ service
Juanjo Marron created AMBARI-16848: -- Summary: clean up import * for STORM and TEZ service Key: AMBARI-16848 URL: https://issues.apache.org/jira/browse/AMBARI-16848 Project: Ambari Issue Type: Technical task Components: ambari-agent, ambari-server Affects Versions: 2.1.0, 2.2.0, 2.4.0 Reporter: Juanjo Marron Assignee: Juanjo Marron Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16797) clean up import * for SPARK service
[ https://issues.apache.org/jira/browse/AMBARI-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16797: --- Status: Patch Available (was: Open) > clean up import * for SPARK service > --- > > Key: AMBARI-16797 > URL: https://issues.apache.org/jira/browse/AMBARI-16797 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16797.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16797) clean up import * for SPARK service
[ https://issues.apache.org/jira/browse/AMBARI-16797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16797: --- Attachment: AMBARI-16797.patch > clean up import * for SPARK service > --- > > Key: AMBARI-16797 > URL: https://issues.apache.org/jira/browse/AMBARI-16797 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16797.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16669) clean up import * for KNOX service
[ https://issues.apache.org/jira/browse/AMBARI-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16669: --- Status: Patch Available (was: In Progress) > clean up import * for KNOX service > -- > > Key: AMBARI-16669 > URL: https://issues.apache.org/jira/browse/AMBARI-16669 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16669.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16669) clean up import * for KNOX service
[ https://issues.apache.org/jira/browse/AMBARI-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16669: --- Attachment: AMBARI-16669.patch > clean up import * for KNOX service > -- > > Key: AMBARI-16669 > URL: https://issues.apache.org/jira/browse/AMBARI-16669 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16669.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16669) clean up import * for KNOX service
[ https://issues.apache.org/jira/browse/AMBARI-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16669: --- Status: In Progress (was: Patch Available) > clean up import * for KNOX service > -- > > Key: AMBARI-16669 > URL: https://issues.apache.org/jira/browse/AMBARI-16669 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16669) clean up import * for KNOX service
[ https://issues.apache.org/jira/browse/AMBARI-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16669: --- Attachment: AMBARI-16669.patch > clean up import * for KNOX service > -- > > Key: AMBARI-16669 > URL: https://issues.apache.org/jira/browse/AMBARI-16669 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16669) clean up import * for KNOX service
[ https://issues.apache.org/jira/browse/AMBARI-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16669: --- Attachment: (was: AMBARI-16669.patch) > clean up import * for KNOX service > -- > > Key: AMBARI-16669 > URL: https://issues.apache.org/jira/browse/AMBARI-16669 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16669) clean up import * for KNOX service
[ https://issues.apache.org/jira/browse/AMBARI-16669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16669: --- Attachment: (was: AMBARI-16669.patch) > clean up import * for KNOX service > -- > > Key: AMBARI-16669 > URL: https://issues.apache.org/jira/browse/AMBARI-16669 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-16362) clean up import * for HDFS service
[ https://issues.apache.org/jira/browse/AMBARI-16362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15294319#comment-15294319 ] Juanjo Marron edited comment on AMBARI-16362 at 5/20/16 9:58 PM: - Patch to import missing check_process_status new review request: https://reviews.apache.org/r/47669/ was (Author: jmarron): Patch to import missing check_process_status > clean up import * for HDFS service > -- > > Key: AMBARI-16362 > URL: https://issues.apache.org/jira/browse/AMBARI-16362 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.3.0, 2.2.0, 2.4.0, 2.2.1 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16362-2.patch, AMBARI-16362.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16362) clean up import * for HDFS service
[ https://issues.apache.org/jira/browse/AMBARI-16362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16362: --- Attachment: AMBARI-16362-2.patch Patch to import missing check_process_status > clean up import * for HDFS service > -- > > Key: AMBARI-16362 > URL: https://issues.apache.org/jira/browse/AMBARI-16362 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.3.0, 2.2.0, 2.4.0, 2.2.1 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16362-2.patch, AMBARI-16362.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (AMBARI-16175) clean up import * : Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia
[ https://issues.apache.org/jira/browse/AMBARI-16175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16175: --- Comment: was deleted (was: Patch to import missing check_process_status) > clean up import * : Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia > -- > > Key: AMBARI-16175 > URL: https://issues.apache.org/jira/browse/AMBARI-16175 > Project: Ambari > Issue Type: Sub-task > Components: ambari-agent, ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-16175.patch > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for: > Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16175) clean up import * : Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia
[ https://issues.apache.org/jira/browse/AMBARI-16175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16175: --- Attachment: (was: AMBARI-16362-2.patch) > clean up import * : Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia > -- > > Key: AMBARI-16175 > URL: https://issues.apache.org/jira/browse/AMBARI-16175 > Project: Ambari > Issue Type: Sub-task > Components: ambari-agent, ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-16175.patch > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for: > Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16175) clean up import * : Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia
[ https://issues.apache.org/jira/browse/AMBARI-16175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16175: --- Attachment: AMBARI-16362-2.patch Patch to import missing check_process_status > clean up import * : Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia > -- > > Key: AMBARI-16175 > URL: https://issues.apache.org/jira/browse/AMBARI-16175 > Project: Ambari > Issue Type: Sub-task > Components: ambari-agent, ambari-server >Affects Versions: 2.0.0, 2.1.0, 2.2.0, 2.4.0 >Reporter: Juanjo Marron >Assignee: Juanjo Marron >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-16175.patch, AMBARI-16362-2.patch > > > Python code at at common-services level used generic imports form > resource_management (from resource_management import *) > Ideally, for easier code tracking and performance, these import should be > more specific, such as: > from resource_management.libraries.script.script import Script > from resource_management.core.resources.system import Directory > This subtask cleans up import * from resource_management and replace it for > specific imports for: > Accumulo, Ambari-metrics, Atlas, Falcon, Flume and Ganglia services -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16362) clean up import * for HDFS service
[ https://issues.apache.org/jira/browse/AMBARI-16362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juanjo Marron updated AMBARI-16362: --- Attachment: (was: AMBARI-16362-2.patch) > clean up import * for HDFS service > -- > > Key: AMBARI-16362 > URL: https://issues.apache.org/jira/browse/AMBARI-16362 > Project: Ambari > Issue Type: Technical task > Components: ambari-agent, ambari-server >Affects Versions: 2.3.0, 2.2.0, 2.4.0, 2.2.1 >Reporter: Juanjo Marron >Assignee: Juanjo Marron > Fix For: 3.0.0 > > Attachments: AMBARI-16362.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
