www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Corey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-10669) locked down Ubuntu 14.04 vm for infrastructure managed whimsy tools
Date Thu, 05 Nov 2015 21:27:27 GMT

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

Geoffrey Corey commented on INFRA-10669:

What I meant with hipchat, was ping me through hipchat if you had any issues getting puppet-kitchen
working or ran into any errors with it. It's much fast to debug through there than email.

As for bundler, puppet isn't really setup to handle that. It has a gem package provider and
we would like to use as much built-in stuff as possible (this provider will also pull in the
deps for that gem, as well as have the ability to specify the version number of the gem you
are declaring an install for). Using an exec to install gems using bundle is not good for
manageability. There are some bundle/r related modules out there that you are free to explore

As for the vagrant file, I've looked at it and it seems to rely on a local checkout of many
files and mounting them in vagrant. This might work for developing the app, but for a production
type setting, we more so want the directory structure created and understood, and then checking
out the files from svn can be completed later (and a discussion on how best to go about that
can happen then as well).

I've seen the apache2 configs, and they will have to be adapted to the way the apache puppet
module handles stuff (i.e. a definition for an http vhost and a definition for an ssl vhost).
The modules part is fairly straight forward. If the module has a class, then it's a simple
one line inclusion in the host's manifest. If the module is a define rather than a class,
we have a way to include it as well but it requires about 2 lines.

> locked down Ubuntu 14.04 vm for infrastructure managed whimsy tools
> -------------------------------------------------------------------
>                 Key: INFRA-10669
>                 URL: https://issues.apache.org/jira/browse/INFRA-10669
>             Project: Infrastructure
>          Issue Type: Bug
>            Reporter: Sam Ruby
>            Assignee: Geoffrey Corey
> Current VM for Whimsy is running 12.04; which should be retired over time.  Please set
up a new VM for whimsy accessible via the web under a new name during the transition.  Once
set up and verified, the existing VM can be taken down

This message was sent by Atlassian JIRA

View raw message