your guessing is right.
Swift is working now. Thank you so much.
I changed project_domain_id and user_domain_id in proxy-server.conf. and
restarted swift-proxy service.
so Swift is working. 😁
2016-07-13 15:44 GMT+09:00 James Clark :
> Hi,
>
> > On Jul 13, 2016, at 3:29 PM, Nalee Jang wrote:
>
Hi,
Can you be more specific about which versions of OpenStack mitaka do you
use? E.g. package, source code installation, etc.
Nikolay Starodubtsev
Software Engineer
Mirantis Inc.
Skype: dark_harlequine1
2016-07-10 20:58 GMT+03:00 zhihao wang :
> Dear Murano team member
>
>
> I want to ins
Below is the latest spec for vlan-aware-vms
https://specs.openstack.org/openstack/neutron-specs/specs/newton/vlan-aware-vms.html
I have a quick question on the above. (multi-tenancy).
Assume the case of nested containers in a VM.
Yes, the containers can be in different networks of the same tena
Hi,
I am trying to understand the mechanism used by Swift to determine
which storage node to send a GET request to.
I have a single node setup with 4 disks: r1, r2, r3 and r4. For a
given container and object-name, the swift-get-nodes -a output shows
the following:
Server:Port Device 127.0.0.1:6
Hi,
here is the section about installing murano in our docs:
http://docs.openstack.org/developer/murano/draft/admin-guide/deploy_murano.html
There are official debian packages for murano
https://tracker.debian.org/pkg/murano
There are also murano packages in ubuntu-cloud.archive
http://ubuntu-cl
I see that this can be related to error_suppression_limit and
error_suppression_interval.
When the GET request is sent, if that node had previously seen errors
>= error_suppression_limit, then for the next
error_suppression_interval seconds, this node would not be used.
Instead, some other node (h
If my calculation is correct, it still have 6 hours to go.
JULY 13, 2016 AT 11:59PM PDT (JULY 14 6:59 UTC) IS THE DEADLINE TO SUBMIT A
TALK.
However, I am seeing
Warning!
Call for Presentations is closed!.
sign from openstack.org website.
Am I missing something?
Jaesuk Ahn, Ph.
I think there was a system error, which is now fixed. I got an immediate
response from OpenStack on twitter about this. Please try now.
Regards,
Swarna.
*408-571-9643*
On Wed, Jul 13, 2016 at 6:10 PM, Jaesuk Ahn wrote:
> If my calculation is correct, it still have 6 hours to go.
>
> JULY 13,
On Thu, Jul 14, 2016 at 6:40 AM, Jaesuk Ahn wrote:
> If my calculation is correct, it still have 6 hours to go.
>
> JULY 13, 2016 AT 11:59PM PDT (JULY 14 6:59 UTC) IS THE DEADLINE TO SUBMIT A
> TALK.
>
> However, I am seeing Warning! Call for Presentations is closed!. sign from
> openstack.org we
