Re: [openstack-dev] [fuel] Capacity table

the business logic. > Do we have to use new design or don’t. > > With best regards, Dmitry > > On 26 Jul 2016, at 17:47, Vitaly Kramskikh > wrote: > > Hi, Dmitry, > > Your design seems to be similar to one of our attempts to fix this bug: > https://review.openstack.o

Re: [openstack-dev] [fuel] Capacity table

pacity only. > > New design pros: > - cloud administrator can easily estimate all available resources for > cloud instances > > New design cons: > - if cloud doesn’t use Ceph then HDD value is zero > > What do you think about the new design? > &

Re: [openstack-dev] [Fuel] Merge IRC channels

OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc.

Re: [openstack-dev] [javascript] [infra] NPM Mirrors (IMPORTANT)

ng fine from dfw.rax, though you may run into > similar issues with other mirrors until those caches warm up. > > Michael > > On Thu, May 12, 2016 at 4:10 AM Vitaly Kramskikh > wrote: > >> Hi, Michael, >> >> I randomly get "error parsing json" for fu

Re: [openstack-dev] [javascript] [eslint-config-openstack] ECMAScript 6 / ECMAScript2015 rules.

_ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. __

Re: [openstack-dev] [javascript] [infra] NPM Mirrors (IMPORTANT)

Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc.

Re: [openstack-dev] [Fuel] Newton Design Summit sessions planning

t;>>> >>>> [1] >>>> http://lists.openstack.org/pipermail/openstack-dev/attachments/20160331/d59d38b7/attachment.pdf >>>> [2] https://wiki.openstack.org/wiki/Design_Summit >>>> [3] https://etherpad.openstack.org/p/fuel-newton-summit-planning >>>> [4] https://wiki.op

Re: [openstack-dev] [Fuel][Nailgun] Random failures in unit tests

them as soon as we face them. Let's > file a bug on each file in CI, and quicly prepare a separate patch > that removes fake thread from failed test. > > Thanks in advance, > Igor > > __ > OpenStack Development Mailing List (not for usage questi

Re: [openstack-dev] [Fuel] Removing logs from Fuel Web UI and Nailgun

>>__ >>OpenStack Development Mailing List (not for usage questions) >>Unsubscribe: >>openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >><http://openstack-dev-requ...@lists.openstack.or

Re: [openstack-dev] [Fuel] UI code freeze

ee to tell us. 2016-03-01 16:09 GMT+07:00 Vitaly Kramskikh : > The new repo has been created: https://github.com/openstack/fuel-ui. > Please move all change requests there. Fuel UI code in fuel-web repo is > going to be removed soon. > > 2016-02-26 19:53 GMT+07:00 Vladimir Ko

Re: [openstack-dev] [Fuel] [FFE] Unlock Settings Tab

s on the fly which require for it to return list of dicts) and support > of this stuff on your own, are you? > > On Wed, Mar 2, 2016 at 10:09 AM, Vitaly Kramskikh > wrote: > >> I think it's not a part of best practices to introduce changes like >> https://review.openstack

Re: [openstack-dev] [Fuel] [FFE] Unlock Settings Tab

ec/custom-graph-execution > [6] > https://blueprints.launchpad.net/fuel/+spec/save-deployment-info-in-database > > -- > --- > WBR, Alexey Shtokolov > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev

Re: [openstack-dev] [Fuel] UI code freeze

iling List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. _

Re: [openstack-dev] [Fuel][Fuel-Library] Nominating Matthew Mosesohn for Fuel Library Core

sts.openstack.org >>> ?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >>> >>> >>> __ >>> OpenStack Developme

Re: [openstack-dev] [Fuel] URL of Horizon is hard to find on the dashboard

how do you handle it with link now? > > On Fri, Feb 12, 2016 at 11:15 AM, Vitaly Kramskikh > wrote: > > Igor, > > > > Then we'll end up with 2 buttons (for HTTP and HTTPS links) for Horizon > and > > every plugin link, which would look quite ugly. We h

Re: [openstack-dev] [Fuel] URL of Horizon is hard to find on the dashboard

right size of line? It'd be easy to understand what to click to > visit the dashboard. > > - Igor > > On Thu, Feb 11, 2016 at 1:38 PM, Vitaly Kramskikh > wrote: > > Roman, > > > > For with enabled SSL it still can be quite long as it contains FQDN. And >

Re: [openstack-dev] [Fuel] URL of Horizon is hard to find on the dashboard

ssage. We've merged small style update to underline Horizon/plugin links, I think it would be enough to solve the issue. 2016-02-09 20:31 GMT+07:00 Roman Prykhodchenko : > Cannot we use display the same link we use in the title? > > 9 лют. 2016 р. о 14:14 Vitaly Kramskikh > написав(ла)

Re: [openstack-dev] [Fuel] URL of Horizon is hard to find on the dashboard

___ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly

Re: [openstack-dev] [Fuel] [Fuel UI] Node role list grouping

> Irc #bogdando > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack

Re: [openstack-dev] [Fuel] [Fuel UI] UI text guidelines

__ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listin

Re: [openstack-dev] [Fuel][Plugins] How do avoid duplicated links in the dashboard?

e questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. __ OpenSta

[openstack-dev] [Fuel] nova-network removal

ch is deprecated since 7.0? -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [Fuel] [Nailgun] Deadlocks and random test failures

gt; traceback, but not an actual deadlock. >> >> I'm not sure could it be a reason for failure or not, it's better to >> ask Alexander Kislitsky. >> >> Thanks, >> Igor >> >> On Wed, Dec 30, 2015 at 2:57 PM, Vitaly Kramskikh >> wrote: &

[openstack-dev] [Fuel] [Nailgun] Deadlocks and random test failures

to affect UI functional tests: cluster reset task may hang <https://bugs.launchpad.net/fuel/+bug/1529613>, so this issue now may affect real deployments. I think we need to do something with it ASAP. -- Vitaly Kramskikh, Fuel UI Tech Lead, Miranti

Re: [openstack-dev] [Fuel] Merge Freeze for cutting stable/8.0 branch

Team Lead > >> bookwar > >> > >> > ______ > >> OpenStack Development Mailing List (not for usage questions) > >> Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:

Re: [openstack-dev] [Fuel] PostgreSQL 9.3 and JSON operations

/listinfo/openstack-dev > >>> >> > >>> > > >>> > > >>> > > ______ > >>> > OpenStack Development Mailing List (not for usage questions) > >>>

Re: [openstack-dev] [Fuel][Ubuntu bootstrap] WebUI notification

> OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [Fuel] [Plugins] Ways to improve plugin links handling in 9.0

think that's possible. > > - Igor > > On Tue, Dec 15, 2015 at 11:53 AM, Vitaly Kramskikh > wrote: > > Hi, > > > > As you may know, in Fuel 8.0 we've implemented blueprint > > external-dashboard-links-in-fuel-dashboard. It will allow plugins to ad

[openstack-dev] [Fuel] [Plugins] Ways to improve plugin links handling in 9.0

r more complex cases plugins will still use the API to create the links manually. -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-de

Re: [openstack-dev] [Fuel] Multiple repos UX

updates and mosX.Y-security are supposed to be available >> online. >> >>>> >> >>>> What do you guys think of that? >> >>>> >> >>>> >> >>>> [0] >> >>>> >> https://github.com

Re: [openstack-dev] [Fuel] Dropping python2.6 compatibility

(AG Nürnberg) > >>>GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > >>> > >>> > >>> > __ > >>> OpenStack Development Mailing List (not for usage questions) > >>> Unsubscribe:

Re: [openstack-dev] [Fuel] Changing APIs and API versioning

u didn't mention (but probably everyone > know about it) > is to solve the issue with fuelclient not beign tested against changes in > nailgun. > We need not only run it for every change in nailgun (or for only those > that touch files under "api" > dir) but also cover m

Re: [openstack-dev] [Fuel] [Fuel UI] Support of separate provisioning is blocked by backend issues

/fuel/+bug/1515893 >> >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [openstack-dev] [Fuel][CI] recheck/reverify support for Fuel CI jobs

gt; up. Restart both tests for this case does not required. > > > /sv > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.opens

[openstack-dev] [Fuel][UI] Fuel UI switched to a new build/module system

incremental compilation, which is usually much faster than gulp build) and triggers refresh in browser. You can run it via gulp dev-server. If you have issues with the new code, feel free to contact us in #fuel-ui or #fuel-dev channels. -- Vitaly Kramskikh

Re: [openstack-dev] [Fuel][Plugins][UX] Component registry

__ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >

Re: [openstack-dev] [Fuel] Bugs status for ui, python and library. And 'area-*' tags.

ld.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.milestone%3Alist=72594&field.tag=are

Re: [openstack-dev] [Fuel] Changing APIs and API versioning

s in the ecosystem. > > > - romcheg > > > > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > ht

Re: [openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

; > 1. Fixing documentation? > 2. bumping API version? > > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > On Wed, Oct 21, 2015 at 3:08 PM, Vitaly Kramskikh > wrote: > >> Hi, >> >> It's yet another time we b

[openstack-dev] [Fuel] [CI] Running fuelclient tests against review requests for fuel-web repo

t to change our CI so it could run tests from another repo against changes in another repo. Can it be done? -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

;> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/ope

[openstack-dev] [Fuel][UI] Bower is gone

development, this change means that you don't need to run "gulp bower" anymore after pulling latest changes, just "npm install" is enough. -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. ___

Re: [openstack-dev] [Fuel] SSL for master node API

_ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >&

Re: [openstack-dev] [fuel] FF Exception for LP-1464656 fix (update ceph PG calculation algorithm)

> OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > _

Re: [openstack-dev] [Fuel] version.yaml in the context of packages

into rpm because it > can only be built together with ISO. > > > [1] > https://github.com/stackforge/fuel-main/blob/master/specs/fuel-main.spec > [2] > https://github.com/stackforge/fuel-web/blob/master/nailgun/nailgun/fixtu

Re: [openstack-dev] [Fuel] Nominating Vladimir Kozhukalov to core reviewers of fuel-main

ubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-req

Re: [openstack-dev] [fuel][plugin] Plugin depends on another plugin

Daniel, Yes, it doesn't work in 6.1 release. My question is: are you OK if we support your case in 7.0 using the approach I described? 2015-07-21 14:13 GMT+03:00 Daniel Depaoli : > > > On Tue, Jul 21, 2015 at 12:02 PM, Vitaly Kramskikh < > vkramsk...@mirantis.com> wrote:

Re: [openstack-dev] [fuel][plugin] Plugin depends on another plugin

gt; > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-

Re: [openstack-dev] [Fuel] Packaged Fuel and "Feature Groups"

uestions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. __ OpenStack Dev

Re: [openstack-dev] [Fuel] interaction between fuel-plugin and fuel-UI

v-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > __ > OpenStack Development Mailing List (not for usage questions) > Unsub

Re: [openstack-dev] [Fuel] Nominate Julia Aranovich for fuel-web core

So, there is no objections and Julia is now a core reviewer for fuel-web. Congratulations! 2015-05-05 16:17 GMT+03:00 Vitaly Kramskikh : > Thanks for voting. If nobody has objections by tomorrow, Julia will get +2 > rights for fuel-web. > > 2015-05-05 15:30 GMT+03:00 Dmitry Pyzh

Re: [openstack-dev] [Fuel] Nominate Julia Aranovich for fuel-web core

< >> skalinow...@mirantis.com> wrote: >> >>> +1 >>> >>> 2015-04-30 11:33 GMT+02:00 Przemyslaw Kaminski : >>> >>>> +1, indeed Julia's reviews are very thorough. >>>> >>>> P. >>>> >>&

[openstack-dev] [Fuel] Nominate Julia Aranovich for fuel-web core

eb repo (mostly for JS/UI stuff). Please vote by replying with +1/-1. -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ.

Re: [openstack-dev] [Fuel] [UI] New design + Bootstrap 3

ge? > > On Mon, Mar 23, 2015 at 10:36 AM, Vitaly Kramskikh > wrote: > > Hi, > > > > We're working on migrating Fuel UI from Bootstrap 2 to Bootstrap 3 and > > changing the design. It's mostly upgrade of styles and markup, but we > also > > plan to

[openstack-dev] [Fuel] [UI] New design + Bootstrap 3

markup for 3 pages: - Environment list <http://94.127.68.84/files/fuel/> - Nodes tab <http://94.127.68.84/files/fuel/nodes.html> - Actions tab <http://94.127.68.84/files/fuel/actions.html> What do you think about the new design? Your feedback is welcome. -- Vitaly

Re: [openstack-dev] [Fuel] Network verification status flag

n/nailgun/api/v1/handlers/network_configuration.py > [3] https://github.com/inveniosoftware/dictdiffer > > P. > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.open

Re: [openstack-dev] [Fuel] [UI] Sorting and filtering of node list

openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. __ OpenStack Development Mailing List (n

Re: [openstack-dev] [Fuel] [nailgun] [UI] network_check_status fleild for environments

om tasks. As you see the logic of > network task verification is not simply based on ready/error status > reading but more subtle. What other settings you have in mind? I guess > when we have more of them one can create a separate table to keep > them, but for now I don't see a point in doing this. > > P. > > > > &

Re: [openstack-dev] [Fuel] [UI] Deploy Changes dialog redesign

mirantis.ru > jaranov...@mirantis.com > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openst

Re: [openstack-dev] [Fuel] [nailgun] [UI] network_check_status fleild for environments

able > to get the latest tasks for specific env. > > Thanks, > > On Thu, Jan 15, 2015 at 7:20 PM, Vitaly Kramskikh > wrote: > >> Folks, >> >> I want to discuss possibility to add network verification status field >> for environments. There are 2 reasons f

[openstack-dev] [Fuel] [Scale] [UI] Improvements to handle 200+ nodes

lter (like one used in Gerrit) 3. Add ability to add arbitrary tags with values to nodes and also allow filtering by them. -- Vitaly Kramskikh, Software Engineer, Mirantis, Inc. __ OpenStack Development Mailing Lis

[openstack-dev] [Fuel] [nailgun] [UI] network_check_status fleild for environments

he UI removes the task. There are a few cases when the UI does this, like changing network settings, adding a new node, etc (you can grep "removeFinishedNetworkTasks" to see all the cases). This definitely should be done on backend. What is your opinion on this? -- Vitaly Kramskikh, So

Re: [openstack-dev] [Fuel] Support of warnings in Fuel UI

file > and add an appropriate messages for restrictions. It will make Fuel UI more > clear and informative. > > Thank you in advance! > > Julia > > -- > Kind Regards, > Julia Aranovich, > Software Engineer, > Mirantis, Inc > +7 (905) 388-82-61 (cell)

Re: [openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

w exactly which plugin with which version >> is used for environment, and I don't see how "conditions" can help >> us with it. >> >> Thanks, >> >>> >>>> >>>> >> On Wed, Dec 10, 2014 at 8:23 PM, Vitaly Kramskikh < &

Re: [openstack-dev] [Fuel] Building Fuel plugins with UI part

nstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> ___ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > ___ > OpenStack-dev mailing > listOpenStack-dev@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly Kramskikh, Software Engineer, Mirantis, Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

2014-12-10 19:31 GMT+03:00 Evgeniy L : > > > On Wed, Dec 10, 2014 at 6:50 PM, Vitaly Kramskikh > wrote: > >> >> >> 2014-12-10 16:57 GMT+03:00 Evgeniy L : >> >>> Hi, >>> >>> First let me describe what our plans for the nearest rel

Re: [openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

for the environment, OS release and then he needs to choose plugins. Really? My proposal for "complex" plugin interface: there should be python classes with exactly the same fields from yaml files: plugin name, version, etc. But condition for cluster deletion and for tasks which are

Re: [openstack-dev] [Fuel][Nailgun]Problems with auto-reloading

rect reloading order > - Enable extention of existing tables in metadata, but I’m not sure what > will be other consequences for that. > > > - romcheg > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.

Re: [openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

ion looks like "Your proposal is wrong and complicated and stuff, but I still don't have my own proposal". So I think it could be a better idea to wait for proposal from Evgeniy and then we'll be able to make a list of pro and contra arguments. > On Nov 28, 2014 9:48 AM, &

Re: [openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

unique, etc), but complex is easier to test and describe in python. > Could you please provide example of such conditions? vCenter and Ceph can be turned into plugins using this approach. Also, I'm not against python version of plugins. It could look like a python class with exactly the same fields form YAML

Re: [openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

t" stuff. >> >>> >>> As result in simple cases plugin developer will have to specify the same >>> condition of every task in tasks.yaml file, add it to metadata.yaml. >>> If you add new checkbox, you should go through all of this files, >>>

Re: [openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

ot;and lbaas:new_checkbox_name" statement. > Once again, in simple cases checkbox and the conditions (one for task and one for is_removable) can be easily pregenerated by FPB, so plugin developer has to do nothing more. If you add a new checkbox which doesn't affect plugin removeabilit

[openstack-dev] [Fuel] [Plugins] Further development of plugin metadata format

orage.volumes_vmdk.value == true". Also, AFAIU, similar approach will be used in implementation of Granular Deployment feature. These simple changes will allow to write much more complex plugins. What do you think? -- Vitaly Kramskikh, Software Engineer, Mirantis, Inc. ___

Re: [openstack-dev] [Fuel] Separate code freeze for repos

but we have to define > some rules how to define that fuel-web is stable. I mean, in fuel-web > we have different projects, so when Fuel UI is stable, the > fuel_upgrade or Nailgun may be not. > > - Igor > > On Fri, Nov 14, 2014 at 3:52 PM, Vitaly Kramskikh > wrote: > >

Re: [openstack-dev] [Fuel] Separate code freeze for repos

x27;s code freeze for the current. > > Thanks, > > On Tue, Nov 11, 2014 at 2:16 PM, Vitaly Kramskikh > wrote: > >> Folks, >> >> There was an idea to make a separate code freeze for repos, but we >> decided not to do it. Do we plan to try it this time? It is rea

[openstack-dev] [Fuel] Separate code freeze for repos

Folks, There was an idea to make a separate code freeze for repos, but we decided not to do it. Do we plan to try it this time? It is really painful to maintain multi-level tree of dependent review requests and wait for a few weeks until we can merge new stuff in master. -- Vitaly Kramskikh

Re: [openstack-dev] [Fuel] fuel-library merge policy and Fuel CI

neer to deal with the test failures if they appear. > > > > [1] > http://www.youtube.com/watch?feature=player_embedded&v=QkCQ_-Id8zI#t=211 > > > -- > Aleksandra Fedorova > Fuel Devops Engineer > bookwar > > -- > Yo

Re: [openstack-dev] [Fuel] Pluggable framework in Fuel: first prototype ready

ion? >>> - What happens if an error occurs during plugin execution? Does >>> it (should it?) fail the deployment? Will we show user an error >>> message >>> with the name of plugin that failed? >>>

Re: [openstack-dev] [Fuel] Propose adding Igor K. to core reviewers for fuel-web projects

> OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly Kramskikh, Software Engineer, Mirantis, Inc. ___ OpenStack-dev maili

Re: [openstack-dev] [Fuel] Proposing Bogdan Dobrelia and Sergii Golovatiuk as core-reviewers for Fuel Library project

40-49-04 > +7 (926) 702-39-68 > Skype kuklinvv > 45bk3, Vorontsovskaya Str. > Moscow, Russia, > www.mirantis.com <http://www.mirantis.ru/> > www.mirantis.ru > vkuk...@mirantis.com > > ___ > OpenStack-dev mailing list &g

Re: [openstack-dev] [Fuel] Cinder/Neutron plugins on UI

enable plugins by default, user should > enable plugin if he wants > it to be installed. > > Thanks, > > On Thu, Oct 9, 2014 at 3:34 PM, Vitaly Kramskikh > wrote: > >> Let me propose another approach. I agree with most of Dmitry's statements >> and it seems in M

Re: [openstack-dev] [Fuel] Cinder/Neutron plugins on UI

interface to: > > 1) Write this command in some YAML and don't care about anything else > > 2) Enable my plugin for particular environment and see if it's really > > enabled both on UI and CLI (and through pure API by simple field > checking) > > > > If it

Re: [openstack-dev] [Fuel] Cinder/Neutron plugins on UI

n developer > > If plugin is set, we add env <-> plugin relation, if it's unset, we > delete it. > Also when user checks the checkbox, UI will be able to retrieve > attributes which plugin provides. But it's not so easy todo, I'm not > sure if we can do it with h

Re: [openstack-dev] [Fuel] Cinder/Neutron plugins on UI

o is installing a package and modify a couple of config files > (run a shell command). > These ones have nothing to do with UI or any checkboxes, aren't they? > 08 Окт 2014 г. 12:49 пользователь "Vitaly Kramskikh" < > vkramsk...@mirantis.com> написал: > > Nikol

Re: [openstack-dev] [Fuel] Cinder/Neutron plugins on UI

it > >> won't)? How should we determine in serializer, which plugins should be > >> applied while generating astute.yaml and tasks.yaml? Should we > >> autogenerate some stuff for plugins which are not even enabled and do > >> needless work? > >> > >&g

Re: [openstack-dev] [Fuel] Cinder/Neutron plugins on UI

un tasks on slaves if it's not required > > Thanks, > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Vitaly Kramskikh, Software Engineer, Mirantis, Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] [OSTF] OSTF stops working after password is changed

p text fields to enter > tenant/user/pass with the message similar to "Default administrative > credentials to OpenStack were changed since the deployment time. Please > provide current credentials so HealthCheck can access OpenStack and run > verification tests." > > I

Re: [openstack-dev] [Fuel] [OSTF] OSTF stops working after password is changed

00 Dmitriy Shulyak : > It is possible to change everything so username, password and tenant fields > > Also this way we will be able to run tests not only as admin user > > > On Wed, Jun 25, 2014 at 12:29 PM, Vitaly Kramskikh < > vkramsk...@mirantis.com> wrote: > >>

Re: [openstack-dev] [Fuel] [OSTF] OSTF stops working after password is changed

place. >> >> >> >> >> >> On Fri, Jun 20, 2014 at 2:01 AM, Mike Scherbakov >> >> wrote: >> >>> >> >>> I'm in favor of #2. I think users might not want to have their >> password >> >>> stored in Fuel Mas

[openstack-dev] [Fuel] [OSTF] OSTF stops working after password is changed

r OSTF during OpenStack installation 2. Provide a field for a password in UI so user could provide actual password in case it was changed What do you guys think? Which options is better? -- Vitaly Kramskikh, Software Engineer, Mirantis, Inc. ___ Ope

Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management section - Wireframes

ontroller. Is it possible to do this? -- Vitaly Kramskikh, Software Engineer, Mirantis, Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] [i18n] Internationalization of Fuel 4.0 UI

Folks, We are glad to announce that we've finished internationalization of Fuel UI and now it can be easily localized. This is an example of environment network settings tab localized to Chinese: [image: Встроенное изображение 2] These changes are available in