On Thu, Mar 21, 2013 at 5:04 PM, Animesh Chaturvedi <animesh.chaturv...@citrix.com> wrote: > > >> -----Original Message----- >> From: Chip Childers [mailto:chip.child...@sungard.com] >> Sent: Thursday, March 21, 2013 1:09 PM >> To: cloudstack-...@incubator.apache.org >> Subject: Re: [ACS41] Baremetal blockers >> >> On Wed, Mar 20, 2013 at 09:01:45PM -0400, Chip Childers wrote: >> > On Wed, Mar 20, 2013 at 02:41:01PM -0700, Animesh Chaturvedi wrote: >> > > We have 1 blocker and 4 critical defects on baremetal >> > > >> > > CLOUDSTACK-1610 Baremetal API addBaremetalPxeKickStartServer fail >> to prepare PXE server causing create instance with Kickstart style image to >> fail >> > > >> > > CLOUDSTACK-1440 Baremetal - Destroy VM fail due to >> com.cloud.exception.OperationTimedoutException >> > > CLOUDSTACK-1614 Baremetal - Reboot VM fail >> > > CLOUDSTACK-1618 Baremetal - Stop VM fail >> > > CLOUDSTACK-1619 Baremetal - Restore/reset VM fail with >> java.lang.NullPointerException >> > > >> > > 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)
