Hello!
Do dependencies required only in some contexts belong into requirements.txt?
Yesterday we had a short discussion on #openstack-nova regarding how to
handle optional requirements. This was triggered by our quobyte nova driver
(https://review.openstack.org/#/c/110722/18), who requires xattr,
Hello. I think there might be something wrong with git-review in your
env. You might want try in another env, preferably linux if its handy. I
noticed your origin is from github? you should clone from here instead:
http://git.openstack.org/cgit/stackforge/congress
Here's what you should get
The Oslo team is pleased to announce the release of:
oslo.i18n 1.3.1: oslo.i18n library
The primary reason for this release is a packaging issue
reported and fixed by Dan Smith.
For more details, please see the git log history below and:
http://launchpad.net/oslo.i18n/+milestone/1.3.1
Please
+1
On Tue, Jan 27, 2015 at 4:05 PM, Aleksandr Didenko adide...@mirantis.com
wrote:
Hi,
After starting implementing granular deployment we've faced a bunch of
issues that would make further development of this feature much more
complicated if we have to support both Simple and HA deployment
Thank you very much
On Tue, Jan 27, 2015 at 1:06 PM, Angus Salkeld asalk...@mirantis.com
wrote:
On Tue, Jan 27, 2015 at 7:00 PM, Dmitry mey...@gmail.com wrote:
I have another question, is it possible to get the stack name in the hot
script?
E.g.
params:
$stack_name:
Hi All,
Due to weather conditions and others traveling we will need to postpone the
Hyper-V meeting until next week.
For issues or questions please email directly or contact one of us on the IRC
channel.
We will resume next week at the usual time.
p
Peter J. Pouliot CISSP
Microsoft
Hi Ariel,
This is indeed one of the use cases that is very relevant to, and can
be supported, with the GBP model. The GBP policy actions provide a way
to “redirect” to a service-instance/chain on matching a traffic
classifier. If you are able to represent the “honeypot” functionality
as a Neutron
Excerpts from Thierry Carrez's message of 2015-01-27 02:46:03 -0800:
Doug Hellmann wrote:
On Mon, Jan 26, 2015, at 12:02 PM, Thierry Carrez wrote:
[...]
I'm open to alternative suggestions on where the list of tags, their
definition and the list projects they apply to should live. If you
not to prolong single mode, I'd like to see it die. However we will
need to be able to add, change, remove, or noop portions of the tasks
graph in the future. Many of the plugins that cant currently be built
would rely on being able to sub out parts of the graph. How is that
going to factor into
I don't see this as crazy, it's not a feature of the cloud, its a
mechanism to get us there. It's not even something that most of the
time anyone sees. Continuing to waste time supporting something we are
ready to replace, and have been testing for a release already is
crazy. It adds to the
On Jan 26, 2015, at 10:16 PM, Philipp Marek philipp.ma...@linbit.com wrote:
Hello Vish,
Nova passes ip, iqn, and hostname into initialize_connection. That should
give you the info you need.
thank you, but that is on the _Nova_ side.
I need to know that on the Cinder node already:
- Original Message -
From: Marc Koderer m...@koderer.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Hi Steve,
I can host it.
Regards
Marc
Thanks Marc!
Thanks Adam, Thierry!
Dani
On Tue, Jan 27, 2015 at 1:43 PM, Adam Young ayo...@redhat.com wrote:
Short term answers:
The amount of infrastructure we would have to build to replicate CRON is
not worth it.
Figuring out a CRON strategy for nontrivial deployment is part of a larger
data
Excerpts from Tim Bell's message of 2015-01-25 22:10:10 -0800:
This is often mentioned as one of those items which catches every OpenStack
cloud operator at some time. It's not clear to me that there could not be a
scheduled job built into the system with a default frequency (configurable,
This is one reason to use the memcached backend. Why replicate these tokens in
the first place.
On Tuesday, January 27, 2015 at 10:21 AM, Clint Byrum wrote:
Excerpts from Tim Bell's message of 2015-01-25 22:10:10 -0800:
This is often mentioned as one of those items which catches every
On Tue, Jan 27, 2015, at 12:44 PM, Julien Danjou wrote:
On Tue, Jan 27 2015, Clark Boylan wrote:
So the issue is that the garbage collector segfaults on null objects in
the to be garbage collected list. Which means that by the time garbage
collection breaks you don't have the info you
On Tue, Jan 27, 2015, at 12:28 PM, Denis Makogon wrote:
On Tue, Jan 27, 2015 at 7:15 PM, Doug Hellmann d...@doughellmann.com
wrote:
On Tue, Jan 27, 2015, at 10:56 AM, Denis Makogon wrote:
On Thu, Jan 15, 2015 at 8:56 PM, Doug Hellmann d...@doughellmann.com
wrote:
On
Short term answers:
The amount of infrastructure we would have to build to replicate CRON is
not worth it.
Figuring out a CRON strategy for nontrivial deployment is part of a
larger data management scheme.
Long term answers:
Tokens should not be persisted. We have been working toward
The Oslo team is pleased to announce the release of:
oslo.messaging 1.6.0: Oslo Messaging API
The primary reason for this release is to move the code
out of the oslo namespace package as part of
https://blueprints.launchpad.net/oslo-incubator/+spec/drop-namespace-packages
This release also
Hi all,
Just a friendly reminder that this week's OpenStack Telco Working Group meeting
is tomorrow, Wednesday the 28th, at 1400 UTC in #openstack-meeting-alt. Please
add any items you wish to discuss to the agenda at:
https://etherpad.openstack.org/p/nfv-meeting-agenda
Marc Koderer has
Dmitry
This is an interesting topic. As per our discussions earlier, I suggest
that in the future we move to different serializers for each granule of our
deployment, so that we do not need to drag a lot of senseless data into
particular task being executed. Say, we have a fencing task, which has
Mike,
You are absolutely right about our current priorities for 6.1 and this
thread is not about immediate action.
But just to be fair, moving Fuel Client to a separate repo was a priori
much more complicated procedure because it is tested together with nailgun.
For Fuel Agent we just need to
Guys,
I'm now here and I don't agree that we need to remove changes
attribute. On the opposite, I think this is the only attribute which
should be looked at on UI and backend, and all these
pending_addition and pending_someotherstuff are obsolete and
needless.
Just assume, that we'll soon have
Updating subject line to attract keystone devs
Daniel Comnea wrote:
+100
Dani
On Mon, Jan 26, 2015 at 1:10 AM, Tim Bell tim.b...@cern.ch
mailto:tim.b...@cern.ch wrote:
This is often mentioned as one of those items which catches every
OpenStack cloud operator at some time. It’s
Dear PTLs, cross-project liaisons and anyone else interested,
We'll have a cross-project meeting today at 21:00 UTC, with the
following agenda:
* Cross-project DevRef akin to Nova's ([1]) [2] (@sigmavirus24)
* Avoiding private symbols in Oslo libraries [3] (dhellmann)
* Discuss the importance of
On 26.01.2015 18:34, Ruslan Kamaldinov wrote:
On Mon, Jan 26, 2015 at 6:12 PM, Andrew Pashkin apash...@mirantis.com wrote:
On 26.01.2015 18:05, Ruslan Kamaldinov wrote:
I think it's still important to perform migration specific checks. We want
to make sure that DB is in expected state after
I have another question, is it possible to get the stack name in the hot
script?
E.g.
params:
$stack_name: {get_global_variable: $stack.name}
On Tue, Jan 27, 2015 at 3:53 AM, Qiming Teng teng...@linux.vnet.ibm.com
wrote:
On Mon, Jan 26, 2015 at 07:44:25PM +0200, Dmitry wrote:
thanks,
I do not like how we are selecting names for our releases right now.
The current process is autocratic and opaque and not fun - which is the
exact opposite of what a community selected name should be.
I propose:
* As soon as development starts on release X, we open the voting for the
name of
On 01/27/2015 06:31 PM, Doug Hellmann wrote:
On Tue, Jan 27, 2015, at 12:28 PM, Denis Makogon wrote:
I'd like to build tool that would be able to profile messaging over
various deployments. This tool would give me an ability to compare
results of performance testing produced by native tools and
Hello,
When applying an IP address filter to a paginated servers query (eg,
supplying servers/detail?ip=192.168limit=100), the IP address filtering is
only being applied against the non-filtered page of servers that were
retrieved from the DB; see [1].
I believe that the IP address filtering
The problem with running in memcached is now you have to keep _EVERY_
token in RAM. This is not any cheaper than cleaning out a giant on-disk
table.
Also worth noting is that memcached can produce frustrating results unless
you run it with -M. That is because without -M, your tokens may be
https://github.com/cschwede/django-swiftbrowser is done by a swift core dev
You should browse:
http://docs.openstack.org/developer/swift/associated_projects.html#associated-projects
On Mon, Jan 26, 2015 at 11:50 AM, Adam Lawson alaw...@aqorn.com wrote:
I'm researching for a web-based
On Tue, Jan 27, 2015 at 1:50 PM, Monty Taylor mord...@inaugust.com wrote:
I do not like how we are selecting names for our releases right now.
The current process is autocratic and opaque and not fun - which is the
exact opposite of what a community selected name should be.
++
I propose:
On 01/26/2015 05:37 PM, Jay Pipes wrote:
On 01/26/2015 07:33 AM, Chris Friesen wrote:
Hi,
I'm interested in the recent work around NUMA support for guest
instances
(https://blueprints.launchpad.net/nova/+spec/virt-driver-numa-placement), but
I'm having some difficulty figuring out what
not to prolong single mode, I'd like to see it die. However we will
need to be able to add, change, remove, or noop portions of the tasks
graph in the future. Many of the plugins that cant currently be built
would rely on being able to sub out parts of the graph. How is that
going to factor
There were some issues with the build job, so this release has just gone
live. I apologize for the delay.
Doug
On Tue, Jan 27, 2015, at 02:05 PM, Doug Hellmann wrote:
The Oslo team is pleased to announce the release of:
oslo.messaging 1.6.0: Oslo Messaging API
The primary reason for this
++ absolutely!
Sent via mobile
On Jan 27, 2015, at 14:19, Jim Meyer j...@geekdaily.org wrote:
+1 all the way down.
More fun double-plus-good.
—j
On Jan 27, 2015, at 1:50 PM, Monty Taylor mord...@inaugust.com wrote:
I do not like how we are selecting names for our releases right
On Thu, Jan 22, 2015 at 7:59 PM, Evgeniy L e...@mirantis.com wrote:
The problem with merging is usually it's not clear how system performs
merging.
For example you have the next hash {'list': [{'k': 1}, {'k': 2}, {'k':
3}]}, and I want
{'list': [{'k': 4}]} to be merged, what system should
On Tue, Jan 27, 2015 at 10:47 AM, Vladimir Kuklin vkuk...@mirantis.com
wrote:
This is an interesting topic. As per our discussions earlier, I suggest
that in the future we move to different serializers for each granule of our
deployment, so that we do not need to drag a lot of senseless data
On Jan 27, 2015, at 3:50 PM, Monty Taylor mord...@inaugust.com wrote:
I do not like how we are selecting names for our releases right now.
The current process is autocratic and opaque and not fun - which is the
exact opposite of what a community selected name should be.
Autocratic? Could
On 01/27/2015 03:55 PM, Douglas Mendizabal wrote:
Hi openstack-dev,
The barbican team would like to announce the release of
python-barbicanclient 3.0.2. This is a minor release that fixes a bug
in the pbr versioning that was preventing the client from working correctly.
The release is
-Original Message-
From: Michael Still [mailto:mi...@stillhq.com]
Sent: Wednesday, January 28, 2015 7:41 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [nova] Nominating Melanie Witt for
python-novaclient-core
Greetings,
I would like to nominate Melanie
Hi all
After having a look at the stats:
http://stackalytics.com/report/contribution/heat-group/90
http://stackalytics.com/?module=heat-groupmetric=person-day
I'd like to propose the following changes to the Heat core team:
Add:
Qiming Teng
Huang Tianhua
Remove:
Bartosz Górski (Bartosz has
Hi list,
I have some questions.
Hope can get help from you guys.
Manila has two driver modes.
For handle share server drivers, the share-network is easy to understand.
For not handle share-servers drivers, manila request admin to do everything
before manila-share service start, and when the
On 01/27/2015 06:05 PM, Jonathan Bryce wrote:
On Jan 27, 2015, at 3:50 PM, Monty Taylor mord...@inaugust.com wrote:
I do not like how we are selecting names for our releases right now.
The current process is autocratic and opaque and not fun - which is the
exact opposite of what a community
Hi John
Thank you so much.
My apologies for bp isn't lined for review, I have used wrong git format.
It's fixed now.
Best
Nachi
2015-01-28 2:39 GMT+09:00 John Garbutt j...@johngarbutt.com:
Hi,
Apologies, we can re-approve that because your code was up before the
deadline.
I was unable to
Hey Monty,
I’d like to weigh in here, because I think there have been some
misunderstandings around Lemming-gate. I’m glad you raised your concerns; it’s
a good test of release naming for us all to discuss and learn from.
To provide a little context for those new to the discussion,
Here is one that is more complete:
https://gist.github.com/harlowja/e22e8c0771b336ca392f
Using a really simple requirement set that will not work:
$ cat test.txt
taskflow
networkx1.5
Running the above gist on that (and waiting for a while; since it does
do a lot of backtracking and trying of
On 01/27/2015 05:21 PM, Sean Dague wrote:
On 01/27/2015 03:55 PM, Douglas Mendizabal wrote:
Hi openstack-dev,
The barbican team would like to announce the release of
python-barbicanclient 3.0.2. This is a minor release that fixes a bug
in the pbr versioning that was preventing the client
Btw try this on 'pip6' (for those that want to); Pip 6+ moved some of
the code around that this uses; for feel to update it though and adjust
it to find where the new stuff is :-P
Joshua Harlow wrote:
Here is one that is more complete:
https://gist.github.com/harlowja/e22e8c0771b336ca392f
Hi,
I have seen Sean Dague's patch [1], if I understood correctly, by this
patch we can reduce the number of DEVSTACK_GATE variables that we need.
Trying to follow this patch to configure my gate job
DEVSTACK_GATE_GLUSTERFS [2].
I am not able to figure out the way to use this patch [1].
+1
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Tue, Jan 27, 2015 at 2:44 PM, Stanislaw Bogatkin sbogat...@mirantis.com
wrote:
+1
On Tue, Jan 27, 2015 at 4:05 PM, Aleksandr Didenko adide...@mirantis.com
wrote:
Hi,
After starting implementing granular deployment
+1 to simple mode removal
On Tue, Jan 27, 2015 at 4:44 PM, Stanislaw Bogatkin sbogat...@mirantis.com
wrote:
+1
On Tue, Jan 27, 2015 at 4:05 PM, Aleksandr Didenko adide...@mirantis.com
wrote:
Hi,
After starting implementing granular deployment we've faced a bunch of
issues that would
- Original Message -
From: Vladik Romanovsky vladik.romanov...@enovance.com
To: openstack-dev@lists.openstack.org
Hi everyone,
Following Steve Gordon's email [1], regarding CI for NUMA, SR-IOV, and other
features, I'd like to start a discussion about the NUMA testing in
On 01/27/2015 12:18 AM, Silvan Kaiser wrote:
Hello!
Do dependencies required only in some contexts belong into requirements.txt?
Yesterday we had a short discussion on #openstack-nova regarding how to
handle optional requirements. This was triggered by our quobyte nova
driver
On 1/27/2015 2:18 AM, Silvan Kaiser wrote:
Hello!
Do dependencies required only in some contexts belong into requirements.txt?
Yesterday we had a short discussion on #openstack-nova regarding how to
handle optional requirements. This was triggered by our quobyte nova
driver
On 01/27/2015 05:19 PM, Jim Meyer wrote:
+1 all the way down.
More fun double-plus-good.
—j
On Jan 27, 2015, at 1:50 PM, Monty Taylor mord...@inaugust.com wrote:
I do not like how we are selecting names for our releases right now.
The current process is autocratic and opaque and not fun -
Monty Taylor mord...@inaugust.com writes:
I do not like how we are selecting names for our releases right now.
The current process is autocratic and opaque and not fun - which is the
exact opposite of what a community selected name should be.
I propose:
* As soon as development starts on
On Wed, Jan 28, 2015 at 9:11 AM, Michael Still mi...@stillhq.com wrote:
Greetings,
I would like to nominate Melanie Witt for the python-novaclient-core team.
(What is python-novaclient-core? Its a new group which will contain
all of nova-core as well as anyone else we think should have core
Greetings,
I would like to nominate Melanie Witt for the python-novaclient-core team.
(What is python-novaclient-core? Its a new group which will contain
all of nova-core as well as anyone else we think should have core
reviewer powers on just the python-novaclient code).
Melanie has been
On 01/27/2015 02:41 PM, Michael Still wrote:
Greetings,
I would like to nominate Melanie Witt for the python-novaclient-core team.
(What is python-novaclient-core? Its a new group which will contain
all of nova-core as well as anyone else we think should have core
reviewer powers on just
On Tue, Jan 27, 2015, at 12:06 PM, victor stinner wrote:
Hi,
What is the Python bug? Do you have a reference to the bug report and the
patch?
http://bugs.python.org/issue21435
Python 3.4.3 release schedule:
3.4.3rc1 will be tagged Saturday February 7 and released Sunday February
8.
Please respond with +1s or any concerns.
+1
--Dan
signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
+1
-Original Message-
From: Dan Smith [mailto:d...@danplanet.com]
Sent: Tuesday, January 27, 2015 3:31 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] Nominating Melanie Witt for
python-novaclient-core
Please respond with +1s or
As I understand it, novaclient would by default not pass the microversion
HTTP header (X-OpenStack-Compute-API-Version) so it would get the server's
MIN_VERSION, ie 2.1 for the foreseeable future. It would be
straightforward to add something like a --api-version=xx command line
argument, or it
On Tue, Jan 27, 2015 at 3:52 PM, Sean Dague s...@dague.net wrote:
On 01/27/2015 02:41 PM, Michael Still wrote:
Greetings,
I would like to nominate Melanie Witt for the python-novaclient-core
team.
(What is python-novaclient-core? Its a new group which will contain
all of nova-core
+1 all the way down.
More fun double-plus-good.
—j
On Jan 27, 2015, at 1:50 PM, Monty Taylor mord...@inaugust.com wrote:
I do not like how we are selecting names for our releases right now.
The current process is autocratic and opaque and not fun - which is the
exact opposite of what a
The network info for an instance is cached as a blob of data (neutron has the
canonical version in most installs), so it isn’t particularly easy to do at the
database layer. You would likely need a pretty complex stored procedure to do
it accurately.
Vish
On Jan 27, 2015, at 2:00 PM, Steven
Hello all,
You may know that for deployment configuration we are serializing
additional prefix for controller role (primary), with the goal of
deployment order control (primary-controller always should be deployed
before secondaries) and some condiions in fuel-library code.
However, we cannot
Hi openstack-dev,
The barbican team would like to announce the release of python-barbicanclient
3.0.2. This is a minor release that fixes a bug in the pbr versioning that was
preventing the client from working correctly.
The release is available on PyPI
Andrew is right about our ability to upgrade packages on a system using
yum update or apt-get upgrade because IBP installs standalone OS
(unlike cloud case). Even more, we'll build Ubuntu images on a master node
by 6.1 and of course we'll be able to use actual repo for that.
Vladimir Kozhukalov
Doug Hellmann wrote:
On Mon, Jan 26, 2015, at 12:02 PM, Thierry Carrez wrote:
[...]
I'm open to alternative suggestions on where the list of tags, their
definition and the list projects they apply to should live. If you don't
like that being in the governance repository, what would have your
Hi Steve,
I can host it.
Regards
Marc
Am 27.01.2015 um 08:40 schrieb Steve Gordon sgor...@redhat.com:
Hi all,
As mentioned in the notes from last week's meeting I am going to be in
transit during our 1400 UTC meeting this Wednesday (28th) [1]. Is anyone else
willing and able to
I think the consensus was found and the resolution is positive.
26 січ. 2015 о 14:37 Tomasz Napierala tnapier...@mirantis.com написав(ла):
+1
On 26 Jan 2015, at 11:33, Roman Prykhodchenko m...@romcheg.me wrote:
Hi Guys,
According to our previous thread [1] and the decision made
The proposed monitoring options make sense, since the Fuel master has nothing
yet, but I would like to ressurect this thread to see if we can discuss some
strategies in order to avoid the /var/log fillup with consequent docker
containers corruption.
Now, a customer facing this corruption can
Guys,
First, we are not talking about deliberate disabling preseed based approach
just because we so crazy. The question is What is the best way to achieve
our 6.1 goals? We definitely need to be able to install two versions of
Ubuntu 12.04 and 14.04. Those versions have different sets of
On Tue, Jan 27, 2015 at 7:00 PM, Dmitry mey...@gmail.com wrote:
I have another question, is it possible to get the stack name in the hot
script?
E.g.
params:
$stack_name: {get_global_variable: $stack.name}
See:
Hi Sean,
Thanks for the heads up, and for adding the stable-compat-jobs to the client.
[1] This is an interesting problem, since the proposal bot keeps the
python-barbicanclient requirements in sync with global-requirements. I’m not
sure what the correct fix for this is?
- Doug
[1]
On 01/27/2015 06:39 PM, Li, Chen wrote:
Hi list,
I have some questions.
Hope can get help from you guys.
Manila has two driver modes.
For handle share server drivers, the share-network is easy to understand.
For not handle share-servers drivers, manila request admin to do
everything
On 1/27/2015 4:41 PM, Michael Still wrote:
Greetings,
I would like to nominate Melanie Witt for the python-novaclient-core team.
(What is python-novaclient-core? Its a new group which will contain
all of nova-core as well as anyone else we think should have core
reviewer powers on just the
On 1/15/2015 5:41 PM, Sean Dague wrote:
On 01/15/2015 06:25 PM, Joe Gordon wrote:
We can side step the dependency graphing and ordering issue by looking
at the list of curently installed packages via pip freeze and not
installing dependencies (pip install --no-deps)
After looking into this
Hi all
After having a look at the stats:
http://stackalytics.com/report/contribution/heat-group/90
http://stackalytics.com/?module=heat-groupmetric=person-day
I'd like to propose the following changes to the Heat core team:
Add:
Qiming Teng
Huang Tianhua
Remove:
Bartosz Górski
+1
Pavlo Shchelokovskyy
Software Engineer
Mirantis Inc
www.mirantis.com
On Wed, Jan 28, 2015 at 8:26 AM, Thomas Herve thomas.he...@enovance.com
wrote:
Hi all
After having a look at the stats:
http://stackalytics.com/report/contribution/heat-group/90
Hi, Travis
Thanks for your reply. I think I'm more talking about the resource
constraints instead of behavior constraints. My example like serial_port_count,
memory_pagesize, hw_numa_nodes etc are all requires resources. Sorry for the
confusion. If image property requires resource
Sorry for slow response, this mail is lost in the mail flood.
For the pre-datastructure code, I think there have been some discussion on it,
like https://wiki.openstack.org/wiki/VirtDriverImageProperties or
https://bugs.launchpad.net/nova/+bug/1275875 . But I do agree that we should
enhance it
Gentlemen,
I have one small question about IBP, and I'm not sure if this is the right
place to ask, but still: how do you plan to build the images for the
image-based provisioning? Will you leverage diskimage-builder
https://github.com/openstack/diskimage-builder or some other tool?
Thanks,
--
Hi Rajdeep,
This may be because of some configuration mismatch. I had same ImportError
while uploading my Cinder Driver during devstack installation, so to deal
with that I have rechecked my logs again and found that the mistake was in
my cinder.conf file, so I think that might be the same case
+1
From: Michael Still [mi...@stillhq.com]
Sent: Tuesday, January 27, 2015 5:41 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [nova] Nominating Melanie Witt for
python-novaclient-core
Greetings,
I would like to nominate Melanie
The infra team has been working hard to update our Python 3 testing for all
projects to run on 3.4 instead of 3.3. Two of the last projects to be able to
shift are oslo.messaging and oslo.rootwrap. The test suites for both projects
trigger a segfault bug in the 3.4 interpreter as it is shipped
On Mon, Jan 26, 2015, at 06:57 PM, Angus Salkeld wrote:
On Tue, Jan 27, 2015 at 8:05 AM, Doug Hellmann d...@doughellmann.com
wrote:
We’ve held up the oslo.messaging release with the namespace package work
for a while now while we work with the nova, designate, and heat teams to
fix
On Thu, Jan 15, 2015 at 8:56 PM, Doug Hellmann d...@doughellmann.com
wrote:
On Jan 15, 2015, at 1:30 PM, Denis Makogon dmako...@mirantis.com
wrote:
Good day to All,
The question that i’d like to raise here is not simple one, so i’d like
to involve as much readers as i can. I’d like
Hi Xarses,
Actually it is multi-hypervisor environment. The error in the nova.log is:
NetworkNotFoundForBridge: Network could not be found for bridge br-int
the above error disappears changing the mech driver order in
/etc/neutron/plugins/ml2/ml2_conf.ini file from mechanism_drivers =
Hi the merge fail error that we reported in ubuntu 12.04 has been solved in
the new ubuntu 14.04 CI master setup.
many thanks to ramy on the update of the repo :)
https://github.com/rasselin/os-ext-testing
cheers!
On Fri, Jan 16, 2015 at 4:58 PM, Punith S punit...@cloudbyte.com wrote:
Hi
Hi the merge fail error that we reported in ubuntu 12.04 has been solved in
the new ubuntu 14.04 CI master setup.
many thanks to ramy on the update of the repo :)
https://github.com/rasselin/os-ext-testing
cheers!
On Thu, Jan 8, 2015 at 7:16 PM, Punith S punit...@cloudbyte.com wrote:
hi,
Hi,
After starting implementing granular deployment we've faced a bunch of
issues that would make further development of this feature much more
complicated if we have to support both Simple and HA deployment modes. For
example: simple mode does not require cluster (corosync, pacemaker, vips,
Punith,
I think it’s because when you installed fresh again on 14.04, the zuul
GitPython dependency was updated to the latest.
I proposed this zuul patch to fix it: https://review.openstack.org/#/c/149336/
Ramy
From: Punith S [mailto:punit...@cloudbyte.com]
Sent: Tuesday, January 27, 2015
On 01/27/2015 07:14 AM, Matt Riedemann wrote:
On 1/27/2015 2:18 AM, Silvan Kaiser wrote:
Hello!
Do dependencies required only in some contexts belong into
requirements.txt?
Yesterday we had a short discussion on #openstack-nova regarding how to
handle optional requirements. This was triggered
On 01/27/2015 02:18 AM, Silvan Kaiser wrote:
Hello!
Do dependencies required only in some contexts belong into requirements.txt?
Yesterday we had a short discussion on #openstack-nova regarding how to
handle optional requirements. This was triggered by our quobyte nova driver
FYI, it wasn’t a change to my repo, but to openstack upstream that solved the
12.04 -- 14.04 issue: https://review.openstack.org/#/c/141518/
So this will help anyone using the Openstack-Infra zuul puppet modules!
Ramy
From: Punith S [mailto:punit...@cloudbyte.com]
Sent: Tuesday, January 27, 2015
On Tue, Jan 27, 2015 at 07:12:29AM -0800, Sean Dague wrote:
On 01/27/2015 12:18 AM, Silvan Kaiser wrote:
Hello!
Do dependencies required only in some contexts belong into requirements.txt?
Yesterday we had a short discussion on #openstack-nova regarding how to
handle optional
1 - 100 of 124 matches
Mail list logo
