[GeoNode-devel] GeoNode Devops

[Patrick Dufour]

Yeah, I've seen that.  Also, I've used the ROGUE Chef cookbooks at
https://github.com/ROGUE-JCTD/rogue-cookbook.

Definitely room for some harmonization.  Just to highlight some of the
(future) benefits, design decisions, in the new code.  Had to strip out
some of the code for the community version.  The CentOS production version
is much more sophisticated but not complete yet.  I'll try to enhance
community version over time.  Here are the advantages:

- Separating variables from playbook files
- Creation of "common roles" that can be used across multiple GeoNode and
other webGIS (GeoDjango) based projects
- Packer integration
- CentOS Development Machine, too (ETA next week).
- Custom filter plugins and fact modules (Ansible is super easy to extend.
More coming on this.)

Regards,
Patrick

On Thu, Apr 7, 2016 at 11:31 PM, Jeffrey Johnson <ortelius at gmail.com> wrote:

> Patrick, This looks interesting. Havent had time to dig in yet, but
> just an FYI, several of us have been using this repo for quite a while
> now https://github.com/GeoNode/ansible-geonode and its already
> published to ansible-galaxy
> https://galaxy.ansible.com/ortelius/geonode/. We should probably make
> an effort to harmonize things.
>
> On Thu, Apr 7, 2016 at 4:24 PM, Patrick Dufour <pjdufour.dev at gmail.com>
> wrote:
> > Good afternoon, everyone.
> >
> > Over the last couple weeks, on behalf of a client, I've been working on
> > building out their devops pipeline for a complex downstream GeoNode
> project.
> > This includes using Slack for comms and core devops tools, such as
> Ansible,
> > Packer, VirtualBox, Vagrant, and Fabric.
> >
> > Their server infrastructure includes running multiple GeoNodes on a
> single
> > CentOS virtual machine, so Ansible has filled a critical gap in managing
> the
> > "state" of their complex machines.  I'm not fully there yet, but have had
> > some successes so far that are worth mentioning
> >
> > First, Ansible has proven remarkably useful in debugging and team
> > cooperation.  Since multiple developers have IDENTICAL virtual machines
> you
> > get the same errors.  Therefore, you can much more quickly (than without
> > Ansible) identify the issues in code without having to run through system
> > checklists.  This save a lot of time!!
> >
> > Second, as part of this effort, I've spun out a community version of the
> > devops tools at:
> >
> > https://github.com/pjdufour/geonode-devops
> >
> > The "geonode-devops" code is still relatively new.  I've completed the
> > Ansible/Vagrant part of the package (the rest still needs testing).
> After
> > installing the core packages on your host/control machine, you can
> deploy a
> > GeoNode development server as easy as
> >
> > vagrant up
> >
> > Hopefully this toolkit will help with day-to-day collaboration.  These
> tools
> > may also help with the on-boarding of new developers to the ever growing
> > GeoNode community!
> >
> > Regards,
> > Patrick
> >
> > _______________________________________________
> > geonode-devel mailing list
> > geonode-devel at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/geonode-devel
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20160407/a699060d/attachment.html>