On 11/16/2015 07:47 AM, Jesse Pretorius wrote:
> Based on the spec's proposed change section [1] I would say that items 4 & 5
> are the next steps. Those steps, however, are kind-of waiting for the gate
> split work. Perhaps the best way to get this done that doesn't have the
> dependency is to
On 9 November 2015 at 19:38, Major Hayden wrote:
>
> What would you propose as the final steps to get the blueprint marked as
> completed? Should documentation be added into openstack-ansible about
> integrating openstack-ansible-security or should a script be provided for
> quicker integration?
On 11/06/2015 05:38 PM, Jesse Pretorius wrote:
> While I applaud the idea, changing the current commit integration test is
> probably not the best approach. We're in the middle of splitting the roles
> out into their own repositories and also extending the gate checks into
> multiple use-cases.
Hey Major,
This sounds like a great next step. It might also be cool to set up
Vagrant to pull Ubuntu 14.04, grab Ansible, and run the scripts on it.
I'll carve out a few hours early next week and have a crack at it.
-Travis
On 11/6/15, 10:59 PM, Major Hayden wrote:
>Hello there,
>
>At this
On Friday, 6 November 2015, Major Hayden wrote:
>
> At this moment, openstack-ansible-security[1] is feature complete and all
> of the Ansible tasks and documentation for the STIGs are merged. Exciting!
Excellent work, thank you!
> I've done lots of work to ensure that the role uses sane defa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello there,
At this moment, openstack-ansible-security[1] is feature complete and all of
the Ansible tasks and documentation for the STIGs are merged. Exciting!
I've done lots of work to ensure that the role uses sane defaults so that it
can be