http://stage.vambenepe.com/archives/1096 IT management in a changing IT world Tue, 09 Mar 2010 22:10:17 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://stage.vambenepe.com/archives/1096#comment-99203 William Vambenepe Tue, 10 Nov 2009 20:00:48 +0000 http://stage.vambenepe.com/?p=1096#comment-99203 William Louth: you're right, metering+billing should also be there. Oversight on my part. I like the way AWS has been thinking out of the box about different ways to charge users, including ways that map directly to the consumed resources. William Louth: you’re right, metering+billing should also be there. Oversight on my part. I like the way AWS has been thinking out of the box about different ways to charge users, including ways that map directly to the consumed resources.

]]> http://stage.vambenepe.com/archives/1096#comment-99195 William Vambenepe — Enumeration of PaaS container types Tue, 10 Nov 2009 17:02:45 +0000 http://stage.vambenepe.com/?p=1096#comment-99195 [...] next post will list desired characteristics of the PaaS environment (meta-capabilities that go across all the [...] [...] next post will list desired characteristics of the PaaS environment (meta-capabilities that go across all the [...]

]]> http://stage.vambenepe.com/archives/1096#comment-99190 William Louth Tue, 10 Nov 2009 13:12:58 +0000 http://stage.vambenepe.com/?p=1096#comment-99190 You seem to be ignoring billing and resource metering (note: metering != billing) which is required by one or more services in support of the "cloud" like qualities hinted at including scalability, reliability and work migration. The container needs to expose runtime resource meters. The cloud services interactions need to expose metering usage. All in a uniform way and correlated with component activity work flows - with flows having multiple cost (chargeback) structures supporting billing/metering from multiple perspectives both operational & non-operational. You seem to be ignoring billing and resource metering (note: metering != billing) which is required by one or more services in support of the “cloud” like qualities hinted at including scalability, reliability and work migration. The container needs to expose runtime resource meters. The cloud services interactions need to expose metering usage. All in a uniform way and correlated with component activity work flows – with flows having multiple cost (chargeback) structures supporting billing/metering from multiple perspectives both operational & non-operational.

]]>