infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Boudnik (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-13733) Add CNAME for an external Bigtop's S3 bucket
Date Thu, 23 Mar 2017 06:10:41 GMT

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

Konstantin Boudnik updated INFRA-13733:
---------------------------------------
    Description: 
At Bigtop project we have a quite large amount of convenience artifacts (Linux packages for
>6 platforms) we publish with every release. The packages are stores on AWS S3. We'd like
to avoid keeping track of changing bucket names (which happened in the past when a commercial
vendor pulled their support from under our feet) and have constant name we can use in the
future.

For the consistency of the deployment recipes we'd like to have a CNAME for the S3 bucket
to be in the form of repos.bigtop.apache.org pointing to bigtop-repos.s3.amazonaws.com


  was:
At Bigtop project we have a number of hosts sitting on AWS and running some intensive CI for
the project: building packages, spinning up the clusters, and testing them. For the consistency
of the deployment recipes we'd like to have a CNAME for the CI master to be in the form of
bigtop-ci.apache.org or, better most preferably, ci.bigtop.apache.org



> Add CNAME for an external Bigtop's S3 bucket
> --------------------------------------------
>
>                 Key: INFRA-13733
>                 URL: https://issues.apache.org/jira/browse/INFRA-13733
>             Project: Infrastructure
>          Issue Type: Task
>          Components: DNS
>            Reporter: Konstantin Boudnik
>            Assignee: Geoffrey Corey
>
> At Bigtop project we have a quite large amount of convenience artifacts (Linux packages
for >6 platforms) we publish with every release. The packages are stores on AWS S3. We'd
like to avoid keeping track of changing bucket names (which happened in the past when a commercial
vendor pulled their support from under our feet) and have constant name we can use in the
future.
> For the consistency of the deployment recipes we'd like to have a CNAME for the S3 bucket
to be in the form of repos.bigtop.apache.org pointing to bigtop-repos.s3.amazonaws.com



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message