Re: [openstack-dev] [Fuel] Testing before switching to upstream librarian

2015-10-20 Thread Sergii Golovatiuk
Hi, On Mon, Oct 19, 2015 at 10:46 PM, Sergey Kolekonov wrote: > Hi, > > I agree with Ivan. Getting rid of forks and moving to puppet-librarian is > complicated work and such problems are nearly unavoidable. It's hard to > cover all possible corner cases with regular tests. > This case shows the

Re: [openstack-dev] [Fuel][Fuel-Modularization] Proposal on Decoupling Serializers from Nailgun

2015-10-20 Thread Evgeniy L
Hi, I have a comment regarding to when/where run translators. I think data processing (fetching + validation + translation) should be done as a separate stage, this way when we start deployment, we are sure that we have everything we need to perform deployment, but I understand that there might be

Re: [openstack-dev] [Fuel] Testing before switching to upstream librarian

2015-10-20 Thread Sergii Golovatiuk
Ivan, BVT is not source of truth. BVT handles couple of scenarios from hundreds. You should rely on swarm test and get parity in % of failed tests. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Mon, Oct 19, 2015 at 9:10 PM, Ivan Berezovskiy wrote: > Hi, > > First of all, I

[openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

2015-10-20 Thread Qiming Teng
Hi, Just encountered this again in code review [1]. The question is about the repository to point to when documenting things up. Between the following links, which one should we use? - https://git.openstack.org/cgit/openstack/sqlalchemy-migrate - https://github.com/openstack/sqlalchemy-migrate I

[openstack-dev] [Magnum] Coe components status

2015-10-20 Thread Vikas Choudhary
Hi Team, I would appreciate any opinion/concern regarding "coe-component-status" feature implementation [1]. For example in k8s, using API api/v1/namespaces/{namespace}/componentstatuses, status of each k8s component can be queried. My approach would be to provide a command in magnum like "magnum

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

2015-10-20 Thread Lingxian Kong
Or, feel free to join our IRC channel for quick response, #openstack-mistral On Tue, Oct 20, 2015 at 4:58 PM, WANG, Ming Hao (Tony T) wrote: > Renat, > > > > Another question is: > > If I use custom action to run Ansible, the Ansible playbook should be stored > on the same server of Mistral. Is i

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

2015-10-20 Thread Lingxian Kong
Hi, Minghao, The answer is yes, if you want to use Ansible playbook in you customized 'ansible actions', you need put the playbooks under a place that your code has access to. BTW, you can send personal email to me in Chinese, in case you want to solve your problems quickly :-) On Tue, Oct 20, 2

Re: [openstack-dev] [Fuel] Assigning VIPs on network config serialization

2015-10-20 Thread Roman Prykhodchenko
My concern here is that there is also a Network check feature that according to its name should check things like whether or not there’s enough IP addresses in all ranges in a network. The problem is that it may be run at any time, even when VIPs are not yet allocated. From a user-side the workf

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

2015-10-20 Thread Matthew Mosesohn
Hi Patrick, During the 7.0 development cycle we made a lot of enhancements to what environment characteristics can be modified through a plugin. One item that plugins cannot directly modify is the default Fuel roles and their metadata. That having been said, there is an open-ended post_install.sh

Re: [openstack-dev] [Fuel] Modularization activity POC

2015-10-20 Thread Evgeniy L
Hi Mike, 1. our plan is to have working partitioning/provisioning in a couple of weeks, networking is more complicated and it's better to ask Vladimir/Ryan. 2, 3. here we have just some general ideas, we should have independent releases on pypi, each component should have responsible perso

Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests from fuel-qa to the plugins

2015-10-20 Thread Simon Pasquier
Thanks for the reply, Andrew! I must admit that I haven't read thoroughly the specification on the new team structure [1]. IIUC plugin developers should be added to the MAINTAINERS file of fuel-qa for the directories that concern their plugins. If I take LMA as an example, this would be: fuelweb_te

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

2015-10-20 Thread WANG, Ming Hao (Tony T)
Renat, Another question is: If I use custom action to run Ansible, the Ansible playbook should be stored on the same server of Mistral. Is it right? Thanks, Tony From: Renat Akhmerov [mailto:rakhme...@mirantis.com] Sent: Monday, October 19, 2015 2:58 PM To: OpenStack Development Mailing List (n

[openstack-dev] [neutron][client] collecting opinions on neutronclient options

2015-10-20 Thread Akihiro Motoki
Hi team, Recently there are many patches to add help messages to neutron *-update sub-commands (or others). I made similar comments and discussions repeatedly in various reviews. I created a etherpad page [1] to dicsuss neutronclient options Once we collect opinions and have a consensus, I will

Re: [openstack-dev] [Fuel][Plugins][Ironic] Deploy Ironic with fuel ?

2015-10-20 Thread Aleksey Kasatkin
+ Pavlo, Andrey. Aleksey Kasatkin On Mon, Oct 19, 2015 at 6:45 AM, wrote: > Hello, > > > > I’m currently searching for information about Ironic Fuel plugin : > https://github.com/openstack/fuel-plugin-ironic I don’t find any > documentation on it. > > > > I’ve tried to install and deploy an O

<    1   2