Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

2016-05-12 Thread Anton Zemlyanov
Hi, I have a question on js-openstacklib. If it is intended for browsers, there will be lots of issues with cross-domain security policy, browser cannot just go to any REST resource it wants. There is either some server-side proxy required or cooperation of the all the REST services we want to

Re: [openstack-dev] [infra] [fuel] [javascript] Supporting ES6

2016-05-11 Thread Anton Zemlyanov
ES6 is risk-free solution. Browsers do not support it properly, but it is not a problem. ES6 code can be compiled to ES5 and be used in browsers until proper ES6 support appear. Fuel uses Babel (https://babeljs.io/) to compile ES6 to ES5. Node 6.x supports it almost completely. Anton On Tue, May

Re: [openstack-dev] [horizon][keystone] SSO

2015-02-09 Thread Anton Zemlyanov
SSO (Single sign-on) is great. There are some problems, though: 1) If the cloud is private without Internet access, then a private SSO service should be up and runnning 2) There is no such a thing as OpenStack ID. Should we use Launchpad? Facebook login? Twitter? 3) Technical difficulties

Re: [openstack-dev] [horizon][keystone]

2015-02-05 Thread Anton Zemlyanov
Hi, I guess Credentials is login and password. I have no idea what is Default Protocol or Discovery Service. The proposed UI is rather embarrassing. Anton On Thu, Feb 5, 2015 at 12:54 AM, Thai Q Tran tqt...@us.ibm.com wrote: Hi all, I have been helping with the websso effort and wanted to

Re: [openstack-dev] [horizon] static files handling, bower/

2015-01-14 Thread Anton Zemlyanov
Solaris is supported by node.js: Solaris 32-bit Binary: http://nodejs.org/dist/v0.10.35/node-v0.10.35-sunos-x86.tar.gz Solaris 64-bit Binary: http://nodejs.org/dist/v0.10.35/node-v0.10.35-sunos-x64.tar.gz I think Solaris is no longer relevant On Tue, Jan 13, 2015 at 7:13 PM, Drew Fisher

Re: [openstack-dev] [Fuel] update existing plugin and add new ones

2015-01-12 Thread Anton Zemlyanov
There was a discussion on whether to put all the fuel plugins into the single repository or have them separate. The problems with all the fuel plugins in single repository are following: - it is impossible to make a branch on a single plugin, branch is applied to the whole repository and all the

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

2014-12-15 Thread Anton Zemlyanov
My experience with building Fuel plugins with UI part is following. To build a ui-less plugin, it takes 3 seconds and those commands: git clone https://github.com/AlgoTrader/test-plugin.git cd ./test-plugin fpb --build ./ When UI added, build start to look like this and takes many minutes: git

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

2014-12-15 Thread Anton Zemlyanov
build 2^N files with all possible combinations of including the plugins? :) P. On 12/15/2014 11:35 AM, Anton Zemlyanov wrote: My experience with building Fuel plugins with UI part is following. To build a ui-less plugin, it takes 3 seconds and those commands: git clone https

Re: [openstack-dev] [horizon] [ux] Changing how the modals are closed in Horizon

2014-12-03 Thread Anton Zemlyanov
The confirmation modal on the top of the other modal is weird and cumbersome. I think disabling clicking outside space (staic backdrop) is the right way to go. Anton On Tue, Dec 2, 2014 at 8:30 PM, Thai Q Tran tqt...@us.ibm.com wrote: I like David's approach, but having two modals (one for the

Re: [openstack-dev] URLs

2014-11-12 Thread Anton Zemlyanov
For the REST API to be visible from browser it should either be on the same domain and port or it should implement CORS spec (Cross-site HTTP requests, https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS). If REST API implements CORS, then every HTTP request will be preceded

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

2014-11-11 Thread Anton Zemlyanov
Modernizing Horizon using Angular is really great. I would suggest a couple of minor things to consider. First, font-awesome is excellent and free font, but there are two problems: it has lots of icons that are not used, it also miss some other icons worth to have. I would suggest Fontello, it is

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

2014-11-06 Thread Anton Zemlyanov
node failures by restoring it from backups. On Wed, Nov 5, 2014 at 8:26 AM, Anton Zemlyanov azemlya...@mirantis.com wrote: Monitoring of the Fuel master's disk space is the special case. I really wonder why Fuel master have no HA option, disk overflow can be predicted but many other

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

2014-11-05 Thread Anton Zemlyanov
Monitoring of the Fuel master's disk space is the special case. I really wonder why Fuel master have no HA option, disk overflow can be predicted but many other failures cannot. HA is a solution of the 'single point of failure' problem. The current monitoring recommendations (

Re: [openstack-dev] [Fuel] Fuel standards

2014-10-23 Thread Anton Zemlyanov
idea, REPL can be separated from command execution logic. Multiple simple components are usually easier to maintain, bigger components tend to become complex and tightly coupled. I also fully support standards of naming files and directories, although it relates to Python stuff mostly. Anton