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

Posted to infrastructure-issues@apache.org by "Chris Lambertus (JIRA)" <ji...@apache.org> on 2016/04/22 21:38:13 UTC

[jira] [Resolved] (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:all-tabpanel ]

Chris Lambertus resolved INFRA-11725.
-------------------------------------
    Resolution: Fixed
      Assignee: Chris Lambertus  (was: Gavin)

I was in leaseweb working on a different machine so I created this one at the same time. Yaml added for whimsy-vm3 and whimsy3 service name added. You should be good to go as soon as the DNS propagates.

> 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: Chris Lambertus
>            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)