On 07/03/14 18:03, Mark Kirkwood wrote:
The wrong concerns the action given to trove-manage in the Prepare
Database section:
$ trove-manage --config-file=PathToTroveConf image_update mysql
`nova --os-username trove --os-password trove --os-tenant-name trove
--os-auth-url http
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
localrc:
disable_service n-net
On 08/07/14 00:40, Amrith Kumar wrote:
I think it is totally ludicrous (and to all the technical writers who work on
OpenStack, downright offensive) to say the “docs are useless”. Not only have I
been able to install and successfully operate a OpenStack installation by
(largely) following
On 08/07/14 17:08, Denis Makogon wrote:
Mark, there are also no documentation about service tuning(no description
of service related options, sample configs in Trove repo is not enough).
So, I think we should extend your list of significant things to document.
Right - I guess most of the
On 08/07/14 17:08, Denis Makogon wrote:
Mark, there are also no documentation about service tuning(no description
of service related options, sample configs in Trove repo is not enough).
So, I think we should extend your list of significant things to document.
...and in case it might be
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
and ask if he needs
any help)
Best regards,
Denis Makogon
On Thu, Jul 10, 2014 at 9:24 AM, Mark Kirkwood
mark.kirkw...@catalyst.net.nz mailto:mark.kirkw...@catalyst.net.nz
wrote:
Where I work we make use of Postgresql for most of our database
needs. It would be nice to be able to offer
In my latest devstack pull I notice that
backup_namespace
restore_namespace
have moved from the default conf group to per datastore (commit
61935d3). However they still appear in the common_opts section of
trove/common/cfg.py
This seems like an oversight - or is there something I'm
On 01/08/14 21:35, Denis Makogon wrote:
I'd suggest to file a bug
report and fix given issue.
Done.
https://bugs.launchpad.net/trove/+bug/1351545
I also took the opportunity to check if all the currently defined
datastores had backup/restore_namespace set - they didn't, so I noted
that
On 02/08/14 18:24, Denis Makogon wrote:
Mark, we don't have to add backup/restore namespace options to datastores that
does't support backup/restore feature.
You should take a look how backup procedure is being executed at Trove-API
service site, see
Hi all,
There is some interest here in making use of Murano for Samba ADDC a
service...so we've been (attempting) to get it up and running in
devstack. In the process I've managed to get myself confused about the
correct instructions for doing this:
- the docs suggest
setup it should be done by a command: tox -evenv -- murano-manage
--config-file etc/murano/murano-api.conf db-sync
It works in my testing environment.
Thanks
Georgy
On Tue, Apr 15, 2014 at 4:11 PM, Mark Kirkwood
mark.kirkw...@catalyst.net.nz wrote:
Hi all,
There is some interest here in making
On 25/09/14 15:37, Qiming Teng wrote:
Hi,
Some weeks ago, I checked my then latest devstack install and I learned
this: event support in Ceilometer is only available for sqlalchemy
backend; mongodb backend was still under development. I have been using
MySQL during the past weeks and now I
I've been looking at how the 3 nova_proxy_admin_* settings are used. I'm
coming to the conclusion that I'm confused:
E.g I note that a standard devstack (stable/juno branch) with trove
enabled sets these as follows:
nova_proxy_admin_pass =
nova_proxy_admin_tenant_name = trove
exchange.
These aren't needed on the guest-agent, and that's probably the reason why a
non-existing value of radmin seems to work. The fact that this exists in
the guest
configuration as well is probably a bug and should be cleaned up.
Cheers,
Nikhil
On Tue, Jan 20, 2015 at 4:05 PM, Mark Kirkwood
On 18/12/14 14:30, 乔建 wrote:
When using trove, we need to configure nova’s user information in the
configuration file of trove-guestagent, such as
lnova_proxy_admin_user
lnova_proxy_admin_pass
lnova_proxy_admin_tenant_name
Is it necessary? In a public cloud environment, It will lead to
On 11/01/15 22:25, Denis Makogon wrote:
Guest agent doesn't need configuration options described above. IIRC,
only taskmanager needs them.
Right - so we need to update the default config files and doco - as they
have them in there.
About passing auth data. What are those benefits of
On 09/05/15 02:28, Monty Taylor wrote:
On 05/08/2015 03:45 AM, Nikhil Manchanda wrote:
Comments and answers inline.
Li Tianqing writes:
[...]
1) why we put the trove vm into user's tenant, not the trove's
tenant? User can login on that vm, and that vm must connect to
On 17/04/15 09:20, Qiming Teng wrote:
Wondering if there is something misconfigured in my devstack
environment, which was reinstalled on RHEL7 about 10 days ago.
I'm often running into mysql connections problem as shown below:
$ mysql
ERROR 1040 (HY000): Too many connections
When I try dump
On 21/06/15 01:32, Doug Hellmann wrote:
Excerpts from Dave Walker's message of 2015-06-20 14:05:48 +0100:
On 20 Jun 2015 1:05 pm, Doug Hellmann d...@doughellmann.com wrote:
SNIP
Whether we want to support 3.4 and 3.5, or just 3.4 and then just 3.5
is an ecosystem question IMO, not an
I've looking at using puppet-swift to deploy a swift cluster.
Firstly - without
http://git.openstack.org/cgit/stackforge/puppet-swift/tree/tests/site.pp
I would have struggled a great deal more to get up and running, so a big
thank you for a nice worked example of how to do multiple nodes!
On 12/06/15 17:27, Mark Kirkwood wrote:
I've looking at using puppet-swift to deploy a swift cluster.
Firstly - without
http://git.openstack.org/cgit/stackforge/puppet-swift/tree/tests/site.pp
I would have struggled a great deal more to get up and running, so a big
thank you for a nice worked
is not immediately useful without surgery :-)
Regards
Mark
On 13/06/15 18:05, Mark Kirkwood wrote:
From what I can see, the ring gets created and rebalanced in
puppet-swift/manifest/ringbuilder.pp i.e calling:
class { '::swift::ringbuilder':
# the part power should be determined
. Unless you explicitly set the
seed (to same value on all node obviously), you won't get the same ring on all nodes. You also need
to make sure you add the same set of drives and in same order.
Regards,
Donagh
-Original Message-
From: Mark Kirkwood [mailto:mark.kirkw...@catalyst.net.nz
On 10/07/15 12:43, Mark Kirkwood wrote:
Hi,
I am using puppet-swift to deploy a swift multi node cluster (Icehouse),
following the setup in supplied tests/site.pp. I am running into two
issues that seem to be related to the subject above:
1/ Errors when the storage replication services try
On 14/07/15 11:05, Mark Kirkwood wrote:
On 13/07/15 06:44, Emilien Macchi wrote:
Yeah, I guess I should raise a bug with Ubuntu so it (maybe) gets sorted
out. However in the meantime we may have to work around it by amending
the dir permissions in puppet (the alternative - rolling our own
On 13/07/15 06:44, Emilien Macchi wrote:
I think this is something that could be fixed in packaging scripts.
I can see you're using Puppet to deploy OpenStack, and fwiw, we are
stopping to manage permissions in Puppet because of packaging overlap.
From now, we totally rely on packaging
Hi,
I'm deploying a swift 1.13 cluster on Ubuntu 14.04 and enabling
ceilometer in the proxy pipeline results in it not working.
The cause appears to be the log directory perms (note I am running the
proxy under Apache):
[Fri Jul 10 05:12:15.126214 2015] [:error] [pid 6844:tid
* require one more puppet run on the
storage nodes:
- one to create the storage servers config and drives
- one to get the ring from the proxy/ringmaster
- one to start the services
Regards
Mark
From 1583d68eedbeaecbacb5a29258343b9e980ce4a4 Mon Sep 17 00:00:00 2001
From: Mark Kirkwood mark.kirkw
After looking at:
https://www.youtube.com/watch?v=9YHvYkcse-k
I have a question (that follows on from Bruno's) about using erasure
coding with geo replication.
Now the example given to show why you could/should not use erasure
coding with geo replication is somewhat flawed as it is
On 15/02/16 23:29, Kota TSUYUZAKI wrote:
Hello Mark,
AFAIK, a few reasons for that we still are in working progress for erasure code
+ geo replication.
and expect to survive a region outage...
With that I mind I did some experiments (Liberty swift) and it looks to me like
if you have:
-
On 16/02/16 17:10, Mark Kirkwood wrote:
On 15/02/16 23:29, Kota TSUYUZAKI wrote:
Hello Mark,
AFAIK, a few reasons for that we still are in working progress for
erasure code + geo replication.
and expect to survive a region outage...
With that I mind I did some experiments (Liberty swift
usters
3:
http://docs.openstack.org/developer/swift/overview_erasure_code.html#region-support
4:
https://specs.openstack.org/openstack/swift-specs/specs/in_progress/global_ec_cluster.html
(2016/02/15 18:00), Mark Kirkwood wrote:
After looking at:
https://www.youtube.com/watch?v=9YHvYkcse-k
On 21/06/17 02:08, Jay Pipes wrote:
On 06/20/2017 09:42 AM, Doug Hellmann wrote:
Does "service VM" need to be a first-class thing? Akanda creates
them, using a service user. The VMs are tied to a "router" which
is the billable resource that the user understands and interacts with
through the
On 20/04/18 04:54, Dean Troyer wrote:
On Thu, Apr 19, 2018 at 7:51 AM, Doug Hellmann wrote:
Excerpts from Mark Kirkwood's message of 2018-04-19 16:47:58 +1200:
Swift has had storage policies for a while now. These are enabled by
setting the 'X-Storage-Policy' header
Swift has had storage policies for a while now. These are enabled by
setting the 'X-Storage-Policy' header on a container.
It looks to me like this is not possible using openstack-client (even in
master branch) - while there is a 'set' operation for containers this
will *only* set 'Meta-*'
36 matches
Mail list logo