Quick update on Whistle deploy tool

[Darren Schreiber]

Some folks complained, over the past few days, that deployments weren't working.

Seems you were correct! I was wrong.

The elff repository for which we relied upon for updated packages seems to have gone away. When that firm took down their servers, the install failed to complete. Turns out we don't NEED elff we just wanted to give you the latest & greatest RPMs in all cases.

So, this requirement has been removed. If your deployment failed, please just click the "Done" button in the cluster manager and it will auto-attempt to re-deploy / upgrade / update your install.

--

Darren Schreiber

CEO / Co-Founder

 visit: www.2600hz.com

 sip:dar...@2600hz.com

 tel: 415-886-7901

[Arkadiusz Fryz]

Hi,

My deployment status says Idle, not Done. Does it mean it was not done correctly? Everything were installed correctly except many issues I had with whistle.

Like, had to manually flush db every time I changed callflow or removed/added voicemail; had to manually start services after server reboot, had  to make sure they are started in correct order otherwise it did not register devices...

Finally I was not able setup outgoing trunk at all even pyite said configuration looks OK....

Do you think all that issues are corrected now? Last time I hit "Idle" button yesterday afternoon but it did not help nor fix my issues.

Regards,

Arek

----
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.

[Darren Schreiber]

Sorry, I meant Idle :-)

Other answers inline below.

From: Arkadiusz Fryz <af...@remacservices.net>
Reply-To: <2600hz...@googlegroups.com>
Date: Fri, 9 Sep 2011 11:21:43 -0500
To: <2600hz...@googlegroups.com>
Subject: Re: Quick update on Whistle deploy tool

Hi,

My deployment status says Idle, not Done. Does it mean it was not done correctly? Everything were installed correctly except many issues I had with whistle.

Like,

* had to manually flush db every time I changed callflow or removed/added voicemail

> This is a design decision that I agree is a defect. The cache keeps the callflow in memory to avoid hitting the DB for numbers that are used a lot, but the cache should be flushed when a specific number is changed. We will be coding this up this week. It is not, in my eyes, an indication that the system is broken it's just an annoying design because if you change a callflow you expect it to work the new way immediately, but in fact it can take time if the number is in use as that resets the timer for the cache expiration. And of course the first thing people seem to do when playing with this is setting up a number and trying all the functions out.

* had to manually start services after server reboot

> My expectation is that you are starting services yourself after reboot. We have discussed this in the office a bunch and have mixed feelings on it. We have settled on the following, which we'll work on implementing next week:

>    We will start services automatically after 60 seconds on the bootup of a server. This is done to allow people who reboot during maintenance but DO NOT want the server to rejoin the cluster to have some time to go in and stop the auto-starting of services themselves. The details on how we will achieve this remain TBD but that is ultimately why your services do not auto-boot – we don't want a micro server to reboot and immediately start thrashing it's database or otherwise if that's the reason it crashed in the first place.

> had  to make sure they are started in correct order otherwise it did not register devices...

This is a bug only with RabbitMQ. RabbitMQ must be started before the other whistle apps. This is a serious bug actually which will be the focus of our attention immediately on Monday – what's really happening is whistle is trying to reconnect to AMQP any time it loses connectivity, but for some reason it's failing to ever actually do so. Check out your logs in /var/log/local0.log

Finally I was not able setup outgoing trunk at all even pyite said configuration looks OK....

> I have to look at your config again. This is in production so I am very sure it works. I'd need your FreeSWITCH CLI logs here.

Do you think all that issues are corrected now? Last time I hit "Idle" button yesterday afternoon but it did not help nor fix my issues.

> Most of the items you list above are design changes we'll be working on next week. Nothing is "broken" or unusable, though, so for the device not registering or making calls we do need to look into your config to see why it's not working.

[Arkadiusz Fryz]

Thank you for your answers!

I can confirm that deploy did the job now. I got all installed.

My next question is: how do I create first account?

I don't want to be connected to winkstart (or I have to??) 

I tried to follow "how to manually add account to clouchdb" but it gave me "database missing view" error.

I'm not able to do the other way because "I'm not admin" (this is from :5984/_utils/).

Wiki says "Your deployment of Whistle should have created an account for you and provided you with either user credentials or an API key." but I did not get that, and I don't see any account in  :5984/_utils

Regards,

Arek

----
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.

[Darren Schreiber]

Well what do you mean when you say "I don't want to be connected to winkstart"? You just want to use APIs?

--

Darren Schreiber

CEO / Co-Founder

 visit: www.2600hz.com

 sip:dar...@2600hz.com

 tel: 415-886-7901

[Arkadiusz Fryz]

Yes, since winkstart did not work for me for some unknown reason, I wanted to play with APIs to see if I will be able to get it to work.

Is it possible? I see many tutorials and examples in wiki but all require account id that I don't have and don't know how to get. 

Should I ask you to get my account id on my deployed whisle or I have to insert it manually to db ?

Or maybe there is not way to use whistel if it's not connected to winkstart?

Regards,

Arek

----
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.

[Darren Schreiber]

Well winkstart didn't work cause your backend wasn't working ;-)

We can re-wire winkstart to the backend and it should be fine and will create the initial account. AFTER that it's easy to use either one

Email me off-list with your username (NOT password) on http://apps.2600hz.com/ and the IP of your server.

[Arkadiusz Fryz]

Ok, email sent.

My backed was fixed - at least I was told everything is ok with my server. But I know we made a lot of manual changes to it in order to make it work..

Anyway... can't wait to get it finally working and move forward :)

Thank you for all your help!

Regards,

Arek

----
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.

[Alexander Shvaryov]

Hi all

I want to use Blue.Box multi-tenant functionality in my local network.
To separate domain, DNS server is required. I would like to use the
"PowerDNS Management" module but I didn't get connect "PowerDNS
Management" to PoverDNS which I installed. Please, tell me what
configuration settings are needed for PowerDNS?

--
Regards,
Alexander Shvaryov

[Alexander Shvaryov]

I apologize for the issue in this discussion ... created a new one.