Hi Tim, See one issue I had when installing congress, below. I'm not sure where to report this as it seems just a bug in the readme.rst at https://github.com/stackforge/congress<https://github.com/stackforge/congress%20and%20in%20the%20prepare_devstack.sh> and in the prepare_devstack.sh script.
The readme references creating a localrc and adding the line below to it: ENABLED_SERVICES=congress,g-api,g-reg,key,n-api,n-crt,n-obj,n-cpu,n-sch,n-cauth,horizon,mysql,rabbit,sysstat,cinder,c-api,c-vol,c-sch,n-cond,quantum,q-svc,q-agt,q-dhcp,q-l3,q-meta,n-novnc,n-xvnc,q-lbaas,ceilometer-acompute,ceilometer-acentral,ceilometer-anotification,ceilometer-collector,ceilometer-alarm-evaluator,ceilometer-alarm-notifier,ceilometer-api,s-proxy,s-object,s-container,s-account But localrc has been deprecated for local.conf AFAICT, and stack.sh failed with errors (urllib3:... connection pool is full, discarding connection...) until I: - Moved "enable_service congress" into the [local|localrc] section of local.conf - Did not include the "ENABLED_SERVICES" line above (it seems to be redundant, not necessary if you are only enabling the default services, and I think caused the errors in stack.sh) I think prepare_devstack.sh needs to be updated to put "enable_service congress" into the [local|localrc] section of local.conf rather than creating localrc (at least when there is a local.conf in the devstack directory). Thanks, Bryan Sullivan | Service Standards | AT&T From: SULLIVAN, BRYAN L Sent: Wednesday, February 11, 2015 9:04 PM To: 'Tim Hinrichs'; 'OpenStack Development Mailing List (not for usage questions)' Cc: HU, BIN; 'Rodriguez, Iben'; 'Howard Huang' Subject: RE: [openstack-dev] [congress][Policy][Copper]Collaboration between OpenStack Congress and OPNFV Copper Hi Tim, It would be great to meet with members of the Congress project if possible at our meetup in Santa Rosa. I plan by then to have a basic understanding of Congress and some test driver apps / use cases to demo at the meetup. The goal is to assess the current state of Congress support for the use cases on the OPNFV wiki: https://wiki.opnfv.org/copper/use_cases I would be doing the same with ODL but I'm not as far on getting ready with it. So the opportunity to discuss the use cases under Copper and the other policy-related projects (fault management<https://wiki.opnfv.org/doctor>, resource management<https://wiki.opnfv.org/promise>, resource scheduler<https://wiki.opnfv.org/requirements_projects/resource_scheduler>) with Congress experts would be great. Once we understand the gaps in what we are trying to build in OPNFV, the goal for our first OPNFV release is to create blueprints for new work in Congress. We might 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 AM To: OpenStack Development Mailing List (not for usage questions) Cc: SULLIVAN, BRYAN L; HU, BIN; Rodriguez, Iben; Howard Huang Subject: 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 and around Palo Alto. And of course, phone/google hangout/irc are fine options as well. Tim On Feb 11, 2015, at 8:59 AM, Zhipeng Huang <zhipengh...@gmail.com<mailto:zhipengh...@gmail.com>> wrote: Hi Congress Team, As you might already knew, we had a project in OPNFV covering deployment policy called Copper<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_copper&d=AwMFaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7s&m=R1ER1wU47Knv6PaOiamDwCm76pwx5uuE47mpn_03mzY&s=S7VfJALm_Pmzb2S-o3NUlcNzLAy9yYceGzcyKX3CA-w&e=>, in which we identify Congress as one of the upstream projects that we need to put our requirement to. Our team has been working on setting up a simple openstack environment with congress integrated that could demo simple use cases for policy deployment. Would it possible for you guys and our team to find a time do an Copper/Congress interlock meeting, during which Congress Team could introduce how to best integrate congress with "vanilla" openstack? Will some of you attend LF Collaboration Summit? Thanks a lot :) -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Prooduct Line Huawei Technologies Co,. Ltd Email: huangzhip...@huawei.com<mailto:huangzhip...@huawei.com> Office: Huawei Industrial Base, Longgang, Shenzhen (Previous) Research Assistant Mobile Ad-Hoc Network Lab, Calit2 University of California, Irvine Email: zhipe...@uci.edu<mailto:zhipe...@uci.edu> Office: Calit2 Building Room 2402 OpenStack, OpenDaylight, OpenCompute affcienado __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org<mailto: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