Since I'm very close to actually making the box work as desired I want to
ask something about the setup scripts for nta.utils and htmengine. They do
not play nice with my provision script. I can see that they are executed
just fine during 'vagrant up', but when I ssh into the box, pip list is
missing all the NuPIC packages.
I am now forced to run these scripts manually after provisioning.
Apparently I then need sudo rights to install both nta.utils and htmengine,
I suspect that might affect the installation (for example: running
supervisord also requires sudo).
Right now I have tried these commands in my provision script to install
nta.utils and htmengine(with the results described above):
cd /home/vagrant/resources/numenta-apps/nta.utils && python setup.py
develop --user
cd /home/vagrant/resources/numenta-apps/htmengine && python setup.py
develop --user
I have tried this both with and without subshells (surrounding the command
with brackets), both apparently with the same results.
So can anyone tell me what is happening when these commands run, but don't
result in installation of packages?
Met vriendelijke groet,
Casper Rooker
[email protected]
On Tue, Nov 10, 2015 at 3:41 PM, Richard Crowder <[email protected]> wrote:
> Thanks for the update Casper. On Windows the mysql installer forces you to
> enter a password for root, that is something that should change in the
> nupic-default.xml file (with currently existing override support via the
> nupic-site.xml). Probably use something simple like 'nupic' for it.
>
> On Tue, Nov 10, 2015 at 2:13 PM, Cas <[email protected]> wrote:
>
>> Just thought I'd give an update. Just now I got the node client working.
>>
>> Some of the problems I encountered that I tried to mitigate:
>>
>>
>> - Model scheduler could not launch. Turns out HTM Engine wants to
>> access rabbitmq_management, so I enabled it with 'rabbitmq-plugins enable
>> rabbitmq_management'. I could not find any documentation about this, did I
>> search in the wrong place?
>> - You HAVE to give a password to mysql-5.6. I thought leaving the
>> password field empty would be ok, but it isn't.
>> - Forward the ports from the webapp and the node client to the same
>> ones on your host.
>> - Getting the requirements for the repositories costs takes a LONG
>> time. Running the setup scripts in the provision script kept giving me
>> trouble, so my solution was to pip install most requirements there. After
>> provisioning I logged in and ran the setup scripts manually. It still took
>> a long time for nupic and capnproto, though.
>> - Using a synced folder is better than trying to git clone during
>> provision...
>>
>> This does mean that I couldn't provision all the requirements. I'll find
>> a middle way to work with this, though. It's better than nothing!
>>
>>
>> Met vriendelijke groet,
>>
>> Casper Rooker
>> [email protected]
>>
>> On Mon, Nov 9, 2015 at 5:44 PM, Cas <[email protected]> wrote:
>>
>>> Hi NuPIC,
>>>
>>> I hope someone can help me clean my vagrantfile up!
>>>
>>> Included is a vagrantfile and a provision script for an ubuntu vagrant
>>> box I am trying to build up. I intend to use vagrant to run htm models
>>> without depending on my host machine. My first choice is HTM Engine. I've
>>> spent hours trying to set up this machine but I keep running into problems.
>>> Some of the persistent ones:
>>>
>>>
>>> - mysql-5.6 will not install properly, causing problems later on in
>>> the provision.
>>> - installing with setup.py takes a long time, has lots of warnings
>>> and doesn't seem to register the python package.
>>> - launching supervisord needs sudo rights, I don't know why.
>>> - provisioning after vagrant halt makes a lot of redundant commands
>>> happen.
>>>
>>> provisioning with a shell script might not be ideal or pretty, but it
>>> gives me faster results compared to first learning chef/puppet/ansible.
>>>
>>> To try out the vagrantfile, put it in a folder together with the
>>> setup.sh script. Obviously you'll need Virtualbox and Vagrant installed.
>>>
>>> With regards,
>>>
>>> Casper Rooker
>>> [email protected]
>>>
>>
>>
>
