Anita Kuno writes:
[...]
Nik and I have talked. Since J2 is too far away to let a system run
without recheck capability (as Joe points out, this is not in compliance
with third party ci requirements), Nik is currently following up on
Sukdev's wiki page (if someone can help Sukdev learn
Where I work we make use of Postgresql for most of our database needs.
It would be nice to be able to offer a Postgresql flavor within the
Trove framework. Is anyone working on adding it in?
If noone else is, then I might look at doing it, if there are folks
working on it - let me know if I
Hello Mark.
There are several patches for Postgresql are hanging at the review queue.
Here's useful link:
https://blueprints.launchpad.net/trove/+spec/postgresql-support
Contact point: Kevin Conway (you can ping him in IRC and ask if he needs
any help)
Best regards,
Denis Makogon
On Thu,
Thanks Denis, will do!
On 10/07/14 19:23, Denis Makogon wrote:
Hello Mark.
There are several patches for Postgresql are hanging at the review queue.
Here's useful link:
https://blueprints.launchpad.net/trove/+spec/postgresql-support
Contact point: Kevin Conway (you can ping him in IRC and
On Wed, Jul 9, 2014 at 5:30 PM, Nikhil Manchanda nik...@manchanda.me
wrote:
Joe Gordon writes:
[...]
This sounds very similar to the v3/v2.1 discussion happening in nova.
All
OpenStack projects need to address these issues and it would be a shame
if
each project chose a different
)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Thursday, July 10, 2014 at 12:18 PM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [trove] Discussion
Joe Gordon writes:
[...]
This sounds very similar to the v3/v2.1 discussion happening in nova. All
OpenStack projects need to address these issues and it would be a shame if
each project chose a different solution, perhaps this is a good topic for
the TC to help tackle? As having different
Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: Thursday, July 3, 2014 at 2:20 PM
To: OpenStack Development Mailing List (not for usage questions) (
openstack-dev@lists.openstack.org) openstack-dev@lists.openstack.org
Subject: [openstack-dev] [trove] Discussion
Hey folks:
There's nothing to discuss on the BP Agenda for this week and most folks
are busy working on existing BPs and bugs, so I'd like to cancel the
Trove blueprint meeting for this week.
See you guys at the regular Trove meeting on Wednesday.
Thanks,
Nikhil
]
Regards,
Doug
From: Iccha Sethi [mailto:iccha.se...@rackspace.com]
Sent: July-03-14 4:36 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [trove] Discussion of capabilities feature
Hey Doug,
Thank you so much for putting
At yesterday's Trove team meeting [1] there was significant discussion around
the Capabilities [2] feature. While the community previously approved a BP and
some of the initial implementation, it is apparent now that there is no
agreement in the community around the requirements, use cases or
@lists.openstack.org
Subject: [openstack-dev] [trove] Discussion of capabilities feature
At yesterday's Trove team meeting [1] there was significant discussion around
the Capabilities [2] feature. While the community previously approved a BP and
some of the initial implementation, it is apparent now
...@rackspace.com]
Sent: July-03-14 4:36 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [trove] Discussion of capabilities feature
Hey Doug,
Thank you so much for putting this together. I have some
questions/clarifications(inline) which would be useful
Hi Craig.
Seems like perfect task to use stevedore and its plugin system. I do agree
that it looks very nasty to have huge dict of managers.
I don't like the idea of placing 'manager' under config groups, because
each config group should be registered, and when it's done only then you
can use
If you want to override the trove guestagent managers its looks really
nasty to have EVERY manager on a single line here.
datastore_registry_ext =
mysql:my.guestagent.datastore.mysql.manager.Manager,percona:my.guestagent.datastore.mysql.manager.Manager,...
This needs to be tidied up and split
The reddwarf 3rd party CI is failing on an oslo sync patch [1] but
Jenkins is fine, I'm unable to find any wiki or guideline on how to
recheck just the reddwarf CI, is that possible?
[1] https://review.openstack.org/#/c/103232/
--
Thanks,
Matt Riedemann
Hello, Mat.
You need to log into https://rdjenkins.dyndns.org/job/Trove-Gate/ (Auth
system uses Launchpad OpenID).
Then you need to find certaun job you need to click Retrigger. The End.
FYI i already retrigged your job. You're welcome.
Best regards,
Denis Makogon
On Sun, Jun 29, 2014 at
On Jun 29, 2014 7:09 PM, Nikhil Manchanda nik...@manchanda.me wrote:
Long term, we're looking to move away from running the integration tests
in the third
party reddwarf-jenkins, so this should soon go away.
FWIW, in the short term, the re-trigger permissions are based on the
trove-developers
As per http://ci.openstack.org/third_party.html#requirements this is not
an acceptable short term solution.
Which is one of the major reasons why we're planning on killing the whole
third-party rdjenkins
tests, and moving all of our trove testing to OpenStack infra.
At this point, I'd really
On 06/29/2014 08:38 PM, Nikhil Manchanda wrote:
As per http://ci.openstack.org/third_party.html#requirements this is not
an acceptable short term solution.
Which is one of the major reasons why we're planning on killing the whole
third-party rdjenkins
tests, and moving all of our trove
Hey folks:
There's nothing to discuss on the BP Agenda for this week and most folks
are busy working on existing BPs and bugs, so I'd like to cancel the
Trove blueprint meeting for this week.
See you guys at the regular Trove meeting on Wednesday.
Thanks,
Nikhil
On Jun 29, 2014 8:53 PM, Anita Kuno ante...@anteaya.info wrote:
On 06/29/2014 08:38 PM, Nikhil Manchanda wrote:
As per http://ci.openstack.org/third_party.html#requirements this is
not
an acceptable short term solution.
Which is one of the major reasons why we're planning on killing the
Hi everyone,
Just a heads up that the date and location for the Trove Juno mid-cycle
meetup has been finalized.
Where: MIT, Cambridge, MA
When: August 20, 21 and 22
If you are interested in attending the mid-cycle meetup, please mark your
calendars and register at
Hey guys,
Just a friendly reminder that we'll (re)review the configurable db
plugins BP on Monday June 23rd. The spec is here:
https://wiki.openstack.org/wiki/Trove/ConfigurableDBPlugins
Please take a moment to review prior to our BP meeting if you have an
interest in this topic.
I've
Denis Makogon writes:
Good day, Stackers, Trove community.
I'd like to start thread related to orchestration based resource
management. At current state Heat support in Trove is nothing else than
experimental. Trove should be able to fully support Trove as resource
management driver.
I
On 16/06/14 13:56, Nikhil Manchanda wrote:
Denis Makogon writes:
Because Trove should not do what it does now (cloud service orchestration
is not the part of the OS Database Program). Trove should delegate all
tasks to Cloud Orchestration Service (Heat).
Agreed that Trove should delegate
Hello folks,
I'd like to propose following small changes to [filter:authtoken]
section in default api-paste.ini:
+admin_tenant_name = %SERVICE_TENANT_NAME%
+admin_user = %SERVICE_USER%
+admin_password = %SERVICE_PASSWORD%
I created a new ticket [1] about this.
Some of core OpenStack components
Hi Denis
On 11/06/14 20:17, Denis Makogon wrote:
Good day, Stackers, Trove community.
I'd like to start thread related to orchestration based resource
management. At current state Heat support in Trove is nothing else
than experimental. Trove should be able to fully support Trove as
Good day, Stackers, Trove community.
I'd like to start thread related to orchestration based resource
management. At current state Heat support in Trove is nothing else than
experimental. Trove should be able to fully support Trove as resource
management driver.
Why is it so important?
Because
Good day, Stackers, Trove community.
I’d like to start thread related to Datastore testing infrastructure.
Why does we need it?
At this time Trove has integrated more than databases. To be precise:
-
MySQL
-
mysql-server
-
percona
-
Cassandra
-
Hi developers,
If you have a chance it would be great to hear any feedback.
I opened a new ticket about admin_{user,tenant_name,
password}:
https://bugs.launchpad.net/trove/+bug/1299332
In this ticket, I suggest following changes in api-paste.ini:
+admin_tenant_name = %SERVICE_TENANT_NAME%
Guys,
In the BP meeting yesterday we briefly discussed the 'Configurable DB
Plugins' BP:
https://blueprints.launchpad.net/trove/+spec/configurable-db-plugins
It was clear I needed to hash this one out in greater detail to
optimally discuss the feature with the group - I've done that and you
On 4/28/2014 2:58 PM, Dan Smith wrote:
I'd like to propose the ability to support a pluggable trove conductor
manager. Currently the trove conductor manager is hard-coded [1][2] and
thus is always 'trove.conductor.manager.Manager'. I'd like to see this
conductor manager class be pluggable like
On 06/02/2014 09:23 AM, boden wrote:
On 4/28/2014 2:58 PM, Dan Smith wrote:
I'd like to propose the ability to support a pluggable trove conductor
manager. Currently the trove conductor manager is hard-coded [1][2] and
thus is always 'trove.conductor.manager.Manager'. I'd like to see this
This is to be more inline with the other services we have ie. taskmanager
[1] that you can override if you see fit.
On Mon, Jun 2, 2014 at 3:55 PM, Russell Bryant rbry...@redhat.com wrote:
On 06/02/2014 09:23 AM, boden wrote:
On 4/28/2014 2:58 PM, Dan Smith wrote:
I'd like to propose the
Sent that a little too quickly...
This is to be more inline with the other services we have ie. taskmanager
[1] that you can override if you see fit. We decided this was an oversight
from the original creation and should be added.
[1]
Trove-Gate appears to sit idle after the last output from the test run. See the
following samples:
Excerpt from https://rdjenkins.dyndns.org/job/Trove-Gate/3792/console
12:59:47 202.03 proboscis.case.MethodTest
(test_instance_returns_to_active_after_resize)
13:47:06
Good day, Trove community.
I would like to start thread related to Trove notification framework.
Notification design was defined as: “Trove will emit events for
resources as they are manipulated. These events can be used to meter the
service and possibly used to calculate bills.”
Hello Team:
Just a quick reminder that the Trove Blueprint meeting on May 26th is
canceled since most folks will be unavailable on Memorial Day.
The next Blueprint meeting will be on Monday, June 2nd. The agenda can
be found at the usual location at:
Matt,
Thanks for sharing this. Pretty cool!
-Craig
On Wed, May 7, 2014 at 11:13 AM, Lowery, Mathew mlow...@ebay.com wrote:
I just wanted to share a project that I've been working on. It's a
development workflow for OpenStack projects.
I like to code in PyCharm and push my changes to a
Just a quick reminder for the weekly Trove meeting.
https://wiki.openstack.org/wiki/Meetings#Trove_.28DBaaS.29_meeting
Date/Time: Wednesday, 7 May - 1800 UTC / 1100 PDT / 1300 CDT
IRC channel: #openstack-meeting-alt
The Meeting Agenda can be found at
I just wanted to share a project that I've been working on. It's a
development workflow for OpenStack projects.
I like to code in PyCharm and push my changes to a DevStack VM. I don't
use Vagrant and I don't like manually scp'ing code. So I created
git-push-devstack or gpd:
Hello folks:
I'm proposing to add Craig Vyvial (cp16net) to trove-core.
Craig has been working with Trove for a while now. He has been a
consistently active reviewer, and has provided insightful comments on
numerous reviews. He has submitted quality code to multiple features in
Trove, and most
+1
On May 6, 2014 4:32 AM, Nikhil Manchanda nik...@manchanda.me wrote:
Hello folks:
I'm proposing to add Craig Vyvial (cp16net) to trove-core.
Craig has been working with Trove for a while now. He has been a
consistently active reviewer, and has provided insightful comments on
numerous
+1
--
Amrith Kumar, CTO, Tesora
| -Original Message-
| From: Nikhil Manchanda [mailto:nik...@manchanda.me]
| Sent: Tuesday, May 06, 2014 5:32 AM
| To: OpenStack Development Mailing List (not for usage questions)
| Subject: [openstack-dev] [Trove] Proposal to add Craig Vyvial to trove
+1
-Original Message-
From: Nikhil Manchanda [mailto:nik...@manchanda.me]
Sent: May-06-14 5:32 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Trove] Proposal to add Craig Vyvial to trove-core
Hello folks:
I'm proposing to add Craig
+1
On 5/6/14, 4:31 AM, Nikhil Manchanda nik...@manchanda.me wrote:
Hello folks:
I'm proposing to add Craig Vyvial (cp16net) to trove-core.
Craig has been working with Trove for a while now. He has been a
consistently active reviewer, and has provided insightful comments on
numerous reviews.
+1
On May 6, 2014, at 4:31 AM, Nikhil Manchanda nik...@manchanda.me wrote:
Hello folks:
I'm proposing to add Craig Vyvial (cp16net) to trove-core.
Craig has been working with Trove for a while now. He has been a
consistently active reviewer, and has provided insightful comments on
+1
-Original Message-
From: Nikhil Manchanda [mailto:nik...@manchanda.me]
Sent: May-06-14 5:32 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Trove] Proposal to add Craig Vyvial to trove-core
Hello folks:
I'm proposing to add Craig Vyvial
I've been thinking about this a bit, and had some ideas. Take the
following as points for thought, rather than my saying this is what we
should do.
How about each Trove participant be assigned a core mentor. This way,
each non-core person knows who they can ask for information about how
+1
From: Peter Stachowski [pe...@tesora.com]
Sent: Tuesday, May 06, 2014 9:06 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Trove] Proposal to add Craig Vyvial to trove-core
+1
-Original Message
On May 6, 2014, at 2:31 AM, Nikhil Manchanda nik...@manchanda.me wrote:
Hello folks:
I'm proposing to add Craig Vyvial (cp16net) to trove-core.
Craig has been working with Trove for a while now. He has been a
consistently active reviewer, and has provided insightful comments on
+1
On Tue, May 6, 2014 at 9:38 AM, Michael Basnight mbasni...@gmail.comwrote:
On May 6, 2014, at 2:31 AM, Nikhil Manchanda nik...@manchanda.me
wrote:
Hello folks:
I'm proposing to add Craig Vyvial (cp16net) to trove-core.
Craig has been working with Trove for a while now. He
+1
On Tue, May 6, 2014 at 5:06 PM, Peter Stachowski pe...@tesora.com wrote:
+1
-Original Message-
From: Nikhil Manchanda [mailto:nik...@manchanda.me]
Sent: May-06-14 5:32 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Trove] Proposal
+1
On 5/6/14, 2:31 AM, Nikhil Manchanda nik...@manchanda.me wrote:
Hello folks:
I'm proposing to add Craig Vyvial (cp16net) to trove-core.
Craig has been working with Trove for a while now. He has been a
consistently active reviewer, and has provided insightful comments on
numerous reviews.
+1
On Tue, May 6, 2014 at 10:09 AM, McReynolds, Auston amcreyno...@ebay.comwrote:
+1
On 5/6/14, 2:31 AM, Nikhil Manchanda nik...@manchanda.me wrote:
Hello folks:
I'm proposing to add Craig Vyvial (cp16net) to trove-core.
Craig has been working with Trove for a while now. He has
Thanks everyone for the show of support.
Craig: welcome to trove-core!
On Tue, May 6, 2014 at 1:17 PM, Vipul Sabhaya vip...@gmail.com wrote:
+1
On Tue, May 6, 2014 at 10:09 AM, McReynolds, Auston
amcreyno...@ebay.comwrote:
+1
On 5/6/14, 2:31 AM, Nikhil Manchanda nik...@manchanda.me
As a non-core, I would like to understand the process by which core prioritizes
Gerrit changes. I'd also like to know any specific criteria used for approval.
If such a process was transparent and followed consistently, wouldn't that
eliminate the need for Hey core, can you review change? in
Hi Mat:
Some answers, and my perspective, are inline:
Lowery, Mathew writes:
As a non-core, I would like to understand the process by which core
prioritizes Gerrit changes.
I'm not aware of any standard process used by all core reviewers to
prioritize reviewing changes in Gerrit. My
Good day, Trove community
I'd like to start thread related to orchestration based resource
management. At current state Heat support in Trove is nothing else than
experimental. Trove should be able to fully support Trove as resource
management driver.
*Why is it so important?*
Because
Good day, Trove community
I'd like to start thread related to orchestration based resource
management. At current state Heat support in Trove is nothing else than
experimental. Trove should be able to fully support Trove as resource
management driver.
*Why is it so important?*
Because Trove
Guys,
I have a few small features / enhancements I'd like to suggest. I'm
willing to contribute the code / unit tests myself, but am looking for a
consensus from the group before I invest the time.
There are a few enhancements on my list -- I will send details each in a
separate email to
I'd like to propose the ability to support a pluggable trove conductor
manager. Currently the trove conductor manager is hard-coded [1][2] and
thus is always 'trove.conductor.manager.Manager'. I'd like to see this
conductor manager class be pluggable like nova does [3].
Note that most of us
Guys,
I have a few small features / enhancements I'd like to suggest. I'm
willing to contribute the code / unit tests myself, but am looking for a
consensus from the group before I invest the time.
There are a few enhancements on my list -- I will send details each in a
separate email to
Good day, Boden.
I think you should file the blueprint for it and put it into BP meeting
agenda.
Best regards,
Denis Makogon
On Mon, Apr 28, 2014 at 9:50 PM, boden bo...@linux.vnet.ibm.com wrote:
Guys,
I have a few small features / enhancements I'd like to suggest. I'm
willing to contribute
Guys,
I have a few small features / enhancements I'd like to suggest. I'm
willing to contribute the code / unit tests myself, but am looking for a
consensus from the group before I invest the time.
There are a few enhancements on my list -- I will send details each in a
separate email to
On 4/28/2014 3:03 PM, Denis Makogon wrote:
Good day, Boden.
I think you should file the blueprint for it and put it into BP meeting
agenda.
Best regards,
Denis Makogon
On Mon, Apr 28, 2014 at 9:50 PM, boden bo...@linux.vnet.ibm.com
mailto:bo...@linux.vnet.ibm.com wrote:
Guys,
I have
Hello Trove/Heat community.
I'd like to start thread related to required use cases (from Trove
perspective). To support (completely) Heat in Trove, it neeeds to support
required operations like:
1.
Resize operations:
- resize a volume (to bigger size);
- consistent resize of
Excerpts from Zane Bitter's message of 2014-04-25 10:05:31 -0700:
On 25/04/14 08:30, Denis Makogon wrote:
Hello Trove/Heat community.
I'd like to start thread related to required use cases (from Trove
perspective). To support (completely) Heat in Trove, it neeeds to
support required
On Fri, Apr 25, 2014 at 8:44 PM, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Zane Bitter's message of 2014-04-25 10:05:31 -0700:
On 25/04/14 08:30, Denis Makogon wrote:
Hello Trove/Heat community.
I'd like to start thread related to required use cases (from Trove
Just a quick reminder for the weekly Trove meeting.
https://wiki.openstack.org/wiki/Meetings#Trove_.28DBaaS.29_meeting
Date/Time: Wednesday, 16 April - 1800 UTC / 1100 PDT / 1300 CDT
IRC channel: #openstack-meeting-alt
The Meeting Agenda can be found at
At the blueprint review for the Trove team on April 14th, we reviewed Allow
volume snapshot as another way for data backuping
(https://blueprints.launchpad.net/trove/+spec/volume-snapshot).
The detailed specification is available at
-agent/fsfreeze-hook.d/mysql-flush.sh.sample
Thanks,
Kevin
From: Amrith Kumar [amr...@tesora.com]
Sent: Monday, April 14, 2014 4:46 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [trove] Blueprint Review: Allow volume
confirmed
On 04/01/2014 03:39 AM, Nikhil Manchanda wrote:
I'd like to announce my candidacy for the Database (Trove) PTL.
I'm currently a member of the Trove Core team, and have been working
on OpenStack and Trove for more than a year and a half now. I've
helped Trove grow from the tiny
I have completed the blueprint and specification for the proposed
instance metadata code that is up for review. We can discuss the
blueprint either here or on the IRC channel.
Related links:
Blueprint: https://blueprints.launchpad.net/trove/+spec/trove-metadata
Specification:
I'd like to announce my candidacy for the Database (Trove) PTL.
I'm currently a member of the Trove Core team, and have been working
on OpenStack and Trove for more than a year and a half now. I've
helped Trove grow from the tiny stackforge project that it was, to
the OpenStack Database project
Just a quick reminder for the weekly Trove meeting.
https://wiki.openstack.org/wiki/Meetings#Trove_.28DBaaS.29_meeting
Date/Time: Wednesday 26 March - 1800 UTC / 1100 PDT / 1300 CDT
IRC channel: #openstack-meeting-alt
Meeting Agenda (https://wiki.openstack.org/wiki/Meetings/TroveMeeting):
1.
Craig Vyvial wrote:
Thats really cool.
+1, thanks Mat for writing this up. I'm going to experiment with this
approach...
Mat Lowery wrote:
Assuming my doc is desirable in some form, where is the best place to put it?
Thanks.
This seems similar to some of the pages under
My colleague, Ranjitha Vemula, just submitted a trove-integration patch
set to add a MySQL 5.6 disk-image-builder element. Two major hurdles were
faced with this patch set.
1) The manager
The resulting MySQL 5.6 image can be registered using mysql as the
datastore, mysql as the manager, and
Excerpts from Lowery, Mathew's message of 2014-03-11 10:33:12 -0700:
My colleague, Ranjitha Vemula, just submitted a trove-integration patch
set to add a MySQL 5.6 disk-image-builder element. Two major hurdles were
faced with this patch set.
snip
In my understanding, D.I.B. elements should
Mathew,
Thats really cool. I've been using vagrant for a while and Ed created this
repo and it works pretty well. We've been using it for about 6 months or
longer. Its nice if you want to be able to test something locally.
https://github.com/ed-/trove-vagrant-vmware
I've been exploring using a
Denis Makogon dmako...@mirantis.com writes:
Let me elaborate a bit.
[...]
Without storing static API contract capabilities gonna be 100% corrupted,
because there's no API description inside Trove.
Im not sure i understand what you mean here.
About reloading, file should not be reloaded,
So I submitted this
dochttp://docs-draft.openstack.org/29/70629/3/check/gate-trove-docs/34ceff7/doc/build/html/dev/install_alt.html
(in this patch sethttps://review.openstack.org/#/c/70629/) and Dan Nguyen
(thanks Dan) stated that there were some folks using Vagrant. (My workflow uses
git push
After reading this I feel it requires me to ask the question:
Do flavors have datastores or do datastores have flavors?
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hey, Danies.
Datastore has a set of flavor that allowed to be used while instance
provisioning with the given datastore.
Best regards,
Denis Makogon
On Wed, Mar 5, 2014 at 5:28 PM, Daniel Salinas imsplit...@gmail.com wrote:
After reading this I feel it requires me to ask the question:
Do
Good day, DBaaS community.
Yesterday, at meeting was mentioned that some one
(maybe from core team) going to schedule hangout meeting
related replication implementation.
Would be better if the person who's going to schedule and organize meeting
will send the notification to openstack-dev to
I'll be honest, after reading your proposal Denis and looking over
what Kaleb has it feels like you both are calling 2 different things
capabilities. Denis, your proposal provides a way of blocking or
enabling api paths to the users. Kaleb's proposal is more about
informing consumers of the api
We have a need to support multiple versions of a single datastore with a single
set of disk-image-builder elements. Let's take MySQL on Ubuntu as an example.
5.5 is already present in trove-integration. Let's say we want to add 5.6 to
coexist. Let's also assume that simply asking for the
Hi Nikhil,
This is great!
You may have assumed this but I wanted to be explicit: To get the higher
timeout, I think all that needs to be done is to upgrade the
boot-hpcloud-vm plugin. Then the plugin will pass the current timeout
(7200 in rdjenkins) down to the net-ssl-simple library. (This is
Hi Mat:
If I recall correctly, rdjenkins is actually running a version of the
plugin specifically built by Matty for it (should be the latest). I'm not
sure why it's still hitting the timeout issue mentioned earlier, so
we'll have to check with Matty and try to figure out what the deal with
that
Trovesters,
One reason for the longer running test was that for the configuration
groups i added a creation of a new instance. This is to test a new instance
will be created with a configuration group applied. This might be causing
the run to be a little longer but i am surprised that its taking
Hi, Craig.
Yes, i thought about configurations test suits.
For now core team, maybe, should extend gate running time.
But for the tempest tests i would suggest to exclude some tests from
'gate'-group (the longest ones).
We need to deal with it asap, because gate failing for four or five days.
Hi all,
Issue #1: Jobs that need more than one hour
Of the last 30 Trove-Gatehttps://rdjenkins.dyndns.org/job/Trove-Gate/ builds
(spanning three days), 7 have failed due to a Jenkins job-level timeout (not a
proboscis timeout). These jobs had no failed tests when the timeout occurred.
Not
Hello, Mathew.
I'm seeing same issues with the gate.
I also tried to found out why gate job is failing. First ran into issue related
to cinder installation failure in devstack. But then I found same problem as
you described. The best option is to increase job time range.
Thanks for such
Denis Makogon dmako...@mirantis.com writes:
Goodday, OpenStack DВaaS community.
I'd like to start conversation about guestagent security issue related
to backup/restore process. Trove guestagent service uses AES with 256 bit
key (in CBC mode) [1] to encrypt backups which are stored
As we decided at meeting, we wouldn't keep our own implementations of
security stuff, we'll use Barbican as single entry point of delivering
secrets.
I hadn't talked with Barbican team, but since oslo-incubator will (someday)
release oslo.crypto lib for all projects, i think that adding
Daniel Salinas imsplit...@gmail.com writes:
https://wiki.openstack.org/wiki/Trove-Replication-And-Clustering-API#REPLICATION
I have updated the wiki page to reflect the current proposal for
replication verbiage with some explanation of the choices. I would like to
open discussion here
Daniel,
Couple questions.
So what happens if/when the volume is different on the nodes in the
replication cluster? If you need to resize the volume larger to handle more
data are you required to resize all the nodes individually? It makes sense
that maybe all the instances could have a different
Goodday, OpenStack DВaaS community.
I'd like to start conversation about guestagent security issue related
to backup/restore process. Trove guestagent service uses AES with 256 bit
key (in CBC mode) [1] to encrypt backups which are stored at predefined
Swift container.
As you can
Goodday, OpenStack DBaaS users/contributors.
I'd like to start topic related to network access to Trove instances.
Basicaly this topic related to security groups inside which are provisioned
inside Trove. Not so long ago, Trove began support Redis DB, supported core
API and extensions
501 - 600 of 797 matches
Mail list logo
