[openstack-dev] [ironic] some notes on ironic functional testing

2014-01-14 Thread Alexander Gordeev
Hello, We (agordeev and vkozhukalov) had a discussion about functional testing flow described here https://etherpad.openstack.org/p/IronicDevstackTesting.From our perspective it has some non-critical, but still notable flaws. If you ask me, it looks a bit strange to create testing networks and

Re: [openstack-dev] [ironic] [QA] some notes on ironic functional testing

2014-01-15 Thread Alexander Gordeev
Hi, Devananda On Wed, Jan 15, 2014 at 8:19 AM, Devananda van der Veen devananda@gmail.com wrote: On Tue, Jan 14, 2014 at 6:28 AM, Alexander Gordeev agord...@mirantis.comwrote: - Secondly, virsh has some performance issues if you deal with 30 VMs (it is not our case for now

Re: [openstack-dev] [Ironic][Nova] Functional testing of Nova Ironic driver

2014-03-24 Thread Alexander Gordeev
Hi, https://etherpad.openstack.org/p/IronicAndDevstackAgain might help you. Should flawlessly work on Ubuntu 12.04. Latest devstack creates baremetal flavor by itself, so you don't need to create it manually. Let me know if you need any additional help. Or it could be better to ask in IRC

Re: [openstack-dev] [ironic] How to use ironic-python-agent ?

2014-04-21 Thread Alexander Gordeev
Hi, You may want to take a look at: https://github.com/openstack/ironic-python-agent/blob/master/imagebuild/coreos/README.md https://github.com/openstack/ironic-python-agent/blob/master/imagebuild/coreos/oem/run.sh#L5-L10 It uses its own build scripts and builds image based on coreos

Re: [openstack-dev] [Fuel][Agent] Moving Fuel Agent to a separate repo

2015-01-26 Thread Alexander Gordeev
Hello Vladimir, totally +1 for separating Fuel Agent out of fuel-web. what will happen with fuel_agent_ci ? On Mon, Jan 26, 2015 at 7:42 PM, Vladimir Kozhukalov vkozhuka...@mirantis.com wrote: Fuelers, As most of you might know we have a bunch of projects inside fuel-web repo which are not

Re: [openstack-dev] [Fuel] Image based provisioning

2015-01-12 Thread Alexander Gordeev
Hello, Andrew, thank you for pointing out all the issues. I left more detailed comments inlined On Tue, Jan 6, 2015 at 3:51 AM, Andrew Woodward xar...@gmail.com wrote: Here is a list of the issues I ran into using IBP before the 23rd. 5 appears to not be merged yet and must be resolved prior

Re: [openstack-dev] [Fuel] Image based provisioning

2015-01-12 Thread Alexander Gordeev
On Tue, Dec 16, 2014 at 11:09 PM, Andrey Danin ada...@mirantis.com wrote: Adding Mellanox team explicitly. Gil, Nurit, Aviram, can you confirm that you tested that feature? It can be enabled on every fresh ISO. You just need to enable the Experimental mode (please, see the documentation for

[openstack-dev] [Fuel] FFE backport IBP-reconnect to 6.0

2015-03-20 Thread Alexander Gordeev
Hello Fuelers, I'm kindly insisting on merging the following 2 patches into 6.0 [1] https://review.openstack.org/#/c/161721/ [2] https://review.openstack.org/#/c/161722/ These patches are going to implement IBP-reconnect [3]. Additionally, it closes one of customer-found bug [4] related to

[openstack-dev] [fuel][shotgun] do we still use subs?

2015-09-30 Thread Alexander Gordeev
Hello fuelers, My question is related to shotgun tool[1] which will be invoked in order to generate the diagnostic snapshot. It has possibilities to substitute particular sensitive data such as credentials/hostnames/IPs/etc with meaningless values. It's done by Subs [2] object driver. However,

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

2015-09-21 Thread Alexander Gordeev
Hi, Mike, fuel-agent is missing here too. http://stackalytics.com/report/contribution/fuel-agent/180 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [fuel][nailgun][volume-manager][fuel-agent] lvm metadata size value. why was it set to 64M?

2016-02-17 Thread Alexander Gordeev
Hi, Apparently, nailgun assumes that lvm metadata size is always set to 64M [1] It seems that it was defined here since the early beginning of nailgun as a project, therefore it's impossible to figure out for what purposes that was done as early commit messages are not so informative. According

Re: [openstack-dev] [Fuel] Wiping node's disks on delete

2016-03-24 Thread Alexander Gordeev
On Wed, Mar 23, 2016 at 7:49 PM, Dmitry Guryanov wrote: > > I have no objections against clearing bios boot partition, but could > you describe scenario, how non-efi system will boot with valid > BIOS_grub and wiped boot code in MBR > I thoroughly agree that it's

Re: [openstack-dev] [Fuel] Wiping node's disks on delete

2016-03-23 Thread Alexander Gordeev
Hello Dmitry, First of all, thanks for recovering the thread. Please read my comments inline. On Tue, Mar 22, 2016 at 1:07 PM, Dmitry Guryanov wrote: > > The first problem could be solved with zeroing first 512 bytes of each > disk (not partition). Even 446 to be