Looking to put a proper implementation of instance backup into OpenStack.
Started by writing a simple set of baseline tests and running against the
stable/icehouse branch. They failed!
https://github.com/dreadedhill-work/openstack-backup-scripts
Scripts and configuration are in the above. Simple
Joe Gordon wrote:
On Thu, Aug 28, 2014 at 2:43 PM, Alan Kavanagh
alan.kavan...@ericsson.com mailto:alan.kavan...@ericsson.com wrote:
I share Donald's points here, I believe what would help is to
clearly describe in the Wiki the process and workflow for the BP
approval process
On Thu, Aug 28, 2014 at 03:44:25PM -0400, Jay Pipes wrote:
On 08/27/2014 09:04 PM, Dugger, Donald D wrote:
I’ll try and not whine about my pet project but I do think there is a
problem here. For the Gantt project to split out the scheduler there is
a crucial BP that needs to be implemented (
On Thu, Aug 28, 2014 at 04:27:59PM -0600, Chris Friesen wrote:
On 08/28/2014 04:01 PM, Joe Gordon wrote:
On Thu, Aug 28, 2014 at 2:43 PM, Alan Kavanagh
alan.kavan...@ericsson.com mailto:alan.kavan...@ericsson.com wrote:
I share Donald's points here, I believe what would help is to
Sean Dague wrote:
On 08/28/2014 03:06 PM, Jay Pipes wrote:
On 08/28/2014 02:21 PM, Sean Dague wrote:
On 08/28/2014 01:58 PM, Jay Pipes wrote:
On 08/27/2014 11:34 AM, Doug Hellmann wrote:
On Aug 27, 2014, at 8:51 AM, Thierry Carrez thie...@openstack.org
wrote:
Day 1. Cross-project sessions /
Anne Gentle wrote:
On Wed, Aug 27, 2014 at 7:51 AM, Thierry Carrez thie...@openstack.org
mailto:thie...@openstack.org wrote:
Hi everyone,
I've been thinking about what changes we can bring to the Design Summit
format to make it more productive. I've heard the feedback from the
On Fri, Aug 29, 2014 at 11:07:33AM +0200, Thierry Carrez wrote:
Joe Gordon wrote:
On Thu, Aug 28, 2014 at 2:43 PM, Alan Kavanagh
alan.kavan...@ericsson.com mailto:alan.kavan...@ericsson.com wrote:
I share Donald's points here, I believe what would help is to
clearly describe in
James Polley wrote:
However, Thierry pointed
to https://wiki.openstack.org/wiki/Governance/Foundation/Structure
which
still refers to Project Technical Leads and says explicitly that they
lead individual projects, not programs. I actually have edit access to
Hi, all
It seems that currently it's hard to backport any database schema fix to
Neutron [1] which uses alembic to manage db schema version. Nova has the
same issue before
and a workaround is to put some placeholder files before each release.
So first do we allow db schema fixes to be backport to
That all makes sense to me.
Doug Hellmann wrote:
Before Juno we set a deprecation policy for graduating libraries that said
the incubated versions of the modules would stay in the incubator repository
for one full cycle after graduation. This gives projects time to adopt the
libraries and
On 29/08/14 04:22, Richard Jones wrote:
Very recently I attempted to fix a simple bug in which a Panel was being
displayed when it shouldn't have been. The resultant 5-line fix ended up
breaking 498 of the 1048 unit tests in the suite. I estimated that it
would take about a week's effort to
On 08/28/2014 06:14 PM, Doug Hellmann wrote:
Before Juno we set a deprecation policy for graduating libraries that said
the incubated versions of the modules would stay in the incubator repository
for one full cycle after graduation. This gives projects time to adopt the
libraries and still
Going a bit further up the thread where we are still talking about
spec reviews and not code reviews...
On 28 August 2014 21:42, Dugger, Donald D donald.d.dug...@intel.com wrote:
I would contend that that right there is an indication that there's a problem
with the process.
We got two
Thanks for your thoughts Radomir. The nova api in question is memoized so
it'll only be called once per request. Caching it for longer would be a
very good idea, but that then brings into play deeper knowledge than I have
about how long to cache things like nova extension configuration. Also, I
On 28 August 2014 21:58, Chris Friesen chris.frie...@windriver.com wrote:
On 08/28/2014 02:25 PM, Jay Pipes wrote:
On 08/28/2014 04:05 PM, Chris Friesen wrote:
The overall scheduler-lib Blueprint is marked with a high priority
at http://status.openstack.org/release/;. Hopefully that would
If you are running version from a stable branch, changes in DB migrations
should generally be forbidden as the policy states since those migrations
are not likely to be executed again. Downgrading and then upgrading again
is extremely risky and I don't think anybody would ever do that.
However,
Hello, stackers. I'd like to start thread related to backuping procedure
for MagnetoDB, to be precise, for Cassandra backend.
In order to accomplish backuping procedure for Cassandra we need to
understand how does backuping work.
To perform backuping:
1.
We need to SSH into each node
Comments in-line @PCM
PCM (Paul Michali)
MAIL …..…. p...@cisco.com
IRC ……..… pcm_ (irc.freenode.com)
TW ………... @pmichali
GPG Key … 4525ECC253E31A83
Fingerprint .. 307A 96BB 1A4C D2C7 931D 8D2D 4525 ECC2 53E3 1A83
On Aug 28, 2014, at 11:57 AM, Sridhar Ramaswamy sric...@gmail.com wrote:
Hi, folks.
I was interested in the problem with storing of samples, that contain
complex resource_metadata, in MongoDB database [1].
If data is a dict that has a key(s) with dots (i.e. .), dollar signs (i.e.
$), or null characters,
it wouldn't be stored. It is happened because these characters
It seems that currently it's hard to backport any database schema fix to
Neutron [1] which uses alembic to manage db schema version. Nova has the
same issue before
and a workaround is to put some placeholder files before each release.
So first do we allow db schema fixes to be backport to
On 08/29/2014 06:54 AM, Salvatore Orlando wrote:
If you are running version from a stable branch, changes in DB
migrations should generally be forbidden as the policy states since
those migrations are not likely to be executed again. Downgrading and
then upgrading again is extremely risky and
Integrating bashate into something as complicated as devstack, the file
ignore problem has come up.
We seem to have 3 approaches out under review right now:
https://review.openstack.org/#/c/117425 : --exclude-dirs
https://review.openstack.org/#/c/115794 : --exclude-dirs (different
On Fri, 2014-08-29 at 11:23 +0200, Thierry Carrez wrote:
Anne Gentle wrote:
On Wed, Aug 27, 2014 at 7:51 AM, Thierry Carrez thie...@openstack.org
mailto:thie...@openstack.org wrote:
Hi everyone,
I've been thinking about what changes we can bring to the Design Summit
On Fri, Aug 29, 2014 at 7:42 AM, Sean Dague s...@dague.net wrote:
Integrating bashate into something as complicated as devstack, the file
ignore problem has come up.
We seem to have 3 approaches out under review right now:
https://review.openstack.org/#/c/117425 : --exclude-dirs
On Aug 29, 2014, at 7:23 AM, Alan Pevec ape...@gmail.com wrote:
It seems that currently it's hard to backport any database schema fix to
Neutron [1] which uses alembic to manage db schema version. Nova has the
same issue before
and a workaround is to put some placeholder files before each
Already done by xing-yang: https://review.openstack.org/#/c/117685/.
Thanks for raising this topic.
Regards,
Ivan Kolodyazhny,
Software Engineer,
Mirantis Inc.
On Fri, Aug 29, 2014 at 7:40 AM, John Griffith john.griff...@solidfire.com
wrote:
On Mon, Aug 25, 2014 at 8:47 PM, Clark Boylan
On Thu, Aug 28, 2014 at 11:12 PM, Brandon Logan
brandon.lo...@rackspace.com wrote:
Kyle,
Does this apply to blueprints that are destined for the incubator as
well? I assume the incubator does require a spec process too.
Incubator code still requires a spec, yes. For the things which are
Hello Denis,
Thank you for very useful knowledge sharing.
But I have one more question. As far as I understood if we have replication
factor 3 it means that our backup may contain three copies of the same
data. Also it may contain some not compacted sstables set. Do we have any
ability to compact
On 08/29/2014 08:53 AM, Dean Troyer wrote:
On Fri, Aug 29, 2014 at 7:42 AM, Sean Dague s...@dague.net
mailto:s...@dague.net wrote:
Integrating bashate into something as complicated as devstack, the file
ignore problem has come up.
We seem to have 3 approaches out under review
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/08/14 12:59, Tim Bell wrote:
-Original Message- From: Michael Still
[mailto:mi...@stillhq.com] Sent: 26 August 2014 22:20 To:
OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev]
While reviewing patches for moving response checking to the clients, I
noticed that there are places where client methods do not return any value.
This is usually, but not always, a delete method. IMO, every rest client
method should return at least the response. Some services return just
the
On Fri, Aug 29, 2014 at 4:29 PM, Dmitriy Ukhlov dukh...@mirantis.com
wrote:
Hello Denis,
Thank you for very useful knowledge sharing.
But I have one more question. As far as I understood if we have
replication factor 3 it means that our backup may contain three copies of
the same data. Also
On 08/29/2014 10:19 AM, David Kranz wrote:
While reviewing patches for moving response checking to the clients, I
noticed that there are places where client methods do not return any value.
This is usually, but not always, a delete method. IMO, every rest client
method should return at least the
On 08/29/2014 10:19 AM, David Kranz wrote:
While reviewing patches for moving response checking to the clients, I
noticed that there are places where client methods do not return any value.
This is usually, but not always, a delete method. IMO, every rest client
method should return at least
On 08/29/2014 10:56 AM, Sean Dague wrote:
On 08/29/2014 10:19 AM, David Kranz wrote:
While reviewing patches for moving response checking to the clients, I
noticed that there are places where client methods do not return any value.
This is usually, but not always, a delete method. IMO, every
Yeah, Sean's proposal looks great to me
On Fri, Aug 29, 2014 at 10:13 AM, David Kranz dkr...@redhat.com wrote:
On 08/29/2014 10:56 AM, Sean Dague wrote:
On 08/29/2014 10:19 AM, David Kranz wrote:
While reviewing patches for moving response checking to the clients, I
noticed that there
Yair,
I am very well plugged-in to this project and feeding the necessary
information to the weekly Tempest IRC meeting. In fact, since a few weeks
ago, I've made a point of sharing weekly with the Tempest team what I am
doing with the LBaaS team from the Tempest point of view.
Cheers
On Thu,
Hayes, Graham wrote:
Yep, I think this works in theory, the tough part will be when all the
incubating projects realize they're sending people for a single day?
Maybe it'll work out differently than I think though. It means fitting
ironic, barbican, designate, manila, marconi in a day?
On Aug 28, 2014, at 3:08 AM, Flavio Percoco fla...@redhat.com wrote:
Unfortunately, as Nataliia mentioned, we can't just get rid of it in
v1.1 because that implies a major change in the API, which would require
a major release. What we can do, though, is start working on a spec for
the V2 of
Stephen
See inline comments.
Susanne
-
Susanne--
I think you are conflating the difference between OpenStack incubation
and Neutron incubator. These are two very different matters and should be
treated separately. So, addressing each one
I agree with Brandon that it will be difficult to find spaces for Octavia,
and the pod is a valid option.
Nevertheless it is always worth trying.
For the traditional load balancing service instead I reckon #1 is a very
good thing to discuss. Problem is that it is also hard to conclude anything
in
I've updated the spec: https://review.openstack.org/#/c/116874/
Major change in this spec: get rid of unpacked upgrade tarball. Use only
lrzipped archives. It will save disk space and network traffic, it will
make upgrade process longer, it will make our upgrade tests longer as well,
it will make
On 08/29/2014 12:25 PM, Zane Bitter wrote:
On 28/08/14 17:02, Jay Pipes wrote:
I understand your frustration about the silence, but the silence from
core team members may actually be a loud statement about where their
priorities are.
I don't know enough about the Nova review situation to say
Kyle,
I am confused. So basically you (and Mark) are saying:
1) We deprecate Neutron LBaaS v1
2) We spin out Neutron LBaaS v2 into it's own project in stackforge
3) Users don't have an OpenStack LBaaS any longer until we graduate from
OpenStack incubation (as opposed Neutron incubation)
I am
Well, I think that there is a sign of a broken (or at least bent) process and
that's what I'm trying to expose. Especially given the ongoing conversations
over Gantt it seems wrong that ultimately it was rejected due to silence.
Maybe rejecting the BP was the right decision but the way the
I think the point is that if there were discussions that lead to
uncertainty about the split, they should have resulted in a - 1/-2 on the
spec instead of letting it sit there.
On Aug 29, 2014 9:46 AM, Jay Pipes jaypi...@gmail.com wrote:
On 08/29/2014 12:25 PM, Zane Bitter wrote:
On 28/08/14
I think this is now more about code reviews, but this is important...
On 29 August 2014 10:30, Daniel P. Berrange berra...@redhat.com wrote:
On Fri, Aug 29, 2014 at 11:07:33AM +0200, Thierry Carrez wrote:
Joe Gordon wrote:
On Thu, Aug 28, 2014 at 2:43 PM, Alan Kavanagh
Hi Dane,
Just wondering if you've made some progression on the matter :)
Regards,
Harm
op 19-08-14 19:08, Dane Leblanc (leblancd) schreef:
Hi Harm:
Unfortunately I haven't had time to complete the changes yet. Even
if/when these changes are completed, it's unlikely that this blueprint
All good points but I want to add an observation.
IRC seems to be the generic answer to all problems and, personally, I don't
think that's a good medium. Having to depend upon who just might be on IRC at
a particular moment seems rather hit or miss. I much prefer something like
email where I
On 28 August 2014 09:50, Markus Zoeller mzoel...@de.ibm.com wrote:
Jay Pipes jaypi...@gmail.com wrote on 08/27/2014 08:57:08 PM:
From: Jay Pipes jaypi...@gmail.com
To: openstack-dev@lists.openstack.org
Date: 08/27/2014 08:59 PM
Subject: Re: [openstack-dev] [nova] refactoring of
On Fri, Aug 29, 2014 at 9:02 AM, Sean Dague s...@dague.net wrote:
If pathspec did the right thing, pulling in the extra dep would be fine,
but it doesn't seem like it does.
After looking at it with fresh eyes, the issue could be resolved by
combining two methods from pathspec and still
On 28 August 2014 23:53, Joe Gordon joe.gord...@gmail.com wrote:
We just finished discussing when to open up Kilo specs at the nova meeting
today [0], and Kilo specs will open right after we cut Juno RC1 (around Sept
25th [1]). Additionally, the spec template will most likely be revised.
We
On 08/29/2014 02:48 AM, Preston L. Bannister wrote:
Looking to put a proper implementation of instance backup into
OpenStack. Started by writing a simple set of baseline tests and running
against the stable/icehouse branch. They failed!
Thanks Paul for your thoughts. See inline [SridharR] ...
On Fri, Aug 29, 2014 at 4:19 AM, Paul Michali (pcm) p...@cisco.com wrote:
Comments in-line @PCM
PCM (Paul Michali)
MAIL …..…. p...@cisco.com
IRC ……..… pcm_ (irc.freenode.com)
TW ………... @pmichali
GPG Key … 4525ECC253E31A83
On 7/29/2014 4:12 PM, Kyle Mestery wrote:
On Tue, Jul 29, 2014 at 3:50 PM, Nader Lahouti nader.laho...@gmail.com wrote:
Hi Kyle,
I have a BP listed in https://blueprints.launchpad.net/python-neutronclient
and looks like it is targeted for 3.0 (it is needed fro juno-3) The code is
ready and
Hi everyone,
In an effort to move the third party work into its own space, we've
created two new mailing lists:
Third-party-announce
This is where we will send announcements that third party operators
need to know about and when the OpenStack Infrastructure team disables
your account, with the
Drago,
It sounds like you convinced me to give D3.js a second chance :). I'll
experiment with what can be achieved using force-directed graph layout
combined with some composable svg object, hopefully this will save me
from placing objects on the canvas on my own.
I've read the barricade_Spec.js
On Fri 29 Aug 2014 12:47:00 PM PDT, Elizabeth K. Joseph wrote:
Third-party-request
This list is the new place to request the creation or modification of
your third party account. Note that old requests sent to the
openstack-infra mailing list don't need to be resubmitted, they are
already in
Hi Ajay,
looks like you need to use NeutronContext feature to configure Neutron
Networks during the benchmarks execution.
We now working on merge of two different comits with NeutronContext
implementation:
https://review.openstack.org/#/c/96300 and
https://review.openstack.org/#/c/103306
could
On 29/08/14 14:27, Jay Pipes wrote:
On 08/26/2014 10:14 AM, Zane Bitter wrote:
Steve Baker has started the process of moving Heat tests out of the
Tempest repository and into the Heat repository, and we're looking for
some guidance on how they should be packaged in a consistent way.
Apparently
On Fri, Aug 29, 2014 at 1:03 PM, Stefano Maffulli stef...@openstack.org wrote:
On Fri 29 Aug 2014 12:47:00 PM PDT, Elizabeth K. Joseph wrote:
Third-party-request
This list is the new place to request the creation or modification of
your third party account. Note that old requests sent to the
Does this look right.
{
VMTasks.boot_runcommand_delete: [
{
args: {
flavor: {
name: m1.small
},
image: {
name: Ubuntu Server 14.04
},
Stefano Maffulli stef...@openstack.org writes:
On Fri 29 Aug 2014 12:47:00 PM PDT, Elizabeth K. Joseph wrote:
Third-party-request
This list is the new place to request the creation or modification of
your third party account. Note that old requests sent to the
openstack-infra mailing list
Sorry here is the context
context: {
users: {
tenants: 1,
users_per_tenant: 1
}
neutron_network: {
network_cidr: 10.%s.0.0/16,
}
}
Because I see this
Issue fixed small syntax mistake in scenario file
Will now look into more details
Thx
From: akalambu akala...@cisco.commailto:akala...@cisco.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date:
On 08/28/2014 11:14 AM, Doug Hellmann wrote:
Before Juno we set a deprecation policy for graduating libraries that said
the incubated versions of the modules would stay in the incubator repository
for one full cycle after graduation. This gives projects time to adopt the
libraries and still
On 08/28/2014 12:34 PM, Doug Hellmann wrote:
On Aug 28, 2014, at 8:36 AM, Mark McLoughlin mar...@redhat.com wrote:
On Thu, 2014-08-28 at 13:24 +0200, Flavio Percoco wrote:
On 08/27/2014 03:35 PM, Ken Giusti wrote:
Hi All,
I believe Juno-3 is our last chance to get this feature [1]
Hi Timur
With this I was able to create networks and attach VM to those networks. Would
I now be able to ssh to this and run command what I am looking for is a
unification of boot-runcommand-delete and this neutron_network so create
network attach to router associate floating ip and ssh to it
On Fri, Aug 29, 2014 at 11:51 AM, Eichberger, German
german.eichber...@hp.com wrote:
Kyle,
I am confused. So basically you (and Mark) are saying:
1) We deprecate Neutron LBaaS v1
2) We spin out Neutron LBaaS v2 into it's own project in stackforge
3) Users don't have an OpenStack LBaaS any
lifeSorry folks, I just had a new daughter since Thursday so I'm on
PTO until Monday, so thanks to the people who discussed about the
blueprint I created and how we can avoid the problem raised by Don for Kilo.
/life
Answers inline.
Le 29/08/2014 19:42, John Garbutt a écrit :
I think this is
On Aug 29, 2014 10:42 AM, Dugger, Donald D donald.d.dug...@intel.com
wrote:
Well, I think that there is a sign of a broken (or at least bent) process
and that's what I'm trying to expose. Especially given the ongoing
conversations over Gantt it seems wrong that ultimately it was rejected due
to
- Original Message -
From: Matthew Booth mbo...@redhat.com
On 14/08/14 12:41, Steve Gordon wrote:
- Original Message -
From: Matthew Booth mbo...@redhat.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
I've just
Once we got dependencies on keystone-python client, Mistral doesn’t build for
me on Mac.
Before, I installed a new openssl (1.0.1h) - keystone authentication didn’t
work with out it, remember?
enykeev suggested to return to the old stock openssl, it worked.
but this sort of sucks to switch
The current backup APIs in OpenStack do not really make sense (and
apparently do not work ... which perhaps says something about usage and
usability). So in that sense, they could be removed.
Wrote out a bit as to what is needed:
On Fri, 29 Aug 2014 11:13:39 -0400
David Kranz dkr...@redhat.com wrote:
On 08/29/2014 10:56 AM, Sean Dague wrote:
On 08/29/2014 10:19 AM, David Kranz wrote:
While reviewing patches for moving response checking to the
clients, I noticed that there are places where client methods do
not
I think the purpose of nova VM is not for persistent usage, and it should
be used for stateless. However, there are use cases to use VM to replace
bare metal applications, and it requires the same coverage, which I think
VMware did pretty well.
The nova backup is snapshot indeed, so it should be
76 matches
Mail list logo
