TimR26's Posts

Hello, I'm extremely new to Hyperic so please be gentle. I rebuilt our development network using vCloud Director and we created some routed Organizations (a couple for my clients and one management org for my catalogs). All orgs have vShield firewalls to prevent traffic flow to each other, and the external network that all the orgs sit on also has a firewall to prevent traffic flow to my management network (for security reasons) which I plan to put Hyperic on. My understanding (so far) about Hyperic is that it is a client based solution meaning the servers you want Hyperic to monitor will require an agent to be installed. Does this mean the server I'm trying to monitor needs to be able to "ping" the Hyperic server, or does Hyperic work much like how vCenter/vCOPS works with VMTools? If Hyperic needs to "ping" the agents then my options are: - install hyperic in each org and management them individually (extra overhead work) - install hyperic in my admin org and open the vShield firewalls to allow Hyperic to communicate with all agents in all orgs (potential security issue, but centralized Hyperic view) I'm hoping I don't have to do either of these options but I'm not really sure...some guidance would be great.

I'm running a vCloud Director Suite Enterprise 5.5 licensed cluster that is hosting our vCOPS vApp. When I license vCOPS, it activates it as the Advanced Version. According to this document (hxxp://www.vmware.com/products/vcloud-suite/compare) my vCloud Suite license should be activating vCOPS as the enterprise version, no? Something seems wrong here...thoughts anyone?

we are building a new development network and will leverage vcloud director. we are going to have a mgmt cluster and a resource cluster. the mgmt cluster will host all wire services (ad, dns, dhcp, file/print, etc), all vsphere services (vcenter, vcops, update manager, etc), and all vcloud services (vcd, vshield, etc). we will be creating a vcenter to manage the mgmt cluster and a vcenter to manage the resource cluster via vcd. my question is related to support. there will be situations that will require us to completely shut down the entire infrastructure due to some major data center upgrades over the next year. i would like to simplify the shutdown and power on procedures by introducing vapps in the mgmt cluster. my thought process is to group certain servers into vapps and define the power up timers on the vapp. for example i would create a vapp that contains all the wire services, another vapp for vcenter/sso/inventory services, a vapp for our sql servers, etc...this way when we create our power down/up procedures, we just need to specify the order of the vapps, and not the individual servers themselves. we can also ensure certain servers power up in the correct order. am i on the right track? is there a better solution?

Hello, Before my question, I'll give a bit of background info. We have a corp network, and we have a pre-prod network. Both on the same wire. The pre-prod network is really just another AD domain, using the same subnet, same vlan as corp. Pilot users will log into that domain with their corp machine and do pilot testing of new apps, etc. If an app passes testing and is ready to move to corp, the servers/devices, etc will simply join the corp domain. This is done in a vsphere cluster. We also have a test network. This is where I work. The test network is physically segregated from the corp/pre-prod network. Initial development on new projects, plus pre-patching, troubleshooting, enchancing of systems is done in this environment. Once initial development is complete, the next phase is pre-production for piloting. This is also done in a vsphere cluster. We want to use vcloud director because we're discovering that each project that comes in wants dedicated resources, etc so we figured that the "infrastructure as a service" capability that vcloud director provides will help us for so many reasons. so now we're turning into a service provider. I would like to join the corp/pre-prod network to the test network physically, and extend the vcloud director resource pool into the pre-prod network (essentially taking control of pre-prod). I would also like to be able to create a cloud of resources for a specific client (a chunk of servers to develop a new app for example) and be able to move that cloud into pre-prod, and eventually into the corp vsphere cluster. my question is this, if i have vcloud director resource pools for test and pre-prod, can I move a clients cloud resources (well, the VMs inside the cloud) into our corp vsphere cluster to be used in corp, or will the servers need to be rebuilt for corp? OR can I/should I add the corp vsphere cluster into the vcloud resource pool and simply move the cloud into the corp pool to give access to the corp network? Any thoughts would be great....I'm kinda stuck, so opinions from others can help me think on different ideas...