fuel-dev team mailing list archive

[Vladimir Kuklin <vkuklin@xxxxxxxxxxxx>]

It should be also related to Nailgun API and CLI.


On Wed, Feb 19, 2014 at 11:45 AM, Mike Scherbakov
<mscherbakov@xxxxxxxxxxxx>wrote:

> Thanks folks.
>
> Vladimir, should we track it in
> https://bugs.launchpad.net/fuel/+bug/1263072, just change description to
> reflect that the only Fuel Library and Documentation are affected?
>
> Thanks,
>
>
> On Wed, Feb 19, 2014 at 3:20 AM, Roman Alekseenkov <
> ralekseenkov@xxxxxxxxxxxx> wrote:
>
>> Vova,
>>
>> We had to use 3.10 in 4 deployments, so there is a definitely value in
>> having an option to select a kernel.
>>
>> +1 to Andrew. I don't even mind having 3.10 as an "experimental" option
>> in the UI dropdown.
>>
>> Thanks,
>> Roman
>>
>>
>> On Tue, Feb 18, 2014 at 2:31 PM, Andrew Woodward <xarses@xxxxxxxxx>wrote:
>>
>>> Yes, I think there is value to allowing this to be set from
>>> fuel-client. I'm hesitant to add it to the UI as it can create other
>>> regressions when the end user does not properly test it. Proper
>>> disclaimers are necessary until we are shipping Centos 7 and 3.10 is
>>> the native kernel.
>>>
>>> On Tue, Feb 18, 2014 at 7:17 AM, Vladimir Kuklin <vkuklin@xxxxxxxxxxxx>
>>> wrote:
>>> > Fuelers
>>> >
>>> > I am asking you how often did you face old Centos kernel-related bugs
>>> (e.g.
>>> > old hardware drivers and vlan-splinters issue) and dreamed of moving
>>> to the
>>> > newer kernel. We do have kernel-ml 3.10 from el-repo included into our
>>> ISO.
>>> > But one will need to specify it manually as the kernel to be installed
>>> by
>>> > altering CentOS installation snippet for Anaconda. Thus I am wondering
>>> if
>>> > there is any value of automating it somehow by providing API calls and
>>> UI
>>> > checkboxes for this workaround.
>>> >
>>> > Thanks
>>> >
>>> > --
>>> > Yours Faithfully,
>>> > Vladimir Kuklin,
>>> > Senior Deployment Engineer,
>>> > Mirantis, Inc.
>>> > +7 (495) 640-49-04
>>> > +7 (926) 702-39-68
>>> > Skype kuklinvv
>>> > 45bk3, Vorontsovskaya Str.
>>> > Moscow, Russia,
>>> > www.mirantis.com
>>> > www.mirantis.ru
>>> > vkuklin@xxxxxxxxxxxx
>>> >
>>> > --
>>> > Mailing list: https://launchpad.net/~fuel-dev
>>> > Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>> > Unsubscribe : https://launchpad.net/~fuel-dev
>>> > More help   : https://help.launchpad.net/ListHelp
>>> >
>>>
>>>
>>>
>>> --
>>> If google has done it, Google did it right!
>>>
>>> --
>>> Mailing list: https://launchpad.net/~fuel-dev
>>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~fuel-dev
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>> --
>> Mailing list: https://launchpad.net/~fuel-dev
>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~fuel-dev
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Mike Scherbakov
> #mihgen
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Yours Faithfully,
Vladimir Kuklin,
Senior Deployment Engineer,
Mirantis, Inc.
+7 (495) 640-49-04
+7 (926) 702-39-68
Skype kuklinvv
45bk3, Vorontsovskaya Str.
Moscow, Russia,
www.mirantis.com <http://www.mirantis.ru/>
www.mirantis.ru
vkuklin@xxxxxxxxxxxx