Open Stack

+ I've just discussed UX for Ubuntu bootstrap in #fuel-dev [1], which
doesn't look very clear at the moment.

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?)

Thanks,

[1] http://irclog.perlgeek.de/fuel-dev/2015-08-17

On Mon, Aug 17, 2015 at 10:08 AM Mike Scherbakov <mscherbakov at mirantis.com>
wrote:

> Hi all,
> 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.
>
> These are the bugs I came across:
> [1] https://bugs.launchpad.net/fuel/+bug/1485188
> [2] https://bugs.launchpad.net/fuel/+bug/1481721
> [3] https://bugs.launchpad.net/fuel/+bug/1482242
> [4] https://bugs.launchpad.net/fuel/+bug/1483188
> [5] https://bugs.launchpad.net/fuel/+bug/1485188
>
> 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?
> 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.
>
> Thanks,
>
> On Mon, Aug 17, 2015 at 12:03 AM Lukasz Oles <loles at mirantis.com> wrote:
>
>> On Mon, Aug 17, 2015 at 7:16 AM, Alexei Sheplyakov
>> <asheplyakov at mirantis.com> wrote:
>> > Lukasz,
>> >
>> >> As I see, unfortunatly script which you recommend to use does not use
>> this
>> >> paths.
>> >> Instead it have hardcoded values.
>> >
>> > Actually the script does use the values from the config file
>> > (/etc/fuel-bootstrap-image.conf) generated by fuelmenu.
>> Ah, I missed it. Thx
>>
>> >> Now we need to update paths in two places. Why is that?
>> >
>> > There are fallback settings in the script so it can work without
>> > fuelmenu/config file.
>> >
>> > Best regards,
>> >       Alexei
>> >
>> >
>> > On Fri, Aug 14, 2015 at 2:12 PM, Lukasz Oles <loles at mirantis.com>
>> wrote:
>> >>
>> >> Hello,
>> >>
>> >> there is some inconsistency here. Currently I'm fixing bug[1] in
>> >> fuelmemu. In my fix[2] I changed paths to repos. As I see,
>> >> unfortunatly script which you recommend to use does not use this
>> >> paths. Instead it have hardcoded values.
>> >> Now we need to update paths in two places. Why is that?
>> >>
>> >> 1. https://bugs.launchpad.net/fuel/+bug/1484648
>> >> 2. https://review.openstack.org/#/c/213090/
>> >> 3.
>> >>
>> https://github.com/stackforge/fuel-main/blob/master/fuel-bootstrap-image-builder/bin/fuel-bootstrap-image#L14
>> >>
>> >> Regards
>> >>
>> >> On Thu, Aug 13, 2015 at 5:39 PM, Mikhail Semenov <
>> msemenov at mirantis.com>
>> >> wrote:
>> >> > Hi all,
>> >> >
>> >> > We have new feature in the upcoming release MOS 7.0 - Ubuntu-based
>> >> > bootstrap
>> >> > in addition to current CentOS-based one. Design spec can be found
>> here.
>> >> >
>> >> > Current 7.0 ISO contains 2 bootstrap images: CentOS-based (default)
>> and
>> >> > Ubuntu-based. You can easily switch to Ubuntu-based bootstrap using
>> this
>> >> > steps:
>> >> > 1. Make sure the master node can access Ubuntu
>> >> > (http://archive.ubuntu.com/ubuntu) and MOS
>> >> > (http://mirror.fuel-infra.org/mos-repos) APT repositories.
>> >> > 2. Run the following command on the master node:
>> >> > fuel-bootstrap-image-set ubuntu
>> >> > 3. Just in a case restart dnsmasq:
>> >> > dockerctl shell cobbler service dnsmasq restart
>> >> > 4. Reboot the slave nodes.
>> >> >
>> >> > There are only 2 weeks left for testing. On 08/27 we will make a
>> >> > decision
>> >> > about using Ubuntu bootstrap by default in MOS 7.0. It depends on the
>> >> > test
>> >> > results and statistics(more deployments - more confidence).
>> >> >
>> >> > I want to ask everyone to try new Ubuntu bootstrap. Please, deploy
>> it on
>> >> > your environments and file bugs in case of failures. It's most
>> important
>> >> > for
>> >> > partners and plugin developers. Feel free to contact Alexei
>> >> > Sheplyakov(feature lead) and me in case of questions.
>> >> >
>> >> > --
>> >> > Thanks,
>> >> > Michael
>> >> >
>> >> >
>> >> >
>> __________________________________________________________________________
>> >> > OpenStack Development Mailing List (not for usage questions)
>> >> > Unsubscribe:
>> >> > OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Łukasz Oleś
>> >
>> >
>>
>>
>>
>> --
>> Łukasz Oleś
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> --
> Mike Scherbakov
> #mihgen
>
-- 
Mike Scherbakov
#mihgen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150817/7911ea95/attachment.html>