<div dir="auto">Or start writing down (in the BP) what you want to put in the driver.<div dir="auto">Network, lbaas, scripts, the order of the scripts and then we can see</div><div dir="auto">if it's possible to adapt to the current coreos driver.</div><div dir="auto"><br></div><div dir="auto">Spyros</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Jan 24, 2017 22:54, "Hongbin Lu" <<a href="mailto:hongbin.lu@huawei.com">hongbin.lu@huawei.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-CA" link="blue" vlink="purple">
<div class="m_1515966872155398614WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">As Spyros mentioned, an option is to start by cloning the existing templates. However, I have a concern for this approach because it will incur a lot of duplication.
An alternative approach is modifying the existing CoreOS templates in-place. It might be a little difficult to implement but it saves your overhead to deprecate the old version and roll out the new version.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Best regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hongbin<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Spyros Trigazis [mailto:<a href="mailto:strigazi@gmail.com" target="_blank">strigazi@gmail.com</a>]
<br>
<b>Sent:</b> January-24-17 3:47 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [magnum] CoreOS template v2<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">Hi.<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">IMO, you should add a BP and start by adding a v2 driver in /contrib.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Cheers,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Spyros<u></u><u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On Jan 24, 2017 20:44, "Kevin Lefevre" <<a href="mailto:lefevre.kevin@gmail.com" target="_blank">lefevre.kevin@gmail.com</a>> wrote:<u></u><u></u></p>
<p class="MsoNormal">Hi,<br>
<br>
The CoreOS template is not really up to date and in sync with upstream CoreOS « Best Practice » (<a href="https://github.com/coreos/coreos-kubernetes" target="_blank">https://github.com/coreos/<wbr>coreos-kubernetes</a>), it is more a port of th fedora atomic template
but CoreOS has its own Kubernetes deployment method.<br>
<br>
I’d like to implement the changes to sync kubernetes deployment on CoreOS to latest kubernetes version (1.5.2) along with standards components according the CoreOS Kubernetes guide :<br>
- « Defaults » add ons like kube-dns , heapster and kube-dashboard (kube-ui has been deprecated for a long time and is obsolete)<br>
- Canal for network policy (Calico and Flannel)<br>
- Add support for RKT as container engine<br>
- Support sane default options recommended by Kubernetes upstream (admission control :
<a href="https://kubernetes.io/docs/admin/admission-controllers/" target="_blank">
https://kubernetes.io/docs/<wbr>admin/admission-controllers/</a>, using service account…)<br>
- Of course add every new parameters to HOT.<br>
<br>
These changes are difficult to implement as is (due to the fragment concept and everything is a bit messy between common and specific template fragment, especially for CoreOS).<br>
<br>
I’m wondering if it is better to clone the CoreOS v1 template to a new v2 template en build from here ?<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><u></u><u></u></p>
</div>
</div>
</div>
</div>
<br>______________________________<wbr>______________________________<wbr>______________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div></div>