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 wrote: > Looks like we merged a database schema change without the migration > script. I'm on it. (We

[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 columns.

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 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 back. >

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, Aug

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 wrote: > Hi, > > I think filing the cross-project bug is ok. I've already uploaded patch > for sahara jobs - https://review.openstack.org/217751

[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

[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. https://bugs.launchpad.net/congress/+bugs/?field.tag=

[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 important

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 [mailto:westlif...@gmail

[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 contri

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

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

te 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 wrote: > >> It's great to

[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] 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 fi

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

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 > not cut short another overlapping meeting. > > > > Also, Tim thanks for the feedback. I

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 conf

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

it is prone to user errors. I am > leaning towards halting the machine and generating an OVA file. > > > > I am looking for suggestions …. > > > > Thanks, > > > > -Shiv > > > > > > *From:* Shiv Haris [mailto:sha...@brocade.com ] > *Sent:* Thur

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

n Mon, Sep 28, 2015 at 2:51 PM Tim Hinrichs 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: Wed

[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 https://bugs.launchpad.net/congre

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

l > > 2015-10-08 9:48 GMT+08:00 zhangyali (D) : > >> Hi Tim, >> >> >> >> Thanks for informing the meeting information. But does the meeting have >> some topics scheduled? I think it’s better to know what we are going to >> talk. Thanks so much! &g

[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

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

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 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 work f

Re: [openstack-dev] Dynamic Policy for Access Control Subteam Meeting

I definitely buy the idea of layering policies on top of each other. But I'd worry about the long-term feasibility of putting default policies into code mainly because it ensures we'll never be able to provide any tools that help users (or other services like Horizon) know what the effective polic

Re: [openstack-dev] Dynamic Policy for Access Control Subteam Meeting

im On Wed, Jun 3, 2015 at 1:53 PM, Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2015-06-03 13:34:11 -0400: > > On 06/03/2015 12:10 PM, Tim Hinrichs wrote: > > > I definitely buy the idea of layering policies on top of each other. > > > But I'd w

Re: [openstack-dev] Dynamic Policy for Access Control Subteam Meeting

Inline. On Thu, Jun 4, 2015 at 6:40 AM, Sean Dague wrote: > On 06/04/2015 08:52 AM, Adam Young wrote: > > On 06/04/2015 06:32 AM, Sean Dague wrote: > >> On 06/03/2015 08:40 PM, Tim Hinrichs wrote: > >>> As long as there's some way to get the *declarative* poli

Re: [openstack-dev] [Congress] summit events

I'm sorry to have missed > the Telco talk. Are slides for those talks available online? > > > On May 12, 2015, at 1:34 PM, Tim Hinrichs wrote: > > > > (On delegation) > > Helping Telcos go Green and save OpEx via Policy > > Wed, May 20 2:4

Re: [openstack-dev] [congress] table with named parameters in rule's left side ?

Hi Radek, 1. You can't use column references on any table except those created by a datasource, mainly because Congress doesn't know the name of the columns for those tables. We've kicked around the idea of letting policy-writers declare the column names of any table, but it's trickier than it so

Re: [openstack-dev] [Congress] summit events

4/pub All these links are available on the wiki. https://wiki.openstack.org/wiki/Congress Tim On Mon, Jun 15, 2015 at 7:51 AM D'ANDREA, JOE (JOE) < jdand...@research.att.com> wrote: > Tim, > > > On Jun 9, 2015, at 10:04 AM, Tim Hinrichs wrote: > > > > Hi Joe, >

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

Hi all, In the last couple of IRCs we've been talking about running a mid-cycle sprint focused on enabling our message bus to span multiple processes and multiple hosts. The message bus is what allows the Congress policy engine to communicate with the Congress wrappers around external services li

Re: [openstack-dev] [Congress] Mid-cycle sprint

ntegrate oslo.messaging thoroughly (even replacing DSE). > > Thanks. > > > > BR > > Zhou Zhenzan > > > > *From:* Tim Hinrichs [mailto:t...@styra.com] > *Sent:* Wednesday, June 17, 2015 05:14 > *To:* OpenStack Development Mailing List (not for usage questi

Re: [openstack-dev] [Congress] Mid-cycle sprint

ng the size of the > Congress team. > > Hotels might be a bit of an issue, as we are getting close, and they are > starting to book up, but the BU admin has let us know that we can get dorm > space is people so desire. > > > > On 06/16/2015 05:13 PM, Tim Hinrichs wrote: > &g

Re: [openstack-dev] [Congress] Mid-cycle sprint

.messaging. But this API is still useful for other external services > that don’t use oslo.messaging notification to publish changes and are > willing to integrate with Congress this way. > > Anyway, I can upload my draft bp for review at first. > > Thanks. > > > > BR > >

[openstack-dev] [Congress] Hands-on-lab setup instructions

At the IRC this week, Bryan asked how he could replicate the environment we used at the Vancouver hands-on-lab. So we added some basic instructions at the end of the lab write-up. https://docs.google.com/document/u/1/d/1lXmMkUhiSZYK45POd5ungPjVR--Fs_wJHeQ6bXWwP44/pub Bryan: hope that helps. Let

[openstack-dev] [Congress] IRC on 6/30 canceled

Hi all, Since almost all the cores are on vacation next week, we're canceling the IRC meeting on 6/30. Expect slow responses for reviews and email all next week. Tim __ OpenStack Development Mailing List (not for usage quest

[openstack-dev] [congress] mid cycle Sprint dates

Hi all! We settled on dates and location for the Congress mid cycle sprint: Aug 6-7 VMware campus, Palo Alto, CA Please RSVP if you plan to come so we can get a headcount. Hope to see you there! Tim __ OpenStack Developmen

Re: [openstack-dev] [congress] mid cycle Sprint dates

AM Jeremy Stanley wrote: > On 2015-07-01 15:40:31 + (+), Tim Hinrichs wrote: > > We settled on dates and location for the Congress mid cycle sprint: > [...] > > Invoking the spirit of Thierry, please remember to add it to the > list at: > > https://wiki

Re: [openstack-dev] [Murano][Congress] Application placement use case

Hi Gosha, This definitely sounds like an interesting use case for Congress. Keep in mind that Congress doesn't itself do placement (though we did some experimentation with that [1][2]). Some thoughts. 1. Let's suppose Murano/Congress/etc. allow us to figure out which app should be deployed in w

Re: [openstack-dev] [Murano][Congress] Application placement use case

Sorry--hit the Send button by accident. > Hi Gosha, > > This definitely sounds like an interesting use case for Congress. Keep in > mind that Congress doesn't itself do placement (though we did some > experimentation with that [1][2]). Some thoughts. > > 1. Let's suppose Murano/Congress/etc. al

[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

[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 m

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

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**. > > * > https://docs.google.com/document/d/1ispw

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

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

[openstack-dev] [Congress][Delegation] Google doc for working notes

Hi all, A (growing) group of folks are interested in working on the problem of delegating policy from Congress to domain-specific policy engines. We started looking at an NFV use case: migrating VMs to reduce energy consumption. In particular we’re looking into building a VM-placement policy

Re: [openstack-dev] [congress][Policy][Copper]Collaboration between OpenStack Congress and OPNFV Copper

Hi Zhipeng, We’d be happy to meet. Sounds like fun! I don’t know of anyone on the Congress team who is planning to attend the LF collaboration summit. But we might be able to send a couple of people if it’s the only real chance to have a face-to-face. Otherwise, there are a bunch of us in a

Re: [openstack-dev] [Congress][Delegation] Google doc for working notes

rom: Debo~ Dutta mailto:dedu...@cisco.com>> Date: Wednesday, February 11, 2015 at 4:48 PM To: Tim Hinrichs mailto:thinri...@vmware.com>> Cc: "Yathiraj Udupi (yudupi)" mailto:yud...@cisco.com>>, Gokul B Kandiraju mailto:go...@us.ibm.com>>, Prabhakar Kudva mailto:

Re: [openstack-dev] [congress][Policy][Copper]Collaboration between OpenStack Congress and OPNFV Copper

also just find some bugs and get directly involved in Congress to address them, or start a collaborative development project in OPNFV for that. TBD Thanks, Bryan Sullivan | Service Standards | AT&T From: Tim Hinrichs [mailto:thinri...@vmware.com] Sent: Wednesday, February 11, 2015 10:22

Re: [openstack-dev] [Congress][Delegation] Google doc for working notes

The Congress side would take care of translating Datalog to that LP problem. Right? Tim Thanks, Yathi. On 2/12/15, 10:02 AM, "Tim Hinrichs" mailto:thinri...@vmware.com>> wrote: Hi Debo and Yathiraj, I took a third look at the solver-scheduler docs and code with your comment

Re: [openstack-dev] [congress][Policy][Copper]Collaboration between OpenStack Congress and OPNFV Copper

of F2F LFC summit.We could have the crash course early next week (Monday or Tuesday), and then Bryan could discuss with Sean in detail when they met, with specific questions. Would this be ok for everyone ? On Fri, Feb 13, 2015 at 7:21 AM, Tim Hinrichs mailto:thinri...@vmware.com>>

Re: [openstack-dev] [congress][Policy][Copper]Collaboration between OpenStack Congress and OPNFV Copper

On Feb 14, 2015 8:04 AM, "Tim Hinrichs" mailto:thinri...@vmware.com>> wrote: Hi Zhipeng, Sure we can talk online Mon/Tue. If you come up with some times the Copper team is available, I’ll do the same for a few of the Congress team. We’re usually available 9-4p Pacific, and fo

Re: [openstack-dev] [congress][Policy][Copper]Collaboration between OpenStack Congress and OPNFV Copper

ok with the time slot. And yes you don't need an account :) On Mon, Feb 16, 2015 at 1:36 PM, Tim Hinrichs mailto:thinri...@vmware.com>> wrote: I just realized Monday is a holiday. What about 8a, 10a, 2-4p Tuesday? I'm happy to try out gotomeeting. Looks like I don't need

Re: [openstack-dev] [Congress][Delegation] Google doc for working notes

y? Ruby De : Tim Hinrichs [mailto:thinri...@vmware.com] Envoyé : jeudi 12 février 2015 19:03 À : OpenStack Development Mailing List (not for usage questions) Objet : Re: [openstack-dev] [Congress][Delegation] Google doc for working notes Hi Debo and Yathiraj, I took a third look at the solver-sc

Re: [openstack-dev] [Congress][Delegation] Initial workflow design

talog to LP substantially. Tim Ruby De : Yathiraj Udupi (yudupi) [mailto:yud...@cisco.com] Envoyé : mardi 24 février 2015 20:01 À : OpenStack Development Mailing List (not for usage questions); Tim Hinrichs Cc : Debo Dutta (dedutta) Objet : Re: [openstack-dev] [Congress][Delegation] Initial workflo

Re: [openstack-dev] [Congress]How to add tempest tests for testing murano driver

Hi Hong, Aaron started working on this, but we don’t have anything in place yet, as far as I know. He’s a starting point. https://review.openstack.org/#/c/157166/ Tim On Feb 26, 2015, at 2:56 PM, Wong, Hong mailto:hong.w...@hp.com>> wrote: Hi Aaron, I am new to congress and trying to write

Re: [openstack-dev] [Congress][Delegation] Initial workflow design

e whether the benefit of migrating to the new solution is worth the cost. And of course there’s a difference between the PoC and the long-term solution. I don’t know what the right answer is for the PoC. Suggestions? Tim Ruby De : Tim Hinrichs [mailto:thinri...@vmware.com] Envoyé : jeud

Re: [openstack-dev] [Congress][Delegation] Initial workflow design

hanging a subscription from an entire table to an arbitrary slice of a table (expressed via Datalog). That functionality will be necessary for dealing with large datasources like Ceilometer. But we don’t have the design fleshed out or the people to build it. Tim Thanks, Ramki From: Tim Hinrich

Re: [openstack-dev] [Congress][Delegation] Initial workflow design

ent is in great shape! Any global policies such as those impacting compute and network (e.g. CPU utilization and network bandwidth utilization) would be handled in Congress and not delegated. It would be worthwhile to capture this. Thanks, Ramki From: Tim Hinrichs [mailto:thinri...@vmware.com

[openstack-dev] [Congress] [Delegation] Meeting scheduling

Hi all, The feedback on the POC delegation proposal has been mostly positive. Several people have asked for a meeting to discuss further. Given time zone constraints, it will likely be 8a or 9a Pacific. Let me know in the next 2 days if you want to participate, and we will try to find a day

Re: [openstack-dev] [keystone][congress][group-policy] Fetching policy from a remote source

Hi Adam, For the most part we've been looking at Congress policy as complementary to Oslo policy, so we haven’t yet tried to incorporate Oslo policy into Congress (though I did some experiments with that a while back). But looking forward, it would definitely be convenient if there were some

Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling

ata(id, {"free_memory_limit": 0.25, }) This policy could be set and delegated by Congress to solver scheduler via the "set_policy" API. or the Solver Scheduler can query Congress via a "get_policy" API to get this policy, and incorporate it as part of the solver

Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling

legated by Congress to solver scheduler via the "set_policy" API. or the Solver Scheduler can query Congress via a "get_policy" API to get this policy, and incorporate it as part of the solver scheduler workflow ? Does this sound doable ? Thanks, Yathi. On 3/16/15, 11:05 AM, "

Re: [openstack-dev] [Congress] [Delegation] Meeting scheduling

Solver Scheduler can query Congress via a "get_policy" API to get this policy, and incorporate it as part of the solver scheduler workflow ? Does this sound doable ? Thanks, Yathi. On 3/16/15, 11:05 AM, "Tim Hinrichs" mailto:thinri...@vmware.com>> wrote: Hi all, The f

Re: [openstack-dev] [Congress] Info on Currently Supported Data Drivers

Hi Bryan, Inline. On Mar 24, 2015, at 12:13 PM, Bryan Sullivan mailto:bls...@hotmail.com>> wrote: Hi, I have a question about where to find the complete set of currently supported data drivers (with table/row details) for Congress. The info at http://congress.readthedocs.org/en/latest/cloudse

Re: [openstack-dev] [Congress] Info on Currently Supported Data Drivers

Hi Bryan, I wish we could claim Congress has most of the data from OpenStack APIs already available for policy, but that’s not the case today. If it were me, I’d start with your use cases, figure out which services and API calls you’ll need to support those use cases, and then check if those AP

Re: [openstack-dev] [Congress] Info on Currently Supported Data Drivers

tion': 'None'}, | | | {'name': 'size', 'description': 'None'}, | | | {'name': 'id', 'description': 'None'}, | | | {'name': 'name', 'descr

Re: [openstack-dev] [Congress] Info on Currently Supported Data Drivers

ist Please let us know if you are running into any issue. Thanks Pierre On Tue, Mar 24, 2015 at 8:39 PM Tim Hinrichs mailto:thinri...@vmware.com>> wrote: Hi Zhenzan, I don't have the CLI in front of me, but check out the 'driver' commands. The command you're

[openstack-dev] [Congress] PTL candidacy

Hi all, I'm writing to announce my candidacy for PTL of Congress for the Liberty cycle. We've made a lot of progress in Kilo, and I'm excited by what we'll achieve in Liberty! To give us some perspective, I compiled a (partial) list of improvements we made in Kilo: * Officially became part o

[openstack-dev] [Congress] [Delegation] Progress on PoC

Hi all, I've been making steady progress on the pieces of the delegation PoC that I volunteered for. Here's the usual design doc for reference. https://docs.google.com/document/d/1ksDilJYXV-5AXWON8PLMedDKr9NpS8VbT0jIy_MIEtI/edit# My main tasks were to spearhead the creation of a skeleton for t

[openstack-dev] [Congress] Cores

Hi all, I'm nominating Alex Yip for core status in Congress. He's active on IRC and gerrit, fixes important bugs routinely, and developed a number of key features for the project: - added a DSL that makes writing datasource-drivers much easier - improved scale-up performance by orders of magnit

Re: [openstack-dev] [keystone] On dynamic policy, role hierarchies/groups/sets etc.

Hi all, Inline. From: Adam Young mailto:ayo...@redhat.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, May 5, 2015 at 8:34 PM To: "openstack-dev@lists.openstack.org"

Re: [openstack-dev] [keystone] On dynamic policy, role hierarchies/groups/sets etc. - Role Assignment

Hi David, See below. On 5/7/15, 1:01 AM, "David Chadwick" wrote: >Hi Tim > >On 06/05/2015 21:53, Tim Hinrichs wrote: >> I wondered if we could properly protect the API call for adding a new >> Role using the current mechanism. So I came up with a simple exa

[openstack-dev] [Congress] summit events

For those of you interested in the Congress events at the summit, here's a list. That list is also available at: https://libertydesignsummit.sched.org/?s=congress 1. Talks (On delegation) Helping Telcos go Green and save OpEx via Policy Wed, May 20 2:40-3:20, Room 110 https://libertydesignsumm

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). Ti

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 s

[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. https://docs.openstack.org/python-n

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, J

[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 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 > list (devstack) (https://bug

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

e 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

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

>> > 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: > >> >>

[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. https://bugs.launchpad.

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

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 exce

[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 so

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 config for Ocata. > At the

Re: [openstack-dev] [Congress] Magnum_driver

view. > It seems everything works. > > Ruben > > - Original Message - > From: "Tim Hinrichs" > To: "Ruben" > Cc: openstack-dev@lists.openstack.org, "timothy l hinrichs" < > timothy.l.hinri...@gmail.com> > Sent: Saturday, Novembe

Re: [openstack-dev] [Congress] Magnum_driver

; > git add > git commit > git review > > Isn't it correct? > > Ruben > > - Messaggio originale - > Da: "Tim Hinrichs" > A: "Ruben" > Cc: openstack-dev@lists.openstack.org, "timothy l hinrichs" < > timothy.l.hinri...@gmail.c

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 OpenStack is in. I know which Cong

Re: [openstack-dev] [Congress] Magnum_driver

;t know if I have been able.. > > Ruben > > ----- Messaggio originale - > Da: "Tim Hinrichs" > A: "Ruben" > Cc: openstack-dev@lists.openstack.org, "timothy l hinrichs" < > timothy.l.hinri...@gmail.com> > Inviato: Mercoledì, 30 no

Re: [openstack-dev] [Congress] Magnum_driver

r "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" > A: "Ruben" > Cc: openstack-dev@lists.opens

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] 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 getting ready to request rele

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 > > remembered that the

[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 Ethiop

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 9:55 AM, Doug Hellmann wr

[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

[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 di

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', 'selec

<    1   2   3   >