wunki / django-salted Goto Github PK

I wanted to try with Debian Wheezy, so I generated a Debian Wheezy Vagrant box using this:
http://stacktoheap.com/blog/2013/06/19/building-a-debian-wheezy-vagrant-box-using-veewee/

I only add to install 3 more packages into this box: python-pip, python-dev, uwsgi
I also needed to modify the /etc/apt/sources.list to add:
deb http://debian.saltstack.com/debian wheezy-saltstack main

After that I modified Vagrantfile to specify this box and to remove the salt.install_type = "daily" (which is specific to Ubuntu).

I ran "vagrant up" and everything was frozen during the "setting hostname". So I manually changed the hostname and everything went fine until the end.

However I cannot access the website (502 Bad Gateway).

Here is the error message by uwsgi:
Fri Jul 26 00:32:56 2013 - -- unavailable modifier requested: 0 --

And here is the error message by nginx:
2013/07/26 00:32:56 [error] 18072#0: *6 upstream prematurely closed connection while reading response header from upstream, client: 10.0.2.2, server: localhost, request: "GET / HTTP/1.1", upstream: "uwsgi://127.0.0.1:3000", host: "127.0.0.1:8080"

I don't know why it doesn't work ? I don't have any more clue.

Hey Guys,

I'm getting a pillar error, not very familiar with pillar but I am getting the error on a few different machines, all that worked with this repo up until recently.

The errors I get are :

[CRITICAL] Rendering SLS "base:example-project.venv" failed: Jinja variable 'dict object' has no attribute 'django'; line 5

[CRITICAL] Rendering SLS "base:example-project.postgresql" failed: Jinja variable 'dict object' has no attribute 'postgresql'; line 6

Obviously I can hardcode the pillar variables to prevent this but otherwise not sure how to fix.

Thanks,
Lars

Would be cool to integrate with Vagrant AWS to give people a quick way to turn their vagrant box into a live server.

I'm open to alternative solutions to use this project to help people quickly get a live server online, obviously Vagrant AWS isn't the only solution.

I understand this may be more MY issue than an issue with django-salted.

I recently set up a new ubuntu 12.04 server and am attempting to make better use of the space for development.

sudo vagrant up
You appear to be running Vagrant outside of the official installers.
Note that the installers are what ensure that Vagrant has all required
dependencies, and Vagrant assumes that these dependencies exist. By
running outside of the installer environment, Vagrant may not function
properly. To remove this warning, install Vagrant using one of the
official packages from vagrantup.com.
Bringing machine 'web' up with 'virtualbox' provider...
[web] Clearing any previously set forwarded ports...
[web] Creating shared folders metadata...
[web] Clearing any previously set network interfaces...
[web] Preparing network interfaces based on configuration...
[web] Forwarding ports...
[web] -- 22 => 2222 (adapter 1)
[web] -- 80 => 8080 (adapter 1)
[web] Running 'pre-boot' VM customizations...
[web] Booting VM...
[web] Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run vagrant up while the
VirtualBox GUI is open.

my research into the issue has primarily lead to "downgrade virtualbox" and I have, to 4.1.26, while before i was using 4.2.18 and getting the same results. I'm wondering if my issues are merely server set up, or incompatibilities with vagrant, virtualbox, and django-salted settings?

Hello, I've been following the steps in the README, the vagrant pox has installed and provisioned but when I go to http://127.0.0.1:8080/admin/ I get the error:

Exception Type: TemplateDoesNotExist
Exception Value:    
admin/login.html
Exception Location: /home/vagrant/env/local/lib/python2.7/site-packages/django/template/loader.py in find_template, line 139
Python Executable:  /usr/local/bin/uwsgi

Will try and workout what's going wrong and report back. I set-up demo_project outside of vagrant (on OS X) and it worked fine.

I installed the versions above, cloned the repo, and ran vagrant up. I got the "501 Bad Gateway", even after waiting a bit. The log from the install showed the contents:

----------
    State: - virtualenv
    Name:      /home/vagrant/env
    Function:  managed
        Result:    False
        Comment:   An exception occurred in this state: Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/salt/state.py", line 1243, in call
    ret = self.states[cdata['full']](*cdata['args'])
  File "/usr/lib/pymodules/python2.7/salt/states/virtualenv_mod.py", line 126, in managed
    runas=runas
  File "/usr/lib/pymodules/python2.7/salt/modules/virtualenv_mod.py", line 126, in create
    virtualenv.__version__.split('rc')[0].split('.')]
AttributeError: 'module' object has no attribute '__version__'

        Changes:   
----------

you get the same error if you "vagrant ssh" and then run "sudo salt-call state.highstate"

/home/vagrant does not contain a /env/ directory for venv which causes uwsgi to keep trying to start and fail.

once logged into the VM, I created the venv by hand and ran the pip commands on it and uwsgi seemed to be happy but still wasn't getting the expected results (but I think we need to worry about one step at a time)

After run the next command fab vagrant syncdb I receive the following message:

The program fab is currently not installed.  You can install it by typing:
sudo apt-get install fabric

Should be fab installed after run the command vagrant up?

I have looked in all files I can think of. Studying to log trace of the entire installation. But I don't see it anywhere.

When I try to run this commando fab vagrant collectstatic I get the following error

vagrant@vagrant:/vagrant$ fab vagrant collectstatic -f fabfile.py
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/fabric/main.py", line 594, in main
    docstring, callables, default = load_fabfile(fabfile)
  File "/usr/lib/python2.7/dist-packages/fabric/main.py", line 156, in load_fabfile
    imported = importer(os.path.splitext(fabfile)[0])
  File "/vagrant/fabfile.py", line 3, in <module>
    from fabtools.vagrant import vagrant

Should be fabtools installed after run the command vagrant up?

When I do "vagrant up" it fails with:

[INFO ] Package bash is already installed
[ERROR ] This master address: 'salt' was previously resolvable but now fails to resolve! The previously resolved ip addr will continue to be used
Minion failed to authenticate with the master, has the minion key been accepted?
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

salt-call state.highstate -l debug

Hello,

The project is a bit dead, but I was hoping someone could help me out. I'm trying to run the salt configuration on my Ubuntu server, skipping Vagrant. Is it possible to do that locally? I read the bit about getting the latest version in the FAQ, but I can't just run that command on the server, probably because the vagrant configuration is missing.

Hello,
When executing command "vagrant up", I can see several errors.

Command: "/home/vagrant/env/bin/pip install --use-wheel --no-index --find-links=/home/vagrant/wheel/example -r /vagrant/demo_project/requirements.txt"

Result:
Ignoring indexes: https://pypi.python.org/simple/
setuptools==0.8dev,>=0.8b2 is required for wheel installs.
pip's wheel support requires setuptools==0.8dev,>=0.8b2.

How can I get setuptools version 0.8b2 ?

Thanks!