Kazoo Bootcamp feedback

[Kirill Sysoev]

Hi All!

It is already a week since First Kazoo Bootcamp (17 - 19 October)

It was EXTREMLY usefull and interesting.

Many things seemed confusing now taken for granted.

Looking at it retrospectively it is very clear that if anybody wants to be familiar with kazoo, visiting this Bootcamp is a MUST.

I personally got an announcement about this training a couple days before it. Was not very easy to replan my schedule. So keep an eye on voipkb.com. The next one is planned approximately for January.

I am attaching a photo to show the great atmosphere during the training. 

Regards,

Kirill

[Darren Schreiber]

Thanks a ton for the picture and great feedback Kirill. We enjoyed having you there, too. I can't believe you flew all the way from Russia on 2 days notice :-)

Now that you understand all the internals of the system, I would appreciate feedback on how we can deliver the message to the open-source community better. The system is clearly complex and people aren't used to having as much control as we give them and this is leading to people believing that the system is intentionally complex or making other assumptions that it's too hard to use.

When in fact, as you've discovered, it's pretty easy :-)

One thing I am thinking of is moving all the passwords and configs into a single file in /etc/kazoo.ini . Here's a sample:

/etc/kazoo.ini

[bigcouch]

cookie = j029jd9032d

host = localhost

port = 5984

admin_port = 5986

[rabbitmq]

cookie = 823j092dj2

host = some.server.com

port = 5672

[whapps]

default_apps = cdrs, hangups, etc.

…

Then having a script, like "configure.sh" that reads the /etc/kazoo.ini file and updates anything that can't be retrieved automatically. For example I'm not sure we can get rid of vm.args because of how Erlang is setup. But maybe I am wrong.

Note that the above is just a sample, I'm tossing ideas around, I'm not sure what I've even written is possible ^. Hence why I'm seeking ideas for simplifying the install and clustering process.

Thoughts and suggestions welcome.

--

Darren Schreiber

CEO / Co-Founder

 visit: www.2600hz.com

 sip:dar...@2600hz.com

 tel: 415-886-7901

[Alejandro Recarey Llerena]

Hi Kirill,

Thanks for the info. Just wanted to say that I also found out a few days before the event and it was too late for me to reschedule. It would be awesome to have an email a couple of weeks before, I am really interested in going to a 2600hz boot camp.

Thanks guys!

> <2600hzbootcamp2.jpg>

[Kirill Sysoev]

Hi Darren!

On my way to Cluecon 2012, during the long flight, I was watching screencast "Erlang for Rubyists" and saw very remarkable slide: 

" - Ruby makes easy things trivial and hard things fun!

  - Erlang makes easy things possible and impossible things trivial! "

So the question is what are you trying to achieve with Kazoo ? :)

One of your blog posts says: 

'At 2600hz we like to say that we’ve “re-written the telephony stack.”'

Let's make an analogy to LAMP stack. It is widely used now and nobody tries to make life easier than it is in reality.

If you want to use this stack, you just need to know how its components should be configured. 

Usually there is only one advice: go and read DOCUMENTATION (wiki or whatever) just because there is already a lot of info published about LAMP components ... or just pay for support.

So, my personal opinion, the key word at the moment is documentation. 

Documentation about the features existing in Kazoo - different flags explanations, structures of db docs, tonns of examples of API utilization will also make life easier, and so on.

Documentation regarding used components could be retrieved directly from component's projects.

Besides that, if we'll look at 2600hz-dev list, we'll see that during last several months questions getting mature like exponential growth wich shows that critical mass could be achieved very soon. 

Kazoo consists of new generation components and learning how to configure this components will open the mind of community and at the end of the day it will be appreciated for sure :) 

So please save your efforts for building new "impossible but trivial" and well documented features. :)

Sorry if I said something wrong. It is my personal opinion, a kind of view from outside.

Best regards,

Kirill

суббота, 27 октября 2012 г., 22:59:43 UTC+4 пользователь Darren Schreiber написал: