Dear List,
i got stuck with a setup of openstack grizzly. This setup consists of:
- swift proxy 1.0.8.1
- swift storage nodes 1.0.8.1
- keystone
- ceilometer
I kept browsing the web and reading openstack docs for days now and
can't just get it working right. Because of openstacks diversity a
w
a 'ResellerAdmin' role and assign that role to your
> ceilometer user. Alternatively you can define the 'reseller_admin_role'
> parameter (default value=ResellerAdmin) in the [filter:authtoken]
> section of /etc/swift/proxy-server.conf.
> Cheers,
> Simon
>
> L
The mystery seems solved. There it a webadmin for swauth.
https://github.com/gholt/swauth#web-admin-install
Does there exists is similar thing for keystone?
Regards, Axel
Am 16.04.13 14:53, schrieb Axel Christiansen:
>
>
> Thanks for your quick reply, Simon,
>
&
Dear List,
after upgrading to grizzly, swift-recon returns this. Could not find out
to much in the logs.
Can one give me a hint?
root@ns-proxy01:~# swift-recon -d -v
===
--> Starting reconnaissance on 6 hosts
===
pipeline = recon object-server
>
> and a [filter:recon] stanza ?
>
> Regards,
> Coleman
>
> -Original Message-
> From: Openstack
> [mailto:openstack-bounces+coleman.corrigan=hp....@lists.launchpad.net] On
> Behalf Of Axel Christiansen
> Sent: 17 A
Hello List,
what GUI-Clients like Cyberduck do exist, wich can talk the v2.0 API?
Thank you
Axel
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help
Hello List again,
on the zmanda-blog is a description to make a swift/keystone setup work
again via the v1.0 API. Had anyone success doing this on grizzly?
I sadly did not.
Regards, Axel
___
Mailing list: https://launchpad.net/~openstack
Post to
up successfully on a devstack ( that's the trunk version, though,
> not grizzly ). There is a mistake in the instructions; the config file to
> modify is not /etc/keystone/keystone.conf but
> /etc/keystone/keystone-paste.ini .
>
> Hope that helps.
>
> Matthieu Huin
&g
Original Message -----
> From: "Axel Christiansen"
> To: "Matthieu Huin"
> Cc: openstack@lists.launchpad.net
> Sent: Wednesday, June 5, 2013 12:14:32 PM
> Subject: Re: [Openstack] grizzly keystone with v1.0 API
>
> Thank you Matthieu,
>
>
>
27;GATEWAY_INTERFACE': 'CGI/1.1', 'wsgi.run_once': False, 'wsgi.errors':
,
'wsgi.multiprocess': False, 'swift.trans_id':
'tx439bd9050f054697b722c4b0db5a4219', 'CONTENT_TYPE': None,
'HTTP_ACCEPT_ENCODING': 'gzip,
05.06.13 15:51, schrieb Axel Christiansen:
>
> Thanks for your configs!
>
>
> Am 05.06.13 15:20, schrieb Matthieu Huin:
>> With the config I've sent, the v1 API is accessible at a URL looking like
>> this: http://endpoint:5000/v1.0
>>
>> What do you g
Dear List,
i am trying to retrieve measurements from swift via ceilometer.
ceilometer stores its measurements in db and so. looks good.
The ceilometer V2 Web API is expecting resource_id as UUID value, for
example. I can not find a UUID anywere. When listing resources (GET
/v2/resources/) the r
Its working now. Must have made a mistake :)
Greets Axel
Am 01.07.13 16:42, schrieb Axel Christiansen:
> Dear List,
>
>
> i am trying to retrieve measurements from swift via ceilometer.
> ceilometer stores its measurements in db and so. looks good.
>
>
> The
Hello List,
does one has to use the real device names in ring-building, like:
swift-ring-builder account.builder add z5-10.0.6.204:6002/sda4 100
Here it is sda4.
Can one use the partition UUID value or the mount point?
What if a drive has a fialure and a reboot of the system is done with
this
Thanks. Thats nice. So mounting via UUID ensures right
drive<->mount-point mapping.
Am 10.07.13 18:23, schrieb Samuel Merritt:
> On 7/10/13 2:25 AM, Axel Christiansen wrote:
>> Hello List,
>>
>>
>> does one has to use the real device names in ring-buil
Hi.
I am using these repos to setup nova on a debian 7. Looks like the
grizzly package nova-api-os-compute is missing and therefore breaks
dependency.
deb http://archive.gplhost.com/debian grizzly main
deb http://archive.gplhost.com/debian grizzly-backports main
Was looking a little around. Do
Hello List,
i got stock getting a swift store running. the base components, a proxy
some storage nodes are prepared. The keystone service is up and seems
working ok. Authentication works.
wehn trying to create a container this happens:
swift -v -s -V 2.0 -A http://10.42.44.206:5000/v2.0 -U dem
@swiftstack.com>
> tonyt...@gmail.com
> <mailto:tonyt...@gmail.com>
> +886 935004793
>
>
> 2013/7/12 Jonathan Lu mailto:jojokur...@gmail.com>>
>
> Hi,
> I once met such problem because I forget to change the own of
> the directory of th
/7/12 Jonathan Lu mailto:jojokur...@gmail.com>>
>>
>> Hi,
>> I once met such problem because I forget to change the own of
>> the directory of the mounted device to swift:swift.
>>
>>
>> On 2013/7/12 16:44, Axel Christiansen wrote:
he drives information in the ring?
> Would you like to show it?
>
> +Hugo Kuo+
> h...@swiftstack.com <mailto:h...@swiftstack.com>
> tonyt...@gmail.com
> <mailto:tonyt...@gmail.com>
> +886 935004793
>
>
> 2013/7/12 Axel Christiansen <mailto:axel.christian...@
Dear List,
i am trying to figure out what ceilometer components nedds to bo
installed an what nodes.
I have 2 swift-proxy-hosts and 1 ceiloemeter-host
These are the packages debian7 respectively the grizzly repo offers:
ceilometer-agent-central - OpenStack efficient metering counters system
. And just the ceilometer-api ist for the dedecated
ceilometer-host?
Axel
Am 24.07.13 15:33, schrieb Julien Danjou:
> On Wed, Jul 24 2013, Axel Christiansen wrote:
>
> Hi Axel,
>
> If you want to only meter Swift, you just need:
>
>> ceilometer-agent-central ceilomet
22 matches
Mail list logo
