Open Stack

On Thu, Jul 11, 2013 at 7:11 PM, James E. Blair <jeblair at openstack.org> wrote:
> Paul Belanger <paul.belanger at polybeacon.com> writes:
>
>> On Thu, Jul 11, 2013 at 9:28 AM, Russell Bryant <rbryant at redhat.com> wrote:
>>> On 07/10/2013 10:29 PM, James E. Blair wrote:
>>>> We're about to roll out our first production CentOS server, so I think
>>>> at this point we've crossed that bridge so we may as well slide down the
>>>> slope.  I'm sorry I couldn't mix any more metaphors in that sentence.
>>>>
>>>> At any rate, yeah, we can handle CentOS6 now, and it sounds like from
>>>> what the two of you have written, it's probably the best bet for
>>>> Asterisk 11.
>>>
>>> Ok, sounds good.
>>>
>>>> Paul, would you be interested in porting your modules to Asterisk 11 on
>>>> CentOS?
>>>
>>> I'd like to help here.  I want to learn more puppet anyway.
>>>
>>> What kind of timeline are we shooting for here?  If we want something
>>> running sooner, could we start with a hacky approach for the Asterisk
>>> configs (get puppet to place a set of files in /etc/asterisk as-is), and
>>> then migrate to a nicer setup over time?
>>>
>> Ya, I don't mind porting them to CentOS, just need the time to do it.
>> Like Russell said, what is the timelines on this?
>>
>> I should have linked it sooner, but I actually game a demo at the last
>> astricon[1] on how they worked.  This is the code used for it.
>>
>> There is one concern about using the modules created, they depend on
>> some specific packaging configuration.  Worst case, we need to create
>> a asterisk-config package with them and use it vs the  CentOS repo.
>>
>> [1] https://github.com/kickstandproject/astricon-2012-presentation
>
> Maybe we should go with Russel's suggestion of the hacky approach
> (require asterisk, copy a bunch of configs in place) and get something
> up that we can start playing with (get hooked up with voip providers, do
> some small scale testing, and let me try out my webrtc idea), and then
> move to your nicer modules as they're ready?
>
> I think the sooner we can have something for Stef to start getting user
> groups using the better (a couple weeks?), and hopefully we can have a
> reasonably reliable system for the summit.
>
If that is the case, we can get an asterisk server up within 1/2 a
day. I don't have a problem getting it provisioned.  I can at least
get the base configuration setup, which makes our migration to puppet
easier.

We'd also need to discussion how credentials are going to be stored,
since we don't want them public.  EG: a public and private git repo
for specific configuration... or just a fully private repo.

--
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger at polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger