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 Thu, 14 Dec 2017 09:31:00 GMT

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

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

Hi [~cml] / [~gstein], Would it be possible to re-open this ticket so that I can continue
the work [~gjm] started to get the Bloodhound live instance at least back up and running.
I am in the process of looking at how to run the salt scripts we have in the project against
the puppet provisioned vm. So if you have any experience of doing that or any external resources
that might help, I would be grateful.



> 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
>             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
(v6.4.14#64029)

Mime
View raw message