On 01.07.2014 04:05, Joshua Harlow wrote:
Greetings all stackers,
I propose that we add Pranesh Pandurangan[1] to the taskflow-core team[2].
Pranesh has been actively contributing to taskflow for a while now, both
in helping develop code and helping with the review load. He has provided
Eric,
Thanks for sharing your work, it looks like an interesting development.
I was wondering how the Keystone token expiry is handled since the tokens
generally have a 1 day validity. If the request is scheduling for more than one
day, it would no longer have a valid token. We have similar
Le 01/07/2014 00:08, Stephen Balukoff a écrit :
Obviously, please feel free to disagree with our process and/or
decision for doing this, but I would ask that if you do, please also
do us the courtesy of explaining how we're supposed to merge code
using the gerrit system without having a PTL
On 06/30/2014 10:43 PM, Jeremy Stanley wrote:
On 2014-06-30 22:11:30 +0800 (+0800), Thomas Goirand wrote:
It'd be nice to fix the fact that oslosphinx hacking are
build-depending on each other. How can we fix this?
They're only build-depending on one another (in the Debian sense)
because
On 06/30/2014 04:35 PM, Jesse Pretorius wrote:
On 30 June 2014 16:05, Eric Frizziero eric.frizzi...@pd.infn.it
mailto:eric.frizzi...@pd.infn.it wrote:
In more detail, some features of the FairshareScheduler are:
a) It assigns dynamically the proper priority to every new user
Hi Belmiro,
On 06/30/2014 11:42 PM, Belmiro Moreira wrote:
Hi Eric,
definitely...
In my view a FairShareScheduler could be a very interesting option
for private clouds that support scientific communities. Basically this
is the model used by batch systems in order to fully use the available
Hi Tim,
for sure this is one of the main issues we are facing and the approach
you suggested is the same we are investigating on.
Could you provide some details about the Heat proxy renew mechanism?
Thank you very much for your feedback.
Cheers,
Lisa
On 01/07/2014 08:46, Tim Bell wrote:
Hi folks,
Could anyone please review this spec for adding a new API to count
resources in Neutron?
https://review.openstack.org/#/c/102199/
Thanks
Xurong Yang
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
I'll chair this week PCI SR-IOV pass-through meeting for those who would like
to attend.
BR,
Irena
From: Robert Li (baoli) [mailto:ba...@cisco.com]
Sent: Tuesday, July 01, 2014 5:00 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [nova][sriov] weekly
Hi Don,
I and my colleague Lisa attend both IRC meetings (today and next week).
In the meantime you can find more info about the FairShareScheduler at
the following link:
https://agenda.infn.it/getFile.py/access?contribId=17sessionId=3resId=0materialId=slidesconfId=7915
Thank you very
-Original Message-
From: Lisa [mailto:lisa.zangra...@pd.infn.it]
Sent: 01 July 2014 10:45
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova][scheduler] Proposal: FairShareScheduler.
Hi Tim,
for sure this is one of the main issues
Le 01/07/2014 10:45, Lisa a écrit :
Hi Tim,
for sure this is one of the main issues we are facing and the approach
you suggested is the same we are investigating on.
Could you provide some details about the Heat proxy renew mechanism?
Thank you very much for your feedback.
Cheers,
Lisa
On 30 June 2014 16:49, Anita Kuno ante...@anteaya.info wrote:
Right now that dashboard introduces more confusion than it alleviates
since the definition of success in regards to third party ci systems
has yet to be defined by the community.
For the record, cinder gave a very clear definition
Hello Devananda
Design spec for the remote firmware setting feature is under review (
https://review.openstack.org/#/c/101122 ). Have received comments on the
APIs and we are converging on the set of required APIs.
Have posted the new patch addressing the comments on the same.
Please check, if
I have some objections. We are trying to follow a strict development
workflow with feature freeze stage. In this case we will have to miss small
enhancements that can emerge after FF date and can bring essential benefits
along with small risks of breaking anything (e.g. changing some config
Hi,
In the following document, there is a setup up procedure for storage and
it seems that swift recommends to use xfs.
http://docs.openstack.org/icehouse/install-guide/install/yum/content/installing-and-configuring-storage-nodes.html
===
2. For each device on the node that you want to use for
Thank you for the video, keep up the good work!,
- Original Message -
Hi folks,
The DVR team is working really hard to complete this important task for Juno
and Neutron.
In order to help see this feature in action, a video has been made available
and link can be found in [2].
On 07/01/2014 08:11 AM, Anant Patil wrote:
Hi,
I use tmux (an alternative to screen) a lot and I believe lot of other
developers use it. I have been using devstack for some time now and
would like to add the option of using tmux instead of screen for
creating sessions for openstack
On Tue, Jul 1, 2014 at 6:21 AM, Osanai, Hisashi
osanai.hisa...@jp.fujitsu.com wrote:
Hi,
In the following document, there is a setup up procedure for storage and
it seems that swift recommends to use xfs.
Anant Patil wrote:
I use tmux (an alternative to screen) a lot and I believe lot of other
developers use it.
I have been using devstack for some time now and would like to add the option
of
using tmux instead of screen for creating sessions for openstack services.
I couldn't find a way to do
I've been working to add ceilometer checks in javelin2. Doing so has
revealed some issues that appear to be a fairly big deal but I suppose
there's some chance I'm doing things completely wrong.
For reference my experiments are being done with a devstack with
ceilometer enabled, running javelin
Ok, I was talking with Édouard @ IRC, and as I have time to work
into this problem, I could file an specific spec for the security
group RPC optimization, a masterplan in two steps:
1) Refactor the current RPC communication for security_groups_for_devices,
which could be used for full
Hi Everyone,
*The Call for Speakers is OPEN for the November OpenStack Summit in
Paris! Submit your talks here:
https://www.openstack.org/summit/openstack-paris-summit-2014/call-for-speakers/.*
There are a few new speaking tracks in the Summit lineup this year so
please review the below
Hello
On Fri, Jun 20, 2014 at 12:48 PM, Radoslav Gerganov rgerga...@vmware.com
wrote:
Hi,
On Wed, Jun 18, 2014 at 4:47 AM, Gary Kotton gkot...@vmware.com wrote:
Hi,
I have encountered a problem with string substitution with the nova
configuration file. The motivation was to move all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 30/06/14 21:34, Alexei Kornienko wrote:
Hello,
My understanding is that your analysis is mostly based on running
a profiler against the code. Network operations can be bottlenecked
in other places.
You compare 'simple script using
Hi,
I won't be able to attend the mid-cycle sprint due to a good family
reason (a new baby 2.0 release expected to land by these dates), so I'm
wondering if it's possible to webcast some of the sessions so people who
are not there can still share their voices ?
-Sylvain
On 07/01/2014 05:56 AM, Duncan Thomas wrote:
On 30 June 2014 16:49, Anita Kuno ante...@anteaya.info wrote:
Right now that dashboard introduces more confusion than it alleviates
since the definition of success in regards to third party ci systems
has yet to be defined by the community.
For
At minimum I can arrange for a phone bridge at the sprint (Intel `lives` on
phone conferences) so we can certainly do that. Video might be more
problematic, I know we did something with Google Plus at the last sprint but I
don't know the details on that.
--
Don Dugger
Censeo Toto nos in Kansa
On Tue, Jul 01, 2014 at 02:01:19PM +0100, Chris Dent wrote:
I've been working to add ceilometer checks in javelin2. Doing so has
revealed some issues that appear to be a fairly big deal but I suppose
there's some chance I'm doing things completely wrong.
For reference my experiments are
Hi,
Thanks for detailed answer.
Please see my comments inline.
Regards,
On 07/01/2014 04:28 PM, Ihar Hrachyshka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 30/06/14 21:34, Alexei Kornienko wrote:
Hello,
My understanding is that your analysis is mostly based on running
a
On 1 July 2014 14:44, Anita Kuno ante...@anteaya.info wrote:
On 07/01/2014 05:56 AM, Duncan Thomas wrote:
For the record, cinder gave a very clear definition of success in our
3rd party guidelines: Passes every test in tempest-dsm-full. If that
needs documenting somewhere else, please let me
Hi,
I attended MongoDB World last week and I thought about giving y'all a
heads up of what's coming next in mongodb-2.8.
- DB Lock will be pushed down to the document level. They demoed this
and I gotta admit, it was quite mind-blowing.
- Support for different storage engines (ala MySQL). They
On Tue, 1 Jul 2014, Matthew Treinish wrote:
In the mean-time you can easily re-enable the full tracebacks by setting both
verbose and debug logging in the tempest config file.
Is there a way to say, via config, no, I really do want exceptions to
cause the code to exit and pooh on the console?
Welcome Zhenguo and Ana to Horizon core.
David
On 6/20/14, 3:17 PM, Lyle, David david.l...@hp.com wrote:
I would like to nominate Zhenguo Niu and Ana Krivokapic to Horizon core.
Zhenguo has been a prolific reviewer for the past two releases providing
high quality reviews. And providing a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/07/14 15:55, Alexei Kornienko wrote:
Hi,
Thanks for detailed answer. Please see my comments inline.
Regards,
On 07/01/2014 04:28 PM, Ihar Hrachyshka wrote: On 30/06/14 21:34,
Alexei Kornienko wrote:
Hello,
My understanding is
Hi,
Please see some minor comments inline.
Do you think we can schedule some time to discuss this topic on one of
the upcoming meetings?
We can come out with some kind of the summary and actions plan to start
working on.
Regards,
On 07/01/2014 05:52 PM, Ihar Hrachyshka wrote:
-BEGIN
On Mon, Jun 30 2014, Joshua Harlow wrote:
There is a balance here that needs to be worked out and I've seen
specs start to turn into requirements for every single patch (even if
the patch is pretty small). I hope we can rework the 'balance in the
force' to avoid being so strict that every
Please don't send review requests to the list. The preferred methods
are discussed here:
http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html
Thanks.
-Ben
On 07/01/2014 03:45 AM, Xurong Yang wrote:
Hi folks,
Could anyone please review this spec for adding a new API
On 06/30/2014 02:28 PM, Mark McLoughlin wrote:
On Mon, 2014-06-30 at 16:52 +, Paul Michali (pcm) wrote:
I have out for review 103536 to add this version to global
requirements, so that Neutron has an oslo fix (review 102909) for
encoding failure, which affects some gate runs. This review
I propose making mysql an abstract element and user must choose either percona
or mariadb-rpm element.CI must be setup correctly
Michael
On Monday 30 June 2014 12:02:09 Clint Byrum wrote:
Excerpts from Michael Kerrin's message of 2014-06-30 02:16:07 -0700:
I am trying to finish off
Rob Crittenden wrote:
Mark Kirkwood wrote:
On 25/06/14 10:59, Rob Crittenden wrote:
Before I get punted onto the operators list, I post this here because
this is the default config and I'd expect the defaults to just work.
Running devstack inside a VM with a single NIC configured and this in
Did they change the license? ;)
Sent from my really tiny device...
On Jul 1, 2014, at 7:17 AM, Flavio Percoco fla...@redhat.com wrote:
Hi,
I attended MongoDB World last week and I thought about giving y'all a
heads up of what's coming next in mongodb-2.8.
- DB Lock will be pushed down
We have a change [1] under review in Swift to make access control lists
compatible with migration to keystone v3 domains. The change makes two
assumptions that I'd like to double-check with keystone folks:
1. That a project can never move from one domain to another.
2. That the
Anita,
This line [1] is effectively a sub-set of tempest-dsm-full, and what we're
currently running manually now. I far as I understood, this is the current
minimum. The exact sub-set (or full set, or if additional tests are allowed) is
still under discussion.
I created a WIP reference
Thanks for the update! Is there anything I need to do for my review 103536 for
adding 1.4.0.0a2 to global requirements?
Regards,
PCM (Paul Michali)
MAIL …..…. p...@cisco.com
IRC ……..… pcm_ (irc.freenode.com)
TW ………... @pmichali
GPG Key … 4525ECC253E31A83
Fingerprint .. 307A 96BB 1A4C D2C7
Hi fuelers,
I'm working on Patching for OpenStack and I have the following questions:
1/ We need to save new puppets and repos under some versioned folder:
/etc/puppet/{version}/ or /var/www/nailgun/{version}/centos.
So the question is which version to use? Fuel or OpenStack?
2/ Which
Hi,
Anthony Veiga and I are currently working on migrating a lab environment
from Neutron Havana w/ OVS plugin to Icehouse w/ ML2 plugin and ran into
a bug[0].
Now the patch that adds the ml2 migration[1] mentions that it was tested
without any data, and that it is waiting on grenade support for
Hi Rob:
Can you try adding the following config to your local.conf? I'd like
to see if this gets you going or not. It will force it to use gre
tunnels for tenant networks. By default it will not.
ENABLE_TENANT_TUNNELS=True
On Tue, Jul 1, 2014 at 10:53 AM, Rob Crittenden rcrit...@redhat.com
1) Puppet manifests are part of Fuel so the version of Fuel should be
used. It is possible to have more than one version of Fuel per
OpenStack version, but not the other way around: if we upgrade
OpenStack version we also increase version of Fuel.
2) Should be a combination of both: it should
Howdy!
I wrote a new version of shellci today and have it up and running and
voting on the sandbox.
It's described on the Github page: https://github.com/SnabbCo/shellci
Currently this is simple shell scripts to receive review.openstack.org
gerrit events, run tests and determine results, then
Hello,
What is the expected behavior of 3rd-party CI systems with regard to
checking out a patch. Should it be tested 'as-is' or should it be merged
into the proposed branch first and then tested?
As I understand it, this behavior for the main OpenStack CI check queue
changed to the latter some
The argument has been made in the past that small features will require
correspondingly small specs. If there's a counter-argument to this example
(a small feature requiring a relatively large amount of spec effort), I'd
love to have links to both the spec and the resulting implementation so we
Much as I dislike the overhead and the extra latency involved (now you need to
have a review cycle for the spec plus the review cycle for the patch itself) I
agreed with the `small features require small specs’. The problem is that even
a small change can have a big impact. Forcing people to
Hi,
my 2 cents:
1) Fuel version (+1 to Dmitry)
2) Could you please clarify what exactly you mean by our patches / our
first patch?
On Tue, Jul 1, 2014 at 8:04 PM, Dmitry Borodaenko dborodae...@mirantis.com
wrote:
1) Puppet manifests are part of Fuel so the version of Fuel should be
used.
On Tue, Jul 1, 2014 at 10:02 AM, Dolph Mathews dolph.math...@gmail.com wrote:
The argument has been made in the past that small features will require
correspondingly small specs. If there's a counter-argument to this example
(a small feature requiring a relatively large amount of spec effort),
On Tue, Jul 1, 2014 at 11:20 AM, Coles, Alistair alistair.co...@hp.com
wrote:
We have a change [1] under review in Swift to make access control lists
compatible with migration to keystone v3 domains. The change makes two
assumptions that I’d like to double-check with keystone folks:
1.
In AWS, an autoscaling group includes health maintenance functionality ---
both an ability to detect basic forms of failures and an ability to react
properly to failures detected by itself or by a load balancer. What is
the thinking about how to get this functionality in OpenStack? Since
We were talking about doing something with google+ for Chris Yeoh, but
haven't really progressed the plan. Does someone want to pick up the
ball with that or shall I?
Michael
On Tue, Jul 1, 2014 at 11:50 PM, Dugger, Donald D
donald.d.dug...@intel.com wrote:
At minimum I can arrange for a phone
As part of the enforce-unique-instance-uuid-in-db blueprint [1] I'm
writing a script to scan the database and find any NULL instance_uuid
records that will cause the new database migration to fail so that
operators can run this before they run the migration, otherwise the
migration blocks if
An AWS autoscaling group can span multiple availability zones in one
region. What is the thinking about how to get analogous functionality in
OpenStack?
Warmup question: what is the thinking about how to get the levels of
isolation seen between AWS regions when using OpenStack? What is the
Hi all,
We created a POC that enables domain-related role checking to components
that do not support domains (such as Nova and Cinder). The code can be
found here: https://github.com/rodrigods/keystone/tree/domain-check
The idea is to use the HttpCheck feature:
Thinking about my favorite use case for lifecycle plug points for cloud
providers (i.e., giving something a chance to make a holistic placement
decision), it occurs to me that one more is needed: a scale-down plug
point. A plugin for this point has a distinctive job: to decide which
group
On Tue, Jul 01, 2014 at 03:21:06PM -0500, Matt Riedemann wrote:
As part of the enforce-unique-instance-uuid-in-db blueprint [1] I'm writing
a script to scan the database and find any NULL instance_uuid records that
will cause the new database migration to fail so that operators can run this
On Mon, Jun 30, 2014 at 11:18 AM, Elizabeth K. Joseph
l...@princessleia.com wrote:
Hi everyone,
The OpenStack Infrastructure (Infra) team is hosting our weekly
meeting on Tuesday July 1st at 19:00 UTC in #openstack-meeting
Meeting minutes and log available:
Minutes:
Greetings list,-
Over the next few weeks I will be working on developing additional Tempest
gating unit and functional tests for the libvirt-lxc compute driver.
I am trying to figure out exactly what is required in order to accomplish
the goal of ensuring the continued inclusion (without
Team,
Please help us select dates for the Containers Team Midcycle Meetup:
http://doodle.com/2mebqhdxpksf763m
Thanks,
Adrian
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
On 07/01/2014 05:59 PM, Adrian Otto wrote:
Team,
Please help us select dates for the Containers Team Midcycle Meetup:
http://doodle.com/2mebqhdxpksf763m
Why not just join the Nova meetup?
--
Russell Bryant
___
OpenStack-dev mailing list
Hi Zhou,
Hi stackers,
I found some problems about the current implement of
limit-volume-copy-bandwidth (this patch has been merged in last week.)
Firstly, assume that I configurate volume_copy_bps_limit=10M, If
the path is a block device, cgroup blkio can limit copy-bandwidth
separately
All,
I am working on a new service to address the problems of Inter Cloud Resource
Federation use cases (e.g. multi region, cloud bursting, resource sharing
across clouds, etc . ).
The new service will integrate multiple OpenStack cloud to work in alliance to
provide resource federation
On 01/07/14 16:23, Mike Spreitzer wrote:
An AWS autoscaling group can span multiple availability zones in one
region. What is the thinking about how to get analogous functionality
in OpenStack?
Correct, you specify a list of availability zones (instead of just one),
and AWS distributes
On 01/07/14 15:47, Mike Spreitzer wrote:
In AWS, an autoscaling group includes health maintenance functionality
--- both an ability to detect basic forms of failures and an ability to
react properly to failures detected by itself or by a load balancer.
What is the thinking about how to get
On 2014-07-01 10:05:45 -0700 (-0700), Kevin Benton wrote:
[...]
As I understand it, this behavior for the main OpenStack CI check
queue changed to the latter some time over the past few months.
[...]
I'm not sure what you think changed, but we've (upstream OpenStack
CI) been testing proposed
On 01/07/14 16:30, Mike Spreitzer wrote:
Thinking about my favorite use case for lifecycle plug points for cloud
providers (i.e., giving something a chance to make a holistic placement
decision), it occurs to me that one more is needed: a scale-down plug
point. A plugin for this point has a
On Jun 14, 2014, at 9:12 AM, Mike Spreitzer mspre...@us.ibm.com wrote:
I am not even sure what is the intent, but some of the behavior looks like it
is clearly unintended and not useful (a more precise formulation of buggy
that is not defeated by the lack of documentation).
IMHO, the API
2014-07-02 2:30 GMT+09:00 Matthew Treinish mtrein...@kortar.org:
Hi Everyone,
During the last qa meeting we were discussing ways to try an increase
throughput
on the qa-specs repo. We decided to have a dedicated review day for the specs
repo. Right now specs approval is a relatively slow
On Tuesday, July 01, 2014 9:44 PM, Anne Gentle a...@openstack.org wrote:
Thank you for the quick response.
The install guide only recommends a single path, not many options, to ensure
success.
I understand the point for writing the document.
There's a little bit of discussion in the
On 7/1/2014 4:03 PM, Matthew Treinish wrote:
On Tue, Jul 01, 2014 at 03:21:06PM -0500, Matt Riedemann wrote:
As part of the enforce-unique-instance-uuid-in-db blueprint [1] I'm writing
a script to scan the database and find any NULL instance_uuid records that
will cause the new database
Zane Bitter zbit...@redhat.com wrote on 07/01/2014 07:05:15 PM:
On 01/07/14 16:30, Mike Spreitzer wrote:
Thinking about my favorite use case for lifecycle plug points for
cloud
providers (i.e., giving something a chance to make a holistic
placement
decision), it occurs to me that one
In the endeavor to move from the default deployment of Keystone being eventlet
(in devstack) to Apache + mod_wsgi, I noticed that there was an odd mis-match
on a single set of tempest tests relating to trusts. Under eventlet a HTTP 204
No Content was being returned, but under mod_wsgi an HTTP
Hi Devananda,
I noticed that firmware update is not on the priority list. I thought
there was strong interest in this capability. The design spec of
out-of-band firmware update has been submitted
https://review.openstack.org/#/c/100842/. We will address the review
comments and uplaod a new
From: Carl Baldwin [c...@ecbaldwin.net]
Sent: Monday, June 30, 2014 3:43 AM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] DVR and FWaaS integration
On Mon, Jun 30, 2014 at 3:43 AM, Carl Baldwin
c...@ecbaldwin.netmailto:c...@ecbaldwin.net
I have manually deployed cinder and it is up and running. Now I wanted to
get the live code coverage for cinder using tempest, I tried to running
each cinder-api services as coverage run /usr/bin/cinder-api it started
but when I tried same with cinder-volume with volume types configured it
failed.
hi Miguel Angel Ajo Pelayo!
I agree with you and modify my spes, but I will also optimization the RPC from
security group agent to neutron server.
Now the modle is 'port[rule1,rule2...], port...', I will change it to
'port[sg1, sg2..]', this can reduce the size of RPC respose message from
Thank you everyone, I'll do my best!
发自我的 iPhone
在 Jul 1, 2014,22:37,Lyle, David david.l...@hp.com 写道:
Welcome Zhenguo and Ana to Horizon core.
David
On 6/20/14, 3:17 PM, Lyle, David david.l...@hp.com wrote:
I would like to nominate Zhenguo Niu and Ana Krivokapic to Horizon core.
Zane,
If you happen to have a link to this blueprint, could you reply with it? I took
a look, but did not find it.
I’d like to suggest that the implementation allow apps to call unauthenticated
(signed) webhook URLs in order to trigger a scale up/down event within a
scaling group. This is
All:
I've updated the Neutron Juno Project Plan [1] page with a timeline
for the remainder of Juno. Similar to Nova, we're going to participate
in both Spec Proposal Deadline (SPD) and Spec Approval Deadline (SAD).
The dates are listed on the wiki, but since these are new, I'm calling
them out
Wearing my HTTP fanatic hat - I think this is actually an important
change to do. Skew like this can cause all sorts of odd behaviours in
client libraries.
-Rob
On 2 July 2014 13:13, Morgan Fainberg morgan.fainb...@gmail.com wrote:
In the endeavor to move from the default deployment of Keystone
Heya,
I was trying to help with the Horizon Juno-2 reviews, and found the launchpad
link
(https://launchpad.net/horizon/+milestone/juno-2) a bit unhelpful in figuring
out
which items actually need reviews, as some of the items marked 'Needs Code
Review'
are works in progress, or already
On 07/01/2014 07:48 PM, Robert Collins wrote:
Wearing my HTTP fanatic hat - I think this is actually an important
change to do. Skew like this can cause all sorts of odd behaviours in
client libraries.
+1. The current behavior of inconsistent response codes between the two
recommended
It could be that it this behavior has merely become more noticeable
since Jenkins is now reverifying patch sets when new comments show up
and it sees that the patch set hasn't been verified recently.
Carl
On Tue, Jul 1, 2014 at 5:00 PM, Jeremy Stanley fu...@yuggoth.org wrote:
On 2014-07-01
On Wed, 2 Jul 2014 00:16:42 +
Osanai, Hisashi osanai.hisa...@jp.fujitsu.com wrote:
So I think if performance of swift is more important rather than scalability
of it, it is a
good idea to use ext4.
The real problem is what happens when your drives corrupt the data.
Both ext4 and XFS
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
92 matches
Mail list logo