[rhos-list] quantum net-create throws 403 forbidden error

[Xin Zhao]

Hello,

While debugging this issue further, I now wonder where the port 9696 is 
supposed to be open, on the network node or the controller node (where 
the networking service API runs) ?
When it's time to define the endpoint of the quantum service, the doc 
says the IP of the endpoint should be the one of the network node, with 
port 9696.
But the quantum-server daemon runs on the controller node on port 9696. 
I must get one of them wrong, any wisdom on this ?

Thanks,
Xin

On 10/11/2013 1:49 PM, Xin Zhao wrote:
> Hello,
>
> I will try the packstack later, right now since I have worked a long 
> way through the RHOS document, I would like
> to finish the remaining two services, quantum and nova, instead of 
> starting over with the new packstack approach,
> if it's possible.
>
> But now I am stuck with configuring quantum. Even after I configured 
> the identity/qpid/plugin part on the network node,
> the command still returns 403 error. Even when I run the same command 
> from the controller host, I get the same error:
>
> [root at controller ~(keystone_admin)]# quantum net-create public01 
> --router:external True --provider:network_type flat 
> --provider:physical_network physnet1
> (403, 'Forbidden')
> [root at controller ~(keystone_admin)]# quantum net-list
> (403, 'Forbidden')
>
> Any help will be greatly appreciated ? Or, should I jump to the 
> "Networking Admin Guide" off the openstack homepage, and start 
> following instructions there
> to configure quantum ?
>
> Thanks,
> Xin
>
>
> On 10/11/2013 11:25 AM, Lars Kellogg-Stedman wrote:
>> On Fri, Oct 11, 2013 at 11:07:28AM -0400, Xin Zhao wrote:
>>> The credential file is the same, and there is nothing in the logs.
>>>
>>> BTW, I may misunderstand the doc, do I also need to configure identity
>>> service, message broker
>>>   and plugin on both the network host and compute nodes ?
>> You only need to run a single instance of these services, but you do
>> need to make sure that your configuration points to the correct host.
>> If you're installing RHOS using packstack this should all be taken
>> care of for you.
>>
>> If you're not installing RHOS using packstack, you may want to try
>> that first; documentation on using packstack for deploying RHOS is
>> available here:
>>
>> https://access.redhat.com/site/documentation/en-US/Red_Hat_OpenStack/3/html/Getting_Started_Guide/part-Deploying_OS_using_PackStack.html
>>
>> This is a largely automated process that can configure a multi-node
>> OpenStack environment.
>>
>
> _______________________________________________
> rhos-list mailing list
> rhos-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rhos-list