<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 07/10/2015 02:25 PM, Kevin Carter
wrote:<br>
</div>
<blockquote cite="mid:1436552750102.45275@RACKSPACE.COM" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
<p>To be clear the present OSAD project really has no intention to
bring package based installations of OpenStack. We'd certainly
not reject the idea and wouldn't mind having an implementation
spec for it but all of our current tooling and design principles
have been based on the fact that we've move away from distro
packages and on to upstream source as it pertains to OpenStack.
The system as it stands today creates an internal repository of
built wheels for your environment and all of the OpenStack
services are installed within LXC containers, where possible and
it makes sense. The installation of these bits comes from the
internal wheel repository and uses pip and all of the pre / post
config happens within the Ansible playbooks.<br>
</p>
</blockquote>
<br>
I understand your frustration with the packaging approach. For a
first approximation, getting the code for OpenStack/Python
operations out of Pip makes sense. Ideally, we would be able to
support both approaches. Red Hat would not support a pip based
install, but I am sure some Centos base users would be happy with
pip.<br>
<br>
We had the same general discussion around devstack. <br>
<br>
<blockquote cite="mid:1436552750102.45275@RACKSPACE.COM" type="cite">
<p>
</p>
<p><br>
</p>
<p>One issue that will become a problem, for users of RedHat
specifically, is the fact that RedHat has no LXC container
templates (at least none that are publicly available) and even
if someone were to make an official RedHat container template
there'd be issues with the containers being able
to connect to the satellite servers as well as other potential
license problems. <br>
</p>
</blockquote>
<br>
I'd leave the issues with getting blessed RHEL LXC support to Red
Hat. Making something that works for CentOS with publically
available LXC containers there would be more what I expect from OSAD
upstream.<br>
<br>
What about Fedora support? It seems to me that we would be far more
likely to have something supportable with Fedora that could then be
backported to CentOS?<br>
<br>
<blockquote cite="mid:1436552750102.45275@RACKSPACE.COM" type="cite">
<p><br>
</p>
<p>I've done some experimenting with a RedHat 7.1 hosts and CentOS
7 containers and things seem to work OK but I'd not say that I
have really put a lot of effort into it. That said, if its
something that you'd all like to work on I'd be happy to help
out to make it all go. <br>
</p>
</blockquote>
<br>
Sounds good. I'll give it a try after the Keystone Midcycle.<br>
<br>
<blockquote cite="mid:1436552750102.45275@RACKSPACE.COM" type="cite">
<p>
</p>
<p><br>
</p>
<div id="Signature">
<div style="font-family:Tahoma; font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px">
<div style="font-size:13px"><font face="Courier New"
size="2"><span style="font-size:10pt">--<br>
<br>
Kevin Carter</span></font></div>
</div>
</div>
</div>
</div>
</div>
<div style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
color="#000000" face="Calibri, sans-serif"><b>From:</b> Adam
Young <a class="moz-txt-link-rfc2396E" href="mailto:ayoung@redhat.com"><ayoung@redhat.com></a><br>
<b>Sent:</b> Thursday, July 9, 2015 11:32 AM<br>
<b>To:</b> Kris G. Lindgren; John Dewey<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a><br>
<b>Subject:</b> Re: [Openstack-operators] OSAD for RHEL</font>
<div> </div>
</div>
<div>
<div class="moz-cite-prefix">On 07/09/2015 02:16 AM, Kris G.
Lindgren wrote:<br>
</div>
<blockquote type="cite">
<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>
</blockquote>
<br>
So, ignoring the Hypervisor for the moment, there is no reason
that the rest of the controllers can't run in separate
Containers. I think a container based deployment would be
fantastic.<br>
<br>
venv is not really sufficient, as the system level binaries
can still conflict (MysQL and LDAP both require system
libraries for Keystone, for example)<br>
<br>
From an Ansible perspective; we need to be able to share the
HTTPD instance for Keystone and Apache, and getting that right
will solve most of the issues deploying in a secure manner.
Putting Them on separate hosts or containers should be a
degenerate case, and thus be supported, too.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<blockquote type="cite">
<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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:klindgren@godaddy.com">klindgren@godaddy.com</a>><br>
<span style="font-weight:bold">Cc: </span>Adam Young
<<a moz-do-not-send="true"
href="mailto:ayoung@redhat.com">ayoung@redhat.com</a>>,
"<a moz-do-not-send="true"
href="mailto:openstack-operators@lists.openstack.org">openstack-operators@lists.openstack.org</a>"
<<a moz-do-not-send="true"
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>
<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>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
moz-do-not-send="true"
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>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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a></div>
<div><a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a></div>
<div><a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a></div>
<div><a moz-do-not-send="true"
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></blockquote>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>