<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">It is hard for kolla to support both release of Ubuntu.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">Because docker separate the image build from deploy. We have no idea about the Ubuntu version in Dockerfile</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">except runing command to test it. We build the image by using Dockerfile. If we want support multi release of </div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">Ubuntu, the Dockerfile will looks like:</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">RUN if [[ $(cat /etc/os-release | awk '/VERSION_ID/{print $2}') == '14.04' ]] then; \</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"> apt-get install openjdk-7-jre \</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"> elif $(cat /etc/os-release | awk '/VERSION_ID/{print $2}') == '16.04' ]] then; \</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"> apt-get install openjdk-8-jre</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"> fi</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">This is still possible. Think about how to use COPY in the Dockerfile to support multi Ubuntu release? like</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">COPY sources.list /etc/apt/sources.list</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">As far as I can find out is:</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">COPY sources.list /etc/apt/sources.list</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><div class="gmail_default">RUN if [[ $(cat /etc/os-release | awk '/VERSION_ID/{print $2}') == '14.04' ]] then; \</div><div class="gmail_default"> sed -i 's/UBUNTU_RELEASE/trusty/' /etc/apt/sources.list \</div><div class="gmail_default"> elif $(cat /etc/os-release | awk '/VERSION_ID/{print $2}') == '16.04' ]] then; \</div><div class="gmail_default"> sed -i 's/UBUNTU_RELEASE/xenial/' /etc/apt/sources.list \</div><div class="gmail_default"> fi</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 7, 2016 at 12:51 AM, Jesse Pretorius <span dir="ltr"><<a href="mailto:jesse.pretorius@gmail.com" target="_blank">jesse.pretorius@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On 6 May 2016 at 16:27, Jeffrey Zhang <span dir="ltr"><<a href="mailto:zhang.lei.fly@gmail.com" target="_blank">zhang.lei.fly@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><span><br><div class="gmail_quote">On Fri, May 6, 2016 at 9:09 PM, Jesse Pretorius <span dir="ltr"><<a href="mailto:jesse.pretorius@gmail.com" target="_blank">jesse.pretorius@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">FWIW OpenStack-Ansible is choosing to support deployment on both Ubuntu 14.04 LTS and Ubuntu 16.04 LTS for both the Newton and Ocata cycles, with the current proposal to drop it in P. The intent is to provide our deployers the opportunity to transition with a mixed deployment.</blockquote></div><br></span><div style="font-family:monospace,monospace;font-size:small">Are you meaning the host/baremetal OS? the openstack-ansible deploy the OpenStack in LXC.</div><div style="font-family:monospace,monospace;font-size:small">So it really do not care about the host machine's OS. Kolla is not care about it, too.</div><div style="font-family:monospace,monospace;font-size:small">I think the openstack-ansible a specify LXC image, and do not support multi base image.</div><div style="font-family:monospace,monospace;font-size:small"><br></div><div style="font-family:monospace,monospace;font-size:small">if not, could u provide any prove for this?</div></div></div></blockquote><div><br></div></span><div>OSA supports the implementation of OpenStack on bare metal or in LXC machine containers, so we need to cater for both. When an LXC machine container is deployed we've chosen to use the strategy of always implementing the same OS in the container as is implemented on the host. This simplifies our testing greatly.</div><div><br></div><div>For the sake of background information, seeing as you asked, the base LXC image we're using comes from <a href="https://images.linuxcontainers.org/" target="_blank">https://images.linuxcontainers.org/</a> giving us the ability to support multiple versions, multiple distributions and multiple architectures, and it's especially nifty that the entire image build process is open source and therefore can be implemented and customised by our deployers.</div><div><br></div><div>I guess this is similar for Kolla in a different way because the image pipeline is defined by the project and implemented through the docker image building processes.</div></div>
</div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a 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 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></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><span style="font-size:13px;border-collapse:collapse"><font face="monospace, monospace">Regards,</font></span></div><div><span style="font-size:13px;border-collapse:collapse"><font face="monospace, monospace">Jeffrey Zhang</font></span></div><div><span style="font-family:monospace,monospace;font-size:12.8px">Blog: </span><a href="http://xcodest.me/" style="font-family:monospace,monospace;font-size:12.8px" target="_blank">http://xcodest.me</a><font face="monospace, monospace"><br></font></div></div></div></div></div></div></div></div></div>
</div>