On Tue, Dec 2, 2014 at 9:40 AM, Akila Ravihansa Perera <raviha...@wso2.com> wrote:
> This is because Kubernetes cannot be treated as an IaaS level entity. > > What if we're to create a hybrid cloud deployment with kubernetes + > OpenStack + EC2 using a single deployment policy? > IMO, we have to leave room for that kind of support in the future. > This should be supported via an abstraction in cloud controller. That is why we validate partitions at Autoscaler, by calling a CC service call. Is there any reason that we cannot think the Kubernetes host not as an IaaS entity? Thanks. > Thanks. > On 1 Dec 2014 14:06, "Imesh Gunaratne" <im...@apache.org> wrote: > >> +1 May be there was a reason to do this at the initial stage. >> >> Thanks >> >> On Mon, Dec 1, 2014 at 11:50 AM, Lahiru Sandaruwan <lahi...@wso2.com> >> wrote: >> >>> Hi all, >>> >>> Currently we do $subject. IMO we should have include this in Cloud >>> Controller. Because that is the place we are keeping IaaS related >>> information and the control of the IaaS objects. >>> >>> Wdyt? >>> >>> Thanks. >>> >>> -- >>> -- >>> Lahiru Sandaruwan >>> Committer and PMC member, Apache Stratos, >>> Senior Software Engineer, >>> WSO2 Inc., http://wso2.com >>> lean.enterprise.middleware >>> >>> email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ >>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146 >>> >>> >> >> >> -- >> Imesh Gunaratne >> >> Technical Lead, WSO2 >> Committer & PMC Member, Apache Stratos >> > -- -- Lahiru Sandaruwan Committer and PMC member, Apache Stratos, Senior Software Engineer, WSO2 Inc., http://wso2.com lean.enterprise.middleware email: lahi...@wso2.com blog: http://lahiruwrites.blogspot.com/ linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
