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] [Comment Edited] (INFRA-10669) locked down Ubuntu 14.04 vm for infrastructure managed whimsy tools
Date Thu, 05 Nov 2015 20:06:27 GMT

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

Geoffrey Corey edited comment on INFRA-10669 at 11/5/15 8:06 PM:
-----------------------------------------------------------------

whimsy-test is down because httpd has not been installed on whimsy-vm2 yet, so that is expected.

Here is what I use for local development/testing: https://github.com/stumped2/puppet-kitchen

The only real difference between it and production is that ldap login is not configured/enabled,
and sudoers is not configured (vagrant user is created, has passwordless sudo, etc), and there
is no access to encrypted things like certs, keys, and passwords.

As for the puppet itself, I use this extensively when writing puppet code: https://docs.puppetlabs.com/references/3.stable/type.html

I am all for this being done in a manageable way and if getting pull requests up means that
>1 person has some understanding of what is going on then +1 :)

Once svnpubsub is setup, it will pull in the apache puppet module by default. The apache module
does not allow edits to /etc/apache2/apache2.conf (the edits it does allow are *very* minor).
You can see examples of vhost definitions in data/nodes/ of the infrastructure-puppet repo.

If you want any help working on setting up the puppet-kitchen repo (or run into errors) I
am happy to help in in hipchat (I've tried to run through the README to make sure it's up
to date, but I could very well be missing steps).

(sorry if this response turned into rambling)

EDIT: forgot to mention, it might be best to make a whimsy_pvm_asf module to track all the
stuff for setting up whimsy. That way it tracks packages needed, config files, users, groups,
etc.

EDIT2: going back through some previous notes, I have the following package dependencies worked
out for the whimsy gem:

debs:
 - libxml2
 - zlib1g-dev
 - libldap2-dev
 - libsasl2-dev

gems:
 - whimsy-asf
 - wunderbar
 - sinatra (unsure of version?)
 - mail
 - ruby2js
 - ruby-ldap2
 - escape


was (Author: coreyg):
whimsy-test is down because httpd has not been installed on whimsy-vm2 yet, so that is expected.

Here is what I use for local development/testing: https://github.com/stumped2/puppet-kitchen

The only real difference between it and production is that ldap login is not configured/enabled,
and sudoers is not configured (vagrant user is created, has passwordless sudo, etc), and there
is no access to encrypted things like certs, keys, and passwords.

As for the puppet itself, I use this extensively when writing puppet code: https://docs.puppetlabs.com/references/3.stable/type.html

I am all for this being done in a manageable way and if getting pull requests up means that
>1 person has some understanding of what is going on then +1 :)

Once svnpubsub is setup, it will pull in the apache puppet module by default. The apache module
does not allow edits to /etc/apache2/apache2.conf (the edits it does allow are *very* minor).
You can see examples of vhost definitions in data/nodes/ of the infrastructure-puppet repo.

If you want any help working on setting up the puppet-kitchen repo (or run into errors) I
am happy to help in in hipchat (I've tried to run through the README to make sure it's up
to date, but I could very well be missing steps).

(sorry if this response turned into rambling)

EDIT: forgot to mention, it might be best to make a whimsy_pvm_asf module to track all the
stuff for setting up whimsy. That way it tracks packages needed, config files, users, groups,
etc.

> 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
(v6.3.4#6332)

Mime
View raw message