Hi Karan,
I faced a similar issue earlier. I was able to resolve this by doing the
following:
1. Changing the values of url's pointing to keystone from localhost/127.0.0.1
to Machine IP address. Restart cinder service.
2.If this does not work. Then replace all the kesytone related config variab
And consider well your networking: available bandwidth, redundancy,
how front-end client traffic and back-end traffic share or don't share
resources. Red Hat, Inc in their storage products typically advocates
keeping internal-to-swift network traffic off of NICs handling client
traffic.
Networkin
Swift has a modular design, and this allows you the flexibility to deploy to
match your needs.
Common deployment patterns are (1) proxy, account, container, object all
running on the same hardware (2) proxy on one SKU and account+container+object
on another SKU (3) proxy on one SKU, account+con
Hi Rem:
I know OUTPUT in the native iptables table is go out, but since l3agent is
playing a role of router, all data from VM to extenal network is
FORWARD/PREROUTE/POSTROUT, so why does l3agent add a
neutron-l3-agent-OUTPUT chain in OUTPUT chain in nat table, is this chain
necessary? The pkg amou
hi,
You can go to http://docs.openstack.org/developer/swift/index.html to find
what you want.
And the Source Documentation will tell you How the servers communicate.
Regards
-- Original --
From: "Pravar Jawalekar";;
Date: Mon, Nov 25, 2013 01:26 PM
T
Hi Dheerendra,
Good to know about this.
Let us know the agenda and place for this session.
We are planning to have Meetup at our office in the last week of Feb or
first week of March 2014. We will post the event schedule on OpenStack
India meetup page once dates are finalized.
Regards,
Balaji.P
Dear Stackers!!
I have one question related to 'how swift is actually deployed in
production environment',
How object/container/auth servers made communicate to actual underlying
storage infrastructure?
I mean do deployment strategy of swift imposes any such restrictions that
services for containe
Hi Dheerendra-
Good to know this ..
Can you kindly update the plans/agenda for the Technical Deep Dive Session.
Thanking you,
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
From: Dheerendra [mailto:dheerendra.madhusudh...@gmail.com]
Sent: Monday, November 25, 2013 9:46
Hi Stackers @Hyd India
We are planning to conduct 2 days technical deep dive/hands-on session on
OpenStack. We are planning somewhere in the 2nd or 3rd week of December.
This session is for new comers to kick-start the OpenStack. Off-course
experienced people are welcome for the session. They can
Hi Stackers @India Hyderabad
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
On Sun, Nov 24, 2013 at 12:40 PM, Daniel Speichert wrote:
> Hi Guillermo,
> Please set:
> libvirt_inject_password=True
> in /etc/nova/nova.conf on compute nodes and try again.
> This feature is very confusing, not documented at all and I don't really
> know what authors tried to to here.
> Probabl
On Sat, Nov 23, 2013 at 1:31 AM, Russell Bryant wrote:
> Greetings,
>
> The maintainers of the PowerVM driver have proposed that it be removed
> from Nova. Their reasons are:
>
> - it is no longer in line with IBM's strategic direction with OpenStack
I have unapproved / untargetted the followin
the output of dkpg is:
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==--==
Hi Guillermo,
Please set:
libvirt_inject_password=True
in /etc/nova/nova.conf on compute nodes and try again.
This feature is very confusing, not documented at all and I don't really know
what authors tried to to here.
Probably the way it works depends on virtualization method. In KVM, you ca
Hi,
Im running devstack, and it looks like the 'nova x509-create-cert' and
'nova x509-get-root-cert' commands are taking a really long time to
complete (minutes). I even get timeouts:
ERROR: HTTPConnectionPool(host='192.168.126.142', port=8774): Read
timed out. (read timeout=600.0)
Telnetting t
On 11/24/2013 08:06 AM, John Smith wrote:
Hi.
Im trying to (re-)run devstack on my vmware fedora 19 vm, but now i
get the error listed below.
It looks like the fedora 19 'i386' directory doesnt exist, there's
just a 'source' and 'x86_64' subdir. For comparison, the fedora 18 dir
f18 does have
Hi Karan
Some more stuff
1. Run cinder --debug list. This will give some info on token sent, url
sent etc.
2.
http://docs.openstack.org/api/quick-start/content/index.html#Openstack-API-Concepts-a09234.
Just look command 1 and 2.
This link and examples will give good details on what is happeni
On Sun, Nov 24, 2013 at 4:53 PM, Steven Dake wrote:
>
>
> John,
>
> theforeman is in your /etc/yum.repos.d directory. It appears either they
> got rid of their i386 dirs or they are down temporarily. Unfortunately
> devstack can't tell the difference between a repo it doesn't need
> (theforeman)
On Sun, Nov 24, 2013 at 4:30 PM, Dean Troyer wrote:
>
> You are simply having a problem reaching the listed repo:
>
>>
>> http://yum.theforeman.org/releases/1.3/f19/i386/repodata/repomd.xml:
>> [Errno 14] HTTP Error 404 - Not Found
>
>
> Can you get this file via curl? Is yum working outside of D
On Sun, Nov 24, 2013 at 9:06 AM, John Smith wrote:
> It looks like the fedora 19 'i386' directory doesnt exist, there's
> just a 'source' and 'x86_64' subdir. For comparison, the fedora 18 dir
> f18 does have an i386 subdir. It was working yesterday :(
> For now I can work around it by setting OF
Hi Karan
This is clear case of authorization. So keystone is not able to authorize
with credential and token you are giving. Token supplied is wrong. Hence
you are hitting the issue.
I was suspecting the tenant definition as you defined it as 'services'. I
thought it is defined as 'service'(no s
Hi.
Im trying to (re-)run devstack on my vmware fedora 19 vm, but now i
get the error listed below.
It looks like the fedora 19 'i386' directory doesnt exist, there's
just a 'source' and 'x86_64' subdir. For comparison, the fedora 18 dir
f18 does have an i386 subdir. It was working yesterday :(
F
Can you past 'keystone tenant-list' and 'keystone role-list' ?
-Dheerendra
On Sun, Nov 24, 2013 at 5:35 AM, Karan Singh wrote:
> Please help I am in urgent need
>
>
> Original message
> From: Karan Singh
> Date: 23/11/2013 18:24 (GMT+02:00)
> To: openstack@lists.openstack.or
On Sun, Nov 24, 2013 at 5:47 AM, Jitendra Kumar Bhaskar
wrote:
> Hi Zakaria,
>
> Can you please share the output of :
> # dpkg -i | grep keystone
The command is
dpkg -l '*keystone*'
If the 2 chars on the left are different from "ii" you probably have to run
dpkg --configure -a
.a.
>
24 matches
Mail list logo
