[openstack-dev] [Charm][Congress] Upstreaming JuJu Charm for Openstack Congress

[SULLIVAN, BRYAN L]

Hi,

I've been working in the OPNFV (https://wiki.opnfv.org/) on a JuJu Charm to 
install the OpenStack Congress service on the OPNFV reference platform. This 
charm should be useful for anyone that wants to install Congress for use with 
an OpenStack deployment, using the JuJu tool. I want to get the charm 
upstreamed as an official openstack.org git repo similar to the other repos for 
JuJu Charms for OpenStack services. I participate in the Congress team in 
OpenStack, who don't know the process for getting this charm upstreamed into an 
OpenStack repo, so I am reaching out to anyone on this list for help.

I have been working with gnuoy on #juju and narindergupta on #opnfv-joid on 
this. The charm has been tested and used to successfully install Congress on 
the OPNFV Colorado release (Mitaka-based, re OpenStack). While there are some 
features we need to continue to work on (e.g. Horizon integration), the charm 
is largely complete and stable. We are currently integrating it into the OPNFV 
CI/CD system through which it will be regularly/automatically tested in any 
OPNFV JuJu-based deployment (with this charm, Congress will become a default 
service deployed in OPNFV thru JuJu).

Any pointers on how to get started toward creating an OpenStack git repo for 
this are appreciated.

Thanks,
Bryan Sullivan | AT


__
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-dev] [Congress] Progress on Congress support in OPNFV Colorado

[SULLIVAN, BRYAN L]

Hi Congress team,

A quick update on progress at OPNFV on integrating Congress into the OPNFV 
Colorado release (Mitaka-based). With the help of RedHat (Dan Radez) and 
Canonical (Narinder Gupta, Liam Young) we are getting very close to upstreaming 
two key things to OpenStack:

-  Congress Puppet module

o   https://github.com/radez/puppet-congress has been tested successfully for 
the OPNFV Colorado release on Centos 7 hosts.

o   This will be used in the base OPNFV deploy for the Apex project (RDO-based 
installer).

o   Dan is in the process of creating the official Puppet repo at 
https://github.com/openstack/puppet-congress

-  Congress JuJu Charm

o   https://github.com/gnuoy/charm-congress has been tested successfully for 
the OPNFV Colorado release on Ubuntu Trusty and Xenial hosts.

o   This will be used in the base OPNFV deploy for the JOID project 
(MAAS/JuJu-based installer).

o   Canonical has asked me to initiate the creation of the 
https://github.com/openstack/charm-congress repo to host this. I'd appreciate 
any help/pointers as to how to get that started.

This module and charm will help other OPNFV projects (e.g. Doctor) as Congress 
will be installed by default on the OPNFV platform, with the necessary 
datasource drivers and configuration ready to go.

I have three policy test cases that are working reliably for Mitaka (see 
https://git.opnfv.org/cgit/copper/tree/tests), soon to be integrated into the 
OPNFV CI/CD program, and will demo them at the upcoming OPNFV Summit in Berlin 
next week. I'll be adding other tests and developing a tested policy library 
once I get over the hurdles of completing the installer support (including for 
FUEL and Compass, the other two OPNFV installer projects).

Feels like it's been a long road, but also that we are nearing a major 
milestone!

Thanks,
Bryan Sullivan | AT

__
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-dev] [congress] Spec for congress.conf

[SULLIVAN, BRYAN L]

Hi Congress team,

Quick question for anyone. Is there a spec for fields in congress.conf file? As 
of Liberty this has to be tox-generated but I need to know which conf values 
are required vs optional. The generated sample output doesn't clarify that. 
This is for the Puppet Module and JuJu Charm I am developing with the help of 
RedHat and Canonical in OPNFV. I should have Congress installed by default (for 
the RDO and JuJu installers) in the OPNFV Colorado release in the next couple 
of weeks, and the congress.conf file settings are an open question. The Puppet 
module will also be used to create a Fuel plugin for installation.

Thanks,
Bryan Sullivan | AT

__
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] [Openstack-operators] OpenStack Contributor Awards

[SULLIVAN, BRYAN L]

(maybe further off-topic)

Re use of NUCs for OpenStack, I have been doing this as a cheap lab environment 
for a few months, using the OPNFV Brahmaputra release (OS Liberty and ODL 
Lithium/Beryllium). It works great, and has really helped me come on board with 
OpenStack (as compared to DevStack) without having to build an expensive 
server/switch environment.

The setup is described at https://wiki.opnfv.org/copper/academy.

Thanks,
Bryan Sullivan | AT

From: Silence Dogood [mailto:m...@nycresistor.com]
Sent: Tuesday, March 01, 2016 2:33 PM
To: Tim Bell 
Cc: OpenStack Development Mailing List (not for usage questions) 
; OpenStack Operators 

Subject: Re: [Openstack-operators] [openstack-dev] OpenStack Contributor Awards

I believe Eric Windisch did at one point run OpenStack on a pi.

The problem is that it's got so little ram, and no hypervisor.  Also at least 
it USED to not be able to run docker since docker wasn't crosscompiled to arm 
at the time.

It's a terrible target for openstack.  NUCs on the other hand...

=/

-Matt

On Tue, Mar 1, 2016 at 3:04 PM, Tim Bell 
> wrote:

Just to check, does OpenStack run on a Raspberry Pi ? Could cause some negative 
comments if it was
not compatible/sized for a basic configuration.

Tim





On 01/03/16 20:41, "Thomas Goirand" > 
wrote:

>On 03/01/2016 11:30 PM, Tom Fifield wrote:
>> Excellent, excellent.
>>
>> What's the best place to buy Raspberry Pis these days?
>
>One of the 2 official sites:
>https://www.element14.com/community/community/raspberry-pi
>
>The Pi 3 is the super nice shiny new stuff, with 64 arm bits.
>
>Cheers,
>
>Thomas Goirand (zigo)
>
>
>Hopefully, with it, there will be no need of raspbian anymore (it was
>there because of a very poor choice of CPU in model 1 and 2, just below
>what the armhf builds required, forcing to use armel which is arm v4
>instruction sets).
>
>
>
>__
>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-operators mailing list
openstack-operat...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

__
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][Policy][Copper]Collaboration between OpenStack Congress and OPNFV Copper

[SULLIVAN, BRYAN L]

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/congresshttps://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 | ATT

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 managementhttps://wiki.opnfv.org/doctor, resource 
managementhttps://wiki.opnfv.org/promise, resource 
schedulerhttps://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 | ATT

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.commailto:zhipengh...@gmail.com wrote:

Hi Congress Team,

As you might already knew, we had a project in OPNFV covering deployment policy 
called 
Copperhttps://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_copperd=AwMFaQc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7sm=R1ER1wU47Knv6PaOiamDwCm76pwx5uuE47mpn_03mzYs=S7VfJALm_Pmzb2S-o3NUlcNzLAy9yYceGzcyKX3CA-we=,
 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.commailto:huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University

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

[SULLIVAN, BRYAN L]

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 managementhttps://wiki.opnfv.org/doctor, resource 
managementhttps://wiki.opnfv.org/promise, resource 
schedulerhttps://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 | ATT

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.commailto:zhipengh...@gmail.com wrote:

Hi Congress Team,

As you might already knew, we had a project in OPNFV covering deployment policy 
called 
Copperhttps://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.opnfv.org_copperd=AwMFaQc=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEsr=B6BWd4kFfgOzAREgThxkmTZKy7dDXE2-eBAmL0PBK7sm=R1ER1wU47Knv6PaOiamDwCm76pwx5uuE47mpn_03mzYs=S7VfJALm_Pmzb2S-o3NUlcNzLAy9yYceGzcyKX3CA-we=,
 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.commailto: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.edumailto: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.orgmailto: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