<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1" style="word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font-family:Calibri,sans-serif">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Good thing to discuss.<br>
<br>
So, if you can launch a Solum Language Pack without the user needing to do extra steps like creating a git repo and populating it, committing, etc, then yeah, I think that fits the app tag definition we came up with. Something a user could go into the catalog,
hit launch, optionally fill out form, and get something running easily. The nice thing about the app tag is that we can selectively put it on things that it makes sense to, rather then just relying on the type of artefact it is. Like this use case.<br>
<br>
Thanks,<br>
Kevin<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF132482"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Keith Bray [keith.bray@RACKSPACE.COM]<br>
<b>Sent:</b> Thursday, June 18, 2015 12:44 PM<br>
<b>To:</b> openstack-dev@lists.openstack.org<br>
<b>Subject:</b> [openstack-dev] [app-catalog] [solum] Base Image tagging vs. App tagging<br>
</font><br>
</div>
<div></div>
<div>
<div>Hi folks,</div>
<div><br>
</div>
<div>I had to leave the app-catalog IRC meeting early today, but I read back through the logs. I wanted to bring up a point about Apps vs. Components, and determination of what is an app and tagging. I don't think it's any more black and white with Solum
language packs than it is with Glance images. </div>
<div><br>
</div>
<div>As an example, a solum user can create a language pack called Ubuntu, LAMP, Wordpress, DockerRegistry, or anything else.. In fact, any Docker image in the public Docker Registry could become a Solum language pack . A language pack can be a base run-time
where the user then layers app code on-top, or it can be a run-time with application code already installed that the user just layers on changes to the app code. Applications and application components can be pre-installed on solum language packs. Solum
layers on the controlled workflow to integrate a user's CI/CD options of choice, where Solum's controlled workflow instills the CI/CD gates (e.g. Tests must pass before we push your app live to production) and ensures proper Heat template selection to match
appropriate reference architecture for the type of app being deployed. Think of Solum as integrating Heat, Auto-scale, Git, Mistral, and up-leveing application deploying to the cloud such that an end-user just needs to specify a language pack, a git repo,
and optionally a test command and application run command. If a base language pack has everything needed to get started, it can be used standalone with an empty git repo or Solum could setup a git repo automatically with the base app code (e.g. Wordpress). </div>
<div><br>
</div>
<div>So, I want to challenge the notion that it's a clear line for solum language packs to not be tagged apps and that glance images are the only artifacts in the gray area.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>-Keith</div>
</div>
</div>
</div>
</body>
</html>