I put it on the Community page http://goo.gl/4V94A
On 4/26/12 11:57 AM, "Marlon Davids" <mdav...@umbee.co.uk> wrote: >Brilliant, thanks Chiradeep, > > > >Unfortunately I don't see the attachment? > > > >>There's a few approaches to the "monitoring VMs" question. > >A. Install agents on the VMs and get the agents to phone back to your >monitoring server. > >B. Add a dedicated monitoring VLAN per tenant and get the tenant VMs to >be dual homed on the original isolated VLAN and the monitoring VLAN C. >Like B, but the VLAN is shared among tenants. There is no isolation >guarantees in this case. > >D. Create a monitoring VLAN. Every tenant creates (or admin creates for > >them) a new routing VM (can be any old Linux distro) that has an >interface on both the monitoring VLAN and the tenant's VLAN. Tenant VMs >add static routes to the monitoring server to go via the new routing VM. > > > >See attached PDF > >You can use (D) to add any special networking service. For example you >can add a site-to-site VPN using the additional routing VM (the >monitoring VLAN becomes a VLAN with public Ips). > > >Kind Regards, >Marlon Davids > >.......................................................................... >.................... >P: +44 (0)845 619 7444 | E: >mdav...@umbee.co.uk<mailto:mdav...@umbee.co.uk> >.......................................................................... >.................... >W: www.umbee.co.uk<http://www.umbee.co.uk/> Managed Hosting Specialists. >.......................................................................... >.................... >Umbee Ltd, TMS House, Cray Avenue, Orpington, Kent, BR5 3QB >Company Registration Number. 06954604. VAT Registration Number 977446172 > >This e-mail and the information it contains are confidential. >If you have received this e-mail in error please notify the sender >immediately. >You should not copy it for any purpose or disclose its contents to any >other person. >The contents of this e-mail do not necessarily reflect the views of the >company. >E&OE > >P Please consider the environment before printing this email > > > >-----Original Message----- >From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] >Sent: 26 April 2012 18:19 >To: cloudstack-dev@incubator.apache.org >Subject: Re: Cloudstack Questions > > > >There's a few approaches to the "monitoring VMs" question. > >A. Install agents on the VMs and get the agents to phone back to your >monitoring server. > >B. Add a dedicated monitoring VLAN per tenant and get the tenant VMs to >be dual homed on the original isolated VLAN and the monitoring VLAN C. >Like B, but the VLAN is shared among tenants. There is no isolation >guarantees in this case. > >D. Create a monitoring VLAN. Every tenant creates (or admin creates for > >them) a new routing VM (can be any old Linux distro) that has an >interface on both the monitoring VLAN and the tenant's VLAN. Tenant VMs >add static routes to the monitoring server to go via the new routing VM. > > > >See attached PDF > >You can use (D) to add any special networking service. For example you >can add a site-to-site VPN using the additional routing VM (the >monitoring VLAN becomes a VLAN with public Ips). > > > > > >On 4/25/12 4:49 AM, "David Nalley" <da...@gnsa.us<mailto:da...@gnsa.us>> >wrote: > > > >>Welcome Marlon > >> > >>> > >>> 1) Will NFS be phased out for secondary storage in the future? > >> > >>I don't think this is going to happen - and if it is, certainly not any > >>time soon. > >> > >>> 2) How do we monitor VM's that are in Cloudstack when they are in an > >>>isolated VLAN does anyone have a clever workaround? > >> > >>I dont have a good answer for this at the moment > >> > >>> 3) Has anyone developed a script for parsing and alerting on warning > >>>events in the management Log yet? > >>> > >> > >>So you should check out Zenoss's CloudStack ZenPack [1] they poll the > >>listEvents API call and parse that for events. > >>Alternatively, you could configure log4j to send logs of warning or > >>higher to syslog - and thus on to some central logging facility like > >>logstash, greylog, or splunk. > >> > >> > >> > >>[1] https://github.com/zenoss/ZenPacks.zenoss.CloudStack > >
