<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi<br>
I will be interested as well. Having these playbooks in ansible can
also be useful<br>
in order to integrate with infra-ansible project.<br>
I really see that collection as a valid alternative for puppet
modules, with the advantages<br>
that ansible can provide, but of course that moving from puppet to
ansible on infra internally<br>
is something that cannot be done easily, and needs a wider
discussion.<br>
If we limit the scope of the ansible playbooks only to infra
components, I think that infra<br>
namespace is the way to go, having an independent group of
reviewers.<br>
<br>
Best<br>
Yolanda<br>
<br>
<br>
<div class="moz-cite-prefix">El 09/09/15 a las 21:31, Ricardo
Carrillo Cruz escribió:<br>
</div>
<blockquote
cite="mid:CADe0dKC6YkSx_yjp4-gg+GqAoYvdjbLpzAXJi9NqYZMx4trm2g@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div dir="ltr">I'm interested in ansible roles for
openstack-infra, but as there is overlap in functionality
<div>with the current openstack-infra puppet roles I'm not sure
what's the stance from the</div>
<div>openstack-infra core members and PTL.</div>
<div><br>
</div>
<div>I think they should go to openstack-infra, since
Nodepoo/Zuul/etc are very specific</div>
<div>to the OpenStack CI.</div>
<div><br>
</div>
<div>Question is if we should have a subgroup within
openstack-infra namespace for</div>
<div>'stuff that is not used by OpenStack CI but interesting
from CI perspective and/or</div>
<div>used by other downstream groups'.</div>
<div><br>
</div>
<div>Regards</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2015-09-09 19:22 GMT+02:00 Paul
Belanger <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:pabelanger@redhat.com" target="_blank">pabelanger@redhat.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb">
<div class="h5">On Tue, Sep 08, 2015 at 06:50:38PM -0400,
Emilien Macchi wrote:<br>
><br>
><br>
> On 09/08/2015 10:57 AM, Paul Belanger wrote:<br>
> > Greetings,<br>
> ><br>
> > I wanted to start a discussion about the
future of ansible / ansible roles in<br>
> > OpenStack. Over the last week or so I've
started down the ansible path, starting<br>
> > my first ansible role; I've started with
ansible-role-nodepool[1].<br>
> ><br>
> > My initial question is simple, now that big
tent is upon us, I would like<br>
> > some way to include ansible roles into the
opentack git workflow. I first<br>
> > thought the role might live under
openstack-infra however I am not sure that<br>
> > is the right place. My reason is, -infra
tents to include modules they<br>
> > currently run under the -infra namespace, and
I don't want to start the effort<br>
> > to convince people to migrate.<br>
><br>
> I'm wondering what would be the goal of
ansible-role-nodepool and what<br>
> it would orchestrate exactly. I did not find README
that explains it,<br>
> and digging into the code makes me think you try to
prepare nodepool<br>
> images but I don't exactly see why.<br>
><br>
> Since we already have puppet-nodepool, I'm curious
about the purpose of<br>
> this role.<br>
> IMHO, if we had to add such a new repo, it would be
under<br>
> openstack-infra namespace, to be consistent with
other repos<br>
> (puppet-nodepool, etc).<br>
><br>
> > Another thought might be to reach out to the
os-ansible-deployment team and ask<br>
> > how they see roles in OpenStack moving foward
(mostly the reason for this<br>
> > email).<br>
><br>
> os-ansible-deployment aims to setup OpenStack
services in containers<br>
> (LXC). I don't see relation between
os-ansible-deployment (openstack<br>
> deployment related) and ansible-role-nodepool
(infra related).<br>
><br>
> > Either way, I would be interested in feedback
on moving forward on this. Using<br>
> > travis-ci and github works but OpenStack
workflow is much better.<br>
> ><br>
> > [1] <a moz-do-not-send="true"
href="https://github.com/pabelanger/ansible-role-nodepool"
rel="noreferrer" target="_blank">https://github.com/pabelanger/ansible-role-nodepool</a><br>
> ><br>
><br>
> To me, it's unclear how and why we are going to use
ansible-role-nodepool.<br>
> Could you explain with use-case?<br>
><br>
</div>
</div>
The most basic use case is managing nodepool using ansible,
for the purpose of<br>
CI. Bascially, rewrite puppet-nodepool using ansible. I
won't go into the<br>
reasoning for that, except to say people do not want to use
puppet.<br>
<br>
Regarding os-ansible-deployment, they are only related due
to both using<br>
ansible. I wouldn't see os-ansible-deployment using the
module, however I would<br>
hope to learn best practices and code reviews from the team.<br>
<br>
Where ever the module lives, I would hope people interested
in ansible<br>
development would be group somehow.<br>
<br>
> Thanks,<br>
<span class="HOEnZb"><font color="#888888">> --<br>
> Emilien Macchi<br>
</font></span>
<div class="HOEnZb">
<div class="h5">><br>
>
__________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage
questions)<br>
> Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage
questions)<br>
Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Yolanda Robla Mota
Cloud Automation and Distribution Engineer
+34 605641639
<a class="moz-txt-link-abbreviated" href="mailto:yolanda.robla-mota@hp.com">yolanda.robla-mota@hp.com</a></pre>
</body>
</html>