ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shantanu Mundkur (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-11826) co-locate does not enforce co-location for a custom service
Date Wed, 10 Jun 2015 06:08:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-11826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shantanu Mundkur updated AMBARI-11826:
--------------------------------------
    Description: 
Defining "co-locate" for a component or a component dependency seems to be ignored or does
not seem to be working with a custom service. Additionally, auto-deploy in the component level
dependency did not get enforced.

For a component:

        <component>
          <name>MYSERVICE_MASTER1</name>
          <displayName>Myservice Master</displayName>
          <category>MASTER</category>
          <cardinality>1</cardinality>
          <versionAdvertised>true</versionAdvertised>
          <auto-deploy>
            <enabled>true</enabled>
            <co-locate>MYSERVICE/MYSERVICE_MASTER2</co-locate>
          </auto-deploy>
          <commandScript>
            <script>scripts/myservice-master1.py</script>
            <scriptType>PYTHON</scriptType>
            <timeout>600</timeout>
          </commandScript>
        </component>

MYSERVICE_MASTER1 and MYSERVICE_MASTER2 end up not co-located.

For a component dependency:
<services>
    <service>
        <name>MYSERVICE</name>
        .....
        <component>
          <name>MY_SERVER</name>
          <displayName>My Server</displayName>
          <category>MASTER</category>
          <cardinality>1</cardinality>
          <dependencies>
             <dependency>
                <name>SVC2/SVC2_MASTER</name>
                <scope>host</scope>
                <auto-deploy>
                  <enabled>true</enabled>
                  <co-locate>MYSERVICE/MY_SERVER</co-locate>
                </auto-deploy>
             </dependency>
          </dependencies>

MYSERVICE/MY_SERVER and SVC2/SVC2_MASTER end up not co-located.

  was:
Defining "co-locate" for a component or a component dependency seems to be ignored or does
not seem to be working with a custom service.

For a component:

        <component>
          <name>MYSERVICE_MASTER1</name>
          <displayName>Myservice Master</displayName>
          <category>MASTER</category>
          <cardinality>1</cardinality>
          <versionAdvertised>true</versionAdvertised>
          <auto-deploy>
            <enabled>true</enabled>
            <co-locate>MYSERVICE/MYSERVICE_MASTER2</co-locate>
          </auto-deploy>
          <commandScript>
            <script>scripts/myservice-master1.py</script>
            <scriptType>PYTHON</scriptType>
            <timeout>600</timeout>
          </commandScript>
        </component>

MYSERVICE_MASTER1 and MYSERVICE_MASTER2 end up not co-located.

For a component dependency:
<services>
    <service>
        <name>MYSERVICE</name>
        .....
        <component>
          <name>MY_SERVER</name>
          <displayName>My Server</displayName>
          <category>MASTER</category>
          <cardinality>1</cardinality>
          <dependencies>
             <dependency>
                <name>SVC2/SVC2_MASTER</name>
                <scope>host</scope>
                <auto-deploy>
                  <enabled>true</enabled>
                  <co-locate>MYSERVICE/MY_SERVER</co-locate>
                </auto-deploy>
             </dependency>
          </dependencies>

MYSERVICE/MY_SERVER and SVC2/SVC2_MASTER end up not co-located.


> co-locate does not enforce co-location for a custom service
> -----------------------------------------------------------
>
>                 Key: AMBARI-11826
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11826
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.7.0
>            Reporter: Shantanu Mundkur
>             Fix For: 2.1.0
>
>
> Defining "co-locate" for a component or a component dependency seems to be ignored or
does not seem to be working with a custom service. Additionally, auto-deploy in the component
level dependency did not get enforced.
> For a component:
>         <component>
>           <name>MYSERVICE_MASTER1</name>
>           <displayName>Myservice Master</displayName>
>           <category>MASTER</category>
>           <cardinality>1</cardinality>
>           <versionAdvertised>true</versionAdvertised>
>           <auto-deploy>
>             <enabled>true</enabled>
>             <co-locate>MYSERVICE/MYSERVICE_MASTER2</co-locate>
>           </auto-deploy>
>           <commandScript>
>             <script>scripts/myservice-master1.py</script>
>             <scriptType>PYTHON</scriptType>
>             <timeout>600</timeout>
>           </commandScript>
>         </component>
> MYSERVICE_MASTER1 and MYSERVICE_MASTER2 end up not co-located.
> For a component dependency:
> <services>
>     <service>
>         <name>MYSERVICE</name>
>         .....
>         <component>
>           <name>MY_SERVER</name>
>           <displayName>My Server</displayName>
>           <category>MASTER</category>
>           <cardinality>1</cardinality>
>           <dependencies>
>              <dependency>
>                 <name>SVC2/SVC2_MASTER</name>
>                 <scope>host</scope>
>                 <auto-deploy>
>                   <enabled>true</enabled>
>                   <co-locate>MYSERVICE/MY_SERVER</co-locate>
>                 </auto-deploy>
>              </dependency>
>           </dependencies>
> MYSERVICE/MY_SERVER and SVC2/SVC2_MASTER end up not co-located.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message