Hey Vijay,
The reason that didn't work is because the netscaler-lbaas-driver-v2 had an
older patch set of the 105610 change. That means it was an entirely different
commit so after you rebased you ended up having two commits with a duplicate
commit message (which means duplicate Change-IDs).
Hi Thiago,
Like for the Windows case, where we have Heat templates for AD DC and other
MSFT related workloads (Exchange, SQL Server, SharePoint, etc) [1], the best
place in OpenStack for Samba 4 DC is a dedicated Heat template.
Heat is the de facto workload orchestration standard for
Hi Folks,
I created a new pollster plugin for ceilometer by:
- adding a new item under enterypoint/ceilometer.poll.central in setup.cfg
file
- adding the implementation code inheriting plugin.CentralPollster
- adding a new source to pipeline.yaml as bellows:
I find a BP here.
https://blueprints.launchpad.net/nova/+spec/implement-rbd-snapshots-instead-of-qemu-snapshots
We have same need for doing snapshot on rbd-backed instance (not full copy,
only snapshot).
Do anyone have thought about this?
Any updates / patch on the BP, or somebody already did
HI All,
I am pretty new to openstack . I am trying to access rest
services to create single/multiple image using nova rest services .
Some how i am not able to access. Can you please point to some
documentation or example ?
--
Regards and Thanks
Soumya Kanti Acharya
Is there anybody working on below bug?
https://bugs.launchpad.net/nova/+bug/1192192
The comments are ends 2014-03-26
I guess we should fix the VCDriver source codes.
If someone is doing now, can you share how to solve the problem?
___
OpenStack-dev
+1, thanks!
On Wed, Aug 13, 2014 at 6:05 PM, Kyle Mestery mest...@mestery.com wrote:
Per this week's Neutron meeting [1], it was decided that offering a
rotating meeting slot for the weekly Neutron meeting would be a good
thing. This will allow for a much easier time for people in
Btw, there is no service.stat record/row in meter table in ceilometer
database.
Regards,
Gary
From: Duan, Li-Gong (Gary@HPServers-Core-OE-PSC)
Sent: Monday, August 18, 2014 3:45 PM
To: openstack-dev@lists.openstack.org
Cc: Duan, Li-Gong (Gary@HPServers-Core-OE-PSC)
Subject: [Ceilometer]
I think it's a very interesting test for docker. I too have been think
about this for some time to try and dockerise OpenStack services, but as
the usual story goes, I have plenty things I'd love to try, but there are
only so many hours in a day...
Would definitely be interested to hear if anyone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 17/08/14 02:09, Angus Lees wrote:
On 16 Aug 2014 06:09, Doug Hellmann d...@doughellmann.com
mailto:d...@doughellmann.com wrote:
On Aug 15, 2014, at 9:29 AM, Ihar Hrachyshka
ihrac...@redhat.com
mailto:ihrac...@redhat.com wrote:
Mark McLoughlin wrote:
[...]
I don't see how any self-respecting open-source project can throw a
release over the wall and have no ability to address critical bugs with
that release until the next release 6 months later which will also
include a bunch of new feature work with new bugs. That's
Hello Doug, All.
This release is currently blocked on landing some changes in projects
using the library so they don’t break when the new version starts using
different exception classes. We’re tracking that work in
https://etherpad.openstack.org/p/sqla_exceptions_caught
It looks like we’re
It seems that VCDriver do not support live migration till now.
I recalled in ATL summit, the VMWare team is going to do some enhancement
to enable live migration:
1) Make sure one nova compute can only manage one cluster or resource pool,
this can make sure VMs in different cluster/resource pool
I see that there are some openstack docker images in public docker repo,
perhaps you can check them on github to see how to use them.
[root@db03b04 ~]# docker search openstack
NAME
DESCRIPTION STARS OFFICIAL
AUTOMATED
ewindisch/dockenstack
Doug Hellmann wrote:
On Aug 13, 2014, at 4:42 PM, Russell Bryant rbry...@redhat.com wrote:
Let me try to say it another way. You seemed to say that it wasn't much
to ask given the rate at which things happen in OpenStack. I would
argue that given the rate, we should not try to ask more of
David,
I'm happy to hear that :)! After thinking a bit, I came up with the
following strategy for further Merlin development: make all the
commits into a separate repository (stackforge/merlin) at least until
the PoC is ready. This will allow to keep project history more
granular instead of
Hi,
Went through the following link:
https://swiftstack.com/blog/2012/09/16/globally-distributed-openstack-swift-cluster/
I'm trying to simulate the 2-region 3-replica scenario. The document says
that the 3rd replica will be asynchronously moved to the remote location
with a 2-region setup.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 18/08/14 11:00, Thierry Carrez wrote:
Mark McLoughlin wrote:
[...] I don't see how any self-respecting open-source project can
throw a release over the wall and have no ability to address
critical bugs with that release until the next release
Hi mistral folks,
I’d like to remind that we’ll have a team meeting today as usually at 16.00 UTC
at #openstack-meeting.
Agenda:
* Review action items
* Current status (progress, issues, roadblocks)
* Further plans
* Release 0.1 scope (BPs and bugs)
* Open discussion
Please also look at
Hi.
I am trying to update my contact information in order to submit my first gerrit
review. I go to review.openstack.org and log in, then go to my account settings
and click on Contact Information. I provide my address and click Save
Changes and get:
Code Review - Error
Server Error
Cannot
On 18/08/14 19:01, Udi Kalifon wrote:
Hi.
I am trying to update my contact information in order to submit my first
gerrit review. I go to review.openstack.org and log in, then go to my account
settings and click on Contact Information. I provide my address and click
Save Changes and get:
On Sat, 16 Aug 2014 18:27:19 +0200
Marc Koderer m...@koderer.com wrote:
Hi all,
Am 15.08.2014 um 23:31 schrieb Jay Pipes jaypi...@gmail.com:
I suggest that tempest should be the name of the import'able
library, and that the integration tests themselves should be what
is pulled out of
Thanks for reply Jay~!
From icehouse, one nova-compute can manage multi clusters I think.
In this case, how should we progress in order to archive the live migration
functions.
Thanks.
John Haan.
2014-08-18 19:00 GMT+09:00 Jay Lau jay.lau@gmail.com:
It seems that VCDriver do not
We recently had a change merged to the run_tests.sh script that Nova
developers would really benefit from knowing about:
https://review.openstack.org/#/c/110746/
Basically, it provides a way to run the pep8 tests *only* against the files
which you have actually touched in your patch. For most
Hi All,
I have a `little` trouble with the volume attachment stability.
The test_stamp_pattern test is skipped since long, you
can see what would happen if it would be enabled [1] now.
There is a workaround kind way for enabling that test [2].
I suspected the acpi hot plug event is not
On Mon, Aug 18, 2014 at 12:18:16PM +0200, Thierry Carrez wrote:
Doug Hellmann wrote:
On Aug 13, 2014, at 4:42 PM, Russell Bryant rbry...@redhat.com wrote:
Let me try to say it another way. You seemed to say that it wasn't much
to ask given the rate at which things happen in OpenStack. I
Clint Byrum wrote:
Here's why folk are questioning Ceilometer:
Nova is a set of tools to abstract virtualization implementations.
Neutron is a set of tools to abstract SDN/NFV implementations.
Cinder is a set of tools to abstract block-device implementations.
Trove is a set of tools to
As the conversation has drifted away from a discussion pertaining the nova
core team, I have some comments inline as well.
On 18 August 2014 12:18, Thierry Carrez thie...@openstack.org wrote:
Doug Hellmann wrote:
On Aug 13, 2014, at 4:42 PM, Russell Bryant rbry...@redhat.com wrote:
Let me
Till now, live migration is not supported by VCDriver in both Juno and
Icehouse.
For icehouse, yes, one nova compute can manage multiple clusters, but live
migration will be failed for such case as target host and source host will
be considered to the same host (Only one nova compute).
I believe that everything can not go as a dock container. For e.g.
1. compute nodes
2. baremetal provisioning
3. L3 router etc
My understanding is that container is good mechanism to deploy
api-controller and scheduler for many services. For backend component of
services (like nova-compute,
Le 18 août 2014 14:36, Salvatore Orlando sorla...@nicira.com a écrit :
As the conversation has drifted away from a discussion pertaining the
nova core team, I have some comments inline as well.
On 18 August 2014 12:18, Thierry Carrez thie...@openstack.org wrote:
Doug Hellmann wrote:
On
I found sahara.openstack.common.db has replaced by olso.db, i wonder the
reason of this replacement. Is the any performance problem of the
original sahara.openstack.common.db
?
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 14/08/14 18:33, Ben Nemec wrote:
On 08/14/2014 08:37 AM, Ihar Hrachyshka wrote:
Hi all,
some plugins depend on modules that are not mentioned in
requirements.txt. Among them, Cisco Nexus (ncclient), Brocade
(ncclient), Embrane
Hi all,
maintenance release of Fuel is finally out. 5.0.1 is primarily bugfix
release with a ton of fixes backported from master (5.1) - 192 bugs were
processed [1].
This is the first release when we produce not only Fuel ISO, but also so
called upgrade tarball. It is a bundle which allows you to
Thanks Mark.
As usual I had to fetch your message from the spam folder!
Anyway, I received a sensible request to avoid running neutron tests for
advanced services (load balancing, firewall, vpn), in the integrated gate.
Therefore the patches [1] and [2] will not run anymore service plugins in
Hey Ionely,
the oslo.db is a graduated version of code from the oslo-incubator
(that was periodically synced to sahara.openstack.common.db). So, the
only reason is to switch to the graduated lib.
On Mon, Aug 18, 2014 at 5:04 PM, lonely Feb lonely8...@gmail.com wrote:
I found
On 18/08/14 12:51, Daniel P. Berrange wrote:
We recently had a change merged to the run_tests.sh script that Nova
developers would really benefit from knowing about:
https://review.openstack.org/#/c/110746/
Basically, it provides a way to run the pep8 tests *only* against the files
(kicking this thread to the dev mailing list)
Thanks for starting this discussion on Juno work efforts, Nate. This would be
a good discussion to pick up at the 3pm CDT IRC meeting today as well. I've
added some thoughts below as well.
I believe the plan is to finalize features and API changes
warn() and warning() are synonyms (literally the same method, aliased). We had
to add a similar alias in the oslo ContextAdapter to support code using both
forms in existing code. If the documented form is warning(), then I agree we
should stick with that, although I don’t think the churn
Yes, that would be a good next step.
Doug
On Aug 17, 2014, at 10:03 PM, Peng Wu peng.e...@gmail.com wrote:
Yes, I am interested in adding these missing gettext functions to
oslo.i18n library.
Guess the next step is to create a blueprint for Kilo?
Thanks,
Peng Wu
On Fri,
On Mon, 2014-08-18 at 14:23 +0200, Thierry Carrez wrote:
Clint Byrum wrote:
Here's why folk are questioning Ceilometer:
Nova is a set of tools to abstract virtualization implementations.
Neutron is a set of tools to abstract SDN/NFV implementations.
Cinder is a set of tools to abstract
On Thu, Aug 14 2014, Yuriy Taraday wrote:
Hi Yuriy,
[…]
Looking forward to your opinions.
This looks like a good summary of the situation.
I've added a solution E based on pthread, but didn't get very far about
it for now.
--
Julien Danjou
# Free Software hacker
# http://julien.danjou.info
On Mon, Aug 18, 2014 at 07:57:28AM +1000, Michael Still wrote:
My recollection is that this was a request from the oslo team, but it
was so long ago that I don't recall the details.
I think the change is low value, so should only be done when someone
is changing the logging in a file already
On Wed, Aug 13, 2014 at 3:29 PM, Doug Hellmann d...@doughellmann.com
wrote:
On Aug 13, 2014, at 4:08 PM, Matthew Treinish mtrein...@kortar.org
wrote:
On Wed, Aug 13, 2014 at 03:43:21PM -0400, Eoghan Glynn wrote:
Divert all cross project efforts from the following projects so we
can
Hello people,
I think backward compatibility is a good idea. We can make the
user/pass inputs for data objects optional (they are required
currently), maybe even gray them out in the UI with a checkbox to turn
them on, or something like that.
This is similar to what I was thinking. We
On Fri, Aug 15, 2014 at 3:01 PM, Joe Gordon joe.gord...@gmail.com wrote:
On Thu, Aug 14, 2014 at 4:02 PM, Eoghan Glynn egl...@redhat.com wrote:
Additional cross-project resources can be ponied up by the large
contributor companies, and existing cross-project resources are not
Neutron Ci Folks,
I have received answers from almost all the CI contacts and I want to
thank you all.
Every case is different and I will review each one of your answer and
questions.
I do understand that every CI is different and this is why I would suggest
two things:
1) Today's Neutron IRC
On 08/18/2014 06:18 AM, Thierry Carrez wrote:
Doug Hellmann wrote:
On Aug 13, 2014, at 4:42 PM, Russell Bryant rbry...@redhat.com wrote:
Let me try to say it another way. You seemed to say that it wasn't much
to ask given the rate at which things happen in OpenStack. I would
argue that
On Aug 18, 2014, at 10:15 AM, Daniel P. Berrange berra...@redhat.com wrote:
On Mon, Aug 18, 2014 at 07:57:28AM +1000, Michael Still wrote:
My recollection is that this was a request from the oslo team, but it
was so long ago that I don't recall the details.
I think the change is low value,
To make some time oriented comparisons in javelin2 I'd like to be
able to access the timestamps on the data dumps in the $SAVE_DIR.
In my experiments I've done this by pushing SAVE_DIR and
BASE_RELEASE into the subshell that calls javelin2 -m create in
grenade.sh.
Is there:
* A better way to
Thank you Akihiro.
I will propose a better organization for this section. Stay tune!
Edgar
On 8/17/14, 10:53 PM, Akihiro Motoki mot...@da.jp.nec.com wrote:
On 2014/08/18 0:12, Kyle Mestery wrote:
On Fri, Aug 15, 2014 at 5:35 PM, Edgar Magana
edgar.mag...@workday.com wrote:
Team,
I did a
On Mon, Aug 18, 2014 at 9:18 AM, Russell Bryant rbry...@redhat.com wrote:
On 08/18/2014 06:18 AM, Thierry Carrez wrote:
Doug Hellmann wrote:
On Aug 13, 2014, at 4:42 PM, Russell Bryant rbry...@redhat.com wrote:
Let me try to say it another way. You seemed to say that it wasn't
much
to
Hi,
Mellanox CI is going down for maintenance.
We will notify as soon as the system is up and ready.
Sorry for the inconvenience,
Omri
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
On 08/18/2014 09:43 AM, Omri Marcovitch wrote:
Hi,
Mellanox CI is going down for maintenance.
We will notify as soon as the system is up and ready.
Sorry for the inconvenience,
Omri
___
OpenStack-dev mailing list
On Mon, Aug 18, 2014 at 11:18:52AM -0400, Russell Bryant wrote:
On 08/18/2014 06:18 AM, Thierry Carrez wrote:
Doug Hellmann wrote:
On Aug 13, 2014, at 4:42 PM, Russell Bryant rbry...@redhat.com wrote:
Let me try to say it another way. You seemed to say that it wasn't much
to ask given
On Mon, 18 Aug 2014, Chris Dent wrote:
The reason for doing this? I want to be able to confirm that some
sample data retrieved in a query against the ceilometer API has
samples that span the upgrade.
The associated change is here:
https://review.openstack.org/#/c/102354
--
Chris Dent
On Mon, Aug 18, 2014 at 11:27:39AM -0400, Doug Hellmann wrote:
On Aug 18, 2014, at 10:15 AM, Daniel P. Berrange berra...@redhat.com wrote:
On Mon, Aug 18, 2014 at 07:57:28AM +1000, Michael Still wrote:
My recollection is that this was a request from the oslo team, but it
was so long ago
Mellanox CI is up and ready.
Thanks
From: Omri Marcovitch [mailto:om...@mellanox.com]
Sent: Monday, August 18, 2014 6:44 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [neutron] [third-party] Mellanox CI Third party system
is going down for Maintenance
Hi,
Mellanox CI is
On 2014-08-17 23:53:12 -0700 (-0700), daya kamath wrote:
[...]
openstack-infra does not get updated as part of the gate jobs
[...]
Right, we use puppet to continuously apply that configuration to our
durable workers and nodepool templates.
--
Jeremy Stanley
On 08/18/2014 10:18 AM, Omri Marcovitch wrote:
Mellanox CI is up and ready.
Thanks
From: Omri Marcovitch [mailto:om...@mellanox.com]
Sent: Monday, August 18, 2014 6:44 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [neutron] [third-party] Mellanox CI Third party
Hi All,
Start of q-svc in devstack fails with error message No type
driver for tenant network_type: vxlan. Service terminated!. I have not choosen
vxlan as ML2 type driver in localrc. I have added the details of localrc file
for my setup below for reference. Can you please
On Fri, Aug 15, 2014 at 01:57:29AM +0400, Boris Pavlovic wrote:
Matt,
One thing did just occur to me while writing this though it's probably worth
investigating splitting out the stress test framework as an external
tool/project after we start work on the tempest library. [3]
I
On Aug 14, 2014, at 8:52 AM, Russell Bryant rbry...@redhat.com wrote:
On 08/14/2014 11:40 AM, David Kranz wrote:
On 08/14/2014 10:54 AM, Matt Riedemann wrote:
On 8/14/2014 3:47 AM, Daniel P. Berrange wrote:
On Thu, Aug 14, 2014 at 09:24:36AM +1000, Michael Still wrote:
On Thu, Aug 14,
On Aug 13, 2014, at 10:32 PM, Michael Still mi...@stillhq.com wrote:
On Thu, Aug 14, 2014 at 2:48 PM, Joe Gordon joe.gord...@gmail.com wrote:
On Wed, Aug 13, 2014 at 8:31 PM, Michael Still mi...@stillhq.com wrote:
On Thu, Aug 14, 2014 at 1:24 PM, Jay Pipes jaypi...@gmail.com wrote:
Just
Folks,
Thanks for joining the meeting today.
As usually,
Meeting minutes:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-08-18-16.00.html
Meeting log:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-08-18-16.00.log.html
Meeting agenda/archive:
Stuart,
I also can't say I've seen this, but I am curious now. I did have a few
questions for you though.
1. When you say you set nf_conntrack_max/nf_conntrack_hash to 256k, did you
really set the hash size that large? Typically the hash is 1/8 of the max,
meaning you'd have 8 entries per
When you don't specify it, the default network type is:
(from lib/neutron_plugins/ml2)
Q_ML2_TENANT_NETWORK_TYPE=${Q_ML2_TENANT_NETWORK_TYPE:-vxlan}
You can try specifying that as vlan in your local.conf file and see what
happens.
-Brian
BTW, this probably should have just gone to
Hi,
My 2 cents for the multiple listeners per load balancer discussion: We have
customers who like to have a listener on port 80 and one on port 443 on the
same VIP (we had to patch libra to allow two listeners in one single haproxy)
- so having that would be great.
I like the proposed status
I'm not sure why, but the default tenant network type was changed to vxlan.
[1]
You now need to specify Q_ML2_TENANT_NETWORK_TYPE=vlan
1.
https://github.com/openstack-dev/devstack/commit/8feaf6c9516094df58df84479d73779e87a79264
On Mon, Aug 18, 2014 at 9:35 AM, Parikshit Manur
Hi All,
I'm working on Third Party CI for Cinder and I've got several issues with
Zuul configuration.
Third Party CI should run dsvm-tempest-full job to test Cinder driver in my
case. It means, that all components should work well, not only Cinder.
E.g.: I'm working on Cinder + Ceph
If you want to run OpenStack services in Docker, I suggest having a look at
Dockenstack:
https://github.com/ewindisch/dockenstack
Adrian
On Aug 18, 2014, at 3:04 AM, Jay Lau
jay.lau@gmail.commailto:jay.lau@gmail.com wrote:
I see that there are some openstack docker images in public
Hi everyone,
The OpenStack Infrastructure (Infra) team is hosting our weekly
meeting on Tuesday August 19th, at 19:00 UTC in #openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is
welcome to to add agenda items)
Everyone interested
On Mon, Aug 18, 2014 at 3:18 AM, Thierry Carrez thie...@openstack.org
wrote:
Doug Hellmann wrote:
On Aug 13, 2014, at 4:42 PM, Russell Bryant rbry...@redhat.com wrote:
Let me try to say it another way. You seemed to say that it wasn't much
to ask given the rate at which things happen in
On Mon, Aug 18, 2014 at 8:18 AM, Russell Bryant rbry...@redhat.com wrote:
On 08/18/2014 06:18 AM, Thierry Carrez wrote:
Doug Hellmann wrote:
On Aug 13, 2014, at 4:42 PM, Russell Bryant rbry...@redhat.com wrote:
Let me try to say it another way. You seemed to say that it wasn't
much
to
On Mon, Aug 18, 2014 at 5:22 AM, Daniel P. Berrange berra...@redhat.com
wrote:
On Mon, Aug 18, 2014 at 12:18:16PM +0200, Thierry Carrez wrote:
Doug Hellmann wrote:
On Aug 13, 2014, at 4:42 PM, Russell Bryant rbry...@redhat.com
wrote:
Let me try to say it another way. You seemed to say
Hi German,
I don't think it is a requirement that those two frontend sections (or
listen sections) have to live in the same config. I thought if they
were listening on the same IP but different ports it could be in two
different haproxy instances. I could be wrong though.
Thanks,
Brandon
On
Hello!
I've published parallels-sdk:
https://github.com/Parallels/parallels-sdk
--
Dmitry Guryanov
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 2014-08-18 20:40:48 +0300 (+0300), Ivan Kolodyazhny wrote:
[...]
I'm looking for something like following:
1) run my Third Party CI for all patch-sets in Cinder
2) run my Third Party CI (Cinder + Ceph backend) for Nova only if it
changes nova/virt/libvirt/rbd.py module.
Does such
Correct, best-effort. There is no guarantee or time boxing on cross-region
replication. The best way to manage cross site replication is by tuning
your replica count to ensure you have primary copies in each region -
eventually. Possibly evaluate if you need write_affinity at all (you can
On Monday 18 August 2014 22:45:17 Dmitry Guryanov wrote:
Hello!
I've published parallels-sdk:
https://github.com/Parallels/parallels-sdk
Sorry, I've sent this mail to the wrong list :(, please, ignore.
--
Dmitry Guryanov
___
OpenStack-dev
Edgar,
Our CI is running the tests (non voting), but don't see it listed on the
review for any patch. Is this due to missing logs? I would like to confirm
this is the issue, will resolve this.
Thanks,
-hemanth
On Mon, Aug 18, 2014 at 8:35 AM, Edgar Magana edgar.mag...@workday.com
wrote:
On 08/14/2014 02:55 AM, Boring, Walter wrote:
Hey guys,
I wanted to pose a nomination for Cinder core.
Xing Yang.
She has been active in the cinder community for many releases and has worked
on several drivers as well as other features for cinder itself. She has
been doing an
On Mon, Aug 18, 2014 at 1:42 PM, Adrian Otto adrian.o...@rackspace.com
wrote:
If you want to run OpenStack services in Docker, I suggest having a look
at Dockenstack:
https://github.com/ewindisch/dockenstack
Note, this is for simplifying and speeding-up the use of devstack. It
provides an
On Mon, Aug 18, 2014 at 8:49 AM, Jyoti Ranjan jran...@gmail.com wrote:
I believe that everything can not go as a dock container. For e.g.
1. compute nodes
2. baremetal provisioning
3. L3 router etc
Containers are a good solution for all of the above, for some value of
container. There is
Agenda items are numbered, and topics, as discussed, are described beneath in
list format.
1) Discuss future of Octavia in light of Neutron-incubator project proposal.
a) There are many problems with Neutron-Incubator as currently described
b) The political happenings in Neutron leave
Yes, I'm advocating keeping each listener in a separate haproxy
configuration (and separate running instance). This includes the example I
mentioned: One that listens on port 80 for HTTP requests and redirects
everything to the HTTPS listener on port 443. (The port 80 listener is a
simple
The Oslo team is pleased to announce release 0.2.0 of oslo.i18n, the library
for managing translated messages in OpenStack.
This release includes a new test fixture for writing tests for classes that
need to use both lazily and immediately translated strings.
Please report bugs on the Oslo
On Sat, Aug 16, 2014 at 06:27:19PM +0200, Marc Koderer wrote:
Hi all,
Am 15.08.2014 um 23:31 schrieb Jay Pipes jaypi...@gmail.com:
I suggest that tempest should be the name of the import'able library, and
that the integration tests themselves should be what is pulled out of the
On Sun, Aug 17, 2014 at 9:24 AM, Jay Bryant jsbry...@electronicjungle.net
wrote:
+2
I prefer the LOG.warning format and support that given the documentation
you shared.
If there is agreement I would create a hacking check.
I think a better approach is to just not care which i used here.
On 08/18/2014 03:38 PM, Julien Danjou wrote:
On Thu, Aug 14 2014, Yuriy Taraday wrote:
Hi Yuriy,
[…]
Looking forward to your opinions.
This looks like a good summary of the situation.
I've added a solution E based on pthread, but didn't get very far about
it for now.
In my
Hi Trevor,
thanks for sharing this minutes!
I would like to cooperate a bit to this project's developments, possibly
without ending up being just deadweight.
To this aim I have some comments inline.
Salvatore
On 18 August 2014 22:25, Trevor Vardeman trevor.varde...@rackspace.com
wrote:
Hi Steven,
In my example we don’t share anything except the VIP ☺ So my motivation is if
we can have two listeners share the same VIP. Hope that makes sense.
German
From: Stephen Balukoff [mailto:sbaluk...@bluebox.net]
Sent: Monday, August 18, 2014 1:39 PM
To: OpenStack Development Mailing
German--
By 'VIP' do you mean something roughly equivalent to 'loadbalancer' in the
Neutron LBaaS object model (as we've discussed in the past)? That is to
say, is this thingy a parent object to the Listener in the hierarchy? If
so, then what we're describing definitely accommodates that.
(And
Hi Salvatore,
It'd be great to get your contributions in this! If you could only bring
your knowledge and experience with Neutron to the table that'd be very
beneficial. Looking forward to it.
Comments in-line
On Mon, 2014-08-18 at 23:06 +0200, Salvatore Orlando wrote:
Hi Trevor,
thanks
No, I mean with VIP the original meaning more akin to a Floating IP…
German
From: Stephen Balukoff [mailto:sbaluk...@bluebox.net]
Sent: Monday, August 18, 2014 2:43 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Octavia] Object Model and DB
a) Most members in favor of keeping the webex meetings for the time being
Correction: most of the people that like to talk over each other in a
large voice conference voiced their approval of voice. Those that prefer
to wait for pauses to speak were unsurprisingly silent, or tried and
failed to
Hi all,
This is intended for those readers interested in reviewing and soon
merging the HA routers implementation for Juno. Assaf Muller has
written a blog [1] about this new feature which serves as a good
overview. It will be useful for reviewers to get up to speed and I
recommend reading it
I agree almost completely with Brandon¹s comments on the incubator.
For Octavia, I think we need to not stress neutron vs incubator vs
spin-out, and just focus on writing some load-balancing code. We¹ve spent
far too much time in Juno working on processes, glue, and APIs, and
precious little on
2014-08-19 4:11 GMT+08:00 Eric Windisch ewindi...@docker.com:
On Mon, Aug 18, 2014 at 8:49 AM, Jyoti Ranjan jran...@gmail.com wrote:
I believe that everything can not go as a dock container. For e.g.
1. compute nodes
2. baremetal provisioning
3. L3 router etc
Containers are a good
On Mon, Aug 18, 2014 at 8:49 AM, Jyoti Ranjan jran...@gmail.com wrote:
I believe that everything can not go as a dock container. For e.g.
1. compute nodes
2. baremetal provisioning
3. L3 router etc
Containers are a good solution for all of the above, for some value of
container. There
1 - 100 of 116 matches
Mail list logo
