Hi Vyacheslav, Answering your questions:
1) Public IPs are chargeable resources for the majority of service providers, they are usually priced at around $5/months per IP. Therefore APS module should be able to price and account them. Another problem (based on our experience with other IaaS products) that in IaaS the customer wants to keep the IP – even when VM is removed. Think about scenario – the tenant creates a VM, then purchases public IP and assingns it to the VM, and then deletes the VM. The customer should keep the IP until explicitly decides to give it up. While we could demo without it, it is pretty much required for production. And I don’t see any way to implement first (and especially second) part of IP management scenario below without making public IP an APS resource. None of these concern private (fixed) IPs though. 2) UnmanagedVE resource is a server created under tenant (via nova boot command). OpenStack image is another resource (images). The goal of UnmanagedVe is to have an object to manage through PA UI; it is not required before any OpenStack resource will be visible/manageable through PA UI. The “image” resource is different – it is required to cover the “Windows 2008 server costs 10 cents/hour for the Operating system itself” price point – so this resource allows the provider to assign price to it. It is required for a provider to offer any non-free operating system images Just to make sure we are on the same page with ceilometer – we do not currently have any scenarios requiring calculation of resource usage with per-VM granularity. Only aggregated resources for the entire tenant are required for billing From: Openstack-aps-package-dev [mailto:openstack-aps-package-dev-bounces+moruga=parallels....@lists.launchpad.net] On Behalf Of Vyacheslav Vakhlyuev Sent: Thursday, April 10, 2014 2:50 AM To: [email protected] Subject: [Openstack-aps-package-dev] Questions regarding shared Resource schema Hi Andre & team, we have several questions from Mirantis side that we'd like to discuss. 1. As far as we know openstack doesn't allow allocating ip-pools without allocating VMs. Also it's not quite clear what is a purpose of weak/singular relation between provider "ip" and customer "ip". Could you please explain this part of the model in more details and describe its business value? 2. For the first draft of APS package UnmanagedVe will seriously increase complexity of the application endpoint itself and APS package. Also there may be some limitations in work of Ceilometer, which may cause improper calculation of resource usage. Just to ensure that we're on the same page - under UnamangedVe you mean an Openstack pre-created image (i.e. Fedora 19, Windows 2008), but with changeable hardware configuration. Is it correct? I believe we should drop it from the resource model until implementing prepaid sucsription with VPSes. -- Kind Regards, Vyacheslav Vakhlyuev Software Engineer Mirantis, Inc www.mirantis.com<http://www.mirantis.com> Skype: vahluev.vyacheslav
-- Mailing list: https://launchpad.net/~openstack-aps-package-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack-aps-package-dev More help : https://help.launchpad.net/ListHelp
