infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-13262) Migrate allura-vm away from Erebus
Date Thu, 06 Jul 2017 14:42:00 GMT

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

Chris Lambertus updated INFRA-13262:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

I reinstalled the VM as 16.04. The host keys will have changed, the new one:
ECDSA key fingerprint is SHA256:lwFx8K4vBr4pDVq6U/9kuzMS6slvzmUmbIn1Tk/gDes.

The basic system definition file in puppet is here:
https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/allura-vm2.apache.org.yaml

Here is an example of one another project set up:
https://github.com/apache/infrastructure-puppet/blob/deployment/data/nodes/ofbiz-vm2.apache.org.yaml

Let me know how I can assist with facilitating the migration. We'd like to have this completed
by 1 August.


> Migrate allura-vm away from Erebus
> ----------------------------------
>
>                 Key: INFRA-13262
>                 URL: https://issues.apache.org/jira/browse/INFRA-13262
>             Project: Infrastructure
>          Issue Type: Planned Work
>          Components: VMWare
>            Reporter: Dave Brondsema
>            Assignee: Chris Lambertus
>
> Note this is a service with uptime requirements.
> (see: https://allura-vm.apache.org/p/allura/wiki/Home/)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message