<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=euc-kr">
</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>
<div>Does OSP support running each service in an LXC container as well? What about nova-cells? How does it handle people who need to carry local changes? What is the upgrade path like with OSP?</div>
<div><br>
</div>
<div>Asking, because in Philly the general consensus, I fel,t was people want to move away from the current system level package stuff and move towards: venv's, "lightweight packages", containers. The only reason that was brought up to keep packages around
was to solve the non-python lib stuff and using a depsolver (yum/apt) that doesn't suck (pip). So I am pretty sure my wants are inline with what other people in the community are either already doing or moving towards.</div>
<div>___________________________________________</div>
<div>
<div> </div>
<div>Kris Lindgren</div>
<div>Senior Linux Systems Engineer</div>
<div>GoDaddy, LLC.</div>
<div><br>
</div>
<div><br>
</div>
</div>
</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>John Dewey <<a href="mailto:john@dewey.ws">john@dewey.ws</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, July 8, 2015 at 11:43 PM<br>
<span style="font-weight:bold">To: </span>"Kris G. Lindgren" <<a href="mailto:klindgren@godaddy.com">klindgren@godaddy.com</a>><br>
<span style="font-weight:bold">Cc: </span>Adam Young <<a href="mailto:ayoung@redhat.com">ayoung@redhat.com</a>>, "<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>" <<a href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [Openstack-operators] OSAD for RHEL<br>
</div>
<div><br>
</div>
<div>
<div>
<div>This would not be acceptable for those running OSP. </div>
<div><br>
</div>
<div></div>
<p style="color: #A0A0A8;">On Wednesday, July 8, 2015 at 10:12 PM, Kris G. Lindgren wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span>
<div>
<div>
<div>I should be more clear. My current thought is to have a venv packaged</div>
<div>inside an rpm - so the rpm includes the needed init scripts, ensures the</div>
<div>required system level binaries are installed, adds the users - ect ect.</div>
<div>But would be a single deployable autonomous unit. Also, have a versioning</div>
<div>schema to roll forward and back between venvs for quick update/rollback.</div>
<div>We are already working on doing something similar to this to run kilo on</div>
<div>cent6 boxen, until we can finish revving the remaining parts of the fleet</div>
<div>to cent7.</div>
<div><br>
</div>
<div>My desire is to move away from using system level python & openstack</div>
<div>packages, so that I can possibly run mismatched versions if I need to. We</div>
<div>had a need to run kilo ceilometer and juno neutron/nova on a single</div>
<div>server. The conflicting python requirements between those made that task</div>
<div>impossible. In general I want to get away from treating Openstack as a</div>
<div>single system that everything needs to be upgraded in lock step (packages</div>
<div>force you into this). I want to move to being able to upgrade say</div>
<div>oslo.messaging to a newer version on just say nova on my control plane</div>
<div>servers. Or upgrade nova to kilo while keeping the rest of the system</div>
<div>(neutron) on juno. Unless I run each service in a vm/container or on a</div>
<div>physical piece of hardware that is pretty much impossible to do with</div>
<div>packages - outside of placing everything inside venv's.</div>
<div><br>
</div>
<div>However, it is my understanding that OSAD already builds its own</div>
<div>python-wheels and runs those inside lxc containers. So I don©öt really</div>
<div>follow what good throwing those into an rpm would really do?</div>
<div>____________________________________________</div>
<div></div>
<div>Kris Lindgren</div>
<div>Senior Linux Systems Engineer</div>
<div>GoDaddy, LLC.</div>
<div><br>
</div>
<div><br>
</div>
<div>On 7/8/15, 10:33 PM, "Adam Young" <<a href="mailto:ayoung@redhat.com">ayoung@redhat.com</a>> wrote:</div>
<div><br>
</div>
<blockquote type="cite">
<div>
<div>On 07/07/2015 05:55 PM, Kris G. Lindgren wrote:</div>
<blockquote type="cite">
<div>
<div>+1 on RHEL support. I have some interest in moving away from packages</div>
<div>and</div>
<div>am interested in the OSAD tooling as well.</div>
</div>
</blockquote>
<div><br>
</div>
<div>I would not recommend an approach targetting RHEL that does not use</div>
<div>packages.</div>
<div><br>
</div>
<div>OSAD support for RHEL using packages would be an outstanding tool.</div>
<div><br>
</div>
<div>Which way are you planning on taking it?</div>
<div><br>
</div>
<blockquote type="cite">
<div>
<div>____________________________________________</div>
<div></div>
<div>Kris Lindgren</div>
<div>Senior Linux Systems Engineer</div>
<div>GoDaddy, LLC.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>On 7/7/15, 3:38 PM, "Abel Lopez" <<a href="mailto:alopgeek@gmail.com">alopgeek@gmail.com</a>> wrote:</div>
<div><br>
</div>
<blockquote type="cite">
<div>
<div>Hey everyone,</div>
<div>I've started looking at osad, and I like much of the direction it</div>
<div>takes.</div>
<div>I'm pretty interested in developing it to run on RHEL, I just wanted to</div>
<div>check if anyone would be -2 opposed to that before I spend cycles on</div>
<div>it.</div>
</div>
</blockquote>
<div><br>
</div>
<div>_______________________________________________</div>
<div>OpenStack-operators mailing list</div>
<div><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a></div>
<div><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></div>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>_______________________________________________</div>
<div>OpenStack-operators mailing list</div>
<div><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a></div>
<div><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></div>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>_______________________________________________</div>
<div>OpenStack-operators mailing list</div>
<div><a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a></div>
<div><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></div>
</div>
</div>
</span></blockquote>
<div><br>
</div>
</div>
</div>
</span>
</body>
</html>