[openstack-dev] update congress

Yue Xin xinyuefeiyang at gmail.com
Sun Jun 5 22:17:15 UTC 2016


Hi Tim

Thank you so much for your response.
 I will try to install mitaka later on, seems interesting.



*Regards,*
*Yue*

On 2 June 2016 at 12:05, Tim Hinrichs <tim at styra.com> wrote:

> Hi Yue,
>
> Sorry it took so long to get back to you.  I wanted to run your script to
> see the errors myself.  The authorization failed errors you're seeing are
> coming from the datasources, right?  In Mitaka, we changed several of the
> datasource drivers to use a newer feature of Keystone when talking to other
> OpenStack projects, to solve some lingering problems.  If I remember right,
> that newer functionality in Keystone wasn't available in all the projects
> back in kilo/liberty.  So it seems you'll want to upgrade those as well.
>
> In summary, you want to use the PushDriver from Congress, which is only
> available in Mitaka.  And the Congress Mitaka datasource drivers require
> Mitaka functionality from several of the other projects.   So it seems
> you'll need to set up a Mitaka version of OpenStack.  Since it sounds like
> you're experimenting, I'd suggest grabbing a VM and setting up a devstack
> installation using the instructions in our README:
> https://github.com/openstack/congress#41-devstack-install
>
> The only thing the README instructions don't tell you is how to run the
> Mitaka version of the code.  (The instructions tell you how to run the tip
> of master.) So to check out the Mitaka version of the code, change the
> line where you clone devstack to check out the stable/mitaka branch, such
> as follows.
>
> git clone https://git.openstack.org/openstack-dev/devstack.git -b stable/mitaka
>
> Here's a video that goes over how to install Mitaka OpenStack on Ubuntu.
> https://www.youtube.com/watch?v=NR3Ye13vdls
>
> Hope that helps,
> Tim
>
>
>
> On Mon, May 30, 2016 at 7:46 AM Yue Xin <xinyuefeiyang at gmail.com> wrote:
>
>> Hi Tim,
>>
>> I have solved the previous questions, now the problem stuck in the
>> keystone. (the solving script is attached)
>> now the problem error is: "authorization failed"
>>
>> *Regards,*
>> *Yue*
>>
>> On 27 May 2016 at 20:06, Tim Hinrichs <tim at styra.com> wrote:
>>
>>> Hi Yue,
>>>
>>> I tried it myself and hit the same problem.  I didn't find a
>>> workaround.  So it seems we have a bug.  Any chance you could install
>>> Mitaka using the DevStack instructions in the ReadMe while we find time to
>>> fix the bug?
>>>
>>> https://github.com/openstack/congress
>>>
>>> Tim
>>>
>>> On Wed, May 25, 2016 at 8:43 PM Yue Xin <xinyuefeiyang at gmail.com> wrote:
>>>
>>>>  Hi Tim,
>>>>
>>>> Thanks for the instruction. But I face some problem here.
>>>>
>>>> The code path of congress is /opt/stack/congress; I go to this path and
>>>> run the command "git fetch origin" the error comes  :
>>>> [image: Inline images 1]
>>>> but I can successfully ping the address git.openstack.org
>>>> [image: Inline images 2]
>>>>
>>>> I solve this problem by
>>>>
>>>> [image: Inline images 1]
>>>> change 'origin' url to https:
>>>> this somehow works for me.
>>>>
>>>> But when I run the command "sudo congress-db-manage --config-file
>>>> /etc/congress/congress.conf upgrade head"
>>>> the error is :
>>>> [image: Inline images 2]
>>>> now I have no clue how to solve it?
>>>>
>>>> Thans a lot for any advice.
>>>>
>>>>
>>>>
>>>>
>>>> *Regards,*
>>>> *Yue*
>>>>
>>>> On 24 May 2016 at 16:44, Tim Hinrichs <tim at styra.com> wrote:
>>>>
>>>>> Hi Yue,
>>>>>
>>>>> That version of Congress definitely doesn't have the Push driver.  The
>>>>> Push driver code was implemented only in the latest release (Mitaka).
>>>>>
>>>>> Here are the upgrade instructions.  They SHOULD work, but let us know
>>>>> if you run into problems, both so we can help you and so we can correct the
>>>>> instructions.
>>>>>
>>>>> https://review.openstack.org/#/c/320652/2/README.rst
>>>>>
>>>>> Tim
>>>>>
>>>>> On Tue, May 24, 2016 at 3:40 AM Yue Xin <xinyuefeiyang at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Tim and all,
>>>>>>
>>>>>> May I ask how to update the congress version with the Tokyo Hands on
>>>>>> Lab environment? cause I use the command "openstack congress list version"
>>>>>> it show the congress is 2013's version.
>>>>>>
>>>>>> The reason why I want to update it is that I write a demo driver,
>>>>>> which I want to push data into the datasource table, but when I use 'curl
>>>>>> -i -g -X PUT ' command , the error is "501 not implemented" , same error
>>>>>> comes with 'curl -X PUSH', I am not sure whether it comes from the version
>>>>>> of congress or not(I thought maybe congress is too old so it doesn't
>>>>>> support push data).
>>>>>>
>>>>>> Thank you very much for your response.
>>>>>>
>>>>>> *Regards,*
>>>>>> *Yue*
>>>>>>
>>>>>
>>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160605/3cb666af/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 34041 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160605/3cb666af/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 147676 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160605/3cb666af/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 21329 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160605/3cb666af/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 46018 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160605/3cb666af/attachment-0007.png>


More information about the OpenStack-dev mailing list