-----Original Message----- From: Animesh Chaturvedi Sent: Thursday, March 21, 2013 2:56 PM To: dev@cloudstack.apache.org Cc: cloudstack-...@incubator.apache.org; Jessica Wang Subject: RE: [ACS41] Baremetal blockers
> -----Original Message----- > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] > Sent: Thursday, March 21, 2013 2:22 PM > To: dev@cloudstack.apache.org > Cc: cloudstack-...@incubator.apache.org; Jessica Wang > Subject: RE: [ACS41] Baremetal blockers > > > > >> > > > > >> > > I am checking if these can be reassigned. If it does not pan > > >> > > out by > > >> tomorrow I will propose to disable the feature for 4.1 release. > > >> > > > >> > I think that a decision is predicated on a more specific > > >> > statement of what we mean by "disable". > > >> > > >> Pinging on this again. I'm leaning towards agreement, but what > > >> *exactly* can we do to disable it and (at the same time) minimize > > >> the > > >> knock- on effect of the change required to disable it. > > > [Animesh>] There is no one available to pick up these defects in > > > time for > > 4.1 so we will disable the feature. Disable means Baremetal will be > > removed from componentContext.xml , the API and UI will not be > available. > > > > Are you sure that removing the plugin from componentContext.xml will > > remove it from the UI? (I'm not, that's why I'm asking) > [Animesh>] Yes, discussed with Alex and Jessica. [Animesh>] Will try out the change and submit a patch. Jessica anything else? [Jessica W] Nothing else except removing Baremetal from listHypervisors API response and listSupportedNetworkServices API response.
