Thanks!
On Mon, Apr 6, 2015 at 06:22 Tom Fifield wrote:
> Reminder: deadline is April 8th.
>
> Please go to:
>
> http://www.openstack.org/user-survey
>
> and tell your friends.
>
> Any problems - mail me :)
>
>
> Regards,
>
>
> Tom
>
> On 26/03/15 11:35, Tom Fifield wrote:
> > Hi all,
> >
> > As
Is there any limit as well for LVM backends ?
On Mon, Apr 6, 2015 at 2:12 AM, John Griffith
wrote:
>
>
> On Sun, Apr 5, 2015 at 2:42 PM, John Griffith > wrote:
>
>>
>> On Apr 5, 2015 2:10 PM, "mad Engineer" wrote:
>>
>>> Read about cinder multi backend support,for using different backend
>>> t
Hi Sripria,
Here is the full log http://pastebin.com/8pqupFnw
It looks the problem is in Neutron-ODL communication. Has anyone seen
this before? Note this only happens after rebooting. stack, unstack,
stack, unstack works.
2015-04-06 11:24:27.177 ERROR neutron.plugins.ml2.managers
[req-177
Thanks Samuel,
I researched and windows send request with win1254 charset. So, I need
to change
win1254 to utf-8 character set in windows. Thank you for your help.
Regards.
2015-04-03 21:29 GMT+03:00 Samuel Merritt :
> On 4/3/15 1:42 AM, mehmet hacısalihoğlu wrote:
>
>> Hi All,
>>
>> When I req
On a single node using multi-backend you should keep in mind all of your
iSCSI traffic going through that node. Usual VG size limits apply of
course as well. Some guidelines I've heard from various OpenStack vendors
in the past suggest 5TB max on a single cinder-volume/LVM node. From there
add m
Hi,
trove-api.log returns :
Error calling get_filesystem_stats TRACE trove.guestagent.api Traceback (most
recent calllast): TRACE trove.guestagent.api
File"/root/sample/trove/trove/guestagent/api.py", line 54, in_call TRACE
trove.guestagent.api timeout=timeout_sec) TRACE trove.guestagent.ap
hey guys,
I have a OpenStack instance behind a firewall...I want to grant API access
via a proxy...proxy works on teh specific OpenStack API ports...I can
authenticate againsta it...but the problem is that authentication returns
me the local OpenStack IP (192.168.100.10)
How can I do to tell Ope
Hi Sharada,
Looks like you are modifying the *.conf.sample files instead of the
*.conf file. Try editing the .conf files under /etc/trove and restart the
Trove services. Then try restarting the Trove services and try again
Thanks,
Mariam.
From: Sharada R
To: "openstack@lists.opensta
> I have a OpenStack instance behind a firewall...I want to grant API access
> via a proxy...proxy works on teh specific OpenStack API ports...I can
> authenticate againsta it...but the problem is that authentication returns
> me the local OpenStack IP (192.168.100.10)
>
> How can I do to tell Op
Hello Alexander,
I faced a similar issue and here are some pointers which helped me debug.
When you reboot, make sure the integration bridge, br-int is there. Also, you
would want to confirm if the OVSDB is connected properly to the controller and
no stale flows exists in the OpenFlow tables.
Sharada,
It sounds like you’re also working with Mariam on this and I saw her response
to you on this. I’ll see if you are able to fix your problem based on her
response.
-amrith
From: Sharada R [mailto:sharu8...@yahoo.com]
Sent: Monday, April 06, 2015 1:45 AM
To: Amrith Kumar; Mark Kirkwood;
11 matches
Mail list logo