Dims,
There are some problems with exception hierarchy which need to be fixed.
-Original Message-
From: Davanum Srinivas [mailto:dava...@gmail.com]
Sent: Tuesday, June 09, 2015 7:32 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev]
Hey everybody!
I've started the poll for the M release. By now, you should have gotten
an email with a link to the vote. If you did not and think that you
should have, please let me know (directly, not to the mailing list
please) and I can re-send and/or fix as necessary.
Please remember that
On 06/11/2015 10:08 AM, Duncan Thomas wrote:
On 11 June 2015 at 10:26, Thomas Goirand z...@debian.org
mailto:z...@debian.org wrote:
Hi,
The current maintainer of suds in Debian sent bug reports against all
packages depending on it. We would like to get rid of suds completely.
On 06/11/2015 11:31 PM, Nikhil Manchanda wrote:
Hi Thomas:
I just checked and I don't see suds as a requirement for trove.
I don't think it should be a requirement for the trove debian package,
either.
Thanks,
Nikhil
Hi,
I fixed the package and removed the Suggests: python-suds in both
-Original Message-
From: Joshua Harlow [mailto:harlo...@outlook.com]
Sent: 14 June 2015 07:52
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] Where are all the research papers?
Out of curiosity is there any known listing of papers (like ACM
Sorry for the long delay. This is fixed in oslo.vmware 0.9.0.
https://github.com/openstack/oslo.vmware/commit/a229faf8ba59724a4fda3f37d5a7473376f93d9c
From: hao wang [mailto:sxmatch1...@gmail.com]
Sent: Saturday, May 30, 2015 12:40 PM
To: openstack-dev@lists.openstack.org
Subject:
Thanks for doing this!
On 6/13/15, 4:26 AM, Jeremy Stanley fu...@yuggoth.org wrote:
Our maintenance has concluded successfully without incident and the
accompanying Gerrit outage was roughly an hour.
We moved 57 repositories to new Git namespaces:
stackforge/cookbook-openstack-bare-metal
Last week was a really bad week for TripleO CI. Several breaking
changes (2 of which Fedora package related) kept at least a subset of
the jobs down for over half the week. Here is a brief summary of the
issues we hit along with links to some of the work arounds.
Fedora 21: python-address package
Hi Salvatore,
Thanks for the comments, added some more information.
Gal
On Sun, Jun 14, 2015 at 7:58 PM, Salvatore Orlando sorla...@nicira.com
wrote:
Gal,
thanks for this summery.
Some additional info inline.
Salvatore
On 12 June 2015 at 19:38, Gal Sagie gal.sa...@gmail.com wrote:
+1
From: Akihiro MOTOKI amot...@gmail.commailto:amot...@gmail.com
Reply-To: OpenStack List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Friday, June 12, 2015 at 8:20 AM
To: OpenStack List
Tim Bell wrote:
-Original Message-
From: Joshua Harlow [mailto:harlo...@outlook.com]
Sent: 14 June 2015 07:52
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] Where are all the research papers?
Out of curiosity is there any known listing of
+1 most definitely!
On Saturday, June 13, 2015, Kevin Carter kevin.car...@rackspace.com wrote:
Hello,
I would like to nominate Ian Cordasco (sigmavirus24 on IRC) for the
os-ansible-deployment-core team. Ian has been contributing to the OSAD
project for some time now and has always had
Hi,
I agree with Vipin. Can we please address the exception handling. We
already have the patches.
Thanks
Gary
On 6/14/15, 12:41 PM, Vipin Balachandran vbalachand...@vmware.com
wrote:
Dims,
There are some problems with exception hierarchy which need to be fixed.
-Original Message-
+1
From: Kevin Benton blak...@gmail.commailto:blak...@gmail.com
Reply-To: OpenStack List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Thursday, June 11, 2015 at 9:15 PM
To: OpenStack List
Hey folks,
I am proposing Harm Waites for the Kolla core team. He did a fantastic job
implementing Designate in a container[1] which I’m sure was incredibly
difficult and never gave up even though there were 13 separate patch reviews :)
Beyond Harm’s code contributions, he is responsible for
+1
On 6/13/15, 1:41 AM, Carl Baldwin c...@ecbaldwin.net wrote:
+1!
On Fri, Jun 12, 2015 at 1:44 PM, Kevin Benton blak...@gmail.com wrote:
Hello!
As the Lieutenant of the built-in control plane[1], I would like
Rossella
Sblendido to be a member of the control plane core reviewer team.
Her
Gal,
thanks for this summery.
Some additional info inline.
Salvatore
On 12 June 2015 at 19:38, Gal Sagie gal.sa...@gmail.com wrote:
Hello All,
I wanted to share some of our next working items and hopefully get more
people on board with the project.
I personally would mentor any new comer
Hi Joshua,
An example of some specs already doing this (they are built using the
cheetah template engine/style):
https://github.com/stackforge/anvil/tree/master/conf/templates/packaging/specs
They are turned into 'normal' spec files (the compilation part)
during build time.
Right, I
On 12 June 2015 at 16:58, Henry Gessau ges...@cisco.com wrote:
On Thu, Jun 11, 2015, Salvatore Orlando sorla...@nicira.com wrote:
Finally, I received queries from several community members that would be
keen
on helping supporting this microversioning effort. I wonder if the PTL
and the
Since there were no objections, and as a follow-up I’ve created a BP for that
in murano: https://blueprints.launchpad.net/murano/+spec/add-shellcheck-jobs
--
Kirill Zaitsev
Murano team
Software Engineer
Mirantis, Inc
On 10 Jun 2015 at 18:07:19, Filip Blaha (filip.bl...@hp.com) wrote:
Thanks
hi magnum team,
I am planing to add periodic task for magnum conductor service, it will
be good
to sync task status with heat and container service. and I have already
have a WIP
patch[1], I'd like to start a discussion on the implement.
Currently, conductor service is an rpc server, and it
On 12 June 2015 at 12:22, Sean Dague s...@dague.net wrote:
On 06/11/2015 06:03 PM, Salvatore Orlando wrote:
As most of you already know, work is beginning to move forward on the
micro-versioned Neutron API, for which a specification is available at
[1]
From a practical perspective there
With respect to using a seed - the facility to supply one to the
rebalance operation has recently been added to puppet-swift master
branch (commit b8b4434), however the seed parameter is not available to
any of the usual calling methods (this looks to be deliberate from the
commit message), so
Hi All,
This is to bring the blueprint secure-kubernetes
https://blueprints.launchpad.net/magnum/+spec/secure-kubernetes in
discussion.
I have been trying to figure out what could be the possible change area to
support this feature in Magnum. Below is just a rough idea on how to
proceed further
Just put here for more comments, thanks!
IMHO, there are three different options, worth discussion before the
designing:
#Opt 1: Magnum as the API. The entire driver layer still leverages the
third-party solutions like swarm or kubernetes, then we have to keep
compatible with their limitation in
On 06/13/2015 01:37 PM, Rich Megginson wrote:
On 06/12/2015 07:30 PM, Adam Young wrote:
On 06/12/2015 04:53 PM, Rich Megginson wrote:
I've done a first pass of setting up a puppet module to configure
Keystone to use ipsilon for federation, using
On Fri, Jun 12, 2015 at 8:51 AM, Ildikó Váncsa ildiko.van...@ericsson.com
wrote:
Hi,
Since we reopened the review for this blueprint we’ve got a large number
of comments. It can be clearly seen that the original proposal has to be
changed, although it still requires some discussion to
I think option #3 is the most desired choice in performance’s point of view,
because magnum is going to support multiple conductors and all conductors share
the same DB. However, if each conductor runs its own thread for periodic task,
we will end up to have multiple instances of tasks for
On 12 June 2015 at 10:49, ZZelle zze...@gmail.com wrote:
Indeed, the doc[1] is unclear
git-review can be installed using: python setup.py install or pip install .
Of those two things we only support pip install . - in part because
you have much less control over mirrors, proxies and inferior
29 matches
Mail list logo