[openstack-dev] [valence] Valence 0.9.0 Release

[Anusha Ramineni]

 Hi,

Valence team is happy to announce the initial release of Valence-0.9.0 to
PyPi. Please find the details below.


Valence PyPi url:  https://pypi.org/project/valence/ .


Documentation and Release Notes for the release can be found at:


Release Notes :
http://valence.readthedocs.io/en/latest/releasenotes/valence-0.9.html

Documentation : http://valence.readthedocs.io/en/latest/


Thanks,
Anusha
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Congress] Congress Dashboard and Containers

[Anusha Ramineni]

Hi Tim, Aimee,

Yes, ideally only congress_dashboard is required on the same server as
horizon for horizon to discover the plugin, but right now
congress_dashboard is also part of congress repo, so congress needs to be
installed on the same server.

I'm thinking for a while to move the repo to separate project, maybe its
high time we move the congress_dashboard repo to separate project like
other projects do? wdyt?
http://docs.openstack.org/developer/horizon/plugin_registry.html


Best Regards,
Anusha

On 9 December 2016 at 03:24, Tim Hinrichs  wrote:

> I wouldn't expect Congress needs to be on the same server as Horizon.
> Anusha, do you know for sure?
>
> Tim
>
>
> On Thu, Dec 8, 2016 at 1:20 PM Aimee Ukasick 
> wrote:
>
>> All - we are looking into deploying Congress in its own container,
>> separate from the container that OpenStack is in. I know which Congress
>> dashboard files need to be copied to Horizon, and from what I can tell,
>> it looks like Congress and Horizon must be running on the same server
>> for the Congress dashboard to work. Is this assumption correct?
>>
>>
>> Thanks!
>>
>>
>> Aimee Ukasick, AT&T
>>
>>
>>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
>> unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Congress] Restart Congress server

[Anusha Ramineni]

Hi Ruben,

If you have configured congress through devstack, the default way of
starting congress server would be
python /usr/local/bin/congress-server --node-id=allinonenode --config-file
/etc/congress/congress.conf ,
but the way you start the service sounds ok, as others would be default
parameters.

Devstack by default should set all the default configurations in
congress.conf required for setting up congress, so make sure you have all
the required services up (nova, glance) from which congress polls data. If
you have an issue with initial setup of congress itself, as Eric suggested
would be better to restack again, as devstack does its job to re-configure
congress again from start.

If you still see the issue, I suggest you join #congress IRC channel , so
that anyone from congress team should be able to help you.

Best Regards,
Anusha

On 6 November 2016 at 22:18, Ruben  wrote:

> Hi Eric,
> also with the old congress.conf file there is the error.
> I've used devstack with a single-process congress deployment.
>
> To stop the congress server I make: screen -x stack and Ctrl-C in the
> congress window.
> To restart the congress server I make: screen -x stack and sudo
> /usr/local/bin/congress-server --debug in the congress window.
>
> Is it possible that I should rejoin the stack?
>
> Ruben
>
> - Original Message -
> From: "Eric" 
> To: openstack-dev@lists.openstack.org
> Cc: "Ruben" 
> Sent: Friday, November 4, 2016 7:23:50 PM
> Subject: Re: [Congress] Restart Congress server
>
> Hi Ruben,
>
> Awesome to hear about your progress!
>
> The error seems to be independent of adding a new driver.
>
> Could you try using the unchanged congress.conf and restarting again to
> see if the same problem shows up?
>
> Also, could you give the command you¹re using the launch congress-server?
>
> Mainly I want to understand whether you¹re using single-process congress
> deployment or multi-process congress deployment. If multi-process, it¹s
> possible that the datasources process was stopped but wasn¹t restarted.
>
>
> If your screen listing (access by pressing Ctrl-A followed by ") shows
> three congress windows like this, then you¹re running in multi-process
> mode:
> 29 congress-api
> $(L)
>   30 congress-engine
>   $(L)
>   31 congress-datasources
>   $(L)
>
> To launch Congress, make sure all three are running properly.
>
> A simpler alternative (but takes some time) is to deploy devstack from
> scratch (saving your work somewhere of course) using the latest versions
> (defaults to single process), which should reduce complications from
> multiple processes and make everything easier for dev-testing.
>
> All the best!
>
>
>
> On 11/4/16, 4:53 AM, "Ruben"  wrote:
>
> >Hi everyone,
> >I've tried to write a datasource driver for Magnum and the unit test for
> >it.
> >So I've add this datasource driver in
> >/opt/stack/congress/congress/datasources/ and the unit test in
> >/opt/stack/congress/congress/tests/datasources/ to test it.
> >Moreover, I've add the driver to /etc/congress/congress.conf, but when I
> >try to restart Congress server I've some errors.
> >
> >
> >"2016-11-04 12:13:00.390 TRACE congress.service self.service_id,
> >service, table)
> >2016-11-04 12:13:00.390 TRACE congress.service   File
> >"/opt/stack/congress/congress/dse2/dse_node.py", line 468, in
> >subscribe_table
> >2016-11-04 12:13:00.390 TRACE congress.service {'table': table})
> >2016-11-04 12:13:00.390 TRACE congress.service   File
> >"/opt/stack/congress/congress/dse2/dse_node.py", line 355, in
> >invoke_service_rpc
> >2016-11-04 12:13:00.390 TRACE congress.service raise
> >exception.NotFound(msg % service_id)
> >2016-11-04 12:13:00.390 TRACE congress.service NotFound: service 'nova'
> >could not be found
> >2016-11-04 12:13:00.390 TRACE congress.service
> >2016-11-04 12:13:00.537 DEBUG oslo_concurrency.lockutils [-] Acquired
> >semaphore "singleton_lock" from (pid=24411) lock
> >/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:212
> >2016-11-04 12:13:00.538 DEBUG oslo_concurrency.lockutils [-] Releasing
> >semaphore "singleton_lock" from (pid=24411) lock
> >/usr/local/lib/python2.7/dist-packages/oslo_concurrency/lockutils.py:225"
> >
> >I don't know what to do to solve it and even if the driver I've written
> >works.
> >Maybe I make mistakes when I restart Congress server..
> >What should I do to restart Congress server?
> >What could I do to test the datasource and solve these problems?
> >
> >Ruben
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

Re: [openstack-dev] [ceilometer] [Congress] ceilometer client `alarms.list()` HTTPException (HTTP N/A)

[Anusha Ramineni]

Hi Eric,

alarm list is not working from before.
I have disabled the same in Mitaka https://review.openstack.org/#/c/254650/
We need to support Aodh to get it working I suppose (
https://blueprints.launchpad.net/congress/+spec/add-aodh-datasource-driver)


Best Regards,
Anusha

On 29 September 2016 at 19:28, Julien Danjou  wrote:

> On Mon, Sep 26 2016, Eric K wrote:
>
> > On a fresh devstack install with ceilometer clients version 2.6.1,
> > client.alarms.list() errors when other things (like client.events.list())
> > succeeds.
>
> Do you have Aodh installed?
> Why not switching to aodhclient?
>
> --
> Julien Danjou
> ;; Free Software hacker
> ;; https://julien.danjou.info
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Congress] Default devstack deployment config

[Anusha Ramineni]

Hi All,

I too agree from the development point of view, its easier if we have a
single process.
But I was wondering, tempest jobs we run on gate, isn't it better they run
with 3 processes deployed, to make sure it works across processes too?

Just a thought, how about we keep both the options, so that developers can
deploy as single process and on gate we can test it with different
processes?

Best Regards,
Anusha

On 13 September 2016 at 18:10, Aimee Ukasick 
wrote:

> I completely agree with a single process deployment for DevStack. I
> ran into issues last week with the multiple process configuration
> while I trying to pinpoint an error.  I was using the pdb command line
> debugger to step through Congress and Oslo Messaging, making a call
> from the CLI. More than once the Congress API couldn't find the
> Process Engine, which I'm sure was caused by uploading code and
> stopping/starting services in the wrong order.  Deploying single
> process Congress to DevStack would have saved me a lot of time.
>
> aimee
>
> On Tue, Sep 13, 2016 at 1:42 AM, Masahito MUROI
>  wrote:
> > Hi Congress folks,
> >
> > I'm in favor of single process for devstack default. It's easy to check
> > logs and tests its feature.
> >
> > best regards,
> > Masahito
> >
> > On 2016/09/13 11:00, Tim Hinrichs wrote:
> >>
> >> I'd agree with a single process version of Congress for devstack.  I'd
> >> say we should even do that for Newton.
> >>
> >> Tim
> >>
> >> On Mon, Sep 12, 2016 at 6:34 PM Eric K  >> > wrote:
> >>
> >> Hi all,
> >>
> >> I want to get people’s thoughts regarding what we should set as
> >> default devstack deployment config for Ocata.
> >> At the moment, it is set to deploy three processes: API, policy, and
> >> datasource-drivers.
> >>
> >> I see some potential arguments against that:
> >>
> >>  1. For most users installing via devstack, running Congress in
> >> three processes bring little benefit, but rather a more complex
> >> and less stable user experience. (Even if our code is perfect,
> >> rabbitMQ will timeout every now and then)
> >>  2. It’s not clear that we want to officially support separating the
> >> API from the policy engine at this point. The supported
> >> deployment options for HAHT do not need it.
> >>
> >> The main argument I see for deploying three processes by default is
> >> that we may get more bug reports regarding the multi-process
> >> deployment that way.
> >>
> >> Our main options for devstack default are:
> >> 1. Single-process Congress (with in-mem transport).
> >> 2. Two-process Congress API+Policy, datasource-drivers. (other
> >> breakdowns between two processes are also possible)
> >> 3. Three-process Congress.
> >>
> >> In the end, I think it’s a trade-off: potentially getting more bug
> >> reports from users, at the expense of a more complex and less
> >> polished user experience that could make a poor first impression.
> >> What does everyone think?
> >>
> >> Personally, I slightly favor defaulting to single process Congress
> >> because from a typical devstack user’s perspective, there is little
> >> reason to run separate processes. In addition, because it is the
> >> first time we’re releasing our complete architecture overhaul to the
> >> wild, and it may be a good to default to the least complex
> >> deployment for the first cycle of the new architecture.
> >>
> >> 
> __
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe:
> >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> >>  unsubscribe>
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >>
> >>
> >> 
> __
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >>
> >
> >
> > --
> > 室井 雅仁(Masahito MUROI)
> > Software Innovation Center, NTT
> > Tel: +81-422-59-4539
> >
> >
> >
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___

Re: [openstack-dev] [Congress] Congress horizon plugin - congressclient/congress API auth issue - help

[Anusha Ramineni]

Hi Aimee,

Thanks for the investigation.

I remember testing congress client with V3 password based authentication ,
which worked fine .. but never tested with token based .

Please go ahead and fix it , if you think there is any issue .

On 22-Jul-2016 9:38 PM, "Aimee Ukasick"  wrote:

> All - I made the change to the auth_url that  Anusha suggested.
> Same problem as before " Cannot authorize API client"
> 2016-07-22 14:13:50.835861 * calling policies_list =
> client.list_policy()*
> 2016-07-22 14:13:50.836062 Unable to get policies list: Cannot
> authorize API client.
>
> I used the token from the log output to query the Congress API with
> the keystone v3 token - no issues.
> curl -X GET -H "X-Auth-Token: 18ec54ac811b49aa8265c3d535ba0095" -H
> "Cache-Control: no-cache" "http://192.168.56.103:1789/v1/policies";
>
> So I really think the problem is that the python-congressclient
> doesn't support identity v3.
> I thought it did, but then I came across this:
> "support keystone v3 api and session based authentication "
> https://bugs.launchpad.net/python-congressclient/+bug/1564361
> This is currently assigned to Anusha.
> I'd like to start work on it since I am becoming familiar with keystone v3.
>
> Thoughts?
>
> aimee
>
>
>
>
> On Fri, Jul 22, 2016 at 8:07 AM, Aimee Ukasick
>  wrote:
> > Thanks Anusha! I will retest this today. I guess I need to learn more
> > about Horizon as well - thanks for pointing me in the right direction.
> >
> > aimee
> >
> >
> >
> > On Fri, Jul 22, 2016 at 6:30 AM, Anusha Ramineni 
> wrote:
> >> Hi Aimee,
> >>
> >> I think devstack by default configured horizon to use v3 .
> >> For V2 authentication, from the logs , auth_url doesn't seem to be set
> >> explicitly to v2 auth_url .
> >>
> >> I have always set explicit v2 auth which worked fine.
> >> For eg:- auth_url = 'http://:5000/v2.0' , for V2
> authentication
> >>
> >> I have raised a patch, to take the auth_url from horizon settings
> instead of
> >> from request.
> >> https://review.openstack.org/#/c/345828/1
> >>
> >> Please set explict v2 auth_url as mentioned above in
> OPENSTACK_KESYTONE_URL
> >> in /openstack_dashboard/local/local_settings.py and restart
> apache2
> >> server . Then v2 authentication should go through fine.
> >>
> >> For v3 , need to add relevant code for v3 authentication in
> contrib/horizon
> >> as presently it is hardcoded to use only v2. but yes, the code from
> plugin
> >> model patch is still a WIP , so doesn't work for v3 authentication I
> guess
> >> I'll have a look at it and let you know .
> >>
> >>
> >> Best Regards,
> >> Anusha
> >>
> >> On 21 July 2016 at 21:56, Tim Hinrichs  wrote:
> >>>
> >>> So clearly an authentication problem then.
> >>>
> >>> Anusha, do you have any ideas?  (Aimee, I think Anusha has worked with
> >>> Keystone authentication most recently, so she's your best bet.)
> >>>
> >>> Tim
> >>>
> >>> On Thu, Jul 21, 2016 at 8:59 AM Aimee Ukasick
> >>>  wrote:
> >>>>
> >>>> The  Policy/Data Sources web page throws the same errors. I am
> >>>> planning to recheck direct API calls using v3 auth today or tomorrow.
> >>>>
> >>>> aimee
> >>>>
> >>>> On Thu, Jul 21, 2016 at 10:49 AM, Tim Hinrichs  wrote:
> >>>> > Hi Aimee,
> >>>> >
> >>>> > Do the other APIs work?  That is, is it a general problem
> >>>> > authenticating, or
> >>>> > is the problem limited to list_policies?
> >>>> >
> >>>> > Tim
> >>>> >
> >>>> > On Wed, Jul 20, 2016 at 3:54 PM Aimee Ukasick
> >>>> > 
> >>>> > wrote:
> >>>> >>
> >>>> >> Hi all,
> >>>> >>
> >>>> >> I've been working on Policy UI (Horizon): Unable to get policies
> >>>> >> list (devstack) (https://bugs.launchpad.net/congress/+bug/1602837)
> >>>> >> for the past 3 days. Anusha is correct - it's an authentication
> >>>> >> problem, but I have not been able to fix it.
> >>>> >>
> >>>> >> I grabbed the relevant code in congress.py from A

Re: [openstack-dev] [Congress] Congress horizon plugin - congressclient/congress API auth issue - help

[Anusha Ramineni]

Hi Aimee,

I think devstack by default configured horizon to use v3 .
For V2 authentication, from the logs , auth_url doesn't seem to be set
explicitly to v2 auth_url .

I have always set explicit v2 auth which worked fine.
For eg:- auth_url = 'http://:5000/v2.0' , for V2 authentication

I have raised a patch, to take the auth_url from horizon settings instead
of from request.
https://review.openstack.org/#/c/345828/1

Please set explict v2 auth_url as mentioned above in OPENSTACK_KESYTONE_URL
 in /openstack_dashboard/local/local_settings.py and restart
apache2 server . Then v2 authentication should go through fine.

For v3 , need to add relevant code for v3 authentication in contrib/horizon
as presently it is hardcoded to use only v2. but yes, the code from plugin
model patch is still a WIP , so doesn't work for v3 authentication I guess
I'll have a look at it and let you know .


Best Regards,
Anusha

On 21 July 2016 at 21:56, Tim Hinrichs  wrote:

> So clearly an authentication problem then.
>
> Anusha, do you have any ideas?  (Aimee, I think Anusha has worked with
> Keystone authentication most recently, so she's your best bet.)
>
> Tim
>
> On Thu, Jul 21, 2016 at 8:59 AM Aimee Ukasick 
> wrote:
>
>> The  Policy/Data Sources web page throws the same errors. I am
>> planning to recheck direct API calls using v3 auth today or tomorrow.
>>
>> aimee
>>
>> On Thu, Jul 21, 2016 at 10:49 AM, Tim Hinrichs  wrote:
>> > Hi Aimee,
>> >
>> > Do the other APIs work?  That is, is it a general problem
>> authenticating, or
>> > is the problem limited to list_policies?
>> >
>> > Tim
>> >
>> > On Wed, Jul 20, 2016 at 3:54 PM Aimee Ukasick <
>> aimeeu.opensou...@gmail.com>
>> > wrote:
>> >>
>> >> Hi all,
>> >>
>> >> I've been working on Policy UI (Horizon): Unable to get policies
>> >> list (devstack) (https://bugs.launchpad.net/congress/+bug/1602837)
>> >> for the past 3 days. Anusha is correct - it's an authentication
>> >> problem, but I have not been able to fix it.
>> >>
>> >> I grabbed the relevant code in congress.py from Anusha's horizon
>> >> plugin model patchset (https://review.openstack.org/#/c/305063/3) and
>> >> added try/catch blocks, logging statements (with error because I
>> >> haven't figured out how to set the horizon log level).
>> >>
>> >>
>> >> I am testing the code on devstack, which I cloned on 19 July 2016.
>> >>
>> >> With both v2 and v3 auth, congressclient.v1.client is created.
>> >> The failure happens trying to call
>> >> congressclient.v1.client.Client.list_policies().
>> >> When using v2 auth, the error message is "Unable to get policies list:
>> >> The resource could not be found"
>> >> When using v3 auth, the error message is "Cannot authorize API client"
>> >>
>> >> I am assuming that congressclient.v1.client.Client is
>> >>
>> >>
>> https://github.com/openstack/python-congressclient/blob/master/congressclient/v1/client.py
>> >> and that client.list_policy() calls list_policy()in the
>> >> python-congressclient
>> >> which in turn calls the Congress API. Is this correct?
>> >>
>> >> Any ideas why with v3 auth, the python-congressclient cannot authorize
>> the
>> >> call to the API?
>> >>
>> >> I looked at other horizon plugin models (ceilometer, neutron, nova,
>> >> cerberus, cloudkitty, trove, designate, manila) to see how they created
>> >> the client. While the code to create a client is not identical,
>> >> it is vastly different from the code to create a client
>> >> in contrib/horizon/congress.py.
>> >>
>> >> Thanks in advance for any pointers.
>> >>
>> >> aimee
>> >>
>> >> Aimee Ukasick (aimeeu)
>> >>
>> >> v2 log:
>> >> 2016-07-20 22:13:56.501455
>> >> 2016-07-20 22:14:30.238233 * view.get_data calling policies =
>> >> congress.policies_list(self.request) *
>> >> 2016-07-20 22:14:30.238318 * self.request.path=
>> >> /dashboard/admin/policies/
>> >> 2016-07-20 22:14:30.238352 * congress.policies_list(request)
>> >> BEGIN*
>> >> 2016-07-20 22:14:30.238376 * calling client =
>> >> congressclient(request)*
>> >> 2016-07-20 22:14:30.238399 * congress.congressclient BEGIN*
>> >> 2016-07-20 22:14:30.238454 * auth_url=
>> http://192.168.56.103/identity
>> >> 2016-07-20 22:14:30.238479 * calling get_keystone_session *
>> >> 2016-07-20 22:14:30.238505 * congress.get_keystone_session BEGIN
>> >> auth_url *http://192.168.56.103/identity
>> >> 2016-07-20 22:14:30.238554 * path= /identity
>> >> 2016-07-20 22:14:30.238578 * using V2 plugin to authenticate*
>> >> 2016-07-20 22:14:30.238630 * v2 auth.get_auth_state=
>> >> 2016-07-20 22:14:30.238656 None
>> >> 2016-07-20 22:14:30.238677 * finished using V2 plugin to
>> >> authenticate*
>> >> 2016-07-20 22:14:30.238698 * creating session with auth *
>> >> 2016-07-20 22:14:30.244407 * congress.get_keystone_session END*
>> >> 2016-07-20 22:14:30.244462 * regtion_name= RegionOne
>> >> 2016-07-20 22:14:30.244491 * calling
>> congress_client.Client

Re: [openstack-dev] [Congress] Nominating Anusha Ramineni and Eric Kao for core reviewer

[Anusha Ramineni]

Thanks. It's great working with you guys and I'm glad to be part of this
team :)
+1.

On 2016/05/14 9:16, Tim Hinrichs wrote:

> Hi all,
>
> I'm writing to nominate Anusha Ramineni and Eric Kao as Congress core
> reviewers.  Both Anusha and Eric have been active and consistent
> contributors in terms of code, reviewing, and interacting with the
> community since September--for all of Mitaka and a few months before that.
>
> Anusha was so active in Mitaka that she committed more code than the
> other core reviewers, and wrote the 2nd most reviews over all.  She took
> on stable-maintenance, is the first person to fix gate breakages, and
> manages to keep Congress synchronized with the rest of the OpenStack
> projects we depend on.  She's taken on numerous tasks in migrating to
> our new distributed architecture, especially around the API.  She
> manages to write honest yet kind reviews, and has discussions at the
> same level as the rest of the cores.
>
> Eric also committed more code in Mitaka than the other core reviewers.
> He has demonstrated his ability to design and implement solutions and
> work well with the community through the review process.  In particular,
> he completed the Congress migration to Python3 (including dealing with
> the antlr grammar), worked through difficult problems with the new
> distributed architecture (e.g. message sequencing, test-nondeterminism),
> and is now designing an HA deployment architecture.  His reviews and
> responses are both thoughtful and thorough and engages in discussions at
> the same level as the rest of the core team.
>
> Anusha and Eric: it's great working with you both!
>
> Tim
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>

-- 
室井 雅仁(Masahito MUROI)
Software Innovation Center, NTT
Tel: +81-422-59-4539



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Congress] Issues with Tox testing

[Anusha Ramineni]

Hi Bryan,

Yes, tempest can be run outside devstack deployments. Please check the
README in https://github.com/openstack/tempest on configuring tempest.

As in liberty, you need to copy the tests to tempest, I guess installing
tempest on diff server also should work as long as congress service is
discoverable (never tried though) . But just to let you know, congress
Liberty version has minimal tempest coverage, In Mitaka we have enabled all
the tempest tests.

Best Regards,
Anusha

On 12 April 2016 at 10:43, Bryan Sullivan  wrote:

> Hi Anusha,
>
> That helps. Just one more question: in Liberty (which I'm currently based
> upon) have the tempest tests been run outside of devstack deployments, i.e.
> in an actual OpenStack deployment? The guide you reference mentions
> devstack but it's not clear that the same process applies outside devstack:
>
> e.g. "To list all Congress test cases, run command in /opt/stack/tempest:"
> references the "/opt/stack" folder which is not created outside of devstack
> environments. Thus to run them in a full OpenStack deployment, do I need to
> install  tempest and create an "opt/stack/tempest" folder to which the
> tests are copied, on the same server where Congress is installed?
>
> I'll try Mitaka soon but I expect to have the same question there:
> basically, are the tempest tests expected to be usable outside a devstack
> deploy?
>
> I guess I could just try it, but I don't want to waste time if this is not
> designed to be used outside devstack environments.
>
> Thanks,
> Bryan Sullivan
>
> --
> Date: Fri, 8 Apr 2016 09:01:29 +0530
> From: anusha.ii...@gmail.com
>
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Congress] Issues with Tox testing
>
> Hi Bryan,
>
> tox -epy27 doesn't run tempest tests , that is tests mentioned in
> https://github.com/openstack/congress/tree/stable/liberty/contrib/tempest
>  ,
> it runs only unit tests , tests present in
> https://github.com/openstack/congress/tree/stable/liberty/congress/tests .
>
> To run tempest tests, you need to manually copy the files to tempest and
> run the tests as mentioned in following readme
> https://github.com/openstack/congress/blob/stable/liberty/contrib/tempest/README.rst
>
> Mitaka supports tempest plugin, so manually copying tests to tempest can
> be avoided if you are using mitaka.
>
> Hope I clarified your question.
>
>
> Best Regards,
> Anusha
>
> On 8 April 2016 at 08:51, Bryan Sullivan  wrote:
>
> OK, somehow I did not pick up on that, or dropped it along the way of
> developing the script. Thanks for the clarification, also that Tempest is
> not required. I should have clarified that I'm using stable/liberty as the
> base. I will be moving to stable/mitaka soon, as part of the OPNFV Colorado
> release development.
>
> One additional question then - are the tests run by "tox -epy27" the same
> as the tests in the folder
> https://github.com/openstack/congress/tree/stable/liberty/contrib/tempest?
> If not, how are those tests supposed to be run for a non-devstack deploy (I
> see reference to devstack in the readme)?
>
> I see that the folders have been reorganized for mitaka. My question is
> per the goal to include as much of the Congress tests as possible in the
> OPNFV CI/CD process. Not that I expect any to fail, I just want OPNFV to
> leverage the full test suite. If for liberty that's best left as the tests
> run by the tox command, then that's OK.
>
> Thanks,
> Bryan Sullivan
>
> --
> Date: Thu, 7 Apr 2016 17:11:36 -0700
> From: ekcs.openst...@gmail.com
> To: openstack-dev@lists.openstack.org
>
> Subject: Re: [openstack-dev] [Congress] Issues with Tox testing
>
> Thanks for the feedback, Bryan. Glad you got things working!
>
> 1. The instructions asking to install those packages are missing from kilo
> (we’ll fix that), but they have been there since liberty. Was it perhaps
> unclear because the line is too long?
>
>- Additionally:
>
>$ sudo apt-get install git gcc python-dev libxml2 libxslt1-dev libzip-dev 
> mysql-server python-mysqldb build-essential libssl-dev libffi-dev
>
>
> 2. Tempest should not be required by the tox tests.
>
> Thanks!
>
> From: Bryan Sullivan 
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Thursday, April 7, 2016 at 4:29 PM
> To: "openstack-dev@lists.openstack.org"  >
> Subject: Re: [openstack-dev] [Congress] Issues with Tox testing
>
> An update: I found that there were two dependencies needed that were not
> clear in the guide at https://github.com/openstack/congress. I also
> installed Tempest which was not referenced before. If these additions are
> correct (they worked for me), they should be added to
> https://github.com/openstack/congress/blob/master/README.rst.
>
> $ sudo apt-get install libffi-dev libssl-dev
> $ cd ~/git
> $ 

Re: [openstack-dev] [Congress] Issues with Tox testing

[Anusha Ramineni]

Hi Bryan,

tox -epy27 doesn't run tempest tests , that is tests mentioned in
https://github.com/openstack/congress/tree/stable/liberty/contrib/tempest
 ,
it runs only unit tests , tests present in
https://github.com/openstack/congress/tree/stable/liberty/congress/tests .

To run tempest tests, you need to manually copy the files to tempest and
run the tests as mentioned in following readme
https://github.com/openstack/congress/blob/stable/liberty/contrib/tempest/README.rst

Mitaka supports tempest plugin, so manually copying tests to tempest can be
avoided if you are using mitaka.

Hope I clarified your question.


Best Regards,
Anusha

On 8 April 2016 at 08:51, Bryan Sullivan  wrote:

> OK, somehow I did not pick up on that, or dropped it along the way of
> developing the script. Thanks for the clarification, also that Tempest is
> not required. I should have clarified that I'm using stable/liberty as the
> base. I will be moving to stable/mitaka soon, as part of the OPNFV Colorado
> release development.
>
> One additional question then - are the tests run by "tox -epy27" the same
> as the tests in the folder
> https://github.com/openstack/congress/tree/stable/liberty/contrib/tempest?
> If not, how are those tests supposed to be run for a non-devstack deploy (I
> see reference to devstack in the readme)?
>
> I see that the folders have been reorganized for mitaka. My question is
> per the goal to include as much of the Congress tests as possible in the
> OPNFV CI/CD process. Not that I expect any to fail, I just want OPNFV to
> leverage the full test suite. If for liberty that's best left as the tests
> run by the tox command, then that's OK.
>
> Thanks,
> Bryan Sullivan
>
> --
> Date: Thu, 7 Apr 2016 17:11:36 -0700
> From: ekcs.openst...@gmail.com
> To: openstack-dev@lists.openstack.org
>
> Subject: Re: [openstack-dev] [Congress] Issues with Tox testing
>
> Thanks for the feedback, Bryan. Glad you got things working!
>
> 1. The instructions asking to install those packages are missing from kilo
> (we’ll fix that), but they have been there since liberty. Was it perhaps
> unclear because the line is too long?
>
>-
>
>Additionally:
>
>$ sudo apt-get install git gcc python-dev libxml2 libxslt1-dev libzip-dev 
> mysql-server python-mysqldb build-essential libssl-dev libffi-dev
>
>
> 2. Tempest should not be required by the tox tests.
>
> Thanks!
>
> From: Bryan Sullivan 
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Thursday, April 7, 2016 at 4:29 PM
> To: "openstack-dev@lists.openstack.org"  >
> Subject: Re: [openstack-dev] [Congress] Issues with Tox testing
>
> An update: I found that there were two dependencies needed that were not
> clear in the guide at https://github.com/openstack/congress. I also
> installed Tempest which was not referenced before. If these additions are
> correct (they worked for me), they should be added to
> https://github.com/openstack/congress/blob/master/README.rst.
>
> $ sudo apt-get install libffi-dev libssl-dev
> $ cd ~/git
> $ git clone https://github.com/openstack/tempest/
> $ cd tempest
> $ ~/git/congress/bin/pip install -r requirements.txt
> $ ~/git/congress/bin/pip install .
>
> (not sure if both pip commands are needed - I'm not an expert on pip
> install)
>
> After that, "tox -epy27" ran thru fine:
>
> ---
> ---
> congress.tests.policy_engines.test_vmplacement.TestComputeVmAssignment.test_set_policy_with_dashes
> 27.623
> congress.tests.policy_engines.test_vmplacement.TestComputeVmAssignment.test_set_policy
> 27.212
> congress.tests.policy_engines.test_agnostic_performance.TestRuntimePerformance.test_simulate_latency
> 1.325
> congress.tests.dse.test_dse.TestDSE.test_policy_tables
> 1.229
> congress.tests.policy_engines.test_agnostic_performance.TestRuntimePerformance.test_select_100matches
> 1.184
> congress.tests.test_congress.TestCongress.test_policy_execute
> 1.127
> congress.tests.test_congress.TestCongress.test_datasource_api_model_execute
> 1.067
> congress.tests.policy_engines.test_agnostic_performance.TestRuntimePerformance.test_update_nonrecursive
> 0.967
> congress.tests.dse.test_dse.TestDSE.test_policy_table_publish
> 0.681
> congress.tests.datasources.test_neutron_driver.TestDataSourceDriver.test_poll_subscribe
> 0.671
> __ summary
> ___
>   py27: commands succeeded
>   congratulations :)
>
>
>
> Thanks,
> Bryan Sullivan
>
> --
> From: bls...@hotmail.com
> To: openstack-dev@lists.openstack.org
> Date: Thu, 7 Apr 2016 11:16:48 -0700
> Subject: [openstack-dev] [Congress] Issues with Tox testing
>
> Hi Congress team,
>
>

Re: [openstack-dev] [Congress] New bug for Mitaka: Glance authentication fails after token expiry

[Anusha Ramineni]

+1 for using keystone sessions,  I have already raised a patch for the same.
https://review.openstack.org/#/c/299121/

Any comments are welcome :)


Best Regards,
Anusha

On 30 March 2016 at 11:33, Kairat Kushaev  wrote:

> Hi,
> I proposed a fix for that: https://review.openstack.org/299136.
> Looking forward for yout feedback in that.
>
> I also reviewed Congress patch a bit and I am wondering if Keystone
> sessions is appropriate approach to work with client in services like
> Congress.
>
>
>
> Best regards,
> Kairat Kushaev
>
> On Tue, Mar 29, 2016 at 10:56 PM, Nikhil Komawar 
> wrote:
>
>> Thanks for bringing this up Eric!
>>
>> On 3/29/16 4:01 PM, Eric K wrote:
>> > I just discovered a bug that¹s probably been around a long time but
>> hidden
>> > by exception suppression.
>> https://bugs.launchpad.net/congress/+bug/1563495
>> > When an auth attempt fails due to token expiry, Congress Glance driver
>> > obtains a new token from keystone and sets it in Glance client, but for
>> > some reason, Glance client continues to use the expired token and fails
>> to
>> > authenticate. Glance data stops flowing to Congress. It might explain
>> the
>> > issue Bryan Sullivan ran into
>> > (
>> http://lists.openstack.org/pipermail/openstack-dev/2016-February/087364.ht
>> > ml).
>> >
>> > I haven¹t been able to nail down whether it¹s a Congress datasource
>> driver
>> > issue or a Glance client issue. A few more eyes on it would be great.
>> > Thanks!
>> >
>> >
>> >
>> >
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> --
>>
>> Thanks,
>> Nikhil
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Congress] Nominating Masahito for core

[Anusha Ramineni]

+1

Best Regards,
Anusha

On 17 February 2016 at 00:59, Peter Balland  wrote:

> +1
>
> From: Tim Hinrichs 
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Tuesday, February 16, 2016 at 11:15 AM
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Subject: [openstack-dev] [Congress] Nominating Masahito for core
>
> Hi all,
>
> I'm writing to nominate Masahito Muroi for the Congress core team.  He's
> been a consistent contributor for the entirety of Liberty and Mitaka, both
> in terms of code contributions and reviews.  In addition to volunteering
> for bug fixes and blueprints, he initiated and carried out the design and
> implementation of a new class of datasource driver that allows external
> datasources to push data into Congress.  He has also been instrumental in
> migrating Congress to its new distributed architecture.
>
> Tim
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Congress] tempest tests in gate not running

[Anusha Ramineni]

Tim,

Previous failure on gate is fixed with this patch
https://review.openstack.org/#/c/247314/
Now congress tempest tests are running, so our tempest plugin worked :)
http://logs.openstack.org/10/237510/5/check/gate-congress-dsvm-api/0bdbb53/console.html

Current gate failures report a different issue which should be solved by
this patch
https://review.openstack.org/#/c/247375/2

Best Regards,
Anusha

On 23 November 2015 at 22:00, Tim Hinrichs  wrote:

> It looks like our tempest tests aren't running in the gate.  Here's a
> recent patch that just merged this morning.
>
> https://review.openstack.org/#/c/242305/
>
> If you go to the testr results, you'll see a list of all the tests that
> were run.
>
>
> http://logs.openstack.org/05/242305/5/gate/gate-congress-dsvm-api/979bc9d/testr_results.html.gz
>
> Two things: (i) there are many tests here that are not Congress-specific
> and (ii) I don't see the Congress tests running at all.  During manual
> testing both these issues were handled by the following lines in our gate
> job config.
>
>
> https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/congress.yaml#L33-L34
>
> The good news, at least, is that congress is getting properly spun up.
>
>
> http://logs.openstack.org/05/242305/5/gate/gate-congress-dsvm-api/979bc9d/logs/screen-congress.txt.gz
>
> Would someone want to volunteer to dig into this?
>
> Tim
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Congress] kilo bug on datasource listing

[Anusha Ramineni]

Yes, this is fixed in liberty as part of this bug ,
https://bugs.launchpad.net/congress/+bug/1492354.
I have cherry-picked the same onto kilo branch -
https://review.openstack.org/#/c/248514/

Best Regards,
Anusha

On 21 November 2015 at 06:07, Tim Hinrichs  wrote:

> Congress stable-maintenance team:
>
> We seem to have a bug in kilo that is making it tough for Bryan Sullivan
> to get things up and running.  The swift driver doesn't have a 'secret'
> field, which is causing a 500 error when listing datasources.  If I
> remember right, we fixed this bug later.
>
> https://bugs.launchpad.net/congress/+bug/1518496
>
> Could someone volunteer to fix it?  I think we should do a release once
> that's in.
>
> Tim
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev