Hi Serg,
On 06/17/2015 05:35 AM, Serg Melikyan wrote:
Hi Emilien,
I would like to answer your question regarding
stackforge/puppet-murano repository asked in different thread:
Someone from Fuel team created first the module in Fuel, 6 months ago
[1] and 3 months later someone from Fuel
On 17 June 2015 at 15:36, Dmitry Guryanov dgurya...@parallels.com wrote:
On 06/17/2015 02:14 PM, Duncan Thomas wrote:
On 17 June 2015 at 00:21, Matt Riedemann mrie...@linux.vnet.ibm.com
mailto:mrie...@linux.vnet.ibm.com wrote:
The NFS, GlusterFS, SMBFS, and Quobyte libvirt volume
On 06/17/2015 12:21 AM, Matt Riedemann wrote:
The NFS, GlusterFS, SMBFS, and Quobyte libvirt volume drivers are all
very similar.
I want to extract a common base class that abstracts some of the
common code and then let the sub-classes provide overrides where
necessary.
As part of this, I'm
Have you checked the blueprint for this at:
https://review.openstack.org/#/c/189445/.
Hope that helps.
Regards,
Mariam.
From: 李田清 tianq...@unitedstack.com
To: openstack-dev openstack-dev@lists.openstack.org
Date: 06/17/2015 02:06 AM
Subject:[openstack-dev]
On 06/17/2015 02:14 PM, Duncan Thomas wrote:
On 17 June 2015 at 00:21, Matt Riedemann mrie...@linux.vnet.ibm.com
mailto:mrie...@linux.vnet.ibm.com wrote:
The NFS, GlusterFS, SMBFS, and Quobyte libvirt volume drivers are
all very similar.
I want to extract a common base class that
Every day I get an email about broken dependencies for the group-based
policy Heat plugin in Fedora (openstack-heat-gbp), because the version
of Heat it depends on is capped. Two points:
1) Would whoever maintains that package (Bob?) please fix it :)
2) Why was this plugin not submitted to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/17/2015 08:53 AM, Emilien Macchi wrote:
Hi Serg,
On 06/17/2015 05:35 AM, Serg Melikyan wrote:
Hi Emilien,
I would like to answer your question regarding
stackforge/puppet-murano repository asked in different thread:
Someone from
Thank you for sharing link to list of things that new module should
satisfy to! It will be really helpful even if list will change over
time. At least we have pointers how to start making our module
compliant.
Regarding figuring out permissions - I don't mind if we will set
puppet-core as group
On 06/17/2015 09:50 AM, Serg Melikyan wrote:
Thank you for sharing link to list of things that new module should
satisfy to! It will be really helpful even if list will change over
time. At least we have pointers how to start making our module
compliant.
Regarding figuring out permissions
Hi Zhenzan,
Yes the oslo.messaging integration task is relevant--oslo.messaging is one
way of achieving cross-process, cross-host messaging. So I'll count you as
interested for the mid-cycle sprint.
Have you looked at the API call that forces a datasource driver to pull
immediately? See
On Tue, Jun 16, 2015 at 8:20 AM, Jay Pipes jaypi...@gmail.com wrote:
Adding -dev because of the reference to the Neutron Get me a network
spec. Also adding [nova] and [neutron] subject markers.
Comments inline, Kris.
On 05/22/2015 09:28 PM, Kris G. Lindgren wrote:
During the Openstack
On 6/16/2015 5:56 PM, Michael Still wrote:
I don't think you need a spec for this (its a refactor). That said,
I'd be interested in exploring how you deprecate the old flags. Can
you have more than one deprecated name for a single flag?
Michael
On Wed, Jun 17, 2015 at 7:29 AM, Matt Riedemann
Hi,
We are preparing a new Juno sub-release.
You can see the status of this work here:
https://etherpad.openstack.org/p/puppet-juno-5.1.0-release
All modules having stable/juno will be released 5.1.0 both in OpenStack
and Puppet forge.
Regards,
--
Emilien Macchi
signature.asc
Description:
Excerpts from Ramakrishnan G's message of 2015-06-17 12:50:25 +0530:
Seems to me like we can keep ironic-lib git repository as a git submodule
of the ironic and ironic-python-agent repositories. Any commit in Ironic
or Ironic-python-agent can change ironic-lib independently. Also, looks
like
Hey,
Thanks for your work guys.
What about kilo release? Is it plan as well? Last summit, you mentioned
that it could be released for end of june?
Cheers,
Arnaud.
On 17/06/2015 15:57, Emilien Macchi wrote:
Hi,
We are preparing a new Juno sub-release.
You can see the status of this work
On 06/17/2015 06:30 AM, Lucas Alvares Gomes wrote:
overlap there rather than competition), how crazy does it sound if we say
that for OpenStack Nova is the compute API and Ironic the Bare Metal API and
so on? Would that be an unacceptable power grab?
It's not that it's unacceptable, but I
Hi!
I work for an events market research company and am in need of recruiting young
developers in the San Francisco Bay Area to answer a short survey to see if
they qualify for an in-depth interview regarding an upcoming developer event in
San Francisco. Is this something I can post your page
On Tue, 16 Jun 2015, Sean Dague wrote:
I'd expect nova to be running on http://localhost/compute not
http://localhost:8774 when running under wsgi. That's going to probably
interestingly break a lot of weird assumptions by different projects,
but that's part of the reason for doing this
A few days ago, I was talking to Rossella, about the need of a RFE for
this [1],
in this case, it's an internal library/nicety for neutron development.
It's not a feature
from the user point of view. And it's not a very big change.
So, we thought that starting by a simple devref to agree on,
Hello,
Right now we can create one replication once, but it is not suitable for
redis. What we will do for this?
And if time permit can the assigner of redis replication tell about the process
for redis replication? Thanks a
Hi Carl,
I know you said at the end of your message below to ping you on IRC, but
there are details here that I'm not sure about, and some suggestions
that I'd like to make, and I think it will be clearer to discuss those
in context. I hope that's OK.
On 11/06/15 17:26, Carl Baldwin wrote:
While I didn't know about the Neutron mid-cycle being next week. I do happen
to live in Fort Collins, so I could easy become available if you want to talk
face-to-face about https://bugs.launchpad.net/neutron/+bug/1458890.
Kris Lindgren
Senior Linux
On Jun 16, 2015, at 14:56, Thomas Goirand z...@debian.org wrote:
On 06/16/2015 12:06 PM, Thierry Carrez wrote:
It also removes the stupid encouragement to use all components from the
same date. With everything tagged at the same date, you kinda send the
message that those various things
On 06/16/2015 11:58 PM, Carl Baldwin wrote:
On Tue, Jun 16, 2015 at 5:17 PM, Kevin Benton blak...@gmail.com wrote:
There seems to be confusion on what causes deadlocks. Can one of you explain
to me how an optimistic locking strategy (a.k.a. compare-and-swap) results
in deadlocks?
Take the
On 06/17/2015 10:15 AM, Arnaud Morin wrote:
Hey,
Thanks for your work guys.
What about kilo release? Is it plan as well? Last summit, you mentioned
that it could be released for end of june?
And we're working hard on that:
https://etherpad.openstack.org/p/puppet-kilo-release
It should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/16/2015 05:58 PM, Mike Bayer wrote:
On 6/16/15 11:41 AM, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
- - instead of migrating data with alembic rules, migrate it in
runtime. There should be a abstraction
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/17/2015 11:27 AM, Anna Kamyshnikova wrote:
Ihar, thanks for bringing this up!
This is very interesting and I think it worth trying. I'm +1 on
that and want to participate in this work.
Awesome.
In fact a lot *not strict* migrations
Hello Solum Developers,
When we were designing the operator languagepack feature for Solum, we wanted
to make use of public urls to download operator LPs, such as those available
for CDN backed swift containers we have at Rackspace, or any publicly
accessible url. This would mean that when a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/17/2015 05:55 PM, Fox, Kevin M wrote:
The biggest issue we have run into with multiple public networks is
restricting which users can use which networks. We have the same
issue, where we may have an internal public network for the
Hi John,
We were trying to push a very similar spec to enhance the security group
API, we covered both DDoS case
and another use case for brute force prevention (We did a research to
identify common protocols login behaviour
in order to identify brute force attacks using iptables) and even some
Policy is supposed to allow access control to work across multiple
services and endpoints. However, each service has specified policy
differently.
Here are some of the basic working assumptions for policy enforcement we
can use to work towards consistent enforcement.
1) A policy rule
On Tue, 16 Jun 2015, Simon Pasquier wrote:
I'm still struggling to see how these optimizations would be implemented
since the current Gnocchi design has separate backends for indexing and
storage which means that datapoints (id + timestamp + value) and metric
metadata (tenant_id, instance_id,
Hi Adrian,
As an FYI, I took a shot at updating the OpenStack wiki view of the Roadmap for
Solum per IRC and developer collaboration, where good progress has been made
over the last cycle delivering on features that make Solum usable in a
production OpenStack system environment. This is, of
On 17/06/15 16:17, Kris G. Lindgren wrote:
See inline.
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy, LLC.
On 6/17/15, 5:12 AM, Neil Jerram neil.jer...@metaswitch.com wrote:
Hi Kris,
Apologies in advance for questions that are probably
Hi guys!
* Do not merge a patch without at least one review from both groups
* Collaborate to make the module compliant
I'm strongly agree with it, because it'll help to avoid some mistakes.
Also, someone from puppet-manager-core may to prompt what are we doing
wrong or better way for
As this Fri Jun 19th did not seem to have weight, I just express my opinion to
the mailing list for the records.
Personally I think this is bad idea, but as not being Glance Driver I can't say
how much need there is for such meeting. The specs should be raised during our
weekly meeting and/or
Hachem a laissé un message pour toi
Tu peux immédiatement répondre via notre messagerie instantanée. Voir tes
messages...
http://eu1.badoo.com/0322198318/in/KMLZfBmG1ho/?lang_id=6g=57-0-4m=61mid=55818daf0006004d0591faaf003ada3301a6
D'autres personnes attendent :
Les liens ne
On Wed, Jun 17, 2015 at 9:08 AM, John Griffith john.griffi...@gmail.com
wrote:
On Tue, Jun 16, 2015 at 8:20 AM, Jay Pipes jaypi...@gmail.com wrote:
Adding -dev because of the reference to the Neutron Get me a network
spec. Also adding [nova] and [neutron] subject markers.
Comments inline,
Great! I'll reach out to you in unicast mode on this Kris, thanks!
On Wed, Jun 17, 2015 at 10:27 AM, Kris G. Lindgren klindg...@godaddy.com
wrote:
While I didn't know about the Neutron mid-cycle being next week. I do
happen to live in Fort Collins, so I could easy become available if you
Ihar Hrachyshka wrote:
On 06/17/2015 05:40 PM, Douglas Mendizábal wrote:
I tend to agree with Thomas that plan D is not ideal. For one, it
prevents changes to the stable branch that span multiple CRs, since
a two patch change would generate two tags and there would be no
clear indication
On 2015-06-17 10:10:22 -0400 (-0400), Doug Hellmann wrote:
Excerpts from Ramakrishnan G's message of 2015-06-17 12:50:25 +0530:
Seems to me like we can keep ironic-lib git repository as a git submodule
of the ironic and ironic-python-agent repositories. Any commit in Ironic
or
On 6/17/2015 8:14 AM, Duncan Thomas wrote:
On 17 June 2015 at 15:36, Dmitry Guryanov dgurya...@parallels.com
mailto:dgurya...@parallels.com wrote:
On 06/17/2015 02:14 PM, Duncan Thomas wrote:
On 17 June 2015 at 00:21, Matt Riedemann
mrie...@linux.vnet.ibm.com
On 6/17/2015 7:36 AM, Dmitry Guryanov wrote:
On 06/17/2015 12:21 AM, Matt Riedemann wrote:
The NFS, GlusterFS, SMBFS, and Quobyte libvirt volume drivers are all
very similar.
I want to extract a common base class that abstracts some of the
common code and then let the sub-classes provide
On 17 June 2015 at 17:19, Thierry Carrez thie...@openstack.org wrote:
Ihar Hrachyshka wrote:
On 06/17/2015 05:40 PM, Douglas Mendizábal wrote:
I tend to agree with Thomas that plan D is not ideal. For one, it
prevents changes to the stable branch that span multiple CRs, since
a two patch
On 6/17/2015 4:46 AM, Daniel P. Berrange wrote:
On Tue, Jun 16, 2015 at 04:21:16PM -0500, Matt Riedemann wrote:
The NFS, GlusterFS, SMBFS, and Quobyte libvirt volume drivers are all very
similar.
I want to extract a common base class that abstracts some of the common code
and then let the
I agree with Rob in terms of tooling and with Travis on rules.Any linting tool is fine with me as long as it does not break the rules we currently have set in Horizon. I believe the rules right now are general enough, so switching to eslint might not be an issue, but its something to look into.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I tend to agree with Thomas that plan D is not ideal. For one, it
prevents changes to the stable branch that span multiple CRs, since a
two patch change would generate two tags and there would be no clear
indication that the first patch should not
On Tue, Jun 16, 2015 at 3:33 PM, Jordan Pittier jordan.pitt...@scality.com
wrote:
On Thu, Apr 9, 2015 at 6:10 PM, Eric Blake ebl...@redhat.com wrote:
On 04/08/2015 11:22 PM, Deepak Shetty wrote:
+ [Cinder] and [Tempest] in the $subject since this affects them too
On Thu, Apr 9, 2015 at
Do consider another use case, that of a private docker cluster...
I may want to use magnum to deploy a docker cluster in a private neutron
network for a mid/backend tier as a component of a larger scalable cloud
application. Floating ip's would not be used in this case since the machines
that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/17/2015 05:40 PM, Douglas Mendizábal wrote:
I tend to agree with Thomas that plan D is not ideal. For one, it
prevents changes to the stable branch that span multiple CRs, since
a two patch change would generate two tags and there would
Without getting into the details from the etherpad [1], a few of us in
IRC today were talking about how the ceilometer compute-agent polls
libvirt directly for guest VM statistics and how ceilometer should
really be getting this information from nova via notifications sent from
a periodic task
Hello everyone:
I would like to test the waters on some new functionality we think is
needed to protect OpenStack deployments from some overload situations due to an
excessive user or DDOS scenario. We wrote this up in the style of an RFE.
Please let us know your thoughts and we can
Lisette Sheehan wrote:
I work for an events market research company and am in need of
recruiting young developers in the San Francisco Bay Area to answer a
short survey to see if they qualify for an in-depth interview regarding
an upcoming developer event in San Francisco. Is this something I
Excerpts from Doug Hellmann's message of 2015-06-16 15:55:04 -0400:
Excerpts from Thierry Carrez's message of 2015-06-16 11:45:51 +0200:
Doug Hellmann wrote:
[...]
I put together a little script [1] to try to count the previous
releases for projects, to use that as the basis for their
Emilien,
Thank you for your proposal, I completely agree with it:
* Move the module under the big tent
Proposed change in infra [1] and corresponding change in governance [2]
* Adding Puppet OpenStack group part of core permissions
I've added puppet-manager-core to puppet-murano-core
* Keep
The biggest issue we have run into with multiple public networks is restricting
which users can use which networks. We have the same issue, where we may have
an internal public network for the datacenter, but also, say, a DMZ network we
want to put some vm's on, but can't currently extend that
Hey there!
Yes, we are duplicating effort. I've spent quite a bit of effort over the
past few months landing features inside openstack that will make it
possible for a JavaScript client to be imported to horizon as a dependency.
This includes CORS, configuration, caching, infra tooling, etc, with
I was involved in the IRC discussion, but to reiterate here this would
be a wonderful thing to get done. The current polling can be terribly
inefficient, and the ceilo team is already looking into other ways to
reduce the impact of it. I'm looking forward to helping with this.
Cheers,
Jason
On
101 - 158 of 158 matches
Mail list logo
