Wok 2.5 and Kimchi 2.5 are now released!
by Aline Manera
On behalf of everyone who has worked hard on this release, I am pleased
to announce the availability of *Wok 2.5* and *Kimchi 2.5*!
Kimchi 2.5 depends on *Wok 2.5*! So make sure to have both of them properly
installed in your system.
Among many features,
Wok 2.5 release includes:
✔ Allow Wok server discover others on same subnet (Check: README-federation.md for more details)
✔ Remove OpenSans fonts need
✔ Bug fixes
Kimchi 2.5 release includes:
✔ Does not depend on Ginger Base anymore
✔ Remove OpenSans fonts need
✔ Move federation feature to Wok
✔ Bug fixes
We have worked hard to ensure that Wok and Kimchi run well on the most
popular Linux distributions including: Fedora 25, Ubuntu 17.04,
openSUSE LEAP 42.2, and CentOS 7. They use standard Linux interfaces so
it should run well on many other distributions too.
You can easily grab this release in tarball format or via git:
✔ https://github.com/kimchi-project/wok/archive/2.5.0.tar.gz
✔ https://github.com/kimchi-project/kimchi/archive/2.5.0.tar.gz
✔ git clone -b stable-2.5.x --recursive https://github.com/kimchi-project/wok.git
There are also some packages available for download at:
✔http://kimchi-project.github.io/wok/downloads/
✔http://kimchi-project.github.io/kimchi/downloads/
Go ahead! Give it a try and let us know what you think!
Although the Wok and Kimchi development have slowed down due the small number of active developers,
Kimchi and Wok are still alive! And I will do my best to keep them going.
Any help on any area is more than welcome. I count on you to make it better and better. ;-)
Regards,
Aline Manera
6 years, 11 months
Cleaning up the datastore erros
by WK
Our kimchi hosts have people constantly working on from the command line
including changing qcow2 image names (our practice is to name them
similar to the instance name so its easy to see whats up in
/var/lib/libvirt/images)
So after a while the wok error log is full of these messages.
and we often get reoccuring pink error message in the WebUI.
Is there a way to cleanout/fix/ignore the datastore
-bill
WOKOBJST0001E: Unable to find 5f48fb31-0d73-4df7-948c-02beefee83d1 in
datastore
WOKOBJST0001E: Unable to find c7d94dcb-185f-4917-9b2e-d304f5ce807b in
datastore
WOKOBJST0001E: Unable to find d7f82fc8-44dd-484f-aaf9-f4ed0de3efe3 in
datastore
WOKOBJST0001E: Unable to find f88269b8-8ca9-4689-b8aa-c7e720e3c396 in
datastore
WOKOBJST0001E: Unable to find b46491f9-4351-4b82-ad57-87568dd55f3e in
datastore
WOKOBJST0001E: Unable to find 7c34a9fd-b3b6-4894-a6f1-baf6b7099403 in
datastore
WOKOBJST0001E: Unable to find 0eb316fe-803c-4b25-9dae-522c02748e5c in
datastore
WOKOBJST0001E: Unable to find 4e5663b8-300d-4ad0-8959-ecdc489e8c71 in
datastore
WOKOBJST0001E: Unable to find 5f48fb31-0d73-4df7-948c-02beefee83d1 in
datastore
WOKOBJST0001E: Unable to find c7d94dcb-185f-4917-9b2e-d304f5ce807b in
datastore
7 years
Help : PAM authentication as user
by Prakash
Dear Users,
Please suggest pointers on where and what to change in wok config so the PAM authentication for my user goes through. Right now, it just comes back to the login page.
Below are the details :
Ubuntu 16.10 (GNU/Linux 4.8.0-46-generic x86_64)
User : db
Output in wok-error.log file
Run command: 'id -Gn db’
out: db adm cdrom sudo dip plugdev lxd libvirt lpadmin sambashare
Run command: 'sudo -l -U db sudo’
out: /usr/bin/sudo
Run command: 'sudo -l -U db’
out: Matching Defaults entries for db on sandbox3:
env_reset, mail_badpass, secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/sbin\:/usr/bin\:/sbin\:/bin\:/snap/bin
User db may run the following commands on sandbox3:
(ALL : ALL) ALL
(ALL : ALL) NOPASSWD: ALL
Thank you all. As my first time, please excuse me if my request for help is not the right approach.
Prakash
Below Image showing the version of Wok, Ginger, Ginger-Base & Kimchi
7 years
Wok Feedback
by Jason Jack
Kimchi Dev,
I didn't want to post an issue, because I solved it, but I think it'd be
useful to post a README update on how to update Wok to to listen on all
network devices so as to be accessed outside of localhost.
I was able to do so by updating /etc/nginx/conf.d/wok.conf to change
127.0.0.1 to 0.0.0.0 and then updating semanage rules:
(on Centos 7)
sudo systemctl stop wokd
sudo systemctl stop nginx
sudo sed -ri 's/127.0.0.1/0.0.0.0/g' /etc/nginx/conf.d/wok.conf
sudo semanage port -a -t http_port_t -p tcp 8001
sudo semanage port -a -t http_port_t -p tcp 8010
sudo semanage port -m -t http_port_t -p tcp 8000
sudo systemctl start wokd
Then after accessing from another machine I had to accept the SSL
certificates first, where it redirected me to
http://127.0.0.1:8010/login.html, which was confusing. Back after going
back to https://my-kimchi-host:8001 the login page successfully loaded.
I found this confusing and couldn't find any documentation or guide. I
think others may find this information useful. Should I post this to
the issue board for feedback?
Sincerely,
Jason
7 years
