[jira] [Commented] (AURORA-1611) Add support for IP addresses instead of just hostnames in Announcer
[ https://issues.apache.org/jira/browse/AURORA-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185999#comment-15185999 ] Stephan Erb commented on AURORA-1611: - I don't quite understand this. Don't you have to announce those datacenter private IPs to in zookeeper? Otherwise you'd do an unnecessary hop over your exit router for any datacenter internal communication. > Add support for IP addresses instead of just hostnames in Announcer > --- > > Key: AURORA-1611 > URL: https://issues.apache.org/jira/browse/AURORA-1611 > Project: Aurora > Issue Type: Story >Reporter: Kunal Thakar > > The thermos announcer is passing hostnames in the serviceEndpoint object that > is sent to ZK. We want the announcer to send IPs instead or in addition to > the hostname that is passed along. What is the best way to achieve this? I am > thinking of adding a new attribute to the Endpoint struct > (https://github.com/apache/aurora/blob/master/commons/src/main/thrift/org/apache/aurora/common/thrift/endpoint.thrift). > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AURORA-1611) Add support for IP addresses instead of just hostnames in Announcer
[ https://issues.apache.org/jira/browse/AURORA-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kunal Thakar reopened AURORA-1611: -- While this approach works, it is causing a big usability issue for us. The mesos and aurora UIs now show private IPs instead of hostnames, and we are not able to easily ssh to those machines with the datacenter private IPs (without resorting to a reverse lookup). I am proposing this small change: https://reviews.apache.org/r/44532 In this approach, executors will have to be started with a parameter 'announcer-set-hostname-cmd'. For example, --announcer-set-hostname-cmd = 'cat /etc/mesos-slave/ip' > Add support for IP addresses instead of just hostnames in Announcer > --- > > Key: AURORA-1611 > URL: https://issues.apache.org/jira/browse/AURORA-1611 > Project: Aurora > Issue Type: Story >Reporter: Kunal Thakar > > The thermos announcer is passing hostnames in the serviceEndpoint object that > is sent to ZK. We want the announcer to send IPs instead or in addition to > the hostname that is passed along. What is the best way to achieve this? I am > thinking of adding a new attribute to the Endpoint struct > (https://github.com/apache/aurora/blob/master/commons/src/main/thrift/org/apache/aurora/common/thrift/endpoint.thrift). > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AURORA-1612) Publish RPMs and debs for 0.12.0
[ https://issues.apache.org/jira/browse/AURORA-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sirois updated AURORA-1612: Attachment: bintray-publish-after-upload-and-explode.png bintry-upload-artifacts.png Attaching some screen shots for safe keeping for docs. > Publish RPMs and debs for 0.12.0 > > > Key: AURORA-1612 > URL: https://issues.apache.org/jira/browse/AURORA-1612 > Project: Aurora > Issue Type: Task > Components: Build, Packaging >Reporter: John Sirois >Assignee: John Sirois > Attachments: bintray-publish-after-upload-and-explode.png, > bintry-upload-artifacts.png > > > 0.12.0 has now been released and so we should deliver official packages for > the release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AURORA-1612) Publish RPMs and debs for 0.12.0
[ https://issues.apache.org/jira/browse/AURORA-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185837#comment-15185837 ] John Sirois commented on AURORA-1612: - A fix for rpm deps and the rpm test environment: https://reviews.apache.org/r/44527/ > Publish RPMs and debs for 0.12.0 > > > Key: AURORA-1612 > URL: https://issues.apache.org/jira/browse/AURORA-1612 > Project: Aurora > Issue Type: Task > Components: Build, Packaging >Reporter: John Sirois >Assignee: John Sirois > > 0.12.0 has now been released and so we should deliver official packages for > the release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AURORA-1185) immutable thrift definition for ITaskConfig is missing some functions
[
https://issues.apache.org/jira/browse/AURORA-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Sirois updated AURORA-1185:
Assignee: (was: John Sirois)
> immutable thrift definition for ITaskConfig is missing some functions
> -
>
> Key: AURORA-1185
> URL: https://issues.apache.org/jira/browse/AURORA-1185
> Project: Aurora
> Issue Type: Bug
> Components: Scheduler
>Reporter: Jay Buffington
>Priority: Minor
>
> src/main/python/apache/aurora/tools/java/thrift_wrapper_codegen.py doesn't
> properly handle lines that look like this:
> 29: optional Container container = { "mesos": {} }
> It will ignore any entries after that line. This means that method calls
> like this will fail to compile
> config = ITaskConfig(...)
> config.getExecutorConfig();
> A work around is to move that line to the end of the struct's definition.
> This was discussed in IRC:
> http://wilderness.apache.org/channels/?f=aurora/2015-03-10#142601
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AURORA-1394) Consistent RPM and Debian packages
[ https://issues.apache.org/jira/browse/AURORA-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185363#comment-15185363 ] John Sirois commented on AURORA-1394: - Stopped progress and unassigned for now to make clear I'm not actually working on this at the moment. > Consistent RPM and Debian packages > -- > > Key: AURORA-1394 > URL: https://issues.apache.org/jira/browse/AURORA-1394 > Project: Aurora > Issue Type: Story >Reporter: Stephan Erb > > Aurora comes with the necessary artifacts to create DEB und RPM packages. > Unfortunately, the packaging is not really consistent. This is confusing for > users, but also a burden for Aurora maintainers. > Some examples: > * different handling of gradle (auto-download vs dependency which has to be > build manually) > * different packages names (e.g., aurora-client vs aurora-tools) > * different configuration mechanism and default config options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AURORA-1612) Publish RPMs and debs for 0.12.0
[ https://issues.apache.org/jira/browse/AURORA-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15185362#comment-15185362 ] John Sirois commented on AURORA-1612: - The deb (ubuntu + debian) vote is taking place here: http://aurora.markmail.org/thread/v6itvwfibdokwpqe > Publish RPMs and debs for 0.12.0 > > > Key: AURORA-1612 > URL: https://issues.apache.org/jira/browse/AURORA-1612 > Project: Aurora > Issue Type: Task > Components: Build, Packaging >Reporter: John Sirois >Assignee: John Sirois > > 0.12.0 has now been released and so we should deliver official packages for > the release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AURORA-1394) Consistent RPM and Debian packages
[ https://issues.apache.org/jira/browse/AURORA-1394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sirois updated AURORA-1394: Assignee: (was: John Sirois) > Consistent RPM and Debian packages > -- > > Key: AURORA-1394 > URL: https://issues.apache.org/jira/browse/AURORA-1394 > Project: Aurora > Issue Type: Story >Reporter: Stephan Erb > > Aurora comes with the necessary artifacts to create DEB und RPM packages. > Unfortunately, the packaging is not really consistent. This is confusing for > users, but also a burden for Aurora maintainers. > Some examples: > * different handling of gradle (auto-download vs dependency which has to be > build manually) > * different packages names (e.g., aurora-client vs aurora-tools) > * different configuration mechanism and default config options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AURORA-1613) Publish documentation for 0.12.0
[ https://issues.apache.org/jira/browse/AURORA-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sirois resolved AURORA-1613. - Resolution: Fixed Bill completed this task on 3/3/2016. > Publish documentation for 0.12.0 > > > Key: AURORA-1613 > URL: https://issues.apache.org/jira/browse/AURORA-1613 > Project: Aurora > Issue Type: Task > Components: Build, Documentation >Reporter: John Sirois >Assignee: Bill Farner > > 0.12.0 has been released so the docs should be re-published. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AURORA-1631) Consider removing --restart-threshold from "aurora job restart"
Maxim Khutornenko created AURORA-1631:
-
Summary: Consider removing --restart-threshold from "aurora job
restart"
Key: AURORA-1631
URL: https://issues.apache.org/jira/browse/AURORA-1631
Project: Aurora
Issue Type: Task
Components: Client
Reporter: Maxim Khutornenko
We have removed {{restart_threshold}} from the updater (AURORA-479,
AURORA-1252, AURORA-1254) but it's still a valid option of the "aurora job
restart". It's now causing similar end user issues (interrupted restarts due to
low default value of 60 seconds) and results in inconsistent user expectations.
Consider removing this option as it does not deliver much value and uses the
old and now defunct {{restart_threshold + watch_secs}} formula for watching
instance health.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
