Re: [openstack-dev] [Ceilometer]:Duplicate messages with Ceilometer Kafka Publisher.

Hi Which version of Kafka do you use? BR Simon On Thu, Aug 11, 2016 at 10:13 AM, Raghunath D wrote: > Hi , > > We are injecting events to our custom plugin in ceilometer. > The ceilometer pipeline.yaml is configured to publish these events over > kafka and udp,

Re: [openstack-dev] [Fuel] [Plugins] Netconfig tasks changes

Hi Adam, Maybe you want to look into network templates [1]? Although the documentation is a bit sparse, it allows you to define flexible network mappings. BR, Simon [1] https://docs.mirantis.com/openstack/fuel/fuel-8.0/operations.html#using-networking-templates On Wed, May 25, 2016 at 10:26 AM,

[openstack-dev] [Fuel][Plugins] custom roles need to configure the default gateway

Hello, This is a heads-up for the plugin developers because we found this issue [1] with the StackLight plugins. If your plugin targets MOS 8 and provides custom roles, you probably want to call the 'configure_default_route' task otherwise the nodes will use the Fuel node as the default gateway

Re: [openstack-dev] [osops-tools-monitoring][monitoring-for-openstack] Code duplication

Hello, You can find the rationale in the review [1] importing m.o.f. into o.t.m. Basically it was asked by the operators community to avoid the sprawl of repositories. BR, Simon [1] https://review.openstack.org/#/c/248352/ On Fri, May 20, 2016 at 11:08 AM, Martin Magr wrote: >

Re: [openstack-dev] [Fuel][Plugins] Tasks ordering between plugins

d Newton releases, the task graph now skips dependencies > that are not found for the role being processed. Now this "requires" > dependency will work that previously errored. > Good to know! Simon > > Best Regards, > Matthew Mosesohn > > On Tue, May 17, 201

Re: [openstack-dev] [Fuel][Plugins] Tasks ordering between plugins

ake any destructive actions early, that breaks > you later. Anchors is good way to resolve possible conflicts, but they > aren't bulletproof. > > - igor > > On Thu, Jan 28, 2016 at 1:31 PM, Bogdan Dobrelya <bdobre...@mirantis.com> > wrote: > > On 27.01.2016 14:44, Simon P

Re: [openstack-dev] [fuel][plugins][lma] Leveraging OpenStack logstash grok filters in StackLight?

The short answer is no. StackLight is based on Heka for log processing and parsing. Heka itself uses Lua Parsing Expression Grammars [1]. For now the patterns are maintained in the LMA collector repository [2] but it's on our to-do list to have it available in a dedicated repo. One advantage of

Re: [openstack-dev] [fuel] switch to upstream haproxy module

On Thu, May 12, 2016 at 6:13 PM, Alex Schultz <aschu...@mirantis.com> wrote: > > > On Thu, May 12, 2016 at 10:00 AM, Simon Pasquier <spasqu...@mirantis.com> > wrote: > >> First of all, I'm +1 on this. But as Matt says, it needs to take care of >>

Re: [openstack-dev] [fuel] switch to upstream haproxy module

First of all, I'm +1 on this. But as Matt says, it needs to take care of the plugins. A few examples I know of are the Zabbix plugin [1] and the LMA collector plugin [2] that modify the HAProxy configuration of the controller nodes. How could they work with your patch? Simon [1]

Re: [openstack-dev] [Fuel][plugins] Changing role regex from '*' to ['/.*/'] breaks MOS compatibility

Thanks Ilya! We're testing and will be reporting back on monday. Simon On Fri, Apr 22, 2016 at 4:53 PM, Ilya Kutukov wrote: > Hello! > > I think your problem is related to the: > https://bugs.launchpad.net/fuel/+bug/1570846 > > Fix to stable/mitaka was commited 20/04/2016

Re: [openstack-dev] [Fuel][plugins] VIP addresses and network templates

influxdb_vip: br-mon > ... > ... > > > I hope, this helps. > > Regards, > > > > Aleksey Kasatkin > > > On Wed, Apr 20, 2016 at 12:16 PM, Simon Pasquier <spasqu...@mirantis.com> > wrote: > >> Hi, >> I've got a que

[openstack-dev] [Fuel][plugins] VIP addresses and network templates

Hi, I've got a question regarding network templates and VIP. Some of our users want to run the StackLight services (eg Elasticsearch/Kibana and InfluxDB/Grafana servers) on a dedicated network (lets call it 'monitoring'). People use network templates [0] to provision this additional network but

Re: [openstack-dev] [Fuel] Compatibility of fuel plugins and fuel versions

Thanks for kicking off the discussion! On Thu, Mar 10, 2016 at 8:30 AM, Mike Scherbakov wrote: > Hi folks, > in order to make a decision whether we need to support example plugins, > and if actually need them [1], I'd suggest to discuss more common things > about

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

Hello Roman, On Fri, Mar 11, 2016 at 9:57 AM, Roman Prykhodchenko wrote: > Fuelers, > > I remember we’ve discussing this topic in our couloirs before but I’d like > to bring that discussion to a more official format. > > Let me state a few reasons to do this: > > - Log

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

PM, Simon Pasquier <spasqu...@mirantis.com> wrote: > What about maintaining a dummy plugin (eg running only one or two very > simple tasks) as a standalone project for the purpose of QA? > IMO it would make more sense than having those example plugins in the > fuel-plugins pr

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

What about maintaining a dummy plugin (eg running only one or two very simple tasks) as a standalone project for the purpose of QA? IMO it would make more sense than having those example plugins in the fuel-plugins project... Regards, Simon On Mon, Mar 7, 2016 at 2:49 PM, Igor Kalnitsky

Re: [openstack-dev] [fuel][plugins][lma]

Hello Shubham, In the coming version of LMA (0.9), we've already ensured that the the Puppet modules configuring the different components of the LMA toolchain can be used without Fuel and we're in the process of documenting all of them as well as how they can be used outside of Fuel. Eventually it

Re: [openstack-dev] [Fuel][Plugins] Multi release packages

Hi, On Thu, Feb 11, 2016 at 11:46 AM, Igor Kalnitsky wrote: > Hey folks, > > The original idea is to provide a way to build plugin that are > compatible with few releases. It makes sense to me, cause it looks > awful if you need to maintain different branches for

[openstack-dev] [Fuel][Plugins] question on the is_hotpluggable feature

Hi, I'm testing the ability to install Fuel plugins in a an environment that is already deployed. My starting environment is quite simple: 1 controller + 1 compute. After the initial deployment, I've installed the 4 LMA plugins: - LMA collector - Elasticsearch-Kibana [*] - InfluxDB-Grafana [*] -

Re: [openstack-dev] [Fuel][Plugins] question on the is_hotpluggable feature

heir roles. AFAIK update_required doesn't support '*'. > > Thanks, > > [1] > https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/fixtures/openstack.yaml#L16-L18 > > On Fri, Feb 5, 2016 at 12:53 PM, Simon Pasquier <spasqu...@mirantis.com> > wrote:

Re: [openstack-dev] [Fuel][Plugins] question on the is_hotpluggable feature

gt; wrote: > > Simon, > > > >>> Any plan to have a nicer experience in future Fuel releases? > > > > I haven't heard about any plans on improvements for that, but management > > team should know better whether it's on roadmap or not. > > > > Thank

Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

nt a StatsD writer using the collectd Python plugin. Simon [1] https://collectd.org/documentation/manpages/collectd-python.5.shtml > > > Regards, > > Emma > > > > > > *From:* Simon Pasquier [mailto:spasqu...@mirantis.com] > *Sent:* Monday, February 1, 2016 9:0

Re: [openstack-dev] [telemetry][ceilometer] New project: collectd-ceilometer-plugin

On Fri, Jan 29, 2016 at 6:30 PM, Julien Danjou wrote: > On Fri, Jan 29 2016, Foley, Emma L wrote: > > > Supporting statsd would require some more investigation, as collectd's > > statsd plugin supports reading stats from the system, but not writing > > them. > > I'm not sure

Re: [openstack-dev] [Fuel][Plugins] Tasks ordering between plugins

> other plugin didn't make any destructive actions early, that breaks > you later. Anchors is good way to resolve possible conflicts, but they > aren't bulletproof. > > - igor > > On Thu, Jan 28, 2016 at 1:31 PM, Bogdan Dobrelya <bdobre...@mirantis.com> > wrote: > &g

Re: [openstack-dev] [fuel][plugins] Detached components plugin update requirement

I see no follow-up to Swann's question so let me elaborate why this issue is important for the LMA plugins. First I need to explain what was our release schedule for the LMA plugins during the MOS 7.0 cycle: - New features were done on the master branch which was only compatible with MOS 7.0. -

[openstack-dev] [Fuel][Plugins] Tasks ordering between plugins

Hi, I see that tasks.yaml is going to be deprecated in the future MOS versions [1]. I've got one question regarding the ordering of tasks between different plugins. With tasks.yaml, it was possible to coordinate the execution of tasks between plugins without prior knowledge of which plugins were

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

Hi all, In the scope of the LMA plugins, we've played with the new ability to insert links in the Fuel dashboard. This works fine from the UI standpoint except that to avoid creating duplicate links we've come up with a solution that is intricate and brittle IMO. Basically we have an exec

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

My 2 cents on RabbitMQ logging... On Fri, Jan 15, 2016 at 8:39 AM, Michal Rostecki wrote: I'd suggest to check the similar options in RabbitMQ and other > non-OpenStack components. > AFAICT RabbitMQ can't log to Syslog anyway. But you have option to make RabbitMQ log to

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

Hello Alicja, Comments inline. On Tue, Jan 12, 2016 at 1:19 PM, Kwasniewska, Alicja < alicja.kwasniew...@intel.com> wrote: > Unfortunately I do not have any experience in working or testing Heka, so > it’s hard for me to compare its performance vs Logstash performance. > However I’ve read that

Re: [openstack-dev] [fuel] Using upstream packages & modules

Hello Alex! On Mon, Nov 9, 2015 at 9:29 PM, Alex Schultz wrote: > Hey folks, > > I'm testing[0] out flipping our current method of consuming upstream > puppet modules from using pinned versions hosted on fuel-infra to be > able to use the ones directly from upstream

Re: [openstack-dev] [Fuel][Plugins] apt segfaults when too many repositories are configured

a transient problem with the remote package repositories. BR, Simon [0] https://bugs.launchpad.net/fuel-plugins/+bug/1514043 On Fri, Nov 6, 2015 at 11:38 AM, Simon Pasquier <spasqu...@mirantis.com> wrote: > Hello, > > While testing LMA with MOS 7.0, we got apt-get crashing and failing t

[openstack-dev] [Fuel][Plugins] apt segfaults when too many repositories are configured

Hello, While testing LMA with MOS 7.0, we got apt-get crashing and failing the deployment. The details are in the LP bug [0], the TL;DR version is that when more repositories are added (hence more packages), there is a risk that apt-get commands fail badly when trying to remap memory. The core

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

.com> wrote: >> >>> Simon, >>> I believe that it's a mistake in fuel-qa. Valid structure is in >>> fuel-web. Please fix the one in fuel-qa. >>> >>> I'm also looking forward for automated adding of people to review >>> requests based on thi

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

; > sgolovat...@mirantis.com> wrote: > >> Tests should be in plugin >> >> -- >> Best regards, >> Sergii Golovatiuk, >> Skype #golserge >> IRC #holser >> >> On Fri, Oct 16, 2015 at 5:58 PM, Simon Pasquier <spasqu...@mirantis.com> &g

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

Hello Fuelers! I'd like to discuss something that I feel is important to improve the quality of the Fuel plugins. Currently, the functional tests for Fuel plugins are located in the fuel-qa project [1]. IMO this isn't viable in the (mid) long term since: - the fuel-qa cores have little knowledge

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

Hello Alexey, On Fri, Oct 16, 2015 at 5:35 PM, Alexey Elagin wrote: > Hello Simon! > > We are going to remove plugins' functional tests from fuel-qa because this > tests don't use for our plugins CI process. > And where are the existing tests going to be stored then?

[openstack-dev] [Fuel][Plugins] request for update of fuel-plugin-builder on pypi

Hi, It would be cool if fuel-plugin-builder (fpb) v3.0.0 could be released on pypi. We've moved some of the LMA plugins to use the v3 format. Right now we have to install fpb from source which is hard to automate in our tests unfortunately (as already noted by Sergii [1]). BR, Simon [1]

Re: [openstack-dev] [Fuel][Plugins] add health check for plugins

Hello Samuel, This looks like an interesting idea. Do you have any concrete example to illustrate your point (with one of your plugins maybe)? BR, Simon On Mon, Aug 10, 2015 at 12:04 PM, Samuel Bartel samuel.bartel@gmail.com wrote: Hi all, actually with fuel plugins there are test for

Re: [openstack-dev] [Monasca] Monasca mid-cycle meetup

Hi, I've had a quick look at the Etherpad which mentions Ceilosca. The name is quite intriguing but I didn't find any reference to it in the Monasca Wiki. Could you tell us a bit more about it? Does it mean that Monasca plans to expose an API that would be compatible with the Ceilometer API? BR,

Re: [openstack-dev] [Fuel][Fuel-library] Using librarian-puppet to manage upstream fuel-library modules

Alex, could you enable the comments for all on your document? Thanks! Simon On Thu, Jul 9, 2015 at 11:07 AM, Bogdan Dobrelya bdobre...@mirantis.com wrote: Hello everyone, I took some time this morning to write out a document[0] that outlines one possible ways for us to manage our

[openstack-dev] [Ceilometer][Gnocchi] question on integration with time-series databases

Hi, Originally, I posted this question on the review [0] that adds InfluxDB support to Gnocchi but Julien felt that it wasn't relevant in the scope of the review. Still I think that it deserves some discussion... The current implementation of the InfluxDB driver for Gnocchi doesn't follow the

Re: [openstack-dev] [Fuel] [Plugins] type available

Hello Samuel, AFAIK there is no such feature yet. The schema validators are here [1] [2]. BR, Simon [1] https://github.com/stackforge/fuel-plugins/blob/master/fuel_plugin_builder/fuel_plugin_builder/validators/schemas/base.py [1]

Re: [openstack-dev] [new][cloudpulse] Announcing a project to HealthCheck OpenStack deployments

On Wed, May 13, 2015 at 3:27 PM, David Kranz dkr...@redhat.com wrote: On 05/13/2015 09:06 AM, Simon Pasquier wrote: Hello, Like many others commented before, I don't quite understand how unique are the Cloudpulse use cases. For operators, I got the feeling that existing solutions fit

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

Hello Samuel, As far as I know, this isn't possible unfortunately. For our own needs, we ended up adding a fixed-size list with all items but the first one disabled. When you enter something in the first input box, it enabled the second box and so on (see [1]). In any case, this would be a good

Re: [openstack-dev] H302 considered harmful

On Wed, Feb 25, 2015 at 9:47 PM, Doug Hellmann d...@doughellmann.com wrote: On Wed, Feb 25, 2015, at 02:59 PM, Robert Collins wrote: On 26 February 2015 at 08:54, melanie witt melwi...@gmail.com wrote: On Feb 25, 2015, at 10:51, Duncan Thomas duncan.tho...@gmail.com wrote: Is there

Re: [openstack-dev] [Fuel] Cache for packages on master node

Hello Tomasz, In a previous life, I used squid to speed up packages downloads and it worked just fine... Simon On Tue, Feb 10, 2015 at 3:24 PM, Tomasz Napierala tnapier...@mirantis.com wrote: Hi, We are currently redesigning our apporach to upstream distributions and obviusly we will need

Re: [openstack-dev] [Fuel] Logs format on UI (High/6.0)

Hello, (resurrecting this old thread because I think I found the root cause) The problem affects all OpenStack environments using Syslog, not only Fuel-based installations: when use_syslog is true, the logging_context_format_string and logging_default_format_string parameters aren't taken into

Re: [openstack-dev] [api][nova] Openstack HTTP error codes

On Fri, Jan 30, 2015 at 3:05 AM, Kenichi Oomichi oomi...@mxs.nes.nec.co.jp wrote: -Original Message- From: Roman Podoliaka [mailto:rpodoly...@mirantis.com] Sent: Friday, January 30, 2015 2:12 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re:

Re: [openstack-dev] [Fuel] Plugins for Fuel: repo, doc, spec - where?

Hello, I pretty much agree with Evgeniya here. Keeping everything (code, docs, specs and tests) in the same repo is essential to keep up-to-date information. Otherwise chances are that it will diverge eventually. See other comments inline. BR, Simon On Fri, Jan 23, 2015 at 4:50 PM, Evgeniya

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

I've added another option to the Etherpad: collectd can do basic threshold monitoring and run any kind of scripts on alert notifications. The other advantage of collectd would be the RRD graphs for (almost) free. Of course since monit is already supported in Fuel, this is the fastest path to get

Re: [openstack-dev] [all] config options not correctly deprecated

FYI, I've forwarded this thread to the operators mailing list as I feel they will be very much interested by this discussion. BR Simon On Fri, Nov 14, 2014 at 1:37 AM, Sean Dague s...@dague.net wrote: On 11/13/2014 06:56 PM, Clint Byrum wrote: Excerpts from Ben Nemec's message of 2014-11-13

Re: [openstack-dev] [Neutron] FWaaS/Security groups Not blocking ongoing traffic

Hello Itzik, This has been discussed lately on this ML. Please see https://bugs.launchpad.net/neutron/+bug/1335375. BR, Simon On Mon, Oct 27, 2014 at 1:17 PM, Itzik Brown itbr...@redhat.com wrote: Hi, When building a firewall with a rule to block a specific Traffic - the current traffic is

Re: [openstack-dev] [NOVA] security group fails to attach to an instance if port-id is specified during boot.

On Fri, Sep 26, 2014 at 10:19 AM, Christopher Yeoh cbky...@gmail.com wrote: On Fri, 26 Sep 2014 11:25:49 +0400 Oleg Bondarev obonda...@mirantis.com wrote: On Fri, Sep 26, 2014 at 3:30 AM, Day, Phil philip@hp.com wrote: I think the expectation is that if a user is already

Re: [openstack-dev] [FUEL] Re: SSL in Fuel.

Hi, On Thu, Sep 11, 2014 at 1:03 PM, Sebastian Kalinowski skalinow...@mirantis.com wrote: I have some topics for [1] that I want to discuss: 1) Should we allow users to turn SSL on/off for Fuel master? I think we should since some users may don't care about SSL and enabling it will

Re: [openstack-dev] [FUEL] Re: SSL in Fuel.

Hello, Thanks for the detailed email, Stanislaw. Your suggestion of deploying a CA container is really interesting. Especially for OSTF and other testing since the tools only need to know about the root CA. Lets back up a bit and list the different options for Fuel users: 0/ The user is happy

Re: [openstack-dev] [Neutron] minimal scope covered by third-party testing

aren't voting for Nova. Instead it would have voted against any subsequent change to Neutron. Simon [1] https://bugs.launchpad.net/neutron/+bug/1301449 Salvatore [1] https://review.openstack.org/#/c/75304/ On 3 April 2014 12:28, Simon Pasquier simon.pasqu...@bull.net

[openstack-dev] [Neutron] minimal scope covered by third-party testing

is working with Neutron *and* Nova (I'm not even talking about security groups). I had a quick look at the existing 3rd party CI systems and I found none running this kind of check (correct me if I'm wrong). Thoughts? [1] https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers -- Simon Pasquier

Re: [openstack-dev] [Neutron] minimal scope covered by third-party testing

: load balancer scenario will stay optional). Salvatore [1] https://review.openstack.org/#/c/75304/ On 3 April 2014 12:28, Simon Pasquier simon.pasqu...@bull.net wrote: Hi, I'm looking at [1] but I see no requirement of which Tempest tests should be executed. In particular, I'm a bit

Re: [openstack-dev] [Neutron] [Nova] libvirt+Xen+OVS VLAN networking in icehouse

Hi, I've played a little with XenAPI + OVS. You might be interested by this bug report [1] that describes a related problem I've seen in this configuration. I'm not sure about Xen libvirt though. My assumption is that the future-proof solution for using Xen with OpenStack is the XenAPI driver but

Re: [openstack-dev] [devstack] libvirt default log level

+1 for your change. I've been hit by the very same issue today. Simon On 15/01/2014 17:56, Steven Dake wrote: Hi, Ken'ichi Omichi submitted a change [1] in devstack to change the default log level to 1 for libvirt. This results in continual spam to /var/log/messages in my development system,

Re: [openstack-dev] [Openstack] [Neutron] Security groups issue when running latest libvirt?

Le 07/11/2013 03:18, Martinx - ジェームズ a écrit : That is true... Back to LibvirtHybridOVSBridgeDriver, Security Groups is working again... Thanks for the feedback Thiago. I've opened a bug on Launchpad: https://bugs.launchpad.net/nova/+bug/1248859 On 6 November 2013 15:03, Simon Pasquier

Re: [openstack-dev] [Heat] How do i implement this usecase:

Team: HPCS-Vertica Location: Noida, India ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Simon Pasquier Software Engineer Bull, Architect of an Open World Phone

Re: [openstack-dev] [Openstack] [Neutron] Security groups issue when running latest libvirt?

://github.com/openstack/tempest/blob/master/tempest/api/network/test_security_groups_negative.py Le 05/11/2013 14:57, Simon Pasquier a écrit : Hi all, I'm struggling with security groups on Havana with Neutron and OVS plugin (GRE tunnels). No problem to create/delete security group rules but even

Re: [openstack-dev] [Neutron] Security groups with XenAPI

Hi Bob, Thanks for the reply. Le 28/10/2013 17:47, Bob Ball a écrit : Hi Simon, Yes, I believe you are right. We were already planning to discuss this very topic at the XenAPI roadmap session at the summit. Hopefully someone will take on tying up this loose end there. Security group

[openstack-dev] [Neutron] Security groups with XenAPI

/openstack/neutron/blob/master/neutron/agent/linux/iptables_manager.py#L346 [3] https://review.openstack.org/#/c/2071 -- Simon Pasquier Software Engineer Bull, Architect of an Open World Phone: + 33 4 76 29 71 49 http://www.bull.com ___ OpenStack-dev

Re: [openstack-dev] [Heat] question about stack updates, instance groups and wait conditions

it depends on the NumberOfComputes or NumberOfWaitConditions parameter, it gets updated when I update one of these. [1] http://paste.openstack.org/show/47142/ [2] http://paste.openstack.org/show/47148/ -- Simon Pasquier Software Engineer Bull, Architect of an Open World Phone: + 33 4 76 29 71 49 http

Re: [openstack-dev] [Heat] question about stack updates, instance groups and wait conditions

that the update has applied. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Simon Pasquier Software Engineer Bull, Architect of an Open World Phone: + 33 4 76 29 71 49

Re: [openstack-dev] VM Ensembles

. Cheers, Rodrigo A. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Simon Pasquier Software Engineer Bull, Architect of an Open World Phone: + 33 4 76 29 71 49 http

[openstack-dev] [Heat] question about stack updates, instance groups and wait conditions

a simpler way to achieve the same result? Regards, [1] http://paste.openstack.org/show/47142/ [2] http://paste.openstack.org/show/47148/ -- Simon Pasquier Software Engineer Bull, Architect of an Open World Phone: + 33 4 76 29 71 49 http://www.bull.com

Re: [openstack-dev] Confused about GroupAntiAffinityFilter and GroupAffinityFilter

Gary (or others), did you have some time to look at my issue? FYI, I opened a bug [1] on Launchpad. I'll update it with the outcome of this discussion. Cheers, Simon [1] https://bugs.launchpad.net/nova/+bug/1218878 Le 03/09/2013 15:54, Simon Pasquier a écrit : I've done a wrong copypaste

Re: [openstack-dev] Confused about GroupAntiAffinityFilter and GroupAffinityFilter

this with the patches that I mentioned below and it works. I will invest some time on this on Sunday to make sure that it is all working with the latest code. Thanks Gary On 9/6/13 10:31 AM, Simon Pasquier simon.pasqu...@bull.net wrote: Gary (or others), did you have some time to look at my issue? FYI, I opened

[openstack-dev] Confused about GroupAntiAffinityFilter and GroupAffinityFilter

Reposting to openstack-dev as I got no answer on the general mailing list. Message original Sujet: [Openstack] Confused about GroupAntiAffinityFilter and GroupAffinityFilter Date : Mon, 2 Sep 2013 11:19:58 +0200 De : Simon Pasquier simon.pasqu...@bull.net Organisation

Re: [openstack-dev] Confused about GroupAntiAffinityFilter and GroupAffinityFilter

/filters/affinity_f ilter.py) Now regarding the AffinityFilter. At this stage this does not work with the AntiAffinity filter. We were banking on this being used with the multiple scheduler policies (https://review.openstack.org/#/c/37407/) Thanks Gary On 9/3/13 10:16 AM, Simon Pasquier simon.pasqu

Re: [openstack-dev] Confused about GroupAntiAffinityFilter and GroupAffinityFilter

I've done a wrong copypaste, see correction inline. Le 03/09/2013 12:34, Simon Pasquier a écrit : Hello, Thanks for the reply. First of all, do you agree that the current documentation for these filters is inaccurate? My test environment has 2 compute nodes: compute1 and compute3. First, I