|
|
| Subject: | Virtual host names |
| Author: | Jan Garaj |
| Posted: | 2014-07-12 19:09 |
I have problem with virtualhosts:
https://hbase.zenosscc
https://opentsdb.zenosscc
https://zenoss5x.zenosscc
They serve Control Center (https://zenosscc), even all zenoss services work correctly.
Endpoint definition for zenossx5 is in /opt/serviced/templates/zenoss-core-5.0.0b1_521.json:
"Endpoints": [
{
"Name": "zproxy",
"Purpose": "export",
"Protocol": "tcp",
"PortNumber": 8080,
"VirtualAddress": "",
"Application": "zproxy",
"ApplicationTemplate": "",
"AddressConfig": {
"Port": 0,
"Protocol": ""
},
"VHosts": [
"zenoss5x"
]
},
Docker forwards port 8080 for this endpoint, so it's OK:
root@ip-172-31-36-54:~# docker ps -a | grep 1d9673e2
d1d9673e23ad ip-172-31-36-54:5000/322mfa8vrbco2mftgpqgis4i3/zenoss-core-testing:latest "/serviced/serviced About an hour ago Up About an hour 0.0.0.0:49153->8080/tcp b0wv2prk1t05pb20zie3qqx7w
Even http://zenoss5x.zenosscc:49153 redirects to https://zenoss5x.zenosscc:49153/zport/acl_users/cookieAuthHelper/login_f... (so zenoss works correctly) only https serve Control Center.
Maybe it is IP problem. I use VM - AWS EC2 instance, so I've deployed zenoss with private IP, but I'm accessing to zenoss via public IP. But also browser links "http://zenoss5x.zenosscc" on VM (zenoss5x.zenosscc is translated to private IP) sees Control Center. No errors/warnings in Zenoss logs (Control Center -> Logs).
So question is: how to setup virtualhosts correctly i.e. zenoss5x.zenosscc -> 0.0.0.0:49153.
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
| Subject: | The control center proxy |
| Author: | [Not Specified] |
| Posted: | 2014-07-17 08:53 |
The control center proxy service will only accept proxy connections on 443. Try https://zenoss5x.zenosscc and that should do the trick. Make sure you have configured your client host file according to the installation and deployment docs.
| Subject: | Thx Matt. |
| Author: | Jan Garaj |
| Posted: | 2014-07-17 11:03 |
Thx Matt.
Yes, I've setup my hosts file correctly (VM has been terminated, so it's doesn't work now):
54.76.144.35 zenosscc hbase.zenosscc opentsdb.zenosscc zenoss5x.zenosscc
But every "https domain" (zenosscc hbase.zenosscc opentsdb.zenosscc zenoss5x.zenosscc) shows only Control Center (no zenoss, no hbase, no opentsdb). The same problem was also in command line directly on VM (/etc/hosts was also configured).
Are you able to run Zenoss5b1 (core) as EC2 c3.2xlarge instance with default Ubuntu 14.04 AMI
I tried it 2 times :( My notes from installation (cmds from documentation): http://pastebin.com/7ZehwT9y
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
| Subject: | I give it up. I tried EC2 |
| Author: | Jan Garaj |
| Posted: | 2014-07-19 04:25 |
I give it up. I tried EC2 installation 2xmore. I've created chef recipe for single host EC2 installation:
https://github.com/jangaraj/zenoss/blob/master/chef/zenoss/recipes/zenos...
Chef deployment takes ~25minutes http://postimg.org/image/5ci3m43xb/
But https://hbase.zenosscc, https://opentsdb.zenosscc, https://zenoss5x.zenosscc serve always Control center http://zenosscc
I'll create bug.
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
| Subject: | Try the adding "--alias |
| Author: | [Not Specified] |
| Posted: | 2014-07-21 18:10 |
Try the adding "--alias zenosscc" to the command starting control center.
| Subject: | Mmaloney/Jplouis thanks. |
| Author: | Jan Garaj |
| Posted: | 2014-07-26 15:14 |
Mmaloney/Jplouis thanks.
My used workaround:
Define the Application port and protocol in the zproxy export section (8080 and tcp) in the service template (refer to Alpha 2 documentation if you are unsure on how to do this - there are examples for zentrap etc in the template as well)..
Disable HTTPS CGI support for Zope in the Zope service config or in the source template and restart or redeploy the app. This will disable the HTTPS absolute URI feature allowing you to use other ports beyond 443, thus any high port will work.
And hooray - zenoss was available on http://
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
| Subject: | Edit template: /opt/serviced |
| Author: | Jan Garaj |
| Posted: | 2014-09-15 14:50 |
Edit template: /opt/serviced/templates/zenoss-core-5*.json
Template for zope.conf is in this json file:
..... HTTPS_SERVER Foobar Server 1.0\n# HTTPS_PORT 443\n# \u003c/cgi-environment\u003e\n\n\u003ccgi-environment\u003e\n HTTPS ON\n\u003c/cgi-environment\u003e\n\n\ .....
Just change "HTTPS ON" -> "HTTPS OFF" and (re)deploy template.
Devops Monitoring Expert advice:
Dockerize/automate/monitor all the things.
DevOps stack:
Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform /
Elasticsearch
| Subject: | please help |
| Author: | [Not Specified] |
| Posted: | 2015-07-16 09:11 |
Define the Application port and protocol in the zproxy export section (8080 and tcp) in the service template (refer to Alpha 2 documentation if you are unsure on how to do this - there are examples for zentrap etc in the template as well).
how do you go about doing this i dont seen to find it
| < |
Previous How to configure Thresold to disk space in zenoss 4.2.4 |
Next Device/Devices template monitors interfaces |
> |