Re: [openstack-dev] [Fuel] Common fuel-core group for all Fuel projects

On Mon, Sep 5, 2016 at 5:39 PM, Andrew Maksimov wrote: > +1 > This is a good proposal, I also think we should have single fuel-core group > for all repos. In real life core reviewers won't set +2 or merge to repos > with which they are not familiar with. Actually one of

Re: [openstack-dev] [Fuel][UX] Throw KVM\QEMU and leave Libvirt on Wizard

On Mon, Dec 21, 2015 at 1:43 PM, Igor Kalnitsky wrote: > What about hypervisor "Qemu", and checkbox option on Settings tab - > "Use KVM extension"? Qemu is not a hypervisor This will be even more confusing. I think "Libvirt" + some tooltip which says "Qemu and KVM" will

Re: [openstack-dev] [Fuel][Solar] SolarDB/ConfigDB place in Fuel

Hi Dima, On Wed, Dec 16, 2015 at 12:03 AM, Dmitriy Shulyak wrote: > Hello folks, > > This topic is about configuration storage which will connect data sources > (nailgun/bareon/others) and orchestration. And right now we are developing > two projects that will overlap a

Re: [openstack-dev] [Fuel][MOS][Bootstrap] Please try Ubuntu bootstrap in MOS 7.0

-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 lo...@mirantis.com

Re: [openstack-dev] [Fuel][MOS][Bootstrap] Please try Ubuntu bootstrap in MOS 7.0

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.

Re: [openstack-dev] [Fuel] Transaction scheme

On Wed, May 6, 2015 at 10:51 AM, Alexander Kislitsky akislit...@mirantis.com wrote: Hi! The refactoring of transactions management in Nailgun is critically required for scaling. First of all I propose to wrap HTTP handlers by begin/commit/rollback decorator. After that we should introduce

Re: [openstack-dev] [Fuel] Nominate Irina Povolotskaya for fuel-docs core

+1 On Wed, Mar 25, 2015 at 8:10 PM, Dmitry Borodaenko dborodae...@mirantis.com wrote: Fuelers, I'd like to nominate Irina Povolotskaya for the fuel-docs-core team. She has contributed thousands of lines of documentation to Fuel over the past several months, and has been a diligent reviewer:

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

Hello Julia, I think node filtering and sorting is a great feature and it will improve UX, but we need to remember that with increasing number of nodes increases number of automation tasks. If fuel user want to automate something he will use fuel client not Fuel GUI. This is why I think sorting

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

Big +1, it would save me a lot of debugging time :) On Thu, Jan 15, 2015 at 5:20 PM, Vitaly Kramskikh vkramsk...@mirantis.com wrote: Folks, I want to discuss possibility to add network verification status field for environments. There are 2 reasons for this: 1) One of the most frequent

Re: [openstack-dev] [Fuel] fuel master monitoring

+1 also. There are so many monitoring tools, but maybe not something written in ruby ;) On Thu, Nov 20, 2014 at 10:40 PM, Igor Kalnitsky ikalnit...@mirantis.com wrote: +1 for Dima's suggestion. We need to stop reinventing the wheel. There are a lot tools around us, so let's pick one of them and

Re: [openstack-dev] [Fuel] fuel master monitoring

On Thu, Nov 20, 2014 at 11:28 PM, Sergii Golovatiuk sgolovat...@mirantis.com wrote: I would rather compare features than ruby vs python. It make sense only as long as you don't need to debug it Best Regards, Sergii Golovatiuk On 20 Nov 2014, at 23:20, Lukasz Oles lo...@mirantis.com wrote

[openstack-dev] [Fuel] [Rally] Using fuelclient as a library - battle report

Hello all, I'm researching if we can use Rally project for some Fuel testing. It's part of 100-nodes blueprint[1]. To write some Rally scenario I used our Fuelclient library. In it's current state it's really painful to use and it's not usable as production tool. Here is the list of the biggest

[openstack-dev] [Fuel] master access control - future work

Dear Fuelers, I have some ideas and questions to share regarding Fuel Master access control. During 5,1 cycle we made some non optimal decision which we have to fix. The following blueprint describes required changes:

Re: [openstack-dev] [Fuel] Authentication is turned on - Fuel API and UI

On Mon, Jul 28, 2014 at 6:37 PM, Lukasz Oles lo...@mirantis.com wrote: As I said in another topic, storing user password in plain text is not an option. Ad. 1. We can create special upgrade_user with the same rights as admin user. We can use it to authenticate in nailgun. It can be done

Re: [openstack-dev] [Fuel] Authentication is turned on - Fuel API and UI

warning in the documentation. [1] https://github.com/stackforge/fuel-library/blob/705dc089037757ed8c5a25c4cf78df71f9bd33b0/deployment/puppet/nailgun/examples/host-only.pp#L51-L55 On Thu, Jul 24, 2014 at 6:17 PM, Lukasz Oles lo...@mirantis.com wrote: Hi all, one more thing. You do not need

Re: [openstack-dev] [Fuel] Authentication is turned on - Fuel API and UI

Hi all, one more thing. You do not need to install keystone in your development environment. By default it runs there in fake mode. Keystone mode is enabled only on iso. If you want to test it locally you have to install keystone and configure nailgun as Kamil explained. Regards, On Thu, Jul

Re: [openstack-dev] [Fuel-dev] access-control-master-node

OAuth as an additional authentication entry would awesome too, but I'm not sure if there would be much demand over Keystone. On Tue, May 27, 2014 at 8:31 AM, Lukasz Oles lo...@mirantis.com wrote: There is some misunderstanding here. By using keystone I mean running keystone on fuel master node

Re: [openstack-dev] [FUEL][Design session 5.1] 28/05/2014 meeting minutes

june 5th? On Fri, May 30, 2014 at 4:33 PM, Vladimir Kuklin vkuk...@mirantis.com wrote: Guys, we gonna have a more extended design FUEL Library design meeting in IRC channel during regular FUEL Meeting on May 5th. So, feel free to add blueprints to meeting agenda and we will consider adding

[openstack-dev] [Fuel-dev] access-control-master-node

Hello fuelers, we(I and Kamil) would like start discussion about Enforce access control for Fuel UI blueprint https://blueprints.launchpad.net/fuel/+spec/access-control-master-node. First question to David, as he proposed this bp. Do you want to add more requirements? To all. What do you think

Re: [openstack-dev] [Fuel-dev] access-control-master-node

] access-control-master-node On 27 May 2014 13:42, Lukasz Oles lo...@mirantis.com wrote: Hello fuelers, we(I and Kamil) would like start discussion about Enforce access control for Fuel UI blueprint https://blueprints.launchpad.net/fuel/+spec/access-control-master-node. First question to David