You are viewing a plain text version of this content. The canonical link for it is here.

Posted to infrastructure-issues@apache.org by "Sam Ruby (JIRA)" <ji...@apache.org> on 2016/04/22 02:09:12 UTC

[jira] [Commented] (INFRA-11725) Ubuntu 14.04 vm for whimsy (in addition to whimsy-vm2)

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

Sam Ruby commented on INFRA-11725:
----------------------------------

perhaps it would be best to move away from whimsy-old and whimsy-test and to instead use whimsy2.apache.org and whimsy3.apache.org, with whimsy.apache.org being an alias for whimsy2.apache.org for now.  Until the original whimsy-vm is decomissioned, perhaps it should be accessed as whimsy-vm1.

> Ubuntu 14.04 vm for whimsy (in addition to whimsy-vm2)
> ------------------------------------------------------
>
>                 Key: INFRA-11725
>                 URL: https://issues.apache.org/jira/browse/INFRA-11725
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: ColoTasks, DNS, Hardware, Whimsy
>            Reporter: Sam Ruby
>            Assignee: Gavin
>            Priority: Minor
>
> Same specs (CPUs and memory) as whimsy-vm2, different colo (leaseweb?).
> The thoughts are that the combination of backups and svn occasionally saturate phoenixnap, affecting whimsy services.
> whimsy-test.apache.org should direct to vm3, and whimsy.apache.org should continue to go to vm2. Once infrastructure-puppet/data/nodes/whimsy-vm3.apache.org.yaml is available and I have sudo access to the machine, I will set the machine up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)