Johnathan02-15-2019 10:39 AM

1. 6.1.2 Installation

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

2. RE: 6.1.2 Installation

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

5. RE: 6.1.2 Installation

I currently run 4.2.5, but when I install any Windows zenpack higher than 2.6.12 to support my Server 2016 systems things start to go south. OID error etc. I'm going to be imaging the drive so I can go back, but I'll be trying this again shortly. I'll post here with my issues. :-)

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

2019-01-15 11:25:57,594 DEBUG zen.pbclientfactory: Lost connection to ::1:8789 - [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost.

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

So you are definitely getting responses from the device for those values. That should eliminate fundamental communications and kerberos issues.

You can also see lines with zen.RRDUtil in them that shows where data is actually stored away. I hope that you ARE seeing values for memory, paging and cpu for this device in your graphs?

I guess the next question is whether it should be collecting other stuff for this device? Has it managed to create Service components and Filesystem components? If not, then you wouldn't expect to see queries in this output to gather performance stats and we need to go back to why the modeler has failed.

Did you try running the modeler in debug against a specific device for a particular plugin? Try limiting it with --collect=zenoss.winrm.FileSystems . Redirect output to a file and see what you get there.

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

So you are definitely getting responses from the device for those values. That should eliminate fundamental communications and kerberos issues.

You can also see lines with zen.RRDUtil in them that shows where data is actually stored away. I hope that you ARE seeing values for memory, paging and cpu for this device in your graphs?

I guess the next question is whether it should be collecting other stuff for this device? Has it managed to create Service components and Filesystem components? If not, then you wouldn't expect to see queries in this output to gather performance stats and we need to go back to why the modeler has failed.

Did you try running the modeler in debug against a specific device for a particular plugin? Try limiting it with --collect=zenoss.winrm.FileSystems . Redirect output to a file and see what you get there.

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

17. RE: 6.1.2 Installation

If I add the user to the local administrators group on the 2016 server I get the components. I'm confused though, as this user has the proper access to parse these components on the 2008 boxes. I'm using the zenoss-lpu.ps1 script, same that is being applied to 2008.

So you are definitely getting responses from the device for those values. That should eliminate fundamental communications and kerberos issues.

You can also see lines with zen.RRDUtil in them that shows where data is actually stored away. I hope that you ARE seeing values for memory, paging and cpu for this device in your graphs?

I guess the next question is whether it should be collecting other stuff for this device? Has it managed to create Service components and Filesystem components? If not, then you wouldn't expect to see queries in this output to gather performance stats and we need to go back to why the modeler has failed.

Did you try running the modeler in debug against a specific device for a particular plugin? Try limiting it with --collect=zenoss.winrm.FileSystems . Redirect output to a file and see what you get there.

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

18. RE: 6.1.2 Installation

2019-01-15 14:00:16,485 WARNING zen.ZenModeler: The plugin zenoss.winrm.FileSystems returned no results.

I am suspecting that maybe the WinRm groups may have changed subtly in 2016?? Do you have another way to walk the queries for filesystems with WinRm and compare the query and the output between 2012 and 2016?

Zenoss ships a winrs command that you might try - here is one I have used in the past:

So you are definitely getting responses from the device for those values. That should eliminate fundamental communications and kerberos issues.

You can also see lines with zen.RRDUtil in them that shows where data is actually stored away. I hope that you ARE seeing values for memory, paging and cpu for this device in your graphs?

I guess the next question is whether it should be collecting other stuff for this device? Has it managed to create Service components and Filesystem components? If not, then you wouldn't expect to see queries in this output to gather performance stats and we need to go back to why the modeler has failed.

Did you try running the modeler in debug against a specific device for a particular plugin? Try limiting it with --collect=zenoss.winrm.FileSystems . Redirect output to a file and see what you get there.

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

Same results. What I have noticed is that if I spin up my previous Zenoss with the Windows zenpack 2.6.12 the modeler logs also show Modeler plugin zenoss.winrm.HardDisks returned no results. However that doesn't seem to generate an event.

One the latest Zenpack, I now see Modeler plugin zenoss.winrm.HardDisks returned no results as an event. Only for 2008r2, and within a 24 hours period this event will clear itself and come back sometimes 2-3 times.

2019-01-15 14:00:16,485 WARNING zen.ZenModeler: The plugin zenoss.winrm.FileSystems returned no results.

I am suspecting that maybe the WinRm groups may have changed subtly in 2016?? Do you have another way to walk the queries for filesystems with WinRm and compare the query and the output between 2012 and 2016?

Zenoss ships a winrs command that you might try - here is one I have used in the past:

So you are definitely getting responses from the device for those values. That should eliminate fundamental communications and kerberos issues.

You can also see lines with zen.RRDUtil in them that shows where data is actually stored away. I hope that you ARE seeing values for memory, paging and cpu for this device in your graphs?

I guess the next question is whether it should be collecting other stuff for this device? Has it managed to create Service components and Filesystem components? If not, then you wouldn't expect to see queries in this output to gather performance stats and we need to go back to why the modeler has failed.

Did you try running the modeler in debug against a specific device for a particular plugin? Try limiting it with --collect=zenoss.winrm.FileSystems . Redirect output to a file and see what you get there.

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

Same results. What I have noticed is that if I spin up my previous Zenoss with the Windows zenpack 2.6.12 the modeler logs also show Modeler plugin zenoss.winrm.HardDisks returned no results. However that doesn't seem to generate an event.

One the latest Zenpack, I now see Modeler plugin zenoss.winrm.HardDisks returned no results as an event. Only for 2008r2, and within a 24 hours period this event will clear itself and come back sometimes 2-3 times.

2019-01-15 14:00:16,485 WARNING zen.ZenModeler: The plugin zenoss.winrm.FileSystems returned no results.

I am suspecting that maybe the WinRm groups may have changed subtly in 2016?? Do you have another way to walk the queries for filesystems with WinRm and compare the query and the output between 2012 and 2016?

Zenoss ships a winrs command that you might try - here is one I have used in the past:

So you are definitely getting responses from the device for those values. That should eliminate fundamental communications and kerberos issues.

You can also see lines with zen.RRDUtil in them that shows where data is actually stored away. I hope that you ARE seeing values for memory, paging and cpu for this device in your graphs?

I guess the next question is whether it should be collecting other stuff for this device? Has it managed to create Service components and Filesystem components? If not, then you wouldn't expect to see queries in this output to gather performance stats and we need to go back to why the modeler has failed.

Did you try running the modeler in debug against a specific device for a particular plugin? Try limiting it with --collect=zenoss.winrm.FileSystems . Redirect output to a file and see what you get there.

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

21. RE: 6.1.2 Installation

I tried using your ansible tool but it's not working for me. New Centos 7 VM. Git cloned to /root/anisble-serviced-zenoss. Installed ansible. hosts file reads:[docker]vmzenoss01 lvm_dev=/dev/centos... rest of the file is left as-is

When I run ./setup I get an error under TASK [Gathering Facts]fatal: [vmzenoss01]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Permission denied (publickey, gssapi-keyex, gssapi-with-mic,password).", "unreachable": true.

I edited /etc/ansible/hosts and put my hostname in there just to see if that's the problem, but the error still occurs. Any ideas?

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something

22. RE: 6.1.2 Installation

I found the solution to my problem. I'm not familiar with anisble, and it wasn't setup correctly. You don't need to just install it, you need to configure it as well, before you'll be able to run the ansible-serviced-zenoss installation script. In my case, I needed to edit /etc/ansible/hosts, and set the ansible_ssh_pass and ansible_ssh_user before it would work correctly. Example /etc/anisble/hosts:

myservername ansible_ssh_pass=<root password> ansible_ssh_user=root

Then you can run ansible all -m ping to test ansible before running the ./setup script. I would suggest adding this to your instructions for those of us who are less experienced :-)

I tried using your ansible tool but it's not working for me. New Centos 7 VM. Git cloned to /root/anisble-serviced-zenoss. Installed ansible. hosts file reads:[docker]vmzenoss01 lvm_dev=/dev/centos... rest of the file is left as-is

When I run ./setup I get an error under TASK [Gathering Facts]fatal: [vmzenoss01]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Permission denied (publickey, gssapi-keyex, gssapi-with-mic,password).", "unreachable": true.

I edited /etc/ansible/hosts and put my hostname in there just to see if that's the problem, but the error still occurs. Any ideas?

That's my theory. They deploy as Docker containers but they don't provide docker-compose files for base configuration. Everything is hidden behind weird layers of complexity, you have to jump through hoops to get access to the downloads (seriously, you have to register and then wait for a human to approve your account before you can download the community edition?), and I saw posts from their staff saying that they either did or wanted to restrict public access to their Docker repos. After all that, you can only do the absolute most basic of the basics. The vast majority of the zenpacks require a subscription to run.

I'm looking at deploying a new physical box with 6.2.1 on it. I was actually hoping for 5.2 but the "getting started" email downloaded a 6.1.2 ISO. I used the link to take me to the documentation and that's where it all fell apart.Community Edition (Core) Installation Guide 6.2.1

So...what is it I'm supposed to do with this ISO? The documentation is absolutely garbage. All it talks about is installation on a virtual appliance. Is every version after 4.2 their attempt to push people to their paid cloud service or something