<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">+1<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">25 бер. 2016 р. о 13:31 Dmitry Pyzhov <<a href="mailto:dpyzhov@mirantis.com" class="">dpyzhov@mirantis.com</a>> написав(ла):</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">As we are going to deprecate logs on UI I'm going to mark following bugs as "won't fix". Any objections?</div><div class="">High priority bug:</div><div class=""><a href="https://bugs.launchpad.net/fuel/+bug/1553170" class="">https://bugs.launchpad.net/fuel/+bug/1553170</a></div><div class="">Medium priority:</div><div class=""><a href="https://bugs.launchpad.net/fuel/+bug/1554546" class="">https://bugs.launchpad.net/fuel/+bug/1554546</a><br class=""></div><div class=""><a href="https://bugs.launchpad.net/fuel/+bug/1539508" class="">https://bugs.launchpad.net/fuel/+bug/1539508</a></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Mar 14, 2016 at 3:02 PM, Roman Prykhodchenko <span dir="ltr" class=""><<a href="mailto:me@romcheg.me" target="_blank" class="">me@romcheg.me</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Folks, I’ve registered a blueprint [1] and created an etherpad document [2] where we can co-work on the spec before posting it to a formal review. Let’s cooperate to summarize what we need to do.<br class="">
<br class="">
<br class="">
1. <a href="https://blueprints.launchpad.net/fuel/+spec/remove-logs-from-nailgun" rel="noreferrer" target="_blank" class="">https://blueprints.launchpad.net/fuel/+spec/remove-logs-from-nailgun</a><br class="">
2. <a href="https://etherpad.openstack.org/p/remove-logs-from_Nailgun" rel="noreferrer" target="_blank" class="">https://etherpad.openstack.org/p/remove-logs-from_Nailgun</a><br class="">
<br class="">
- romcheg<br class="">
<br class="">
> 14 бер. 2016 р. о 09:53 Bogdan Dobrelya <<a href="mailto:bdobrelia@mirantis.com" class="">bdobrelia@mirantis.com</a>> написав(ла):<br class="">
<div class="HOEnZb"><div class="h5">><br class="">
> On 03/14/2016 09:38 AM, Anastasia Urlapova wrote:<br class="">
>> +1 to Vitaliy, it would be nice find somewhere a details for migration.<br class="">
>> And one more concern I should highlight - for some users logless UI may<br class="">
>> be challenging thing.<br class="">
>> The logs removing shouldn't affect the UX.<br class="">
><br class="">
> Logs will still live at the master node's /var/log/remote<br class="">
><br class="">
>><br class="">
>><br class="">
>> Nastya.<br class="">
>><br class="">
>><br class="">
>> On Sat, Mar 12, 2016 at 3:08 AM, Andrew Woodward <<a href="mailto:xarses@gmail.com" class="">xarses@gmail.com</a><br class="">
>> <mailto:<a href="mailto:xarses@gmail.com" class="">xarses@gmail.com</a>>> wrote:<br class="">
>><br class="">
>> I think we can address it by retaining deployment logs in<br class="">
>> nailgun/ui, this also removes the chicken and egg problem. after LMA<br class="">
>> is deployed it can be allowed to re-own 'logs' button on UI once<br class="">
>> it's deployed, including redirecting fuel logs there.<br class="">
>><br class="">
>> On Fri, Mar 11, 2016 at 2:07 PM Mike Scherbakov<br class="">
>> <<a href="mailto:mscherbakov@mirantis.com" class="">mscherbakov@mirantis.com</a> <mailto:<a href="mailto:mscherbakov@mirantis.com" class="">mscherbakov@mirantis.com</a>>> wrote:<br class="">
>><br class="">
>> We can sort out details later. In a worst case, the warning will<br class="">
>> be there in Newton too, and feature will go away only in O*<br class="">
>> release. So let's proceed with the bug..<br class="">
>><br class="">
>> On Fri, Mar 11, 2016 at 1:02 PM Vitaly Kramskikh<br class="">
>> <<a href="mailto:vkramskikh@mirantis.com" class="">vkramskikh@mirantis.com</a> <mailto:<a href="mailto:vkramskikh@mirantis.com" class="">vkramskikh@mirantis.com</a>>> wrote:<br class="">
>><br class="">
>> We can add the warning, but I think before we do this we<br class="">
>> should have clear migration plan. According to this thread,<br class="">
>> some parts are still not clear.<br class="">
>><br class="">
>> 2016-03-11 22:00 GMT+03:00 Mike Scherbakov<br class="">
>> <<a href="mailto:mscherbakov@mirantis.com" class="">mscherbakov@mirantis.com</a> <mailto:<a href="mailto:mscherbakov@mirantis.com" class="">mscherbakov@mirantis.com</a>>>:<br class="">
>><br class="">
>> Deprecation warning for Fuel<br class="">
>> Mitaka: <a href="https://bugs.launchpad.net/fuel/+bug/1556244" rel="noreferrer" target="_blank" class="">https://bugs.launchpad.net/fuel/+bug/1556244</a>.<br class="">
>><br class="">
>><br class="">
>> On Fri, Mar 11, 2016 at 8:59 AM Roman Prykhodchenko<br class="">
>> <<a href="mailto:me@romcheg.me" class="">me@romcheg.me</a> <mailto:<a href="mailto:me@romcheg.me" class="">me@romcheg.me</a>>> wrote:<br class="">
>><br class="">
>> Since there are a lot of supporters for this idea,<br class="">
>> what do you folks think about creating a BP spec<br class="">
>> where we can describe what we should do in order to<br class="">
>> remove logs from UI and Nailgun? I also propose to<br class="">
>> file a bug about adding a deprecation warning to<br class="">
>> Mitaka release of Fuel.<br class="">
>><br class="">
>><br class="">
>>> 11 бер. 2016 р. о 16:55 Bogdan Dobrelya<br class="">
>>> <<a href="mailto:bdobrelia@mirantis.com" class="">bdobrelia@mirantis.com</a><br class="">
>>> <mailto:<a href="mailto:bdobrelia@mirantis.com" class="">bdobrelia@mirantis.com</a>>> написав(ла):<br class="">
>>><br class="">
>>> On 03/11/2016 04:46 PM, Mike Scherbakov wrote:<br class="">
>>>> +1 to remove logs from Fuel UI in Fuel Newton.<br class="">
>>>> In Fuel Mitaka we'd need to put a deprecation<br class="">
>>>> warning somewhere.<br class="">
>>><br class="">
>>> I agree, there is not much sense having non<br class="">
>>> flexible (no content<br class="">
>>> filters) logs view in UI. LMA plugins shall cover<br class="">
>>> this area as well.<br class="">
>>><br class="">
>>>><br class="">
>>>><br class="">
>>>> On Fri, Mar 11, 2016, 04:57 Patrick Petit<br class="">
>>>> <<a href="mailto:ppetit@mirantis.com" class="">ppetit@mirantis.com</a> <mailto:<a href="mailto:ppetit@mirantis.com" class="">ppetit@mirantis.com</a>><br class="">
>>>> <mailto:<a href="mailto:ppetit@mirantis.com" class="">ppetit@mirantis.com</a>>> wrote:<br class="">
>>>><br class="">
>>>><br class="">
>>>> On 11 March 2016 at 12:51:40, Igor Kalnitsky<br class="">
>>>> (<a href="mailto:ikalnitsky@mirantis.com" class="">ikalnitsky@mirantis.com</a><br class="">
>>>> <mailto:<a href="mailto:ikalnitsky@mirantis.com" class="">ikalnitsky@mirantis.com</a>> <mailto:<a href="mailto:ikalnitsky@mirantis.com" class="">ikalnitsky@mirantis.com</a>>)<br class="">
>>>> wrote:<br class="">
>>>><br class="">
>>>>> Patrick,<br class="">
>>>>><br class="">
>>>>> Sorry, but I meant another question. I<br class="">
>>>>> thought that LMA plugin should<br class="">
>>>>> be installed in some environment before we<br class="">
>>>>> can start use it. Is<br class="">
>>>>> this a<br class="">
>>>>> case? If so, it means we can't use for master<br class="">
>>>>> node until some<br class="">
>>>>> environment is deployed.<br class="">
>>>><br class="">
>>>> Right. This is the chicken and egg problem I<br class="">
>>>> mentioned earlier...<br class="">
>>>><br class="">
>>>> But this is not a “problem” specific to Fuel.<br class="">
>>>> My take on this is is<br class="">
>>>> that ops management tooling (logging,<br class="">
>>>> monitoring) should be<br class="">
>>>> installed off-band before any OpenStack<br class="">
>>>> deployment. In fact, in<br class="">
>>>> real-world usage, we frequently get asks to<br class="">
>>>> have the monitoring and<br class="">
>>>> logging services of StackLight installed<br class="">
>>>> permanently for<br class="">
>>>> multi-enviroments. And so, one approach would<br class="">
>>>> be to make Stacklight<br class="">
>>>> backend services the first bits of software<br class="">
>>>> installed by Fuel (if<br class="">
>>>> not already there), then reconfigure Fuel to<br class="">
>>>> hook into those<br class="">
>>>> services and only then, enter into the regular<br class="">
>>>> OpenStack<br class="">
>>>> provisioning mode.<br class="">
>>>><br class="">
>>>>><br class="">
>>>>><br class="">
>>>>> On Fri, Mar 11, 2016 at 12:52 PM, Patrick Petit<br class="">
>>>>> <<a href="mailto:ppetit@mirantis.com" class="">ppetit@mirantis.com</a><br class="">
>>>>> <mailto:<a href="mailto:ppetit@mirantis.com" class="">ppetit@mirantis.com</a>> <mailto:<a href="mailto:ppetit@mirantis.com" class="">ppetit@mirantis.com</a>>><br class="">
>>>>> wrote:<br class="">
>>>>>><br class="">
>>>>>> On 11 March 2016 at 11:34:32, Igor Kalnitsky<br class="">
>>>>>> (<a href="mailto:ikalnitsky@mirantis.com" class="">ikalnitsky@mirantis.com</a><br class="">
>>>>>> <mailto:<a href="mailto:ikalnitsky@mirantis.com" class="">ikalnitsky@mirantis.com</a>> <mailto:<a href="mailto:ikalnitsky@mirantis.com" class="">ikalnitsky@mirantis.com</a>>)<br class="">
>>>>>> wrote:<br class="">
>>>>>><br class="">
>>>>>> Hey Roman,<br class="">
>>>>>><br class="">
>>>>>> Thank you for bringing this up. +1 from my<br class="">
>>>>>> side, especially taking<br class="">
>>>>>> into account the patch where we tried to solve<br class="">
>>>>>> logrotated logs problem<br class="">
>>>>>> [1]. It's complex and unsupportable, as well as<br class="">
>>>>>> already existed<br class="">
>>>>>> logview code in Nailgun.<br class="">
>>>>>><br class="">
>>>>>> Patrick, Simon,<br class="">
>>>>>><br class="">
>>>>>> Does LMA plugin support logs from master node?<br class="">
>>>>>> Or it's designed to<br class="">
>>>>>> watch environment's logs?<br class="">
>>>>>><br class="">
>>>>>> No it’s not designed specifically for<br class="">
>>>>>> environment logs. Can be adapted to<br class="">
>>>>>> any log format.<br class="">
>>>>>><br class="">
>>>>>> Would just need to write a parser like you<br class="">
>>>>>> would with logstach when logs are<br class="">
>>>>>> not standard.<br class="">
>>>>>><br class="">
>>>>>> Patrick<br class="">
>>>>>><br class="">
>>>>>><br class="">
>>>>>><br class="">
>>>>>> Thanks,<br class="">
>>>>>> Igor<br class="">
>>>>>><br class="">
>>>>>><br class="">
>>>>>> [1]: <a href="https://review.openstack.org/#/c/243240/" rel="noreferrer" target="_blank" class="">https://review.openstack.org/#/c/243240/</a><br class="">
>>>>>><br class="">
>>>>>> On Fri, Mar 11, 2016 at 11:53 AM, Patrick Petit<br class="">
>>>>>> <<a href="mailto:ppetit@mirantis.com" class="">ppetit@mirantis.com</a><br class="">
>>>>>> <mailto:<a href="mailto:ppetit@mirantis.com" class="">ppetit@mirantis.com</a>> <mailto:<a href="mailto:ppetit@mirantis.com" class="">ppetit@mirantis.com</a>>><br class="">
>>>>>> wrote:<br class="">
>>>>>>> Fuelers,<br class="">
>>>>>>><br class="">
>>>>>>> As Simon said, we already have a log<br class="">
>>>>>>> centralisation solution for MOS<br class="">
>>>>>>> delivered as a Fuel plugins known as<br class="">
>>>>>>> StackLight / LMA toolset. And so<br class="">
>>>>>>> objectively, there is no need to have log<br class="">
>>>>>>> management in Nailgun anymore.<br class="">
>>>>>>> To<br class="">
>>>>>>> go one step further we suggested several times<br class="">
>>>>>>> to have a StackLight agent<br class="">
>>>>>>> installed on the Fuel master node to also<br class="">
>>>>>>> collect and centralise those<br class="">
>>>>>>> logs.<br class="">
>>>>>>> There is a little bit of a chicken and egg<br class="">
>>>>>>> problem to resolve but I think<br class="">
>>>>>>> it<br class="">
>>>>>>> is worth a try to have that nailed down in the<br class="">
>>>>>>> roadmap for Fuel 10.<br class="">
>>>>>>> Cheers<br class="">
>>>>>>> - Patrick<br class="">
>>>>>>><br class="">
>>>>>>><br class="">
>>>>>>> On 11 March 2016 at 10:07:28, Simon Pasquier<br class="">
>>>>>>> (<a href="mailto:spasquier@mirantis.com" class="">spasquier@mirantis.com</a><br class="">
>>>>>>> <mailto:<a href="mailto:spasquier@mirantis.com" class="">spasquier@mirantis.com</a>> <mailto:<a href="mailto:spasquier@mirantis.com" class="">spasquier@mirantis.com</a>>)<br class="">
>>>>>>> wrote:<br class="">
>>>>>>><br class="">
>>>>>>> Hello Roman,<br class="">
>>>>>>><br class="">
>>>>>>> On Fri, Mar 11, 2016 at 9:57 AM, Roman<br class="">
>>>>>>> Prykhodchenko <<a href="mailto:me@romcheg.me" class="">me@romcheg.me</a><br class="">
>>>>>>> <mailto:<a href="mailto:me@romcheg.me" class="">me@romcheg.me</a>> <mailto:<a href="mailto:me@romcheg.me" class="">me@romcheg.me</a>>><br class="">
>>>>>>> wrote:<br class="">
>>>>>>>><br class="">
>>>>>>>> Fuelers,<br class="">
>>>>>>>><br class="">
>>>>>>>> I remember we’ve discussing this topic in our<br class="">
>>>>>>>> couloirs before but I’d<br class="">
>>>>>>>> like<br class="">
>>>>>>>> to bring that discussion to a more official<br class="">
>>>>>>>> format.<br class="">
>>>>>>>><br class="">
>>>>>>>> Let me state a few reasons to do this:<br class="">
>>>>>>>><br class="">
>>>>>>>> - Log management code in Nailgun is<br class="">
>>>>>>>> overcomplicated<br class="">
>>>>>>>> - Working with logs on big scale deployments<br class="">
>>>>>>>> is barely possible given the<br class="">
>>>>>>>> current representation<br class="">
>>>>>>>> - Due to overcomplexity and ineffectiveness<br class="">
>>>>>>>> of the code we always get<br class="">
>>>>>>>> recurring bugs like [1]. That eats tons of<br class="">
>>>>>>>> time to resolve.<br class="">
>>>>>>>> - There are much better specialized tools,<br class="">
>>>>>>>> say Logstash [2], that can<br class="">
>>>>>>>> deal<br class="">
>>>>>>>> with logs much more effectively.<br class="">
>>>>>>>><br class="">
>>>>>>>><br class="">
>>>>>>>> There may be more reasons bus I think even<br class="">
>>>>>>>> the already mentioned ones are<br class="">
>>>>>>>> enough to think about the following proposal:<br class="">
>>>>>>>><br class="">
>>>>>>>> - Remove Logs tab from Fuel Web UI<br class="">
>>>>>>>> - Remove logs support from Nailgun<br class="">
>>>>>>>> - Create mechanism that allows to configure<br class="">
>>>>>>>> different log management<br class="">
>>>>>>>> software, say Logstash, Loggly, etc<br class="">
>>>>>>>><br class="">
>>>>>>>> - Choose a default software to install and<br class="">
>>>>>>>> provide a plugin for it from<br class="">
>>>>>>>> the box<br class="">
>>>>>>><br class="">
>>>>>>><br class="">
>>>>>>> This is what the LMA/StackLight plugins [1][2]<br class="">
>>>>>>> are meant for. No need to<br class="">
>>>>>>> develop anything new.<br class="">
>>>>>>><br class="">
>>>>>>> And I'm +1 with the removal of log management<br class="">
>>>>>>> from Fuel. As you said, it<br class="">
>>>>>>> can't scale...<br class="">
>>>>>>><br class="">
>>>>>>> [1]<br class="">
>>>>>>> <a href="http://fuel-plugin-lma-collector.readthedocs.org/en/latest/" rel="noreferrer" target="_blank" class="">http://fuel-plugin-lma-collector.readthedocs.org/en/latest/</a><br class="">
>>>>>>> [2]<br class="">
>>>>>>> <a href="http://fuel-plugin-elasticsearch-kibana.readthedocs.org/en/latest/" rel="noreferrer" target="_blank" class="">http://fuel-plugin-elasticsearch-kibana.readthedocs.org/en/latest/</a><br class="">
>>>>>>><br class="">
>>>>>>><br class="">
>>>>>>>><br class="">
>>>>>>>><br class="">
>>>>>>>><br class="">
>>>>>>>> References<br class="">
>>>>>>>> 1. <a href="https://bugs.launchpad.net/fuel/+bug/1553170" rel="noreferrer" target="_blank" class="">https://bugs.launchpad.net/fuel/+bug/1553170</a><br class="">
>>>>>>>> 2. <a href="https://www.elastic.co/products/logstash" rel="noreferrer" target="_blank" class="">https://www.elastic.co/products/logstash</a><br class="">
>>>>>>>><br class="">
>>>>>>>><br class="">
>>>>>>>> - romcheg<br class="">
>>>>>>>><br class="">
>>>>>>>><br class="">
>>>>>>>> __________________________________________________________________________<br class="">
>>>>>>>> OpenStack Development Mailing List (not for<br class="">
>>>>>>>> usage questions)<br class="">
>>>>>>>> Unsubscribe:<br class="">
>>>>>>>> <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a><br class="">
>>>>>>>> <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>>?subject:unsubscribe<br class="">
>>>>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
>>>>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe</a>>><br class="">
>>>>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>>>>>>>><br class="">
>>>>>>><br class="">
>>>>>>> __________________________________________________________________________<br class="">
>>>>>>> OpenStack Development Mailing List (not for<br class="">
>>>>>>> usage questions)<br class="">
>>>>>>> Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a><br class="">
>>>>>>> <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>>?subject:unsubscribe<br class="">
>>>>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
>>>>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe</a>>><br class="">
>>>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>>>>>>><br class="">
>>>>>>><br class="">
>>>>>>> __________________________________________________________________________<br class="">
>>>>>>> OpenStack Development Mailing List (not for<br class="">
>>>>>>> usage questions)<br class="">
>>>>>>> Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a><br class="">
>>>>>>> <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>>?subject:unsubscribe<br class="">
>>>>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
>>>>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe</a>>><br class="">
>>>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>>>>>>><br class="">
>>>>>><br class="">
>>>>>> __________________________________________________________________________<br class="">
>>>>>> OpenStack Development Mailing List (not for<br class="">
>>>>>> usage questions)<br class="">
>>>>>> Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a><br class="">
>>>>>> <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>>?subject:unsubscribe<br class="">
>>>>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
>>>>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe</a>>><br class="">
>>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>>>> __________________________________________________________________________<br class="">
>>>> OpenStack Development Mailing List (not for<br class="">
>>>> usage questions)<br class="">
>>>> Unsubscribe:<br class="">
>>>> <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a><br class="">
>>>> <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>>?subject:unsubscribe<br class="">
>>>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
>>>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe</a>>><br class="">
>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>>>><br class="">
>>>> --<br class="">
>>>> Mike Scherbakov<br class="">
>>>> #mihgen<br class="">
>>>><br class="">
>>>><br class="">
>>>> __________________________________________________________________________<br class="">
>>>> OpenStack Development Mailing List (not for usage<br class="">
>>>> questions)<br class="">
>>>> Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a><br class="">
>>>> <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>>?subject:unsubscribe<br class="">
>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>>>><br class="">
>>><br class="">
>>><br class="">
>>> --<br class="">
>>> Best regards,<br class="">
>>> Bogdan Dobrelya,<br class="">
>>> Irc #bogdando<br class="">
>>><br class="">
>>> __________________________________________________________________________<br class="">
>>> OpenStack Development Mailing List (not for usage<br class="">
>>> questions)<br class="">
>>> Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a><br class="">
>>> <mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>>?subject:unsubscribe<br class="">
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>> __________________________________________________________________________<br class="">
>> OpenStack Development Mailing List (not for usage<br class="">
>> questions)<br class="">
>> Unsubscribe:<br class="">
>> <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br class="">
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>><br class="">
>> --<br class="">
>> Mike Scherbakov<br class="">
>> #mihgen<br class="">
>><br class="">
>> __________________________________________________________________________<br class="">
>> OpenStack Development Mailing List (not for usage questions)<br class="">
>> Unsubscribe:<br class="">
>> <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br class="">
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>><br class="">
>><br class="">
>><br class="">
>><br class="">
>> --<br class="">
>> Vitaly Kramskikh,<br class="">
>> Fuel UI Tech Lead,<br class="">
>> Mirantis, Inc.<br class="">
>> __________________________________________________________________________<br class="">
>> OpenStack Development Mailing List (not for usage questions)<br class="">
>> Unsubscribe:<br class="">
>> <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br class="">
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>><br class="">
>> --<br class="">
>> Mike Scherbakov<br class="">
>> #mihgen<br class="">
>> __________________________________________________________________________<br class="">
>> OpenStack Development Mailing List (not for usage questions)<br class="">
>> Unsubscribe:<br class="">
>> <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br class="">
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>><br class="">
>> --<br class="">
>><br class="">
>> --<br class="">
>><br class="">
>> Andrew Woodward<br class="">
>><br class="">
>> Mirantis<br class="">
>><br class="">
>> Fuel Community Ambassador<br class="">
>><br class="">
>> Ceph Community<br class="">
>><br class="">
>><br class="">
>> __________________________________________________________________________<br class="">
>> OpenStack Development Mailing List (not for usage questions)<br class="">
>> Unsubscribe:<br class="">
>> <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
>> <<a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br class="">
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>><br class="">
>><br class="">
>><br class="">
>><br class="">
>> __________________________________________________________________________<br class="">
>> OpenStack Development Mailing List (not for usage questions)<br class="">
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
>><br class="">
><br class="">
><br class="">
> --<br class="">
> Best regards,<br class="">
> Bogdan Dobrelya,<br class="">
> Irc #bogdando<br class="">
><br class="">
> __________________________________________________________________________<br class="">
> OpenStack Development Mailing List (not for usage questions)<br class="">
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class="">
</div></div><br class="">__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class=""></blockquote></div><br class=""></div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>