Re: [openstack-dev] [congress] generic push driver

It's probably worth considering PATCH instead of PUT for updating the table. http://restcookbook.com/HTTP%20Methods/patch/ You could also think about using JSON-patch to describe the requested update. It provides fine-grained update semantics: https://tools.ietf.org/html/rfc6902 Tim On Fri,

[openstack-dev] [Congress] Is it possible that congress policy do live-migration

Adding [Congress] to the subject line for proper filtering... Congress lets you execute most of the Nova client API calls. You use the same arguments you would use for the Nova client. Here are the docs for the live-migration API: scroll down to live-migrate.

Re: [openstack-dev] [congress] Using congress to improve the consistency of configuration files.

Hi Valentin, Sounds like an interesting use case. Typically we've focused on information available through APIs. In this case the information would be pulled off the disks of the machines running each service. Here's the info for our weekly meeting. If you can make that, it's a good place to

Re: [openstack-dev] [Openstack-dev] [Congress] [Designate]

This error happens happens when the translator thinks there's an object/dictionary when in actuality there's just a string. I don't know of a good way to know where in the translator the problem is, other than simplifying the input and the translator and rerunning (which you're already doing).

[openstack-dev] [Congress] PTG Activities options

Hi all, At the last IRC I volunteered to pick out a couple of group activities for the upcoming PTG. First cut is below. I could imagine dinner, an outing, or both. Restaurants --- Two options jumped out at me. If neither of these seems good I can keep looking. 1. Desta

Re: [openstack-dev] [congress] ocata client causes feature regression with pre-ocata server

At some point the client sometimes made multiple API calls. I think (c) seems right too. Tim On Sun, Jan 22, 2017 at 1:15 AM Monty Taylor wrote: > On 01/21/2017 04:07 AM, Eric K wrote: > > Hi all, > > > > I was getting ready to request release of congress client, but I >

Re: [openstack-dev] [congress] ocata client causes feature regression with pre-ocata server

How about we go into the preocata server and change requirements.txt to ensure it only supports the older clients. Something like... Python-congressclient>2.3<2.5 Or whatever the versions are. Tim On Fri, Jan 20, 2017 at 7:07 PM Eric K wrote: > Hi all, > > I was

Re: [openstack-dev] [Congress] Installation/Deployment Docs

The reason we have devstack instructions under Users is because they are so easy and make it simple to test drive Congress. To test drive you need at least a couple of services besides Congress, which makes devstack a good fit. But maybe users don't care about install at all. Operators care about

Re: [openstack-dev] [Congress] Magnum_driver

> I've seen that there is a failure for "gate-congress-pe-replicated-nv". > It's strange because I didn't have failure before. > So, what should I do now? > > Ruben > > - Messaggio originale - > Da: "Tim Hinrichs" <t...@styra.com> > A: "Ruben"

Re: [openstack-dev] [Congress] Magnum_driver

a single commit. > I don't know if I have been able.. > > Ruben > > - Messaggio originale - > Da: "Tim Hinrichs" <t...@styra.com> > A: "Ruben" <r.manganiel...@studenti.unisa.it> > Cc: openstack-dev@lists.openstack.org, "timothy l h

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

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

Re: [openstack-dev] [Congress] Magnum_driver

mmit > git review > > Isn't it correct? > > Ruben > > ----- Messaggio originale - > Da: "Tim Hinrichs" <t...@styra.com> > A: "Ruben" <r.manganiel...@studenti.unisa.it> > Cc: openstack-dev@lists.openstack.org, "timothy l hinrichs&q

Re: [openstack-dev] [Congress] Magnum_driver

iver and its unit test to review. > It seems everything works. > > Ruben > > - Original Message - > From: "Tim Hinrichs" <t...@styra.com> > To: "Ruben" <r.manganiel...@studenti.unisa.it> > Cc: openstack-dev@lists.openstack.org, &qu

Re: [openstack-dev] [Congress] Magnum_driver

o try to add the translation of pods, containers and services? > > I've add the code to review. > > Ruben > - Original Message - > From: "Tim Hinrichs" <t...@styra.com> > To: "Ruben" <r.manganiel...@studenti.unisa.it> > Cc: openstack-de

Re: [openstack-dev] [Congress] Magnum_driver

> TypeError: argument of type 'Cluster' is not iterable > 2016-11-24 20:56:27.435 TRACE congress.datasources.datasource_driver > 2016-11-24 20:56:27.435 INFO congress.datasources.datasource_driver [-] > magnum:: finished polling > > > Any suggestions to solve it? > I've

Re: [openstack-dev] [Congress] Magnum_driver

It's hard to debug that remotely. If you add the requirements.txt file with the magnum-client to the code you submitted to gerrit, the tests will run on gerrit, and I can see the errors for myself. The error message is pretty clearly saying that the module can't be found. Not sure what to

Re: [openstack-dev] [Congress] Magnum_driver

Ruben, All the software that gets imported by your code needs to be listed in requirements.txt so that when tox runs, it installs that software. When I did some debugging for you I made the necessary change, so if you add that back into your change, that error should disappear.

Re: [openstack-dev] [Congress] Magnum_driver

Hi Ruben, The fieldnames you care about are the fields as they show up in the JSON that gets returned from the magnum-client methods inside the datasource driver, e.g. from these methods... self.magnum.cluster_template.list() self.magnum.cluster.list() Several ways to check that you have the

Re: [openstack-dev] [Congress] Magnum_driver

Hi Ruben, Did a little debugging for you... 1) Run your unit tests $ tox -epy34 congress.tests.datasources.test_magnum ... File "/Users/tim/opencode/congress/congress/tests/datasources/test_magnum_driver.py", line 3, in from congress.datasources import magnum_driver File

Re: [openstack-dev] [Congress] Error datasource create

Here's the pertinent error. It looks like you have a typo in one of your translators. 2016-11-08 12:15:29.906 TRACE congress.dse2.dse_node InvalidParamException: Params (field_translators, selector_type) are invalid. Valid params: ('translation-type', 'table-name', 'parent-key', 'id-col',

[openstack-dev] [Congress] Fwd: Your draft logo & sneak peek

Hi team, I just received a draft version of our project logo, using the mascot we selected together. A final version (and some cool swag) will be ready for us before the Project Team Gathering in February. Before they make our logo final, they want to be sure we're happy with our mascot. We can

[openstack-dev] [Congress] Project for Ruben

Hi Ruben, It's great that you've decided to add a datasource driver for Magnum. A datasource driver is a good place to start. In terms of getting started, if you haven't read thru the docs, start there. The Cloud Services section will give you info on datasources; at the end there is a section

Re: [openstack-dev] [release][congress][searchlight] projects in danger of being left out of newton

Congress tagged RC1 on Friday. Tim On Mon, Sep 19, 2016 at 7:52 AM Nikhil Komawar wrote: > I think searchlight went right ahead into 1.0.0 so, I doubt if we will > have rc1. (this is just initial info, I will defer the details to the > project lead). > > > > On 9/19/16

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

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

[openstack-dev] [Congress] PTL non-candidacy

Hi all, I've decided it's time to step down as PTL of Congress. Partly because I have so many outside responsibilities, and partly because we have such a strong team, the time is right for someone else to lead the project. We've made so much progress over the past couple of years, and there's

Re: [openstack-dev] [Congress] Stack trace returned to end user bug

The Api node on Oslo-messaging sends a request to the policy node asking for say policy alpha. The policy node raises an exception, which Oslo returns to the API node. I'd imagine there is some way to have the Ali node extract the original exception or tell Oslo to return the only the original

Re: [openstack-dev] [Congress] Enabling Remote Debugging

I'd be concerned about merging a change to eventlet this late in the cycle. Threading problems are notoriously difficult to find during testing. I'd recommend pushing the patch to Gerrit, so that we can all try it out when debugging, and we check it in after the Newton release. Eric, +1 to your

[openstack-dev] [Congress] python-client push bug?

Hi all, As I was sanity checking the latest python-client, which we need to release by tomorrow, I may have found a bug that we should fix before releasing. If it's a bug in the server, that can be fixed later, but if it's a bug in the client, we should get that fixed now.

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

a Ramineni > >> > <anusha.ii...@gmail.com> 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

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

a 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 <t...@styra.com> wrote: > > Hi Aimee, > > > > Do the other APIs work? T

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

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

[openstack-dev] [Congress] Mascot

Hi all, As a reminder, we need to come up with a list of 2-3 mascots so the OpenStack Foundation can choose 1 and turn it into a logo for Congress. The mascots must come from the natural world (animals, plants, mountains, waterfalls, etc.). Deadline is July 27. I'll get the thread started with

Re: [openstack-dev] [puppet] [Congress] Request to create puppet-congress

Hi Dan, As far as the Congress team is concerned, that'd be great! Let us know how we can help. Tim On Tue, Jun 7, 2016 at 12:54 PM Dan Radez wrote: > I'd like to get puppet-congress started. > > I've written some code based on the cookie cutter structure but I've not >

Re: [openstack-dev] [congress] Spec for congress.conf

'. ``verbose`` Controls whether the INFO-level of logging is enabled. If false, logging level will be set to WARNING. Default is false. Deprecated. ``debug`` Whether or not the DEBUG-level of logging is enabled. Default is false. Tim On Tue, May 31, 2016 at 10:18 AM Tim Hinrichs &l

Re: [openstack-dev] [congress] Spec for congress.conf

We should add a section to our docs that details the config option names, their descriptions, and which ones are required. We should backport that to mitaka and maybe liberty. Tim On Mon, May 30, 2016 at 12:49 AM Masahito MUROI < muroi.masah...@lab.ntt.co.jp> wrote: > Hi Bryan, > > > On

Re: [openstack-dev] update congress

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

Re: [openstack-dev] [Congress] driver (authentication issue)

When you're doing testing like this, the easiest solution is to disable authentication. Here are the instructions from the previous email: To use curl, the easiest thing to do is go into /etc/congress/congress.conf and change the auth_strategy from keystone to noauth, and restart the congress

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

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

Re: [openstack-dev] [Congress] driver (authentication issue)

Hi Yue, Added the mailing list to this one too. Responses inline. If you're comfortable with IRC, you can go to the #congress channel on chat.freenode.net to ask question in real time. Would likely be quicker than debugging over email. On Fri, May 13, 2016 at 2:03 PM Yue Xin

Re: [openstack-dev] [Congress] with vm-placement and the third party module

ate one?(seperate driver and module) > > Thank you very much > > *Regards,* > *Yue* > > On 11 May 2016 at 21:22, Tim Hinrichs <t...@styra.com> wrote: > >> Hi Yue, >> >> I got the vm-placement code added to a datasource that seems to spin up >> and is w

Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

;> > >>>> The most straightforward use case I would suggest is when there is > >> a > >>>> problem on an instance that is caused by some problem on the > >>>> physical host. Then: > >>>> > >>>> ·Vitrage will noti

Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

Hi Alexey, Thanks for the overview of how you see a Congress-Vitrage integration being valuable. I'd imagine that the right first step in this integration would be creating a new datasource driver within Congress to pull data from Vitrage. It doesn't need to pull all the data in your list to

[openstack-dev] [Congress] Austin recap

Hi all, Here’s a quick summary of the Congress activities in Austin. Everyone should feel free to chime in with corrections and things I missed. 1. Talks Masahito gave a talk on applying Congress for fault recovery in the context of NFV.

[openstack-dev] [Congress] No meeting on April 27

No meeting for next week (April 27), since we'll be in Austin at the summit. We will send out an update about what happened during the summit next week. Tim __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [Congress]Authorization mechanisms for each user

gt; > Thanks your information, > and I'll put these information in order by myself, and consider how to > achieve it. > I'm interested in Congress project, so I'll watch the activity of Congress. > > Best regards. > > Yuki > > > > 2016-04-19 7:35 GMT+09:00 Tim

Re: [openstack-dev] [Congress]Authorization mechanisms for each user

Hi Yuki, That description was very helpful. In short, policy.json doesn't work because the person setting policy is not permitted to change policy.json (which happens in part because policy.json has no API for controlling it). In that case, using Congress makes sense. I know someone was doing

Re: [openstack-dev] [Congress]Authorization mechanisms for each user

Hi Yuki, As Masahito mentioned, the usual way to authorize API calls in OpenStack is through policy.json. If I remember right, you can make a decision about whether an API call is permitted using (i) all the values in the API call and (ii) the Keystone role of the user making the request. I'm

Re: [openstack-dev] [congress][release] missing build artifacts

Looks like the congress job is working now. We have a tarball for our latest RC: http://tarballs.openstack.org/congress/congress-3.0.0.0rc3.tar.gz Thierry added the links back for the tarball. https://github.com/openstack/releases/commit/beee35379b3b52ed7d444d93d7afd8b6603f69b6 So it looks

Re: [openstack-dev] [congress][release] missing build artifacts

Hi Doug, Thanks for letting us know. Here's what we're intending... - We'd like to release the server code for Mitaka. - We release the client to Pypi, so that's already taken care of. - We haven't moved our docs off of readthedocs yet, so we're taking care of that as well. I gave a +1 to your

Re: [openstack-dev] [Congress] Push Type Driver implementation

| n| | | | | ++--+--+--++-+--+ // List the datasources $ openstack congress datasource list 'NoneType' object has no attribute '

Re: [openstack-dev] [Congress] HOL test completed

Fantastic! We have our rc1 request in for the same Sha. Hopefully that will end up being Mitaka. Tim On Mon, Mar 21, 2016 at 4:48 PM Eric K wrote: > Happy to report that everything in Congress HOL* works as expected after > all the merges today**. > > * >

Re: [openstack-dev] [Congress] Push Type Driver implementation

I tried the doctor driver out. I just added the file to congress/datasources, and set up /etc/congress/congress.conf to include congress.datasources.doctor_driver.DoctorDriver. I could create a new doctor driver, but afterwards I couldn't list all the datasources, and I couldn't push any data to

[openstack-dev] [Congress] PTL candidacy

Hi all, I'm writing to announce my continued candidacy for Congress PTL. In the Mitaka cycle we've been working hard and making great progress on a number of things. The largest change is a new distributed architecture built on top of oslo-messaging. That architecture is key to enabling us to

[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

[openstack-dev] [Congress] Mid-cycle sprint debrief

Hi all, TL;DR. We had a great midcycle sprint. If you want to help us move Congress toward its new distributed architecture, there are a list of items you can help with below. 1. We had a productive mid-cycle sprint last week! Here were the topics we covered... - Design discussions about

[openstack-dev] [Congress] Mid-cycle sprint and next week's IRC

Just a reminder that next week Jan 26-Jan 28 is the Congress mid-cycle Sprint in the Bay Area. It's not too late to attend. It'd be best to register, but we'd love to have you in any case. More details here: https://wiki.openstack.org/wiki/Sprints/CongressMitakaSprint Also, since we're at the

Re: [openstack-dev] [Congress] [infra] IRC broken

working first, or if we just all happened to notice #congress first.) If anyone has any other pertinent details, please include them. Tim On Wed, Dec 9, 2015 at 5:07 PM Anita Kuno <ante...@anteaya.info> wrote: > On 12/09/2015 07:33 PM, Tim Hinrichs wrote: > > It seem

[openstack-dev] [Congress] IRC broken

It seems IRC is broken for the meeting we're supposed to be having right now. The symptom is that you can logon but may only see a fragment of the users/messages that are being sent. We even had a partitioning where 2 people could exchange messages, and a different 2 people could exchange

[openstack-dev] [Congress] Mid-cycle meet-up

Hi all, We're having a mid-cycle meet-up January 26-28 in the Bay Area. Here's a tentative schedule. Comments, suggestions, questions? Tue Jan 26: Discussion with Monasca team about integration. - Intro to Congress (slides or whiteboard) - Intro to Monasca (slides or whiteboard) - Design

Re: [openstack-dev] 答复: [congress]role in Congress

nt > > user. In this way, some typical or common predicates could be defined in > > a individual admin board, and other tenant user could choose which one > > to use. > On the other hand, this mentions about which user has permission to edit > and to see a policy by H

Re: [openstack-dev] [congress]role in Congress

Hi Yali, We didn't discuss role assignment for service users in Tokyo. Could you explain a bit more what you need? Tim On Sun, Nov 29, 2015 at 7:33 PM zhangyali (D) wrote: > Hi Tim and All, > > > > I remember there is a topic named “role assignment for service users”

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

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.

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

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.

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

Excerpts from Wed, Nov 11, 2015 at 10:14 AM Clint Byrum wrote: > > But as Renat mentioned, the part about triggering Mistral workflows from > > a message does not yet exist. As Tim pointed out, Congress could be a > > solution to that (listening for a message and then starting

Re: [openstack-dev] [keystone] [Mistral] Autoprovisioning, per-user projects, and Federation

without writing a policy. Tim On Mon, Nov 9, 2015 at 8:57 AM Adam Young <ayo...@redhat.com> wrote: > On 11/09/2015 10:57 AM, Tim Hinrichs wrote: > > Congress happens to have the capability to run a script/API call under > arbitrary conditions on the state of other OpenSta

Re: [openstack-dev] [keystone] [Mistral] Autoprovisioning, per-user projects, and Federation

, but it doesn't have a general purpose policy language that describes which states are permitted. Congress and Mistral are complementary, and each can stand on its own. Tim On Mon, Nov 9, 2015 at 6:46 AM Adam Young <ayo...@redhat.com> wrote: > On 11/06/2015 06:28 PM, Tim Hinri

Re: [openstack-dev] [keystone] [Mistral] Autoprovisioning, per-user projects, and Federation

Congress allows users to write a policy that executes an action under certain conditions. The conditions can be based on any data Congress has access to, which includes nova servers, neutron networks, cinder storage, keystone users, etc. We also have some Ceilometer statistics; I'm not sure

[openstack-dev] [Congress] Summit recap

Hi all, It was great seeing so many Congress people in Tokyo last week! Hopefully you've all had a chance to recover by now. Here's an overview of what happened. I was planning to go over this at this week's IRC meeting, but forgot about the U.S. time change and missed the meeting--sorry about

[openstack-dev] [Congress] IRC canceled during summit

As you might expect, next week's IRC is canceled since many of us will be attending the Tokyo summit. Tim __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Congress] Monasca @10a on Thu in Tokyo

Hi all, At the summit next week, we're planning on a 10a meeting on Thursday with the Monasca team for a deep dive. All are welcome. Tim __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Congress] Congress and Monasca Joint Session at Tokyo Design Summit

Fabio, I haven't heard back on this so I'm assuming Wed 3:40-4:20 works for you. Tim On Wed, Oct 14, 2015 at 10:51 AM Tim Hinrichs <t...@styra.com> wrote: > Hi Fabio, > > We now have a schedule. I've tentatively booked you for half of our slot > Wed 3:40-4:20. Does that

[openstack-dev] [Congress] Tokyo summit schedule

Hi all, I put a tentative schedule online for the Tokyo summit. If there are things you'd like to discuss that aren't on there, let me know. https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Congress Masahito: could you reach out to the OPNFV people that wanted to talk about their

Re: [openstack-dev] [Congress] Congress and Monasca Joint Session at Tokyo Design Summit

(fgiannet) < fgian...@cisco.com> wrote: > Thanks a lot Tim. > I really appreciate. > Fabio > > From: Tim Hinrichs <t...@styra.com> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org

Re: [openstack-dev] 答复: [Congress] Tokyo sessions

tter to know what we are going to >> talk. Thanks so much! >> >> >> >> Yali >> >> >> >> *发件人:* Tim Hinrichs [mailto:t...@styra.com] >> *发送时间:* 2015年10月2日 2:52 >> *收件人:* OpenStack Development Mailing List (not for usage questions) >> *主题:

[openstack-dev] [Congress] Couple new bugs for liberty

Hi all, Another round of manual testing revealed a couple more bugs. The ones at the bottom without the Fix-committed: https://bugs.launchpad.net/congress/+bugs/?field.tag=liberty-rc2 I have a patch for 1503392 in review. It'd be great if someone could pick up

Re: [openstack-dev] [Congress] Congress and Monasca Joint Session at Tokyo Design Summit

28, 2015 at 2:51 PM Tim Hinrichs <t...@styra.com> wrote: > > Hi Fabio: Thanks for reaching out. We should definitely talk at the > summit. I don't know if we can devote 1 of the 3 allocated Congress > sessions to Monasca, but we'll talk it over during IRC on Wed and let you

[openstack-dev] [Congress] Tokyo sessions

Hi all, We just got a tentative assignment for our meeting times in Tokyo. Our 3 meetings are scheduled back-to-back-to-back on Wed afternoon from 2:00-4:30p. I don't think there's much chance of getting the meetings moved, but does anyone have a hard conflict? Here's our schedule for Wed:

Re: [openstack-dev] [Congress] Congress Usecases VM

gt; *From:* Shiv Haris [mailto:sha...@brocade.com <sha...@brocade.com>] > *Sent:* Thursday, September 24, 2015 9:53 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Congress] Congress Usecases VM > > > > First of all I

Re: [openstack-dev] [Congress] hands on lab

Hi Alex, I went through the HOL. Some feedback... 1. When starting up, it paused for a while showing the following messages. Maybe that caused the issues I mention below. Waiting for network configuration... Waiting up to 60 more seconds for network configuration... 2. Maybe spell out the

Re: [openstack-dev] [Congress] Congress Usecases VM

.com>] > *Sent:* Thursday, September 24, 2015 9:53 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Congress] Congress Usecases VM > > > > First of all I apologize for not making it at the meeting yesterday, could &g

Re: [openstack-dev] [Congress] Congress and Monasca Joint Session at Tokyo Design Summit

Hi Fabio: Thanks for reaching out. We should definitely talk at the summit. I don't know if we can devote 1 of the 3 allocated Congress sessions to Monasca, but we'll talk it over during IRC on Wed and let you know. Or do you have a session we could use for the discussion? In any case, I'm

Re: [openstack-dev] [Congress] Congress Usecases VM

> can create, delete a rule within a policy and viewing different data > sources. > Can you please provide me the list of CLI commands for the same. > Waiting for the reply. > > > Regards > Himanshu Sharma > > On Sat, Sep 19, 2015 at 5:44 AM, Tim Hinrichs <t...@st

[openstack-dev] [Congress] stable/kilo

Could someone look into why we can't get this change to merge into stable/kilo. Note that kilo was last cycle's release. https://review.openstack.org/#/c/222698/ I tried a couple of obvious things but still no luck: https://review.openstack.org/#/c/225332/ Tim

Re: [openstack-dev] [Congress] Congress Usecases VM

It's great to have this available! I think it'll help people understand what's going on MUCH more quickly. Some thoughts. - The image is 3GB, which took me 30 minutes to download. Are all VMs this big? I think we should finish this as a VM but then look into doing it with containers to make it

[openstack-dev] [Congress] PTL candidacy

Hi all, I’m writing to announce my candidacy for Congress PTL for the Mitaka cycle. I’m excited at the prospect of continuing the development of our community, our code base, and our integrations with other projects. This past cycle has been exciting in that we saw several new, consistent

Re: [openstack-dev] [congress] IRC hangout

Hi Shiv, Our IRC is #congress. Tim On Mon, Sep 14, 2015 at 10:45 AM Shiv Haris wrote: > Hi, > > > > What is the IRC channel where congress folks hangout. I tried > #openstack-congress on freenode but is seems not correct. > > > > -Shiv > > > > > > > > *From:* Su Zhang

[openstack-dev] [Congress] Ending feature freeze

Hi all, We're now finished with feature freeze. We have our first release candidate and the stable/liberty branch. So master is once again open for new features. Couple of things to note: 1. Documentation. We should also look through the docs and update them. Documentation is really

[openstack-dev] [Congress] bugs for liberty release

Hi all, I've found a few bugs that we could/should fix by the liberty release. I tagged them with "liberty-rc". If we could all pitch in, that'd be great. Let me know which ones you'd like to work on so I can assign them to you in launchpad.

[openstack-dev] [Congress] Feedback on distributed architecture

I ran the basics of our new distributed architecture by Shawn from Twitter. Here's his response. We just held a Congress mid-cycle meet-up to discuss its distributed architecture. We decided on an architecture where the policy engine runs in its own process; each datasource driver runs in its

Re: [openstack-dev] [ceilometer] [rally] [sahara] [heat] [congress] [tripleo] ceilometer in gate jobs

I pushed a patch for Congress dependent on your patch. https://review.openstack.org/#/c/217765/ Tim On Thu, Aug 27, 2015 at 8:05 AM Sergey Lukjanov slukja...@mirantis.com wrote: Hi, I think filing the cross-project bug is ok. I've already uploaded patch for sahara jobs -

Re: [openstack-dev] [congress] simulation example in the doc not working

Hi Su, Try using 'action' instead of 'null'. 'action' is a built-in policy. It's possible that seemingly insignificant changes made the API call more strict and now force the policy you provide to actually exist. Let me know if that doesn't work, and I'll investigate further. Tim On Tue,

Re: [openstack-dev] [congress][requirements] Requirements proposal job fails

Thanks for sorting that out. +1ed the change. Tim On Thu, Aug 20, 2015 at 12:53 PM Andreas Jaeger a...@suse.com wrote: On 08/20/2015 09:32 PM, Robert Collins wrote: It was just removed from global requirements, because it was not used. That's clearly wrong. So let's refer that and add it

[openstack-dev] [Congress] [Murano] multiple numbers of arguments for table

Hi all, We're contemplating a small syntax change in the Congress policy language and wanted to see if it would cause anyone problems. Currently you can write rules that give a single table differing numbers of columns. In the following example, the 'error' table has both 1 column and 2

Re: [openstack-dev] [congress] [murano] Congress jenkins job is failing

Looks like we merged a database schema change without the migration script. I'm on it. (We'll get our tempest tests running in gate again ASAP.) Tim On Tue, Aug 18, 2015 at 7:36 AM Filip Blaha filip.bl...@hp.com wrote: Hi Congress team. Our jenkins job testing integration congress and

Re: [openstack-dev] [congress] [murano] Congress jenkins job is failing

Hi Filip, I just submitted a revert of the problematic change. Once it merges, all should be well again. Sorry for the trouble. Tim On Tue, Aug 18, 2015 at 7:57 AM Tim Hinrichs t...@styra.com wrote: Looks like we merged a database schema change without the migration script. I'm

Re: [openstack-dev] [Congress] Confused syntax error when inserting rule.

Hi Rui, The problem with the following rule is that there are a bunch of hidden variables in the not cinder:volumes(...) literal. The error message shows the hidden variables. The syntax restriction is that every variable in a negative literal must appear in a positive literal in the body.

[openstack-dev] [Congress] Mid-cycle sprint summary

Hi all, We just finished up a great 2 day sprint focusing on a new distributed architecture for Congress. Details can be found in the etherpad: https://etherpad.openstack.org/p/congress-liberty-sprint Here's the summary. 1. Architecture. Each datasource driver will run in its own process;

[openstack-dev] [Congress] meeting time change

Hi all, We managed to find a day/time where all the active contributors can attend (without being up too early/late). The room, day, and time have all changed. Room: #openstack-meeting-2 Time: Wednesday 5p Pacific = Thursday midnight UTC Next week we begin with this new schedule. And don't

Re: [openstack-dev] [Congress] meeting time change

. http://eavesdrop.openstack.org/#Congress_Team_Meeting https://review.openstack.org/#/c/207981/ Tim On Fri, Jul 31, 2015 at 9:24 AM Tim Hinrichs t...@styra.com wrote: Hi all, We managed to find a day/time where all the active contributors can attend (without being up too early/late). The room

Re: [openstack-dev] [Congress] How to start a replica ?

Could you show us the contents of /tmp/congress.conf? Tim On Mon, Jul 27, 2015 at 3:09 PM Wong, Hong hong.w...@hp.com wrote: Hi Tim and Alex, I see congress recently added the HA functionality, and I was looking at the tempest test code to understand how to start a replica. I created a

  1   2   >