The Bangalore CloudStack User Group meetup is planned for 5th February. This month’s focus is on CloudStack administrators and operators – scoping, deployment design, capacity planning, production experiences etc.
The agenda is still being worked on. If you wish to speak at the event, please drop us a line at http://www.meetup.com/CloudStack-Bangalore-Group/events/99690432/
If you wish to attend, please RSVP at http://www.meetup.com/CloudStack-Bangalore-Group/events/99690432/
Power packed event featuring speakers from Giles Sirett (CEO, ShapeBlue), Ravi Gururaj (VP-Cloud Platforms at Citrix Systems) and Shashank Likhite,Sr. Director, Product Engineering at SunGard Availability Services
Agenda:
10:00 – 10:30 – Registration & coffee
10:30 -11:00 – “key cloud trends for 2013” Giles Sirett, CEO, ShapeBlue
11:00 – 11:30 – “Citrix’s cloud vision for 2013” Ravi Gururaj, VP-Cloud Platforms at Citrix Systems
11:30 – 12:00 – “Building cloud for a fortune 500 MSP” Shashank Likhite,Sr. Director, Product Engineering at SunGard Availability Services
12:00 – 12:30 – panel discussion and Q&A
12:30 – 13:30 – Business networking lunch
Please RSVP at Cloud trends for 2013 – an executive briefing
A minimal CloudStack deployment has one zone, one pod and one cluster running with a single shared NFS primary storage. The shared storage hosts the virtual disks for all instances running on the same cluster.
Multiple instance of different types and workloads are hosted on the same cluster. Instances running disk bound workloads like database services compete with instances running CPU/Memory bound tasks like application services. This can lead to unpredictable IO performance as instances are competing for the same shared disk resources. As load increases on the storage server, disk performance on all instances start to degrade.
If you have one of these ASWC interfaces and have to get it working with a Honda City, 1729_Auto_Detect.pdf can help.
The interface (1729 harness) is the same as the Honda Fit as sold in the US. Thanks to the excellent support at Axxess for the detailed instruction.
We were counting the number of metrics graphing software we are using at work. Turns out we use a lot of them and each one has their own quirks (which is why we ended up running all them in the first place).
A nice short term goal would be to reduce the list to not more than 2 and finally only have our custom stackable grapher (based on collection3) be “the” graphing solution for network, hosts and application metrics.
Collection4 is already out, so a upgrade too is in order.