infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Chambers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-13255) Migrate bloodhound-vm away from Erebus
Date Mon, 12 Feb 2018 00:28:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-13255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360187#comment-16360187
] 

John Chambers commented on INFRA-13255:
---------------------------------------

Thanks [~cml] and [~gstein]. I understand the concern and am happy to go with live.bloodhound.a.o
so can this be setup please. Also what is the process for getting an SSL certificate for that
url?
Once we have the redirect from live.bloodhound.a.o and the SSL certificate configured then
I think this ticket can be closed. I can make the changes to the project website and announce
on the dev and user lists that the projects issue tracker is back online.

> Migrate bloodhound-vm away from Erebus
> --------------------------------------
>
>                 Key: INFRA-13255
>                 URL: https://issues.apache.org/jira/browse/INFRA-13255
>             Project: Infrastructure
>          Issue Type: Planned Work
>          Components: VMWare
>            Reporter: Gary Martin
>            Assignee: Chris Lambertus
>            Priority: Minor
>             Fix For: Sep 2017
>
>
> bloodhound-vm needs to be moved to another host , LW,PNAP, etc.
> Note that bloodhound-vm is an important service with uptime to take note of.
> It also has a direct mount to svn (check /etc/fstab) that must be maintained.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message