<div dir="ltr">+ I've just discussed UX for Ubuntu bootstrap in #fuel-dev [1], which doesn't look very clear at the moment.<div><br></div><div>Mikhail - can you please help to clear it up? Namely, can I build Ubuntu bootstrap on Fuel master without direct Internet access? How can I trigger its build (is it from Fuel menu or from master node console?)</div><div><br></div><div>Thanks,</div><div><br></div><div>[1] <a href="http://irclog.perlgeek.de/fuel-dev/2015-08-17">http://irclog.perlgeek.de/fuel-dev/2015-08-17</a></div><div><br><div class="gmail_quote"><div dir="ltr">On Mon, Aug 17, 2015 at 10:08 AM Mike Scherbakov <<a href="mailto:mscherbakov@mirantis.com">mscherbakov@mirantis.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi all,<div>what is the current status of the feature in terms of readiness for production use? I'm wondering as I see a number of bugs, and so we might want to still have it in experimental mode for 7.0, and enable in 8.0.</div><div><br></div><div>These are the bugs I came across:</div><div>[1] <a href="https://bugs.launchpad.net/fuel/+bug/1485188" target="_blank">https://bugs.launchpad.net/fuel/+bug/1485188</a><br>[2] <a href="https://bugs.launchpad.net/fuel/+bug/1481721" target="_blank">https://bugs.launchpad.net/fuel/+bug/1481721</a><br>[3] <a href="https://bugs.launchpad.net/fuel/+bug/1482242" target="_blank">https://bugs.launchpad.net/fuel/+bug/1482242</a><br>[4] <a href="https://bugs.launchpad.net/fuel/+bug/1483188" target="_blank">https://bugs.launchpad.net/fuel/+bug/1483188</a><br>[5] <a href="https://bugs.launchpad.net/fuel/+bug/1485188" target="_blank">https://bugs.launchpad.net/fuel/+bug/1485188</a></div><div><br></div><div>QA team - what is your point of view? Do you see that it's converging to working solution with high level of confidence or not?</div><div>Some of the bugs seem to be blocking easy scale testing [1,2,4,5]. If it's the case, then I would rather revert back to CentOS-default: we can't block testing at this stage in the release timeline.</div><div><br></div><div>Thanks,</div></div><div dir="ltr"><div><br><div class="gmail_quote"><div dir="ltr">On Mon, Aug 17, 2015 at 12:03 AM Lukasz Oles <<a href="mailto:loles@mirantis.com" target="_blank">loles@mirantis.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Aug 17, 2015 at 7:16 AM, Alexei Sheplyakov<br>
<<a href="mailto:asheplyakov@mirantis.com" target="_blank">asheplyakov@mirantis.com</a>> wrote:<br>
> Lukasz,<br>
><br>
>> As I see, unfortunatly script which you recommend to use does not use this<br>
>> paths.<br>
>> Instead it have hardcoded values.<br>
><br>
> Actually the script does use the values from the config file<br>
> (/etc/fuel-bootstrap-image.conf) generated by fuelmenu.<br>
Ah, I missed it. Thx<br>
<br>
>> Now we need to update paths in two places. Why is that?<br>
><br>
> There are fallback settings in the script so it can work without<br>
> fuelmenu/config file.<br>
><br>
> Best regards,<br>
> Alexei<br>
><br>
><br>
> On Fri, Aug 14, 2015 at 2:12 PM, Lukasz Oles <<a href="mailto:loles@mirantis.com" target="_blank">loles@mirantis.com</a>> wrote:<br>
>><br>
>> Hello,<br>
>><br>
>> there is some inconsistency here. Currently I'm fixing bug[1] in<br>
>> fuelmemu. In my fix[2] I changed paths to repos. As I see,<br>
>> unfortunatly script which you recommend to use does not use this<br>
>> paths. Instead it have hardcoded values.<br>
>> Now we need to update paths in two places. Why is that?<br>
>><br>
>> 1. <a href="https://bugs.launchpad.net/fuel/+bug/1484648" rel="noreferrer" target="_blank">https://bugs.launchpad.net/fuel/+bug/1484648</a><br>
>> 2. <a href="https://review.openstack.org/#/c/213090/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/213090/</a><br>
>> 3.<br>
>> <a href="https://github.com/stackforge/fuel-main/blob/master/fuel-bootstrap-image-builder/bin/fuel-bootstrap-image#L14" rel="noreferrer" target="_blank">https://github.com/stackforge/fuel-main/blob/master/fuel-bootstrap-image-builder/bin/fuel-bootstrap-image#L14</a><br>
>><br>
>> Regards<br>
>><br>
>> On Thu, Aug 13, 2015 at 5:39 PM, Mikhail Semenov <<a href="mailto:msemenov@mirantis.com" target="_blank">msemenov@mirantis.com</a>><br>
>> wrote:<br>
>> > Hi all,<br>
>> ><br>
>> > We have new feature in the upcoming release MOS 7.0 - Ubuntu-based<br>
>> > bootstrap<br>
>> > in addition to current CentOS-based one. Design spec can be found here.<br>
>> ><br>
>> > Current 7.0 ISO contains 2 bootstrap images: CentOS-based (default) and<br>
>> > Ubuntu-based. You can easily switch to Ubuntu-based bootstrap using this<br>
>> > steps:<br>
>> > 1. Make sure the master node can access Ubuntu<br>
>> > (<a href="http://archive.ubuntu.com/ubuntu" rel="noreferrer" target="_blank">http://archive.ubuntu.com/ubuntu</a>) and MOS<br>
>> > (<a href="http://mirror.fuel-infra.org/mos-repos" rel="noreferrer" target="_blank">http://mirror.fuel-infra.org/mos-repos</a>) APT repositories.<br>
>> > 2. Run the following command on the master node:<br>
>> > fuel-bootstrap-image-set ubuntu<br>
>> > 3. Just in a case restart dnsmasq:<br>
>> > dockerctl shell cobbler service dnsmasq restart<br>
>> > 4. Reboot the slave nodes.<br>
>> ><br>
>> > There are only 2 weeks left for testing. On 08/27 we will make a<br>
>> > decision<br>
>> > about using Ubuntu bootstrap by default in MOS 7.0. It depends on the<br>
>> > test<br>
>> > results and statistics(more deployments - more confidence).<br>
>> ><br>
>> > I want to ask everyone to try new Ubuntu bootstrap. Please, deploy it on<br>
>> > your environments and file bugs in case of failures. It's most important<br>
>> > for<br>
>> > partners and plugin developers. Feel free to contact Alexei<br>
>> > Sheplyakov(feature lead) and me in case of questions.<br>
>> ><br>
>> > --<br>
>> > Thanks,<br>
>> > Michael<br>
>> ><br>
>> ><br>
>> > __________________________________________________________________________<br>
>> > OpenStack Development Mailing List (not for usage questions)<br>
>> > Unsubscribe:<br>
>> > <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>
>><br>
>><br>
>><br>
>> --<br>
>> Łukasz Oleś<br>
><br>
><br>
<br>
<br>
<br>
--<br>
Łukasz Oleś<br>
<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>
</blockquote></div></div></div><div dir="ltr">-- <br></div><div dir="ltr">Mike Scherbakov<br>#mihgen</div></blockquote></div></div></div><div dir="ltr">-- <br></div><div dir="ltr">Mike Scherbakov<br>#mihgen</div>