<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Jesse Pretorius <<a href="mailto:jesse.pretorius@gmail.com">jesse.pretorius@gmail.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, March 22, 2016 at 7:40 AM<br>
<span style="font-weight:bold">To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [tc][fuel][kolla][osa][tripleo] proposing type:deployment<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On 22 March 2016 at 09:15, Thierry Carrez <span dir="ltr">
<<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
For OSA, we don't produce the deployment tool, only a set of playbooks. I was thinking we might need a type:packaging tag to describe which things we produce are just about packaging OpenStack things for usage by outside deployment systems (Ansible, Puppet,
Chef, Deb, RPM...). So I'm not sure your type:deployment tag would apply to OSA.<span class="HOEnZb"><font color="#888888"><br>
</font></span></blockquote>
</div>
<div><br>
</div>
Yeah, I suppose it depends on how you define 'deployment tool'. OSA is an umbrella project providing Ansible roles which deploy services, and playbooks that put them together in an integrated deployment.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Fuel similarly has libraries, Puppet roles, plugins, etc which are all packaged together to provide what we call 'Fuel'.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">I expect that there are other similarities - for instance 'Keystone' may be a service, but that service has libraries and all combined together we call it a daemon service.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">I guess it would be nice to have some sort of designation to allow easier filtering for consumers, assuming that this actually does add value to Operators/Packagers who consume these projects.</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>Jessie,</div>
<div><br>
</div>
<div>The only requirement is:</div>
<ul>
<li>
<div>The repository contains software that deploys at minimum</div>
<div> deliverables tagged with starter-kit:compute in the</div>
<div> projects.yaml file.</div>
</li></ul>
<div>I guess we could add more if needed, but I'm a big fan of less is more, so I'd be open to adding requirements if the above is unclear that the tool (puppet/chef/osa/kolla/fuel/triploe0) needs to deploy OpenStack and it needs to be functional afterwards.</div>
<div><br>
</div>
<div>I think the "functional afterwards" is unstated and probably needs an update to the patch to differentiate between packaging efforts and deployment efforts.</div>
<div><br>
</div>
<div>I also think the project should deploy the dependencies required to operate start-kit:compute which include a database of their choosing and a message queue service supported by oslo.</div>
<div><br>
</div>
<div>Note compute-kit is not onerous – there are only a few projects which have the starter-kit:compute tag. They include keystone, glance, neutron, and nova. Clearly that could change in the future, but at present, it wouldn't be a burden on any deployment
project to just simply apply the tag and move on.</div>
<div><br>
</div>
<div>Thanks for jogging my thought processes – I'll update the review this morning.</div>
<div><br>
</div>
<div>Regards</div>
<div>-steve</div>
<div><br>
</div>
</body>
</html>